Database Info

No MTP or PTP for Rooted Nexus 5?

I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.

aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.

ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online

aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4

Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go

ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.

ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.

By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.

The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!

Unable to copy files to Nexus 5

Please help.
I have rooted and installed SuperSu and TWRP on my device.
I tried to connect my phone to my computer, it gets detected and drivers are installed.
When I cannect it as MTP, the drive on the phone does not appear on my coimputer. When I change to PTP, it appears as camera. But I can't copy files to it.
I have tried with another computer with the same result.I have rebooted the computers and I also reset my phone which didn't help.
What am I doing wrong?
Thank you

xdm9mm said:
Please help.
I have rooted and installed SuperSu and TWRP on my device.
I tried to connect my phone to my computer, it gets detected and drivers are installed.
When I cannect it as MTP, the drive on the phone does not appear on my coimputer. When I change to PTP, it appears as camera. But I can't copy files to it.
I have tried with another computer with the same result.I have rebooted the computers and I also reset my phone which didn't help.
What am I doing wrong?
Thank you
Click to expand...
Click to collapse
enable adb in developer options and then connect to your pc, that fixed connection for me

thenobol said:
enable adb in developer options and then connect to your pc, that fixed connection for me
Click to expand...
Click to collapse
if you mean usb debugging, I have already done that...

xdm9mm said:
if you mean usb debugging, I have already done that...
Click to expand...
Click to collapse
Do you just not see the device within you folders? Might be a driver issue, I had some problems with that initially.
Also, I had issues trying to transfer pictures/videos from my PC to the phone as well. IT would start the transfer but started crashing a few times before I was able to transfer everything over successfully. But that might just be a Win 8.1 compatibility or driver issues as well.

skyo12 said:
Do you just not see the device within you folders? Might be a driver issue, I had some problems with that initially.
Also, I had issues trying to transfer pictures/videos from my PC to the phone as well. IT would start the transfer but started crashing a few times before I was able to transfer everything over successfully. But that might just be a Win 8.1 compatibility or driver issues as well.
Click to expand...
Click to collapse
Yes I don't see the device. Maybe it's caused by the old Nexus 4 drivers.. anyway I uninstalled "Android Device" from my computer's device manager, unplugged the phone, then it miraculously installed the drivers... I'm copying mp3's to my phone now.
Thanks

Sounds like a driver issue. Google "Android naked usb drivers" those worked well for me

[Solved] USB suddenly stopped working

I have a Nexus 5 that I have had about a month now and I had the USB on it working before about a week ago. I plugged it in today and neither my desktop or laptop could recognize it anymore. Both computers are running Windows 8.1.1 and the issues seems to be new as I can neither get USB storage or ADB to find it. The closest I can get it to working is to switch the USB mode to PTP and it reads that but I don't want to pull photos off. When I have it in MTP, it makes the sound of it plugging in and my phone shows it is plugged into a computer but Explorer shows nothing and it says it is working normally in device manager. I've tried everything from enabling and disabling debugging, restarted both my phone and computer tried reinstalling the drivers (both by the computer automatically finding them and manually installing them) but nothing seems to work. Is it possible that Windows Update could of broke the drivers since my computer installed updates yesterday? I also have Linux on my laptop and it appears to read fine with Linux.

That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA

EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
OK thanks. I'll give it a try because it was showing up as ACER ADB Device under device manager
EDIT: I updated the drivers and used the USB composit drivers instead and it got MTP working again. When I set it to USB composit, it installed Google's ADB drivers and the Nexus 5's USB drivers so everything is working again. Thanks for your help

EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
I can´t manually update driver because of this:

when i update the acer adb it says the driver is up to date and everything is all same. what to do?

Thanks! Thought I was going to go crazy. Worked for me...

i set the driver to MTP as mentioned above and the phone started to show up on the explorer but now i couldnt copy any files from my laptop to the
phone. It displays like that and if clicked yes then the copy wouldnt happen.what is the problem.

Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.

wangdaning said:
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
Click to expand...
Click to collapse
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.

Big tree said:
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Click to expand...
Click to collapse
That msg comes when you're in PTP mode I think...Only certain formats are supported.
Check under storage, expansion menu and make sure you are set to the first option...not PTP.
Above guy mentioned to have phone in USB debugging mode when setting up drivers.

If the device is showing then you need to point to the drivers for it (download them from google). I reinstalled windows a few days ago and had the acer issue (device first shows up in device manager as nexus 5 then switches to acer), windows wants it to be an acer device. Stop windows and then install the correct drivers,
For me I had to click the auto install in windows tray and tell it to stop. After a few times it worked.

No I'm connecting in MTP mode. Ahh its gettn irritating.

OnePlusOne not recognized by ADB/in Android Debugging mode after update to YOG4PAS3JL

