Toggle sidebar Toggle sidebar
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

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.
Audit13 said:
PMset: https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-29#post-25703979
Click to expand...
sleepimage files doesn't seem to exist
PnETJRr.png


Files that exist
nHFt2DP.png
 
I believe Hibernate mode = 0 means the contents in ram are not saved to the SSD which probably explains the lack of a sleep image.

Mode 3 and 25 stores a copy of the ram contents to the drive.
 
Audit13 said:
I believe Hibernate mode = 0 means the contents in ram are not saved to the SSD which probably explains the lack of a sleep image.

Mode 3 and 25 stores a copy of the ram contents to the drive.
Click to expand...
Ok, still any reason why I'm getting crashes and kernel panics. Is this a 10.14 update?
 
I also get crashes just setting hibernate mode to 0. I additionally had to switch off autopoweroff, which fixed the crashes.

Note I also raised standbydelay as well as autopoweroffdelay to 60488 (=one week), however, I am not sure if this is required. I initially rust raised the standbydelay, which helped a bit - the MBP did not crash after one day sleep, but crashed after a period longer than 2 days (not sure why).

Anyway, as stated above, hibernate=0 and autopoweroff=0 fixed it.

Here's my pmset -g output (Macbook Pro 15 late 2013):

Currently in use:
standbydelay 604800
standby 1
womp 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 1
gpuswitch 2
networkoversleep 0
disksleep 10
sleep 180
autopoweroffdelay 604800
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 180
acwake 0
lidwake 1
 
  • Like
Reactions: minivan09ia and ponta pon pon
My Dime Is Up said:
Ok, still any reason why I'm getting crashes and kernel panics. Is this a 10.14 update?
Click to expand...
There was a bootrom update with 10.14.1, not with 10.14.2.

An update to the latest Mojave may help.

When I updated my early 2015 13" to 10.14.1, the bootrom was updated even though it was running an Intel 600p internally. It's the first time that my air accepted a bootrom update with a third party internal nvme drive.
 
I just installed the NGFF ST-NGFF2013-C and it arrived from China.
Installed a 970 EVO 512 and am getting great speeds.

Original APPLE SSD was getting 650/716
New Samsung 970 Evo is getting 1350/1500

After clean installing 10.14.2, then migrating from cloned SSD of my drive, the fans were going nuts and the temps seemed high. I don't know what the temps were like before with stock Apple SSD blade, but I notice fans more with this Samsung 970. Has anyone else experienced this?
 
buzzworm said:
After clean installing 10.14.2, then migrating from cloned SSD of my drive
Click to expand...

I'm about to do this tomorrow myself..

I'm wondering if there is good reason or best practice perhaps to do a clean install of 10.14.2 and then just migrate over user data but manually reinstall Apps?

Sometimes I use new drives/machines as a chance to refresh that aspect of my setup and start anew.

Any reason to do that here (or not)?

Otherwise my plan is to do the fresh Mojave install but do a Migration Assistant from one of my USB connected Time Machines.
 
buzzworm said:
I just installed the NGFF ST-NGFF2013-C and it arrived from China.
Installed a 970 EVO 512 and am getting great speeds.

Original APPLE SSD was getting 650/716
New Samsung 970 Evo is getting 1350/1500

After clean installing 10.14.2, then migrating from cloned SSD of my drive, the fans were going nuts and the temps seemed high. I don't know what the temps were like before with stock Apple SSD blade, but I notice fans more with this Samsung 970. Has anyone else experienced this?
Click to expand...
YEs, the 970 Evo is known to produce quite a low of heat. It should run a bit cooler once migration is over and the spotlight indexing finished.
 
mbosse said:
YEs, the 970 Evo is known to produce quite a low of heat. It should run a bit cooler once migration is over and the spotlight indexing finished.
Click to expand...

