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

[gilles_polysoft]

Hi Guys,

I'd like to upgrade a MacBook Air (2013). Do you think that a samsung evo 960 / 950 pro is a good choice ?
Thank's

Samsung Evo 960 or Pro (960 too) are good devices, and they both work with High Sierra.
WD Black drives work too. We don't know yet for Intel P600.
Don't forget : High Sierra is still (for a few days) a beta. You ought to first install High Sierra on your actual AHCI SSD, then (only then) you can install the new Samsung NVMe SSD.
[doublepost=1506048207][/doublepost]

It can't be the case that all TLC SSDs are incompatible; Wouark's screenshot shows THNSN5256GPUK which is a Toshiba XG4 drive with TLC NAND (successor to justaviet's Toshiba XG3, which is MLC, faster, and which can actually be bought at retail as the OCZ RD400), and the WD Black drive that Gilles tested should also be SanDisk TLC with a Marvell controller.

Hello,

Yes that's true the WD Black is a TLCSSD with Sandisk chips and Marvell controller.
Note that I have also succesfully tested a 512 GB 960 Evo which is TLC, a 960 Pro which is MLC (which I gave to one of my employees and he is using it for over a week in a mid 2015 MacBook Pro retina 15"), and also made tests with a SM961 with no problem at all.

So TLC seems not to be at all the problem with PM961 drives. Both TLC and MLC drive work
I guess if PM961 don't work is because of a firmware problem.
I founded a little Carbon X1 gen3 and will get it in a few days... I'll try to do some firmware backup with the Lenovo exec... don't promise but I'll keep you informed.

Also, a few news...

I did further tests there :

• first I upgraded all my test systems (MBPr 13" late 2013, MBPr15" mid 2015, MBA 13" early 2015) to High Sierra "GM candidate" (build 17A362a) without any problem.
• also I tried unsuccessfully to boot those test machines on El Capitan (10.11.6) with both the NVMe driver of JimJ740-Macvidcards, and the nvme_patch from Rehabman. Both with no success (either forbidden logo or double kernel panic...).
• While booting from an external disk with El Capitan and "jimj740" NVMe drive, thought, I was able to mount and read the internal NVMe SSD (of course not in APFS...)
• same results with Sierra 10.12.6 : unable to boot with the nvme_patch from Rehabman.

I think what is missing here is that I don't use Clover...
Also, maybe nobody is interested in using El Capitan with NVMe drives... (other than Apple ones).
High Sierra works...

But... I did another experiment with the WD Black drive.
I read it was possible to format it with 4K sectors... so I did it.
I wrote a Xubuntu 17.04 distribution on a 8GB USB drive, I booted my MBPr 13" late 2013 on it (with NVMe WD black inside).

I installed smartmontools and nvme-cli :

sudo apt install smartmontools nvme-cli​

And I formatted the NVMe drive with 4K sectors :

nvme format -l 1 /dev/nvme0​

Well.. guess what : the WD drive now works natively on macOS Sierra (surprisingly not El capitan).
I was able to boot on a "vanilla" Sierra install and the installer did recognize the SSD and installation went flawlessly...

So that's interesting : with 4K capable drives we don't even need High Sierra...

​

 

[theitsage]

@gilles_polysoft Amazing work!

 

[maenpaa24]

Excuse me, but I wonder why you say that high sierra is still in beta. It sounds to me like if the final release could stop supporting the nvme drives. Could that happen?

Thank you.

Samsung Evo 960 or Pro (960 too) are good devices, and they both work with High Sierra.
WD Black drives work too. We don't know yet for Intel P600.
Don't forget : High Sierra is still (for a few days) a beta. You ought to first install High Sierra on your actual AHCI SSD, then (only then) you can install the new Samsung NVMe SSD.
[doublepost=1506048207][/doublepost]

Hello,

Yes that's true the WD Black is a TLCSSD with Sandisk chips and Marvell controller.
Note that I have also succesfully tested a 512 GB 960 Evo which is TLC, a 960 Pro which is MLC (which I gave to one of my employees and he is using it for over a week in a mid 2015 MacBook Pro retina 15"), and also made tests with a SM961 with no problem at all.

So TLC seems not to be at all the problem with PM961 drives. Both TLC and MLC drive work
I guess if PM961 don't work is because of a firmware problem.
I founded a little Carbon X1 gen3 and will get it in a few days... I'll try to do some firmware backup with the Lenovo exec... don't promise but I'll keep you informed.

Also, a few news...

I did further tests there :

• first I upgraded all my test systems (MBPr 13" late 2013, MBPr15" mid 2015, MBA 13" early 2015) to High Sierra "GM candidate" (build 17A362a) without any problem.
• also I tried unsuccessfully to boot those test machines on El Capitan (10.11.6) with both the NVMe driver of JimJ740-Macvidcards, and the nvme_patch from Rehabman. Both with no success (either forbidden logo or double kernel panic...).
• While booting from an external disk with El Capitan and "jimj740" NVMe drive, thought, I was able to mount and read the internal NVMe SSD (of course not in APFS...)
• same results with Sierra 10.12.6 : unable to boot with the nvme_patch from Rehabman.

I think what is missing here is that I don't use Clover...
Also, maybe nobody is interested in using El Capitan with NVMe drives... (other than Apple ones).
High Sierra works...

But... I did another experiment with the WD Black drive.
I read it was possible to format it with 4K sectors... so I did it.
I wrote a Xubuntu 17.04 distribution on a 8GB USB drive, I booted my MBPr 13" late 2013 on it (with NVMe WD black inside).

I installed smartmontools and nvme-cli :

sudo apt install smartmontools nvme-cli​

And I formatted the NVMe drive with 4K sectors :

nvme format -l 1 /dev/nvme0​

Well.. guess what : the WD drive now works natively on macOS Sierra (surprisingly not El capitan).
I was able to boot on a "vanilla" Sierra install and the installer did recognize the SSD and installation went flawlessly...

So that's interesting : with 4K capable drives we don't even need High Sierra...

​

 

[myst02]

Quick update from me:

Yesterday I received both the Intel 600p SSD and Adapter. I made a backup of everything, downloaded High Sierra GM, put the install files on an USB drive and upgraded to High Sierra on my original ssd.
Then I installed the intel ssd with the adapter and booted from the high sierra install usb. The ssd is not being recognized in disk utility.

So I thought, okay, it's not working because maybe intel ssds aren't supported. For testing, I took out my Samsung 960 evo from my desktop pc and tried using it in the mb with the adapter. Really weird thing is, it isn't being recognized either. Hasn't the 960 evo been tested successfully by someone here?

This is the adapter I'm using: https://www.amazon.de/gp/product/B01GHSE7Z2/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
Is my adapter broken or am I doing anything wrong? I also tried disabling SIP and using kapton tape on the adapter.

EDIT: Also tried booting from Ubuntu and windows, both do not recognize the drive. I noticed that the SSD gets warm when the Macbook is powered on, so it's running, just not recognized.

 

[imprimis1]

Quick update from me:

Yesterday I received both the Intel 600p SSD and Adapter. I made a backup of everything, downloaded High Sierra GM, put the install files on an USB drive and upgraded to High Sierra on my original ssd.
Then I installed the intel ssd with the adapter and booted from the high sierra install usb. The ssd is not being recognized in disk utility.

So I thought, okay, it's not working because maybe intel ssds aren't supported. For testing, I took out my Samsung 960 evo from my desktop pc and tried using it in the mb with the adapter. Really weird thing is, it isn't being recognized either. Hasn't the 960 evo been tested successfully by someone here?

This is the adapter I'm using: https://www.amazon.de/gp/product/B01GHSE7Z2/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
Is my adapter broken or am I doing anything wrong? I also tried disabling SIP and using kapton tape on the adapter.

EDIT: Also tried booting from Ubuntu and windows, both do not recognize the drive. I noticed that the SSD gets warm when the Macbook is powered on, so it's running, just not recognized.

Part of the situation appears to be 4KB vs 512B block formatting.

There are still unresolved concerns regarding the interaction between the SSD firmware (or firmware variant) and the model/year and EFI firmware of the MacBook. And also whether at least some TLC devices pose some additional compatibility issue.

It is my understanding, from perusing the hackintosh forums, that Hynix/Lite-On/Plextor and Intel devices may require the IONVMeFamily.kext to be patched via a hex editor, due to an Advanced detect feature for default block formatting size peculiar to devices from these manufacturers, even on High Sierra.

However, it may also be the case that your Intel 600p is incompatible due to firmware and/or TLC-NAND related issues, as well.

It's becoming clear at this moment that the number of compatible SSDs is a relatively limited class, and the bootrom and kext updates inherent to High Sierra (which merely allow the machine to recognize 512B block format SSD's by the hardware at initialization, and by the OS natively, and also recognize APFS partitions at boot/in the OS, as well), will not greatly expand the list of compatible drives.

I'd be curious to know whether re-formatting these devices with 4k block sectors from a PC m.2 AHCI/NVMe-compatible motherboard in Linux (where, presumably, they would be recognized) might alleviate some of these symptoms. Of course, not all of these devices permit 4k block formatting, but I believe all the ones under discussion at this stage of the thread do.

 

[myst02]

Part of the situation appears to be 4KB vs 512B block formatting.

There are still unresolved concerns regarding the interaction between the SSD firmware (or firmware variant) and the model/year and EFI firmware of the MacBook. And also whether at least some TLC devices pose some additional compatibility issue.

It is my understanding, from perusing the hackintosh forums, that Hynix/Lite-On/Plextor and Intel devices may require the IONVMeFamily.kext to be patched via a hex editor, due to an Advanced detect feature for default block formatting size peculiar to devices from these manufacturers, even on High Sierra.

However, it may also be the case that your Intel 600p is incompatible due to firmware or TLC-NAND related issues, as well.

It's becoming clear at this moment that the number of compatible SSDs is a relatively limited class, and the bootrom and kext updates inherent to High Sierra (which merely allow the machine to recognize 512B block format SSD's to be recognized by the hardware at initialization, and by the OS natively), will not greatly expand the list of compatible drives.

Yep, that's also what I thought, but why is my Samsung 960 Evo not being recognized with the adapter then too? It's MLC and has been tested by someone in this thread already. I'm wondering if I have a faulty adapter...

Or could it be possible that the adapter is not compatible to NVMe SSDs? It looks kinda the same as the Sintech one though.

Also did some research on the Intel 600p, people on tonymacx86 say it's natively supported.

 

[imprimis1]

Yep, that's also what I thought, but why is my Samsung 960 Evo not being recognized with the adapter then too? It's MLC and has been tested by someone in this thread already. I'm wondering if I have a faulty adapter...

Or could it be possible that the adapter is not compatible to NVMe SSDs? It looks kinda the same as the Sintech one though.

Also did some research on the Intel 600p, people on tonymacx86 say it's natively supported.

Some of these converter/adapters certainly do appear to have quality control issues.


960 Evo is TLC 3D-NAND, for sake of clarity. That may not be the issue, of course. And certainly a number of MLC-based devices seem to fail recognition.

 

[myst02]

Some of these converter/adapters certainly do appear to have quality control issues.


960 Evo is TLC 3D-NAND, for sake of clarity. That may not be the issue, of course. And certainly a number of MLC-based devices seem to fail recognition.

I'm probably going to return/exchange the adapter.

Another thing, you said that some SSDs need a patched kext file in order to work. But why not just patch that file? Or does that only work on Hackintosh?

 

[imprimis1]

I'm probably going to return/exchange the adapter.

Another thing, you said that some SSDs need a patched kext file in order to work. But why not just patch that file? Or does that only work on Hackintosh?

That is a question that remains to be fully tested. I tried to follow a RehabMan patch on Lite-On and Plextor NVMe MLC SSD's in multiple of my MacBooks, and it does not work (assuming that there were no errors in the suggested patch on my or RehabMan's sides). I did this with High Sierra. I haven't tried it on Sierra (10.12) with the patch suggested for that one (which may be better tested).

The drives are not acknowledged or recognized at the hardware level, it seems.

Caveat: There were different values suggested for the Sierra version of the patch (paraphrasing: "hardware-dependent, keep trying them until you find one that works"), that I didn't try on the High Sierra one (nor were they discussed in RehabMan's instructions for the 10.13 one).

-----

Installing High Sierra (virginally) updates the bootrom on the relevant Apple models to enable them to boot from 512B block-format SSDs and APFS partition schemes. And the OS itself now contains the appropriate kext's to recognize these natively at the software level. But apparently, there are other issues extending from the hardware level of some makes/models of SSD that these updates do not address, and for which no trivial solution exists.

The information from the hackintosh forums can only be partially useful in these pursuits on actual Apple equipment (mainly valuable at the OS level, less so for hardware-level issues). The PC motherboard (circuitry-level/PCH) and UEFI implementations are likely to be far more forgiving than what these Late 2013-2015 MBP / 2013-2017 MBA portables tolerate.

My speculative/inconclusive belief is that your Intel 600p is incompatible, and that your 12+16 m.2 adapter may be faulty as well, causing a wild goose chase. Some of these adapters appear to have solder bridges where there shouldn't be any, or dry solder joints, to say nothing of what problems may be in the inner layers of the PCB.

When selecting an SSD, you can't rule out that inaccurate information is being deliberately put out there (fake positive compatibility results) to frustrate/mislead/thwart potential competition in the arbitrage/resale aspects of these SSD replacements.

 

[gilles_polysoft]

Excuse me, but I wonder why you say that high sierra is still in beta. It sounds to me like if the final release could stop supporting the nvme drives. Could that happen?

Thank you.

Hello,
I said that High Sierra is still a beta, because it is still ! And I don't say that about anything regarding NVMe drives, only because any beta software should be used with caution.

It won't last : final release is awaited for tomorrow...
And don't be afraid of it to stop supporting NVMe drives.
The last version which is supposed to be the golden master (17A362a) don't change anything and works perfectly.
[doublepost=1506245364][/doublepost]

Yep, that's also what I thought, but why is my Samsung 960 Evo not being recognized with the adapter then too? It's MLC and has been tested by someone in this thread already. I'm wondering if I have a faulty adapter...

Or could it be possible that the adapter is not compatible to NVMe SSDs? It looks kinda the same as the Sintech one though.

Also did some research on the Intel 600p, people on tonymacx86 say it's natively supported.

Hello,

M.2 to 12+16 Adapters are passive... so they are not, in any sense, "compatible with NVMe SSD" or not..
It's the Mac that supports NVMe drive or not...

I may test an Intel 600p in a few days, but as for the Samsung 960 Evo it's absolutely not normal that it is not recognized.
Could you tell what is your BootRom version ? (and version of the 960 Evo)
[doublepost=1506248377][/doublepost]

That is a question that remains to be fully tested. I tried to follow a RehabMan patch on Lite-On and Plextor NVMe MLC SSD's in multiple of my MacBooks, and it does not work (assuming that there were no errors in the suggested patch on my or RehabMan's sides). I did this with High Sierra. I haven't tried it on Sierra (10.12) with the patch suggested for that one (which may be better tested).
[...]
The drives are not acknowledged or recognized at the hardware level, it seems.

