FW13: Failed to update BIOS (3.17 -> 3.22) [fixed]

Framework Laptop 13
1

Tried to update from 3.17 to 3.22 using UEFI, get stuck in a boot loop… I unplug the USB when device is off between updates and boot back in. I’m still on 3.17.

├─System Firmware:
│ │   Device ID:          4e494f28c524fcd4beef1b131512b664c09476d1
│ │   Summary:            UEFI System Resource Table device (updated via NVRAM)
│ │   Current version:    0.0.3.17
│ │   Minimum Version:    0.0.0.1
│ │   Vendor:             Framework (DMI:INSYDE Corp.)
│ │   Update State:       Failed
│ │   Update Error:       failed to update to 0: error-unsuccessful
│ │   GUID:               b3bdb2e4-c5cb-5c1b-bdc3-e6fc132462ff
│ │   Device Flags:       • Internal device
│ │                       • Updatable
│ │                       • System requires external power source
│ │                       • Supported on remote server
│ │                       • Needs a reboot after installation
│ │                       • Cryptographic hash verification is available
│ │                       • Device is usable for the duration of the update
│ │   Device Requests:    • Message

I try to redo the update, but get Full FW Update using same version is not allowed. I modify the efi/boot/startup.nsh file with -allowsv, and get the same initial issue. No errors in error.log.

I came across this thread: Getting an error saying "Error 331: Full FW Update using same version is not allowed. Include -allowsv in command line to allow it." when updating to newest bios?

Trying to update to 3.19 shows “Update to image with lower VCN is not allowed”. Ok, that’s mentioned in the thread, so I try to reinstall 3.17.

That fails completely with “Update BIOS failed”, which is a different issue to the original thread.

These are the UEFI files used:

Framework_Laptop_11th_gen_Intel_Core_BIOS_3.17_EFI.zip  Framework_Laptop_13_11th_Gen_Intel_Core_BIOS_3.22.zip
Framework_Laptop_13_11th_Gen_Intel_Core_3.19_EFI_c.zip
2

Some screenshots:

IMG_3263
IMG_32631920×1440 322 KB

IMG_3264
IMG_32641920×1440 193 KB

3

The “No AC connected” error.
There have been reports of when the battery is at 100% it thinks the AC is not connected.
Discharge to something like 80-90%, plug the AC in and try again.

1 Like
4

That seemed to fix it! Got my BIOS on 3.22 now. Odd that I couldn’t directly upgrade form 3.17 to 3.22 and had to look for all these extra steps.