Updating Chrome OS





Updating Chrome OS is now possible due to the Chrome OS dev install. 

If you installed Chrome OS using the main method on this blog, Chrome believes it is in Dev mode even though it technically isn't. This allows you access to a full Shell terminal for upgrading.


Step 1: Confirm that your build has a dev install by entering the terminal (CTL+ALT+T) and entering the command:
Shell

If the terminal accepts the command and then writing changes colour, then you can proceed to step 2, if not and you get an error message, then your build is not actually a dev install, this would apply to those using a build roughly before 26. To find out your build, go to the help option under settings. If you are running an older build then you will need to start again from the Chromium OS install.

Step 2: Open the Dev terminal (CTL+ALT+F2, you may need to hold CTL and alternate pressing ALT and F2).

             
Step 3: Run the command:
sudo su

Step 4: Log in using 'chronos' as the username, no password should be required, but if so it is 'facepunch'.

Step 5: Run the command:
bash <(curl -s -L https://goo.gl/1PhRNb)

Step 6: The script will run and automatically find your build and download the relating build and install it over the top.

Step 7: allow for Chrome OS to install, you will not actually get a completed message, you will get a time completed message, after it has finished extracting and unpacking etc. It is best to leave this for about 20 minutes just to make sure it has installed all the required components.

Step 8: reboot by either a reset button on your computer ( if it has one) or by cutting the power by holding the power button.

Note: Once you have rebooted, you may get a screen displaying a message about a kernel boot, this is nothing to worry about, this screen was originally hidden in Chrome OS. Chrome OS will then boot into your newly updates Chrome OS.

Step 9: Confirm that the update has completed by viewing help section in the settings.

96 comments

  1. Hi Seth,
    I have a HP Folio 9470m Elitebook, runninng Chromium 28.0.1484.1 (Developer Build 195382), platform 4028.0.2013_04_20_1746 (Developer Build - hexxeh) vanilla x86-generic. I have a 500GB SDD (sda) and run Chromium on a 30GB mSATA disc (sdb?). Triple booting with Win7 and Ubuntu from the SSD and Chromium for the mSATA.
    I followed your instructions as above, but during Unpacking I get the following error:
    RootFS Start: xxx RootFS size: xxx
    mount: special devices /dev/sda12 does not exist.
    I presume this is because of the fact I install to /dev/sdb. There is a /dev/sdb12, I check in the file system. Can I edit your script?
    Can you recommend a distribution as well (1-18). I downloaded HP Chromebook 14.
    Thanks, Edwin

    ReplyDelete
    Replies
    1. The best way to resolve this issue is to remove all the other hard drives while doing this as it prevents issues with default install locations etc and that build would be the best for that laptop, the pixel would also be a good build choice

      Delete
    2. I ran into this issue as well using an 8gb USB drive. I worked around it by...
      1. download script with "wget http://goo.gl/8v1ZkV"
      2. edit script with "vi 8v1ZkV"
      3. in top section change WORKDIR=/home
      4. at end of file change /dev/sda12 to /dev/sdb12
      5. and on the dd= line change sda3 to sdb3
      6. press the Esc key
      7. type "ZZ" to save the script
      8. type "bash 8v1ZkV" to run modified script
      9. pick a release and hope for the best!

      I had luck with (#14) HP chromebook 14 q000-q099? release on a Lenovo Thinkpad T440p 20AN-006FUS
      Everything works but on first boot it got stuck checking for updates, let it sit awhile and just power it off and on again. Booted just fine after that.

      Delete
  2. Quick question; will updating Chrome OS cause all files stored locally to be deleted? Thanks.
    -Matt

    ReplyDelete
    Replies
    1. Hi Matt, the script to upgrade should not remove local files as it does not write over the user area however I would back IP your files to gdrive just in case.

      Delete
  3. Is there anyway to autoupdate? Will we have to manually update every time?

    ReplyDelete
  4. Auto updates will not work with Chrome OS as it requires a Chrome number which I will not give instructions on how to obtain as it would allow you to claim chromebook offers.

    ReplyDelete
    Replies
    1. This comment has been removed by the author.

      Delete
    2. Is there no way to use an existing Chrome Number (one where offers have been claimed; resolving the moral dilemma), but allowing auto updates. I suspect like most on this thread, it would valuable to gain the autoupdate capability on an old laptop given to less technical family members/freinds?

      Delete
  5. Hi Seth, I've tried to do this but I'm told I have insufficient space in the temporary folder that is automatically assigned - any ideas? thanks

    ReplyDelete
    Replies
    1. This is normally only when trying to upgrade the USB with chromium on it, I'm currently working on sorting this out so you can upgrade the USB but at the moment it isn't possible and you should not get this issue when using a HDD as the partition table is different to a USB installed chromium

      Delete
  6. Hi Seth - when I run 1.sh it stops after (slowly) listing the first 4 options. The computer isn't frozen - any suggestions?

    ReplyDelete
    Replies
    1. How slow are we talking as this depends on your internet connection. This can take about half an hour depending on your internet connection. This also depends on googles data traffic as this information is pulled from their servers.

      Delete
  7. This comment has been removed by the author.

    ReplyDelete
  8. Hey Seth,
    I can't manage to get in developer mode. and as normal user i can't use the terminal.
    everytime i try to get in developer mode my computer just shuts down.

    pressing esc + f3 + power should be my first step but as i said my pc just shuts down.

    any thoughts?

    ReplyDelete
    Replies
    1. I think developer mode is ctrl + alt + f2. Or ctrl + alt + t to enter crosh shell.

      Delete
  9. I've just recently found this blog of yours and I think it's quite cool! It's like you're giving free tech support for the chrome OS. It's rare to find an atlruistic spirit in the digital world, especially when it comes to software concerns. Definitely gonna follow the steps you laid out here. Thanks!

    Carlene Schnitzer @ stewarttechnologies.com

    ReplyDelete
  10. Hi, I followed all the steps on My Parallels VM of Chrome OS, but when I run the script I just get a request for password and then this :
    initctl: Unkown job: powerd

    Any ideas of I'm doing wrong?

    Thanks

    ReplyDelete
  11. Hi,
    I managed to create an automated script (i.e. no user input required) to update Chrome OS which is also a lot faster that http://goo.gl/4suhf and after the first run, checks that the latest update is different to the installed version.

    Anyway, I need to know two things:
    How would I set this as a startup program without root permissions(ideally, I can implement the commands into the script so that the first time you run it, it is set as a startup program)?
    Most importantly, is there a terminal command which would allow me to alert the user that an update has been installed and that the user should restart?

    Link here: https://drive.google.com/file/d/0B8MdcIpGk1y8d3NmNjlVOGNiTWc/edit?usp=sharing

    ReplyDelete
  12. is there anything you can do to make the script not take like 20 minutes to list the builds? Its quite annoying to have to wait, when i know what build works with my laptop....

    ReplyDelete
    Replies
    1. I edited my script for you so that it prints everything super-quickly and gives you a choice.

      Just do "curl -L http://goo.gl/rxdhN9 | bash"

      I'm working hard on finding a way to bypass the HWID check as well: Watch this space!

      Delete
    2. There is an issue with your script. It keeps going through the build options but never let's you pick one, even if you don't type anything it says it didn't understand that and goes back through the options. Just so you know :)

      Delete
    3. I'm not quite sure why it did that. Nothing wrong with the script.

      This worked for me: "bash <(curl -s -L http://goo.gl/GYWcgT)"

      Delete
    4. It worked for me. I downloaded the new script from http://goo.gl/rxdhN9 and I can confrim that it's quite a lot faster than original one.
      Bypassing the HWID would be cool, Rowan, I'm looking forward to it.

      Delete
  13. I am finding that the upgrade no longer works, it is installs as it should be it never updates the OS. I have a Acer AO756-2623 with 33.0.1750.152 and it is stuck there. I have used the script listed above before and it upgraded fine. Any suggestions?

    ReplyDelete
    Replies
    1. It's not to do with my script - I didn't change the installation process, only the choices. It's likely that the update corrupted your kernel(this is the case if your caps-lock indicator blinks) , which would be a problem with your machine, or possible if you chose an incompatible image (such as if you upgraded from a 32 bit image to a 64 bit image by choosing a different model).

      In short, you can't fix it and you'll have to reinstall. In future, perhaps try not to do anything on Chrome OS during the upgrade.

      Delete
  14. please help me!
    I'm stuck on step 6!
    nothing hapenning when i type the commend...
    BTW, what is step 5?

    ReplyDelete
  15. Can,t update with new script. "/dev/fd/63: line 902: initctl: command not foind" error appers after entering "bash <(curl -s -L http://http://goo.gl/eIAcL5)". What am I doing wrong?

    ReplyDelete
    Replies
    1. There may be an issue with the FTP server that the script is hosted on. Try this command instead

      bash <(curl -s -L http://goo.gl/GYWcgT)

      Regards

      Taron

      Delete
    2. Make sure you run it as root.

      Delete
  16. I am getting the same error as shining17, I modifed the path to include /sbin since that is where initctl appears to be, now I am getting this error
    initctl: Rejected send message, 1 matched rules; type="method_call", sender=":1.28" (uid=1000 pid=10659 comm="initctl stop powerd
    ) interface="com.ubuntu.Upstart0_6.Job" member="Stop error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")

    ReplyDelete
    Replies
    1. There may be an issue with the FTP server that the script is hosted on. Try this command instead

      bash <(curl -s -L http://goo.gl/GYWcgT)

      Regards

      Taron

      Delete
  17. Hi, using the new script for updating Chrome Os gives following error : /dev/fd/63: line 955: version.txt: input/output error.

    I used a SSD 32G and all used it for Chrome OS.

    What do I do wrong ? Is there a solution ?


    Thanks

    Robert

    ReplyDelete
    Replies
    1. There may be an issue with the FTP server that the script is hosted on. Try this command instead

      bash <(curl -s -L http://goo.gl/GYWcgT)

      Regards

      Taron

      Delete
  18. Hi Taron , tried new command and same error, other line error.

    Regards

    Robert

    ReplyDelete
    Replies
    1. I've had a look into this and spoken to the person who helps with this and there isn't actually anything wrong with the script. What build of Chromium OS did you use as this is sounding like a Chromium OS related issue.

      Delete
  19. got the same error... what is wrong?

    ReplyDelete
    Replies
    1. I've had a look into this and spoken to the person who helps with this and there isn't actually anything wrong with the script. What build of Chromium OS did you use as this is sounding like a Chromium OS related issue.

      Delete
    2. i used the latest hexxeh build (Build 4028)

      Delete
    3. I am currently working on a temp fix for this as we are unsure what the issue is as the line with the error does not actually have any command based code. I will hopefully have this posted by 12pm tonight. Keep an eye on the updates post.

      Delete
  20. Hello Taron,

    I upgraded from chromium OS to Chrome OS using the build for HP Chromebox. Version 34.0.1847.118 platform 5500.100.0 stable channel zako.

    It works very well, has no bugs but is missing the updates.

    Regards

    Robert

    ReplyDelete
  21. Hello,

    Update does not work for me !

    robert

    ReplyDelete
    Replies
    1. Hi Robert, I am currently working on a temp fix for this as we are unsure what the issue is as the line with the error does not actually have any command based code. I will hopefully have this posted by 12pm tonight. Keep an eye on the updates post.

      Delete
  22. Tryed to update the system using "bash <(curl -s -L http://goo.gl/GYWcgT)". Still getting an error. What am i doing wrong? And how can I get the latest update in this case?

    ReplyDelete
    Replies
    1. Hi, I am currently working on a temp fix for this as other people seem to be having a similar issue. What is the error message you are presented with?

      Delete
  23. Replies
    1. It isn't possible to provide a wifi fix if your wifi does not work with Chrome OS. If you are using Chromium OS you can attempt to compile for your wifi module but there is no promise you could get it to work. The easiest way to get a working wifi connection is to find a wifi card that is in one of the chromebooks and use that in your laptop.

      Delete
  24. Hello Taron
    Problem of updating is now solved. I did a new install of chromium build, upgrade to chrome os and now your scripts work fine. Thanks a lot for your help.

    Robert

    ReplyDelete
  25. This comment has been removed by the author.

    ReplyDelete
  26. Hi, I was wondering if there was a way to edit the boot parameters on Chrome OS like Grub. My computer boots up in 10 seconds, but the backlight is off. It takes another 30 seconds for the backlight to come back on. I have boot parameters that I have used with other linux os's and I was wondering where to put the parameters. Thanks -John

    ReplyDelete
  27. This comment has been removed by the author.

    ReplyDelete
  28. This comment has been removed by a blog administrator.

    ReplyDelete
    Replies
    1. Just curious, but why have you posted this????

      Delete
  29. Hello,

    I have successfully made the chromium to chrome conversion on an old Sony Vaio VGN-G1. However, I lost both wi-fi and LAN access (via satellite). Is there anything I can do to gain at least the LAN access? I understand because of many chromium installs (Hexxeh, Arnold the bat) that wifi comes and goes depending on the image downloaded. I have had both wi-fi and LAN success with chromium builds on this machine over the last couple of years.

    I am not super technical but from other comments made about 32 bit, I decided to use the CR-48 download. I did this with both http://goo.gl/GYWcgT & the 1.sh script. The results were the same, no LAN, no WiFi. One other image download, stated that it failed because it needed an x86-64 cpu so I assume I need 32 bit. 1) Are there any other images that might work? 2) Is there any way to get the LAN working on the CR-48 image? I 'did' connect the LAN cord directly from the Satellite router to the Sony PC. Thanks for any help you can give me.
    --Karen

    ReplyDelete
    Replies
    1. Hi, the only thing you can do is try different builds. Find a chromebook that has an Ethernet or Wifi adapter the same as what is in your laptop and try that build.

      Delete
  30. I also get the syntax error after having entered the modified code to correct the line 902 error Taron...what can I do to get Chrome OS or total Chromium OS updates? Thanks!

    ReplyDelete
    Replies
    1. Hi,

      You can use the Update Chrome OS 2 method for the moment while I try and find this issue.

      Taron

      Delete
  31. Hi taron,

    New script (tl2MOe) for updating Chrome OS does not work. The previous script (eIAcL5) did work fine. Any suggestion how to update Chrome OS to the new build.

    Thanks and Regards

    Robert

    ReplyDelete
    Replies
    1. Thanks for the notification, when you try the new script, what message do you get?

      For now you can use the Update Chrome OS 2 method under the instructions tab

      Taron

      Delete
  32. Hello taron,

    first error line = : invzlid option 12 : set: -
    a whole lot of lines with errors all starting with /dev/fd63 : line 13 : $
    these errors continue till line 53

    Robert

    ReplyDelete
  33. hi Taron, thank you for the support. I just began to follow your tutorial, but I can't go further since my netbook (HP MINI 110 1030LA) does not detect my wifi signal, i'm trying to install the chromium ChromeOs Vanilla version and I can't pass the welcome window. what can I do? Should I try the LIME version? If that works, can I use this same tutorial to upgrade to Chrome Os? Thanks Again; sorry for my bad english, I'm from Mexico.

    ReplyDelete
  34. Hi Taron,

    This are the errors I get with the new script.

    localhost / # bash <(curl -s -L http://goo.gl/tl2MOe)
    : invalid option 12: set: -
    set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
    /dev/fd/63: line 13: $'\r': command not found
    /dev/fd/63: line 16: $'\r': command not found
    /dev/fd/63: line 21: $'\r': command not found
    /dev/fd/63: line 26: $'\r': command not found
    /dev/fd/63: line 29: $'\r': command not found
    /dev/fd/63: line 34: $'\r': command not found
    /dev/fd/63: line 38: $'\r': command not found
    /dev/fd/63: line 39: $'\r': command not found
    /dev/fd/63: line 46: $'\r': command not found
    /dev/fd/63: line 49: $'\r': command not found
    /dev/fd/63: line 50: syntax error near unexpected token `$'{\r''
    'dev/fd/63: line 50: `DEBUG() {
    localhost / #

    Regards

    Robert

    ReplyDelete
  35. Exactly same error as Robert right now

    ReplyDelete
  36. Hello Taron,

    After your personal Ice Buck Challenge did you have the opportunity to look at the update script for Chrome os?
    Regards

    Robert

    ReplyDelete
    Replies
    1. Hi Robert, I am still looking at the script as the error you're getting shouldn't be possible. The lines of code it mentions don't actually have any code in them and nor should they.

      For now you will have to use the 'Update Chrome OS 2' method. Although slower and less convenient, it does still work.

      Taron

      Delete
    2. Hi Robert,

      Please use the same console command but substitute the URL for this one.

      http://goo.gl/BxCiRq

      Let me know how this goes as I'm currently unable to test this as I am at work.

      Taron

      Delete
  37. Hello Taron,

    Tried the new script but same errormessages. The only script that is still working is : http://goo.gl/eIAcL5 but this script gives the 32 pssoble choices but does not update the cript I use.

    Robert

    ReplyDelete
  38. Hi. Yes i get the exact same error messages as Robert does. Both with the old adress and the new one

    ReplyDelete
  39. plz help,
    localhost / # bash <(curl -s -L http://goo.gl/tl2MOe)
    : invalid option 12: set: -
    set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
    /dev/fd/63: line 13: $'\r': command not found
    /dev/fd/63: line 16: $'\r': command not found
    /dev/fd/63: line 21: $'\r': command not found
    /dev/fd/63: line 26: $'\r': command not found
    /dev/fd/63: line 29: $'\r': command not found
    /dev/fd/63: line 34: $'\r': command not found
    /dev/fd/63: line 38: $'\r': command not found
    /dev/fd/63: line 39: $'\r': command not found
    /dev/fd/63: line 46: $'\r': command not found
    /dev/fd/63: line 49: $'\r': command not found
    /dev/fd/63: line 50: syntax error near unexpected token `$'{\r''
    'dev/fd/63: line 50: `DEBUG() {
    message is shown, how to solve

    ReplyDelete
  40. Hey Guys,
    You can fix the errors in the tl2MOe script by removing the escape characters in vi.
    vim tl2MOe
    :%s/^M//g
    :wq

    (use CTRL+V CTRL+M to produce ^M as its a special character, don't type it as ^M)

    ReplyDelete
  41. Hi Taron,

    Michael did post a solution for the script. Can you make the changes please.

    Thanks

    Robert

    ReplyDelete
  42. Hi Taron,

    New script works fine. Updated to 5841.98.0 -peppy stable build.

    Thanks again for your help

    Robert

    ReplyDelete
  43. Hello,

    It is possible to upgrade to dev channel ?

    Thanks in advance.

    Guillaume

    ReplyDelete
  44. Hello,

    Have anyone link for 6158.36.0 beta update? If the answer is no, can you give me link for 37 stable update. If you have one of course.

    Thanks.

    ReplyDelete
  45. Mine fails. Here is the output...

    powerd stop/waiting
    Working in /home/chronos/user/tmp.crosrec/
    Downloading config file from https://dl.google.com/dl/edgedl/chromeos/recovery/recovery.conf
    There are 34 recovery images to choose from:

    0 -
    1 - HP Pavilion Chromebook
    ...
    34 - Asus Chromebook C300

    Select a recovery image to download. This will be saved for next time: 22

    Downloading image zipfile from https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_5841.98.0_stout_recovery_stable-channel_mp-v3.bin.zip

    cat: /mnt/stateful_partition/unencrypted/update_url: No such file or directory
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    100 500M 100 500M 0 0 6958k 0 0:01:13 0:01:13 --:--:-- 7425k
    Unpacking the zipfile
    RootFS Start: 286720 RootFS Size: 2641920
    mount: special device /dev/sda12 does not exist
    localhost / # mount: special device /dev/sda12 does not exist

    ReplyDelete
    Replies
    1. Hi, you may need to use the update 2 method

      Delete
  46. I've got a Lenovo SL410 that I've got Chromium running on alright (I would love to figure out how to choose either the trackpoint or trackpad, as opposed to having both on) and I've tried to install the Chrome OS twice, once with the lenovo X131e, and then with the pixel build.
    Neither of them took.
    Any recommendations on which build may work with this hardware?
    (Essentials: Core 2 Duo, 4000HD graphics)

    Any help would be appreciated. If not, I guess I'll just keep going through the list!
    Cheers,
    Brent

    ReplyDelete
  47. This comment has been removed by the author.

    ReplyDelete
  48. Everything's fine. I've been able to upgrade to Chrome with different builds directly to a flash drive just by changing the .sh file where it says /dev/sda/... to /dev/sdb/..., so it upgrades the pendrive info and not tries to work on my hdd.
    After that when I reboot, there is a dialog saying the hardware doesn't match the original and no updates will occur. Is there a hack to do to fix it? I would like to have my Pc working with Windows as well as with Chrome OS and with latest version (and of course with no boring dialogs)? Thanks a lot for everything guys!

    ReplyDelete
  49. This comment has been removed by the author.

    ReplyDelete
  50. I get permission denied after entering the bash command.

    ReplyDelete
  51. Hi, I am trying to upgrade from chronium to chrome os, and keep getting an error after reboot about CPU, and that i need i686. Does anyone know which of the 41 images supports i686?

    I have a Fujitsu M2010 netbook.

    Thanks in advance.

    ReplyDelete
    Replies
    1. Just some further information, I read somewhere that I need to enable visualization in the bios. But the bios on this netbook is very limited, and doesn't have any options for it.

      Also the CPU is an Intel Atom N280 1.66Ghz if that helps.

      Thanks.

      Delete
    2. Looks like this wiki article might help narrow down the images, by CPU type.
      http://en.wikipedia.org/wiki/Chromebook#Chromebook_models

      Delete
    3. Tried CR-48 and during install got
      /dev/fd/63: line 991: 5279 Bus error (core dumped) dd if=image_file of=/dev/sda3 bs=512 skip=rotfs_start count=rootfs_size

      but after a reboot, it booted into chrome OS.

      I got a warning that updates won't work :(

      Anyways, I am glad I worked it out in the end.

      Cheers.

      Delete
  52. Hello,I follow steps to update the Chromium OS to Chrome OS,
    but, I have a problem after reboot my vmware .
    It have a Black Screen after boots,I can only use Ctrl+Alt+F2 ,
    How can I do for this situation ? sorry , my English is not good , thanks .

    ReplyDelete
  53. Hi everybody! Just installed the samsung series 5 chromebook and have no touchpad. Im running a toshiba nb205 with intel atom processor. Any ideas on how to get the touchpad working? External mouse works.
    Thanks!
    Facundo

    ReplyDelete
    Replies
    1. Hi again. It appears that the salix touuchpad used within the nb205 has major issues with unix based operating systems and as such won't be possible to use within Chrome os.

      Delete
  54. config file isn't valid error both with curl and bash 1.sh

    # bash <(curl -s -L http://goo.gl/8v1ZkV)
    Working in /home/chronos/user/tmp.crosrec/
    Downloading config file from https://dl.google.com/dl/edgedl/chromeos/recovery/recovery.conf

    ERROR: The config file isn't valid.

    You may need to run this program as a different user. If that doesn't help, it
    may be a networking problem or a problem with the images provided by Google.
    You might want to check to see if there is a newer version of this tool
    available, or if someone else has already reported a problem.

    ReplyDelete
    Replies
    1. I managed to install it manually using a url from downloading the list file ;)

      Delete
  55. Older versions of Pixel allowed screen touch working (i.e. pre-39) newer ones don't, but Chromium OS 47 allows touch, so I will use the Chromium OS instead of the Google one.

    ReplyDelete
  56. Hello. Are there any 32 bit images available from the list of Chrome OS versions?

    ReplyDelete
  57. Hello. Are there any 32 bit images available from the list of Chrome OS versions?

    ReplyDelete

Let us send you cool stuff!

We promise, we will only send you awesome stuff which will make your day!

About Me

Not much to say other than an IT Technician.
Previously a Windows 8/8.1 Developer and also Skype for Windows 8 Developer.
Also used to work as an Apple repair technician, (the people who actually do the work, not the morons at the front!)