Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe

[dimickh]

Hey guys, I'm looking to upgrade SSD on my 2015 MacBook 13.
I googled a bit and it seems that macOS doesn't support the Autonomous Power State Transition or APST for the NVME drives. This is the feature that sends SSD controller into a deep-sleep state when it's not used, and it also seems to be affecting some power-saving CPU functions too.
According to some tests done by AnandTech ( https://www.anandtech.com/show/13759/comparing-adata-sx8200-pro-vs-hp-ex950/9 ), the difference between power-saving mode(lpm enabled) and without it is quite substantial:

Has anybody done a battery life comparison with stock apple ssd vs nvme drive ?
Since battery drain in a sleep mode could be easily fixed by enabling hibernation I'm mostly interested in how it affects runtime in regular usage tasks like web-surfing or movies playing.
Thanks.

 

[a-maxime]

Yes, You need only your efi-backup from your laptop ("I have to make a backup of current rom with the programmer chip?") and the MBP114.fd from Firmware.pkg. Insert patch from MBP114.fd to your backup.

p.s. Please save original efi-backup to safe place =)


p.s. I add patch from FirmwareUpdate.pkg (MBP114.fd) to this message. Please add patch to your efi-backup (unzip first). p.s. Please save original efi-backup to safe place =)
I'm not to be held in charge for the use of this software with illicit aims or broken your hardware.

Instruction for future. This post contain instruction and say next:
https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-65#post-26224320

"

1. macOS Installation Media
   • The installation media contains the 2015 MacBook donor firmware with the update NVMe driver
2. • Extract the system firmware update from macOS Installation Media
     • Mount the InstallESD.dmg on the installation media in the folder Contents/SharedSupport
       In the InstallESD.dmg image, locate the Packages/FirmwareUpdate.pkg package
       
       Open the FirmwareUpdate.pkg file with Pacifist or The Archive Browser and open the enclosed Scripts archive
       
       
       • Open the Scripts archive inside the Scripts archive
         • The Archive Browser automatically opens up these archives
   • Extract the appropriate firmware update from Tools/EFIPayloads in the Scripts archive for the 2015 MacBook equivalent of the 2013-2014 MacBook you are upgrading
     • The following file are included with macOS 10.13.5 “High Sierra” (10.14.6 actual)
       • MBP114_0183_B00.fd for the 2015 MacBook Pro (MBP114.fd actual for 10.14.6)

"

Oh thanks a lot, I didn't understand it before but macOs Installation Media includes EFI PayLoad for each type of Mac. I used MBP114.fd and I located GUID 51116915-C34B-4D8E-86DB-6A70F2E60DAA, then extracted the ffs file into my downloads folder where I've dowloaded yours. Just to be sure, I tried a MD5 checksum but couldn't find a match between both of them, is it normal ?

Spoiler: Specs Info

MacBook Pro 15" Late 2013 (11,2)
macOS Mojave 10.14.6 (18G87)
2 GHz Intel Core i7
8 Go 1600 MHz DDR3

 

[applesed]

Quick question, for a late 2013 macbook pro 15, is there any options better than the OWC Aura Pro X2? (Please mention if your suggestion includes any adapter) Thanks.

 

[cyonix]

My idea was to get a ready-to-use-rom without a programmer chip. So I can send it to mattcard maker and he flash it to mattcard and send it to me. I would save money, cause I need only the mattcard with proper rom for 65€

Do you able to upload a mbp11,2/mbp11,3 156.0.0.0.0 rom with added dxe nvme driver from MBP114.fd?

Yes, You need only your efi-backup from your laptop ("I have to make a backup of current rom with the programmer chip?") and the MBP114.fd from Firmware.pkg. Insert patch from MBP114.fd to your backup.

p.s. Please save original efi-backup to safe place =)


p.s. I add patch from FirmwareUpdate.pkg (MBP114.fd) to this message. Please add patch to your efi-backup (unzip first). p.s. Please save original efi-backup to safe place =)
I'm not to be held in charge for the use of this software with illicit aims or broken your hardware.

Instruction for future. This post contain instruction and say next:
https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-65#post-26224320

"

1. macOS Installation Media
   • The installation media contains the 2015 MacBook donor firmware with the update NVMe driver
2. • Extract the system firmware update from macOS Installation Media
     • Mount the InstallESD.dmg on the installation media in the folder Contents/SharedSupport
       In the InstallESD.dmg image, locate the Packages/FirmwareUpdate.pkg package
       
       Open the FirmwareUpdate.pkg file with Pacifist or The Archive Browser and open the enclosed Scripts archive
       
       
       • Open the Scripts archive inside the Scripts archive
         • The Archive Browser automatically opens up these archives
   • Extract the appropriate firmware update from Tools/EFIPayloads in the Scripts archive for the 2015 MacBook equivalent of the 2013-2014 MacBook you are upgrading
     • The following file are included with macOS 10.13.5 “High Sierra” (10.14.6 actual)
       • MBP114_0183_B00.fd for the 2015 MacBook Pro (MBP114.fd actual for 10.14.6)

"

 

[a-maxime]

My idea was to get a ready-to-use-rom without a programmer chip. So I can send it to mattcard maker and he flash it to mattcard and send it to me. I would save money, cause I need only the mattcard with proper rom for 65€

Do you able to upload a mbp11,2/mbp11,3 156.0.0.0.0 rom with added dxe nvme driver from MBP114.fd?

I think that the BootROM dump include many private information such as serial number etc, so no one would be able to provide this imo

 

[DmitryZ]

Just to be sure, I tried a MD5 checksum but couldn't find a match between both of them, is it normal ?

I implement this patch to my efi-backup - hibernation working perfectly. That's all. =)

Do you able to upload a mbp11,2/mbp11,3 156.0.0.0.0 rom with added dxe nvme driver from MBP114.fd?

No, i think it's bad idea. You need flashing your backup from your laptop with patch from MBP114, cause backup contain your serial number and other system information from your laptop.

 

[jackqueenking]

Hey guys, I'm looking to upgrade SSD on my 2015 MacBook 13.
I googled a bit and it seems that macOS doesn't support the Autonomous Power State Transition or APST for the NVME drives. This is the feature that sends SSD controller into a deep-sleep state when it's not used, and it also seems to be affecting some power-saving CPU functions too.
According to some tests done by AnandTech ( https://www.anandtech.com/show/13759/comparing-adata-sx8200-pro-vs-hp-ex950/9 ), the difference between power-saving mode(lpm enabled) and without it is quite substantial:

Has anybody done a battery life comparison with stock apple ssd vs nvme drive ?
Since battery drain in a sleep mode could be easily fixed by enabling hibernation I'm mostly interested in how it affects runtime in regular usage tasks like web-surfing or movies playing.
Thanks.

Depending on the health of your battery you could lose up to 30% with an NVME drive. macOS doesn't support PCI-e active state power management or at least you can't enable it for third party drives. Apple designs the laptops where all components are low in power usage and probably implement their own power protocols especially since nowadays the ssds are soldered samsung/toshiba must design them in such a way that they allows the macbooks to live up to the minimum specifications provided by apple.

The other thing to note is its not only the NVME drive that will consume more battery, the drive itself is faster and thus the CPU utilization/frequency also increases to attempt to keep up with drive which in turn consumes battery even if its in shorter bursts. Newer CPUs don't suffer as much from this because they are more efficient.

 

[tiagocoelho]

It's anyone selling their SPI to J6100 adapter in the UK? The only one I can find is $60 online, but I only need it to patch the driver, so it's quite expensive for something I'll only use once.

 

[jisakiel]

One doubt of mine. If on a mattcard with patched nvme - is there a sustainable way to keep the bootrom updated and nvme-patched? I.e. for further spectre fixes that might appear later on.

(if I understand correctly - dumping my current bootrom and patching it would get me stuck on that version forever, missing any subsequent updates unless I open up the laptop, remove the nvme, remove the mattcard and let the original drive update, then redo everything again... a bit of a messy process, to be honest).

Bonus points if it was doable (updating the mattcard) without opening up the macbook and unplugging the mattcard (and reclipping it etc etc), by the way.

 

[gingerdude]

One doubt of mine. If on a mattcard with patched nvme - is there a sustainable way to keep the bootrom updated and nvme-patched? I.e. for further spectre fixes that might appear later on.

(if I understand correctly - dumping my current bootrom and patching it would get me stuck on that version forever, missing any subsequent updates unless I open up the laptop, remove the nvme, remove the mattcard and let the original drive update, then redo everything again... a bit of a messy process, to be honest).

Bonus points if it was doable (updating the mattcard) without opening up the macbook and unplugging the mattcard (and reclipping it etc etc), by the way.

I do not believe so at this time.

Two problems:

1) Apple seems to prevent an update even with a signed ROM when the Apple drive isn't present, or at least one sufficiently close to the Apple original in some way we don't quite understand yet. You need this install to work because it will migrate your machine's specific data into the proper places in the updated ROM. If you just flashed a generic copy you would loose this information.

Maybe we could figure out what pieces of information are relevant and manually copy them over like we are doing with the NVMe driver portion to bypass this issue?

2) The software flash looks for a signed ROM and we can't sign the ROM without Apple's key. Physically connecting to the chip (either Matt card or directly to the board) bypasses this check and forces the firmware onto the chip. The chip itself doesn't care that the firmware is unsigned, that's the job of the flash software to check that.

If someone comes up with a software flasher that bypasses the hardware and signature checks it may be possible. I personally don't work with firmware, even though I am a developer, so I would have no idea where to start.
[doublepost=1567794552][/doublepost]I have a question:

For people with mid 2015 machines, when you hit the option key does your drive appear orange or grey?

How about the people who said their firmware updates fine with the aftermarket they chose (for example certain Samsung drives)?

I'm thinking the firmware has a list of drive identifiers that dictate which ones are considered "acceptable" internal drives, and these may show up grey versus orange. Maybe this is used to allow firmware updates. Perhaps we can modify that list, it it exists.

 

[IgorGIV]

Does anyone know if there are any problems with Intel 760p and hibernation/sleep mode and with bootcamp?

 

[MauriceG]

I want to upgrade my MBP 2015 13 inch with the New Kingston A2000 SSD.
I have read that it’s compatible. However, I cannot find any user experiences.
The reasons for selecting this model are:
- low price, good brand
- low power usage (for a TLC type)
- good performance
Could anybody please share his/her experience?

Please! Especially interested to learn about the power usage.

 

[taozhong]

I've upgrade my MBA 13" 2013mid with Crucial P1 1TB, however the write speed seems not as my expectations; I'm hoping it can runs around 1000MB/s because this SSD official speed for write is 1700MB/s (PCIe 3.0 x 4).

PS. My MBA shows PCIe 2.0 x 4

 

[erkoolio]

Hey,

I was reading and trying different ways to flash new bootrom while having the OWC Aura Pro X inside my mid-2014 MBP.
While did make some progress I was unable to flash or force the flash to my MBP.

I got to point where I was able to stage the flash and my current version of bootrom 149.000.000 was going to be updated with newer version 156.000.000 However the flash on the reboot was unsuccessful. Apparently there is only try when installing new bootrom and if it fails that's it. The bootrom update cannot be forced while 3rd party SSD is inside.

That got me thinking that could OWC (and possibly other manufacturers) somehow mask there SSD to match Apples SSD ids? I don't believe that it will check online if SSD has certain Guid while flashing the bootrom, I think this check is done inside the flashing process. Also in package there is folder "AppleSSDFirmware" that contains a list of dictionaries with headline Valid Firmware Revisions. I really don't know if this leads anywhere, I'm just frustrated that we are being left out of bootrom updates that may contain crucial security updates.

 

[gingerdude]

Hey,

I was reading and trying different ways to flash new bootrom while having the OWC Aura Pro X inside my mid-2014 MBP.
While did make some progress I was unable to flash or force the flash to my MBP.

I got to point where I was able to stage the flash and my current version of bootrom 149.000.000 was going to be updated with newer version 156.000.000 However the flash on the reboot was unsuccessful. Apparently there is only try when installing new bootrom and if it fails that's it. The bootrom update cannot be forced while 3rd party SSD is inside.

That got me thinking that could OWC (and possibly other manufacturers) somehow mask there SSD to match Apples SSD ids? I don't believe that it will check online if SSD has certain Guid while flashing the bootrom, I think this check is done inside the flashing process. Also in package there is folder "AppleSSDFirmware" that contains a list of dictionaries with headline Valid Firmware Revisions. I really don't know if this leads anywhere, I'm just frustrated that we are being left out of bootrom updates that may contain crucial security updates.

You may have partly answered my question from up above. I am trying to figure out if there is a valid list of SSDs somewhere that we might be able to hack and get it to work.

 

[erkoolio]

You may have partly answered my question from up above. I am trying to figure out if there is a valid list of SSDs somewhere that we might be able to hack and get it to work.

Could someone with original apple ssd post a photo their system report where we could see the SSD Guid? We could then look if that one shows up in the dictionary? Or better yet, I'll post the dictionary below and if someone with original SSD could look for _any_ similarities between that list and any SSD property that could get things moving.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Payloads</key>
<dict>
<key>Mac-BE088AF8C5EB4FA2_APPLE_SSD_SM0032L</key>
<array>
<string>Mac-BE088AF8C5EB4FA2_APPLE_SSD_SM0032L/Payloads.txt</string>
<string>Mac-BE088AF8C5EB4FA2_APPLE_SSD_SM0032L/DXZ77A0Q.BIN</string>
</array>
<key>Mac-77F17D7DA9285301_APPLE_SSD_SM0032L</key>
<array>
<string>Mac-77F17D7DA9285301_APPLE_SSD_SM0032L/Payloads.txt</string>
<string>Mac-77F17D7DA9285301_APPLE_SSD_SM0032L/DXZ67A0Q.BIN</string>
</array>
<key>Mac-4B682C642B45593E_APPLE_SSD_SM0032L</key>
<array>
<string>Mac-4B682C642B45593E_APPLE_SSD_SM0032L/Payloads.txt</string>
<string>Mac-4B682C642B45593E_APPLE_SSD_SM0032L/DXZ87A0Q.BIN</string>
</array>
</dict>
<key>Valid Firmware Revisions</key>
<dict>
<key>Mac-BE088AF8C5EB4FA2_APPLE_SSD_SM0032L</key>
<array>
<string>APPLE_SSD_SM0032L DXZ75A0Q</string>
</array>
<key>Mac-77F17D7DA9285301_APPLE_SSD_SM0032L</key>
<array>
<string>APPLE_SSD_SM0032L DXZ86A0Q</string>
</array>
<key>Mac-4B682C642B45593E_APPLE_SSD_SM0032L</key>
<array>
<string>APPLE_SSD_SM0032L DXZ85A0Q</string>
</array>
</dict>
</dict>
</plist>

Of course if these train of thought will lead to nowhere and someone in here already knows this, please reply or say something.

 

[pedrosimao]

Hello!
Two years ago @gilles_polysoft gave me a great help when my original SSD flash drive form apple failed and my efi rom was incompatible with nvme drives. He sent me one of his ssd drives to me and thanks to him I didn't loose too much time and money.
Since then I was never able to fix the reboot issue, when I reboot the system doesnt see my drive, Only when I shutdown and turn on again. So now I decided to do the EFI ROM mod.
I was searching online and found this (kind of expensive) adapter for the CH341A programmer:
https://www.ebay.com/itm/323438231470

Considering it costs 50 bucks, I wonder if any of you know a cheaper or DIY version?
Anyone? Thanks a lot!

 

[markintosh13]

I have upgraded a 13" early 2015 MBP (i7, IG) with a short Sintek adapter and a 2TB Sabrent Rocket.

I have persistent wake issues - every morning, every evening after work, i more often than not experience a ? folder wake up followed by a kernel panic reset or sometimes what appears to be a normal wake up followed by a beach ball and a KP.

Super annoying

pmset data:
System-wide power settings:
Currently in use:
lidwake 1
autopoweroff 1
standbydelayhigh 86400
autopoweroffdelay 28800
proximitywake 0
standby 1
standbydelaylow 10800
ttyskeepawake 1
hibernatemode 3
powernap 1
gpuswitch 2
hibernatefile /var/vm/sleepimage
highstandbythreshold 50
displaysleep 10
sleep 10 (sleep prevented by sharingd)
acwake 0
halfdim 1
tcpkeepalive 1
disksleep 10

Any thoughts or suggestions?

 

[DmitryZ]

I have upgraded a 13" early 2015 MBP (i7, IG) with a short Sintek adapter and a 2TB Sabrent Rocket.

I have persistent wake issues - every morning, every evening after work, i more often than not experience a ? folder wake up followed by a kernel panic reset or sometimes what appears to be a normal wake up followed by a beach ball and a KP.

Need implement patch from MacBook 15 2015 to your efi chip.
Detail https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-65#post-26224320

 

[markintosh13]

Further to my last Kernal Panics post

Spoiler: Latest KP crash reporter log

Sat Sep 7 09:00:07 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f98dd5b30): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0x75 VID/DID=0x50121987
. FW Revision=ECFM12.2\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.270.1/IONVMeController.cpp:5334
Backtrace (CPU 0), Frame : Return Address
0xffffff92266b3a10 : 0xffffff8015bae6ed
0xffffff92266b3a60 : 0xffffff8015cea185
0xffffff92266b3aa0 : 0xffffff8015cdb8ba
0xffffff92266b3b10 : 0xffffff8015b5bb40
0xffffff92266b3b30 : 0xffffff8015bae107
0xffffff92266b3c50 : 0xffffff8015badf53
0xffffff92266b3cc0 : 0xffffff7f98dd5b30
0xffffff92266b3e20 : 0xffffff801625f387
0xffffff92266b3e90 : 0xffffff801625f2a9
0xffffff92266b3ec0 : 0xffffff8015bed885
0xffffff92266b3f40 : 0xffffff8015bed425
0xffffff92266b3fa0 : 0xffffff8015b5b0ce
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[A67B3600-6FE3-3037-AC41-8C2D353B6250]@0xffffff7f98dc8000->0xffffff7f98e07fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[1D716047-7F62-3FFA-8C01-26C166B3739A]@0xffffff7f96988000
dependency: com.apple.iokit.IOPCIFamily(2.9)[BFDEB8D4-50FE-3DDB-87B7-F6A504393830]@0xffffff7f96495000
dependency: com.apple.driver.AppleEFINVRAM(2.1)[B83F29B8-24AC-303B-BBBA-CF332168FDE6]@0xffffff7f96b5e000
dependency: com.apple.iokit.IOStorageFamily(2.1)[71BB22B0-3075-35A1-B04E-FBAC574DA80D]@0xffffff7f9677e000
dependency: com.apple.iokit.IOReportFamily(47)[0BC9F93B-456A-3D97-BE4C-69DCBB5E8A3C]@0xffffff7f970a2000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18G95

Kernel version:
Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64
Kernel UUID: C41337A1-0EC3-3896-A954-A1F85E849D53
Kernel slide: 0x0000000015800000
Kernel text base: 0xffffff8015a00000
__HIB text base: 0xffffff8015900000
System model name: MacBookPro12,1 (Mac-E43C1C25D4880AD6)

System uptime in nanoseconds: 21680220485873
last loaded kext at 19120865666865: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f99440000, size 32768)
last unloaded kext at 19183718076115: com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2 (addr 0xffffff7f9935c000, size 28672)
loaded kexts:
com.apple.filesystems.afpfs 11.1
com.apple.nke.asp-tcp 8.0.2
com.apple.filesystems.smbfs 3.3.2
com.apple.driver.AudioAUUC 1.70
com.apple.fileutil 20.036.15
com.apple.filesystems.autofs 3.0
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.ApplePlatformEnabler 2.7.0d0
com.apple.driver.AGPM 110.25.11
com.apple.driver.AppleUpstreamUserClient 3.6.5
com.apple.driver.AppleGraphicsDevicePolicy 3.50.12
com.apple.AGDCPluginDisplayMetrics 3.50.12
com.apple.driver.AppleHDA 282.54
com.apple.driver.AppleHV 1
com.apple.driver.AppleCameraInterface 6.8.0
com.apple.driver.eficheck 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.iokit.IOBluetoothSerialManager 6.0.14d3
com.apple.driver.pmtelemetry 1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleBacklight 170.12.12
com.apple.driver.AppleMCCSControl 1.5.9
com.apple.iokit.BroadcomBluetooth20703USBTransport 6.0.14d3
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleSMCLMU 212
com.apple.driver.AppleLPC 3.1
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleThunderboltIP 3.1.2
com.apple.driver.AppleIntelBDWGraphics 12.1.0
com.apple.driver.AppleIntelBDWGraphicsFramebuffer 12.1.0
com.apple.driver.AppleUSBCardReader 456.260.3
com.apple.driver.AppleVirtIO 2.1.3
com.apple.filesystems.hfs.kext 407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleSystemPolicy 1.0
com.apple.driver.AppleTopCaseHIDEventDriver 138.4
com.apple.filesystems.apfs 945.275.7
com.apple.driver.AirPort.BrcmNIC 1400.1.1
com.apple.private.KextAudit 1.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 6.1
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 6.1
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 201
com.apple.security.TMSafetyNet 8
com.apple.security.SecureRemotePassword 1.0
com.apple.kext.triggers 1.0
com.apple.driver.AppleGraphicsControl 3.50.12
com.apple.driver.DspFuncLib 282.54
com.apple.kext.OSvKernDSPLib 528
com.apple.iokit.IOAVBFamily 760.6
com.apple.plugin.IOgPTPPlugin 740.2
com.apple.iokit.IOEthernetAVBController 1.1.0
com.apple.iokit.IOSkywalkFamily 1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSSE 1.0
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.driver.AppleSMBusController 1.0.18d1
com.apple.driver.AppleHDAController 282.54
com.apple.iokit.IOHDAFamily 282.54
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.14d3
com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.14d3
com.apple.iokit.IOBluetoothHostControllerTransport 6.0.14d3
com.apple.driver.IOPlatformPluginFamily 6.0.0d8
com.apple.AppleGPUWrangler 3.50.12
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.iokit.IONDRVSupport 530.51
com.apple.AppleGraphicsDeviceControl 3.50.12
com.apple.iokit.IOAcceleratorFamily2 404.14
com.apple.iokit.IOGraphicsFamily 530.66
com.apple.iokit.IOSurface 255.6.1
com.apple.iokit.IOAudioFamily 206.5
com.apple.vecLib.kext 1.2.0
com.apple.driver.usb.networking 5.0.0
com.apple.iokit.IOSerialFamily 11
com.apple.filesystems.hfs.encodings.kext 1
com.apple.driver.AppleThunderboltDPInAdapter 5.6.9
com.apple.driver.AppleThunderboltDPAdapterFamily 5.6.9
com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.5
com.apple.driver.AppleActuatorDriver 2450.1
com.apple.driver.AppleHIDKeyboard 208
com.apple.driver.AppleHSBluetoothDriver 138.4
com.apple.driver.IOBluetoothHIDDriver 6.0.14d3
com.apple.iokit.IOBluetoothFamily 6.0.14d3
com.apple.driver.AppleMultitouchDriver 2450.1
com.apple.driver.AppleInputDeviceSupport 2440.2
com.apple.driver.AppleHSSPIHIDDriver 55.1
com.apple.iokit.IONVMeFamily 2.1.0
com.apple.driver.AppleThunderboltNHI 4.7.9
com.apple.iokit.IOThunderboltFamily 6.8.6
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.driver.corecapture 1.0.4
com.apple.driver.AppleHSSPISupport 55.1
com.apple.driver.AppleIntelLpssSpiController 3.0.60
com.apple.driver.AppleIntelLpssDmac 3.0.60
com.apple.driver.AppleIntelLpssGspi 3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI 1.2
com.apple.driver.usb.AppleUSBXHCI 1.2
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.iokit.IOUSBFamily 900.4.2
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.quarantine 3
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 493.0.0
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleUSBTDM 456.260.3
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.iokit.IOUSBMassStorageDriver 145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice 408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily 408.250.3
com.apple.iokit.IOStorageFamily 2.1
com.apple.kext.CoreTrust 1
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.iokit.IOUSBHostFamily 1.2
com.apple.driver.usb.AppleUSBCommon 1.0
com.apple.driver.AppleBusPowerController 1.0
com.apple.driver.AppleSEPManager 1.0.1
com.apple.driver.IOSlaveProcessor 1
com.apple.iokit.IOReportFamily 47
com.apple.iokit.IOTimeSyncFamily 740.2
com.apple.iokit.IONetworkingFamily 3.4
com.apple.driver.AppleACPIPlatform 6.1
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.Libm 1
com.apple.kec.corecrypto 1.0

EOF

[doublepost=1567862939][/doublepost]

Need implement patch from MacBook 15 2015 to your efi chip.
Detail https://forums.macrumors.com/thread...ssd-to-m-2-nvme.2034976/page-65#post-26224320

The MacBook in question is a 2015.

 

[maxthackray]

That moment you realise your post has over 5000 replies....

Huge thanks to the community! Hope people found the answers they were looking for

 

[erkoolio]

Hey,

came up with another idea. When I run the command in terminal to force update bootrom, it does not update it, it only stages it. I was wondering if that staged bootrom could be found and flashed with ch341 (and the logic board adapter)?
The questions that I have not been able to answer are that when the bootrom is staged, does it mean it is ready for flashing?
Or is there some other operations that will happen during the flashing that will handle the data transfer from the old bootrom to the new one?

 

[PLjelly]

MacBook Air 2013 (bought for 228$ without disk) with Adata SX6000 Pro. For my gf this speed is more than enough. I had a little bit problem to install Mac OS Mojave so I gave it to professional service and they done it for 20$.
Disk was also cheap because I bought it for 50$ so ended up with something about 300$ for perfect working MacBook Air 2013

 

[DyingStar]

Probably overkill at this point, but just confirming I put a 1TB Sabrent Rocket in a Mid 2014 MBP11,3 (15" 2.8) using the small Sintech Adapter purchased new on Amazon. The adapter came with tape applied already. Everything went off without a hitch!

Well, sort of. TLDR and questions at bottom.

I needed to stay on 10.13.6 due to my Hackintosh desktop that is not on Mojave and needing to swap Logic Pro X files of the same version between the two machines.

At first the drive and adapter did not appear to fit in the hard drive connector on the motherboard and kept popping back out. THIS MAY BE IMPORTANT FOR ALL 2014 15" MACBOOK PROS - I had to insert the drive and adapter at approximately a 30 degree upward angle and apply more force than I would have liked, at which point it plugged all the way in with an obvious clicking sound and the screw holes lined up.

At this point I discovered the Macbook had only had up to Yosemite (MacOS 10.10) installed on it. I had to order a 120GB OWC Aura drive (found one used for $20) just so I could get a newer BootRom flashed. I also had to insert the OWC drive at a 30 degree angle so either it's just my Macbook or everyone's going to have that problem.

I installed High Sierra 10.13.6 on the OWC drive, and then went ahead and upgraded to Mojave using the App Store as word on the street is that NVMe support is further improved on the newest Mojave BootRom and it is my understanding that installing an older MacOS on a machine will not overwrite a newer BootRom...right?

I then swapped the OWC drive for the Sabrent SSD, plugged my High Sierra install USB back in, and the Sabrent SSD popped right up. Formatted to AFPS, installed the OS, and was able to import all settings, apps, and files from my previously dead Macbook's still working SSD in about 2 hours.

I toyed with the idea of fixing the hibernation issue but last night I only lost 3% percent of my battery with the lid closed after using "sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0", and I used to lose 1-2% on my now dead Macbook Pro 15 Mid 2012. Other folks getting similar results of a negligible impact?

TLDR:
30 degree angle to get adapter plugged in
Install worked after BootRom updated past High Sierra

Questions:
Will "newer" versions of BootRom be overridden by downgrading OS?
Anyone else not seeing a huge difference with hibernation turned off?

 

[dimickh]

Depending on the health of your battery you could lose up to 30% with an NVME drive. macOS doesn't support PCI-e active state power management or at least you can't enable it for third party drives. Apple designs the laptops where all components are low in power usage and probably implement their own power protocols especially since nowadays the ssds are soldered samsung/toshiba must design them in such a way that they allows the macbooks to live up to the minimum specifications provided by apple.

The other thing to note is its not only the NVME drive that will consume more battery, the drive itself is faster and thus the CPU utilization/frequency also increases to attempt to keep up with drive which in turn consumes battery even if its in shorter bursts. Newer CPUs don't suffer as much from this because they are more efficient.

Can you post your personal battery life measurements? Of course, if you have the 2015 model. I searched a lot but still wasn't able to find an adequate comparison in battery life with replaced ssd. Consumption table found in this topic is useful but still doesn't represent the actual power consumption (according to it installing a MyDigitalSSD should give even better battery life than stock apple ssd, which is highly unlikely)

Also, I don't think that drive speeds affect battery life in any way, these speeds may be capped by CPU but this will just lead to longer waiting times for you as a user. I guess the better power efficiency with never CPUs is a merit of special nvme controller which is better-optimized for such workloads rather than improved manufacturing process(from 22nm -> 14 nm)