Contribute
Register

X1 Carbon 2017 (5th) can't install High Sierra due to the SSD PM981

Status
Not open for further replies.
Same issue with spoofed 10.12.6 kext, no visible difference.

Your HackrNVMeFamily*.-spoof was not generated correctly.
The md5 of the binary (97453a86ff4fb636d516a3427e7eb833) does not match any of the plists in the patch-nvme project.
Correct md5 for 10_12_6_sec2018-001 would be cde08888426959748a7c1e01f990643e.
 
Your HackrNVMeFamily*.-spoof was not generated correctly.
The md5 of the binary (97453a86ff4fb636d516a3427e7eb833) does not match any of the plists in the patch-nvme project.
Correct md5 for 10_12_6_sec2018-001 would be cde08888426959748a7c1e01f990643e.
Do I need to use 10.12.6 update 2018 to create the spoof kext?

I'm using 10.13.3 on a VM to do this, as I can't even finish installer on the target machine.
 
Do I need to use 10.12.6 update 2018 to create the spoof kext?

Not necessarily because you can use the --unpatched argument to provide the path to IONVMeFamily.kext 10.12.6 with 2018-001 update. But you still need IONVMeFamily.kext from that version and you need to use the --unpatched argument. Without --unpatched, you need to be running the script on 10.12.6.

I'm using 10.13.3 on a VM to do this, as I can't even finish installer on the target machine.

No idea what you mean by "this".

Note from FAQ:
Note: DO NOT use a VM to create your USB. VMs are known to create invalid/corrupt USB installers. Use real hardware to create your USB installer.
 
Do I need to use 10.12.6 update 2018 to create the spoof kext?

I'm using 10.13.3 on a VM to do this, as I can't even finish installer on the target machine.
Here is the HackrNVMeFamily-spoof genarated from sec2018-001,and the md5 is matched cde08888426959748a7c1e01f990643e. Pls have a try.It crashed when I start to install it freshly by USB device. I give up to install 10.13.3 on PM981 now, just make a 10.12.6 image copy from other PC and restore to X1C 2017 by using config.plist patched now, it works well now. If you have any further news, pls share with me. Tks
 

Attachments

  • HackrNVMeFamily-10_12_6_sec2018-001-spoof.kext.zip
    91.8 KB · Views: 100
Do I need to use 10.12.6 update 2018 to create the spoof kext?

I'm using 10.13.3 on a VM to do this, as I can't even finish installer on the target machine.
Not necessarily because you can use the --unpatched argument to provide the path to IONVMeFamily.kext 10.12.6 with 2018-001 update. But you still need IONVMeFamily.kext from that version and you need to use the --unpatched argument. Without --unpatched, you need to be running the script on 10.12.6.



No idea what you mean by "this".

Note from FAQ:
Using patched kext from 12.6 and ssdt can drive pm981 in 13.x,but it isn't stable. I only can use it for a data disk, if install the macOS13.x in pm981 would fail. I install 13.3 in a SATA SSD.
a15b4afegy1fomu8sl87jj20ga09umzm.jpg




a15b4afegy1fomua9h5tpj20p60k742p.jpg
 

Attachments

  • nvme.zip
    93.5 KB · Views: 139
Last edited:
Right, still crashing with the correct spoof kext.
 

Attachments

  • HackrNVMeSpoof.zip
    1.9 MB · Views: 78
Using patched kext from 12.6 and ssdt can drive pm981 in 13.x,but it isn't stable. I only can use it for a data disk, if install the macOS13.x in pm981 would fail. I install 13.3 in a SATA SSD.
a15b4afegy1fomu8sl87jj20ga09umzm.jpg




a15b4afegy1fomua9h5tpj20p60k742p.jpg
Right, still crashing with the correct spoof kext.

It is not really surprising (mixing old kexts with new systems generally not expected to work) and may be same result with this hardware and 10.12.6 anyway.
 
It is not really surprising (mixing old kexts with new systems generally not expected to work) and may be same result with this hardware and 10.12.6 anyway.
Just odd to me that this NVMe causes random crashing at all, even without patches.
Hopefully we can generate spoofed 10.3.3 kext soon and try that.
 
Just odd to me that this NVMe causes random crashing at all, even without patches.
Hopefully we can generate spoofed 10.3.3 kext soon and try that.

No need for class-code spoof with 10.13.x as 10.13 has better native support for 512 byte LBA NVMe.
The problem with this specific device is likely something else.

Did you check to see if you have the latest firmware?
 
It is not really surprising (mixing old kexts with new systems generally not expected to work) and may be same result with this hardware and 10.12.6 anyway.
If I use the 13.x's NVMe kext will instant restart. I'm also waiting Samsung to update firmware. But PM981 is an OEM product. And seems can't get support from Samsung.
 
Status
Not open for further replies.
Back
Top