I've been noticing (especially since a little after the GB update) my battery dying very quickly... sometimes not lasting more than 6 hours of moderate use.
I started reading threads here, there, and anything a google search would bring back. Apparently the battery drain is caused by the system's suspend process going rogue. I installed the full version of System Panel to monitor my usage, and sure enough suspend was taking up a lot more cpu cycles than anything else on my phone.
From reading further there isn't any specific phone setting/app that can fix this bug. Then I read something interesting... someone said that they only see the problem if they plug their phone in (usb or wall charge... doesn't matter), then unplug it without a restart.
Since I sit at a desk all day I frequently plug my phone in (nandroid backups, moving files to/from my sd card, etc.). I decided to do a test. I already have Tasker kill my ringer when my phone is plugged into any usb, so I added an exit task to reboot the phone when I disconnect usb.
I disconnected my phone from usb, and it restarted automatically... exactly what I wanted. Since then I haven't seen suspend do a damn thing. I have turned wifi on/off, killed data sync/turned back on, etc... all the things people have tried to fix the issue. Still nothing over the past couple of hours for suspend.
I will continue to monitor... so far it looks very promising.
Look forward to seeing your results!
Sent from my DROID X2 using XDA App
Yeah, I'm betting that will work just fine. I've been seeing it go nuts after being plugged in for a while and did mention it in another thread. I was suspicious of suspend but hadn't had enough time to be sure. Now that I know its that well have to see if there is a more elegant fix than restarting every time we unplug. That does work though. Good job point out the exact problem.
Sent from my DROID X2 using XDA App
What are you using to auto reboot when u-plugged??? I can't find that option in system panel or task manager.
Sent from my DROID X2 using Tapatalk
colonel187 said:
What are you using to auto reboot when u-plugged??? I can't find that option in system panel or task manager.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Appliation called TASKER. It allows your phone to autoperform routines based oncertain events
How did you set up the profile? I've been missing around for a bit and i cant figure it out...
Sent from my DROID X2 using XDA Premium App
I tried the reboot trick and im going on 16 hours at 70% battery. Plus system panel shows cpu under 1% when device is suspended.
Sent from my DROID X2 using Tapatalk
Thank you for finding this out. I tried this on my DX2 after full charge and its at 62% going on 11 and a half hours with moderate use.
Will deff. do from now on, would love to know wtf is up with this.
Seems like every phone has there bugs. I came from htc incredible and ut wont charge to 100% while on. You have to bump charge it while off to get the lost 10%
Sent from my DROID X2 using Tapatalk
So, are you supposed to unplug, then restart or shut down (while still plugged in), unplug, then restart? I understood it as the latter, but you're making it sound like the former. I tried method two today and I'm at 50% after 13hrs of moderately heavy use (1-2hr streaming music, a lot of texting, etc.), which I'm pretty happy with. It's a definite improvement over the last few days.
I must be doing it wrong, can't seem to fix the bug
Sent from my DROID X2
Unplug first. Then reboot.
Sent from my DROID X2 using Tapatalk
colonel187 said:
Unplug first. Then reboot.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I've done that, my phone must just hate me
Sent from my DROID X2
does it have to be a full reboot or can it be a hot reboot?
So far this seems to be working for me. I did the reboot after unplug this morning. Will update later on. Battery hasn't dropped nearly as quickly as it has before when going through these forums using the browser on the 3g network connection. It used to flat out suck the life outrageous my battery in what seemed like 2hrs flat before when browsing on 3g...
If its as simple as rebooting my phone after every charge im cook with that as i have read it's good to reboot at least once a day anyways and that seems like the perfect time for doing it. Thanks to the info. VERY useful
Not sure. If you can hotboot and it works. I would like to know.
Sent from my DROID X2 using Tapatalk
colonel187 said:
Not sure. If you can hotboot and it works. I would like to know.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Sry but what exactly is hotboot? Is that when u reboot with option on power button instead of just power down wait and power up?
After a few days I can definitely say that having Tasker reboot my phone after unplugging from USB has GREATLY improved my battery life. Tasker is kind of expensive as far as apps go... you could always get a free reboot widget from the market, and just remember to hit it when you unplug
Hotboot essentially just reboots the O/S and not the entire phone. Its more like logging out and then logging back in on a windows machine.
Sent from my DROID X2 using Tapatalk
Related
so, ive discussed IMO a very nasty thing about this phone I dont like. Of course my goal is to not let my battery die. But it has happened to me a few times. Im finding that after the battery dies, It takes me about 20 minutes to get the phone powered back on. Even if it is plugged into a power outlet. It simply does nothing for about 20 minutes after it is plugged in. Doesnt respond to power button, battery pull, etc.
So..I thought, maybe its a measure like blackberries where they wont power the radio back on until the battery reaches "x" percent. Doesnt seem to be the case either.
Ive had many HTC devices including the OG Evo, never seen anything like this...any ideas?
It's a mystery to me as well. It's happened a couple times to me. The only way I could power it on is by letting it sit on the charger for several minutes.
I think it might have to do with the way we rooted them. The developer mentioned an issue with letting the power go dead. It may not be a problem if you are in fast boot mode.
Hmmm...............
sent from my DAMN EVO!!!
Mine has a problem powering on while it is charging. I'll have to take out the battery and unplug it to get it to turn on.
im finding out that people who are using cwm have a problem charging with power off. Im using twrp so Im sure this doesnt pertain to me..but its got to be something kernel or recovery related. im gonna ask over in vipers thread and see what kind of answers I get
Happens to me often as well. When I plug mines in, its usually good to go about 2 minutes after the red light stops blinking.
Sent from my PG86100 using XDA App
Alchem!st said:
Happens to me often as well. When I plug mines in, its usually good to go about 2 minutes after the red light stops blinking.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
dude it took me 23 minutes to get my phone back on yesterday
Success100 said:
dude it took me 23 minutes to get my phone back on yesterday
Click to expand...
Click to collapse
Damn, that sucks. I'm using TWRP I also suspect it may have something to do with clockwork. Although it could just be that the battery needs to charge to a certain point for the phone to kick in. Who knows.. LOL
Sent from my PG86100 using XDA App
I just ended up trading mine in for a refund. I found the 3d offered very little over the original Evo, and mine had worse reception and call quality than the original. I am now using a nexus s until a better phone comes out.
My thread on the moto support forum:
https://supportforums.motorola.com/thread/61040
Anyone else run into this issue? Worst case if it comes down to it, think they will give me a new Photon?
Hey, I ran into this.. https ://supportforums.motorola.com/message/400251[/url]
It is sort of similar to what happened in your case. Sorry I can't be of much help.
I had the same thing happen when I flashed the 198_7 update in RSD. I pulled the battery and let it sit for a minute. Then I restarted in recovery mode (Hold Volume down +Power, press volume down until you see "Boot Android (No BP)" and then press Volume Up. You should see the message "Cold-Booting Linux" and hopefully the phone will restart. Not sure what caused the error or if this was what even fixed it but I've had no issued since. Let us know if this works, I for one would like to know if this is a real fix or mine just coincidentally worked afterwards.
EDIT: I just tried the "Cold-Boot" again and after it restarted I had no CDMA service, don't worry a quick reboot restores connections. So it seems that this option may actually bypass the modem power up which is probably why it worked. I'm still still not sure what the "no BP" stands for though, anyone?
Was using RSD to manually install 198_6 and now the phone won't turn on unless plugged into a wall charger and then it displays "modem will not power up (2)". Anyone able to help save my butt?
Click to expand...
Click to collapse
Was a no go. Couldn't get into recovery. Took it to sprint and supposedly the battery is dead as well. Biggest concern is them digging for any messing around. Was able to factory reset and lock the bootloader so they shouldn't be able to call shenanigans. My evo shift is now my clock and useful as long as there is wifi lol
Sent from my PG06100 using XDA App
I saw that thing once, but it was normally - returned the battery and went to recovery normally.
Sprint said they couldnt do anything, looks like its Asurion time :\
Started messing with the phone while waiting on asurion and i can get it to get into fastboot, etc options. It will wait a while but still goes back to the modem will not power up and battery is too low to flash :/ any suggestions on how to maybe charge the battery i know sprint is saying the battery failed but that seems unlikely
Sent from my PG06100 using XDA App
Also seems like the phone knows when it is plugged into an outlet vs my computer. When the phone is connected to my computer it turns the led white, while the outlet turns the led green then the screen turns on. If i could get the screen on while plugged into my computer i could maybe get my phone back in working order
Sent from my PG06100 using XDA App
Joker had a little trick but you had to hack up a USB cable to get it to work. You might ask him. But that seemed to charge.
I just went ahead and called asurion, photon should be here tomorrow afternoon. Still cant figure out why the phone bricked. Oh well :/
Sent from my PG06100 using XDA App
What were you doing when it happened?
Sent from my Photon via XDA
Rsd back to stock to take my phone in for rebooting and screen of death issues lol
Sent from my PG06100 using XDA App
Did you have it fully charged?
I believe it was lower than normal when i use rsd, that may have been why
Sent from my PG06100 using XDA App
That is probably true.
Sent from my Photon via XDA
Well despite my user error i am so happy to be back with a photon. This one seems to be bug free as well. The screen if death and reboots definitely must have been hardware related. This one also does not seen to heat up as bad either. This thread can be closed.
Sent from my MB855 using XDA App
Glad you are back up and rolling.
Sent from my MB855 using XDA App
Don't let your phone uncharged if you got 5% that's a warning sing you need to plug the charged the soon as possible i have so much problem with new photon because now. hopefully it save somebody time.
I have a rooted Photon that I let totally die one day by accident.
No problem - plugged in charger for awhile and it booted fine.
Jasonfnts1 said:
Don't let your phone uncharged if you got 5% that's a warning sing you need to plug the charged the soon as possible i have so much problem with new photon because now. hopefully it save somebody time.
Click to expand...
Click to collapse
Ive let that happen to me twice and no problems. Even to the point where it won't turn on till its plugged.
Sent from my MB855 using xda premium
Hummm I have let my photon completely discharge for 2 or 3 times cause I had to calibrate my battery, never had a problem for doing it.
Never has a problem here either...
Sent from my MoPho using XDA Premium.
Jasonfnts1 said:
Don't let your phone uncharged if you got 5% that's a warning sing you need to plug the charged the soon as possible i have so much problem with new photon because now. hopefully it save somebody time.
Click to expand...
Click to collapse
I can confirm this i let it die out the other day and now it doesn't charge from wall outlet i have to plug it in the computer which sucks now im probably going to call Sprint
Sent from my MB855 using xda premium
Has to be more to the story because many times mine has been drained to the point it shuts off and it's fine.
My first thought is something to do with if you've used the bootstrap recovery. That hijacks part of the boot process and wont allow the phone to be turned off and charge from a wall outlet but a USB outlet will work fine.
That's my 2 pennies ...
KSmithInNY said:
Has to be more to the story because many times mine has been drained to the point it shuts off and it's fine.
My first thought is something to do with if you've used the bootstrap recovery. That hijacks part of the boot process and wont allow the phone to be turned off and charge from a wall outlet but a USB outlet will work fine.
That's my 2 pennies ...
Click to expand...
Click to collapse
I used bootstrap a while ago maybe start of Dec but this just happened out of the blue any fix
Sent from my MB855 using xda premium
RockoDev said:
I used bootstrap a while ago maybe start of Dec but this just happened out of the blue any fix
Click to expand...
Click to collapse
Nah, hell i don't even know if that has anything to do with anything ... i was just making a suggestion to help spark discussion
I remember readying something to where you have to jump start the phone. It had something to do with connecting to neg and pos on the battery posts on the phone. Try looking around for it. I too have drained my battery serveral times till it turns off and no problems.
BHermes21 said:
I remember readying something to where you have to jump start the phone. It had something to do with connecting to neg and pos on the battery posts on the phone. Try looking around for it. I too have drained my battery serveral times till it turns off and no problems.
Click to expand...
Click to collapse
Oh do it to the phone because ive had to that with the battery to charge it a lil
Sent from my MB855 using xda premium
Jasonfnts1 said:
Don't let your phone uncharged if you got 5% that's a warning sing you need to plug the charged the soon as possible i have so much problem with new photon because now. hopefully it save somebody time.
Click to expand...
Click to collapse
i have had my mopho die quite a few times...alsmost every few days with no probs. not sure what happened with yours, but it is deff not and should not be an issue.
Yeah, I can't even count how many times I've used my phone till it turns off, and on a few occasions after having it turn off on its own I've turned it on again still without plugging in to try and kill it just a little more, for calibration ideas I had run across and was trying. Still wall charged and powered up without issue though.
Maybe you have a bad battery?
MoPhoACTV Initiative
Wierd
never happened to me, i've let it discharge completely quite a few times that has never happened?
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.