Fastboot Protocol Complete Guide: Definition, Commands, and Implementation

Fastboot is a protocol for communicating with the bootloader via USB connection. It is designed to be easily implementable and works across Linux, Windows, and macOS platforms. Fastboot provides a lower-level USB-based method for updating file systems in Android systems compared to recovery mode.

The Android development package includes the fastboot.exe tool for communicating with Android devices, primarily performing operations such as partition image flashing, partition erasing, device rebooting, and retrieving device status information. When interacting with Android systems via the fastboot protocol, the Android device needs to boot into bootloader mode, where only basic hardware initialization occurs, including buttons, USB, storage system, and display modules, to support partition image writing and system boot mode switching.

Entering Fastboot Mode:

There are two ways to enter fastboot mode: 1) Through key combinations while the device is powered off; 2) Through ADB commands after the Android system has booted. The command adb reboot bootloader passes the boot mode as a parameter to Linux's boot process. After key detection completes, the system checks if a boot mode parameter was passed; if present, it overrides the previous key detection setting.

When the final boot mode is FASTBOOT_MODE , the system enters the fastboot mode startup process, which primarily completes USB device initialization, starts the fastboot command processing thread, registers fastboot command handlers, displays the fastboot menu, and initializes menu button detection programs.

Common Fastboot Commands:

Fastboot command format: fastboot [<option>] <command>

Common commands include:

fastboot erase boot - Erase boot partition

fastboot flash boot path/boot.img - Flash boot partition

fastboot update update.zip - Batch flashing (packages required partitions into update.zip)

fastboot reboot - Reboot device

fastboot getvar version:version-bootloader - Get bootloader version

USB Transfer Requirements:

Two endpoints: one input and one output

Full-speed USB: maximum packet size 64 bytes

High-speed USB: maximum packet size 512 bytes

Super-speed USB: maximum packet size 1024 bytes

Protocol is entirely host-driven and synchronous, unlike the multi-channel, bidirectional, asynchronous ADB protocol

Transfer Process:

Step 1: Host sends a command (ASCII string in a single packet not exceeding 64 bytes) Step 2: Client responds with a single packet not exceeding 64 bytes, starting with "OKAY", "FAIL", "DATA", or "INFO" Step 3: Data phase - host or client sends specified data size Step 4: Client responds with a single packet Step 5: Command execution completes

Fastboot provides high system permissions for image flashing, erasing, and device information queries. Compared to other flashing methods, it offers convenient and flexible operation but has the disadvantage of complex unlocking requirements. Additionally, fastboot runs in the bootloader, so for blank devices, a small system must first be flashed via low-level USB burning before fastboot can be used.