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
Related
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city?
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
akashi said:
I am trying to connect my Nexus 4 to my PC and use the ADB commands. I have the following problems:
ADB driver is installed and "USB Debugging" turned on the Nexus 4. Device shows up on Device Manager, however "adb devices" does not list the device and unable to communicate with the attached device.
The Nexus drive, regardless of MTP or PTP disappears from Windows Explorer when "USB Debugging" is turned on, Turning off "USB Debugging" brings back the drive.
USBView shows the device with a RED light, but it appears working on Device Manager.
I do not have this problem with my other laptop and desktop.
Using Windows 7 x64 Ultimate and Nexus 4 - Stock 4.2.2
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
heat361 said:
I had sort of the same problem, try uninstalling the driver in device manager, then unplug and replug your USB. Then when you plugged in the USB go to device manager and right click on the device and click scan for hardware changes. See if that works.
I'm not sure if this is a problem caused by windows update or the new updated SDK, but it has been a big problem for me.
Click to expand...
Click to collapse
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
I really do not want to reinstall Windows!
Thanks.
Click to expand...
Click to collapse
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
heat361 said:
OK try right clicking on the the device in device manager and choose update driver, then Browse my computer, then let me pick From a list of devices. After choose have disk on and find the file where your USB drivers are and click next. It may prompt you that windows can't verify the publisher Just click install this driver software anyway.
See if this works.
Click to expand...
Click to collapse
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
Try pointing the path to the Google drivers in the android-sdk in device manager and not the naked drivers.
akashi said:
I have tried installing the drivers from the latest SDK and also the "Naked Drivers" found here: http://forum.xda-developers.com/showthread.php?t=1996051
Still have the problem.
Click to expand...
Click to collapse
This is what I did and waited for the PC to install the adb drivers.
I plugged the phone in and with the USB plugged in turned it off while holding the volume up and down keys. This made my nexus 4 go into download mode and the PC automatically installed the adb drivers. After I just unplugged and held the power button to restart the device hope this helped.
Sent from my Nexus 4 using xda premium
akashi said:
Thanks for the quick reply.
I tried your suggestion but it did not solve the problem. After re-plugging the USB, Windows listed the device as "Nexus 4" and did not find any drivers for it. I manually installed the Naked Drivers (proven to work on my laptop and desktop) but still facing the same problem
Thanks.
Click to expand...
Click to collapse
When you uninstalled what's there now, you did make sure to check the box that will remove the old drivers from your PC?
Just in case, HERE is another source for the drivers.
dinhume echoes
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
akashi said:
Thanks to everyone for their help.
Just to confirm I have already tried:
Uninstalling the ADB driver via Device Manager and selecting "Delete the driver software for this device" and rebooting.
After reboot, Windows could not locate any drivers and I manually selected the drivers found inside the SDK (08/27/2012,7.0.0000)
The device shows up on Device Manager as working but does not work with adb commands. However, fastboot commands work!
I tried the above with the Naked Driver and had the exact result.
If I boot into the bootloader, I am able to run fastboot commands perfectly!
I have already ruled out my USB port as it works perfectly on VMware.
I am thinking my Windows 7 is messed up somehow and re-installation is looking like the only solution :crying:
Click to expand...
Click to collapse
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
El Daddy said:
4.2.2 requires updated adb and fastboot. It looks like you have an older version.
Click on the ota help desk link in my signature. The new version is attached to the first post. Replace the old adb and fastboot files with the new ones. Then try again.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks. I tried version 16.01 and still have this problem.
The problem is whenever I uninstall/install the ADB driver or disconnect/reconnect the USB, **ONLY** the "Nexus 4" appears on the Device Manager which I manually install the ADB drivers to. There is not a second "Nexus 4" on the Device Manager for the MTP or PTP.
On my laptop when I remove all drivers and reconnect the USB cable, I always see 2 "Nexus 4" listed on Device Manager. One for the ADB interface and the other for the MTP or PTP.
Please help!
Any ideas please?
Any Solution to ADB connection problems?
Hi was there any solution to this, as I seem to have the same issue.
I have tried different drivers and MTP & PPP modes as well as loading the PDAnet drivers and software.
Each time now I take care to remove all the drivers and also delete the drivers in all modes (Android running and Bootloader running)!
MTP & PPP load different copies of the drivers.
I can get either "Nexus 4" showing up in the device driver or "Google ADB Interface" or Android ADB interface" according to the driver loaded.
I can see the device when Android is running ie "ABD Devices" gives me the serial number and connected, then I can send an ADB command "adb Reboot-bootloader" the Nexus then reboots into the bootloader screen, the device driver changes to the bootloader driver (installs if not installed) however then I loose connection to the Nexus phone! "ADB Devices" returns none connected.:fingers-crossed:
I also tried unplugging and plugging back in the phone in bootloader mode but do not get adb to see the handset or it to react to commands.
I'm just about ready to try a toolkit to see if I can get past this roadblock!!!
Current computer is Win7-x64
This weekend I will try on a different computer.....Win8-X64
All comments appreciated
That's because you cant use adb when in boot loader. You use fastboot
Sent from my Nexus 4 using xda app-developers app
I have same problem on my work laptop DELL when my custom desktop machine works just fine with both Nexus 4 and 7. :/
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
akrabi said:
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
Click to expand...
Click to collapse
Did you enable usb debugging?
Also check that you have an option selected under Settings>Storage>USB Computer connection, not having either MTP or PTP selected there will also bork adb.
If you still can't get it to work, try Koush's universal drivers: Link
still not working...
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
akrabi said:
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
Click to expand...
Click to collapse
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
taodan said:
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
Click to expand...
Click to collapse
Ok, so I'm with my Nexus connected as an MTP device, with the driver from XDA installed (see attached image), USB Debugging enabled:
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
C:\>
Any advice???
Anyone has any advice??
I really have not idea what to do. Tried everything...
Thanks
Works on a different computer
I've connected the phone to my borther's PC and installed the drivers from the SDK. It worked without any problem.
I really can't figure out why it's not working on my laptop.
[Solved]
OK...
So as I said before I tried connecting when PTP is checked and when neither PTP nor MTP are checked and on both couldn't install the drivers properly (neither from xda nor from sdk).
What worked for me:
1. Uncheck both PTP & MTP
2. Device Manager -> Nexus 4 -> Update Driver Software -> Browse my computer for driver software
3. Now instead of browsing to the location I went to "Let me pick from a list..."
4. It should show a list of devices/manufacturers. Clicked "Show All Devices"
5. On the bottom right click "Have a disk"
6. Point to the android_winusb.inf file from Android SDK
7. Choose Android ADB Interface from the list
8. Let driver install
Click to expand...
Click to collapse
Hoped it will help someone.
Thanks to everyone that tried to help. :good:
Hello guys!
I have already read some topics on this forum but it is my first message.
As indicated in the title, I cannot connect my Nexus 4 on my computer using MTP. This computer is running Windows 8.1 Update 1. So far I have tried every method I have seen on the web so I am a little bit desperate.
I have tried to plug my device on other computers and it was automatically detected on Windows 7, Windows 8.1 Update 1 and Ubuntu 14.04.
On my computer, as it does not auto-configure MTP I have tried to install ADB drivers, hoping it would help me. Universal ADB drivers, Naked Drivers and drivers from the SDK didn't changed anything. I also tried changing USB port.
It always recognised my phone as a "Nexus 4" in the "Other devices" section of the Device Manager (I do not have "Android Device" section), except in when MTP + debugging are activated. Then I have both "Nexus 4" and "MTP", in "Other devices" section.
It does not work in PTP mode either and I also tried uninstalling/reinstalling the Nexus Root Toolkit, even if I do not see how it can help...
One last point: I have the "connected as multimedia device" notification on my Nexus 4 when MTP is activated, even if it's not recognised by Windows.
Do you have any idea of what I can do?
Have you tried Nexus 4-specific drivers? Try following this guide.
Marvlesz said:
Have you tried Nexus 4-specific drivers? Try following this guide.
Click to expand...
Click to collapse
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Bartimoot said:
I have already tried to follow this guide, it just helped me to install ADB drivers but I still don't have access to the content of my Nexus from my computer. I just tried it again, just in case. No changes
Click to expand...
Click to collapse
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Here is another post from another forum that has something you could try:
still1 said:
ttwiitch said:
still1 said:
1. make sure Settings ->Storage -> Menu[3 dots on top right] -> USB Computer Connection is MTP
2. USB debugging is disabled (if you ever enabled it)
3. make sure the drivers installed is MTP drivers rather than adb device(you do this when you unlock/root nexus)
point 3 is important. thats the reason why its not getting detected
Click to expand...
Click to collapse
2. Where in setting do I check for USB debugging?
3. How do I check this? (I'm not rooted)
Click to expand...
Click to collapse
2. developer option.. if you have not enabled developer option then you wouldnt have enabled USB debugging. so skip this
3. Connect your nexus to PC-->Go to Control panel-->device manager
you will see something like Android adb in device manager
Right Click and click "Update device Software"
Click "Browse your Computer for driver Software"
Click "Let me Pick from a list of device drivers on my Computer"
Click Next, for the device list shown.
Click to expand...
Click to collapse
Tell us how it goes..
Thank you for spending some of your time to help me Marvlesz, I really appreciate.
Marvlesz said:
Last time I had such an issue: I uninstalled the drivers using Device Manager, then installed the drivers from that guide, plugged in my phone and it worked..
Click to expand...
Click to collapse
Yes, I saw it worked for a lot of people, for what I have read, but it seems that I am not that lucky
When picking from the list, I tried from the Android Device section and it displays "Unable to find any drivers for this device". Same Results in “Mobile devices”.
When I try “Show all devices”, I have a lot of possibilities. I just tried “MTP Device” from both “Standard MTP-Compliant Device” and “Standard MTP-Compliant devices” sections, and it displayed “The install class is not present or is invalid”
Am I cursed?
I was wondering, is it possible that the problem is coming from my hardware? Or its drivers? (Those for the motherboard maybe?)
EDIT: I just found this thread : http://forum.xda-developers.com/showthread.php?t=2493734
I will try it and I will keep you updated when it is done.
EDIT 2:
So I tried the solution... and it worked! :good:
I had the N version of Windows 8.1, mainly to avoid useless software like Windows Media Player, and it was the exact problem.
Sorry for taking a little of your time, and thank you again!
No problems, I'm glad you had it fixed.
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.