Fix Android Stuck in Fastboot Mode

If your Android phone is stuck on the fastboot screen and won’t boot normally, the fix is usually to exit fastboot with a simple command, force a reboot, or reflash the correct firmware. This article walks you through every working method, from the quickest key combination to the more advanced command-line fixes, and explains why the problem happens in the first place.

What Fastboot Mode Actually Is

Fastboot is a low-level protocol built into most Android devices, used by developers and repair technicians to flash partitions, unlock bootloaders, and install custom recoveries. When you see the fastboot screen — typically a black background with an Android robot and text like “FASTBOOT MODE” or “fastboot mode” — the phone’s normal operating system is not loaded. Instead, the bootloader is running a minimal environment that waits for commands from a computer over USB.

Because fastboot runs before Android starts, it is separate from the recovery mode you access with a different button combo. Many users confuse the two, but recovery (often labeled “Recovery Mode”) is for factory resets and OTA updates, while fastboot is for flashing. Knowing which one you are in matters, because the exit commands are different.

Why Phones Get Stuck in Fastboot

There are several common causes, and the right fix depends on which one applies to you:

Accidental button press: Holding Volume Down + Power for too long during a reboot can trigger fastboot.
Failed OTA or system update: A partially installed update can leave the bootloader waiting for a flash that never completes.
Corrupted boot image: If the boot partition is damaged, the device may fall back to fastboot as a safe state.
Unlocked bootloader with missing OS: After unlocking, some devices wipe data and if the OS is absent, they boot straight to fastboot.
Bad USB connection during a flash: A cable that disconnects mid-flash can leave the bootloader in a waiting state.

Understanding the cause helps you choose between a simple reboot and a full firmware reflash. If the phone entered fastboot by accident, a forced restart usually works. If it happened after an update or flash, you likely need to reflash the stock firmware.

Quick Fix: Force Reboot Your Phone

The first thing to try is a forced restart, which clears the temporary state without erasing data. The exact button combo varies by manufacturer, but these are the most common:

Press and hold the Power button for 10–15 seconds until the screen goes black and the device restarts.
If that doesn’t work, press and hold Power + Volume Down for 10–15 seconds.
If the screen shows a menu with “Start” or “Restart Bootloader”, use the volume keys to highlight Start and press Power to select it.
For Samsung devices, press and hold Power + Volume Down for more than 7 seconds to force a reboot from Download Mode.

If the phone vibrates or the screen flashes but returns to fastboot, the bootloader is likely waiting for a command rather than being stuck. In that case, move on to the command-line method.

Exit Fastboot with a Computer (ADB & Fastboot Commands)

If a forced reboot doesn’t work, you need a computer with the Android SDK platform-tools installed. These tools include the fastboot command, which can tell the bootloader to reboot normally. Here’s the step-by-step process:

Install platform-tools: Download the official Android SDK Platform-Tools from the Android developer website and extract the folder. On Windows, you’ll use fastboot.exe; on macOS/Linux, the command is ./fastboot.
Enable USB debugging (if possible): If your phone is stuck in fastboot, you can’t enable it now, but if you had it enabled before, the fastboot commands will still work. If not, you may need to use the device’s own menu to select “Restart Bootloader” or “Start” first.
Connect the phone to your computer with a USB cable. Use a data cable, not a charge-only one.
Open a terminal/command prompt in the platform-tools folder.
Check device detection: Type fastboot devices. If you see a device ID (like 1234567890ABCDEF fastboot), the phone is recognized.
Send the reboot command: Type fastboot reboot and press Enter. The phone should exit fastboot and boot normally.
If fastboot reboot doesn’t work, try fastboot continue, which tells the bootloader to continue a previously interrupted boot.

If the device is not recognized, install the correct USB drivers for your phone brand from the manufacturer’s website, and try a different USB port (preferably a USB 2.0 port on the back of a desktop).

When to Reflash the Stock Firmware

If the phone is stuck because the system partition is corrupted or missing, a simple reboot won’t help. You’ll need to reflash the original firmware. This process differs by brand, but the general steps are:

