Do you guys pay customs tax and VAT when ordering from Amazon.com to EU, or do they have local warehouses from where they ship already imported goods?
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
Great drive and great price but one thing to be aware of is that the drive uses Advanced Format native sectors (4Kn) opposed to 512 sector emulation (512e) which means you are likely to have issues cloning to the drive if if the source wasn’t also formatted (4Kn). Migration assistant should work find however.
I am planning to upgrade my macbook air 11" 2015 with nvme drive.
As far as I remember from the old posts, old sintech green is better then new sintech black. In the updated first post there is a image of sintech green but link of sintech black. So I got little confused. Which adapter should I buy ?
For the drive; I am planing to buy "Sabrent Rocket Pro 1TB"
As far as I remember from the old posts, old sintech green is better then new sintech black. In the updated first post there is a image of sintech green but link of sintech black. So I got little confused. Which adapter should I buy ?
For the drive; I am planing to buy "Sabrent Rocket Pro 1TB"
The air is running the latest OS and bootrom? If not, it may be a good idea to update both and then use the air to see if the panics continue.
[doublepost=1553683915][/doublepost]
Both the short green and short black are fine. I'm running the short green in a 2015 13" Air and the short black in a 2017 Air 13".
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
If I recall correctly, installing Sierra requires a nvme drive that can be further in 4k sectors; otherwise, High Sierra or Mojave must be used.
Last edited:
Hello,
My MacBookPro 11,1 has Firmware 149.0.0.0.0, running macOS 10.14.4.
Somewhere I found that 151.0.0.0.0 is the current one?
My Mac still has 149.0.0.0.0. Perhaps because i installed the betaOS or because of my SamsungSSD?
Do I have to reinstall my original SSD and update my macOS on this SSD again to 10.14.4 to get the current BootRom?
Does this update solve the nvme-hibernate problems?
Thanks in advance!
My MacBookPro 11,1 has Firmware 149.0.0.0.0, running macOS 10.14.4.
Somewhere I found that 151.0.0.0.0 is the current one?
My Mac still has 149.0.0.0.0. Perhaps because i installed the betaOS or because of my SamsungSSD?
Do I have to reinstall my original SSD and update my macOS on this SSD again to 10.14.4 to get the current BootRom?
Does this update solve the nvme-hibernate problems?
Thanks in advance!
I just realized the security update is part of 10.14.4 and is a separate download for Sierra and High Sierra which will update the BootROM on those systems.
So it’s true that you need an Apple OEM drive installed to get the BootROM to update?
[doublepost=1553710966][/doublepost]If the update doesn’t include NVME driver then I suppose just missing out on some lower level hardware security patching without the BootROM update.
So it’s true that you need an Apple OEM drive installed to get the BootROM to update?
[doublepost=1553710966][/doublepost]If the update doesn’t include NVME driver then I suppose just missing out on some lower level hardware security patching without the BootROM update.
There were two versions of the black sintech adapter :
- a first version, sold between 2017 and mid to late 2018, had incorrect wirings (similar to the chenyang adapter) and, like thé chenyang, made problems occur : lost of ssd at reboot, kernel panics, etc
- a second version, currently sold (I don’t know precisely from when but I think since october 2018 maybe) has the proper wirings and works perfectly, like the sintech green and long black
The long black adapter doesn’t handle “double side” m.2 ssd (due to their thickness) and is to avoid with double size SSDs.
[doublepost=1553723208][/doublepost]
No, to this date the BootRom updates that come with lot of security updates simply don’t work on 2013-2015 MacBook Air and pros while booted on any NVMe drive.
This has been tested and verified with OWC and Transcend NVMe drives (Aura Pro X and JetDrive 850), Apple genuine NVMe drives ( Polaris SM0512L ) and any other M.2 NVMe drive with sintech adapters.
Simply, those Mac don’t get their bootrom updated while booted on NVMe drives ( neither on any external drive too).
Bug reports have been sent to Apple and I can only recommend to everyone here to send bug reports (this is little effort which can have great results)
Bug reports can also been sent for the hibernation problem with NVMe drives on 2013-2014 macs.
As for the BootRom not updated this has a negative and a positive effect :
- On the positive side, this prevent the patch of NVMe driver to be smashed at each BootRom update
- On the negative side, one doesn’t benefit from potential security updates in BootRom updates
There is a way to know if any BootRom update will ever bring a full NVMe driver supporting hibernation (even on beta versions), without the need to install it :
- When an update is available, let macOS download it but don’t install it yet
- Open the /Library/Updates folder
- You will find inside a folder named with the revision of the update, open it
- Inside, there is among other thins the package named “FirmwareUpdate.pkg”
- Open it with pacifist, find the Payload folder inside the EFI updates folder
- Then you can edit the BootRom of, say, the MacBookPro11.1 with efitool
It it is compressed and has a size of 10k, it won’t handle hibernation.
If it is not encapsuled compressed and has a size of 24k, then it is ok for wake up from hibernation
- NVMe drives with 4K sector size (ex. : Sabrent Rocket) do work natively with macOS 10.12, of course you need to have your BootRom up to date before installation
1. Update OS X to the newest version on the OEM SSD so the bootrom gets updated as well.
2. Install the Sintech adapter and NVMe drive
3. Install the correct version of osx?
Hi,
You are very knowledgable and I was wondering if you could look at my post about a bootrom update that appears to have been applied to my MacBook Air 2015 while a Intel 600p nvme drive was installed: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-149#post-27223730
Early 2015 13" MacBook Air 7,2 system report before and after update from 10.14.3 to 10.14.4, reflectively:
Bootrom with 10.14.3: 182.0.0.0.0
Bootrom with 10.14.4: 184.0.0.0.0
I reinstalled 10.14.4 with an original Apple SSD and nothing appears to have changed.
Thank you.
Last edited:
I’ve heard reports of the Boot Rom version updating but not the EFI version. What different things do they contain? Thanks!
[doublepost=1553734666][/doublepost]
You can use with 10.12 and up but on 10.12 4K is required.
[doublepost=1553734944][/doublepost]
Do you know if your EFI version had also changed when first did the install without the Apple drive? Someone on another thread with a NVME drive in a iMac said their BootROM updated but not the the EFI. I had thought that the EFI version would always change if Bootrom updated. I’m not sure functions you see with one vs the other.
Does this post provide the information you need: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-149#post-27223011 ?
If you need more information, please let me know and I'll try to find it. Thanks.
I missed that. You have the latest BootROM based on the list from the link I provided earlier. Not sure about the EFI version though. Do you know if it changed after you first did the update?
I can't say if it changed after I upgraded because I neglected to run the EFI check while running bootrom 182.0.0.0.0. All I can say is that the EFI version did not change when I reran the 10.14.4 update with an original Apple SSD.
I started a new thread in the Macbook Air forum to see which EFI version corresponds to which EFI version.
The latest release of 10.14.3 came out on February 7/19 according to this article: https://www.macrumors.com/2019/02/07/apple-releases-macos-10-13-4-facetime-fix/
The EFI version on my 2015 Air after installing 10.14.4 is EFI Version: MBA71.88Z.F000.B00.1902151233.
If I'm reading the EFI string correctly, the EFI version is dated 2019-02-15 which is 8 days after the last GM revision of 10.14.3 was released, although I'm not sure if this is an indication of anything.
With the release of 10.14.4 being March 25/19 (https://www.macrumors.com/2019/03/25/apple-releases-macos-mojave-10-14-4/) which is over a month after the EFI version date, this may or may not be significant too.
You’d think you’d have a new date stamp. You’ll have to compare with others that have your MacBook Air model that have done the update to what EFI version they have.
[doublepost=1553749144][/doublepost]
Is there a way check after you’ve installed the update? I’m interested in checking for my Late 2015 iMac before I install a NVME. Thanks.
Successfull installation of the sandisk extreme pro 1to Nvme, with the correct sintech adaptater; Installation went like a breeze, I did purchase the sintech external enclosure for my apple SSD (a costly purchase maybe, but for me it was worth it).
Speed test wise, 1394.1 MB/s write, 14739MB/s read.
This disk is similar to WD Black so I suspect performance are on par.
Speed test wise, 1394.1 MB/s write, 14739MB/s read.
This disk is similar to WD Black so I suspect performance are on par.
Last edited:
Others are also reporting a February date stamp that have the latest BootROM so either the EFI version didn’t change or the date stamps are probably older based on when Apple started testing them.
https://eclecticlight.co/2018/10/31/which-efi-firmware-should-your-mac-be-using-version-3/
I thinking that if the BootROM is current that you you have the full update but don’t know why the also list an EFI version. Don’t believe they started that until High Sierra. I can only check the BootROM on my MacBook Pro because running Sierra which doesn’t support the EFI check command.
[doublepost=1553752311][/doublepost]Doing more reasearch I now see that the EFI Check and EFI versions are an extra security measure for Apple to report modified firmware. If your BootROM updated then I think you got the full update.
Last edited:
so it should be possible here to include the NVMe driver for older Macbooks before updating to 10.14.4??
I upgraded my late 2013 MacBook Pro 13" 11,1 to 10.14.4 and it's EFI version is MBP111.88Z.F000.B00.1902141640 with a date stamp of 2019-02-14 and is 1 day before my 2015 Air's EFi date stamp of 2019-02-15.
Based on comments I see at the bottom of the article (https://eclecticlight.co/2018/10/31/which-efi-firmware-should-your-mac-be-using-version-3/), a February, 2019 date stamp appears to be common for many models of MBPs. The last comment is dated March 28/19 and its response is interesting:
Post:
I noticed that that the eficheck date stamp for the latest firmware is from February. Is this a new date stamp or didn’t change form the last firmware? Is the BootROM and EFI version different components that provide different functions? If so is it possible for an error to occur where the BootROM get’s updated but not the EFI version?
This is new EFI firmware, and simply has two different version numbers because Apple changed the numbering system. They’re the same thing, just two different ways of recognising which version it is.
Howard.
Howard.
Last edited:
It see
So it’s confirmed that the firmware was updated on your MacBook Air even without the OEM drive installed. I wonder if this will only occur with certain Mac models or 3rd party drives?
So it’s confirmed that the firmware was updated on your MacBook Air even without the OEM drive installed. I wonder if this will only occur with certain Mac models or 3rd party drives?