Android Bootloop: Causes and 5 Solutions

What is a Bootloop on Android

Bootloop (from English boot — loading, loop — cycle) is a critical error where an Android device cannot complete a normal operating system boot and infinitely reboots at the stage of showing the manufacturer's logo, splash screen, or immediately after it. The user sees the screen dim, the logo appears, and then everything repeats. The device becomes virtually unusable.

Symptoms:

• Cycle: logo → dimming → logo...
• Sometimes it reaches the unlock screen, but after entering a code or gesture, it reboots again.
• The device may respond to button presses but not enter the system.
• In some cases, booting stops on a black screen with a logo, and a reboot happens automatically after a few seconds.

Causes of a Bootloop

Causes are divided into software (most common) and hardware.

1. Corruption of system files after a failed firmware update, OS installation failure, or root application (e.g., Magisk) operation.
2. Conflicting third-party apps, especially after their update. Often culprits are launchers, antiviruses, or optimization utilities.
3. Incorrect custom recovery (TWRP, CWM) operation or modules installed through it.
4. Problems with the data partition — filesystem corruption, bad blocks on internal storage.
5. Failure after a settings reset or cache wipe that wasn't completed correctly.
6. Hardware malfunctions: storage drive failure (eMMC), RAM issues, CPU overheating.
7. Incorrect firmware flashing (e.g., installing firmware for a different model or region).

Solutions

Start with the simplest and safest methods, moving to more drastic ones. Before any actions, if possible, back up important data (via ADB if USB debugging was enabled, or via recovery if you have access to the data partition).

Method 1: Force Reboot

Sometimes a bootloop is caused by a temporary glitch that can be fixed by a full power cycle.

1. Press and hold the power button for 10-15 seconds until the device vibrates and turns off.
2. Release the button, wait 5 seconds.
3. Turn on the device with a normal press of the power button.

If the problem persists, move to the next method.

Method 2: Boot into Safe Mode

Safe mode disables all third-party apps. If the system boots in it — a installed program is at fault.

How to enter (methods vary by manufacturer):

• Standard (Android 4.0+): When turning on the device, when the logo appears, press and hold the volume down button. The words "Safe mode" will appear in the corner of the screen.
• Samsung: When turning on, when the logo is visible, press the volume down button.
• Xiaomi/Redmi/POCO: When turning on, when the logo is visible, press and hold the volume down button.
• Huawei/Honor: When turning on, when the logo is visible, press and hold the volume down button.

What to do next:

1. If you booted into safe mode, open Settings → Apps.
2. Find and uninstall recently installed apps, especially file managers, launchers, accelerators that may have had access to system files.
3. Reboot the device into normal mode.

If the problem remains, proceed to Recovery.

Method 3: Wipe Cache Partition

Cache can become corrupted and cause boot issues. This operation does not delete personal data.

Entering Recovery Mode: The button combination depends on the model. Most common:

• Samsung, Google Pixel, HTC, Sony: Volume Up + Power (release when the logo appears).
• Xiaomi, Redmi, POCO, OnePlus: Volume Up + Power.
• Huawei, Honor: Volume Up + Power, but sometimes Volume Down + Power (if the first doesn't work).
• Motorola, Nokia (Android One): Volume Down + Power.

If no combination works, search online for "how to enter recovery on your model".

Steps in Recovery (volume buttons to navigate, power button to select):

1. Select "Wipe cache partition".
2. Confirm selection (Yes).
3. After completion, select "Reboot system now".

If the bootloop continues after this, a factory reset is necessary.

Method 4: Factory Reset

Warning! This will delete ALL data from the device's internal storage: photos, contacts, messages, apps, and their settings. Try methods 1-3 first.

In Recovery Mode:

1. Select "Wipe data/factory reset".
2. Confirm the action (Yes or Factory data reset).
3. After completion, select "Reboot system now".

The device will reboot and start initial setup as new.

Method 5: Flash Stock ROM

This is the last and most complex method, requiring preparation. Use it if all previous methods failed, or if the bootloop occurred after an unsuccessful attempt to install a custom firmware/recovery.

What you'll need:

1. A computer with Windows/Linux/macOS.
2. Official firmware (Stock ROM) for your device's exact model (e.g., SM-G991B for Samsung Galaxy S21 5G). Download only from trusted sources (official manufacturer sites or reliable repositories).
3. Drivers for your device (usually included in the firmware package or separately on the manufacturer's site).
4. USB cable (original is best).
5. Charged battery (at least 60%).

General algorithm (specific steps depend on manufacturer):

For Samsung (uses Odin):

1. Boot the device into Download Mode (usually Volume Down + Volume Up + Power, then confirm with Volume Up).
2. Install drivers on the PC.
3. Run Odin (as administrator).
4. Add firmware files (AP, BL, CP, CSC) to the corresponding sections.
5. Connect the device to the PC (it should appear green in Odin).
6. Click Start.
7. After completion, the device will reboot.

For Xiaomi/Redmi/POCO (Mi Flash Tool):

1. Boot the device into Fastboot Mode (power off, hold Volume Down + Power).
2. Install drivers and Mi Flash.
3. In Mi Flash, select the path to the firmware folder (the folder must contain the images file, etc.).
4. Check the "Clean all" option (full wipe) or "Clean all and lock" (if you want to relock the bootloader).
5. Click "Select" to specify the folder, then "Flash".
6. After completion, the device will reboot.

For Google Pixel (Fastboot):

1. Boot into Fastboot (power off, hold Volume Down + Power).
2. Install platform-tools (ADB and Fastboot) on the PC.
3. Extract the firmware (images like boot.img, system.img, vendor.img, recovery.img, etc.).
4. In the command line (as administrator), navigate to the folder with the images and run:

   fastboot flash boot boot.img
   fastboot flash system system.img
   fastboot flash vendor vendor.img
   fastboot flash recovery recovery.img
   fastboot flash userdata userdata.img  # caution, deletes data
   fastboot reboot
   

   (Commands may vary depending on the firmware. Follow the instructions from the firmware source).

Important: The first boot after flashing may take 5-10 minutes.

Bootloop Prevention

1. Do not install apps from untrusted sources. Use only Google Play or official manufacturer stores.
2. Be careful with root privileges and custom recoveries. Install only verified modules and make a full backup (nandroid) before making changes.
3. Before updating firmware, ensure the battery charge is >80% and the device is connected to a stable power source.
4. Regularly back up important data (in Android settings or via ADB).
5. If the device was rooted or a custom recovery was installed, after a factory reset via recovery, you may need to reinstall Magisk or TWRP, otherwise a bootloop may occur.
6. Avoid "cleaning" system folders (system, vendor) via file managers with root privileges. This will almost certainly cause a bootloop.

If none of the methods helped and the device still won't boot, the problem may be hardware-related (e.g., storage drive wear). In this case, contact the manufacturer's service center.

Last updated: February 15, 2026. Information verified for relevance to Android 14/15 and popular skins (One UI 6, MIUI 14, EMUI 12, OxygenOS 14).