Skip to main content

How to beat ChromeOS EOL and carry on getting updates

ChromeOS devices are great in loads of ways, but they have built-in obsolescence. Google will stop providing updates at a predetermined time according to the schedule you can find here. So the best you will achieve is 6.5 year if you buy the device on the launch day. In reality, it will be generally much less. It's something to watch as a good deal might not be such a good deal if the device only has two years left.

Once a device reaches its "due" date, you get a red pop up telling you its time to update every time you log in. The update section tells you there are no more updates. Now the device will work fine - for a while. You might get another 6 months use out of it before core services like Gmail stop working. However, if you are prepared to do a little work, you can install the OS of your choice onto the device and carry on using the device and not accept this. If you want ChromeOS, then you can install Cloudready from Neverware. I'll outline the basic steps below:

Put your device into Developer Mode. For most devices, this means hitting the ESC - Refresh - Power buttons. On some devices - like the Samsung Chromebox, the is a little dip switch to do it. Either way, the device reboots and you get ChromeOS is missing or damaged. Hit Ctrl-D and follow the onscreen prompts. When the device reboots - hit Ctrl - D and the device boots into Developer Mode.

If your device was managed - then make sure it is in an OU with forced re-enrollment turned off while you tinker.

We are going to modify the BIOS on the machine. Some machines have a hardware lock on this. It may be a screw or a jumper on the motherboard. You need to find out where this is (if present). has guides for some devices - Samsung Chromebox and 550. So for the Samsung Chromebox the jumper indicated in the picture must be closed:

Inline image 1

Once you have flashed your BIOS you can open this again.

Fire the machine up and login to it. Open up Chrome and hit Ctrl + Alt + T. This will bring up the terminal. Run the following commands:

sudo -s
flashrom --wp-disable

Reboot the device and log back in.
Open up the terminal again Ctrl + Alt + T. The run the following commands:

sudo -s
cd;bash <(curl

There is an alternative Sea BIOS source and the script would be:
cd; curl -LO && sudo bash

The second one comes from - the site gives lots of good information.

You are now at the point of no return and can potentially brick your device. Follow the onscreen instructions to the letter. With the bios flash option FULL ROM should work with most devices - but check your one here (or at if using that BIOS).
Assuming you get no errors, you can reboot the device. ChromeOS has now gone!

You need a bootable USB stick with your new OS on it. Could be Windows, Linux or Cloudready to go back to ChromeOS. Pop it into a USB port before you reboot.

Reboot. Hold ESC down and hammer the "2" key. ESC selects the boot option and 2 is USB boot. If all is well, you should boot from the USB key and be able to install the OS. Once it is all working, I suggest you re-enable the BIOS lock.

This allows you to carry on using the device indefinitely. There are a few things to be aware of:

  • No support for ARM based devices - so Samsung 303's are toast.
  • If you want to use the enterprise version of Cloudready, when you enrol the device, it will use a new ChromeOS licence - its seen as a different device.
Over the coming year, I'll be doing this on numerous Asus, Acer and Samsung Chromeboxes and LG Chromebases. All work absolutely fine - but are coming to the EOL date so there is is no need to accept planned obsolescence.

Just an update on this - the location of the hardware lock for Asus/Dell/HP and Acer (under the heat pipe) hardware locks are shown below:

Video Walkthrough


  1. Hi,

    Great guide, many thanks. I saw the video on your channel on youtube on the pixel with cloudready and looks absolutely great. I'm seriously considering putting it on my 2013 pixel. Do you mind if I ask a few questions?

    1. Which have you found better ubuntu or cloudready? Any issues with either?
    2. Do you have to flash a modified bios, and if you had a preference over mrchromebox or the Johnlewis one which would you choose?
    3. I've galliumOS dualbooting on an Acer c720, which runs great, but when booting you've to choose with CTRL+D or CTRL+L, is it the same with cloudready, or does it just boot straight back into the OS.
    4. Are there any other idiot proof guides you'd recommend.

    Again, many thanks

    1. I used Ubuntu on it to start with and moved to Cloudready. Ubuntu worked OK - but the 32Gb drive meant it was a bit limited. You also need to setup custom screen resolutions and configure the top row on the keyboard - so a bit of manual setup. Cloudready does support Linux apps - so you do get the best of both worlds. The only down side is that on the current version of Cloudready is that it won't sleep - just shuts down.

      Yes you have to flash a modified BIOS - so on a Pixel, you have to take the back off and remove the BIOS lock screw. Mine is on the Johnlewis bios - not tried the other one.

      If you flash the BIOS it goes straight into the OS you have installed - no CTRL-L

      I've not seen any other guides - I just put this together from the bits and pieces I found online. Just remember, if you choose to flash your Pixel there is a chance you will kill it - unlikely - but possible. Good luck.


Post a Comment

Popular posts from this blog

Delete a specific email using GAM

If a user send an inappropriate email to a loads of people or get stung by some sort of email exploit you can quickly delete the email from all of the recipients using a GAM command.
Step 1 - get the email header Go into Google Vault and search for the offending user or someone known to have got the message.
Click show details and grab the email ID. This will be a long string of characters followed by
Step 2 - find out who has the email Go into Google Vault and find the original message sent by the offending user. Look at the details to see who got it. Copy the list and dump it into a spreadsheet. Clean up to just a list of emails with a column header 'mail'. Save as a csv file.
Step 3 - delete messages with GAM Put your CSV file in your GAM folder - this e.g. assumes its called mail.csv
gam csv mail.csv gam user ~mail delete messages query rfc822msgid:MESSAGEIDHERE doit

The alternative nuke option is:
gam all users delete messages query rfc822msgid:MESSAGEI…

My favorite GAM commands - well a few of them at least!

Where would be without GAM? Paying for expensive syncing tools or doing tedious manual tasks in the admin console. GAM can automate most things you might want to do in G Suite. So these are a few of my favourite commands - one I use either as part of a batch file - or just standalone. There are loads more - but these are ones that are used daily.
Classroom Create a spreadsheet of all your domains classes - gam print courses todrive

Create a spreadsheet of a teacher's classes: gam print courses teacher todrive

Bulk create classes:
gam csv classes.csv gam create course alias ~alias name ~alias section ~subject teacher ~teacher status ACTIVE

where classes.csv is a list of classes you want to make.

Add teachers:
gam csv teachers.csv gam course ~alias add teacher ~teacher

Add students:
gam csv students.csv gam course ~alias add teacher ~student

Sync Students (in this example to a group - but could be an ou/csv file)
gam csv groups.csv gam course ~groupmail sync students g…