After using Nexus Root Toolkit cannot connect in regular USB mode - Nexus 10 Q&A, Help & Troubleshooting

I have used Nexus Root Toolkit twice successfully on two different computer, but on both occasions that has left the computer unable to connect to the Nexus 10 outside debugging mode.
I think it is "Step 1" in the driver install guide that tells me to:
2.) Launch Device Manager using the button bellow.
- Identify whatever device resembles your Nexus and right click it
- Select 'Uninstall'
- Check the box for 'Delete the driver software for this device'
- Select 'OK'
3.) Unplug your device and Launch USBDeview using the button bellow
- Use USBDeview to uninstall any;
- Android ADB Interface device's,
- Samsung USB devices,
- Google USB drivers
- ... or ANYTHING else you see that resembles your Nexus.
- In particular look for devices with Vendor ID
- "18d1" or... "04e8"
- Simply right click these devices, and select the option to:
- "Uninstall Selected Devices"
Click to expand...
Click to collapse
After doing this i can no longer connect the Nexus 10 as usb drive or/MTP. If i connect it, it simply says charging, and the Windows device manager doesn't list any new devices at all. Its like it isn't connected at all. If i enable usb debugging, i can use Nexus Root Toolkit without problem.
The computer in question is running Windows 8.1, and i first installed the Universal drivers that didn't work, and then got it to work with RAW drivers.
I assume that something got uninstalled that shouldn't have been, but i don't know what. Any help is appreciated, i don't fancy reinstalling windows

Related

[Q] adb Mode/usb developing mode does not work

I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.
It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with
erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse

Nexus 4 cannot be recognized as MTP after root

I'm running Windows 7 64bit and followed the Ultimate guide to unlock and root my Nexus 4.
Everything went well but now it looks like that Windows won't recognize my phone as a device. When I plug in the phone, the auto-play window will pop out and recognize it as Nexus 4, but there is no other options. (Normally the auto-play will ask if open folder to view files or transfer photos). I can't see my phone in device manager either.
If I turn on the USB debugging mode, I can see it in device manager but still cannot see it in My Computer. Looks like Windows can't access the SD card at all.
I tried switching to the camera mode but the problem remained. Please help.
desperate bump. can anyone help?
Maybe it's a stupid advice, but have you tried change the USB port in PC?
glancer2315 said:
desperate bump. can anyone help?
Click to expand...
Click to collapse
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Colourkey said:
Maybe it's a stupid advice, but have you tried change the USB port in PC?
Click to expand...
Click to collapse
yes, i did.
abaaaabbbb63 said:
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Click to expand...
Click to collapse
thanks for your advice. the problem is that, without USB debugging mode on, I can't see Nexus 4 in Device manager, even though the Windows Auto-play will say Nexus 4 connected. (Nothing in My Computer either)
With USB debugging mode on, I uninstalled the driver and Windows would try installing the driver. Now it shows up as MTP device with an exclamation mark. I tried manually update the driver (direct it to the Google SDK folder and pick the android_windowsusb.inf) but it says it does not support x64. I don't think the 64 bit driver is digitally signed.
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
SovereigN7 said:
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
Click to expand...
Click to collapse
i did and it remains the same.
Is there anyway I can know all the files names of the drivers so that I can manually delete them from system folder? When I uninstalled it from the device manager, I don't see the option "Delete the driver software for this device".
I can still see it under "adb devices" list.
I think there are some conflicts in the drivers.
Now when I connect Nexus 4 (without USB debugging mode on), it will show up in device manager under Android Device.
With USB debugging, it will then show up under Portable Devices.
However, it's supposed to work the other way around. that is (no USB debugging --> portable device; with USB debugging --> Android Device).
How can i solve this?
Have you tried manually installing the drivers before plugging in the phone, vs letting windows choose the drivers it wants to install? One option you could try is installing PDA Net on your pc. It will install reliable drivers on your pc.
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Alex240188 said:
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Click to expand...
Click to collapse
thank you for your long and detailed reply.
this is what i wanted to do, but the problem is that when I uninstall them, I don't get to see the option "delete the driver software for this device". What should I? cuz every time I plug in Windosws just tries to automatically install the driver for me.
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
glancer2315 said:
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
Click to expand...
Click to collapse
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Alex240188 said:
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Click to expand...
Click to collapse
hi, adb devices works. (will list my device when usb debugging is on)
with usb debugging off, under portable device, the device status says "This device cannot start. (Code 10)". thanks.
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
glancer2315 said:
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
Click to expand...
Click to collapse
I have this same issue I'm trying to find a fix, that's how I found your thread. Alex gave very good info make sure you go back to his posts and hit his "Thanks" button, I did it on everyone one of his posts in this thread. I'm starting to think it's a hardware issue and not a software issue, I've never had this issue on any device. When I got it new running stock 4.2.2 MTP didn't work. ADB works and PTP works, just not MTP no matter what I try. I recommend you learn to use, ADB push and pull to move your files if you don't already know how to use it (To use ADB I need to check PTP for it to work and not MTP) you might need to do the same. I will keep you posted if I find a fix.
Sent from my Nexus 10 Pimpin AOKP 4Life
I'm just getting more and more confused with this.
If Adb works then you must have an Adb driver installed for the phone. However your also stating that you get no box for uninstall driver.
With USB debugging disabled you said that it appears as an android phone rather than a portable device. This should not be.
With debugging disabled what happens if you Try to uninstall in device manager
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
My theory still stands that you have updated the mtp driver with adb drivers. Hence why mtp doesn't work but ptp does.
The problem is getting to a position where you can uninstall the adb drivers from the mtp device and let it reinstall the proper drivers
Sent from my Nexus 4 using xda app-developers app
I plugged another Nexus 4 in, and all the drivers loaded perfectly. I then tried my Nexus 4 phone, and nothing happens. No mtp, no adb, no boot loader drivers. Its my phone. My next step is to find a zip file that I can flash via custom recovery, which will bring all the binaries and ROM back to stock. Anybody know where I can find this? I'll probably lose the custom recovery, but hopefully it will be fixed and I can flash the custom recovery again.
LG-E960

