Android Stuck in Boot Loop — Complete Recovery Guide

A boot loop is one of the most stressful Android problems — the phone is alive but unreachable, your data feels trapped, and one wrong button press can turn a recoverable phone into a hard brick. The good news: most boot loops are fixable, often without losing data, and the fix takes 15 to 60 minutes. The bad news: the wrong recovery attempt can make the situation permanently worse. This guide walks through the exact triage we use at Droid Rooter, in order, with explicit warnings on every destructive step.

The short answer

If your phone vibrates and shows the brand logo, then resets in a loop, boot into recovery mode for your brand and try Wipe cache partition first (it does not delete your data). If that fails, the next safe step is a factory reset from recovery (with a clean backup plan). If neither works, the system partition is corrupted and you need a clean firmware reflash — that is specialist territory and we do it remotely for customers daily.

What is a boot loop, exactly?

A “boot loop” is any state where the phone repeatedly attempts to start up but never reaches the lock screen. The exact symptoms vary:

• Logo loop — phone vibrates, shows the brand logo for 5 to 10 seconds, then restarts and repeats. Most common pattern. Almost always a corrupted system partition or a failed OTA update.
• Animated boot loop — phone gets to the animated boot logo (the “G” on Pixel, the spinning Samsung dot, the Mi animation) but never finishes. Slightly worse than logo loop — usually means the OS is loading partly but failing on a service.
• Lock-screen flash loop — phone reaches the lock screen for a moment then resets. Often caused by a single rogue app installed at boot, or a corrupted account credential.
• Recovery loop — phone keeps booting into recovery mode rather than the OS. The OS partition is unbootable; recovery itself is fine.
• Bootloader loop — phone boots to the “fastboot” or “download mode” screen and refuses to leave it. Usually a partition flag is in the wrong state.

The pattern matters because it tells us which partition is broken — and which fix is appropriate.

Why boot loops happen — the five real causes

1. A failed OTA update. Interrupted by a flat battery, a forced power-off, or a flaky cellular connection during the apply-update step. By far the most common cause.
2. A broken Magisk or root module. A module that runs at boot crashes the boot sequence; without ability to disable it from inside the OS, the phone loops forever. Magisk’s safe-mode boot (volume-down during boot) usually fixes this.
3. A corrupted system app installed at boot. A specific app — often a recently installed accessibility service or a system overlay — crashes the OS as it loads.
4. A failed custom-recovery or custom-ROM flash. TWRP/OrangeFox flash that did not complete, or a ROM flashed without wiping the data/cache partitions properly.
5. Failing flash storage. Rare on phones less than 4 years old, but real on older devices. The eMMC or UFS chip starts returning bad blocks; the OS cannot read its own files.

Step 1: Try safe mode first (non-destructive, fast)

If your phone reaches the lock screen for even a moment, safe mode is worth trying first. Safe mode boots Android with no third-party apps loaded — if the boot loop is caused by a single rogue app, safe mode will succeed where normal boot fails.

How to enter safe mode varies slightly by brand:

• Most brands — start the phone normally, then press and hold the volume-down key through the entire boot animation until you see “Safe mode” in the corner.
• Magisk-rooted devices — hold volume-down for 5 to 10 seconds during boot to skip Magisk modules. This single trick rescues most root-related boot loops.
• Samsung devices already at the logo loop — power off, hold power + volume down for 15 seconds, release power but keep volume down held until safe mode appears.

If safe mode boots successfully, identify and uninstall the most recently installed app — it is almost certainly the cause. Then reboot normally.

Step 2: Boot into recovery mode for your brand

If safe mode is not reachable, recovery mode is your next stop. Recovery is a separate mini-OS built into every Android phone — it can wipe cache, factory reset, and apply firmware updates without the main OS being bootable.

Samsung (Galaxy S, A, Z, Note, Tab)

1. Power the phone off completely (hold power + volume down for 30 seconds if it is stuck).
2. With the phone off, hold Volume Up + Power simultaneously. Older Samsungs also need the Bixby key (Volume Up + Bixby + Power).
3. Release Power when the Samsung logo appears, but keep Volume Up held.
4. Recovery menu opens after 5 to 10 seconds.

Google Pixel

