Fix for Android File Transfer (AFT) and Mac (Mountain Lion, Mavericks) "device not found" issue
I have a fix for the Device Not Found issue but Incapsula keeps preventing me from posting it.
I'm going to do it line by line and see what the issue is.
Hi, I figured it out.
It's a bad driver from Verizon.
When you plug in the phone, it first attaches as an "installer" and presents an ISO960 (cdrom) image to the OS.
f you wait, it will go away and the device will mount under AFT just fine, and present your files.
If you're in a hurry, you can go to the S5 screen, under the alerts click on the USB thing, and check the "MTP device" box, which puts the phone immediately into media transfer mode.
Wait.. what? you installed that thing called "Kies?" Or you (like me) accidentally forgot that Verizon porks for drivers, and ran the installer instead of just waiting for MTP with AFT to kick in?
Here's your fix:
I found out (after installing Kies on the computer that stopped working) that Kies uses a driver called "ssuddrv.kext" when its installer runs.
It lives in /System/Library/Extensions/ssuddrv.kext
launch terminal and execute:
sudo r m -rf /System/Library/Extensions/ssuddrv.kext
** note there is a space on purpose in the "r m" command because Incapsula would not let me post a command that removes files. brilliant.. so omit the space when you try this. **
really, just delete it... At first, I just moved it and rebooted to see if anything else would break. It's been about a week, and nothing has broken, and AFT + MTP on the Galaxy S5 is working just fine again.
On both machines.
The Verizon installer and Kies both install that dysfunctional ssuddrv.kext driver. Just delete it. Then reboot, then connect your phone and you're back to the point at which you can either wait for the device to go into MTP mode or you can manually check the box. Myself, I'm lazy, so I wait.
Wish I could find a way to stop the phone from presenting an installer to the OS that doesn't work.
Way to be awesome, Verizon. Worse than bloatware: bloatware that doesn't work.
-jre
I have a fix for the Device Not Found issue but Incapsula keeps preventing me from posting it.
I'm going to do it line by line and see what the issue is.
Hi, I figured it out.
It's a bad driver from Verizon.
When you plug in the phone, it first attaches as an "installer" and presents an ISO960 (cdrom) image to the OS.
f you wait, it will go away and the device will mount under AFT just fine, and present your files.
If you're in a hurry, you can go to the S5 screen, under the alerts click on the USB thing, and check the "MTP device" box, which puts the phone immediately into media transfer mode.
Wait.. what? you installed that thing called "Kies?" Or you (like me) accidentally forgot that Verizon porks for drivers, and ran the installer instead of just waiting for MTP with AFT to kick in?
Here's your fix:
I found out (after installing Kies on the computer that stopped working) that Kies uses a driver called "ssuddrv.kext" when its installer runs.
It lives in /System/Library/Extensions/ssuddrv.kext
launch terminal and execute:
sudo r m -rf /System/Library/Extensions/ssuddrv.kext
** note there is a space on purpose in the "r m" command because Incapsula would not let me post a command that removes files. brilliant.. so omit the space when you try this. **
really, just delete it... At first, I just moved it and rebooted to see if anything else would break. It's been about a week, and nothing has broken, and AFT + MTP on the Galaxy S5 is working just fine again.
On both machines.
The Verizon installer and Kies both install that dysfunctional ssuddrv.kext driver. Just delete it. Then reboot, then connect your phone and you're back to the point at which you can either wait for the device to go into MTP mode or you can manually check the box. Myself, I'm lazy, so I wait.
Wish I could find a way to stop the phone from presenting an installer to the OS that doesn't work.
Way to be awesome, Verizon. Worse than bloatware: bloatware that doesn't work.
-jre
Last edited:
Facebook
Twitter
Instagram