I don't see the point here...

High Sierra natively recognize every 512B or 4K NVMe SSD, being it an Apple NVMe SSD, a WD Black -toshiba SSD, Samsung SSD... so it's absolutely useless to try to use RehabMan patch here.

If the BootRom is up to date, the drive is recognized by the EFI and will show up at "boot menu" if it has an OS on it (being it 10.11, 10.12, Windows, linux etc.)
Only recent OS will then be able to achieve boot, but this is only "secondary" here...
The first preoccupation should be : is my BootRom up to date so that my drive would be recognized at EFI level ?

The problem of the drive being recognized by the OS is at a higher lever

My speculative/inconclusive belief is that your Intel 600p is incompatible, and that your 12+16 m.2 adapter may be faulty as well, causing a wild goose chase. Some of these adapters appear to have solder bridges where there shouldn't be any, or dry solder joints, to say nothing of what problems may be in the inner layers of the PCB.

I never had adapters with solder bridges but I tested both Sintech adapter (I have bought 10s of them) and Chenyang.
Both are only 1-layer 2-side PCB

When selecting an SSD, you can't rule out that inaccurate information is being deliberately put out there (fake positive compatibility results) to frustrate/mislead/thwart potential competition in the arbitrage/resale aspects of these SSD replacements.

fake positive compatibility results ? Please be serious...

 

