May 2026 - flashrom - mail.coreboot.org

LIBUSB_TRANSFER_STALL error
by dvb＠fpm.kubsu.ru May 29, 2026

May 29, 2026

Greetings! I was using flashrom to flash MX25L6445E chip with CH341A USB device. The chip is read without errors, but once I try to write it says the following: ===================================== > flashrom -p ch341a_spi -c "MX25L6436E/MX25L6445E/MX25L6465E" -w dump.202.bin flashrom v1.7.0 (git:v1.7.0) on Linux 6.8.0-117-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Updating flash chip contents... cb_in: error: LIBUSB_TRANSFER_STALL cb_out: error: LIBUSB_TRANSFER_STALL ch341a_spi_spi_send_command: Failed to write 36 bytes Register read failed! Erase/write done from 0 to 7fffff Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... cb_in: error: LIBUSB_TRANSFER_STALL ch341a_spi_spi_send_command: Failed to read 4100 bytes cb_in: error: LIBUSB_TRANSFER_STALL read_flash: failed to read (00000000..0x7fffff). Can't even read anymore! Your flash chip is in an unknown state. Please report this to the mailing list at flashrom(a)flashrom.org or on chat (see https://flashrom.org/contact.html for details), thanks! cb_in: error: LIBUSB_TRANSFER_STALL cb_out: error: LIBUSB_TRANSFER_STALL ch341a_spi_spi_send_command: Failed to write 36 bytes Register read failed! cb_out: error: LIBUSB_TRANSFER_STALL enable_pins: Failed to write 4 bytes Could not disable output pins. ===================================== Sometimes the error is LIBUSB_TRANSFER_TIMEOUT. The result is erased regions on the chip, which were to be written. The error first appeared on v1.3.0, but thecompilation of v1.7.0 didn't solve the problem. I tried different USB ports, USB hub with external power, other laptop - nothing helps. Please advise. -- Sincerely, me...

1 0

Flashing using ch341a
by cab May 29, 2026

May 29, 2026

I am trying to flash a Macronix chip MX25L25673... using external programmer ch341a and a WSON8 probe. Even though the chip is not listed in `` `flashrom --list-supported` `` option, I understand that this chip is flashable using flashrom. I tried flashing using the flashrom packaged with debian v1.6.0 and also built flashrom from the main branch in github v1.8.0-devel. I use the WSON 8 Probe that has an impression at the end to aid with aligning the probe to the pins in motherboard like the one listed in the link https://www.alibaba.com/product-detail/SOP8-WSON8-QDFN8-Microchip-Surface-M… I use ch341a v1.7 with 3.3V settings I get inconsistent result. Below are the two results I get during many attempts. I either get "unknown ST SPI chip" or "unknown SPI chip". In both options, the status is `NOT WORKING` for `PROBE READ ERASE WRITE` I was wondering if you are aware of this issue and know how to fix it? $ flashrom -p ch341a_spi --flash-nameflashrom v1.6.0 on Linux 7.0.9-205.fc44.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Found ST flash chip "unknown ST SPI chip" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE This flash part has status UNTESTED for operations: WP $ flashrom -p ch341a_spi --flash-name flashrom v1.6.0 on Linux 7.0.9-205.fc44.x86_64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE This flash part has status UNTESTED for operations: WP

1 0

FAILED: ASRock X470 Master SLI/ac
by Jeff Erbrecht May 4, 2026

May 4, 2026

