Database Users

Can no longer connect via adb

Now I know your first thought “I bet this tool didn’t even use Search like the rest of the shlubs on here”. Well you are mistaken. I have not only searched xda but even tried Google and Yahoo (just in case) as well. I have found numerous posts (like HERE and HERE and many others) with similar situations but haven’t seen a resolution. Here is the rundown:
Running JF’s 1.5 CRB21 ROM
Hard SPL (HSPL10.95.3000)
JF’s 1.43 Recovery Image
SDK 1.5_r1
Fastboot.exe placed in System32
Haykuro’s Updated Drivers placed in System32
Windows XP 2002 SP3
I have been able to flash nandroid backups without issue in the past but adb started intermittently not recognizing my phone when I flashed from JF’s RC33 to JF’s 1.5. I was able to restore a backup once but now adb will not recognize my phone at ALL. Tried different USB plugs and cables with no result. If I mount the phone to view the SD card via Windows Explorer it shows as “HTC Dream Composite ADB Interface” in Device Manager. However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order. I have deleted my SDK and drivers and re-downloaded/installed them and STILL cannot get adb to connect. It has to be something simple I am missing here right? Any idea why this would have worked without issue in the past and now not at all? Could it have been a Windows Security update? (That's about the only thing I can thing that has changed other than the newer ROM)
Thank you for your help.

Did you update you USB Drivers or try reloading them?

Also.... Settings > Applications > Development > USB debugging has to be checked....
and stop being a tool.
nah im jk.

USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent

Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.

gPhunk said:
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Click to expand...
Click to collapse
Repent .. Repent..
Did reloading the USB Driver work?.. Did for me =)

billc.cn said:
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
Click to expand...
Click to collapse
How do I know which one to install? (I am running Vista Home Premium 32bit)
Thank you for your help

Use the x86 drivers. Also try installing them in safe mode. That made it work for me

ubernicholi said:
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
Click to expand...
Click to collapse
Thanks man - I was able to install the drivers but am still unable to view my device. It shows as "HTC Dream" in Device Manager but when I run "adb devices" in the command line, it yields a blank list. Further commands (I.e. adb shell) say "cannot find device. Running fastboot commands result in "waiting on device". This happens on both my laptop and my home pc so I am beginning to think it's the phone. Should I have something loaded on the phone? I have USB Debugging checked so that's not it. Any ideas?

possibly the problem is that ADB does not work in Bootloader mode, it is designed to work while the phone is running.
However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order.
Click to expand...
Click to collapse
Yuo are obviously trying this in bootloader mode, underline for emphasis.
try >fastboot devices
see if that shows you your phone
Otherwise try ADB while in the OS already.

ADB does not find device

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!

No guide on the RUU? Download link?

