Zitat von Lost_N_BIOS im Beitrag #15

---

Thanks, most looks to be stock/invalid/placeholder info there. UUID can be tied to windows activation, but not always. Is windows still activated after you do windows update scan?

We could maybe guess month/year, but it could be made long time before launch/purchase too, hard to say. I just setup an Asus Z170 here and gathered it's info so I can see how it all compares to board stickers and BIOS dump.

Main thing is really LAN MAC ID, which is end of UUID, rest only needed to get corrected if your windows wont activate, or in case you need to RMA, but they may already deny that due to you moving/messing with the serial sticker.
Give me a bit, and I'll get this sorted out for you tonight probably

---

I'll pick some random data then for the rest of the UUID/Serial. From the board I'm using as comparison, I've found the data in dumped BIOS in 3 modules, and now I can see the format it's laid into the BIOS using too (UUID is a bit funky, partially backwards, but not all etc)
Serial sticker on board is not used at all in BIOS, long white sticker (first two chunks of #'s) is part of the BIOS Serial number + YY/MM at begining. UUID is random data now (As far as I can tell) + MAC at end
Give me about 15 minutes or so and I'll have a BIOS for you.

* Edit @MathiasMM - your BIOS layout is not exact same as I was using to compare with, it's missing some sections and volumes probably due to your using stock BIOS to recover. And I see the same comparing with an actual full dump from your board.
I have a dump from same system, I'll use that and rebuild you a complete BIOS, but it's only 3606 BIOS, can you flash that stock BIOS in from Asus, and send me BIOS region dump again using 3606, then I can make you full BIOS, then you can put in with FPT, once done, then re-update to 3805.
I think that is best way to do this, that way your UUID, serial and all that get put back in correct location and so that you have complete BIOS on there not partial as you have now (missing 1 NVRAM volume, 1 data padding file and 4 entire BIOS volumes)

Zitat von Lost_N_BIOS im Beitrag #17

---

* Edit @MathiasMM - your BIOS layout is not exact same as I was using to compare with, it's missing some sections and volumes probably due to your using stock BIOS to recover. And I see the same comparing with an actual full dump from your board.
I have a dump from same system, I'll use that and rebuild you a complete BIOS, but it's only 3606 BIOS, can you flash that stock BIOS in from Asus, and send me BIOS region dump again using 3606, then I can make you full BIOS, then you can put in with FPT, once done, then re-update to 3805.
I think that is best way to do this, that way your UUID, serial and all that get put back in correct location and so that you have complete BIOS on there not partial as you have now (missing 1 NVRAM volume, 1 data padding file and 4 entire BIOS volumes)

---

Crap, sorry I forgot about that, and 3606 from Asus download would not be complete either, it would be same/similar to the partial one you programmed in already (Missing same volumes etc). I will take this dump and fix it for you

YOu can't flash like that with FPT unless you have unlocked FD and a complete BIOS file (including FD, GbE, ME, BIOS regions, which is not available for download from Asus usually, but I did not check this boards stock BIOS package)
Checked what I had in storage, 1805 is complete, so 3606 may be as well, checking now.. All you need to flash is the BIOS region. I checked, 3606 is complete BIOS, but you can't flash full BIOS like that anyway due to security locks (FD locked/ME Locked, unless you unlocked that during your Pi recovery programming)

Open 3606.cap in UEFITool, expand down to BIOS region, select BIOS region itself and right click, choose extract, save as BIOSreg36.bin, then flash using FPT >> FPTw -bios -f biosreg36.bin

Then reboot, load optimized, set anything you need to set, then make new dump >> FPTw -bios -d biosreg3606.bin

After this, you will need to unlock BIOS lock via grub again before you can reflash the BIOS I will send you as final one (If you want, I can disable that in this BIOS, but it will be reset next time you reflash any stock BIOS)
Actually, I will send you full unlocked BIOS if you want, BIOS lock disabled and FD unlocked, but you'll have to program it on with programmer (Then above still applies about next stock flash, for BIOS lock anyway, not FD/ME that will remain unlocked)

You may need to unlock BIOS lock now too, sorry I thought you did before, but just remembered you used programmer to recover. Here's how to unlock it - [GUIDE] Grub Fix Intel FPT Error 368 - BIOS Lock Asus/Other Mod BIOS Flash
Or you can simply extract body from capsule of 3606 and program that on with your programmer, then send me FPT dump of BIOS region.

Then I'll sort this out. Sorry for all the hassles, but I think it's best to do this way so you get complete BIOS on there, not sure what it all does when there or causes being missing, but I'd want my BIOS to be properly complete so any instability I might have later I know wouldn't be due to this.
If you don't want to mess with all this though, and are happy/fine using the board as it is now, I can just send you back corrected GbE file which you can fix LAN MAC ID with, up to you?

Yeah, of course I can always flash it with the programmer, I'll probably just dump what I have now with the Pi, check that it reads something, and then try flashing full bios from you afterwards.
If that won't work, I should already have a programmer in the mail, but with the chinese new year and all, who knows when that'll happen...

I'll try to flash 3606, tonight, hopefully, and get back to you.

I need you to program in stock 3606, run it, and then dump region for me though (So NVRAM gets populated), then I can fix and send you full file again. I thought you programmer before already with your raspberry Pi?

I can just edit this dump I have of 3606, but it's got someone elses data in it, and I'd rather have clean NVRAM sections from your system and stock BIOS ran on it, but if it's a lot of hassle to do all this for you I can just edit this file (or the stock one)
Or, send you only the fixed GbE to correct your LAN. All up to you. Seeing 3606 stock now, I don't know how you got this partial 3805 BIOS on there, unless 3805 from Asus is partial and 3606 is not, I'll check now. Nope, 3805 is complete too, all volumes, pad file etc, not sure how your dumped region looks the way it does?

Seeing this now, and since you already flashed in a stock package once. Just wait, I will edit stock 3805 for you that you're using now, and you can program it in.

Please unlock BIOS Lock via grub using my guide above, you can start on step #6, because here >> your variable is >> 0x8A7
Rename the .efi file to >> Shell.efi

Maybe that being locked only allowed you to partially dump the BIOS region before?

To be honest, I have no idea how anything happened in this case, and you said that the Pi method did not always write to the chip, so I can't be sure that I already programmed with the PI :)

I'd prefer for everything to be sorte out, honestly. I'll just do an fpt flash of 3606 bios region, hope that it works and then I'll send you a dump of that.

See my edits above. And since it was bricked, and you recovered with Pi, it at least wrote in something good!

No need to 3606 stuff now, see my edited in thoughts above about 3805. We'll just do that, since I see it's complete too and you already blanked everything out anyway, no need to not do it that way. The only difference will be the second NVRAM volume will be missing, but it will be created on your end once you start the board
I have to run for now, but will work on 3805 full BIOS for you, please unlock your BIOS region for now as mentioned above. That way it's out of the way, and you can program in BIOS region in full via FPT, then program in GbE via FPT, and there wont be any need for programming via raspberry or flash programmer until/unless you want to program in the complete BIOS later for updated ME region and fully unlocked FD (That I'll put in the BIOS)

