Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe

[Audit13]

No issue until now, all is working perfectly...

Does this mean you have deep sleep working on a pre-2015 MBP? That would be great news.
[doublepost=1543100773][/doublepost]

I wouldn't do that, too risky because the mainboard with its serial is linked to the previous owners iCloud.
And I assume the guys who sell these spare parts have no clue who the previous owner was to unlock it.
These shops usually sell this stuff to repair shops so they can desolder the individual components.

Wiping the drive will remove iCloud from the Macbook and the device will be removed from user's list of devices on iCloud.com.

I had a 2011 MBP and 2013 MBA under my iCloud account. I gave the 2011 to my sister-in-law and the Air to my niece. I never signed out of iCloud on either Macbook before wiping the drives. After wiping, the devices were removed from my iCloud list.

 

[rexoserox]

Does this mean you have deep sleep working on a pre-2015 MBP? That would be great news.
[doublepost=1543100773][/doublepost]


Wiping the drive will remove iCloud from the Macbook and the device will be removed from user's list of devices on iCloud.com.

I had a 2011 MBP and 2013 MBA under my iCloud account. I gave the 2011 to my sister-in-law and the Air to my niece. I never signed out of iCloud on either Macbook before wiping the drives. After wiping, the devices were removed from my iCloud list.

A lot of people having trouble with used mainboards. Last time I read about it Apple implemented some sort of activation lock and you need your Apple ID. https://support.apple.com/en-us/HT204756
Recover the passcode to unlock your Mac
1. Click All Devices, then select the Mac that’s locked
2. Click Unlock, then follow the onscreen instructions to verify your identity with your Apple ID password.
3. Once you have your passcode, enter it on your Mac.

Not sure about the Mac. But they do implement locks that are dependent on hardware for example on the iPhone.


here some folks having trouble with used mainboards
https://www.ifixit.com/Answers/View/344826/Replaced+Logic+Board+w-+Used,+Can't+Log+In
or here
https://www.ifixit.com/Answers/View/383403/Mother+Board+locked+How+to+unlock

 

[adbono]

Does this mean you have deep sleep working on a pre-2015 MBP? That would be great news.
[doublepost=1543100773][/doublepost]

For me yes, i've a hibernatemode = 3 . i close the lid, and i reopen the next day its starts instantly, for the battery i lose about 5-6%.

Option on Energy saver :
"put hard disk to sleep when possible" checked


I've also tested the hibernation mode manually

 

[Jilly Bowman]

Just updated three MBP 13" to Mojave 14.1, Some people on here have reported that the bootrom now updates, even with NVMe drives installed. none of these updated. they all have Samsung NVMe drives. Any comments? the macs were two x 2015 and a 2013.

 

[Babia23]

Hi,

Newbie here. I'm planning to upgrade my Macbook Pro 15" mid-2014 and I've spent a few hours reading this thread. Thank you all for your contributions, I believe I know now how to proceed and what are the risks.

I have a question, though, which I haven't seen dealt with until now.

Since I have bought an external case to put the old SSD in, I was wondering if the simplest procedure woudn't be as follows:
1) Putting my new Samsung EVO 1TB in the external case and connect it to the Macbook Pro.
2) Using SuperDuper to make a bootable clone of the internal Macbook SSD into the Samsung NVMe.
3) Testing if the clone works by rebooting the computer using the external disk still in its enclosure.
4) If it works, then swap the disks.

Do you see any reason it shouldn't work?

 

[Jilly Bowman]

Hi,

Newbie here. I'm planning to upgrade my Macbook Pro 15" mid-2014 and I've spent a few hours reading this thread. Thank you all for your contributions, I believe I know now how to proceed and what are the risks.

I have a question, though, which I haven't seen dealt with until now.

Since I have bought an external case to put the old SSD in, I was wondering if the simplest procedure woudn't be as follows:
1) Putting my new Samsung EVO 1TB in the external case and connect it to the Macbook Pro.
2) Using SuperDuper to make a bootable clone of the internal Macbook SSD into the Samsung NVMe.
3) Testing if the clone works by rebooting the computer using the external disk still in its enclosure.
4) If it works, then swap the disks.

Do you see any reason it shouldn't work?

If the new drive is NVMe then it wont work in the enclosure, it needs a PCI bus to work, not Esata.

 