[myst02]

Hello,

M.2 to 12+16 Adapters are passive... so they are not, in any sense, "compatible with NVMe SSD" or not..
It's the Mac that supports NVMe drive or not...

I may test an Intel 600p in a few days, but as for the Samsung 960 Evo it's absolutely not normal that it is not recognized.
Could you tell what is your BootRom version ? (and version of the 960 Evo)

Hello,

bootrom version is MBA71.0171.B00 (MB air early 2015). I did a bit of research and it seems to be the newest available for the Air 2015. The samsung 960 evo ssd is rev. 1.1.
Please also check your private messages.

 

[imprimis1]

I don't see the point here...

High Sierra natively recognize every 512B or 4K NVMe SSD, being it an Apple NVMe SSD, a WD Black -toshiba SSD, Samsung SSD... so it's absolutely useless to try to use RehabMan patch here.

If the BootRom is up to date, the drive is recognized by the EFI and will show up at "boot menu" if it has an OS on it (being it 10.11, 10.12, Windows, linux etc.)
Only recent OS will then be able to achieve boot, but this is only "secondary" here...
The first preoccupation should be : is my BootRom up to date so that my drive would be recognized at EFI level ?

The problem of the drive being recognized by the OS is at a higher lever

According to the discussions on the insanelymac and tonymac86 forums, Hynix, Lite-On, and Plextor devices require an additional patch to override a pecularity in their SSD firmware, else the OS will not recognize the device.