1. Power off completely.
2. Hold Volume Down + Power until the bootloader screen appears.
3. Use Volume Down to highlight Recovery mode and press Power to select.
4. When the “no command” Android-with-triangle screen appears, hold Power + tap Volume Up once to enter the full recovery menu.

Xiaomi, Redmi and POCO

1. Power off completely.
2. Hold Volume Up + Power until the Mi logo appears.
3. Recovery menu opens directly.

OnePlus

1. Power off completely.
2. Hold Volume Down + Power for 10 seconds until the OnePlus logo appears.
3. Recovery menu opens directly.

Other brands (Realme, Oppo, Vivo, Motorola)

Most use Volume Up + Power with the phone off. Hold for 10 to 15 seconds. If that does not work, try Volume Down + Power for the same duration. Look up the exact combo for your specific model before trying anything else.

Step 3: Wipe cache partition (safe, non-destructive)

From the recovery menu, use volume keys to navigate and power to select. The first option to try is Wipe cache partition — this clears system caches and dynamic state without touching your photos, contacts or apps.

1. Highlight Wipe cache partition.
2. Press Power to select.
3. Confirm if prompted.
4. After completion (5 to 30 seconds), highlight Reboot system now and select.

If the boot loop is gone after the cache wipe — you are done. About 35 percent of boot loops we see resolve at this step alone, with no data loss.

Step 4: Factory reset from recovery (DESTRUCTIVE — back up first if possible)

If cache wipe did not help, the next step is a full factory reset from recovery. This wipes all user data — photos, apps, accounts, settings — but preserves the system partition.

If you have a clean backup or no other choice:

1. From the recovery menu, highlight Wipe data / factory reset.
2. Press Power to select; confirm twice when prompted.
3. The wipe takes 1 to 5 minutes.
4. After completion, highlight Reboot system now and select.
5. The phone boots into the initial setup wizard.

If the boot loop is gone after the factory reset — the cause was user-data corruption rather than a system-partition problem. Set the phone back up and consider what you installed in the days before the boot loop began.

Step 5: When the phone refuses recovery — clean firmware reflash

If neither cache wipe nor factory reset fixes the loop, the system partition itself is corrupted. The fix is a clean reflash of the exact matching firmware for your device.

This is the step where most DIY attempts brick the phone permanently. The risks:

• Wrong region or variant — a Samsung A52 SM-A525F firmware on an SM-A525M phone bricks both modems and Wi-Fi.
• Wrong baseband or bootloader version — downgrading bootloader is permanently disabled on many devices via anti-rollback fuses.
• Interrupted flash — a USB cable that drops mid-flash can brick the phone hard enough that it cannot enter download mode again.

We do this remotely for customers daily and have never bricked a phone in 160+ jobs because we verify the exact firmware variant first and run a guided flash from a known-good environment. If you are not 100 percent confident in your model code, your firmware source and your flash tool, stop here and contact us first.

Hard-brick signs — when to stop trying

A few signs the phone has crossed from boot-loop to hard-brick territory:

• The phone shows no logo, no LED, no vibration after 30 minutes plugged into a known-good charger.
• The phone gets noticeably hot when plugged in but the screen stays completely dark.
• The phone reaches recovery once but fails the recovery boot on subsequent attempts.
• The phone enters fastboot or download mode but refuses any flash command with hardware errors.

In these cases, stop pressing combos and contact a specialist immediately. Continuing to retry can damage the eMMC or UFS storage further, push the device into permanent EDL mode, or trigger anti-rollback fuses that limit future firmware options.

What never to do, no matter what YouTube says

• Do not select random options in fastboot or download mode. “Wipe userdata” via fastboot has no confirmation and is irreversible.
• Do not install firmware from random forum threads. Use only your manufacturer’s official firmware tool (Samsung Smart Switch / Odin, Xiaomi Mi Flash, OnePlus MSM Tool) or a vetted repository like SamMobile.
• Do not pull the cable mid-flash. A 30-second flash interruption is the difference between a fixable phone and a paperweight.
• Do not factory reset a phone with valuable data via recovery without a backup plan. Recovery’s Wipe data is irreversible.

When to call a professional

For any boot loop with valuable data, or any case where you are not 100 percent sure of the next step, contact us before pressing another button. Most of our boot-loop jobs finish in 30 to 90 minutes remotely, recover the user data intact, and end with a clean working phone — for far less than the cost of a replacement device. See our performance repair and firmware services for what is included.