The latest beta bios to the Z87 Pro3 3.20 has already the AMI NVMe by default, no mod needed.
Thank you, I’ll try that instead! I looked at the description before and didn’t notice NVMe mentioned so I didn’t try it…
Hello.
Excuse me for requesting a support, I have a problem with a 1 pad file being removed by MMTool Aptio 4.50.0023 in an image from a root volume 00 while modifying a DXE child volume 01:00-00.
I’ve found this corruption while validating the change using a UEFITool.
Modified image was never flashed.
Please advise.
HP Compaq Elite 8300 SFF Intel Q77 Express
BIOS K01 v03.08
Source BIOS file K01_0308.BIN link for download
Original OEM installation package
Volume of the pad file:
ZeroVector:
46 4C 53 48 4B 30 31 30
33 2E 30 38 20 20 68 84
FileSystem GUID: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Full size: 3C0000h (3932160)
Header size: 48h (72)
Body size: 3BFFB8h (3932088)
Revision: 2
Attributes: 0003FEFFh
Erase polarity: 1
Pad file removed by MMTool:
File GUID: E4536585-7909-4A60-B5C6-ECDEA6EBFB54
Type: F0h
Attributes: 00h
Full size: 18h (24)
Header size: 18h (24)
Body size: 0h (0)
State: F8h
Header checksum: 86h
Data checksum: AAh
Screenshot of the pad file in the source image viewed from UEFITool:
Use the UEFI tool method instead of the AMI tool. Compare again the 2 images with UEFI tool.
Thanks for the suggestion.
I’ve just tried the UEFITool and it seems that it may corrupt the image because I’m unable to flash it due to an error while the original image file is flashing fine probably due to an unexpected discrepancy between an original one and a modified one by UEFITool.
Modification was performed using 0.28.0 release, result visually seems to be correct when comparing an original image with a modified one.
When comparing the differences using an UEFITool NE A59 release that doesn’t have a modification engine, root volume of a BIOS region receives a Text field value: UsedSpace. Original file doesn’t have any text.
Difference between Information area
Original:
Fixed: Yes
Base: AF0000h
Header address: FFAF0000h
Data address: FFAF0048h
Offset: 60000h
ZeroVector:
46 4C 53 48 4B 30 31 30
33 2E 30 38 40 40 1E 00
Signature: _FVH
FileSystem GUID: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Full size: 3C0000h (3932160)
Header size: 48h (72)
Body size: 3BFFB8h (3932088)
Revision: 2
Attributes: 0003FEFFh
Erase polarity: 1
Checksum: 5A81h, valid
Modified:
Fixed: Yes
Base: AF0000h
Header address: FFAF0000h
Data address: FFAF0048h
Offset: 60000h
ZeroVector:
46 4C 53 48 4B 30 31 30
33 2E 30 38 20 20 68 84
Signature: _FVH
FileSystem GUID: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Full size: 3C0000h (3932160)
Header size: 48h (72)
Body size: 3BFFB8h (3932088)
Revision: 2
Attributes: 0003FEFFh
Erase polarity: 1
Checksum: F657h, valid
I’m trying to flash it through a BIOS/UEFI Utility menu - there is an option to flash an image file.
Flasher starts to read the image and throws an error without any informative description.
Original image flashes fine.
Do I have to try to flash the modified image using the suggested tools like UBU or the resulting image is corrupted?
Edit:
I’ve corrected the ZeroVector and a Checksum of the root volume (file system), now it doesn’t have a UsedSpace text. However, the image still unable to be flashed.
Will try to flash it with UBU or something else.
@Thump
This is the thread about how to modify an AMI UEFI BIOS. Users, who want to know how to get a modded BIOS properly flashed, should read the start post of >this< thread and post their problem into the linked thread.
Sure, but can you please clarify if a modification of ZeroVector of the filesystem is OK?
It seems that UEFITool 0.28.0 always do this for my image file.
@Thump
If the UEFITool v0.28 is not able to insert the NVMe module without touching other BIOS modules, you should either change the in-use BIOS modding tool (e.g. by choosing one of the MMTool versions) or change the specific NVMe module (e.g. by inserting the “small” variant).
Please follow strictly the guide and don’t try to invent anything new.
MMTool removes the pad file in my case.
The problem isn’t connected with a module size: same UEFITools behavior in case of removal any module or even rebuild-only.
I just done it (NvmExpressDxe_4.ffs) with MMtool 4.x, PAD is preserved, but NOT with UEFItool 0.25/0.28 (CORRECTED)
Now as bios mod flash… users tend to forget that its a modified file that the OEM/BIOS security has a role here…they dont like those files.
Besides the last resource of using an SPI programmer, some HP motherboards can allow the mod by using the FPT tool, but it must have access to bios regions for writing, so do the mod from a FPT tool dump and mod it.
The access to bios regions on some motherboards could be already unlocked or not, manual unlock is needed or using (on some HP boards) the ME/SPI jumper to get this “unlocked” dump.
Now using the search box in this forum ( Search results for ‘Elite 8300’ - Win-Raid Forum (level1techs.com)), you will get several post in witch you can see all this and follow other users experiences, determine witch method can solve the mod flash issue, that its normal and happens a lot in OEM/Branded machines.
Hello everyone,
Thanks for your help. I am now able to boot on W10 from my SSD! 
Finally, i removed some DxE drivers by following tips from BIOS Guru CodeRush. Many room was available, then i add NvmExpressDxe_5.ffs and I also unlocked some bios menus with AMIBCP v4.53
Here is the bios i use now (for ROG G771JM) Modded203_bios.zip (2.1 MB)
For W10 installation, i try to clone fresh installation without success (using clonezilla): SSD was visible in the bios + it was booting from SSD 
, but then BSOD appears 
1st time i got SSD visible in the bios and almost W10 booting from NVME SSD!
so new fresh installation of W10-21H2 on the SSD (w/ USB and MediaCreationTool) => works perfectly 
Here is a crytaldiskmark test with the 500GB SSD (samsung SSD 980)
My 2016 laptop is running better than before (maybe faster than when it was new)
Thanks @MeatWar, @Fernando for your support and answers! This forum is awesome! Big thumbs up to this community !
2 Likes
Hello, I just modified my BIOS file to insert the NVMe module (NvmExpressDxe_Small) without problems following the steps of this guide.
The latest version is 213, but it is already applied in the BIOS.
Can I change the modified ext from 213 to 214? Won’t the BIOS be unusable?
I would greatly appreciate your support.
Original: 2.29 MB file on MEGA
Modded: 2.16 MB file on MEGA
@skull001
Welcome to the Win-RAID Forum!
Your NVMe modded BIOS seems to be fine and ready for being flashed.
Regarding the procedure how to flash a modded ASUS UEFI BIOS please look into the first post of >this< thread.
Good luck!
Dieter (alias Fernando)
hello, I modified my BIOS file to insert the NVMe module (NvmExpressDxe5) following the steps of this guide. And complete flash bios on laptop vaio svp11 with comand “afudos ‘bios-name’.rom /GAN” (afudos v3.04).
But my laptop still can’t use the nvme ssd hard drive. Please help me.
Original: link
Modded: link
Your mod seems correct, now follow the guide from Fernando, @ point#9: [HowTo] Get full NVMe support for all Systems with an AMI UEFI BIOS - Special Topics / NVMe Support for old Systems - Win-Raid Forum (level1techs.com)
i i finished flashing. But still cant use nvme ssd.
@haklet
Welcome to the Win-RAID Forum!
What does “can’t use the nvme ssd” mean?
Did you follow my guide by booting off off an USB Flash drive containing a clean Win10/11 Image?
Are you sure, that your BIOS flashing was successful?
Do you see a device named “PATA” listed as bootable device within the BIOS (after having enabled CSM)?
Good luck!
Dieter (alias Fernando)
@Fernando
Thank for answers.
What does “can’t use the nvme ssd” mean?
i mean my laptop not recognized nvme ssd
Did you follow my guide by booting off off an USB Flash drive containing a clean Win10/11 Image?
i followed your guide step by step.
Are you sure, that your BIOS flashing was successful?
i sure my bios successful flash
Do you see a device named “PATA” listed as bootable device within the BIOS (after having enabled CSM)?
i dont see a device named “PATA” and my bios dont have CSM menu.
@hakiet
Thanks for the answers. Here are the next ones:
- How did you check whether the OS of your laptop detects the NVMe SSD?
- Which OS are you running on the laptop?
- Which NVMe SSD (manufacturer and model) did you connect to the laptop?
That’s a relatively old Haswell Laptop, all reviews I could find say it has an M2 SATA slot. I heavily doubt that this laptot ever will recognize a NVME disk?
Please give the full laptop model!