Recover an Android Phone Stuck in a Boot Loop Using ADB and Fastboot (No Root)

If your Android phone keeps restarting before it reaches the home screen, you’re facing a boot loop. This can happen after a failed OTA update, a corrupted system app, or an accidental change in a critical partition. While a factory reset often works, it wipes all data. This tutorial shows how to break the loop using ADB and Fastboot without rooting, preserving your data whenever possible.

Before You Start

• Charge the device to at least 50 % to avoid power loss during flashing.
• Install the latest Android Platform‑Tools on your PC (contains ADB and Fastboot).
• Download the official stock firmware for your exact device model (e.g., boot.img, system.img) from the manufacturer’s site or a trusted archive.
• Back up any important files on an external SD card or via a PC if you can still access the internal storage in recovery mode.
• Enable USB debugging if possible. If the phone never reaches the OS, you’ll enable it from a custom recovery later.

Step 1 – Get the Phone into Fastboot Mode

1. Power off the device completely. If it restarts automatically, hold the Power button for 10‑12 seconds to force a hard shutdown.
2. Enter fastboot mode using the manufacturer‑specific key combo:
   • Pixel / Nexus: Hold Power + Volume Down until the Fastboot screen appears.
   • Samsung (ex‑One UI): Hold Power + Volume Up + Home (or Bixby) for a few seconds.
   • Other OEMs: Usually Power + Volume Down works; consult the device manual if unsure.
3. Connect the phone to your PC via a good quality USB‑C cable.
4. Open a terminal (Windows Command Prompt, PowerShell, macOS/Linux terminal) and verify the connection:

   fastboot devices

   You should see a line like 0123456789ABCDEF fastboot. If nothing appears, try a different cable or USB port.

Step 2 – Prepare a Minimal Recovery (If Needed)

Some devices automatically boot into the stock recovery when they detect a corrupted boot image. The stock recovery often lacks ADB access. Installing a lightweight custom recovery such as TWRP temporarily gives you ADB while keeping the system untouched.

2a – Download the correct TWRP image

• Visit twrp.me and locate the exact model.
• Download the .img file (e.g., twrp-3.5.2-0-xyz.img).

2b – Flash the recovery

fastboot flash recovery twrp-3.5.2-0-xyz.img

After flashing, reboot directly into recovery:

fastboot reboot recovery

The device should now boot into TWRP, where ADB is enabled by default.

Step 3 – Verify ADB Access from Recovery

1. From your PC, run:

   adb devices

   You should see recovery next to the device serial.
2. If you see unauthorized, swipe the “Allow USB debugging” prompt on the phone (even in recovery, TWRP shows it).

Step 4 – Pull Critical Partitions for Backup (Optional but Recommended)

Before flashing anything, back up the current boot and system partitions. This gives you a fallback if the new firmware misbehaves.

# Create a folder on your PC
mkdir -p ~/android-backup
# Pull boot image
adb pull /dev/block/bootdevice/by-name/boot ~/android-backup/boot_original.img
# Pull system image (may be large; you can skip if space is limited)
adb pull /dev/block/bootdevice/by-name/system ~/android-backup/system_original.img

These commands work on most devices that expose the block paths via recovery. If the path differs, use adb shell ls /dev/block/bootdevice/by-name/ to list available partitions.

Step 5 – Flash the Stock Boot Image

The most common cause of a boot loop is a corrupted boot.img. Re‑flashing the stock boot image often restores normal startup while leaving user data untouched.

5a – Locate the correct boot image

• Extract the boot.img from the stock firmware you downloaded in the preparation step. Most firmware packages are zip files; inside you’ll find boot.img.

5b – Flash the image

fastboot flash boot boot.img

Wait for the “OKAY” response. Then reboot:

fastboot reboot

If the device boots normally, the problem is solved. If the loop persists, continue to Step 6.

Step 6 – Re‑flash the System Partition (When Boot Image Alone Isn’t Enough)

