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.
Related
i swear i have the worst luck. haven't even had the phone a day and already i went to check the time and the phone was off and wouldn't turn back on, had to pull the battery. now just a few min ago i felt a vibration in my pocket so i took the phone out and it was starting back up "starting services". it must have rebooted in my pocket.
if i go back into the sprint store for this they are not going to be happy to see me again after all the strings they pulled to get me into this phone after being well out of my 30 days with my 3d.
Edit: i just went to sprint and they tested the battery and said it was bad. maybe that's why it was charging so slow? hooked up to the charger the phone died while using it. that seems way too slow right?
Edit again. The new battery didn't fix my problem.
Ask for a new back cover. There have been numerous post about how some back covers are not a tight enough fit allowing the battery to break contact which results in a reboot. Sprint appears to be aware of this as there are reports of stores having spare back covers to give to people who request them.
mine had the updated cover with the rubber/foam inside. the phone was faulty, they replaced it and it looks like the problem is solved.
last night when i got the phone and i put it on the charger i started using it and it sucked the 15% of battery out when on the charger. i started charing at 7pm and by 2 am it was only at 50%. pretty sure some thing was wrong with the phone. this new one charged up in about an hour.
Mine does the same at random times of the day.... went to sprint and they told me it was a software bug... that sound right to you guys?
Sent from my MB855 using XDA App
mercNstein said:
Mine does the same at random times of the day.... went to sprint and they told me it was a software bug... that sound right to you guys?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Mine has been fine since it was replaced.
Sent from my MB855 using Tapatalk
I've had my phone reboot first thing in the morning when I first turn it on. When it happens, it reboots twice and then no problem thereafter. It's done this three mornings so far, rebooting twice each time. It's happened both before and after rooting. I wonder if it has to do with being fully charged and reboots until its no longer fully charged. Luckily it's not every morning and it's easy to live with until the update is released. I know we have the leak, but I'm waiting for the official update.
DualSportDad said:
Mine has been fine since it was replaced.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
ok cool ill look to replace mine then.
I had the same issue with reboots when I first started it up after it activated it would restart few times. Then today I had 60% battery life left and I powered off the phone and started it up again it said I had 3% battery left. Not sure whats going on. Also I am having bluetooth headset issues. My top of the line motorola finiti constantly loses connection and has to regain it. I have also experienced the call audio issues on several occasions. Unfortunately for me I was given this phone by Sprint and can't return it for another device. My only recourse is to wait till Motorola comes out with a firmware update.
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
this is my second rezound. On the first one when the battery died it could no longer charge. i tried all chargers with zero luck. i was running stock with 1.02.605.6 with root and CWM. I exchenaged it and ran clean rom 4.1 w Amon Ra 3.15. I am now having the same problem. i bought another battery so i could atleast turn it on. what could this be?
PLS HELP
You are trying the AC charger that comes with the phone?
Via Rezound using XDA Premium
yes i have tried everything including the adapter that came with the phone.
Try a car charger, could be the amperage o draw.
i bought another battery and called verizon. They are sending me a new phone. for the return i need to get this thing back to stock from clean rom 4.1. if i re lock the bootloader and run GB RU. would i be good? will that take the boot loader back? radios?
It will still show it had once been unlocked, there is a thing on htcdev about it. You may get by or you may incur the charge back it depends on how close they (VZW employees) look at it after it scans in at the VZW warehouse, once it gets back to HTC too late to charge you back, but that is the first thing our friends at HTC look for.
Really strange battery experience last night. I've never had any problems with my phone.
Last night, I put my phone on the dock (EZO) around 1am. it had about 30% charge at the time... I saw the charge light on....
This morning, I looked expected to see green and saw no light at all. When I picked up the phone, it was cold... Turning the phone one didn't work.
Plugging the std charger it came with did nothing. No charge light at all.
I put my extended battery in, and the phone came up just fine. I then put the dead std battery into the back charger of the dock and left it for a couple hours as I got ready for work.
When I got to work, I put it into the phone and it had close to a 60% charge. I plugged in the charger at work and the charge light came on. Right now it is plugged in and approaching 90%.
Not really sure what happened last night. but apparently, when the bat loses all power, charging it via the phone may not work for some reason.
Paulb787 said:
i bought another battery and called verizon. They are sending me a new phone. for the return i need to get this thing back to stock from clean rom 4.1. if i re lock the bootloader and run GB RU. would i be good? will that take the boot loader back? radios?
Click to expand...
Click to collapse
NO, that would not work because your hboot is higher and the ruu will see that and fail.
Alright so my Vibrant won't charge. I JUST recovered my phone from a brick, (I was having issues with the battery life on Slim Roms 4.0 compared to 3.9--in the middle of flashing back I accidently wiped my internal memory. As I was recovering it using Odin, my fat cat jumped on my bed and caught on my phone cord bricking it.) Flashed using Heimdall and was able to get my phone into working order.
Now, I placed Slim Roms 4.0 back on my phone initially after the unbricking to have something working on it, even though the battery life less than impressed me.
So I charged it like normal yesterday, got it to 100% and was fine and dandy with it working. (Still sucking up battery life like a vampire in a fat camp.)
So the update 4.1 went live yesterday, I flashed it immediately to that. The battery life was amazing! So I do the normal thing when I flash to a new ROM. Let it die completely before charging it completely. It's now dead and will not charge.
Symptoms;
I plugged in my normal cable for work (a cheap cable I purchased off of Ebay.) And up comes the round loading symbol. Followed by a darkening of the screen, followed by nothing.
One thing to note, is while it has it's loading circle on, the bottom buttons light up when I touch them.
My Steps;
-I attempted different USB ports since I charge through my work computer. No luck.
-I "borrowed" my co-workers USB cord and USB to wall plug. Attempted the new cable in the computer first. No luck.
-Plugged the borrowed USB into the wall charger. Same thing happens.
-Used my own cheapy cable in wall charger. Same thing.
-Took co-workers complete set and plugged it in in a different room. Nothing.
-Took out my battery, plugged in USB, placed battery back in. Nothing.
-Hold down the Vibrant buttons to get into Bootloader, it resets the loading circle and nothing more.
So now I'm sitting here wondering what to do. I do not have rubbing alcohol readily available, however since it charged to 100% yesterday I do not believe that is the issue, but I'd be willing to try if I had access.
Something you should know, I am using a Samsung Epic 4G battery in my phone.
-For those who might judge saying it is dumb, I have gotten 54 hours out of that battery on one ROM before, that is with texting, talking on the phone and installing apps. I'm fond of this thing, however I have my stock battery at home still.-
Any suggestions you guys have would be appreciated. I have tried things that I found on this forum and basic tech support to no avail. (I am at work so the things I can use are fairly limited. However cords are of no shortage.)
Alright, I unplugged my phone from being plugged into the wall charger for an hour and 3 minutes later it decides to turn itself on.. Not sure what's going on but I'm not going to complain.
So my question now is, can anyone explain this or help prevent this in the future?
From what I've heard draining a battery until it dies can damage it. But, I'm not an expert on that. It's possible that the battery needed more time to recover from the drain.
rmelendez3 said:
From what I've heard draining a battery until it dies can damage it. But, I'm not an expert on that. It's possible that the battery needed more time to recover from the drain.
Click to expand...
Click to collapse
Really? I was always told it prolongs battery life. Now I need to research this! Thank you.
knoka said:
Really? I was always told it prolongs battery life. Now I need to research this! Thank you.
Click to expand...
Click to collapse
I had something similar happen when running lithium volt ROM. My battery completely died and the phone cut off (obviously.) I plugged it in the charger and it immediately tried to boot the phone up but it was bootlooping at the startup screen. I let it sit there for 20 minutes or so thinking maybe it is charging but as soon as i unplug the charger the phone cut off. Luckily I have an extra battery, popped it in, flashed a new ROM thinking that was the problem, turns out it was something to do with the ROM(maybe it needed a certain amount of battery power to boot up). My completely dead battery worked on the cm7 ROM I flashed, plugged in the charger and it booted up normally and started charging.
Sent from my SGH-T959 using XDA Premium App
iTz KeeFy said:
I had something similar happen when running lithium volt ROM. My battery completely died and the phone cut off (obviously.) I plugged it in the charger and it immediately tried to boot the phone up but it was bootlooping at the startup screen. I let it sit there for 20 minutes or so thinking maybe it is charging but as soon as i unplug the charger the phone cut off. Luckily I have an extra battery, popped it in, flashed a new ROM thinking that was the problem, turns out it was something to do with the ROM(maybe it needed a certain amount of battery power to boot up). My completely dead battery worked on the cm7 ROM I flashed, plugged in the charger and it booted up normally and started charging.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Oh so it could be ROM related? :/ That makes sense considering I just installed a brand new ROM. Thank you!
knoka said:
Oh so it could be ROM related? :/ That makes sense considering I just installed a brand new ROM. Thank you!
Click to expand...
Click to collapse
Yea it could be ROM related but it also could be a number of other things. Hopefully flashing a new ROM will fix the issue.
Sent from my SGH-T959 using XDA Premium App
iTz KeeFy said:
Yea it could be ROM related but it also could be a number of other things. Hopefully flashing a new ROM will fix the issue.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Thank you. I might just have to downgrade back to 3.9. It's almost a shame. xD
I'm going to test my old battery in this ROM just to make sure before I downgrade.
You need to use your Samsung usb charger, and wall adapter only. These two are the only ones that will actually work. I had this same problem and realized it was because I wasn't using the Samsung stuff. Even when pugging into the computer, use the Samsung USB cabe only. As for the battery your using... I wouldn't recommend it, no matter the fantastic battery life you must be getting.
whatiznt said:
You need to use your Samsung usb charger, and wall adapter only. These two are the only ones that will actually work. I had this same problem and realized it was because I wasn't using the Samsung stuff. Even when pugging into the computer, use the Samsung USB cabe only. As for the battery your using... I wouldn't recommend it, no matter the fantastic battery life you must be getting.
Click to expand...
Click to collapse
Daw it's a fellow Samsung battery.
Thank you about the cable, I need to purchase another one anyways, mine at home seems to not be connecting very well. :/
ROM. some roms do that. it will not let you power up while charging if the battery is very low. you will get the circle and the battery symbol after. sometimes you still cant unless you pull the battery. happened to me many times
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.