Shame.
Just build a standalone installer of the 10.14.2 EFI firmware update. Again, no dice as it would appear that the SSD is checked as part of the verification process.
Looks like I'll have to keep the original drive
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
Just build a standalone installer of the 10.14.2 EFI firmware update. Again, no dice as it would appear that the SSD is checked as part of the verification process.
Looks like I'll have to keep the original drive
Was the original Apple SSD inside the Macbook at the time of installation?
Yes, you will need to disable hibernation or flash a modded bootrom to avoid panics associated with sleep.
[doublepost=1544373929][/doublepost]
I have an Intel 600p SSD inside an early 2015 13" Air. When I updated to 10.14.1 from 10.14, the update did update the bootrom. This is the first time that my Air accepted a bootrom update with an nvme drive inside.
You could sell the original drive and buy a smaller Apple SSD to keep for bootrom updates?
Yes, it was.
From this link https://apple.stackexchange.com/que...e-ssd-drives-via-the-use-of-a-sintech-adapter
Y.H Wong said:
I've done a little research into transplanting NVMe Driver from one firmware to another and I did the following:
In Terminal: /usr/libexec/firmwarecheckers/eficheck --integrity check and found that my EFI version was actually: MBP112.88Z.0147.B00.1809171519
Downloaded the latest combo update as a test: https://support.apple.com/kb/DL1987?locale=en_US
From pkg, Extract EFI/Payloads directory, find this file, MBP112.scap and open it using UEFI Tool mentioned in the guide earlier.
Seached and found the same EFI version mentioned above and checked for the same GUID NVMe driver "511116915..."
Then follow Y. H. Wong's idea of transplanting NVMe Driver from MBP114.fd to MBP112.scap via UEFI Tool:
/usr/libexec/efiupdater -p /path/to/EFIPayloads --force-update
I'm pretty sure this will work but I don't want to brick my system since I don't have a CH341A or another machine to use.
Given these steps, do any of you foresee a problem?
Last edited:
I am currently considering buying 1 TB of the ADATA XPG SX8200 series.
What is the difference between using SX8200 and SX8200 Pro on “MacBook Pro Retina 15' Late2013” ?
What is the difference between using SX8200 and SX8200 Pro on “MacBook Pro Retina 15' Late2013” ?
Last edited:
I personally see it failing due to the signing but if does work that would be awesome. Keep us updated on the progress.
I was unable to get the efiupdater command with the --force-update flag on to upgrade my Macbook Pro 2013 to the latest stock firmware from 10.14.1, so not sure if the above will work.
Hey guys, can anyone help me?
Bought the Sintech Adapter and tried to mount a Samsung 970 Evo. I'll try to give many Information as possible.
I got a MacBook early 2015 with 128 GB SSD delivered with El Capitan. I'm using it for 2 years now. OS Mojave made my battery very weak so I reinstalled High Sierra. Then I opened my Mac, disconnected the battery and used the Sintech Adapter on my Samsung Evo 970 500 GB. It took me a while that the MacBook recognized the HDD because of the partition. Now it doesn't let me instsll High Sierra from a bootable USB because it says, that my SSD is a PCI and needs a GUID partition. If I press erase I press OS Journaled partition and get a succesfull message. But I still can't install OS X again.
Any suggestions?
Bought the Sintech Adapter and tried to mount a Samsung 970 Evo. I'll try to give many Information as possible.
I got a MacBook early 2015 with 128 GB SSD delivered with El Capitan. I'm using it for 2 years now. OS Mojave made my battery very weak so I reinstalled High Sierra. Then I opened my Mac, disconnected the battery and used the Sintech Adapter on my Samsung Evo 970 500 GB. It took me a while that the MacBook recognized the HDD because of the partition. Now it doesn't let me instsll High Sierra from a bootable USB because it says, that my SSD is a PCI and needs a GUID partition. If I press erase I press OS Journaled partition and get a succesfull message. But I still can't install OS X again.
Any suggestions?
Attachments
Hello, anybody has problem with unpack FirmwareUpdate.pkg?
when i type
pkgutil --expand FirmwareUpdate.pkg FirmwareUpdate
Could not open package for expansion: FirmwareUpdate.pkg
tried with sudo too, file exist in folder (auto type with tab using so name is good)
when i type
pkgutil --expand FirmwareUpdate.pkg FirmwareUpdate
Could not open package for expansion: FirmwareUpdate.pkg
tried with sudo too, file exist in folder (auto type with tab using so name is good)
Can you go to ‚Darstellung‘ and let it display all devices? Then select the top device level and show us the screenshot again?
Magnus
From the little I have seen, the Pro version seems to run at the same temps as the non-Pro version, so its faster controller seems to be reasonably frugal. Your MBP only has PCIe 2.0, so you won't see any faster sequential read/write speeds over using the non-Pro version. Costs of both sticks seem to be identical. Hopefully, we'll see some tests on Mac hardware soon.
I'm about the farthest from an expert on anything here, but is there a software method of dumping your current firmware to file and putting it on a usb drive so that you have something to recover off of in case it goes wrong? You'd still need to get a CH341A and borrow a computer, but at least then you'd have some recourse.
I don't know if that's possible, but it seems like it would be a good idea. I'm super interested in the outcome of your experiment here, so if you do try it, be sure to let us know!
Wait, how were you able to modify the scap file with UEFI Tool? The latest version has the replace option disabled and the old version won't open scap files.
I can dump the EFI rom to a .bin, but I don't know if you can flash that through efiupdater.
EDIT: Okay, I renamed the scap file to fd and it let me open it fine. That feels a little wrong, but I did the replace, verified it, everything looked good. Ran the efiupdate as described and rebooted, but it didn't appear to actually do anything. There were no errors I noticed through the efiupdate process and I ran it as root.
I'm on the previous mojave bootrom (.0146) so I thought I would use this as an opportunity to upgrade. Checked system report when I got back to osx and it was still showing 111.0146.000 instead of the newest Mojave bootrom version (.0150 I think it was?). I also extracted the rom and checked the checksum, which was still the old version.
Maybe I missed a step, but I don't feel like it. Maybe I need to update to regular .0150 first, but I kind of doubt that as well.
I can dump the EFI rom to a .bin, but I don't know if you can flash that through efiupdater.
EDIT: Okay, I renamed the scap file to fd and it let me open it fine. That feels a little wrong, but I did the replace, verified it, everything looked good. Ran the efiupdate as described and rebooted, but it didn't appear to actually do anything. There were no errors I noticed through the efiupdate process and I ran it as root.
I'm on the previous mojave bootrom (.0146) so I thought I would use this as an opportunity to upgrade. Checked system report when I got back to osx and it was still showing 111.0146.000 instead of the newest Mojave bootrom version (.0150 I think it was?). I also extracted the rom and checked the checksum, which was still the old version.
Maybe I missed a step, but I don't feel like it. Maybe I need to update to regular .0150 first, but I kind of doubt that as well.
Last edited:
I tried using the efiupdater command just to get version 149.0.0.0 installed from the 10.14.1 combo updater. Like you, I ran as root, got what looked like success but then rebooted and nothing happened. No update.
Found a whitepaper that might have something to do with that:
https://www.blackhat.com/docs/eu-17...e-State-Of-Apples-EFI-Security-Support-wp.pdf
paper above said:
I don't know for sure, but maybe it's detecting the fact that the rom has been modified and is blowing off the flash? It goes on to talk about how to do the work manually, which I haven't tried yet. It's worth noting that this paper is basically about rootkit development methodology, so I don't know what the implications of reading/using it are.
I tried taking the modified bootrom and repackaging it into the combo updater, and it tried to run (warned it would damage my system, so it detected that I messed with it) but it ended up exiting with an unspecific error about how it couldn't complete. A reboot after (hey, I could get lucky) showed that nothing significant happened.
Something else I tried was installing the factory hard drive and doing the update that way. My modified efi did nothing, but the stock combo update did get me to 149. So it's not the hard drive blocking it.
My next step is going to be making up a manual update process from that whitepaper and attempting that.
If anyone has 50 rep on Stack Overflow (I only have 8
) and wanted to do someone a solid favor, it'd be awesome if you ask "Y.H Wong" if he can give a more complete explanation of how he did it.
I found a new problem.
I used sintech ST-NGFF2013-B so far, but I purchased sintech ST-NGFF2013-C this time.
I found a problem Reference code: PPN001 displayed in Apple Diagnostics.
Reference code: PPN001 (not found in reference codes list)
There may be an issue with the power management system.
SMC reset and NVRAM clear have no effect.
---------
..........................................EFI ........................ ST-NGFF2013-B.................................... ST-NGFF2013-C
................................................MZ-HPV256...SUNEAST NVME 512GB...MZ-HPV256...SUNEAST NVME 512GB
MacBook Pro 13 2014 149.0.0.0.0 ...........OK.....................OK...................... NG...................NG
MacBook Pro 13 2015 180.0.0.0.0 ...........OK.....................OK....................... NG..................NG
MZ-HPV256: samsung PCIe AHCI
SUNEAST NVME 512GB: suneast PCIe NVMe
sintech ST-NGFF2013-B: isolated pins by myself, shows PCIe 2.0 x4 5MB/s
sintech ST-NGFF2013-C: no treatment, shows PCIe 2.0 x4 5MB/s
OK: always showed ADP000: No issues found.
NG: sometimes showed PPN001: There may be an issue with the power management system.
---------
I estimate that the power manager detected unexpected power consumption, but ST-NGFF2013-B and ST-NGFF2013-C should be the same circuit and it is suspected that a leak occurred somewhere.
Apple Diagnostics
https://support.apple.com/en-us/HT202731
Apple Diagnostics- Reference codes
https://support.apple.com/en-us/HT203747
MacBook Pro late 2013 13” PPN001 PFM006 fan at full speed and slow
https://www.ifixit.com/Answers/View/491642/MacBook+Pro+late+2013+13”+PPN001+PFM006+fan+at+full+speed+and+slow
Apple diagnostic PPN001. Fan running high, computer slow
https://discussions.apple.com/thread/8403877
[Additional notes 2018/12/13]
I suspected that pins are not insulated well, so I did same insulation treatment for ST-NGFF2013-C as ST-NGFF2013-B. The problem was resolved. Although ST-NGFF2013-C is affixed with insulation tape from the time of purchase, it seems to be insufficient even PCIe lane is x4.
[Additional notes 2018/12/17]
Unfortunately it was a mistake that I thought that the error code was resolved. It was found that even if the number of tests was increased, ST-NGFF2013-B or ST-NGFF2013-C occurred even if insulation treatment was applied. However, no error occurs in Apple's genuine SSD.
It is not clear what the cause is, but since all of the MacBook Pro 13 used for this test has 16 GB of RAM (usually 4 GB, 8 GB), It may be that there is little margin with the power consumption to judge (it is a selfish guess to the last).
I used sintech ST-NGFF2013-B so far, but I purchased sintech ST-NGFF2013-C this time.
I found a problem Reference code: PPN001 displayed in Apple Diagnostics.
Reference code: PPN001 (not found in reference codes list)
There may be an issue with the power management system.
SMC reset and NVRAM clear have no effect.
---------
..........................................EFI ........................ ST-NGFF2013-B.................................... ST-NGFF2013-C
................................................MZ-HPV256...SUNEAST NVME 512GB...MZ-HPV256...SUNEAST NVME 512GB
MacBook Pro 13 2014 149.0.0.0.0 ...........OK.....................OK...................... NG...................NG
MacBook Pro 13 2015 180.0.0.0.0 ...........OK.....................OK....................... NG..................NG
MZ-HPV256: samsung PCIe AHCI
SUNEAST NVME 512GB: suneast PCIe NVMe
sintech ST-NGFF2013-B: isolated pins by myself, shows PCIe 2.0 x4 5MB/s
sintech ST-NGFF2013-C: no treatment, shows PCIe 2.0 x4 5MB/s
OK: always showed ADP000: No issues found.
NG: sometimes showed PPN001: There may be an issue with the power management system.
---------
I estimate that the power manager detected unexpected power consumption, but ST-NGFF2013-B and ST-NGFF2013-C should be the same circuit and it is suspected that a leak occurred somewhere.
Apple Diagnostics
https://support.apple.com/en-us/HT202731
Apple Diagnostics- Reference codes
https://support.apple.com/en-us/HT203747
MacBook Pro late 2013 13” PPN001 PFM006 fan at full speed and slow
https://www.ifixit.com/Answers/View/491642/MacBook+Pro+late+2013+13”+PPN001+PFM006+fan+at+full+speed+and+slow
Apple diagnostic PPN001. Fan running high, computer slow
https://discussions.apple.com/thread/8403877
[Additional notes 2018/12/13]
I suspected that pins are not insulated well, so I did same insulation treatment for ST-NGFF2013-C as ST-NGFF2013-B. The problem was resolved. Although ST-NGFF2013-C is affixed with insulation tape from the time of purchase, it seems to be insufficient even PCIe lane is x4.
[Additional notes 2018/12/17]
Unfortunately it was a mistake that I thought that the error code was resolved. It was found that even if the number of tests was increased, ST-NGFF2013-B or ST-NGFF2013-C occurred even if insulation treatment was applied. However, no error occurs in Apple's genuine SSD.
It is not clear what the cause is, but since all of the MacBook Pro 13 used for this test has 16 GB of RAM (usually 4 GB, 8 GB), It may be that there is little margin with the power consumption to judge (it is a selfish guess to the last).
Last edited:
Where'd you get that adapter from?
Is that the short or full length one?
(Having trouble searching the model number - thx)
[doublepost=1544746693][/doublepost]I just grabbed a 2TB Samsung 970 EVO to try out in my 2015 15" MacBook Pro
Should I be getting the short or long Sintech adapter?
Long: http://a.co/d/8rmlmGv
Short: http://a.co/d/ap6JkQo
Do I have the right product links there?
Thanks for any expertise from anyone with Samsung EVO 970's
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
So - I bought this adapter after seeing confirmed reports of the EVO drive working with it in the 2015 15"
Adapter: http://a.co/d/ap6JkQo
My plan so far, unless anyone tells me a better way, is to use:
macOS Mojave Patcher from:
http://dosdude1.com/mojave/
...to make a bootable USB installer and then boot to that and install a fresh copy of Mojave on the installed EVO drive and then restore from a time machine backup.
Good idea?
Anything I'm missing?
Will I have the correct bootrom by installing a fresh copy of Mojave this way or will I still get stuck with an older, non NVME ready, bootrom if I do it this way?
Adapter: http://a.co/d/ap6JkQo
My plan so far, unless anyone tells me a better way, is to use:
macOS Mojave Patcher from:
http://dosdude1.com/mojave/
...to make a bootable USB installer and then boot to that and install a fresh copy of Mojave on the installed EVO drive and then restore from a time machine backup.
Good idea?
Anything I'm missing?
Will I have the correct bootrom by installing a fresh copy of Mojave this way or will I still get stuck with an older, non NVME ready, bootrom if I do it this way?
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Provided your at 10.13.6 with latest security patches you'll be at the same Bootrom version that Mojave is at on a 11,4 MBP
I wouldn't use that method for the USB install. Either create one yourself via Terminal or download Disk Creator and use that if your not comfortable with Terminal.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
The adapter Looks good. Mine is green but they should be The same. There is no need for The Mojave Patcher. I even think it would be counterproductive. I updaded to 10.14.1 with the Apple 256SSD. Then changed the SSD and Booted from an usb device. From there i installed Mojave. Everything went smooth. Never Had a Kernel panic. Also check here for further infos on specs and correct EFI versions and other helpful infos:
https://beetstech.com/blog/apple-proprietary-ssd-ultimate-guide-to-specs-and-upgrades
https://eclecticlight.co/2018/12/11/lockrattler-4-18-should-now-highlight-new-updates/
Also I like the painting perspective...
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Small update. Macbook pro 13 inch late 2013. High Sierra won't install on original Apple SSD because of failing SMART. I try several times to install High Sierra and Mojave on Apple SSD. Finally I plugged additional USB3 drive and installed Mojave and run it several times (it's wokring slower but wokring).
In addition I clone USB3 Mojave to internal Apple SSD using Disck Utility. So finally I had Mackbook running on original Apple SSD.
Finally I've discovered that my bootroom was updated to 149.0.0.0! I cannot tell when this happened. Sorry...
In addition I clone USB3 Mojave to internal Apple SSD using Disck Utility. So finally I had Mackbook running on original Apple SSD.
Finally I've discovered that my bootroom was updated to 149.0.0.0! I cannot tell when this happened. Sorry...
Ok - So there's a way to create a normal/legit Mojave USB installer?
I had no idea - thank you...
Making one in Terminal now....made
[doublepost=1544808012][/doublepost]How do you guys normally do your data transfer here onto these new NVME drives?
Would you suggest just restoring from a Time Machine backup?
A full/complete clone with CarbonCopyCloner?
Normally I'd mount up the former internal drive and restore right from that to the new internal, but that Apple SSD with it's unique connector gets in the way of that in this case, so I'm thinking of just doing Time Machine restore from Backup when installing Mojave on the 970 EVO.
Last edited:
Edit 1: Will do. I'm currently waiting on the adapter to get delivered and then I will see how things go.
Edit 2: I just ran everything that I went through and I think it did work! I'm waiting for the adapter to come but I ran all the commands on an apple SSD. I don't see any reason of this not working on an non-apple ssd since we are manually updating the EFI.
@tshelby73 It passed the integrity check with no problems!
@erudyne, The firmware file name and version would remain the same since we actually modifying just a piece of the original firmware. Here's how i confirmed:
From the original Mojave update file, you had extracted your MBP firmware right? In my case, the firmeware was MBP112.SCAP file.
Using this article as a guide: https://www.modmy.com/how-mount-your-efi-partition-macos
I copied the firmware onto my desktop and compared the two.
Edit 3: See the attached screenshoot. The left shows the original firmware for my MBP 15, 2013 A1398. The guide provided by CMD+Q (Click on most liked posts) told me what firmware to use.
The right shows the firmware currently sitting on my EFI volume with the updated driver from the 2015 version.
For anyone wanting to try this, please note that I mentioned earlier that I had the original ssd in the macbook when i updated my firmware manually.
Could someone please try this out with a non apple ssd? My adapter is still being shipped so I can't try out yet. If it does work, I will try to replicate the steps and if needed, post a guide.
Edit 4: Re-uploaded screenshot and added modified plus 2015 version of the same nvme driver. I'm really confused why as to why an external device was needed now. Did I modify the right thing?
Attachments
Last edited: