@awaulin - Do not reboot, write back your original BIOS region dump with FPT or AFU, then reboot will be OK
This is due to you flashed BIOS with AFU in past Nothing you can do to fix this now except you can flash BIOS I sent you with AFU (Use >> AFU /P /B /N at least)
If you want to fix this system to where you can use FPT properly, then you need flash programmer.

Also, I never suggested to use FPTw64, only FPTw or DOS version. Anyway, nothing can fix the problem with FPT until you get programmer, so no need to try anymore. All this covered on page 4
Sorry, I didn't know you'd previously flashed BIOS with AFU

If I understand correctly, then I must first flash the original region with AFU /P /B /N in DOS, and then the BIOS you provided using AFU /P /B /N?

@awaulin - If you already revived the system via recovery, you don't need to do anything now. What I would try, so you don't have to use AFU again, is recover with the BIOS I sent you.
I may need to put that back into a capsule for you, for recovery method to work, not sure. Just in case, here is that file (try original mod w/ recovery first, if that fails, try this) - http://s000.tinyupload.com/index.php?fil...769169291393549

But yes, if you need to flash the BIOS I sent you, since you already used AFU in the past, you have to flash via AFU (Windows or DOS, whichever AFU version you've been using that allowed you to flash mod BIOS) >> AFU /P /B /N
No need to flash original BIOS with AFU, you can do that with EZ Flash or whatever stock tools/method is, but it's not needed here.

Recovery does not work with both mods. Only stock firmware work with recovery.
I note that EZ Flash also does not see these files...
Flash first mod with AFU /P /B /N - that work fine.
Many, Many Thanks!!

Try both files I sent you with .bin extension instead of .213, for recovery. It may not work, but worth it to try, since you got it to flash stock BIOS for recovery.
EZ Flash will not flash mod BIOS, this is a given.

Or, so, did you get it flashed in now, and NVME Mod BIOS in to I mean? You're welcome!
If yes, good, I was hoping to help you not have to AFU Flash it, but I know that's what everyone runs too (And you see the issues it causes already here with you and on page 4 too) But yes, already too late for you, so it didn't really matter

I tried recovery with both files. Recovery does not work. And work with stock BIOS.
As i see Recovery procedure uses EZ Flash for write BIOS.
I can only write your Mod with AFU.
But it does work! Thanks!

@Lost_N_BIOS: I tried hard to read the topic a little bit on the weekend. I managed to read the bios (did not seem blocked) and attach it here. I've never worked with AFUDOS or flashed a BIOS at all (except on the default path), but I hope I'll manage it :-)

TW

@Torchwood - See post #3, do that, then make me FPT BIOS region dump using info below (Must do post #3 first)

Check BIOS main page and see if ME FW version is shown, if not then download HWINFO64 and on the large window on left side, expand motherboard and find ME area, inside that get the ME Firmware version.
Once you have that, go to this thread and in the section "C" download the matching ME System Tools Package (ie if ME FW version = 10.x get V10 package, if 9.0-9.1 get V9.1 package, if 9.5 or above get V9.5 package etc)
Intel Management Engine: Drivers, Firmware & System Tools

Once downloaded, inside you will find Flash Programming Tool folder, and inside that a Windows or Win/Win32 folder. Select that Win folder, hold shift and press right click, choose open command window here (Not power shell).
At the command prompt type the following command and send me the created file to modify >> FPTw.exe -bios -d biosreg.bin

Right after you do that, try to write back the BIOS Region dump and see if you get any error, if you do show me image of the command entered and the error given >> FPTw.exe -bios -f biosreg.bin
^^ This is important step, don't forget ^^


If you are stuck on Win10 and cannot easily get command prompt, and method I mentioned above does not work for you, here is some links that should help
Or, copy all contents from the Flash Programming Tool \ DOS folder to the root of a USB Bootable disk and do the dump from DOS (FPT.exe -bios -d biosreg.bin)
https://www.windowscentral.com/how-add-c...creators-update
https://www.windowscentral.com/add-open-...menu-windows-10
https://www.laptopmag.com/articles/open-...ator-privileges

Or here is simply registry edit that adds "Open command window here as Administrator" to the right click menu
Double-click to install, reboot after install may be required
http://s000.tinyupload.com/index.php?fil...134606820377175


Then, tell me what you want done to the BIOS

Warning, I am a complete noob to bios modding!

@Lost_N_BIOS

Hi! So I was excited to install my new Samsung 970 EVO NVMeM.2 SSD into my Asus G751YJ-DH71 as a bootable drive thinking, “it has a PCIe SSDin it already so this should just plug-in-play” ...oh was I wrong. After a few days of research, and reading this forum thread over a few times, it sounds like the BIOS needs to be modded to support the NVMe SSD…With all your warnings and saying how much of a pain this BIOS was to mod, I have been reluctant to attempt this on my own. And if I understand it correctly, the mod needs to be done using on my own bios dump and not someone else’s.

