September 2025 - flashrom - mail.coreboot.org

HP 11MK G9EE - M44236-001 - "W25Q64JW...M"
by Tim Tech Oct. 20, 2025

Oct. 20, 2025

Hello, attached are two text documents: output from --wp-disable and output from erase/write - let me know if any other information is needed. Chip in question is "W25Q64JW...M" Thanks, Tim

2 5

Flashrom reads fail with Dediprog due to I/O pins
by Vincent Fazio Oct. 3, 2025

Oct. 3, 2025

We recently ran into an issue reading data from some chips via Dediprog (https://ticket.coreboot.org/issues/609) It appears to be related to maybe not taking some I/O pins into account: https://github.com/flashrom/flashrom/blob/05976c7e93ea64031f6bb3b1eee812023… We have a diff in the ticket that worked for us on our specific combination of dediprog + firmware + flashchips but were hesitant to submit a patch since the sample size was so low. Does anyone else use a Dediprog to program flash and has capacity to try the changes and see if things break or if their use cases start working where they failed before? Vincent Fazio Automated Test Software, Technical Lead Extreme Engineering Solutions, Inc. https://www.xes-inc.com

2 1

Ver1.6 -p internal not available
by Victor Camacho Sept. 29, 2025

Sept. 29, 2025

Hi, First, thank to developers for all their hard work. Short background, I have a few PC Engines computer 2x apu2 and 2 x apu4 Working on updating all to recommended v4.17. TinyCore on old PC engines did not work for me. Install Debian 13, apt install flashrom which installed flashrom 1.4. I was able to update the 2 apu2 devices. Install Debian 13 on apu4. Install flashrom and received error about failed to read fmap. Research implied using updated flashrom 1.6. Build and install flashrom 1.6 (your instructions are simple and spot on, thank you) Used command that I used on apu2 flashrom -p internal -w apu4_v4.17.0.3.rom -c W25Q64JV-.Q --fmap -i COREBOOT ==== /usr/local/sbin/flashrom -p internal -w apu4_v4.17.0.3.rom -c W25Q64JV-.Q --fmap -i COREBOOT flashrom v1.6.0 on Linux 6.12.43+deb13-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Error: Unknown programmer "internal". Valid choices are: dummy, serprog, buspirate_spi, rayer_spi, pony_spi, linux_mtd, linux_spi, spidriver. Please run "flashrom --help" for usage info. === I could not figure out what programmer to use. Any advice would be appreciated, Victor

2 5

The motherboard of the 1355U (Raptor Lake) processor failed to successfully update the BIOS through flashrom.
by ⁣⁣⁣⁣ SongRz Sept. 29, 2025

Sept. 29, 2025

Hello, our industrial control computer uses the 1355U processor. Since the computer is at the customer's site, we can only flash the BIOS through flashrom. We downloaded the source code via git and compiled version 1.7, as well as the 1.6 version downloaded from flashrom.org for testing. We used the command sudo ./flashrom -p internal -w abc.bin to flash the BIOS. The following error occurred: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- gy@debian:~/GWADL_Flashpkg250927_linux$ sudo ./flashrom1_7 -p internal -w ADL2H003T-Z15-STATE-GW-6COM-1525.ROM [sudo] password for gy: flashrom v1.7.0-devel (git:v1.6.0-20-g4b370beb) on Linux 6.1.0-0.deb11.39-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org No DMI table found. Found chipset "Intel Alder Lake-P". Enabling flash write... SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. FREG1: BIOS region (0x00500000-0x00ffffff) is read-write. FREG2: Management Engine region (0x00001000-0x004c0fff) is read-write. Enabling hardware sequencing because some important opcode is locked. OK. Found Winbond flash chip "W25Q128.V" (16384 kB, Programmer-specific) on internal. Reading old flash chip contents... done. Updating flash chip contents... Erase/write done from 0 to ffffff Verifying flash... FAILED at 0x0050008f! Expected=0xf8, Found=0xf0, failed byte count from 0x00000000-0x00ffffff: 0x1 Your flash chip is in an unknown state. Get help on chat (see https://flashrom.org/contact.html) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"!------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- If we ignore the prompt and force a restart, the motherboard may fail to boot after multiple restarts. We need to use a burner to reflash the BIOS to be able to boot, which means there is something wrong with my operation. I also tried to use the same command to flash the corresponding BIOS file on the motherboard with the 10710U processor, as well as on the 1165G7 motherboard. They were all fully flashed. Please help me look into this and tell me what the problem is. Thank you.

2 1

Unable to Write/Erase BIOS on ThinkPad T530/W530 with flashrom
by Danylo Holovka Sept. 28, 2025

Sept. 28, 2025

Hello flashrom developers, I am unable to write or erase the BIOS on my ThinkPad T530 with a W530 motherboard (essentially a W530 in a T530 chassis) using flashrom. Setup: Laptop: ThinkPad T530 (W530 motherboard) GPU: Nvidia Quadro K1000M (discrete only, Nvidia-only mode) iGPU: Intel HD Graphics present but not in use OS: Linux (EndeavourOS, Wayland) Flashrom version: 1.6.0 BIOS: Coreboot with TianoCore (EDK2) payload Flash chips: Verified original chips Problem: flashrom fails to write or erase the BIOS chips on both this system and a stock T530 board. Isolating the WP pin with Kapton tape had no effect. WP pin appears held low by motherboard circuitry. Errors reported by flashrom: ERASE FAILED! Erase/write done from 0 to 7fffff Write failed! Uh oh. Erase/write failed. Checking if anything has changed. Questions: 1. Could the Coreboot + TianoCore image or motherboard configuration prevent flashrom from writing even when the correct chip is selected? 2. Are there supported methods to bypass WP pin constraints on this hardware? 3. Any recommended workarounds for this scenario? I can provide logs or further hardware details if needed. Your guidance would be greatly appreciated. Thank you, Danylo Holovka

1 0

Re: Chipset is in an unknown state error
by Spencer Strait Sept. 26, 2025

Sept. 26, 2025

I am sorry, I did not send the device information. The device is a Lenovo 300e Yoga Chromebook Gen 4, and the motherboard part number is 5B21L33482. I am not sure if you also required the device's serial number. Thank you. ________________________________ From: Spencer Strait Sent: Thursday, September 11, 2025 8:24 AM To: flashrom(a)flashrom.org <flashrom(a)flashrom.org> Subject: Chipset is in an unknown state error Good morning, I work for a contracted Lenovo Repair service, and I am attempting to program a new chromebook motherboard with a specific serial number, and I am getting a constant erase and read/write error, as well as an error message stating that chipset is in an unknown state. I have the battery unplugged and all the screws removed, and I continue to get the same error. This is the second motherboard that has had the same error, and I have already sent the first replacement motherboard back to Lenovo back, believing that the problem was caused by a hardware failure. I cannot continue the repair for this device until I move past this chipset error. I can send you a picture of the error and just the error, if that will help. Thank you, and I await your reply, Spencer S

2 1

adding a chip
by Special Needs Sept. 26, 2025

Sept. 26, 2025

I have been running in to this flash ROM allot recently :FM25W128 I was wondering if you could add it to flashrom. My current MB bios has Intel ME, and I am concerned with how secure the server will be that I'm building.

2 1

Kernel Driver for Internal SPI Access on Windows
by madam smith Sept. 10, 2025

Sept. 10, 2025

Hi Flashrom team, I'm a forensic engineer focused on hardware-level validation and SPI flash access across locked platforms. I've worked extensively on probing SPI flash from T2 MacBooks and similar devices, and recently developed a custom Windows kernel-mode driver for MMIO mapping and SPI controller access. As part of this work, I’ve begun creating a signed kernel-mode driver designed to enable internal SPI flash access on Windows—particularly for platforms where external programmers aren’t viable or where forensic traceability is essential. The driver emphasizes modularity, context preservation, and empirical validation, and I’m exploring how it could interface with Flashrom’s internal programmer logic. I understand Flashrom currently relies on external drivers like WinRing0 or portio.sys for low-level access on Windows, but these solutions are unsigned, fragile, and often flagged by modern security tools. I’d like to ask whether the team would be open to discussing the possibility of integrating or supporting a signed kernel-mode driver for secure internal access on Windows. If there’s interest, I’d be happy to share technical details, constraints, and potential implementation paths. I deeply appreciate the work you’ve done on Flashrom—it’s an invaluable tool for the hardware security and research community. Best regards, James

2 1