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.
Hey guys, I ordered a drive for my daughter MBA 13" Early 2015, she currently has Mojave and Boot Rom shows 186.0.0.0.0

I know this thread is long, just quickly tell me if this Bootrom version is correct and supports NVM3 M.2 drive.
Ordered the
Sabrent 512GB Rocket NVMe PCIe M.2 2280
186 will work with a nvme drive with Mojave. In fact, the Air will take a bootrom update with a nvme drive installed.
 
  • Like
Reactions: xantic
I have had a problem with my SX8200 Adata Pro 1 TB NVMe SSD in my 2015 13" MBP. Installed it about a year ago. Now I dropped my macbook (about 1 foot) while it was in a thin cover. When I tried to turn it on after a few hours: I get the folder with the quotation mark instead of the apple logo. No recovery mode available. I managed to get it working after trying to reboot several times, but the screen went blank after 1 minute.
I also had longer times of working, even 2 hours. But in the end always at some time the folder with the quotation mark (boot disk not found).

So I ended up installing a new SX8200 SSD, now everything works again like before. The fault of the old SSD could have been heat- or shockrelated. Using it now with an external USB enclosure as a huge USB Stick.

While installing the new SSD, I also replaced the thermal paste of the CPU and GPU with a thermal pad. It is an easy procedure, which is recommended after 1-3 years of use. Seems to run cooler since!
I used the smallest Carbonaut pad and cut it - video how replace thermal paste can be found on youtube!
 
  • Like
Reactions: vpujols
I have upgraded 4 early 2015 13" Airs with nvme drives and they all accepted the Catalina bootroom updates during a clean or upgrade install from the latest Mojave bootrom.
Which NVME drives did you upgrade them with? I wonder if my suspicions are correct that as long as the SSD Thermal Sensors respond that they will take a BootROM update.
Thanks!
 
Hey guys, I ordered a drive for my daughter MBA 13" Early 2015, she currently has Mojave and Boot Rom shows 186.0.0.0.0

I know this thread is long, just quickly tell me if this Bootrom version is correct and supports NVM3 M.2 drive.
Ordered the
Sabrent 512GB Rocket NVMe PCIe M.2 2280

I asked the same question a few posts earlier. My 2013 MBA 13” is also running on Mojave. Apparently the number we see in our computer is a new format. The one mentioned in the first (wiki) post is an old format. As such, I deduce that any number in the new format will always be newer/later than that shown in the first wiki page. So it should be able to support NVMe drive.

P/S: I’ve also just ordered SX8200 Pro. Will update once I get it and the Sintech adapter.
 
P/S: I’ve also just ordered SX8200 Pro.

That and the Sabrent were my 2 contenders but decided to go with the Sabrent based on the charts published on first page. Good luck.

My sintech short adapter is finally coming home today after like 3 weeks..!!!!
 
  • Like
Reactions: Audit13
Which NVME drives did you upgrade them with? I wonder if my suspicions are correct that as long as the SSD Thermal Sensors respond that they will take a BootROM update.
Thanks!
I have used Intel 600p, Intel 760p, HP ex900, and Lexar nm600. These are all low-end drives with the exception of the 760p and have worked flawlessly with Mojave and Catalina.
 
  • Like
Reactions: xantic
Guys, help me with suggestions please
I've collected some candidates for 2015 machine:
Transcend 110s (TS1TMTE110S)

Crucial P1 (CT500P1SSD8)
WD Blue SN550 (WDS100T2B0C)
Silicon Power P34A80 (SP512GBP34A80M28)

As you might guess, despite demanding tasks, I seek for power-optimized solution.
The problem is - only the first one is listed in @gilles_polysoft 's test chart. I wouldn't mind it much if it wasn't pretty different from AnandTech rating, another one I use. I can't really compare those two. Maybe something is related to power management and power modes Macs use, I don't know, but digits differ (660p for instance)

I don't really want to mess with dram-less QLC and lean towards WD, but there's so little info...
Which one of those would you suggest?
 
OK, if anyone has any ideas, this is the result of opening console just after my machine got out of a hang. This happens several times per day, sometimes several times per hour, depending on usage. It only seems to happen with my 3rd party ssd. Any thoughts?
...
fault 14:17:32.996516-0500 kernel IntelAccelerator previous NotReady transaction [ID=4576364, IOSurfaceID=24] sent. kr=0x0

same behavior here on my MBP (a1502) running Catalina; been thinking that my decision to replace my keyboard, resulting in upgrading to an i7 3.1GHz and replacing batteries, might have been a mistake...G-Drive Mobile ext has been randomly ejecting though...not sure what's going on, but my console shows similar Intel Accelerator errors. for me though, heavy browser demands seem to lag the whole system (cursor jumps), fighting the cursor lag usually ends with crash to shutdown state...
 
So i haven't found anything particulary useful about my situation regarding Windows 10 on a 2014 rmbp w upgraded ssd from a 2015 rmbp (SSUBX). If you are having problems installing/running Windows 7/8/10 (any build) then know that you are not alone. :) [yes i've used the forum search, google and various other engines]

To be a little more exact:

I have a 2014 13" retina macbook pro - it came with SDNEP (Marvell controller, 2x pciex) 128GB drive.
I dont want to mess with firmware (i use the sleep feature constatly) so i've chosen to upgrade to a genuine Apple ssd - Samsung SSUBX 512GB. Everything went well, macos cloned just fine, speeds were as i'we expected...
...Until one day i've decided to install Windows 10 via BootCamp Assistant - little did i know what a sh*tstorm i've released upon to myself.

First Try: Create USB Windows installer via Bootcamp assistant, boot from created usb drive -> Windows installer fails to start. (tried all builds from 150X - 1909, earlier builds tend to go further in the install process)
Second attempt: Same "bootcamping" as before but i've removed the ssd (the upgraded one) - whoilá the Windows installer starts perfectly but 'course there's nowhere to be installed - i think i got this "" idea from an apple support thread.
Third attempt: ok i realized that this problem has to do something w windows drivers, so i downloaded bootcamp drivers for 2015 rmbp - this gave some progress - i can install windows but after the installer reboots for the first time it stuck on "Setting up services/devices or Please wait w circle animation"
Fourth attempt: Try install windows2go on a pc box - it ran fine on my rmbp w installed ssubx until it didn't. - "Please wait" on windows start screen.
Fifth attempt: Installed windows on an external usb ssd w a neat trick involving using virtualbox for starting the windows install but cut it before the first reboot on install. - This also works - for some time, same as before.

So beware that if you try to install an ssd from a 2015 machine in a 2013-2014 macbook pro it could "cripple" your machine somewhat. (running windows natively)
Yes, I can confirm this on an Air 2013 and on an Air 2014. Tried also everything. SSD is an OEM Apple SSD 512 SSUBX. Windows installation stops at the spinning circle.

Note: Windows/Bootcamp installation runs successfully through on my original stock Air 128 GB SSD's, both SSUAX (Samsung and Sandisk).
I created an image from this bootcamp Partition and recovered it to the 512 SSUBX. It works, but when I boot into Windows, the whole system stuck. Mouse is jerking and jumping. Startmenue not accessible, nothing.

- Recovering the Bootcamp Partition (and Win 10 itself) also works flawlessly on the original stock Air 128 GB SSD's. -

It seems, running Windows on 2013/2014 machines with upgraded Apple SSUBX SSD's is not possible.
Btw, OS X is running perfectly on this 512 SSUBX SSD.

Has anybody tried Windows/Bootcamp installation on 2013/2014 MacBook Airs with an 256 or 512 GB SSUAX SSD?
 
Last edited:
Yes, I can confirm this on an Air 2013 and on an Air 2014. Tried also everything. SSD is an OEM Apple SSD 512 SSUBX. Windows installation stops at the spinning circle.

Note: Windows/Bootcamp installation runs successfully through on my original stock Air 128 GB SSD's, both SSUAX (Samsung and Sandisk).
I created an image from this bootcamp Partition and recovered it to the 512 SSUBX. It works, but when I boot into Windows, the whole system stuck. Mouse is jerking and jumping. Startmenue not accessible, nothing.

- Recovering the Bootcamp Partition (and Win 10 itself) also works flawlessly on the original stock Air 128 GB SSD's. -

It seems, running Windows on 2013/2014 machines with upgraded Apple SSUBX SSD's is not possible.
Btw, OS X is running perfectly on this 512 SSUBX SSD.

Has anybody tried Windows/Bootcamp installation on 2013/2014 MacBook Airs with an 256 or 512 GB SSUAX SSD?
I ran into this exact problem and the only way I found to fix it was to find a donor motherboard from a 2015+ machine. Now no problems with boot camp on my 512 ssubx.
 
I ran into this exact problem and the only way I found to fix it was to find a donor motherboard from a 2015+ machine. Now no problems with boot camp on my 512 ssubx.
Does the 2015+ Logicboard fit into a 2014 case? I'm wondering if your newer Logicboard is compatible with the remaining 2014 electronic.
 