Nexus 4 not showing up in my computer as MTP Storage

Hi Guiz, So you all probably have heard this a million times but i have tried every i can to fix this. I have tried many options such as Deleting and re-installing the drivers, trying a different usb port 2.0 and 3.0 I have restored my phone. And my phone only comes up as PTP Camera which is useless since i cant root my N4. This problem occured after i updated to Android 4.3. So my question is how can i make my N4 show up as MTP Storage?
I'm running on Windows 8. Thanks in advance.
Zypent said:
Hi Guiz, So you all probably have heard this a million times but i have tried every i can to fix this. I have tried many options such as Deleting and re-installing the drivers, trying a different usb port 2.0 and 3.0 I have restored my phone. And my phone only comes up as PTP Camera which is useless since i cant root my N4. This problem occured after i updated to Android 4.3. So my question is how can i make my N4 show up as MTP Storage?
I'm running on Windows 8. Thanks in advance.
Click to expand...
Click to collapse
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
I've been trying to solve this myself, i thank you!!! Finally!!
danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
Thats the problem it doesnt show up.
Zypent said:
Thats the problem it doesnt show up.
Click to expand...
Click to collapse
I also have this problem, my nexus 4 won't show up in device manager (windows 8) it will make the noise and will only show up in my computer if I have usb debugging enabled and select media device, any other combination it won't show up in device manager or in my computer.
What do I do?
foliage said:
I also have this problem, my nexus 4 won't show up in device manager (windows 8) it will make the noise and will only show up in my computer if I have usb debugging enabled and select media device, any other combination it won't show up in device manager or in my computer.
What do I do?
Click to expand...
Click to collapse
Today i've got my new Nexus 4, succesfully unlocked & rooted with this toolkit, but had problems with installing google usb drivers and Universal Adb Driver.
The solution is based on several steps.
I solved my problem this way, hope it will help someone
I have windows 8.1 64-bit, so i had to solve firts the problem with driver signature
1.
How To Disable And Bypass Driver Signature Enforcement In Windows 8
Tutorial link
Tutorial video
If you have problems with driver installations, try this:
2.
Remove hidden existing Nexus 4 or Android Nexus ADB Interface in Device Manager
i had to cleanup the drivers remained after few failed adb driver installations because of the problem in the first step
- (OPTIONAL) Install Nexus Root Toolkit and run it
- (OPTIONAL) click on Full Driver Installation Guide and at step 1
- open Device Manager, click View and select the option Show hidden devices
- now you will see some additional hidden devices (greyed out)
- because i wanted to install the drivers from start i deleted them, that means uninstalled them and added checkmark for deleting local files
- screenshot is attached so you can better understand
Remove the devices that could make problems
3.
- Run Nexus Root Toolkit
- click on Full Driver Installation Guide
- at Step 1 open USBDeview
- in my situation i deleted all the entries with google name
- screenshot in the attach
Final step:
4.
Install drivers for Nexus 4
- Run Nexus Root Toolkit
- click on Full Driver Installation Guide
- at Step 2 i installed Solution #1 - Universal drivers
- maybe you'll need to manually add drivers, if you have an entry in Device Manager that as yellow !
- right click on it - update drivers - browse my computer for drivers - I've added the path to installed Solution #1 - Universal drivers
"C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
- i repeated it for connection as mtp, ptp and none of that - selection for this is made on nexus: settings - storage - ... in the right upper corner - usb computer connection. so this way the device had installed the needed drivers
- screenshot is added in attach
I've used Wugs Toolkit for installing drivers and after that unlocking and rooting the Nexus 4.
My problem was that there was present HIDDEN ADB Interface under Android Device, after above mentioned steps, my nexus is working properly when connected as MTP device
danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
Brilliant!!!
Not showing up in device manager
danielms22 said:
1 quick Forum search would easily have solved this for you.
But since you're here:
1. Enable USB debugging: Go to phone settings -> About -> Tap build number repeatedly until developer menu is enabled. Go there and tick USB debugging.
2. On your PC, go to your device manager (when the Phone is plugged in and set to MTP), locate the phone, right click on it -> properties
3. go to the Driver tab
4. click Update Driver
5. click Browse my Computer for driver software
6. click Let my pick...
7. select USB Composite Device
8. finish up with the assistant
9. be happy
Click to expand...
Click to collapse
I am also facing this issue since flashing 5.0. It doesn't even come up on device manager. Any suggestions?
amj2403 said:
I am also facing this issue since flashing 5.0. It doesn't even come up on device manager. Any suggestions?
Click to expand...
Click to collapse
same here ==

