Bricked my new AMD 7040 with the wrong BIOS update

Following the Windows installation I tried to update the BIOS as it was recommended on the framework documents. Unfortunately I was in a hurry and did a very bad job: Downloaded und updated BIOS for Framework 16, which I wasn’t prevented from. :grimacing:

Now the Laptop ends up in a screen saying I have to check Expansion Bay Connection - which only would be available on Framework 16, as far as I know (see screenshot below).

Pushing the Power-Button again the Laptop starts to Windows, but neither mouse nor touchpad are functional anymore. I tried USB keyboard and mouse, which fails too.

With that it seems to me I have no chance to update to the correct BIOS.

Does anybody have any idea, how I can unbrick the Laptop?

Thanks in advance

I do updates using a USB stick following the “EFI method” listed at the bottom of the Firmware Updates page. I think you may be able to find a USB port that can still run this script and re-flash the firmware to the AMD 13” edition.

Good luck.

K3n.

1 Like

Hi,

I did not know it was possible to do it that way.
It is mainly only other users here.
Raise a support ticket via the web site to get FW support.
Maybe there is a bios unbrick method they have not told us about, but I think you will get a replacement mainboard.

1 Like

Wow. Have you contacted support yet? knowledgebase.frame.work/contact/contact-us-rJfw7Ryglx

Just to check, you preformed the update from windows, following Framework’s guide, correct? Other than downloading the FWL16 update by mistake.

1 Like

Downloaded and performed BIOS update via Windows. Haven’t contacted support until now. Thought that maybe some experiences already exist in community.

Update:

  • I resetted the mainboards CMOS as described here: Fully Resetting the Mainboard State - Framework Guides
  • tried to connect USB Stick on various USB Ports of FWL. No success
  • tried to get back contact to the the keyboard and touchpad. No success.
  • Tried to use USB mouse and keyboard on different USB ports of the FWL. No success
  • Connected Lenovo Docking Station with FWL and mouse and keyboard on Docking Station. Success. get back mouse and keyboard control :slight_smile:
  • Connect USB stick with Windows BIOS-Update via Docking Station. Success
  • Starting BIOS Update via Windows. Failed. USB C Port modules seemed to have lost charging capabilities and BOIS Update can only performed if Laptop is on AC. :sad_but_relieved_face:

As others have said, you’d be better off trying to update using the EFI packages rather than any OS-Specific ones.

Thank you all for your fast answers. I don’t bother with updating the EFI packages if this fits better. My recent opinion is, that this wouldn’t work because it requires also an USB-C module feasible for AC charging. As far as I understood BIOS update in each version checks for AC on at USB-C¹. Incorrect BIOS seems to have disabled the formerly working settings for the USB-modules.

¹Please correct me if I’m wrong there

It’s disappointing that they haven’t included a check that you are updating with a BIOS that matches your machine! I hope that doesn’t mean there are no integrity checks either?

Do you recall if it was the Driver Bundle or the BIOS Update package?

Windows 11 Linux Other
Driver Bundle Download Driver Bundle (v2.06) 2025-09-08 Included in kernel
BIOS Update Download BIOS 3.07 Update to BIOS 3.07 using LVFS Download BIOS 3.07 (EFI Shell update)

knowledgebase.frame.work/en_us/framework-laptop-16-bios-and-driver-releases-amd-ryzen-7040-series-BkeqkVovp

You will only know if you try it. The requirement for power being connected might just be a recommendation to minimize the chance of an interrupted BIOS update.

Worst case scenario, if you’re feeling particularly brave, you could try flashing the chip directly like this absolute baller Success in recovering from bad BIOS upgrade - Framework 13 AMD 7040

(But definitely exhaust all other options first (including contacting support))

Make sure you have enough charge in your battery (north of 50% ideally) before you try the following:

  • Use 7zip to unpack the BIOS update EXE.
  • Open the platform.ini file with a text editor (e.g. notepad)
  • Find the [AC_Adapter] section, set the flag from 1 to 0 (or 2 or 4).
  • Save the file.
  • Then run the H2OFFT-Wx64.exe file to continue.

1 Like

One more thing: If the battery charge is low…you ‘might’ still still able to charge the laptop with a USB-A to USB-C cable. It would charge the laptop slowly at around 5w. (Yes, I’m aware that the usual USB-PD charging is not working for you)

1 Like

The part that controls charging is the PD firmware and the EC firmware.
You can upgrade just those bits back to FW13 versions. That would get the usb charging working. Then, do a normal firmware upgrade of the bios, back to FW13 bios.
It all depends how much battery you have left.
What does FW support say?

Thank you for all or your answers and support.

  • @MJ1 I’ve first done the bundle update and second the BIOS update.
  • @Second_Coming Thank you for your suggestion. I will try this, as the battery is around 80% charged :+1:
  • @Brian_Gregory This is the next option for me :slight_smile:

First of all I will wait some more time for the supports response

1 Like

Is this also a case of FW not accepting contributions from the community.
For example, the tool we use to install custom EC firmware specifically checks that you are using the correct firmware type before installing it.
Why FWs own tools don’t do the same is beyond me.
This is not a digital signature. It is a simple check that one only installs lotus firmware if the currently existing firmware reports it’s name as lotus.

1 Like

All of the other firmware installers Framework has distributed do check the model number. This is absolutely an anomaly.

2 Likes

Trying at first solution from @Second_Coming , the Laptop reboots, then get stuck with the Message “Update failed; EFI Error 21; firmware update failed!!!”And additionally “Please make sure system has adapter”

Afterwards trying EFI packages returns “CapsuleApp: failed to query capsule capability - Unsupported”

:grimacing:

1 Like

@Andres_Quast
I have just thought through your problem and how to recover it.
In short, you are completely stuck without a specially built recovery bios from FW.
So, don’t waste your battery, and just wait for FW support to sort you out.
None of the bios files you can download will fix your problem.

Expanding on the above:

  1. there are various things to try, but they would all waste battery power, so the priority would be getting usb charging working again.
  2. the charging is controlled by the EC and PD firmware. Not the BIOS We could force an update to a FW13 EC, but i don’t know how to force a PD update to match.
  3. The BIOS update program probably thinks you now have a FW16, so switching to a FW13 BIOS probably will not work, without a special bios that bypasses all those safety barriers. This bug allowing you to flash a FW16 bios to a FW13 is probably not the same bug to flash a FW16 to a FW13, so it will stop you doing that.
  4. because of the above, I think only FW support can help you with a recovery BIOS, but my guess is they will have to send you a replacement mainboard.