ROM Download

Please note: I no longer maintain, provide, or support custom Chromebook firmware; this page is left here for archive purposes only.

This page contains a command to download and run a script, which will flash custom firmware with a SeaBIOS payload on approaching 40 models of Intel based Chromebook – allowing you to run an alternative OS such as Linux. The script will work with ChromeOS or pretty much any Linux distro (at least no one has told me otherwise).

There are 3 types of firmware mod – RW_LEGACY, BOOT_STUB, and Full ROM – not all Chromebooks work with each one:

  • RW_LEGACY modifies a 2MB section of the ROM leaving the stock functionality intact, including the scary developer screen, and will not brick your device. Some Chromebooks already come with a working RW_LEGACY slot, although many of them do not (non-functional keyboard on Panther, non-functional display on Auron_Yuna, or just plain missing, etc.). As well as fixing aforementioned bugs, updating the RW_LEGACY slot can enable further functionality such as booting from SD card/eMMC. So, even in the case of a functioning stock RW_LEGACY, it may be fortuitous to update.

  • BOOT_STUB modifies the last 1MB of the ROM, removing the scary developer screen, but also removes the ability to run ChromeOS natively, carrying a chance of bricking your device. This also leaves the “REFRESH + POWER” functionality of the stock ROM intact, meaning, when you press these keys, the device will immediately reboot and attempt to run ChromeOS Recovery (which isn’t there any more), and give you a blank screen. The only way to then stop it from attempting to run ChromeOS Recovery on every boot, is to take the device apart and disconnect the battery.

  • Full ROM, as the name suggests, is a complete ROM containing a coreboot build with a slice of SeaBIOS on top, and is the most risky. Again, this will remove the ability to run ChromeOS natively. Flashing one of these will wipe out your product data. In the case of Sandy/Ivybridge Chromebooks a full ROM enables hardware virtualisation extensions and suspend. Other models full ROM’s also probably contain idiosyncrasies that the stock firmware does not.

You need to be in dev mode and to have disabled write-protect by enabling a jumper/removing a screw (usually the latter, located somewhere on the main board). Disabling write-protect is not necessary when flashing RW_LEGACY unless you want to make the legacy slot default. See each respective supported Chromebook’s developer information page (if available) for info on opening your Chromebook up and disabling write-protect.

[TABLE=3]

Jenkins is now being used along with some scripts, to automate building, and to reduce chances of a brick from human error. Run the script like so, making sure you are only in Crosh shell *not* the *root* Crosh shell if running from ChromeOS:

