Chromebook mostly bricked due to a setting I changed in coreboot

Support Linux Support
1

Codename: Fleex - Board: Octopus

Hey everyone, just want to raise an issue that I assume won’t be too likely to happen but will force me to reflash firmware manually with a bios programmer. Here is what happened in chronological order:

  • I installed coreboot about 3 months ago without any issues
  • I updated firmware to the 10/13/25 release, which gave me access to new settings
  • I changed the setting in Avanced Configuration –> Platform Setup Menu –> Restore AC power after loss to “Power off (S5)” to prevent my chromebook from turning on after I plugged it in when it was shut down for a while.
  • Today I reflashed chromeos firmware in the mrchromebox script with a recovery usb - any attempt to reset ec (power + refresh) or enter recovery (esc + refresh + power) instantly turns the chromebook off. Likely its due to the fact that I changed the setting earlier.

Right now I can power the chromebook on but I can’t install chrome os because I can’t access the recovery menu. I’ll try to unbrick it sometime this week.

2

I’ve verified that changing the setting was the issue. I have an identical chromebook and after changing the setting to “Power On (S0)” on the secondary device I was able to restore chromeos without any issues.

3

I’ll be removing that option in the next release

4

There were 2 settings that are also in the advanced section that looked like they had something to do with chromeos, and after disabling them I started experiencing the issue that I had posted about. Is there anyway to fix coreboot if it’s power looping?

5

there’s nothing in setup options related to ChromeOS as this firmware is not built to boot ChromeOS.

I plan on adding a feature to reset all settings if it boot loops 5x in a row, but for now you could need to manually clear the NVRAM using a SuzyQ or USB programmer

6

If I clear the nvram, would I need to reinstall coreboot, or would it just be reverted back to its original state when it was installed by the script?

7

the whole point of clearing the NVRAM is that you don’t need to reflash anything :wink:

1 Like
8

Hi, i have a problem with hp chromebook g7 14, the firmware UEFI correct flash, by script, then i install Windows on eemc, but i make changes in the advanced settings, disable tpm or other advanced option, when save changes the Chromebook turn off screen, and don’t boot only feel overheatead, i extract the firmware from windbond with programmer 341a black, can this have a vp, and hwid, i flash a stock drawcia firmware without vpd and hwid, with the WP disable, but the result is the same, blackscreen and don’t boot, and only feel overheated. I use a neoprogrammer on other Windows device.