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!
I was messing with my galaxy core prime (android 4.4.4) using a app to remove system apps that you can't with the stock app manager.. (no reason for crap like smartcard manager, bluetooth, wifi sharing..etc to be running when i haven't authorized such things, seems like security risk imo)
Was also editing the autorun list and messing with Norton applock and phone encryption settings to try to further secure it.
Welp, I f'ed things up because phone crashed and now can't do anything.. can't access home screen, settings, call/txt, nothing. So I booted into the stock bootloader and tried formatting the entire thing including cache..
Didn't fix the problem, can't finish the setup wizard without it crashing, get message saying setup, hangouts, and keyguard stopped working and then my phone bricks and can't do absolutely anything. No backup either.
I have been googling and googling for solutions but everything I read says to either:
-Reformat from bootloader (tried a 100 times)
-Wipe with TWRP or CWM (don't have either and can't access play store)
-Use Kies (won't detect my device since I can't enable MTP)
-ADB sideload twrp or cyanogen (cant, usb debugging probably not enabled since I formatted and no way to enable it since setup of android fails)
Odin can't detect anything either.. probably due to same reason. (Cant enable MTP or usb debugging)
So am I totally screwed? What are my options here?
I noticed the stock bootloader has a option to install from external storage.. can I put my sd card in a phone that does work and download twrp, cyanogenmod, (or ANYTHING else to fix this) to that, then put it back in my bricked phone and re flash it that way? That way I wouldn't need mtp or usb debugging... or won't that work?
Wasted so much time trying to fix this guys, googling and even formatted my pc removing Linux and reinstalling Windows hoping suddenly my pc would detect it.. atleast on linux when I used "adb devices" command it detected my device (trying to sideload anything didn't appear to work though, phone says error about verifying it and tries again and says completed and reboots but no sign of the rom I just supposedly sideloaded anywhere)
removing Linux and installing Window seems to have been a mistake because on windows using "adb devices" returns a blank list.. Tried different cords, ports, kies 2 and 3, reinstalling drivers, disabling firewall..etc but like I said even if I do get adb to detect it, what can I do from there without mtp or debugging?
Sorry for wall of txt, just want to be descriptive as possible so I don't get all replies telling me to try stuff that I've tried 100 times or just flat out won't work for my particular problem because of the above reasons..
will be sincerely grateful to anyone that took the time to read this and try to help me.
I've been trying to root my OPO for two days now and I've continued to have this issue. After installing Android Studio + the SDK, as well as downloading the Google USB Driver, when I connect my phone to my computer it shows up as an MTP device under unknown devices. If I allow it to automatically download drivers, it becomes a portable device instead. But I need it as an ADB device. I've already started USB debugging on the phone, as well as switched between all the different USB options on the phone (charging, MPT, PTP, MIDI, etc.) and still no good
When I try to update the driver for the "MTP" device, the Google USB drivers don't show up, and if I try to browse manually, it comes up with the error message saying how "the folder you specified doesn't contain a compatible driver." What do I do?
Thanks!
tli said:
I've been trying to root my OPO for two days now and I've continued to have this issue. After installing Android Studio + the SDK, as well as downloading the Google USB Driver, when I connect my phone to my computer it shows up as an MTP device under unknown devices. If I allow it to automatically download drivers, it becomes a portable device instead. But I need it as an ADB device. I've already started USB debugging on the phone, as well as switched between all the different USB options on the phone (charging, MPT, PTP, MIDI, etc.) and still no good
When I try to update the driver for the "MTP" device, the Google USB drivers don't show up, and if I try to browse manually, it comes up with the error message saying how "the folder you specified doesn't contain a compatible driver." What do I do?
Thanks!
Click to expand...
Click to collapse
Just want root? No custom recovery or rom?
Then use kingoroot or kingroot app on phone and get root without pc
Make sure you've fast net connection.
Mr.Ak said:
Just want root? No custom recovery or rom?
Then use kingoroot or kingroot app on phone and get root without pc
Make sure you've fast net connection.
Click to expand...
Click to collapse
Don't exactly want to use them due to the risks / IMEI debacle.
I have exactly the same issue.
I managed to get root by flashing SuperSU (only on a system less basis)
This just got the rooting side sorted but I'd still want to be able to get ADB working again on the phone.
I tried with three different laptops and the issue is persistent. I am running Cyanogen 13.1 coated beautifully with a Boeffla kernel and a slimlined build.prop (have to boast because everyone can agree, the Oneplus One is a revolution on its own)
tli said:
Don't exactly want to use them due to the risks / IMEI debacle.
Click to expand...
Click to collapse
Trsut me,there are no risks involved.
The Problem:My Xperia Z1's screen is fubar and I need to extract some documents.
Potential solution:Somehow enable USB-debugging and use Vysor to control the phone via my PC and get the documents or use some tool to extract files through commands.
So far I've gotten none the wiser and reached multiple dead ends through googling, I'm very new to this. I downloaded flashtool64 which detects my phone so if flashing would be required that would be possible, I don't really know what flashing does - was hoping it might enable debugging by default. I also tried ADB, installed the drivers and everything, but it doesn't detect my phone, I also couldn't find any helpful commands through googling.
Anyone with some serious expertise in this area that can help me? :good:
Hi, I've come to these forums because you guys are knowlegeable.
I essentially uninstalled thorugh ADB the package installer (com.google.android.packageinstaller) and little did I know that was a big mistake on my part, as I didn't realize the package installer was a core part of the system. All was going well until i turned on and off my phoen, and it is now always stuck in recovery mode.
- Rebooting the phone just sends me back to the menu.
- I've not tried wiping the data yet, since I want to keep my files (for the moment).
- Connect with MiAssistant allows me to connect my phone to my PC, but it in sideload mode automatically. I can go in fastboot mode though, and fortunately I have turned USB Debugging on.
As I've come to realize, a factory reset or flashing a ROM would fix my issue, but also delete all my files (photos, music...). I was planning to do a backup of my photos, but now it's too late.
Is there any way I can access my files and pull them to my PC on sideload/fastboot mode?
The only thread i have seen with a similar problem is this one: https://forum.xda-developers.com/showthread.php?t=2487147
I also get the error:closed when I try an adb pull.
Thanks in advance.