I have an ASRock X470 Master SLI/ac board that previously ran a 2700x on old/stock firmware. I upgraded to a 5700x which required newer firmware, so I also ugpraded the firmware to P4.40. I did this using the manufacturer's standard tool, not flashrom. This version removes support for the 2000 series CPUs. I later upgraded the mainboard for the 5700x as well, and then I was planning on using this X470 board + my older 2700x (which I still had laying around) for my homelab/secondary computer. But of course it won't POST since it's now running the newer firmware for the 5700x. I tried using flashrom to downgrade to P3.40 (the newest version that supports 2000 series) since the manufacturer's tools don't let you downgrade normally. I ran into a couple hurdles, and finally an error, so now I'm stuck. 1. There were three chips reported by flashrom. They were all mapped to the same physical address so I assumed it didn't matter which one to pick, and chose the -35F one: Found Macronix flash chip "MX25U25635F" (32768 kB, SPI) mapped at physical address 0x00000000fe000000. Found Macronix flash chip "MX25U25643G" (32768 kB, SPI) mapped at physical address 0x00000000fe000000. Found Macronix flash chip "MX25U25645G" (32768 kB, SPI) mapped at physical address 0x00000000fe000000. 2. The dumps for all three chips are different despite having the same physical address. Not sure if this is expected. $ sha256sum MX* e14ce07966a1d4ee0a96a154d2fbe8e69579512286f66e3e245d1aba0adbf332 MX25U25635F.rom 7d88f910042d42f70f49c1eec467f5d1508d524be62ca0a18340373dceb069bb MX25U25643G.rom e70c35775d12a515aa5e82039456f4d103be652fa27633a3fcdca1c7c795cbb3 MX25U25645G.rom 3. The image from the manufacturer is only 16 MiB while the reported capacity is 32 MiB. So I padded it by appending it to itself to get to 32 MiB. 4. Finally, I get an error when flashing: $ sudo flashrom -p internal -c MX25U25635F -w v340padded.rom ... Reading old flash chip contents... done. Updating flash chip contents... FAILED at 0x00c01000! Expected=0xff, Found=0x4e, failed byte count from 0x00c01000-0x00c01fff: 0x100 ERASE FAILED! Erase/write done from 0 to 1ffffff Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. Your flash chip is in an unknown state. I get similar errors with the -43G and -45G chips. Any insight would be appreciated!

1 0

GigaDevice GD25B127D (marking 25B127DSIG) via CH341B (black) MinProgramment
by vozniu4OK May 3, 2026

May 3, 2026

Hello flashrom team, I would like to report a successful operations with the *GigaDevice GD25B127D* SPI flash chip (marking on chip: *25B127DSIG*). *Programmer:* CH341B (USB) *Chip status:* Works correctly with -c GD25B128B/GD25Q128B definitions. *Full log of the operation (Read/Erase/write/Verify):* http://paste.flashrom.org/view.php?id=3825 Thank you for maintaining such a great tool! Best regards, [v4]

1 0

Re: HI flashrom team,
by wcrvf May 2, 2026

May 2, 2026

