Chrome OS is missing or damaged

You are using a Chromebook or some other sort of Chrome OS device and then get a message saying something like this

How to Reset a Chromebook | Digital Trends

What does the Chrome OS is missing or damaged page mean?
The “Chrome OS is missing or damaged” error page is a result of a problem with your computer (usually hardware related)! Causes of this error can range from accidentally pressing the recovery keyboard shortcut (CTRL+ESC+RELOAD) to a damaged piece of hardware!

To find out the cause

Before you can troubleshoot, you need to know what’s causing the error! To find out this information, press TAB once on the Chrome OS is missing or damaged error page! Then you should find one of the recovery reasons below!

Error code details

The error code troubleshooting infomration has been modified from it’s original verison! I have added if it’s hardware, firmware, OS, or user related!

  • 0x02: The hardware recovery button was triggered (user related)

    • The user accidentally hits the recovery button (esc+refresh+power).
    • On newer devices (2013+), power OFF and power ON will fix this issue.
  • 0x05: TPM error in read-only firmware (hardware and//or firmware related)

    • Cold reboot (remove battery and AC power, then attach power and restart).
    • If still failing after that, try contacting the firmware team.
  • 0x11: Developer flag mismatch (OS related)

    • Installing Recovery image will fix this issue.
  • 0x13: Unable to verify key block (OS related)

    • Installing Recovery image will fix this issue.
  • 0x14: Key version rollback detected (firmware related)

    • Reset the TPM: boot a test image in recovery mode (esc + refresh + power) and run chromeos-tpm-recovery.
  • 0x17: Firmware version rollback detected (firmware related)

  • Reset the TPM: boot a test image in recovery mode (esc + refresh + power) and then run chromeos-tpm-recovery.

  • 0x1b: Unable to verify firmware body (firmware related)

    • Flash firmware (bios & ec) using flashrom tool or with servo to fix.
  • 0x2b: Secure NVRAM TPM initialization error (firmware related)

    • Close the lid/ shutdown the DUT, then power on after 20 seconds
Did you know?

I actually got the “Secure NVRAM TPM initialization error” once on my chromebook?

  • 0x43: OS kernel failed signature check (OS and/or hardware related)

    • The kernel looks invalid. This is usually caused by key mismatch, data corruption, or memory / driver / IO error in last boot.
    • Can be solved by installing Recovery image, or re-key your firmware.
    • See the next section for further debugging details.
  • 0x48: No bootable disk found (hardware or firmware related)

    • Installing Recovery image will fix this issue.
  • 0x54: TPM read error in readwritable firmware (firmware related)

    • Need to reboot (refresh+power) or power cycle > 30 times to wipe TPM

WARNING! Wiping the TPM will erase all data on the device! Be sure to backup any data you wish to save to an external storage space (such as a flash drive or SD card) before wiping the TPM!

0x5b: No bootable kernel found on disk (hardware or firmware related)

  • Can be solved by installing Recovery image.
  • Or try to re-key your firmware (make sure write protection removed, or already CCD open):
    • Switch DUT to developer mode and boot
    • Run chromeos-firmwareupdate --mode=recovery --force

Now, I’ve gone over the common Chrome OS is missing or damaged error codes and now you know how to fix it if you ever get one!