Related
Hey there,
I have my Vibrant for a good year now since it came out pretty much. Last week it just stopped charging out the blue. The battery is completely empty and shows a thermometer with a warning sign and stops charging seconds after its plugged in. So I assumed it might be a battery malfunction and I got my spare battery in as soon as I came home and tried charging - same problem. I think it is highly unlikely that both batteries fail at the same time. Therefore, I assume there is something wrong with the temp sensor in the phone. I saw a few people have a similar problem with the epic 4G, but the discussion got really side tracked by other issues. My phone is rooted, but I was running stock froyo, so that shouldn't be the problem or should it?
I just wanna know if anybody had the same problems and if there is a quick solution, I google and forum searched a while but as soon as you throw in the term battery it gets spammed with battery life discussions.I just checked my files I have on the phone, apparently I have the premium insurance - does that mean I just can go to the next Tmo store and get a replacement? Any feedback is greatly appreciated.
Phill
Well for your problem, i suggest you try a different rom and see if the problem persists... maybe its a bug
And as for insurance, you mail the phone in and pay a deductible, which should be like 135$ or so. They send you a refurb.. or if you say it wus lost, you dont have to mail in phone
Sent from a cell tower to the XDA server to you.
thanks for the quick reply. Is there a way to reflash without a battery?
I don't see it as a bad thing. If your phone gets too hot and keeps charging that's going to burn something inside. When my phone won't charge I know I have let it down. So it can cool down. But to fix your problem reboot the phone. You can keep charging it after it boots up
Sent from my SGH-T959 using Tapatalk
pro1st said:
thanks for the quick reply. Is there a way to reflash without a battery?
Click to expand...
Click to collapse
As long as your phone can run successfully for a couple minutes, i dont see why not
Sent from a cell tower to the XDA server to you.
Mine did something similar. I picked it up after putting it on the charger. It was hot and would not come on. I unplugged it and let it cool off for a while and it cleared up.
I got that message once...
Vibrant was in a car dock, with power.
It was *HOT* out and sun was hitting the back of the unit. (A/C on of course)
Google Navigation was running (display brightness max)
Google Listen was running
Bluetooth was passing music to a speakerphone
When I run the phone with that setup, the charger can't even keep up with the phone power needs. The battery level slowly drops. No question the phone is working hard.
This was a true heat issue... I removed the charger and turned off the display to let it cool off a bit. (I was almost home).
So the question again, is your phone hot or is it a false reading?
Robert
Hey,
I am sorry I didn't clarify the actual battery temp. It is normal - so its neither in the sun or in a too cold spot when I try charging it. The phone probably runs for one for a few seconds before turning off so there is no chance of the battery stats wipe. I think I will try to find an external charger and try to charge the batteries this way to have enough juice for flashing a new rom. Thanks for all the replies!
Does it charge the battery with the phone off? If not, I don't think a new ROM will help.
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
c0olcast said:
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
Click to expand...
Click to collapse
Sorry for resurrecting an old thread, but a resolution never seemed to be made here. Has anybody found a fix to this?
As of yesterday, my wife is having the same issue with my old Vibrant phone which she now uses. It's flashed with Bionix V 1.3.1 and Tigerblood overclock to 1.2ghz. This could be the issue, the Tiger Blood overclock, but I'm not sure. I'm out of the country for three weeks and currently she's left with a dud of a phone that keeps giving her the temperature warning in the triangle when plugged in while the phone is powered off followed by it stop charging. When she turns it on, she gets to the SD card check and then the phone completely freezes. Once in a while it's able to stay on for a minute or so before freezing, but more often than not the phone does not fully turn on and just goes frozen after a few seconds, sometimes at the Tigerblood logon screen before making it to the desktop. Me being 4000 miles away doesn't make it easier to help her but I've recommended she leave the phone unplugged, battery out for the night to see what happens. I also told her to take off her silicon case thinking maybe that has something to do with the overheating. Well after 7 hours of her letting it sit to cool off like that, with the case off, she plugged it back in and is having the same issues as yesterday. Absolutely no progress made. One of her colleagues said she should try leaving the phone in rice confused:) so she's giving that a go and another guy in a phone shop who she went to for advice after work said that the motherboard might need replacing. I'm convinced all it needs is to have the Tigerblood removed or reflash a rom onto it but there's really no knowing unless I have it in my hand.
Is there any quick fix to this problem without having to do all that? Surely there must be a way to charge the phone without it heating up and freezing up. She's tried plugging it into different rooms, on her laptop, etc, none seem to get rid of the temperature problem. I've had the phone since August 2010 and never had any issues with it. I also never once saw that temperature error message so was taken aback when she showed me it over skype. I just upgraded to the S3 and gave her the phone 2 weeks ago, but surely it shouldn't just die out just like that? Thought the Vibrants were made tougher than that?
Any help would be greatly appreciated. Much thanks in advance
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Update- Phone doesn't even turn on anymore, no signs of life
danny_extremex said:
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
polosprt009 said:
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
Click to expand...
Click to collapse
Some kernels require a certain amount of power to fully boot the phone up and will not charge until it has 5% battery or so. I personally think her battery may be unable to hold a charge or like I said before it doesn't have enough juice to boot the phone because of the kernel. There is a way to charge the battery with the phone off. You can use ANY kind of usb cord, I used an old printer usb cable when I had to do this. All you do is cut off the side that is not usb and strip the positive and negative wires(red and black), then place the stripped wires on the positive and negative connectors on the back of the phone and insert the battery (make sure it's a snug fit). Plug the usb end into your pc and charge the battery that way, DO NOT let charge for over 2 minutes at a time. Wait five minutes and do it again if you have to. If she gets it to boot up, I would definitely flash a new kernel first to see if thats how the problem originated.
Sent from my SGH-T959 using xda premium
I can't seem to find a thread here with my exact concern and if there is I apologize..
Sometimes if I connect the charger overnight and try to wake-up the phone it is unresponsive. Also, when this happens the charge light will stay on even with the cable unplugged as if its still charging. Sometimes if I wait long enough the lock screen will slowly appear and then it works, other times I'll have to pull the battery.. This can also happen if the phone is just sitting for 1-2 hours without me using it but mostly with the charger overnight.
Anyone else having these issues? Just a little more info, I am using the 2750 Extended battery which is the only one I've used from day one. The original battery has never been used in this phone. Could this be a battery issue? It has done this before and after the last OTA update...
Bone stock, no root.
Hmmmmm....that's odd
Sent from my ADR6425LVW using XDA App
This happened to me as well for a while. I ended up having to reboot the phone which seemed to help for a bit. I always figured it was something lagging in the sense ui. If you end up with a solid answer, Id like to know as well.
Hmm , never had that happen or read any threads regarding it. Might have a bad phone if it's within the warranty get a new one.
UgXvibe said:
I can't seem to find a thread here with my exact concern and if there is I apologize..
Sometimes if I connect the charger overnight and try to wake-up the phone it is unresponsive. Also, when this happens the charge light will stay on even with the cable unplugged as if its still charging. Sometimes if I wait long enough the lock screen will slowly appear and then it works, other times I'll have to pull the battery.. This can also happen if the phone is just sitting for 1-2 hours without me using it but mostly with the charger overnight.
Anyone else having these issues? Just a little more info, I am using the 2750 Extended battery which is the only one I've used from day one. The original battery has never been used in this phone. Could this be a battery issue? It has done this before and after the last OTA update...
Bone stock, no root.
Click to expand...
Click to collapse
This happened to me once but my phone was super hot when it happened..it eventually led me to factory resetting my phone and I haven't had it since.
I think I'm gonna try using the battery that came with the phone for awhile to look for a change. I'd rather warranty the extended battery than the phone.. If that doesn't work I'll factory reset it.
This is exactly why I haven't rooted yet, gotta get the perfect unit first while I'm still under warranty.
Sent from my ADR6425LVW using xda premium
What cable were you using to charge it with?
I've had stuff like this happen with a few cheap cables, and occasionally with others. I've been told it is from well used cables breaking down on the inside or without good enough insulation.
Try a fresh or rarely used cable, after a fresh reboot. I ended up throwing a couple of old cables away and didn't have this problem again or anything similar until lately with a retractable cable I use.
Sent from my HTC Rezound using Tapatalk. Forgive autocorrect.
I have used both the cable and adapter from this phone and the one I had for my old Incredible. Doesn't seem to matter and the Rezound cable is obviously pretty new. That's why I'm hoping it's a battery issue. I'll keep you guys posted...
Sent from my ADR6425LVW using xda premium
Mine used to do that, it would also be somewhat unresponsive most noticable when doing the unlock pattern, it wouldn't make it all the way through the pattern like it thought I was lifting my finger, it did only do this when it was on the charger too. Then it just stopped doing it, I don't remember if it was when I rooted or if I changed chargers or what. Are you using the charger and cable that came with the phone? I may have been using my standalone battery chargers USB plug to charge when it was doing that. Has been about that long since it did it.
I use the charger and cable that came with the phone at work and my old Incredible charger and cable at home. Problem happens with both.
So it is not the extended battery. I installed the stock battery last night and it locked up again. Next stop, factory reset.
Sent from my ADR6425LVW using xda premium
yup,. still doing it..
In case anyone happens upon this thread with the same concern.... A factory reset did correct the problem.. And now I can safely root!!
Curious, when I get a new device one of the first things I do is do a factory reset.
It has been the fix for a number of devices in the past that I just do it automatically now.
Verizon will still exchange your device regardless of root/unlock. As long as it's a manufacterer issue, and not a result of you blowing up your phone from oc, or installing custom software and bricking it.
Hey guy, i was running CM9 nightly from a couple days ago and have been on the cm9 other roms since around mid january.
My phone started bogging down really slow and then i restarted it which took forever and when it finally restarted there was some crap about your device cannot be encrypted and needs a factory reset. So i then went for another reboot to go to CWM to restore a nandroid and it got stuck at splash screen.
I pulled the battery after a while and now i have absolutely nothing and can't even get the screen to turn on. i tried charging all night to see if it had just died to no luck.
Any tips?
the4finger said:
Hey guy, i was running CM9 nightly from a couple days ago and have been on the cm9 other roms since around mid january.
My phone started bogging down really slow and then i restarted it which took forever and when it finally restarted there was some crap about your device cannot be encrypted and needs a factory reset. So i then went for another reboot to go to CWM to restore a nandroid and it got stuck at splash screen.
I pulled the battery after a while and now i have absolutely nothing and can't even get the screen to turn on. i tried charging all night to see if it had just died to no luck.
Any tips?
Click to expand...
Click to collapse
Download mode?
Tried another charged battery?
can't get download mode and I have tried my old normal sized battery of which I'm not sure of its charge to no luck
Sent from my GT-P7510 using XDA Premium HD app
the4finger said:
can't get download mode and I have tried my old normal sized battery of which I'm not sure of its charge to no luck
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
Try USb jig
and try charging battery from external charger or a new battery
What u said in op can't brick a phone
Just tried a jig and got nothing on both batteries. i have the phone connected to a charger with the original battery and it's heating up ALOT in the top section near the camera.
I work with someone that has an SII so i might try their battery tomorrow if not i'm at ends with what could possibly have happened
Tried a battery of my workmate and still nothing.
I think the main board may be gone because it's giving me nothing
EDIT: Alirght since no one can seem to help me is there any repairers in australia for the hardware side of things?
So you didn't use stock battery, that maybe busted your phone
Sent from my sgs2 running cm9
so your saying the Samsung 2000mah battery busted it? If so I'd be the first!
Sent from my GT-P7510 using XDA Premium HD app
Oh it was samsung's battery. Well then chances battery causing your problem are much slimmer
Sent from my sgs2 running cm9
For a couple weeks now, ever since I had to fix my Music player not showing my files, my phone has had this weird habit:
It'll be plugged in. All the time. Pretty much 24/7. But as soon as I take it off the charger - give or take a few minutes - it will turn off. No warning. No nothing. To turn the phone back on, it has to be charging. When I turn it back on, the battery % will be anywhere between 0% and 100%.
I have no idea what's going on, and it's making it impossible to use the phone off the charger without the battery charger pack. And that lasts what - an hour at best?
I thought it might be the ROM I had installed, and I was going to revert to the stock ROM today, but I instead upgraded from 2.3.7 LiquidSmooth to LiquidSmooth's new ICS ROM. I thought it would work, but after setting everything up and letting go of the charger, it died again in a couple minutes. The difference this time was that it showed the htc screen, but then went black and nothing. With the old rom, it just went black and done.
I apologize if there's another thread on this, but I haven't been able to find anything online in the past week or three.
Thanks in advance.
Mine has been doin the same thing. Sometimes being difficult to turn back on. Totally stock phone. I think mostly when plugged in. I will try to keep track.
Sent from my ADR6400L using xda app-developers app
So far today it has shut down 3 times. Once while plugged in and twice not. All 3 times sent the batt from 3/4 charge to under 5% when I fired the phone up. I am usingthe stock batt but am going to maybe wedge somethingbetween the batt and the cover to see if it wil do anything. I dont want to do a full reset.....i may be switching to the galixy 3. But rumers of a 4 in beginning of 2013 may have me holding off.
Sent from my ADR6400L using xda app-developers app
I new battery fixed my problem
Sent from my ADR6400L using xda app-developers app
Yeah sounds like the battery has given up the ghost.
My phone has been doing this as well. This is the stock battery from March 2010. This only happens when Im not on WiFi. Also this only started after I flashed from the ICS leak to another ROM. I think its strange, but I ordered a new battery to be sure.
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.