* Edit >> @MathiasMM - Here is fixed 3805 files, new system details are in the package, program both files with commands below

FPTw.exe -gbe -rewrite -f gbe.bin
FPTw.exe -bios -rewrite -f biosregion.bin

http://s000.tinyupload.com/index.php?fil...199240554452303

Then when programmer arrives, if you want, you can program in entire BIOS (Fixed.bin) to have the unlocked FD. That way, next time you want to update modified BIOS, or ME, you wont have any issues.
BIOS Lock is already disabled in this BIOS region, so that's done as soon as you flash it in

Zitat von Lost_N_BIOS im Beitrag #23

---

See my edits above. And since it was bricked, and you recovered with Pi, it at least wrote in something good!

No need to 3606 stuff now, see my edited in thoughts above about 3805. We'll just do that, since I see it's complete too and you already blanked everything out anyway, no need to not do it that way. The only difference will be the second NVRAM volume will be missing, but it will be created on your end once you start the board
I have to run for now, but will work on 3805 full BIOS for you, please unlock your BIOS region for now as mentioned above. That way it's out of the way, and you can program in BIOS region in full via FPT, then program in GbE via FPT, and there wont be any need for programming via raspberry or flash programmer until/unless you want to program in the complete BIOS later for updated ME region and fully unlocked FD (That I'll put in the BIOS)

* Edit >> @MathiasMM - Here is fixed 3805 files, new system details are in the package, program both files with commands below

FPTw.exe -gbe -rewrite -f gbe.bin
FPTw.exe -bios -rewrite -f biosregion.bin

http://s000.tinyupload.com/index.php?fil...199240554452303

Then when programmer arrives, if you want, you can program in entire BIOS (Fixed.bin) to have the unlocked FD. That way, next time you want to update modified BIOS, or ME, you wont have any issues.
BIOS Lock is already disabled in this BIOS region, so that's done as soon as you flash it in

---

You're welcome, and it's great all is working properly still @MathiasMM - You flashed the BIOS region using above command too correct? If yes, and you don't mind, can you dump that region for me now, so I can see if it's only partial like before, or if entire contents were written in this time (For my reference/peace of mind)
If you're done messing around now, it's OK

Zitat von Lost_N_BIOS im Beitrag #25

---

You're welcome, and it's great all is working properly still @MathiasMM - You flashed the BIOS region using above command too correct? If yes, and you don't mind, can you dump that region for me now, so I can see if it's only partial like before, or if entire contents were written in this time (For my reference/peace of mind)
If you're done messing around now, it's OK

---

Thanks @MathiasMM- that one is now complete BIOS region with all volumes as it should be! I don't know how it worked before with only half the regions in there??

Zitat von Lost_N_BIOS im Beitrag #27

---

Thanks @MathiasMM- that one is now complete BIOS region with all volumes as it should be! I don't know how it worked before with only half the regions in there??

---

Yes, I guess it must be a lot of fluff in there if it can run with only half the volumes it should have. And for sure, now you have programmer so you can recovery any time you run into issues again.

But, be sure next time, to make some backups first and try to have someone check them before you write anything, that way if system details are still there on the BIOS they can be recovered and put back into a new file before you write it

Sure, if the chip on my nex motherboard is removable, I'll probably just read it from the programmer before doing any upgrade or anything :)