Sidebar 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.
I´m having problems with Syntech Adapter and 2TB Samsung 970 EVO.

Macbook Pro Mid 2015 .

I was having problem with Native Instruments Traktor, crashing when analysing new AIFF songs.
After some investigation I found out that the problem is file system related.

Any tips?
 
I have successfully flashed modified rom. It didn't as should on first time. I have MBA 13" mid 2013. Rom modified by instructions in this thread. It didn't well because I didn't maybe read correctly this forum. Ordered programmer
CH341 as mentioned and rom clip. But after I had torn down my MBA to locate EFI chip on motherboard, I found out, it isn't possible in this case. So first time no modification done. So then I was looking for cheaper than 50€ J6100 adapter, only thing I found was Rebelsimcard easy flasher. After making my own cable for this adapter, connected and tried fo flash rom with Flashtool. At first flashtool didn't find any chip to flash, but when battery was not connected ant then connected charger, flasthool found chip and flashing did begin. Of course at first I made backup and checked it, then flashed modified rom. All went well.
I like that apple logo appeared as soon as I pressed power button, no delay as previously. And boot time seemed faster. But the best thing is sleep, or hibernatemode 25. It now really works and when I don't use my computer, I can just close lid, it really hibernates. After opening no panics and showing loading screen maybe a couple seconds.

I am really happy. So now I just want to swap Samsung 960 evo to something less energy hungry, maybe Intel 760p
 
  • Like
Reactions: Alpenjodel, Audit13 and mbosse
geoluv said:
"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
Click to expand...

Procedure followed by Pepijn to run the high sierra firmware installer:
1. get the FirmwareUpdate.pkg file from the OS installer app's installESD.dmg
2. extract the contents using pkgutil --expand /path/to/FirmwareUpdate.pkg <path somewhere else>/FirmwareUpdate
3. in terminal, cd to the Scripts directory inside the expanded FirmwareUpdate pkg directory.
4. with Scripts as your working directory, run these 2 commands, then reboot:
sudo /usr/libexec/FirmwareUpdateLauncher -p "$PWD/Tools"
sudo /usr/libexec/efiupdater -p "$PWD/Tools/EFIPayloads"
5. at the reboot, firmware will be updated if there are any updates to be applied.
Click to expand...

I tried using the process in the link above to get my late-2013 MacBook Pro (MBP111.88Z.0146.B00.)
to the latest firmware in 10.14.1 without an original Apple SSD. I'm using the HP 920EX. I was hoping to move to the
149.0.0.0.0 firmware supposedly in 10.14.1's update.

Running FirmwareUpdateLauncher found that my SMC was already up to date, so no action taken.

When running efiupdater as prescribed I got this:

efiupdater version 16.220.2~8



