I put all that text in spoiler. Picture I posted above is generic example of grub and setup_Var usage, I am trying to get you to go there/do that etc!

Nothing you show in image or long text list has anything to do with what I am telling you to do. Please follow my directions at post #34 for how to use grub and setup_var and use commands from post #41 I gave you.
Otherwise no progress will be made.

Okay!
I try to make bootusb of your direction!!

I check bios lock disabled from extractor default

Now make a bootusb !!

Then, I have a question

I used to uefi shell only check|See Value.

Bios value is modified by SPI program

Then, have a difference uefi shell between grub??

Difference means if i see value of Setup_var, then the result is difference of shell uefi and grub

Just, Question!!

UEFI Shell not part of this process, it shows you incorrect things, you proved this on post #41, stop using that for this BIOS
BIOS Lock question, I'm not sure what you mean, that's also unrelated to what you're trying to do here - if you mean from my guide, that way just what I wrote the guide to help people change that setting for Asus board using this method, you are changing other variables instead (The settings/variables you wanted to change, not BIOS Lock)

BIOS values/BIOS itself etc, is not modified at all with programmer or program. Grub and setup_var will change the variable live in current BIOS, no flashing or programming required. Yes, difference will always be between Shell and Grub, since Shell does not show you the correct things for changing these settings, on this particular BIOS.

So please forget about using Shell or RU etc, for now, only use Grub and Setup_var. Please! I can't say this many more times, otherwise I will just have to accept you don't want or need my help, since you stray from what I'm trying to help you do and try some other methods which are not working for you over and over again.

I am sure half our battles are probably due to language differences and translations etc Please just do as I mentioned, figure out how to get booted to grub and then use setup_Var with the commands I gave you in post #42 (Show me image of this screen once you enter both)

Thank you for your help!!

I get the grub shell and using set_var try to change value

but below image!!

i got "cant set variable using efi " ㅠㅠ

That's not the grub file from my guide, please use the one attached in my guide first. Where did you get the .efi file you are using?
The one in my guide might not work either, I know of two other modified ones for BIOS editing purposes, but you need to try the one in my guide first. Then show me image of it same way, input commands and output given.

I found the shell file in the guide and booted it.

I got your shell.efi file from your guide and booted it.

Grub shell version == 2.00+20130519

Great, sad to see same result though, but thank you for checking to be sure.

Now, please test these grubs one at a time using Setup_var2 and Setup_var3 instead (Same variable ID's, just different command)
Use only Setup_Var2 with the one in that folder, and only Setup_Var3 with the one in that folder. See if any change, or same for each one

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


Also, lets try this - Please download all three versions of H2OUVE from here, and run the following commands from each of the versions and see if we can get any output files
https://github.com/mikebdp2/Insider_BIOS_Tools

H2OUVE.exe -gv vars.txt
H2OUVE.exe -gs -all Setup.txt

H2OUVE.exe -gv vars.txt
H2OUVE.exe -gs -all Setup.txt

this command occur error "IHISI Get platform info fail in SMI!"

and setup_var2, 3 have a same error "error can't set variable using efi (error : 0x8)"

ㅠㅠ

Do you get the above error "platform info fail in SMI" with all three versions of H20UVE?

Can you setup_var (any version) variable 0x9 (Default is 0x1 to put back), try change to 0x2 (Firmware config "test" instead of production) To see if you can then see advanced menu with the DCI setting

Here is the problem, this BIOS is internally RSA Signed as I suspected when you first tested the mod BIOS I sent you (with DCI setting change)
https://www.bios-mods.com/forum/Thread-R...hitelist-Unlock

nothing can be done here with this, time to forget about that and use another system for whatever your plans were with this one.
Microcode, ME, and NVRAM are only things outside of the secure sections that can be changed