@raven1234 - FPT from windows starts, you must run it from the command line as you mentioned on the third line of your report

The error with FPT and making backup is due to some of your BIOS regions being locked (FD or ME or both). All explained here - [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing
FPT from DOS not working for you may be due to your DOS setup, I've seen rufus mentioned a few times with issues so it may not be best method. I suggest using this method - <Request> Flagship X470 Gaming 7 Wifi Motherboard BIOS Fix

Please post an image of meinfowin from command line. You may need to either purchase a CH341A flash programmer and jumper cable, or program the "BIOS Region" only if you are locked out of the rest.
You will need the tools mentioned there if you wanted to update the ME region any time in the future, this does not apply to your NVME mod as that's in the "BIOS Region" only. I can give better answer once you show meinfowin report

To flash the "BIOS Region only", which you shouldn't be locked out of doing, use the following command from command prompt with FPTw (not x64 version, same applies with AFU don't use x64, just the windows version)

1. First backup "BIOS Region" >> fptw -bios -d biosregion.bin
2. Then flash the "BIOS Region" only >> fptw -rewrite -bios -savemac -f N751JKAS.205.M1

If you get argument error with the above, remove -savemac switch, we can fix later from your backup.

So, these methods in Asus section did not work for you, mainly AISuite or Asus Live Update (Win8 section of downloads for your system), when switching out files, change file name to match w/ one you switch out. Or USB Flashback method, rename BIOS to N751JK.205 or N751JK.rom?
[Guide] How to flash a modded AMI UEFI BIOS

Zitat von Lost_N_BIOS im Beitrag #3329

---

@raven1234 - FPT from windows starts, you must run it from the command line as you mentioned on the third line of your report

---

Hi Fernando,

Thanks again truly for your attention and help on this. After I flash the BIOS, and reboot the server, it doesn't boot back up so I'm not able to get into the BIOS settings afterwards. These are the exact steps I'm taking:

1) Logging into IPMI via web based IP for Supermicro
2) I go to Maintenance - Bios update and upload the modded BIOS
3) This is a screenshot of the BIOS update before I click on Start Upgrade. I leave "Preserve SMBIOS" checked because of what I've read on keeping it. https://imgur.com/a/wyBN2Zh
4) After the flash, it ask if I want to reset the machine and I select yes. The machine gets rebooted and that's where the KVM console then shows a black screen and machine doesn't boot up.
When it fails, I then go back into IPMI and flash the old BIOS and reboot the machine. The KVM console then shows the server as booting up correctly with the original BIOS.

I've attached both the original and the modded BIOS here. Thanks again

Hi Fernando,

Thanks allot for the contribution links, I tried those this morning with some help and could not get it to work either. I did notice after flashing using the guide above instead of via the IPMI flash, that when it completed there was an error on the bottom of the screen https://imgur.com/a/7HJJIKG My guess is that this just doesn't work for my mother board.

Thanks again for all of your help on this


To you or anyone who's able to contribute a successful modded BIOS for the X9DRi-LN4F+ (It uses the X9DR3P5 BIOS ) https://www.supermicro.com/products/moth...X9DRi-LN4F_.cfm I would be more than thankful and happy to send a $500 donation to. If IPMI access is needed, I can provide it.

Sorry about that, the error code looks easier to read here https://imgur.com/a/XgBYQcw

It says "Invalid OPCODE at" and then names an address. I was able to blow the image up a bit on this screenshot

I have a feeling that opcode error has to do with the media I used to boot into Freedos with and not related to the actual BIOS update itself. Although it shows as successful, it unfortunately still doesn't boot back up after the modded BIOS has been flashed.

Flashing is fine regardless of that invalid opcode thing, it's the modified FW that's broken.
The FW itself is fairly old and needs to have DXE drivers in specific compression format (Tiano) with a specific structure, also started later on with DEPEX section. Black screen after flashing indicates that DXE dispatcher not only fails to dispatch the newly-inserted driver, but also crashes in process.

UPD: try this attached file.

Thanks so much, I was able to flash and boot the server back up with your modded BIOS. The drive I believe showed up as well during boot “pata: SS” This is the first time I’ve gotten this far! I wasn’t able to boot Linux bc of what I believe is a required OS reload and will do that as soon as I get back. I’ll let you know how it goes!

I did an OS reload and rebooted the server after I flashed the new MOD. I can see the pata: ss drive show up now as a boot option, it even shows up in the BIOS, but it can't seem to boot from the NVMe drive. Any ideas?

Bob,

You need to create a Uefi boot entry for your OS installation. If you restored a backup its possible that the boot entry in NVRam is missing. At this point you need to create an efi shell usb stick. Usually they are made by formating a usb disk fat32 and creating an EFI/BOOT folder and copying shellx64.efi into the BOOT folder. Depending on how old your firmware is you have to pick the right shellx64 that is compatible for your uefi version. From there you boot into shell and 'map -r' all your drives. You should see your nvme drive listed as fsn: where n is a number. From there you use bcfg to get a listing of your boot entries "bcfg boot dump" and after the last one you type "bcfg boot add n [path the windows boot loader] [Your OS Name]" where n is the sequential last number item and using the correct path to your OS's bootloader efi file. I had to do this on my Z68 board to get my Nvme drive to load Clover and Mac OS. I suppose if you install your OS fresh it should add the uefi boot entries on their own. Good luck!

Also take note that it's an UEFI-only driver and Linux installed in legacy mode can't boot from it. Please make sure you are booting the installer in UEFI mode (even better, you an try to disable CSM completely, so no legacy mode will become available, but it can be impossible for EFI this old).