ROM Payload path: <CFURL 0x7fa345600050 [0x7fff9125b8f0]>{string = file:////Users/gaijin/Downloads/fw/macos1/FirmwareUpdate.pkg/Scripts/Tools/EFIPayloads/, encoding = 134217984, base = (null)}

Current EFI Version string: MBP111.88Z.0146.B00.1804111138

Checking ROM file for version: /Users/me/Downloads/fw/macos1/FirmwareUpdate.pkg/Scripts/Tools/EFIPayloads/MBP111.scap

EFI currentVersion: [MBP111 0146.00 1804111138 Release]

EFI updateVersion: [149.0.0.0.0~0 B&I]

Curent < Update

---------- Running bless ----------

EFI found at IODeviceTree:/efi

Will need to copy 8523776 bytes to EFI system partition

No auxiliary booter partition required

System partition found

Preferred system partition found: disk0s1

Returning booter information dictionary:

<CFBasicHash 0x7f83e2d0f120 [0x7fff9125b8f0]>{type = mutable dict, count = 4,

entries =>

0 : <CFString 0x108d7f3c0 [0x7fff9125b8f0]>{contents = "Data Partitions"} = (

disk1s1

)

1 : <CFString 0x108d7e9a0 [0x7fff9125b8f0]>{contents = "Preboot Volumes"} = (

disk1s2

)

2 : <CFString 0x108d7f3e0 [0x7fff9125b8f0]>{contents = "Auxiliary Partitions"} = (

)

3 : <CFString 0x108d7ebe0 [0x7fff9125b8f0]>{contents = "System Partitions"} = (

disk0s1

)

}



Mounting at /Volumes/bless.oilW

Executing "/sbin/mount"

Returned 0

Creating /Volumes/bless.oilW/EFI/APPLE/FIRMWARE if needed

Deleting previous contents of /Volumes/bless.oilW/EFI/APPLE/FIRMWARE

Deleting /Volumes/bless.oilW/EFI/APPLE/FIRMWARE/MBP111.scap (8520304 bytes)

Opened dest at /Volumes/bless.oilW/EFI/APPLE/FIRMWARE/MBP111.scap for writing

preallocation not supported on this filesystem for /Volumes/bless.oilW/EFI/APPLE/FIRMWARE/MBP111.scap



/Volumes/bless.oilW/EFI/APPLE/FIRMWARE/MBP111.scap created successfully

Relative path of /Volumes/bless.oilW/EFI/APPLE/FIRMWARE/MBP111.scap is \EFI\APPLE\FIRMWARE\MBP111.scap

IOMedia disk0s1 has UUID 8DAAE463-901C-4D17-BDC0-1352D3332DB6

Executing "/sbin/umount"

Returned 0

Write to RTC: 0

Setting EFI NVRAM:

<CFBasicHash 0x7f83e2e00000 [0x7fff9125b8f0]>{type = mutable dict, count = 1,

entries =>

2 : <CFString 0x108d7ec20 [0x7fff9125b8f0]>{contents = "efi-apple-recovery"} = <CFString 0x7f83e2c02c80 [0x7fff9125b8f0]>{contents = "<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>8DAAE463-901C-4D17-BDC0-1352D3332DB6</string></dict></dict><key>BLLastBSDName</key><string>disk0s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\APPLE\FIRMWARE\MBP111.scap</string></dict></array>"}

}



---------- bless complete ----------

bless returned 0

Background color default set successfully

efiupdater exit status = 0
Click to expand...

I then rebooted, but nothing. System seemed shutdown - black screen. I waited a few mins and then hit the power button. Once, nothing. Twice, got power. Everything booted up fine, but no firmware update.

Has anyone else tried this and had success on getting the latest 149.0.0.0 version? Does 149.0.0.0 fix the deep sleep/hibernate issue on pre-2015 models?
 
Last edited:
Leo Bruno said:
I´m having problems with Syntech Adapter and 2TB Samsung 970 EVO.

Macbook Pro Mid 2015 .

I was having problem with Native Instruments Traktor, crashing when analysing new AIFF songs.
After some investigation I found out that the problem is file system related.

Any tips?
Click to expand...
How did you find out it's related to the file system? Which os are you using?
 
Does the Kernel Panic only occur in Macs 2013-2014 ?
I am thinking about buying a 2015 Model.
But I am not sure if you still get kernel panics. (hibernation and sleep on 2015 work as we know)
 
rexoserox said:
Does the Kernel Panic only occur in Macs 2013-2014 ?
I am thinking about buying a 2015 Model.
But I am not sure if you still get kernel panics. (hibernation and sleep on 2015 work as we know)
Click to expand...
yes as per post 2565 of this thread
 
Audit13 said:
How did you find out it's related to the file system? Which os are you using?
Click to expand...

After traktor crashes, a system report is raised, containing this ingormation.

I’m using mac os x 10.4.1 mojave and windows 10 on a 3 partitions on the same disc environment.

I’m getting problems on windows as well.

I have read someone realting the same problem somewhere (file system failures using this kind of adapter) before realizing that I had problems too.

Windows 10 event viewer shows a ton of disk malfunction error alerts.

I recomend that anyone using thease adapters, to install W10 and run it a few times, to have some data to collect with event viwer.
 
  • Like
Reactions: Audit13
Last edited:
  • Like
Reactions: rexoserox and mbosse
Berlinsky said:
Hi,correct Im on a non dGPU Macbook Pro 11,4. The ones with dGPU are 11,5.

Actually I don't think you need to switch to a Macbook Pro without dedicated GPU for heat reasons regarding the SSD.
One major design flaw in most newer and thinner Macbook Pros is heat dissipation from CPU/Chipset areas. So if you do CPU intensive stuff make sure all ventilation is dust free and working properly. Also, letting air go under it may help.

I ordered this one here: http://eshop.sintech.cn/ngff-m2-pcie-ssd-card-as-2013-2014-2015-macbook-ssd-p-1143.html

directly from China since I needed some tools... was the easiest upgrade I ever did.
Click to expand...


Thank You!!!
 
  • Like
Reactions: Berlinsky
I just experienced another kernel panic..
in the report we can see:

Code: 
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f849374c6): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x157 VID/DID=0xa804144d
. FW Revision=2B6QCXP7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.220.5/IONVMeController.cpp:5327