[Babia23]

If the new drive is NVMe then it wont work in the enclosure, it needs a PCI bus to work, not Esata.

Thanks. It seems I had missed something quite essential.

 

[geoluv]

Just updated three MBP 13" to Mojave 14.1, Some people on here have reported that the bootrom now updates, even with NVMe drives installed. none of these updated. they all have Samsung NVMe drives. Any comments? the macs were two x 2015 and a 2013.

You have to update to 10.14.1 to get the new bootrom, 10.14 didn’t update my bootrom either

 

[Jilly Bowman]

You have to update to 10.14.1 to get the new bootrom, 10.14 didn’t update my bootrom either

It was an update to 10.14.1, tried both update and clean install. no bootrom update.
did get update with an apple ssd, but not with samsung NVMe ssd's.

 

[avdo]

My pleasure. Writing speeds are what to be expected and are the same under Win10 / OS X writing around 2500MB/sec reading about 3000MB/sec in Black Magic Speed Disk Test and a bit higher in AmorphousDiskMark.

Hi Berlinsky,

May I ask what are you currently running, HS or Mojave?
[doublepost=1543154477][/doublepost]Hello all,

Just a couple of questions specifically about the 970 EVO

I'm assuming that updating the firmware of a 970 EVO is possible on a MacBook Pro 11,5 within Win10 on a Bootcamp partition ?

Also, does anybody know if the 970 EVO runs cooler within Win10 on Mac hardware as Nvme 1.3 spec supports host controlled power switching?

I'm assuming that the whole issue is that the 970 EVO is basically hotter and more power hungry by design therefore irrespective of correct power mode switching ( which I think is controlled by IONVMeFamily.kext ) it's going to use more power, simple as ?


Thanks

Avdo

 

[mad cow disease]

A lot of people having trouble with used mainboards. Last time I read about it Apple implemented some sort of activation lock and you need your Apple ID. https://support.apple.com/en-us/HT204756
Recover the passcode to unlock your Mac
1. Click All Devices, then select the Mac that’s locked
2. Click Unlock, then follow the onscreen instructions to verify your identity with your Apple ID password.
3. Once you have your passcode, enter it on your Mac.

Not sure about the Mac. But they do implement locks that are dependent on hardware for example on the iPhone.


here some folks having trouble with used mainboards
https://www.ifixit.com/Answers/View/344826/Replaced+Logic+Board+w-+Used,+Can't+Log+In
or here
https://www.ifixit.com/Answers/View/383403/Mother+Board+locked+How+to+unlock

That is a useless board due to not knowing the firmware password (local, hardware), not the iCloud password (the OS being locked). The Apple support document you've linked has nothing to do with the iFixit links that you posted below.

Please don't post inaccurate information, it confuses the people reading this thread.

 

[jackqueenking]

For me yes, i've a hibernatemode = 3 . i close the lid, and i reopen the next day its starts instantly, for the battery i lose about 5-6%.

Option on Energy saver :
"put hard disk to sleep when possible" checked


I've also tested the hibernation mode manually

This is not the correct test. Hibernate mode 3 does not power off your mac completely, it stores the contents of the session in RAM and makes a carbon copy on the drive just in case your battery dies thus when you open your mac after letting it sleep the whole night, if the battery has not died your session will be restored from ram hence why you lose 5-6% and you won't observe the hibernate problem for pre 2015 models. This is mode is effectively a safer mode than hibernate mode 0 since you don't lose your data if your mac dies while its lid is closed.

The real test is to set it to hibernate mode 25 (Copies contents to drive and powers off mac completely) with standby = 0 and then from the terminal type without quotations "pmset sleepnow". Then wait a minute or so, power on your mac, if it works you should see a loading bar at the bottom of the screen, if it doesn't work your mac will restart twice which means there's still no support for NVME wake up in pre 2015 models.

 

[Berlinsky]

Hi Berlinsky,

May I ask what are you currently running, HS or Mojave?
[doublepost=1543154477][/doublepost]Hello all,

Just a couple of questions specifically about the 970 EVO

I'm assuming that updating the firmware of a 970 EVO is possible on a MacBook Pro 11,5 within Win10 on a Bootcamp partition ?

