# Success in recovering from bad BIOS upgrade - Framework 13 AMD 7040

**URL:** <https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598>\
**Category:** Community Support\
**Tags:** not-booting, amd-7040\
**Created:** [March 24, 2025, 8:52pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598 "2025-03-24T20:52:46Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![Richard6](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@Richard6](https://community.frame.work/u/Richard6)\
**Post date:** [July 31, 2026, 12:09am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/64 "2026-07-31T00:09:13Z")

</div>

I’ve ordered the [CH341A kit](https://www.amazon.com/dp/B07VNVVXW6). It comes with a clip rather than a vertical pogo pin I see in all of the above pictures. Does the clip have connectivity issues and is it compatible with the Framework 13’s chip? Should I purchase the pogo pins as well?

Update: I’ve been told by AI that the SOIC8 clip above does not work on WSON8 chips, so I need to separately purchase a WSON8 8\*6 mm pogo pin probe.

---

<div class="post-metadata">

**Author:** ![DHowett](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dhowett/32/1990_2.png) [@DHowett](https://community.frame.work/u/DHowett)\
**Post date:** [July 31, 2026, 3:37pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/65 "2026-07-31T15:37:03Z")

</div>

You will need a WSON8 probe, the SOIC8 clip will not fit over the geometry of the chip or make contact with the pins.

---

<div class="post-metadata">

**Author:** ![Adrian\_Joachim](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/adrian_joachim/32/9949_2.png) [@Adrian\_Joachim](https://community.frame.work/u/Adrian_Joachim)\
**Post date:** [July 31, 2026, 8:29pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/66 "2026-07-31T20:29:32Z")

</div>

> [@Richard6](#):
>
> It comes with a clip rather than a vertical pogo pin

Apart from it probably not fitting be really careful with clips, it is extremely easy to knock off tiny components near the flash with it, don’t ask me how I know XD.

---

<div class="post-metadata">

**Author:** ![Scale\_Hardwarebox\_De](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/scale_hardwarebox_de/32/17007_2.png) [@Scale\_Hardwarebox\_De](https://community.frame.work/u/Scale_Hardwarebox_De)\
**Post date:** [August 1, 2026, 9:33pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/67 "2026-08-01T21:33:58Z")

</div>

Has anyone managed to read the BIOS of a Framework 16 yet?  
I’ve been trying to do this but simply haven’t succeeded so far. I started by trying a CH341A programmer. Whenever I attach it to the chip, the power supply drops (the power LED dims, and the chip isn’t detected).  
Hoping for better results, I then got an RT809F programmer, as the software is supposed to be better. Unfortunately, there was no improvement with that device either.  
I’m at a loss—can anyone here help?  
I’ve used both programmers with and without a 1.8V adapter, but the chip still isn’t detected.  
The motherboard is completely unpowered—no battery, no external power supply connected. It just isn’t working.

---

<div class="post-metadata">

**Author:** ![widely\_crumpled](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@widely\_crumpled](https://community.frame.work/u/widely_crumpled)\
**Post date:** [August 4, 2026, 5:32pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/68 "2026-08-04T17:32:06Z")

</div>

Hi @Scale_Hardwarebox_De,

I tried letting you know in my reply [here](https://community.frame.work/t/need-help-with-bios-dump/83414/2) that the issue you are facing is mostly likely an issue with the power supply to your flash chip, not the programmer.

Have you tried programming the flash chip with the mainboard powered? If you do try, make sure to not connect the VCC pin (pin 8) from your programmer/power supply to the chip.

From the datasheets I could find, the flash chips for the Framework 12 and 16 are basically identical other than the voltage (the Framework 12 uses 3.3V instead of 1.8V). Datasheet for [W25R256JVxx](https://www.winbond.com/resource-files/W25R256JV%20RevD%2006162020.pdf) (Framework 12) & datasheet for [W25R256JWxx](https://www.winbond.com/resource-files/W25R256JW%20RevB2%2009072018.pdf) (Framework 13 & 16)

---

<div class="post-metadata">

**Author:** ![DHowett](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dhowett/32/1990_2.png) [@DHowett](https://community.frame.work/u/DHowett)\
**Post date:** [August 4, 2026, 7:06pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/69 "2026-08-04T19:06:27Z")

</div>

> [@Scale\_Hardwarebox\_De](#):
>
> Whenever I attach it to the chip, the power supply drops (the power LED dims, and the chip isn’t detected).

I have found with _some_ Framework devices that, if the power supply from the flasher is enabled when you push the pogo jig on, it will short out.

Bus Pirate reports this and disables VOUT. Other flashers might just give up.

Try to push down the pogo jig and making sure it is secure _before_ connecting the flasher to USB.

---

<div class="post-metadata">

**Author:** ![Richard6](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@Richard6](https://community.frame.work/u/Richard6)\
**Post date:** [August 6, 2026, 6:38am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/70 "2026-08-06T06:38:22Z")

</div>

![bios](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/a/5/a596fc748c6b64a8a1d9e74b59cb9c142f46c09c.jpeg)

Add me to the list 😎

[This video](https://www.youtube.com/watch?v=mSLKlLcOAKM) was especially concise and helpful. Thanks everyone for saving me hundreds of dollars!

---

<div class="post-metadata">

**Author:** ![David\_Henry](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@David\_Henry](https://community.frame.work/u/David_Henry)\
**Post date:** [August 6, 2026, 7:25am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/71 "2026-08-06T07:25:40Z")

</div>

Did it work for the first write or did you have to do several attempts (like in my case, 3) before writing was successful?

---

<div class="post-metadata">

**Author:** ![Quantum](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/quantum/32/49861_2.png) [@Quantum](https://community.frame.work/u/Quantum)\
**Post date:** [August 6, 2026, 7:44am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/72 "2026-08-06T07:44:00Z")

</div>

Well, it seems like I just found myself in the same boat doing the 3.20 update today. It’s a wonder that the update still hasn’t been pulled from LVFS when it’s been bricking so many people’s boards…

I am still waiting for a response from Framework support, but I am preparing for the worst given that my laptop is a bit old. Unfortunately, I am mostly a software person and my forays into hardware stuff are limited, and I’ve never tried flashing a chip like this before… Hence, I am doing some research in preparation and have some questions.

> [@David\_Henry](#):
>
> I followed your steps (bought the same stuff for ~32€, used the same tricks with ceramic coasters - first time I used them in ten years 😅, same commands) and it worked!

What did you actually buy? From comparing your pictures to AliExpress listings and YouTube videos, it looks like a black CH341A programmer with a 1.8 V level shifter and a WSON8 6×8 mm pogo pin thing?

From what I’ve read online about that specific black model, and from this message earlier:

> [@jim\_m](#):
>
> If you are going to use the cheap CH341 programmers, you should first connect a DMM or scope and verify that with the voltage divider board, it is actually programming at 1.8V (or what ever voltage it should be). These had a design flaw and the main board would not program at 3.3V (1.8V with the divider), so you were not only programming at an out of spec voltage, but also back feeding other components with a higher than rated voltage. There is a fix for it, and some of them had the fix, but most do not (search for CH341 voltage fix).

There are some concerns with the programmer not outputting the correct voltage? Has anyone run into any issues with the voltage? Did you all do the voltage fix or something?

I’ve seen newer versions of the CH341A with different colours that don’t seem to have the voltage issue, but they all seem to be sold out on AliExpress… I hope it’s not because of everyone running into the same issue.

> [@Richard6](#):
>
> Add me to the list 😎

Did you use the pogo pins or was that the clamp? It’s not super clear from your picture. I would rather not have to manually hold down the pogo pins if possible.

Also, has anyone tried the CH347 instead of CH341A? It’s supposed to be much faster at programming these chips due to supporting higher SPI clocks and also doesn’t cost a fortune (unlike some of the fancier programmers…), and it might really help here if I end up having to hold pogo pins down.

---

<div class="post-metadata">

**Author:** ![Richard6](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@Richard6](https://community.frame.work/u/Richard6)\
**Post date:** [August 6, 2026, 7:58am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/73 "2026-08-06T07:58:51Z")

</div>

It wrote successfully the first time, but I had more trouble getting it to detect the chip. In the end the problem was fixed by applying more pressure.

---

<div class="post-metadata">

**Author:** ![David\_Henry](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@David\_Henry](https://community.frame.work/u/David_Henry)\
**Post date:** [August 6, 2026, 7:59am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/74 "2026-08-06T07:59:10Z")

</div>

> [@Quantum](#):
>
> > [@David\_Henry](#):
> >
> > I followed your steps (bought the same stuff for ~32€, used the same tricks with ceramic coasters - first time I used them in ten years 😅, same commands) and it worked!
> 
> What did you actually buy? From comparing your pictures to AliExpress listings and YouTube videos, it looks like a black CH341A programmer with a 1.8 V level shifter and a WSON8 6×8 mm pogo pin thing?

Yes, exactly :

- The CH341A : [https://www.amazon.fr/dp/B0CMXP8V7Z](https://www.amazon.fr/dp/B0CMXP8V7Z)
- The WSON8 probe : [https://www.amazon.fr/dp/B0F4XH8NXL](https://www.amazon.fr/dp/B0F4XH8NXL)

I just followed previous poster’s choices for the hardware to buy.

> [@Quantum](#):
>
> There are some concerns with the programmer not outputting the correct voltage? Has anyone run into any issues with the voltage? Did you all do the voltage fix or something?

I didn’t do anything about the voltage. Just added the 3.3V → 1.8V converter sold with the CH341A programmer pack.

---

<div class="post-metadata">

**Author:** ![Richard6](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@Richard6](https://community.frame.work/u/Richard6)\
**Post date:** [August 6, 2026, 8:00am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/75 "2026-08-06T08:00:32Z")

</div>

I separately bought a WSON8 8x6mm clip. I wrote about my setup in more details [on reddit](https://www.reddit.com/r/framework/comments/1vgx4mw/flashing_my_bios_chip/). I think [this guy](https://www.youtube.com/watch?v=kB7scNyY8Ck) shows a few alternative hardware to the CH341A. I never verified the voltage and just trusted that the items would work.

---

<div class="post-metadata">

**Author:** ![Quantum](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/quantum/32/49861_2.png) [@Quantum](https://community.frame.work/u/Quantum)\
**Post date:** [August 6, 2026, 8:17am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/76 "2026-08-06T08:17:41Z")

</div>

Thanks for the quick reply, guys.

> [@Richard6](#):
>
> I think this guy shows a few alternative hardware to the CH341A. I never verified the voltage and just trusted that the items would work.

Yeah, I watched the video, which is how I found out about the CH347. The documentation on this model is very lacking. I see two different versions on AliExpress, none of which inspires confidence:

- [https://www.aliexpress.com/item/1005005615745631.html](https://www.aliexpress.com/item/1005005615745631.html), which says literally nothing about voltage, except it appears to “work” for people.
- [https://www.aliexpress.com/item/1005010508477025.html](https://www.aliexpress.com/item/1005010508477025.html), which is 1.8 V, but from the reviews, it seems like the voltage is switchable in software and it might get it wrong?

The alternatives in that video are all kinda crazy expensive. Like, the XG Pro T76 is $150 USD as linked in the description, and I think that wipes out a large chunk of the savings from trying to repair this motherboard.

But I guess I might as well try with the black CH341A if no one seems to be having trouble with it. If any of you have an oscilloscope or a multimeter, it would be nice to lay the whole voltage issue to rest for posterity. Otherwise, I guess I might just do some multimeter testing when my parts arrive.

Also, how did you end up holding down the pogo pins while flashing?

---

<div class="post-metadata">

**Author:** ![Richard6](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@Richard6](https://community.frame.work/u/Richard6)\
**Post date:** [August 6, 2026, 4:20pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/77 "2026-08-06T16:20:46Z")

</div>

Held it down with my father’s steady hands. It only took around 5 minutes to flash in my case, so it wasn’t too bad. Others had more creative setups.

---

<div class="post-metadata">

**Author:** ![Quantum](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/quantum/32/49861_2.png) [@Quantum](https://community.frame.work/u/Quantum)\
**Post date:** [August 7, 2026, 3:12am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/78 "2026-08-07T03:12:32Z")

</div>

> [@David\_Henry](#):
>
> - Extraction command:

I’ve independently extracted the 3.20 BIOS, both with `tail | head` and with InsydeH2O extractor and got the same hash. For anyone else who might need it: [https://dl.quantum2.xyz/firmware/framework-3.20-bios.bin](https://dl.quantum2.xyz/firmware/framework-3.20-bios.bin)

The hashes:

- MD5: `8bc4cde1b7e8413b9b405b8e7b243e1f`
- SHA1: `b562976496f3bafba5e07f2d96b03804a708f90d`
- SHA256: `a645413ee19c7cf287917a717099883ea37ed6b556c74cf31adbc5b1afcc9c05`

@David_Henry can you confirm it’s the same file you successfully flashed?

I also forked InsydeH2O extractor and fixed the compilation issues on Linux, if anyone needs it in the future for other BIOS versions: [GitHub - quantum5/InsydeH2O-extractor-2: InsydeH2O firmware extractor (compilable on Linux) · GitHub](https://github.com/quantum5/InsydeH2O-extractor-2)

The command to run is:

```auto
git clone https://github.com/quantum5/InsydeH2O-extractor-2.git
cd InsydeH2O-extractor-2
cmake .
make
./extractor /path/to/bios.cap

```

`BIOSFILE.FD` in the directory would be the one to flash.

---

<div class="post-metadata">

**Author:** ![widely\_crumpled](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@widely\_crumpled](https://community.frame.work/u/widely_crumpled)\
**Post date:** [August 7, 2026, 3:48am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/79 "2026-08-07T03:48:22Z")

</div>

Thank you for the advice. I obviously cannot speak for @Scale_Hardwarebox_De, but for me, with my Framework 12, the led of my ch341a dims regardless of whether the pogo jig is connected before or after plugging it into usb. I guess this probably isn’t the right place to talk about it though - this post is labeled for the Framework 13 AMD 7040 mainboard.

---

<div class="post-metadata">

**Author:** ![David\_Henry](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@David\_Henry](https://community.frame.work/u/David_Henry)\
**Post date:** [August 7, 2026, 3:02pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/80 "2026-08-07T15:02:25Z")

</div>

> [@Quantum](#):
>
> The hashes:
> 
> - MD5: `8bc4cde1b7e8413b9b405b8e7b243e1f`
> - SHA1: `b562976496f3bafba5e07f2d96b03804a708f90d`
> - SHA256: `a645413ee19c7cf287917a717099883ea37ed6b556c74cf31adbc5b1afcc9c05`
> 
> @David_Henry can you confirm it’s the same file you successfully flashed?

Yes, I get the same hashes.

---

<div class="post-metadata">

**Author:** ![Quantum](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/quantum/32/49861_2.png) [@Quantum](https://community.frame.work/u/Quantum)\
**Post date:** [August 17, 2026, 6:19am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/81 "2026-08-17T06:19:12Z")

</div>

> [@Quantum](#):
>
> Also, has anyone tried the CH347 instead of CH341A? It’s supposed to be much faster at programming these chips due to supporting higher SPI clocks and also doesn’t cost a fortune (unlike some of the fancier programmers…), and it might really help here if I end up having to hold pogo pins down.

Answering my own question here: I bought a CH347 programmer for $5 on AliExpress and found that it works and the flash took less than a minute. It was enough to just hold down the pogo pins in one hand while I did that.

I also bought a black CH341A programmer to check with my multimeter, and it has the voltage bug. If anyone still needs to fix their laptop, I’d strongly recommend getting the CH347 instead.

I also did an in-depth explanation on my blog: [Fixing a bricked AMD 7040 series Framework 13” laptop with $20 tools | Quantum](https://qt.ax/ffw)

---

<div class="post-metadata">

**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:** [August 18, 2026, 11:09pm UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/82 "2026-08-18T23:09:44Z")

</div>

> [@Quantum](#):
>
> has anyone tried the CH347 instead of CH341A? It’s supposed to be much faster at programming these chips due to supporting higher SPI clocks and…  
> Answering my own question here: I bought a CH347 programmer for $5 on AliExpress and found that it works and the flash took less than a minute…

It’s good to know it works.  
However, do note that higher clocks are not necessarily going to be a good thing when the connection to the chip is still via an unscreened unbalanced ribbon cable and the chip is still being programmed while connected to its original circuit.

---

<div class="post-metadata">

**Author:** ![Quantum](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/quantum/32/49861_2.png) [@Quantum](https://community.frame.work/u/Quantum)\
**Post date:** [August 19, 2026, 1:34am UTC](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/83 "2026-08-19T01:34:08Z")

</div>

> [@DataBase](#):
>
> However, do note that higher clocks are not necessarily going to be a good thing when the connection to the chip is still via an unscreened unbalanced ribbon cable and the chip is still being programmed while connected to its original circuit.

Yes, I agree that higher clocks isn’t always better, and my fallback option was always to lower the clock if the data rates ended up being too fast. That didn’t turn out to be necessary and I saved a lot of time and effort holding down the pogo pins, and hopefully that will save others some headache.

Still, if you can get the faster programmer, you should, because you can always slow it down, while you can’t make the slower programmer faster.

[Previous page](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598.md?page=3)
