After Froyo - Can't get back into ADB - Droid X General

I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z

Zaphod-Beeblebrox said:
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Click to expand...
Click to collapse
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony

anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
I honestly didn't expect this to work, but since I didn't have any better ideas, I might as well try it. Man was I wrong.
The reason I did not think this would work is that I had downloaded the Moto Drivers (just the drivers, not the full MotoConnect software) from the Moto website. I did not expect there to be any difference.
Evidently the software on the phone does have more drivers than the downloadable package from Moto.
Thanks for the help.

I've tried doing this...turning off Dev mode, and turning on USB Mass Storage mode, but still no motoconnect setup screen comes up. Any other way to get those drivers installed?

anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
Like Zaphod, I very much appreciate the help and did not expect this to work lol. Thanks much.

Yesterday at work I couldn't get into adb either because the devices drivers no longer loaded. I had to edit the driver inf file. It seems like the usb diver id changed.I'm on my phoebe right now and works rcd wasn't working anyway. You can get the new id if you open up device manager sand open the properties for the phone.the last tab has device details and the first or second has the new id. Just add that in the inf. Should look like the other entries. Just try adding rfd drivers with that new inf.

media sync mode gets you adb.
might say driver not installed when you click on it but adb will startup and work properly.
least on mine it does. win7 64bit

anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
while i got adb using the method i described above, this is still a nice find lol
i would of nvr saw this cause im always in debugging mode .
thanx for this

drewlamo1 said:
while i got adb using the method i described above, this is still a nice find lol
i would of nvr saw this cause im always in debugging mode .
thanx for this
Click to expand...
Click to collapse
cant get it to work, ive tried all the above? keep getting error: device not found

Zaphod-Beeblebrox said:
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Click to expand...
Click to collapse
change from pc mode to media sync mode in the notification window

If turning on and off USB Debug mode doesn't work, then do this, it will almost certainly work:
http://alldroid.org/default.aspx?g=posts&m=7662#post7662

teenfaces said:
change from pc mode to media sync mode in the notification window
Click to expand...
Click to collapse
Exactly as this is the fastest and simplest way to fix it. I freaked about about a week ago when my X would not work threw ADB anymore and that is the trick that took care of it. And it is proven to work it has been posted hundreds of times on many other site/forums.

Related

[Problem] Adb won't show up devices whatever I do...

I Tried guides that try to solve this from everywhere, Including here,
I used latest version of the android usb-drivers that comes with the latest Android SDK (downloaded directly from google with the SDK download GUI thinggy).
Tried to uninstall all usb roots,
Tried force removal of driver using external app and re-installations
Tried different drivers from multiple locations,
And still, whatever I try - there is notihng on the "adb devices" list
"List of devices attached"
<CR>
<CR>
C:\.......>
Everything shows up okay, on first run of the adb the 'whatever' service starts and everything is fine
Device DOES appear properly on device manager "Android Composite ADB Interface".
Windows DOES the pnp beep whenever I check or uncheck the "Debugging mode"
This hapnned both on STOCK ROM (first or second software version of the phone released) and on latest Cyanogen 5.0.6
One thing I did noticed, "Android ADB Device" Either appear under "Android" type (usb debugging on) or under USB Controllers (When usb debugging is off).
Ho, I did not mentioned the phone, I'm talking about Nexus One.
Thanks for any help.
Amm, any ideas?
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
I take it your on Windows, so I might not be much help as I use Linux strictly but try to run the command prompt as Administrator (right click > run as I think) and then
adb kill-server
adb start-server
Not sure if that will help but I know in Linux you must start the ADB server as root in order to see the attached devices, so I assume in Windows you must start it as Administrator.
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Beackman said:
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
Click to expand...
Click to collapse
I Ment just that when I said "Tried force removal of driver using external app and re-installations"
drew630 said:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Tried that just now, on windows I'm in the Administrators group, that should work... It doesn't :/
bmxrideher said:
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Click to expand...
Click to collapse
Good idea, but still no salvation :/
Try uninstalling the mass storage driver for the phone, this worked for me
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Synestr said:
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Click to expand...
Click to collapse
No problem, lol, almost a month later. Glad I could help.
Naemion said:
No problem, lol, almost a month later. Glad I could help.
Click to expand...
Click to collapse
Hells to the yea, I now has root and rom and I am a happy boy!
Thanks again
hmm >.< nothing is working for me this laptop is not detecting my (Nexus S) device in ADB
windows sees it fine, drivers are installed (for normal mode and ADB mode), mass storage works,
but ADB Devices list shows up empty
2 other phone works just fine (SGS & XT720)
Update: went to another computer and it shows up properly.... (you just gotta "luv" windows )
Try installing htc sense from htc website even if running vanilla. It will install the driver properly. Then un-install sense and keep drivers. It's the only thing that worked for me.
Sent from my HTC Vision using XDA App

