Zitat von Lost_N_BIOS im Beitrag #149

---

If not, they're "UnderPowered" - tell em we said so! if they wont send you BIOS, tell them to at least update and correct the available 10GB download with proper latest BIOS

---

@nimaim - same/same there, best done with FPT. I am not sure, maybe AFU skips serial, UUID In backup, I know it leaves in place during flash over but that's by design. Someone would need to give me their serial, UUID and a FPT+AFU backup and I could compare and see.
I may already have all that from you early on, at least FPT backup, not sure if you specifically told me your UUID, Serial, LAN MAC ID etc (Usually that's not in BIOS region, but sometimes it is if no GbE region)
End user would have to edit specific BIOS regions to put in their board details before using, which same as purchasing programmer in advanced, many will not do it, think it's OK without, forget etc and then have issues/wonder why afterward and need help fixing without having a backup to get data from.
You know, even if he gave exact direction (extract this module this way, edit here in hex, add your details, remove this etc - many people wouldn't do, wouldn't understand how to do, need help with doing, ignore and so on.

In general, yes that is possible to do, and would be same as leaving his data in place as it is. Other board specific things are also stored in NVRAM (x2 volumes in a FPT backup), but those are less important to be concerned about.

Since there is only one year warranty on these, serial and UUID might not matter too much, still on stickers too anyway, but missing from BIOS or incorrect and warranty claim may make them deny RMA.
Sometimes these values also matter to windows activation, tied into SLIC during activation.

I'll add in secondary mod tonight to new link, with updated microcodes.

Few questions. From a stock vendor Bios after modding we should use the tools they provide to flash the modified bios and if not and we use FPT to flash won't that write over the mac address UUID etc details in the bios?

Using UEFItool right after opening the Bios image it looks like every GUID at root is the same that doesn't make any sense?

I am unsure which setup we Extract as is, is it the setup or AMITSEsetupdata? If its the "setup" module how did you find it by searching or any other way of finding it more quickly in UEFITool, see screenshots above? Also what is the microcodes all about? Is that missing from the modded Bios?

Sorry one more thing when I extract the AMITSE PE32 with IRFExtractor_0.3.5_win This is all I get, but the setup PE32 seems to have plenty of data in the text file.

@pcfr33k - flashing BIOS I am not sure, I would suggest trying the stock flashing tool/batch before anything else, that way all your system details are kept.
If you get security errors, then you may be forced to flash via FPT, but I've not seen anyone mention that with testing AMIBCP changes, few people here and over at notebookforums I seen comment on changing settings and no one mentioned having to flash a certain way with edited BIOS.
So I assume it's OK, but you will have to try and confirm to see what happens. If you are forced to flash via FPT, make a backup of the BIOS region first (FPTw -bios -d filename.bin) and edit that, then flash it back via FPTw -bios -f modfilename.bin.
In this instance, you cannot share the file otherwise it will overwrite your details to other systems.

To summarize, yes, if you use FPT, only what is in the file will be written, so if it's a stock BIOS with blank or generic serial or LAN that is what will be written, that's why you backup via FPT then edit, then reflash, and that is why I said you can't share that file with others.
If you flash via regular method, you can edit stock BIOS, share it with others etc. Only then, if they use FPT will get generic data overwritten, thus do not use FPT with stock BIOS unless you edit it first, and if stock flash tools/batch files work OK without error on modified BIOS.
If stock tools do work, then FPT should not be used for anything, unless it's your own personal backup edited and you prefer FPT for easier flashing or for whatever reason.

As of now, no one has sent me a complete BIOS dump via FPT or programmer, so I can't be sure, but usually LAN MAC ID is stored in GbE region, which is not touched during the above FPT commands, and all the files we've been posting, sharing, editing look to be "BIOS region" only.
Full BIOS dump would be 16MB, someone with programmer would need to send me a dump to confirm the LAN MAC ID is outside of BIOS region. I assume FD is locked, so without pinmod you can't dump entire BIOS via FPT (FD and ME would not be dumped), but someone can try >> FPTw -d bios.bin
If error, or still only 10MB dump, then it's only partial dump, programmer would be required or Pinmod to unlock FD and then dump entire BIOS.

On your questions about what to edit specifically, the second image above shows the correct AMITSE GUID B1DA0ADF-4F77-4070-A88E-BFFE1C60529A, that is what you extract PE32 as-is and edit.
Not AMITSE/SetupData under that, it's an entirely different GUID, that's where individual settings are stored when you change something in AMIBCP
Third image, "Setup" Yes, PE32 as-is there, and on both be sure you replace as-is too if you extract that way, or you can extract/replace "Body" too if you wanted, just make sure you put back same way you extract and both replace/remove after you pick a file shows same sizes in UEFITool.
First image, if you want more details on the GUID's, you can use UEFITool NE Alpha version to do your searching, extracting etc, view files via hex within UEFITool. I use that version for everything except actual edits, then to replace/remove files I use the regular version

For your last image, IFR question AMITSE does not give IFR, only the "setup" (not AMITSE SetupData, regular setup) in this instance gives you an IFR output to use.

@Lost_N_BIOS I can send you my full bios dump via PM later.. Also, Ive had no luck flashing these edits / mods via AFU. Always comes back with secure policy fail. I'm guessing this is because AMIBCP saves these edited files as unsecured. So in my testing, I HAD to use FPT, there was no other way. What this means for distribution, I don't know, does that mean we cannot share this latest one with the community LNB?

@nimaim - normally for modern BIOS, AFU is useless for mod BIOS, unless you can find certain working version/method per your BIOS. Did you try this method - https://linustechtips.com/main/topic/592...r-motherboards/
Download the files there, and then only pay attention to the flashing procedure. Yes, if this fails too, we need to find working AFU (I'll send you huge package), because it's not ideal at all to use FPT, you overwrite board details that way (And remove all personal NVRAM) as we've been discussing.
Yes, this is not good to share with everyone yet if FPT is only way to flash it, unless user dump then mod their own BIOS region (extract AMITSE PE32 and AMITSE SetupData as is, replace as-is using UEFITool) then flash back.

I was not aware of this issue, or we would have worked this out long ago. Now we need to figure it out! Did you try AFUDOS yet?

If we can't get it, we may have to make packages of modified files with images showing user how to modify a FPT BIOS region dump, then reflash.
Package coming your way via PM

Was thinking last night, maybe I can find and remove the security capsule, like they did for Asrock BIOS. Are you up for some crash course testing to help me find that @nimaim? If we find, then AFU flash should be fine with stock AFU Flasher.

* Edit - @nimaim - can you please test this package, flashing using AFU or the batch file contained (Stock batch, edited for file name only) Be ready for recovery, not high chance, but still... thanks from everyone for testing
http://s000.tinyupload.com/index.php?fil...443927254256181

Sorry LNB, I was very busy this weekend. I will try to test in the next few days. Laptop is currently back together too (had to take it to work for a bit) so will have to take that back apart, which is easy, but time consuming.

To answer your question, yes I've used both AFUWIN and AFUDOS to test flashing some of your BCP edits but it doesn't like it at all. Even your modded V5 with /GAN parameter didn't seem to work for me.

I already gave it a try and got a memory error, I just re-flashed with FPT before rebooting didn't need programmer. See if you get the same error 1d Error: Failed to load image into memory. It probably never flashed, actually it didn't ever flash, it was the read portion of AFUWIN64Gui.

@nimaim - Sounds like no need to test, I sent @pcfr33k similar edit for his model too.
Seems something else needs changed at same time probably, I'll look into it more when I can, I've also asked a few other specialist on the subject to look into it on another thread, so maybe they will be able to tell me what I'm missing.

Thanks guys ... obviously keep us all informed. @pcfr33k just to confirm, you are using AFUWINx64 to flash? What version? That way, I can test another path (e.g. AFUDOS). Also, what command line options are you using to flash it with? I think the default options tries to flash everything?

@Lost_N_BIOS do you know if there is a AFU linux version out that supports APTIO V5 and /GAN? I thought I saw one floating around somewhere but link was dead.

EDIT: From what I remember, with all the mods I've been testing using FPT with, I could not even flash the stock BIOS using AFU (same secure policy error). I guess it checks what's currently flashed and if it's properly signed? So maybe we should try to establish a baseline that works with the stock BIOS and AFU before we proceed further. I was trying to do this before I dumped the BIOS (for a pure "factory" backup) but I could not so I just flashed the stock BIOS with FPT -bios.

Using the one that Lost_N_BIOS provides with the package, same one you downloaded. I was going to try AFUDOS but not sure if that will work with Aptio5 Bios? I am sticking with AFUWIN64 GUI or the F.Bat file. DOn't want to test outside of that as most users would not want to either who aren't prepared to create a Rufus Caldera DOS flash boot etc etc.

Question for you about the changes you made to try to boot PEG only, were you still able to boot and boot only to black screen? If so I am working on automating a quick fix without having to re-flash with programmer so I can do multiple tests with changes in bios that will not brick bios and still boot even to black screen and not have to use the programmer every time.

Zitat von pcfr33k im Beitrag #162

---

Using the one that Lost_N_BIOS provides with the package, same one you downloaded. I was going to try AFUDOS but not sure if that will work with Aptio5 Bios? I am sticking with AFUWIN64 GUI or the F.Bat file. DOn't want to test outside of that as most users would not want to either who aren't prepared to create a Rufus Caldera DOS flash boot etc etc.

Question for you about the changes you made to try to boot PEG only, were you still able to boot and boot only to black screen? If so I am working on automating a quick fix without having to re-flash with programmer so I can do multiple tests with changes in bios that will not brick bios and still boot even to black screen and not have to use the programmer every time.

---

L0st_N_Bios made the settings in F.Bat he included /capsule. One more thing I am seeing GbE warning that region does not exist if I use DOS FPT or WINw64 same message. Do you see this when you flashed the unhidden menu bios? I did not notice really until recently.

@nimaim - you may be onto something, since you can't even reflash stock dump. Can you dump with AFU, the one included in stock package, GUI or command line version, and then flash it back (instead of FTP dump)?

/P would be the only thing necessary to flash back in the mod, it's main "BIOS" region, and that is all we are modding here. So yes, you can/should try only that since it's all that's required here.
Flashing stock package, and then immediately flashing mod package may help, similar to what you see in this guide outlined at end in flashing method - https://linustechtips.com/main/topic/592...r-motherboards/
May also be worth a shot to download that guides exact AFU and try that method exactly as outlined but with these stock and mod BIOS (not the ones I sent you guys for "Security" checks, the original mod BIOS from this menu mod only)
But, reading that guide, I think it may only be getting around "BIOS Lock" not the AFU Security, however I am not certain about that.

@pcfr33k - I did not include /capsule, only mentioned that as a test method for you to try if you wanted to see if it would work (anyone trying, be ready to recover!) And the switches in the batch files I sent to you both, are the ones from stock package, I didn't edit any of that.
As mentioned GbE warning can be ignored, it's informational letting you know GbE region is not included (Normal for FPT in certain situations) The only time you wont see it is if you are flashing entire BIOS (FPTw f -bios.bin) that includes GbE region (16MB BIOS flash/file - complete dump/reflash)