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
@Lost_N_BIOS
Well, if your experience says that BV - 1.30 / .34 should write properly, this way I suggest using the last dump I’ve attached here.
BV ID / 1.34 .bin
-------------
Yeah, you got it right. I know it’s crazy but otherwise it doesn’t want to work: 00/FF or couldn’t find the chip.
-------------
I remember you answered someone about some SOIC clips from a certain brand that makes quality clips - I tried to search in my country but I didn’t find it, I will find that comment of yours and then I will see if I can find it on the net.
-------------
I’m not sure about that, I googled to find some info about pros/cons of unlocking BIOS but I couldn’t find anything informative.
x. Does unlocking the BIOS somehow affect its security?
If not, then it is possible to unlock it, although it is not mandatory because I don’t really think the hidden features will be useful to me
-------------
Thanks a lot, bro! Thank you a LOT!
@EthanWalker - OK, I will grab that dump
Maybe bad cable connection somewhere, or one of the pins tips slid up into the clip a little and wasn’t connecting right?
Pomona 5250 - But when you use this you have to make your own cables, or purchase long Dupont M/F cables (or a large set like x120 of short ones and connect them together)
Here is example, but you can probably get cheaper on ebay or other places - https://www.amazon.com/CPT-063-Test-Clip…a/dp/B00HHH65T4
About the menu unlock, I meant I’m sure I can probably unlock it (or already have) No, what this does is allow you access to all the hidden BIOS settings, so you have a full BIOS menu instead of a limited one.
But yeah, if you don’t think you need any hidden settings, then you may not want it.
You’re welcome, good vibes from my way to you, always!!
* Edit - Hey! So, I go to put your dump into the folder I have for this Asus, and I already have a folder from you for this model from 2019???
But, it looks like I stopped working on that mid-way through, what happened back then?
All SOIC8 clips I bought, came with issues.
In any case, holding the pins with fingers, although complicated - works much better than attaching and detaching the clip thousands of times to receive errors in the final result. ;D
Well, in my case, the price is not a big problem BUT patience may be a problem because I’m kinda tired to wait for looooong time deliveries of SOIC8 clips
I will try a few thousand more times to connect and check if the connection with programmer is OK - if not, I will try the DIY method with Pomona 5250.
I don’t even know what hidden features it unlocks - if the main features are Oveclocking option: in this case, don’t even loose your time to unlock it 
If there are some useful features, in that case: Yes, please unlock it, but as I said before, this is not mandatory - NVMe is my priority.
Thank you, buddy!
-----------------------
and Here we go again
Well, you sent me already a modded Bios with all the benefits included, I mean the NVMe mod and microcodes - and I flashed it with AFU (following another user’s method here and somehow ignoring your FPT method because I didn’t have a programmer)
The bios was flashed succesfully * but it also brought negative results, for example: the keyboard backlight stopped working + other side effects. (you advised us that AFU method will broke the bios)
So, then you asked me to buy a programmer and dump the BIOS, and send it to you.
*** I tried a thousand of times, couldn’t get it done properly - - - disease - - - Now I’m back, ready to continue the mission X.
@EthanWalker - Ahh, well then you need a Pomona clip, no problems with those, easy and quick!
Well, menu unlock stuff would be up to you to decide if you need or not. Some people want for OC if/when possible, others want to change graphics memory, or memory timings etc.
Those are the main things people usually want unlock menu for, or also voltages.
Ahh, OK, thanks for explaining what happened before. I also have “programmer dump” from you on 7/2019 too, as well as a BIOS region dump (from unknown, AFU or FPT)
So, to fix the KB backlight issue, do you know if any of those three files are from before this happened with the KB backlight? I assume it’s still not working now, correct?
I’ll read back and check out our discussion about all this I know you can fix this on some systems with software, so I’ll have to see if you did try that or not already etc
OK, I see in post #30 (last post on page 2) Svan fixed his backlight via >> AFUDOS backup.bin /N /GAN
Do that with your original FPT or AFU dump, from before you flashed in the MOD BIOS. Then after KB backlight working, I will make you new BIOS based on new FPT dump I will help you to make (or you can programmer dump again, up to you?)
@Lost_N_BIOS
just to not loose our time with insignificant things: Don’t unlock Bios, let’s focus on NVMe and Microcodes.
The BIOS region dump was obtained with FPT.
Then I messed up the keyboard with AFU.
Then I remember that I flashed it again, to recover the backlight (but I have no idea how I did this, and what method I used - I would love to take a look into the conversation but I need to go to work - didn’t sleep all night)
EDIT:
Yes, I followed the SVAN’s method and backup’d via AFUDOS.
Thank you very much for your time and efforts, buddy!
OK, it’s not a problem to do, only adds a few minutes, but if you don’t need we can skip for now
See my edit above when you get back, it will help you fix the backlight. Then we’ll make a new dump via FPT or programmer, then I will do the mods to that new dump.
Get some sleep, no rush here You’re welcome, always happy when I can help!
No, I recovered my backlight with AFUDOS already.
No, I can’t sleep, I have to go to work )))
So, I have to check my folder with dumps, I don’t remember which one is the original - or maybe I will read the entire topic and I’ll find it 
@EthanWalker - Ohh! So, backlight is already working, in the programmer dump you sent me now? If yes << To that, then no need for you to do anything, I just need to redo the mods for you, then you program back in
Sorry, I read that backwards, thought you needed to sleep from working all night. OK, well then get to work before your late
@Lost_N_BIOS
Yep, I recovered it with AFUDOS method and backlight is working. There are still some other issues but not so significant: the computer starts itself when I plug the charger (it is power up without pressing the Power Button) + sometimes it doesn’t boot up from USB devices.
Try reflash of latest BIOS using stock method to fix those issues, or it may be normal? If you do this, you’ll have to send me new dump, if it fixed those things, otherwise you’ll program back in the problem if I use this dump now.
Or, have you already tried that previously?
I think I tried that already but not remember the result:
1. I tried and that didn’t fix the issues
or
2. I tried but I couldn’t reflash because I was getting an error, something like: this version (the stock) is too old bla bla.
Sincerely I don’t remember, I will check our conversation later because I remember I wrote something about this.
Anw, I’m ok with these because the laptop is working great. The fact that it boots up without power button, doesn’t bother me at all (the delay on boot is a bit annoying but since it doesn’t affect the performance, I’m OK with this)
Delay on boot may be due to messed up ME FW, I will clean and update that when I redo the mods.
@Lost_N_BIOS
So, to avoid confusing and unclear situations, I peered through the thread to refresh my memory and remember the steps I took.
Long story short:
You modded my BIOS, adding the following changes:
- EFI RST 14.8.2.2397
- oRom RST 14.8.2.2397 TRIM Mod
- NVME + M.2 Mod Insert
- All microcodes removed in main volume except updated 40661
- All original microcodes remain in secondary (last) volume >> updated I flashed it with AFU - and messed up the Keyboard backlight. You explained me that AFU brings various problems and partially corrupts the BIOS.
Then you suggested me to Fix the keyboard backlight with AFU - and then, after I get the programmer (which I didn’t have yet) - to dump the BIOS and send it to you.
I fixed the keyboard backlight with AFU. I couldn’t dump because of the faulty programmer… After 1 year I came back - and dumped the BIOS using the 1.34 version of software and BV ID (post #106)
That’s it 
So, you want to try and fix the FPT issue, correct? Anything else, or just that?
I am not 100% sure best/easiest way to do that, may be we force downgrade you to stock older BIOS, then you re-update to latest again via stock method.
It’s too bad there is not a newer BIOS out yet, that would be a lot easier to do I think
When you try to re-update stock BIOS using stock method, what is the “stock method” to update this BIOS, and what is the exact error you get (be exact)
Can you update BIOS from within the BIOS, or is it only the “live Update” software? I see, when choosing win8.1, “windows BIOS update Utility” software, is that what you tried to use? If not, try that, and see what error it gives you, if any
Same for “Live Update” app, if that has BIOS update feature, also try that and see if it will let you reflash latest stock BIOS again or not.
Best to try and reflash stock, using some non-AFU method, before we do anything with programmer
Can you see ME FW version on BIOS main page, also check with HWINFO64 as shown below
I’m not sure if I know what’s the FPT issue.
After I fixed the keyboard with AFU - you said to dump the BIOS and send the dump. Now what is the FPT issue, I don’t really know. 
The stock method is flashing with WinFlash tool from the Asus website - the Live Update doesn’t have this feature, I mean upgrade/downgrade BIOS etc.
And if I’m not wrong, there is a way to flash via BIOS menu.
• So, should I try to flash with WinFlash to get there error ? I got it right ?
• When you say Reflash stock - you mean the BIOS update from the website, right ?
Yes, the ME version is showing up:
Intel ME Version: 9.0, Build 1482, Hot Fix 30
:::UPDATE:::
The WinFlash tool says - the BIOS file is older than my current version.