@code9523 - you are too funny! >> “I know this partial BIOS wont work, I know it’s wrong size… But I flash it anyway” ??? Since you knew it was wrong size, and wouldn’t work, what did you think the outcome would be when flashing? Magic?
Yes, I would not use AFU on this system anyway, it’s Intel based so use Intel FPT. Don’t use blindly, ie without help, instructions, us telling you to do this or that, I’m only speaking in general here in regards to AFU or FPT and my preference.
You have a hardware flash programmer, so you really never need to use either of these, except maybe later once you get it all sorted and put back together, then I would use FPT for any flashing I needed to do.
About 16MB file? It could be broken, did they say it was working dump wherever you grabbed it from? I’ve not looked at or used any 16MB file for anything, and didn’t plan to either, so it doesn’t matter to me if it works or not.
But yes, if that is a working file, it would need BG disabled and ACM/BG entries removed from FIT before it could ever have a chance to work. And another but, it can’t work anyway due to production ME FW is there, so you can basically toss that out.
I may use it for what I mentioned above though, so please attach by themselves into a single zip/rar so I only have to download those if I need them later.
Now, I have tool to work with this BIOS properly, please wait, test BIOS coming soon
plutomaniac - Thanks for the FIT info, I tried old and new, but didn’t have one old enough I guess Thanks, that was all I really wanted to check in FIT, about the BG, I assumed you did but wasn’t sure and since he mentioned it at first post I wanted to check to be sure.
On the stock dumped region thoughts I mentioned, I only thought maybe an actual stock dumped region would = 8MB vs that HDR region, but yes if it’s same then same issue would be presented anyway.
Yes, I wanted to increase it due to UEFITool would not rebuild at a BIOS region swap only, and I’m not great at FD editing to resize region, so wasn’t sure if I could build it manually in hex and then correct the FD BIOS region size etc.
And now mentioning that, this would leave final file 31MB, so still 1MB too small, so something’s got to be corrected in my mind (as you mentioned, by build with FIT instead)I did consider FIT building too, but it wasn’t working for me yesterday so never made it that far.
I’ve never built a BIOS like that with FIT, changing region sizes etc, so this may be best done by you at first, unless you don’t want to do it? I will try now since you sent me that FIT
* Edit - I looked, and don’t see what I expected at Flash Layout, all sizes are zero, so lost on doing that with FIT - Edit 2, never mind, that ways easy, and not unexpected
** Edit - @code9523 - Here is BIOS to test, put on with programmer only
First test these two BIOS trying the 2017 one first - Straight stock region swap in - one with latest original included microcode for your CPU, other with 2017 microcode from BIOS at post #4 ACM/BG removed from FIT on ALL
Stock2017
Stock2019
Then if both fail to boot, test these BIOS again trying 2017 first. These are same as above but with your original NVRAM in place and old original Setup, AMISTE, AMITSE/SetupData, 2 x StdDefaults outside NVRAM swapped in
This much easier than NVRAM swap of setup entries in NVRAM - other way nearly impossible for me, takes hours to redo all NVRAM especially when there is 100’s of entries.
These may fail no matter what, for many various reasons related to the new/old swapping of the modules mentioned above, but also due to AMI Hash mismatch (Sometimes that cause any BIOS edit to fail, other times nothing)
Stock2017NV
Stock2019NV
http://s000.tinyupload.com/index.php?fil…731289720798234