Related
Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?
Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.
Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.
just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.
Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02
Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!
Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.
Hello everyone,
So I've installed ACER's adb drivers, but when I connect the tablet to my computer it shows up as an MTP device. I've tried updating the driver and manually browsing to the driver's location, but windows says that driver is not compatible with my device? BTW: I am running a fresh install of Windows 7 64-bit.
Any tips would be appreciated.
Thanks!
I'm having the same issue. It seems like everyone else's Iconia "just worked" with adb.
I've tried installing the acer drivers. It puts a folder in my Program Files directory...but I don't see what I'm supposed to do there. There's "EUUDriverInstaller" but when I click on it nothing (seems to) happens.
When I plug the device in it uses some generic Microsoft driver to show the device contents but composite adb doesn't show up at all like it does for my Droid.
I've reboot several times on both device and laptop. I've uninstalled / reinstalled the application that made that driver directory.
I opened an application in the driver directory under the x64 folder and it opened up the windows driver installer and installed some drivers...but still no composite adb when I plug it in.
It was called "dpinst" and installed:
Linux Developer Community Net
Acer, Inc (androidusb) USB
Google, Inc (WindUSB) USB
then a couple others about a modem and ports
It is on usb debugging and I've toggled it on and off.
It's running 3.1 stock and I'm on x64 Windows 7
Both command prompt adb devices is empty under "List of devices attached" and Eclipse devices is empty.
My sdk is fully updated.
Curiously it appears Acer hides the driver if you specify Honeycomb 3.1
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
apapousek said:
If you're going to be playing around with development, I highly recommend installing a Linux distribution. Android is built upon Linux, and there are quite a few development tools which just work better under it. Anyway, if you try Linux, the udev rules for the iconia are:
UBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="user" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="user" #ACER
where you replace "user" with your username, but keep it in quotes.
Click to expand...
Click to collapse
I appreciate the suggestion, but I'd rather not install another partition just to adb connect this tablet.
Some additional differences I've noticed.
It seems like the tablet is going straight to mounting if that means anything. Connecting my Droid doesn't bring up the Autoplay menu while connecting the tablet automatically asks me how I want to access the data in the autoplay menu. It does *say* usb debugging is on, but no "ACER composite ADB interface" appears in my device manager.
Edit:
It seems like my situation is comparable to this guy in regards to the device just being treated like a flash drive. forum.xda-developers.com/showthread.php?t=734139 He says the rom was the problem...but I can't see why this stock rom should have an issue.
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
I'm too on Windows 7 64bits and for the drivers I go to http://support.acer.com/us/en/product/default.aspx
If you want I have re-upload the drivers on my 4shared
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
bpivk said:
I had the same problem on my Windows 7 computer.
The solution is simple. Just go into Devices and Printers or whatever it's called (the one where you see the printers, cameras,...). My version of Windows is in my native language so I don't know the exact name but you'll find it. You won't see the option in Device Management so don't search there. I found the proper location by accident.
Then you'll see the Acer icon and mine had an exclamation mark on it. So I right clicked on it and updated drivers (point the new drivers to Acer driver directory that holds adb drivers). Acer has to be in USB debugging mode (option under settings).
ADB then worked for me and it was a lot less hassle that I had with using ADB on my HTC Desire.
I'm used to all the different quirks when using computers but I do agree that Linux always worked best with ADB. So far I had to think of creative ways to set ADB on my Windows computer. No Android device ever installed drivers in the same way or even worked until I messed with it a little.
Click to expand...
Click to collapse
I don't seem to have another icon. I have this one referring to the Iconia Tab, but when I right click on it it just treats it like a flash drive.
I can't link the picture yet (need to have 8 posts), but there is on "Acer Iconia Tab" in Devices and Printers, but there's no yellow exclaimation mark and when I right click it it just has the option to browse files, it treats it like a flash drive.
It's under "Unspecified"
EVEALEX62 said:
I'm too on Windows 7 64bits and for the drivers I go to
EDIT : [Had to remove URLS to quote]
Just extract and launch the setup
have a good day.
PS : Sorry for my poor English
Click to expand...
Click to collapse
I've downloaded those drivers, unzipping them, and ran the setup several times =/.
EDIT:
I feel like a tool, someone at stack overflow suggested I switch to a different port (not just unplugging / re-plugging it into the same one), I guess that finally told windows to reanalyze it. Should have figured it would have been something silly for such a basic problem, shame on me for keeping all my other ports full.
Thanks for the help everyone!
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
EVEALEX62 said:
Sorry I have forget to say :
1) click right on the "!" and choose uninstall. (on device manager)
2) Unplugg the USB
3) Install the setup (post above)
4) replugg the USB and wait for Windows install the drivers ...
Click to expand...
Click to collapse
That worked! Thanks.
Figured it out
Hey guys,
Thanks for all of your suggestions, but none of them worked. I ended up having to disable automatic driver installation, then went into Windows\System32\DriverStore\FileRepository and deleted the folders corresponding to the drivers that windows kept on insisting I wanted. After that everything worked great!
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
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!