Last edited:
Guys, help me with suggestions please
I've collected some candidates for 2015 machine:
Transcend 110s (TS1TMTE110S)

Crucial P1 (CT500P1SSD8)
WD Blue SN550 (WDS100T2B0C)
Silicon Power P34A80 (SP512GBP34A80M28)

As you might guess, despite demanding tasks, I seek for power-optimized solution.
The problem is - only the first one is listed in @gilles_polysoft 's test chart. I wouldn't mind it much if it wasn't pretty different from AnandTech rating, another one I use. I can't really compare those two. Maybe something is related to power management and power modes Macs use, I don't know, but digits differ (660p for instance)

Hi,

There is not only the Transcend 110s but also the WD Blue SN550 in the charts (it has been added recently)
As for the Crucial P1 it will have numbers similars to the Intel 660p
As for the Silicon Power, it will behave similarly to other Phison E12 / Toshiba TLC drives listed in the chard

The numbers in the charts differs from AnandTech tests because the condition differs :
- they are made on a PCIe 2.0 Mac (not on a PCIe 3.0 windows machine)
- only 500-512GB capacity drives are tested in order to be able to compare similar drives (1TB drive will have better write performances)
- read and write tests I made are only a long 100GB read and write test, which has been choosed because I can precisely measure power consumption during this test

As for your choice, I would prefer the Silicon Power P34A80 which is based on a Phison E12 controller with Toshiba TLC nand, all of which shows the best performance / price and also the best performance / consomption both in the charts and in real world.
 
Hi,

There is not only the Transcend 110s but also the WD Blue SN550 in the charts (it has been added recently)
As for the Crucial P1 it will have numbers similars to the Intel 660p
As for the Silicon Power, it will behave similarly to other Phison E12 / Toshiba TLC drives listed in the chard

The numbers in the charts differs from AnandTech tests because the condition differs :
- they are made on a PCIe 2.0 Mac (not on a PCIe 3.0 windows machine)
- only 500-512GB capacity drives are tested in order to be able to compare similar drives (1TB drive will have better write performances)
- read and write tests I made are only a long 100GB read and write test, which has been choosed because I can precisely measure power consumption during this test

As for your choice, I would prefer the Silicon Power P34A80 which is based on a Phison E12 controller with Toshiba TLC nand, all of which shows the best performance / price and also the best performance / consomption both in the charts and in real world.


Im also wondering about a power efficient drive for a Mid 2014 15" MBP.
Would the Kingston A2000 be a good choice possibly?
- Its 4 lanes so presumably faster than the a1000
- Kingston claim its idle power consumption to be .0032W Idle / .08W Avg which seems pretty competitive
- price seems pretty competitive...and its available locally in norway which saves me horrendous import fees.

i have no idea how manufacturers claimed power consumptions compare to those on @gilles_polysoft 's test chart.

Thoughts?
 
Im also wondering about a power efficient drive for a Mid 2014 15" MBP.
Would the Kingston A2000 be a good choice possibly?
- Its 4 lanes so presumably faster than the a1000
- Kingston claim its idle power consumption to be .0032W Idle / .08W Avg which seems pretty competitive
- price seems pretty competitive...and its available locally in norway which saves me horrendous import fees.

i have no idea how manufacturers claimed power consumptions compare to those on @gilles_polysoft 's test chart.

Thoughts?

Manufacturers power consumption claims do not apply to our case because it is not the intended use, and MBs do not/cannot use all available powerstates from third party nvme drives.
 
Hi!
I have a problem to make my cloned bootcamp partition bootable.

Very difficult to search within this thread, so...
I have MBP 15" mid 2015 (High Sierra 10.13) with Adata SX8200 Pro 512GB
I have an unknown adapter with NMVe text on it, it's not from sintech or any from the first page (I've ordered one from Sintech just in case, waiting)
Anyway, I've successfully cloned my OSX partition (typing from it) using CCC (Carbon Cloner) on a manually created APFS container+partition
I don't have any Apple SSD to USB or NVMe to USB adapters, so I had to use an intermediate external HDD + a bootable eternal SSD with High Sierra 10.13.6

Also I've added a FAT partition and restored it later from BOOTCAMP intermediate partition using Disk Utility
it copied all files but it's not bootable.
I've tried to fix it with Paragon hard disk manager (Correct Bootcamp boot record, etc.)
did not work

