Firmware Type: Stock (attempting to install UEFI Full ROM)
Firmware Version: Google_Lantis.13606.424.0
Internal storage type: eMMC (64 GB)
Summary of the Issue
I attempted to install the MrChromebox UEFI Full ROM firmware after successfully disabling write protection using the WP jumper (battery disconnect did not disable WP on this model).
The script created a successful 16 MB stock firmware backup before flashing.
During the flashing process, the script failed with:
After rebooting, the Chromebook no longer boots ChromeOS and always enters ChromeOS Recovery.
Recovery detects the USB correctly, verifies the recovery image, starts installing ChromeOS, but always fails near the end with:
Installation of software failed
error clobbering lockbox space: 132
Rollback version stored in the TPM
tpmc clear failed (0x84)
The device never booted into the MrChromebox UEFI firmware. It only boots into ChromeOS Recovery.
Steps to Reproduce
Disabled write protection using the WP jumper on a HP Chromebook 14a (LANTIS).
Ran the official MrChromebox firmware utility and selected Install/Update UEFI Full ROM.
The script failed during the flashrom step with “SPI Configuration is locked down”. After rebooting, the device only boots into ChromeOS Recovery, which always fails to complete.
Expected Behavior
The UEFI Full ROM firmware should have been written successfully and the device should have booted into the MrChromebox UEFI firmware instead of ChromeOS Recovery.
this is a normal output from flashrom, it has nothing to do with the flash failing. To determine the cause of that, I’d need the flashrom.log that was generated when flashing, which is now erased since you rebooted.
please pastebin the full recovery.log from the recovery media so I can see what’s going on there
Hi, sorry to insist and waste your time, but I haven’t been sleeping well these past few days wondering if the problem would be solved by backing up the original ROM, I’d just like to know if that would help, I’m waiting for the programmer to arrive.. Thank you
your firmware is corrupted to the point to where the recovery process can’t fix it:
manpage for more details.
ERROR: get_ro_range: Could not find WP_RO in the FMAP
Machine Model: lantis
Write Protect: HW=1 SW=1
Last Boot Version: RO=Google_Lantis.13606.424.0 ACT/recovery=Google_Lantis.13606.424.0
Firmware Updater: RO=Google_Lantis.13606.533.0 RW=Google_Lantis.13606.710.0
INFO: get_manifest_key_from_crosid: Identified the device using libcrosid, matched chromeos-config index: 1200, manifest key (model): lantis
>> Starting firmware updater.
>> Target image: images/bios-lantis.ro-13606-533-0.rw-13606-710-0.bin (RO:Google_Lantis.13606.533.0, RW/A:Google_Lantis.13606.710.0 (w/ECRW:), RW/B:Google_Lantis.13606.710.0 (w/ECRW:)).
coreboot table found at 0x78b54000.
Found chipset "Intel Jasper Lake".
Enabling flash write... Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
New value is 0x8b.
SPI Configuration is locked down.
FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG1: BIOS region (0x00381000-0x00ffffff) is read-write.
FREG2: Management Engine region (0x00001000-0x00380fff) is read-only.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see https://flashrom.org/ME for details.
GPR0: Warning: 0x00001000-0x000f5fff is read-only.
At least some flash regions are write protected. For write operations,
you should use a flash layout and include only writable regions. See
manpage for more details.
OK.
Found Winbond flash chip "W25Q128.V..M" (16384 kB, Programmer-specific) on internal.
>> Write protection (internal): 0 (disabled; HW=1, SW=0).
INFO: update_firmware: Loading current system firmware...
INFO: load_system_firmware: Reading SPI Flash (programmer internal)...
Warning: Setting BIOS Control at 0xdc from 0x8b to 0x89 failed.
New value is 0x8b.
GPR0: Warning: 0x00001000-0x000f5fff is read-only.
At least some flash regions are write protected. For write operations,
you should use a flash layout and include only writable regions. See
manpage for more details.
WARNING: load_firmware_version: No valid section 'RO_FRID', missing version info.
ERROR: do_update: Cannot load system active firmware.
Thanks for confirming, I actually have a CH341A + SOIC8 clip on the way instead of a SuzyQ — since it connects directly to the Winbond chip and bypasses the cr50/CCD layer entirely, would that work equally well (or better) for restoring my full stock backup ROM?