While it does not officially support booting from NVMe, a few sources have indicated that this is entirely possible, and may be a BIOS/UEFI imposed limitation. Would it be possible for someone to take a look at this and give me a more detailed response as to how this can be achieved? I know it's possible with clover but I want to avoid the hassle of needing multiple bootloaders (since I'm going to dual boot). Thanks!

@DarkWorld - Need link to BIOS, or you can do the mod yourself - [Guide] How to get full NVMe support for all Systems with an AMI UEFI BIOS

Zitat von Lost_N_BIOS im Beitrag #2

---

@DarkWorld - Need link to BIOS, or you can do the mod yourself - [Guide] How to get full NVMe support for all Systems with an AMI UEFI BIOS

---

Check BIOS main page and see if ME FW version is shown, if not then download HWINFO64 and on the large window on left side, expand motherboard and find ME area, inside that get the ME Firmware version.
Once you have that, go to this thread and in the section "C" download the matching ME System Tools Package (ie if ME FW version = 10.x get V10 package, if 9.0-9.1 get V9.1 package, if 9.5 or above get V9.5 package etc)
Intel Management Engine: Drivers, Firmware & System Tools

Once downloaded, inside you will find Flash Programming Tool folder, and inside that a Windows or Win/Win32 folder. Select that Win folder, hold shift and press right click, choose open command window here (Not power shell).
At the command prompt type the following command and send me the created file to modify >> FPTw.exe -bios -d biosreg.bin

If you are stuck on Win10 and cannot easily get command prompt, and method I mentioned above does not work for you, here is some links that should help
Or, copy all contents from the Flash Programming Tool \ DOS folder to the root of a USB Bootable disk and do the dump from DOS (FPT.exe -bios -d biosreg.bin)
https://www.windowscentral.com/how-add-c...creators-update
https://www.windowscentral.com/add-open-...menu-windows-10
https://www.laptopmag.com/articles/open-...ator-privileges

This is Phoenix BIOS not AMI. It is UEFI BIOS though, so NVME Mod can be applied, once we find safest method to do that

Also, once you do find the ME FW version, and get the ME Tools package, please also run the following command from MEInfoWin folder >> MEInfoWin.exe -verbose
and show me the bottom of that report (Checking to see if bootguard is enabled here, on left/FPF side if Measured + Verified Boot are both enabled then you cannot modify BIOS)

Alright, the laptop actually had to be sent back for a day or so to get it wiped (former enterprise laptop, they forgot to wipe it), but I'll do that once I get it back. I'll need a SOIC8 Flash Programmer to flash the modified BIOS since this is Broadwell right?

Also, if I brick it will I be able recover by flashing back the original firmware with a live USB or do I need to flash it back with the programmer?

Why did you waste your time and someone's $$ (Free money for postal service I suppose ) you could and should have wiped it yourself

Broadwell has nothing to do with needing a programmer or not, we'll only know if you need one you can dump the BIOS region.
I forgot to mention also, as soon as you dump it, try to write it back and if error show me the command entered and the error given all on same screen. Here is command to write it right back to BIOS after you dump >> FPTw.exe -bios -f biosreg.bin

If you brick the board then it's a brick, usually no recover will be possible without flash programmer. However, some systems have a built in recovery method, that if the BIOS is not bricked badly enough, that can sometimes recover the BIOS via USB
If you can write back BIOS region without hassle, then no worries, it wont brick from NVME Mod.

Zitat von Lost_N_BIOS im Beitrag #6

---

Why did you waste your time and someone's $$ (Free money for postal service I suppose ) you could and should have wiped it yourself

---

I thought maybe you purchased and told someone it contained data, so they wanted it back. Sounds more reasonable if it wasn't a purchase you made, if it was they should have just told you to wipe the drive.
It makes no sense to worry enough to have you send it to them so they could erase, you could have already copied data and been ruling the world with their data in that scenario

That may be, but I've gotten it back now, so just a few days wastyed :D

The UEFI dump is here: https://drive.google.com/file/d/0B5SvZ7D...iew?usp=sharing

The error log when trying to flash it back is here: https://drive.google.com/file/d/0B5SvZ7D...iew?usp=sharing

And the chip ID is: MX25L12805D

thanks!

Zitat von Lost_N_BIOS im Beitrag #8

---

I thought maybe you purchased and told someone it contained data, so they wanted it back. Sounds more reasonable if it wasn't a purchase you made, if it was they should have just told you to wipe the drive.
It makes no sense to worry enough to have you send it to them so they could erase, you could have already copied data and been ruling the world with their data in that scenario

---

@DarkWorld - Sorry for the delay, I'm always behind, hard to keep up sometimes

So you do, or do not have a flash programmer? BIOS Lock and SMI/SMM Lock are both enabled, and these are located in a non-standard module so I don't think you can change them using setup_var

If you have a programmer, send me full dump with programmer. If you do not, we'll have to test and see if the stock update package will flash in a mod BIOS for you or not, I will make this for you tonight

IN the ME System tools folder you downloaded previously, find the MEInfo folder, and run the following from admin command prompt >> MEInfoWin.exe -verbose
Check the end of this report, on Measured and Verified boot, do you see enabled on the left/FPF side? If yes, you cannot use mod BIOS, if no, then we're OK (This is Intel BootGuard)

Will do!

Don't worry about it if you're busy, I'm using another SSD for now.

(Sorry, no flash programmer)

OK, let me know about MEInfo result before I send any mod BIOS

Zitat von Lost_N_BIOS im Beitrag #13

---

OK, let me know about MEInfo result before I send any mod BIOS

---

                                        FPF                 ME
                                        ---                 --
Force Boot Guard ACM:                   Enabled
Protect BIOS Environment:               Enabled
CPU Debug Disabled:                     Disabled
BSP Initialization Disabled:            Disabled
Measured Boot:                          Disabled
Verified Boot:                          Enabled
Key Manifest ID:                        0x1
Enforcement Policy:                     0x3
 

Any update? Same MEInfo result, same laptop here.