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
I have the 970 1Tb in my late 2013 15" model, no reason it won't in the 2015 ones. I believe the 2015's already have newer NVMe supporting roms, you should be fine for the most part.
so my A1502 (mbp 13) has a 4x nvme drive, but a lot of the speeds here shown for the 970 samsung are nowhere near where samsung is claiming performance-wise... are these not running @4x?
seems to be about on par with the 2x drives...
i've ordered the long black adapter, but i'm still on the fence about which drive to buy... i would like to retain the most battery life i can (coming from a lenovo to my mbp, it's one of the biggest downsides already), and if i can save some money by not affecting performance by getting a mydigitalssd SBX over a samsung 960 or 970evo drive, i may as well do that...
while i dont' doubt most people wouldn't even be able to tell the difference, for my use-case i'm copying 8-10GB files from the drive to the drive all day long, and would love the extra performance boost if i'd actually get it...
seems to be about on par with the 2x drives...
i've ordered the long black adapter, but i'm still on the fence about which drive to buy... i would like to retain the most battery life i can (coming from a lenovo to my mbp, it's one of the biggest downsides already), and if i can save some money by not affecting performance by getting a mydigitalssd SBX over a samsung 960 or 970evo drive, i may as well do that...
while i dont' doubt most people wouldn't even be able to tell the difference, for my use-case i'm copying 8-10GB files from the drive to the drive all day long, and would love the extra performance boost if i'd actually get it...
To get your mbp into the firmware update mode, shut it down, wait 20 seconds then push the power button down until you see the apple logo and progress bar. It will take a good 5 - 8 seconds for the loading bar and apple to show up. Then flash the firmware. You'll know you've got it right when you re-read the firmware from dosdude1's tool and the checksum differs from the originals you downloaded.
You need to have the magsafe plugged in and powered - it (for obvious reasons) won't enter the flash mode from battery power.
edit: I suck at typing on this laptop
You need to have the magsafe plugged in and powered - it (for obvious reasons) won't enter the flash mode from battery power.
edit: I suck at typing on this laptop
Last edited:
I'm also struggling for flash the firmware, however I'm failing like as guys above. So, I have some questions to ask you.
- Do you use original SSD to flash the firmware? (Prior to flashing, should I re-install the stock ACHI SSD?)
- Must I have any device like a SPI programmer to use dosdude1's ROM tool?
- Can I see any indication if my MBP successfully enters into the firmware update mode?
(Is there any difference in booting screen between normal mode and firmware programming mode?)
- and any special setting for flashing the rom?
Sorry to ask you too many question, but please help!
Thank you, I was giving up when I saw the booting progress bar. And that’s what I was checking post flash. The older check sum is 7 something newer is 5D I believe. Will give this a try and post results.
Long time reader, first time posting. First off, I'm using a rMBP early 2015, long black sintech adapter and the EVO 960 1TB.
The issue i'm experiencing is using dosdude's bootROM, seems that i might need to be updated to support the rMBP 13 Early 2015 as i'm getting a "Could not detect your system's EEPROM type. The operation could not proceed". I've already extracted the data from the MBP114_0182_B00.fd file.
Anyone else experiencing this?
The issue i'm experiencing is using dosdude's bootROM, seems that i might need to be updated to support the rMBP 13 Early 2015 as i'm getting a "Could not detect your system's EEPROM type. The operation could not proceed". I've already extracted the data from the MBP114_0182_B00.fd file.
Anyone else experiencing this?
Don't think you need it for a 2015 macbook - only 2013/2014 units need the firmware hack. The 2015 models aready have the NVMe DXE driver in the firmware so long as its been upgraded to high sierra at least once using the original Apple supplied ACHI SSD.
I have tried so far with no success. I’m gonna try to switch to old HDD and try again. Apparently we should hear beeps that MBP is in firmware update mode. Which I have never heard. Will try with old hdd and report back.
M.2 is a PHYCICAL interface. Look at this the same way the USB-C port is being used for Thunderbolt and displayport now. Multiple protocols, once connector. You can put m.2 on the end of a sata III chip, PCIe bus, etc... You can speak SATA over the PCIe bus... basically, you could write a program to send commands with data packets to the device and it will respond. NVMe is simply a protocol, a language, way of speaking to a device. Now, since the slot in the macbooks is a PCIe interface, you can use put ANY type of device in there you want. You could put raw voltage adusted signals from an ethernet cable and talk directly out of the m.2 slot to an ethernet network.
So, NVMe is a system level communication stack designed for efficient data tranfer. You can do it on 1, 2, 4, 8 or 16 lane interfaces. Yes, if you had a 16 lane drive you could plug into a regular PCIe slot and fly. Here is a linkon BASICS of NVMe
http://www.nvmexpress.org/wp-content/uploads/NVMe_Overview.pdf
In otherwords, yes, the 2013 with an adapter board and M.2 NVMe ssd will work, you just need to hack the firmware (to avoid hibernation panics) and choose a drive that isn't power hungry like the MyDigitalSSD.
Thank you folks for the quick reply. That's great that I don't need the firmware hack.
Any thoughts on how to deal with the constant battery drainage? Ever since the NVMe has been installed I've noticed that the back of the laptop gets extremely hot and battery depletion is much quicker than with stock SSD.
I've also been experiencing the random kernel panics while using the laptop. I have made the pmset adjustments suggested and still get the panics.
Any thoughts on how to deal with the constant battery drainage? Ever since the NVMe has been installed I've noticed that the back of the laptop gets extremely hot and battery depletion is much quicker than with stock SSD.
I've also been experiencing the random kernel panics while using the laptop. I have made the pmset adjustments suggested and still get the panics.
The PMSET commands aren't necessary on the rMBP 2015 - it already has all the requirements to handle the new SSD PROVIDED it was previously upgraded (or preferably fresh installed) to MacOS High Sierra.
The 960 EVO is one of the more power hungry drives, so you'll have to accept the fact that battery life will not be as good as with the stock apple drive.
When I have some time I'll do a runtime review of the apple drive and compare it with my Toshiba XG5 - From memory istat menus said that the Toshiba equipped machine was drawing ~10W at idle.
I have to repair a friends significant other's macbook pro same vintage as mine, so I'll do the tests when they show up with the sick computer - so I'll have the tools out again - living in a small apartment makes it difficult to have a proper workbench, so electronics on the coffee table is the way I roll (of course properly ESD grounded with an ESD mat and wrist strap!!)
The 960 EVO is one of the more power hungry drives, so you'll have to accept the fact that battery life will not be as good as with the stock apple drive.
When I have some time I'll do a runtime review of the apple drive and compare it with my Toshiba XG5 - From memory istat menus said that the Toshiba equipped machine was drawing ~10W at idle.
I have to repair a friends significant other's macbook pro same vintage as mine, so I'll do the tests when they show up with the sick computer - so I'll have the tools out again - living in a small apartment makes it difficult to have a proper workbench, so electronics on the coffee table is the way I roll (of course properly ESD grounded with an ESD mat and wrist strap!!)
Last edited:
I purchased this adapter http://eshop.sintech.cn/ngff-m2-pcie-ssd-card-as-2013-2014-2015-macbook-ssd-p-1139.html a while ago and am using it in a 2015 MBA. I think it is giving me a wake up issue (just happened). I didn't notice it at first since I also use an SD card in the slot as extra storage. But since my battery seems to be draining faster with the lid closed, I ejected it since I read it will keep the laptop from a deeper state of sleep. Should I get another adapter?
My checksums are different - but I could see how these change over time in the SPI also. Anyway, just tried getting into the "firmware programming mode" again after the latest from from vk2fro: Still no luck. I started ROMTool from Terminal and see that the flashrom inside the ROMTool reports "read-only" areas. I am assuming you see the same issue?
Code:
objc[419]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff883a8c90) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10761ccd8). One of the two will be used. Which one is undefined.
Mapping low megabyte at 0x0000000000000400, unaligned size 0xffc00.
Mapping low megabyte, 0xffc00 bytes at unaligned 0x0000000000000400.
sh: dmidecode: command not found
dmidecode execution unsuccessful - continuing without DMI info
Warning: SPI Configuration Lockdown activated.
FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: Warning: Management Engine region (0x00002000-0x0018ffff) is read-only.
FREG4: Warning: Platform Data region (0x00001000-0x00001fff) is read-only.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see http://flashrom.org/ME for details.
PR0: Warning: 0x00000000-0x00001fff is read-only.
PR1: Warning: 0x00190000-0x0060ffff is read-only.
PR2: Warning: 0x00632000-0x01ffffff is read-only.
Mapping low megabyte at 0x0000000000000400, unaligned size 0xffc00.
Mapping low megabyte, 0xffc00 bytes at unaligned 0x0000000000000400.
sh: dmidecode: command not found
dmidecode execution unsuccessful - continuing without DMI info
Warning: SPI Configuration Lockdown activated.
FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only.
FREG2: Warning: Management Engine region (0x00002000-0x0018ffff) is read-only.
FREG4: Warning: Platform Data region (0x00001000-0x00001fff) is read-only.
Not all flash regions are freely accessible by flashrom. This is most likely
due to an active ME. Please see http://flashrom.org/ME for details.
PR0: Warning: 0x00000000-0x00001fff is read-only.
PR1: Warning: 0x00190000-0x0060ffff is read-only.
PR2: Warning: 0x00632000-0x01ffffff is read-only.
Write/erase is not working yet on your programmer in its current configuration.
Aborting.Edit: Perhaps I am waiting for the wrong chime? https://support.apple.com/en-us/HT202768
Last edited:
I tried using my old original mbp ssd, but had no luck, Rom Tool kept getting "Can't read EEPRom" Error. Switched back to the new SSD will give a few more tries. Perhaps we need to find a way to force the mac to get into the Firmware recover mode using a command before a restart.
Regarding "bootrom mod" for MBP2013-2014,
I failed to flash the modified rom to my MBP 2014-mid, too.
I switched to my old stock SSD but it didn't work, neither.
The strange thing is "Romtool" still says flash completed successfully but I confirm real bootrom doesn't change anything when I checked it by UEFI Tool.
I failed to flash the modified rom to my MBP 2014-mid, too.
I switched to my old stock SSD but it didn't work, neither.
The strange thing is "Romtool" still says flash completed successfully but I confirm real bootrom doesn't change anything when I checked it by UEFI Tool.
Yes, I am thinking the same thing - either you can somehow bring these systems into the recovery/programming mode for firmware/EFI ROM (boot arguments?), or we’ll have to try and make the ROM modifications to the UEFI capsules (scap files) that carry the firmware for the 2013-2014 MacBooks. The MBP111_0145_B00.scap includes the same NVMe driver section that should be easy to replace (same GUID 51116...) via UEFITool. This process will have to be done from the stock SSD as the process can only be invoked from an internal drive:
Code:
sudo /usr/sbin/bless -mount / -firmware ~/Desktop/MBP111_0145_B00_with_NVMe.scap --recovery --verbose --setBoot --nextonlyI just had a conversation with dosdude1, he is going to check it there could compatibility issues with post 2012 MBPs, as that’s what he had when he wrote the tool. Let’s wait and see.
Has somebody upgraded to High Sierra v5? Is it safe to do so? Does the firmware update get installed when the computer contains (aftermarket) NVMe?
Seems this OS update brings a lot of change! https://eclecticlight.co/2018/06/01/whats-in-the-high-sierra-10-13-5-update/
Thanks in advance!
Seems this OS update brings a lot of change! https://eclecticlight.co/2018/06/01/whats-in-the-high-sierra-10-13-5-update/
Thanks in advance!
For what it's worth, I've been trying on my own 2012 MacBook pro (not for an NVMe mod obviously, but for a different firmware modification), and I'm having the same trouble as you guys. No indication that the laptop is entering EFI Programming Mode, and the flash doesn't seem to update.
Just loaded 10.13.5 on my 2015 MBP, loaded ok but bootrom not updated with NVMe drive. I put the old apple drive back in and updated that to 10.13.5 and bootrom updated to 121.176.B00 then put NVMe back in and all seems fine so far.
Just noticed that with 10.13.5 the terminal command 'createinstallmedia' seems to have disappeared.
Last edited:
Hello everyone
Can someone please give me advise, i done all steps from post #1345 of vk2fro except of flashing new rom and have few questions:
1. When i dumped firmware from my mac and open it in UEFItool it shows unknown file system messages
Is it bad? or i can just ignore this ?
2. So i have downloaded from appstore "high sierra install.app" (10.13.5 version) and grab from it by "pacifist.app" NVMe driver from MBP114_0183_B00.fd. When i replace NVMe part in my bios i see different checksum - my is C0h instead of D5h. Data size is 25820
So is it bad or it's because of the updated firmwares in latest "high sierra install.app" ?
3. And finally is it necessary to update firmware of my MBR mid 2014 (with apple ssd) if i'm already updated to latest high sierra update (10.13.5) to get flawless workin of intel's 760p 1tb driver? I'm already bought sintech latest version adapter (black) and
going to buy new ssd in next week. Want to clarify all things before buy and flashing firmware
p.s. sorry for my english, hope someone will understand what i'm trying to say
Can someone please give me advise, i done all steps from post #1345 of vk2fro except of flashing new rom and have few questions:
1. When i dumped firmware from my mac and open it in UEFItool it shows unknown file system messages
Is it bad? or i can just ignore this ?
2. So i have downloaded from appstore "high sierra install.app" (10.13.5 version) and grab from it by "pacifist.app" NVMe driver from MBP114_0183_B00.fd. When i replace NVMe part in my bios i see different checksum - my is C0h instead of D5h. Data size is 25820
So is it bad or it's because of the updated firmwares in latest "high sierra install.app" ?
3. And finally is it necessary to update firmware of my MBR mid 2014 (with apple ssd) if i'm already updated to latest high sierra update (10.13.5) to get flawless workin of intel's 760p 1tb driver? I'm already bought sintech latest version adapter (black) and
going to buy new ssd in next week. Want to clarify all things before buy and flashing firmware
p.s. sorry for my english, hope someone will understand what i'm trying to say
Last edited: