Related
so, ive discussed IMO a very nasty thing about this phone I dont like. Of course my goal is to not let my battery die. But it has happened to me a few times. Im finding that after the battery dies, It takes me about 20 minutes to get the phone powered back on. Even if it is plugged into a power outlet. It simply does nothing for about 20 minutes after it is plugged in. Doesnt respond to power button, battery pull, etc.
So..I thought, maybe its a measure like blackberries where they wont power the radio back on until the battery reaches "x" percent. Doesnt seem to be the case either.
Ive had many HTC devices including the OG Evo, never seen anything like this...any ideas?
It's a mystery to me as well. It's happened a couple times to me. The only way I could power it on is by letting it sit on the charger for several minutes.
I think it might have to do with the way we rooted them. The developer mentioned an issue with letting the power go dead. It may not be a problem if you are in fast boot mode.
Hmmm...............
sent from my DAMN EVO!!!
Mine has a problem powering on while it is charging. I'll have to take out the battery and unplug it to get it to turn on.
im finding out that people who are using cwm have a problem charging with power off. Im using twrp so Im sure this doesnt pertain to me..but its got to be something kernel or recovery related. im gonna ask over in vipers thread and see what kind of answers I get
Happens to me often as well. When I plug mines in, its usually good to go about 2 minutes after the red light stops blinking.
Sent from my PG86100 using XDA App
Alchem!st said:
Happens to me often as well. When I plug mines in, its usually good to go about 2 minutes after the red light stops blinking.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
dude it took me 23 minutes to get my phone back on yesterday
Success100 said:
dude it took me 23 minutes to get my phone back on yesterday
Click to expand...
Click to collapse
Damn, that sucks. I'm using TWRP I also suspect it may have something to do with clockwork. Although it could just be that the battery needs to charge to a certain point for the phone to kick in. Who knows.. LOL
Sent from my PG86100 using XDA App
I just ended up trading mine in for a refund. I found the 3d offered very little over the original Evo, and mine had worse reception and call quality than the original. I am now using a nexus s until a better phone comes out.
Was running AOKP milestone 4 when spontaneously there appears on my screen an empty battery icon. This was in spite of the fact that battery was fully charged. The phone was completely unresponsive 2 rebooting or going into recovery. I was able to get my computer to recognize the phone 1 time and I odined back to stock gingerbread. Booted fine and seemed to be okay when it happened again. Now it just sits at an empty battery icon. The computer no longer recognizes it. If I plug it in to charge it briefly displays what appears to be stock recovery. The stock recovery however is not responsive to any key presses. Anyone experienced this or have any ideas how I can rectify it. Fortunately I have a backup fascinate and was able to activate it. I'd like to keep the other as a spare if I can figure out how to get it to respond.
Sent from my backup (lol) SCH-I500 using Tapatalk
thedoman said:
Was running AOKP milestone 4 when spontaneously there appears on my screen an empty battery icon. This was in spite of the fact that battery was fully charged. The phone was completely unresponsive 2 rebooting or going into recovery. I was able to get my computer to recognize the phone 1 time and I odined back to stock gingerbread. Booted fine and seemed to be okay when it happened again. Now it just sits at an empty battery icon. The computer no longer recognizes it. If I plug it in to charge it briefly displays what appears to be stock recovery. The stock recovery however is not responsive to any key presses. Anyone experienced this or have any ideas how I can rectify it. Fortunately I have a backup fascinate and was able to activate it. I'd like to keep the other as a spare if I can figure out how to get it to respond.
Sent from my backup (lol) SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Did you try switching batteries?
Sent from my Glitched AOKP Unicorn.
Absolutely. Tried 3 others all Samsung, all previously used w/o problem. Don't think AOKP did anthing. Can you flash a phone to death? I certainly have changed mine up enough over the last year.
Sent from my SCH-I500 using Tapatalk
thedoman said:
Absolutely. Tried 3 others all Samsung, all previously used w/o problem. Don't think AOKP did anthing. Can you flash a phone to death? I certainly have changed mine up enough over the last year.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Every piece of equipment has a different life span. If you can not Odin to fix it, it may be more than software.
Sent from my Glitched AOKP Unicorn.
thedoman said:
....Can you flash a phone to death? I certainly have changed mine up enough over the last year.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Flash memory does have a limit to the number of times that it can go through the erase/program cycle but it's somewhere between 10,000 and 100,000 cycles for NAND flash.
I've had some charging issues after flashing to AKOP, but that may or may not be related to your issue.
Sometimes I can get it to respond in download mode then take it to stock but most of the time it's just a waiting game. Everything seems to run fine on stock. If I go to CM7 or AKOP (or any ICS ROM) I randomly get instant battery drain and an somewhat unresponsive charging port.
I've also noticed some of the Fascinates that come through where I work only take certain batteries. Some take the blue Samsung and others take the black ones.
Hey guys,
I have the AT&T Note that I rooted thanks to this forum and its devs. The ROM I have on there currently is an ICS build from The Collective.
Anyways, the situation is that my phone ran out of juice and shut itself down. No problem there. I got my charger and plugged my phone into the wall.
Here's where the problem is: the screen won't activate even hours after I've left it plugged into the wall. However, it does seem to be vibrating every few seconds.
I would appreciate it if anyone could tell me what kind of joke my phone is playing on me. Thanks in advance.
that is odd that that would just happen like that. Have you unplug the charger then removed the battery for 5 or 10 seconds? Then try to boot on just battery
almost sounds like a hardware issue
Sent from my SAMSUNG-SGH-I717 using xda premium
tagmwar said:
that is odd that that would just happen like that. Have you unplug the charger then removed the battery for 5 or 10 seconds? Then try to boot on just battery
almost sounds like a hardware issue
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just tried it. Nothing happened
Do you have CWM? If so, try to get into it and see if the screen will show.
-Once you go NOTE, you'd say 4 inches a Joke
SKyRocKeting727 said:
Do you have CWM? If so, try to get into it and see if the screen will show.
-Once you go NOTE, you'd say 4 inches a Joke
Click to expand...
Click to collapse
Yes I have CWM on it, but my Note's screen won't turn on so I'm not able to access it...I tried connecting it to my computer but my computer won't recognize it either anymore.
I guess I'm just going to take it to my AT&T store nearby and ask if they can replace it.
Have you tried putting it in DL mode??
Sent from my SAMSUNG-SGH-I717 using XDA
Hold power button down for about 10 secs it will vibrate, quickly hold the volume up and down at the same time. It will reboot into recovery. Do a full wipe and reinstall ROM. That should help.
Sent from my G-Nizzle.
Thanks everyone, went to the AT&T store and found out that swapping out the battery fixed the problem...weird.
Sew if odin will reconize it and flash att recovery then start over
sent from my galaxy note running saurom 7.1 @1.83
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
stanleyopar2000 said:
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
Click to expand...
Click to collapse
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
jonah1234 said:
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
stanleyopar2000 said:
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
Click to expand...
Click to collapse
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
smtom said:
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I had 4.0 LiquidSmooth ICS JMOD my custom ROM on my phone ever since the rom first came out.and it was perfectly...fine...
and this same problem happened when I had GB ThunderShed CM7..but my gf told me to pull the battery out and leave it out for 20 minutes..then it put it back in. It worked. She did this many times with her Droid 1. Since it was problematic with this issue. (first android phone OF COURSE its going to have problems) Now she's an iPhone user i'm constantly trying to convert back lol
anyway...as stated before..it's now done it again and this time it's totally dead. my phone was trying to tell me something I bet.
How old is your phone?
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Doubt that'll work if its the same as mine. PC and adb won't see it. And I used known good batteries and charger from my other bolt.just gonna hold on to it in case I find one with a busted screen for cheap on craigslist
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Lightning Won't Strike Twice Folks
disconnecktie said:
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
I had 2 differernt batteries one extended...the other the stock small one. both would not charge. and both had decent battery power when I shut it off.
Shadow Death said:
How old is your phone?
Click to expand...
Click to collapse
Got it a month after it came out first 4G LTE phone maaan
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
this phone does not. I had two batteries with a decent charge and they didn't charge on it. The ROM I was using was a AOSP rom. not sense based...so there was no power menu and a fastboot option to uncheck
wampuscat said:
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
Click to expand...
Click to collapse
yep. it did die in my hands. I'm chalking this up to hardware failure as well...
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
two batteries and they do the same thing..and I cant boot into ADB mode if the damon can't detect the device on.
playerjunglejosh said:
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Yep. the Motherboard is fried. has to be.
Thank you so much everyone for your advice, concern and help..but nothing can fix or repair hardware failure to this extent
I got a used HTC Rezound. It's amazing...it's everything the T-Bolt should have been
even though I had this problem before and a long term battery pull fixed it...Looks like Lightning Will Not Strike Twice for The Thunderbolt.
Thank you for your concern and support....but it's just as good as a future spare parts phone on craigslist.
This thread can be locked now.
Hello,
So last night I was using my optimus g, the notification that my battery was too low came up, and the phone shut off. After that I went to charge my phone and the usual red light did not come up around the power button and the phone will not charge. There is no water damage or sudden incident that could have caused this to happen. AT&T will not replace the phone due to a small scratch on the front of the screen done a couple months ago. Does anyone have any suggestions about how to get my phone to charge and turn on again??
Any help is greatly appreciated! Thanks!
have you tried to hold the power button down for like 10 seconds? try a different plug outlet and plug it in and see what happens
If you can't get it working then send it in to LG since AT&T won't help you.
Have you tried a different charger? Tried usb charging? Somewhere in this forum are instructions for removing the back case and battery. Two others had similar problems and removing the battery helped.
Sent from my LG-F180K using xda app-developers app
Jank4AU said:
Have you tried a different charger? Tried usb charging? Somewhere in this forum are instructions for removing the back case and battery. Two others had similar problems and removing the battery helped.
Sent from my LG-F180K using xda app-developers app
Click to expand...
Click to collapse
Yeah, I tried a lot of different chargers, USB charging and different outlets. I will have to try to remove the battery i guess. AT&T told me that I could not have LG repair it because it has a small crack in the bottom left that I made a couple months prior to this happening. Do you know how to get to the thread about removing the battery? I cant seem to find it =/
Anyone have any other ideas?
Here's the thread for accessing the battery btw.
http://forum.xda-developers.com/showthread.php?t=2127122
Sent from my Optimus G
If that doesn't do the trick then replacing the damaged portion of the phone and then claiming warranty would probably work, especially since it's already bricked and you don't have to worry too hard about it not turning on again after you reassemble it because again, it's already bricked probably a whole lot cheaper than buying a new one off contract.
Sent from my LG-E970 using xda premium
DeathmonkeyGTX said:
If that doesn't do the trick then replacing the damaged portion of the phone and then claiming warranty would probably work, especially since it's already bricked and you don't have to worry too hard about it not turning on again after you reassemble it because again, it's already bricked probably a whole lot cheaper than buying a new one off contract.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
The only problem is that the crack is on the front class screen, and I have heard that the screen is hard to replace
Before you open it up and go fiddling around on the inside, try these (in order):
1. Hold down your power button for at least 15 seconds.
2. Plug in your charger
3. (If that doesn't work) Use a different outlet/adapter.
4. If all else fails, try the 15 second power button thing and then connect it to your computer.
My Nook Tablet's display wouldn't work once and it took me the better part of a week to figure out that holding the power button down for 10+ seconds manually turns it off (I was a noob). (I then plugged it into my computer instead of the charger and it powered on!) A lot of people forget to try the simple things first...
amazingbonz said:
The only problem is that the crack is on the front class screen, and I have heard that the screen is hard to replace
Click to expand...
Click to collapse
Ok, let me rephrase that. A new one is $450. You can get a screen/digitizer for ~$85. I'm not a math whiz but to me the difficulty is worth saving that much cash.
download mode
it could be a software problem try going into download mode (holding vol down and power then plugging it in at the same time) it may take a couple trys but if you can get into that then it could possibly be a software issue maybe its a prob with bootloader if it is try useing some teenybins somthing similar happened to me i unlocked the bootloader and everthing got better post back if you can get into download mode
I too have started having problems charging this phone when it goes all the way down which it does fast usually listing android operating system or my screen as the main culprit....try booting to bl then recovery and clearing cache and dalvic....I use twrp recovery and there no battery stat wipe function but in rom toolbox pro there is although the merits of such is questionable.....I also used a battery calibration app recently and it seemed to help... I've also had to plug it up and just leave it for a while whether it's convenient or not it works....???
I've wondered about awesome kernel cleaning script... As well as some of the battery saving apps in conjunction with Eco mode and power saver function.... I've used juice defender ultimate for a while and recently battery guru from Qualcomm and Antutu but same crash today leaving phone down 2 hours plus easily not to mention getting stuck in power save popup warning viscious cycle of popping up every keystroke is gonna get this device slammed up against a wall and I don't want to replace it but any help on this also appreciated....
Sent from my LG-E970 using xda premium
USB Cable
Have you tried another USB cable? :silly: I stopped using USB cords ever since my grandpa got a wireless charger (yes, my grandpa ) but you better be careful with those since not all of them are compatible with LG phones, check the reviews and device compatibility, mine is a Powermat 3X
im having the same problems too... using the latest cyanagen mod... the battery just doesnt hold the charges like it says and shuts off.. i need this phone as an alarm......
There's problems with fast charge for cm try turning it off its on by default
Sent from my LG Optimus G using xda app-developers app
Same problem ughhhhhhhhhhhhhhhhhhh
I have this problem now, and can't get it to work. Anybody figure it out?
So there seems to be a desease of optimuses
My phone was charging while I was sleeping, and I accidentaly putted my hand on my phone while I was sleeping, and the phone was seriusly hot! I got up, upluged the phone from the charger, let it cooldown, plug it in on another charger, the phone responded in the first place, but the red flashing light was coming up really quickly. I switched it of and on and now it is showing me the battery that is shown when the device is charging. Been doing this charge for like an hour or more, with varius attempts to switch it on but it still it wont switch on! Any tips or anything? I am going to leave it charging for a coupe of hours and see if I have any results...
My phone started having issues where it would randomly shut off and sometimes holding power for approx 20 seconds or so would turn it back on or other button combinations sometimes requiring me to force download mode. I have always been able to force it back on however previously when plugged into a charger the notification light wouldn't do anything.
It shut off yesterday and I have tried every combination of buttons for at least 30 seconds, including trying to force download mode with volume up and down and USB into computer and nothing. The difference this time every time I plug it in the notification light either is solid or pulsing rapidly and will not turn on or go to download mode.
Phone is rooted running paulicats aosp and has been since I got the phone 3 months ago, it was dropped in water the week I got the phone but was disassembled and cleaned that day with no issues until this last week.
Any help or input is greatly appreciated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bump
Sent from my SAMSUNG-SGH-I747 using xda app-developers app