@ Fernando

Thank you sir for replying back.
per you instruction on this page Guide for ASUS mainboards with an AMI UEFI BIOS
[Guide] How to flash a modded AMI UEFI BIOS

i tryied the option
A) witch after freshly formatted about 8 USB Flash Drive drive from 32MB Fat to 16GB FAT 32 did not work for me. when i hit the Flashback button on the board it will light up for time and just go dead. i try that about 8 to 10 times no luck.
B) try to flash the modded bios with freshly formatted fat32 drives but it's keep giving me error " Selected file is not a EFI BIOS!) (error attached)

Please advise...

The correct name file of the mod bios should be: M5A99FX.cap
for Bios Flash Back operation, a small USB 2.0 fat32, after press BFB button if the led stays ON fixed, get another USB drive.
During BFB operation led will blink and it will take some time, with led flashing increasing until it stops. Depending on bios and model can take several minutes.
Seems that Fernando was quicker than me...

Alright, when I flashed with AFUWINx64_v3.05.04 I received a ROM size error. I also tried to flash it with the EZ Flash 2 Utility from within BIOS itself. THere I got a Security Verification failure. I'm wondering about re-modding with the smaller NVMe DXE. THoughts?

Cheers,
RAWEast

Thanks for the quick reply.

I ran AFUWINx64 in a CMD window I started with administrator rights. I first put the origional BIOS file in the same directory as the AFU utility and named it as per usual, p8z77vlx.cap, then ran the utility. (afuwinx64.exe p8z77vlx.cap) It ran without errors.
Next I removed the CAP file and copied the modded BIOS file into the directory named as p8z77vlx.rom and ran the AFU (afuwinx64.exe p8z77vlx. /gan)
I am using Wingows 10 64 bit so I used afuwinx64 v3.05.04.
I took a screen shot of the dialogue.

Cheers,

Hi, I've only added the NVMe module to the BIOS. Yes, both the pre and post modified BIOS's are exactly the same size. I did try the AI Suite, and it seemed to load the BIOS OK, but no change in the access to the NVMe.

I'm leaning toward starting the whole process over from the start. Perhaps I did something out of sequence. I used to go nuts looking for errors in the SYSGEN file on TNSII systems in the 80's.

Any other ideas?

Cheers,

Nope, nada. I also tried loading windows to the NVME, nogo.

OK, Then let me try downing it to an earlier version. At least that will confirm the ability to flash and be demonstrated by the version reported.

That went smoothly. Was able to downgrade from 2501 to the previous version 2403. So, at least that confirms the BIOS flash process is not the issue.

I'll do a little research and see what else I can confirm.... Unless you have a rabbit in your hat. :)

Cheers,
RAWEast

Hey Fernando, Thank you again for your help. It is much appreciated.

While I have not yet booted from the drive, it is in cloning process as I type. The issue was with the flashing. It was able to get it flashed using the AI Suite. One small detail in the process was not picked up on during the late night endeavors. I missed the step of replacing the image file after the AI Suite Update utility verified the file but before selecting the flash command.
I have some data migration and organizing to do, but so far, it looks like a done deal. The PATA_SS option is now available.

Stay Safe

Cheers,
RAWEast

Followed exaclty the steps, but with no luck. First updating the bios i got "security flash failed" but after that i just open and saved (doing notging else) with UBU software succeded to update the bios with the correct information but no PATA was inserted on BOOT devices.
Motherboard: ASROCK H81 Pro BTC R.2