Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe
- Thread starter maxthackray
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Nope, NVMe are the ‘polaris’ drives that came after SSUBX. The latter are a safe upgrade.
Nope, NVMe are the ‘polaris’ drives that came after SSUBX. The latter are a safe upgrade.
I was under the impression that the Pros ran hotter/used more power than the EVOs. Maybe it is just that same generation though (e.g. 960 Pro vs 960 EVO and 970 Pro vs 970 EVO)
Connecting my 2.5 370x to my 4K does cause my fans to spin up, but they do settle down shortly after.
I'm pretty happy with it. Performance is very fast and I've had no problems with it so far. It's only 512GB though, so I was thinking about upgrading to a larger size 1TB 970 Pro or EVO or possibly a larger 960 Pro.
The system is a 2015 15" model, so I don't have sleep/kernel panic problems.
As far as I know, the 970 Evo runs pretty hot, hotter than the Pro sibling.
Excellent, this is encouraging to hear.
As I have a 970 EVO 2TB in my 2015 2.2ghz 15" and it's running super cool - I actually would like to help test this.
When people say "it's far hotter" - What temperature numbers are considered cool or hot (or not)?
I'm blown away with what a great match mine is so far in this machine.
It appears to be running cool as a cucumber so far, but I'd like to help contribute here if possible.
Does it make sense to first put the replacement NVME drive into an external USB enclosure, clone the internal drive to it and make it bootable, then install the NVME drive into the MacBook Pro?
I have a 256GB internal drive and got a 256GB USB flash drive, wasn't able to clone due to usable space being slightly smaller on the USB flash drive, but have multiple Time Machine backups and a (non-bootable) disk image.
I'm paranoid about attempting this without a working bootable clone LOL.
I have a 256GB internal drive and got a 256GB USB flash drive, wasn't able to clone due to usable space being slightly smaller on the USB flash drive, but have multiple Time Machine backups and a (non-bootable) disk image.
I'm paranoid about attempting this without a working bootable clone LOL.
To me, it makes more sense to update to create a CCC or TM backup, create a HS or Mojave installer, update to the latest Mojave release to ensure the MBP is running the latest bootrom, swap out the drives, boot from TM or CCC and restore to the nvme drive. This method avoids having to buy an nvme enclosure that you may use only once.
SUMMARY
Thanks for all the inputs. Let me summarize the results so far:
- MBP 2013-2015 can be upgraded by using an adapter from Sintech (B oder C revision) and a PCIe M.2 SSD.
- on 2013 and 2014 MBP there are sleep/hibernation issues. The workaround is to disable hibernation.
- by updating Bootrom to the HS or Mojave version, NVMe (quicker transfer) can be enabled (SSD must also support that). Transfer speeds can be much higher then on PCIe x4 MBPs (e.g. 15" models).
- 2 ways to resolve sleep issues on MBP 2013 and 2014: modify bootrom by either 1) SPI programmer + J6100 connector (post 1801 and youtube below) OR (a bit safer): 2) by using a Matt card and a SPI programmer. However, a Matt card costs about 60 EUR. (Post #1281,2791) www.cmizapper.com/products/mattcard.html
- many SSD draw more power than the original Apple SSD. The Samsung SSD are known to have a rather high power surge (Post 1776 recommends Adata XPG SX8200, also Intel 760p is often recommended).
Please correct me if you find mistakes. I will update this post.
Thanks for all the inputs. Let me summarize the results so far:
- MBP 2013-2015 can be upgraded by using an adapter from Sintech (B oder C revision) and a PCIe M.2 SSD.
- on 2013 and 2014 MBP there are sleep/hibernation issues. The workaround is to disable hibernation.
- by updating Bootrom to the HS or Mojave version, NVMe (quicker transfer) can be enabled (SSD must also support that). Transfer speeds can be much higher then on PCIe x4 MBPs (e.g. 15" models).
- 2 ways to resolve sleep issues on MBP 2013 and 2014: modify bootrom by either 1) SPI programmer + J6100 connector (post 1801 and youtube below) OR (a bit safer): 2) by using a Matt card and a SPI programmer. However, a Matt card costs about 60 EUR. (Post #1281,2791) www.cmizapper.com/products/mattcard.html
- many SSD draw more power than the original Apple SSD. The Samsung SSD are known to have a rather high power surge (Post 1776 recommends Adata XPG SX8200, also Intel 760p is often recommended).
Please correct me if you find mistakes. I will update this post.
Last edited:
Maybe you can add that besides the Matt Card one could use an SPI programmer + J6100 connector to directly program the onboard bootrom
This is probably just related to my system, but just a PSA.
I was getting some odd slowdowns on new web tabs and a couple hiccups here and there (all were tolerable, but seemed odd).
I ended up doing a fresh install of Mojave and not using Migration Assistant. I copied over my files manually and "did it the old way" and have been re-installing Applications, etc.
Smooth as silk now.
Again - this is most likely due to something legacy that was hanging around on my particular system, but it did remind me that even as nice as Migration Assistant is, at some point it's never a bad idea to start with a fresh install.
These 2015's really are the perfect candidates for this upgrade.
Everything about this feels totally genuine/OEM and native. Everything works perfectly as one would expect. I'm really happy about that, especially having been in the Hackintosh world for the better part of this decade.
That said - I am back to thinking about another Hack actually (for my desktop setup). haha
I was getting some odd slowdowns on new web tabs and a couple hiccups here and there (all were tolerable, but seemed odd).
I ended up doing a fresh install of Mojave and not using Migration Assistant. I copied over my files manually and "did it the old way" and have been re-installing Applications, etc.
Smooth as silk now.
Again - this is most likely due to something legacy that was hanging around on my particular system, but it did remind me that even as nice as Migration Assistant is, at some point it's never a bad idea to start with a fresh install.
These 2015's really are the perfect candidates for this upgrade.
Everything about this feels totally genuine/OEM and native. Everything works perfectly as one would expect. I'm really happy about that, especially having been in the Hackintosh world for the better part of this decade.
That said - I am back to thinking about another Hack actually (for my desktop setup). haha
Hello! I have Samsung Evo 960 ssd in my MBP 13'' 2014 installed. for a year. All working good except one thing:
after booting to BootCamp and rebooting back to macOS i've getting kernel panics sometimes. 2 or 3 KP before normal boot
Anybody have the same issue? Is it possible to fix it?
Maybe this issue already listed here and some solutions already exists, but i didn't found anything.
after booting to BootCamp and rebooting back to macOS i've getting kernel panics sometimes. 2 or 3 KP before normal boot
Code:
Anonymous UUID: E63ED211-D3EA-AD10-7658-97D624EFF929
Tue Dec 25 02:31:19 2018
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8cf05172): nvme: "Fatal error occurred. CSTS=0x3 US[1]=0x0 US[0]=0x84 VID/DID=0xa804144d
. FW Revision=3B7QCXE7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.230.1/IONVMeController.cpp:5327
Backtrace (CPU 0), Frame : Return Address
0xffffff91f9673a10 : 0xffffff8009daeafd
0xffffff91f9673a60 : 0xffffff8009ee85a3
0xffffff91f9673aa0 : 0xffffff8009ed9fca
0xffffff91f9673b10 : 0xffffff8009d5bca0
0xffffff91f9673b30 : 0xffffff8009dae517
0xffffff91f9673c50 : 0xffffff8009dae363
0xffffff91f9673cc0 : 0xffffff7f8cf05172
0xffffff91f9673e20 : 0xffffff800a45dd87
0xffffff91f9673e90 : 0xffffff800a45dca9
0xffffff91f9673ec0 : 0xffffff8009deaf65
0xffffff91f9673f40 : 0xffffff8009deab15
0xffffff91f9673fa0 : 0xffffff8009d5b0ce
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[E3F646E0-5B0C-3ABC-88D1-728309F221C8]@0xffffff7f8cef0000->0xffffff7f8cf2ffff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A69BF990-ABB3-3731-A7A2-9C1FB76BCF6F]@0xffffff7f8b084000
dependency: com.apple.iokit.IOPCIFamily(2.9)[7EA30FDD-A2FB-390F-99DD-42BC19691BB4]@0xffffff7f8a695000
dependency: com.apple.driver.AppleEFINVRAM(2.1)[E68F9756-227E-3378-8E22-F37409594A7F]@0xffffff7f8b10a000
dependency: com.apple.iokit.IOStorageFamily(2.1)[7D6A3E9B-D1CD-3F8B-9800-C4B943806679]@0xffffff7f8ae83000
dependency: com.apple.iokit.IOReportFamily(47)[75A625B5-0DEB-343A-A723-9D72533F098C]@0xffffff7f8aa49000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
18C54
Kernel version:
Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64
Kernel UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9
Kernel slide: 0x0000000009a00000
Kernel text base: 0xffffff8009c00000
__HIB text base: 0xffffff8009b00000
System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)
System uptime in nanoseconds: 57378326753
last loaded kext at 2168659320: com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.9f2 (addr 0xffffff7f8cfa6000, size 49152)
loaded kexts:
com.Logitech.Control Center.HID Driver 3.9.7
com.joshuawise.kexts.HoRNDIS 6
com.apple.iokit.IOBluetoothUSBDFU 6.0.9f2
com.apple.driver.AppleUSBStorageCoexistentDriver 456.230.1
com.apple.driver.AppleUSBCardReader 456.230.1
com.apple.driver.AppleUSBTCKeyEventDriver 254
com.apple.driver.AppleUSBTCButtons 254
com.apple.driver.AppleUSBTCKeyboard 254
com.apple.iokit.SCSITaskUserClient 408.200.1
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.driver.AppleVirtIO 2.1.2
com.apple.filesystems.hfs.kext 407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleSystemPolicy 1.0
com.apple.filesystems.apfs 945.230.6
com.apple.driver.AirPort.BrcmNIC 1400.1.1
com.apple.private.KextAudit 1.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 6.1
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 6.1
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 190
com.apple.security.TMSafetyNet 8
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.9f2
com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.9f2
com.apple.iokit.IOBluetoothHostControllerTransport 6.0.9f2
com.apple.iokit.IOUSBMassStorageClass 4.0.4
com.apple.driver.AppleUSBMultitouch 263
com.apple.driver.IOBluetoothHIDDriver 6.0.9f2
com.apple.iokit.IOBluetoothFamily 6.0.9f2
com.apple.iokit.IOUSBHIDDriver 900.4.2
com.apple.driver.usb.AppleUSBHub 1.2
com.apple.driver.AppleUSBAudio 315.6
com.apple.driver.usb.IOUSBHostHIDDevice 1.2
com.apple.iokit.IOAudioFamily 206.5
com.apple.vecLib.kext 1.2.0
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2
com.apple.driver.AppleThunderboltDPInAdapter 5.5.8
com.apple.driver.AppleThunderboltDPAdapterFamily 5.5.8
com.apple.driver.AppleThunderboltPCIUpAdapter 2.1.4
com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.4
com.apple.driver.AppleHPM 3.3.0
com.apple.driver.AppleIntelLpssI2CController 3.0.60
com.apple.driver.AppleIntelLpssDmac 3.0.60
com.apple.driver.AppleIntelLpssI2C 3.0.60
com.apple.iokit.IOSerialFamily 11
com.apple.filesystems.hfs.encodings.kext 1
com.apple.driver.AppleUSBMergeNub 900.4.2
com.apple.driver.AppleXsanScheme 3
com.apple.iokit.IONVMeFamily 2.1.0
com.apple.driver.AppleThunderboltNHI 4.7.6
com.apple.iokit.IOThunderboltFamily 6.8.1
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.driver.corecapture 1.0.4
com.apple.driver.AppleIntelLpssGspi 3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI 1.2
com.apple.driver.usb.AppleUSBXHCI 1.2
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.iokit.IOUSBFamily 900.4.2
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.quarantine 3
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 493.0.0
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleUSBTDM 456.230.1
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.kext.CoreTrust 1
com.apple.iokit.IOUSBMassStorageDriver 145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice 408.200.1
com.apple.iokit.IOSCSIArchitectureModelFamily 408.200.1
com.apple.iokit.IOStorageFamily 2.1
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.iokit.IOUSBHostFamily 1.2
com.apple.driver.usb.AppleUSBCommon 1.0
com.apple.driver.AppleBusPowerController 1.0
com.apple.driver.AppleSEPManager 1.0.1
com.apple.driver.IOSlaveProcessor 1
com.apple.iokit.IOTimeSyncFamily 700.7
com.apple.iokit.IONetworkingFamily 3.4
com.apple.iokit.IOReportFamily 47
com.apple.driver.AppleACPIPlatform 6.1
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
EOFMaybe this issue already listed here and some solutions already exists, but i didn't found anything.
I had also struggled with this KP for months, since I installed 960evo on my MBP-2014mid. For months, I had tried to solve this problem with various trials such as clean-installation, retaping kapton tape, replacing new adapter, but anything hadn't worked. Finally I bought HP Ex920 512g and re-installed it about a month ago, and this KP has completely gone. (You can see my histories in my posts.) I assume this was some compatibility problem between Samsung ssd and macbook, related to power draw.
thank you for answer!
What about speed test on HP ssd? my evo have 1200/1200mbps
Reseting the SMC and then the PRAM solved de KP problems after using Boot Camp for me.
Reset SMC -> pay close attention to the instructions
Reset PRAM
Are you resetting it after every bootcamp usage? I was making single resets a lot of times during this year with custom ssd
I have the DG 2.5 2015 15" with a 1tb 970 EVO and tbh I rarely hear the fan spin up and I'm using Logic Pro X with multiple effects / plug-in's so it's under load regularly. I'm also permanently connected to my Clarett audio interface via Thunderbolt 2 so the I/O is under load as well.
Out of curiosity, what was the reported SSD temperature and ambient room temperature?
Last edited:
Which machine do you mean?
I only have the 2.2 now.
Winter and cold here though, with both machines, as all testing of this was in the last 2weeks
I still have never even heard the fans on the 2.2.
What an awesome machine (for me)!
Ok, I finally had time during the holidays to finish it. It worked with a bootable mojave installer USB. I had a lot of troubles restoring from time machine and ended up installing a fresh Mojave and restored data from the setup menu then. I don't know, but 3 different and new time machine backup restores failed during restoring via the bootable stick.
Nevermind though: it works now. Will give you updates on how it runes with my 2014 macbook.
Thanks for your help guys
Yes, after every usage. I have no idea what it is, but I think windows is messing with some registers that a simple power cycle doesn't clean. And because of that, I avoid using bootcamp whenever I can. I only boot it for games now and when I want any other feature, I use Virtual Box.
Hi loki.
On amazon (italy) the Crucial P1 is on a good deal just for today. Did you have any issue with it ? Which macbook pro are you using ? Any relevant difference compared to the original apple ssd expecially regarding battery and speed ?
Thank you.
Hi
Crucial P1 uses QLC nand. Unless you know what it means, avoid it and consider other MLC or TLC drives. QLC will be ok for a very light use, but not at all with an intense use : it has a low write cycles capability,
low TBW, low speed once SLC cache has been filled (70MB/s) and high power drain (3W during up to 30 minutes) after long write operations which have used SLC cache.