Become a MacRumors Supporter for $25/year with no ads, private forums, and more!

Upgrading 2013/2014 Macbook Pro SSD to M.2 NVMe

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

otosan

macrumors regular
Aug 9, 2010
125
45
Back in the mid-70s I was a software developer on mini-computers, which meant writing in assembly language—just pointing out that I’m ancient so go easy on me, or don’t. 😉

Back in May 2020, my mid-2014, 15”, 2.5GHz, 512G SSD booted into the black screen with a folder containing a question mark. Nothing I could do would revive it and I found your excellent thread.

I read the first couple pages and bought a 512G Samsung 970 Pro SSD and a Sensico M.2 adapter rather than Sintech (impatient with 2 WK delivery because I was down).

Through dumb luck more than skill, everything worked the first time. I was able to perform an internet install of Catalina (already on that rev before it failed) and got a time machine backup to work. Since then I’ve installed every Catalina update without issue.

My MBP is at Apple Service getting some free work done replacing the delaminating screen and I learned the hard way that I had to remove the non-OEM SSD before they would repair it—back and forth twice to them.

The three problems with nvme SSDs: no Bootcamp, Hibernate hang-up and high power consumption have all bit me but I installed Parallels, used the Terminal command to stop hibernation and live with about 1/2 to 2/3 battery life, which isn’t too bad since I put in a new battery in March because the old one had swollen causing the touch pad to barely function.

While it’s being repaired I’m thinking of getting a used Apple SSD so I have some flexibility. I have a couple questions and would appreciate your collective wisdom.

1. Since my mid-2014 MBP has PCIe 2.0, will it pickup any speed with an SSUBX SSD?

2. I noticed the 1TB SSUBX is wider than my original SSD. Since I don’t have my MBP at the moment, will the 1TB fit?

3. If I don’t buy a used Apple SSD, do you think I will be able be able to migrate to Big Sur with the 970Pro?

4. In your opinions, should I try and get Nvmefix and Lilu to work and will it port to Big Sur?

Thanks for all that all of you have contributed. I’m in your debt.

1. SSUBX will still pick up speed since even though yours is 2.0, it still x4. But again, UBX speed at most is 1200ish

2. 1TB should fit, i see the space is enough.

3. I think you will be able to use NVME drive in big sur.

And btw, you can do bootcamp in NVME drive, been doing it on dozens unit.
 
Comment

Jedi82

macrumors member
Feb 25, 2014
32
6
Sorry to bother you guys one more time but I ask tons just to be sure to do the right thing because I’m a newbie on this.

