Hello,
I've posted this a few days ago in htc one thread, but got no answers, so I thought maybe this is no phone-specific problem and i need a larger group of counselors
My phone (HTC one m9) will only charge or connect to pc _once_ per reboot (power on, plug usb in - everything ok, charging and connection to pc. plug out, plug in again - nothing. No charge, no connection, until reboot)
Currently i'm s-off, rooted, newest htc rom, nougat. But the problem started when i was s-on on cyanogenmod, marshmallow, so...i don't know. Cleaned the usb port. Used some battery-calibration app from play market. No idea, please help.
I don't think it's hardware-related since it works one time, but how can it be software related when i'm on a new rom? Any weird app? Dunno, i'd say my apps are pretty standard. Xposed doesn't work on nougat, so nothing to do with that.
can be set as resolved. I've exchanged the usb flex (and the sdcard-flex after ripping some bloody wires...), and it works again. Seems like it was some sort of loose contact.
Related
Hi,
I have flashed cyans 5.0.7 rom and lost after first restart somehow connectivity to USB computer.
I cant fastboot with USB, neither I can USB connect to w7 or vista. It says usb device not recognizable.
Any idea what to do to correct this issue?
Thanks
FERO
try connecting your USB and then rebooting the phone. It usually works for me.
Infinite76 said:
try connecting your USB and then rebooting the phone. It usually works for me.
Click to expand...
Click to collapse
Same, just reboot your phone, should work.
Issue 1326
I believe this is a known bug. Issue 1326 on the cyanogenmod google code page.
http://code.google.com/p/cyanogenmo...ty Version Model Owner Summary Stars Modified
It comes from using a charger that doesn't supply the normal amount of charge. No damage, as they say a reboot will fix. An attempt to fix is being made, but no stable release has the fix. In the meantime, reboot or use chargers with adequate power.
First off, this is probably the wrong section to post this in, but that is not my reason for response.
I too have this issue, no USB connections will be recognized when I plug in. No fastboot, no adb, no ums mount in recovery. Moreover, though the battery is good, it will no longer hold a charge for more than 2 hours. A simple reboot will not fix this. Will your phone charge via USB? Will headphones work? Both are a yes for me. I have spoken with Steve (Cyanogen) about this, and we are both certain it is a hardware issue. If you are having the same problems as I am, it is most likely that a solder from the usb port to the board is broken.
Now for the good news. I think I can fix this, but I need to wait until my family leaves (all visiting for my graduation ceremony). I am going to open it up, and if my suspicions are correct, try to fix the connection. I will report back when done.
cloverdale said:
First off, this is probably the wrong section to post this in, but that is not my reason for response.
I too have this issue, no USB connections will be recognized when I plug in. No fastboot, no adb, no ums mount in recovery. Moreover, though the battery is good, it will no longer hold a charge for more than 2 hours. A simple reboot will not fix this. Will your phone charge via USB? Will headphones work? Both are a yes for me. I have spoken with Steve (Cyanogen) about this, and we are both certain it is a hardware issue. If you are having the same problems as I am, it is most likely that a solder from the usb port to the board is broken.
Now for the good news. I think I can fix this, but I need to wait until my family leaves (all visiting for my graduation ceremony). I am going to open it up, and if my suspicions are correct, try to fix the connection. I will report back when done.
Click to expand...
Click to collapse
No reason for me to think that it is soldering or connection issue. My phone works just fine and it worked well with SuperE this morning before I changed to Cyans ROM.
The battery gets charged properly, I am sure about that as I have been out with my phone all day long and stayed at 56% no problem.
Restart helped this but I am probably going to change rom because of this to something else.
I get this problem too, although intermittently. I'm certain it is a rom issue, as it's only started happening with the eclair roms, but it hasn't been a big enough of a deal for me to stop using cyan's rom or anything. As mentioned, a phone reboot fixes it every time.
Another issue I get more often is where I'll plug it in to the USB cord, mount it, then after a minute it will drop the USB connection and I'll have to mount it again. Might be related, might not. Also not worth switching roms for.
I should also add that I'm not having any battery issues like Dr Cloverdale mentioned, so I think that's something else entirely.
I found the cause of this issue (#1326) last month and posted the fix, it's in the 5.0.8-test series. More info:
http://code.google.com/p/cyanogenmod/issues/detail?id=1326
[newbie rant]
That being said, this is the development forum, not the 'start a thread about an issue without searching first" forum.. Posting on, or even searching the CM thread (or google?) would have lead you to the information above. You can do better than that!
/newbie rant
Hi there,
My Nexus S (i9023) phone recently fell into a water bucket and I immediately pulled it out.
Not much damage was done to it except of one thing: after I put it in a bag of rice like stated on the internet for overnight, and then plugged it in again to the charger, it seems like something was different.
When I plug the phone to the AC power - phone DOES charge, but nothing else happens.
It doesn't turn on screen and informs "charging", and doesn't have the "charge when phone is off" option anymore. Instead it would just turn the phone on.
Also, when connecting the phone to the computer nothing happens, it's just charging the phone! can't mount USB anymore
I took the phone to a lab which handles these cases. They replaced the USB port and cleaned all the corrosion. They said it's fixed now, and indeed the USB port is new.
But then after coming back home it's still the same.
I'm sick of being dependant on other people and would like to fix it myself.
Any clue which part of my phone was fried? Where can I get it?
Thanks!
-zeek
Are u rooted?
Try a different ROM. Maybe one ur ur backups.
If it still does connect then it has to be the ROM assuming ur computer has the proper drivers still.
Good luck
Vs Nexus S 4G
Thanks!
Thank you!!!
Problem solved after I loaded one of my backups.
Any explanation to that? even when the phone was turned off it couldn't charge it in off mode and now it can.
How come it's a software issue?
Thanks!
I can only guess that ur ROMs kernel had a "fast charge" option. If so this doesn't allow computer connection. How it got switched to that option... who knows .... maybe the sudden power surge.
If not that, then ... strange things happen when a phone get wet.. the sudden power surge could have changed the power output causing CPU adjustments... who knows.
I'm just happy it worked for u.
I'd recalibrate ur battery asap.
Good luck
Vs Nexus S 4G
Hi, the same thing happened to me, only it wasn't a bucket, it was a pool, and changing the ROM didn't work (I've flashed at least three different ROMs since then, kind of hard when the USB port doesn't work but eh, what can you do).
Also, it's on a Gio, not a Nexus S, but the principle should still be the same, yes?
Hi
I recently bought a Desire S from a friend. I went about rooting it but when I plugged it into my PC it is not recognised at all, literally nothing pops up on the phone or the PC.
I've checked the settings in the phone and USB debugging is enabled and I always changed default connection type.
I have even booted into Hboot and plugged the USB in, but still nothing.
The phone charges perfectly fine and I've tried plenty of different cables. My other Android phone works perfectly when plugged it.
I'm starting to think its a hardware issue, anyone else heard of this? common problem? any fixes?
Thanks
Re install htc sync and drivers, then remove sync and try again
“Pressure is something you feel when you don't know what the hell you're doing.”*―*Peyton Manning
I have the same problem, sort of. When I plug mine in all is well at first, but give the phone one tiny nudge (or just wait a few minutes) and it goes back to charge-only mode. It's probably a slightly loose connection somewhere in the USB port on your phone.
To be sure, try if it works in Linux. The Linux USB stack sucks infinitely less than what Windows uses.
Thanks for the replies. I tried Ubuntu but exactly the same (it worked with my Nexus 4)
Thats a little annoying, thankfully charging still works, just unsure how long that will last for! plus I cant root it! but I dont exactly need it rooted but I tend to do it anyway.
I've sorted it now. It was a loose ribbon cable, plugged that back in after taking the phone apart and its working.
Bootloader unlocked and custom recovery flashed. Ready to rock.
So I'm on my second M8 (first one had some build issues). Only had it about a week and have hardly been using it since I haven't had time to transfer everything from my old phone. To that end, I haven't charged it much, and when it has been charging I haven't really been paying attention.
Today I am paying attention and it is saying that it is "slow charging" and that I should use the supplied adapter and cable.
I am using the supplied adapter and cable. I'm completely stock running only weaksauce (no S-Off, bootloader unlock, etc).
I had USB debugging on, turned that off. I've rebooted the phone, no difference.
I get the error message whether the phone is on, or turned off at only the charging screen.
I've tried some other adapters and get the same results.
Ideas?
TraderJack said:
So I'm on my second M8 (first one had some build issues). Only had it about a week and have hardly been using it since I haven't had time to transfer everything from my old phone. To that end, I haven't charged it much, and when it has been charging I haven't really been paying attention.
Today I am paying attention and it is saying that it is "slow charging" and that I should use the supplied adapter and cable.
I am using the supplied adapter and cable. I'm completely stock running only weaksauce (no S-Off, bootloader unlock, etc).
I had USB debugging on, turned that off. I've rebooted the phone, no difference.
I get the error message whether the phone is on, or turned off at only the charging screen.
I've tried some other adapters and get the same results.
Ideas?
Click to expand...
Click to collapse
I've seen this twice and heard about it once, first time was where I didn't have the usb cable properly plugged into the adapter (might not be your case since you tried different adapters, but you never know) and a second time when I didn't plug in the adapter correctly and only had one prong in the socket lol not sure how I didn't cause a fire that time cause it took me awhile to figure out. (I think you're smarter than I am so this is highly unlikely )
And lastly my cousin had the problem and his was due to a bad usb cable.
The Stig 04 said:
I've seen this twice and heard about it once, first time was where I didn't have the usb cable properly plugged into the adapter (might not be your case since you tried different adapters, but you never know) and a second time when I didn't plug in the adapter correctly and only had one prong in the socket lol not sure how I didn't cause a fire that time cause it took me awhile to figure out. (I think you're smarter than I am so this is highly unlikely )
And lastly my cousin had the problem and his was due to a bad usb cable.
Click to expand...
Click to collapse
Definitely not due to cables being in wrong.
I also tried another 10' 24/28 awg cable I got and the same thing.
It may be the charger, and I think I am going to try to hit up the Verizon store tomorrow and see if I can try one of theirs.
In the meantime, I have access to iPhone/iPad chargers. Can anyone confirm that they don't get the "slow charge" message when using one of these? If so, and I get it on that as well, then we may have an issue.
Ok, I just did a factory reset on my phone and it appears the problem has gone away.
I'm not sure why this would have done it.
I did the following to my phone originally:
1) Rooted with weakauce/SuperSU
2) Attempted to S-off with firewater (unsuccessful)
3) Installed sunshine to test, but did not go through with it to s-off (i.e. pay).
Apart from that, all I have done was install a handful of apps from the store.
I am going to try and recreate what I previously did and see if the issue reoccurs.
UPDATE:
So, things looked fixed after the reset. I re-rooted and loaded some things onto the phone and everything appeared fine.
I then decided to plug my phone into my juicing brick (RAVPower RP-PB17).
As soon as I did that I got the message again that it was slow charging (even though this is 2.1A charger).
After that, I continued to get the message regardless of what I plugged it into to charge...even the original charger..even after a reboot.
I was going to test this again by doing another factory reset and then plugging back into the RAVPower to see if that caused the problem. Before I did that, I looked around and found what is apparently a battery reset procedure documented in several places. The most "official" place I could find it documented was here:
http://support.t-mobile.com/docs/DOC-10943
Basically you hold both volume and the power button down for about 1-2 minutes while connected to the HTC charger. Sure enough, this seemed to clear the "slow charge" indicator again and now whatever I plug it into (including the RAVPower) seems to work fine.
I'm going to call HTC back and see what they say about this.
UPDATE:
Called HTC and told them what happened... that the phone was giving me "slow charge" until I factory reset it, and then started giving it again after I plugged it into my juicing brick.
I then told them about the re-calibration procedure I found and performed and that how now the device appears totally fine regardless of what charger I use.
I told them I was concerned because it was a new phone and asked them to explain why it was necessary. I also asked them if they had anywhere on their site, or publicly available a document explaining the re-calibration procedure and under what conditions it was necessary.
The girl I spoke to was really worthless (more than the guy I web-chatted with who just said "return it"). She said there is no public facing documentation on how to perform the re-calibration. She couldn't explain why I had the problem. Really all she could do was offer a repair/replacement.
I believe I'm still within the return period with Amazon - but I've already returned my first M8 due to build issues. I'm happy with the build quality of this one, but concerned that I had these charging issues already.
Should I return it and hope for a 3rd one with no problems?
I was having the slow charge issue for the past couple of days and tried everything suggested including a factory reset, different chargers, different cords, everything and still could not get my phone back to normal. I then took a really close look at the USB port on the phone and noticed pocket lint in there. It was preventing the plug from seating the whole way and would only slow charge.
To clean it, I shut the phone off and used a small safety pin to get the lint out. After that my charger is working normally again.
jsaxon2 said:
I was having the slow charge issue for the past couple of days and tried everything suggested including a factory reset, different chargers, different cords, everything and still could not get my phone back to normal. I then took a really close look at the USB port on the phone and noticed pocket lint in there. It was preventing the plug from seating the whole way and would only slow charge.
To clean it, I shut the phone off and used a small safety pin to get the lint out. After that my charger is working normally again.
Click to expand...
Click to collapse
Thanks for this. I'd been having this problem for weeks now. I took a small pin and pulled out a TON of lint from in the charger port. Now all is good. Thanks again!!!
So recently I started having this problem. My Nexus 5 stopped charging all of a sudden.
After messing around I found out that I could charge the phone when it is turned off, but when I boot it (while connected) it doesn't show the charging icon. Only when looking up the battery status at the setting menu it says charging.
To my surprise fastboot was still working (adb wasnt) what brought me to think it's not the hardware.
So far I have done a factory reset, wiped everything, installed stock kernel and recovery, downgraded to stock 5.0 (I don't even know why, just thought its worth a shot...).
At some point I took the phone apart to try to determine whether I tore out the connector itself, and noticed nothing.
I'm really running out of ideas here... I can live with having to reboot the phone for charging, but I really need it to connect to the computer.
Any help will be appreciated!
You tried different USB cables and chargers? USB debugging enabled? Computer is a trusted machine in adb?
I have 2 computers on which adb is trusted. Both stopped working. I tried a few cables, all of them worked with another phone, but did not with mine.
Adb is enabled. :/
Did you try revoking all computers and re-establishing trust after flashing a stock ROM?
Strange that fastboot commands work and adb doesn't.
Nope, but I tried connecting to another one and no dialog popped up.
Btw, an hour ago it just started working... All of a sudden...
I should be happy, but now I have no chance in finding what was the problem.
Anyways thank you for now, if I have any more issues I'll update.
I assume it's physical damage to the usb board/module (since it started working while no change to the software was done in the past few days).
I will order a new one just in case.
Thank you again guys!
Maybe a loose internal connection? You could try removing the back to looking for loose connections.
Did so, didn't notice anything strange.
I do have experience with soldering, but I would rather not touch it before I get a new one, just in case I screw up. Small components are no fun.
The thing that still bugs me though is I had fastboot working perfectly fine all that time. Oh well