Thanks mbosse. I've been reading old posts and looks like the Intel 770P and ADATA XPG SX8200 are better options. Think I'm getting the ADATA and returning this Samsung 970. The bottom of the machine is noticeably warmer now and it doesn't "feel" good to me.

Looks like I'll have to disable standby on the machine as well as I don't dare brave the EFI mod. This is my main axe and I can't afford hack it to that degree right now.

turbineseaplane I did a recovery install holding option+command+r so it would load latest version of mojave. Then migration assistant. Don't have the time nuke/pave this machine. Transfer of 450GB took 30 mins! amazing!
 
  • Like
Reactions: turbineseaplane
Audit13 said:
There was a bootrom update with 10.14.1, not with 10.14.2.

An update to the latest Mojave may help.

When I updated my early 2015 13" to 10.14.1, the bootrom was updated even though it was running an Intel 600p internally. It's the first time that my air accepted a bootrom update with a third party internal nvme drive.
Click to expand...
Oh I'm already on 10.14.2, I was just using 10.14 broadly to specify the whole update.
 
I unable to get my machine to hibernate correctly. I've set "hibernatemode" to 25.
when I sleep from the menu or type in "sudo pmset hibernatemode 25" to get it to hibernate immediately the display turns off, but it doesn't hibernate.

I reset SMC. Not sure what I'm missing.

Here are my settings (plugged into mains).

System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
womp 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 1
gpuswitch 2
networkoversleep 0
disksleep 10
standbydelayhigh 10800
sleep 1 (sleep prevented by screensharingd)
autopoweroffdelay 28800
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 10
highstandbythreshold 50
acwake 0
lidwake 1
mahogany-3:~ brandon$
 
Check post #2732 above. Hibernatemode 25 apparently is not guaranteed to work; on my MBP 15" late 2013 it does not work either.

Using the settings as given in mentioned post the sleep/wake crashes disappeared. My MBP also loses practically no battery while sleeping.
 
Last edited:
  • Like
Reactions: buzzworm and Audit13
Hi all! I've got MBP late 2013 and i want to upgrade ssd to Intel 660 or 760 with sintech adapter. I tried to read all discousion, so that's i understood:
1. 2015s MBP only one MacBook with no deepsleep issue.
2. Intel's ssd has lower temp than samsung, and maybe more stable.
3. There is one way to fix deep sleep issue with 2013-2014 MPB - flash bootroom with 2015's boot room. Is there any instruction?
4. Maybe non-NVMe ssd's works correctly but slower?
Thanks!
 
  • Like
Reactions: buzzworm
Just wanted to share my experiences: I swapped the original 128 GB SSD in my 2014 MBA with an Intel 760p 512 GB. I followed CMD+Q's guide. I bought the long black Sintech rev C adapter from their shop in China. It took about 2 weeks for the package to arrive in The Netherlands. It came pre-taped with some black rubbery tape on the connector. The SSD swap was done within 1 hour.

After the swap I used a Time Machine backup on an external HD to boot the MBA and restore the most recent backup. At first the intel SSD was not shown as a target during the restoration process. After formatting the SSD with the disk utility available from the setup menu it was found and I could restore the Time Machine backup. I have had no issues with freezes. I disabled hibernation to avoid the known wake up issues. Speed is great, about 3x-4x faster than the original Apple SSD. And I am happy with the extra space.

Thanks to Gilles_polysoft for all the great research work and CMD+Q for his great guide!

I am still trying to fix the hibernation issue with a Bootrom update, without wanting to spend $50 on a simple PCB + Hirose connector. I will add a post once I have done this successfully.
 
  • Like
Reactions: mbosse and Berlinsky
ok I just installed High Sierra 10.13.6 on my rMBP 2013, Apple SSD.
Now the BootROM is MBP112.0146.B00

Is my BootROM fully upgraded to use a Toshiba XG5 now or should I also install Mojave?
I read that Mojave uses the same EFI than last High Sierra. Well I hope it will work now...

Thanks, this thread rocks xD
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back