Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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'd like to know this too please.

I'm actually doing this on 2 MBP - is there anything different I need to consider for an early-2015?

I'm more concerned about getting hibernation correct.

Hibernation does work afaik natively with Macs early 2015 or later. Just Macs 2013 / 2014 seem to have the deep sleep hibernation issue.
 
Hibernation does work afaik natively with Macs early 2015 or later. Just Macs 2013 / 2014 seem to have the deep sleep hibernation issue.

That's good to know - it's the mrs' mac so needs to run as original or else I'll be getting collared every 5 mins to fix
 
If you have another Mac with an original Apple SSD just put the functioning original SSD in your Mac with the bad ssd and reinstall High Sierra. Once High Sierra is installed your bootrom is also updated and you have NVMe support.
Then you can remove the Apple SSD and insert your Samsung Evo 970 and install High Sierra.
Guys we are able to update the EFI firmware using 3rd party SSD drives; this requirement is no longer true. See previous posts :)
 
Guys we are able to update the EFI firmware using 3rd party SSD drives; this requirement is no longer true. See previous posts :)

Is the EFI firmware up[date automatic on OS update?

Also - can someone confirm if this is the correct Intel 760p? https://amzn.to/2zzrRQR
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
haven't checked for a while. There was a way to manually update/hack the bootroom for mac 2013/2014. But it required special hardware. Is there a way now a couple of months later to do it just with software?
 
Guys we are able to update the EFI firmware using 3rd party SSD drives; this requirement is no longer true. See previous posts :)
That's great to hear. I am on a MacBook Pro 13" early 2015 with Samsung 961. Currently in the process of upgrading to Mojave. Hoping that my boot ROM mbp121.0171.b00 is already the latest or gets upgraded if it is not.

Edit: looks like you have to force the EFI update. But still good that we can update with a 3rd party drive in there.
 
Last edited:
haven't checked for a while. There was a way to manually update/hack the bootroom for mac 2013/2014. But it required special hardware. Is there a way now a couple of months later to do it just with software?

I’ve pretty much read everything and the only one that can be done with software is the cheese grater desktop Mac. Our laptops all have to be done with a chip programmer. Theoretically it can be done but I think Apple has it locked somehow and no one has found a way around that.
 
I’ve pretty much read everything and the only one that can be done with software is the cheese grater desktop Mac. Our laptops all have to be done with a chip programmer. Theoretically it can be done but I think Apple has it locked somehow and no one has found a way around that.

yeah wouldn't be Apple if they don't lock / make it difficult for third party repairs :D
I think Apple is not going to address that issue for the 2013/2014 Macs since they are almost 5 years old.
 
I'm in the middle of my ssd upgrade, with an Adata sx8200 on a MacBook Pro retina late 2013 ( MacBookPro11,1 ) .... I just clean installed Mojave.

I'm going to see if I need the boot rom upgrade to solve any delay/sleep problem.
Actually my boot rom is the stock MBP111.0146.B00, and reading all posts I've come to the conclusion that maybe a "software upgrade" with Room Tool is the simplest way to go.

So I downloaded "room tool 2" and managed to dump the rom.
Everything went well, I believe, but Room tool offered several options regarding the IC to read, with a default of MX25L6445E. I went ahead and got the rom.bin file, that I can open with UEFItool.
It seems ok since I can find the "nvme" string inside ....

My doubt is: for a MacBook Pro retina 13" late 2013 .... can anybody confirm that the IC is actually a
MX25L6445E ?

I would not like to disassemble all the machine just to see the label on the chip ... from what I saw on iFixit the chip in on the bottom side of the motherboard.