Certain Intel SSDs were also discussed as requiring the same override patch (although that is not expressly indicated in the Pike or Rehabman patch documentation, whose general importance is disappearing due to 4K reformatting instructions and the High Sierra release).

The native (unpatched) 10.13 High Sierra .kext, which resolves many of the issues with 512B block size, is not sufficient left unpatched to enable those devices to work.

(This may or may not necessarily be relevant to the earlier poster's Intel 600p issue)

Even with the patch in mind, that doesn't establish whether those brands of devices are all otherwise 'well-behaved' enough firmware/hardware-wise to function with these MacBook models.

The users on those forums, of course, have very permissive UEFI implementations on their less-proprietary PC motherboards.
.
I'd be curious to know whether reformatting them on a PC in Linux to a 4K sector size, and perhaps flashing any currently available firmware update, might get these specific SSDs working.

 

[myst02]

Special NVMe patches are only required for SSDs from Plextor, LiteOn and Hynix. I found nothing about Intel SSDs, so I assume they are supported natively in HS.

http://www.insanelymac.com/forum/to...er-macos-sierra-is-ready/page-42#entry2356251

I'll try something today and post results.

 

[mikeboss]

@gilles_polysoft

thank you very much for all the testing you did!
I found one small error in your list -> Mac Pro (Late 2013) the SSD is connected using PCIe 2.0 only.

https://www.anandtech.com/show/7603/mac-pro-review-late-2013/8

regards,
michael

 

[maenpaa24]

Samsung Evo 960 or Pro (960 too) are good devices, and they both work with High Sierra.
WD Black drives work too. We don't know yet for Intel P600.
Don't forget : High Sierra is still (for a few days) a beta. You ought to first install High Sierra on your actual AHCI SSD, then (only then) you can install the new Samsung NVMe SSD.
[doublepost=1506048207][/doublepost]

Hello,

Yes that's true the WD Black is a TLCSSD with Sandisk chips and Marvell controller.
Note that I have also succesfully tested a 512 GB 960 Evo which is TLC, a 960 Pro which is MLC (which I gave to one of my employees and he is using it for over a week in a mid 2015 MacBook Pro retina 15"), and also made tests with a SM961 with no problem at all.

So TLC seems not to be at all the problem with PM961 drives. Both TLC and MLC drive work
I guess if PM961 don't work is because of a firmware problem.
I founded a little Carbon X1 gen3 and will get it in a few days... I'll try to do some firmware backup with the Lenovo exec... don't promise but I'll keep you informed.

Also, a few news...

I did further tests there :

• first I upgraded all my test systems (MBPr 13" late 2013, MBPr15" mid 2015, MBA 13" early 2015) to High Sierra "GM candidate" (build 17A362a) without any problem.
• also I tried unsuccessfully to boot those test machines on El Capitan (10.11.6) with both the NVMe driver of JimJ740-Macvidcards, and the nvme_patch from Rehabman. Both with no success (either forbidden logo or double kernel panic...).
• While booting from an external disk with El Capitan and "jimj740" NVMe drive, thought, I was able to mount and read the internal NVMe SSD (of course not in APFS...)
• same results with Sierra 10.12.6 : unable to boot with the nvme_patch from Rehabman.

I think what is missing here is that I don't use Clover...
Also, maybe nobody is interested in using El Capitan with NVMe drives... (other than Apple ones).
High Sierra works...

But... I did another experiment with the WD Black drive.
I read it was possible to format it with 4K sectors... so I did it.
I wrote a Xubuntu 17.04 distribution on a 8GB USB drive, I booted my MBPr 13" late 2013 on it (with NVMe WD black inside).

I installed smartmontools and nvme-cli :

sudo apt install smartmontools nvme-cli​

And I formatted the NVMe drive with 4K sectors :

nvme format -l 1 /dev/nvme0​

Well.. guess what : the WD drive now works natively on macOS Sierra (surprisingly not El capitan).
I was able to boot on a "vanilla" Sierra install and the installer did recognize the SSD and installation went flawlessly...

So that's interesting : with 4K capable drives we don't even need High Sierra...

​

Hi! Could you clarify me if you could have also formatted the samsung 960 evo with 4k sectors in order to be able to boot sierra as you did with the WD black. I mean if the samsung 960 can be formatted either with 4k and 512b sectors. Or is it only compatible with 512b sectors?

Thank you.

 

[myst02]

Hi! Could you clarify me if you could have also formatted the samsung 960 evo with 4k sectors in order to be able to boot sierra as you did with the WD black. I mean if the samsung 960 can be formatted either with 4k and 512b sectors. Or is it only compatible with 512b sectors?

Thank you.

Samsung 960 is not compatible with 4k sectors.

 

[maenpaa24]

Samsung 960 is not compatible with 4k sectors.

Mmm, is there any disadvantage because of that fact? By the way, do you know any other opal compliant nvme 4k/512b block size ssd drive that fits on these apple machines?

Thank you again, because you have been of great help for me.

 

[imprimis1]

Samsung 960 is not compatible with 4k sectors.

The Samsung 960 Evo is 4K block-aware.

 

[maenpaa24]

The Samsung 960 Evo is 4K block-aware.

Sorry, but I can not understand what being aware of the 4k block size means. Does it mean that it can be formatted to 4k sectors like the WD black?

 

[Audit13]

Hi,

i am very interested in upgrading a mid-2013 Air. Could someone recommend a good adapter for my MBA from a vendor that ships to Canada?

Thank you.

 

[gilles_polysoft]

@gilles_polysoft

thank you very much for all the testing you did!
I found one small error in your list -> Mac Pro (Late 2013) the SSD is connected using PCIe 2.0 only.

https://www.anandtech.com/show/7603/mac-pro-review-late-2013/8

regards,
michael

Hello,
you're absolutely right, I've updated the table, see it attached

Hi! Could you clarify me if you could have also formatted the samsung 960 evo with 4k sectors in order to be able to boot sierra as you did with the WD black. I mean if the samsung 960 can be formatted either with 4k and 512b sectors. Or is it only compatible with 512b sectors?

Hello,
The 960 Evo can't be, to my knowledge, formatted with 4K blocs, which are mandatory to boot Sierra.
So you can't boot Sierra (10.12.6) natively on a 960 Evo, but you can boot High Sierra (10.13) which was just released.

 

[TokMok3]

Note that I have also succesfully tested a 512 GB 960 Evo which is TLC, a 960 Pro which is MLC (which I gave to one of my employees and he is using it for over a week in a mid 2015 MacBook Pro retina 15"), and also made tests with a SM961 with no problem at all.

​

Thank you for all the testing that you had done and for sharing that information. What are the sequential reading and writing speeds after installing the 512GB 960 Pro in the MacBook Pro Mid 2015? Has the system gain speed performance by installing the 960 Pro over the native drive which came with this system?

Thank You!​

 

[gilles_polysoft]

Thank you for all the testing that you had done and for sharing that information. What are the sequential reading and writing speeds after installing the 512GB 960 Pro in the MacBook Pro Mid 2015? Has the system gain speed performance by installing the 960 Pro over the native drive which came with this system?

Thank You!​

Hello,
After installing the 512 GB 960 Pro, I got around 2800MB/sec read, 2000MB/sec write on the MBPr 15" mid 2015.
I can't say it has gained speed because I haven't used the original drive (256GB) with High Sierra...
But it does work well I'm satisfied

 

[TokMok3]

Hello,
After installing the 512 GB 960 Pro, I got around 2800MB/sec read, 2000MB/sec write on the MBPr 15" mid 2015.
I can't say it has gained speed because I haven't used the original drive (256GB) with High Sierra...
But it does work well I'm satisfied

Thank you, that is a significant increase in performance. I have read that it requires an adapter to install this drive, what adapter did you use?

Thank you again.

 

[gilles_polysoft]

Thank you, that is a significant increase in performance. I have read that it requires an adapter to install this drive, what adapter did you use?

Thank you again.

Hello,
I used both "Sintech" and "Chenyang" adapters.
I bought mostly "sintech" because they have lots in stock and they're cheaper.
In my tests I can't see any difference between both adapters.
What made a difference was, again, to put kapton tape at the back of the adapter so that the signal isn't too close to the shield of the Apple MLB 12+16 connector (either this would produce a short circuit or unwanted capacitance).

Here is a photo of both adapters...
I just noticed the "chenyand" has a solder join between two pins, this seems to be normal... I checked with a multimeter between the same pins on the "Sintech" adapter and they are also connected (0.20 ohms between 2 pins).