Someone commented above about using Kapton tape or some other insulator to avoid having the pins short out on the metal housing. Try that first, I doubt the connector failed because they are nothing more than trace wires that map one interface to another. If you have a microscope you could look to see if any of the solder joints on the connector are broke or if it may be shorting out when you have it installed. I've had the same thing happen before. The flashing question mark folder just means it cannot find an operating system which means either you don't have one installed properly on the drive or the drive is malfunctioning (i.e., drive pins are shorting to ground as described above). Good luck and let us all know what fixes it.
Red line; however, it looks like you have the newer adapter whereby kapton tape isn't required.
Yes, it certainly looks like I was not running the latest Mojave before updating to Catalina.
Did you upgrade to 10.14.6 using the original Apple SSD? If not, this would explain why the bootrom didn't update. Afaik, only 2015 MacBooks accept a bootrom update with a third party nvme drive.
Yes, High Sierra is what was needed.
I've seen this happen before and it is because the SSD may soon be failing. If that is the case then it will not update. In addition if it does not have two SSD sensors as shown in ASD 162 then it will not update the boot rom to 158.0.0.0. I have noticed that the update to 159.0.0.0 seems to work with various NVME drives. So it is a bit shocking that his doesn't seem to update. Some MBAs would not update unless I updated to HS or Mojave first and then to Catalina. Perhaps that could be part of the problem as well? Anyhow, let us know what fixes it for you so that we can update the first post with our accumulated knowledge.
Try upgrading to 10.15.4 002 which came out just 3 weeks ago. Hopefully then it will update the Boot ROM and please report back whether or not it does. Perhaps it is only from 158 to 159 that doesn't do the SSD check.
I've never seen a post from a 2013 or 2014 owner say that their MacBook accepted a bootrom update with a nvme drive inside when upgrading tree OS.
Hi,
Just wanted to chime in on my experience.
Macbook Pro 13 Inch 11.1 mid 2014
10.15.4
Bootrom 157.0.0.0 (used the internet recovery both times + TM backup)
Edit: used this copy of the Sintech Green Short Adapter with success: Zer One adapter
Carte Adaptateur de Disque Dur pour Convertisseur D'adaptateur SSD à NVME pour 2013 2014 2015 Macbook Pro/Macbook Air
Caractéristiques : Remplacement : Compatible avec : Pro Retina A1398 A1502 (ME864 ME865 ME866 ME293 ME294). Compatible avec : Pro Retina A1502 A1398 (MGX72 MGX82 MGX92 MGXA2 MGXC2). Compatible avec : Pro Retina A1502 A1398 (MF839 MF840 MF841 MJLQ2 MJLT2). Compatible avec : Air A1465 A1466 (M...www.amazon.fr
Previously went for a 500GB Samsung 970 EVO PLUS that I used for a month, but the heat generated was quite a burden.
So I recently switched to a Corsair 1TB MP510. R/W speeds are the same since it's the PCIE 2.0 4x that limits the SSD anyway (I get 1400 / 1400 give or take).
I gained around 5 to 8 degrees in Idle / light usage (970 EVO drawing 0.75A vs 0.16A for the MP510).
Only downside is that the 970 had no sleep issues whatsoever - never had any hibernation problem nor any panic report during the course of the month. (with standard settings - sleep mode 3)
The MP510 does have those issues (got it 3 night in a row). But I can live with it, as it runs much cooler and draws less.
Tried the NVMeFix as well but doesn't seem to work on mid 2014 MBP.
Those are my 2cts
Does this happen if you do a fresh installation rather than restoring a backup?
That I havent tried yet. Will do that later today. I was hoping I didnt need to go that route. CCC was working great for me before.
I have put nvme drives into three early 2015 13" Airs and none have the wake issue. I did fresh installs.