In any case I went ahead to prepare a "patched" rom.
I was unable to find the firmware section that Gilles indicated (inside the Mojave install I can't find any "FirmwareUpdate.pkg".... maybe no boot rom upgrade with it).
But on the thread regarding the Mac Pro I found a guide with links also to a "NVMe_DXE.ffs" file that I dowloaded .... I REALLY HOPE THAT THIS DRIVER IS OK FOR a MacBook Pro .... (can anybody confirm?)

Finally with UEFITOOL I managed to substitute the nvme driver in my original rom with this new one ... and now I have a "rom_nvme.bin" ready for use ....

I repeat myself: I don't know if I'll need it, but just in case, the plan is to use Room Tool 2 to flash the new rom (well I hope it can also write!).

Any suggestions?
 
## Mojave update no new firmware on Macbook Air 2014 ##
I have for a long time been experimenting with the 3rd party NVMe drives in MacBook Pro/Air 2013-15.
I have had mostly sleep issues, never had a problem with not recognizing the drive on installation etc. I also wondered if it would be better with the OS X Mojave update.

- I checked the MB firmware before and after the update (on original Apple SSD). No change
- I tested now Sintech long black adapter v.2. No kapton tape at all like I did on the short Sintech green adapters.
- Samsung EVO 970 500 GB, 1380 MB/s write and 1530 MB/s read. The 2014 MBA runs 4-lane and 5G.
- The Evo 970 is freaking hot (can't touch it) but I never got over 97 degrees C on the CPU in HWMonitor. Once I quit the stress test (did 5 x yes > /dev/null) it sure cools down fast to about 40-47 C.

- I never experience any problems with large file transfers on Evo 970. Does anyone know if this is in fact a better choice than 960?

Still I have this in pmset:
sudo pmset -a standby 0 hibernatemode 0 autopoweroff 0

I am testing to see if the battery drains less now on Mojave. I guess with this setting I will never be able to recover from unsaved work if I leave the MBA closed for 3 weeks (completely power drained)?

## Update ##
I left the MBA closed for 2 days and there was no power drain. I don't think that happened with High Sierra, lost 30% battery. But then I have maybe not done this test scientificly correct.
 
Last edited:
yes, just close the lid for more than 3+ hours and your mac should be in hibernation mode.
Or you could try the the commands
sudo pmset hibernatemode 25
pmset sleepnow

that will give you the results in minutes (I am not sure how many minutes exactly in mojave, see post 2036)

5QrA1.png


I did the test last night as follow steps:
0. close the lid at 0:30 AM (keep the AC adapter plugging in)
1. open the lid at 7:45 AM (so the test lasted for 7-hour and 15-minutes)

And the screen turned on as soon as I opened the lid and macOS woke up immediately, so I think the machine did not enter deep sleep or hibernate mode at all....

Maybe I need some adjustment of my pmset parameters?
 
Maybe I need some adjustment of my pmset parameters?
To test deep sleep on Mojave:

sudo pmset -a standbydelaylow 180
sudo pmset -a standbydelayhigh 360
sudo pmset -a standby 1

Close the lid and wait about 10 minutes before opening it again.
Afterwards reset everything to their previous values.

Could probably also set them lower, that's just what values I've used. My 2014 MBPr 13" completely freezes after this process.
 
close the lid at 0:30 AM (keep the AC adapter plugging in)

As Mackube pointed out there are now 3 parameters for standby in mojave.
I guess because your AC adapter was plugged in and you had enough battery life left pmset switched to standbydelayhigh 86400.
86400 seconds are exactly 24 hours. So in your case you had to close your lid for 24+ hours.

As mentioned earlier for fast results
sudo pmset hibernatemode 25
pmset sleepnow


or MacKube's solution should work too in 6+ Minutes.
 
I'm in the middle of my ssd upgrade, with an Adata sx8200 on a MacBook Pro retina late 2013 ( MacBookPro11,1 ) .... I just clean installed Mojave.

I'm going to see if I need the boot rom upgrade to solve any delay/sleep problem.
Actually my boot rom is the stock MBP111.0146.B00, and reading all posts I've come to the conclusion that maybe a "software upgrade" with Room Tool is the simplest way to go.

So I downloaded "room tool 2" and managed to dump the rom.
Everything went well, I believe, but Room tool offered several options regarding the IC to read, with a default of MX25L6445E. I went ahead and got the rom.bin file, that I can open with UEFItool.
It seems ok since I can find the "nvme" string inside ....

My doubt is: for a MacBook Pro retina 13" late 2013 .... can anybody confirm that the IC is actually a
MX25L6445E ?

I would not like to disassemble all the machine just to see the label on the chip ... from what I saw on iFixit the chip in on the bottom side of the motherboard.

In any case I went ahead to prepare a "patched" rom.
I was unable to find the firmware section that Gilles indicated (inside the Mojave install I can't find any "FirmwareUpdate.pkg".... maybe no boot rom upgrade with it).
But on the thread regarding the Mac Pro I found a guide with links also to a "NVMe_DXE.ffs" file that I dowloaded .... I REALLY HOPE THAT THIS DRIVER IS OK FOR a MacBook Pro .... (can anybody confirm?)

Finally with UEFITOOL I managed to substitute the nvme driver in my original rom with this new one ... and now I have a "rom_nvme.bin" ready for use ....

I repeat myself: I don't know if I'll need it, but just in case, the plan is to use Room Tool 2 to flash the new rom (well I hope it can also write!).

Any suggestions?
You can't flash the modified bootrom file to your MacBook via software means. You need to do it using a hardware programmer.
## Mojave update no new firmware on Macbook Air 2014 ##
I have for a long time been experimenting with the 3rd party NVMe drives in MacBook Pro/Air 2013-15.
I have had mostly sleep issues, never had a problem with not recognizing the drive on installation etc. I also wondered if it would be better with the OS X Mojave update.

- I checked the MB firmware before and after the update (on original Apple SSD). No change
- I tested now Sintech long black adapter v.2. No kapton tape at all like I did on the short Sintech green adapters.
- Samsung EVO 970 500 GB, 1380 MB/s write and 1530 MB/s read. The 2014 MBA runs 4-lane and 5G.
- The Evo 970 is freaking hot (can't touch it) but I never got over 97 degrees C on the CPU in HWMonitor. Once I quit the stress test (did 5 x yes > /dev/null) it sure cools down fast to about 40-47 C.

- I never experience any problems with large file transfers on Evo 970. Does anyone know if this is in fact a better choice than 960?

Still I have this in pmset:
sudo pmset -a standby 0 hibernatemode 0 autopoweroff 0

I am testing to see if the battery drains less now on Mojave. I guess with this setting I will never be able to recover from unsaved work if I leave the MBA closed for 3 weeks (completely power drained)?
The 970 runs hot; I've swapped mine out for an Intel 760p. Others use the ADATA SX8200. Comparable speeds and power usage.
 
Ok, just to be sure. I have a Macbook Pro 2015 with a 760p and a sintech black adaptor on High Sierra, bootrom MBP121.0177.B00 . I can safely update to Mojave without a apple ssd, right? There are no issues with it?
 
Ok, just to be sure. I have a Macbook Pro 2015 with a 760p and a sintech black adaptor on High Sierra, bootrom MBP121.0177.B00 . I can safely update to Mojave without a apple ssd, right? There are no issues with it?
Correct :) 2015 and later Macbook's do not have any hibernation issues. Older ones simply need to change their pmset values using a simple comand so there's never really a huge problem :)
 
You can't flash the modified bootrom file to your MacBook via software means. You need to do it using a hardware programmer.

The 970 runs hot; I've swapped mine out for an Intel 760p. Others use the ADATA SX8200. Comparable speeds and power usage.
Thanks @Trunkz I just read some reviews yesterday concerning power usage and heat. I will opt for the Intel 760p as I have had good experience with the Intel 600p and the 760p is falling now price wise. I use the Evo 970 for Hacintoshes since they are really cheap these days (and blazing fast).

For my test I had 4 programs open yesterday, 99% battery. Closed the lid on the MBA and this morning it was 97%. Do you think it did not enter deep sleep? Everything was normal like with orignal ssd.
 
You can't flash the modified bootrom file to your MacBook via software means. You need to do it using a hardware programmer.


Why?
After all, Apple has been writing new rom by software every time they decided, my boot room was updated by installers many times during the past years ....
Unless ROOM TOOL is unable to write ... but why can it work on Mac Pros and not on MacBook pros?
 
First, thank you guys for the amazing work here! I have two questions:
1) Is Intel 760p better than Samsung 960 Evo? I read about better thermal performance and longer battery life. My current setup is with Samsung, but I found a good deal for the Intel SSD: if the difference is relevant I'll switch.
2) Mojave update: an original Apple SSD is needed? I can update just using the Samsung device already in?