I successfully flashed my device using this command—thank you! sudo flashrom -p raiden_debug_spi:target=AP -c "GD25B128B/GD25Q128B" -w coreboot_edk2-atlas-mrchromebox_20260409.rom On Sat, May 2, 2026 at 12:11 PM wcrvf <guaidaoniao(a)gmail.com> wrote: > Hello flashrom team, > > i don't know how to deal with it > > I am reporting a flash failure on a Google Pixelbook Go (Board Name: > ATLAS). [System Info] - Device: Google Pixelbook Go (ATLAS) - Environment: > ChromeOS Developer Mode / Ubuntu (Linux 6.14.0) - Programmer: internal - > Hardware WP: Disabled via SuzyQable (Cr50 CCD opened, FlashAP Always) > [Error Description] While attempting to flash the Full ROM firmware, I > encountered the following errors: 1. Warning: Setting BIOS Control at 0xdc > from 0x8b to 0x89 failed. 2. SPI Configuration is locked down. 3. FREG0 > (Descriptor) and FREG2 (ME) are locked. 4. "Opaque flash chip" detected, WP > operations not implemented. [Attached Log] (Please find the attached > /tmp/flashrom.log for detailed output) It seems the Intel Kaby Lake chipset > is locking the SPI configuration, preventing flashrom from performing > erase/write operations even with hardware write-protect disabled via CCD. > Regards, > > Thanks > > > > ChromeOS Device Firmware Utility Script [2026-04-30] > (c) Mr Chromebox <mrchromebox(a)gmail.com> > ********************************************************* > ** Device: Google Pixelbook Go > ** Board Name: ATLAS > ** Platform: Intel KabyLake > ** Fw Type: Full ROM / UEFI > ** Fw Ver: MrChromebox-4.22.2-5-g822782a1001 (02/13/2024) > ** Update Available (04/09/2026) > ** Fw WP: Disabled > ********************************************************* > ** [WP] 1) Install/Update UEFI (Full ROM) Firmware > ** [WP] 2) Restore Stock Firmware > ** 3) Backup Current Firmware > ** [WP] 4) Flash Custom Firmware > ** 5) Set Hardware ID (HWID) > ** C) Clear UEFI NVRAM > ********************************************************* > Select a numeric menu option or > R to reboot P to poweroff Q to quit > 1 > > Install/Update UEFI Full ROM Firmware > > IMPORTANT: flashing the firmware has the potential to brick your device, > requiring relatively inexpensive hardware and some technical knowledge to > recover.Not all boards can be tested prior to release, and even then slight > differences in hardware can lead to unforseen failures. > If you don't have the ability to recover from a bad flash, you're taking a > risk. > > You have been warned. > > Do you wish to continue? [y/N] y > > > Downloading Full ROM firmware > (coreboot_edk2-atlas-mrchromebox_20260409.rom) > > ############################################################################################################################################################################## > 100.0% > ############################################################################################################################################################################## > 100.0% > > Creating device HWID from board name > > Persisting device HWID > > VPD extracted from current firmware > > Disabling software write-protect and clearing the WP range > > Installing Full ROM firmware (may take up to 90s) > > Error running cmd: /tmp/flashrom -p internal:boardmismatch=force > --use-first-chip --ifd -i bios -N -w > coreboot_edk2-atlas-mrchromebox_20260409.rom >/dev/null 2>&1 -o > /tmp/flashrom.l > og > > Press enter to view the flashrom log file, then space for next page, q to > quit > > > > > > FAILED at 0x00c00000! Expected=0xff, Found=0x5f, failed byte count from > 0x00c00000-0x00c00fff: 0x1dc > ERASE FAILED! > Erase/write done from 200000 to ffffff > Write Failed!Uh oh. Erase/write failed. > Your flash chip is in an unknown state. > Get help on IRC (see https://www.flashrom.org/Contact) or mail > flashrom(a)flashrom.org with the subject "FAILED: <your board > name>"!------------------------------------------------------------------------------- > DO NOT REBOOT OR POWEROFF! > Restoring PCI config space for 00:1f:5 reg 0xdc > >

1 0

"this means we need to add special support to your board"
by Lily cohen May 1, 2026

May 1, 2026

Hello, I am using an arc gpu which functionally requires adding rebar, however my system isnt the newest so I have to modify my bios to make to run. I have ran the command as specificed in the man guide for intel 8th generation chipsets, mine is h370m pro4 which runs h370 chipset as such: Sudo flashrom -p internal:ich_spi_mode=auto -w newamazingrebar.rom -f The output I got finished with the quote in the title, the full output is this. The last section is most important. flashrom 1.4.0 on Linux 6.17.0-23-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Cannot open file stream for /dev/mtd0 No DMI table found. Found chipset "Intel H370". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG1: BIOS region (0x00300000-0x00ffffff) is read-write. FREG2: Management Engine region (0x00003000-0x002fffff) is read-only. FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME for details. At least some flash regions are write protected. For write operations, you should use a flash layout and include only writable regions. See manpage for more details. 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. check_for_unwritable_regions: cannot write/erase inside Flash Descriptor region (00000000..0x000fff). Write Failed!Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Good, writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running.

1 0