@Alexis
After having checked both BIOSes, I can give you the information, that your modded BIOS is ready for being flashed - no Pad-file has been altered.
By the way - we both would have saved a lot of time, if you would have strictly followed my guide.
Good luck!
@Alexis
Thanks for your feedback.
Let me explain the reason for your comfusion:
The DXE Driver Volume of a BIOS is always compressed, but its total size must not be touched by the BIOS modification.
Consequence: The insertion of any DXE driver module has to be compensated by a stronger compression of all other modules, which are inside the DXE Driver Volume. That is why the sizes and checksums, which are shown by the NE Alpha UEFITool, have been changed after having completed the NVMe module insertion.
1 Like
I mean, I’m okay with it if you want to give it a spin. It’s been working fine for me.
Edit by Fernando: Tagged for kawaii15 to get him/her notified about the reply
@Fernando Hi, I’ve read a lot of your guides about the bios mod to insert the nvme dxe on old PCs, I think I’ve done everything right, you could check my bios for safety and on asus motherboards I didn’t quite understand what to use to flash the changed bios, I used uefi tool directly, searching and then inserting the file after the last pad, I don’t quite understand this capsule for asus thanks in advance.
@acidburn87
Welcome to the Win-RAID Forum!
Where are your modded and the original BIOS? I can’t see them.
Regarding your question about how to flash a modded ASUS mainboard BIOS please read the start post of >this< thread and post your additional questions there.
Good luck!
Dieter (alias Fernando)
1 Like
The bios link is here
I read the flash part but I’m not sure I understood correctly if I have to use afudos or Intel Flash Programming Tool, and also the encapsulation maybe I’m wrong these are the 2 things I didn’t understand well forgive me
@acidburn87
Your modded *.ROM file seems to be fine.
Regarding the flashing procedure please post your questions into the appropriate thread (linked within my last post).
ok and thanks for checking, so please confirm that the correct procedure is to open the .cap file and edit it and when it is saved in .rom there is no need to make it go back to .cap correct?
ok for the flash procedure I’m going to the discussion you reported and thank you very much
Hello! Where would I obtain a EFI NVMe module file for my P8P67 Pro Rev3.1 3602 mobo?
Read it… you’ll find it…
EDIT: Yes my friend, you should… you cant miss it because its like this:
This is what you will need:
lol… i need…this is what you will need, simple humm
So careful and to READ: [Guide] How to flash a modded AMI UEFI BIOS - BIOS/UEFI Modding / BIOS Modding Guides and Problems - Win-Raid Forum (level1techs.com)
1 Like
I’ve read through it a few times. Guess I’m overlooking it. I’ll look again.
Ah. It didn’t stand out to me under that section. I see it now. Thanks!
tbf to myself I’ve been reading a lot of forum posts to learn how to do this bios flash.
I’ve never messed with a BIOS before so this is fun and exciting.
Hello,
I am a total modding noob and new to this forum.
A few weeks back I started a little project when I got a gifted used Dell Inspiron 3847 from work, which I have been upgrading since with cheap parts bought from Ebay: Upgraded to Win10 pro, better CPU, silent fans, maximum amount of ram, better Nvidia graphics card. It already came with a 250GB SSD which I would now like to replace with a NVMe SSD in a PCIe 1x slot. I know the PCIe 1x slot is not optimal, but it is a fun project nevertheless.
However the firmware/bios does not support a NVMe SSD boot even with the latest bios version A11 for this Dell Inspiron 3847, which brings me here.
I have read a lot, and I found the right software “ME System Tools v9.1 r7” which matches the ME version on my mainboard with the help of HWiNFO64. And later I found the MECLR1 jumper on the mainboard to unlock the flash. Then I created a efi shell boot usb stick, which I was able to start from after disabling secure boot. And then I used the efi shell usb stick boot to dump the whole flash and also only the bios part. Also when I do fpt.efi -I now, the info of that output displays read/write access with “yes” for the different areas of the flash when the MECLR1 jumper is in the other, non default, position.
So I dumped the whole flash which results in a 8MB file and I dumped only the bios part which results in a 4MB file.
Does it matter if I work on the full flash or just the bios part of the flash as long as I would correctly write them back later for the purpose of adding nvme boot support ?
With UEFITool_0.28.0_win32 I loaded the full and just the bios part and added the nvme module NvmExpressDxe_5 after the last entry just as described in the guide.
Could somebody please be so kind to verify my work before I do the critical part and attempt to flash it back ? I hate to get it wrong after all the many hours I have put into this upgrade project. I checked the padding areas which the unmodified and the modded nvme boot version side by side, they look the same, but I do not want to chance it.
dell_inspiron_3847_firmware_full.zip (6.9 MB)
dell_inspiron_3847_only_bios.zip (4.7 MB)
For flashing the full or bios file back I will use fpt.efi -F filename or fpt.efi -F -bios filename from the efi shell usb boot stick, correct ? Which one is preferable please ?
Thanks a lot
Well, as i saw that you used the tips i gave to another user, this also applies to you in the matter of flashing mods.
Every machine has its own method difficulties to apply a mod… image modification and security usually prevents the flashing, the FPT tool has its own cmds and should learn it.
The best option is only flashing the bios region (-bios -f), avoiding tampered with the rest of the firmware regions, ME DESC GBE EC…
Now be aware that you should be prepared for anything… this mod world.
What we can check is the correct volume insertion of the NVMe DXE module, other than that is all up to the user to take risks, no one can assure you of 100% in a mod, at least me, i will never assume that to no one.
I checked your bios_region mod file and seems correctly inserted in the right volume, with original pad file still present as the original, so seems ok to flash.
Hello! Very nice guide! Congrats!
Before try this on my MB Asus m5a97 evo rev.1.01, I need to know if the process is the same for *.ROM bios files ???
@daltonfcm
Welcome to the Win-RAID Forum!
The suffix of the BIOS file doesn’t matter. Only important is, that it is an AMI UEFI one.
Good luck!
Dieter (alias Fernando)
hello sir good evening from philippines any tutorial for asus p7h55m 1st gen lga1156?
non uefi board could read these:
Hello,
today I flashed my uvme bios mod as posted earlier from within an efi usb boot stick with
fpt.efi -F -bios biosfilename
and then installed a pcie 1x nvme adapter with a new nvme ssd.
Then I did a
sc.exe config stornvme start= boot
in the old windows installation and then proceeded to
restart from a linux usb stick and copied the sata attached ssd’s data over to the nvme ssd.
Then I shut down the computer, disconnected the sata ssd and booted from the nvme ssd.
I also used the windows 10 tools to extend the windows partition on the nvme ssd.
And I am very pleased that the nvme bios mod for the Dell Inspiron 3847 works.
Thanks for all the information provided here!
2 Likes
I’ve modded an ASUS B85M-E (3602) BIOS and added the v5 NVME DXE (NvmExpressDxe_5.ffs) to it.
Can someone verify if this modded file by me is safe to flash and will work to enable NVME booting?
I checked the report and generated an UEFITool diff of the original 3602 BIOS and the modded BIOS, the only difference seems to be a removed bit of free space, and the new module.
Thanks in advance, and happy holidays.