it’s recommended to read the file using flashrom 3x and making sure all 3 are valid images and have the same checksum before writing. The error sounds like you’re not getting a good read on the chip, since it can’t read/parse the IFD
When I scan it, it reads 1 Mbyte of information.
hasan@haszen:~$ sudo flashrom -p ch341a_spi -r badflash.rom
[sudo] hasan için parola:
flashrom unknown on Linux 6.8.0-51-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip “W25Q80.V” (1024 kB, SPI) on ch341a_spi.
This flash part has status UNTESTED for operations: WP
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to [email protected] if any of the above operations
work correctly for you with this flash chip. Please include the flashrom log
file for all operations you tested (see the man page for details), and mention
which mainboard or programmer you tested in the subject line.
Thanks for your help!
Reading flash… done.
hasan@haszen:~$ ./cbfstool badflash.rom read -r RO_VPD -f vpd.bin
E: This is a legacy image that contains only a CBFS
E: The image will be left unmodified.
hasan@haszen:~$ ./gbb_utility badflash.rom --get --hwid | sed ‘s/^hardware_id: //’ > hwid.txt
ERROR: No GBB found in badflash.rom
hasan@haszen:~$ sudo flashrom -p ch341a_spi -v <coreboot_edk2-kaisa-mrchromebox_20240914.rom> --ifd -i bios
Error: Extra parameter found.
hasan@haszen:~$ sudo flashrom -p ch341a_spi -v coreboot_edk2-kaisa-mrchromebox_20240914.rom --ifd -i bios
flashrom unknown on Linux 6.8.0-51-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip “W25Q80.V” (1024 kB, SPI) on ch341a_spi.
This flash part has status UNTESTED for operations: WP
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to [email protected] if any of the above operations
work correctly for you with this flash chip. Please include the flashrom log
file for all operations you tested (see the man page for details), and mention
which mainboard or programmer you tested in the subject line.
Thanks for your help!
Reading ich descriptor… done.
Couldn’t parse the descriptor!
hasan@haszen:~$
that’s the wrong chip, 1mb is the EC, the main firmware flash is 16 or 32mb
OK, I found it, I have another eprom “Gigadevice 25Q127CWIG”
What do you call Shellball ROM? I found a full ROM in the firmware script section, but I couldn’t find a Shellball ROM. I scanned its own bios information, extracted the vpd and hwid information, and then I got stuck on the step of injecting it into the shellball ROM.
One more question: Why am I removing the vpd and hwid information from the bios I scanned myself? Also, why am I removing the vpd and hwid information from the ROM I downloaded from your site?
was my explanation above not clear?
you don’t need a shellball ROM. That’s for people who 1) are going back to stock, and 2) were idiots and didn’t take care to make a backup of their stock firmware.
You’re wanting to run Windows, so you need the UEFI Full ROM firmware image. Your device has stock firmware on it now, so you should 1) back that up before doing anything else, and 2) extract the VPD from the stock firmware image and inject it into the new UEFI firmware before flashing, so that the device’s serial # and LAN MAC address are persisted – as per the documentation
I succeeded, thank you sir
1 Like