My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
durthquake said:
My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
Click to expand...
Click to collapse
No, but I am sure if you have a custom recovery on your phone with a custom rom an official update sure isn't going to help ..but I figured it would just error out. How did it brick it ? he was unable to load Hboot anymore ?
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Could you get into hboot and run the ruu? If you can do that, the phone isn't bricked...
Sent from my ADR6425LVW using XDA App
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I suspect the no charging is due to running the battery down all the way. There's a thread or two about that issue. I think the solution was to pull the battery, plug in the charger then put the battery back in while phone is connected to charger. Then you might have to wait up to 30 minutes for the light to turn on and for it to start charging.
And yeah, if you can boot into hboot you should be able to get the phone back with RUU or if the ROM is fine then flash Amon Ra recovery in fastboot.
It didn't allow anything to be done in hboot. It won't even turn on now, i have him my battery to try and still doesn't turn on.
Sent from my ADR6425LVW using Tapatalk
Well read through this thread:
http://forum.xda-developers.com/showthread.php?t=1434532
and see if you can at least get it charged up again. Then go from there.
Both me and my wife have had the OTA for at least a week and we have not had any issues with the OTA.
Also, I must say, this is the first time I have heard of the OTA causing bricking of the unit.
If you can't get it charged, try the writing hack to get it involved. Basically you just take a regular usb cable and snip the connector off. From there you take the ground and the power, and then you put the ground and power to the battery in the respective places. Worked for a bad Atrix flash that killed my battery.
Sent from my Galaxy Nexus using Tapatalk
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
drtnsnw said:
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
Click to expand...
Click to collapse
That's not a brick. That's a pain in the ass.
tekhna said:
That's not a brick. That's a pain in the ass.
Click to expand...
Click to collapse
+1
a brick is just what it is.. a brick.
which means the phone is done. you can't use it again.
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If it can get to the HTC screen, it isn't bricked. Put your battery in his phone and see if it can get to HBOOT.
durthquake said:
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I don't think you can write off the battery/charging issue. It takes some time for people who have let their battery fully drain to get the phone to charge it again although they were able charge on an external charger iirc. Anyway, point is it may be the phone not the battery that needs to "wake up" (for lack of a better term) again.
So definitely go through that dead battery charging thread and try everything in there to get the phone to charge the battery again. Then you'll know the phone is functioning as it should, atm it may not be.
I don't understand how the the OTA forced itself since all of Scotts ROMs are debloated. Everyone that rooted and debloated running stock, said that the update failed in recovery, I know I witnessed it on mine. Being on an ICS build, one would think that the update wouldn't even be downloaded.
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
con247 said:
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
Click to expand...
Click to collapse
I am said friend.
Durthquake sits in the cube next to me. He watched the whole event transpire.
Here's what happened and what was tried and the resolution,
Rezound reboots to the HTC screen. Won't show the think brilliantly words. Just stayed on HTC.
So I did a battery pull and rebooted phone and same thing. Just HTC.
Now I reboot to recovery, get hboot and try to do a wipe. It blinks like its going to try to go to recovery then turns off.
Do another battery pull boot maneuver and it does the same thing.
As we are at work I did have to work so I leave it on the stock wall charger for about an hour and try to turn on again. HTC screen so I leave it to see what happens, maybe I didn't wait long enough.
Like 35 minutes later screen goes black.
Now it won't power on, won't go to hboot, basically a brick. So I pull my battery give it to durthquake who gives me his rezound battery. His phone turns on, mine doesn't.
Now I try pulling sim, sdcard, and putting my battery back in. Still nada. Phone be properly bricked.
Bring it home put sim, sdcard, and battery back in and put on HTC wall charger overnight. In the am nothing. Still a pretty beats brick.
Go to vzw and the try charging turning on etc. Nada. They say since the ota they've had about 5 of these in.
The resolution is vzw sending me a new rezound and I buying a new phone so I can give the resound to my gf.
Sent from my Galaxy Nexus using Tapatalk
Related
I'm having a hard time turning my phone on while its charging. It is difficult otherwise, but impossible during charging. Am I the only one with this issue?
Sent from my PG86100 using XDA Premium App
I literally just experienced this, so frustrating. Especially with a case.
Sent from my PG86100 using XDA Premium App
Are you rooted and have clockwork? There are issues with it with power when off, not charging and could be result kept it.
I don't have clockwork, have the other one. Name escapes me currently.
Sent from my PG86100 using XDA Premium App
This is one of the reasons I am going for the SGS2. Most times I have to--have to--do a battery pull to get it to turn back on. Sometimes the SDcard too. Sometimes it doesn't even charge. Sometimes I charge it while on and wake up to a green light, phone locked hard off (requiring battery pull and sdcard pull), and when I boot it up (if I can) the battery is completely dead.
It's a major issue with the 3d. There have been a ton of threads. And BTW, it happens on rooted AND stock devices. My phone died last night. Took me 32 effin minutes to get it to come back on. One of the reasons I'm getting rid of it
sent from my DAMN 3D!!!
Success100 said:
It's a major issue with the 3d. There have been a ton of threads. And BTW, it happens on rooted AND stock devices. My phone died last night. Took me 32 effin minutes to get it to come back on. One of the reasons I'm getting rid of it
sent from my DAMN 3D!!!
Click to expand...
Click to collapse
2 days before release I stopped into my local Radioshack to play with the demo phone. I saw it turn on, we played with it. Powered off...and never came back on. One of my friends did that eventually too.
...can't say I'm not scared of that happening to me.
daneurysm said:
2 days before release I stopped into my local Radioshack to play with the demo phone. I saw it turn on, we played with it. Powered off...and never came back on. One of my friends did that eventually too.
...can't say I'm not scared of that happening to me.
Click to expand...
Click to collapse
I can believe it...
How the f this thing made it into production with this big of a software glitch Or whatever the he'll it is riddles me
Success100 said:
I can believe it...
How the f this thing made it into production with this big of a software glitch Or whatever the he'll it is riddles me
Click to expand...
Click to collapse
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
pinky059 said:
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
Click to expand...
Click to collapse
Actually I absolutely noticed this before rooting...but back then I barely ever powered off. Nothing to flash, no way to flash it. I'm pretty sure it was just the same except we had much much much less reason to power off and reboot.
daneurysm said:
Actually I absolutely noticed this before rooting...but back then I barely ever powered off. Nothing to flash, no way to flash it. I'm pretty sure it was just the same except we had much much much less reason to power off and reboot.
Click to expand...
Click to collapse
I never did. I could power it on no problem before rooting. Didn't flash anything (I like Sense, what can i say...)....anyways, I noticed it afterwards and maybe it is true what that guy at AlphaRev said, it is the way HTC designed it for some weird reason....
Not a big deal for me though, now that he told me that...
pinky059 said:
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
Click to expand...
Click to collapse
this happens to my coworker that has this phone, and she is NOT rooted. And the above method never worked for me. Ive done that a million times trying to get it back on. Thanks for the tip though..
This has happened to me as well several hundred times it seems! It also did it when the phone was new. We had gone away on vacation like the week after the 3D came out, my phone had died while we were out, I plugged it into the charger, went to power it back on a couple hours later, and NOTHING! Probably took me a good 20-25 minutes to finally get it to come back on, with me eventually pulling the battery. This was stock at the time.
My 2 biggest gripes with the 3D, signal/call quality, and the power on glitch...
So for some unknow reason I opened my lockscreen this morning and did a little facebooking, some texting... anyway I rebooted whle I was in the shower to clear the caches and when I got out it was off. I pushed the power button repeatedly,vol down and pwr, battery pulls, and nothing. I let it sit with the battery out on my dresser while I was at work aprox. 5hrs and when I got home put the battery in and let it charge for about 3 or 4 hrs. The light dont come on when plugged and it still wont boot. Tried my freinds battery no dice. I'm very frustrated that it just "died" for no reason I never had heat issues or reboot issue. I'm on the leaked ruu running BAMF v1.2 with no problems.
My question is whether anyone else has had this problem. I'm sure their is no fix something is really wrong with my hardware but I just wanted see what others have experienced. FYI my rezound was about 18 days old...
Well, I definitely can't think of a more cut-and-dry example of a hardware failure. I'd take it back immediately and see if you can get a physical replacement at a Verizon store.... hopefully a store in your area still actually has the Rezound for sale..
had the same problem, try a different battery.
can you boot into bootloader?
http://forum.xda-developers.com/showthread.php?t=1544933
Happened to me sort of phone was at 7% battery then automatically shot off no down animation like it's suppose to. So I thought the battery was just fully dead so I charged it and the light came on for a minute and the shot off and no charging. I went to VZW and it was the battery 3.8v and then they gave me a new battery half off 3.7v and it worked and no more ics battery charging issues as well.
Ndaoud360 said:
Happened to me sort of phone was at 7% battery then automatically shot off no down animation like it's suppose to. So I thought the battery was just fully dead so I charged it and the light came on for a minute and the shot off and no charging. I went to VZW and it was the battery 3.8v and then they gave me a new battery half off 3.7v and it worked and no more ics battery charging issues as well.
Click to expand...
Click to collapse
They are replacing the 3.8's for free if you call and complain, call and try to get a credit for the 3.7 battery you bought...
mjones73 said:
They are replacing the 3.8's for free if you call and complain, call and try to get a credit for the 3.7 battery you bought...
Click to expand...
Click to collapse
Damn I should have known! VZW owes me $20! Well I would have rather spent the $20 because 3.8v is terrible with ics even with fix.
Try Pulling SIM Card Trick
When I put my Rezound in the car dock, the Rezound powered down and wouldn't restart. While out of the car dock, the Rezound would reboot but crash when starting the desktop and continue the cycle between boot and crash. Different symptoms from yours but the solution may work. I was able to boot and operate the Rezound without a SIM card so I could backup my data. A new SIM card did not help. So I did a factory reset and wipe (without the SIM card). Put the original SIM card back in the phone. Restarted the Rezound and it has been working better than before.
See if the phone will start without a SIM card. Otherwise, the electronics may have died.
Also, Verizon may terminate your SIM if you exchange the phone. I learned the hard way. Your choices are to have Verizon note in their system to NOT TERMINATE the SIM card, or the other choice is that Verizon will need to give/send you a new SIM card with the new refurbished phone. If you keep the original SIM card, put the SIM card in the new phone when you receive it.
Good luck,
I had the same problem once my phone would not charge or boot. I read somewhere that if you plug in your phone and take out the battery for a bit like 5 - 10 seconds and put the battery back in and make sure to put the back cover back on it should start charging. You have to leave it pluged in when you take out the battery. It worked for me hopefully it will work for you too.
Thanx guys it was the battery went to Verizon put in the new battery and it poped on made me feel dumb Cus I tried my friends battery
Sent from my ADR6425LVW using XDA
There may be an issue with the new ICS RUU I'm not sure.
I've been running Nils' ICS Business sense and on my first rezound the battery stopped charging. So I went back to VZ and got a new one, no matter of taking the battery in/out fussing with it changed the situation.
My 2nd rezound came in and I flashed the new ruu and loaded up nils 3.2 at the time. Now just last night it stopped charging the battery the same as my first phone.
I used the same recovery, CWM and the same rom as well. I'm not sure what to make of this. I thought it was just my first phone before my second one started doing the same thing last night.
I can plug them in and the orange charge light will come on for about 3 seconds then shut off.
If I had some way to charge the battery I could try and see if I could fix it but they both now do not charge batteries. I'm going to have to go back to verizon for a replacement again...
winston856 said:
I used the same recovery, CWM and the same rom as well. I'm not sure what to make of this.
Click to expand...
Click to collapse
Considering that CWM has known issues with the Rezound, why would you be using it?
Via Rezound using XDA Premium
krelvinaz said:
Considering that CWM has known issues with the Rezound, why would you be using it?
Via Rezound using XDA Premium
Click to expand...
Click to collapse
I was just going to say..umm very well known issue with cwm . I didn't think anyone was still using it.
Sent from my ADR6425LVW using xda premium
krelvinaz said:
Considering that CWM has known issues with the Rezound, why would you be using it?
Via Rezound using XDA Premium
Click to expand...
Click to collapse
Yea but I'm using amon ra and had the same problem
Sent from my ADR6425LVW using XDA
Hard to tell what you are using, your post says you were using CWM....
If you are still using it note that one of the issues is charging...
...CWM was causing serious issues, like when your battery would die, it wouldn't re-charge..
Click to expand...
Click to collapse
Via Rezound using XDA Premium
winston856 said:
There may be an issue with the new ICS RUU I'm not sure.
I've been running Nils' ICS Business sense and on my first rezound the battery stopped charging. So I went back to VZ and got a new one, no matter of taking the battery in/out fussing with it changed the situation.
My 2nd rezound came in and I flashed the new ruu and loaded up nils 3.2 at the time. Now just last night it stopped charging the battery the same as my first phone.
I used the same recovery, CWM and the same rom as well. I'm not sure what to make of this. I thought it was just my first phone before my second one started doing the same thing last night.
I can plug them in and the orange charge light will come on for about 3 seconds then shut off.
If I had some way to charge the battery I could try and see if I could fix it but they both now do not charge batteries. I'm going to have to go back to verizon for a replacement again...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1489687
Your issue is CWM... I went through the same thing.
So I got my Amaze on Friday, rooted and installed Energy Rom on Saturday, and phone just died on me on Sunday.
I was in the middle of playing Scramble with Friends and phone froze up on me. I had to take the batter out to reset it since the power button was not responsive. After I pulled the battery and put it back in, the phone would turn on.
So i read and read and found out people usually bought new batteries since the most likely culprit was a dead battery. I have a friend with the same phone and tried his battery. I saw the HTC Logo come on for a brief second and then that was it, nothing else. Phone died again and did not turn on (under his batter). I recharged my battery in his phone and tried that as well, but no luck.
Any ideas what went wrong and what I can do to fix this?
The phone is completely dead and not turning on. So that means I can't get into bootloader and recovery.
About Phone:
Unlocked Bootloader
TWRP recovery
Faux Kernel
ENERGY Rom
Any incite on this would be great. Thanks in advance!
Plug it in to the wall charger for 30-45min. Unplug and pull battery again. Put battery back in and you should be good...
Don't be alarmed if the orange led light flashes... It's normal when the phone dies. Be happy you're using twrp and not an old recovery that doesn't have charging while off
http://forum.xda-developers.com/showthread.php?t=1561104
Amaze Bricked
http://forum.xda-developers.com/showthread.php?t=1575191
[Q] Bricked Amaze Won't turn on
I hope that's XBoarder's TWRP 2.0.0...
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks, i actually read those threads before i posted. I think there are more threads about that but i tried all options and none seemed to work. I will try plugging it in the wall and pulling battery out but the battery is at a 100% charge right now (i can confirm from a friends phone). However, if its just a glitch, then i will try the wall charger trick.
Thanks.
ars88 said:
Thanks, i actually read those threads before i posted. I think there are more threads about that but i tried all options and none seemed to work. I will try plugging it in the wall and pulling battery out but the battery is at a 100% charge right now (i can confirm from a friends phone). However, if its just a glitch, then i will try the wall charger trick.
Thanks.
Click to expand...
Click to collapse
Once you get it booted, I recommend 4EXT recovery... But that's just my opinion
Sent from my HTC_Amaze_4G using Tapatalk 2
Thanks - tried the battery solution but unfortunately it didn't work out for me. Phone just refuses to power up.
Assuming its an official brick.
i have a similar problem, well my battery had charged and running fine for several months, so i unplugged the battery to put my sim on it, and plug it back in when it was booting up it froze on the boot logo, so i took off the battery again so i can reboot it
and ever since it wont come back on, wont either go to the bootloader, so i let it charged all night and nothing happen no led blinking or on, so got my friends amaze's battery to test and it would not do anything at either, right now i am waiting for my replacement, but i hate the fact that this had happen to me
oh wow - well i ordered a replacement as well. I really hope it doesn't come down to a software issue and they don't end up covering the device since it has been rooted.
If the phone is completely dead and non-booting, there's no way for T-Mobile to determine if it's rooted or not. Only until it gets back to HTC to be refurbished could they (HTC) find out but at that point it won't matter to anyone anyhow.
And it couldn't possibly be a software issue. There's something physically defective inside the device that caused it to die.
htc amaze 4g refuse to turn on.
hi all, i'm a newbie here, though i have always loved the XDA. I unlocked my bootloader last night, downloaded and reinstalled my fav apps since i didnt do a backup. while i was downloading the XDA app, my fone freezed and eventually went off. When i tried to get it back on, it got stuck on the white htc screen and later went off after some seconds. It has refused to come on till the time of this post. i really need urgent advice.
I was yet to install a recovery software before the tragedy occurred.
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.