@Lost_N_BIOS , so I boot into the files or can I do this on desktop?
@suikoden - You run from desktop, open command prompt (not power shell) at the folder location and run command for 32 and 64 for each version folder.
@Lost_N_BIOS , I am always getting "LoadDeviceDriver returned false. Error 1: Unable to load Driver"
For all versions? Are you running the command from the folder than contains the version you are trying to do at that time? It may not work, for any version, but not all should give you same error, if always same error something is done wrong (show me image of command ran and error)
Thanks @suikoden - I think maybe this is due to CMD prompt not ran as admin, sorry for not mentioning. Please run as Admin, select version folder, hold shift and press right click, choose open command window here.
If that does not make admin CMD prompt for you, you may need to right click from start menu and hold shift, then choose run as admin, then navigate via CD to the folder on your desktop with the files
@Lost_N_BIOS - It has worked now. Everything succesful except for the 32 command on the 5.03.1107 and the oldest version didn’t display any message.
Screenshots of the two attached
When I can find some time I’ll cook up some modded firmware for the GB X370 boards, time is short atm though.
Great @suikoden , now, upload that entire package back to me leaving all the NVRAM.txt in place where they are, so you know which version gave what output.
Thanks! @ket - I copied over someone’s mods from F22b to F24, but without user having a programmer it’s probably not best to have them test.
File sizes changed and new settings added in AMITSE and NVRAM main and inner, and those were the only two locations containing all of the mods edits.
Due to that, and the new settings/file size changes, I assumed it’s probably not best to use a mod with transfer like that anyway, even if it was bootable and worked, since it likely removed many of the fixes/changes from F22b to F24 update
@ket thank you very much for your work
@Lost_N_BIOS and what about the command that didn’t work or the ones that didn’t say anything?
will edit them in in the next few minutes
EDIT: here is the folder: https://mega.nz/#F!1e5zBawA!kBLUdZuPcOTTYrIVGNeeOw
It’s just something we try @suikoden it either works, or not, and only on some chipsets. That’s why I said leave everything in place, so you know which versions exactly are the ones that worked, if any.
This is with the F22b mod flashed in correct? If not, please reflash that version and do it all again 
Wow - 8.5MB return on a 516KB initial sent package? Will check and let you know if anything worthwhile.
*Edit - great, looks like several of the versions worked! Let me know question I asked above about if BIOS was F22b mod or not, if not please flash that version and then redo and rezip.
If it was F22b mod, great, thanks. Now flash to F24 final and repeat and send me the package back for it, so I can compare and change to match the F22b mod.
Oh, that was the F24, damn.
I’ll flash the F22b once I get home again
@suikoden - it’s OK, was that F24 final? If yes, great, I have one part of the puzzle now, just need the F22b part next. Flash f22b mod BIOS you were using before, then load optimized defaults, and set SATA/SSD stuff how you want and then boot to windows and run SCEWin again for f22b-mod set of NVRAM.txt
What do you need at offset 0x00e6dfff ? To get there, open file in hex and depending on app you can type 00e6dfff in top left corner somewhere and hit enter, or somewhere up in the file, edit, view menu at top you should find a go to address or jump to offset etc there you put 00e6dfff
Or you can scroll down to that location, start scrolling down and somewhere on screen you should see the digits going down as you scroll, it will also be on left side of hex digits too, like 1, 2, 3, 4 in a list, only hex starting at 0000000, then 0000010 etc
@Lost_N_BIOS i need to edit the offset so i can flash into it you said.
I can somehow just not find this offset am I dumb or what am I doing wrong. I tried Ctrl+F CTRL+G and scrolling and cannot find it
@Lost_N_BIOS if the file is larger than 16,777,216 bytes it will not work, AMD would have to do some restructuring for the new filesize to be valid.
@ket - I meant file sizes of modules was different, like AMITSE, AMITSE/SetupDATA, NVRAM main and one inside FW Volume, that’s all, not BIOS image itself.
@suikoden - offset to edit for F22b-mod BIOS, the $BDR starts at e6df9c, a bit past that is your edit location e6dfff (Sounds like you found it, otherwise how did you get that exact offset value, since it’s correct one?)
F24 final $BDR is at 00e76d2c and byte to edit is at 00e76d8f. What hex program are you using? Search for $BDR as text/string (Not Unicode), or use go to address or jump to etc and input those offsets.
@suikoden - see image here - [OFFER] Gigabyte GA-Z370-Aorus Gaming 7 BIOS mod (6)
Answer if you are still unsure >> 76d8fh
@Lost_N_BIOS - it worked, thanks! here it is for F22b mod https://mega.nz/#F!YDhGjYAS!bl-xbWbScT6_Nsp_cUSeKA