Fastboot: Command

: Writes a specific image file (like recovery.img ) to a designated partition.

| Requirement | Description | |-------------|-------------| | | Included in Android SDK Platform-Tools (Windows, macOS, Linux) or standalone package. | | Device state | Device booted into bootloader mode (often via adb reboot bootloader or hardware key combo). | | Driver (Windows) | Google USB Driver or OEM-specific bootloader driver. | | Unlocked bootloader | Most non‑OEM operations (flashing, erasing) require an unlocked bootloader . | | USB connection | Direct USB 2.0/3.0 connection (avoid hubs). |

If your phone is on and connected to your PC, run: adb reboot bootloader 3. Essential Fastboot Commands Reference fastboot command

If you are stuck in a bootloop or selling the device, you can wipe user data via Fastboot.

: Lists all connected devices currently in fastboot mode. : Writes a specific image file (like recovery

| Error Message | Likely Cause | Solution | |---------------|--------------|----------| | < waiting for any device> | No device in fastboot mode / driver issue | Check fastboot devices ; reinstall driver; try different USB port. | | FAILED (remote: Command not allowed) | Bootloader locked | Unlock bootloader first ( fastboot flashing unlock ). | | FAILED (remote: partition table doesn't exist) | Wrong partition name | Use fastboot getvar all to list valid partitions. | | cannot load 'image.img' | Missing file or wrong path | Provide absolute path or ensure file is in working directory. | | remote: flash write failure | Partition size mismatch or corrupted image | Verify image checksum; ensure correct firmware variant. | | Slot Unbootable | A/B slot invalid | Use fastboot set_active other and reflash. |

You must enable "OEM Unlocking" in your device's Developer Options before most commands will work. 2. How to Enter Fastboot Mode | | Driver (Windows) | Google USB Driver

To verify a device’s fastboot health and readiness for flashing: