I accidently installed cwm on my phone with Rom manager and let it die. Obviously it wouldn't charge up because i was using cwm. So I popped in the extended battery and installed amon ra 3.15 with Scotts cleanflash tool. The dead battery still won't charge. How do I fix it?
Sent from my ADR6425LVW using Tapatalk
have you tried turning your phone off then putting in the dead battery. place it on the charger while the phone is still off and try to charge it. enable/disable fast boot may help also.
when testing cwm a few months back I ran into the same issue, but it was solved by switching to amon ra and charging the dead battery once in a standalone charger.
***EDIT: I just came across this thread when doing a search:
http://forum.xda-developers.com/showthread.php?t=1489687
This should help you out.
randpost said:
have you tried turning your phone off then putting in the dead battery. place it on the charger while the phone is still off and try to charge it. enable/disable fast boot may help also.
when testing cwm a few months back I ran into the same issue, but it was solved by switching to amon ra and charging the dead battery once in a standalone charger.
***EDIT: I just came across this thread when doing a search:
http://forum.xda-developers.com/showthread.php?t=1489687
This should help you out.
Click to expand...
Click to collapse
Thanks. Im still toying with it but so far all I get is a flicker of the orange light after I hit the power button. Will try with fast boot enabled.
Sent from my ADR6425LVW using Tapatalk
pmania said:
Thanks. Im still toying with it but so far all I get is a flicker of the orange light after I hit the power button. Will try with fast boot enabled.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
excerpt from another post:
"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!"
If it comes down to it, just take the battery into VZ and get a defect replacement.
randpost said:
excerpt from another post:
"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!"
If it comes down to it, just take the battery into VZ and get a defect replacement.
Click to expand...
Click to collapse
I did something similar to this. Reboot phone to bootloader while plugged in, then swap to the dead battery then rebooted. Then I let it charge to about 40% before I had to take it off. It died a while ago and the charging problem persists.
Sent from my ADR6425LVW using Tapatalk
pmania said:
I did something similar to this. Reboot phone to bootloader while plugged in, then swap to the dead battery then rebooted. Then I let it charge to about 40% before I had to take it off. It died a while ago and the charging problem persists.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
try the recovery method with the battery in question, meaning: don't use the extended. just throw the the phone onto usb with the dead battery and try adb recovery.
hopefully you can save yourself a trip to VZ.
randpost said:
try the recovery method with the battery in question, meaning: don't use the extended. just throw the the phone onto usb with the dead battery and try adb recovery.
hopefully you can save yourself a trip to VZ.
Click to expand...
Click to collapse
I will tomorrow. I don't have computer access now. I'll keep the extended charged though
Sent from my ADR6425LVW using Tapatalk
pmania said:
I will tomorrow. I don't have computer access now. I'll keep the extended charged though
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes! Good luck and happy Easter!
randpost said:
Let us know how it goes! Good luck and happy Easter!
Click to expand...
Click to collapse
Welp I just tried the adb reboot recovery and I am still getting the flashing light.
Will try again.
When this happened to me I had to keep plugging and unplugging the charging cable while holding the power button to get it to turn on. It's worth a try!
I did what others did n plugged into computer n booted to bootloader/ect
My rezound died this week end and wouldnt charge. Took it the VZ store and found out they no longer had in-store tech support. Anyway, the in store person concluded the charge port somehow wouldnt take a charge. Ended up calling tech support for a replacement. Should be here by Tues
Well I figured it out. I just got home to try again and I looked at the cmd window. It turns out I only typed "adv reboot recover" so yea my bad . Worked like a charm!
Sent from my ADR6425LVW using Tapatalk
pmania said:
Well I figured it out. I just got home to try again and I looked at the cmd window. It turns out I only typed "adv reboot recover" so yea my bad . Worked like a charm!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
awesome man. glad you got it working.
Related
so i followed the instructions to unroot my evo 3d...went back to stock sprint rom and when i did the fastboot and adb i chose to reboot and now my phone won't turn on. did a search i can't find any resolve to this problem. ive tried to take the battery out...boot into recovery...even when i plug in my phone the led light doesn't come on anymore...battery is fully charged too...any ideas?? help me please
poktangju said:
so i followed the instructions to reroot my evo 3d...went back to stock sprint rom and when i did the fastboot and adb i chose to reboot and now my phone won't turn on. did a search i can't find any resolve to this problem. ive tried to take the battery out...boot into recovery...even when i plug in my phone the led light doesn't come on anymore...battery is fully charged too...any ideas?? help me please
Click to expand...
Click to collapse
Try pulling out the battery and putting it back in, then plugging the phone in and rebooting it.
tried your suggestion and still won't power on...led light doesn't even come on when plugged in to charger...
VladBelsky said:
Try pulling out the battery and putting it back in, then plugging the phone in and rebooting it.
Click to expand...
Click to collapse
See if this helps http://forum.xda-developers.com/showthread.php?t=1281729
thanks...looks like my phone is d u n...dun
VladBelsky said:
See if this helps http://forum.xda-developers.com/showthread.php?t=1281729
Click to expand...
Click to collapse
This is a complete guess/longshot but take out the battery, plug in the charger and hold down the power button. While the power button still held, unplug the power cord from the phone and insert the battery. This once worked to get my old Xperia X10 to respond. Different phone, but thought it might be worth a try.
thanks for trying to help but no dice...
spywhite said:
This is a complete guess/longshot but take out the battery, plug in the charger and hold down the power button. While the power button still held, unplug the power cord from the phone and insert the battery. This once worked to get my old Xperia X10 to respond. Different phone, but thought it might be worth a try.
Click to expand...
Click to collapse
Have you tried adb reboot recovery? If by some miracle adb sees the phone you can just flash a recovery and load up a rom. Might have to try acting like you power it on. It could be actually powered up but not screen or led responsive.
3VO Sent
I've had a problem like this with my phone before, I let my battery get to zero while in recovery mode and phone wouldnt do anything. The battery seemed like it was so low the phone didn't recognise it was there. I hooked it up to a variable dc voltage box and jumped it for a bit and it worked. U could either stop at a sprint store and see if they have a charged battery, or get one of those things that charges the battery outside of the phone, its like a universal battery charger or somethin.
Sent from my PG86100 using xda premium
sorry for my ignorance but how to i go about doing the adb reboot recovery?
ifly4vamerica said:
Have you tried adb reboot recovery? If by some miracle adb sees the phone you can just flash a recovery and load up a rom. Might have to try acting like you power it on. It could be actually powered up but not screen or led responsive.
3VO Sent
Click to expand...
Click to collapse
i do have a wall charger that charges the battery outside the phone and i was really hoping that it was due to low battery but even with a fully charged battery still won't power on. thx tho
troublein420 said:
I've had a problem like this with my phone before, I let my battery get to zero while in recovery mode and phone wouldnt do anything. The battery seemed like it was so low the phone didn't recognise it was there. I hooked it up to a variable dc voltage box and jumped it for a bit and it worked. U could either stop at a sprint store and see if they have a charged battery, or get one of those things that charges the battery outside of the phone, its like a universal battery charger or somethin.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Have you tried another battery ?
Sent from my HTC EVO 3D X515a using XDA App
Are you using an old version of twrp?
sent from my EVO 3D via XDA app
i had twrp 1.0 before the phone bricked...
z50king said:
Are you using an old version of twrp?
sent from my EVO 3D via XDA app
Click to expand...
Click to collapse
Twrp 1.xxx would think the phone was in recovery after the battery died. It made it so you needed to pull the battery for a while to let the capacitor drain and reset twrp
sent from my EVO 3D via XDA app
Download ADB from http://developer.android.com/sdk/index.html
Download the zip
unzip somewhere
Open SDK manager
Download sdk platform-tools and tools (other stuff is optional)
open cmd and use "cd <directory>" to navigate to platform-tools in the android sdk folder (e.g. "cd /android-sdk-windows/platform-tools/"
Download htc sync http://dl3.htc.com/application/HTCSyncv3.0.5579.exe
uninstall after installed
connect phone to computer
type "adb devices" in a cmd/terminal
if it recognizes your device, it's not bricked
try "adb reboot bootloader" and see if it gets into bootloader. If it does, flash TWRP 2.0 and flash a ROM. Your device should now be usable.
If that doesn't work, you could probably download the bootloader file and push it to your phone but you'll have to ask someone else about that.
What is TWRP?
Sent from my HTC EVO 3D X515m using Tapatalk
Castellano2 said:
What is TWRP?
Sent from my HTC EVO 3D X515m using Tapatalk
Click to expand...
Click to collapse
Team Win Recovery Project
http://teamw.in/project/twrp2
Hey guys,
I installed Rezrom v3.2 on my Rezound yesterday, and it was stable for the most part until this morning. My phone died last night and even though it has been on the charger all day I can't get it to boot into bootloader. When I try to power it on the phone boots then dies immediately. After that I have to let it sit on the charger for another 10 minutes or so before I can try anything again.
I've tried a battery pull (like 40 times)
Like I said can't boot into bootloader, and as such can't get into recovery.
When I connect it to my computer the computer makes sounds as if hardware has been connected, but it doesn't show up in "My Computer"
Please help
Sounds like a bad battery I would see if you can find a friend with a rez and see if their battery works? Have you tryed booting without the battery in not sure if that works on this phone worked on my evo but that sounds like a battery problem to me
Sent from my ADR6425LVW using XDA
Kbarnes57 said:
Hey guys,
I installed Rezrom v3.2 on my Rezound yesterday, and it was stable for the most part until this morning. My phone died last night and even though it has been on the charger all day I can't get it to boot into bootloader. When I try to power it on the phone boots then dies immediately. After that I have to let it sit on the charger for another 10 minutes or so before I can try anything again.
I've tried a battery pull (like 40 times)
Like I said can't boot into bootloader, and as such can't get into recovery.
When I connect it to my computer the computer makes sounds as if hardware has been connected, but it doesn't show up in "My Computer"
Please help
Click to expand...
Click to collapse
I cant recall exactly, but somewhere on these forums there is a thread or two about this. And they also have exact steps on how to fix it, ive never heard of it with rezrom, but im sure it would be the same solution. I wish i could help more but ill see if i can locate where i found the thread.
It's because of clockwork, it doesn't allow the phone to charge in this state
Your only hope is another battery to get it powered to flash amon ra or a battery charger. I've used my thunderbolt to fix this problem
Sent from my ADR6425LVW using Tapatalk
superchilpil said:
It's because of clockwork, it doesn't allow the phone to charge in this state
Your only hope is another battery to get it powered to flash amon ra or a battery charger. I've used my thunderbolt to fix this problem
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
The recovery won't let it charge but it should still provide power to the phone when pluged into the wall or usb. I have amon ra and I had 2% battery level pluged it in booted to recovery flashed a kernel did the hboot flash rebooted and still had 2% then it started charging so I know the phone recives power in recovery. Besides it will deffinetly charge when it is powered off which he said he tried and still couldnt boot I say bad battery but you could be right mabey it is your recovery
Sent from my ADR6425LVW using XDA
Symptoms:
1. Hitting power does nothing
2. Power + down volume does nothing
3. Plugging into AC power = no green light
4. Plugging into USB (computer) power = green light (which stays on after unplugging)
I have:
1. Tried battery and SD card pull while plugged in and not plugged in
2. A friends BH5X battery
3. Leaving the battery out for an hour
4. Leaving it charge via the Motorola AC adapter over night
I am out of ideas. Something else that may help... when the phone died I plugged it in (AC) and it rebooted to the recovery menu. I hit reboot, and since then it will not power on... or charge apparently.
Even with a charged battery it wouldn't boot?
Sent from my MB870 using xda premium
CadenH said:
Even with a charged battery it wouldn't boot?
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Had a coworker charge my battery in his Droid X to 80% before he had to leave. I don't know what his battery was charged to in his phone, but I tried his as well with the same results. Does it have to be charged to 100%?
Xeno62277 said:
Had a coworker charge my battery in his Droid X to 80% before he had to leave. I don't know what his battery was charged to in his phone, but I tried his as well with the same results. Does it have to be charged to 100%?
Click to expand...
Click to collapse
I wouldnt think so.
So the battery just simply died and wont boot up now? You werent doing anything else to it?
jsgraphicart said:
I wouldnt think so.
So the battery just simply died and wont boot up now? You werent doing anything else to it?
Click to expand...
Click to collapse
My battery will boot my coworkers Droid X. When it died it shutdown due to low battery. I plugged it into AC power... it booted up to recovery, and I hit reboot from the menu... after that it is completely unresponsive.
Xeno62277 said:
My battery will boot my coworkers Droid X. When it died it shutdown due to low battery. I plugged it into AC power... it booted up to recovery, and I hit reboot from the menu... after that it is completely unresponsive.
Click to expand...
Click to collapse
If the battery worked on your coworkers droid X then its not your battery. Which means its hardware or software related. Were you running any roms or anything or were you completely stock?
jsgraphicart said:
If the battery worked on your coworkers droid X then its not your battery. Which means its hardware or software related. Were you running any roms or anything or were you completely stock?
Click to expand...
Click to collapse
I've been running Eclipse 2.1 for a while now with no issues... even if I was having a ROM issue... wouldn't still at least boot to the M logo or stock recovery?
Xeno62277 said:
I've been running Eclipse 2.1 for a while now with no issues... even if I was having a ROM issue... wouldn't still at least boot to the M logo or stock recovery?
Click to expand...
Click to collapse
Yes, it should. Or if you had bootstrap on there (which you should if you flashed stuff) it would boot into that if you turned the phone on when the phone was plugged in. Its really hard to say what it is when your phone simply died of low battery and now wont boot. I'm just as stumped as you right now since you pretty much tried everything I would have.
jsgraphicart said:
Yes, it should. Or if you had bootstrap on there (which you should if you flashed stuff) it would boot into that if you turned the phone on when the phone was plugged in. Its really hard to say what it is when your phone simply died of low battery and now wont boot. I'm just as stumped as you right now since you pretty much tried everything I would have.
Click to expand...
Click to collapse
Yeah when I said it booted to recovery I meant the bootstrap recovery. Since it won't boot I guess I don't have to worry about VZW finding out it was rooted... lol. Maybe I can get them to replace it.
Xeno62277 said:
Yeah when I said it booted to recovery I meant the bootstrap recovery. Since it won't boot I guess I don't have to worry about VZW finding out it was rooted... lol. Maybe I can get them to replace it.
Click to expand...
Click to collapse
Yeah, maybe you can get a replacement before they even know its rooted. lol. Just keep trying to boot it though. Maybe you'll get lucky.
Does your computer recognize the phone when you plug it in? You said the light comes on when its connected to your pc. If you can get adb running you can try to reboot the phone using adb.
Sent from my MB870 using xda premium
CadenH said:
Does your computer recognize the phone when you plug it in? You said the light comes on when its connected to your pc. If you can get adb running you can try to reboot the phone using adb.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
No, and it will not power on... just green light... which stays on even after disconnecting it from the usb.
I did some more googling and reading. Then came across the Factory style programming cable.
So you flashed your phone and now it thinks the battery is dead (even though it's not) and it won't let you flash it again to fix it? Or, your battery really is dead and you don't have a way to charge it because your phone is soft-bricked and won't charge the battery. What do you do?
With this cable you don't even need a battery in your phone. This is our clone of what is generally referred to as a Motorola "Factory Cable".
Unlike a normal USB cable these cables are wired in a way that compatible Motorola phones recognize as a "factory" programming cable. This allows the phone to power up and be flashed without having a battery in the phone. Depending upon the model of the phone, it may also boot up differently than it does with a normal USB cable.
Click to expand...
Click to collapse
Sounds like my problem exactly (minus the flashing part... which I did over a month ago). I went ahead and ordered it
Xeno62277 said:
I did some more googling and reading. Then came across the Factory style programming cable.
Sounds like my problem exactly (minus the flashing part... which I did over a month ago). I went ahead and ordered it
Click to expand...
Click to collapse
Cool. I hope this works out for you.
Xeno62277 said:
I did some more googling and reading. Then came across the Factory style programming cable.
Sounds like my problem exactly (minus the flashing part... which I did over a month ago). I went ahead and ordered it
Click to expand...
Click to collapse
Please let us know just for informational purposes. .
cyanogenmod
If you can get to bootstrap why not just use a card reader throw eclipse or some rom on your micro which should have come with an sd adaptor and just reflash from bootstrap?
Perpetual Void said:
If you can get to bootstrap why not just use a card reader throw eclipse or some rom on your micro which should have come with an sd adaptor and just reflash from bootstrap?
Click to expand...
Click to collapse
It won't power on at all... that's why I need the factory cable... it doesn't require a battery.
Well, I finally got that factory programming cable. That didn't power the phone on either... it did power on my fiancee's droid 2 with no battery in it though. I figured the phone was completely hosed (also noticed the battery bulging a bit), so I got a warranty replacement. Since I couldn't even get it to boot with the programming cable I have no doubt VZW will not waste any time trying to repair it... at least I hope that's what they will do.
If a lithium ion battery begins to bulge it can be dangerous if not replaced. This is rare but with these batteries if one were defective it could reach 1.5V per cell during use. This would render the battery unchangeable and its discharge would cause the copper plating to create a short circuit in the cellphone.
Sent from my MB870 using xda premium
S3AL3DF4T3 said:
If a lithium ion battery begins to bulge it can be dangerous if not replaced. This is rare but with these batteries if one were defective it could reach 1.5V per cell during use. This would render the battery unchangeable and its discharge would cause the copper plating to create a short circuit in the cellphone.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Yeah I chucked that battery and got a new one. Thinking that's what killed my old phone.
Good Morning. Last night I flashed the latest RUU so I could install Nils latest Business Sense. After the RUU flash, everything booted fine so I rebooted into the boot loader and flashed the latest TWRP. It said it flashed fine, press power to reboot. I did that and now nothing.
I don't get a charging light when I plug it in, I let it sit over night on the charger, still nothing.
I've pulled the battery, I've tried connecting it to my PC so I can run adb reboot, nothing.
The phone is S-OFF. I've done some messed up stuff before but I've always been able to at least get a response out of the phone. With this, I don't get anything.
Appreciate any help anyone can provide. Thanks!
To clarify, I can't get into HBOOT, nothing. Why would flashing TWRP do that?
ChaOConnor said:
Good Morning. Last night I flashed the latest RUU so I could install Nils latest Business Sense. After the RUU flash, everything booted fine so I rebooted into the boot loader and flashed the latest TWRP. It said it flashed fine, press power to reboot. I did that and now nothing.
I don't get a charging light when I plug it in, I let it sit over night on the charger, still nothing.
I've pulled the battery, I've tried connecting it to my PC so I can run adb reboot, nothing.
The phone is S-OFF. I've done some messed up stuff before but I've always been able to at least get a response out of the phone. With this, I don't get anything.
Appreciate any help anyone can provide. Thanks!
To clarify, I can't get into HBOOT, nothing. Why would flashing TWRP do that?
Click to expand...
Click to collapse
Silly question, but did you verify md5 sums on the RUU and twrp?
If not go ahead and check those from where you downloaded them and see if they match.
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
Silly question, but did you verify md5 sums on the RUU and twrp?
If not go ahead and check those from where you downloaded them and see if they match.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not a silly question at all. Yes, they do match.
I'm just at a loss, I can't get the phone to register anything. Won't turn on, won't pick up when connected to a PC, no screen flash, no charging light. Nothing. Very odd.
ChaOConnor said:
Not a silly question at all. Yes, they do match.
I'm just at a loss, I can't get the phone to register anything. Won't turn on, won't pick up when connected to a PC, no screen flash, no charging light. Nothing. Very odd.
Click to expand...
Click to collapse
You can't get into the bootloader?
Sent from my ADR6425LVW using Tapatalk 2
ChaOConnor said:
Not a silly question at all. Yes, they do match.
I'm just at a loss, I can't get the phone to register anything. Won't turn on, won't pick up when connected to a PC, no screen flash, no charging light. Nothing. Very odd.
Click to expand...
Click to collapse
Ok next thoughts. If you know for sure your battery had a decent charge, leave battery out for a few hours and try again.
If you are not sure see about trying someone elses charged battery or go to a VZW store and try one of their batteries.
Realistically the only thing twrp could do is possibly have the same bug CWM has and not allow the phone to charge when powered off. Hadnt heard of this but also havent run 2.2 since i just got the sgsiii
Sent from my SCH-I535 using xda app-developers app
ijustwantmydock said:
You can't get into the bootloader?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
No, it's like it won't turn on.
I thought it was like the old CWM issue when a battery ran down and you had to let it charge over night. I did that. But nothing happens even when I connect it to a PC, I should in theory if it's the same problem, adb and reboot it.
I may very well have bricked it, but it just doesn't make sense. The MD5's matched. There was no power disconnect. It finished properly and told me to push power to reboot.
nosympathy said:
Ok next thoughts. If you know for sure your battery had a decent charge, leave battery out for a few hours and try again.
If you are not sure see about trying someone elses charged battery or go to a VZW store and try one of their batteries.
Realistically the only thing twrp could do is possibly have the same bug CWM has and not allow the phone to charge when powered off. Hadnt heard of this but also havent run 2.2 since i just got the sgsiii
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Okay, I'll give that a shot. Thanks!
ChaOConnor said:
Okay, I'll give that a shot. Thanks!
Click to expand...
Click to collapse
You see it more with computers but sometimes when things go funky, you cannot just do a normal battery pull as the capacitors dont drain that fast. So by leaving the battery out and letting the capacitors drain you might luck out.
You can also for a quick try pull battery and hold the power button down for 30 seconds and try. If not try leaving the battery out for a few hours.
If that doesnt work let us know and we will come up with other ideas.
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
You see it more with computers but sometimes when things go funky, you cannot just do a normal battery pull as the capacitors dont drain that fast. So by leaving the battery out and letting the capacitors drain you might luck out.
You can also for a quick try pull battery and hold the power button down for 30 seconds and try. If not try leaving the battery out for a few hours.
If that doesnt work let us know and we will come up with other ideas.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's funny you said that, I was thinking about when I flash the bios on my MB I always drain the capacitors after I flash and before I reboot. I tried the quick pull and held the power for 30 seconds. No joy.
I'll let it sit without the battery for a few hours and try.
The ***** of it is, I'm in Afghanistan right now, so I'm pretty much SOL for getting another battery, etc. Oh well... guess when I get home from deployment I'll just buy a few phone if I really hosed this up.
Did you download the first version of the recent update he put up because it was messed up and said not to download that one. Try contacting Con see if he can help
Sent from my Sense4 ICS Rezound
LakerStar25 said:
Did you download the first version of the recent update he put up because it was messed up and said not to download that one. Try contacting Con see if he can help
Sent from my Sense4 ICS Rezound
Click to expand...
Click to collapse
Just posted over there, thanks!
nosympathy said:
You see it more with computers but sometimes when things go funky, you cannot just do a normal battery pull as the capacitors dont drain that fast. So by leaving the battery out and letting the capacitors drain you might luck out.
You can also for a quick try pull battery and hold the power button down for 30 seconds and try. If not try leaving the battery out for a few hours.
If that doesnt work let us know and we will come up with other ideas.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No dice, nothing happening. Hmm... I'm really at a loss. I just ordered another batter to try, but that's going to take a week or two to get here.
EDIT: Good news! Left the battery out over night, this time it booted up fine. Defintely related to some weird electrical issue after flashing.
ChaOConnor said:
No dice, nothing happening. Hmm... I'm really at a loss. I just ordered another batter to try, but that's going to take a week or two to get here.
EDIT: Good news! Left the battery out over night, this time it booted up fine. Defintely related to some weird electrical issue after flashing.
Click to expand...
Click to collapse
Bah. None of this voodoo stuff works on my phone. I've become certain ICS broke it but I have a cracked screen... :crying: Unless something electrical is fried. I never smelled anything...
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.