My Rezound was at 7% then completely shot off and would not charge but it did give off a blinking or solid light for a few seconds, then turned off and wont charge.
I took it to VZW and they put a new battery and it worked, so I bought a new battery.
Then the next week I had my phone half charged in my pocket when I went to go skateboarding. After I skated I checked my phone for calls, texts,etc. It was off and would not turn on, so I went to charge it and the same thing as first time happened.
I think the phone is destroying the battery after a certain amount of time. I know my phone is not over heating for sure.
I was running Newts Endeavor rom but I doubt thats the cause. VZW is sending me a replacement phone so will wait and see.
Any ideas on the problem?
are you running CWM?
If you are check this thread http://forum.xda-developers.com/showthread.php?t=1489687
IrvChynaman said:
are you running CWM?
If you are check this thread http://forum.xda-developers.com/showthread.php?t=1489687
Click to expand...
Click to collapse
This thread might be right it did happen when I switched from an old cwm to cwm touch.
Ndaoud360 said:
This thread might be right it did happen when I switched from an old cwm to cwm touch.
Click to expand...
Click to collapse
Its a problem with both regular and touch versions of CWM. I highly recommend you switch over to Amon Ra
IrvChynaman said:
Its a problem with both regular and touch versions of CWM. I highly recommend you switch over to Amon Ra
Click to expand...
Click to collapse
Well I cant now because battery is dead I might wait till replacement comes and charge battery then switch to amon and send back replacement if thats the cause.
Ndaoud360 said:
Well I cant now because battery is dead I might wait till replacement comes and charge battery then switch to amon and send back replacement if thats the cause.
Click to expand...
Click to collapse
you can try running the "adb reboot" command and see if your phone boots into the OS. from there your battery should be charging which you can use to give your phone enough juice to switch recoveries. if it doesn't reboot after several tries, then yeah i would say wait for the replacement to switch over to Amon RA.
IrvChynaman said:
you can try running the "adb reboot" command and see if your phone boots into the OS. from there your battery should be charging which you can use to give your phone enough juice to switch recoveries. if it doesn't reboot after several tries, then yeah i would say wait for the replacement to switch over to Amon RA.
Click to expand...
Click to collapse
Yea device not found error.
The drivers for the phone are on the computer right and dont have htc sync on it
Related
I have been running BulletProof 2.2 and flashed the newest Faux Kernel yesterday with no problems. Today randomly I found the phone with the Black Screen of Death and I did the 3 button power reset trick. I thought it worked but when I looked down again the phone off.
I pulled the battery but couldn't get the phone to respond. I plugged it in and the charging indicator light did not appear. I tried with a second battery and had the same result.
I have tried to get into recovery and hboot with no luck on either battery.
Plugging into a computer also yields no response.
Does anyone have any clue what could have happened? Thanks.
miclflores said:
I have been running BulletProof 2.2 and flashed the newest Faux Kernel yesterday with no problems. Today randomly I found the phone with the Black Screen of Death and I did the 3 button power reset trick. I thought it worked but when I looked down again the phone off.
I pulled the battery but couldn't get the phone to respond. I plugged it in and the charging indicator light did not appear. I tried with a second battery and had the same result.
I have tried to get into recovery and hboot with no luck on either battery.
Plugging into a computer also yields no response.
Does anyone have any clue what could have happened? Thanks.
Click to expand...
Click to collapse
Which recovery version were (are) you running?
Try replacing the battery and seeing if the phone boots up.
Then use xboarders latest recovery or stock recovery because some of the older custom recoveries don't charge the phone while it's powered off.
Here's a tip! The Anker batteries on Amazon are a good buy! They work well and you can even get them with a Universal charger so you shouldn't have this worry again.
Binary100100 said:
Which recovery version were (are) you running?
Try replacing the battery and seeing if the phone boots up.
Then use xboarders latest recovery or stock recovery because some of the older custom recoveries don't charge the phone while it's powered off.
Here's a tip! The Anker batteries on Amazon are a good buy! They work well and you can even get them with a Universal charger so you shouldn't have this worry again.
Click to expand...
Click to collapse
I just flashed the other recovery that allows charging while off.. but I never thought about the problem he might be having. If the battery dies all the way, and it isn't capable of charging while powered off, you have a phone that can't work until the battery has at least enough juice to get to the point it CAN charge don't you? I am assuming that is the problem you are thinking he has?
Binary100100 said:
Which recovery version were (are) you running?
Try replacing the battery and seeing if the phone boots up.
Then use xboarders latest recovery or stock recovery because some of the older custom recoveries don't charge the phone while it's powered off.
Here's a tip! The Anker batteries on Amazon are a good buy! They work well and you can even get them with a Universal charger so you shouldn't have this worry again.
Click to expand...
Click to collapse
I am running 5.0.2.7.
I do have an Anker battery, with external charger as a backup, and already tried it with that and the stock battery. I tried again yesterday evening and I got it to turn on but when I looked away and looked back again, the phone was off again and I have not had any response since.
It's almost as if it can't get power from the batteries or from a charger. Will probably go to a local store today and see if they can do anything.
Thanks
miclflores said:
I am running 5.0.2.7.
I do have an Anker battery, with external charger as a backup, and already tried it with that and the stock battery. I tried again yesterday evening and I got it to turn on but when I looked away and looked back again, the phone was off again and I have not had any response since.
It's almost as if it can't get power from the batteries or from a charger. Will probably go to a local store today and see if they can do anything.
Thanks
Click to expand...
Click to collapse
Can you get access to the bootloader?
Binary100100 said:
Can you get access to the bootloader?
Click to expand...
Click to collapse
Nope. No response at all. Getting a warranty exchange from T-Mobile. Thanks.
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
Am I just missing it? I did a search "clockworkmod recovery now official" nothing...
Just curious as I was going to post in the thread that it has been found that CWM will not charge a battery when it gets so low that the phone shuts down.
Marine6680 said:
Am I just missing it? I did a search "clockworkmod recovery now official" nothing...
Just curious as I was going to post in the thread that it has been found that CWM will not charge a battery when it gets so low that the phone shuts down.
Click to expand...
Click to collapse
I don't know if this is the one you were looking for or not, but this is the only one I could find:
http://forum.xda-developers.com/showthread.php?t=1478012&highlight=cwm+recovery
Hope I helped!
I cant find it either.
maniac2k said:
I cant find it either.
Click to expand...
Click to collapse
Thought it was just me who couldn't find that thread, although one of the users got a little intense near the end of the thread and it vanished shortly after that. (I actually have a question in to the forum mod about that....)
I don't think the other thread is the one the OP referred to.
People are saying CWM is messing up people's ability to charge from a dead battery, can't confirm it myself but the original thread is gone.
That thread isn't it.
So Mods... whats up?
I wasn't following the thread lately... someone got trollish?
idk. I have the touch recovery image incase it is gone forever for some reason.
You can still get the official CM recovery from Clockwork mod can't you ? I think it got pulled because people were complaining about some issues with it and Jmztaylor was swearing and blowing up the thread saying it was the user's fault and nothing wrong with the recovery itself.
Well, people say that you can not charge with the phone powered down when using CWM, switching to amon ra fixes it.
Having started with the evo 4g I love amon ra. Touch recovery is neat, but I'd rather have reliable. Never had an amon ra backup fail to restore. Far to many times I have with CWM.
Sent from my ADR6425LVW using XDA App
Just for the record, I never once said it is the user fault. Me and nilsp worked out our issue and looking into the issue he was having. Everyone else was complaining about having to create 1 file on the sdcard. As for the original thread I'm sure it was straight up deleted.
But onto the issue at hand IRT charging. Yes the charging issue was reported. I also talked to the guy on irc. I tried to recreate the same issue and I couldn't exactly.
Here was my setup. Both extended battery and regular battery. Both dead to the point the phone shut off. Plugged into the wall the light would light then go off. But I left it there. For about 2 hours. And when I came back the light was lit and I could boot the phone. When the phone got booted it was at around 40%. So that tells me it is charging just not showing the light. I did this with both batteries.
This is my experience with it FWIW....
Some people are impatient... not waiting long enough for the battery to charge up to a decent point.
That could be the issue.
Marine6680 said:
Some people are impatient... not waiting long enough for the battery to charge up to a decent point.
That could be the issue.
Click to expand...
Click to collapse
This. I figured out pretty quickly I needed to wait until the orange LED quit blinking before I could boot up my phone.
Sent from my Vizio tablet using xda premium
jmztaylor said:
Just for the record, I never once said it is the user fault. Me and nilsp worked out our issue and looking into the issue he was having. Everyone else was complaining about having to create 1 file on the sdcard. As for the original thread I'm sure it was straight up deleted.
But onto the issue at hand IRT charging. Yes the charging issue was reported. I also talked to the guy on irc. I tried to recreate the same issue and I couldn't exactly.
Here was my setup. Both extended battery and regular battery. Both dead to the point the phone shut off. Plugged into the wall the light would light then go off. But I left it there. For about 2 hours. And when I came back the light was lit and I could boot the phone. When the phone got booted it was at around 40%. So that tells me it is charging just not showing the light. I did this with both batteries.
This is my experience with it FWIW....
Click to expand...
Click to collapse
while I haven't used CW on the rezound (since amon ra was already ported and it works, so I didn't bother), I don't see any recovery being the reason of phones not "charging properly", since this has been a complaint since launch day if the battery died, the phone did not want to charge.
Pretty sure HTC even opened a ticket about it.
nrfitchett4 said:
while I haven't used CW on the rezound (since amon ra was already ported and it works, so I didn't bother), I don't see any recovery being the reason of phones not "charging properly", since this has been a complaint since launch day if the battery died, the phone did not want to charge.
Pretty sure HTC even opened a ticket about it.
Click to expand...
Click to collapse
CWM on the bionic kept the bionic from ever fully turning off when connected over USB until they fixed it with an update. So I believe it to be possible.
Sent from my ADR6425LVW using XDA App
From what I understood...
When charging with the phone off, the device actually boots into a special recovery mode where the screen is disabled.
The MT4G did this. The first versions of CWM had a bug where it would boot into the regular recovery mode instead when trying to charge with the device off.
So yea phone wont boot or charge or do anything. No a single screen will turn on i press the power button and it just stays the way it is dead. Im pretty convinced that i bricked it since i cant get to anything. All i was doing was making a backup and then when i went to flash the zip file it said no sdcard. So i did what i always do with this error bull the battery take out sdcard put it back in and go back to recovery to try again. Except this time it wont power back on into anything. Is there any hope for me?
What recovery did you have installed?
con247 said:
What recovery did you have installed?
Click to expand...
Click to collapse
i had amon ra recovery i know there were problems with cwm but i had amon ra and i cant get to it either
Leave the battery out and make sure it is unplugged from USB. Do that for like an hour.
con247 said:
Leave the battery out and make sure it is unplugged from USB. Do that for like an hour.
Click to expand...
Click to collapse
ok ill try that and get back to you.
It probably isn't dead. I have heard this happening before and leaving it without the battery or USB connection for several hours fixed it.
con247 said:
It probably isn't dead. I have heard this happening before and leaving it without the battery or USB connection for several hours fixed it.
Click to expand...
Click to collapse
Same concept as with computers I assume. By leaving it disconnected it allows all the capacitors to drain which means anything funky going on with the phone should "reset"
Sent from my ADR6425LVW using xda app-developers app
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.