Here is my process...
1. Identifying my Samsung 950 Pro ACPI path (using ioreg):
I found it to be
IOACPIPlane:/_SB/PCI0@0/RP09@1d0000/PXSX@0 . Under the PXSX value I have HackrNVMeController, holding IONVMeBlockStorageDevice@1.
which translates to
_SB.PCI0.RP9.PXSX
if I'm not mistaken.
2. Creating the SSDT
I'm using the latest (2017-01) release from your Github. Using ACPI 6.1.
Copying your code from your guide.
Replacing RP13 with RP9.
Saving as SSDT-NVMe-Pcc.aml with ACPI Machine Language Binary format.
3. Placing it on USB with Sierra 12.3 Installer
At EFI/CLOVER/ACPI/Patched.
Another .aml is in this folder. As far as I know, they won't interfere. It's SSDT-USB-H170N-WIFI.aml.
"It is possible your OEM already defined a _DSM method at the ACPI path"
Since I do not believe this is the case, I think I'm good to go.
-----
Creating the HackrNVMeController.kext for the installer
I am on 11.6, booted with HackrNVMeController.kext. I tried using
./patch_nvme.sh --spoof 10_11_6
which gives me MD5 error. I tried using it without the --spoof value, also MD5 error. Is this because Im booted off the HackrNVMeController.kext? I have a IONVMeFamily.kext in System/Library/Extensions and I think it's not been altered with, but I don't know. Can it be the Hackr.kext alters it every boot and therefore it's not "vanilla", giving me md5 mismatch?
IOReg screenshot provided.
Thanks for all help!