[REQUEST] Asus GL504GW Bios Unlock

[Lost_N_BIOS]

Sorry I didn't make that more clear! Yes, I need to see error so I can tell you how to get around it if possible, before I send you back mod BIOS

So, error 167 is a pain, sometimes. Usually I can get variables for you to unlock this via grub and setup_var, but your BIOS the setup module I can't get valid IFR output from to see all the setting variables I even checked the other old BIOS too, sometimes this happens, I don't know if it's due to some error with the IFR tools, or Asus blocks it somehow but it's very rare when this happens so I think maybe some error causes it.

First, lets see if the easy way can get you around it (a BIOS bug). Put the system to sleep (S3) for one minute, then wake it up and try the FPT flash again, do you get same error or flash successful now?

If not, then you may need flash programmer, unless you can find other thread here or in google that mentions which AFU version allows flashing mod BIOS onto this model. Or, I can send you one simple test mod BIOS to try flashing using this method, download the files in this guide, but then only pay attention to last spoiler for flashing method.
https://linustechtips.com/main/topic/592...herboards/

Let me know outcome of S3 sleep test, if it fails too, then I will send you mod BIOS with one updated CPU microcode and you can try above method to see if it will let you flash or not.

IVAR!!!! I have a feeling someone is going to kill him soon as crazy as he's been acting
I worry Floki might do something and get killed too, or commit suicide or something, he's getting bad end of the stick lately

[feluchi]

Usually I can get variables for you to unlock this via grub and setup_var, but your BIOS the setup module I can't get valid IFR output from to see all the setting variables  I even checked the other old BIOS too, sometimes this happens, I don't know if it's due to some error with the IFR tools, or Asus blocks it somehow but it's very rare when this happens so I think maybe some error causes it.

This is for you:
https://www.sendspace.com/file/6c0810

This is valid IFR output from his file biosreg.bin

[Lost_N_BIOS]

Thank you Feluchi!!! How do you get it from files like this when that happens? I tried many ways, extracting module different, using MMTool or UEFITool etc.
I can't give you rep, it's still broken (magically I made it work today!!!) I really appreciate it, hope you can tell me how you get it, I run into this issue sometimes, it's rare but it does happen from time to time

RocoCoco90 - Before trying below, try the sleep bug I mentioned - put system to S3 sleep for one minute, then wake it up and try the FPT flash again, if it fails then carry on with below.

Here is guide I made, you can start at step 6 because I've gathered the variables you need to edit for you already
https://www.win-raid.com/t3908f16-GUIDE-Grub-Setup-Var-Guide-Fix-Intel-FPT-Error-BIOS-Lock-Bit-Set-HSFS-W-Asus-or-Other-Mod-BIOS.html

Rename your .efi file to >> Shell.efi

You need to change the following variables.
BIOS Lock >> 0xB47
Flash Protection Range Registers (FPRR) >> 0x1201

So, at grub prompt, you will enter the following one at a time.
setup_var 0xB47 0x0
setup_var 0x1201 0x0

Then reboot and try FPT flash again.

If this fails and you still get error 167, then let me know I will send you simple edit so you can test the method I linked in post #10 at linustechtips

[RocoCoco90]

Thank you Feluchi!!!  How do you get it from files like this when that happens?  I tried many ways, extracting module different, using MMTool or UEFITool etc.
I can't give you rep, it's still broken  (magically I made it work today!!!)  I really appreciate it, hope you can tell me how you get it, I run into this issue sometimes, it's rare but it does happen from time to time

RocoCoco90 - Before trying below,  try the sleep bug I mentioned  - put system to S3 sleep for one minute, then wake it up and try the FPT flash again, if it fails then carry on with below.

Here is guide I made, you can start at step 6 because I've gathered the variables you need to edit for you already
https://www.win-raid.com/t3908f16-GUIDE-Grub-Setup-Var-Guide-Fix-Intel-FPT-Error-BIOS-Lock-Bit-Set-HSFS-W-Asus-or-Other-Mod-BIOS.html

