Quick Answer
A Chromebook stuck restarting in a loop is most often caused by a failed ChromeOS update or corrupted system files. Hold Esc + Refresh, then press Power to enter recovery mode and reinstall ChromeOS — this fixes the vast majority of boot loops without losing your Google-synced files.
Common Causes
- A ChromeOS update that failed partway through installation
- Corrupted system partition data
- A third-party extension or Developer Mode change conflicting with boot
- A failing storage chip causing repeated boot verification failures
- A stuck power button registering repeated presses
- Rare hardware faults on the motherboard
Step-by-Step Fixes
1. Let It Try a Few Times First
Occasionally a single failed update cycle resolves itself after 2-3 automatic restart attempts. If it’s still looping after that, move to a hard reset.
2. Force a Hard Reset
Hold Refresh + Power for 10 seconds, release, then power on normally. This clears a stuck restart cycle caused by a temporary glitch.
3. Boot Into Recovery Mode
Hold Esc + Refresh, then press Power while still holding both. This brings up the ChromeOS recovery screen, from which you can reinstall the OS using a recovery USB.
4. Check for a Stuck Power Button
On some models, a physically stuck or sticky power button can register as repeated presses, causing what looks like a boot loop. Inspect and gently clean around the button.
5. Disconnect All Peripherals
USB drives, SD cards, or docking stations can occasionally interfere with the boot sequence. Remove everything and attempt to boot with nothing connected.
6. Exit Developer Mode If Enabled
If you or someone else enabled Developer Mode, a failed boot verification can cause looping. Pressing Space at the OS verification screen and confirming will return to Verified Mode (this does erase local data).
7. Run a Full Recovery Install
If the loop persists, create a recovery USB from another computer using the Chromebook Recovery Utility and reinstall ChromeOS fully. This resolves corrupted system partitions that a simple reset can’t fix.
Still Not Fixed?
If a full recovery install still results in a boot loop, or the recovery screen itself won’t load, this points to a hardware fault, most commonly a failing eMMC/storage chip. At this point, professional diagnosis is the right next step rather than repeated recovery attempts.
FAQ
Will a recovery install delete my files?
It wipes local storage, but anything synced to your Google account (Drive files, bookmarks, extensions, settings) restores automatically after signing back in.
How do I make a ChromeOS recovery USB?
You’ll need another computer, an 8GB+ USB drive, and the Chromebook Recovery Utility extension. Full steps are in our recovery USB guide.
Is a boot loop always a hardware problem?
No — most boot loops are caused by a failed software update and are fully fixable with a hard reset or recovery install. Hardware failure is the less common cause, usually confirmed only after recovery doesn’t help.
Fixes by Chromebook Brand
Boot loops can come from firmware, storage or battery issues, and the most common trigger is not the same on every brand. If you know your brand, its dedicated guide goes further:
