Quick Answer
An ASUS 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, which fixes the vast majority of boot loops without losing your Google-synced files.
Common Causes on ASUS Chromebooks
- A ChromeOS update that failed partway through installation
- Corrupted system partition data
- A charger with the wrong wattage causing power instability during boot on ASUS Detachable and Flip models
- A failing storage chip causing repeated boot verification failures
- A stuck power button registering repeated presses
- Overheating triggering a protective restart under heavy load
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. Check the Charger
ASUS Chromebooks, especially Detachable and Flip 2-in-1 models, can behave erratically on boot if powered by an underrated third-party USB-C charger. Try the original ASUS charger, or see our ASUS charger compatibility guide before assuming it’s a system fault.
4. 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.
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. Rule Out Overheating
If the restarts happen mainly during demanding tasks or after the device feels hot, check our ASUS overheating guide, a protective thermal shutdown can look like a random boot loop.
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. If the ASUS Chromebook also won’t turn on reliably or has an unresponsive trackpad, 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.
Can a bad charger really cause a boot loop on ASUS Chromebooks?
Yes. Some ASUS 2-in-1 models are picky about USB-C power delivery wattage, and an underrated charger can cause the system to brown out and restart repeatedly during the power-hungry boot sequence.
Is a boot loop always a hardware problem?
No, most boot loops are caused by a failed software update or a power issue and are fully fixable with a hard reset, a known-good charger, or a recovery install. Hardware failure is the less common cause, usually confirmed only after those steps don’t help.
