Zitat von Lost_N_BIOS im Beitrag #30

---

Great it's now working more than 30 minutes @lwoody7110 - I told you it was possible and would be easy!

As for the system details, it's easier for me to just swap out the entire NVRAM volume, and certain padding sections if details are there, which on the paddings is hard to explain if you aren't familiar with UEFITool
LAN MAC is either in the above mentioned sections, or in GbE region. Please zip a backup of both your now current working BIOS freshly dumped, and then an original BIOS dump before any of the edits.
This way I have both files and for sure the ones I want, and don't have to download previous files trying to find out what's what etc. You can upload to a file host, or attach here is there's enough space (you may need to split rar/zips, that's why I suggested file host instead)

Once I have both files, I can either show you how to do once I check them and find locations of data in question, or do it for you, then you reprogram again and then you'll be all done.

---

@lwoody7110 - so 15.12.2018_x3470 is the newly corrected "Good BIOS", that you need UUID, serial, LAN ID etc from x3470o.zip put back into, correct? I assume so, only double-checking to be certain

The x3450o.zip file, what is it's issue, ME problem, or needs board details problem? If it needs board details corrected, I need a dump from it's original BIOS also

It's easy to do, so yes I can show you with a few images and some short instructions. I'll get this info and files to you tonight, once you let me know for sure what's going on with the last file, and or add that other needed dump if that one needs details corrected.

Zitat von Lost_N_BIOS im Beitrag #32

---

@lwoody7110 - so 15.12.2018_x3470 is the newly corrected "Good BIOS", that you need UUID, serial, LAN ID etc from x3470o.zip put back into, correct? I assume so, only double-checking to be certain

...spot on.



The x3450o.zip file, what is it's issue, ME problem, or needs board details problem? If it needs board details corrected, I need a dump from it's original BIOS also

This board has the exact same issue as the one fixed with 15.12.2018_x3470. This file is the original dumped BIOS. My logic is that the perhaps the same copy of mac, serial, uuid from x3450o.zip into a 2nd copy of 15.12.2018_x3470 would also fix the 2nd motherboard.


It's easy to do, so yes I can show you with a few images and some short instructions. I'll get this info and files to you tonight, once you let me know for sure what's going on with the last file, and or add that other needed dump if that one needs details corrected.

Thank you. I look forward to learning something new.

---

OK, thanks! And yes, I agree with your thoughts if those are exact same systems. However, then they will both have same serial, UUID, and LAN MAC ID, you don't want that do you?
If not, attach images of any and all stickers on the board itself, front and back, and be sure to check sides of connectors like side of 24 pin, top/bottom sides of PCI/PCIE too. Also check inside case, outside top/bottom/back etc.

Never mind, if this is original dumped BIOS for that system, and it has the ME issue from post one, then this one only needs ME fixed and it will be good to go. I will do this tonight, never mind the above!

Will get this done and a short how to for you tonight so you can do yourself too, but only for the serial, UUID, LAN MAC ID for the initial system (Above ME issue to fix, we already have a guide here for that here)

*edit 100 - @lwoody7110 - I just thought of something easy for you.
If this second system is exact same model, you can take the fixed BIOS from Plutomaniac, open with UEFITool (Regular version), extract ME region, and then open second system with messed up ME's backup.bin, replace the ME region with the extracted ME from Plutomanic's BIOS.
Only do that if the systems are exact same model, then no detail swapping will be required. Once done, program that with programmer.

Then all that's left is correcting the first systems details, which I'll do and show you how to do tonight

Zitat von Lost_N_BIOS im Beitrag #34

---

OK, thanks! And yes, I agree with your thoughts if those are exact same systems. However, then they will both have same serial, UUID, and LAN MAC ID, you don't want that do you?
If not, attach images of any and all stickers on the board itself, front and back, and be sure to check sides of connectors like side of 24 pin, top/bottom sides of PCI/PCIE too. Also check inside case, outside top/bottom/back etc.

Never mind, if this is original dumped BIOS for that system, and it has the ME issue from post one, then this one only needs ME fixed and it will be good to go. I will do this tonight, never mind the above!

Will get this done and a short how to for you tonight so you can do yourself too, but only for the serial, UUID, LAN MAC ID for the initial system (Above ME issue to fix, we already have a guide here for that here)

