Help with Phone Shutdown Issues? - Thunderbolt Q&A, Help & Troubleshooting

Hey everyone, I could use some help with a few Thunderbolt issues I have.
Here's a few points of description about the issues:
Whenever I use data on the phone (either 3G or 4G), the phone browses fine for about 3-5 minutes, then suddenly powers off. When I power it back on, the phone says it has 0% battery left, and will very quickly turn itself back off. When I plug it in to charge, the phone will turn on without issue and say it has whatever % battery it had before it turned off suddenly the first time.
If I simply use the phone for calls or non-internet things, the phone works fine. Once it's turned off once, though, it'll think it has 0% battery and not even offline things will work.
The phone seems to work OK for short-burst internet browsing, like checking email, but anything continuous (web browsing, streaming music) will shut it down within a few minutes
While plugged in, I can browse the internet, stream music, etc. just fine without the phone ever having any issues.
As a less serious and potentially unrelated problem,
The phone is not recognized by any computer. I have tried changing USB cables, computers, laptops, installing drivers, etc., but the phone only lists itself as "Charging" and never says anything about USB connections / USB debugging.
The issues first started when I tried out LiquidSmooth ICS about a month ago, with the recommended newer radio. I tried running the MR2 and MR2.5 radios on LiquidSmooth, and that didn't seem to change anything, so I went back to my old Gingerbread AOSP ROM, but the problems persisted.
Now I'm running stock with the stock radio (S-ON unrooted), and once again the problems are the same. The phone has been trying to download the ICS OTA update, but it always says "DOWNLOAD FAILED."
Anyways I'm not sure if the hardware on the phone has just broken, or if it's possible to fix through software. Anyone have any ideas? It would be much appreciated.

Sounds like you have a bad battery. Only thing I can say is you must not have properly unrooted your device or you have one of the few phones that will not do an ota update. I had this happen to my original droid when froyo came out. They try pushing the update but just wouldn't accept it. Also maybe your battery issue is causing your update issue. So just get a new battery and go from there.
Sent from my Nexus 7 using Tapatalk HD

I replaced my batt and my problems (the same as yours) went away!
Sent from my iPad using Tapatalk

Related

[Q] Radio in my Vibrant behaves strange

It started out of a blue, one day my phone started to lose signal. Nobody was able to call me and I wasn't able to call anyone (Same deal with texts). So, I rebooted device and I still wasn't been able to use it, and in addition battery level decreased suddenly from sth like 70% to 3%. After about 10 minutes I was able to use it again. I thought that problem was my old TeamWhiskey Bionix, so I flashed CM10. Issue repeated several times a day. I tried different radios - nothing helped. Fortunately, WIFI still works, so I can use SIP...
Anyone has idea what can be the problem?
And I almost forgot... One week before radio freezed - I rebooted and device was alive again, so I forgot about it until now :/
EDIT//
Now I'm no more able to charge it cause Interface crashes when i plug USB in...

[Q] Odd problem spanning multiple ROMs

This problem seems to be getting progressively worse.
Basically what will happen is that the phone will either lock up completely or shut off unexpectedly. Upon reboot, the phone will either show that the battery is now at 0% or 3% or whatever and/or it won't be able to "see" any T-Mobile towers. If I pull the battery and reboot, the battery indicator will show the true charge % for a while, up until the next lockup or shut off.
Sometimes it'll last for hours and sometimes it'll shut off shortly after I turn it on. The only real common thing is that I'm usually actively accessing the internet in some fashion, like using Facebook or Zillow. Syncing and other background access doesn't seem to affect it, since this only seems to happen when I'm actually looking at the phone.
The IMEI matches the back sticker, and this problem has followed me across a few different roms, even after ODIN flashing a stock rom, rerooting, etc.
Any ideas? Right now I'm using my old TM506 because I don't trust my vibrant and need a working, reliable phone.
I can't be certain but it could be a bad battery, I have a few and one of them started giving me problems similar to this.
Vibrant 360° Productions
PAC, PA & BAKED (hopefully soon)

[Q] Phone shutting off after recent OTA

Problem: Phone shuts off and often upon restart the battery displays low to no power when it was at full charge before shut down.
Isolating the Problem
Will only shut down if mobile network is turn on and has been in use
Will not shut down if left plugged into a power source
If issue occurs you can recover by rebooting the phone while plugged into a power source
Using a wi-fi connection will not replicate the problem
Is not an issue with third party as issue is replicated with "Safe Mode" on
Backstory:
My phone is rooted and had/has [ROM] Official Thunderbolt ICS running. At the time I did not have OTA Killer flashed so when the recent OTA came out it tried to install and in my ignorance/stupidity I accepted. It obviously didn't work and I went back to the forum and found out why.
A friend of mine has a Thunderbolt completely stock and this same issue has been happening to him. From what Verizon's TS has said this is a known issue that is hit-and-miss and they replace your phone until you find one that works (took him 3 times). That's all well and good except my phone is rooted and they'll charge me $300 for the replacement.
(Finally) The Question:
Does anybody else have the know-how to fix this problem? I can give whatever specs you would like and am fairly good at keeping a log of what I did/what happened. (necessary for IT and troubleshooting)
Replace your battery. The battery you have is bad.
Sent from my Infected Rezound using Tapatalk 2

[Q] Phone won't turn on

Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.

Phone bricked after UPDATING to CM 10.1 RC2

A few days ago I did an automatic update from 10.1 to 10.1 RC2 through the built in option available on devices running cyanogen. Later I found out that the HTC one x+ can not update the kernel, thus giving me problems with the camera (It would freeze the phone etc). I knew I had to flash the kernel manually but I left it alone as the problem didn't seem like much at the time. Now I have installed many roms to this phone, from AOKP to android revolution HD. So I am fairly experienced with this sort of thing. I should say that I have no mods etc installed, Kernel I am using was the old one before updating because I thought it would also be automatically updated threw the update.
Since the update my phone has been recharging at an incredible speed when the internet is off. Now the problem happened this morning, after unplugging the phone from the charger (The original charger but with a different usb cable) the phone ran extremely hot. It was mostly underneath the camera but then the screen and then the entire phone. I mean I felt the heat when it was in my pocket! I checked the phone and to my surprise the battery hadn't gone down much (maybe like %2).
So I thought the best thing to do is re calibrate the battery and restart the phone. But doing that, when I turned it back on it had drained to about %20! And afterwards it was draining fast super quickly. something like %3 every minute. But I thought nothing of it and decided to bring along my charger to college, thinking I could just charge it up again when I get there. This has happened once before and when it wouldn't turn on, recharging it fixed it all.
So I got to college and now I cant turn the bloody thing on! Its been plugged in for 2+hours but there is no light or anything. It wont go to recovery mode either by pressing vol down + Power button.
I am thinking the only way I can fix this thing is to take the phone apart and car jump the battery using a cut up usb charging cable. Is there any other way? if not how would I go about doing this.
Any help would be much appreciated. I am a student and I don\t have much money, and I still have the phone for another 6-8 months on contract!

Categories

Resources