I couldn't find a working version of Winclone for 10.13, probably "Make EFI bootable" bootable could help

So for now I see only one solution to start a bootcamp from scratch which should make the partition bootable and then update it with a clone

If someone knows how to properly make it bootable or clone without starting from scratch please share that information

thank you

UPDATE/Solution

Answer to myself
I've managed to successfully clone my bootcamp with Winclone 7.0.1 pro (it works with High Sierra)

1. Restore your bootcamp partition with Disk Utility to manually created FAT partition on your new NVMe SSD (larger or the same size with your bootcamp, it automatically reduces the size of it, the rest part will be left as unallocated space you can add it later) One can use Paragon Hard Disk manager (HDM) for the same steps, I've used Disk Utility, just because I thought it would do it w/o any issues.

2. Open Winclone and Make EFI bootable for that new cloned bootcamp partition.

After this the partition becomes bootable, but restarts my MBP while spinning on the Windows Loading Screen

3. Open Paragon HDM, Correct Bootcamp boot record, Adjust Bootcamp to Dissimilar Hardware

Once done boot into windows, it will stop loading with the blue screen showing different options (one can load in safe mod fine, in my case the disk had allocation issues and I needed to fix them. Unfortunately in Safe mode right click is not available, so it was difficult to operate)
hence, restart back into mac os

4. Open Paragon HDM and check/fix file system integrity of the new bootcamp.

It will fix them if exist

Windows now can load.

5. One needs to create new virtual drive in Parallels for new bootcamp drive.

Solved.

P.S.
NO sleep/battery drain issues, closed the lid still 100% battery after night
One issue "AMD-Action:authenticate:SP" couldn't download blackmagic disk speed from the appstore.
Not sure thou if that problem didn't exist earlier
UPDATE
csrutil clear in recovery/terminal fixed the issue

so Adata SX8200 pro 512gb with unknown ($3) adapter

5GB stress file

adataSX8200pro512gb.jpg
 
Last edited:
I have a mid 2015 15 " MBP 11.4, running Catalina Beta with BOOTRom 197.0.0.0.0. It doesn't match the BootRom recommenced in the post. Can I use the M.2 NVMe upgrade
 
I have a mid 2015 15 " MBP 11.4, running Catalina Beta with BOOTRom 197.0.0.0.0. It doesn't match the BootRom recommenced in the post. Can I use the M.2 NVMe upgrade
For your MPB Boot rom version should be higher or the same as MBP114.0177.B00 (old format)
my mid 2015 15" has that version running High Sierra 10.13
You have a higher/updated version (197.0.0.0/new format)
So yeah, should be fine with NVMe
 
So do I understand things right?...
I have a mid 2014 (11.3) MacBook Pro 15” currently running Catalina 10.15.3 on the original apple 256Gb. Boot ROM 158.0.0.0.0

I’m considering the Kingston A2000 or sabrent Rocket 1Tb with long sintech adapter (as recently recommended to me by sintech).

I will have problems waking from hibernation unless hibernation value is set to 0 in terminal. But will the laptop still wake from sleep as normal - like if I close the lid for 10 min and open it again?battery will drop ~10% over night due to no hibernation mode and battery may drain faster under use due to faster and hotter ssd, otherwise things “should” work pretty much as normal?

And a Matt card can be installed to negate the hibernation issue correct?

...I mean theoretically speaking...is this close to a realistic summary?
 
Just upgraded my MBPr 13" early 2015 with short Sintech and Samsung 970 Evo 500GB.
Installed Catalina and some necessary soft.
Thats great!
Thanks all for nice topic!
 

Attachments

  • DiskSpeedTest3.png
    DiskSpeedTest3.png
    226.1 KB · Views: 338
NVMeFix v1.0.2 (no build available yet, has to be built manually) should fix random timeout panics on certain controllers (e.g. Samsung PM981).
 
I have a mid 2015 15 " MBP 11.4, running Catalina Beta with BOOTRom 197.0.0.0.0. It doesn't match the BootRom recommenced in the post. Can I use the M.2 NVMe upgrade
That's odd. Your BootROM actually looks like it matches an old iMac, not a Macbook Pro. On the tables, it's listed as iMac 14,4. Mine is a 2015, and I'm running Catalina. I have 196.0.0.0.0
 
NVMeFix v1.0.2 (no build available yet, has to be built manually) should fix random timeout panics on certain controllers (e.g. Samsung PM981).

I tried the first version and could’t get it to work. How did you do it?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.