Recover a Soft‑Bricked Android Phone Using Fastboot and ADB

17 min read Step‑by‑step guide to recover a soft‑bricked Android device by flashing stock firmware with Fastboot and ADB, without needing root. October 11, 2026 10:30 How to Unbrick a Soft‑Bricked Android Phone Using Fastboot and ADB (No Root)

Before you start

Soft‑bricking occurs when the operating system fails to boot, usually showing a boot loop, a black screen, or the Android logo that never progresses. Unlike a hard brick, the device still powers on and can communicate with a computer via fastboot or adb. This tutorial walks you through a safe, repeatable process to restore the original firmware without rooting the device.

Why this works: Fastboot talks directly to the bootloader, which runs before Android is loaded. By flashing the stock partitions (boot, system, vendor, etc.) you replace the corrupted software with a known‑good image supplied by the device manufacturer.

What you will need

  • A Windows, macOS, or Linux PC with a stable internet connection.
  • A USB‑C or Micro‑USB cable that supports data transfer (charging‑only cables will not work).
  • The Fastboot and ADB binaries. The easiest way is to download the Android Platform‑Tools package.
  • The exact stock firmware for your device model (often a .zip or .tar containing fastboot images). Manufacturer websites, XDA‑Developers, or trusted firmware archives are typical sources.
  • Patience and a fully charged phone (≥70 %). Power loss during flashing can permanently brick the device.

Warning: Flashing the wrong firmware will turn a soft brick into a hard brick. Double‑check the model number, region code, and Android version before proceeding.

Step 1 – Install Platform‑Tools

  1. Download the platform-tools zip for your OS from the official Android developer site.
  2. Extract the archive to a location you can easily access, e.g., C:\adb on Windows or ~/adb on macOS/Linux.
  3. Add the folder to your system PATH so you can run adb and fastboot from any terminal.
    • Windows: Right‑click This PC → Properties → Advanced system settings → Environment Variables → Path → Edit → New and paste the folder path.
    • macOS/Linux: Add export PATH=$PATH:/path/to/platform-tools to your ~/.bashrc or ~/.zshrc and run source ~/.bashrc.
  4. Open a new terminal window and verify the installation by typing fastboot --version. You should see the version number without errors.

Step 2 – Prepare the stock firmware

  1. Locate the exact firmware for your device. The filename usually contains the model (e.g., Pixel_5a_2022_09_01.zip) and the Android version.
  2. If the file is a .zip, extract it with any archive tool. Inside you will find a collection of .img files such as boot.img, system.img, vendor.img, and sometimes radio.img.
  3. Create a dedicated folder (e.g., stock_firmware) and copy all extracted .img files there. This keeps the flashing command tidy.

Step 3 – Enable Developer Options & USB Debugging (if possible)

If the device still boots enough to display the Android UI, enable the following before entering fastboot mode. This is optional for fastboot, but it ensures adb can be used for a quick sanity check.

  1. Open Settings → About phone and tap Build number seven times. You will see a toast confirming "You are now a developer".
  2. Return to the main Settings screen, open System → Developer options, and toggle USB debugging ON.

Step 4 – Boot into Fastboot mode

  1. Power off the device completely. Hold the Power button for about 10 seconds to ensure it is truly off.
  2. Enter the device‑specific fastboot key combination. Common combos:
    • Pixel/Google: Power + Volume Down (hold both until the Fastboot screen appears).
    • Samsung (ex‑Download mode): Power + Volume Up + Home (or Bixby) then press Volume Up again.
    • OnePlus: Power + Volume Up while the device is off.
  3. The screen should show a text‑only interface with the Android logo and the word “FASTBOOT”. If you see a different UI (e.g., “Download mode”), you are in the wrong mode – power off and retry the correct key combo.
  4. Connect the phone to your PC via the data‑capable USB cable.
  5. Open a terminal on the PC and run fastboot devices. You should see a device ID like 0123456789ABCDEF fastboot. If nothing appears, try a different USB port, a different cable, or enable “USB debugging” again.

Step 5 – Unlock the bootloader (if required)

Most manufacturers lock the bootloader to prevent unauthorized flashing. Unlocking is a prerequisite for flashing most stock images. The process varies by OEM, but the generic fastboot command works on many devices.

  1. In the fastboot terminal, execute fastboot flashing get_unlock_ability. If the output says 0, the bootloader cannot be unlocked on that device (common on some carrier‑locked phones). In that case, you must use the OEM’s official unlocking tool or contact support.
  2. If the ability is 1, run fastboot flashing unlock. The device will display a warning screen; use the volume keys to confirm and the power button to proceed.
  3. After unlocking, the device will perform a factory reset automatically. This erases user data, so the backup step in the next section is essential.
  4. When the screen reboots into fastboot again, you can continue.

    Some OEMs (e.g., Xiaomi, OnePlus) require you to register an unlock code on their website before the command works. Check the manufacturer’s developer portal if the generic command fails.

Step 6 – (Optional but recommended) Back up the existing partitions

Even a soft‑bricked device may still have readable partitions. Backing them up gives you a safety net if the flashing process goes wrong.

  1. Create a folder on your PC, e.g., backup_fastboot.
  2. Run the following commands, adjusting the list of partitions to match those present in your firmware package:
    fastboot flash --download-only boot boot.img
    fastboot flash --download-only system system.img
    fastboot flash --download-only vendor vendor.img
    # Add other partitions as needed, e.g., radio, vbmeta
    
    This copies the images from the phone to the PC without overwriting anything on the device.
  3. Verify the files exist in backup_fastboot. Store them on an external drive before proceeding.