Rename your .efi file to >> Shell.efi

You need to change the following variables.
BIOS Lock  >>  0xB47
Flash Protection Range Registers (FPRR) >> 0x1201

So, at grub prompt, you will enter the following one at a time.
setup_var 0xB47 0x0
setup_var 0x1201 0x0

Then reboot and try FPT flash again.  

If this fails and you still get error 167, then let me know I will send you simple edit so you can test the method I linked in post #10 at linustechtips

Sorry I have no responded in a few days, I was swamped at work and also dealing with solving issues on my main desktop PC. I just bought all new EKWB rads and pumps that I had to get up and running.

[RocoCoco90]

I am still getting the 167 error after trying the sleep method.

[RocoCoco90]

Ok I did everything you said and FPTw.exe -bios -f biosreg.bin has worked! I have attached the screenshot of the success.

https://ibb.co/jT1MzXN

[Lost_N_BIOS]

No problem about a delay in reply, I'm always behind too. Hope you are enjoying the new rads!

FPT Success! Now I will make you unlocked BIOS, please wait

Quick test of a single setting change instead of BIOS unlock for now, flash this via >> FPTw.exe -bios -f OCPMTest.bin
http://s000.tinyupload.com/index.php?fil...4349238968

Do you get OverClocking Performance Menu now or no? If no, on your Main BIOS page, what does it show at the bottom for Access Level?
If yes, can you show me images of all the memory related settings you can see, so I can unhide any still missing (This is all you needed, correct?)

[RocoCoco90]

No problem about a delay in reply, I'm always behind too.  Hope you are enjoying the new rads!

FPT Success!  Now I will make you unlocked BIOS, please wait

Quick test of a single setting change instead of BIOS unlock for now, flash this via >> FPTw.exe -bios -f OCPMTest.bin
http://s000.tinyupload.com/index.php?fil...4349238968

Do you get OverClocking Performance Menu now or no?  If no, on your Main BIOS page, what does it show at the bottom for Access Level?
If yes, can you show me images of all the memory related settings you can see, so I can unhide any still missing (This is all you needed, correct?)

I am not sure I did it right, I flashed it through the Command Prompt in windows and rebooted into my bios and saw no change in the menu. Was I supposed to do it via the GRUB method booting from the USB? Also the access level in the Main bios page says Administrator. A;so I went back into windows and tried to reflash FPTw.exe -bios -f OCPMTest.bin thinking I might have done something wrong the first time and now I am getting the 167 error again.

Yes the new rads are great. I did my first ITX build in a NZXT H200I case that I modified. I have a 240 45mm rad in the front with 3 80cfm fans in push pull, and a rear 120 45mm with 1 80cfm fan. I delided my 9900k and replace the solder with liquid metal and am doing direct die cooling with der8auers OC frame in a fully custom loop. The other specs are 16gb of 4266 ram and a 2080ti also in that custom loop. I can post pictures once it's done, I'm still waiting on my powered RGB splitter because apparently you can't daisy chain RGB splitters off a mother board header.

[RocoCoco90]

Any idea why the FPTw.exe -bios -f OCPMTest.bin failed the second time?

[Lost_N_BIOS]

First, did you use Admin Command prompt? If not, then maybe didn't' flash, it must be administrator command prompt, not regular CMD prompt, or powershell.

If it doesn't show up after successful above flash method is used, then this is normal, as I mentioned that was only a test to see if a single settings change allowed it to show up or not, or if further edits are needed. Since you get error 167 again, sounds like you flashed it in properly, and this test failed. Thanks for letting me know 167 showed back up, I will attempt to set that to disabled on subsequent test files I send you.

Wow, that is a lot of rads! I used to WC, but only had one 240 on CPU, with 4 fans, and even with slower fans it got to be too loud for me so I went back to air.

I will make you new BIOS to test tonight, please wait and do nothing