I still don’t understand the point on disable hibernation and so on on this Mac (because I ignore of course). My Mac now when I close the lid go to sleep, if I leave it awake I see that the screen goes black (after 15 min) but have no problem running macOS underneath and of course I noticed that during the night he lost like 8-10% of battery when close :(

Now, if I set this line with the terminal what it will happen?

I also read a lot about nvmefix and ask if I have to do to install it what I see in a not so dated post here (I linked already) because I never found some guide on the web to do it right

thanks guys!!!!

PS: for example, I just turn on my mbp now in the morning (yesterday night after finish work I just closed the lid) and I discover that my Mac rebooted even if he have now 35% of battery :(

1. Yes, it would be good idea to do that on 2013 models to prevent hibernation issue, also put : darkwakes 0 in those lines as well
2. You dont have to do it just to make thing work, but it would be good addition if your ssd play nice with it.
 
Last edited:
Comment

otosan

macrumors regular
Aug 9, 2010
125
45
Sorry to bother you guys one more time but I ask tons just to be sure to do the right thing because I’m a newbie on this.

I still don’t understand the point on disable hibernation and so on on this Mac (because I ignore of course). My Mac now when I close the lid go to sleep, if I leave it awake I see that the screen goes black (after 15 min) but have no problem running macOS underneath and of course I noticed that during the night he lost like 8-10% of battery when close :(

Now, if I set this line with the terminal what it will happen?

I also read a lot about nvmefix and ask if I have to do to install it what I see in a not so dated post here (I linked already) because I never found some guide on the web to do it right

thanks guys!!!!

PS: for example, I just turn on my mbp now in the morning (yesterday night after finish work I just closed the lid) and I discover that my Mac rebooted even if he have now 35% of battery :(

So let me explain it briefly.

2013-2014 model have issue with hibernation due to broken NVME driver on it's EFI.

The issue itself is : If your macbook went into hibernation state of any kind (whether automatically or manually triggered), it will refuse to wake up properly, and went into those blank screen state.

Solution is to patch your EFI completely using a programmer (which i doubt most of user willing to do) or,

Disable any form of hibernation by config it through terminal, which is using this line of code

sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0 darkwakes 0

by doing so, your macbook will only go into one kind of "sleep", which is screen sleep (by closing your lid, or trigger it using hotkey)

yes your macbook will eat more battery during this "pseudo" sleep, but if you managed to pick up an SSD that have good idle power, it wont draw that much of battery,

one extra thing you might need to do since you are using macbook pro (on macbook air it's disabled by default) is to disable tcpkeepalive as well, so your macbook wont keep waking up due to network connection

you can do this by adding another line on those terminal code above :

tcpkeepalive 0

or, simply turn off your WiFi and Bluetooth before closing the lid. It will do the trick as well.

as for NVMEFix, installing it wont harm you, but whether it can bring extra benefit or not is depends on your SSD.

step is pretty straightforward if you are on Mojave,

1. Disable SIP from recovery (csrutil disable)
2. Enable debug boot args brom recovery as well (nvram boot-args="0x144")
3. Donwload LiLu, NVMEFix kext and Hackintool
4. Install the kext to S/L/E using Hackintool
5. Reboot one or twice and check your idle consumption using iStats menu

for your reference, on one of my installation on 2013-2014 macbook air, it only losing less than 10% of battery if i close the lid and leave it overnight.

But best practice for this model is of course : shut it down when you are not using it.
 
Comment

Jedi82

macrumors member
Feb 25, 2014
32
6
Otosan...you are very very precious, thanks for your amazing posts and reply, for real. So...let's see if I did all good (I will then try nvmefix):

1) open terminal and launch this line: sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0 darkwakes 0 tcpkeepalive 0
2) confirm with my mac password and launch pmset -g command and here is what I read (check also the warning at the beginning) from the console: https://prnt.sc/v5z9da (it's all good or?)
3) instead of just close the lid, I will shut it down when I will not using it

That's it right? Hope for the best about the losing of battery!

EDIT

Just finish to install nvmefix also and I hope I did it the right way. I used Hakintool app to install the two kext and it was not so easy to understand how to do it despite the guide found here.

If I can help someone else newbie like me, I found this tricks to understand how to install kext (paragraph 6 - The Hackintool Method) and here you can find what's the meaning of S/L/E or L/E (wow, so new to me!).

I then reboot my Mac two times and no crash or strange behaviour so I think it's all good now :) With iStats I see this, don't know if it's good or bad values :)

So let me explain it briefly.

2013-2014 model have issue with hibernation due to broken NVME driver on it's EFI.

The issue itself is : If your macbook went into hibernation state of any kind (whether automatically or manually triggered), it will refuse to wake up properly, and went into those blank screen state.

Solution is to patch your EFI completely using a programmer (which i doubt most of user willing to do) or,

Disable any form of hibernation by config it through terminal, which is using this line of code

sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0 darkwakes 0

by doing so, your macbook will only go into one kind of "sleep", which is screen sleep (by closing your lid, or trigger it using hotkey)

yes your macbook will eat more battery during this "pseudo" sleep, but if you managed to pick up an SSD that have good idle power, it wont draw that much of battery,

one extra thing you might need to do since you are using macbook pro (on macbook air it's disabled by default) is to disable tcpkeepalive as well, so your macbook wont keep waking up due to network connection

you can do this by adding another line on those terminal code above :

tcpkeepalive 0

or, simply turn off your WiFi and Bluetooth before closing the lid. It will do the trick as well.

as for NVMEFix, installing it wont harm you, but whether it can bring extra benefit or not is depends on your SSD.

step is pretty straightforward if you are on Mojave,

1. Disable SIP from recovery (csrutil disable)
2. Enable debug boot args brom recovery as well (nvram boot-args="0x144")
3. Donwload LiLu, NVMEFix kext and Hackintool
4. Install the kext to S/L/E using Hackintool
5. Reboot one or twice and check your idle consumption using iStats menu

for your reference, on one of my installation on 2013-2014 macbook air, it only losing less than 10% of battery if i close the lid and leave it overnight.

But best practice for this model is of course : shut it down when you are not using it.
 
Last edited:
  • Like
Reactions: pimu96
Comment

ipadawan

macrumors member
Aug 29, 2019
34
4
Searching and reading on this site and this forum, I didnt not found an answer.

I got a MBP mid 2015 with an Crucial 1TB, it is been there for a few months now. Last week it started getting kernal panics, specialy when I left my MBP for a few minutes along. When I left the MBP for a few minutes alone, or it goes to sleep or I close the lid, it doesn’t react anymore or start blowing very loud. It looks like that the data in Ram is saved, because so far as I can see after a restart the data comes back when I let the MBP open all the files and apps. Often I have to press the power key very long to turn the MBP off. It shows also after the laptop open but not yet in sleep, the question mark to show I have no drive. After turning it down and back on its a gamble thet it starts up correctly. Sometimes it restarts again after the first progress bar at 70%.

I read about that the macbookpro mid 2015 has no pmset issues. But those are my settings.

pmset -g | grep standby
standbydelayhigh 86400
standby 1
standbydelaylow 10800
highstandbythreshold 50

pmset -g | grep hibernatemode
hibernatemode 3

Are those weird settings?

I am not sure if this started with the latest Catalina update 10.15.7
Does some other people here having the same issue? Does it helps if I compile the NVMEFix and install the kext?

Are there settings that I could try?
My silent knight info looks oke, but if some needs it,I will show them here.
 
Comment

Pametfisher

macrumors newbie
Oct 23, 2020
9
1
Thanks Otosan, for the detailed answer to my questions and Jedi82. It fills in some gaps I didn’t completely follow after reading the preceding 298 pages. I wish I’d bought a Sabrent, rather than the 970 pro, maybe I’ll change it.
 
  • Like
Reactions: otosan
Comment

otosan

macrumors regular
Aug 9, 2010
125
45
Otosan...you are very very precious, thanks for your amazing posts and reply, for real. So...let's see if I did all good (I will then try nvmefix):

1) open terminal and launch this line: sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0 darkwakes 0 tcpkeepalive 0
2) confirm with my mac password and launch pmset -g command and here is what I read (check also the warning at the beginning) from the console: https://prnt.sc/v5z9da (it's all good or?)
3) instead of just close the lid, I will shut it down when I will not using it

