@Frustrated
Either use extracted bios_region or body extraction for mod working file, both serve the same purpose, the goal here is remove the CAP header of 2Kb, avoid breaking signature (MMtool).
This header must be restored for USB BfB ONLY, the resulting file (CAP) will NOT be useful in EZflash on bios setup, this is ALWAYS valid for working with body extraction or bios_region.
I completely overlooked your link to UEFI tools github⦠So should I use the latest version which I can see youāre using in the screenshots above? Or should I stick to the older versions you list in that last screenshot?
2: Open MMTool 4.5.0 and load the *.rom file created in past step, and add NvmExpressDxe_5.ffs
3: Make sure the driver (NvmExpressDxe_5.ffs) got inserted before saving
4: Open UEFITool A71 again and extract bios region from the modded *.rom file made with MMTool in previous step
5: Open the original biosfile.cap with UEFITool V0.28.0 and add the modded bios region
6: Save as āM7G.CAPā
7: Load onto USB drive and insert to āROG Connectā USB port and press + hold āROG Connectā button for 3 seconds.
8: Diode doesnāt start to blink as described in the mobo manual, it just shines solid green, which (as far as I have googled myself to know) means ābios file not acceptedā. Correction: It does start to blink when I press the correct button, but only three times slowly, and then one time quick, then stops.
Iām using a Sandisk 32GB USB 3.0 pen formatted as FAT32.
Ty! Although, I would appreciate to make it on my own. I donāt know which version you have used here i.e. (I donāt want the beta).
But could you spot anything I did wrong in my screenshots/list?
Small USB disk as possible, even better a 2.0
Oh⦠Hm. I think I might have one somewhere.
Edit:
I just realised that Iāve been pressing the Clr CMOS button, not the rog connect
I tried again with my own modded bios, and now it blinks 3 times, and then turns off.
Youāre probably right that I need to try with a different usb drive.
Edit 2:
Just tried with the standard untouched bios update. Itās the exact same thing. So I guess the USB drive is to blame after all. Can you recommend something known to work? Itās the same bios version as is already installed though. I donāt know if that could cause problems?
Its a common issue know on Asus USB BFB, the USB disk, the format, the name or board has an issue.
PSU off, cold Reset (CMOS Battery off), a couple of minutes to drain, 1 DIMM only and try it again.
@MeatWar which bios revision did you use for this build? I noticed you had the latest ābetaā open in your screenshots. Iām not really that excited about installing that version, so just checking to be sure.
Optional mod flash using non-CAPSULE file, in this guide
Well⦠itās is the last and BETA, dont like it, do it yourself, thatās all from me, good luck.
Well thatās what Iām trying to, but Iāve tried to get a confirmation if Iām doing it right three times now, and you still havenāt answered?
thatās all from me, good luck.
lol okayā¦
To be honest, if the guide told people āwhyā instead of just ādo thisā it would be a lot easier to understand.
Example: Why do you use two different versions of UEFITool? You still havenāt answered that either, despite it being asked earlier by other users. Really not making it less confusing.
Well if the mod was badly done, already was toldā¦, but your issue is flashing the modā¦
Seems your USB BFB function is out of order since you cant even falsh an Original Asus file, so it leaves the option linked using a non- CAp fileā¦what else dont you understand or whats wrong in the guides???
told people WHAT???
DIDNT YOU SAW the screenshot? CANT YOU FXXX read that the NE is used FOR EXTRACTION and the regular for swapp operations???
Do you know HOW MANY users did succedd using this guide⦠I LOST COUNT and NEVER HAD IT, do you want me to SAY the issue hereā¦by using the correct words???
I forgot to say it worked with a different USB i found today. MB.
So now I just wanted to make sure my own mod was properly made before trying again, as I donāt want the beta bios.
DIDNT YOU SAW the screenshot? CANT YOU FXXX read that the NE is used FOR EXTRACTION and the regular for swapp operations???
First off, calm down mate. Thereās no need to get rude.
Incredibly childish behaviour, especially from a moderator.
What Iām asking here is, why two different revisions of the apparently same software, is needed? I think there might be a language barrier here, judging from your replies. Hope this makes better sense.
Hi Fernado,
I sign this community to say thank you for your modded bios.
This bios is working well, while flashing bios, it reflect that NVME module update.
NVME is working well but it s strange that no PATA or PATA_SS visible under boot section.
while choosing boot priority, it does not reflect nvme anywhere but strange thing is that bios displays windows boot manager and it boots from nvme.
NVME detects in PCI Express X16 Gen 3.0 slot only.
it does not reflect in PCI Express X1 Gen 2.0 slot.
@reyan
Welcome to the Win-Raid Forum!
Yes, I have developed and verified the success of this specific method to get boot support for any NVMe SSD by simply inserting 1 NVMe module into the DXE Driver Volume of any AMI UEFI BIOS, but there are still differences to modern BIOSes with natively full NVMe support.
Nevertheless it made me happy being able to help owners of an old PC or Laptop system to use an NVMe SSD as bootable system drive. Not even our BIOS Guru CodeRush thought in April 2015, that my method would work (please read the second post of this thread).
If you see such āerrorā messages even after having opened an extracted original (untouched) HP BIOS file, there is nothing to worry about regarding the flash of a BIOS, where the only modification has been the insertion of the missing NVMe module.
You have to use the option "Insert afterā¦
For me the insertion of the NVMe module into the HP BIOS by using the UEFITool worked fine:
Thanks,i was able to insert and create modified bios. Now when i flashed that bios back i get no display and get caps lock 2 long and 2 short (corrupted bios), tried with normal and small nvme with same result. Flashed back stock bios and working normal.
hp nvme.rar (8.0 MB) normal nvme and small included
@Crijopoga
Thanks for your interesting feedback!
Meanwhile I have checked your modded BIOS, where you have inserted the āsmallā NVMe module. Your modification work seems to be well done.
After having thought about the possible reasons why your HP system didnāt work after having flashed your modded BIOS, I had only these 2 ideas:
a) The specific and obviously not completely AMI compatible HP BIOS structure (details not visible with any MMTool, error messages given by the UEFITool) may have prevented a proper integration of the NVMe module.
b) Maybe we both havenāt integrated the module into the correct location at the end of the DXE Driver BIOS Volume. The problem of this specific BIOS is, that the end of this Volume is not clear. Maybe the Module/Volume with the GUID starting with 9EF18CEE belongs to it as well.
Then I made a test with the AMI MMTool 4, which knows the best, where the 100% correct place for an added DXE Driver is (but unfortunately doesnāt show the exact location by opening the original HP BIOS).
I inserted the small NVMe module into the second (highlighted) of the listed Volumes.
Here is the picture:
After having inserted the module this way and saved the modded BIOS, I opened it with the UEFITool.
Surprisingly I got this picture, which shows the related part of the BIOS:
As you can see, the AMI MMTool has inserted the NVMe module twice (before and after the GUID 9EF18CEE module)
It is up to you to decide, whether you want to flash such modified BIOS.
Anyway I wish you good luck!