Oh 
Okay. BTW Laptop works without any problem. That’s nice to have people like you in this forum.
1 Like
Hello! I have screwed up my bios in the exact same way I think. Can you guys help me? @lfb6 please?
But i have a slightly different motherboard. I have a GL502VM with i7-6700HQ and a GTX1060 6GB I have already read the bios chip according to the discussions above.
Here is a drive link with the bios files: asus bios – Google Drive
What did you do exactly?
It happened last year but i just now got around to having time with figuring it out. So i flashed a modded bios with the same tool to enable the igpu and than looked around in the bios, changed some things and when i saved it, the laptop didn’t restart just cut the power to itself and after that didn’t post a single time, black screen and fans going, tried resetting the bios but that did nothing. I uploaded the rom dump that the modding tool created and the modded rom also, and the bios file which i read with a ch341
OK, so bios region mod.rom was working before changing settings.
Take the bricked bios dump, open it in UEFITool 0.28, expand, right click bios region “Replace as is”, choose your mod.rom, save as “new.rom”.
Compare structure and parser messages for “Bricked bios.bin” and “new.rom” with UEFIToolNE alpha 68.
Flash the file back with the CH341, read the chip again in a separate process, compare new chip content wit “new.rom”, if they’re 100% identical you should be good again.
The program i found when I searched for this is UEFIExtract NE A68 but I’m not really sure what I have to look for with this utility. I dragged both bios files on the program in file explorer and it made reports and stuff but I really don’t know what i’m doing
If I had meant UEFIExtract I would have written UEFIExtract
On the github page I found can’t find uefi tool ne a68 only a67 is that alright?
UEFItool_NE for extraction of the bios volumes and UEFItool regular version 0.28/0.25 for replacing.
Releases · LongSoft/UEFITool (github.com)
Sorry to hear that, i hope you’r going to fix this issue soon as possible. After that, I suggest you to lock your GPU at 0.700mV from MSI Afterburner. With this way it still consume more W than iGPU but… Your battery life will be longer.
That’s not a very precise test, just that the structure seems to be correct. The both firmwares will differ just in the bios region in NVRAM, that’s the first EFI volume in bios region, the one between the two paddings without GUID in its name. Attach the file if you feel unsure.
Now it’s just flashing the vreated firmware properly.
I looked at it but it would be great if you could look at it because I don’t really know anything about how bioses work and stuff. I uploaded the new.rom file to the drive folder i linked previously.
https://drive.google.com/drive/folders/14IG-fhJuFSW7VZ8B4GN1MUYFTgoLCVNn?usp=drive_link
Properly done- looks correct. If your machine worked when installing the modded bios region it should work now, too!
Good luck!
Hello lfb6,
I was wondering I you were able to work your magic on my exact same machine.
The problem on my side however may not entirely be NVRAM related.
Machine stopped booting after a UEFI Keys installation (that failed I belive).
I’ve followed everything on this thread (and some others) but with no success.
I leave here what I currently have:
- Two dumps of the contents of the BIOS chip.
- Latest FW from ASUS.
- The complete backup of my UEFI keys I made before trying to change them.
I would really appreciate some help/guidance.
Cheers
@ MPSO85
The static parts of the bios are identical to stock, the original keys are stored in nvram but are marked invalid, new / other keys were not installed!
Oh. Can that “invalid” thing be responsible for me not having output signal (or anything) when turned on?
I read that the Nvidia card output does require “valid” UEFI keys to work, somehow. It was a Notice on the Arch article I used when I tried to do Secure Boot signing. If this is the case, how do I fix this?
Any suggestions?
And thank you for your timely response.
NVRAM seems ‘a little’ corrupted, last entry shouldn’t be “invalid”.
Try this one, it’s simply NVRAM replaced by stock: dump.zip (5.5 MB)
You sir, are a god.
Thank you so very much. This one served me for many years and now will be joinning my personal fleet of home servers.
Glad to hear it worked 