That's it right? Hope for the best about the losing of battery!

EDIT

Just finish to install nvmefix also and I hope I did it the right way. I used Hakintool app to install the two kext and it was not so easy to understand how to do it despite the guide found here.

If I can help someone else newbie like me, I found this tricks to understand how to install kext (paragraph 6 - The Hackintool Method) and here you can find what's the meaning of S/L/E or L/E (wow, so new to me!).

I then reboot my Mac two times and no crash or strange behaviour so I think it's all good now :) With iStats I see this, don't know if it's good or bad values :)

0.14A on Idle looks good.
 
  • Like
Reactions: X3m
Comment

herb2k

macrumors regular
Jun 8, 2020
100
40
Has anybody tried what this guy does in this video?


Not sure what the Linux step is for - at the end of his video he mentioned he needed to use an OEM SSD to perform the upgrade and have the appropriate firmware flashed. Other than that, it's pretty much a step by step summary of the first post of this thread :)
 
Comment

dcrosb123

macrumors newbie
May 26, 2020
5
0
As far as NVMEFix goes, why is Mojave suggested instead of say Catalina? Is it likely it'll end up working with Big Sur too? Just trying to see if I should try installing as I'm currently on Catalina and would like to upgrade to Big Sur once the final is released. Thanks!
 
Comment

herb2k

macrumors regular
Jun 8, 2020
100
40
As far as NVMEFix goes, why is Mojave suggested instead of say Catalina? Is it likely it'll end up working with Big Sur too? Just trying to see if I should try installing as I'm currently on Catalina and would like to upgrade to Big Sur once the final is released. Thanks!

I use it on Catalina, works fine.

Nobody is sure about compatibility yet with Big Sur - I have tried a couple of times and no luck (yet!)
 
Comment

quaresma

macrumors regular
Jan 20, 2013
119
206
As far as NVMEFix goes, why is Mojave suggested instead of say Catalina? Is it likely it'll end up working with Big Sur too? Just trying to see if I should try installing as I'm currently on Catalina and would like to upgrade to Big Sur once the final is released. Thanks!

I am thinking of downgrading to Mojave, because NVMeFix is just not working correctly on Catalina. After a couple of days it stops loading. It works fine the first day or two, but then suddenly it stops working. Don’t know why?

Maybe I’ll try Big Sur once its released, but I’m usually not comfortable installing the first version of a new OS.
 
Comment

Jedi82

macrumors member
Feb 25, 2014
32
6
How do you know and check if nvmefix is loading fine? I don’t see the tool on my Mac except from the system library kext file
 
Comment

mo5214

macrumors member
Sep 20, 2019
68
46
Soooo, finally here I am again with another test with my MBPro Late 2013 15''. Here is what I did:

1) mount my new Sabrent Rocket NVMe PCIe M.2 2280 SSD 512GB with my Sintech short adapter
2) install a fresh copy of Catalina with APFS encrypted file system (maybe it's this the cause...)
3) set all the basics and noticed since the beginning that my Mac is more fast
4) Boot ROM version: 162.0.0.0.0
5) System report... of my new SSD on my Mac
6) changed thermal paste on my Mac that is soooo clean and perfect
7) tested 3 of my Sintech adapters (I bought three of them)

This is my new video benchmark of the disk...why so slow? It's not good :( -->https://streamable.com/jlwkpo

The system as ended indexing my disk, I'm not doing nothing heavy, system is now very empty so...what can I do?