Also, does anybody know if the 970 EVO runs cooler within Win10 on Mac hardware as Nvme 1.3 spec supports host controlled power switching?

I'm assuming that the whole issue is that the 970 EVO is basically hotter and more power hungry by design therefore irrespective of correct power mode switching ( which I think is controlled by IONVMeFamily.kext ) it's going to use more power, simple as ?


Thanks

Avdo

Hi Avdo,
I did a clean install of Mojave 10.4.1 installer from an external USB SSD. And yes Samsung Magician can be used under bootcamp, but make sure that you're not trying to install Win10 1809 won't work, only the April Update Win10 works right now.
I don't know if the 970 EVO runs cooler under Win10, hardly using it.

best.

 

[adbono]

This is not the correct test. Hibernate mode 3 does not power off your mac completely, it stores the contents of the session in RAM and makes a carbon copy on the drive just in case your battery dies thus when you open your mac after letting it sleep the whole night, if the battery has not died your session will be restored from ram hence why you lose 5-6% and you won't observe the hibernate problem for pre 2015 models. This is mode is effectively a safer mode than hibernate mode 0 since you don't lose your data if your mac dies while its lid is closed.

The real test is to set it to hibernate mode 25 (Copies contents to drive and powers off mac completely) with standby = 0 and then from the terminal type without quotations "pmset sleepnow". Then wait a minute or so, power on your mac, if it works you should see a loading bar at the bottom of the screen, if it doesn't work your mac will restart twice which means there's still no support for NVME wake up in pre 2015 models.

Hi,
I did the test, but i got a freeze at login time. i have to restart 'by power button' to get the apps already opened.
this is my config :

System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
disksleep 10
standbydelayhigh 86400
sleep 5 (sleep prevented by Google Chrome)
autopoweroffdelay 28800
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 5
highstandbythreshold 50
acwake 0
lidwake 1

 

[Audit13]

Hi,
I did the test, but i got a freeze at login time. i have to restart 'by power button' to get the apps already opened.

Looks like hibernation is not working properly on the pre-2015 Macbooks.

Thanks for checking.

 

[adbono]

but i think this freeze is not related to the nvme, i've found that others have the same problem, even with stock ssd.
i'll do a NVRAM/SMC reset, and FileVault disabling. maybe that's change something

 

[Audit13]

but i think this freeze is not related to the nvme, i've found that others have the same problem, even with stock ssd.
i'll do a NVRAM/SMC reset, and FileVault disabling. maybe that's change something

I don't know because I have not experienced the same freezing with my late 2013 13" MBP.

 

[avdo]

Hi Avdo,
I did a clean install of Mojave 10.4.1 installer from an external USB SSD. And yes Samsung Magician can be used under bootcamp, but make sure that you're not trying to install Win10 1809 won't work, only the April Update Win10 works right now.
I don't know if the 970 EVO runs cooler under Win10, hardly using it.

best.

Thanks for the info Berlinsky, much appreciated.

 

[jackqueenking]

Hi,
I did the test, but i got a freeze at login time. i have to restart 'by power button' to get the apps already opened.

Could be a fluke, there have been several reports on this thread that indicate hibernate working once or twice when the initial switch is done and then it stops working. I have never experienced the freezing problem you just got with my 2014 and original apple SSD. Try clearing NVRAM and resetting the SMC and run the same test again. Also leave your sound on so you can hear how many times the startup sound plays.

 

[phorust]

Just wanted to report a success after searching through this thread. I've got my A1398 EMC 2745 "Late 2013" MBP 15" working using the short Sintech adapter and an ADATA / XPG SX8200 960GB drive. Also tried a 970 EVO and the JSER adapter, both which worked. Initially I thought they were not working because I could not see the drive in Disk Utility or diskutil under 10.14's internet recovery, but after making myself a 10.13 bootable USB to recover with, I can see both the SX8200 and the 970 EVO, with either adapter. I'm keeping the Sintech because the PCB is black and matches the logic board, and the included heatsink of the XPG and less rumors of power issues give it the edge over the 970.

I'm pushing about 1280 MB/s write and 1480 MB/s read according to Black Magic.

I had to run sudo pmset -a hibernatemode 0 in to get the MBP to wake from deep sleep. I've had pretty low battery drain (<3%) overnight with my limited testing.

