This is the page to come to if you want to poke around your Chrome OS device. These are devices that shipped from the factory with Google Chrome OS on them. For some details about Google Chrome OS and how it differs from Chromium OS, see the note in the FAQ about Google Chrome OS.
This guide is not targeted at people doing Chromium OS development or building/installing a hand-built Chromium OS image. For that information, see the Chromium OS Developer Guide. This guide is instead targeted at people who just want to hack around on their hardware.
All of the instructions on this page require your Chrome OS device to be in Developer Mode. The way to do this is a little different on each device, so you'll have to refer to the developer information for your Chrome OS device to figure out how.
Caution: Modifications you make to the system are not supported by Google, may cause hardware, software or security issues and may void warranty.
Note that putting your device into developer mode inherently makes it a little less secure. Specifically, it makes the "verified boot" that's built-in to your hardware a little bit more lax, allowing your hardware to run custom (non-Google-signed) images. It also gives you access to a "root" shell.
The procedure for booting custom images on your Chrome OS device may also be device-specific.
You can tell that you're in Developer Mode if you see one of these screens when you turn the device on:
device-specific. In addition, if you've made changes to the SSD image while in developer mode, you may have to use the recovery process to restore your device to the factory condition. However, as long as you don't crack open the case, you shouldn't be able to do anything that can't be undone by recovery (software).
If you're a Linux hacker, you probably know that Google Chrome OS is built on top of Linux and you're wondering how you can jailbreak your device so you can get to a command prompt. It turns out: there's no need. The command prompt is built in to your device!
IMPORTANT NOTE: Before following these instructions, remember to put your device into Developer Mode (see above).
One way to get the login prompt is through something called VT-2, or "virtual terminal 2". This is probably familiar to the Linux hackers out there. You can get to VT-2 by pressing:
...where the [ => ] key is the right-arrow key just above the number 3 on your keyboard.
Once you have the login prompt, you should see a set of instructions telling you about command-line access. By default, you can login as the
The instructions do tell you how to get back to the browser, but because it's so important, I'll also put it here. Just press:
...where the [ <= ] key is the left-arrow key just above the number 1 on your keyboard.
SIDE NOTE: For the technical-minded, you may realize that the top-rows of the keyboard on a Chrome OS device are actually treated by Linux as the keys F1 through F10. Thus, the [ => ] key is actually F2 and the [ <= ] key is actually F1.
SIDE NOTE: If you're fooling around, you might also notice that kernel messages show up on VT-8.
Because you booted into developer mode, you also have an alternate way to get a terminal prompt. I'll mention this as well, since the alternate shell is a little nicer (in the very least, it keeps your screen from dimming on you), even if it is a little harder to get to. To use this alternate way:
Note that entering the shell this way doesn't give you all the instructions that VT-2 does (like how to set your password). You might want to follow the VT-2 steps once just to get the instructions.
If you want to get back to the browser without killing the shell, you can do it with [ Alt ] [ Tab ].
SIDE NOTE: You can actually create as many shells as you want. Just hit [ Ctrl ] [ Alt ] [ T ] again and a second shell will be opened. You can [ Alt ] [ Tab ] between them.
NOTE: If you mount the root filesystem in writeable mode, even if you make no changes, it will no longer be verifiable and you'll have to use a recovery image to restore your system when you switch back to normal mode.
To make your rootfs writable, run this from a shell:
Then reboot. Your rootfs will be mounted read/write.