I apologize for the imperfect English, and I thank you in advance for your answers.
 
First, thank you guys for the amazing work here! I have two questions:
1) Is Intel 760p better than Samsung 960 Evo? I read about better thermal performance and longer battery life. My current setup is with Samsung, but I found a good deal for the Intel SSD: if the difference is relevant I'll switch.
2) Mojave update: an original Apple SSD is needed? I can update just using the Samsung device already in?

I apologize for the imperfect English, and I thank you in advance for your answers.


Based on what I've gathered and researched, the Intel 760p is superior than the Samsung 960 Evo when it comes to low power consumption thus, battery life. However, I don't believe that the Intel 760p has performance speeds as high as the 960, but that performance is ignored if using a MacBook that doesn't support the speeds.

As for updating on a third-party SSD, it seems that it's possible as the bootrom has not changed for 2015 and later devices, I am uncertain and will perform my own tests when Mojave becomes more stable and I see verified results that it supports my device!
 
Why?
After all, Apple has been writing new rom by software every time they decided, my boot room was updated by installers many times during the past years ....
Unless ROOM TOOL is unable to write ... but why can it work on Mac Pros and not on MacBook pros?

The macpro has an older rom chip and is updated differently and even then its hit or miss on being able to be updated software only from what I’ve read on it.
 