Hi,
I have a very serious problem with my OnePlusOne (64GB) after updating to version YOG4PAS3JL. Since the update, ADB no longer recognizes my phone.
It doesn't depend on the computer I'm using, I have tried to use my phone on 3 different computers (Windows) that I use on a regular basis and none shows my phone with the command adb devices.
Connecting via MTP is no problem, but when I enable Android debugging with USB, my phone will not show up in Windows Explorer.
I have also attached a Samsung Galaxy Note 4 and a HTC phone, both are recognized by ADB.
If I change the mode to MTP, it will show up as portable device called A0001 in the windows device manager. If I switch to Android Debugging, it will simply disappear and not show up
as "other device" or usb device without driver. So I can't even reinstall Android ADB Interface, it also doesn't show up in the Device Manager any longer. If I try to install a driver for my OnePlus One when it is in MTP mode, it will also only allow me to install MTP drivers (no possibility to install the previously so fine working Samsung USB drivers).
I have literally tried every solution out there I have found, from unplugging and restarting my phone, using different USB ports, using different USB cables, reinstalling Samsung USB drivers (didn't help as phone did not show up as unrecognizes device any longer), uninstalling Google USB driver, adding OnePlusOne to the .inf usb driver file myself (which mostly resulted in an "no compatible driver was found in this folder"-error), installing fastboot (didn't change anything), universal adb driver setup, pdanet, using USDBDeview, removing drivers with the bacon root toolkit to removing mtp files from the inf folder of windows to prevent MTP driver installation, but nothing worked
I would prefer to go back to the version before YOG4PAS3JL, where ADB worked fine or install a different ROM, but I have seen that every guide states that you need to have ADB to install a new ROM. As my phone is not rooted and I can no longer use ADB with my phone, I'm basically pretty stuck and don't know what to do I'm pretty desperate after two days of trying to solve this problem without success and would be so thankful for any suggestion what I could do.

Same situation...let me know if you find any solution.

Same situation here. Anf I guess this might have a link with my lack of internet connection while tethering.
Did any of you tried the USB or wifi tether? Does it work?
Sent from my A0001 using XDA Free mobile app

USB Connection Issues

I just rooted my s8+ with partcyborg's samfail and everything is working great except the usb isn't being recognized. I can see my phone on my computer and I can move files to my desktop but on my phone I get this message - "The connected device is unable to access data on this device. Reconnect the USB cable and try again." I have USB debugging enabled in settings. I'm using windows 10. ADB is up to date. I installed the samsung USB drivers. The device isn't recognized in kies or smart switch.
I'm at a total loss here. Any ideas? Could this be related to the 80% battery bug I was seeing? It's been at 80% for a while now.
Apologies if this is an obvious fix. I haven't rooted a phone since kitkat I looked around but the other threads weren't helpful.

chikichiken said:
I just rooted my s8+ with partcyborg's samfail and everything is working great except the usb isn't being recognized. I can see my phone on my computer and I can move files to my desktop but on my phone I get this message - "The connected device is unable to access data on this device. Reconnect the USB cable and try again." I have USB debugging enabled in settings. I'm using windows 10. ADB is up to date. I installed the samsung USB drivers. The device isn't recognized in kies or smart switch.
I'm at a total loss here. Any ideas? Could this be related to the 80% battery bug I was seeing? It's been at 80% for a while now.
Apologies if this is an obvious fix. I haven't rooted a phone since kitkat I looked around but the other threads weren't helpful.
Click to expand...
Click to collapse
So what do you wanna do with your USB connection? Just MTP (e.g. transfer files like you would when connecting a USB-Stick to PC) or you wanna do some ADB operations?
If you just want to transfer files, there's no need to have USB-Debugging enabled (in fact this is kind of a security risk when you connect to an unknown pc)

jaannnis said:
So what do you wanna do with your USB connection? Just MTP (e.g. transfer files like you would when connecting a USB-Stick to PC) or you wanna do some ADB operations?
If you just want to transfer files, there's no need to have USB-Debugging enabled (in fact this is kind of a security risk when you connect to an unknown pc)
Click to expand...
Click to collapse
I'm trying to use the phone as a bootable drive because my USB stick was stolen. I want to put a linux distro on my laptop.

chikichiken said:
I'm trying to use the phone as a bootable drive because my USB stick was stolen. I want to put a linux distro on my laptop.
Click to expand...
Click to collapse
In the past I used an app on play store call drive droid to boot linux.....
I have the same issue on mine and have not found a fix been looking for a while i kinda just gave up

TheMadScientist said:
In the past I used an app on play store call drive droid to boot linux.....
I have the same issue on mine and have not found a fix been looking for a while i kinda just gave up
Click to expand...
Click to collapse
Yeah I've been trying to use drivedroid but it says there are issues with the mass storage. I'm going to send the dev a message with the ROM and see if there's anything he can do. For now just gonna flash back to stock

chikichiken said:
Yeah I've been trying to use drivedroid but it says there are issues with the mass storage. I'm going to send the dev a message with the ROM and see if there's anything he can do. For now just gonna flash back to stock
Click to expand...
Click to collapse
I'm sure he has looked into it. I talk to him quite a bit now that I think about it I have not heard nothing about it