My Framework 16 AMD (Ryzen 7040) BIOS update was interrupted. Nowhere on the guides does it talk about a crisis recovery mode, yet Copilot told me to hold FN + ESC and press the Power button and it seemed to make my USB (USB in top left port, USB-C charger in top right port) blink differently than if I normally turned it on so I’m assuming there is a crisis recovery mode. I tried it with the EFI Shell update… but I need the BIOS recovery capsule (.bin) for version 4.04 for my board revision, but I can’t find anything like that on framework websites, only the EFI Shell updates for when you already have a working BIOS. Why not make the recovery capsules public? At least then people could recover their motherboards.
I’m pretty sure that’s what’s wrong since I tried power draining (plugging in the battery made 2 red flashes), I tried motherboard reset by flipping the switch 10 times for 2 seconds each before that, and yeah, nothing is working for me.
You have been lied to by the lying machine. Contact support.
The announcement of the 4.04 release still exists in the forums here: Framework Laptop 16 Ryzen 7040 BIOS 4.04 Release STABLE
The zip file containing the 4.04 EFI file is on the Content Delivery Network (CDN) here: https://downloads.frame.work/bios/Framework_Laptop_16_Amd_Ryzen7040_BIOS_4.04_EFI.zip
It’s not obvious that you can search for these things in the forum but the historical record survives (for now).
FW do not have a recovery process for this situation.
They tend to just RMA the mainboard.
So contact FW support via their web site form. I hope FW add the following features in future mainboard designs:
- EC firmware backup and recovery.
- charger chip firmware backup and recovery.
- BIOS firmware backup and recovery.
- tools to set the correct serial numbers etc. Back in after the recovery.
These are possible by soldering on developer connectors onto the FW16 board, but i think it would be better if FW actively supported this and publish the recovery methods.