Don't want Chrome OS on your Chromebook? OK says Google.

happygeek 0 Tallied Votes 408 Views Share

According to François Beaufort who is a French 'Happiness Evangelist' at Google (and no, I didn't make that up), Chromebook users will soon be able to choose what operating system they want. In a publicly shared post from last week, Beaufort states that "in order to support installing and testing custom code on Chrome OS devices, the chromium team is currently adding the ability to easily enable Debugging Features when the device is booted in Developer Mode." This will mean that such things as removing the rootfs verification top enable OS file modification will be possible, along with enabling SSH access using standard test keys and, importantly, booting from USB for installing an OS image off a USB drive.

OK, so but these changes will likely make the process easier. That said, you are still talking about having to 'powerwash' the Chromebook into the Dev Channel and enable debugging features, so it's still not for the feint-hearted and there's always the opportunity to brick your device if you get it wrong.

So is anyone here already running a dual-boot Chromebook, or inspired to get rid of ChromeOS following this news? If so, let us know how you get on.

Dani AI

Generated

A short, practical update that expands on ’s original note and the replies from and .

The low-level path still exists: Developer Mode plus the debugging features gives you the ability to make the root filesystem writable and boot alternate images. The Chromium developer docs show the exact workflow and even the command used to remove rootfs verification (sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification). That capability is powerful but it disables verified boot and will wipe local data when toggling modes — so treat it as a last resort and read the device docs first. (chromium.googlesource.com)

For most people who just want a usable Linux environment, the official “Linux (Beta)” / Crostini containers are the safer, easier option. They run in a lightweight VM, don’t require Developer Mode or firmware flashing, and are supported on most devices launched in 2019 or later. Try Crostini first before doing anything that modifies firmware or partitions. (chromium.org)

If a full dual‑boot or ChromeOS replacement is required: chrx offers a two‑phase installer for dual‑boot setups, and MrChromebox’s firmware utility is the common path to RW_LEGACY or full‑UEFI firmware if you need to boot arbitrary ISOs. Both approaches are model‑specific, usually require disabling firmware write‑protect (screw or software flag), and carry a real risk of bricking. Note that crouton has been archived and GalliumOS is no longer actively maintained, so follow current chrx/MrChromebox guidance and have recovery media ready. (chrx.org)

Practical checklist: back up everything; create a Chromebook recovery USB before you start; confirm your exact model on chrx/MrChromebox compatibility pages; test from a live USB when possible; and consider whether buying a cheap x86 laptop (as did) or using a Pi‑based rig (as noted) is a faster, lower‑risk solution than firmware surgery. If continuing, read the device‑specific docs top‑to‑bottom and keep recovery instructions at hand. (support.ctl.net)

Member Avatar for Member #46692
Member #46692

I was toying with the idea before, I thought hmmm, these chrome books are cheap, reasonable spec and has an ssd drive. But for whatever reason, I think I looked at the hacks required, and decided against it, even though I'm quite familiar with hacks and linux.

Got myself a smallish notebook wiped it and put lubuntu on. Less hacking. I don't know, would be good to hear others experiences.

Chromatix 0 Newbie Poster

I'm not afraid of jumping through a few hoops to get the OS I want installed the way I want. One of the things which turned me off Chromebooks was the need to keep ChromeOS installed alongside your chosen system, eating up disk space which is already scarce. The need to manually select the secondary boot option on every boot was also nasty.

Incidentally, the whole cloud storage thing is the major turnoff of ChromeOS for me; that and the idea of the whole desktop essentially being a web browser. I habitually write more efficient software than average in my day job - I don't want to go in the opposite direction at home.

With this new option, it looks like a much fairer matchup between a ChromeBook with a different OS and a Raspberry Pi 2 adapted into a laptop form factor, now that the latter is truly fast enough for daily use.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.