If it was open source we could fix it..

So it's their NVME driver who fails... I think we need to send the reports every time, AND write anything in the comment that's about the third-party ssd. So they make correctly compatible third-party ssd's
 
geoluv said:
I was answering his first sentence: only the '13-'14 MacBook boards experience kernel panic errors during wake from hibernation from lack of driver support.
Click to expand...

It’s not only the 13-14 who are experiencing kp, my 2015 is also getting these panics.
 
Zkryvix said:
It’s not only the 13-14 who are experiencing kp, my 2015 is also getting these panics.
Click to expand...
which ssd are u using? i installed intel 760p 1t and sintech short adapter on 13macbook pro 2015 and have 0 problems. The only cons is the battery drains a little bit faster.
 
BBsan said:
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...
Click to expand...

I'm willing to try this on my spare '13 11" i5 air board once my 660p arrives today. I don't have a programmer, I will risk bricking it for the culture:) If I brick it I will order the programmer.

I also have a '15 i7 8 gig board on the way that I am going to attempt to install in my '13 chassis to see if that is a viable work around for the nvme driver issue. I'm almost positive it will work. I've seen some parts websites even list the boards from '13-'15 as cross compatible. Just remember if you install a '15 board in a '13-'14 chassis you should put a NVME drive in it, you can re-use the ahci drive but you'll have issues when waking from hibernate. Just like how the ''13-'14 boards don't get the complete nvme driver the '15 boards don't get the complete ahci driver as per Apple's efforts to limit forward and backward compatibility. (There is almost no reason to re-use the AHCI Apple drive because 512gb third party pcie nvme cards cost as little as $60, about the same as what you could sell your stock Apple 128-256gb x2 ahci ssd for).
 
  • Like
Reactions: mbosse and uehithneu
Hi everybody. Very new on here. I have read through some of this thread but not all. I have a Mackbook Pro 15 mid 2015 which i have just upgraded from Sierra to Mojave (yep, skipped High Sierra). I want to replace the existing Apple 256Gb SSD to a larger capacity. From this thread the combination I'm looking at is an 480Gb XPG Adata SX8200 + either a Sintech NGFF M.2 PCIe 2280 (Black) or the JSER 12+16 pin all of which are relatively cheap and seem to give the performanceBattery life ratio that I'm looking for. Everything suggests it should work fine. I've read that Mojave doesn't update the firmware, is that likely to cause me any problems?

Also I have been made aware of the 512Gb XPG Adata SX8200 Pro. Does any one have any experience of this? How well does it perform in terms of battery life?

Sorry to skip the niceties and dive right in but trying to make a decission and you gus seem to jave a wealth of knowledge. :)
 
