i5-1240P updated fine, used the EFI method (files on a FAT formatted USB, rebooted and selected it to start the USB) this time (previously when I updated to 09) none of my efi variables got nuked, so I am a happy man.
so far CPU speed and fans seem ok, fans do act a bit more aggressive, but might be fine for my use cases. (and can be configured) Arch linux user, sometimes windows but havent check win.
Wait what, i got the exact same thing here! What`s the foam thing? First time i hear of this behavior…
It’s actually possible I moved some foam around as i just did a clean of the insides today to diagnose a touchpad issue ([RESPONDED] Spurious clicks while using touch pad - #7 by anarcat), but i can’t tell what foam we’re talking about here… where can i read more about this?
update: i found this explanation, [SOLVED] Constant Red Blinking Lights when Powered On - #2 by Morpheus636. i can confirm that pushing on the little tab by hand turns off the flashing led, so it looks like i somehow moved the pad in my operations! taking the pad off and aligning it again with the engraving in the metal sheet fixed it!
also, shout out to the framework team for pushing out a BIOS release so far away from the hardware release date of that platform, with LVFS support, even. That’s pretty amazing, don’t listen to the naysayers, you rock. 
I did manage to fix my issue as well. Taking the input cover off I noticed a small black outline square and figure that the black foam piece must have shifted at some point during the disassembly process. A small piece of double sided tape helped stick it back together and in the right spot.
Just did the update, via EFI. For me, even with battery extender disabled, the float feature isn’t working. It keeps jumping between 79% and 80% (I’ve set the limit to 80%)…
After failing to upgrade a standalone 3.06 FW13 12th-Gen Intel mainboard to 3.08 in January (12th Gen Intel Core BIOS 3.08 Release - #662 by Anthony_Garrett_Guil), I again attempted the EFI upgrade method following the standalone instructions on OP and experienced no positive change in behavior from my last attempt.
PD upgrades still work without issue, but the BIOS upgrade still fails at the same point (the “After PD updates, it will reboot automatically, then start the BIOS capsule update” point in OP’s instructions; the reboot occurs, but the BIOS capsule update never happens).
Nearly identical messages are reported as the 3.08 failures: Error 331: Full FW Update using same version is not allowed. Include -allowsv in command line to allow it., Succeed to write Framework_Laptop_13_12th_Gen_Intel_Core_capsule_signed_allsku_3.17.cap.
The only significant change in behavior is that the system now reboots after each failed attempt instead of shutting down, which leads to an endless loop of failed upgrade attempts if left unattended. The only way to stop it is to pull the upgrade media between reboots.
A video of one complete loop of failure:
I’m still on 3.06 as a result.
Perhaps this is helpful: Framework Laptop 13 - 12th Gen Intel Core BIOS 3.17 Release Stable - #53 by real_or_random
LVFS upgrade fails as expected because this is a standalone system with no battery.
The initial step appears to signal success:
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 0.0.3.6 to 0.0.3.17? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This firmware update includes the following changes: ║
║ ║
║ • Update Intel CSME to 16.1.32.2418v0.2_A0_Corporate ║
║ • Update PD firmware version 0.1.2E to improve system power consumption ║
║ with low power HDMI/DP expansion cards when no monitor is attached. ║
║ • Fixed retimer updates cause ports to stop working after the update. ║
║ • Fixed retimer capsule update causes the device in standalone mode to ║
║ reset and fail updating during the update process. ║
║ • Added battery lifetime extender functionality.(See below for details) ║
║ • Add USB4 PCR Measurement BIOS option in the advanced setup menu. ║
║ • Fixed the battery extender setting overwritten battery charge limit on ║
║ boot. ║
║ • Fixed high temperature causes continuous CPU throttling to LFM. ║
║ • Fixed battery charging limit is reset by battery extender reset timer. ║
║ ║
║ Laptop (12th Gen Intel Core) must remain plugged into a power source for ║
║ the duration of the update to avoid damage. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Waiting… [***************************************]
Successfully installed firmware
Do not turn off your computer or remove the AC adapter while the update is in progress.
Devices with the latest available firmware version:
• UEFI dbx
• Unifying Receiver
Devices with no available firmware updates:
• KEK CA
• Patriot M.2 P310 240GB
• UEFI CA
• UEFI Device Firmware
• UEFI Device Firmware
• Windows Production PCA
• frame.work-LaptopADLDB
• frame.work-LaptopADLKEK
An update requires a reboot to complete. Restart now? [y|N]:
After the reboot nothing has changed, and fwupdmgr get-updates reports Update Error: failed to update to 785: error-pwr-evt-batt.
$ fwupdmgr get-updates
Devices with no available firmware updates:
• KEK CA
• Patriot M.2 P310 240GB
• UEFI CA
• UEFI Device Firmware
• UEFI Device Firmware
• Windows Production PCA
• frame.work-LaptopADLDB
• frame.work-LaptopADLKEK
Devices with the latest available firmware version:
• UEFI dbx
• Unifying Receiver
Framework Laptop (12th Gen Intel Core)
│
└─System Firmware:
│ Device ID: ...
│ Summary: UEFI System Resource Table device (updated via NVRAM)
│ Current version: 0.0.3.6
│ Minimum Version: 0.0.3.0
│ Vendor: Framework (DMI:INSYDE Corp.)
│ Update State: Transient failure
│ Update Error: failed to update to 785: error-pwr-evt-batt
│ GUID: a30a8cf3-847f-5e59-bd59-f9ec145c1a8c
│ 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
│
└─Laptop 13 Intel 12th Gen Core System Update:
New version: 0.0.3.17
Remote ID: lvfs
Release ID: 112012
Summary: Framework Laptop System Firmware for Intel 12th Gen Core Mainboards
License: Proprietary
Size: 36.1 MB
Created: 2025-04-24
Urgency: High
Tested: 2025-04-29
Distribution: fedora 41 (workstation)
Old version: 0.0.3.9
Version[fwupd]: 1.9.29
Vendor: Framework
Duration: 2 minutes
Release Flags: • Trusted metadata
• Is upgrade
• Tested by trusted vendor
Description:
This firmware update includes the following changes:
• Update Intel CSME to 16.1.32.2418v0.2_A0_Corporate
• Update PD firmware version 0.1.2E to improve system power consumption with low power HDMI/DP expansion cards when no monitor is attached.
• Fixed retimer updates cause ports to stop working after the update.
• Fixed retimer capsule update causes the device in standalone mode to reset and fail updating during the update process.
• Added battery lifetime extender functionality.(See below for details)
• Add USB4 PCR Measurement BIOS option in the advanced setup menu.
• Fixed the battery extender setting overwritten battery charge limit on boot.
• Fixed high temperature causes continuous CPU throttling to LFM.
• Fixed battery charging limit is reset by battery extender reset timer.
Issues: CVE-2024-49200
CVE-2024-30211
CVE-2024-26021
CVE-2024-31068
CVE-2024-25078
CVE-2023-34424
CVE-2023-38655
CVE-2023-40067
CVE-2023-48361
CVE-2024-21844
CVE-2023-45230
CVE-2023-45232
CVE-2023-45233
132380
CVE-2023-45234
Checksum: ff32fd8dfe10a353361e599bdbb3a49c503768beeb4664be4a34a5f40ac110fd
It seems that standalone updates are still not possible.
Took me a while to get around to doing this, just ran it and my CSME is now also on the latest version. So I updated (without issues) via LVFS and ran the EFI update after that (without issues) to update the CSME. Thanks again!
Gentoo (UEFI Stub, ZFS)
12th Gen i7-1280p
v3.08 → v3.17 (UEFI Shell script)
Following these instructions https://knowledgebase.frame.work/en_us/framework-laptop-bios-and-driver-releases-12th-gen-intel-core-Bkx2kosqq
Update hung at “Update PD1 Progress:”
After waiting for over an hour, fans full tilt and hot enough to fry some eggs (and getting hotter as time went on), I began to worry of a meltdown.
I tried to dirty boot by manually holding the power down for up to 30 seconds the first time, 60 seconds the second time, it was unresponsive. It didn’t respond to keyboard commands either.
Finally, I unplugged the power and just let it drain down the battery, which occurred rapidly, within 15 minutes (the battery was at 100% prior to starting the upgrade).
I let it cool down to room temperature and plugged the power back in. After giving it 20 minutes to charge a bit, I decided to power on the machine again. The result was no display (not even backlit), it stayed powered on for about 40 seconds before rebooting and the cycle continues indefinitely.
Here is a video: Proton Drive
I have this same issue trying to update a 1280p mainboard from 3.08 to 3.17 via the EFI shell method.
Framework support agreed to a one-time replacement of the mainboard, which I’m thankful for.
I’ll admit, I was pretty heated in the discussion with support. However, in my 20+ years as an IT professional, I’ve never once bricked a device from a firmware update. Maybe I’ve been lucky in the past but irrespective of that, my apologies for how unkind I was dealing with this issue.
Having said that, I applaud the support staff for taking my frustration and tone in stride and ultimately doing the right thing, thank you!