UPDATE: tried one more time with one of my Sintech adapter and now it's seems OK and have constant values: https://prnt.sc/v4rgl3. Maybe it's not always the same speed when testing?

Now I'm asking what's next:

1) Do i have also to open terminal and apply this: sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0 ?
2) Do i have to install and set NVMEfix like I see here on this quick guide?

PS: Did you also noticed, when reboot that the MBP stay a little longer with a black screen and then start booting normally?


1: 2015 models -> no. 2013-2014 -> yes.
2: it is good to have, as it reduces idle SSD power consumption on some NVMe drives (I read on here that for some SSDs it didn't work.)
[automerge]1603718492[/automerge]
How do you know and check if nvmefix is loading fine? I don’t see the tool on my Mac except from the system library kext file

IORegExplorer. Search for NVMe and if you see NVMeFix module. You are golden
 
Comment

Jedi82

macrumors member
Feb 25, 2014
32
6
1: 2015 models -> no. 2013-2014 -> yes.
2: it is good to have, as it reduces idle SSD power consumption on some NVMe drives (I read on here that for some SSDs it didn't work.)
[automerge]1603718492[/automerge]


IORegExplorer. Search for NVMe and if you see NVMeFix module. You are golden

soooooo, I think I'm fine right? :) --> https://prnt.sc/v7njxc
 
Comment

Spiros Poullos

macrumors newbie
Oct 1, 2020
8
1
My 2TB Silicon Power NVME arrived!
Monday I'm picking up from the post office my Sintech Adapter as well!
IMG_20201028_202906.jpg
IMG_20201028_202906.jpg
 
  • Like
Reactions: macpro_mid2014
Comment

whyso

macrumors newbie
Aug 20, 2020
17
1
Hi, Im getting a shutdown report sometimes when my MBP 13" Late 2013 with Sintech long adapter + Samsung 970 PRO. any solution for this issue? Expand the quote below for the full report.

Sleep Wake failure in EFI





Failure code:: 0x0131150e 0x0000001f





Please IGNORE the below stackshot





================================================================


Date/Time: 2020-10-29 19:53:01 +0500


OS Version: ??? ??? (Build ???)


Architecture: x86_64


Report Version: 29





Data Source: Stackshots


Shared Cache: 0xcc45000 3DBADAB6-C9D0-30D5-BC26-BAC41D2318DF





Event: Sleep Wake Failure


Duration: 0.00s


Steps: 1





Time Awake Since Boot: 18s











Process: swd [271]


Architecture: x86_64


Footprint: 376 KB


Start time: 2020-10-29 19:53:01 +0500


End time: 2020-10-29 19:53:01 +0500


Num samples: 1 (1)





Thread 0x72f 1 sample (1) priority 4 (base 4)


<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>


1 start + 1 (libdyld.dylib + 70661) [0x7fff70968405] 1


1 ??? [0x10e2b2454] 1


1 ??? [0x10e2b21dd] 1


1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 135942) [0x7fff70ad1306] 1


*1 ??? [0xffffff80002e7206] 1


*1 ??? [0xffffff800099b999] 1


*1 ??? [0xffffff80008b4a31] 1


*1 ??? [0xffffff800030a387] (running) 1





Binary Images:


0x7fff70957000 - 0x7fff7098cfff libdyld.dylib (732.8) <98960E27-A08B-36DA-A5CB-8538B2D6757E> /usr/lib/system/libdyld.dylib


0x7fff70ab0000 - 0x7fff70adcfff libsystem_kernel.dylib (6153.11.26) <4CE9D54A-A975-348E-B878-EE74EDFC956B> /usr/lib/system/libsystem_kernel.dylib


Model: MacBookPro11,1, BootROM 162.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2.4 GHz, 4 GB, SMC 2.16f68


Graphics: kHW_IntelIrisItem, Intel Iris, spdisplays_builtin


Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343235533641465236412D50422020


Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343235533641465236412D50422020


AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.77.105.1 AirPortDriverBrcmNIC-1429)


Bluetooth: Version 7.0.0f8, 3 services, 27 devices, 1 incoming serial ports


Network Service: Wi-Fi, AirPort, en0


USB Device: USB 3.0 Bus


USB Device: Internal Memory Card Reader


USB Device: Apple Internal Keyboard / Trackpad


USB Device: BRCM20702 Hub


USB Device: Bluetooth USB Host Controller


Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2
 
Comment

otosan

macrumors regular
Aug 9, 2010
125
45
Hi, Im getting a shutdown report sometimes when my MBP 13" Late 2013 with Sintech long adapter + Samsung 970 PRO. any solution for this issue? Expand the quote below for the full report.

"Sleep Wake Issue" clearly written. Your mac is 2013 model which have broken sleep. So you should disable any kind of sleep from terminal.

sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0 darkwakes 0 tcpkeepalive 0
 
Comment
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.