Dev Server now available for special builds

Dev servers are now available to update ChromiumOS special builds. Starting at version R45-7216, both x86 and amd64 versions are available.

Please test and feedback!

To update, get to command prompt (Ctrl-Alt-T), then enter shell as normal. Then issue the following commands:

For amd64 builds

update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:9080/update

For x86 builds

update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:9090/update

As ever, this update will overwrite any customisations you may have done (such as flash and API_KEYs). Please backup beforehand!

Happy updating!

Share on Google+Tweet about this on TwitterShare on FacebookShare on LinkedInShare on TumblrShare on Reddit

35 thoughts on “Dev Server now available for special builds”

  1. Hi Arnold,

    Just want to say that I am really impressed by your work. I’m now using your build of Chromium OS as my main OS on my desktop and it’s running better than I could have ever expected!

    Question: do you know if there are plans in the Chromium OS community to switch to linux kernel 3.19? I want to try out Chromium OS on my Surface Pro 3 and heard that 3.19 included drivers for the type cover ;).

  2. Hey Arnold, thanks for the build! Works flawlessly on my 2014 MacBook Pro (even Broadcom wireless works!) but I’ve got a few questions:

    1. Have you planned adding AppleSMC module? (Should be in mainstream Linux) The fan is hardly spinning, and there’s no way of adjusting it.

    2. I tried dd’ing the A-ROOT and STATE partition onto /dev/sda4 and 5 (1,2,3 occupied by EFI and OSX), but Chromium OS is looking for a /dev/sda1 STATE partition. Any way to provide an alternative STATE partition?

    Thanks!

      1. Thanks for your reply!

        For anyone else that’s wondering, it looks like the partition layout is modifiable, but hard coded (can only be changed while building) 🙁 so probably no multi-booting.

        1. Actually, this one should be relatively easy to fix – just pull up your favorite Linux distro, mount the ROOT-A partition that you dd’d to the HDD, open the chromeos_startup file under /sbin in that partition, find the $STATE_DEV = { line, and then replace the 1 after the } with the partition number for your custom STATE partition. I’ve encountered this problem numerous times, and this has worked to solve it every time.

          I adapted that from this partially outdated, but very helpful guide. Note that the article mentions a $ROOT_DEV variable within the {} brackets, but the variable changed in recent ChromiumOS versions; I have yet to verify this.

          1. Note #1: this comes in very handy when dual-booting. Other than my BIOS not wanting to boot ChromiumOS from UEFI when I dd the partitions manually, it works perfectly. 😀

  3. Hi
    It s really great work from you, very much Appreciated. I have used the special builds using USB and enabled chrome OS single app kiosk kept in Permanent mode. When I insert USB in a machine it supposed get into the kiosk application after booting up. But only on one machine (where I have done the kiosk process) the application is starting up whereas on all the other machines Chrome OS is booting up. Is there any way to fix this problem?
    Thanks a lot
    Vas

  4. Hey arnold, I tried your latest special build and the elantech touchpad work! but it have a small issue like no tap-to-click and mouse or touchpad not recognized in settings. So I try to check to /etc/X11/xorg.conf.d/ conf files and tada! there’s only 20-touchscreen.conf file… usually there are 2 more file:

    https://chromium.googlesource.com/chromiumos/platform/xorg-conf/+/master/20-mouse.conf

    https://chromium.googlesource.com/chromiumos/platform/xorg-conf/+/master/40-touchpad-cmt.conf

    Thank’s for your kindness to contribute to this great project! 🙂

    1. Thanks for the above links. They are what I need to build in to support the CMT driver stack. I should be able to make a start on that for the next special build..

  5. Hi
    I am trying to fix the broadcom wifi on a dell d620 but your instructions are for 3.4.0. do you have any for 3.19.0?
    Thanks
    Ken

  6. I am using an ageing Dell Vostro with an Intel Core i3-2350M CPU @ 2.30GHz . I am unable to run the Android Runtime apps, and also unable to get audio output through the audio jack. The inbuilt speakers work fine though.

  7. There was a script out there somewhere that added your api keys for you along with flash and pdf etc. I can’t find it now. does anyone out there know where this is?
    Thank you,
    Gary

  8. Your welcome, btw I got this thing when I try to update it from command line:

    update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:9080/update
    [0723/142604:INFO:update_engine_client.cc(555)] Forcing an update by setting app_version to ForcedUpdate.
    [0723/142604:INFO:update_engine_client.cc(557)] Initiating update check and install.
    [0723/142604:INFO:update_engine_client.cc(579)] Waiting for update to complete.
    [0723/142617:ERROR:update_engine_client.cc(325)] Update failed, current operations is UPDATE_STATUS_IDLE

    Thanks for your response 🙂

      1. I made a USB-stick, booted it, installed my API-keys, flash etc. All working great.
        Then I installed from this stick (4GB) to another one (32GB) from a shell as root, using :


        chromeos-install --skip_src_removable --skip_dst_removable --dst /dev/sdc

        /dev/sdc being my second USB-stick, /dev/sda the first USB and /dev/sdb being my internal HD.
        Can I use your update method for this new USB-stick, without risking my internal HD being erased ?

        PS: flash etc is still working on this new install

  9. Thanks Arnold for this project support. I work at a college which is in the process of migrating to chromebooks as the predominant platform. For all of those old HP 4330, 4340 and 5320m laptops in our fleet, the special dev version is perfect for recycling otherwise aged but good hardware with the bonus of training staff in new features via USB or making the jump to full Chrome OS. Thanks again for your support, its brought new life to our fleet and made my month 🙂

  10. The special build works well on my old laptop (chromebook)! There is only an issue with the screen flashing and resetting when going into settings and back again to the chromium browser window. It continues to run fine afterward.
    Thanks!

  11. Will this (and other updates in the future) overwrite the mod (changing the state partition number) I made to the {ROOT-A partition}/sbin/chromeos_startup file? That mod enables me to quad-boot ChromiumOS with Windows 7, 8.1, and 10. Also, will updating via the dev server wipe all my hard drive data, or just the ChromiumOS partitions?

  12. Hi Arnold! When I try to install chrome os special builds on Lenovo Z50 laptop, wifi drivers are not working. So unable to install chrome OS. Can you please help me on that issue. Thanks a lot.

  13. Hey there,

    sorry for using the comments to ask about another issue, but, do you know any updated guide to make Windows 8/10 and Chromium OS dual boot?

    Thanks in advance.

Leave a Reply

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