📱 Flash Tool Guides

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.

Difficulty: 🟡 Intermediate
Read time: 9 min
Updated: November 15, 2026
Tool Version: v35.0.1+ (Platform-Tools)
Medium Risk
🪟 Windows 🍎 macOS 🐧 Linux
Verified Working: November 4, 2026

Pre-Flight Checklist

Complete ALL items before proceeding. Skipping any step increases the risk of bricking your device.

Requirements met 0 / 6

Guide Steps

Guide Progress
0/7 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:

fastboot --version

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:

  1. On your phone, open Settings → About Phone and tap Build Number 7 times to enable Developer Options.
  2. Go to Settings → System → Developer Options.
  3. Enable OEM Unlocking and USB Debugging.
⚠️ If OEM Unlocking is grayed out, your phone may be carrier-locked or require an active internet connection to verify OEM eligibility.

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):

adb reboot bootloader

Method B — via hardware keys (phone powered OFF):

  • Google Pixel / Motorola / Xiaomi: Hold Power + Volume Down until the Fastboot screen appears.
  • OnePlus: Hold Power + Volume Up + Volume Down.

Verify your computer recognizes the connected device:

fastboot devices

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:

fastboot flashing unlock

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:

fastboot reboot fastboot

Your phone will restart into a recovery-based interface displaying the word fastbootd. Now you can flash logical partitions directly.

💡 Boot partitions (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:

# Windows: flash-all.bat # Linux / macOS: ./flash-all.sh

Option B — Flashing Core Boot Partitions (Kernel, Recovery, Root):

# Android 12 and older standard boot: fastboot flash boot boot.img # Android 13+ GKI (Generic Kernel Image) root/kernel: fastboot flash init_boot init_boot.img # Custom recovery or vendor ramdisk: fastboot flash vendor_boot vendor_boot.img

Option C — Flashing Logical Partitions in fastbootd:

fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash product product.img

If you are performing a clean system restoration or switching ROMs, format user data:

fastboot -w

Once flashing is complete, reboot your phone back into Android:

fastboot reboot

The first boot will take several minutes while Android rebuilds runtime caches. Keep the phone connected until the initial welcome setup screen appears.

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.

  1. Those partitions are now dynamic logical partitions stored inside the super container.
  2. Run the command: fastboot reboot fastboot to switch into userspace fastboot (fastbootd).
  3. 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:

  1. Open Windows Device Manager with the phone connected in Fastboot mode.
  2. Look under "Other devices" for an entry with a yellow exclamation mark (often labeled "Android").
  3. Right-click → Update driver → Browse my computer → Let me pick from a list of available drivers on my computer.
  4. Select "Android Device" and choose "Android Bootloader Interface" from Google.
  5. 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 to boot_a and boot_b)
  • To switch active slots: fastboot set_active a or fastboot 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.

🚫 Never re-lock with custom binaries: If you re-lock the bootloader while running a custom ROM, modified boot image, or custom recovery, the phone's cryptographic verification will fail on the next boot, causing a hard brick ("Your device is corrupt and cannot boot").
Never miss a fix.

Prioritize our guides in your Google search results.

Set as Preferred

No comments yet. Be the first to share your experience with this guide!

Leave a Comment —

Your email address will not be published. Required fields are marked *