Home
last modified time | relevance | path

Searched refs:OKAY (Results 1 – 12 of 12) sorted by relevance

/system/core/fastboot/fuzzy_fastboot/
Dextensions.h39 enum Expect { OKAY = 0, FAIL, DATA }; enumerator
42 {"okay", OKAY},
48 {OKAY, "okay"},
Dextensions.cpp180 if (packed_test.expect == OKAY && in ExtractPacked()
DREADME.md197 …OKAY` response, or be encoded in `INFO` responses. Thus, the parser attribute is used to specify a…
Dmain.cpp1697 if (test.expect == extension::OKAY) { // only testing the success case in GenerateXmlTests()
/system/core/fastboot/device/
Dcommands.cpp147 return device->WriteStatus(FastbootResult::OKAY, "Erasing succeeded"); in EraseHandler()
167 return device->WriteStatus(FastbootResult::OKAY, ret.message); in OemCmdHandler()
191 return device->WriteStatus(FastbootResult::OKAY, ""); in DownloadHandler()
212 return device->WriteStatus(FastbootResult::OKAY, "Flashing succeeded"); in FlashHandler()
248 return device->WriteStatus(FastbootResult::OKAY, ""); in SetActiveHandler()
254 auto result = device->WriteStatus(FastbootResult::OKAY, "Shutting down"); in ShutDownHandler()
262 auto result = device->WriteStatus(FastbootResult::OKAY, "Rebooting"); in RebootHandler()
270 auto result = device->WriteStatus(FastbootResult::OKAY, "Rebooting bootloader"); in RebootBootloaderHandler()
278 auto result = device->WriteStatus(FastbootResult::OKAY, "Rebooting fastboot"); in RebootFastbootHandler()
314 status = device->WriteStatus(FastbootResult::OKAY, "Rebooting to recovery"); in RebootRecoveryHandler()
[all …]
Dcommands.h27 OKAY, enumerator
Dfastboot_device.cpp159 return WriteStatus(FastbootResult::OKAY, message); in WriteOkay()
/system/core/adb/
DOVERVIEW.TXT100 1. For success, the 4-byte "OKAY" string
106 Note that the connection is still alive after an OKAY, which allows the
107 client to make other requests. But in certain cases, an OKAY will even
112 the "OKAY" answer, all further requests made by the client will go
DSYNC.TXT15 "OKAY" or "FAIL" as per usual.
68 request (but not to chunk requests) with an "OKAY" sync response (length can
DSERVICES.TXT19 After the OKAY, this is followed by a 4-byte hex len,
43 <serial-number>. After the OKAY response, every client request will
201 After the OKAY, the service sends 16-byte binary structure
Dprotocol.txt281 "OKAY" response is sent, otherwise a "FAIL" message is returned. Once
285 server: "OKAY"
/system/core/fastboot/
DREADME.md31 The first four bytes of the response are "OKAY", "FAIL", "DATA",
43 c. OKAY -> the requested command completed successfully. Go to #5
57 The first four bytes of the response are "OKAY", "FAIL", or "INFO".
65 c. OKAY -> success. Go to #5
86 Client: "OKAY" success
92 "OKAY" indicate success
114 OKAY response. If the variable is unknown, the bootloader
119 should return an empty OKAY response for unknown
135 a single packet starting with "OKAY". Clients
433 0x03 0x00 0x00 0x03 OKAY
[all …]