Step 7 – Flash the stock images

Now you will replace the corrupted partitions with the clean ones you extracted earlier.

  1. Navigate to the folder containing the .img files.
    cd /path/to/stock_firmware
  2. Flash each partition in the order recommended by the manufacturer. A typical order is:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
# If a radio image is present, flash it next
fastboot flash radio radio.img
# Finally flash the vbmeta (verified boot) image if it exists
fastboot flash vbmeta vbmeta.img
  1. Watch the terminal output. Each command should finish with OKAY. If you see FAILED, note the error message – common causes are mismatched partition sizes or a locked bootloader.
  2. When all partitions are flashed, run fastboot reboot to restart the device.

    Some devices require a special command after flashing, such as fastboot flashing lock to re‑lock the bootloader, or fastboot oem lock. Check the OEM’s flashing guide for any post‑flash steps.

Step 8 – Verify the device boots normally

If everything went well, the phone will boot into the stock Android setup wizard. You should see the usual welcome screens, not a boot loop.

  1. Allow the device to finish booting. The first boot after flashing can take longer (up to 2‑3 minutes) as the system indexes data.
  2. Complete the initial setup (language, Wi‑Fi, Google account). If the device reaches the home screen, the unbrick succeeded.
  3. Open Settings → About phone → Build number and verify the Android version matches the firmware you flashed.

Step 9 – Optional: Re‑lock the bootloader

Keeping the bootloader unlocked leaves a small attack surface. If you do not plan to flash custom ROMs, re‑locking is advisable.

  1. Boot back into fastboot mode (Power + Volume Down).
  2. Run the appropriate command for your device:
    • Pixel/Google: fastboot flashing lock
    • Samsung (Download mode): Use Odin to re‑lock, or follow the OEM’s fastboot command.
    • OnePlus: fastboot oem lock
  3. The device will perform another factory reset. After it restarts, the bootloader is locked again.

Troubleshooting common failures

1. Fastboot does not detect the device

  • Ensure the USB cable is data‑capable. Some cheap cables only charge.
  • Try a different USB port or a different computer.
  • On Windows, install the appropriate OEM USB drivers (Google USB Driver, Samsung USB Driver, etc.).
  • On macOS/Linux, you may need to add a udev rule (Linux) or grant permission (macOS) for the device.

2. "FAILED (remote: ...)" during flashing

  • Check that the .img files match the device’s partition layout. Flashing a system image meant for a different region (e.g., EU vs. US) often fails.
  • If the error mentions size mismatch, the firmware is for a different hardware revision. Download the correct variant.
  • Make sure the bootloader is unlocked. Some OEMs return FAILED (remote: locked bootloader) if you skip Step 5.

3. Device gets stuck in fastboot loop after reboot

  • Power off the phone, then boot into fastboot again and re‑flash the vbmeta image. A corrupted verified‑boot metadata can prevent the OS from loading.
  • Some devices require a separate dtbo.img (device tree overlay). If your firmware package includes it, flash it with fastboot flash dtbo dtbo.img before the system image.

4. “No command” or “Recovery mode” appears after flashing

  • This usually means the boot.img didn’t flash correctly. Re‑flash boot.img alone:
    fastboot flash boot boot.img
  • If the problem persists, try flashing a known‑good boot image from the same firmware package, or download a fresh copy of the firmware.

Alternative method: ADB sideload (when fastboot is unavailable)

Some devices (notably many Samsung models) expose a recovery mode that can accept an OTA package via ADB sideload. This method works when the bootloader is locked but the recovery is still functional.

  1. Download the official OTA zip for your device. It should be the same version you intend to restore.
  2. Boot the phone into recovery mode:
    • Power off, then press Power + Volume Up + Home/Bixby (or the OEM‑specific combo) until the recovery screen appears.
  3. In the recovery menu, select Apply update from ADB (or similar wording).
  4. Connect the phone to the PC and run:
    adb sideload path/to/ota_package.zip
    The PC will stream the zip to the device; progress is shown on both sides.
  5. When the sideload finishes, choose Reboot system now. The device should boot into the freshly installed stock ROM.

Post‑recovery checklist

  • Verify Android version: Settings → About phone → Android version.
  • Check for OTA updates: Run a manual check to ensure the device is on the latest security patch.
  • Restore data: If you backed up contacts, messages, or apps, now is the time to restore them via Google backup, Samsung Smart Switch, or your preferred method.
  • Re‑enable developer options: If you need ADB debugging again, turn it back on.

When to seek professional help

If you encounter any of the following, stop and consider a repair service:

  • The device does not enter fastboot or recovery mode at all (hard brick).
  • Fastboot reports device locked and you cannot obtain an unlock code from the OEM.
  • The eMMC/NAND chip shows read‑write errors (fastboot may report FAILED (remote: flash write error) repeatedly).

Summary

Recovering a soft‑bricked Android phone with Fastboot and ADB is a systematic process: install platform‑tools, obtain the exact stock firmware, unlock the bootloader (if needed), flash the required images, and verify the boot. By following the steps above, you can bring a non‑booting device back to life without rooting or third‑party tools. Remember to back up before flashing, double‑check firmware compatibility, and keep your device charged throughout the operation.

User Comments (0)

Add Comment
We'll never share your email with anyone else.