I used to be able to
1. Plug my phone in via USB (unmounted - meaning "charge only")
2. Open up a command prompt and navigate to the correct folder.
3. Type "adb devices"
4. Receive a long string of characters that indicated that adb recognized the device.
Now this only happens for me if the phone is in recovery already. For example:
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT05SHL05247 recovery
Things I've tried:
* Re-installed SDK
* Re-installed HTC Sync
* Manually re-installed drivers for phone
It is interesting to note that when the phone is on and plugged in, Device Manager sees it as a disk drive no matter if the phone is mounted as a disk drive or not. Strange.
Everything worked fine until I went on vacation. Now it's messed up!
The question is: how do I get adb to recognize my phone again?
is usb debugging still on?
when you plug in the USB cable do you get the screen to select
charge only, HTC Sync Disk drive etc..
if not go to "Settings" -> "Connect to PC"
and turn on "Ask Me"
I had a bad USB port, would only charge could not get any PC connection to work until phone was replaced, works now
Bill
Thanks for the responses.
mdwoods said:
is usb debugging still on?
Click to expand...
Click to collapse
Yes, I checked and USB Debugging is selected.
btedeski said:
when you plug in the USB cable do you get the screen to select
charge only, HTC Sync Disk drive etc..
if not go to "Settings" -> "Connect to PC"
and turn on "Ask Me"
I had a bad USB port, would only charge could not get any PC connection to work until phone was replaced, works now
Bill
Click to expand...
Click to collapse
Yup, when I plug it in I get the pop-up asking me what kind of connection I want.
Any other ideas?
Still nothing! I'm going to be selfish and bump in case a fresh pair of eyes can help me solve this.
Something similar happened to me. I tried many things over and over again. I changed kernals, roms, reinstalled drivers, etc. Eventually, I just reformatted my computer and it worked. I don't know why reinstalling the drivers wouldn't work when reformatting did. I honestly have no idea, but that reformat did the trick for me.
ADB not working when booted is a somewhat commonly-reported problem with King's kernels. Try flashing the stock kernel and see if it starts working again. Also, wipe your caches in the future before flashing a new kernel. This seems to prevent a lot of issues.
I has this same problem. I believe I wrote a thread about it. When I toggled USB debugging off and then back on, that is what solved the problem. Believe me, I went through hours of reinstalls of multiple androidusb.inf drivers plus HTC Sync among others. It wasn't until a "what the hell, let's give it a try" moment that I toggled USB debugging off/on. Like you, I had it on the whole time. Still don't know what caused the mishap but this is what fixed it for me.
Sent from my PC36100 using XDA App
Thanks for the last two ideas. I love Fresh ROM, but have been having major issues with it lately, and this must have been tied into it. I installed Baked Snack with the custom baked snack "speed" kernel and the issue went away (along with all my other issues). Yay.
I don't doubt that toggling the USB Tethering check box would have fixed it, though. And that's just funny. Sad and funny.
Sprockethead said:
I don't doubt that toggling the USB Tethering check box would have fixed it, though. And that's just funny. Sad and funny.
Click to expand...
Click to collapse
Actually, I found an answer to that question. I am experimenting with Andromadus CM10 on a HTC Desire Z and this is what happens:
The mobile phone declares what USB device it is. You can look at this on the linux computer you have connected it with:
Code:
lsusb -v -d 0bb4:0c91
The string after "-d" is what you get from a plain lsusb command. The important part of the output of that command is
Code:
bInterfaceClass 255 Vendor Specific Class
"adb devices" only shows the phone if this 255 is present.
With the phone in fastboot and recovery, I always could see the 255 on my linux box. Normally booted, I sometimes had it, sometimes not.
If I had it the device was called "HTC Vision", if I didn't have it, it was a "HTC Desire / Desire HD / Hero (Charge Mode)"
Toggling "USB Debugging" actually helped me to make it a "HTC Desire" and get adb over USB working.
Hey guys,
I've scoured the forums and was wondering if anyone has any information on unbricking a htc desire, nothing works on it, when plugged into the mains a orange led comes on and when i try and press the power button the led goes out, although when i plug the device into my computer it connects via usb as a adb device i've tried hard resets and fast boots but both dont work. is there a command i could use to kick it out of ADB mode?
anyway thanks guys
Soapysoap93 said:
Hey guys,
I've scoured the forums and was wondering if anyone has any information on unbricking a htc desire, nothing works on it, when plugged into the mains a orange led comes on and when i try and press the power button the led goes out, although when i plug the device into my computer it connects via usb as a adb device i've tried hard resets and fast boots but both dont work. is there a command i could use to kick it out of ADB mode?
anyway thanks guys
Click to expand...
Click to collapse
Please post more data about the phone.
Have you tried booting into hboot or fastboot ?
http://developer.android.com/guide/developing/tools/adb.html
adb shell reboot might get you out of adb.
I don't know but maybe adb logcat might help you diagnose the problem.
Perhaps this is USB brick?
http://forum.xda-developers.com/showthread.php?t=691639
ok i've tried kicking it out of adb mode and that doesnt work it doesnt see the phone, but in device manager it says "android composite adb interface" and i dont know if its a usb brick the phone wont turn on for me to find out
So my screen is broken and i am trying to use [email protected] but i can't enable the usb debugging. Is there any way to enable it on the computer?
I don't want to flash a rom because i want to keep the data.
I have the same problem, screen on my wifes E4GT is broke but phone seems to work. When I connect via USB it shows the two devices but no drives show up. Tried kies and it says to enable debugging mode, which I thought I did but I don't remember.
Hi guys!
Haven't been here for a long time but now I need help or guidelines for the problem:
I got HTC Desire with shattered screen - LCD and digitizer. It lights up but no image.
Phone connects to computer as Adnroid Phone on Mac and USB Mass Storage Device on Windows so I assume the USB Developer mode s not enabled.
Is there any chance of recovering contacts without screen replacement?
Thanks!
gutaker said:
Hi guys!
Haven't been here for a long time but now I need help or guidelines for the problem:
I got HTC Desire with shattered screen - LCD and digitizer. It lights up but no image.
Phone connects to computer as Adnroid Phone on Mac and USB Mass Storage Device on Windows so I assume the USB Developer mode s not enabled.
Is there any chance of recovering contacts without screen replacement?
Thanks!
Click to expand...
Click to collapse
You can't assume that usb debugging isn't enabled just because it connects to the PC as a hard drive. Try using "adb devices" to see if your device is properly configured for adb.
Thanks,
Already done that but I forgot to mention... I get empty "List of devices attached".
When I connect another phone with Debugging Mode enabled "adb devices" lists connected device without any problems.
Any other ideas?
gutaker said:
Thanks,
Already done that but I forgot to mention... I get empty "List of devices attached".
When I connect another phone with Debugging Mode enabled "adb devices" lists connected device without any problems.
Any other ideas?
Click to expand...
Click to collapse
Adb should work in recovery. Boot in recovery, connect your phone and try "adb devices" again.
So I have my girlfriend's water-damaged HTC Desire 620 and am trying to recover some data not stored anywhere else. The screen works and the phone boots but digitiser does not work. It will charge and connecting to my PC it recognises it as an MTP device that is empty. The phone is locked, there's no custom recovery and adb debugging is not enabled. My attempts to resolve so far are:
1. New digitiser/digitiser+screen assembly failed - I assume the connector is faulty.
2. OTG cable with mouse - mouse doesn't work, light doesn't come on. Cable/mouse aren't faulty as checked with own phone.
3. Android SDK / adb - when booted normally, no adb devices are recognised at all. When I boot in recovery it recognises a device but it is unauthorised. As I have zero access to the phone itself, I can't physically enable debugging on it.
So that's as far as I've gotten. From what I gather, without the device being authorised I won't be able to get adb to work. I am way out of my depth at this point but any help would be amazing. Even just to know if this really is a lost cause or not.
Thanks