12/17/2022 0 Comments Uefitool 0.21.5![]() ![]()
The UUID is hard to get, unless you have previously run from the cmd prompt: wmic csproduct get name, identifyingnumber,uuid as described in the BIOS Chip Recovery Program post and video or you can use your Pomona clips to read from an original good chip that came on the mobo from ASUS, and it would contain those three identifiers and you can see and record them using the FD44Editor. Don't know if it is the same locations for C6H. ![]() #Uefitool 0.21.5 mac#The MAC was on the 24 pin ATX power connector. Your mobo S/N from AI Suite 3 must be a general placeholder? On my R5E the S/N was on a sticker at the top of the board: 15 digits after "000-". #Uefitool 0.21.5 verification#Other than writing to the chip with a EEPROM programmer, the usual flash process involves a signature verification so that the boot can start from a trusted source, to my knowledge. The UUID might also have to do with security. I understand you can access the NIC from within BIOS, maybe it has something to do with that, or maybe it has something to do with security because every MAC is unique. #Uefitool 0.21.5 code#I too wondered why the BIOS code would contain the MAC address of the NIC but I searched for it in the binary image of my BIOS and it was found at two different addresses. Good news that the BIOS programmed with the CH341A is working! And without entering all the identifiers. #Uefitool 0.21.5 serial number#According to the AI Suite 3, my motherboard's current serial number is MB-1234567890, so I might patch that later (I think the tool UEFIPatch might help there, but I haven't used it yet) as for my UUID, I imagine I will need to boot into the BIOS to get that, and if it needs to be changed, again, I'll change it later on.Īsus CAP to ROM file (same process for converting to BIN files): I would think that the MAC address for the NICs would be a part of the NIC's chipset, not the BIOS, but I could be wrong in either case, I'm using my wired NIC right now, and it's working just fine. I didn't add any identifiers, but I might do that later seems to be running just fine (actually, I finally got my G.Skill F4-3200C14-16GTZ (32GB total, 2 sticks) to run at the promised 3200Mhz, and it seems stable thus far took some tweaking, but that's a story for another time). I downloaded the vanilla BIOS from Asus's website, versions 14 then I used UEFITool () to convert the. I did end up using the Pomona clips (I had ordered a different set of test clips, but what arrived didn't match what was shown on the product page it also was so chunky that I couldn't grab the Winbond chip, because there are some (mysterious) headers next to it that physically prevent the clip from attaching). ![]() If you didn't add those identifiers, is it working ok? Maybe they are on protected memory blocks of the original chip and adding the new code from the CAP file doesn't disturb it? ![]() I am curious to know if you used the Pomona clips to read a known good bios image into a BIN file, then wrote that to the bad chip? Or did you use a file from the downloaded CAP file? The latter would not have the MAC address, UUID and motherboard Serial No, which I understand can be added using the FD44Editor utility. I used an EEPROM programmer to copy the good BIOS image onto a replacement Winbond chip to replace the corrupted one. Hi, and congrats on recovering from a corrupted BIOS chip w/o an RMA! I just did that myself with the dual BIOS R5E. If anyone is interested, I can put together a guide for resuscitating your BIOS using a BIOS programmer (won't fix non-BIOS problems, but if flashback isn't working, or if you bricked the BIOS, it should work). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |