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

[Biochem-anon]

Model: MacBookPro11,1
System Firmware Version: 430.0.0.0.0
System Version: macOS 11.2 (20D64)
SSD: Samsung SSD 970 EVO Plus 500GB

The latest versions of both Ssdpmenabler and NVMeFix individually cause my computer to crash during startup. How do I get the log files needed for the developers to fix the problems?

 

[Nandmp]

I have upgraded from Catalina to Big Sur and now I am unable to boot with any unsigned kext loaded. On Catalina I could boot with Lilu and NVMefix installed.
Does anyone else has this Problem?
I have a late 2013 retina MacBook and a 1tb crucial p2

Nermind, forgot i need to:
nvram boot-args="keepsyms=1"
on big Sur.
At least Lily and NVMefix are working again. SsdPmEnabler still not possible; Maybe trying the opencore method next...

 

[BitMac]

I'd like to report that SsdPmEnabler did not work with my MBA Mid 2013. Tried it with both Adata SX8200 Pro 512GB and Sabrent Rocket Q 2TB (RKT30Q.1) resulting in boot error loop running on Big Sur 11.1 with the exception of Lilu and NVMEfix.

I've got the same setup (except mine is a SX8200 Pro 1TB) and unable to load SSdPmEnabler with the same boot error loop (Mojave 10.14.6).
I'll try to install Lilu & NVMEfix only. Did that install work for you? Any change in battery life?

 

[MauriceG]

Hi guys,

I have two problems after the upgrade of my macbook.. changed the original ssd with the new Sabrent ssd (MBP Retina late 2013).

1). I get the error VDH002 when I use the diagnostic (Power on +D) (Like the comment here attached below)


2). When I power on my macbook I get 20/30 seconds of black screen before the apple logo appears.
(Like the comment here attached below)



Did anyone solved these problems?

Thanks in advance guys!

2) same issue with mbp 12.1. Cold boot takes a very long time wih Big Sur and Intel 660p. I gave up on analyzing the logs (several errors during Boot/start). After start everything works fine. Blackmagic readings ok etc. Cold start takes more than 2 minutes.

 

[man1sshhh]

I've got the same setup (except mine is a SX8200 Pro 1TB) and unable to load SSdPmEnabler with the same boot error loop (Mojave 10.14.6).
I'll try to install Lilu & NVMEfix only. Did that install work for you? Any change in battery life?

None with Adata SX8200 Pro. It gave me the same idle power consumption when plugged in. Seeing that I decided to move on to Sabrent Rocket Q; which did fell down to 0.11A from ~ 0.18A. You could try and go through few discharge cycles on the Adata and see if there's any noticeable difference.

 

[patdavenpo]

Hi All,

I'm trying to upgrade an MBP (early 2015, Big Sur) with the Crucial P2 SSD, and am getting stuck when installing Big Sur on the SSD using an external enclosure. First, I reformat the SSD as APFS (GUID Partition Map), then select that drive as the destination for install. At the end of the install, during the first prompted reboot, I get an error icon and the message "support.apple.com/mac/startup".

SOLVED: Big Sur install requires access to a "secure" wifi network. Created local hotspot with phone as a work-around.

Kind regards,
Pat

 

[startergo]

Using NFHK adapter with Samsung SSD 970 PRO 512GB in MacBookPro11,3 System Version: macOS 11.1 (20C69)
Using:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   48    2 0                  0x87000    0x87000    as.vit9696.Lilu (1.5.1) D60C2938-D19C-3211-A6D0-A6BA466B8A6F <8 6 5 3 2 1>
   49    0 0                  0xd000     0xd000     as.lvs1974.DebugEnhancer (1.0.3) 1E95F30C-CD13-3659-A39B-C33199B7C62D <48 8 6 5 3 2 1>
   50    0 0                  0xd000     0xd000     org.acidanthera.NVMeFix (1.0.5) B770910E-57A2-3513-8CF3-08709D7E6AA7 <48 8 6 5 3 2 1>
   51    0 0                  0x7000     0x7000     com.cdf.Innie (1.3.0) DAF7FB11-5303-3B26-BE94-45F4BB79D3CE <5 3>
   77    0 0                  0x8000     0x8000     com.ZLab.SsdPmEnabler (0.1.1) D54B8413-BEBE-310E-A320-2D413544D234 <14 5 3>
  160    0 0xffffff7fa2406000 0x2000     0x2000     com.evosx86.driver.lspcidrv (1.0) CE6EC87B-AAB5-9D7B-B249-4D986DEABED4 <5 3>

@kvic SSD Idling current shows 0.00A from 0.4A !

 

[kvic]

@kvic SSD Idling current shows 0.00A from 0.4A !

lol. So after all, MacBookPro11,3 is indeed vulnerable to the "0.00A" glitch?

