Android Phone Stuck on Boot Loop? 5 Ways to Recover Your Phone Without Losing Data
Your Android phone stuck on the logo? Use these 5 recovery methods — Safe Mode, cache wipe, ADB sideload fixes, and trusted data recovery — to break a boot loop without wiping everything.
If your Android phone is stuck on a boot loop — Samsung/Google logo, then restart, forever — do not jump straight to a factory reset. In many cases you can interrupt the loop, remove the bad update, and keep your photos.
This walkthrough prioritizes data‑safe fixes first, then heavier recovery options used by US and UK Android owners on Pixel, Samsung, OnePlus, Motorola, and other unlocked devices. Exact key combos vary by brand; when in doubt, search “[your model] recovery mode keys”.
What a boot loop looks like
- Logo appears → vibration → reboot → repeat
- You never reach the lock screen PIN/pattern
- It started after an app update, Android OS update, or the phone hitting 0% battery
Charge the phone for at least 30–60 minutes before troubleshooting. A critically low battery can mimic a software loop — and charging faults need their own path (Android won’t charge). Also see force restart if you only have a freeze, not a true loop.
Method 1: Force restart, then boot into Safe Mode
A force restart clears a soft hang without erasing data.
Force restart (common patterns)
- Pixel / many clean Android devices: hold Power until the logo appears again
- Samsung: hold Power + Volume Down for about 10–20 seconds
- Other OEMs: hold Power for 20+ seconds
Enter Safe Mode while looping
If you can briefly reach the power menu:
- Hold Power until power options appear
- Long‑press Power off
- Tap Safe Mode
If you only have hardware keys, many Samsung devices boot to Safe Mode by holding Volume Down after the logo appears during restart.
In Safe Mode, third‑party apps are disabled. If the phone stays stable:
- Open Settings → Apps
- Sort by last updated
- Uninstall recent social, cleaner, theme, or VPN apps
- Restart normally
Method 2: Wipe the cache partition (does not delete photos)
A corrupted cache after an OTA update is a classic boot‑loop trigger — especially after Android 16 upgrades.
- Force power off
- Boot into Recovery Mode (often Power + Volume Up, or Power + Volume Down + Bixby on some Samsungs)
- Use volume keys to highlight Wipe cache partition
- Confirm with Power
- Select Reboot system now
This is one of the highest‑reward, lowest‑risk steps. It will not factory reset your phone.
Method 3: Uninstall the bad app or update with ADB
If Safe Mode works but normal mode loops, a package is likely crashing system_server or a launcher process.
On a computer:
- Enable USB debugging ahead of time if you can still access Settings; if not, some devices still authorize a previously trusted PC
- Install Android Platform Tools (Google’s official ADB)
- Connect the phone by USB
- Run:
adb devices
adb shell pm list packages -3
Uninstall a suspicious package (example):
adb shell pm uninstall -k --user 0 com.example.badapp
Or disable it temporarily:
adb shell pm disable-user --user 0 com.example.badapp
Also try rolling back a bad system WebView/Chrome update from Safe Mode via Settings → Apps → Android System WebView → Uninstall updates when that button is available.
Method 4: Pull your data before any reset
If you still cannot stay on the home screen, prioritize files:
- Try connecting to a PC and opening the phone’s storage (MTP). Some phones mount storage even when the UI loops intermittently.
- Use Google account backups: Photos, Contacts, and SMS (if backup was enabled).
- For locked‑out internal storage, a reputable Android data recovery tool plus OEM USB drivers may recover images, documents, and messaging data depending on encryption/lock‑state.
- Remember WhatsApp needs its own backup habit next time (WhatsApp before repair).
Do this before Method 5. Once you factory reset, local data that was never synced is gone. Photo‑specific tactics: recover deleted photos.
Method 5: Sideload a repair package or factory reset (last resorts)
Option A: Sideload an official OTA / repair image
Advanced users with a matching stock package can use recovery ADB sideload:
adb sideload update.zip
Only use packages from your manufacturer or a trusted source for your exact model and carrier variant.
Option B: Factory reset from recovery
In recovery, choose Wipe data/factory reset only after you have extracted what you can. Afterward:
- Complete setup and sign into Google — expect FRP if an account was on the device
- Restore apps from backup
- Avoid reinstalling the same shady “cleaner” or cracked APK that may have caused the loop
- Keep 2–3 GB free going forward (Android storage full)
Extra checks that prevent a repeat loop
- Keep at least 2–3 GB free storage — Android updates fail hard on full disks
- Install apps from Google Play only (Play Store repairs)
- Delay major OS updates for a few days if early adopters report bricks on your model
- Turn on automatic backups for Photos and device data
- Replace a swollen battery / visit a repair shop if the phone reheats and reboots even in Safe Mode
- Migrate authenticators before the next shop visit (move 2FA)
Brand-specific tip sheet
| Brand | Recovery keys (typical) | Notes |
|---|---|---|
| Google Pixel | Power + Volume Down (Fastboot), then Recovery | Very ADB‑friendly |
| Samsung Galaxy | Power + Volume Up (+ Bixby on older models) | Wipe cache is often enough |
| OnePlus / Oppo | Power + Volume Down | Oxygen/ColorOS recovery labels vary |
| Motorola | Power + Volume Down | Safe Mode via power‑off long press |
When it is probably hardware
Seek repair if you see:
- Boot loop that continues after factory reset
- No charging indicator / extreme heat near the battery
- Water damage history
- Storage suddenly reporting raw capacity errors
Software steps will not fix a failing eMMC/UFS chip. Prep with before sending for repair.
Do / Don’t
Do
- Safe Mode + cache wipe first
- Pull data before factory reset
- Use official OTAs only
Don’t
- Reset as step one
- Flash random “debloat ZIPs”
- Pay for FRP bypass tools if you hit Google lock after wipe
Related FixingHacks guides
- Force restart a frozen phone
- Before sending a phone for repair
- Android FRP lock after repair
- Android 16 problems after update
- Android storage full
- Google Play Store not working
Bottom line
Start with Safe Mode and cache wipe — those two steps resolve a large share of Android boot loops without sacrificing your camera roll. Escalate to ADB removal and file extraction next, and treat factory reset as the final move, not the first.
Frequently Asked Questions
What causes an Android boot loop?
Common causes include a bad app update, corrupted cache, failed system update, depleted/faulty battery behavior, or storage almost full. Less often, it is a hardware fault.
Does wiping the cache partition delete photos?
No. Wiping the cache partition removes temporary system cache, not your personal photos, downloads, or WhatsApp media.
Will a factory reset delete everything?
Yes. A factory reset removes apps and local files that are not synced to Google Drive, Photos, or another cloud backup. Extract data first when possible.
Is Safe Mode safe for data?
Yes. Safe Mode disables third-party apps temporarily so you can remove a bad package.
What if FRP appears after I finally reset?
Sign in with the previous Google account. Do not use illegal bypass tools — see our FRP guide.
Related fixes
How to Recover Deleted Photos on Android (Before They Are Gone Forever)
Restore deleted Android photos from Trash, Google Photos, USB recovery, and dedicated software — act fast before data is overwritten.
Read the fixHow to Turn Off Safe Mode on Android (Exit Safe Mode, 2026)
Stuck in Android Safe Mode? Learn how to exit safely with a restart, why Safe Mode appears, what stays disabled, and fixes when the phone boots back into Safe Mode.
Read the fixSamsung Battery Drain on One UI: Find the Culprit and Restore All-Day Life
Fix Samsung Galaxy battery drain on One UI: Adaptive battery, rogue apps, 5G/Always On Display, caching, deep sleeping apps, and when a cell needs service.
Read the fix