@davidm71 - your dump is only used here for info purposes, to see board specific detail locations etc, I will make him BIOS from stock or other dump etc if needed (since you are not sure about validity)
But yeah, main reason I asked you for the dump was just to see all sys info locations and layout etc.

@ibsajc - I can make you BIOS, no need to pay them, and you can get BIOS chip much cheaper on ebay, even more-so if you order 3-5 at a time.
I will get BIOS made for you shortly, sorry I mean to make it tonight and got busy trying to fix something else. Yes, I know all about UUID, serial and how they are made etc.
Black programmer is fine, or you can get green, up to you. FD44Editor is not used here, well it can possibly be for inspection or edit too if you wanted, but I wont use it, and it only fixes data into one location (and sometimes not properly)

What do you mean about >> MAC addresses I do not need any verification after 20 years as a Linux administrator << ??

MAC address goes into GbE region of BIOS twice (and same ID, not both) at 0h and 1000h.
I'm still trying to find secondary MAC Location, that was main reason I asked davidm71 for his dump, but alas he doesn't know his second MAC ID, so I can't verify if it's even stored in his BIOS either.

SN may have added letters in front of it, that may or may not be in your Linux dump info, this would be date of manufacturer by letter code

What is the above attached file? Some random dump? If yes, and only ME FW is different, how are you comparing?
If it's actual dump from running board, and not some fake dump posted at a BIOS repair/recovery site to help user fix BIOS, then there should be lots of differences vs stock BIOS or any other BIOS.
if it's from these sites, then yes, it's stock BIOS with added FD and ME which may be from any time when the file was made. This kind of BIOS should only be used as last resort recovery
Yes, UUID original has MAC ID at end.

@davidm71 Thanks for the dump. For now, it's the only one available. I just need it to find where to put SN, UUID and MAC addresses. I couldn't find the second MAC address, did you disable the network card?
Only @Lost_N_BIOS can know if it helps me and if what I did is good, I do this for the first time in 20 years as a Linux administrator. I flashed over 100 BIOS but didn't have to rewrite any so far.

Zitat von Lost_N_BIOS im Beitrag #556

---

What do you mean about >> MAC addresses I do not need any verification after 20 years as a Linux administrator << ??

---

Zitat von Lost_N_BIOS im Beitrag #556

---

I'm still trying to find secondary MAC Location, that was main reason I asked davidm71 for his dump, but alas he doesn't know his second MAC ID, so I can't verify if it's even stored in his BIOS either.

---

Zitat von Lost_N_BIOS im Beitrag #556

---

SN may have added letters in front of it, that may or may not be in your Linux dump info, this would be date of manufacturer by letter code

---

Zitat von Lost_N_BIOS im Beitrag #556

---

What is the above attached file?

---

@ibsajc - Ahh, gotcha, about the MAC ID's

Yes, I too searched xxxxxx5/xxxxxx6/xxxxxxxx4 too because that is the norm, but nothing, and we talked in PM about it, he doesn't have the board anymore so we'll have to move ahead without and see if it works or not.
Some MAC ID's are stored in chip FW, but I did expect this one to be in the GbE since same LAN chip for both and first one is there.

Use UEFITool 25.0 to extract GbE, padding area, and body of FD44 module, make sure you get MAC x2 in GbE at 0h and 1000h.
Edit in, then replace. Be sure to do rest of system info as you see it in both other sections (first/main padding file inside BIOS region at 4000h withing that padding area)
And in SMBIOSFlashData (ie FD44820B-F1AB-41C0-AE4E-0C55556EB9BD) << This is what FD44Edtitor uses/inserts to, sometimes incorrectly, so put in manually as you see it in davidm71's BIOS

Sounds like you will be OK to fix and test yourself But, if you want me to do it let me know
When you go to write to the chip, use Colibri or ASProgrammer, both included in this package - http://s000.tinyupload.com/index.php?fil...213094641136166

Maybe eventually @C:/con/con will reply back, and if he has board still and sends dump, then we can see if two MAC ID"s in his or if only one in BIOS and one in FW etc

Zitat von Lost_N_BIOS im Beitrag #559

---

Sounds like you will be OK to fix and test yourself

---

@ibsajc - Sorry, no, I didn't check that file, I asked you what it was and you didn't comment so I wasn't sure.
From your images, looks like you missed MAC ID #2 in GbE area (that would be 2000h on straight hex file, or 1000h on extracted GbE region) - But stock BIOS does not contain GbE like a dumped, you need to extract his GbE, edit MAC ID x2, and swap into your target file
Now, checking file.... >>

