Finally got the stuff. Did the connection (followed this guide [GUIDE] Flash BIOS with CH341A programmer).
Use Asprogrammer to read but got all 00. (Asprogrammer cannot also detect the bios chip so I chose it manually). Tried other software too and same results
Do I need to connect PSU to the motherboard and how to proceed?
Does the PSU has to been switched on (as in the back switch to provide power [position 1])?
Update: Oww… sh*t got it to connect
Thanks all
Ok, got the dump. The m/b is GA-AB350M-D3H. Anyone can help extract the info required from the dump bios? (mac, serial, uuid etc2).
What info/details are actually required anyway from the bios?
Also please provide instruction on how to insert the extracted info to new bios file if possible.
File link:
Those firmwares changed format somwhere between F30 and F52g so it might be possible you experience whats been described in the thread linked by MeatWar.
Regarding board specific data- there’s often very little for consumer boards sold separately. I’d assume this raw section here:
But you’re the only one who has the information what to find. So either post serial, uuid, mac- everything you may have on the package ot on stickers or search the file with a hex editor and UEFIToolNE for the relevant data.
My bad. Forgot to post those details from board stickers:
mac: 1C1B0DEE81BD
1/B/H4A016 00337
not sure waht is the above
Sorry, I’m not able to find any of those details in the firmware.
Same here.
So what can I do? Anyone can help?
Is it possible that those info are not stored in the bios?
@lfb6 Can you tell me how you do the search? Just use hex editor and search for hex/text values?
The larger problem might be the scenario described in MearWars link.
There’s a block with raw data beginning with BSA, but it’s empty. There’s the block with some clear text and some encrypted? stuff.
You can search in hex editor or in UEFIToolNE, the latter has the advantage to be able to search in compressed regions.
Board should start with stock bios, so I’d try that first. If it’s a brick it’s not the missing board specific data.
But I compared the static parts of your dump to stock and there is no relevant difference. What did brick the board? Maybe it’s good enough to empty NVRAM?
@lfb6
“You can search in hex editor or in UEFIToolNE, the latter has the advantage to be able to search in compressed regions.”
I tried both hex editor and UEFIToolNE and found nothing
“Maybe it’s good enough to empty NVRAM?”
How to do this? I tried resetting BIOS & clear CMOS and it’s no go.
Still
Secure boot?
Probably not. There no newer entries regarding secure boot but both NVRAM have several entries for setup as last values.
Replace the first NVRAM volume in your dump with the one from stock firmware 52g (0x37000 to 0x56FFF), replace the second NVRAM (0x57000 to 0x76FFF) with FF
(Rename to 350_N.zip.001 and 350_N.zip.002)
350_N.zip.001.zip (6 MB)
350_N.zip.002.zip (4.8 MB)
Thanks. This’ll take a while