Or did you mean you got it when connected to AC power..

I'd like to report that SsdPmEnabler did not work with my MBA Mid 2013. Tried it with both Adata SX8200 Pro 512GB and Sabrent Rocket Q 2TB (RKT30Q.1) resulting in boot error loop running on Big Sur 11.1 with the exception of Lilu and NVMEfix.

Based on members' feedback here so far, I think it's quite conclusive that MacBookPro11,1 and MacBookAir6,2 do not support lower power modes on 3rd-party NVMe SSDs. As I mentioned a few posts back, very likely Windows 10 will crash too.

I don't have the hardware to test but adventurous users with one/both hardware can explore in Windows 10 or even better Linux to see why that's the case. Perhaps you could figure out something.

 

[startergo]

Or did you mean you got it when connected to AC power..

Yes on AC power. I will update on battery.

 

[kvic]

Yes on AC power. I will update on battery.

AC power is good enough for me (I don't need the reading on battery).

This. Together with the ADATA SX8200 Pro below. Something I don't understand what's going on(*).

Nevertheless, sounds like great news for the respective SSD owners. Perhaps among the owners could cross check SSD firmware & etc..to figure out something.

It's the "1 Hour" scale and yes, it was on an AC adapter the entire time. I did the same test with a Sabrent Rocket 1TB on my other MBA7,2, but just realized it was stuck with an El Capitan Boot ROM. Once I get it up to date, I'll try again.

EDIT:

(*)
By that I meant Samsung 970 Pro (also 970 EVO) was reported with little effect as in the recent months:

• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29423997
• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29465782

Not sure if now both of them try out +NvmeFix will see better results or not. Ping @mlol adn @developeralioz

Also, ADATA SX8200 Pro is "notoriously" indifferent to NvmeFix. @fiftystorm's discovery is encouraging.

I recall @Stratus Fear reported seeing something similar on battery alone on his MacBookPro11,3 + ADATA SX8200 Pro. Not sure if he saw the same on AC. Back then in lack of details and on _battery_, I concluded he was stepping on the "0.00A" glitch.

With @fiftystorm's detailed report on AC power:

• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29543449

Perhaps it'll be a good idea for @Stratus Fear to come back with similar details on AC power. So that we could draw some sort of conclusion that it's norm (great news) for ADATA SX8200 Pro rather than one single instance of exception.

 

[stadya]

Just installed fresh copy of catalina using SN550 500gb,

Im trying to measure power wattage, what application should i use ?

Can you please share your thoughts, I'm planning to buy SN550 1tb but first, I'd like to know ssd speed and power consumption. I have MBP 13" 2015

 

[startergo]

AC power is good enough for me (I don't need the reading on battery).

I also run in through OpenCore. I don't know if that makes a difference, but just as a side note. OC has better driver (kexts) utilization.

 

[ramur]

Can you please share your thoughts, I'm planning to buy SN550 1tb but first, I'd like to know ssd speed and power consumption. I have MBP 13" 2015

Speed: I'm using Blackmagic Disk Speed Test. SSD is WD SN 550 1TB, Speed see below picture;

 

[Stratus Fear]

AC power is good enough for me (I don't need the reading on battery).

This. Together with the ADATA SX8200 Pro below. Something I don't understand what's going on(*).

Nevertheless, sounds like great news for the respective SSD owners. Perhaps among the owners could cross check SSD firmware & etc..to figure out something.



EDIT:

(*)
By that I meant Samsung 970 Pro (also 970 EVO) was reported with little effect as in the recent months:

• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29423997
• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29465782

Not sure if now both of them try out +NvmeFix will see better results or not. Ping @mlol adn @developeralioz

Also, ADATA SX8200 Pro is "notoriously" indifferent to NvmeFix. @fiftystorm's discovery is encouraging.

I recall @Stratus Fear reported seeing something similar on battery alone on his MacBookPro11,3 + ADATA SX8200 Pro. Not sure if he saw the same on AC. Back then in lack of details and on _battery_, I concluded he was stepping on the "0.00A" glitch.

With @fiftystorm's detailed report on AC power:

• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29543449

Perhaps it'll be a good idea for @Stratus Fear to come back with similar details on AC power. So that we could draw some sort of conclusion that it's norm (great news) for ADATA SX8200 Pro rather than one single instance of exception.

The behavior of my MBP with the SX8200 Pro is the same as @fiftystorm’s attached graph. However, I see the same power draw behavior in none/SsdPmEnabler/NVMeFix/SsdPmEnabler+NVMeFix regardless of power source.

What I have noticed about 0.00A readings, however, is that with my usual cadre of apps open, it’s pretty rare. If I close everything out to try and minimize disk access, 0.00A is logged much more frequently. Additionally, while it isn’t really evident from the detailed graph, it does seem some small, yet non-zero amount of current is being drawn when 0.00A is displayed. If I watch the sensor dropdown from the menu bar, and not drill down into the graph proper, the bar next to “SSD” does oscillate between showing a sliver of blue and then nothing while reading as 0.00A. I’ve also noticed roughly a 6°C drop in idle temperature of the SSD in this state vs not having any of the kexts installed at all, from 37°C on average to 31°C. Without Bjango updating iStat to show more precision in readings, it can’t really be fully proven what I’m seeing I suppose, but I’m not convinced it’s a glitch. (This is all again regardless of power source, I consistently see the same behavior plugged in)

Sorry for lack of graphs, I don’t have my laptop with me at time of writing.

 

[mork4]

Anyone noticed bootrom update with 11.2 release?

 

[macpro_mid2014]

Anyone noticed bootrom update with 11.2 release?

Yes.

MacBook Pro 15" mid-2014 Silicon Power 1Tb.

BootRom updated from 429.0.0.0 to 430.0.0.0

ALSO,

After downloading the update through System Preferences -> Software Update, the Macbook rebooted and installed the new BootRom. What a surprise when I logged back in to notice that I still had 11.1.
The macOS update to 11.2 installed only AFTER redownload all the 3.25 GB again.
I am NOT running any "power management" kext, though. No clue whether they still work or not.

Cheers,

 

[pacificoast]

Hey @MauriceG, I didn't see more exchanges your issue on the last two pages. If you had a 2013-2014 MacBookPro, I could offer one explanation: The SSD from the 2015 MBA would be a reason for unsuccessful firmware update attempts. I am not 100% confident on all the details, but the SSD that came with my MacBook11,1 is a Samsung-based PCIe AHCI SSD, and the SSDs in the 2015 models, like the MacBookAir7,2, is a Samsung-based PCIe NVMe SSD (Apple SSUBX?). Firmware upgrades will not work with an NVMe drive present if you are not past the 162.0.0.0.0 or so firmware revision on the MacBookPro11,1. Anyway, fingers crossed you can solve your issue!

Hi @Cmd+Q Thanks so much for your posts on how to update the MBP boot rom it work well after a couple of tweaks.

I have a MacBook Pro Retina 15" Late 2013 (MacBookPro11,3) running High Sierra and recently downloaded Big Sur and then followed your instructions. However, on first attempt nothing happened when trying to power up after applying your "sudo bless..." command. I thought I had bricked my MBP as I could not get the power come back on. However, after several panicked attempts of hitting the power button my MBP started back up but did not update the boot rom.

Then I noticed there is another firmware file named "MBP112.scap" so I used that filename in your command instead and everything worked like a charm. One thing I noticed was the start up sound had a lower tone when preparing to install the new firmware so you know then it's probably going to work. My firmware version now shows 429.0.0.0.0 slightly higher than the "MBP111.scap" 427.0.0.0.0 version.

Now on to installing my Crucial P2 1TB SSD... I had wanted to do it last weekend but didn't realize these MBPs needed a special Pentalobe P5 (aka PL4) screwdriver to open up the back cover. I now have my Wiha driver in hand thanks to Amazon's speedy delivery.

To Infinity, And Beyond!

 

[JR2006]

I have the mid-2015 15" MacBook Pro that came with th2 512GB Apple SSD. I just replaced it with the Crucial P2 2tb NVMe. I copied a CC clone of Big Sur to the new NVMe and updated to 11.2. Idle SSD was around .21A. I downloaded SsdPmEnabler and followed the instructions for installing the kext. The idle SSD power usage dropped down to .01 and bounces around as processes use the SSD. You can see the results in the attached picture. The kext was installed just before 5:29. That is excellent results which I hope continue to work with future updates.

 

[mlol]

By that I meant Samsung 970 Pro (also 970 EVO) was reported with little effect as in the recent months:

• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29423997
• https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29465782

Not sure if now both of them try out +NvmeFix will see better results or not. Ping @mlol adn @developeralioz

after last update with 430.0.0.0.0 BootROM I saw 50mA current. Thank you kvic for your work

 

[kvic]

Now I believe someone from Apple is reading this thread. lol

(Hi there. Hello~)

 

[fiftystorm]

I would love to hear success stories from MBA. Pls let me know if you run into any ssdpmEnabler issues.

I just did a test with SsdPmEnabler / NvMeFix on my other MacBook Air (13-inch, Early 2015, 2.2 GHz) with a Sabrent Rocket. No graph this time, sorry.

Setup:

Mojave 10.14.6 (18G7016)​

MacBookAir7,2​

Intel Core i7 2.2 GHz​

Boot ROM Version: 425.0.0.0.0​

Sabrent Rocket 1TB + Sintech short adapter​

AC Power Adapter connected​

iStat indicated the following for idle power draw.

None - 0.17 A​

NvMeFix - 0.12 A​

SsdPmEnabler - 0.07 A​

NvMeFix + SsdPmEnabler - 0.02 A​

 

[Biochem-anon]

lol. So after all, MacBookPro11,3 is indeed vulnerable to the "0.00A" glitch?

Or did you mean you got it when connected to AC power..



Based on members' feedback here so far, I think it's quite conclusive that MacBookPro11,1 and MacBookAir6,2 do not support lower power modes on 3rd-party NVMe SSDs. As I mentioned a few posts back, very likely Windows 10 will crash too.

I don't have the hardware to test but adventurous users with one/both hardware can explore in Windows 10 or even better Linux to see why that's the case. Perhaps you could figure out something.

I have a MacBookPro11,1 and have had the problem with the power management kexts leading to crashing. Do you think that it might be the same underlying issue leading to this under Windows 10: https://answers.microsoft.com/en-us...-3989-4d8b-9926-2633673b78ed?tm=1612258078907

EDIT: Does macOS transition non-Apple SSDs to the L0S power state with the included NVMe drivers? If not, then maybe we could use the power management kexts to do that, which would at least be better than L0, even if it is not as good as L1. For reference, L0S is referred to as a moderate power savings, L1 as maximum power savings, and L0 as disabled link power state management under the power plan in Windows. The default balanced power plan uses L0S while plugged in and L1 on battery power.

 

[BoPl]

For MacBook Pro 13" mid 2014 users - I just updated my to Big Sur 11.2 with new Boot Rom 430.0.0.0.0 and tried to install the SsdPmEnabler kext again - No Luck!😢 The SsdPmEnabler still doesn't work on our MacBook Pro 11.1 model.

 

[MauriceG]

The behavior of my MBP with the SX8200 Pro is the same as @fiftystorm’s attached graph. However, I see the same power draw behavior in none/SsdPmEnabler/NVMeFix/SsdPmEnabler+NVMeFix regardless of power source.

What I have noticed about 0.00A readings, however, is that with my usual cadre of apps open, it’s pretty rare. If I close everything out to try and minimize disk access, 0.00A is logged much more frequently. Additionally, while it isn’t really evident from the detailed graph, it does seem some small, yet non-zero amount of current is being drawn when 0.00A is displayed. If I watch the sensor dropdown from the menu bar, and not drill down into the graph proper, the bar next to “SSD” does oscillate between showing a sliver of blue and then nothing while reading as 0.00A. I’ve also noticed roughly a 6°C drop in idle temperature of the SSD in this state vs not having any of the kexts installed at all, from 37°C on average to 31°C. Without Bjango updating iStat to show more precision in readings, it can’t really be fully proven what I’m seeing I suppose, but I’m not convinced it’s a glitch. (This is all again regardless of power source, I consistently see the same behavior plugged in)

Sorry for lack of graphs, I don’t have my laptop with me at time of writing.

I agree, you might be right. I assume that iStat menus simply cuts off the less significant digits. So 9mA would be displayed as 0.00A (and not rounded to 0.01A). Intel specifies max. 9 mA for Idle (660p). IStat reports 0.00A on battery and 0.17A on power adapter. You could argue that it’s wishfull thinking... But it could also be correct. No kext files, Big Sur, latest boot rom.

 

[MauriceG]

Hi @Cmd+Q Thanks so much for your posts on how to update the MBP boot rom it work well after a couple of tweaks.

I have a MacBook Pro Retina 15" Late 2013 (MacBookPro11,3) running High Sierra and recently downloaded Big Sur and then followed your instructions. However, on first attempt nothing happened when trying to power up after applying your "sudo bless..." command. I thought I had bricked my MBP as I could not get the power come back on. However, after several panicked attempts of hitting the power button my MBP started back up but did not update the boot rom.

Then I noticed there is another firmware file named "MBP112.scap" so I used that filename in your command instead and everything worked like a charm. One thing I noticed was the start up sound had a lower tone when preparing to install the new firmware so you know then it's probably going to work. My firmware version now shows 429.0.0.0.0 slightly higher than the "MBP111.scap" 427.0.0.0.0 version.

Now on to installing my Crucial P2 1TB SSD... I had wanted to do it last weekend but didn't realize these MBPs needed a special Pentalobe P5 (aka PL4) screwdriver to open up the back cover. I now have my Wiha driver in hand thanks to Amazon's speedy delivery.

To Infinity, And Beyond!

If you have a 11,3 model, than you should have used a file with 113 in the name. It can have another extension. (You don’t mention the first file that you used). But it works, 👍🏼