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

[iLikeHackintosh]

Don't waste yours or others time!
Please read important post about the matter on this thread:

• How to change hidden CFG Lock setting

 

[canyondust]

Don't waste yours or others time!
Please read important post about the matter on this thread:

• How to change hidden CFG Lock setting

What is this in relation to?

 

[iLikeHackintosh]

What is this in relation to?

Related to many posts/quetions on this thread, which are already answered in How to change hidden CFG Lock setting.

Maybe you can update your initial post by adding this link, so everyone can read these instructions without asking same questions again and again.

 

[canyondust]

Fantastic idea. I’ll do it as soon as I’m at a computer.

 

[iLikeHackintosh]

just checked your new updates bios on my board, extracted it and load UEFItool and see that nothing changed:

I suppose you misunderstood entire concept there. I recommend to read more about UEFI and how it works. To patch AMI BIOS you need AMI BIOS Configuration Program, which enables to modify parameters in a BIOS ROM without rebuilding from source. Then you flash your motherboard with patched BIOS. But setup_var isn't for patching BIOS, its for reading/writing UEFI configuration. Even Windows boot loader has special GUI for editing those variables. But some variables are not accessible via GUI. That's why you need this setup_var utility.

 

[MAC_OS]

I suppose you misunderstood entire concept there. I recommend to read more about UEFI and how it works. To patch AMI BIOS you need AMI BIOS Configuration Program, which enables to modify parameters in a BIOS ROM without rebuilding from source. Then you flash your motherboard with patched BIOS. But setup_var isn't for patching BIOS, its for reading/writing UEFI configuration. Even Windows boot loader has special GUI for editing those variables. But some variables are not accessible via GUI. That's why you need this setup_var utility.

yeah thanks, now I understand that setup_var is only for reading/writing UEFI configuration, therefor now I need your advice, so here is my result, please tell me it's correct or not, because it's looks same as yours uploaded-image in post #16

this is image from my last result using setup_var_3 0x4EF 0x00 which gave as this:
Too small Setup variable detected, ignoring.

 

[iLikeHackintosh]

therefor now I need your advice

Please read How to change hidden CFG Lock setting carefully. You have all answers there

 

[canyondust]

For the record, I definitely did NOT use Setup_Var_3. I possibly used Setup_Var2 though, I honestly can't remember.
And I do consider my patch successful as verified by VerifyMsrE02.efi

 

[lordstar]

For the record, I definitely did NOT use Setup_Var_3. I possibly used Setup_Var2 though, I honestly can't remember. And I do consider my patch successful as verified by VerifyMsrE02.efi

thanks, I will try it, but only Setup_Var2 or Setup_Var_2? and how you then verified by VerifyMsrE02.efi ?

 

[canyondust]

I either used setup_var or setup_var2, definitely no second underscore and no _3 (they might work but I didn’t use them)