Zitat von Dogway im Beitrag #221

---

Do I need to insert the nvme modules at a specific "volume"? I'm using a Gryphon Z87, same as this post.

---

Following instruction on the post [Discussion] NVMe BIOS Modules and NVMe Support (8) 117, I have inserted the three NVMe modules extracted from the Asus Z97 Deluxe v2401 Bios to my own Z77 platform Bios.

I used Volume Index 02 (from Fernando's last post: where the CSMCORE module is located) and the insert FFS options: "As Is".

Have i done it right, so i can use Bios Flashback?

Zitat von Fernando im Beitrag #230

---

If I were you, I would do it.
According to my knowledge and experience the insertion of originally not present BIOS modules is much less risky than the replacement of any already existing ones.

---

Just modded my bios, hope i did it right. Do you think its possible to Samsung 950 Pro be working with this adapter on my MSI X79A-GD65 (8D)? Thahts how my bios image looks like now ( didnt flash it yet) http://scr.hu/0rkf/pzm95

I already inserted the NVMe modules, haven't tested though as I will keep it for a future upgrade.
My question is, for example, if I buy a Samsung 950, wouldn't it be preferable to include to the bios the Samsung modules instead of ASUS (mobo)?

Zitat von Fernando im Beitrag #234

---

@ BoBi1234:
I don't see any NVMe modules within your screenshot.

---

The Bios Flashback did not work with the 3 NVMe modules inserted. The light stays and do not blink as normal it should.

I re-tried Bios Flashback with a previous Bios file without the inserted NVMe modules and everything works normal afterward...

What i did (my previous post 229):
After having inserted the three NVMe modules extracted from the Asus Z97 Deluxe v2401 Bios to my own Z77 platform Bios (renamed bios.bin) and opened with MMTool 5.0.0.7, then when I "save Image as" to a new folder to same bios.bin name but it says "save it unsigned" I clicked OK then used the ASUS "BRenamer.exe" to have the proper name to use the flashback feature.

Something goes wrong in MMTool when "Save Image As", as it tells it is unsigned.

Do i have to use the Insert FFS Options: "Compressed" and not "As Is" ??

Is this the normal behavior??

Thanks for your inputs.

I didn't extracted them, I inserted them "As Is" from the ones you provide first page from Deluxe v2401.

My problem is that MMTool v5.0.0.7 tells when I click "Save Image As", it's saved unsigned.

You just answered me by saying that you're using the "Insert compressed" option and that i better use the MMTool v4.50.0.23 instead of v5.0.0.7...Gonna try that, thanks.
----------------------------------------------------------------

EDIT: Sept 28th, 00h20am

Flashed OK!! Success, all went fine with Bios Flashback and the 3 NVMe Modules inserted compressed with MMTool v4.50.0.23.

I was just using the wrong version of MMTool!

MMTool 5.x (not sure about 4.x) changes the capsule GUID (and blanks the hashes) when saving an image that has a capsule, to notify that the image is unsigned. It also tells you that the image can't be signed, for obvious reasons - it would be a serious security risk to have the private keys in such a tool. What probably happens is that your BIOS Flashback version is not aware of this GUID. You need to understand that it has to know the structure and integrity of the file, it can't just flash every file you throw at it.