andmoreyer.blogg.se - Fastboot unknown command oem

DATA -> the requested command is ready for the data phase.

OKAY -> the requested command completed successfully. The remaining 252 bytes of the response (if present) provide a textual failure message to present to the user.

Payload is expected to be NULL terminated.Ĭ. The payload is printed as-is with no newline at the end. It differs from info in that no formatting is applied. They should be displayed and then step #2 repeats. TEXT -> the remaining 252 bytes are arbitrary. The print format is: "(bootloader) " + InfoMessagePayload + ‘\n’ī. INFO -> the remaining 252 bytes are an informative message (providing progress or diagnostic messages). Additional bytes may contain an (ascii) informative message.Ī. The first four bytes of the response are “OKAY”, “FAIL”, “DATA”, “INFO” or “TEXT”. Host sends a command, which is an ascii string in a single packet no greater than 4096 bytes.Ĭlient response with a single packet no greater than 256 bytes.

Fastboot data is wrapped in a simple protocol see below for details.

Device will act as the server, fastboot will be the client.

The protocol is entirely host-driven and synchronous (unlike the multi-channel, bi-directional, asynchronous ADB protocol).

Max packet size must be 64 bytes for full-speed, 512 bytes for high-speed and 1024 bytes for Super Speed USB.

Two bulk endpoints (in, out) are required.

It is designed to be very straightforward to implement, to allow it to be used across a wide range of devices and from hosts running Linux, macOS, or Windows. The fastboot protocol is a mechanism for communicating with bootloaders over USB or ethernet.