cd;bash <(curl https://johnlewis.ie/flash_cb_fw.sh)

If for some reason you need to run an older build, you will have to flash it manually. See the ROM Archive.

Please note: I no longer maintain, provide, or support custom Chromebook firmware; this page is left here for archive purposes only.

Join the conversation

1295 Comments

  1. Not relly worried about it so to speak but it wont let me run your script.. says rom is read only general error=1.. ive got a jumper on the 2 posts so iknow its closed.. but still showing srp0 and srp1…

  2. Hi John, after reading through all your FAQ’s and other info, I noticed that you mentioned dual booting ChromeOS and another operating system with your firmware would be tricky. What if I installed the firmware, then installed Chromium OS, and then Ubuntu on top of that. Any way that would work? Wouldn’t the Ubuntu installation process install GRUB bootloader and allow me to partition the drive correctly? I love the simplicity and speed of Chrome/Chromium OS, but since my only computers are a Acer C720 Chromebook and an Asus Chromebox, I’d like to run Ubuntu as a secondary system on at least one of them for occasional use when Chrome OS doesn’t cut it. Thanks again for all your hard work!

    1. If you want to dual boot, you’re going to have a much easier time using ChrUbuntu with your particular device. It’s theoretically possible, but I’m not aware of anyone having done it yet with SeaBIOS. You’re going to have to become a pioneer if you want to go down that road.

  3. Thanks John, I had previously tried a ChrUbuntu install and it failed, but finally got it to work last night.

  4. This is not necessarily a question for John, but has anyone tried his latest script on an Acer c720-3404? Its a new acquisition and I haven’t fooled with the write-protect yet, but I plan to in the next couple of days. Any troubles noticed yet?

    1. Somebody tried to run it on 32-bit and the statically linked flashrom binary is 64-bit. Nothing else reported so far. Perhaps you should ask on the community too.

  5. They are both 1. (current status and at boot) even with jumper.. but some other odd things.. under firmware used at boot it says unknown… previous unknown..

    1. The hardware write-protect isn’t disabled then. That’s the problem. Check your foil, or alternatively use a cut down HD jumper, or even a carefully wedged watch screwdriver (but that’s awkward).

  6. A few days ago I posted that I had a problem getting my Dell Chromebook to recognize the 4GB of RAM, as it was only showing 2GB. I finally found a work around by editing the grub bootloader and deleting GRUB_CMDLINE_LINUX = “mem=1024m” entirely. Now it reads:

    GRUB_DEFAULT=0
    GRUB_HIDDEN_TIMEOUT=0
    GRUB_HIDDEN_TIMEOUT_QUIET=true
    GRUB_TIMEOUT=5
    GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
    GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

    I hope this helps someone. It worked for me. Running a Dell Chromebook 11 – Corebook with Ubuntu 14.04 Note there is nothing under GRUB_CMDLINE_LINUX_DEFAULT=quiet splash”

    1. Strange. Perhaps Grub was reading the cmd line that the ISO was booted with, and put that in. mem=1024 certainly wouldn’t get in there by default. BTW, you should put the line back in minus the “mem=1024” as that *is* there by default.

  7. Well Mr. John Lewis I greatly appreciate all your hard work on Seabios and your recent help on my issue however after a complete teardown I found 2 “resisters” completely broken off the board under the cpu heatsink so Im assuming its a hardware issue. Im actually suprised the machine boots and is completely usable(as usable as ChomeOs will allow). Thanks again!

  8. Hi, I’m trying to update under Ubuntu 14.10 32bit – Gnome desktop, (C720 2848)

    I released protection screw long time ago so it is not hard protected but disabling soft protection gives me a error like,,

    “” cannot execute binary file: Exec format error “”

    Did anyone experience this symptom?

    Should I boot from other Linux distro?…

  9. Hi, I’m using C720-2848 with Ubuntu 14.10 32bit Gnome.

    I get this flashrom write protection error,

    “cannot execute binary file: Exec format error”

    But I removed hard protection screw long time ago at the first installation of this flashrom. So I cannot guess what went wrong…

    modifiying tpm_tis.force or others related with this error?

  10. Just trying to make sure of something here. Have I read correctly that I have to remove the write protect screw on my Acer C720 for the ROM flash to work?

  11. Ok thanks. Sorry to bother you with one more question. Have you heard of anybody bricking their devices or running into significant other issues on an Acer C720? I realize that I’m 100% responsible for my own machine, and that there are risks involved, but just wondered if the success rate is pretty good with that model? Just don’t want to ruin my brand new machine.

  12. Sorry for bothering you with one more question. Just want to make sure I’m doing it right. I’ve already got my C720 in dev mode, so now I need to remove the write protect screw. After I do that, I just boot up to Chrome OS, open a crosh terminal shell and run your script from the ROM download page? That’s it? Do I log into the crosh shell as chronos? Does the script completely wipe my device? I think I’ve read your info and FAQ’s through but didn’t see specific instructions all laid out. Please forgive my ignorance and if there’s instructions clearly laid out someplace and I missed it, please point me in the right direction. Thanks so much for your time and efforts! I’ll be making a donation to support your endeavors if and when I get this to work.

    1. The reason the instructions aren’t displayed in 1. 2. 3. format is because it is a) more complicated than that, and b) going to encourage people who don’t know what they’re doing to screw their machines up. The script does not wipe your device, but since you won’t be able to use your device with one of my ROM’s without at least booting from another OS, having an intact ChromeOS is of little use.

  13. Thanks for bearing with me here. When you say it’s more complicated than that, am I missing something? Is there more to it than the steps I asked you about previously?

    1. What I mean is, there are other things to be taken into consideration, which is why you should read the ROM Download, FAQ, and probably look at the community before your flash. If a relative computer illiterate comes here, sees the 5 simple steps (or whatever it is) and follows them without taking account of the surrounding information, they may well end up disappointed.

  14. By the way, I am thinking in updating the bios on my c720. It is running one of yours from a few months ago. I have read lots of comments and the FAQ… but could not find instructions to upgrade. Is there anything special to do or just re-run the same script that I ran when it was still a normal chromebook?
    Thanks!

  15. Hello! After installing seabios on my acer Chromebook cb3-111 the internal ssd is not detected as a boot device but, it can be seen by the ubuntu Linux installer, any tips?

  16. Hi John,
    I flashed one on your roms on a Toshiba Chromebook 2 AKA Swanky. I would like to go back to the stock firmware.
    I ran your script with option 2 – Modify my Chromebook’s ROM back to the stock payload. When the script executes it stops and gives the following error when it tries to Download shellballs/swanky/bios.cbfs:
    *** shellballs/swanky/bios.cbfs could not be downloaded. Please try again later. ***
    The directory https://johnlewis.ie/Chromebook-ROMs/shellballs/swanky/ only has a file called ‘bios.cbfs.new’ but no file called ‘bios.cbfs’.
    Any help would be appreciated on how to go back to the stock firmware. Thanks.

  17. Thanks for the stock CBFS; Option 2 works to return to stock.
    If you have installed linux on an Acer C910; does sound, wifi, trackpad work OOTB if so which kernel/distribution did you use? If I flash your rom on an Acer C910 (Yuna) can I return it back to stock with your script (option 2?).

    1. Yes, it works OOTB in Fedora 22. Fedora 21 needs a kernel update. AFAIAA, option 2 will work with Yuna (particularly as that is one of the models I tested the script with).

  18. Thanks for your roms. In the description you write ‘Note that flashing one of these ROM’s will remove the ability to run ChromeOS in all but 3 cases.’ Are the 3 cases the RW_LEGACY ones; Pixel 2, Acer 740/910? On those models can you press Crtl-D at the scary screen to boot into ChromeOS?

    1. Yes, assuming you haven’t wiped it off in the process of putting another distro on. But obviously, when you write Grub to the mbr, you won’t be able to boot ChromeOS.

  19. John,

    You said: “But obviously, when you write Grub to the mbr, you won’t be able to boot ChromeOS.”

    I have not replaced the ROM in my HP Chromebook 14 (Falco) but I have installed one of Hugh Greenberg’s distros using the dual-boot scenario via partition 7, like ChrUbuntu; this method writes grub to /sda not /sda7. ( see https://www.distroshare.com/distros/get/14/#comment-1803627619 )
    I can still boot Chrome OS via Ctrl-d but I can also boot the linux distro via Ctrl-L – no problem. Is this contrary to your statement above? I’m just wondering if your ROMs do something differently…

    Thanx for all your efforts,
    -DennisL

    1. Yes, my ROM’s use SeaBIOS, which has a different boot mechanism to the stock ROM’s. Therefore you won’t be able to run ChromeOS, unless you install one of Arnold the Bat’s builds, and somehow fudge the bootloader to boot both.

  20. Hi,

    I got a new Lenovo Yoga 11e chromebook, and I’d like to know firts, if it is possible to install any Linux dist to it. I tried everything with chrubuntu but there is no way to boot another thing than chromeos. Pleas elet me know step by step if it is anyway to do it. This device has a eMMC HD.

    Tks!

  22. Hi. I had been running one of your old C720 ROMs for I guess almost two years now, and have decided to update today, and got this:

    flashrom v0.9.4 : bc6cab1 : Oct 30 2014 07:32:01 UTC on Linux 4.0.6-300.fc22.x86_64 (x86_64), built with libpci 3.1.10, GCC 4.8.x-google 20140307 (prerelease), little endian
    sh: crossystem: command not found
    ROM image contains too many regions
    FAILED

    *** BOOT_STUB could not be written. This is usually because a custom firmware without flashmap has previously been written to the device. You may need to flash a shellball ROM and restore your product/GBB data. ***

    Can I reboot safely now? Don’t want to turn it off and have a brick :) I’m running Fedora 22 64-bit… Thanks!

    1. You can reboot safely, because nothing has been changed. If you want to use option one, you will have to flash back to stock/shellball beforehand (preferably stock so you have your serial number and hardware ID).

  23. There are two caveats you should really highlight for Bay Trail users as I am a little ticked off that after all the reading I did, and I do research the crap out of things, that these 2 things were not abundantly clear.

    1.) Beyond the simple reason of legacy boot SeaBIOS even after modified will not boot to the native eMMC storage and you have to setup a bootloader (aka GRUB) on USB to boot to eMMC (the internal storage).

    Had that been clear from the very beginning I would have nope’d right out of this little endeavor.

    2.) There is currently no support for sound. This is not your fault, but you should have more clearly highlighted this. Part of the benefit of you having done this is that you and others can forewarn us of these things. This is a lesser issue that I might have overlooked (although it makes alternatives like crouton, which may not be ideal – but has everything working more or less, look more favorable).

    This is just my opinion of someone who is more concerned with getting work done at the moment than tinkering.

    1. What, you mean this information, that I put in https://johnlewis.ie/baytrail-release/ the first day I released the firmware, which of course you found because you “research the crap out of things”? I’ve also written those two caveats in the sticky post on the community. I will concede that I should probably also put it in the ROM Download page though …

    3. And finally, of course, if you didn’t fancy “tinkering”, perhaps you shouldn’t have been fucking about, flashing your Chromebook in the first place …

  24. Nevermind my previous comment. Went with option 4 and all good. Guess my product data was long gone anyway… Thanks!

  25. Hi John I am running a derivative of Slackware 14.1 with kernel 4.0.4 on an Acer 910 (Yuna). Cannot seem to get the touchpad to work. Unable to upgrade the kernel. modprobe chromeos_laptop gives: ‘ERROR: could not insert ‘chromeos_laptop’: No such device’. With same install everything works on Acer 720. Were you able to get the touchpad to work with a kernel < 4.1; do you have any suggestions (besides kernel upgrade). Thanks.

  26. Dear John:

    You’re the man. I’m running your Parrot ROM from Sept. 4, 2014, on my C7. It’s apparently flawless, which is to say, everything works (on Ubuntu 15.04). Are there any benefits to flashing your shellball-stock hybrid? I suppose what I’m asking is whether “quality and consistency improvement[s]” are merely stylistic or actual.

    Your answer won’t determine whether I’ll install it — because I will — but will merely stave off my placebo effect of improvement or validate my perception of an actual improvement, as the case may be.

    Thanks again. Keep up the good work.

    1. If you run the stock/BOOT_STUB hybrid, suspend will probably be broken on the C710, but, the overall quality and consistency will be better. So, if you are finding little idiosyncrasies with the custom ROM (which you haven’t yet, by all acconts), and you aren’t too bothered about suspend, then the stock/BOOT_STUB hybrid will be an improvement. In your case, I think you should probably stick with what you have if it’s working for you.

  27. I have the Dell 11 Chromebook, CANDY model.. Is there any way to get ChrUbuntu on it? It’s not supported here it seems.

    1. Maybe you need to reread the page. Under “Currently supported models – BOOT_STUB only” it reads:

      Dell Chromebook 11 (2015) AKA Candy

      So, it is supported.

  28. Hi John

    I would like to know how to restore my original bios configs? I have installed linux using your custom seabios, but now I want to restore the bios and the chromebook back to factory so I could sell it. Any help would be appreciated. I did make a back up of the original bios files.

  29. So I used the script on my c710 Chromebook (got tired of my wife killing my Crouton chroot by accident on reboot). Everything worked great, except that now when I close the lid, the computer reboots after opening it. Does this seem consistent with a BIOS issue?

    Is my best way forward to get a custom build of coreboot and flash it manually? Where would I get started for the process for this?

    1. This is expected when only updating the BOOT_STUB on pre-Haswell Chromebooks. You can run the script again and choose option 4 to flash a full ROM where suspend/resume should work. Alternatively, you can configure your system to hibernate (which doesn’t rely on the BIOS).

      There are various how-to’s (both here and other places) on how to build your own coreboot, but it’s not recommended unless you are fairly technically proficient and determined (you will almost certainly brick your device unless you’re lucky).

  31. I successfully installed seabios on an x131e and am now running debian jessie. All is well except that the function key (marked as a square turned 45 degrees, I think chromeos called it the star key) does not work, it is recognized by neither xev nor showkeys. Is it some strange thing used only by chros or is it a regular fn key which may be either debian or seabios’s fault?

  32. Hi, I flashed your C720 ROM and looks to works like a charm (except backup product info failed). Where can I find the “source code” of your build ? Thanks a lot.

  33. Well, it said *** Something went wrong. Perhaps you’re running a custom ROM without product data in? ***
    But it was the original ROM, just GBB flags was changed. Maybe it was the problem? (GBB flags). Or maybe because I had no $HOME/Downloads/ directory?

    I used option #4 to flash full custom ROM.

    With the full custom ROM, I noticed that “4 second press power button” doesn’t power off. I think it can be an issue if the laptop freeze.

    Kind regards

    1. I guess it could’ve been because of no ~/Downloads directory, yes, I’ll modify the script to test for that.

      Okay, we’re narrowing it down. Now which model?

      You just need to hold the power button for longer.

      If that’s all the issues you’ve found, you’re sitting pretty. ;)

  34. “Okay, we’re narrowing it down. Now which model?’
    I said it in my first post, Acer C720 ;) Aka Peppy (Celeron 2957U, 2GB RAM).

    “You just need to hold the power button for longer.”
    Nice to know :D

    “If that’s all the issues you’ve found, you’re sitting pretty. ;)”
    Yes, currently all fine. I bought Acer C720 cause I knew about coreboot and Linux install. I installed Linux (elementaryOS) day-1. But I wait a bit to test “pure” coreboot. And I’m very interested in coreboot build, but I don’t want to start from scratch…

    P.S: Now I plan to buy an Asus Chromebox to do the same as “small” linux desktop.

    1. Indeed you did. So many comments/posts flying around it’s difficult to keep track. Source code is here.

      If you’re going for a Chromebox, you’re probably better off with Matt DeVillier’s builds. He’s gone to quite a lot of trouble to make sure they work perfectly.

  35. Hi John,
    I tried to install one of yours firmware on my Acer Chromebook and something went wrong, I already wrote you a comment and told me send you pictures of the screen, can you send me an email so I can send you this pictures ?.
    Thanks in advanced.
    Pablo.

  36. Sorry guys, it’s a little unclear whether Asus c300 is supported or not, trying to run a script and get the following:
    Option 4:

    flash_chromebook_rom.sh: line 117: supported for this operation. Report to the G+ community at: command not found
    flash_chromebook_rom.sh: line 118: https://plus.google.com/communities/112479827373921524726\n\n: No such file or directory

    [2015-07-18 10:20:03+0100]: You have a Chromebook/box which is not currentlychronos@localhost ~ $

    As for option 1:
    Connecting to johnlewis.ie|151.80.40.78|:443… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 1048576 (1.0M) [text/plain]
    Saving to: ‘bios.cbfs.new’

    bios.cbfs.new 100%[========================================================================>] 1.00M 4.71MB/s in 0.2s

    2015-07-18 10:22:34 (4.71 MB/s) – ‘bios.cbfs.new’ saved [1048576/1048576]

    –2015-07-18 10:22:34– https://johnlewis.ie/Chromebook-ROMs/shellballs/quawks/quawks.md5
    Resolving johnlewis.ie… 151.80.40.78
    Connecting to johnlewis.ie|151.80.40.78|:443… connected.
    HTTP request sent, awaiting response… 200 OK
    Length: 883 [text/plain]
    Saving to: ‘quawks.md5’

    quawks.md5 100%[========================================================================>] 883 –.-KB/s in 0s

    2015-07-18 10:22:34 (108 MB/s) – ‘quawks.md5’ saved [883/883]

    flashrom v0.9.4 : 15e4dc9 : Apr 02 2015 22:53:02 UTC on Linux 3.10.18 (x86_64), built with libpci 3.1.10, GCC 4.9.x-google 20150123 (prerelease), little endian
    Mapping BYT IBASE at 0xfed08000, unaligned size 0x200.
    Mapping BYT SBASE at 0xfed01000, unaligned size 0x200.
    w25q_disable_writeprotect(): error=1.
    FAILED

    [2015-07-18 10:22:35+0100]: Software write-protect could not be disabled. This usually means hardware write-protect is still enabled. Please check, and try again.

    1. The download page clearly states that the ASUS C300 is only supported for BOOT_STUB i.e. option 1

      The last message you’re getting is because you haven’t removed the write-protect screw. Please remove it if you wish to go further with this.

  37. Hi John, I did the trick with the hardware write protection, and entered the command you listed above. It all seemed to work out fine. I chose option 2, to use an alternative OS. Now I have the seaBIOS (version 1.8.1) but for some reason it won’t read my usb drives. I’ve used two now. It just keeps saying booting from hard drive when I press 2. I know this is all my fault for being a beginner, but I would really really appreciate your help. Please and thank you. (To clarify, in the USB drives I have .iso files of elementaryos freya amd64 maybe that’s the problem???)

  38. Toshiba Chromebook 2 (Swanky), checking in.
    Booting Debian 8 and Kali Linux just fine with SanDisk Cruzer 16GB.

    Thanks for the hard work.

    1. No problem. And thank you for reporting another success story – when most of what you hear is people having trouble getting it working, it’s nice to know that there are those who aren’t. :)

  39. Hey John, I got it working. I just used an app to make the iso into a bootable usb and then it worked. Thank you! :)

  40. I recently flashed my bios to seabios using the script provided at the start of the page . I have an acer c710 . The issue is when I boot from USB I get a prompt that not enough memory to run image. I have 2GB ram and 16 GB SSD. I googled around and saw that if i change the boot options im able to boot a linux distro but the issue is Ubuntu won’t boot to the the gui. Only smaller distros run like core boot. I was wondering how I can flash the bios again or is there a work around ?

  41. Hello,

    i did a full flash rom on a acer c720 (i3 cpu) with no errors. It is booting normally to seabios but there is no boot menu when i try to press “ESC” (when it is prompted to do so). As a result it automatically tries to boot from the Hard Disk (which has the original ChromeOS) and is getting stuck there.

    When i change the Hard disk, to a brand new ssd, it finds no boot on the new hard disk and boots the CBFS. From there i get a Jeltka login prompt after i press enter.

    Can i have some assistance please?

    2. So, pressing a key on the keyboard isn’t doing anything? I think, just to get something working, you should flash back to shellball, restore your product data, and update the BOOT_STUB instead. Try that and come back to me.

  42. Also i don’t know if it matters, but i re-enabled back the write-protect after i flashed the rom.

  43. Zon, I noticed some firmware/keyboard issues at boot. Then try with an external USB keyboard. The build-in keyboard works at boot only if I boot Linux first. If I press power button in GRUB, the keyboard doesn’t work any more at next boot… But USB keyboard works. I have some seabios “ESC” problem too and I think everything is due to the same firmware/keyboard problem.

    1. Yes, I would have similar experiences at times, @fkxmail. Booting a Linux kernel does often “unlock” whatever is stopping the keyboard/controller from working when it gets itself in a tiz.

  44. Finally, maybe the “ESC” problem isn’t keyboard related. Cause today I noticed if ESC fail at seabios, then if I close the chromebook when I’m in GRUB instead of power-off with power button, then ESC works when I re-open the chromebook…

  45. I am trying to install in and it ask me for a input I put it in and it still say I typed it in wrong

  46. Just for clarifiction’s sake, I need to do this FROM the ChromeOS crosh shell? Or can I run this from a linux mint command line? (Acer C720) Thanks! :)

  47. Can I run this from a linux shell, or does it require a ChromeOS Crosh shell? Thanks.

  48. My apologies, I posted from two different computers (work vs. home) and didn’t see that my comment was awaiting moderation. Didn’t mean to come across as pushy/rude. :)

  49. hey, long story short; i was trying to put windows on my c710 back in the day; kept on receiving the blue screen. I did create a backup of my rom before i even began; so just wondering if you can do a quick explanation of flashing it back to chrome OS and leaving it alone.

    Please and Thank You!

    –Shawn

  50. Hi John,

    Thank you for your great software. C710-2847 mfg date 2012/11/22. Used option 2, and now may USB boot, butthe 320MB HDD is not detected, not bootable. I’ve installed Ubuntu on the HDD, but its useless.

    Options:
    A) Reflash with option 4 (Hope I can from USB Ubuntu, because I’ve already reformatted my HDD)

    B) Replace the HDD with SSD, and hope it will be detected.

    That’s all for now. Leaning towards reflash for now.

    Thanks,
    Doug

    1. Yeah, I’m beginning to think going back to SeaBIOS 1.8.x for standard Chromebooks might be better – the ChromeOS version I have compiled seems to be picky about boot devices.

Leave a comment