Contribute
Register

Hack recognizes NVMe Samsung 960 PRO but can't find system files on startup

Status
Not open for further replies.
Joined
Feb 27, 2017
Messages
59
Motherboard
Gigabyte Gaming 3 GA-H270
CPU
i7-7700K
Graphics
GTX 1050 Ti
Mac
  1. iMac
I am working on my second build.

OS X 10.12.3

only hardware needing to be mentioned is the NVMe SSD Samsung 960 PRO M.2

I am trying to use the Samsung 960 PRO as the boot drive.

I got it working OS X to recognize the drive with this patch and kext

http://www.insanelymac.com/forum/to...g-nvme-under-macos-sierra-is-ready/(hopefully links are allowed)

kext: NMVEFamily.kext


Everything works great until: I complete the multibeast setup and then reboot. Instead on booting I get a circle and slash sign, prohibitory sign, where the apple should be.

I looked this up and it says It means the OS can't find a system folder to startup off of.

If anybody has anything they think I might try to get that fixed please let me know.

I will post a copy of my config.plist for the newest hack Samsung 960 PRO/efi/clover/config.plist

thanks.



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ACPI</key>
<dict>
<key>DSDT</key>
<dict>
<key>Debug</key>
<false/>
<key>DropOEM_DSM</key>
<false/>
<key>Fixes</key>
<dict>
<key>AddDTGP_0001</key>
<false/>
<key>AddHDMI_8000000</key>
<false/>
<key>AddIMEI_80000</key>
<false/>
<key>AddMCHC_0008</key>
<false/>
<key>AddPNLF_1000000</key>
<false/>
<key>DeleteUnused_400000</key>
<false/>
<key>FIX_ACST_4000000</key>
<false/>
<key>FIX_ADP1_800000</key>
<false/>
<key>FIX_INTELGFX_100000</key>
<false/>
<key>FIX_RTC_20000</key>
<false/>
<key>FIX_S3D_2000000</key>
<false/>
<key>FakeLPC_0020</key>
<false/>
<key>FiX_TMR_40000</key>
<false/>
<key>FiX_WAK_200000</key>
<false/>
<key>FixAirport_4000</key>
<false/>
<key>FixDarwin_0002</key>
<false/>
<key>FixDisplay_0100</key>
<false/>
<key>FixFirewire_0800</key>
<false/>
<key>FixHDA_8000</key>
<false/>
<key>FixHPET_0010</key>
<false/>
<key>FixIDE_0200</key>
<false/>
<key>FixIPIC_0040</key>
<false/>
<key>FixLAN_2000</key>
<false/>
<key>FixRegions_10000000</key>
<false/>
<key>FixSATA_0400</key>
<false/>
<key>FixSBUS_0080</key>
<false/>
<key>FixShutdown_0004</key>
<false/>
<key>FixUSB_1000</key>
<false/>
<key>NewWay_80000000</key>
<false/>
</dict>
<key>Name</key>
<string>DSDT.aml</string>
<key>Patches</key>
<array>
<dict>
<key>Comment</key>
<string>Rename HDAS to HDEF</string>
<key>Find</key>
<data>
SERBUw==
</data>
<key>Replace</key>
<data>
SERFRg==
</data>
</dict>
</array>
<key>ReuseFFFF</key>
<false/>
</dict>
<key>HaltEnabler</key>
<false/>
<key>SSDT</key>
<dict>
<key>DropOem</key>
<false/>
<key>Generate</key>
<dict>
<key>CStates</key>
<false/>
<key>PStates</key>
<false/>
</dict>
</dict>
</dict>
<key>Boot</key>
<dict>
<key>Arguments</key>
<string>dart=0</string>
<key>DefaultVolume</key>
<string>Samsung 960 PRO</string>
<key>Legacy</key>
<string>PBR</string>
<key>Log</key>
<true/>
<key>Secure</key>
<false/>
<key>Timeout</key>
<integer>3</integer>
<key>XMPDetection</key>
<string>NO</string>
</dict>
<key>Devices</key>
<dict>
<key>Audio</key>
<dict>
<key>Inject</key>
<string>1</string>
</dict>
<key>FakeID</key>
<dict>
<key>ATI</key>
<string>0x0</string>
<key>IMEI</key>
<string>0x0</string>
<key>IntelGFX</key>
<string>0x0</string>
<key>LAN</key>
<string>0x0</string>
<key>NVidia</key>
<string>0x0</string>
<key>SATA</key>
<string>0x0</string>
<key>WIFI</key>
<string>0x0</string>
<key>XHCI</key>
<string>0x0</string>
</dict>
<key>USB</key>
<dict>
<key>FixOwnership</key>
<false/>
<key>Inject</key>
<false/>
</dict>
<key>UseIntelHDMI</key>
<false/>
</dict>
<key>DisableDrivers</key>
<array>
<string>Nothing</string>
</array>
<key>GUI</key>
<dict>
<key>Hide</key>
<array>
<string>Windows</string>
<string>\EFI\BOOT\BOOTX64.EFI</string>
</array>
<key>Language</key>
<string>en:0</string>
<key>Mouse</key>
<dict>
<key>Enabled</key>
<true/>
<key>Speed</key>
<integer>8</integer>
</dict>
<key>Scan</key>
<dict>
<key>Entries</key>
<true/>
<key>Legacy</key>
<string>First</string>
<key>Tool</key>
<true/>
</dict>
<key>ScreenResolution</key>
<string>1920x1080</string>
<key>Theme</key>
<string>tonymacx86</string>
</dict>
<key>Graphics</key>
<dict>
<key>Inject</key>
<dict>
<key>ATI</key>
<false/>
<key>Intel</key>
<true/>
<key>NVidia</key>
<false/>
</dict>
</dict>
<key>KernelAndKextPatches</key>
<dict>
<key>AppleRTC</key>
<true/>
<key>AsusAICPUPM</key>
<true/>
<key>KernelCpu</key>
<false/>
<key>KernelHaswellE</key>
<false/>
<key>KernelLapic</key>
<false/>
<key>KernelPm</key>
<true/>
<key>KextsToPatch</key>
<array>
<dict>
<key>Comment</key>
<string>External icons patch</string>
<key>Find</key>
<data>
RXh0ZXJuYWw=
</data>
<key>Name</key>
<string>AppleAHCIPort</string>
<key>Replace</key>
<data>
SW50ZXJuYWw=
</data>
</dict>
<dict>
<key>Comment</key>
<string>Increase 15 port limit to 26 in AppleUSBXHCIPCI</string>
<key>Find</key>
<data>
g710////EA==
</data>
<key>Name</key>
<string>AppleUSBXHCIPCI</string>
<key>Replace</key>
<data>
g710////Gw==
</data>
</dict>
</array>
</dict>
<key>RtVariables</key>
<dict>
<key>BooterConfig</key>
<string>0x28</string>
<key>CsrActiveConfig</key>
<string>0x3</string>
</dict>
<key>SMBIOS</key>
<dict>
<key>BiosReleaseDate</key>
<string>09/03/2013</string>
<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>BiosVersion</key>
<string>IM142.88Z.0118.B00.1309031249</string>
<key>Board-ID</key>
<string>Mac-27ADBB7B4CEE8E61</string>
<key>BoardManufacturer</key>
<string>Apple Inc.</string>
<key>BoardType</key>
<integer>10</integer>
<key>ChassisAssetTag</key>
<string>iMac-Aluminum</string>
<key>ChassisManufacturer</key>
<string>Apple Inc.</string>
<key>ChassisType</key>
<string>13</string>
<key>Family</key>
<string>iMac</string>
<key>Manufacturer</key>
<string>Apple Inc.</string>
<key>Mobile</key>
<false/>
<key>ProductName</key>
<string>iMac14,2</string>
<key>SerialNumber</key>
<string>C02NRD7HFLHH</string>
<key>Trust</key>
<false/>
<key>Version</key>
<string>1.0</string>
</dict>
<key>SystemParameters</key>
<dict>
<key>InjectKexts</key>
<string>YES</string>
<key>InjectSystemID</key>
<true/>
<key>NvidiaWeb</key>
<false/>
</dict>
</dict>
</plist>
 
