Complete Fastboot & ADB Flashing Guide for Android
Complete guide to flashing Android devices using Google Fastboot and ADB platform tools. Covers bootloader unlocking, switching to fastbootd for Android 10+ dynamic partitions (super.img), and modern GKI partition flashing.
Pre-Flight Checklist
Complete ALL items before proceeding. Skipping any step increases the risk of bricking your device.
Guide Steps
Download the official Android SDK Platform-Tools ZIP from Google and extract it to a simple location such as C:\platform-tools.
Open a Command Prompt or PowerShell window in that folder, or add the folder to your system PATH environment variable, then verify the installation:
You should see a version string (e.g., fastboot version 35.0.1). Always use modern binaries so dynamic partition commands work properly.
Before you can flash images via Fastboot, your phone bootloader must be unlocked:
- On your phone, open Settings → About Phone and tap Build Number 7 times to enable Developer Options.
- Go to Settings → System → Developer Options.
- Enable OEM Unlocking and USB Debugging.
You can enter bootloader mode using either ADB while Android is running, or physical hardware buttons:
Method A — via ADB command (phone powered ON with USB debugging):
Method B — via hardware keys (phone powered OFF):
- Google Pixel / Motorola / Xiaomi: Hold
Power + Volume Downuntil the Fastboot screen appears. - OnePlus: Hold
Power + Volume Up + Volume Down.
Verify your computer recognizes the connected device:
You should see your phone serial number followed by fastboot. If the list is empty, update your Google USB Drivers in Device Manager.
If your bootloader is locked, run the official unlock command in your terminal while in fastboot mode:
For older legacy devices (pre-2016), the command was fastboot oem unlock.
A confirmation screen will appear on your phone. Use the volume keys to highlight Unlock the bootloader and press the Power key to confirm. This permanently erases all personal files on the device.
Modern Android devices group system partitions (system, vendor, product, system_ext, odm) inside a single dynamic container called super. You cannot flash these partitions from standard bootloader fastboot.
To flash dynamic partitions, reboot your device into userspace fastbootd:
Your phone will restart into a recovery-based interface displaying the word fastbootd. Now you can flash logical partitions directly.
boot, init_boot, vendor_boot) can be flashed in standard bootloader mode. Logical partitions (system, product, vendor) must be flashed in fastbootd.Option A — Automated Factory Image (Google Pixel & Factory Packages):
Extract the full factory archive and run the official flashing script:
Option B — Flashing Core Boot Partitions (Kernel, Recovery, Root):
Option C — Flashing Logical Partitions in fastbootd:
If you are performing a clean system restoration or switching ROMs, format user data:
Once flashing is complete, reboot your phone back into Android:
The first boot will take several minutes while Android rebuilds runtime caches. Keep the phone connected until the initial welcome setup screen appears.
Congratulations! Flash Successful!
You've successfully completed all steps. Your device should now be running the new firmware. If it's booting normally — you're done! Check the troubleshooting section below if you encounter any issues.
Troubleshooting & FAQ
Common errors and their solutions. Read this before asking for help.
This happens on devices running Android 10 or newer when you try to flash system, vendor, or product from standard bootloader Fastboot.
- Those partitions are now dynamic logical partitions stored inside the
supercontainer. - Run the command:
fastboot reboot fastbootto switch into userspace fastboot (fastbootd). - Once your phone shows the fastbootd menu on screen, re-run your flash command. It will write successfully.
If fastboot devices returns a blank line:
- Open Windows Device Manager with the phone connected in Fastboot mode.
- Look under "Other devices" for an entry with a yellow exclamation mark (often labeled "Android").
- Right-click → Update driver → Browse my computer → Let me pick from a list of available drivers on my computer.
- Select "Android Device" and choose "Android Bootloader Interface" from Google.
- Also verify you are using a direct motherboard USB port, not an external hub.
Modern Android phones use seamless update slots (Slot A and Slot B). Bootloader commands like fastboot flash boot boot.img automatically write to the currently active slot.
- To check your current active slot:
fastboot getvar current-slot - To manually flash both slots:
fastboot flash --slot=all boot boot.img(or flash specifically toboot_aandboot_b) - To switch active slots:
fastboot set_active aorfastboot set_active b
Starting with Android 13 and the Generic Kernel Image (GKI) architecture, the ramdisk is separated from the kernel:
- Root solutions (such as Magisk or KernelSU) and custom ramdisks on devices launched with Android 13+ are flashed to init_boot:
fastboot flash init_boot init_boot.img - On devices launched with Android 12 or older, root continues to be patched in the standard boot partition:
fastboot flash boot boot.img - Custom recoveries (like TWRP) on newer partition schemes are frequently flashed to vendor_boot:
fastboot flash vendor_boot vendor_boot.img
Yes, but ONLY after completely flashing 100% official stock factory firmware on all slots.
Prioritize our guides in your Google search results.
No comments yet. Be the first to share your experience with this guide!