Download the official stock firmware for your exact model number from a trusted source (the manufacturer’s site or a reputable firmware archive).
Install the manufacturer’s flashing tool. Common ones include:
- Google Pixel: Use the flash-all.bat (Windows) or flash-all.sh (Mac/Linux) script from the factory image.
- Samsung: Use Odin (Windows only). Load the firmware files into the correct slots (BL, AP, CP, CSC) and click Start.
- OnePlus: Use the MSM Download Tool for unbricking, or fastboot commands for manual flashing.
- Xiaomi/Redmi: Use Mi Flash Tool with the official ROM in “Fastboot” format.
Follow the tool’s instructions carefully. Do not disconnect the cable until the process finishes and the phone reboots.

Reflashing wipes all user data, so only do this if you’ve backed up or if you’re okay with losing everything. It’s the most reliable fix for a truly bricked device, but it’s also the most risky if you flash the wrong firmware.

Common Problems and Their Specific Fixes

Here are the most frequent issues people hit when trying to exit fastboot, and how to solve each:

“fastboot devices” shows nothing: Install the correct USB driver, try a different cable, or enable USB debugging if you can boot to recovery. On Windows, check Device Manager for an unrecognized device.
“< waiting for any device >” forever: The phone is not in fastboot mode (maybe it’s in recovery or download mode). Hold the correct button combo to enter fastboot again.
“FAILED (remote: not allowed)” when flashing: This usually means the bootloader is locked. You need to unlock it first (which voids warranty and wipes data) via fastboot oem unlock or the manufacturer’s official method.
Phone reboots to fastboot after every restart: The boot partition is corrupt. Reflash the boot image or the entire firmware.
Battery drain while in fastboot: Fastboot mode uses very little power, but if the battery is critically low, the device may not respond. Leave it plugged in for 30 minutes, then try again.

Safety and Precautions Before You Flash

Flashing firmware is safe if you follow instructions, but there are real risks:

Data loss: Unlocking the bootloader or flashing a full firmware wipes all personal data. Always back up before starting.
Wrong firmware: Flashing a ROM meant for a different model can hard-brick your phone. Double-check the model number in Settings > About (if you can boot) or on the box.
Interrupted flash: Never unplug the cable during a flash. A power outage or cable disconnect can leave the device in an unbootable state.
Warranty: Unlocking the bootloader and flashing custom firmware usually voids the manufacturer warranty. Re-locking the bootloader after flashing stock may restore it, but not always.
If you’re unsure: Contact the manufacturer’s support or a professional repair service. Do not attempt a flash if you don’t understand the steps.

Alternatives to Fixing It Yourself

If the command-line methods feel too technical, or if the phone is still under warranty, consider these alternatives:

Manufacturer repair: Samsung, Google, OnePlus, and others offer out-of-warranty repair services. They can reflash the firmware or replace the motherboard if needed.
Local phone repair shop: Many independent shops have the tools and experience to unbrick Android devices. Ask for a quote before agreeing.
Use the device’s own recovery menu: If you can boot into recovery mode (usually Power + Volume Up), you may be able to select “Reboot system now” from there. This is different from fastboot, but worth trying if fastboot commands fail.
Trade-in or recycle: If the phone is old and the repair cost is high, consider a trade-in or recycling program. Some manufacturers offer credit for broken devices.

Frequently Asked Questions

Will I lose my data if I exit fastboot?

No. Exiting fastboot with a forced restart or the fastboot reboot command does not erase any data. Only reflashing the firmware or unlocking the bootloader will wipe your phone.

What if my phone is stuck in fastboot and won’t turn off?

Hold the Power button for 15–20 seconds. If that doesn’t work, hold Power + Volume Down for 15 seconds. If the screen goes black, release and press Power again to boot normally. If it returns to fastboot, you’ll need the computer method.

Can I exit fastboot without a computer?

Yes, in many cases. Try the forced restart button combo first. If that fails, look for a “Start” or “Restart” option on the fastboot screen using the volume keys and select it with Power. Some devices also respond to holding Power + Volume Up for 10 seconds.

Why does my phone keep going into fastboot mode by itself?

This usually indicates a hardware button issue (a stuck volume key) or a corrupted boot image. Check if the volume buttons are physically stuck. If not, reflash the stock firmware to restore the boot partition.

Is fastboot mode the same as recovery mode?

No. Fastboot is a bootloader interface for flashing partitions, while recovery mode is a separate environment for factory resets and installing OTA updates. They are accessed with different button combinations and serve different purposes.

What does “fastboot continue” do?

It tells the bootloader to continue a previously interrupted boot sequence. If your phone was in the middle of a boot when it got stuck, this command might let it finish booting to Android without a full reboot.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →