Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by Tobinejumi

  1. I guess that might be my mistake then, no. I fallowed the ReadMe and i don't see anything about a SSDT patch, can you point me int he right direction please? Sorry I'm noob at this.


    If you read this readme, it contain some links:




    10.12 UPDATE

    By tricking the system, we can prevent IONVMeFamily.kext from loading. It involves injecting a fake "class-code" such that the IOPCIClassMatch in IONVMeFamily's Info.plist no longer matches.

    With this technique, HackrNVMeFamily and IONVMeFamily can co-exist. Applies to installation scenarios and to post-install.

    See here for further details: http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/page-29?do=findComment&comment=2322636

    Or here: https://www.tonymacx86.com/threads/guide-hackrnvmefamily-co-existence-with-ionvmefamily-using-class-code-spoof.210316/

  2. So I went through the topic and I have to admit i'm a bit confused.

    Could someone sum up what is currently required to install macos the vanilla way on a Samsung 960 Pro NVMe drive?



    My way to do it: First install clover and system on sata HDD, boot in, patch NVMe, made it visible to disk utility and create partitions. Then install Clover on NVMe and copy clover EFI from sata HDD, also carbon copy system. Then boot from NVMe. Possibly it's not the most short way, but it works for me.

  3. No idea.  After I applied the update, it never showed in my update history... (App Store bug, I guess).

    That's why I named this plist after the build#.


    Correct use of patch_nvme.sh is with only './patch_nvme.sh --spoof'.  No need to specify the plist as it will be determined automatically (as is written in my guide).


    Thank you!

    Yes, they call it 2017-002 security update. Autodetection with --spoof works fine, great improvement. 

  4. ACPI path is _SB.PCI0.RP09.PXSX


    Extra injections required on 10.11.6 for certain SSDs are documented in my guide (linked from patch-nvme README).

    SSDT patch created and installed, DSDT patch in clover config installed, spoof-code kext generated and installed - system boots up ok. Thank you!

    Here goes one question: do i still need to generate new spoof class kext after every system update? If so, can you add script for 10.11.6 2017-001 security update?

  5. If you do the class-code spoof, you will not need to remove IONVMeFamily.kext.

    Updates without the class-code spoof are challenging due to the need to remove IONVMeFamily.kext.

    Lazy people (those that don't implement the class-code spoof) will be greeted by a system that doesn't boot after updates...

    Yes, i see. Will try spoof method when find any free sata drive for win install on this system. Do not want to mix OSX/win boot partitions at one drive.

  6. If you have supplemental update 3 installed, you need 10_11_6_supp2016-003.

    Run script with supp2016 list, got next output:


    Creating patched HackrNVMeFamily-10_11_6_supp2016-003.kext

    Vanilla MD5 matches expected MD5 entry (0aed9374ab41e40976bd191cba126423)

    Patched MD5 matches expected MD5 entry (477dadd3231cbe4327813fa1832871fc)

    Then placed generated kext in Clover kexts folder, restart... No joy. System doesn't see this drive.


    Reply at my spoof guide, with files/images as requested in "Problem Reporting".

    Where is this guide?

  7. Well, still trying to find workaround for my problem: 
    installed 10.11.6 at SATA hdd
    updated to Security update 3
    run script and got next:

    Oleksiis-Mac-Pro:patch-nvme-master leszek$ ./patch_nvme.sh 10_11_6_sec2016-003
    Creating patched HackrNVMeFamily-10_11_6_sec2016-003.kext
    WARNING: Vanilla MD5 (0aed9374ab41e40976bd191cba126423) does not match expected MD5 (b3b4dd50b2bbd9cc4dc901fad12643ac)
    WARNING: Patched MD5 (477dadd3231cbe4327813fa1832871fc) does not match expected MD5 (6ea6fd529ee962f6308b95a854897556)

    Is it ok to use generated kext (attached)?