# Bios: external flashing

**URL:** <https://community.frame.work/t/bios-external-flashing/52269>\
**Category:** Framework Laptop 13\
**Created:** [June 4, 2024, 8:34pm UTC](https://community.frame.work/t/bios-external-flashing/52269 "2024-06-04T20:34:39Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![monopole](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@monopole](https://community.frame.work/u/monopole)\
**Post date:** [June 4, 2024, 8:34pm UTC](https://community.frame.work/t/bios-external-flashing/52269/1 "2024-06-04T20:34:39Z")

</div>

i typically disable intel ME in the bios by using an external flashing config, but the bios chip on this 13th gen mainboard (i7-1360P cpu) is notably different from the 8 lead bios chips i usually connect to. the chip is wider and flatter, and its leads are not readily accessible like most other older bios chips i’ve worked with.

i typically use a soic-8 clip and a ch341a bios programmer to read and write bios chips. i do see a chip that looks like a bios chip, a winbond W25R256JVEN, between the cpu and the memory, under the lower right plastic covering.

input is appreciated, thanks!

---

<div class="post-metadata">

**Author:** ![MJ1](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mj1/32/15519_2.png) [@MJ1](https://community.frame.work/u/MJ1)\
**Post date:** [June 4, 2024, 8:44pm UTC](https://community.frame.work/t/bios-external-flashing/52269/2 "2024-06-04T20:44:31Z")

</div>

You’ll need a pogo pin adapter. It’s not a soic-8.

> [@How to prepare for reflashing firmware](http://community.frame.work/t/how-to-prepare-for-reflashing-firmware/31001/):
>
> I’m rebuilding my firmware to try to fix a keyboard issue I’ve been having. I followed [DHowett’s guide for building](https://www.howett.net/posts/2022-04-adding-an-ec-feature-1/). I’m using Windows Subsystem for Linux. It seems to have built a correctly-sized binary. I followed the warning to use GCC 10. I’ve got ectool booting properly and showing version as well, but I chickened out before reflashing because I really don’t want to brick my laptop. Before doing the reflash, what tools should I get or other preparation can I do to ensure I’ll be able to re…

---

<div class="post-metadata">

**Author:** ![monopole](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@monopole](https://community.frame.work/u/monopole)\
**Post date:** [June 4, 2024, 9:12pm UTC](https://community.frame.work/t/bios-external-flashing/52269/4 "2024-06-04T21:12:04Z")

</div>

hah, i had just found some videos about these adapters for the wson package bios chips.

thanks for confirming this is the correct route.

---

<div class="post-metadata">

**Author:** ![monopole](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@monopole](https://community.frame.work/u/monopole)\
**Post date:** [June 7, 2024, 8:53pm UTC](https://community.frame.work/t/bios-external-flashing/52269/5 "2024-06-07T20:53:34Z")

</div>

ok, i have confirmed that with a wson-8 to dip-8 pogo adapter it is possible to read the bios from the chip that i suspected is the bios. note that using such a pogo adapter is error prone and requires holding the adapter seated with just the right force for 3-4 minutes.

the intel ME version i’m seeing from the bios image is 16.1.25.2124.

---

<div class="post-metadata">

**Author:** ![blur](https://avatars.discourse-cdn.com/v4/letter/b/dbc845/32.png) [@blur](https://community.frame.work/u/blur)\
**Post date:** [October 31, 2025, 1:11am UTC](https://community.frame.work/t/bios-external-flashing/52269/6 "2025-10-31T01:11:09Z")

</div>

Did you successfully disable intel ME? I know it has been over a year… Thought it was worth a shot if for nothing else than to revive community discussion around this topic.

I see mixed signals surrounding the topic on this pull request for me\_cleaner:

> <https://github.com/corna/me_cleaner/pull/384>
>
> I haven't tested with others Intel ME for the 15 version, but I guess that shoul…d work, as the PCI device (Intel ME) is not present anymore and seems to act like it's disabled, but I'll need to do more tests with AMT to be sure.
> 
> If someone is looking at this pull request and is willing to test the soft-disable, since Intel ME 15 might have different HAP bit offsets between chipsets etc, although I'm not really sure about that, I don't have any other computers to test with.
> 
> Thanks to @dt-zero and @6d6178667269747a for previous versions of Intel ME.
> 
> If that doesn't work, try this guess:
> https://github.com/corna/me\_cleaner/pull/384#issuecomment-1220260578

---

<div class="post-metadata">

**Author:** ![FedX](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@FedX](https://community.frame.work/u/FedX)\
**Post date:** [August 31, 2026, 4:14pm UTC](https://community.frame.work/t/bios-external-flashing/52269/7 "2026-08-31T16:14:43Z")

</div>

Yeah, also curious how this ended up, but mostly as a backup.

~~It looks perfectly possible to do internal flashing on Framework Devices using the Coreboot instructions on ME\_Cleaner and the `framework_tool --dump-ec-flash` and `--flash-ec` commands.~~

 

~~However, it seems the Framework Laptops (or more accurately the Chromewbook firmware they are based on) don’t use a standard ifd binary, but I can’t figure out what format or how to convert it. Probably reasonable to track down the bit manually and re-flash it, but for that I would _really_ like a backup external flasher.~~

EDIT: that’s wrong.

---

<div class="post-metadata">

**Author:** ![GhostLegion](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ghostlegion/32/3356_2.png) [@GhostLegion](https://community.frame.work/u/GhostLegion)\
**Post date:** [August 31, 2026, 9:21pm UTC](https://community.frame.work/t/bios-external-flashing/52269/8 "2026-08-31T21:21:36Z")

</div>

They don’t use Chromebook firmware other than the Chromebook FW laptop that got produced. If you’re referring to the EC, it has nothing to do with the Intel ME.

---

<div class="post-metadata">

**Author:** ![FedX](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@FedX](https://community.frame.work/u/FedX)\
**Post date:** [August 31, 2026, 10:24pm UTC](https://community.frame.work/t/bios-external-flashing/52269/9 "2026-08-31T22:24:55Z")

</div>

Well, yes, [I was referring to the EC firmware](https://github.com/FrameworkComputer/EmbeddedController/). Clearly I did not understand the difference between the EC and BIOS firmwares…my bad.

---

<div class="post-metadata">

**Author:** ![GhostLegion](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ghostlegion/32/3356_2.png) [@GhostLegion](https://community.frame.work/u/GhostLegion)\
**Post date:** [September 1, 2026, 4:10am UTC](https://community.frame.work/t/bios-external-flashing/52269/10 "2026-09-01T04:10:56Z")

</div>

It’s all good. Sorry if I came across harshly.