If anyone knows how to get adb working with the Iconia-

I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
kjy2010 said:
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
Click to expand...
Click to collapse
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
looking335 said:
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
Click to expand...
Click to collapse
And please my op... of course I tried the drivers from acer's site, both of them. And my sdk kit works, just like I said. But thanks!
officetally said:
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
Click to expand...
Click to collapse
Glad it was something simple!
Sometimes we always overlook the simple things.
But I would not have told on myself.to many other things could blame it on.giggles

Nexus 4 appears as unknown device

Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
jining said:
Hello, I am trying to connect my nexus 4 to my computer to put some music on. This used to work, but now it is being detected as an unknown device. I tried updating the drivers to the Universal Naked driver, but it just says the best driver is already installed. I tried with USB debugging on and off, no difference. Also tried 2 different usb cables.
Cyanogenmod Version: 10.1.1-mako
Build: JDQ39E
Thank you for any help!
Click to expand...
Click to collapse
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
vorbatello said:
What OS are you using? Windows? Mac? A linux distro?
Also, are you sure you're using MTP instead of PTP (Settings > Storage > menu > Usb Computer Connection) ?
You can try to install google's drivers from the android sdk as well.
Click to expand...
Click to collapse
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
jining said:
I am using Windows 7, it was set to PTP, I just set to MTP, but it still does the same thing. I have turned off my USB debugging in the developer menu as well.
Click to expand...
Click to collapse
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
vorbatello said:
I know this is a silly thing to ask, but have you tried rebooting your phone? Something like this happened to me before and a reboot fixed it.
Also, if you have a custom kernel, check that you have USB fast charge disabled. And after that fails, try installing google's drivers. Sorry, I'm just spouting out random ideas at this point.
Click to expand...
Click to collapse
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
jining said:
Thanks for the suggestions. I am using Franco kernel, how do I turn off fast charge?
Click to expand...
Click to collapse
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
vorbatello said:
Use trickster mod and go to the Kernel Specific page. If fast charge is ticked off, there's not much we can do from there.
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Also, have you tried to install google's drivers or make a nandroid and reflash a clean rom?
EDIT: You could also try Koush's universal driver: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I'm afraid I'm out of ideas at this point
Click to expand...
Click to collapse
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
jining said:
Hmm I am in the trickster mod on the kernel specific screen, but I don't see anything about USB fast charge Where might I get googles drivers? I can't seem to install any drivers because as soon as I uninstall the unknown device, it auto installs some drivers.
Thanks for the help!
Click to expand...
Click to collapse
So I tried installing the newest Franco kernel Milestone (3), and the USB fast charge is off. I also tried installing a different CM mod, but there is no difference. I also tried installing the universal you gave me, but that didn't work, and i installed the google driver from SDK and that didn't work.
I don't know what else to do...
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
maxiiik said:
Hi, try to completly unninstall ALL drivers for nexus, samsung or android related, than install official drivers for nexus 4 and then connect nexus 4. Should work.
Click to expand...
Click to collapse
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
jining said:
I tried that, no luck...I don't know what else to do, I have tried 3 different cables. I tried using the drivers that come with the nexus 4 toolkit, but no luck. It charges when plugged in, but i get nothing else. Also it seems like half the time its not even in the device manager as an unrecognized device, and then it intermittently pops up a window saying unrecognized device detected... maybe my USB port is broken on the phone?
Is there something simple I have overlooked to get 4.2.2 to work with my computer?
Click to expand...
Click to collapse
Have you managed to solve this? I'm facing almost the same problem!
No, I tried for hours with no luck. I am glad I am not the only one, hopefully a solution will come to us. I have been using airdroid to transfer files from my phone in the mean time.
Im also having the same issue except my computer only recognizes my phone when its connected as a camera.
Sent from my Nexus 4 using xda app-developers app
I am having a similar problem with my daughter's Nexus 4 phone, which is not rooted nor unlocked - it is still completely stock. It was just updated to Android 4.3, however I can't say that this is the cause of the problem because she never attempted to connect her phone to the desktop machine before.
I have a Windows 7 x64 box at home, and spent over two hours last night trying to get the computer to correctly recognize the Nexus 4 phone. I was hoping that the standard MTP Windows driver would handle it perfectly, but no luck. I tried the Google usb drivers, and the ADB interface was recognized, but still no access to the internal storage. I then gave the Naked Drivers a try, and no joy there either.
I am beginning to suspect that the MTP drivers on my desktop are munged, but do not relish the thought of a Win 7 wipe and reinstall.
Anyone else have any ideas?
Thanks much!
I am having a similar problem where I have USB storage set to MTP and Windows doesn't pick it up, whereas PTP Windows will pick up but I can't access any folders other than the camera related folders like DCIM.
So my workaround is doing it the old fashioned way through CMD in windows using adb push.
Example:
Assuming you have all the stuff you want to transfer in a folder called stuff, adb is located in C:\adb, and your folder known as stuff is also in C:\adb:
C:\adb>adb push stuff /data/media/0
The above command starting from the ">" will transfer all files in the folder called stuff to the root of /sdcard. In the N4, /sdcard is symbolically linked to /data/media/0.
Of course you need USB debugging enabled for this to work...
Device Manager (Hopefully this helps)
In the start menu type device manager, in that window you should see android and or something similar at the top. You want to drop the menu down and right click what should say Google ADB Interface and delete it, make sure you check the confirmation box. After reboot your computer! Once booted plug your phone in a viola!!!
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Roktgr said:
I'm having a similar issue.
I can open device manager but there in no Android anything listed. All that comes up when I plug my phone in is 'unrecognized usb device'. I have 5 different cable I have tired. The OS will only bring up the usb error in a USB 3.0 port. It will not do anything if I use the 2.0 port.
I have gone and tried to manually update the drivers through the device manager but when I select the drivers from Android SKD or any of the other driver packs I get an error that it is not a x64 driver.
I found one suggestion about modding the driver to include the device but windows will not even recognize the device other than a unknown usb.
I'm going to have a bricked computer soon. Any help would be appreciated.
Click to expand...
Click to collapse
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
First, Google universal naked drivers xda. Try those. If they don't work go into device manager and go to where it says let me choose drivers from my computer. Then look for the android composite adb interface.
If you're on win 8 you'll need to allow unsigned drivers. Google how to do that
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#1 is the phone doesn't do anything in USB debug mode. I keep seeing references to having to approve the computer connection but I haven't seen that yet. I have tired 9 usb ports. 6 on my main computer will not bring anything, not even the usb drive. 3 on the labtop will only bring up a 'unrecognized usb drive'.
Click to expand...
Click to collapse
Hello,
"#1 is the phone doesn't do anything in USB debug mode." This is normal!
How I experienced the USB debugging option is that, if turned ON:
1. The Nexus does not appear in my Windows env
2. BUT when in recovery mode, I can use the "adb" commands
If USB debugging turned OFF:
1. Then I CAN see the Nexus in my Windows env
2. BUT I cannot use the "adb" commands in recovery mode.
So you definitely need to have the USB debugging option turned off if you want to see your nexus in Windows, IMO
---------- Post added at 04:16 PM ---------- Previous post was at 04:02 PM ----------
Roktgr said:
Windows 7x64 on all machines. I am trying this on 2 work computers and getting the same result. I have 2 issues that I think are the root of the issue.
#2 is the computer will not recognize the device in anything other than a 'unrecognized usb drive' (UUD). Everyone keeps mentioning the Android Composite ADB interface. It's not there, it doesn't show up or as an option. I can go into the device manager and find the UUD and try and update the driver via the manual method with a disk but it doesn't list any type of hardware that is related to Android or ADB.
Click to expand...
Click to collapse
I think you really have an issue with the drivers. I would install the Google USB drivers. Maybe a bit heavy but then you can be sure that drivers are fine:
http://developer.android.com/sdk/win-usb.html

