Chromium OS, How To

Dev Server Updates now available!

257 Comments

Fed up with constantly installing new Chromium OS version from USB?

Look no further, I now present to you – “The Dev Update Server”. 

Resplendant with the finest daily compilations, its ready for you to upgrade your installed ChromiumOS to the latest and greatest x86-generic version.

Check the status of the Dev Server on twitter @chromium_bot since the server needs to go offline to build the latest version at around 05:00 GMT daily. Once compiled and presented, the status will say its available.

In order to update go to command line on your deployed Chromium ([ Ctrl ] [ Alt ] [ F2 ]) and log in as chronos with the password of ‘password’ (or whatever your distribution is set to). You can also use SSH.

Then sudo to su

sudo su

Once in the admin shell, update the client with the following:

For amd64  builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:8081/update
For x86  builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update
For amd64 special builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:9080/update
For x86 special builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:9090/update

This will take a while dependant on a couple of things:

  • Whether the image is compiled yet (the dev server creates a sync image on 1st use which can cause timeouts)
  • What other load the server is under.
  • Your bandwidth (some of the updates can be large).

Simply try the update command again if you get an update error or timeout similar to the below:

LAST_CHECKED_TIME=0
PROGRESS=0.000000
CURRENT_OP=UPDATE_STATUS_REPORTING_ERROR_EVENT
NEW_VERSION=0.0.0.0
NEW_SIZE=0
LAST_CHECKED_TIME=0
PROGRESS=0.000000
CURRENT_OP=UPDATE_STATUS_IDLE
NEW_VERSION=0.0.0.0
NEW_SIZE=0
[1228/134834:ERROR:update_engine_client.cc(237)] Update failed.

Once its running you should see notifications from the server saying all is fine and progressing:

LAST_CHECKED_TIME=0
PROGRESS=0.000000
CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE
NEW_VERSION=0.0.0.0
NEW_SIZE=0
LAST_CHECKED_TIME=1356707131
PROGRESS=0.000000
CURRENT_OP=UPDATE_STATUS_UPDATE_AVAILABLE
NEW_VERSION=0.0.0.0
NEW_SIZE=237376171
LAST_CHECKED_TIME=1356707131
PROGRESS=0.000000

Finally, the download will begin:

LAST_CHECKED_TIME=1356707131
PROGRESS=0.000012
CURRENT_OP=UPDATE_STATUS_DOWNLOADING
NEW_VERSION=0.0.0.0
NEW_SIZE=237376171
LAST_CHECKED_TIME=1356707131
PROGRESS=0.000012
CURRENT_OP=UPDATE_STATUS_DOWNLOADING
NEW_VERSION=0.0.0.0
NEW_SIZE=237376171
LAST_CHECKED_TIME=1356707131
PROGRESS=0.002867

If all goes well, the updates will download and the install will progress to finalising:

CURRENT_OP=UPDATE_STATUS_FINALIZING
NEW_VERSION=0.0.0.0
NEW_SIZE=237376171
LAST_CHECKED_TIME=1356708887

This can tale a while (go for a beer whilst waiting) but ‘should’ result in:

CURRENT_OP=UPDATE_STATUS_UPDATED_NEED_REBOOT
NEW_VERSION=0.0.0.0
NEW_SIZE=237376171
[1228/154101:INFO:update_engine_client.cc(241)] Update succeeded -- reboot needed.

You should now also be able to update your stateful partition (where dev tools sit) using:

sudo stateful_update

Which in turn should output:

Downloading stateful payload from http://vps2.arnoldthebat.co.uk:8080/static/stateful.tgz
 HTTP/1.1 200 OK
 Date: Fri, 28 Dec 2012 15:42:43 GMT
 Last-Modified: Fri, 28 Dec 2012 15:07:27 GMT
 Content-Length: 42236449
 Content-Type: application/x-gtar
 Server: CherryPy/3.1.2
 Connection: Keep-Alive
Successfully downloaded update
Performing standard stateful update.

You ‘should’ be able to use the process above to update Hexxxeh and others vanilla builds as well but this is (as ever) completely untested.

Subsequent updates for the OS and stateful partition will now automagically point to the new dev server (you can change using the –omaha-url noted above) so all you need to do is:

