(help) Nexus 6p MTP/PTP not working - Drivers refuse to install - Nexus 6P Q&A, Help & Troubleshooting

I just upgraded "(downgraded") to a smaller case. i was using an Asus 170m plus motherboard. Now i have an Asus z170i mobo. On the old mobo my nexus was seen with no issue, however, i did have to utilize some device manager wizardary to get adb and fastboot to work. This time around on the ITX board, i had no issues getting ADB or Fastboot to work but it will not install the required drivers for my 6p.
I have updated the drivers with Android SDK. I've even went as far as downloading Huawei drivers, MTP drivers and Intel Android Drivers. I have tried different cables. No luck. I have searched this issue and found no one with the exact issue i have. No matter what i choose, PTP or MTP it will not install. I can uninstall drivers, and switch to charging and back to MTP/PTP - it will just not install.
For whatever reason the phone shows up under MTP portable devices, as well.
This phone works on my old build and my computer at work. I am stumped.
Anyone have any ideas or has seen this before?
Issue here:
http://imgur.com/a/Cf5wq
EDIT * i think this is a USB port issue.. Not sure why. I have plugged into 2.0, 3.0 and 3.1. Just went over to another computer in the house and it worked instantly.

The issue was resolved by entering this into cmd: net localgroup Administrators local service /add

Related

Problems connecting via MTP

Ok so a little background. After hearing about the Carbon backup app a while ago I decided to install it and followed the instructions to do so. One of these steps is to change the normal USB drivers to the ATB ones from the Android SDK. I did this and it all went well without a hitch. However I came to add some movies on to my nexus 7 today and it would only recognize my device in PTP mode (as per the Carbon app requires). I proceeded as normal but found that I could not create a new folder for my films. When i tried i was faced with this error:
However I found that I could create a new folder in one of the existing sub-directories so I proceeded with that. I started copying the movie files over and got another pop up looking like this:
After clickking yes I was soon faced with another error screen:
This happens for nearly every video file i have tried to transfer. I have tried uninstalling the ADB drivers and letting windows install the default drivers it used the first time, however now it will not find any driver software for my nexus 7 unless I point it to the ADB drivers. Whenever I try to connect my device as an MTP device instead of PTP windows will not recognise it and nothing will show up in my computer. Is there any way that i can defer back to the default drivers and use my device on MTP instead of PTP?
Just for a bit of extra info, the same problem is occurring on my nexus 4.
Thanks
Hmm, i have adb drivhttp://forum.xda-developers.com/showthread.php?t=2214386alongside stock drivers for mtp as im sure many do n do not face this problem.
Have you uninstalled the backup app and cleaned the registry?
Try going in to device manager and enable 'show hidden devices' and search for any leftover usb drivers or interface that might interfere with the stock drivers. As a last resort you can download your usb chipset drivers, then uninstall all chipset drivers and usb devices including those hidden, then reinstall the chipset and other drivers u may need. Eg.printer drivers, then try again.
Previously i had a sony erricson phone and it's SE's software screwed up the usb interface n i wasnt able to connect anythin thru usb mtp. That helped me. Alternatively, if u have system restore on you can try restoring to a date before this all happened.
Also, check your device for any apps or settings that might interfere usb functions like usb debugging altho it's rare. Not sure what you did but you might have semi/permanently broken some settings in the device...if you had an earlier backup which was flawless, try restoring to that first. Remember to play safe when doing all troubleshooting, windows isnt exactly smart with device drivers =< worse case you have to reset both the usb drivers and device if nothing works...
Unrelated but might help http://forum.xda-developers.com/showthread.php?t=2214386
Or
http://forum.xda-developers.com/showpost.php?p=39752670&postcount=5
i faced the same problem last week. what i do is go through step by step like what nexus root toolkit suggest. start from scratch. remove all previous drivers and reinstall. Follow to the letter what it says. So the problem is just probably of a bad driver stuff. Remember to restart too.

[Q] ADB will not connect to new nexus 7