*edit 100 - @lwoody7110 - I just thought of something easy for you.
If this second system is exact same model, you can take the fixed BIOS from Plutomaniac, open with UEFITool (Regular version), extract ME region, and then open second system with messed up ME's backup.bin, replace the ME region with the extracted ME from Plutomanic's BIOS.
Only do that if the systems are exact same model, then no detail swapping will be required. Once done, program that with programmer.

Then all that's left is correcting the first systems details, which I'll do and show you how to do tonight

---

I had exactly the same problem. Thanks to your help, my PC is working again. I have one more question: How can I change the MAC address? I can not apply the method Lwoody7110 used. I do not have the original rom file anymore. Is there another way? I changed the GbE region with UEFITool and a hexeditor. After re flashing the chips, the system did not want to boot. The message "Initializing Intel (R) Boot Agent (then the version number) came up: The LAN adapter's configuration is corrupted or has not been initialized." The Boot Agent can not continue. " I had not considered, that the checksum is not correct anymore. After flashing back the version 7H3_0122.bin from plutomaniac the computer boots again. But UUID has changed. The original I had manually entered in the bios together with the serial number.

@lwoody7110 - All stickers I'd need to see, but only if you do not have original BIOS dumps for both machines, which you do (I believe) so no need for images of stickers.
With original dumps, all details needed are within the BIOS. I was waiting to hear back from you before doing anything.
Sorry I forgot about system one needing fixed too and was waiting to hear what you needed done with system two (If you could do yourself using what I mentioned) or it's details

Yes, MAC is stored in GbE but often repeated in a few key BIOS areas, and yes sometimes as you mentioned combined with other values to create UUID or other keys.
ME can be fixed similar way, if you didn't get it already, can't be sure from what you mentioned? Extract ME region from good BIOS with UEFITool and place in non-good ME BIOS, then program in with programmer.
This only applies if ME also resides on that same BIOS chips dump, sometimes if there are two BIOS chips ME is on another chip.

So tonight I will fix system one's details, correct? x3470o.zip >> Into 15.12.2018_x3470
And then system two ME and details, correct? x3450o.zip Transfer ME from System one, done
Then show you where details copied from (only do that from same system backup to same system, otherwise you transfer serial, UUID, win keys etc to wrong machine)

@Jo0404 - check the motherboard, on the lan port itself there is often a sticker with MAC Address on it. If not, zip and upload al stickers from your board and I will see if any look like MAC address..
If you do not have the MAC Address, what were you putting into GbE region?? Do you have your UUID from before? If yes, put on text and include in the images zip

[quote=Lost_N_BIOS|p66099]@lwoody7110 - All stickers I'd need to see, but only if you do not have original BIOS dumps for both machines, which you do (I believe) so no need for images of stickers.
With original dumps, all details needed are within the BIOS. I was waiting to hear back from you before doing anything.
Sorry I forgot about system one needing fixed too and was waiting to hear what you needed done with system two (If you could do yourself using what I mentioned) or it's details

I have original BIOS (for both motherboards) so no need for stickers. These are x3470o.zip and x3450o.zip. I am happy to fix system 2 (x3540o.zip) myself with your guidance

Yes, MAC is stored in GbE but often repeated in a few key BIOS areas, and yes sometimes as you mentioned combined with other values to create UUID or other keys.
ME can be fixed similar way, if you didn't get it already, can't be sure from what you mentioned? Extract ME region from good BIOS with UEFITool and place in non-good ME BIOS, then program in with programmer.
This only applies if ME also resides on that same BIOS chips dump, sometimes if there are two BIOS chips ME is on another chip.

So tonight I will fix system one's details, correct? x3470o.zip >> Into 15.12.2018_x3470 YES
And then system two ME and details, correct? x3450o.zip Transfer ME from System one, done YES
Then show you where details copied from (only do that from same system backup to same system, otherwise you transfer serial, UUID, win keys etc to wrong machine) Understood, and looking forward to trying this myself

plutomaniac Weird, I've never seen this strange parsing behavior with the volumes in UEFITool! What causes that? Is there any easy way to parse the BIOS region so I can easily show lwoody7110 my originally planned details transfer process?

@lwoody7110 - due to how this BIOS acts in UEFITool I cannot easily explain/show you the details copy over, sorry about that but it's a bit more involved than usual which I planned to easily show you with a few images and short descriptions.
However, due to this BIOS structure/format it's not as easily shown/explained like I usually would be able to, so I just have to do it and pass along the fixed files for you. Here is both BIOS fixed
http://s000.tinyupload.com/index.php?fil...519796800582079