Jilly Bowman said:
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.
Click to expand...

Same thing for me: no bootrom update until I re-installed the original Apple SSD and re-run the 14.1 updater. Only then I got the updated bootrom.
 
M1diman said:
Hi everybody. Very new on here. I have read through some of this thread but not all. I have a Mackbook Pro 15 mid 2015 which i have just upgraded from Sierra to Mojave (yep, skipped High Sierra). I want to replace the existing Apple 256Gb SSD to a larger capacity. From this thread the combination I'm looking at is an 480Gb XPG Adata SX8200 + either a Sintech NGFF M.2 PCIe 2280 (Black) or the JSER 12+16 pin all of which are relatively cheap and seem to give the performanceBattery life ratio that I'm looking for. Everything suggests it should work fine. I've read that Mojave doesn't update the firmware, is that likely to cause me any problems?

Also I have been made aware of the 512Gb XPG Adata SX8200 Pro. Does any one have any experience of this? How well does it perform in terms of battery life?

Sorry to skip the niceties and dive right in but trying to make a decission and you gus seem to jave a wealth of knowledge. :)
Click to expand...

Hi, look at this post for power usage of different SSDs: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-100#post-26819852

Its a great sum up of different models.
 
Berlinsky said:
Hi, look at this post for power usage of different SSDs: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-100#post-26819852

Its a great sum up of different models.
Click to expand...

Thanks for that. Some interesting stats. Certainly the Adata SX8200 stacks up well. Unfortunately the Pro version wasn't listed in it so none the wiser. I can get the 1Tb SX8200 Pro for about £180 so its tempting but dont want to buy it if it runs hot and is heavy on the battery. Im told it uses a different controller from the standard SX8200 so could make a difference. I can get the 960Gb SX8200 for about £210. If I'm unable to to find anything definitive on it, may play safe and stick to the 960Gb version. On the other hand I could dig deeper and go for the 1Tb Samsung 970 Pro. Comes in at £360 but battery life on it is meant to be as good if not better the the Apple SSD's. Decisions, Decisions :)
 
I'm using a late 2013 Macbook Pro. I just got a Samsung 970 evo and can't seem to get the mac to recognize the NVMe ssd. I'm assuming it's because the MBP hasn't been updated past Sierra, therefore it doesn't recognize NVMe. I was able to see it when booting to linux using the same MBP. Is there a way to manually update the bootrom (firmware)??

Can anyone point me in the right direction? THanks!



EDIT:

I was able to fix this issue.
In short... Kinda..

-Borrow a friends MBP with original Apple ssd that fits your MBP.
----(Make sure to backup the borrowed ssd, or clone it first.. I used SuperDuper to clone)
-Wipe the borrowed ssd using their mac. Do not use APFS as format.
----(yours won't read it if theirs is updated to High Sierra or newer, or formatted using APFS)
-Put the borrowed ssd into your MBP and install Sierra.
-Then download High Sierra or newer and install it. I went directly to Mojave.
----(this will update your bootrom with latest firmware version)
-Remove borrowed ssd and put your new NVMe m.2 ssd with adapter into your MBP.
-Get desired MacOS version onto a bootable flash drive.
-Use flash drive to install desired MacOS version onto Your NVMe ssd.
------Now your done------
Be sure to put the borrowed ssd back where it came from and set everything back up the way it was for your awesome helpful friend.
 
Last edited:
Reo87 said:
I'm using a late 2013 Macbook Pro. I just got a Samsung 970 evo and can't seem to get the mac to recognize the NVMe ssd. I'm assuming it's because the MBP hasn't been updated past Sierra, therefore it doesn't recognize NVMe. I was able to see it when booting to linux using the same MBP. Is there a way to manually update the bootrom (firmware)??

Can anyone point me in the right direction? THanks!
Click to expand...

This may help: https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-65#post-26224320
 
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