Nothing more on the way, just boot from USB and FLASHSPI.EXE MA74S2H2.FC … no checksum error, it seemed to be flashing the right way, no error messages at all.
Shut down the computer and never went online again, just black screen.
Right now i’m trying to fix the board replacing the ROM chip, but i wish to know what was wrong with the process, because i still want to upgrade my bios if i get it back to life.
So, for someone who can take a look, here are both original FC bios and modded one.
If i get success bringing it back to live, i will drop a line here to help.
Since I don’t remember a similar report from any other user, I am very sorry, that you ran into such trouble after an update of the AMD AHCI ROM module of your Gigabyte mainboard BIOS. I have already downloaded both BIOS files you have uploaded and will do a deeper look into them to find out the reason for the BIOS flash failure.
If you have just replaced any module, which is before/above the sensitive modules, by using CBROM155, you have done a big mistake, because it is needed to correct the location of the sensitive modules. The tool CBROM155 is able to correct the checksum, but not to replace the sensitive modules into the correct location within the BIOS.
Regarding the recovering of a working BIOS I wish you good luck! Maybe >this< thread will help you.
by mistake I have just uploaded two times de original BIOS. Below I attach the right modded one.
You are right, but I looked at ahci (PCI B) and it wasn’t near the protected modules you mention.
I tried with CBROM 1.98 and the flash program told me checksum error, and then used CBROM 1.55… you know the result.
As far as I know, there are two other recovery methods when dealing with Gigabyte Dual BIOS. The first one is just short two pins from the Main BIOS chip, who forces bypass of Main BIOS check and brings all the work to the Backup BIOS. It worked for me, but I just damaged the chip (the chip was smoking at the end of the shorting trick). But for now the Backup BIOS brings up the system and tries to repair Main BIOS (no BIOS found), and get in a endless boot loop.
The second method involves replacing the chip, and cross fingers so Backup is now able to restore Main BIOS. I’m waiting for the hardware and will try.
Maybe I can drop a couple of lines for both methods.
Mmmmmmm, I’m not sure about this, the last modded BIOS I attached contains item number 21 for the injected PCI ROM (B) = ahci.bin Where de original one does not contain the same ahci version and is listed in item number 12.
Total compress code space = D3000h(844.00K) Total compressed code size = 822FAh(520.74K) Remain compress code space = 50D06h(323.26K)
** Micro Code Information ** Bridge ID | Bridge ID North South Update ID CPUID | North South Update ID CPUID ---------------------------------------+--------------------------------------- C0012102 0401 | 1000002 0000 |
Total compress code space = D3000h(844.00K) Total compressed code size = 8390Bh(526.26K) Remain compress code space = 4F6F5h(317.74K)
** Micro Code Information ** Bridge ID | Bridge ID North South Update ID CPUID | North South Update ID CPUID ---------------------------------------+--------------------------------------- C0012102 0401 | 1000002 0000 |
Thanks for having uploaded again both BIOS files, which now really are different. As I already have written, you forgot to insert something like a “Dummy” into the place, where the original AMD AHCI ROM module was. So the following modules inclusive the MEMINIT have been moved from their original place. Example: The original MEMINIT location started at offset 76350, within the modded BIOS the MEMINIT module starts at offset 73F30.
I hope, that you will be able to recover your original BIOS. After having a working Computer again, you may retry te BIOS modding procedure. Before you start, I recommend to read >this< and >this< thread.
You were right again, no dummy module has been injected in replacement of AHCI.bin original module. Following the links you gave me, I just have put SL.bin dummy module in the position of AHCI.dll, and new AHCI.dll right at the end of the bios.
Please, can you take a look at this new mod BIOS for my board and tell me if I have missed anything else?
I have just checked the freshly reupdated BIOS and didn’t find any mistake (apart from naming the AHCI ROM file AHCI.bin instead of ahci.BIN) and nothing that you may have missed. So I am pretty sure, that your system will work fine after having flashed the updated BIOS.
You certainly mean the AHCI.bin (resp. ahci.BIN) and not the AHCI.dll (original name: ahci.DLL).