has there been a release yet to get ADB to work on windows 7? or a way to get it to work?
Yes the ADB install works from the site, the issue is the drivers. Which can be circumvented by adding these lines to the android_winusb.inf file in the usb_driver folder
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
That I believe is what fixed it for me.
Edit: actually just unzip this file to your android-sdk-windows\usb_driver folder, because you have to add it in two different places and its too early in the morning to explain it.
Or install HTC Sync. That's what helped me because it installed the drivers I needed for me...
http://www.htc.com/us/support/droid-eris-verizon/downloads/
es0tericcha0s said:
Or install HTC Sync. That's what helped me because it installed the drivers I needed for me...
http://www.htc.com/us/support/droid-eris-verizon/downloads/
Click to expand...
Click to collapse
It didn't work for me hence the fix that I use.
I've been running ADB on all 3 of my win7 pro machines for the past few months. Installed HTC Sync from the HTC site and also did the USB fix to the file mentioned above. I would say make sure you've got the latest version of HTC sync and try again.
edit: Disregard I can't read.
Thanks for the input. Out of town atm and ill get the crap working when I get back
Sent from my FroyoEris using XDA App
Related
Does anyone know how to get the ADB to work? I tried downloading the usb_driver from Android SDK but that didn't help.
ADB works the same way with the eris as with any Android based phone. You may want to tell people what operating system you are using to get things started.
Assuming you meant windows ( usually thats the case ) you first want to download the htc driver. There are two out there, the 32 bit one and the 64 bit one. This is what I meant by what operating system. Once you have picked a driver, you want to go into your device manager and apply that driver to the ADB device where it is listed by clicking the "update" driver button.
You need the HTC Sync software.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
you can get the one in the sdk to work by adding the Vendor and Product ID to the .inf file. i had to do this to get it to work with the leaked 2.1.
esmith972 said:
You need the HTC Sync software.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
Click to expand...
Click to collapse
You don't need that. The USB driver can be downloaded through the Android SDK.
GrdLock:
While you can download it from the SDK, the version made by HTC in the Sync program is alot easier to install as it puts the driver files in the correct places on your windoze machine to auto-install.
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
ihtfp69 said:
In case anyone still needs this
Click to expand...
Click to collapse
Thanks. It took a while to find this post
Before I rooted (when phone was at 1.5), it connected to ADB just fine. Now that it's running 2.1, it won't recognize it. I've re-updated the USB stuff through the SDK too.
ihtfp69 said:
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
Click to expand...
Click to collapse
Big thanks!!!
ihtfp69 said:
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
Click to expand...
Click to collapse
will try this
paOol said:
will try this
Click to expand...
Click to collapse
Worked perfectly. Definitely try it
ihtfp69 said:
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
Click to expand...
Click to collapse
Thanks! Once I did this I used Device Manager to install a driver for the ADB Device with a yellow exclamation mark. Windows detected the phone and now my "adb devices" command shows the phone.
I don't need HTCSync as I using :MyPhoneExplorer
I don't need the full Android SDK as I'm not a dev but I'm using ADB and fastboot.
So I proceed like this to install HTC driver +ADB/Fastboot without additional files:
HTC Driver:
Double clic on setup_3.0.5579.exe (dwnld from HTC support site)
Choose the language and clic next (stop when it list the things to install: air,...)
Go to c:/user/yourname/AppData/Local/Temp
Order the files by date and choose the last folder created (so the temp folder were the files were extracted for the full package install)
Delete all *.prq except the ones for the drivers (3 files, 2 if you choose between x86 and x64)
Clic next in the HTCSync install box.
All deleted prq will be 'installed' but in fact no
Check... only drivers are installed
nb: do this if you don't have a sense ROM and don't need HTCSync of course.
Hope this will help
ADB:
Download the SDK, open it with 7zip and take the 'tools' you want
nb: 7zip can't open the HTCSync.exe so the driver extraction was not possible for me. If you can access the files in th exe you may get the driver directly. Not good enough in IT (and/or not enough time to search for the right tool).
Hope this will help
truc007 said:
I don't need HTCSync as I using :MyPhoneExplorer
I don't need the full Android SDK as I'm not a dev but I'm using ADB and fastboot.
So I proceed like this to install HTC driver +ADB/Fastboot without additional files:
HTC Driver:
Double clic on setup_3.0.5579.exe (dwnld from HTC support site)
Choose the language and clic next (stop when it list the things to install: air,...)
Go to c:/user/yourname/AppData/Local/Temp
Order the files by date and choose the last folder created (so the temp folder were the files were extracted for the full package install)
Delete all *.prq except the ones for the drivers (3 files, 2 if you choose between x86 and x64)
Click to expand...
Click to collapse
Nice hack truc. Worked for me. Editing the Google USB driver didn't work because it complained the hash on the .inf files was corrupted. I'm on Windows 8.
So I used ECLIPS3's master app to root my phone (worked great by the way, thanks ECLIPS3 ) But now whenever I plug my phone back in with USB debugging on, it won't find the drivers. Even when I have it look in the USB drivers folder I installed with the Android SDK. I tried removing it with device manager and reinstalling, but still didn't work. I guess it's not that big a deal since I have root now and can just flash the roms from sd card. But I'd still like to know if there's a way to fix this just in case. Never know when you might need it
I didn't use the master app but I did have the same problem with my last rom update. My quick solution was to update the android_winusb.inf file in the usb_driver section of the sdk (there are a couple of ways to correct this problem- this was just the easiest at the time).
I added this line to the [Google.NTx86] section:
; HTC Eris After 2.1
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
You may have to check the DeviceInstance Id in your device manager to see what ID to use if this line doesnt work.
Thanks for the help! But I already found a work around. I read that if you downloaded htc sync it would put the drivers where it needs to be and install automatically, which it did. But thanks anyway
Everything was cool on my old 32 bit win 7 computer. I got a new computer, and I can no longer see my Archos 101 G9 in windows explorer. I can get adb to connect fine, but it can be tedious for transferring lots of files. Anyone successfully get this to work on 64 bit windows 7 for anything more than just adb?
I hate commenting that I don't have this issue. Do you have the latest media player? At least I remember that media player includes the mtp drivers. If you look at device manager, can you identify the tablet? If yes, you could try removing the tablet driver. After that the next time you plug your archos to your PC it should reinstall the drivers.
You can also Google apps that enable UMS. SGS3 easy ums works on my phone. I haven't tried them on my tablet, though.
Sent from my GT-I9100 using xda app-developers app
I wonder if there is some other driver issue. It keeps pretending that it's my GS3 that's plugged in, and I can't figure out how to convince it otherwise. It also doesn't get the MTP part, and AFAIK I have the latest WMP installed, however, that doesn't recognize the device either.
ProfLonghair said:
I wonder if there is some other driver issue. It keeps pretending that it's my GS3 that's plugged in, and I can't figure out how to convince it otherwise. It also doesn't get the MTP part, and AFAIK I have the latest WMP installed, however, that doesn't recognize the device either.
Click to expand...
Click to collapse
So your archos appears as GS3? Delete the driver/device from device manager. Maybe it will get right driver after that.
Sent from my GT-I9100 using xda app-developers app
That's just it: I tried uninstalling that, and removing the drivers, and it still shows up like that, even after a reboot. I'm going to try to track down the specific files in the S3 driver and remove them manually this evening, maybe that will help.
Try a different USB port if possible. Win doze sometimes gets this area wrong.
Sent from my ARCHOS 80 COBALT using xda app-developers app
ProfLonghair said:
Everything was cool on my old 32 bit win 7 computer. I got a new computer, and I can no longer see my Archos 101 G9 in windows explorer. I can get adb to connect fine, but it can be tedious for transferring lots of files. Anyone successfully get this to work on 64 bit windows 7 for anything more than just adb?
Click to expand...
Click to collapse
If you can connect with ADB then the device is set to use developer Debug mode.
Go into settings on the Archos tablet and turn off the Debug mode and then it should try to connect normally as a MTP device. You then may need to turn off or reboot both the computer and tablet before connecting it again.
Also, when trying to un-install a USB driver you may need to have it plugged in for it to show up in Device Manager. Then when you select to uninstall the driver you need to unplug the device and reboot the computer to allow it to clear out the old driver first.
Oddly though, on mine, it still works with the tablet set in either mode, but I do not have any ADB driver installed on my Win 7 64bit computer (yet), nor do I have any drivers for a cell/smartphone installed on it either. So, could be some other driver conflicts from other things on your end.
win 7 64 bit
I had the same problem, Archos has the wrong info.
[Google.NTx86]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
[Google.NTamd64]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
&PID_1509 is the correct identity for G9 tablets. Thank cajl for providing the fix. Link to post. --> http://www.modaco.com/topic/347961-anyone-got-good-adb-drivers-for-g9-80/
stevemp said:
I had the same problem, Archos has the wrong info.
[Google.NTx86]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
[Google.NTamd64]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
&PID_1509 is the correct identity for G9 tablets. Thank cajl for providing the fix. Link to post. --> http://www.modaco.com/topic/347961-anyone-got-good-adb-drivers-for-g9-80/
Click to expand...
Click to collapse
Not sure what that's all about, but I had just downloaded the ADB USB Driver right from the Archos website and it worked in both Windows XP and Windows 7 64-bit. Here's roughly the same sections as you listed, but from the .inf file from Archos:
[Google.NTx86]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1501
... several other things here
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
... several more things here
[Google.NTamd64]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1501
... several other things here
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
... several more things here
Notice that it has 1501 in the first line of each section, but then has 1509 in the line further down. Don't really know what difference it makes (nor do I really care) because the ADB USB Driver file from Archos worked fine for me.
But the original poster said ADB was working... just could not get a 'normal' MTP connection to work for transferring files. Which makes no sense at all unless they have developer Debug mode turned on in the tablet set. If Debug mode is not on, then both Win XP and Win 7 should just automatically find and install an MTP driver (since that's the crappy file transfer method Microsoft wants everyone to use).
The MTP drivers just auto-magically installed on both of my computers by just plugging in the USB cable to the tablet (with Debug off). So, I have no idea why the original poster (and several other people) have problems with getting that side of things to work.
Good luck figuring out what's going on with that. Sorry I can't be of any help because I've never had that problem.
Got it!!!!!
I deleted two files from c:\winsows\system32\
WinUSBCoInstaller.dll
WinUSBCoInstaller2.dll
and, in c:\windows\system32\drivers
I had removed
WUDFRd.sys
(actually, renamed to WUDFRd.bak, but whatever)
and restoring that one file, with deleting the other two, and I can see the stupid thing now!
Thank you for the attempts at help. I saw tons of different things on tons of different sites, not 100% sure which which one caused me to rename that file, but hey, it's working now, and that's the important thing.
I have an el cheapo RFTech M109S tablet http://www.geeks.com/details.asp?invtid=M109S I've found drivers to get windows to recognize it (it comes up a s samsung tablet) but adb fails to see it.
I've tried start/stopping adb, different USB ports, different drivers (have not yet tried a different PC, don't have access to one). So my next step would be to modify android_winusb.inf and add in the correct VID and PID for this tablet. Does anyone know what these are?
Or has anyone run into the same issue with this tablet and managed to solve it?
thanks!
It never fails
after 2 days of searching and 30 minutes after I posted my question, I found my answer. Here's the steps in case anyone else has this POS.
The drivers I found are here ADB does not recognize the device.
For rooting I used the [RK29][TOOL] Root RK29 Tab Toolkit The drivers in this thread did not work, and initially the tool did not work. So I copied
;RockChip SDK
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006
from the android_winusb.inf in in the RK29 thread and pasted it into the inf I got from kmods.net. Even though adb does not see the device the RK29 toolkit was able to root the device.
falconae said:
after 2 days of searching and 30 minutes after I posted my question, I found my answer. Here's the steps in case anyone else has this POS.
The drivers I found are here ADB does not recognize the device.
For rooting I used the [RK29][TOOL] Root RK29 Tab Toolkit The drivers in this thread did not work, and initially the tool did not work. So I copied
;RockChip SDK
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0006
from the android_winusb.inf in in the RK29 thread and pasted it into the inf I got from kmods.net. Even though adb does not see the device the RK29 toolkit was able to root the device.
Click to expand...
Click to collapse
Had this problem too with my Acer device glad its fixed for you
svensonic1 said:
Had this problem too with my Acer device glad its fixed for you
Click to expand...
Click to collapse
Now if I can just find a ROM that will work on this cursed thing...
Anybody with a working link for correct drivers on Windows (I'm on 8.1)?
Thank you! And merry Christmas!
gorman42 said:
Anybody with a working link for correct drivers on Windows (I'm on 8.1)?
Thank you! And merry Christmas!
Click to expand...
Click to collapse
Take the normal ADB Drivers you allready got and do the following:
(This worked out for me just fine)
1. Swipe from the right to open the charms bar.
Tip: If you have a keyboard, use WIN+I and then skip to Step 3.
2. Tap or click on Settings.
3. Tap or click on Change PC settings at the bottom of the charms bar.
4. Choose Update and recovery from the list of options on the left of the PC settings window.
Note: Prior to Windows 8.1, choose General instead and then skip to Step 6.
5. Choose Recovery.
6. Locate Advanced startup, at the bottom of the list of options on your right.
7. Tap or click on Restart now.
Wait through the Please wait message until Advanced Startup Options opens.
Click to expand...
Click to collapse
Ehm... my problem begins at "take the normal drivers you already got. I don't have the drivers.
gorman42 said:
Ehm... my problem begins at "take the normal drivers you already got. I don't have the drivers.
Click to expand...
Click to collapse
i cant post outside links...
replace the DOT with a dot... xD
www dot mediafire dot com/?nwr2j8i7t7dh9f3
Rev 6 USB drivers needed for Fire HD6
gorman42 said:
Anybody with a working link for correct drivers on Windows (I'm on 8.1)?
Thank you! And merry Christmas!
Click to expand...
Click to collapse
In terms of using Android SDK manager to get the drivers, some of the old links out there for user defined sites will download old drivers which won't work on the HD6. I found the Rev 6 Kindle Fire USB driver was needed for correct install and ADB of the HD6 4th generation.
Use user defined add-on site s3 dot amazonaws dot com slash android-sdk-manager slash redist slash addon.xml
http://kindle-sdk.s3.amazonaws.com/2ba63011a73a0a0d0f35e001696677ec92a825cb.zip
yep, it's quite true that the .../redist/addon.xml has updated info for the newest drivers. ("newest" meaning, sept/oct 2013, since that's what all the files inside are actually dated)
I am so utterly sick of every single "guide" saying how getting the USB/ADB drivers is so "easy"........ "just install the entire ginormous spamazon-modified SDK/NDK! it's fun!"
I don't want the stupid sdk. I don't want a bunch of bloat I'm not going to use, and god knows what else it's doing. I also don't want to DL a possibly-skeezy .exe (no offense) from random intarwebs dropbox-type-sites.
all I (and I think many of us) want is:
- adb, fastboot, etc. binaries (I like this one)
- adb usb drivers
I don't get why every mfgr needs their own "special drivers" (well some of the nvidia stuff can get weird) - it used to be that the generic Google ADB/composite driver worked on so many more phones. and the fact that Win7 used to be surprisingly cool about making that happen automagically.
not to mention the fact that my HD6 (and plenty of other devices) work 100% with adb in linux, and I think they are all just using basic generic libusb. (speaking of which, I really ought to have tried using Zadig first on Win7, before wasting time on KindleDrivers.exe. zadig is some pretty neat stuff for getting a proper generic libusb driver in Windows.)
and even the the KindleDrivers install binary failed every single time I ran it - right at the very end. but at least it left the driver folders for me to play with. which was, like, 95% close enough, at least...
I had to end up changing one of the 64-bit entries in android_winusb.inf:
basically just changed the 06 to F2, in 2 places. since back in 2013, 1949:00F2 HD6 was nonexistent or something.
Code:
; For 64-bit os
[Amazon.NTamd64]
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
to
; For 64-bit os
[Amazon.NTamd64]
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_00F2
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_00F2&MI_01
and then device manager finally did what it was supposed to.
Thanks for the .inf clue
tarvoke said:
I had to end up changing one of the 64-bit entries in android_winusb.inf:
basically just changed the 06 to F2, in 2 places. since back in 2013, 1949:00F2 HD6 was nonexistent or something.
Code:
; For 64-bit os
[Amazon.NTamd64]
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
to
; For 64-bit os
[Amazon.NTamd64]
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_00F2
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_00F2&MI_01
and then device manager finally did what it was supposed to.
Click to expand...
Click to collapse
Thanks, this just saved me more slogging and it is really appreciated.