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
Hey Arnold,
I can’t get updates working on R57-special, whenever I run:
update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:9080/update
I’m getting this:
Forcing an update by setting app_version to ForcedUpdate.
Initiating update check and install.
Waiting for update to complete.
Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kSuccess(0)
Meanwhile, on router I can see there is no single packet destined at dev server. What am I doing wrong?
Thanks in advance!
Thats because that’s the latest version currently available.
I’ve tried the update but i recevie that error:
[0121/132532:INFO:update_engine_client.cc(486)] Forcing an update by setting app_version to ForcedUpdate.
[0121/132532:INFO:update_engine_client.cc(488)] Initiating update check and install.
[0121/132532:INFO:update_engine_client.cc(517)] Waiting for update to complete.
[0121/132545:ERROR:update_engine_client.cc(232)] Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kOmahaErrorInHTTPResponse(37)
Yup, its currently down waiting a deployment of R64
Hello Arnold,
Is the update server for amd64 special builds (http://chromebld.arnoldthebat.co.uk:9080/) gone forever? It seems to have been down for at least a week now.
Not at all. I’ve just been really busy so havent had time to configure it!
hi,
whatever link i try i get Always: ErrorCode:kOmahaErrorInHTTPResponse(37)
The update servers are down currently whilst I prepare a new release.
Thanks for the effort on this project!
Any updates on the update servers?
Just prepping version R64 for release, so as soon as Ive finished testing, plus a bit of feedback from the masses, Ill unleash the update servers to the world.
Yeah!
Thanks again for the hard work.
hay on the special builds are you still updating that because my laptop works on only those builds but the last time it was updated was on Aug 28th 2017… have you stopped support or just have been busy?
Still updating!
I’m running a few HP ProBook 4525e units with the Chromium build you provided in another post. I’m trying to get the WiFi working (suddenly all of the units just say the WiFi is turned off and only work on Ethernet). I was hoping updating would help, but I can’t seem to get things to update.
Appreciate any help in advance!
Likely the lack of support for the Broadcom cards causing the problem. If you have a spare unit, I can try to build in support?
why im getting this error arnold?
Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kSuccess(0
No idea. What version are you currently on?
how to check version in chromebook?
ontop it shows chromium 66.0.3359.203
i manage to wipe password for dell chromebook but now im stuck with amazon customer service window,how can i install new os ?current its shows on top chromium 66.0.3359.203
need help, whenever i try to “sudo stateful_update”, it give me these result
gzip: stdin: not in gzip format
Hi Arnold, is the x86 server dead? Thanks for your awesome work with everything else 🙂
Yes, x86 is dead since its just too much overhead to support. Sorry!
Hello Arnold!I have a problem. I can not pass the “Checking for Update” screen. Is there a way to “bypass” this screen / step? Nb: I install the latest version of amd64 build. Thanks
Just press escape on the keyboard
Hi ,
I get this error:
localhost ~ # update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8081/update
[0502/010811.420469:INFO:update_engine_client.cc(479)] Forcing an update by setting app_version to ForcedUpdate.
[0502/010811.420666:INFO:update_engine_client.cc(481)] Initiating update check.
[0502/010811.426242:INFO:update_engine_client.cc(510)] Waiting for update to complete.
[0502/010827.768537:ERROR:update_engine_client.cc(211)] Update failed, current operation is UPDATE_STATUS_IDLE, last error code is ErrorCode::kOmahaErrorInHTTPResponse(37)
localhost ~ #
Any idea ?
Thanks, see you.
Update servers aren’t currently running. As soon as I get R83 working, Ill sort it.
Hi Arnold!
First of all, thank you very much for providing us with the builds and this dev server 🙂
Do you know if you’ll be able to get the dev server running in the future? I’m getting the same error as Xavier by trying to update an amd64 build (ErrorCode::kOmahaErrorInHTTPResponse(37)).
Thanks!
The dev server will be back online this weekend I hope. Just got to finish of testing.
Hi – thank you for your hard work and the wonderful project!
Do the update servers currently running? I get the HTTP Response 37…
Franz
The update servers will be back online soon. I have had to rebuild them hence the delay….
After going down to R72 to get my wireless adapter to work I can not upgrade. I get the same error message a lot of other have stated. UPDATE_STATUS_IDLE. Is there something I’m doing wrong? Will it not update from R72 to latest?
Thanks for everything you do on this project.
It ‘should’ but the update server is currently getting prepped for the new build so offline at the moment,
Hey Arnold great work with your chromium os builds .
But on my fresh install of Camd64 Nov 12 2020 special build
the command stateful_update is not found
i dont know wether i am doing something wrong or … what..
I’m getting the idle error message for updates yet again. Is the server down for a new release once more?
Also, I’ve got an old, no longer supported, Haswell-era Chromebox that I’ve installed the Coreboot UEFI on and have booted your ChromiumOS build on. I see some oddities with the IntelHD graphics card (not letting me change resolutions, etc.) I suppose there’s a driver issue there?