How to Unbrick an Android Phone Using Fastboot and ADB (No Root)

When an Android device gets stuck in a boot loop, shows only the Fastboot screen, or refuses to start after a bad OTA, the term “bricked” is often used. In most cases the hardware is fine; the software simply needs to be re‑flashed. This tutorial shows you how to bring a non‑functional phone back to life using the official Fastboot interface and ADB tools, without requiring root or custom recoveries.

Before you start

• Computer running Windows 10/11, macOS, or Linux.
• USB‑C or micro‑USB cable that supports data transfer.
• Latest ADB & Fastboot platform‑tools downloaded and extracted.
• Device‑specific factory image (stock firmware) from the manufacturer’s official site.
• Optional: OEM USB drivers (Windows) – e.g., Google USB Driver, Samsung USB Driver, etc.

If any of these items are missing, the procedure will stop at the first roadblock.

Understanding the tools

Fastboot is a low‑level protocol that runs when the bootloader is unlocked and the device is in “Fastboot mode”. It lets you write raw images to individual partitions (boot, system, vendor, etc.). ADB (Android Debug Bridge) works when Android is running, but it is also useful for pulling logs before the device becomes unresponsive.

Because Fastboot works before the OS boots, it does not need root access. However, most manufacturers lock the bootloader to protect the device; unlocking it will wipe the device and may void warranty. This guide explains both unlocked and locked‑bootloader scenarios.

Step 1 – Install ADB & Fastboot on your computer

If the commands are not found, double‑check the PATH entry or run the executables directly from the extracted folder.

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

When the device still boots enough to show the Android UI, enable USB debugging to pull logs or backup data before flashing.

If the phone never reaches the OS, skip this step and move straight to Fastboot mode.

Step 3 – Boot the device into Fastboot mode

The key combination varies by manufacturer. Below are the most common methods:

• Pixel / Nexus: Power off, then hold Power + Volume Down until the Fastboot screen appears.
• Samsung (ex‑One UI): Power off, then hold Power + Volume Up + Bixby (or Volume Up only on newer models) and select “Download mode”. Fastboot is not available on most Samsung devices; they use Odin instead (covered in the “Alternative” section).
• OnePlus: Power off, then hold Power + Volume Up.
• Other OEMs: Search for “bootloader mode” for the specific model.

Connect the phone to the PC via USB while it is in Fastboot mode.

Step 4 – Unlock the bootloader (if required)

Many manufacturers ship devices with a locked bootloader. Unlocking is a one‑time operation that wipes the device.

Some OEMs (e.g., Xiaomi, Huawei) require an unlock code obtained from their developer portal. Follow the OEM’s official instructions if you encounter that situation.

Step 5 – Download the correct factory image

Flashing the wrong image can brick the device permanently. Always use the exact model number (e.g., Pixel 5 (redfin)) and the latest stable build from the manufacturer’s site.

• Google devices: Google Factory Images
• OnePlus: OnePlus Firmware
• Motorola: Motorola Firmware

Download the zip file and extract it. Inside you will find a script (e.g., flash-all.sh) and a set of .img files (boot, system, vendor, etc.).

Step 6 – Flash the stock firmware

There are two ways: use the provided script (simpler) or flash each partition manually (more control). The script works on macOS/Linux; Windows users can run the batch file flash-all.bat after enabling execution permissions.

The device should now boot into the fresh Android system. The first boot may take a few minutes as it optimizes apps.

Alternative method – Samsung devices (Odin)

Samsung phones do not expose Fastboot; they use a proprietary tool called Odin. If you have a Samsung device stuck in a boot loop, follow these steps:

1. Download the correct .tar.md5 firmware from SamMobile or the official Samsung site.
2. Install Odin on Windows and the Samsung USB drivers.
3. Boot the phone into Download mode (Power + Volume Down + Home/Bixby).
4. Connect to PC, open Odin, and load the firmware file into the AP slot.
5. Leave Auto Reboot and F. Reset Time checked, then click Start.
6. When Odin shows “PASS”, the phone will reboot into stock Android.

Because this guide focuses on Fastboot, the Samsung section is brief. Users should consult Samsung‑specific tutorials for deeper troubleshooting.

Troubleshooting common failures

Device not detected in Fastboot

• Check that the phone is truly in Fastboot mode – the screen usually says “FASTBOOT” or shows a minimal UI.
• On Windows, reinstall the OEM USB driver via Device Manager (right‑click the unknown device → Update driver → Browse my computer → Let me pick).
• On Linux, add a udev rule:

  sudo nano /etc/udev/rules.d/51-android.rules
  SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
  # Replace 18d1 with your vendor ID (run lsusb to find it)
  sudo udevadm control --reload-rules && sudo service udev restart

Bootloader unlock rejected

• Some carrier‑locked devices disallow unlocking. In that case, the only viable path is to use the OEM’s official “repair” service or replace the device.
• If the OEM requires an unlock code, request it from the developer portal and use fastboot oem unlock [code].

Flashing fails with “cannot write partition”

• Ensure you are using the correct image for your exact model. A mismatched system.img will be rejected.
• Some newer devices use the fastboot flash --slot=all syntax for A/B partitions. Adjust the command accordingly.

  fastboot flash boot boot.img --slot=all

• Try adding the --skip-reboot flag and reboot manually after all partitions are written.

Device boots to a black screen or keeps looping

• Boot into recovery (Power + Volume Up) and wipe cache partition.
• If the problem persists, re‑flash the firmware, ensuring you did not skip the vendor partition.
• As a last resort, perform a factory reset from the recovery menu, which will delete any leftover user data that may be causing the loop.

Verification – confirm the device is healthy

Once the phone boots, perform these quick checks:

1. Open Settings → About phone and verify the Android version matches the firmware you flashed.
2. Run adb devices from your PC; the device should appear as device, not offline.
3. Open a terminal and execute adb shell getprop ro.bootloader to confirm the bootloader state (locked/unlocked) as you intended.
4. Test basic functions – call, Wi‑Fi, camera – to ensure hardware drivers are functional.

If any component fails, revisit the troubleshooting section or consider flashing a different firmware version (e.g., an older stable build).

When to seek professional help

If the device refuses to enter Fastboot mode, shows hardware‑level errors (e.g., “No bootable device”), or the bootloader is permanently locked by the carrier, the software route may no longer be viable. In such cases, contacting the manufacturer’s support or a certified repair shop is advisable.

With the steps above, most software‑related bricks can be resolved without expensive repairs. The key is preparation: the right drivers, the exact factory image, and patience during flashing. Good luck, and enjoy your revived Android phone!