Successfully patched Z170X-UD5 TH CFG Lock (MSR Ex02)

[canyondust]

Could you please elaborate a little more. I have for sure a locked MSR 0xE2 register (see attached picture).

Hi!
No picture attached.
Assuming you have already extracted the BIOS section and converted it to text, can you upload that text file?

EDIT: Picture now available

 

[obus]

Sure. Here we go.

 

[obus]

And here is the *.bin file if you need it.
And the firmware too.

 

[canyondust]

Sure. Here we go.

Looks like the only mention of CFG Lock in your image is:

CFG Lock, VarStoreInfo (VarOffset/VarName): 0x537, VarStore: 0x1

so you'd boot from the recommended Grub Shell USB key and type:

setup_var_3 0x537 0x00

 

[obus]

Thank's I will test that immediately.
Will report back in a while.

 

[canyondust]

Thank's I will test that immediately.
Will report back in a while.

Also, the reason you got multiple returns on the CFG lock is because the socket setup references a variable called SAPMCTL_CFG LOCK, which is of course NOT what you want

 

[obus]

Ok command "setup_var_3 0x537 0x00" in grub unfortunately didn't work.
Still Locked.

 

[canyondust]

Ok command "setup_var_3 0x537 0x00" in bruh unfortunately didn't work.
Still Locked.

I love that it autocorrected Grub to Bruh

But setup_var_3 DID work as a command?
if you type
"setup_var_3 0x537" it should tell you the state of that register. 0x1 (or 0x01) is locked, 0x0 (or 0x00) is unlocked. You can use this to test the variable after you've tried to change it.

SO:
setup_var_3 0x537 0x00 <- to set it
setup_var_3 0x537 <-to check it

if it checks at 0x00, but once you reboot it goes back, then something might be resetting it when you reboot, but I've never seen that happen before

 

[obus]

The command is working. "setup_var_3 0x537" didn't give what you expected "0x1 (or 0x01) is locked, 0x0 (or 0x00) is unlocked".
It gave the same message as the first one Iv'e tried see attached picture:

 

[canyondust]

The command is working. "setup_var_3 0x537" didn't give what you expected "0x1 (or 0x01) is locked, 0x0 (or 0x00) is unlocked".
It gave the same message as the first one Iv'e tried see attached picture:

interesting. you might be using a different grub shell than I? The one I use gives way more output than what you see there. I'll track it down.

EDIT: Try this one:

GitHub - datasone/grub-mod-setup_var: A modified grub allowing tweaking hidden BIOS settings.

A modified grub allowing tweaking hidden BIOS settings. - datasone/grub-mod-setup_var

github.com