I just got a brand new Nexus 7 and I went to root it with the nexus 7 toolkit. Long story short the Nexus's serial number would not show up under the attatched devices.
I have tried uninstalling the driver, reinstalling both the driver provided by the nexus 7 toolkit and asus. Neither work. Interestingly eclipse will not connect either.
Device manager shows the adb interference as working however adb will not return a connected device.
I also tried putting the nexus into ptp mode and using adb even though I did not do that with my previous nexus 7. When the Nexus is in PTP mode device manager will not allow me to install drivers for the adb interference. Which is odd since I thought if I installed adb drivers once I wouldn't have to again.
EDIT: I should also add that adb in fastboot and stock recovery works. I was able to try reflashing the device with a stock nexus 7 ROM but it didn't work. Still couldn't connect to abd while android was booted. Also I noticed that my old nexus has both mtp and adb available at the same time. However the new nexus only allows one or the other. E.g. I can't access the files system while adb is enabled and vice versa.
Do you guys have any idea why this is happening? My old nexus works fine.
theaftermath said:
I just got a brand new Nexus 7 and I went to root it with the nexus 7 toolkit. Long story short the Nexus's serial number would not show up under the attatched devices.
I have tried uninstalling the driver, reinstalling both the driver provided by the nexus 7 toolkit and asus. Neither work. Interestingly eclipse will not connect either.
Device manager shows the adb interference as working however adb will not return a connected device.
I also tried putting the nexus into ptp mode and using adb even though I did not do that with my previous nexus 7. When the Nexus is in PTP mode device manager will not allow me to install drivers for the adb interference. Which is odd since I thought if I installed adb drivers once I wouldn't have to again.
EDIT: I should also add that adb in fastboot and stock recovery works. I was able to try reflashing the device with a stock nexus 7 ROM but it didn't work. Still couldn't connect to abd while android was booted. Also I noticed that my old nexus has both mtp and adb available at the same time. However the new nexus only allows one or the other. E.g. I can't access the files system while adb is enabled and vice versa.
Do you guys have any idea why this is happening? My old nexus works fine.
Click to expand...
Click to collapse
I will be watching this thread as am having the same issue right down to working fine in ptp or camea mode, but am unable to click and drag files to the device. And similiarily to you, have no problems with the 16g nexus only the 32. I am using skippen's toolkit.
A possible solution.
aircooledbusses said:
I will be watching this thread as am having the same issue right down to working fine in ptp or camea mode, but am unable to click and drag files to the device. And similiarily to you, have no problems with the 16g nexus only the 32. I am using skippen's toolkit.
Click to expand...
Click to collapse
I forgot I made this thread. I have since since solved the issue and have both mtp and adb at the same time with this particular nexus 7.
First of all installing new drivers on my windows 7 installation was causing a problem. So I backed up and reinstalled. However, while that solved other problems it did not solve my issues with the Nexus.
After a lot of fiddling I finally got it to work by using the official google usb driver. http://developer.android.com/sdk/win-usb.html
Now here's the thing. I discovered that windows treated each combination of adb+mtp or adb+ptp, adb alone, mtp alone, and ptp as a seperate device. So while they all might use the same driver windows considered them different devices.
So basically what I did was install google's driver whenever a combination of usb modes did not work correctly. So in adb+mtp (which is what I really want to be able to use) I went to device manager found my nexus 7 under android devices or whatever it is called and installed the the official google driver. It proceeded to tell me there was an error but then it proceeded to work perfectly. The error may have been just my computer acting up because of all the drivers I'd been installing/uninstalling trying to get this to work.
Also, when you go into device manager and try to install the usb driver you typically right click on the device, select update driver and then click search computer, browse to the folder containing the driver and install. Sometimes that would fail for me, windows would say I already had an updated driver. Thankfully I did find a workaround that forces windows to install the driver you want to install no matter what.
When you get to the part where you browse your computer for the driver click let me pick from a list of device drivers on my computer. Then there should be a button that says I have the disk. Click on that browse to the folder with drivers, say yes to any warnings and continue.
If the I have a disk button does not appear and instead a list of possible manufacturers or devices shows up just click on one of the entries. Then the I have the disk button should appear.
The danger with forcing windows to install the driver you want is that you can install any driver for anything and possibly damage something.
Hope this helps!

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 drivers not working

Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Re
Hi Ghosta,
Are you using a USB 3 port? as i have had many strange issues with these the ports. The issue is caused by one of the intel drivers cant remember exactly which way but there is no easy way to fix this. If this is your issues i would try and find if you have a USB 2.1 port you can use or the Esata ports on laptops tend to be usb 2.1 inside...even though they dont look like it haha
Hope this helps
ghosta12 said:
Hello. Im new to the Nexus 10. I downloaded skipsoft Android toolkit, installed adb drivers in the package and rooted the Nexus and installed recovery..it was easy using the toolkit. So the ADB drivers must have worked- at least in the environment it is used in to do these things. But these drivers dont work to transfer files between the nexus and the computer running winxp. I have USB debugging and PTP, have tried every other dirver package that has been mentioned on all available forums, have tried different usb ports, different cables etc. n my computer the device is recognised as a Nexus 10 but clicking on it gives a blank page, so cannot see the Nexux files. WTF this is driving me mad. Any ideas?
Click to expand...
Click to collapse
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
peterk-1 said:
What does Device Manager show? Device name, its Properties and exclamation mark?
You do know that if your device has a "password" then you must be logged in to see its contents.
Click to expand...
Click to collapse
Thanks for the replies and suggestions. All shows up OK in device manager, the device is not password protected, and the laptop has usb2 ports. I had another try today, after connecting the nexus it shows up in my computer as a camera, labelled nexus 10, with the camera icon. When I click on the icon it opens a special folder, must be a camera folder and the camera and scanner wizard starts. After a while it detects the photos on the nexus ( I have loaded a lot on it via USB otg using flash drive ), but thumbnails of the photos are not downloaded as I usually see when I connect a camera. The wizard downloads photos back to the computer, but each photo is about 18 kB instead of the 2 mb they originally were. So it appears a connection is happening, but a very strange one. I don't like to be beaten on problems like this one, but searching the net has not given me any answers, and I don't understand the android system well enough to know what to try next.
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
peterk-1 said:
I think your device is working. If you connect it up as it now is and then go into Settings > Storage and tap the top RH corner menu you get the USB Computer Connection and select that and change it to MTP you should find it is now visible in My Computer or after auto install of the driver it will be visible. I'm brain dead - you said you had a PTP connection!
Click to expand...
Click to collapse
No PTP conection or MTP connection either. The Nexus also shows up in Device Manger under Imaging Devices when USB deugging is on, which is causing the camera and scanner wizard to start, although it doesnt work properly. When i disable it nothing happens at all. No idea where to go from here.
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
peterk-1 said:
There is or was an issue with XP see http://forum.xda-developers.com/showthread.php?t=2305943
Click to expand...
Click to collapse
Thanks for the suggestion, I had already tried that but I did it again just to make sure. It did not work for me.
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
capnkrunch said:
Have you tried following the driver install guide from Wug's toolkit? I've never used Skipsoft's but if it doesn't have you delete old drivers properly it's possible there's some old or corrupted driver sticking around from all the installs you've done. If you follow Wug's guide exactly you should end up with the only the correct drivers installed. Also, what ROM and kernel are you using? It's possible the issue is there.
Click to expand...
Click to collapse
I used a program called usbdeview to uninstall every USB driver with an "android" or "adb" description which should have cleaned up my drivers? Then after reinstalling drivers I tried again no difference. I ran android-tools and can push and pull files to and from the computer and nexus, (from command line) so I believe I have eliminated hardware problems and software problems on the nexus. This leaves the computer, which works perfectly with my other android devices running 4.1.1.
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
peterk-1 said:
Just in case this helps. In usbdeview I have 5 nexus 10 entries. They all have the vendor id of Google 18d1 and a unique Product ID . Which driver connects is related to the device settings:
PID Device settings
4ee1 MTP
4ee2 MTP + USB debugging
4ee5 PTP
4ee6 PTP + USB debugging
d002 USB debugging
With the device connected I can change settings and see the change in connected driver in USBDeview.
Click to expand...
Click to collapse
This info does provide me with some way forward. With USB , when connected ptp I have a nexus 10 USB composite device and a nexus 10 digital still camera connected with the green light in USB deview, and also a blank device name, connected, description android composite device with a purple light. I'm guessing purple means not working. But changing drivers does nothing to change the purple light. Switching to mpt gives an additional blank name Google nexus adb interface also with purple light shown as connected. All connected devices show vendor 18d1. Drivers tried 1) clockworkmod (supplied with skipsoft); 2) naked drivers 3) Google drivers. Any clues what to try next?
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
peterk-1 said:
2 things to check. I just tried running usbdeview from Wug's toolkit. It was v2.0 and wasn't the same as the version I have installed v2.3 - and there have been a significant number of changes. If you have XP pro x64 then you must use the x64 version of usbdeview - again I think Wug's may only ship with 32 bit usbdeview http://www.nirsoft.net/utils/usb_devices_view.html You will also find an explanation of the coloured radio buttons.
If you find you need to update usbdeview then I would suggest you uninstall the device drivers (instructions in Wug's toolkit?) then new drivers from http://developer.android.com/sdk/win-usb.html#top and follow the linked install instructions.
Click to expand...
Click to collapse
I gave up completely on this, and connect via wifi using ES file explorer. I bought my wife a new tablet an Acer Aconia A1-830 and it has the same problems, impossible to connect via ADB, with exactly the same symptoms. Yet our phones connect via ADB without a problem, but both are Androild 4.1 or earlier and the tablets 4.2 or younger. Obviously an Android generated problem that arose when 4.2 was released and on which has no fix.

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