Hi,
I recently bought my first Android phone, an HTC Hero, from a helpful eBayer here in the UK. When I got the phone, it had already been rooted and had a custom ROM, v4 RC1 of EzHero, installed.
I want to update this custom ROM to v5.1, because there are some problems with the current version that's installed. (For example, the phone doesn't ring because there are no ringtones installed! Also, the camera doesn't work, and the phone crashed and rebooted whilst I was in the middle of a call last night.)
So, after some reading around on these forums, I tried following the instructions on this thread: http://cleanimport.xda/index.php?threads/709220/. The basic first step is to download the SDK from Google and instruct it to download the USB driver. So far so good. (I am using Windows 7 BTW.)
However, I have been unable to get the USB driver installed correctly, such that when I run the command:
Code:
adb devices
I get nothing back. (Not strictly true -- the first time I ran it it said it was starting a daemon, then said something like "devices list", but listed no devices. The second time I ran it, it didn't mention the daemon, but still didn't list my device.)
When I connect the phone to my computer (via USB, and with USB debugging enabled), I basically get a balloon at the bottom right of the screen to say that it is installing drivers, and then it says it had some problems. It lists out several devices, each with a green tick or a red cross against them. Invariably, one of the devices listed is called simply "ADB", and it always has a red cross against it. I am not specifically prompted to point the system towards any drivers for the device.
If I go into Device Manager, I currently see, under "Other devices", three devices:
- ADB
- Multimedia Controller
- Multimedia Video Controller.
The icon for each of these has a little yellow exclamation mark. If I double-click on ADB, I am given the chance to Update driver. Doing this gives me two options, and I choose "Browse my computer for driver software". This prompts me to "search for driver in this location" and I choose "C:\android-sdk-windows\usb_driver". (I have also tried pointing it to the subfolder "i386", but this gives the same result. I am on a 32-bit Intel system.) There is also a checkbox "Include subfolders", again I have tried both options, and both lead to the same outcome.
I then click Next and receive this error message:
Windows was unable to install your ADB
Windows could not find driver software for your device.
[...]
Click to expand...
Click to collapse
If, instead of clicking Next, I click "Let me pick from a list of device drivers on my computer" and then select "Mobile devices" and click Next, I am presented with a blank list and a button reading "Have Disk". Clicking on this lets me browse, this time, for an .inf file. But selecting the android_winusb.inf file gives the following error message:
---------------------------
Select Device
---------------------------
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 32-bit systems.
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
This is about as far as I have got! I have tried experimenting with a couple of things, but with ultimately the same result:
Running (as administrator) USBDEview and uninstalling anything that starts with HTC, or ADB, or Android, or USB Mass Storage device
Editing the .inf file using the modifications described below:
The first modification I tried is described in comment 44 of issue 1039 on the Android Google Code forum (link removed because I don't have permission to post external links!):
Code:
;HTC Hero
%USB\VID_0BB4&PID_0FFE.DeviceDescRelease%=androidusb.Dev, USB\Vid_0bb4&Pid_0ffe&Rev_0100
You can find / adapt those description with your material manager (look in advanced tabs)
To have a nice name of device, add at the end of file something like
USB\VID_0BB4&PID_0FFE.DeviceDescRelease="HTC Hero rev 0100"
The second modification I tried is described in comment 99:
Code:
[Google.NTx86]
; HTC Hero
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
And the third is described in post 2 of a recent Android Developers Google
Groups thread entitled "cannot install USB drivers for HTC Slide, Android 2.1, Windows Vista 32 bit" (link removed because I am not allowed to post external links!). For this one, I consulted the information displayed when I go into Device Manager > ADB > Properties > Details > Hardware Ids, so the actual lines I added to the .inf file are as follows:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&REV_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
I also tried a slight twist on this:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
since all the other devices in the .inf file didn't include the &REV_0100&MI_01 parameters for the %SingleAdbInterface% line.
Finally, I also tried various times to uninstall devices from Device Manager, e.g. ADB, the two multimedia controllers with exclamation marks against them, and USB Mass Storage Device (which does indeed have three lines on the Properties > Details > Compatible Ids screen, as advised by a blog post I found on the Android Simplicity blog entitled "How-To #0: How to Install Usb Driver on Your Computer" (link removed because I do not have permission to post external links!).)
I really can't think of much more to try, so would really appreciate any pointers, however small, from the experts!
Another option might be to give up on Windows and try doing the whole process under Ubuntu Linux, which I have installed under dual-boot. However, the instructions for updating ROMs/making backups/recovery/etc. appeared to rely on some Windows executables so I figured that could be a risky approach (especially given I know very little about how to work Linux...!).
Thanks for reading
Michael
Don't need them. Get the latest HTC Sync and install the My HTC driver and adb will work.
Thanks for such a quick reply btdag!
Really? That would certainly make things a lot easier, however dreamersipaq does make a point of reinforcing how important it is not to have HTC Sync installed in his instructions:
At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done)
Click to expand...
Click to collapse
[...]
HTC Sync does not like to play nice with the reflash tool
Click to expand...
Click to collapse
[...]
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it)
Click to expand...
Click to collapse
Does this not matter after all?
To get adb working I just installed the latest HTC Sync and drivers and then added ;C:\Path\To\SDK\Tools to my Windows Environment Variables as described in this guide:
http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735&sid=d1d70142a6264965b8c370bf1afa64d0
no problems with adb since
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Thanks for all the help.
I'm pleased to say I've now managed to install the update, and my phone is now ringing!
In the end I worked out that I did not in fact need ADB at all. Since the phone had already been rooted and had a custom ROM installed, it dawned on me that it must already have the requisite recovery image installed. And indeed it did. So all I had to do was install Titanium Backup, back up my apps and settings, also take a nandroid backup just to be on the safe side, and then factory reset/wipe and install the update. (And then restore apps and settings using Titanium Backup.) Problem solved!
As an aside, I think there is certainly scope for more 'newbie' documentation. (Or would this be on the Wiki, currently down?) I'm certainly very grateful to those who have taken the trouble to set out what they have learnt already, for the benefit of others. For example though, even after spending several hours searching and reading up all the newbie guides I could find, I still had to read between the lines quite a lot to work out what a 'radio' was, what purpose the recovery image serves, how ADB fits into the whole picture, why there are multiple custom ROMs available for the same version of Android and how to choose one, etc. Perhaps one day I will be advanced enough to attempt that myself!
CyberWalrus said:
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Click to expand...
Click to collapse
Thank you very much! I was reading this trying to get my G1 to work and it did. Windows 7 x64 won't allow me to install the android_winusb.inf driver but droid explorer did.
Phone nor computer will recognize adb/usb
First of all, my is rooted but somehow the superuser.apk file is missing. When trying to activate wifi tethering it asks if the device is rooted. The answer is, yes! I can boot into recovery mode but I do not have a way to get the superuser to open without adb. Can anyone help me?
Unable to Instal ADB Drivers
I'm having similar issues trying to root my MyTouch 4G. I've been following steps on the cyanogen wiki website for this device, which refers you to their site's instructions for setting up SDK & ADB drivers.
I've downloaded the SDK zip file, extracted to the C drive and made sure file paths are all the same as per the instructions. When following the instructions under Windows, I've added to variable values ;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools (and double checked these folders on C drive to be sure they're accurate).
When trying to manually update device drivers for ADB, I select the file android_winusb.inf and get 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."
My device has USB debugging enabled and is in mass storage mode (I've read on other forums that this can fix).
Not really sure what else to try? Any way I can change the .inf file to make Windows recognize it? Running Windows Vista 64.
Hi and good morning.
I have seen on the thread, "post your X10 screen" or something like that. And I have seen some that have a different WiFi icon, battery in right corner. How do I change that? Is it custom ROMs or what?
Thanks for all help.
Sent from my X10i using XDA App
Sikiduck said:
Thanks for all help.
Click to expand...
Click to collapse
Hi.
See the tutorial link in my signature, it's really quite easy to do.
Do I have to start with ADB for noobs: http://forum.xda-developers.com/showthread.php?t=532719 and install Droid Explorer?
And then "Three tutorials for modifying your x10 OS aesthetically" and then: "framework-res Icon Pack (Modding)"?
Thanks
EDIT: Im not getting a notification of Android ADB when i plug in my USB. I have tried to download USBdeview and see if there is HTC Android, but there is not.
I have a Xperia X10i phone and the only thing that is listed is "Sony Ericsson sa0101 ADB Interface Driver" and "Sony Eri Memory Stick USB Device".
When I uninstall ADB Interface driver nothing happens. Just freeze for a couple of seconds but thats it.
Whats wrong?
Can someone help me?
Sikiduck said:
Do I have to start with ADB for noobs: http://forum.xda-developers.com/showthread.php?t=532719 and install Droid Explorer?
Click to expand...
Click to collapse
nephron said:
Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now,
1. Run SDK Manager.exe located in the android-sdk-windows folder
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r7+
1. Run SDK Manager.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
Click to expand...
Click to collapse
Sikiduck said:
And then "Three tutorials for modifying your x10 OS aesthetically" and then: "framework-res Icon Pack (Modding)"?
Click to expand...
Click to collapse
It would be an idea to read the three tutorials yes and the packs are there for you to use when you've learned how to edit apks. If the adb driver is already installed I'm not sure why you're removing it, you need it to use adb.
Hi all, I need help pls, i try SDK Manager work but I hawe problem. I fallow thys steps http://forum.xda-developers.com/showthread.php?t=532719 all works great, SDK Manager update and download all data but when I conect x10 on usb computer auto install "Sony Ericsson sa0101 ADB Interface Driver" and not the "androidwinusb86.cat" what i need for SDK Manager recognise me x10. Haw I can pls ghet install the right usb driver tu SDK recognise me x10? I need sdk for run the ADB for run JIT on me phone. PLS help thys noob thx
Or if smebody hawe som simple gude how enable JIT on X10, I welkom them, thx
Edit: win 7 ultimate 32b
btw sorry shuld by in difrend post, how enable JIT on x10.
thx
any help pls?
Hello!
I have gone through a lot of threads before posting this here. I am facing an issue with Android device debugging - the device isn't getting listed on Devices tab in Eclipse IDE. (Please refer to screenshots) (To get 'Devices' tab 'Windows -> Show view -> Devices'). So while starting to debug there is no way to choose a device as device listing shows blank. The strange thing is that it used to work fine before and under windows explorer I can browse the files.
I am using Windows Vista Home premium, 32-bit OS
What all I have tried:
In phone:
1. USB debugging is enabled in phone under 'Settings-> Developer options'
2. Disabled and enabled USB debugging
3. Restarted the phone
In Eclipse:
1. Under 'Debug configurations->Target(tab)', 'Always prompt to pick device' is selected. It prompts but doesn't show any device on the device list!
2. Tried resting ADB under Devices tab. (To get 'Devices' tab 'Windows -> Show view -> Devices'
3. Reinstalled latest Android SDK along with ADB
4. Installed Eclipse Juno
In windows CMD under /platform-tools/ directory where the Android SDK Tools is installed, ran the following commands without getting any positive outcome:
Shut down Eclipse, unplugged the device and tried running:
adb kill-server
adb start-server
Plugged it back in and ran
adb devices
Mobile device details:
Model = Galaxy S2 GT-i9100
Rooted = yes
OS Ver. = 4.0.3
Kernel ver. = 3.0.15
[email protected] #k3-27b
Other details can be found in the attached screenshot.
Eclipse version: Indigo Service Release 1
Build id: 20110916-0149
Any help will be appreciated,
Thanks,
Ambar!
Debugging Samsung in Eclipse...
ambar_bs said:
Hello!
I have gone through a lot of threads before posting this here. I am facing an issue with Android device debugging - the device isn't getting listed on Devices tab in Eclipse IDE. (Please refer to screenshots) (To get 'Devices' tab 'Windows -> Show view -> Devices'). So while starting to debug there is no way to choose a device as device listing shows blank. The strange thing is that it used to work fine before and under windows explorer I can browse the files.
Ambar!
Click to expand...
Click to collapse
I ran into a similar problem this evening, though I am not sure if you are having the same issue. In my case eclipse would not recognize my Samsung i9000m when plugged in. This surprised me as I have debugged with this phone in the past but I have recently loaded Cyanogenmod 10.1 on it.
I checked Windows Device Manager (Control Panel) and noted that for some reason, Device Manager was showing an error for my i9000m, no driver had been assigned. I have installed the Samsung drivers in the past and they are still installed but I suspect some difference in naming of the device in CM10.1 which confused Device manager. I selected "Update Driver" option in Properties for the device and then selected the option that had windows go search for the correct driver. To my surprise, Windows 7-64 bit found and installed what appears to be a Generic Android Device named "Android Composite ADB Device". I am not sure if Vista will be the same or if this is even the same problem you are having, but check your Device Manager to see if errors are flagged...
Hello,
I've a problem since I changed my Rom : I take the CyanogenMod 10.3 for my Alcatel OT995, it works fine on my device, but I can't use adb command line neither other features using adb.exe ! I can only access to storage mass device, so I think I have a problem with the USB drivers which connect ADB command to my phone.
I can add that before I've installed this Rom on the device, I've installed many drivers on the PC : Firstely I installed the owner's driver provided by Alcatel in the AlcatelAndroidManager.exe package, secondly I installed the Google USB drivers provided because I'm using Android Virtual Devices (AVD Manager) to do some developping works.
I used to launch adb with "adb start-server" so it's still working, I don't obtain any device in the list with "adb devices", why don't I get it ?
I've realized some cleaning actions : I uninstalled the USB drivers of Alcatel's software, I uninstall the Google USB driver , to finish I reboot the PC but it don't changed anything !
Moreover, I tryed to apply this (well explained) post without any success :http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396 ; I see finely in the list, I can't find "Android devices" category, neither "Usb Adb" entry... so my device is not recognized in the "Settings Panel". However the storage mass device appears as a volume named "F:".
Help me please.
The post #4 published by Incubus 26jc saved me at http://forum.xda-developers.com/showthread.php?t=735937
Almighty! lets get started,
I have a 64 bit computer running Windows 7 professional.
First let me mention I tried to fix this on my own. darn I tried.
Just plugging the tablet into computer shows a windows explorer page named Autoplay that let me view pictures on device on a folder named
Computer\Trio HD Elite 7.85 Tablet
Installed android-studio-bundle-141.1903250-windows in
Error- SDK required.
Downloaded jdk-7u79-windows-x64 (java development kit)-install reboot PC
Open C:\Andriod in windows explorer, open SDK Manager
A command prompt window flashes briefly, then closes.
click start, search for run key in sysdm.cpl go to advanced, environment variables create new path named JAVA_HOME that does directly to the java .exe file
(this was checked by reinstalling the java development kit, then opening Java typing where java it tells me C:\Windows\System 32 even though the path is
C:\Program Files\Java\jdk1.7.0_79
opening ADB works!
Download Extras- Android USB Driver
open CMD key in
cd C:\Andriod\platform-tools
this brings me to the directory where Android ADB is.
abd devices
no devices detected.
Installed Samsung Kiles.
TRIED to install PDAnet.. failure.
tried to open Device manager, where a entry marked Trio HD Elite 7.85 Tablet sits, and update the driver to the C:\Andriod\extras\google\usb_driver
it complains about driver being unsigned. Using This guide I used step Two downloaded Driver Signature Enforcement Overrider (DSEO) and ran it.
went into the C:\Andriod\extras\google\usb_driver folder and manually keyed in every title in the folder.
each time program stated had signed successfully. The computer is now saying test mode in the bottom right hand corner. however trying to update driver gives same error.
I'm amusing the device needs to be in developer mode, which it cant be put into because it's locked.
The Trio Support is useless there steps do not open any settings. Also tried a list of alternate ways to open tablet recovery. and since ADB isn't reconizing the device I can't run adb reboot recovery
So. end result, im here with coffee and no milk,
A generic tablet cobbled together from who knows where,
and a locked screen.
Think you can help?
ANY assistance is appreciated.
So i have a cheap generic tablet that says Trio Stealth G4X 7.85