IONVMeFamily.kext bin patch data

If this is what you are looking for macOS Sierra only (for El Capitan click here):
System_Information_NVMExpress
Then here is your patch data:

<dict>
	<key>Comment</key>
	<string>IONVMeFamily IONameMatch</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>InfoPlistPatch</key>
	<true/>
	<key>Find</key>
	<data>PHN0cmluZz5wY2kxNDRkLGE4MDQ8L3N0cmluZz4=</data>
	<key>Replace</key>
	<data>PHN0cmluZz5wY2kxNDRkLGE4MDI8L3N0cmluZz4=</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#1</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>ibPoAgAAweAMBQAQAACJgw==</data>
	<key>Replace</key>
	<data>ibPoAgAAweAJBQAQAACJgw==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#2</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>D7aMiIIAAACD+QwPhTIBAA==</data>
	<key>Replace</key>
	<data>D7aMiIIAAACD+QkPhTIBAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#3</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>AMeDpAAAAAAQAABIi0gISA==</data>
	<key>Replace</key>
	<data>AMeDpAAAAAACAABIi0gISA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#4</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>SYnGTYX2dGFBwecMSWP/vg==</data>
	<key>Replace</key>
	<data>SYnGTYX2dGFBwecJSWP/vg==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#5</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>hv8PAABIwegMD7cPgeH/Dw==</data>
	<key>Replace</key>
	<data>hv8PAABIwegJD7cPgeH/Dw==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#6_7</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>icGB4f8PAABIAdFIgfn/DwAAdzs=</data>
	<key>Replace</key>
	<data>icGB4f8BAABIAdFIgfn/AQAAdzs=</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#8</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>SYHF/w8AAEnB7QxJiwQkSA==</data>
	<key>Replace</key>
	<data>SYHF/w8AAEnB7QlJiwQkSA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#9_10</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>BgIAAEyNuAAQAABMiflIgeEA8P//SYmGGgEAAEmJjiIBAABBvAAQAABJKfQ=</data>
	<key>Replace</key>
	<data>BgIAAEyNuAACAABMiflIgeEA8P//SYmGGgEAAEmJjiIBAABBvAACAABJKfQ=</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#11</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>AABJiY4iAQAAugAQAABIKQ==</data>
	<key>Replace</key>
	<data>AABJiY4iAQAAugACAABIKQ==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#12</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>yAAAAEkp17gAEAAATYskJA==</data>
	<key>Replace</key>
	<data>yAAAAEkp17gAAgAATYskJA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#13</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>4b+AQBUGTYnWugAQAABFMQ==</data>
	<key>Replace</key>
	<data>4b+AQBUGTYnWugACAABFMQ==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#14</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>iWTY+EmBxAAQAABJgccA8A==</data>
	<key>Replace</key>
	<data>iWTY+EmBxAACAABJgccA8A==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#15</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>Bf8PAABIwegMZvfB/w8PlQ==</data>
	<key>Replace</key>
	<data>Bf8PAABIwegJZvfB/w8PlQ==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#16</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>weIIQQ+2wcHgDEQJ0EQJwA==</data>
	<key>Replace</key>
	<data>weIIQQ+2wcHgCUQJ0EQJwA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>IONVMeFamily Pike R. Alpha Patch#17</string>
	<key>Disabled</key>
	<false/>
	<key>Name</key>
	<string>IONVMeFamily</string>
	<key>Find</key>
	<data>RYTJD5XAD7bAweAMRAnYRA==</data>
	<key>Replace</key>
	<data>RYTJD5XAD7bAweAJRAnYRA==</data>
</dict>

Put that in the “KernelAndKextPatches” section of your Clover config.plist A big thank you (twice) to Marc aka Mork vom Ork for providing the data of my patches.

Note: It currently works well enough for a wider release – hence sharing the data here – but there are probably a few more things that can be done to polish it up a little, but I only want to do this after a long testing period.

Also. I have no intention to work on support for El Capitan or older versions of OS X. My focus is on patches for macOS Sierra only.

Edit: If TRIM support isn’t enabled on your setup then run:
sudo trimforce enable