[Q] ADB not working in MTP mode

I'm wondering if anyone has run into this. ADB works fine if I have my phone connected and set to PTP. But if it is set to MTP, adb devices returns nothing connected. MTP itself still works fine to copy files over, and device manager shows the Android ADB device. It's not a huge issue to need to switch it, but it would be nice if there was a simple fix.
raptir said:
I'm wondering if anyone has run into this. ADB works fine if I have my phone connected and set to PTP. But if it is set to MTP, adb devices returns nothing connected. MTP itself still works fine to copy files over, and device manager shows the Android ADB device. It's not a huge issue to need to switch it, but it would be nice if there was a simple fix.
Click to expand...
Click to collapse
3 possible steps:
i) update SDK manager on your computer
ii) check USB debugging is..... well......checked in the phone settings
iii) update the drivers ( SDK manager or Google platform)
Another possibility is to ask your question in the window "search this forum of this thread.
Good luck
raptir said:
I'm wondering if anyone has run into this. ADB works fine if I have my phone connected and set to PTP. But if it is set to MTP, adb devices returns nothing connected. MTP itself still works fine to copy files over, and device manager shows the Android ADB device. It's not a huge issue to need to switch it, but it would be nice if there was a simple fix.
Click to expand...
Click to collapse
Hmm, it works fine for both of mine. I'd say try to uninstall and delete your ADB drivers, and reinstall them. Follow this thread
gunner1937 said:
3 possible steps:
i) update SDK manager on your computer
ii) check USB debugging is..... well......checked in the phone settings
iii) update the drivers ( SDK manager or Google platform)
Another possibility is to ask your question in the window "search this forum of this thread.
Good luck
Click to expand...
Click to collapse
Hey, while your reply was very informative and useful, you did not read his post properly. ADB works for him only in PTP mode. MTP doesn't work.
exb0 said:
Hmm, it works fine for both of mine. I'd say try to uninstall and delete your ADB drivers, and reinstall them. Follow this thread
Hey, while your reply was very informative and useful, you did not read his post properly. ADB works for him only in PTP mode. MTP doesn't work.
Click to expand...
Click to collapse
As surprising as it might be I did read the post.
My answer is based on my own experience. The Nexus 7 was seen in PTP mode but not in MTP.
To address the issue, after a thorough reading in the XDA forum and thanks to the knowledge of our Forum members, I updated the SDK manager and re-install the drivers.
Hope I answer your concern.
gunner1937 said:
As surprising as it might be I did read the post.
My answer is based on my own experience. The Nexus 7 was seen in PTP mode but not in MTP.
To address the issue, after a thorough reading in the XDA forum and thanks to the knowledge of our Forum members, I updated the SDK manager and re-install the drivers.
Hope I answer your concern.
Click to expand...
Click to collapse
Ah, my mistake. I'm sorry!
I did try searching but most of the posts I found were eith er than MTP was not working at all or ADB was not working at all.
I have uninstalled and reinstalled the ADB driver, but I will try completely removing the SDK next.
gunner1937 said:
As surprising as it might be I did read the post.
My answer is based on my own experience. The Nexus 7 was seen in PTP mode but not in MTP.
To address the issue, after a thorough reading in the XDA forum and thanks to the knowledge of our Forum members, I updated the SDK manager and re-install the drivers.
Hope I answer your concern.
Click to expand...
Click to collapse
This is 99% a driver issue.
I had a similar experience when first setting up my n4.
Debugging on = adb but no mtp
Debugging off = not and obviously no adb
I uninstalled the adb drivers where possible.
Plugged in with mtp mode on and debugging off
Let it automatically install mtp drivers
Switch debugging on
Wait for it to install what it can by itself then manually install the adb driver
Results in fully functional adb & mtp
Sent from my Nexus 4 using xda app-developers app
Well, uninstalling the SDK did not work. I was able to get it working. After uninstalling the ADB drivers and plugging the device back in I saw that the device was still showing up as the ADB interface. I repeated the process a few times and it eventually stopped appearing. After that I reinstalled the driver and everything seems to be working.
i have the same problem
everything works, including PTP, but MTP refuses to work
ther's no error, no missing driver, it just don't appear
i have tried a lot of reinstall and removals

