Restart patterns are diagnoses: read yours first
A phone that restarts itself is telling you when it hurts, and the pattern is most of the diagnosis. Restarts tied to a specific app or action (always in the same game, always when the camera opens): app-level, the friendliest case. Restarts under load or heat (gaming, navigation, fast charging, summer): thermal or power delivery, pointing at battery health or cooling. Restarts at random moments including idle, with no pattern at all: system-level corruption or a failing component. And the boot loop, restarting during startup without ever reaching the home screen, is its own emergency lane, covered separately below.
Two more pattern details sharpen the picture. Does the phone fully reboot (manufacturer logo, full boot time) or just flash and return (a 'soft reboot' of the interface)? Soft reboots implicate software almost exclusively; full reboots keep hardware in the pool. And what does the battery do around the restart: a phone that dies at 20-40 percent and boots showing a much lower or higher level is broadcasting the classic worn-battery signature, voltage sag under load tricking the phone into emergency shutdown, which our battery health calculator can quantify in two minutes.
Before deep diagnosis, clear the two banal causes that embarrass everyone: a stuck power button (press it through its travel, remove the case, clean the seam, a button that clicks oddly or sits flush is a suspect, the same hardware-trigger logic as Safe Mode loops), and critically low storage (below about 1 GB free, Android becomes unstable in exactly this way, check Settings, Storage and run our storage cleanup if needed). Both cause endless misdiagnosed 'random' restarts and both cost minutes to rule out.
The software ladder for random restarts
With patterns read and banalities cleared, run the software ladder in order. Rung one: update everything, system, Play system update (a separate item in settings many people never see), and all apps, then Android System WebView and Chrome explicitly, whose bad releases have historically caused mass instability. Rung two: the Safe Mode verdict, use our Safe Mode guide's method and live there for a few hours. Stable in Safe Mode convicts an installed app, and the recency-based hunt (recent installs, overlay and accessibility holders, cleaner-boosters, off-store apps) plus staged uninstalls finds it.
Rung three, for phones unstable even in Safe Mode: wipe the cache partition from Recovery, power off, hold Power and Volume Up to Recovery, select Wipe cache partition, harmless to your data and the specific cure for post-update instability where a system update left stale caches behind. Rung four: hunt the log. A restart writes its dying words to the system log, and 'adb logcat' captured around a reproduced restart, pasted into our Logcat Analyzer, distinguishes a kernel panic (hardware-leaning) from an endlessly crashing system service (software, and named), the five-minute technician move from our crash guide that regularly redirects an entire diagnosis.
Rung five is the factory reset, with its honest framing: it is the definitive software-versus-hardware experiment. Full backup first (our backup guide), reset (our reset guide), then use the phone lightly WITHOUT restoring apps for a day. A clean phone that still restarts has proven hardware guilt beyond appeal, no further software rituals are worth your time, and the repair conversation begins with that fact as Exhibit A. A clean phone that runs stable convicts your old app set or accumulated state, restore selectively and watch for the returning offender.
Heat, power and the worn-battery signature
Restarts under load are usually power delivery failing at the moment of maximum demand, and the battery is the lead suspect on any phone past its second year. The physics: processors spike current draw under load, an aged battery's internal resistance turns that spike into a voltage sag, and the phone's protection circuitry interprets the sag as imminent death, cutting power. The signatures: restarts during gaming or camera use, restarts in cold weather (resistance rises), the jumping battery percentage described earlier, and shutdowns at 15-40 percent that a charger instantly revives.
Confirm rather than guess: get the battery's current capacity (a battery app, or the ADB route in our battery health article) and feed it with the design capacity into our Battery Health Calculator. Health under 80 percent alongside the load-restart pattern is as close to certainty as phone diagnosis gets, and the fix, a battery replacement, is among the cheapest repairs that exist, routinely resurrecting phones their owners had written off as haunted. This single paragraph resolves an enormous share of 'my phone restarts randomly' complaints on phones older than two years.
True thermal restarts, distinct from voltage sag, come with the phone genuinely hot to the touch, and the fix list is our overheating guide's: case off under load, no charging-while-gaming, out of the sun, and the background-heater hunt (Settings, Battery naming what burned energy). A phone that restarts hot AND has a worn battery has both problems feeding each other, resistance makes heat, heat ages the battery, and the battery swap addresses both at once. Chargers earn a final suspicion: a failing charger or cable delivering dirty power causes restarts specifically while plugged in, tested in minutes by swapping to a known-good set, the same one-variable-at-a-time discipline as our charging guide.
Boot loops: the phone that cannot finish starting
A boot loop, logo, restart, logo, forever, blocks all the normal fixes because you cannot reach Android, so the sequence works from outside. First: charge for thirty minutes on a known-good charger regardless of what you believe the battery holds, deep discharge mimics boot loops convincingly. Second: force a clean start, hold Power (with Volume Down on many phones) for twenty-plus seconds, let it fully die, then boot once more. Third: attempt Safe Mode from power-off (hold Volume Down from the logo through boot, per our Safe Mode guide), because an app crashing at startup causes loops that Safe Mode sails past, and the fix is then simply uninstalling the newest apps from within Safe Mode.
Fourth: Recovery Mode (Power plus Volume Up from off), which loads before Android and is the diagnostic fork: Recovery reachable means the low-level system is alive, run Wipe cache partition and reboot, the single highest-yield boot-loop fix, especially for loops that began after a system update. Fifth, still looping: back in Recovery, the factory reset, with the data reality stated plainly: if backups were current (the monthly three-glance habit from our backup guide), this costs an evening; if not, pause here, because a repair shop can sometimes extract data from a looping phone BEFORE a reset, and wiping first forecloses that, choose deliberately based on what the phone holds.
Recovery unreachable, or loops surviving even a factory reset: hardware, most commonly failing flash storage (the phone equivalent of a dying SSD) or a board fault after drops or liquid, and no home remedy applies. The economics follow every repair chapter: board-level work versus device value, with the data-recovery question asked first if anything unbacked-up matters. And the prevention coda writes itself from the causes: storage kept above the critical floor, updates installed (half of loop cases follow interrupted or corrupted updates, never power off mid-update), quality chargers, and backups current, so that even the worst loop is an inconvenience, not a loss, exactly the resilience posture every guide in this series builds toward.