Step 1. Download required files

There are several requirements for this to work.
  • 2 USB drives of decent size (8GB is a good size)
  • A chromiumOS install ( we suggest Arnold the Bat Special builds) available HERE. CloudReady does not work with this!!
  • 2 Recovery images (we suggest EVE and Caroline) available HERE.
  • available HERE.
  • A Live linux distribution that contains Gparted live ( TuxBoot is a great option to create one)

Step 2. Install ChromiumOS

Warning! Installing Chromium OS on a hard drive formats the entire drive not just a partition.

Extract your ChromiumOS intsall and use software called Rufus (recommended) or Win32diskimager to flash the image file to your usb drive.

Restart your computer once completed and then boot from the USB drive.

Once you've done this, you will be on the Chromium installation screen. From here, you need to install Chromium to your hard drive, first by pressing Ctrl+Alt+F1, logging in as "chronos".

You then want to find out what drive you wish to install this too. Run the following command:

sudo fdisk -l
This will list all your available drives and there drive names and their size e.g /dev/sda

When you have found the correct drive you wish to install to, run the following command where *YOURDRIVEHERE* is replaced by your actual drive e.g sda

/usr/sbin/chromeos-install --dst /dev/*YOURDRIVEHERE*
Once Chromium OS has installed, simply turn off your computer, remove your memory stick and turn back on.

You have now installed Chromium on your HDD.

You are now free to format your memory stick, instructions on a safe method can be found here. Do NOT use any other format method as there is a high risk of corrupting your memory stick.


Step 3: resize a partition

Boot into your Live Linux USB or Gparted live USB. Depending on the distro you choose, you may be asked whether you want to install. You DON'T want to install - make sure if you're prompted to choose "Just trying" or "Live". 

Then follow this video (only follow the start if you're using Gparted live) and resize the sda1 and sda3 partitions as shown. You only need to shrink sda1 by about 5 GB and expact sda3 by the same amount.

You can then turn the PC off. Make sure you don't boot back to your installed Chromium OS in this stage - Chromium will try to repair itself because you've modified partition sizes. The good news: you're almost there! Now you'll need your 2 USBs, or if you're really crafty and can somehow figure out how, you might only need 1 (if you're an amateur/intermediate with Chromium you should really have 2).
Step 4. Upgrade to ChromeOS through Chromefy

On 1 USB, you need that same ChromiumOS build from before, o n the other, copy the following 3 files as you would any other file:

  • 1) the extracted copy of the recovery file (we suggested EVE earlier) ending in .bin.
  • 2) the extracted Caroline recovery file ending in .bin
  • 3)

I highly suggest you rename the recovery file 'recovery.bin' and the Caroline recovery 'Caroline.bin'. This is for later.
Now, plug in the USB with ChromiumOS flashed onto it, and boot into it.   

On my laptop, it prompted me when I selected my USB which type of boot I want, and you need to select 'Alternate USB boot'. When you do this, you'll notice after you get past the Chromium splash screen that you see the install wizard again: this is a good and necessary sign! 

We'll press Ctrl+Alt+F1 as we did before in order to enter the chronos shell. Enter the "chronos" username again. Then, plug in the USB with the 3 files on it, into another USB port on the laptop (don't unplug the one with Chromium on it!) 

We'll now use the
Linux command, which checks what partitions are available on your PC. You'll need to determine what partition is the one with the files on it. The size that is displayed may help you, as well as the fact that the partition you're looking for will likely only have 1 option.
Once you've found it, we'll mount it to make it available to us for installation. Enter these commands below one by one, and make sure to replace the 'X' in sdX with your computer's hard drive (normally 'a')and the full name of the recovery.bin files you downloaded earlier, you can use 'tab' to autocomplete names.

sudo mkdir /home/chronos/tempfolder
sudo mount /dev/YOURDRIVEHERE /home/chronos/tempfolder
sudo cd /home/chronos/tempfolder
sudo mkfs.ext4 /dev/sdX1

Then, press Ctrl+Alt+F1 to return to Chromium, press Shut Down, remove your USB and turn your PC on. If everything's gone well, you're now running ChromeOS, and should see a Google logo greeting you when you start up.

This page is ONLY for Project Mercury updates. This is the change log and updates for Chrome OS on mobile devices.

Update 08/010/2018

Project Mercury confirmed working devices (images to be released shortly):

Sony tablet Z Gen 1-4.
Google Nexus 10.

In development:
Samsung S8 partially working, GPS, Bluetooth and touch issues present. (Exynos)
Galaxy s9 in development. Knox proving to be an issue on this device. (Exynos)

Dropped support:
Samsung Galaxy s6
Samsung Galaxy s6 edge
Samsung Galaxy s7

Repost due to accidental deletion. Oringinal content and support comments can be found HERE!

Chrome OS is the operating systems installed on Google's Chrome devices based on Chromium OS. It not only looks prettier but also comes with a few extras here and there.

Chromium OS, an open source OS made popular by the amazing Hexxeh and Arnold the bat. Since then, many have wondered how to get Chrome OS and I'm here to tell you how.

This will work with Apple OS X computers too, as long as they are Intel based and hardware compatible.

The total amount of time for you complete all of the instructions should be about twenty minutes in total.

Chrome OS also includes all the codecs and missing pieces from Chromium OS such as flash and MP3. If you wish to get the codecs that are missing without upgrading to Chrome OS due to any reason, there are instructions at the top of the screen on how to do this.

You must read the disclaimer which can be found here.

Instructions on how to dual boot can be found here or under the instructions heading.

All updates regarding this and anything else are now posted in the updates post.

Step 1. install Chromium OS.

First install Chromium OS onto your hard drive. Instructions on how to do this can be found here!


NOTE: Not all graphic cards are supported, if you get a blank screen before or after the Chromium logo then try the on board graphics if possible, if not, your hardware may not work with Chromium.

Installing Chromium OS on a hard drive formats the entire drive not just a partition. Remove ANY other drives you do NOT want Chromium OS installed to. This includes removable drives such as USB as SD cards. If you have multiple drives and can't remove them, follow these instructions to install.

Boot from the USB and follow the setup page, if you have no network try another build. If you used Arnold then use Hexxeh etc. 
Once you have set up your Chromium OS, log in using a Google account.
Now enter a terminal by pressing Ctrl + Alt + T. You may need to alternate between Alt and T while holding Ctrl.

Here you will need to run the command:

You will then be prompt for the username and password which are:

facepunch for hexxeh builds and there is no password for bat builds

Follow the on screen prompts.

Once Chromium OS has installed, simply turn off your computer, remove your memory stick and turn back on.

You have now installed Chromium on your HDD.

You are now free to format your memory stick, instructions on a safe method can be found here. Do NOT use any other format method as there is a high risk of corrupting your memory stick.

Step 2. Upgrade to Chrome OS.

Boot into Chromium OS and open the developer console
CTL + ALT + F2

  • you may need to alternate ALT and F2 while holding CTRL.

Here you will need to type the command:
sudo su

Then you will need to follow the prompts for username and password as listed above.

There is now one more command that you will need to run that is the final step in installing Chrome OS.

bash <(curl -s -L
Type the above command and then press enter.

you will now be given the options to select a build of Chrome OS, each build is for a different Chromebook/Chromebox and so hardware varies with each choice. Find a complete list with numbers here!

Note: If you do not get this far due to a read write error or other problems, you can continue by using the update method 2 mentioned in the instructions at the top of the page as this will allow you to continue.

Pick the build of Chrome OS you would like by typing the corresponding number and pressing enter.

The script will then begin to download and install Chrome OS for you, this will take about 2 minutes on a 120Mb internet connection.

Once the script has finished running you are ready to reboot.

(You will know if the script has finished running as you won't be able to exit the developer console by pressing

Reboot and you will now have Chrome OS installed!!!

If Chrome OS then does NOT boot, the image of your chosen Chrome OS install simply doesn't work on your hardware so just repeat the install of Chromium OS and try another build. If none of the recovery images boot then you will not be able to use Chrome OS and will have to stick with Chromium OS.


Be aware that booting Chrome OS will produce a message regarding malformed ID's. This is simply from a health check upon boot, simply close this and continue using Chrome OS. This poses no risk or issues. METHOD TO BYPASS IS UNDER INSTRUCTIONS.


Once Chrome OS has been installed and you have logged in you may receive an error stating that your account has been used on a higher build number than the current install, all this means is that your user profile has been loaded from the chromium OS install from earlier and as chromium OS uses a newer source code, Chrome OS thinks you have downgraded, to fix this simply go into settings -> advanced settings -> power wash, let this run for about two minutes and you will be good to go. YOU WILL LOSE ALL DATA WHEN DOING THIS!
As many of you know, I have been running this site for a while now and nothing has really been well done or published correctly and everything seems to be missing loads of information. So let me just correct that!

The entire thing done on this site is called the #BringChromeHome Project. The project is basically a way too ambitious project of showing how Chrome OS is a great platform to use in both large enterprise environments and smaller ones like your home.

The project doesn't just focus on Chrome OS but also Chromium OS on which Chrome OS is built from. Chrome OS is essentially identical to Chromium OS but with a few licensed things here and there and a little bit of a user interface change that is purely design and function remains identical.

The #BringChromeHome Project focuses mainly on bringing Chrome OS to desktop and laptops however it also focuses on mobile devices. There hasn't been much news relating to Chrome OS on mobile devices however there is some good news coming very soon.

After being in touch with someone who wished to know more of my work involved in this I'm going to give you some background information on the project and be more transparent with whats currently under development and how far along they are!!

The project was started in February 2013 based off a script I had written for person to use about 6 months before hand. Since then, the script has been through many changes to accommodate for changes in Chromium OS and Chrome OS and also to tidy things up and make things run much faster.

The team currently, as has only ever consisted of myself with brief help from one external person. This means I currently, manage the script, modify, test and deploy anything to do with the project.

The current script is a modified script of the original that is still available as a secondary use script if the first should fail as their updates methods vary slightly. The current script was modified by Rowen Allen who has been linked several times throughout the site. He initially added an auto build detect to the script for use when updating and also made the script slightly shorter and run faster. 

Although Rowen was never part of the project team he certainly improved the script beyond what I could and this has been a major help to the project.

Nothing much has really changed since the script was edited other than testing on other devices along side this.

Current devices being tested with Chromium OS and Chrome OS:

  • Nexus 4 - Chrome OS working image with missing device components
  • Nexus 5 - Chrome OS half working image with many missing components
  • Nexus 7 2012 - Fully working Chromium OS with bugs and glitches
  • Samsung Galaxy S4 - Chromium OS working with many missing components
  • iPhone 4- Chromium OS boots but nothing currently works
  • iPhone 5 - Chromium OS has unstable boot and nothing currently works
  • Xperia Z - Chromium OS Boots, missing many components / Chrome OS boots but nothing works.
  • Xperia Z Tablet - Chromium OS Boots, missing many components / Chrome OS boots but nothing works.
  • Hp Slate 7 - Chromium OS boots, everything appears to work. 
The above listed devices outline the current project in terms of bringing Chromium/ Chrome OS to mobile devices.

Many of the devices have some degree of functionality but have issues regarding battery life and many things appear to not work such as Bluetooth or WIFI for example.

This device breakdown is from my last note take of what was working on the 28/9/2014. Many things have changed since then so be aware things have improved and there is VERY good news on the way in regards to some of these devices which should hopefully be announced during my time in London around December the 12th.

Hopefully this has given you a bit more of an insight into the #BringChromeHome project and how things are progressing. If you have any questions, queries or recommendations, then please, do get in touch at

All updates to Chromium OS and upgrading to Chrome OS will now be posted here.

UPDATE: 15/06/2017

Once again sorry for the heavily delayed updates. Chrome OS currently has 135 devices available. Unable to change order displayed as the conf file MUST match the verified order by Google.
Note: Device 79 is listed as N/A. This is an unknown model built by Quanta. Laptop is all that I can confirm. (test at own risk). Project Mercury update:
Project Mercury will have its own updates post on here and be similar to the #BringChromeHome project. Chrome OS is currently fully working on Sony Tablet Z (1-4) and Nexus 10. Partially working on Samsung S6 and S7 with current work on S8 beginning shortly. Will begin testing on Google Pixel shortly.

More updates to come within the next 2 days! Confirmed! maybe!

UPDATE: 13/12/2016
Sorry for the 10 months of nothing however this has become very very tedious to maintain along with the other projects involved such as Chrome OS on android etc...

MAJOR UPDATE! The build numbers NO LONGER correlate to what they did previously. This will be corrected within the next couple of days.
The previous list of numbers will be on the build numbers page underneath the new/temp numbers so you can find out what your new number will be.

Chrome on Android is now Project Mercury. Fully working on Tablet z and Nexus 10. More details shortly.

Update: 22/02/2016
Big news! I have started a new project as part of the #BringChromeHome project. I'm currently building a custom Chrome OS with built in updater and all the small things Chromium OS is missing. Not much news yet but I would like some alpha testers very soon!!

Update: 18/02/2016

79 builds are now available, this includes the Chrome OS builds that are for OnHub routers. I highly advise not using these as I have zero idea what they are like as they have never been tested outside their initial hardware. I may remove these.

Update 20 04/11/2015

Change in Script to cycle through long list of builds available. Stops the list being too long to fit on the screen. Fix Provided by Rowan Allen (

Link to the script should never change as all changes are made in a file referenced in the upgrade script.

Total Number of builds currently stands at 75.

Update 19 01/10/2015

Due to the number of builds, the top of the script will get cut off when selecting your build. This page contains a list and their relating number.

New look.

UPDATE 18 21/09/2015
Major update!

Due to being a complete idiot, I accidentally deleted the post! I have recreated it however all the comments are missing so if you need help just ask me :) SORRY!

Changes have been made to the script which has fixed the issue with the new config file layout. All 62 current images are now available.

The build list will be updates weekly on Saturdays at 9PM GMT to reflect if any new builds available

Exactly 18,259 lines of code have been removed as unneeded within the config file.

Currently 61 builds are available.

Update 17 16/09/2015


MAJOR ISSUES WITH SCRIPT! Due to Google making changes to their config file, the current script does not work. I have modified the script as a temp fix. You will only have access to builds available on the 10 Jun 2015 and nothing newer. I will hopefully have a fix in place for this soon.

Update 16 15/09/2014

Made changes to the disclaimer and where it can be found. It can be found here.

Making minor changes to the upgrade script, new script should be posted within the next couple of days.

Working on porting Chromium OS to Sony Xperia Z tablet.

Functioning Chromium OS on Nexus 5. NFC is also working with limited application. Bluetooth does NOT work and neither does front camera.

More news and possible image coming soon.

Update 15 03/09/2014

Decided to have a new design for the site. Hopefully this gives a much cleaner look although the content is pretty much the same.

Moved a few details from the main tutorial page to the instructions page and references added.

Update 14 31/08/2014

Script hosting has been changed and so the URL has changed. The new script can be found @

There appears to be no issues with this as of now. This will work exactly the same as the previously correctly hosted script.

Update 13 13/08/2014

Script hosting has been changed and so the URL has changed. The new script can be found @

There may be issues with this new hosting so please be patient and let me know if there are any issues.

Update 12 12/08/2014 critical!

Change to script hosting.

Due to Rowan's change of circumstance, he will not longer be hosting the script and as such I will move to hosting the script either myself or through a third party provider. Please be aware, that until the script has been hosted elsewhere, the script will NOT work.

Expected to resume by 18:00 GMT today.

I would like to thank Rowan for his major contribution to this project and all the time he has spent on this.


Update 11 05/08/2014

Page giving info on how to upgrade to Chrome OS on your USB drive without having to install it to your HDD/SSD.

Please be aware it will not always work and is experimental.

This can be found under the instructions tab or here!

Page on how to dual boot using two drives as well as one has also been posted. This can be found under the instructions tab or here!

Update 10 05/08/2014
Copyright notice!!

Please note that although this tutorial is intended to help everyone, some people have been claiming this work as their own and distributing the script to make money from YouTube monetisation and blog posts etc. Please be aware that although I encourage you to spread the word on this, the scripts used are protected by copyright and as such, copyright claims have been made to remove such material from the internet.

By all means, tell people about it, in fact please do, tweet it, blog it, G+ it just do not make money from that specific page.

Update 10.2:
Started work on Chrome OS on the Xperia Z tablet. Not much info to give at the moment but more news will follow shortly, this is the because of the slow progress on the Nexus Chrome OS. MORE NEWS SOON!

Thank you for your time and support with this project.


UPDATE 9 26/05/2014


Major script update: - Script has been updated to run faster and also allow for easier updating.

The script link has been changed!

New update method. The new script performs a build check and will automatically install the newer build number that matches your original build choice. Simply run the script used to originally install Chrome OS. BE AWARE THE ADDRESS USED HAS CHANGED SO MAKE SURE YOU USE THE NEW ONE! THIS HAS BEEN UPDATED ON THE MAIN PAGE AND ALSO THE UPDATING CHROME OS PAGE!!

UPDATE 8 7/03/2014

  • There is now a method to bypass the malformed hardware ID error message upon boot.
  1. Go to settings
  2. Under the 'users' heading, select 'manage other users'
  3. Untick 'show usernames and photos on the sign-in screen'
This may require 2 step verification users to enter a new code every time during logging on however this may not be required as the device should remain linked to your Google security configuration.

  • Chrome numbers. Please be aware that if you are installing Chrome OS onto a Chromebook or Chromebox due to any reason, you will still receive the malformed hardware ID message. I will not give instructions to add a Chrome number even if you already have a Chrome OS device as the message will still show due the supplied Chrome number not matching the actual Chrome number of your device.

UPDATE 7 5/03/2014

  • Finding errors with the script. Corrections soon to be made
  • Solution: Use the update to Chrome OS section and use that method.
  • Minor changes to be made to script.

UPDATE 6 13/01/2014
  • Added a forum to the blog, contains compatible hardware. Needs building up so please contribute with your hardware.

UPDATE 5 11/01/2014
  • Currently working on methods to upgrade Chromium OS to Chrome OS on a USB memory stick without having to install it to a HDD. Several plausible methods, including use of GRUB by myself & +Keith Valdez.
  • Managed to upgrade Chromium OS on a Nexus 4 to Chrome OS. Major bugs include; no touch, no connectivity other than micro usb which keyboard and mouse DO work. Nothing functions as should.

UPDATE 4 7/01/2014
  • I am currently working on the issue of not being able to upgrade Chromium OS to Chrome OS while on a USB memory stick due to the partition table type.
  • Managed to install a bootable Chromium OS on a nexus 4 phone, touch was not working and neither was sound or WiFi. Keyboard and mouse worked using a micro USB adapter. Major work in progress.
  • New-ish website design, same as old design but different colour scheme and also corrected the Java script issue of not being able to reply.

  • I am making changes to the script used for the upgrade process so you may encounter errors with odd returns such as 'I can't do that so I will now die' please be patient while I make these changes and this will hopefully be completed by Saturday 4th Jan 14. Thanks 

  • There is now a way to upgrade Chrome OS without having to start from a fresh install of Chromium OS. To find out how, check the instructions tab at the top of the page

  • When upgrading to Chrome OS you will now be presented with a malformed hardware ID error message. This message is simply a hardware health check that has been implemented into the Chrome OS code, this does not mean there is anything wrong with your computer or anything else. There is nothing that I can do to remove this. It is perfectly fine to carry on using Chrome OS.

About Me

Not much to say other than an IT Systems Analyst and Google Systems and Service vulnerability Analyst.

Previously a Windows 8/8.1 Developer and also Skype for Windows 8 Developer.

Also used to work as an Apple Systems Specialist, (the people who actually do the work, not the morons in store.)