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?

Zitat von Lost_N_BIOS im Beitrag #301

---

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 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.

Zitat von Lost_N_BIOS im Beitrag #303

---

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.

---

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

Zitat von Lost_N_BIOS im Beitrag #306

---

@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

---

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.

Zitat von Lost_N_BIOS im Beitrag #308

---

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.

---

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

Zitat von Lost_N_BIOS im Beitrag #310

---

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

---

Zitat von Fan im Beitrag #277

---

hey everyone, I found a easy blind flash way, this only need you have a stock bios. Rename the stock bios to GK5CN.BIN, put it into your FAT32 usb disk, and press Ctrl + Home when boot. And it will flash the GK5CN.BIN.

---

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????

Zitat von Lost_N_BIOS im Beitrag #313

---

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????

---

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