Ctrl u google chrome update#
The ChromeOS firmware doesn't actually look at the kernel, it just looks for a ChromeOS-specific header that describes it. On later models, you can also enable booting a custom Chromium OS kernel from USB. It doesn't matter who signed it, so you can build and boot your own kernel and rootfs. In developer mode, the RW firmware doesn't verify that the kernel is signed by Google, just that it looks like a correctly signed kernel image. The normal-mode boot process is roughly this: RO firmware verifies and launches the RW firmware, RW firmware verifies and launches the kernel, the kernel verifies the rootfs as it's read from the disk.