Confirmed GbE comments above, you need to swap in that entire region, then replace your MAC ID x2 (I only see Davidm71's MAC ID there x1, and rest of GbE missing).
Extract GbE region from Davidm71's BIOS using UEFITool 25.0, in hex editor at 0h put your MAC ID, and then at 1000h put your MAC ID again, then save and replace this GbE region into your mod BIOS

Then, on the entire file as a whole in hex, at 0x2D4000h, you need to fix this entire block with your serial, UUID, and MAC ID. And at 0x2F0FE0h same needs done.
So basically, I think you uploaded the wrong file for me to check, or you never saved your intended changes maybe? This file from end of post #554 (new.bin) system info-wise is untouched Davidm71's info
Ohhh! I see what you did, you replaced blank areas in stock BIOS, with Davidm71's info and not your own as test edit, correct? If yes, all look like it's done properly, but you just need to do it with your Serial/UUID/MAC.
And you need to to the GbE extract edit I mentioned - extract, edit, replace, instead of editing the stock GbE

Zitat von Lost_N_BIOS im Beitrag #561

---

Ohhh! I see what you did, you replaced blank areas in stock BIOS, with Davidm71's info and not your own as test edit, correct?

---

Zitat von ibsajc im Beitrag #558

---

It 's the BIOS version 3204 (from the ASUS website) from which I extracted (with the help of UEFITool from AMI Aptio capsules -> Extract body ...) the .bin file in which I added as test SN, UUID and the MAC address from the davidm71's dump. I don't know if it's okay, that's what I was asking.

---

Zitat von Lost_N_BIOS im Beitrag #561

---

If yes, all look like it's done properly, but you just need to do it with your Serial/UUID/MAC.

---

Zitat von Lost_N_BIOS im Beitrag #561

---

Confirmed GbE comments above, you need to swap in that entire region, then replace your MAC ID x2 (I only see Davidm71's MAC ID there x1, and rest of GbE missing).

---

Yeah, sorry, I missed that, due to when I went to check now, I didn't look at 558 only what you mentioned at the post where BIOS link was.
You can do this much easier with UEFITool 25.0, if you want me to show you image of what/how to extract for edit and then you replace same way, let me know.
MAC Address, unknown about 2nd port, he does not have that board anymore, nor a Ethernet/MAC issue / we assume there was not LAN issue when he dumped it.
And, it's normal for same MAC ID to be in GbE region twice, actual board dumped BIOS has double GbE region often, stock BIOS does not as it's meant to be a partial in-place update to current in-bios contents.
Do as I mentioned, extract GbE region from his BIOS, edit the MAC ID at 0h and 1000h with your main first MAC ID only, then replace back into file. Later you can test putting second MAC ID at second location, but I've never seen that be how these MAC ID's are stored with dual Ethernet boards.
2nd MAC ID is probably stored in the chip FW

Zitat von Lost_N_BIOS im Beitrag #563

---

You can do this much easier with UEFITool 25.0, if you want me to show you image of what/how to extract for edit and then you replace same way, let me know.

---

Zitat von Lost_N_BIOS im Beitrag #563

---

2nd MAC ID is probably stored in the chip FW

---

@ibsajc - Please use 25.0 as mentioned, newer can cause issues on BIOS rebuild. Probably not in this case due to where you are editing, but I did not check if that second volume with FD44 module has any problems when using 28 or not.
The padding and GbE module should not be an issue, but that FD44 module inside volume may be, so best to stick with 25.0 until you know how to check to be sure it's OK. Best practices, you know, until you know how to check post-edit vs pre-edit for issues.

For doing the actual edit with UEFITool, you need to extract only #1 from davidm71's BIOS, the other two # below, you edit the stock one to match davidm71's for that entire small block area in each instance, except with your data at the specific info locations
1. Extract davidm71's GbE As-Is and then edit, then replace As-Is to your target stock BIOS.
2. From the stock target BIOS, Main padding between volumes in BIOS region, extract As-Is and replace As-Is
3. From the stock target BIOS, FD44 module (aka SMBIOSFlashData / FD44820B-F1AB-41C0-AE4E-0C55556EB9BD) expand to RAW area, select that, extract body, edit, replace body.

Main thing to keep in mind, always replace the same way you extracted. If any header checksums of modules you edit need corrected UEFITool will do that on rebuild

Yes, plutomaniac is a ME FW genius!! And yes, always make backup, and then have someone check it to be sure it's OK and valid if you don't know for sure how to check, before you do any erase or writes

@Lost_N_BIOS when you have time can you make me a BIOS according to your method starting from the original ASUS (3204 from post #547) but with SN, UUID and the MAC address from davidm71's dump. I would like to compare it with what I did and maybe I will learn something more.

Zitat von Lost_N_BIOS im Beitrag #565

---

2. From the stock target BIOS, Main padding between volumes in BIOS region, extract As-Is and replace As-Is

---

@ibsajc - Sorry, I forgot to mention, on stock BIOS that first padding is placeholder for backup NVRAM volume which is not in stock BIOS. You'll be extracting and editing the second padding, you can tell which is correct based on size
Don't swap this padding from one BIOS version to another, there is vBIOS copy in there that may differ between BIOS versions, so always extract from target, edit the sys info part, then replace back in. Just FYI

Here is 3204 BIOS test edited as you requested, but why use old BIOS version??? You should use 3602
http://s000.tinyupload.com/index.php?fil...174209096595275

Zitat von Lost_N_BIOS im Beitrag #567

---

Sorry, I forgot to mention, on stock BIOS that first padding is placeholder for backup NVRAM volume which is not in stock BIOS. You'll be extracting and editing the second padding, you can tell which is correct based on size

---

Zitat von Lost_N_BIOS im Beitrag #567

---

Here is 3204 BIOS test edited as you requested, but why use old BIOS version??? You should use 3602

---

@ibsajc - Only the padding one you have to extract, edit, put back, into same version, but yes, you can make the sys info edits same across any version, just be sure you extract and edit in that info block and then replace
GBE and the FD44 module you can swap in from other versions, provided FD44 module is same size in each (I didn't check), but it's not best practice to get yourself used to editing like that (neither is straight on hex edit of entire file)
Best to not edit this as a direct .bin file, due to the FD44 module being inside a volume, that module header checksum would be changed, and that volume checksum would need changes, and that wouldn't happen in a straight hex edit

Zitat von Lost_N_BIOS im Beitrag #569

---

@ibsajc - Only the padding one you have to extract, edit, put back, into same version, but yes, you can make the sys info edits same across any version, just be sure you extract and edit in that info block and then replace
GBE and the FD44 module you can swap in from other versions, provided FD44 module is same size in each (I didn't check), but it's not best practice to get yourself used to editing like that (neither is straight on hex edit of entire file)
Best to not edit this as a direct .bin file, due to the FD44 module being inside a volume, that module header checksum would be changed, and that volume checksum would need changes, and that wouldn't happen in a straight hex edit

---