Folks have been loading Ubuntu and other operating systems of custom firmware on Chromebooks for almost as long as Google’s been making Chrome OS available.

But now the company’s making it even easier for users to run custom code on a Chromebook, thanks to new debugging features that are available in developer mode.

debugging chromebook

In a nutshell the new features remove rootfs verification, which lets you modify operating system files, enables SSH access to the device using standard test keys and lets you boot from a USB drive. Users can also set a custom password for dev and system root logins.

At this point you’ll need to switch to the Chrome OS dev channel, enable Developer Mode, and wipe your hard drive before you can turn on debugging features.

Eventually the settings should graduate from Dev Channel so that you’ll be able to use them on beta or stable channels of Chrome OS. But you’ll probably always need to set your Chromebook to developer mode.

via +François Beaufort

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign


Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

Subscribe to Liliputing via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 9,503 other subscribers

2 replies on “Google makes it easier to load custom code on Chromebooks”

  1. I really wish the whole user/developer switcheroo was not as destructive.

    Damn it, the whole segregation between “users” and “developers” is iffy. I noticed the same mentality during the keynote of the Ara dev conference, and it rubbed me the wrong way there as well.

    For me the power of the PC was that there was no shark delineation between user and developer. You could start out easily enough with preinstalled defaults, and then transition more and more towards “developer” as you learned how the system worked etc.

    With the sharp delineation these days, you pretty much has to come at it with a desire to go “developer” From day one. And then perhaps ask for permission from the corporations on high before doing so.

Comments are closed.