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
Thanks! Not worried about every last bit of speed. Just figure I might as well do 2TB vs. 1TB for an extra couple of hundred bucks, and stop worrying about what data I need to keep in Mac and my various Parallels VM sessions to keep free disk space available.
Is this the part? https://www.amazon.com/HP-EX950-Internal-5MS24AA-ABC/dp/B07MZFJ8FH
I assume w/ Simtec green or short black, and I'm set?
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Yeah. Newegg and their eBay store have it for $359 right now - best I’ve seen was them at $349 a while back.
I expect over time it will drop a lot more just as the EX920 did...but who knows when
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
The bootrom gets updated even with a 3rd party SSD installed, however the EFI driver doesn’t, it only gets a new timestamp (from 14.2.2019) but the revision number remains the same. And, I think, this EFI is the only thing that matters for a NVME drive to function properly. My iMac still has normal sleep issues after 10.14.4’s bootrom update, my guess is that MBPs also retain their hibernation problems.
The terminal command for the EFI version check:
/usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check
Here is the terminal output for my 2015 13" Air updated to 10.14.4 with an Intel 600p nvme drive:
EFI Version: MBA71.88Z.F000.B00.1902151233
I replaced the Intel 600p name drive with an original Apple 256 GB SSD and upgraded from 10.14.3 to 10.14.4. Here is the terminal output:
EFI Version: MBA71.88Z.F000.B00.1902151233
Both EFI versions are the same. Should it have changed when I upgraded from 10.14.3 to 10.14.4 using the original Apple SSD?
I have not had hibernation problems on a 2017 or 2015 13" Air.
Last edited:
If you haven’t had issues even before the update, perhaps it doesn’t matter much. We are trying to update Macs with problems, so that they possibly get solved. iMacs 2015 got bootrom updates even with a 3rd party blade, however EFI version remained (sleep problems also persist). Part of the MacBook reports above say that even their bootrom did not change :/
It does matter.
As much we're trying to help people that got macs with problems after NVMe SSD upgrades, it is extremely important to gather as much info and keep first (wiki) post updated for any future buyers and hassle free upgrade options.
P.S. That's the reason i'm begging everyone to have updated signature or try to list theirs Mac(book) in the post in which they're sharing some new info.
I'm not sure why my bootrom was updated on my 2015 and 2017 Air with a nvme drive but others did not have a bootrom update. I'm not sure of it has anything to do with a particular MacBook model, nvme drive, previous bootrom, or all three.
I posted a screenshot to show that the EFI version in the Air did not change by installing 10.14.4 with an original Apple SSD.
[doublepost=1553633175]
I'm using the short black adapter in 2017 Air with an HP ex900 with no issues.
[[/doublepost]
No problems with an HP ex900 in a 2017 Air.
Attachments
Last edited:
Perhaps someone good with the technical terminology should first explain us the difference between EFI and Bootrom, are they the same, or one is part of the other, or they are not connected at all? In which one is the NVME DXE driver located, what does the Matt card / SPI programmer affect? All things considered, is it all about the EFI driver, not the bootrom version, as with 10.14.4 the bootrom changed, the EFI and the sleep problems did not.
Not that I know of. According to Sintech the adapters should be internally (concerning electronics) identical. However, since I do not own a short adapter I cannot provide information based on first hand experience, which is why I mention I got the long ones
Last edited:
This list appears to have been updated to include the latest EFI versions after installing both the 10.14.4 and new security update. Maybe some people without updated EFI haven’t installed the security update.
https://www.google.com/amp/s/eclect...mware-should-your-mac-be-using-version-3/amp/
Your bootrom will also get an update on High Sierra and Sierra with the security update.
[doublepost=1553643557][/doublepost]
Pretty sure EFI and BootROM version both refer to the same thing.
https://www.google.com/amp/s/eclect...mware-should-your-mac-be-using-version-3/amp/
Your bootrom will also get an update on High Sierra and Sierra with the security update.
[doublepost=1553643557][/doublepost]
Pretty sure EFI and BootROM version both refer to the same thing.
Last edited:
I thought the long ones had to be manually trimmed in some cases, which is why I was planning to get a black Sintech short (for my late 2013 Pro 15"), or am I confused or mis-remembering earlier posts?
Even though the long adapter had to be trimmed in some cases, the long and short adapters are internally identical.
Sabrent Rocket's are on a great sale right now.
https://slickdeals.net/f/12967240-s...b-nvme-usb-3-1-external-160-2tb-300-much-more
https://slickdeals.net/f/12967240-s...b-nvme-usb-3-1-external-160-2tb-300-much-more
Hello,
I have a Macbook Air 13'' early 2014. I read the test results on compatibility of different nvme ssd brands in this thread, and picked Kingston A1000. I ordered Sintech ST-NGFF2013C adapter as recommended here. The Amazon links are https://www.amazon.com/gp/product/B07C8XDV11/ and https://www.amazon.com/gp/product/B01CWWAENG/, respectively.
Since I installed the drive, there has been multiple occurrences of kernel panic, which I am not sure if they are related to the hibernation issue that has been discussed here. It is my understanding that setting standby to 0 is a good workaround for that issue, so let me paste my pmset -g output:
The kernel panics I keep getting is the following. If needed I could paste the full report.
Now, I wonder if this is somehow related to hibernation, because it never happened when I'm using the laptop. Sometimes the laptop fails to wake up only after a couple minutes after I close the lid. When this happens, 1) the apple logo on the back of the screen would light up for a second, and then extinguish, 2) when I open the lid, the machine does not wake up, and it has to be hard reset, 3) when it boots up, the panic report is generated.
Any help in pointing me to the right direction is appreciated!
I have a Macbook Air 13'' early 2014. I read the test results on compatibility of different nvme ssd brands in this thread, and picked Kingston A1000. I ordered Sintech ST-NGFF2013C adapter as recommended here. The Amazon links are https://www.amazon.com/gp/product/B07C8XDV11/ and https://www.amazon.com/gp/product/B01CWWAENG/, respectively.
Since I installed the drive, there has been multiple occurrences of kernel panic, which I am not sure if they are related to the hibernation issue that has been discussed here. It is my understanding that setting standby to 0 is a good workaround for that issue, so let me paste my pmset -g output:
Code:
System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 0
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
disksleep 0
standbydelayhigh 86400
sleep 60
autopoweroffdelay 28800
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 60
highstandbythreshold 50
acwake 0
lidwake 1The kernel panics I keep getting is the following. If needed I could paste the full report.
Code:
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8bca4172): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x2 VID/DID=0x50082646
. FW Revision=E8FK11.R\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.230.1/IONVMeController.cpp:5327
Backtrace (CPU 0), Frame : Return Address
0xffffff90a9833a10 : 0xffffff8008baeb0d
0xffffff90a9833a60 : 0xffffff8008ce8653
0xffffff90a9833aa0 : 0xffffff8008cda07a
0xffffff90a9833b10 : 0xffffff8008b5bca0
0xffffff90a9833b30 : 0xffffff8008bae527
0xffffff90a9833c50 : 0xffffff8008bae373
0xffffff90a9833cc0 : 0xffffff7f8bca4172
0xffffff90a9833e20 : 0xffffff800925e147
0xffffff90a9833e90 : 0xffffff800925e069
0xffffff90a9833ec0 : 0xffffff8008beb085
0xffffff90a9833f40 : 0xffffff8008beac35
0xffffff90a9833fa0 : 0xffffff8008b5b0ce
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[ABA6DFDD-AC72-3008-83FE-EF9722E66FEB]@0xffffff7f8bc8f000->0xffffff7f8bccefff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A2492141-9480-3177-BC7D-455925BB4A2E]@0xffffff7f899c5000
dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f89495000
dependency: com.apple.driver.AppleEFINVRAM(2.1)[328FCBD7-8C2C-3A4A-AF92-9270C1403891]@0xffffff7f89b9b000
dependency: com.apple.iokit.IOStorageFamily(2.1)[9B2E7108-AA17-3998-BF41-4B1297F455E5]@0xffffff7f897c0000
dependency: com.apple.iokit.IOReportFamily(47)[5F165AE5-F4F2-3415-857C-34F2462A730E]@0xffffff7f89cea000Now, I wonder if this is somehow related to hibernation, because it never happened when I'm using the laptop. Sometimes the laptop fails to wake up only after a couple minutes after I close the lid. When this happens, 1) the apple logo on the back of the screen would light up for a second, and then extinguish, 2) when I open the lid, the machine does not wake up, and it has to be hard reset, 3) when it boots up, the panic report is generated.
Any help in pointing me to the right direction is appreciated!
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
According to your pmset report, all your modes have been set to “0” so your system should only be sleeping and will not hibernate. Once battery is dead it will just shut off and boot up fresh once plugged back in. It might be an issue with the Nvme drive.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.