Yeah, seeing your phone endlessly restart after an OTA update is infuriating. I've been there with dozens of users. Before you panic and factory reset (which nukes your photos, texts, and everything), here's the fix that works 80% of the time.
Wipe the cache partition
The culprit here is almost always corrupted cached system data from the old version clashing with the new update. The system cache gets confused and can't boot. Wiping it forces the OS to rebuild fresh cache files.
- Turn off the phone completely. Hold power + volume down (or power + volume up for some older models).
- You'll see a recovery menu. Use volume keys to navigate, power to select.
- Look for "Wipe cache partition" — not "Factory reset" or "Format data". Don't touch those.
- Confirm the wipe. It takes about 5–10 seconds.
- Select "Reboot system now".
That's it. Your phone should boot normally. I've fixed Samsung Galaxies, Pixels, OnePlus, and Xiaomi phones this way. No data lost. None.
Why does this work?
Android stores optimized app data in a cache partition separate from your user data. When an OTA update lands, it expects that cache to be either compatible or empty. If the cache holds data from the previous major version (say Android 12 -> 13), the boot process trips over itself trying to reconcile old and new. Wiping it removes that conflict. The system rebuilds the cache on its first boot, which adds a minute or two to the initial boot, but then you're golden.
When wiping cache doesn't fix it
If you're still in the boot loop after the cache wipe, the problem is more specific. Here are the less common variations I've seen:
Corrupted system app data
Sometimes a single app like Google Play Services or a carrier bloatware app has corrupted data that crashes the system on boot. Try booting into Safe Mode (hold volume down during boot on most phones). If it boots in Safe Mode, you can uninstall recently updated apps one by one. The app that triggered it is usually the last one updated before the OTA.
Insufficient storage space
An OTA needs free space to unpack and apply. If your device storage is over 90% full, the update can leave half-committed files that break boot. If you can get into recovery mode, some recoveries let you delete files via ADB. Connect to a PC, run adb shell rm -rf /sdcard/Downloads/* to free space. Then clear cache again and reboot.
System partition corruption
This is rare but happens. The OTA might have a bad checksum or the flash memory has a bad block. For this, you need to reflash the system partition. Tools like Samsung Odin or Google's flash-all script for Pixels work. You'll need the factory image for your exact model. This wipes user data, so it's a last resort. But I've seen it resurrect phones that were bricked for weeks.
Prevention tips for next time
| What to do | Why it helps |
|---|---|
| Keep 10–15% storage free | Gives the OTA room to decompress and apply safely |
| Don't update when battery is below 30% | Power loss mid-update causes corruption |
| Update apps before a major OTA | Reduces app cache conflicts with the new OS |
| Back up regularly | Because even pros get a bad OTA every few years |
Boot loops suck but they're fixable. Cache wipe first, always. Safe Mode second. Factory reset or reflash last. Don't skip steps.