update_engine_client --update

and

sudo stateful_update

Finally, in all cases, reboot your client!

Usual Caveats, E&OE stand. The Update Server could work fantastically and make you more attractive to other humans/species from other worlds as well as updating your base build perfectly. It could also create a black hole of NGC 4889 proportions and end the world as we know it as well as bricking your install completely. You have been warned!

Further details and notes available http://goo.gl/OBG2Y

257 thoughts on “Dev Server Updates now available!”

  1. Hi Arnold,firstly i wanted to really thank you for the builds you provide.Secondly i have a samsung np n102s netbook and it works awesome with the chromium os but not able to get the screen set.Its on 767×600 and looks awful.Looks like the display driver is missing.Please help me out

    Reply

    1. Hi

      The display drivers don’t look too stable at the moment and don’t work with many graphics cards. I’m not building anything specific to address this at the moment but if it starts to affect my test netbooks, Ill see what I can sort

      Reply

  2. Thanks a lot for this. Everything is working fine including flash, Youtube, mp3, mp4, pdf and hangout.
    I had used your dec 28 th build img for 64bit. Using Hp Pavilion dv6000. Only the server update need to be set up. Using scan disk 16gb usb for OS. not yet installed on HDD.
    One doubt. when the update takes place each time, do I have to re-install the touchpad, flash etc?
    Please let me know. Then only I will decide to upate from server or wait and do it after some gap.

    Reply

        1. On the vanilla builds, you need to get to shell, sudo su and then issue “stop apmanager”. This will fix it.

          Its disabled on the special builds if you want to try that.

          Reply

    2. Funny, I use a SanDisk Cruzer Facet too, but with 8GBs for the system. I do have SanDisk Ultras(3) though, that have 16 GBs.

      Reply

  3. I’m wondering if anyone has made utilities to re-apply mods after a system update like this. It would be useful to just launch a script after updating. I’m thinking it should function almost like init.d, but more like postUpdate.d
    Thoughts?

    Reply

  4. Arnold,

    after tring update my build with

    update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update

    as root i got this as you mentioned

    CURRENT_OP=UPDATE_STATUS_UPDATED_NEED_REBOOT
    NEW_VERSION=0.0.0.0
    NEW_SIZE=258139971
    [0103/233326:INFO:update_engine_client.cc(252)] Update succeeded — reboot needed.

    but after reboot i still have same build

    Version 28.0.1484.1 (195382)
    Platform 4028.0.2013_04_20_1746 (Developer Build – hexxeh) vanilla x86-generic
    Firmware F.11

    can you help me?

    after reboot i have tried

    localhost bin # sudo stateful_update
    Downloading stateful payload from https:/.hexxeh.net/chromeos/track/vanilla/static/stateful.tgz

    gzip: stdin: unexpected end of file
    tar: Child returned status 1
    tar: Error is not recoverable: exiting now
    Successfully downloaded update
    Missing var or dev_image in stateful payload.
    localhost bin #

    but got an error

    Reply

    1. Hi.

      The stateful update does seem to have been removed in later builds from the dev server so don’t worry too much about that not working!

      Re the same version update; Ive seen that a couple of times but never really got to the bottom of it. Is it still occuring?

      Reply

  5. Hi Arnold, is there a way to manually update each build using USB, the same way as I would with, say Android? I would prefer to update every weekly build as opposed to a daily.

    Reply

  8. Isn’t the latest build still using a slightly old ui? The latest UI for as far as I know puts the apps icon on the right of all the others without a background, but on your build it shows on the far left with a semitransparent black background. Also, in the newer ui, windows are translucent. Is there anything you know about the slightly newer ui and how to get it? Thanks. (sorry for being so fussy xD)

    Reply

  10. Hi,

    trying to do updates on hexxehs 20th April 2013 build, none of your builds work on my x202e, the updates get as far as finalizing, then error every time. any ideas?
    ( bit of a noob to chromium )

    Reply

      1. Hi,

        still does:
        > checking
        > downloading
        > finalizing
        > update_status_reporting_error_event
        > update_status_idle
        > update failed

        any idea where chrome stores logs for this so I can see what is actually happening?

        Reply

        1. I found it in /var/logs

          Use the terminal to get to it then copy the file to the Download folder using cp.

          Reply

  11. ok, so I found the log, and I think this is what is causing it to fail:

    No recognised cros_XXX bios option on kernel command line
    configure failed/

    Reply

  12. The Dev server doesn’t seem to work anymore. I’ve tried several times a day over the last week to configure the initial update_engine_client command but always times-out.

    Reply

  13. I downloaded the build (5498.0.2014_02_19_0209) and it is working fine on a Lenovo S10e. I tried to update as per instructions at the top of the page, but it keeps failing. I am running Chromium OS from a USB stick so I can confirm presumably that the dev server wont work from USB. Am I correct in thinking that if I wanted to update the build, I would have to download a fresh build from http://chromium.arnoldthebat.co.uk/ and then copy it/overwrite my existing image?

    Also, I want to use a USB wireless modem (Huawei E160). Is this possible with Chromium OS? I followed the guidance on the page ‘Mobile dongle support for Chromebooks’ – [https://support.google.com/chromebook/answer/3463300?hl=en&ref_topic=3406281] but I could not get it to work.

    Reply

    1. Hi

      As far as I know/have tested, updates only work once installed to hard drive..

      Re the dongle, its unlikely to be built into the build so would require additional modules, sorry!

      Reply

  14. I’m getting the followingg error message in the log (/var/logs/update_engine_client.log):
    [0311/134626:INFO:libcurl_http_fetcher.cc(87)] Starting/Resuming transfer
    [0311/134626:INFO:libcurl_http_fetcher.cc(98)] Using proxy: no
    [0311/134626:INFO:libcurl_http_fetcher.cc(51)] We are connected via wifi, Updates allowed: Yes
    [0311/134626:INFO:libcurl_http_fetcher.cc(206)] Not setting http(s) curl options because we are in test mode or running a dev/test image
    [0311/134626:INFO:libcurl_http_fetcher.cc(508)] Setting up timeout source: 1 seconds.
    [0311/134654:INFO:update_attempter.cc(1116)] Already updated boot flags. Skipping.
    [0311/134700:ERROR:libcurl_http_fetcher.cc(312)] Unable to get http response code.
    [0311/134700:INFO:libcurl_http_fetcher.cc(329)] No HTTP response, retry 1
    [0311/134710:INFO:libcurl_http_fetcher.cc(87)] Starting/Resuming transfer
    [0311/134710:INFO:libcurl_http_fetcher.cc(98)] Using proxy: no
    [0311/134710:INFO:libcurl_http_fetcher.cc(51)] We are connected via wifi, Updates allowed: Yes
    [0311/134710:INFO:libcurl_http_fetcher.cc(206)] Not setting http(s) curl options because we are in test mode or running a dev/test image
    [0311/134710:INFO:libcurl_http_fetcher.cc(508)] Setting up timeout source: 1 seconds.
    [0311/134741:ERROR:libcurl_http_fetcher.cc(312)] Unable to get http response code.
    [0311/134741:INFO:libcurl_http_fetcher.cc(344)] Transfer resulted in an error (0), 0 bytes downloaded
    [0311/134741:INFO:libcurl_http_fetcher.cc(355)] No further proxies, indicating transfer complete
    [0311/134741:INFO:omaha_request_action.cc(823)] Omaha request response:
    [0311/134741:ERROR:omaha_request_action.cc(838)] Omaha request network transfer failed.
    [0311/134741:INFO:hardware.cc(147)] Booted in dev mode.
    [0311/134741:INFO:action_processor.cc(68)] ActionProcessor::ActionComplete: OmahaRequestAction action failed. Aborting processing.
    [0311/134741:INFO:action_processor.cc(73)] ActionProcessor::ActionComplete: finished last action of type OmahaRequestAction
    [0311/134741:INFO:update_attempter.cc(872)] Processing Done.
    [0311/134741:ERROR:update_attempter.cc(1255)] Update failed.

    That seemed like the most relevant bit. The whole log file is here: Click here

    Reply

  15. hi there

    had dell’s chromium os build on the system and used the update codeing updated nicely.

    however, it did a rewrite not an update so no passwords work for the sudo command so can not activate wifi.

    help needed thanks

    Reply

  16. Hi,
    trying to update first time, always get following:
    localhost user # update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update
    [0412/223451:INFO:update_engine_client.cc(481)] Forcing an update by setting app_version to ForcedUpdate.
    [0412/223451:INFO:update_engine_client.cc(483)] Initiating update check and install.
    [0412/223451:INFO:update_engine_client.cc(507)] Waiting for update to complete.
    LAST_CHECKED_TIME=0
    PROGRESS=0.000000
    CURRENT_OP=UPDATE_STATUS_IDLE
    NEW_VERSION=0.0.0.0
    NEW_SIZE=0
    [0412/223456:ERROR:update_engine_client.cc(356)] Update failed.
    localhost user #

    Pleas help

    Reply

      1. It was local drive. Will wait for the x86_64, thank you.
        By the way – is that ‘weekly’ builds considered more stable than daily?
        Today I’ve manually installed latest weekly from 13.04, and eventually analog sound output of my motheboard doesn’t work any more – volume bar can be moved but there is no sound.
        It was OK on earlier daily builds from beginning of March

        Reply

  17. Hi Arnold,

    thank you for special build. Im using Cx86OS_R34-5196_Multi_2.
    why i cant update with your instruction?
    always getting error msg like this;
    ERROR:update_engine_client.cc(314)] Update failed.

    what should i do? or should i reinstall with different build? if must be, what you recommend for stable build?

    sorry for my bad english

    Reply

  18. No matter what I do I get an update failed message – happening for the last week.

    0506/175007:error:update_engine_client.cc(248)

    Does this after a couple of update checks and then says Status_reporting_error_event.

    Is there an issue w/the dev server or my system?

    Reply

      1. Thank you – successfully updated this morning. I appreciate your work and efforts here. Our schools are moving to Chromebooks so its enabled me to repurpose a netbook and learn more about the OS.

        Reply

  19. I’ve been trying for a couple of weeks now to configure updates as described above, I have gone so far to write a script and left it running for days and still I continue to get:

    ERROR:update_engine_client.cc(xxx)] Update failed

    I’m running 35.0.1866.2(254366) from this site; I’m just trying to understand if the update servers are having problems, are down or if there is a problem with this build.

    Reply

    1. Hi

      Can you stop that script please since I see your IP address causing exceptions on the dev server and killing it.. You are trying to update to amd64 generic which doesnt exist on that server yet..

      Reply

      1. Why would it be trying to update to amd64, I have x86 installed.


        Version 36.0.1982.2 (269091)
        Platform 5868.0.2014_05_19_0508 (Developer Build - buildbot) developer-build x86-generic

        It is apparently almost working now; however, now when I run stateful_update I get a 404 Not Found.


        Downloading stateful payload from http://srv01.arnoldthebat.co.uk:8080/static/stateful.tgz
        HTTP/1.1 404 Not Found
        Date: Tue, 20 May 2014 00:34:30 GMT
        Content-Length: 1202
        Content-Type: text/html;charset=utf-8
        Server: CherryPy/3.2.2

        gzip: stdin: unexpected end of file
        tar: Child returned status 1
        tar: Error is not recoverable: exiting now
        Successfully downloaded update.
        Missing var or dev_image in stateful payload.

        Reply

        1. Ooops, I thought that would have been fixed by now. Shouldn’t make any difference really to you unless you are installing a load of 32 bit only patches?

          Ill look to break out the dev servers into differing flavours if its giving lots of people grief.

          Reply

  20. What may I do when this happens
    LAST_CHECKED_TIME=1400468390
    PROGRESS=0.000000
    CURRENT_OP=UPDATE_STATUS_IDLE
    NEW_VERSION=9999.0.0
    NEW_SIZE=303079630
    [0518/205954:ERROR:update_engine_client.cc(385] Update Failed

    Reply

  21. Hi,

    I managed to update successfully. I was using the 32 bit build but it looks like it updated to 64 bit and then broke as the 64 bit builds don’t seem to work on my machine. Is there any command line switch to ensure the 32 bit build is used or should it do this automatically?

    Thanks,

    Reply

    1. its not this, after checking manually I discovered that many of the latest builds break so the update is updating to a build that doesn’t work.

      keep up the good work however!

      Reply

  22. Hey, I just wanted to say thank you for the work that you’re doing. I’ve been wanting to “experiment” with a chrome book (now that I’ve shoehorned Android onto pretty much everything that I own with a usb port) and I couldn’t justify the money for another device. I’ve used your builds as a jumping off point for installing ChromeOS on my laptop, but have now moved back to using your builds.
    Thanks again!

    BTW I was able to get my realtek 8191se (wifi) to work by adding a copy of rtl8192sewf.bin (from a working linux distro) to /lib/firmware/rtlwifi. I didn’t have wifi until I added that file. I’m using a daily build from May 27, 2014.

    Reply

  23. Is it me or do the automatic updates not work anymore since the most recent builds? Installed fresh and ran the command to add the link to the update but it’s failing everytime. There’s a new X86 build but for some reason it’s not seeing it at all. Guess I’m having to go back to USB installation 🙁

    Reply

    1. this what im getting
      update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update
      [0614/112431:INFO:update_engine_client.cc(647)] Forcing an update by setting app_version to ForcedUpdate.
      [0614/112431:INFO:update_engine_client.cc(649)] Initiating update check and install.
      [0614/112431:INFO:update_engine_client.cc(676)] Waiting for update to complete.
      LAST_CHECKED_TIME=0
      PROGRESS=0.000000
      CURRENT_OP=UPDATE_STATUS_IDLE
      NEW_VERSION=0.0.0.0
      NEW_SIZE=0
      [0614/112437:ERROR:update_engine_client.cc(385)] Update failed.

      and the update_engine_client –install just returns this
      [0614/113137:INFO:update_engine_client.cc(647)] Forcing an update by setting app_version to ForcedUpdate.
      [0614/113137:INFO:update_engine_client.cc(649)] Initiating update check and install.
      [0614/113137:INFO:update_engine_client.cc(676)] Waiting for update to complete.
      LAST_CHECKED_TIME=0
      PROGRESS=0.000000
      CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE
      NEW_VERSION=0.0.0.0
      NEW_SIZE=0
      LAST_CHECKED_TIME=0
      PROGRESS=0.000000
      CURRENT_OP=UPDATE_STATUS_REPORTING_ERROR_EVENT
      NEW_VERSION=0.0.0.0
      NEW_SIZE=0
      LAST_CHECKED_TIME=0
      PROGRESS=0.000000
      CURRENT_OP=UPDATE_STATUS_IDLE
      NEW_VERSION=0.0.0.0
      NEW_SIZE=0
      [0614/113153:ERROR:update_engine_client.cc(385)] Update failed.

      This was working last week

      Reply

  24. After installing from USB to hard disk, I tried to update according your recommendation on your website.

    I get the following error message:

    ERROR: update_engine_client.cc (385) update failed.

    Any ideas ?

    Reply

  25. Updates work using command line but automatic updates via settings appear to not work – reports no new updates available.

    Reply

  26. You are a savior. Was thinking i’d be stuck on a February build b/c all later builds had some weird video flicker during install … anywho the update server is working flawlessly. Only about 20 more netbooks to go ! lol converting all these aging netbooks into chromebooks is saving my company oodles of $ thanks again Arnold.

    🙂

    Cheers!

    Reply

      1. still need some guidance on how to turn off automatic updates. It’s great and works wonderfully, but isn’t very practical if something stops working at a critical moment. Build Im currently on is fairly stable. I’ve google’d quite a bit but to no avail on how to stop auto updates. and i’ve tried a few omaha_url changes but none seem to stick. the next day it’s downloading a new update.

        Reply

  27. Posted this question under another thread, but perhaps it belongs here. What’s the word on the stateful partition update?

    This in no way turns me off of these builds. This is stellar work!

    Reply

  28. I’m struggeling to get it to work. Am I missing something?

    Trying to get the updates working on an USB stick (in the back of a Dell Vostro 270 desktop, with crashed hard drive), but the command keeps returning update failed.

    Reply

    1. Updates dont (or didnt) work from the USB drive. It needs installing to hard drive. Its more than likely a switch in a config file somewhere so you might want to try looking for that

      Reply

  30. I apologize if this has been answered elsewhere. I have the special build installed on a dell mini 9 and have the touchpad and broadcom wireless drivers all working perfectly. If I upgrade from the dev server what is the likelihood that those wont work again? I want to upgrade so I can run netflix. I get an error now saying I need to upgrade chrome. I have no problem going through the steps to enable wireless and touchpad but want to make sure the latest builds will support that. Thanks.

    Reply

    1. Its very likely it wont work! Im trying to get a bit more automated in the special builds and if I can sort that, Ill look to provide a dev server specially for the special builds to things should continue working

      Reply

  31. Still struggling with the stateful partition update. Getting the error below…not sure where that URL is coming from. I’m using your builds.

    localhost / # sudo stateful_update
    Downloading stateful payload from http://sd-64185.dedibox.fr:8080/static/stateful.tgz
    HTTP/1.1 404 Not Found
    Date: Mon, 18 Aug 2014 23:13:30 GMT
    Content-Length: 1202
    Content-Type: text/html;charset=utf-8
    Server: CherryPy/3.2.2

    gzip: stdin: unexpected end of file
    tar: Child returned status 1
    tar: Error is not recoverable: exiting now
    Successfully downloaded update.
    Missing var or dev_image in stateful payload.

    Reply

  32. I was asked by a Friend, to customize his Chrombook to his preferences.
    To get familiar with Chrom-OS, I first looked for a VM-Player- image of Chrome and found Build 4028 from hexxeh.net.
    It run right out of the box on my VM-Player 4.06 (running on CENTOS 6.5) . Because I couldn’t access the Chrome Web Store,
    I looked for updates and found your site.
    The update according your Infos run succesfully the 1st time ending …………….. Update succeeded — reboot needed
    So I rebooted and got the Following for ever:

    “early console in decompress_kernel
    KASLR using RDTSC….
    Decompressing Linux… Parsing ELF… Performing relocations… done
    Booting the Kernel ”

    I tried it a 2nd Time >> same results

    I downloaded one of your daily images, put it on a USB-Stick
    tried to start my VM from that stick (using plpbt.iso bootloder)

    >>same mesage as above.

    I used the Stick, to boot my doughters Thoshiba Satellite

    >> running just fine
    Did you change bootloader or booting options in bootloader on this update ????

    Reply

    1. No changes to bootloader other than that which the Google team develop and release. The later versions have considerable changes compared to the hexxeh builds, purely due to the additional updates from the Google dev team

      Reply

  34. chronos@localhost / $ sudo su
    localhost / # sudo stateful_update
    Downloading stateful payload from http://sd-64185.dedibox.fr:8080/static/stateful.tgz
    HTTP/1.1 404 Not Found
    Date: Sun, 31 Aug 2014 16:09:01 GMT
    Content-Length: 1202
    Content-Type: text/html;charset=utf-8
    Server: CherryPy/3.2.2

    gzip: stdin: unexpected end of file
    tar: Child returned status 1
    tar: Error is not recoverable: exiting now
    Successfully downloaded update.
    Missing var or dev_image in stateful payload.

    Reply

  35. Last comment was in August. I have tried multiple times to update chromeos build using above method:

    update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update

    All I get is: ERROR: update_engine_client.cc(346) Update failed.

    I have tried multiple times spanning over 5 hour time period.

    Also, is there a a tutorial or instructions for adding extra bluetooth drivers? Is it possible to install backports?

    Best regards,

    Reply

    1. Let me have a look at the dev server and see if its misbehaving. Last time I tested, you had to have it installed on your hard drive for it to work. Running from USB failed. One potential workaround would be to install it on a secondary USB stick and boot from that (there must be a setting flag disallowing updates from initial USB – which I need to look for!) which may disable the switch

      Reply

  36. Hi Arnold,
    Firstable, I really want to thanks you for your great job concerning Chromium OS with purpose of maximum hardware compatibility.
    However, I tried the update steps above from my Vanilla Build and everything is flowing; but the last command to update stateful does not work! So, when I reboot my computer, the system (just updated) can not be launched….
    I’m forced to use Vanilla Build version as a start, because I tested a lot of your builds, and none provides me a wifi connection, but on Vanilla Build my wifi card is working fine!
    I’m using Dell Inspiron 17R laptop, and the only chance I have to use Chromium OS with Wifi is to update the browser provided with Vanilla Build..
    So how can I only upgrade my chrome browser from Chromium Vanilla OS ?? (Because, the Browser installed by defaut is not compatible with the WebStore anymore!)
    I hope you will help me!
    Best regards.

    Reply

        1. Im not entirely sure the stateful_update is even working anymore! Ill see if I can have a look this weekend. You dont need the command though to update the system. It works fine without

          Reply

          1. Thank you for your reply. I finally found
            a version whitch is compatible with my wireless device ! The weekly build from
            augustus the 3rd. I added Adobe flash player successfuly. Everything seems to ne ok, except Google+ and Gmail webpage are crashing every time I try… Hangouts extention is not working neither…
            So I updated my Chromium version 38.0.2109.0 to 41.0.2271.2 successfuly when using complete command line ‘Omaha url’ !
            But with this updated version, after the reboot, my wireless device is not working anymore, once again!!!
            So I downgrade to v38 again and let the system running like this, with wifi OK.

            Last question: is it possible to upgrade my Chromium browser only??
            I hope newer version will fix my Google+ and Gmail webpages display issue.
            Thank you very much for your support.
            Best regards.

  37. Thanks a lot.
    I hope my wireless device will be ok with your next special build…

    I don’t understand why it is working fine with release 38.0.2109.0 only. IT mystery, or you have an explaination maybe ??

    It is a shame that Hangouts, Google+ and Gmail pages can not be launched normaly in the release 38 browser !! Bad luck for me. And after a few days testing this release I can tell you that all video player applications I tried are not working neither. Applications are crashing as Hangouts does !

    I think I can not use this release any longer…

    Reply

    1. Thats the problem with cutting edge code sadly. It can be unstable!! Its a case of finding a build from the weekly or dailys which suits your needs and sticking with that for a while. Once Im happy with the spcial builds, Ill create a dev server but releases will be tested a bit more on that!!

      Reply

  38. After more investigation, I can tell you that the build 38.0.2109.0 I’m using, is not responsible for the issues generated with Google+ Gmail pages and Hangouts app.
    No! This issue is occuring because I installed Adobe Flash Player path to read also mp3 and mp4 files with following command:
    curl -L http://goo.gl/MuVta5 | bash
    It seems there is a conflict when installing this package.

    But it is a shame that without this package, I can not read some pages requiring Adobe Flash as radio stream websites, and even my Google Play music !! I have many mp3 and mp4 on my second HDD running, and without this package I can not read it neither. Idem for all video files with extention AVI, MPG, MKV… or others.

    Conclusion: I will update my Chromium OS to Chrome OS with wifi-free [ 🙁 ] and enjoy Google environment at least !
    I will take a look on next special builds you will release and test it, and I hope it will be once with better compatibility for me!

    Thank you for your interest to my issues and your help.
    Best regards.

    Reply

  39. Hi Arnold, Thanks for giving a second live to our Acer netbook. Chromium runs well. Only thing is that netflix is not working. It seems that it got to do something with Silverlight?! Any change we get a solution for that in the near future?

    Thanks!
    Perry

    Reply

    1. I believe that the Netflix plugin is a proprietary version specific to Chrome OS and can’t be legally added to Chromium OS builds

      Reply

  40. I use your system in my card and it goes well. Could you build a small one which can be put into a 2G sdcard ?

    Reply

    2. Maybe, you could use another CD/DVD/USB/SD Card with 4 GB or higher. If you don’t have any removable storage device with enough storage, you could buy one. You can find them for pretty cheap(5 dollars or less for an individual 4GB device, or more money for higher storage if you want better performance).

      Reply

  42. The command doesn’t work for me(update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update
    ). I’ve tried it numerous times. I always get an error message:[0317/195359:ERROR:update_engine_client.cc(347)] Update failed. Do you know what exactly is wrong based on this last line I get. If so, can you/I fix it somehow?

    Reply

  43. Hi Arnold,
    It’s Rakesh again. I have managed to install the 21 Feb 2015 build in my lenovo hardrive. Booting from my hard drive. But the lemon part is that i still have no wifi and cannot do anything as the continue button is greyed out. I know this is a problem. But i was so irritated, i said to myself, Damn, this is hard. So i went ahead and put the os on my hard drive. Now what shall I do? Is there a developer code that I can put in the developer screen to somehow enable my wifi…. Cos without wifi I’m screwed. If anyone can help me, I’ll be highly obliged. Again my wifi card is broadcom… Please please help!

    Reply

  44. Hi,

    I make it.
    I installed first a Hexxeh Version and update it with your Version. But the command update stateful_update din’t work for me.
    But it is ok.

    Do you know how to get the flashplayer working?

    Thanks

    Reply

  45. Hi!

    Maybe you could edit the post to reflect the port number change, as this is what the main about/how-to points to for updating instructions.

    Thanks for your work with this, much appreciated!

    Reply

  46. Hi Arnold,

    I’m having the same issue reported here over a year ago: “…:error:update_engine_client.cc(248)”

    I was wondering if it has to do with a server issue.

    Thanks in advance!

    Reply

  47. Hi Arnold,

    Since abouta year I am following your development and I really like what you do so THANKS!

    I got Chromium running on an old EEEPC but now I am stuck and want to ask you if you could help me.

    I am trying to update an older version of Chromium in VM with the Dev servers. (Not Hexxeh’s build)

    I issued the command:
    update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update

    But now I get the error: (I can’t copy or find logs so I will retype it here)
    [0402/133126:INFO:update_engine_client.cc(282)] Forcing an update by setting app_version to ForcedUpdate.
    [0402/133126:INFO:update_engine_client.cc(284)] Initiating update check and install.
    [0402/133126:INFO:update_engine_client.cc(290)] Waiting for update to complete.
    LAST_CHECKED_TIME=0
    PROGRESS=0.000000
    CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE
    NEW_VERSION=0.0.0.0
    NEW_SIZE=0
    LAST_CHECKED_TIME=0
    PROGRESS=0.000000
    CURRENT_OP=UPDATE_STATUS_REPORTING_ERROR_EVENT
    NEW_VERSION=0.0.0.0
    NEW_SIZE=0
    LAST_CHECKED_TIME=0
    PROGRESS=0.000000
    CURRENT_OP=UPDATE_STATUS_IDLE
    NEW_VERSION=0.0.0.0
    NEW_SIZE=0
    [0402/133142:ERROR:update_engine_client.cc(224)] Update failed.

    I have searched with google but can’t find the ERROR code 224.

    The virtual machine is working with a GUI and Ethernet on VMware Workstation 11, Hardware compatibility Workstation 9.0.
    I can login and everything but I can’t get the update to work for the store.

    I hope you can help with the error code and maybe have a solution on how to still get the update.

    Thanks in advance!

    Reply

    1. Did you install this image to a Workstaion Hard drive or simply convert the img file? The latter will not update since the OS is hardcoded to prevent what it thinks is a USB based build.

      Reply

  48. Hello, Arnold. I’m on a x86 special build, and whenever I run the update command I get:
    Password:

    localhost / # update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:9090/update
    [0422/153334:INFO:update_engine_client.cc(433)] Forcing an update by setting app_version to ForcedUpdate.
    [0422/153334:INFO:update_engine_client.cc(435)] Initiating update check and install.
    [0422/153334:INFO:update_engine_client.cc(464)] Waiting for update to complete.
    [0422/153334:ERROR:update_engine_client.cc(207)] Update failed, current operations is UPDATE_STATUS_IDLE

    It does this no matter if I use VT-2 or crosh. Any ideas? My internet connection is working fine. Is it because there are no updates available or is the server down?

    From,
    Geoffrey

    Reply

      1. Thanks for the prompt reply. I’m on version 50.0.2637.0. Downloaded it a while ago. Currently it’s my only OS… Hard drive failed. Running on USB. 😀

        Reply

  49. Keep getting this: Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kOmahaErrorInHTTPResponse(37)

    Reply

  50. In order to get Dev Updates do I need to join the Dev channel under
    Settings > About Chromium OS?

    I don’t mind doing it but would fix/break getting dev updates?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.