Sometimes the system partition gets corrupted, especially after a failed OTA. Re‑flashing the entire system image restores the OS without wiping user data, but it does reset system settings.

6a – Prepare the system image

• Extract system.img from the stock firmware zip. If the firmware provides a payload.bin, use the payload-dumper-go tool to extract individual images.

6b – Flash the system image

fastboot flash system system.img

On some devices the system partition is split (e.g., system_a / system_b for A/B devices). Use the appropriate name:

fastboot flash system_a system.img

6c – Reboot and verify

fastboot reboot

Give the phone a few minutes to finish the first‑boot sequence. If it reaches the lock screen, the loop is resolved.

Step 7 – Optional: Flash a Fresh Stock ROM

If both boot and system images are intact but the loop persists, the issue may be deeper (e.g., corrupted vendor partition). Flashing the full stock ROM is the cleanest solution.

1. Extract the full set of images (boot.img, system.img, vendor.img, odm.img, etc.) from the firmware package.
2. Flash each partition in the order recommended by the manufacturer. A typical sequence for a non‑A/B device:

   fastboot flash boot boot.img
   fastboot flash system system.img
   fastboot flash vendor vendor.img
   fastboot flash odm odm.img
   fastboot flash product product.img

3. For A/B devices, you may need to flash the “_a” and “_b” slots separately, then set the active slot:

   fastboot flash boot_a boot.img
   fastboot flash boot_b boot.img
   fastboot set_active a   # or b, whichever you just flashed

4. After flashing, run fastboot reboot. The first boot can take 5‑10 minutes.

Step 8 – Verify the Device Is Stable

Once the phone boots, perform these checks:

• Open Settings > About phone and confirm the Android version matches the firmware you flashed.
• Navigate through a few apps to ensure they launch without crashing.
• Monitor the battery level for a few hours; a lingering boot loop often shows up as rapid drain.

If everything works, you have successfully rescued the device without a full factory reset.

Troubleshooting Common Issues

Fastboot Doesn’t Recognize the Device

• Make sure USB debugging (or at least OEM unlocking) is enabled in the bootloader. Some manufacturers require you to enable “OEM Unlock” in the developer options before fastboot can communicate.
• Try a different USB port or a direct connection (no hubs).
• On Windows, install the appropriate Google USB drivers.

ADB Shows “device unauthorized” in Recovery

• Reboot into the custom recovery again; TWRP sometimes resets the ADB key.
• On the PC, delete the adbkey files located in %USERPROFILE%\.android\ (Windows) or ~/.android/ (Linux/macOS) and reconnect.

Flashing Fails with “FAILED (remote: Invalid partition)”

• Verify you are using the correct partition name for your device (e.g., system_a vs system).
• Some OEMs lock certain partitions; you may need to unlock the bootloader first (fastboot oem unlock). This will wipe user data, so treat it as a last resort.

Device Still Boots into a Loop After All Images Are Flashed

• Check the logcat output from recovery (if available) to see if a specific service crashes.
• Consider flashing the vendor and odm partitions, which hold hardware‑specific binaries.
• As a final measure, perform a factory reset from the stock recovery (this will erase user data but often clears persistent boot‑loop triggers).

When to Consider Professional Help

If you have tried the steps above and the phone still refuses to boot, the hardware (e.g., eMMC or NAND) may be failing. At that point, a warranty claim or a professional repair shop is the safest option.

Summary

Recovering a boot‑looped Android device with ADB and Fastboot is a methodical process:

1. Enter fastboot mode and confirm the PC connection.
2. Optionally flash a minimal recovery (TWRP) to gain ADB access.
3. Back up the current boot and system images.
4. Flash the stock boot.img. If needed, flash system.img or the full ROM.
5. Reboot, verify stability, and perform post‑recovery checks.

Following these steps lets you rescue most software‑related boot loops while keeping your personal data intact. Always keep a copy of the original firmware and double‑check device model numbers before flashing.