So, I followed your instructions to get the tools and create the attached bios dump. I also was able to follow your instructions to use Grub to fix the FPT vars to flash a new bios using FPT. Now I think all I need is to flash a "correctly" modded bios...is this something you can help me with?

System Info:
Asus G751YJ-DH71
Bios Version: 213
Intel Core i7-4710HQ (Intel HM87 – Lynx Point)

After more extensive reading, and since I was only looking to get my hard drive working, I was able to update my bios to support NVMe and install the 970 EVO using the information in this thread and in the ROG-G751-JY-BIOS-211-NVMe-Upgrade-Guide-Step-by-Step thread on the Asus forum. Instead of using the tools listed in the other forum, however, I used FPT for backup and flashing.

Thanks for all your work in this thread!

I tried this and for the most part...works.....but....I have noticed at LEAST once a week a blue screen of death.

Hi, is anyone active here?

@Lost_N_BIOS
I apologize for the disappearance and for not leaving any message.
I went through that disease that everyone is afraid of, I haven't even touched my laptop since then - because my vision and priorities have changed radically.
Now that I've recovered, I found some time to buy a new CH341A programmer and a new SOIC8 clip, so I managed to dump Bios.

I dumped with versions 1.29, 1.34 and 1.38 (although it may sound silly but I thought that maybe there will be a difference - but no, all the dumps obtained are equal)

In addition, I dumped both the 25Q64FV chip series (this being engraved on the chip) and the 25Q64BV (according to your indication).
I compared them all in the HEX editor. Absolutely all dumps are equal.

Here is what I got:



Is it possible to do something ?
25Q64FV dump.bin

Thanks a lot in advance!

@tsnyder321 - Sorry, I did not see your post until now I will make you BIOS tonight
Ohh wait, you got it sorted out? If yes, great work! Sorry I missed helping you

@Blackwind - Sounds like you need to tweak some BIOS settings still if you have OC CPU or memory, that or you may have some windows driver issues or something.
Test stock BIOS for a few weeks and see if same, or mod BIOS, but at stock CPU/Memory settings to rule those changes out if you made any.

@EthanWalker - I am always active here, but also always buried trying to help with all the new incoming threads each day too, so
Sorry to hear you had the virus, but it's GREAT to hear you are OK and made it through!!!!

The main issue is more about writing to chip, often many software may read OK. For W25Q64FV use 1.30 or 1.34 and W25Q64BV ID - Or Colibri
Send me (only this, limited internet) dump you made with 1.34 and BV ID, then I will edit, and you write back using 1.30 or 1.34 and BV ID too or write will fail.
* Edit - OK, I see your BIOS file above in your edit now, thanks. So if all files = 100% match at read, great, I just need any single one. But make sure you do write back with info above

Refresh me, what do you need done to BIOS, thanks
Again, very happy to know you are healthy and doing better now!!

@Lost_N_BIOS
Just to confirm, so as not to do anything stupid, as I did with AFU last time
You want me to send you a dump made with this ID: 25Q64BV - and with program version 1.30 or 1.34, right?

• I wanted to add NVMe support to my G751JY and update microcodes - these are the main modification I need.
• But I'm not against some other improvements.

P.S I had cancer
Thanks buddy for the kind words and encouragement, I appreciate that
---------------------------------------

@Lost_N_BIOS

Made it with 1.34 because 1.30 says I'm violating him somehow )))
It is so hard to do... My clip started giving me the most-known troubles... So, I took out the pins from the SOIC clip and I connected each wire and held it with my fingers

BV 1.34.bin

@EthanWalker - First of all, sorry for my confusion! I assumed you meant coronavirus due to the way you said that, I didn't expect or even think of cancer.
Very sorry to hear that happened!! Hope you have a full recovery and quick long lasting remission!! Stay strong, and keep yourself surrounded with love!

So, since you said ALL the dumps you made with all the various versions were 100% hex match, all those are OK and same/same and all those versions can apparently "read" from this chip without issue.
In my own personal testing, and others here, I know only 1.30 or 1.34 with BV ID will write properly (But, I can't remember what all I tested that failed, and I can't find that thread anymore now where I posted results/info/images etc )

In regards to 1.30 and Access violation error can be ignored, carry on and it's fine What do you mean you took out the pins and held 8x pins by hand?? Crazy!
Hope you have a good clip to use to write. Sorry for any confusion there, I planned to just grab your dump you attached above, since you said all were 100% hex match, no new dump was needed.
So, which dump do you want me to use now? I can't compare them, since they wont match previous one due to being taken at different times, so you have to decide if you feel this one is for sure dumped OK or use previous.

I've not looked in the model folder yet, but I assume I can probably unlock BIOS menu for you to if you want that?
If not, then NVME mod + update microcodes