Fastboot Unlocking Guide for Android in 2026
Complete 2026 fastboot unlocking guide: every unlock command, driver setup, device-not-detected fixes and slot checks. Free Windows tool.
Everything the fastboot unlock flow actually involves: the correct command for each OEM, why the device disappears from fastboot devices, and how to verify the slot state afterwards.
What the Fastboot Guide — Commands & Fixes covers
Every Unlock Verb — Covers fastboot flashing unlock, flashing unlock_critical and the legacy fastboot oem unlock.
Mode Entry Per Brand — Key combinations and adb commands to reach the bootloader on Pixel, Xiaomi, OnePlus, Motorola and Sony.
Driver Troubleshooting — Resolves the classic fastboot devices empty list caused by a missing Google USB or OEM driver.
Slot & State Checks — Reads current-slot, unlocked flag and verified boot state so you flash to the right slot.
Step-by-step: how to do it with FRPB
- 1Install platform-tools and the fastboot driver: FRPB bundles Google platform-tools and installs the correct USB driver for the connected chipset, so adb and fastboot are on PATH without a manual SDK download.
- 2Confirm the device is visible to fastboot: Run fastboot devices before anything else. An empty list means driver or cable, not a broken device — FRPB reports the USB VID/PID it sees to make that distinction obvious.
- 3Read the current bootloader state: Check the unlock flag, current slot and verified boot state so you know what you are changing and which slot the boot images belong to.
- 4Run the unlock command for your OEM: Use fastboot flashing unlock on 2015-and-later devices, flashing unlock_critical where the vendor requires it, or the legacy fastboot oem unlock on older hardware.
- 5Verify, then flash: Re-read the unlock flag after the reboot, confirm slot A or B, then flash boot, recovery or a full firmware package with checksum validation.
Frequently asked questions
What is the difference between fastboot flashing unlock and fastboot oem unlock? fastboot flashing unlock is the standardised Android command introduced for devices launching with Android 6 and later. fastboot oem unlock is the older vendor-specific command still used by some legacy handsets. Using the wrong one returns a FAILED (remote: unknown command) response rather than damaging the device.
Why does fastboot devices show nothing? Almost always a driver problem. Windows needs the Google USB Driver or the OEM's fastboot driver bound to the device in bootloader mode — the adb driver used in normal Android mode will not match. A charge-only USB cable and a USB 3 hub are the next most common causes.
Do I need fastboot to unlock every Android phone? No. Samsung Galaxy devices use Download Mode with Odin-protocol tooling, MediaTek devices often use BROM mode, and Qualcomm devices can use EDL 9008. fastboot covers Pixel, Xiaomi, OnePlus, Motorola, Nothing, Sony and most Qualcomm reference hardware.
What does the FAILED (remote: unlock not allowed) error mean? The bootloader rejected the command because OEM unlocking is disabled in Developer Options, the device is carrier-locked, or the OEM requires an online approval step (Xiaomi's Mi Unlock waiting period is the common example). No local tool can override that decision.
Is fastboot safe to use? The read-only commands are safe. fastboot flash writes partitions and fastboot erase wipes them, so a wrong partition name or a mismatched firmware build can leave the device unbootable. FRPB validates the image checksum and the target slot before it writes anything.
Does unlocking the bootloader with Fastboot erase personal data? Yes. Under standard Android security architecture, executing bootloader unlock verbs (e.g. fastboot flashing unlock or fastboot oem unlock) triggers an automatic cryptographic wipe of the user data partition (userdata / metadata) to protect owner encryption keys. Read-only commands such as fastboot devices and fastboot getvar all do not erase or modify data.
Is the FRPB tool safe and legal to use?
FRPB is built strictly for authorised device owners and licensed repair professionals. Always confirm you own the handset — or hold explicit written permission from its owner — before running any recovery or unlock module.
Everything runs offline over a local USB connection. The installers are code-signed and adware-free, so you can trust exactly what runs on your machine.