Difficulty
Easy
Steps
5
Time Required
30 - 45 minutes
Sections
1
- How to recover Chrome OS to its original factory state
- 5 steps
Flags
2
Needs More Images
A few more images would make this guide’s procedures crystal clear.
Member-Contributed Guide
An awesome member of our community made this guide. It is not managed by iFixit staff.
BackSamsung Chromebook Series 3 (XE303C12-A01US)
Full Screen
Options
History
Save to Favorites
Download PDF
Edit
Translate
Get Shareable Link
Embed This Guide
Notify Me of Changes
Stop Notifications
Introduction
What you need
Step 1
How to recover Chrome OS to its original factory state
- Backup any data on the hard drive since this will be wiped out when you decide to get a fresh Chrome OS.
Backup any data on the hard drive since this will be wiped out when you decide to get a fresh Chrome OS.
1024
Step 2
- Step 2: Once that’s completed, you will need the use of 3 fingers: One to hold escape, one to hold the refresh button, and one to poke the power button.
- If done correctly, your Chromebook will reset and have a screen that will tell you that you’re in recovery mode.
- From here, you can enter dev mode or restore to a new Chrome OS.
Step 2: Once that’s completed, you will need the use of 3 fingers: One to hold escape, one to hold the refresh button, and one to poke the power button.
If done correctly, your Chromebook will reset and have a screen that will tell you that you’re in recovery mode.
From here, you can enter dev mode or restore to a new Chrome OS.
Step 3
- Install the Chromebook Recovery Utility Chrome App from the Chrome Web Store.
Install the Chromebook Recovery Utility Chrome App from the Chrome Web Store.
Step 4
- Step 4: Once you download the OS, put it on a fresh and wiped out USB or SD card and insert it in the Chromebook, but not the USB 3 ports.
- Once the Chromebook has read the USB/SD card, this is the point of no return (for your hard drive at least)
Step 4: Once you download the OS, put it on a fresh and wiped out USB or SD card and insert it in the Chromebook, but not the USB 3 ports.
Once the Chromebook has read the USB/SD card, this is the point of no return (for your hard drive at least)
Step 5
- Let the Chromebook do its thing.
- Once it’s done, you should go back to the original setup process and you are good to go!
Let the Chromebook do its thing.
Once it’s done, you should go back to the original setup process and you are good to go!
To reassemble your device, follow these instructions in reverse order.
Cancel: I did not complete this guide.
35 other people completed this guide.
Author
with 4 other contributors
JAShadic
Member since: 02/03/2014
1,041 Reputation
1 Guide authored
Badges:
12
+9 more badges
Team
Apple fan boys
Member of Apple fan boys
Community
49 Members
41 Guides authored
dematisch - May 6, 2015
Reply
what can be the problem if there is an error message? freakin ukranian took my laptop away didnt know what he was doing charged me 2000rubles just for the nerves and travelling an hour to him to collect the computer with the same $@$*. i followed all the troubleshoots on the chrome os recovery site. is it idiotic to get a new mother straight away?
Liam Nye - Feb 23, 2016
Reply
it deosn’t work at all
jimstha126 - Aug 25, 2016
Same here….
Tiffanie Smith - Aug 15, 2016
Reply
I did everything the internet says to do to fix this on my Chromebook and it still says the same thing and hasn’t changed. But I noticed that if I click ctrl+alt+ shift+R it will change the tab recovery_reason to 0×05 TPM error in read-only firmware and then if I click ESC+ refresh+power button, the tab recovery reason goes back to 0×02 recovery button pressed. So I’m very confused. The screen when I turn it on is a white background that has a giant yellow exclamation mark with words under it saying Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card. (note: the blue USB port will NOT work for recovery) I brought it to the store I bought it from but they literally didn’t care or help me in anyway and they sent me away
Kelli Frederick - Mar 22, 2017
same problem. Did you find a way to fix this?