Hey guys. So, after this night, I decided to leave the macbook unplugged with the screen closed to see how the deep sleep was, and I think I have a problem.

mWtTs52.png


Almost 50% during the night. Again, this is my first mac, not sure if it's normal or not, I just want to make sure.

Also, updating from HS to Mojave with the 760p worked just fine, running Mojave now and no issues at all, except from this one (well, not sure if it's even a issue).
 
Based on what I've gathered and researched, the Intel 760p is superior than the Samsung 960 Evo when it comes to low power consumption thus, battery life. However, I don't believe that the Intel 760p has performance speeds as high as the 960, but that performance is ignored if using a MacBook that doesn't support the speeds.

I was referring at the ssd's temperature (thermal performance). My Samsung SSD is quite a bit hot. The Intel is colder? (I read about a different controller..)

As for updating on a third-party SSD, it seems that it's possible as the bootrom has not changed for 2015 and later devices, I am uncertain and will perform my own tests when Mojave becomes more stable and I see verified results that it supports my device!

I have a early 2015 13" mackbook pro. The update is not at all a priority, so I'll wait for other people experiences. Thanks a lot!
 
About to embark on upgrading late 2013 MBP retina.
Have a 960GB SX8200 and the short JSER adapter several others appear to be successfully using.
Will start with High Sierra upgrade, Time Machine backup to external drive, and while that's happening will be reading lots of this thread.

Can anyone point to a specific post as the "definitive how-to"?
 
It appears that Mojave 10.14.1 Public Beta 1 has new firmware version, numbered MBP112.88Z.0147.B00, and with a build date of Fri Aug 17 05:23:38 PDT 2018.

Unfortunately the NVMe driver does not look like the one from the 2015 machines. I did a comparison and there are only two differences between the two binaries, and not in code regions; I I'm not sure I want to be the person testing out whether it fixes the hibernate and power issues... but if anyone wants to try, I'd love to hear their experience.

Upgrading to this firmware will probably require re-patching to maintain the newer NVMe driver, unfortunately.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.