Flashing a Blank Chip with Patched BIOS File in *.fd Format Using the CH431A Module. about rebaruefi HOT 11 OPEN

Just change the extension to rom or bin and flash ...
Make sure ch341 voltage is 3.3V. It wont kill the chip immediately if it's 5V, but it's risky ...

from rebaruefi.

Thank you for your reply. I did give that a try, but no joy. That got me wondering and I opened the existing official BIOS and the patched one next to each other in a HEX editor. The two files are radically different, so I'm a little lost now. I read through the entire tutorial on here about patching BIOS to enable ReBar and from what I understood the differences should be relatively minor after patching.

Do you set the voltage using the jumper on the pins marked 1, 2, 3, TX, RX, GND, and 5V? The jumper is currently sitting on 1 and 2.

from rebaruefi.

Haven't flash Asus bios with CH before, so I'm not sure if capsule needs to be removed or not, but fd extension is from mmtool and you can safely rename it. Do a dump of current bios and compare...
Sorry, I have a different version of CH341 and had to do a wire mod to get 3.3. Check the manual.

from rebaruefi.

The BIOS files ASUS provides are definitely CAP files. Although I'm not sure what removing a capsule means.

So looking at both the cap file and the *.fd file (which I have renamed to be a *.rom file now) I can see the most obvious difference is that in the cap file the entire structure is contained within a master heading called "AMI Aptio capsule", and in the patched file the begins one step below this with "Intel image". Does that mean anything?

I have compared both files with the UEFITool, and with the exception of the above discrepancy, the differences are in fact quite small. Just the few lines added or changed during the patching process.

So it looks like the patched file is actually what it claims to be, which is good. Now I just need to figure out how to get it onto a chip that will post.

from rebaruefi.

from rebaruefi.

You can remove capsule with uefitool or hex editor.

from rebaruefi.

I managed to remove it.

I also managed to find a programmer to use with the CH431 that didn't report an error on verification, but the chip still won't post on the motherboard.

In order to make a real comparison, I used the reader to extract a copy of the working BIOS that is actually on the chip on the motherboard. However, when I open this in EUFITool, it says "Image parsing failed - Invalid UEFI volume". I find it very odd that the one BIOS the tool reports errors on is the untouched working one provided by ASUS themselves. Unless it was corrupted during the read process. Would that be likely?

from rebaruefi.

Are you sure chips are compatible? What are the serial numbers on them?

from rebaruefi.

I bought the blank one from a highly-rated seller on eBay who specializes in BIOS related hardware.

Chip preinstalled on M/B: Winbond 25Q128FVIQ - 1825

Chip I received: GigaDevice GD25Q128CPIG - EP16262E - AH1319

from rebaruefi.

Okay, you may be on to something there. I tried reading the BIOS off the Winbond chip, saving it, and writing it onto the GigaDevice chip. The GigaDevice chip won't post when I install it. The only other thing I can think of is that my CH431 module is bad and garbling things up during reads and/or writes.

from rebaruefi.

From specs, both chips should be compatible. Pinout is the same but their clocks are different - although I don't think that should be the problem. Problems when opening bios dump are not normal. Is the chip correctly recognized by software when connected?
Try this software: https://drive.google.com/file/d/17AM2kboLrQkkwRFT_dvCEoroWLkHdp8T/view?usp=sharing

from rebaruefi.