So... I've somehow screwed up recovery, and now adb won't do anything... it connects (adb devices shows my serial#)...
Im tired of dianosing it, I just want to use the RUU and flash back to factory, and re-root.
Problem is, with the lack of modding around here... there's no sticky or link. It was somewhat difficult to find info on flashing back to factory status. Searching here, AndroidForums, and google.
The exe I downloaded starts to go through installshield and then does nothing. (the filename is RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe)
My computer is XP Home
what am I doing wrong?

That's the right file. So you run it, and you see installshield come up but then it never opens the window to walk you through starting your actual restore? Sounds like you have an issue with your computer too then.

check your drivers, reinstall if necessary.
if no go, barrow a computer and try it from there. I've found WinXP to be the easiest system to mod the Hero from (prolly because of my comfort with command line interface)

obededom said:
check your drivers, reinstall if necessary.
if no go, barrow a computer and try it from there. I've found WinXP to be the easiest system to mod the Hero from (prolly because of my comfort with command line interface)
Click to expand...
Click to collapse
I can second this advice. I tried to run the .exe from a Win7 machine unsuccessfully. It would partially initiate the recovery process but then close itself after trying to detect the phone. In WinXP, the process was successful on the first attempt. If you don't have access to an XP machine, perhaps try starting the .exe as XP compatibility mode? You can right-click on the file and go to Properties to find those options.

This is a XP machine...
I can run adb devices and see the phone... and in fastboot usb the phone does show up device manager.

Hero "Device not recognized", no ADB connection - solved...NOT...MAYBE NOW?

When I connect my hero (VillainRom 10) to my PC (Win7 64) all I get is a "USB Device not recognized" error, the phone is being charged, but I get not ADB connection.
Plus, I get the "connect to PC" dropdown on the phone, selecting something (e.g. disk drive) has no effect however.
It really randomly stops working and as randomly works again for a short period of time.
I have tried different USB ports, the cable that shipped with the Hero and a normal miniUSB cable, HTC drivers and those that come with the SDK, removing battery while connected, restarting Phone and PC etc etc.
Once I saw that some dust gathered in the Hero's USB port, so I removed it and it worked after that. Some time later it stopped working however and I can't get it working again although everything is perfectly clean.
This is especially annoying since I started developing a game for Android and debugging is almost impossible now :[
All help is greatly appreciated!

Have you tried...
adb kill-server
adb start-server
(adb devices)
I had the same issue under Linux, where this helped, I don't know about Windows though (doesn't hurt to try though)

I had this the other day, go to Device Manager, find the ADB device, and then get it to download drivers of the net. For me, the drivers downloaded where for the HTC Dream, but still, it worked and now I have the ADB connection works
Hope this helps

I had a similar problem and I solved it by installing HTC Sync.

^ +1
installing HTC Sync worked for me

Thanks for all those tips, but I actually tried all of them, restarted adb server, I can't load new drivers via device manager because my Hero is not being displayed as ADB device but as "Unknown" (but I manually tried different drivers) and I also have HTC Sync installed.
You have some other ideas?
(meanwhile I'll try some stuff myself if I have time)

Could it be the USB cable?

I uninstalled HTC Sync, uninstalled ALL usb drivers (except keyboard and mouse, using usbdeview) installed VillainRom 12 on my Hero, downloaded and installed HTC Sync and 64-bit drivers from softpedia and now it seems to work more or less stable.
I hope it continues to do so and that this here may help someone else!

Argh!
stopped working after reboot...
now it's switching from nothing happening at all when I plug it in, showing me the "Device not recognized" error, or, in very few cases, working for several seconds, then loosing the connection.
I start to believe that this is a hardware defect, but why did it use to work in the past then??
Thanks alot for your help!

Not using a 64 bit machine worked for me. Although it took 5 computers, this fixed the problem for me.
(should note I was also having troubles rooting on my x64 machines.)
Defn shouldn't have upgraded everything to 64-bit. Doh!
Sent from my Super Duper EzHero using XDA App

Tried on a 32-bit XP laptop - didn't work :[
but thx
edit: tried on another win7 x64 laptop - nothing happened at all !?

i've been on ALL the same problem with you
and i'm tiring to find the way out
hope anyone can help us too....

Good to hear I'm not alone! Let me know if you find out something (whatever it is)!
2 days ago it suddenly worked perfectly as if nothing had happened all the while.
programmed happily... next day pc boot - good ol' "device not recognized"
it seems to be exactly this problem:
http://blogs.msdn.com/b/usbcoreblog...cted-or-comes-up-as-unknown-device_3f00_.aspx
now I/we need to find out what causes this on the hero
somthing that could have to do sth with it working 2 days ago is that my hero's battery was completely drained and it was force-shut down. Only after attaching power I could boot the hero. Then also the usb connection (with adb) worked.
very strange...
edit:
someone else seems to have the exact same problem on linux (so it's os independant)
http://forum.xda-developers.com/showthread.php?t=653295
another guy with a potentially interesting solution in post #7
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7211035
which leads to this:
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
(I will try it nao

update: got it working (let's see how long by doing the following)
(you'll need the android sdk for it)
shut down hero
remove and reinsert battery
boot into fastboot (Hold [back] and [power] key)
open cmd
cd into the andoid sdk tools dir (for me cd C:\android-sdk-windows\tools)
exectute "fastboot oem boot"
let hero boot
now you should have at least adb connection, now unplug and plug hero and you should have full connection (sd-card, whatever you want)
if that didn't help you can try the stuff from this link (posted that earlier already):
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
(I had planned to do all the steps, but the first one already fixed it - strange)
edit:
works on 1 other PC I've tested so far - will try our car's pc next

update: stopped working again, not even fastboot was able to connect
removing the battery while in fast boot while being plugged to the pc and reinserting the battery fixed it
strange strange...

Remove phone from PC
Uninstall htc sync
Run usbdeview-x64 and remove any htc (or unrecognised usb devices)
Restart
Reinstall HTC Sync - latest version .33 or something
Plug in phone (allow it to get drivers from windows update etc, if not use the ones in the HTC Sync folder)

I did this several times but it didn't help as my problem is a problem of the hero, not of the pc not finding the right drivers.

Send it back for repair then...

I will first try fixing it myself

[Q] What's the micro usb port for?

Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq

It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.

Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.

I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was

I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq

Drivers from acer website.

I have adb installed should this not be enough?

You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.

I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq

I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6

I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium

Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq

don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.

If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App

gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.

I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.

sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.

Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try