HP Chromebook 14 G5 Shuts Down During Firmware Replacement Without the Battery

0
17
Asked By MellowPine42 On

I've installed Linux Mint on several Chromebooks, but this HP Chromebook 14 G5 (HWID "Snappy") is giving me trouble. The firmware instructions indicate that the battery should be disconnected and the machine powered from an external charger before changing the write-protect state. However, after disconnecting the battery and connecting a new 65W USB-C charger, the Chromebook briefly displays the "OS verification is disabled" screen, shuts off, and repeatedly tries to start again. It seems unable to remain powered by the charger alone. Is there a reason a 65W charger may not be sufficient, and is there a safer way to disable write protection and install replacement firmware?

3 Answers

Answered By QuietHarbor7 On

Some Chromebook models cannot operate reliably without a battery because of embedded-controller limitations or the way their power hardware is designed. The Snappy platform appears to be one of them. A compatible SuzyQ-style debug cable may be a better option than trying to run it battery-free. Another possibility is a board-specific method involving the write-protect pin, but that requires identifying the correct flash chip and following the hardware documentation carefully.

MellowPine42 -

That makes sense. I was confused because the documented minimum charger rating is lower than 65W, but the issue may be that the Chromebook simply cannot maintain power without the battery rather than needing more wattage.

Answered By CautiousCircuit9 On

If the battery is connected, the firmware utility can often handle the write-protect process and guide you through the required reboot. Avoid manually forcing write protection off with flashrom unless you are certain the procedure applies to this exact model; using the wrong sequence can leave the Chromebook unable to boot. Make a recovery plan before flashing anything.

Answered By SilverMaple18 On

One reported workaround is to reconnect the battery, open a virtual console, check the write-protect status, and then use the model’s firmware utility to install UEFI firmware. However, this should be treated as model-specific advice and followed only after verifying the instructions for the exact HWID. The safer general approach is to let the utility perform the checks and prompts rather than issuing low-level flash commands manually.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.