I had Mojave installed, experienced the spotlight reindexing issue, and I think the high disk use pushed my OEM 1TB drive over the edge and it died. Now to see if it can be resurrected... that's a lot of NAND to go to waste.

 

[6e23]

Just wanted to report a success after searching through this thread. I've got my A1398 EMC 2745 "Late 2013" MBP 15" working using the short JSER adapter and an ADATA / XPG SX8200 960GB drive. Also tried a 970 EVO and the Sintech adapter, both which worked. Initially I thought they were not working because I could not see the drive in Disk Utility or diskutil under 10.14's internet recovery, but after making myself a 10.13 bootable USB to recover with, I can see both the SX8200 and the 970 EVO, with either adapter...

Interesting, I had the same problem--booting from internet recovery did not detect a 512GB Intel 760p via Sintech A in MBA 2015 11", but booting from USB Mojave installer worked perfectly.

 

[rexoserox]

That is a useless board due to not knowing the firmware password (local, hardware), not the iCloud password (the OS being locked). The Apple support document you've linked has nothing to do with the iFixit links that you posted below.

Please don't post inaccurate information, it confuses the people reading this thread.

Well, you are partially right.
The link I posted there is a section about locking your lost or stolen mac.
As far as I understand that is special firmware lock connected to your iCloud.

"The Lost Mode feature of Find My Mac will remotely lock the Mac with a firmware password for one-time use. The user’s Mac receives the lock instruction from iCloud, restarts, and asks for the system lock PIN code that they set up. After entering the passcode the Mac starts up from the designated startup disk and disables the passcode."

Nevertheless any firmware lock is pain in the a** to reset. What I want to say is that you might be unlucky and get a firmware locked board if you try to replace your mainboard.

 

[geoluv]

"I guess the flashing itself should not be that much of a problem (see https://gist.github.com/elvisizer/2dfa119e959ae6f35389d4d56054f067 for further description) The main point AFAIK is to inject a newer NVME driver into the (pre 2015) SCAP EFIPayload file that needs to be flashed.

If I understand correctly, @y-h-wong raw-edited the SCAP file (with hex editor e.g.) and copied the NVME driver from a newer Bootrom into the update for your pre 2015 MBA/MBP. The SCAP files can be extracted from the latest Mojave InstallESD (Packages/FirmwareUpdate.pkg/Scripts/Tools/EFIPayloads).

Edit: Ok I just learnt that you can replace the NVME part using UEFI-Tool. This means, a new SCAP file can be built like that. I'm just not yet confident enough on this to flash it using the mentioned commands, as I don't have any flashing hardware available right now and don't want to kill my system in case something goes wrong."

looks like all you need is uefi tool

 

[geoluv]

Buying a used MacBook main board on eBay is no more or less risky than buying a used or refurbished iPhone on eBay. I would not buy a used board from someone with feedback that I found to be questionable or inadequate. I would feel very comfortable buying one from a well known seller of used/refurbished Apple products with thousands in feedback that maybe offers a warranty period longer than what eBay covers.

 

[BBsan]

"I guess the flashing itself should not be that much of a problem (see https://gist.github.com/elvisizer/2dfa119e959ae6f35389d4d56054f067 for further description) The main point AFAIK is to inject a newer NVME driver into the (pre 2015) SCAP EFIPayload file that needs to be flashed.

If I understand correctly, @y-h-wong raw-edited the SCAP file (with hex editor e.g.) and copied the NVME driver from a newer Bootrom into the update for your pre 2015 MBA/MBP. The SCAP files can be extracted from the latest Mojave InstallESD (Packages/FirmwareUpdate.pkg/Scripts/Tools/EFIPayloads).

Edit: Ok I just learnt that you can replace the NVME part using UEFI-Tool. This means, a new SCAP file can be built like that. I'm just not yet confident enough on this to flash it using the mentioned commands, as I don't have any flashing hardware available right now and don't want to kill my system in case something goes wrong."

looks like all you need is uefi tool

this was my answer on stack exchange

But to be clear: this is just theoretical - I did not try this!

Is there anyone with a J6100 Adapter who is willing to try this SW solution?
If I do it and it fails, my Mainboard would be fried!

EDIT:
After some further digging I just found out the UEFITool can only create cap files - but they are not signed. I guess that's the reason why nobody else tried this approach yet...