# BIOS update stuck **URL:** \ **Category:** Community Support\ **Tags:** freezing-crashing, amd-7040\ **Created:** [July 7, 2026, 10:30pm UTC](https://community.frame.work/t/bios-update-stuck/83416 "2026-07-07T22:30:20Z")\ **Posts on this page:** 12\ **Page:** 3
**Author:** ![Torbjorn\_Granlund](https://avatars.discourse-cdn.com/v4/letter/t/dbc845/32.png) [@Torbjorn\_Granlund](https://community.frame.work/u/Torbjorn_Granlund)\ **Post date:** [August 18, 2026, 8:35pm UTC](https://community.frame.work/t/bios-update-stuck/83416/42 "2026-08-18T20:35:46Z")
It’s not “cheaper” to desolder the flash chip unless you have engineers working without salary. This latest debacle has already cost more than a new laptop in lost productivity. While we can accept occasional hardware issues, the widespread bricking of Framework computers, and Framework’s unwillingness to address the problem, is not acceptable. With that in mind, fixing bricked Framework laptops even at zero cost is too expensive, as one has to assume the laptop can be bricked again by known-broken firmware, incurring additional lost productivity. If Framework had pulled the bad BIOS when they were informed about the problem, that that would have saved us a lot of headache and costs. As I write this, more laptops are getting bricked. (While I am not familiar with how exactly Framework’s BIOS upgrade works, it seems unlikely that the update method matters. Say that there is a bug in the Linux fwupdate stuff? But surely the images are cryptographically signed? If fwupdate messes up its download, the new image would be rejected!) ---
**Author:** ![goldenspinach](https://avatars.discourse-cdn.com/v4/letter/g/f1d935/32.png) [@goldenspinach](https://community.frame.work/u/goldenspinach)\ **Post date:** [August 19, 2026, 12:39am UTC](https://community.frame.work/t/bios-update-stuck/83416/43 "2026-08-19T00:39:52Z")
Related thread with more links: [Upgrading to BIOS 3.20 on Ryzen 7040 series may brick your machine](https://community.frame.work/t/84031) TLDR: **do not upgrade to BIOS 3.20** unless you want to risk bricking your laptop. Even though Framework encouraged the BIOS 3.20 update, Framework will not replace bricked mainboards that are “out of warranty”. This is a major f-up on the part of Framework. ---
**Author:** ![balupton](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/balupton/32/18824_2.png) [@balupton](https://community.frame.work/u/balupton)\ **Post date:** [August 19, 2026, 2:39am UTC](https://community.frame.work/t/bios-update-stuck/83416/44 "2026-08-19T02:39:52Z")
> [@Torbjorn\_Granlund](#): > > Does Framework expect us to buy new motherboards and then hope the new motherboard is not bricked too? My mainboard was only about a month old when it bricked from this bios update, so it affects the latest batches of mainboards too. The mainboard was a warranty replacement of a prior one that had charging/power issues. > [@Torbjorn\_Granlund](#): > > It’s not “cheaper” to desolder the flash chip unless you have engineers working without salary. There are guides on how to fix the bad bios update without desoldering: [Fixing a bricked AMD 7040 series Framework 13” laptop with $20 tools | Quantum](https://qt.ax/ffw) > [@goldenspinach](#): > > This is a major f-up on the part of Framework. It is shocking to me that there are now numerous threads, some very lengthy and detailed, and that framework’s only official response so far are private warranty responses; yet they are still posting new marketing everyday of their reliability, support, repairability and pushing new hardware. It seems so disconnected. I’m blessed to be in Australia where there is Australia Consumer Law that protects us from such shenanigans, but the lack of compassionate and mission orientated communication from Framework on this has had made me really double take my recommendations of Framework; and the longer there isn’t such communication, the deeper the said disconnect and my concern grows. ---
**Author:** ![Andrew\_Moise](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Andrew\_Moise](https://community.frame.work/u/Andrew_Moise)\ **Post date:** [August 19, 2026, 3:51am UTC](https://community.frame.work/t/bios-update-stuck/83416/45 "2026-08-19T03:51:38Z")
> It’s not “cheaper” to desolder the flash chip unless you have engineers working without salary. Not only that, resorting to these hobbyist shenanigans feels totally different when you know the only reason for it is that FW can’t be bothered to stand behind their product. You worked hard on something but it still needs a little tinkering sometimes? Fine. That’s actually kind of fun. You shipped me something you already knew was shoddy, and then told me to fuck off and pony up $500 more when I lost the die-roll and it broke my hardware? That’s not fun. That doesn’t feel good at all. (I don’t even have a FW13, let along a bricked one; I am only in this because I was reading up trying to figure out if I should apply the current update for my FW16. Even hearing about it secondhand I am appalled on behalf of the people impacted though.) ---
**Author:** ![Niklas\_Deppermann](https://avatars.discourse-cdn.com/v4/letter/n/b19c9b/32.png) [@Niklas\_Deppermann](https://community.frame.work/u/Niklas_Deppermann)\ **Post date:** [September 19, 2026, 7:46am UTC](https://community.frame.work/t/bios-update-stuck/83416/46 "2026-09-19T07:46:26Z")
Happend to me too yesterday. Shame on you, Framework, for still offering this “Update” ---
**Author:** ![Eric\_Chen](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@Eric\_Chen](https://community.frame.work/u/Eric_Chen)\ **Post date:** [October 10, 2026, 3:40pm UTC](https://community.frame.work/t/bios-update-stuck/83416/47 "2026-10-10T15:40:02Z")
This is still happening. I used dolphin to update to Fedora 44 and clicked update all and laptop bricked. The diagnostic leds are all green and everything powers on but no display Why the bios update is still available is baffling ---
**Author:** ![pkunk](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@pkunk](https://community.frame.work/u/pkunk)\ **Post date:** [October 11, 2026, 1:20am UTC](https://community.frame.work/t/bios-update-stuck/83416/48 "2026-10-11T01:20:37Z")
At this point for this release version. Running it in anything except the UEFI USB method is really taking chances if it wil update correctly. Try an external display and see if that still works. It could just be coinciding with a display cable that has managed to work its way loose, or it was a little loose and finally just separated enough to no longer display a signal. ---
**Author:** ![Eric\_Chen](https://avatars.discourse-cdn.com/v4/letter/e/90db22/32.png) [@Eric\_Chen](https://community.frame.work/u/Eric_Chen)\ **Post date:** [October 11, 2026, 3:57am UTC](https://community.frame.work/t/bios-update-stuck/83416/49 "2026-10-11T03:57:42Z")
Nope display cable definitely seated. Usbc display doesn’t work either The 12 diagnostic LEDs are green so no issues with ram/CPU/display/battery, same as people above I am 2 months of out warranty and they said I need to purchase a new mainboard and then I found this post ---
**Author:** ![Mateusz\_Kijowski](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Mateusz\_Kijowski](https://community.frame.work/u/Mateusz_Kijowski)\ **Post date:** [October 12, 2026, 11:21am UTC](https://community.frame.work/t/bios-update-stuck/83416/50 "2026-10-12T11:21:26Z")
This thread [Upgrading to BIOS 3.20 on Ryzen 7040 series may brick your machine - #57 by Igiveup](https://community.frame.work/t/upgrading-to-bios-3-20-on-ryzen-7040-series-may-brick-your-machine/84031/57) suggests that you can get a free replacement. Maybe support needs some pushing to offer you a replacement ? ---
**Author:** ![DataBase](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/database/32/48360_2.png) [@DataBase](https://community.frame.work/u/DataBase)\ **Post date:** [October 12, 2026, 2:26pm UTC](https://community.frame.work/t/bios-update-stuck/83416/51 "2026-10-12T14:26:05Z")
I don’t know for sure, but I suspect the problem is actually something in the older BIOSs. It certainly looks like nothing in your BIOS gets updated until the first time you reboot after you run the update file, which means it’s still the old BIOS running while the flashing happens. Weirdly my own 7040 series FW13 has been updated to every single BIOS version, starting from 3.03 with zero issues. I am careful though, for instance I disconnect everything except the charger before upgrading. ---
**Author:** ![Andrew\_Moise](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Andrew\_Moise](https://community.frame.work/u/Andrew_Moise)\ **Post date:** [October 12, 2026, 6:05pm UTC](https://community.frame.work/t/bios-update-stuck/83416/52 "2026-10-12T18:05:26Z")
Just a heads up - the clock, on their liability about a BIOS update they provided to you, starts when you get the BIOS update and not when you purchased the machine. Check your local laws obviously, but if they ship you an update that you applied in the recommended standard manner and then it ruins your machine, then most jurisdictions consider them responsible, whenever or however the machine was purchased. “Warranty” on the original machine against failures not caused by some external factor is just totally irrelevant. ---
**Author:** ![pkunk](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@pkunk](https://community.frame.work/u/pkunk)\ **Post date:** [October 12, 2026, 8:03pm UTC](https://community.frame.work/t/bios-update-stuck/83416/53 "2026-10-12T20:03:20Z")
It may be recoverable with a low level BIOS flash (directly to the flash chip), but it takes the tools and patience to accomplish this. Maybe see if a local repair shop has a programmer and is willing to quote a price to recover the existing image (want to have this for the serial info it contains) Then flash a new image in its place. Some people have done it themselves successfully. [Previous page](https://community.frame.work/t/bios-update-stuck/83416.md?page=2)