What Is an Android Bootloop?

A bootloop is when your Android device continuously restarts — it powers on, shows the manufacturer logo or loading animation, and then reboots before ever reaching the home screen. It can repeat indefinitely, making the device unusable.

Bootloops after a firmware flash are frustrating but usually recoverable. Understanding why they happen is the first step to fixing them.

Common Causes of Post-Flash Bootloops

  • Incorrect firmware version: Flashing firmware meant for a different model, region, or hardware variant.
  • Incomplete flash: The flashing process was interrupted (USB disconnect, power failure).
  • Corrupted firmware file: A partially downloaded or damaged firmware package.
  • Wiping cache not performed: After flashing, old cache data can conflict with the new firmware.
  • Incompatible GApps or Magisk: If flashing custom ROMs with additional packages, version mismatches cause loops.
  • Partition mismatch: Flashing only some partitions when a full flash was required.

Step 1: Try a Simple Battery Pull or Force Restart

Before anything else, try a force restart:

  • Hold the Power button for 10–15 seconds until the device powers off, then turn it back on.
  • On some Samsung devices: hold Power + Volume Down for 10 seconds.

If the bootloop persists after 2–3 attempts, move to the next steps.

Step 2: Boot Into Recovery Mode and Wipe Cache Partition

This is the least destructive fix and should be tried first:

  1. Power off the device completely.
  2. Boot into recovery mode. The button combination varies:
    • Samsung: Power + Volume Up + Home (or Bixby)
    • Xiaomi/Redmi: Power + Volume Up
    • Google Pixel: Power + Volume Down, then select Recovery
    • Most MTK devices: Volume Up + Power
  3. In recovery, navigate using volume buttons, confirm with power button.
  4. Select "Wipe Cache Partition" and confirm.
  5. After the wipe, select "Reboot System Now".

If the device boots successfully, you're done. If it loops again, proceed further.

Step 3: Factory Reset from Recovery

Warning: This erases all personal data. Only proceed if the cache wipe didn't help and you've exhausted other options, or if data loss is acceptable.

  1. Boot into recovery mode (same steps as above).
  2. Select "Wipe Data / Factory Reset".
  3. Confirm the wipe.
  4. Reboot the system.

Step 4: Re-Flash the Correct Firmware

If recovery options don't resolve the bootloop, a clean re-flash is the most reliable fix. This means completely overwriting the current firmware with a fresh, verified copy:

  1. Identify your exact device model number and region (from the box, Settings, or IMEI sticker).
  2. Download the correct stock firmware from a trusted source — double-check the model number and build match exactly.
  3. Use the appropriate flashing tool:
    • Samsung devices: Odin (Windows)
    • MediaTek devices: SP Flash Tool
    • Qualcomm devices: QFIL or EDL mode flashing
    • Fastboot-compatible devices: ADB/Fastboot commands
  4. Flash with the "Format All + Download" or equivalent full-wipe option.

Step 5: EDL / Download Mode (Last Resort)

If the device won't even enter recovery, you may need to enter Emergency Download Mode (EDL) for Qualcomm devices, or Download Mode for Samsung. These low-level modes bypass the normal boot chain and allow direct firmware flashing even on heavily corrupted devices.

EDL mode entry varies by device — consult your specific model's documentation or manufacturer support resources.

Preventing Bootloops in the Future

  • Always verify firmware matches your exact model + hardware variant + region.
  • Download firmware files fully before flashing — check file size against expected value.
  • Use original or high-quality USB cables during flashing.
  • Wipe cache partition after every major firmware change.
  • Never interrupt a flash in progress.

Summary

Most bootloops after firmware flashing are recoverable. Start with the least destructive solution (cache wipe), escalate to factory reset if needed, and as a last resort, re-flash correct stock firmware using the appropriate tool for your device's chipset.