I’m running a Batch 5 Framework with Arch Linux. Attempting to launch a firmware/BIOS update through LVFS + Discover results in a seemingly bricked machine. The screen does not power on, the side codes blink out a POST code of blue, green, green, green, green, green, blue, green, and the laptop shuts down afterwards, then attempts to reboot with the same symptoms. This occured when upgrading from 3.02 to 3.07, and with 3.07 to 3.09-beta. Both LVFS and LVFS-Testing were enabled as discover sources. In both cases, the update was unsuccessful, even after device recovery (see below.)
Performing a board reset by removing, then reinserting, the CMOS battery appears to un-brick the laptop. After board reset, attempting a reboot will (after a failure) succeed, and the system will return to normal operation. Note that the attempted firmware/BIOS upgrade will not be applied, even after recovery.
Note that the 3.07 update WAS successful with the EFI shell method, if the firmware update is that necessary (e.g., I upgraded to 3.07 from 3.02 through that method because I needed the BIOS charge limit feature.) but is a tedious and risky maneuver.
I’m creating this thread as a feeler to see if anyone else has experienced similar issues, to alert Framework support, and to see if there’s a better firmware update procedure for the future that doesn’t result in nearly bricking my laptop.