Error message running script: An error occurred flashing the Full ROM firmware. DO NOT REBOOT!

[TheArkive]

I tried following the README instructions and got the following error:

An error occurred flashing the Full ROM firmware. DO NOT REBOOT!

I was on ChromeOS 91 when I tried this. I was able to get advice from MrChromebox (yay!)

Apparently after disabling Write Protect one must reboot. This does not seem to be included in the README instructions.

The original wiki from MrChromebox site for Pixelbook (EVE) is here:

https://wiki.mrchromebox.tech/Firmware_Write_Protect#Open_the_CCD

It states to reboot after disabling WP.

Also your suggested commands are different from those suggested by MrChromebox.

MrChromebox version:

cd; curl -LO mrchromebox.tech/firmware-util.sh
sudo install -Dt /usr/local/bin -m 755 firmware-util.sh
sudo firmware-util.sh

source: https://mrchromebox.tech/#fwscript

The fix for this situation is the following (from MrChromebox):

1) DO NOT REBOOT
2) run:   sudo flashrom -w /tmp/bios.bin -n

this will restore the old firmware

3) Reboot - using the script options (R from the main menu)
4) You will likely have to run recovery after this.  Developer mode should still be enabled.

I actually got a white screen that persisted for a while. This white screen seems to be harmless. It occurs after the firmware update if you select Shutdown from the touchscreen. Just F2 (Refresh) + Power to restart. I was indeed prompted to run recovery after subsequent power-on. I actually got an "unexpected error" the first time I tried the Recovery operation. I didn't have to erase/re-create the recovery media (thankfully), or try using a different USB stick.

I'm now back into the normal OS with developer mode still enabled. Most of the WP and CCD status are still open and Y.

Now the script has worked and I'm running my alt OS on my Pixelbook.

[CoupDeKai]

Thank you so so much for posting this, I got to the same point and wow is "DO NOT REBOOT!" ever a scary thing to see in red font when you've just messed with the bios...

I assume that had I rebooted I would have needed an EEPROM programmer tool to fix it, instead a few extra commands and I've finally got my OS of choice installed.