Well he said he tried clearing CMOS, which should be same/similar, but maybe he didn’t do it correctly or long enough?
ME version/package etc, what is that needed for with EFI AFU? He’s already on latest BIOS, unlocked, so ME would be same in stock and mod BIOS, and it’s not used for anything AFU/EFI.
Booting to EFI/Shell/AFU “Should” simply be a matter of exiting the BIOS correctly towards shell, or booting directly to shell/AFU EFI file from boot menu, depending on how these are setup
But yes, I think he can reset as you mentioned though, but it’s been a few days now, he disappeared? 
I am confusing AFU with FPT, the Intel FPT package is ME dependent correct? I think there would be more steps/keystrokes with an EFI Shell boot, and more chances of something more severely going wrong since you can set/change variables in an EFI shell environment that are permanent no? For example, I modified my PreAlloc memory for an intel gfx from 32Mb to 64Mb in order for it to work correctly in MacOS on an older HP Laptop, no matter how many times I flash a new Bios those values never change, its permanent, until I reset the variable. You could also do all of these BIOS modifications in your guide from an EFI shell with set variable command no? I actually would like to stay away from testing this blind method of flashing the Bios in an EFI shell and stick with FPT DOS.
I thought maybe so, but wasn’t sure 
Yes, FPT version needs to come from matching ME system tools package
You are correct, it would be more, and different key strokes, so you’d need to do it and write those down for him/others. But no, you wouldn’t be using shell in a manner where you’d accidentally change a variable like you considered, other commands would need to be type for that to start happening (setup_var)
For the AFU, you’d boot to shell and simply run F.NSH instead of F.BAT, same thing but it’s a batch file for EFI, open it in hex or notepad and you’ll see what I mean.
I agree, FPT DOS is best, but that’s only OK to use if you have a backup first.
Ok I will look into it, what would be the minimal command string(s) to use with F.NSH?
Guide to blind recovery of your OP Laptop that will only boot to black screen (No LCD Signal) using an EFI Shell and AFU Flash using your stock OP Bios.
You will need another PC obviously to format a USB flash drive as FAT32 and to place the EFI folder and files onto the flash drive.
https://www.dropbox.com/s/p7gaxzdeem35wc…%20LCD.zip?dl=0
@pcfr33k - thanks 
. This is the default command from F.NSH >> @AfuEfix64.efi GK5CN6XN109.ROM /p /b /capsule
I would just use that as it is. I still have not heard back again from @Pear - hope he didn’t give in so quickly and return the system without waiting for help to fix it
Mine flashed perfectly fine with "AfuEfix64.efi GK5CN6XN109.ROM /p /reboot" I don’t know what F.NSH is , look over my guide. Of course mine is a different rom. He will also need someone who has has not installed any addtional drives to boot to EFI shell to see if USB is FS0, FS1 or FS2, most likely FS1, my USB shows as FS2 because I have a second NvMe drive. So in my guide I mention this and how to mount it. From the help guide for EFI AFU it looks like I only needed to use /P for program and /reboot commands nothing else, and tested 100% working fine.
F.NSH is EFI batch file, so like when you are in DOS you can type F.bat for the stock batch file, this is same thing only for EFI. Sorry, I assumed you would have downloaded his BIOS package, I gave you link on post #295
So at step #8 in your guide he can just type f.nsh instead, but he’d also need other areas of your guide adjusted for that as well (since the f.nsh needs placed on the USB too (Root I assume)
However, yes, he can just follow your guide exactly as written too, especially since you’ve tested this method. f.nsh just types the command out for you, same as a batch file would in any DOS situation.
So after he mounts the flash drive he can just type "f.nsh" without the quotes and inside that file will be "AfuEfix64.efi GK5CN6XN109.ROM /p /reboot" without the quote of course. I can test that to, then revise the guide for a generic guide and one for him with his bios name already in f.nsh? I can also place his Bios file in the zip package to. I wonder if I can automate the mounting of the USB drive in the F.NSH or in the startup.nsh which he would change if its not FS1.
I’ll finish up Monday Night.
Yes, close, it runs this command for his BIOS >> AfuEfix64.efi GK5CN6XN109.ROM /p /b /capsule
You probably could auto mount, but hard to know without knowing what FSx that would be. Yes, that is his stock BIOS package in #295, so stock name in the command at F.NSH already
No rush, he’s disappeared, hopefully just busy for now and will be back soon
Wow this process is actually simpler than any other and now we have another way to recovery using the OP stock Bios and AFU, thanks for motivating me to test this new way and to write a short procedure, now we have a way to flash stock bios blindly using EFI Shell USB Boot and EFI AFU.
I just modified the startup.nsh had to remove the pause and added @FS1: to mount the removable (USB) drive and my guide says if that doesn’t work change FS1 to FS2. It would be a good idea for someone to test this to make sure the flash starts just put in a some fake bios name and if AFU does not start that means the mount point must be FS2, I am almost sure for whoever has a stock OP and did not add any additional boot drives with a filesystem it will most likely be an FS1 mount point.
Link for Pear:
https://www.dropbox.com/s/1jix7ag1jwv0hn…_Files.zip?dl=0
Does it need to be named exactly with that name or it just has to be 5 characters before the .bin? I added this to my different ways to recovery thread, also will this only work with the OP stock bios or will this work with your own Bios Backup using AFU or even a backup of a modified Bios using FPT? This also may be a better way if you have Secure boot enabled because the EFI Shell boot using AFU will only work if Secure Boot is disabled and if it is not its tricky but included what to do in my guide.
Nevermind you already said you need a stock bios but the naming for me its GK7CN.BIN not sure if the naming matters or not? I also wonder with Secure boot enabled and CSM enabled or disabled will matter with this simple method we don’t need any of the other methods 
Thanks @pcfr33k For your question to @Fan in my experience with other boards, when you can invoke a recovery like that, usually it does not matter if the BIOS is mod or stock it will take it but in this instance it may only take stock (?), as far as the recovery name it probably differs for each model.
Hopefully Fan will tell us where he pulled that from in the BIOS or which app gave the recovery name (Possibly Phoenix Tool)
So now that you’re familiar with this method, did you already consider and test to see if AFU EFI will flash a mod BIOS???
Well @Fan method doesn’t work for me, and yes Secure Boot needs to be disabled as far as I can tell? I will try now to see if we can flash a modified bios with EFI AFU, not optimistic, but hoping it will work.
Nope did not work the usual error secure rom unable to verify.
I did rename the rom from rom to bin I wonder if it should be rom? I will also change the name to GK5CN.bin to see, nope nothing to do with BIN or ROM or the filename that procedure does not work 
You may need to find the correct recovery name for your BIOS, try GK7CN6SN1 or GK7CN6S
Thanks for checking, thought maybe we’d get lucky , should have known better Na, bin/rom same/same to any BIOS app usually (except old AMI tools)
Someday, hopefully, I will have time to figure out how to break that AFUWin CMD line tool! I’m sure it can be done
Oh, I forgot to tell you my method is not good.
I found it is based on bios capsule update, so you could not use this to get recovery, because this need operational bios framwork.
I found this method on UEFI Tool, the bios include two recovery region, so there are two recovery methods, this is one. In the hex view of the region, I found the file name. so may be your model name is not the same.
I’m now finding another way to get blind flash by using bootblock,
this may no need operational bios, even we can flash our moded bios.
Thanks for the info @Fan
I’m wondering why the other unlocked guide has not blown up with comments and discussions/questions etc? Do you guys think I should change the title to the board names like GK5CN6Z etc, instead of the brand names, maybe more people would find in search results?
I mentioned months ago in the Notebook forum thread about unhiding Bios Menus I should go back there and mention you have completed the work with a guide. There will be more hits after that I am sure!!
I think @nimaim did post about it after I posted the guide, but maybe since the threads are so popular there things get buried very quickly.
I thought about joining there and posting the guide over there too, but that would detract from people coming over here and joining our discussions and I’m not sure I want another thread/forum to try and keep up with too.
How do I reset BIOS settings after an unsuccessful undervolt? I’ve tried removing the CMOS, battery and RAM’s overnight but didn’t work.
Fixed: If anyone has this problem, you have to turn off the system, press and hold Fn + D, then press and release the power button, keep on holding Fn + D for 30 seconds and you should see the screen turn on. I did this with the CMOS, battery and RAM plugged in.