Hey,
yesterday my phone is fallen on ground and my display is now broken.
before i buy a new display, i wanted to check if everything else works..
and i see that my phone charges only when turned off.
i have latest cm10.2 installed and use the internal ssh server to check several things.
i see that voltage and capacity are falling.
Code:
cat /sys/class/power_supply/battery/batt_vol
cat /sys/class/power_supply/battery/capacity
it notice that it's plugged in and it know if its usb or ac
Code:
cat /sys/class/power_supply/usb/online
cat /sys/class/power_supply/ac/online
cat /sys/class/power_supply/battery/batt_charging_source
and it really don't charge
Code:
cat /sys/class/power_supply/max8922-charger/status
cat /sys/class/power_supply/max8907c-charger/status
cat /sys/class/power_supply/battery/status
All says "Not charging"..
i also noticed that usb otg works without problems but my computer don't find my phone when i plug in. i think by default it should be a mtp device or something? usually i never use usb connection..
has anybody an idea what could be wrong?
i think maybe my device is stuck in usb otg mode..
but what can i do?
Edit:
Okay, since "reboot recovery" looks like it don't start anymore..
I will try tomorrow again..
Hmm, i tested on a other device. If i reboot to twrp recovery and do a hard reset, the phone starts twrp again until i boot system through twrp..
usb device still don't work, so i don't have adb and no option to leave twrp without a display..
Greetings from germany
Hummtaro
Related
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.
Hi all,
I have dropped and destroyed the screen. Hooking up to the computer I noticed on one occasion that the device showed up when doing a ./adb devices. However since then it hasn't done it. I know that USB Debugging is turned off.
Is there anyway to force it on, say booting it into recovery mode?
I could do with access to the shell before I send it off for repair.
Cheers,
Jodi
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
I just did "adb reboot recovery" and my FTV1 turned off and never came back on. Unplugged everything, plugged back in, nothing. Then I went to the bedroom where there's another FTV, and its dead also. How did I do this and is there a fix?
edit: by dead I mean it wont even power on. Neither FTV can get to the first white amazon logo. No video output, no light on the front.
Try plugging into your computer and monitor the status of the USB device drivers being loaded. If the computer seems to be recognizing it, try 'adb devices' or 'fastboot devices ' to further check the status of the device. A simple 'adb reboot' or 'fastboot reboot' may get it booting again.
mrlaugh01 said:
Try plugging into your computer and monitor the status of the USB device drivers being loaded. If the computer seems to be recognizing it, try 'adb devices' or 'fastboot devices ' to further check the status of the device. A simple 'adb reboot' or 'fastboot reboot' may get it booting again.
Click to expand...
Click to collapse
Do you mean connect the FTV to my pc? with USB? Not sure I have a cable like that (fat usb on each end). The FTV is not the slightest bit warm when the power cable is plugged in so I doubt I can adb to it.
It can't hurt to try the USB a to USB a cable thing. If your stuck what do you have to lose? Were you rooted/ unlocked / and on a pre-rooted rom?
Michajin said:
It can't hurt to try the USB a to USB a cable thing. If your stuck what do you have to lose? Were you rooted/ unlocked / and on a pre-rooted rom?
Click to expand...
Click to collapse
I'll have to get one of those cables. Does quality matter? Found it direct from China for under $1: http://www.ebay.com/itm/30CM-High-S...ata-Transfer-Charger-Cable-Cord-/282210741043
I was on rbox's latest pre-rooted rom. I updated the FTV1's on different days yet they both died at about the same time. Right after I gave one of them the adb command "reboot recovery."
I misread your post and was under the assumption you were using a Fire Stick. But USB ADB should be possible. Here's a quick search result: https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-to-fire-tv-device
mrlaugh01 said:
I misread your post and was under the assumption you were using a Fire Stick. But USB ADB should be possible. Here's a quick search result: https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-to-fire-tv-device
Click to expand...
Click to collapse
sorry for delayed response, was out of town and didnt want to think about my two FTV paperweights.
I looked at that link and it says this:
"If you plan to connect your computer to your Fire TV device using a USB cable, turn on USB Debugging."
I never did USB debugging so I never turned that on and even if I did I'm fairly certain the FTV is not turning on since its not even slightly warm. Do you think I should order the USB A to A cable anyway and try?
I cant believe I'm the only one that has had this happen...
Yes I believe it'll work still... The Fire devices have a system 'adb mode' when it first boots up. Booting up TWRP on a Fire Stick is a similar process you can probably follow. But if you're not getting my power, or it's not not powering up, you may have bricked it.
Hey gals and guys,
my girlfriend dropped her Xiaomi A2 lite and no the touchscreen doesn't respond. The phone has the stock Android One and I can only access fastboot.
Code:
fastboot devices
recognizes the phone.
The recovery is the stock recovery.
Code:
adb devices
won't recognize the phone and gives me an empty line as output
I also can't access the phone via usb with my filebrowser. If I try, the phone makes a "bing"-sound and the filebrowser gives me:
Code:
unable to open MTP device
I am using archlinux and I also have a windows device available.
Is there any chance on getting pictures etc from the phone?
Any suggestions besides getting a replacement for the touchscreen?
Thank you so much.
Connecting via USB probably needs you to click something.
I'm guessing developer mode is not enabled...
If you've got a micro USB OTG cable, you could plug a mouse in.
If you boot TWRP (fastboot boot twrp-3.3.1-dees-troy.img) you should be able to get adb and usb transfers working. Don't need to install it, just boot it. Not sure if that works without unlocked bootloader.
If you've got a micro USB OTG cable, you could plug a mouse in.
Click to expand...
Click to collapse
This did the trick.
Thank you