x3470o.rom did not contain your full name? But 15.12.2018_x3470_works.rom and x3450o.rom do, is that because you had not entered a name into the X3470o system, but did later after you got ME working again or sometime interim, so that it's into the working BIOS now but not the initial backup?
I went ahead and left it in there on the "Works.rom", in case you wanted, if not you can blank out via hex using 20 20 20 etc at the location shown in the details files I included. To verify UUID's are correct you can check using this from command line >> wmic csproduct get uuid

There may be other board specifics, settings, windows keys etc, that I cannot easily grab right now due to this parsing issue with UEFITool.
So, if you need those (ie windows isn't activating) hopefully I can get for you later once Plutomaniac replies about this UEFI parsing, if he knows

@Jo0404 - also, if you cannot find MAC on any stickers, check your router/switch logs and see if you can recognize the system. Or, you can use command I gave above to grab current UUID and get MAC ID from that using info below (unless it pulls from same invalid location you have now?)
You may need to dump the BIOS using FPT or programmer.

LAN MAC ID is stored in the BIOS GbE region at 1000h, and then two more times as part of the UUID as follows
UUID = 13h / 19 bytes at both of the following locations (which includes LAN MAC in a certain way as noted below) >> 00510066 - 00510078 (Secondary @ 00511066 - 00511078)

UUID ending w/ MAC info as follows - Going backwards
Last UUID Bytes = Second MAC Bytes (2nd going forwards)
2nd from last UUID Bytes = First MAC Bytes (1st)
Third "" "" UUID Bytes = Last MAC ID Bytes (6th going forwards)
Forth "" "" UUID Bytes = Second from last MAC Bytes (5th going forwards)
Fifth "" "" UUID Bytes = Third From last Bytes (4th going forwards)
Sixth "" "" UUID Bytes = Forth from last bytes (3rd going forwards)

@Lost_N_BIOS
Thanks for your help. Before I flashed with 7H3_0122.bin from plutomaniac, I heave read out the UUID and the MAC. See attached pictures. After flashing I entered the serial number and the UUID D39391D5-2603-11DF-BBDA-05C1CEC518A9 in the bios. In Windows I changed the MAC address from 88: 88: 88: 88: 87: 88 to 18: A9: 05: C1: CE: C5 with ChangeMac-2010. If I now look in the bios I see as UUID 57C5ADBA-03B8-11E9-BBDA-888887888888
Attached the currently flashed file and images. I would be glad if you could help me further.

Are the thermals all right on your board? Maybe its thermal protections shutting down the system?

I flashed 15.12.2018_x3470_works-FixDetails.rom and unfortunately it doesn't work. Luckily I had the good sense to backup the current BIOS before applying 15.12.2018_x3470_works-FixDetails.rom!

I am now unable to enter the BIOS settings via PS/2 or USB keyboards. The system does not POST and hangs on the initial HP splash screen. Only once, I also saw the error in the photo below related to the NIC. Note that I cannot get to see this error again as the board is halted. I assume I got lucky one time to see it.

I've turned the system off for now. Lets hope Plutomaniac has an idea as clearly these HP BIOSs are a bit unusual.

I can upload todays backup if that might help? It is the BIOS Plutomaniac created but with the GbE region from the original BIOS. It has corrected GbE region (the correct mac address) but wrong UUID.

Re: Windows, this system is Win7 era and has a sticker on the case. That said, Windows has unregistered itself but I think that's because of the number of motherboard swaps and the number of mac address changes issue against a single installation of Windows 7. I'm 99% sure I can reactivate Windows using the telephone method once the hardware in this case is stable.

I haven't swapped in motherboard #2 to test your x3450.rom. I'll swap it in (or not) once we know where we stand with motherboard #1.

Thanks again for your help and support.


Jo0404
Same NIC error?

Zitat von davidm71 im Beitrag #42

---

Are the thermals all right on your board? Maybe its thermal protections shutting down the system?

---

yes, I got the same error message. After switching off and on, the message came back. After re flash with the backup that I had done, the system rebooted normally. it seems to me that the UUID has changed as described in my previous post. The MAC address is always incorrect. Just like after the first flash with the bin-file from plutomaniac.