How to regain mtp access for usb file transfers

Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
For me turning off adb and reconnecting the cable fix the issue. Try it and report back.
Please ignore my spelling mistakes. English is not my native language.
Yes, but I now have both abd and mtp.
My rooted Nexus 7 (2012) previously had no problems connecting to my Windows 7 computer and I was able to transfer files via the USB without any problems. After installing Android 4.4, I am only able to get it to connect via the PTP option (camera files only). I downloaded the latest Nexus 7 driver from Asus' web site and tried the above step to no avail. After several hours of eye strain from perusing the forums, it's time to ask the experts. Thanks in advance
EDIT: Finally got it to work after following the instructions on this thread: (Took several tries)
http://forum.xda-developers.com/showthread.php?t=1934306
zzvelik said:
My rooted Nexus 7 (2012) previously had no problems connecting to my Windows 7 computer and I was able to transfer files via the USB without any problems. After installing Android 4.4, I am only able to get it to connect via the PTP option (camera files only). I downloaded the latest Nexus 7 driver from Asus' web site and tried the above step to no avail. After several hours of eye strain from perusing the forums, it's time to ask the experts. Thanks in advance
EDIT: Finally got it to work after following the instructions on this thread: (Took several tries)
http://forum.xda-developers.com/showthread.php?t=1934306
Click to expand...
Click to collapse
Dd you thank the post author?
Anderson2 said:
Dd you thank the post author?
Click to expand...
Click to collapse
I just did (Never really noticed that feature before)
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
I followed this advice, but didn't work for me. However, I then chose the 2nd option, "USB Composite Device", updated that and Voila! The "Unknown Device" with yellow warning still appeared, but I deleted that and all is good, thank you.
simple fix turn usb debbugging off
So your computer can install the driver for u
It worked!
Anderson2 said:
Many nexus 7 (and I believe nexus 5) users have had the annoying problem of losing the ability of their windows pc recognizing the nexus as a mtp device. In my case this happens every time I have to root the device. Something about installing the necessary adb drivers seems to mess up the ability of Windows 7 to install the correct driver for mtp access. Typically, the nexus will connect in ptp (camera) mode but not ptp. Updating the android phone driver just doesn't change anything. I tried all the recommended steps but nothing worked till now. Here is what worked.
After rooting, my Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it was an entry for "Google nexus ADB interface".
**there was NO entry for "portable devices" **
1. In device manager, with the nexus connected via usb cable, I clicked on the "Google nexus ADB interface" (inside android phone entry) and selected to update the driver, then selected "browse my computer for driver software", chose "c:\Windows" and - this is what is different - selected **let me pick.... **
2. The resulting options included 2 choices, but no mtp option, and I selected "Google nexus ADB interface"
3. When it installed, suddenly "portable devices" appeared in the Windows device manager with nexus 7 in it !! But with the yellow error symbol.
4. Next, I right clicked on the "portable devices /Nexus 7" entry and updated it as usual. Yellow error icon disappeared and now mtp works fine.
The important points are that
- standard 'update the driver' does not restore the mtp driver (perhaps because the correct Windows driver is in a different location and has an older date), but selecting one of the 2 offered choices in **let me pick.... ** within the c:\Windows\ directory worked to recreate the entry for "portable devices" and when that was updated, mtp connection was restored and I could copy and transfer files via usb cable!
Hope this helps someone else. Thank you Vyom for verifying this worked and refining my description to make it more precise.
Click to expand...
Click to collapse
Lots of thanks! It worked... I can now connect my rooted Nexus 7 under MTP mode!
zzvelik said:
My rooted Nexus 7 (2012) previously had no problems connecting to my Windows 7 computer and I was able to transfer files via the USB without any problems. After installing Android 4.4, I am only able to get it to connect via the PTP option (camera files only). I downloaded the latest Nexus 7 driver from Asus' web site and tried the above step to no avail. After several hours of eye strain from perusing the forums, it's time to ask the experts. Thanks in advance
EDIT: Finally got it to work after following the instructions on this thread: (Took several tries)
http://forum.xda-developers.com/showthread.php?t=1934306
Click to expand...
Click to collapse
I've been trying to fix this issue for way too many damn hours. Thank you so much for coming back to your own post and putting in the solution. This has been driving me CRAZY. Happy holidays

[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.

Categories

Resources