ADB Interface Error - Nexus 7 Q&A, Help & Troubleshooting

Hi,
Trying to get my Nexus 7 connected to my laptop running Windows XP (32bit), SP3, to allow me to root it.
I've downloaded the Nexus Root Toolkit and I've tried installing all the different drivers from there (USB Debugging is OK), and even the Samsung drivers.
Every time, I get a error on the android ADB interface (can't install). I can't post a picture yet (need 10 posts on here), but I get the following in device manager:
Android Device
Nexus (!)
Other Devices
MTP (!)
Any ideas where I'm going wrong? I think I've read somewhere that XP is difficult to get communicating.
Cheers.

Oh, and it tries to install wdtCoinstaller01007 as standard for a driver.
Have also tried *01009

I have the same problem.
I guess the MTP while in debugging mode is not important

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

No ADB mode, driver issue?

I'm Italian, sorry for my English.
A few days ago I unlocked the bootloader via Toolkit, rooted and flashed the TWRP recovery _.
But I had hard difficulty:
After driver installed, I unlocked bootloader, enable debugging and then NOTHING!
In practice, the N7 was recognized by windows 7 64bit only in FastReboot mode ..
I tried in every way possible, deleted and reinstalled the driver 50 times, restored windows to a previous point, installed the drivers manually tried without toolkit, but how ADB just do not want to know.
For hours I was still with the bootloader unlocked but without root, until came to my rescue a friend with another notebook but same windows 7 64. Load the Toolkit, install the drivers and everything goes perfectly, I do everything in 5 minutes.
On my laptop there is always the issue driver ADB, in the future I still need my PC recognized the N7 in ADB, how can I do?
One thing that I think is not well understood is that there is no "Generic Class Driver" for ADB nor for fastboot...
... even though the very driver that works for one mode (or phone/tablet device) may be perfectly fine with a different device. The wire protocol for both fastboot and adb are extremely simplistic.
So, what that means is that if the Hardware ID used by the USB device endpoint registers on the bus with a different VendorID/ProductID, Windows will (correctly) not use a previously-installed ADB driver, or previously installed fastboot driver - even though they would probably work just fine.
Here is an example. The Nexus 7 registers the following Hardware ID when ADB debugging is turned on in the OS:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
On the other hand, if you are using TWRP, it's adbd daemon shows up on the PC as:
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
This means that you might need to install a different driver for using the ADB with the OS, and a different driver for ADB under TWRP - even though it is exactly the same hardware on the other end of the cable! In the absence of a generic class driver for a given USB endpoint, Windows tries to match drivers in it's local (& internet) database based on this VID/PID pair.
If you have a look at the [ADB/FB/APX Driver] Universal Naked Driver 0.72 thread - and download it and have a look at it's included "android_winusb.inf" file - you will see literally hundred of different VID/PID pairs in the driver's android_winusb.inf file in the installer package, corresponding to many hundreds of phones/tablets. Same driver with hundreds of devices listed as compatible.
In the past I recall taking the Google (SDK) USB driver, and manually editing into place matching VID/PID pairs for a HTC phone into the .inf file. It worked perfectly; I probably flashed that phone hundreds if not thousands of times using the Google Driver (My PC is a Windows 7 Pro x64 machine btw).
Anyhow, I have pulled this stunt twice now - once editing the .inf file for the Google Driver, and I did it once with the Universal Naked driver too. You can choose which driver you want to start with.
If you want to give it a roll, you can start with any of those three drivers:
- Google (SDK) USB driver
- XDA "Universal Naked" driver
- Asus Nexus 7 USB Driver (Look under Download)
Note that since you are using W7 x64, make sure that you add each new entries to the .inf file twice - once in the ".NTx86" section, and duplicated again in the ".NTamd64" section. When editing .INF files, make sure to use an editor which preserves simple text file formatting - use "notepad", not "wordpad"
If you want a reference for what values to use, see the bottom end of this post. You should see exactly these same values in your Device Manager, however.
Note that if you see the device show up in the Device Manager as being correctly identified and marked as "working normally" - but it doesn't work - you should probably remove that driver and re-install from a different driver package.
This would certainly be the case for any drivers you saw associating with VID/PID pairs that look like:
VID_18D1&PID_4E40 bootloader/fastboot
VID_18D1&PID_4E41 single adb
VID_18D1&PID_4E42*&MI_01 composite adb
VID_0955&PID_7330 avx mode
VID_18D1&PID_D001 adb in TWRP (maybe CWM too, I didn't check)
That's a lot to throw at you, especially with Italian <=> English in the mix.
Feel free to ask questions.
bftb0
Hello,
I tried to follow your advice but I have not solved.
I'll explain what I did, so you can correct me.
-Uninstalled previous drivers (from device manager, control panel)
-Restart the PC
-Modified the inf file. Package Asus Nexus 7 USB driver (ntx86 and NTamd64 sections) attach screenshots
-Linked N7 (usb debugging actived)
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
I tried to change also too XDA "Universal Naked" driver by following the same procedure.
I tried to create another account on my pc, but no ADB!
View attachment 1734997
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Use "Google USB drivers" you get after you install from here http://developer.android.com/sdk/index.html
Its drivers work with 4.2.2
I got 4.2.2. rooted with ADB working now via only this and no other method
No problem with adb in 4.2.2... I tested yesterday (no need psw too...)
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Marco16V said:
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
Click to expand...
Click to collapse
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
bftb0 said:
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
Click to expand...
Click to collapse
When the drivers are not installed and I connect to pc N7, is only recognized as a portable device, then later recognized as Google Nexus 7.
To install the drivers (modified as described) I click reinstall driver, then later recognized (if connected to pc in android mode, with usb debugging actived) as Android Device in another voice, ADB interface. But is not recognized by the toolkit under adb devices, and even when I try using cmd.
1-When I install the drivers. seem to be installed correctly.
2-Sorry, where can I find Hardware IDs in Device Manager? What is the difference between OS adb and TRWP adb?
3 - In other pc (with same N7, same cable, same driver, same toolkit) I had no problems. I tried to change only the USB port.
4-I uninstall the driver from device manager (uninstall voice) and ask to be also uninstalled software from the PC
In some Italian forum, I found people with the same problems.
Solved by formatting PC. I would not do that ...
Thanks for your help, sorry for my English and my limited skills
AW: No ADB mode, driver issue?
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sdk but I have not solved.
I use Android 4.2.1. I'm having problems with the update! I can not update OTA (N7 stuck under the impending reboot). I also tried to download the zip file to upgrade the memory and flash it from recovery but the installation is not completed (error 7 build.prop).
I also tried to flash the factory image 4.2.1 (keeping userdata) and start again. Nothing, same mistakes!
Too many problems!
Marco16V said:
2-Sorry, where can I find Hardware IDs in Device Manager?
Click to expand...
Click to collapse
(Note I attached some pictures below)
From the Device Manager:
- Select the Device in question by right-clicking. Choose "Properties"
- A window with three tabs will appear: General, Driver, and Details. Select Details
- The "Property" combo-box-selector has 20 or 30 items - the 2nd one in the list is Hardware Ids. I attached two pictures from Win7-Pro-x64 (below)
But note as I said before: You should NOT be seeing the ADB endpoint under "Portable Devices" - if ADB Debugging is turned on in the OS, you should see it under "Android Phone" or something similar. In any event, the hardware Ids will identify it exactly
Marco16V said:
What is the difference between OS adb and TRWP adb?
Click to expand...
Click to collapse
Well, as far as the behavior of the USB driver on the PC, almost nothing. Unfortunately - for better or for worse - both TeamWin (TWRP) and CWM authors put their ADB interface on the bus with the VID/PID pair of USB\VID_18D1&PID_D001, whereas the OS puts all its USB interfaces on 18D1/4Exx.
So, even if you get a driver installed for the OS "adb" mode (say by using the Google SDK USB driver or the Asus Nexus 7 driver), it won't work for the custom recovery... unless you fix up the driver installer package to have the matching VID/PID pairs (18D1/D001) in the .INF file for that driver.
I think folks find this confusing - they think, "wait, I have a ADB driver installed" - why does it not work?
OK, there are a couple more things to try (at least before I give up). Roughly they try to answer these questions:
Q1) Is this a toolkit issue, or a driver issue?
Q2) Is it a prior driver you installed that you are not observing that is causing the problem?
The first one (Q1) is easiest to diagnose: when your PC Device Manager indicates that a device is "working normally" - AND THE VID/PID ID MATCHES WHAT YOU SHOULD EXPECT FOR THE MODE THE TABLET IS IN (regular OS, recovery boot, fastboot mode), can you communicate with the device from the Windows command line? e.g.,
Code:
C:\foo> cd C:\blahblah\sdk-platform-tools-directory
C:\blahblah\sdk-platform-tools-directory> fastboot devices
or
C:\blahblah\sdk-platform-tools-directory> adb devices
If you can communicate with the tablet from the command line - your device ID will be printed by the above commands, then you don't have a driver problem at all - there is something screwy about the way your toolkit is installed.
OK, Q2 -
When Windows installs a driver, it caches it into a kind of database. I suppose it is possible that a prior driver installation might be causing trouble. You can observe - from the device manager - all the drivers that are installed - even for devices that are not currently connected to your computer.
This is done by setting the "devmgr_show_nonpresent_devices=1" environment variable. It can be done semi-permanently this way, or for a single invocation of the device manager this way..
See the third image attached (devmgr-all-devices.jpg ) - it is my computer in that "show all devices" mode. See all that rubbish in there? It's from other Android devices (HTC, Samsung, etc).
You can walk through each one of those - even the devices that are not currently attached - and inspect the VID/PID pair to see if they happen to match the values that you are expecting to see for the different operating modes on the Nexus 7. I'll leave it up to you whether you want to do this or not; it is a bit tedious. Just don't start deleting drivers willy-nilly if you don't know what they are associated with.
Marco16V said:
Thanks for your help, sorry for my English and my limited skills
Click to expand...
Click to collapse
I am understanding everything you are saying - and your english is far better than my italian
good luck!

[Q] PC always try to install MTP drivers with N7

I have a Nexus 7 that used to be able to be seen (and trnasfer files) on my Win 7 64-bit Ultimate pc. It is not visible in Explorer now- think it happened after upgrade to 4.2.2
I have tried various ways and means from this site and others but still unsuccessful. My pc kept wanting to install MTP USB drivers everytime I plug the N7 into it even when I have it set as PTP; and the drivers always failed.
I downloaded the Universal naked Drivers and tried to install it as well but problem is that my device only show up as MTP USB (under portable devices) instead of as N7; and under that the drivers is always the failed MTP USB drivers. I cannot browse to install Universal Drivers here cos the pc will not accept it.
Really running out of my wits. Any advises please?
Thanks.
I had initial problems connecting to my pc after installing all the drivers from a toolkit. After searching, I followed a tip and installed pdanet on my phone and pdanet for android on my pc. Now I connect exactly like my phone or other storage with full access to the user storage on the n7 from the pc. Win 7 pro 64bit.

[Q] Nexus 7 USB connectivity to Windows XP SP3

Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
o82239 said:
try this...
http://forum.xda-developers.com/showthread.php?p=34608868
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Sent from my Nexus 7 using xda app-developers app
:-/
Is there any justice for me in this bad bad world of octa-core processors and Razer Edge!!! :'(
ansh360 said:
It worked, but the MTP keeps popping up for installation again and again.. and I am STILL NOT ABLE TO SEE MY DEVICE
Click to expand...
Click to collapse
??? It worked and it doesn't work ???
What worked?
Try to delete the precompiled inf-file 'C:\WINDOWS\inf\wpdmtp.pnf', edit the 'C:\WINDOWS\inf\wpdmtp.inf' (see link in the post in the top...), open the XP device-manager, right-click in the yellow '!' and 'update driver'...
twics said:
I have exactly the same problem with my windows xp laptop it was OK until I wiped my laptop and reinstalled xp SP1-3 I can't seem to solve it either.
Click to expand...
Click to collapse
Do you have edit the 'C:\WINDOWS\inf\wpdmtp.inf'?
Sent from my Nexus 7 using xda app-developers app
I had a lot of problems myself getting Windows XP to work with my Nexus 7 as well... eventually I discovered that installing the latest version of Windows Media Player fixed the problem.
I wrote up a post on this issue on another forum (Sorry, XDA - this was before I discovered you guys), back in December of last year.
Anyway, here is my original post...
http://www.nexus7nexus10.com/forum/nexus-7-help/2600-cannot-connect-pc-2.html#post36608
(Actually, this whole thread is worth reading.)
The only nuisance factor is having to remember to re-enable USB debugging (Titanium Backup needs USB debugging enabled, and complains if itsn't) AFTER I've run some MTP Windows XP related file backups (USB debugging needs to be disabled, or MTP won't work)...
....or at least that is my experience.
Hope this is of some use.
Rgrds,
Ged.
Hello guys,
I have the same issue on windows XP with Nexus 7. I tried everything what was suggested and nothing is working.
I have Windows XP SP3 with WMP11 and MTP porting kit installed as well. the device is recognized and driver is instaled fine. But it's not visible on "my computer" in MTP mode. I tried to turn on usb debugging and still device is invisible in windows explorer, the same is when usb debugging is turoned off.
When device is in PTP mode it appears in "my computer" and i'm able to browse it and see all pictures and photos.
How can i browse my device in MTP mode and copy files there? Please reply if anybody knows what to do to fix this issue.
Thank you.
ansh360 said:
Guys, I know i am repeating again the question but despite reading 15-20 posts and uncountable articles, I am still not able to get my nexus 7 working with the Windows XP SP3.
1) To start with, I downloaded the google drivers from ASUS and the MTP Porting Kit from microsoft.When i plug in the device with USB Debugging on, Windows shows 3 new devices- NEXUS 7 & Android ADB Interface.. and ofcourse Windows XP can not find the drivers for any. So i open the device manager and it shows Nexus 7 under unidentified devices. I install the drivers for ADB interface (the ones i downloaded from Asus) and the device becomes ready to use. But there is no option to browse the device from my computer or portable devices. Then i switch the debugging on, and now there is a new device- MTP under unidentified devices. Then i install the MTP Porting Kit, but the MTP device still shows a problem with the driver.
2) The second part of the problem is that all this did not work and even my WMP11 does not recognise the Nexus 7.
The device is just connected and charging!!! What am i doing wrong here???
Click to expand...
Click to collapse
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Taowtp said:
Recently got a 2012 Nexus 7 from a retailer selling this model with updated Android at very attractive price, and initially able to connect to computer so promptly rooted the device with the Nexus Root Toolkit from Wugfresh Development (in this forum), afterwards had same problems with not being able to read / transfer files.
Tried every fix I could find in other threads, and although device manager saying that connected as 'ADB Device' with debugging on, or 'Google Nexus 7 ADB Device' with MTP on and debugging off, still stuck with no access.
Looking closer at the MTP configuration ('Google Nexus 7 ADB Device') under device manager noticed that details listed manufacturer as 'ClockWorkMod' , and eventually that this originated within a Windows\Inf file titled 'oem60'.
I cut and pasted the 'oem60' file to another directory (to keep it safe just in case this upset something else) then on reconnecting the Nexus 7 as MPT with debugging off, device manager found and installed the correct driver at last. Now able to see and transfer files to / from it.
Presumably could alter the relevant lines in the 'oem60' file, which aren't hard to find, and put it back to original directory, but my other devices also working fine so not done so as yet.
Click to expand...
Click to collapse
The above workaround was spot on, thanks

[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