MrChromebox.techMrChromebox.tech
Donate via Paypal
Give via Patreon
Get Help on the Forums
Github Repos
Donate via Paypal
Give via Patreon
Get Help on the Forums
Github Repos
  • News & Updates
  • Getting Started
  • FAQ
  • Supported Devices
  • Firmware Utility Script
  • ChromeOS Boot Modes
    • Normal Mode
    • Recovery Mode
    • Developer Mode
    • Legacy Boot Mode (aka AltFw)
  • Firmware 101
    • Firmware Types
    • Firmware Write Protect
      • Disabling FW WP
    • Flashing Firmware
    • Flashing Manually
    • Updating Firmware
    • Booting Your OS
  • Known Issues
  • Help and Support
    • Debugging / Getting Help
    • Compiling Your Own Firmware
    • Unbricking
      • With a ch341a USB Programmer
      • With a Suzy-Q Cable
  • Reverting to ChromeOS
    • Flashing Stock Firmware
    • Making a Recovery USB
    • Booting the Recovery USB

ChromeOS Device Firmware

The firmware used by ChromeOS devices is built around serveral open-source projects, and consists (mainly) of a hardware init component (coreboot) and one or more payloads (depthcharge for Verified Boot and ChromeOS, SeaBIOS for Legacy Boot Mode) which are subsequently executed. The firmware resides on an SPI flash chip and uses the layout shown below. The shaded sections at the bottom are read-only, which is enforced by the firmware write-protect screw on the main board (sometimes with a sticker as well on some newer models). When we talk about updating the firmware on ChromeOS devices, we're referring to either the RW_LEGACY or (RO) BOOT_STUB sections, or to the entire firmware image (often referred to as a "full ROM"). These three update types are described in more detail below.

ChromeOS firmware layout

Last Updated:: 7/9/24, 7:17 PM
Prev
ChromeOS Boot Modes
Next
Known Issues