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
  • Known Issues
  • Glossary
  • 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
    • Updating Firmware
    • Flashing Manually
    • Booting Your OS
  • Reverting to ChromeOS
    • Flashing Stock Firmware
    • ChromeOS Recovery USB
  • Help and Support
    • Making a Bootable USB
    • Debugging / Getting Help
    • Compiling Your Own Firmware
    • Unbricking
      • With a ch341a USB Programmer
      • With a Suzy-Q Cable
  • Documentation Sitemap
  • Contributing

Flashing MrChromebox Custom Firmware

Refer to Firmware Types for information about the different firmware types available for flashing on a ChromeOS device.

DRAGONS LIE AHEAD

Flashing the firmware has the potential to brick your device, requiring relatively inexpensive hardware and some technical knowledge to recover. Not all boards can be tested prior to release, and even then slight differences in hardware can lead to unforeseen failures. If you don't have the ability to recover from a bad flash, you're taking a risk. Flashing Full ROM firmware will remove your ability to run ChromeOS.

Firmware Flashing TLDR

  1. Enable developer mode.
  2. Disable write protect (if flashing the UEFI Full ROM firmware).
  3. Run the Firmware Utility Script.
  4. If you are flashing Full ROM firmware, the script will prompt you to make a backup of your stock firmware. Store it in a safe place (Google Drive, another PC, etc), as reverting to stock firmware without a backup is more difficult and has some limitations (you can easily lose your VPD and HWID).
  5. Assuming no errors occur, power off the device using the script menu option.

IMPORTANT

If an error occurs when flashing the UEFI Full ROM firmware, do not shutdown. Using the script menu option, restore the stock firmware from your backup, and copy the log file to a safe place so you can provide it for troubleshooting.

NOTE

If you disconnected the battery to disable firmware write protect, you can plug it back in now. You will not need to disconnect it again for any subsequent flashing.

Booting

UEFI Full ROM Firmware

The first boot after flashing can take up to a minute before the display turns on - be patient and do not interrupt the first boot.

If your device still hasn't booted after 2 full minutes, perform a Hard Reset ([Refresh+Power]).

RW_LEGACY Firmware

On the Developer Mode boot screen, press Ctrl+L. If a payload menu selection appears, choose edk2.

Press ESC when you see the boot splash screen for either SeaBIOS or edk2 to access the boot menu / select your boot device.

Related Documentation

  • Firmware Utility Script - Complete script feature reference
  • Firmware Types - Understanding RW_LEGACY vs UEFI Full ROM
  • Disabling Write Protection - Required for UEFI Full ROM
  • Developer Mode - How to enable Developer Mode
  • Booting Your OS - Next steps after flashing
  • Updating Firmware - How to update UEFI firmware
  • Unbricking - Recovery from failed flash
Last Updated:: 11/25/25, 10:22 PM
Prev
Firmware Write Protect
Next
Updating Firmware