[Q] driver for USB tethering and mass storage - Hero, G2 Touch Q&A, Help & Troubleshooting

Hi
Is there a driver to install to be able to use USB tethering and the mass storage device function on my Hero? I don't care about ADB or HTC sync, I just want to share internet and copy files.
I use froydvillain 1.5 (android 2.2). It's for my friend's computer which is probably running Windows XP/Vista/7

I think its either built into windows, or in the adb drivers, as part of HTC sync.
I use tether with Froyd fine, so I can check my drivers tomorrow if needed

Well if I need to install HTC Sync or not is precisely what I am looking. I am going to visit one of my friend and he doesn't have internet. I wondered if I could just plug my hero in his computer.

Seems like windows xp only needs a .inf file and that vista and 7 already have the driver builtin (just like linux)
http://www.google.com/support/android/bin/answer.py?hl=en&answer=182134

Related

Newbie needs help with adb

Hi.
I'm trying to make some custom native software for android but I need some help getting started.
What I have done so far is getting a HTC Hero, GSM version.
Flashed a custom rooted ROM. update-hero-generic-2.73.405.38-rooted-signed.zip
Installed the sdk and ndk on Windows.
Downloaded and built the open source android project in a VMWare ubuntu image.
What I'm trying to do now is to get ADB talking to my Hero.
I have USB debugging on in the applications->development menu on in the Hero.
When I attach the phone to my XP PC it detects it and asks for drivers, I point it to drivers in android-sdk-windows\usb_driver, windows won't load them because they do not match the hardware.
I can install the driver manually but eventhough the device manager lists it as working (android phone with android composite ADB interface) adb cant find it.
adb devices just give me an empty list.
I tried this on a Windows 7 box and it seemed to work there, is there something special I need to do to get it working on XP?
Installing HTC Sync (drivers included) should resolve.
Thanks!
I actualy tried that before posting but it did not seem to work.
I now tried it again and this time I manually installed the driver in the HTC directory and now it works.

Wired Tether not working

I have CELB 2.7 installed with Cyanogen 5.0.8-DS, I have tried on both an xp machine as well as a windows 7 32 bit machine, neither works, I have installed the NDIS driver on windows xp, I turn on USB debugging, I turn on USb tethering inside the wireless/networks settings, I plug the phone in, it installed some drivers for windows 7, and windows xp. I manually installed NDIS into xp, but I dont see anything.
Im not even sure what is supposed to happen, am I supposed to see another network connection or something?
Also, do i need ADB installed for this to work?

[Q] ADB with CM7

Has anyone been able to access their touchpad via ADB on with CM7 Alpha?
If so, what's the trick. I'm running Win7 Pro 32bit, Android SDK is installed with the latest Java 1.7 and USB debugging is on and displayed in notification.
FYI - I'm used to using ADB with my droid eris on GSB so I've tried most of the known stuff. Are there ADB drivers for the TouchPad around?
Thanks in advance.
All ADB drivers are in essence the same, you should be able to use the official ones Google releases with any device.
To get ADB running with my TouchPad(Windows 7 x64) I had a USB Mass Storage Device with the hardware id(USB\VID_0BB4&PID_0C02&REV_0227) I had to go an change the device driver to a USB Composite Device, once I did that the ADB interface showed up and I was able to install the driver.
The mass storage device I changed was this one (USB\VID_0BB4&PID_0C02&REV_0227) and not this one (USB\VID_0BB4&PID_0C02&REV_0227&MI_00).
Here is a link to the Official ADB Google driver http://api.ge.tt/0/8FtSNo8/0/blob/download you may need to force the driver to install.
Worked perfect. Thanks!
adbWireless ftw. No need for cables/drivers.
https://market.android.com/details?id=siir.es.adbWireless&feature=search_result
This worked for me. No modded .ini file or driver needed.
It detected and installed the"USB Composite Device" automatically.
http://rootzwiki.com/topic/6622-cm7-adb-driver/
win7 x64

Stupid HTC drivers....

So I battled with the MTP drivers forever and gave up...at least Windows 7 was able to communicate/see the device. Then I installed winamp...
Now Not only does Winamp not find the HOX+ under devices, but windows doesn't see anything on the phone. It shows up as a driver under My Computer..but no communication with it is possible. I simply get a message saying the device is not present or has stopped working....
Anyone else have trouble?
i was having the same issue. what i found was that i had both USB 2.0 and USB 3.0 ports on my laptop, (windows 7 x64) which i wasnt aware of. switched over to USB 2.0 ports and it mounted as a cd drive, prompted to install software and installed all drivers. kinda crazy, but thats what i did.

Android 4.2.2 / CM10.1 and Windows 8 ADB Functionality

So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.

Categories

Resources