@pipes80 - In your image at post #12 - test item 5713648
To unsupress that, edit >> 46 02 19 82 12 06 5D 11 01 00 >> Change to >> 46 0A 00 00 00 00 00 00 00 00
This = below, and removes the suppression and gray out if all at same time.
Suppress IF 0A 82
False (46 0A 00 00 00 00 00 00 00 00)
Then test, if you can see item in BIOS or not (ROOT menu that contains this setting must already be visible, or you need other edit to that first)
If you CAN see root menu that contains this setting, but the setting still not visible after above edit, then you need to do AMITSE/SetupData edit.
In AMITSE/SetupData BODY >> Search BA 0E, find the one with 7B 04 and 7C 04 near it, then edit the 15th byte after BA 0E, if 01, change to 07, if 09, change to 0F, if other show me and I will tell you
noi work this modified, 15h byte is 30 or i wrong byte
------------------
do you think it will enable this option if gray out 19 82?
@pipes80 - Sorry, I don’t understand your first comment at post #18? Ohh!
I see what you mean, you are in wrong model for the 15th byte stuff I mentioned at post #17, this is about Access Level Edit, this is done in AMITSE/SetupData module NOT Setup
I gave you the exact edit you need to make, directly in front of 05 91 7B 04 7C 04 BA 0E 01 00 AD 09 10 10 00 02 00 >> Edit >> 46 02 19 82 12 06 5D 11 01 00 >> Change to >> 46 0A 00 00 00 00 00 00 00 00
Then make BIOS, test and see if you can then see “test item 5713648” if not, then you also need to do AMITSE/SetupData Edit on top of that to change Access Level
Test this setup module edit by itself first! You may not need to edit AMITSE/SetupData to change Access Level.
Let me explain this edit above, see also, this post (#53+55) for more in-depth examples of this kind of edit
Before >>
Suppress If {0A 82}
TRUE {46 02}
Gray Out If {19 82}
QuestionID 0x115D equals value 0x1 {12 06 5D 11 01 00 }
After Edit >> we change ALL Suppress instruction If to false, and take up remaining space of all other variables/commands instead>>
Suppress If {0A 82}
FALSE {47 0A 00 00 00 00 00 00 00 00}
Other settings, we’re discussing in your other thread. The above only about the setting you asked about in #12 ("test item 5713648)
For other suppressed items, yes, you need to unsuppress and or ungray first too, then after that if still hidden you may also need access level edit on top of that (in AMITSE/SetupData)
Yes, that is the only place this is located, as I mentioned.
In post #17 I discuss TWO different edits (Change suppression & Change Access Level), in TWO different modules (Setup & AMITSE/SetupData).
Do first edit in setup only, then test. If still not visible, then do second one on top of that mod BIOS, in AMITSE/SetupData module.
Also Setup and SetupData (Actual >> AMITSE/SetupData) are not the same BIOS module at all! AMITSE/SetupData, you will find below AMITSE, or within expanded AMITSE module itself (some BIOS), usually near bottom of DXE volume (same volume w/ setup)
What you show in image above is Setup module, NOT SetupData - Don’t get these confused or mix them up while editing 
in amisetupdata body I cannot find the hexadecimal sequence, that option from unmodified bios is not visible
Please see my edits above, I edited probably 3-5 times while you were replying
That “sequence” is not in AMITSE/SetupData, not at all. Please read over what I wrote about AMITSE/SetupData and how to find/edit at post #17 (last sentence there is all there is about this, nothing else related to this in that post, only last line)
If you can’t get it figured out, let me know and I will do the edit, then send you before/after both modified modules so you can see the edit, and two BIOS to test (one with Setup edit only, and second with both Setup + AMITSE/SetupData edit)
Similar edit also explained in post #10, but for different BIOS setting
I’m not sure if that’s right, but offset 15h should be fifth value horizontally, counting offset value is 0, right? because if it is not so I need someone to explain to me a little bit to read the hexadecimal in the hex editing software, be patient friend but I’m a bit of a blind
You’re still mixing up the two different module edits I discussed. 15th byte edit comments do NOT apply to anything inside “Setup” module (Shown in your image, selected tab is “Setup” module)
Additionally, the bytes you have highlighted in the image are not used to locate/edit anything AMITSE/SetupData, and will not be found in there either. See post #17 for how to find area to edit in AMITSE/SetupData and what the 15th byte comment applies to after you locate this area
As mentioned, if you want, I will do both edits, and send you before/after files, so you can then see what is done and you will then understand right away
ok, if you want to change, after you send it to me I will try to understand the change because I have no idea where to look for the byte 15h
Here, please pay attention to how I extracted these modules, if you use them to insert into any BIOS. I extract setup PE32 “As-Is” and AMITSE/SetupData BODY, after expanded all the way with UEFITool, inside select SetupData and extract BODY.
This only important if you use these modules, otherwise you can extract/replace however you are used to.
Otherwise, just use these so you can compare side by side stock and Mod files, to see the edits.
http://s000.tinyupload.com/index.php?fil…868177934846405
Setup PE32 edit should be tested in mod BIOS by itself first
Then, if not visible, make new mod BIOS with both Setup PE32 & AMISTE/SetupData edit in BIOS at same time
I have find amitsesetupdata, i replace as body with uefitool, i flash with fpt command
--------------------------------
that modding no wrok, freeze my bios
@pipes80 - Sounds like you replaced incorrect module w/ wrong files, or incorrect module in incorrect way etc. The files are fine, it’s just user insert error
That’s why I said be careful if you used those files, I expected that would happen and hoped you would not insert them unless you were 100% sure how, asked for more info etc! 
Better you extract/replace your own files your own way, just use my files to look at side by side with hex editor, then make your own same edit.
If you want to know exactly what you did wrong, send me the file you flashed in and I will check it and let you know, show you in images etc
I assume probably you didn’t expand AMITSE/SetupData and select SetupData and then replace BODY. But, could be you replaced Setup PE32 as-is incorrectly (if you did not expand to PE32, select it, then replace as-is)
Hard to say, I’d have to see your file you flashed
Could also be UEFITool version used, if you have not already replaced these modules with version you are using and flashed a mod BIOS already and it’s OK (due to padding remove/add issue)
I have not checked if this BIOS has issues relating to that or not, suggest you use 25.0
Or, send me your original FPT BIOS region dump, and I will do the edit inserts for you if you want?
And, you should be following my instructions!! Setup edit only should have been tested first, what was the outcome of that edit/flash??
I will try as you told me but it is not new as a problem to not see the oc screen in the bios anymore … yes I expanded the pe32 as I always do and went directly to the pe32 image section and I replace the body and rebuilt
Please see edits above In files I sent, there is no “replace PE32 BODY”, only replace PE32 As-Is and that only applies to Setup PE32.
AMITSE/SetupData must be expand down to SetupData and then that exact module selected and replaced as BODY. Send me the file you edited and flashed, I will tell you what was wrong
Did you test the setup edit only by itself? Even if you tested earlier, before I sent you files. If yes, what happened with that ONLY?
What?? Sorry, what you mention about OC section, not sure what you mean? Or what BIOS you are using at that time etc.
same problem, freeze at oc opening schedule here my mod in picture
-------------------------
is the overclocking section of the bios
First image "Setupdata.bin" this is not setupdata anything, this is setup PE32, sounds like you are not replacing something correctly still.
Yes, I know what OC section of the BIOS is
Since you did not send me BIOS you edited to check… Are you flashing stock BIOS mod with M-Flash, or are you flashing FPT mod BIOS region? If FPT mod BIOS region, please send me your original FPT Dump, I will edit it.
If stock BIOS flash via M-Flash, let me know, I will make you two BIOS with setup edit to test something out about not being able to enter OC section of the BIOS
the setupdata image I compared it with yours and it is identical, so I don’t know, maybe the problem of the bios block is something else, I used both ways to flash the bios
Yes, but how you replace is the issue here I was thinking. And the file names, and folder names you are using to keep files in are incorrect (As I outlined above), so I’m sure this is causing some confusion on yoru end vs the actual BIOS and what I describe etc
Please send me the BIOS you flashed that messes up the BIOS, first one you made after I sent you files, then I can see if you are replacing wrong or not.
The issue may be the setup edit, but I need to check what you’re flashing first to rule that out. MSI BIOS picky sometimes, so setup edit may need to be different, but I can’t tell you for sure until I see what you flashed (or I send you stock BIOS I edited and you test and get same result)
This nothing to do with BIOS lock, that only blocks you from flashing if enabled.
So, are you going to send me your edit so I can check if you inserted my files I sent correctly, or do you want me to just make same edit and send you BIOS and you test and let me know if same outcome or not?
where i send the file bios compressed? is 10 MB?
---------------------
i send mega link https://mega.nz/file/rwpnRQjT#0lcaWowJ42…cG01IuTskr90E_M