Unable to recognize MTP mode on computer

So as a start to this, the phone is recognizable when running adb devices, I can see it listed there. However, when trying to use the phone in MTP mode, it tells me that there is not a suitable driver.
What I have tried so far:
Uninstalling device in Device Manager on Windows 10
Reboot both phone and laptop
Downloading the latest driver version from Google
Turning off USB Debugging on the 6P
Connecting phone
Attempt to use recently downloaded USB Driver on phone
So when all that is said and done, I get the following screens attached below.
https://imgur.com/a/gni6o
I also tried using this guide to find a MTP Device:
http://www.howtogeek.com/195607/how...evice-to-show-up-in-file-explorer-if-it-isnt/
But that does not exist in either the latest zip download of the USB drivers, or the Google SDK drivers.
I only have the option for:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Could anyone provide me with some ideas?
EDIT: I have also tried two USB cables, both have the same issue. The Nexus 6P OEM Cable, and the iOrange Cable.
slixzen said:
So as a start to this, the phone is recognizable when running adb devices, I can see it listed there. However, when trying to use the phone in MTP mode, it tells me that there is not a suitable driver.
What I have tried so far:
Uninstalling device in Device Manager on Windows 10
Reboot both phone and laptop
Downloading the latest driver version from Google
Turning off USB Debugging on the 6P
Connecting phone
Attempt to use recently downloaded USB Driver on phone
So when all that is said and done, I get the following screens attached below.
https://imgur.com/a/gni6o
I also tried using this guide to find a MTP Device:
http://www.howtogeek.com/195607/how...evice-to-show-up-in-file-explorer-if-it-isnt/
But that does not exist in either the latest zip download of the USB drivers, or the Google SDK drivers.
I only have the option for:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Could anyone provide me with some ideas?
EDIT: I have also tried two USB cables, both have the same issue. The Nexus 6P OEM Cable, and the iOrange Cable.
Click to expand...
Click to collapse
Nexus Root Toolkit has an excellent guide for straightening out Nexus driver issues. Very thorough. Works for me every time.
83097markcynt said:
Nexus Root Toolkit has an excellent guide for straightening out Nexus driver issues. Very thorough. Works for me every time.
Click to expand...
Click to collapse
Did not seem to help me. Still unable to to use my Nexus as an MTP device.
Bump, does anyone have a resolution for this? Have also tried from all the settings here:
http://windowsreport.com/windows-10-doesnt-recognize-android/
Going to wipe the phone soon, but would like to take some stuff off of it before doing so.
Both PTP and MTP mode don't work. I have tried installing the Windows Feature Pack, and the MTP package from Microsoft....
slixzen said:
Bump, does anyone have a resolution for this? Have also tried from all the settings here:
http://windowsreport.com/windows-10-doesnt-recognize-android/
Going to wipe the phone soon, but would like to take some stuff off of it before doing so.
Both PTP and MTP mode don't work. I have tried installing the Windows Feature Pack, and the MTP package from Microsoft....
Click to expand...
Click to collapse
Mine works with PTP mode but not MTP. Could it be Android N interfering? Would like to know how to resolve this matter as well.
having the exact same issues, anyone else have any ideas? did you ever get this resolved?
im going to smash something shortly and I never have in my life...heh
Nope, reinstalled Windows. That resolved the issue.
I had something similar happen. Try running this command at the dos prompt.
net localgroup Administrators local service /add
slixzen said:
Bump, does anyone have a resolution for this? Have also tried from all the settings here:
http://windowsreport.com/windows-10-doesnt-recognize-android/
Going to wipe the phone soon, but would like to take some stuff off of it before doing so.
Both PTP and MTP mode don't work. I have tried installing the Windows Feature Pack, and the MTP package from Microsoft....
Click to expand...
Click to collapse
Thx for getting back to me, I'm about to do the same thing...my windows update wont update anyway and its been pissing me off (not that I care besides OCD)
Now I just have to try to figure out what I need to do to reinstall the (free) windows 10 dealio
To the comment below, tried that, no idea what its supposed to do but didn't fix anything for me.

Categories

Resources