I've been over this article a lot. I don't have a windows machine to work with.
 
I've been over this article a lot. I don't have a windows machine to work with.

Your computer can run Windows.
Windows 10 takes only about 15 minutes to install to a fast NVMe SSD from USB3 stick.
 
thank for the replay. I am currently downloading the Windows 10 ISO.

however I got the Samsung 960 PRO to be recognized and OS X 10.12.3 installed. However after I do the OS X setup and run multibeast and restart I get the Prohibitory symbol halfway through the boot.
 

So I folled Mork Vom Ork's guide on insanely Mac and my problem was that I didn't copy the clover EFI folder from the USB drive to the EFI folder of the new NVMe SSD. As soon as I did that the prohibitory sign on boot went away and I was able to boot into OS X. However every time I boot up into OS X it says " the drive you inserted in not recognizable by this computer" with options to initialize, ignore, and eject. It doesn't seem to be affecting anything. not sure though. wondering how I can get this error message to go away on startup?

your guide with the class code spoof I believe is over my head. I went over it many times but after I found my SSD path in Device manager I kind of got lost at the code part.

thanks for you help. you've been a great resource for getting the NVMe SSD up and running.
 
However every time I boot up into OS X it says " the drive you inserted in not recognizable by this computer" with options to initialize, ignore, and eject. It doesn't seem to be affecting anything. not sure though. wondering how I can get this error message to go away on startup?

It probably means you have a disk connected to your system that has no HFS+ or NTFS partitions...

your guide with the class code spoof I believe is over my head. I went over it many times but after I found my SSD path in Device manager I kind of got lost at the code part.

Work on it in your spare time... because it is definitely the only sane way to deal with system updates...
 
It probably means you have a disk connected to your system that has no HFS+ or NTFS partitions...



Work on it in your spare time... because it is definitely the only sane way to deal with system updates...


Thanks again for the input.

Yes I will work on it.

Maybe ill be able to find some people with my skill level to help explain it better.

Thanks again for all your help.
 
Status
Not open for further replies.
Back
Top