I ran a diagnostics test and I am getting VDH002 which seems to be a problem with the storage device even though i have no problems. Maybe this is because I have a 3rd party ssd?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe
- Thread starter maxthackray
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I wrote this problem in Dec 13, 2018, with no response.
https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-108#post-26905290
I think that all MacBook Pro 13 retina would show this result, and I did not found this error with MacBook Air 13.
Even now, it has not resolved yet.
There is 2 way to do Apple Diagnostics, 1 is "D" at start-up, 2 is "opt+D" at start-up ( usually using network).
The version of Diagnostics is not same, for example "D" :1.0.35r2, "opt+D": 1.1.35r2.
I never found error PPN001 in "opt+D" diagnostics. It may feel Apple bugs.
I ran the diagnostic routine by holding down the D key on a 2017 Air with a 256 GB HP ex900 and the short, black Sintech adapter and it came back with ADP000 which means no issues found.
Edit 1: ran diagnostics for the 2017 Air by holding down the option+ D key and also received ADP000 which indicates no issues found.
Edit 2: ran both versions of the diagnostics on an early 2015 13" Air with a 256 GB Intel 660p and short, green Sintech adapter and received ADP000 too.
Last edited:
You seem to have the best luck out of all of us
Edit: It is probably because the 2015+ models have full support for NVME
Last edited:
Apple recommends using diagnostic tool "D" for 2013+ models, that's why I am afraid that error would not be a bug.
https://support.apple.com/en-us/HT202731
I wonder if @gilles_polysoft have faced this error during his tests
Probably you have a 2014 15' mbp?
Cant find a chip on board to connect clip on 13'
That's probably why. I wouldn't be surprised if this is an issue with pre 2015 models and the support for NVME drives in the EFI
Yep, I wish I bought the JTAG connector but I think if I can't get the chip to read this week I'm going to just buy the Matt Card, since it's only slightly more expensive than the adapter and it requires no modification of the firmware.
Last edited:
as i have read matt card have to be prepared by somebody (seller?!) from before and sended with proper data, by default its blank, right?
Yep, on the website you specify the version you need.
Even with the ordering of the Matt Card, a mod is [probably] needed, but it is less risky to flash the Matt Card than it is to flash the real BIOS chip.
Don't know if it is related with the PPN001 error but i've noticed that using the intel 760p launching pmset -g in sleep 1 appear "sleep prevented by addressbooksourcesync".
Troubleshotting is to remove google accounts and using icloud sync for contacts.
Well using stock ssd it works, using nvme ssd in my case intel 760p it appear again and again.
So I belive that if sleep doesn't work properly could result a SMC issue than an error releted to power management.
@wawon launching pmset -g tru terminal do you get sleep prevented by addressbooksourcesync?
Troubleshotting is to remove google accounts and using icloud sync for contacts.
Well using stock ssd it works, using nvme ssd in my case intel 760p it appear again and again.
So I belive that if sleep doesn't work properly could result a SMC issue than an error releted to power management.
@wawon launching pmset -g tru terminal do you get sleep prevented by addressbooksourcesync?
I also have a 760p I will check tonight. I remember seeing something that is preventing sleep.
Edit: I checked the pmset -g output and i do not have this prevention. I've also got iCloud contacts in sync and a google account only syncing mail.
Last edited:
I've got a feeling that my MacBook Pro early 2015 is overheating.
I was trying to use the Adata XPG SX8200 with long sintech adapter on my Macbook Pro early 2014 without success. The computer was getting extremely hot mostly because running iCloud sync in the background. Also when I put it in my laptop bag and took it out an hour later it would be extremely hot as the fans were running. I think because of that one time the battery got swollen and now last only half of the time. I was also annoyed that I have to reset the computer every time I closed the lid and opened it again.
So I got the 2015 and switched the drive with long sintech adapter and the issue still persists. I installed the fresh Mojave. Restored my time machine. Brought it to work today, bettery drained to 84% and computer was hot. When running iCloud sync the temperatures were around 97C. When I forced quit "bird" and "cloudd" the temps went down 60C... which is still hot. I attached the screenshot with temp and processes running currently. Do you guys happen to have any advice beside buying original apple ssd or switching to windows?
Current Bootoot ROM Version: 182.0.0.0.0
I've also attached the wake up log.
I've also ordered short sintech adapter. It should arrive tomorrow and I will do further temperature testing however I'm loosing patience and might switch to ... Matebook pro.
I was trying to use the Adata XPG SX8200 with long sintech adapter on my Macbook Pro early 2014 without success. The computer was getting extremely hot mostly because running iCloud sync in the background. Also when I put it in my laptop bag and took it out an hour later it would be extremely hot as the fans were running. I think because of that one time the battery got swollen and now last only half of the time. I was also annoyed that I have to reset the computer every time I closed the lid and opened it again.
So I got the 2015 and switched the drive with long sintech adapter and the issue still persists. I installed the fresh Mojave. Restored my time machine. Brought it to work today, bettery drained to 84% and computer was hot. When running iCloud sync the temperatures were around 97C. When I forced quit "bird" and "cloudd" the temps went down 60C... which is still hot. I attached the screenshot with temp and processes running currently. Do you guys happen to have any advice beside buying original apple ssd or switching to windows?
Current Bootoot ROM Version: 182.0.0.0.0
I've also attached the wake up log.
I've also ordered short sintech adapter. It should arrive tomorrow and I will do further temperature testing however I'm loosing patience and might switch to ... Matebook pro.
Attachments
Last edited:
i get exactly the same with sx8200pro, just i am different weight category user
my CPU starts to be a lot hotter, SSD no more 45 C
thats why i sell it and now target Kingston a1000 with pci-e 3.0x2
Last edited:
Try SMC e PRAM resetI've got a feeling that my MacBook Pro early 2015 is overheating.
I was trying to use the Adata XPG SX8200 with long sintech adapter on my Macbook Pro early 2014 without success. The computer was getting extremely hot mostly because running iCloud sync in the background. Also when I put it in my laptop bag and took it out an hour later it would be extremely hot as the fans were running. I think because of that one time the battery got swollen and now last only half of the time. I was also annoyed that I have to reset the computer every time I closed the lid and opened it again.
So I got the 2015 and switched the drive with long sintech adapter and the issue still persists. I installed the fresh Mojave. Restored my time machine. Brought it to work today, bettery drained to 84% and computer was hot. When running iCloud sync the temperatures were around 97C. When I forced quit "bird" and "cloudd" the temps went down 60C... which is still hot. I attached the screenshot with temp and processes running currently. Do you guys happen to have any advice beside buying original apple ssd or switching to windows?
Current Bootoot ROM Version: 182.0.0.0.0
I've also ordered short sintech adapter. It should arrive tomorrow and I will do further temperature testing however I'm loosing patience and might switch to ... Matebook pro.
You could also try diagnostic (holding D +power on) to ceck errors
OMFG, I realized that I was off by one pin on the cable from the clamp to the reader.
The chip is 8 pin, the cable connector is 10 pin. I shifted it over one pin and now I'm golden.
Mac boots up just fine, unfortunately I don't have a new drive yet. I wasn't going to waste my money until I was certain I could flash the BIOS without messing anything up.
Since it boots I'm going to safely assume I did everything right, if anything fails at least I have 4 copies of the original ROM dump.
The chip is 8 pin, the cable connector is 10 pin. I shifted it over one pin and now I'm golden.
Mac boots up just fine, unfortunately I don't have a new drive yet. I wasn't going to waste my money until I was certain I could flash the BIOS without messing anything up.
Since it boots I'm going to safely assume I did everything right, if anything fails at least I have 4 copies of the original ROM dump.
Attachments
Last edited:
Late 2013 Pro 13" stock SSD bootrom updated from 151 to 153 with 10.14.5.
Mid-2014 Air 13" stock SSD bootrom updated from 112 to 115 with 10.14.5.
Early 2015 Air 13" Intel 660p bootrom updated from 184 to 186 with 10.14.5.
2017 Air HP ex900 bootrom updated from 184 to 186 with 10.14.5.
I encountered no problems when updating all four MacBooks from 10.14.4 to 10.14.5.
Mid-2014 Air 13" stock SSD bootrom updated from 112 to 115 with 10.14.5.
Early 2015 Air 13" Intel 660p bootrom updated from 184 to 186 with 10.14.5.
2017 Air HP ex900 bootrom updated from 184 to 186 with 10.14.5.
I encountered no problems when updating all four MacBooks from 10.14.4 to 10.14.5.