122 thoughts on “IONVMeFamily.kext bin patch data

  1. Pingback: Stock Apple NVMeFamily.kext is a GO… – Pike's Universum

      • Yes, with this patch you can use your NVMe-device as a bootdisc. No longer need of NVMeGeneric.kext. Just type the above entries to your CLOVER config.plist and select your SIERRA (and right now ONLY Sierra) NVMe drive as bootdisc. Worx 4 me w/o any errors.
        ONCE AGAIN A BIG THANKS TO PIKE for this amazing patch. Great work.

      • As Mr. Mork vom Ork said I also can boot sierra, I tested it. Also now we can start in safe mode… Thanks again to Mr. Pike and Mr. Mork vom Ork.

  2. Hi, I have an OCZ RD400 512GB card, which uses the NVMe. I’ve added the patch to clover but unfortunately my drive still doesn’t show up in Disk Utility, or anywhere for that matter. I was never able to get it to work with the old NVMegeneric kext either in Sierra or even El Capitan, would always give me a kernel panic on boot up. Any ideas how to get sierra to see it?

      • It goes through the boot so quickly, but I didn’t catch any errors or mention of the NVMeFamily – I may try recording it with my phone and watching it back 😛 I have tried the boot argument with both nvme=0x3, and 0xf. Any other combinations I should try? I checked the logs but couldn’t find the Kernel.log to see how the boot went, does sierra log the boot sequence differently or am I just not seeing it?

      • I’ve tried a couple different things – Used clonezilla to clone my Sierra SSD to the RD400 NVMe. From the boot menu I can select the RD400 and clover opens just find and starts the Sierra boot sequence, but can’t seem to find the root drive. I’m assuming thats the RD400. I sent you an email with a picture of where it stops, likely makes more sense to you than to me 😛 thanks again for your work on this!

      • Ok. The IONVMeFamily.kext doesn’t seem to be loaded. Did you copy the kext to the Clover other folder? See what Marc wrote about it for the installer. Maybe that will do the trick for you.

    • Hi Calvin, first of all: is your hardware (PC) BIOS capable of NVMe ? Do you have an option for this within your BIOS? If not, check for BIOS update on vendors page. If it is capable for NVME, you should see your drive within BIOS settings, so could choose as boot drive. If this is NOT the case, i would say, your current BIOS isn’t capable for use with NVMe-devices. Please check this first, than reply again, so we may can help.

      • Hi, yes it shows up in the BIOS and even shows the UEFI partition in my boot options. I have a windows 10 sad, and the RD400 shows up and works well in windows 10 (after the driver updates of course) I had formatted it with the HFS+ and put the EFI partition on it hoping that it would help it show up, but still nothing. Thanks for being willing to help!

      • I also cannot see my drive during install. However, when I add nvme=0x1 or nvme=0xf I always get KP.

      • Open a terminal window in the Installer App and load the patched kext manually (from some other volume). That worked for me.

        Note: The reason for this is that the mounted BaseSystem.dmg is missing some vital kexts, like HFS.kext et all.

      • The problem is that I can’t patch kext manually. I believe it will be good idea to post patched kext with clover patch data, because it will easier for people to get it, instead of writing you emails.

      • I tried to load IONvmefamily.kext from S/L/E. Didn’t work. You wrote that I have to load from other volume. I have no other volumes or you meant that I need to copy IONvmefamily.kext to some other USB drive and load it from there?

      • Hi,pikeralpha
        Thanks for your great work!
        I’m installing latest Sierra on my DELL precision M5510 laptop,and failed to load kext and the patch. Seems like I still can load the patched kext while install app launched as you’ve said. But how?
        I’ve checked the install and disk utility interface and cannot find any option or button to open a terminal.
        please tell me how.

        Thanks a lot!!

      • Hi,

        You’ve checked the disk utility from the installer? In that case you had to quit the installer and used the menu. Opening the terminal can be done from the same menu.

  3. hello , i am here now .I had an unexpected these days, I tried on asrock z97extreme 6, with kext to patch, but in the process of installation, I do not see the disk 950 Pro 512GB (NVME) in utility disk..

    • Is that with Clover or Chameleon?

      Note that I (first) had the same issue with RevoBoot and had to load the kext manually, from the terminal window. After closing it and going back into the installer window is was there (also in Disk Utility) as it should.

  4. Congratulation Piker Alpha that a really good work currently using El capitan but as soon as web driver will be available for the GTX 1080 i’ll switch all my setup to Sierra, Sierra is already installed on my 850 Evo for testing but i will wait 1-2 month before using it at my principal OS

  5. please please please an El Cap patch for this? Will be so useful for existing systems. Will it be very time consuming to back port it to el cap?

  6. I have made some more tests: normaly you cant use the SIERRA installer with NVMe-devices, cause it won’t load them. You have to load the IONVMeFamily.kext via terminal. BUT there is a solution if you use CLOVER as your bootloader:

    just copy IONVMeFamily.kext from SIERRA to your CLOVER kext folder (EFI – CLOVER – kexts – Other) of your INSTALL SIERRA USBstick. Apply the patch to your CLOVER config.plist – select your USBstivk as bootdevice within BIOS – et voila: you should be able to boot from your stick into SIERRA installer and you should be able to select your NVMe-device as installdevice for SIERRA.

    Tested this method here twice and it works perfectly.

    • Thank you for this update Marc.

      Note that I don’t use Clover, but the M2 drive shows up in the installer App with RevoBoot so I take it that it can be done with Chameleon as well, but booting from the M2 drive fails with: Waiting for root device. As if the kext isn’t loaded or something.

      Edit: Problem solved! The Info.plist on my M2 drive was damaged, and after replacing the plist everything is fine.

  7. As few people already wrote there – El Capitan pleaaase! As it is current stable, and will be such for at least few months – many people will say you big thank you for backporting your great work to El Capitan!
    P.S. Does anybody know if it is compatible with latest Toshiba SSDs? Like OCZ RD400 or Toshiba XG3

    • Good news. I just e-mailed Marc (and one other person) the first test kext for El Capitan (10.11.5) and it appears to work, but let’s just wait and see what the testers have to say about it.

      • HI, Pikeralpha,
        I tried to install 10.12 but always gives me a skl framebuffer kp, so I’m wondering if you could also send me a binary patch for 10.11.5 to test. I have already sent a email to you and it is as same as the address I used here.
        big thanks!

  8. I am running with the 10.11.5 binary right now but even when it is Clover/kexts (or when I kextload it) I do not see my Intel P3600 PCI-e SSD.

    Any advice, or would you like any files or remote access, Pike?

    • Rehabman’s script kextdDoes not work for me on El Capitan with Intel 750 PCI-E SSD.

      Works on Sierra DP3 with low and disappointing speed rates… Kernel panics with DP5 (and yes I redid the patched kext) … 😦

      Seems Apple changed/improved the IONVME kext in DP5 and somewhat borked patched kext for Intel 750 PCI-E SSD…

      • Was wondering if you ever got it working on your Intel 750? I’ve been trying to get mine recognized on my old Z68 board of all things. I’m hopeful it will work considering the Clover NVMExpressdxe driver recognizes the drive. Thanks.

  9. Pingback: IONVMeFamily.kext changes in Sierra DP2 (build 16A239j) – Pike's Universum

      • Not so bad 🙂 (Italian way to say that every things looks super).
        Code I made is obviously inspired by Rehabman for the idea of making a secondary kext, only hate scripts for security reasons, and code is portable for every one wants to implement (also nothing gets done if there are errors, so hope no troubles).

        It seem (to me) that Apple improved compatibility with latest version of the kext, maybe the sign that a full support coming?

        PS Tested on a 950 pro M.2, the bad is only that is not mine…

      • Yes, Apple still improved the kext. But: w/o Pike’s patch, a SAMSUNG SM950 Pro still get NOT recognized. Just tested… 😉 This is what i believe: apple doesn’t implement full Support for SAMSUNG SM xxx SSDs within the next 5 macOS releases. Thats cause they want to sell their own (overpriced) SSDs with their Build-To-Order Macs. And THIS is why there is a hackintosh-scene. The guys within that scene make impossible things possible (for all of us).

  10. Thanks for your reply will wait to hear from you thanks again for your huge Work 😀
    i prefer a clover patch to paste my self rather than installing some other kext, thank you again couldn’t appreciate your help more :p

  11. So assuming I correctly modified the EFI files as described…(99%) sure I did, it does not work with the intel 600P as far as I can tell….
    based on the complication, and that this is a dual boot machine, win10 is going on the m.2 SSD and Sierra went onto the Crucial SATA drive….
    I don’t have time to fiddle around hoping the installer will “see” the m.2 … if anything I will hedge my bets that I can clone the drives back and forth at a later date if needed….

  12. Finally got sierra to install to Intel 750 thanks to this. Had previously got the SSD recognised by Rehabman’s kext patch but until now unable to install to SSD. BIG MASSIVE THANKS.

    Very clever! Wish I was this clever!

    • So Rich,
      To clarify to install Sierra straight from USB Clover Key you can’t just drop the generated kext into the EFI folder and delete the IONVMEfamilty kext.. You need to drop patch data into clover? Can you explain how you did it?

      Thanks

      • Yes that is correct. You need to install the clover nvme driver using clover configurator and add this patch in the appropriate place in the config.plist. I added this using appropriate txt editor not configurator. Start the installer and you should either see the nvme drive as an option to install to or if it’s not yet formatted access it with disk utility in installer and format. I’m not 100% sure those steps work as I took a slightly different route. I installed to a sata, then used rehabman patch and nvme was mountable from sierra, I reran the installer and targeted the nvme drive. However, whatever I tried I could not complete the install until I used this patch as the nvme would not boot.

      • Richard –

        Were you able to boot normally after the installation on the 750 (assuming 750 is your boot drive)? I used Pike’s patch and installation went fine, but system won’t boot without the USB. Copied all files from the Clover/kexts/Other folder in the USB and copied over to the EFI partition on the boot drive, but didn’t help. Any pointers?

        Thanks

      • Yes I am able to boot from the 750, but it might require the rehabman patched kext (https://github.com/RehabMan/patch-nvme) and this has to be created on the machine version of your choice.

        So I installed to a SATA, created this kext and then copied it to the /Library/Extenstions/ on the SSD, and dont forget to remove the IONVMeFamily.kext from /S/L/E

        Its a few steps to get there but it works.

      • Richard –

        Actually I realized what I was doing wrong : post-installation, Pike’s patch needs to be applied to the config.plist that is now on the installed EFI partition (not the USB installer), for the NVMe to work as a standalone boot disk. With that change, I’m able to boot normally without needing the USB stick. Leaving this out here for other folks that may come here by way of Google…

        I get Rehabman’s point about the risk of doing this, however I’ve never had HackrNVMe work for me on 10.12 before (tried again last night after your comment, still didn’t work). Built on the same machine, removed IONVMe and Pike’s patch, installed the kext to /S/L/E but no luck. So I’ll stick with Pike’s patch for now until…something bad happens…

      • Sree,

        Does that patch also work on 12.1 not needing a new patched kext for every OS X update? Do you also use the nvme efi driver as well?

        I got mine working with 12.0 just with the patched kext. Haven’t tried 12.1 yet.

        Thanks

    • Hey Rich,
      Can I see your patch data for your 750 SSD? I copied the kext patches into an block. Xcode wouldn’t open it otherwise. Can’t get the usb installer to see the drive though.

      Thanks

  13. Hi Pike, are you getting any weird reliably issues with NVMe used as a boot/os drive ?
    Simple things like editing ACPI tables _SB. etc I want to change to _SB_. but it never saves the change. Other times when rebooting I see nothing after PCIe detection until the logon screen, others I get to see the boot, yesterday I booted to find I had a projector added to my Displays that I don’t have etc etc

    Is this just an NVMe issue being still newish to hackintoshes ?

    I must add that I am not using RevoBoot (would love to but can’t find enough guides/help)

    Martin

  14. So I am trying to install sierra on my dell xps 15 using clover. If I dont have the patch on my config.plist my system boots but my SSD is not listed in Disk utility. If I add this patch to my config.plist my system gives a kernel panic. So my question is do I have to have the IOnvmeFamily.kext in the kexts/other folder? If yes. Do i get that kext from a macSierra laptop. thank you
    my SSD is Samsung PM951 NVME 1024gb
    SKYLAKE INTEL core i7-6700HQ

    • Augusto and all, I as well have the Dell CPS 15 9550. I have added the patches to config.plist and have populated /EFI/CLOVE/KEXTS/other with a copy of IOnvmeFamily.kext. I am able to boot into Sierra’s installer but the SSD is still not listed in Disk Utility to get it formatted.

      Any help is much appreciated!

      • @Justin Mackey. I got my laptop to boot and shown my SSD on the Disk Utility. Do you have the
        SATA-RAID-282a.kext and SATA-100-series-unsupported.kext in your CLOVER/other folder? This are for some of the skylake unsopported SATA controlers. I have those. You can check you system configuration with HWiNFO64 program. It gives you good information about your system

  15. I finally got the patch working though the debug session showed that the device ids weren’t being patched but it still worked. Pike is that the correct device id for the Sierra installer ionvmefamily kext on the usb? pci144d,a804 ?? Still worked on my Intel 750 after changing that to pci8086,0953 FWIW..

    Thanks

      • Well I’m not sure its Finding what it wants to Replace. I recorded a video of the debug logs and the first two patches for me are saying ‘Not Patched!’. This is on the Sierra USB installer. In anycase it still recognizes the drive. Not sure what the long term effect will be. Thanks

      • I’m sorry Piker I don’t understand. Your looking for a804 and replacing it with a802? Shoudn’t you be looking for 0108, 0200? Sorry I’m a little confused.

    • Cyberdocsite,

      I did not have to change the device ID to make this patch work on my Intel 750. As Pike mentions, it is auto-magic 🙂 Also i haven’t tried yet on 12.1, still on 12.0 for now.

  16. I changed my config.plist and added the kext in the ‘other’ folder, but my installer can’t find the ssd.
    I’m on a Dell XPS 15 9550 15″, i7 6700HQ, 512 nvme ssd.

  17. Hello People,
    I am running Sierra 10.12.1 On Gigabyte z170x UD5 motherboard, I had Samsung 250gb M.2 pro yesterday and I tried everything that you guys mention about but no luck. I copied the codes to Efi/clover/config, and also I copied IONVMeFamily.kext form S/L/E to Clover/kexts/others. I do not know what is wrong. is there anyone help me ?

    • Please run the script from Rehabman or Micky1979 and visit a hack related forum for end-user support as I am done with NVMe support. Sorry, but I need all my free time for new stuff.

      • Thanks for quick response,
        I finally got it, what I did, I copied the script to under
        KernelAndKextPatches

        AppleRTC

        AsusAICPUPM

        Debug

        KernelCpu

        KernelHaswellE

        KernelLapic

        KernelPm

        KextsToPatch

        Comment
        IONVMeFamily IONameMatch
        Disabled

        Name
        IONVMeFamily
        InfoPlistPatch

        Find

        ....

        and its worked

        Thank you
        PHN0cmluZz5wY2kxNDRkLGE4MDQ8L3N0cmluZz4=
        Replace
        PHN0cmluZz5wY2kxNDRkLGE4MDI8

    • Hey Eric – please describe exactly what you did to make the 600P work! Did you install from 10.12.1?

      I have tried the same but no joy so far.

      • I install from 10.12.1
        I use UniBeast 7.0.1 to create bootusb and add code to config.plist.

        my config.plist

        ACPI

        DSDT

        Debug

        DropOEM_DSM

        Name
        DSDT.aml
        ReuseFFFF

        SSDT

        DropOem

        Generate

        Boot

        Arguments
        -v dart=0
        Debug

        DefaultVolume
        LastBootedVolume
        Legacy
        PBR
        Secure

        Timeout
        3
        XMPDetection

        CPU

        UseARTFrequency

        Devices

        Audio

        Inject
        1

        FakeID

        ATI
        0x0
        IMEI
        0x0
        IntelGFX
        0x0
        LAN
        0x0
        NVidia
        0x0
        SATA
        0x0
        WIFI
        0x0
        XHCI
        0x0

        USB

        FixOwnership

        Inject

        DisableDrivers

        Nothing

        GUI

        Hide

        \EFI\BOOT\BOOTX64.EFI
        Windows

        Language
        en:0
        Mouse

        DoubleClick
        500
        Enabled

        Mirror

        Speed
        8

        Scan

        Entries

        Legacy
        First
        Linux

        Tool

        ScreenResolution
        1920×1080
        Theme
        tonymacx86

        Graphics

        Inject

        ATI

        Intel

        NVidia

        NvidiaSingle

        KernelAndKextPatches

        AppleRTC

        AsusAICPUPM

        Debug

        KernelCpu

        KernelHaswellE

        KernelLapic

        KernelPm

        KextsToPatch

        Comment
        External icons patch
        Disabled

        Find

        RXh0ZXJuYWw=

        Name
        AppleAHCIPort
        Replace

        SW50ZXJuYWw=

        Comment
        change 15 port limit to 26 in XHCI kext (100-Series-10.12)
        Disabled

        Find

        g710////EA==

        Name
        AppleUSBXHCIPCI
        Replace

        g710////Gw==

        Comment
        IONVMeFamily IONameMatch
        Disabled

        Name
        IONVMeFamily
        InfoPlistPatch

        Find
        PHN0cmluZz5wY2kxNDRkLGE4MDQ8L3N0cmluZz4=
        Replace
        PHN0cmluZz5wY2kxNDRkLGE4MDI8L3N0cmluZz4=

        Comment
        IONVMeFamily Pike R. Alpha Patch#1
        Disabled

        Name
        IONVMeFamily
        Find
        ibPwAgAAweAMBQAQAACJgw==
        Replace
        ibPwAgAAweAJBQAQAACJgw==

        Comment
        IONVMeFamily Pike R. Alpha Patch#2
        Disabled

        Name
        IONVMeFamily
        Find
        D7aMiIIAAACD+QwPhTIBAA==
        Replace
        D7aMiIIAAACD+QkPhTIBAA==

        Comment
        IONVMeFamily Pike R. Alpha Patch#3
        Disabled

        Name
        IONVMeFamily
        Find
        AMeDpAAAAAAQAABIi0gISA==
        Replace
        AMeDpAAAAAACAABIi0gISA==

        Comment
        IONVMeFamily Pike R. Alpha Patch#4
        Disabled

        Name
        IONVMeFamily
        Find
        SYnGTYX2dGFBwecMSWP/vg==
        Replace
        SYnGTYX2dGFBwecJSWP/vg==

        Comment
        IONVMeFamily Pike R. Alpha Patch#5
        Disabled

        Name
        IONVMeFamily
        Find
        hv8PAABIwegMD7cPgeH/Dw==
        Replace
        hv8PAABIwegJD7cPgeH/Dw==

        Comment
        IONVMeFamily Pike R. Alpha Patch#6_7
        Disabled

        Name
        IONVMeFamily
        Find
        icGB4f8PAABIAdFIgfn/DwAAdzs=
        Replace
        icGB4f8BAABIAdFIgfn/AQAAdzs=

        Comment
        IONVMeFamily Pike R. Alpha Patch#8
        Disabled

        Name
        IONVMeFamily
        Find
        SYHF/w8AAEnB7QxJiwQkSA==
        Replace
        SYHF/w8AAEnB7QlJiwQkSA==

        Comment
        IONVMeFamily Pike R. Alpha Patch#9_10
        Disabled

        Name
        IONVMeFamily
        Find
        BgIAAEyNuAAQAABMiflIgeEA8P//SYmGGgEAAEmJjiIBAABBvAAQAABJKfQ=
        Replace
        BgIAAEyNuAACAABMiflIgeEA8P//SYmGGgEAAEmJjiIBAABBvAACAABJKfQ=

        Comment
        IONVMeFamily Pike R. Alpha Patch#11
        Disabled

        Name
        IONVMeFamily
        Find
        AABJiY4iAQAAugAQAABIKQ==
        Replace
        AABJiY4iAQAAugACAABIKQ==

        Comment
        IONVMeFamily Pike R. Alpha Patch#12
        Disabled

        Name
        IONVMeFamily
        Find
        yAAAAEkp17gAEAAATYskJA==
        Replace
        yAAAAEkp17gAAgAATYskJA==

        Comment
        IONVMeFamily Pike R. Alpha Patch#13
        Disabled

        Name
        IONVMeFamily
        Find
        4b+AQBUGTYnWugAQAABFMQ==
        Replace
        4b+AQBUGTYnWugACAABFMQ==

        Comment
        IONVMeFamily Pike R. Alpha Patch#14
        Disabled

        Name
        IONVMeFamily
        Find
        iWTY+EmBxAAQAABJgccA8A==
        Replace
        iWTY+EmBxAACAABJgccA8A==

        Comment
        IONVMeFamily Pike R. Alpha Patch#15
        Disabled

        Name
        IONVMeFamily
        Find
        Bf8PAABIwegMZvfB/w8PlQ==
        Replace
        Bf8PAABIwegJZvfB/w8PlQ==

        Comment
        IONVMeFamily Pike R. Alpha Patch#16
        Disabled

        Name
        IONVMeFamily
        Find
        weIIQQ+2wcHgDEQJ0EQJwA==
        Replace
        weIIQQ+2wcHgCUQJ0EQJwA==

        Comment
        IONVMeFamily Pike R. Alpha Patch#17
        Disabled

        Name
        IONVMeFamily
        Find
        RYTJD5XAD7bAweAMRAnYRA==
        Replace
        RYTJD5XAD7bAweAJRAnYRA==

        RtVariables

        BooterConfig
        0x28
        CsrActiveConfig
        0x67
        MLB
        D25341100QXDM671H
        ROM
        UseMacAddr0

        SMBIOS

        BiosReleaseDate
        09/03/2013
        BiosVendor
        Apple Inc.
        BiosVersion
        IM142.88Z.0118.B00.1309031249
        Board-ID
        Mac-27ADBB7B4CEE8E61
        BoardManufacturer
        Apple Inc.
        BoardSerialNumber
        D25341100QXDM671H
        BoardType
        10
        ChassisAssetTag
        iMac-Aluminum
        ChassisManufacturer
        Apple Inc.
        ChassisType
        13
        Family
        iMac
        Manufacturer
        Apple Inc.
        ProductName
        iMac14,2
        SerialNumber
        D25LHACKF8JC
        SmUUID
        854D1208-3088-48F8-8AEF-05F94254631B
        Trust

        Version
        1.0

        SystemParameters

        InjectKexts
        Yes
        InjectSystemID

        Edit: Please note that the source code tags are missing and thus the XML format is broken!

  18. Like Eric Chang, I’ve also succesfully installed MacOS Sierra onto the Intel 600p SSD NVME.

    I used Unibeast 7.0.1 for the Sierra USB Installer. Added patches the KextToPatch section. And voila.

  19. Hey there. I’m having trouble understanding the instructions listed here as they seem to be aimed to people who are familiar with programming. How and where do we patch the data? Is this being done within Mac OS X “Terminal”? Or are we somehow modifying “NVMeGeneric.kext” I dont understand where I’m supposed to patch the data listed above. Also, where do I find “KernelAndKextPatches” section of your Clover config.plist and how do I modify it? Am I changing the text in Terminal or opening the file with TextEdit?

    I apologize for my ignorance here as I’m usually very good with computers but this is especially confusing to me. I’m trying to get my Mac to recognize a Samsung 960 EVO SSD which is installed in an external Thunderbolt enclosure.

    Any help would be greatly appreciated. Thanks!

    • If you don’t have a “KernelAndKextPatches” section in your Clover config.plist then you must add it (with the patch data) or simply use Rehabman’s script, or the app to create a patched kext. When the latter works, then you can add the data to your Clover config.plist

    • Open config.plist with plist editor and search for kextsTopatch. Then copy and paste all of this in there. Also there is an easyway with rehabMan patchnvme repo on git hub. Google it is your friend

      • Aargh. I’ve been Googling away. I don’t think I have the brain for this type of coding and it also makes me super nervous about messing up my system by doing the wrong thing. Would either of you be into guiding me through the necessary steps over the phone? I would gladly pay you for your time! Could pay through Paypal. I have a Samsung 960 Pro that I really want to get working on my Mac.

  20. Is there any way to get the Hynix PC300 to work with this patch? I was previously able to use the NVMeGeneric.kext to work in El Capitan

    • Sorry, I have no idea if the patches work with this device. I checked and see a firmware update for it. That might actually be more fun. I mean to patch it and to make it compatible without a patched kext.

  21. hellò pike , how are you ?
    I have an annoying problem with Sierra, my pc is very slow when i reboot it, today I tried to install El Capitain on a ssd AHCI, when I put the kext to patch the config plist (for NVME) El Capitan is also very slow to reboot, but when I remove the kext to patch from config.plist, like a miracle reboot it is very fast, as it can depend on?
    happy new year Pike

    • I am fine. Thanks. Happy new year to you!

      About the slow reboot issue. Is cold boot faster than a warm boot? Does is take long before it reboots, or does it take longer to warm boot? Do you have trim enabled?

      One thing is that Clover patching may take some time, but it shouldn’t matter if that is done after a cold or warm boot. Another thing is that the NVMe drive may need to finish the writes, and possibly also writes a hibernate file. That also takes time. Is hibernate enables or disabled? If you disabled it (check with pmset -g) then you should no longer have the diskimage.

  22. Hellò Pike , thank of heart for your answer, I have hibernate =0 and trim Enabled. Reboot is slow both hot and cold

    • A warm boot is a reboot. As in Apple logo -> Restart… and sudo reboot in a terminal window.
      A cold boot is when you flip the power switch and press the power button on the PC case.

      • Hello Pike ,I’m using the kext hack Racer, I’ll explain better what happens: I thought it was a bug in the Sierra, but I tried to install EL AHCI on a disk (SSD), if I put kext to patch in config.plist (For EL 10.11. 6) OSX is slow to restart, but if I remove the patch to kext, OSX is very fast, I do not know if I was clear to express myself, if you want to have a you Tube video.
        PS: I have two SSD NVME, on a I sierra and another Windows, Windows is quick to restart, while Sierra is very slow in the restart and obviously well off, so I thought it appropriate to experiment on a disk not NVME

      • Ok so you have El Capitan installed on a SSD (not a M.2 NVMe SSD) and with the Clover patches in place it takes longer to reboot. Does it take long(er) to reboot with the patched kext as well, or not? If yes, then what you are seeing is the result of NVMe housekeeping. Like I said earlier and I cannot change this.

      • … then you are confirming that the delay is caused by a random write of NVME disc? Pike yesterday … but I have noticed that on 5 consecutive restarts (sudo reboot) 2 of these were quick ..while other 3 no … mhmm Pike … I am stubborn I ..I like to understand what are the problems that can be solved

  23. hello Pike
    can you see?
    2017-01-09 18:49:45 +0100
    Assertion status system-wide:
    BackgroundTask 0
    ApplePushServiceTask 0
    UserIsActive 1
    PreventUserIdleDisplaySleep 0
    PreventSystemSleep 0
    ExternalMedia 1
    PreventUserIdleSystemSleep 0
    NetworkClientActive 0
    Listed by owning process:
    pid 48(powerd): [0x0000000200088005] 00:59:05 ExternalMedia named: “com.apple.powermanagement.externalmediamounted”
    pid 100(hidd): [0x00000cda000981c4] 00:04:17 UserIsActive named: “com.apple.iohideventsystem.queue.tickle.4294968439.3”
    Timeout will fire in 573 secs Action=TimeoutActionRelease
    Kernel Assertions: 0x4=USB
    id=500 level=255 0x4=USB mod=01/01/70, 01:00 description=com.apple.usb.externaldevice.14700000 owner=Silicon-Power8G
    id=501 level=255 0x4=USB mod=01/01/70, 01:00 description=com.apple.usb.externaldevice.14600000 owner=Keyboard Hub
    id=503 level=255 0x4=USB mod=01/01/70, 01:00 description=com.apple.usb.externaldevice.14400000 owner=Gaming Mouse G502
    id=505 level=255 0x4=USB mod=01/01/70, 01:00 description=com.apple.usb.externaldevice.14e00000 owner=ASM107x
    Idle sleep preventers: IODisplayWrangler

  24. Hello,

    I am attempting to install Mac OS Sierra on a 2015 MacBook Pro, and not on a Hackintosh. I am using an ADATA SX8000, which is recognised when booting the laptop in PartedMagic Linux. I am unable to have the Sierra installer recognise the NVMe drive however. The SSD is connected to the computer via a Sintech adapter. Any assistance would be greatly appreciated.

    Matthew,
    Montréal, Canada

      • Hi Matthew,

        Let’s first have a look at the supported modules:

        Samsung XP941 (MZHPU128HCGM MZHPU256HCGL MZHPU512HCGL)
        Samsung SM951 PCIE-AHCI (MZHPV128HDGM MZHPV256HDGL MZHPV512HDGL)

        And here are the listed modules that are supported:

        Samsung SM951 PCIE-NVME (MZVPV128HDGM MZVPV256HDGL MZVPV512HDGL)
        Samsung PM951 PCIE-NVME (MZFLV128HCGR MZFLV256HCHP MZFLV512HCJH)
        Samsung 950 PRO (MZVKV256 MZVKV512)

        The interesting thing here is that all supported modules are AHCI and all modules that are not supported are NVMe. In short. I don’t know if this is going to work, but the fact that you see it under PartedMagic Linux may be an indication that it can/should work – they may not support my hacked up (unsigned) kext.

        1.) You need a patched kext, but that also means that you need to allow unsigned kext to load (think SIP settings). I assume that you know how to do this.

        2.) You either need to rename the factory vanilla kext from IONVMeFamily.kext to something like: IONVMeFamily_kext.original and use a hacked up kext, or replace it with a patched kext.

        3.) You need to lift kext load restrictions (think SIP) in order to get the patched kext to work.

        I myself replaced the factory vanilla IONVMeFamily.kext with a patched kext. Using the same name. This works for me.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s