Database Users

[Q] Random Rebooting and Overheating

I had bought my xperia sometime around October'10 & updated it to 2.1 when it was available & then started facing this problem. The battery gets overheated, specially when charging, & when any activity is performed on the phone then, the phone goes into a loop of rebooting, stabilizing only when the battery cools off. Not only that, when on the move, apps like maps is initiated, the phone often reboots, so much so that it sometimes happens 4/5 times in a day, 2/3 times together. Since yesterday, the phone rebooted more than 10 times, twice with a sudden jarring sound while closing down. Also sometimes there is a burning rubber smell coming from the back of the battery. I have tried everything from reinstalling the android software to sending it off to a repair centre only for them to say that it is liquid damage when I know for a fact that no liquid has EVER touched it. Please someone help me. What do I do? Would downloading a custom rom or Zzdizus new custom kernel help since it undervolts? Anyone got any working fixes

markboi13 said:
I had bought my xperia sometime around October'10 & updated it to 2.1 when it was available & then started facing this problem. The battery gets overheated, specially when charging, & when any activity is performed on the phone then, the phone goes into a loop of rebooting, stabilizing only when the battery cools off. Not only that, when on the move, apps like maps is initiated, the phone often reboots, so much so that it sometimes happens 4/5 times in a day, 2/3 times together. Since yesterday, the phone rebooted more than 10 times, twice with a sudden jarring sound while closing down. Also sometimes there is a burning rubber smell coming from the back of the battery. I have tried everything from reinstalling the android software to sending it off to a repair centre only for them to say that it is liquid damage when I know for a fact that no liquid has EVER touched it. Please someone help me. What do I do? Would downloading a custom rom or Zzdizus new custom kernel help since it undervolts? Anyone got any working fixes
Click to expand...
Click to collapse
Have you used SEUS and/or flashtool yet?
SEUS is the sony ericsson software for repairing and updating the phone to the latest software.
I recommend using the 2.1 firmware with the .54 baseband
Here is a link to flashtool for you and has a link inside of it too with a how to on how to use flashtool.
http://forum.xda-developers.com/showthread.php?t=920746
Try this before you flash any ROMS. Which you have to do more to get to that point. Let me know what you need help with and if you tried flashtool or SEUS yet to fix the problem.

im having the same issues... when i charge it it overheats... then when i use it it starts to reboot... i already made a factory reset and reinstalled the rom.. the 2.1 .54 baseband.. and still does it....

markboi13 said:
I had bought my xperia sometime around October'10 & updated it to 2.1 when it was available & then started facing this problem. The battery gets overheated, specially when charging, & when any activity is performed on the phone then, the phone goes into a loop of rebooting, stabilizing only when the battery cools off. Not only that, when on the move, apps like maps is initiated, the phone often reboots, so much so that it sometimes happens 4/5 times in a day, 2/3 times together. Since yesterday, the phone rebooted more than 10 times, twice with a sudden jarring sound while closing down. Also sometimes there is a burning rubber smell coming from the back of the battery. I have tried everything from reinstalling the android software to sending it off to a repair centre only for them to say that it is liquid damage when I know for a fact that no liquid has EVER touched it. Please someone help me. What do I do? Would downloading a custom rom or Zzdizus new custom kernel help since it undervolts? Anyone got any working fixes
Click to expand...
Click to collapse
I have heard this story too many times.
They are lying about the liquid damage.
The x10 overheats due to firmware used in the x10.
This causes it to die forcing you to buy a new handset.
You take it back again and you tell them to replace the motherboard.
Be persistent.

Soo annoying, CM7 rooted G2 just died, no rhyme or reason

My T-Mobile USA G2 has been rooted running CM7 stable with no issues for a few months now. I reboot the phone a few times per week. Everything has been great for months, then all of a sudden my battery was low and the phone started to slow down. I figured it was just setCPU lowering the CPU down to the 245mhz I had it set to. Then all of a sudden it froze, I had to pull the battery, I thought that was kind of weird, but figured what the hell, why not. A good reboot can't hurt, right?
WRONG.
I put the battery back in and at the boot animation (blue arrow circling Android on a skateboard above "Cyanogen Mod 7" banner) shows up, but the arrow starts to stutter, then the screen dims -> then goes black. So I figure the time out activated, no big deal. Then I realize I can't wake hte phone up! No matter what I did, if I plugged it into my PC, the screen would come on (lock screen) but it wouldn't register any touching of the screen, therefore I couldn't unlock the phone, and it would just time out again.
I ended up having to reboot into CWM and do a Wipe Data and re-install of CM7 from my SD card for it to work!! I tried wiping dalvik cache, battery stats, etc... everything except for wiping Data, but nothing worked. I HAD to wipe my data and re-install the OS...
Anyone know why this happened? Or what could have caused it? At this point I downloaded the newer version (7.0.3) and after wiping installed that, now I have to re-download all of my apps and re-setup all of my settings (extreme pain in the @$$ and very time consuming)...
Thanks in adv.

Do a search, I thought there was some issue with low cpu speeds and waking the phone up from sleep. Basically, the cpu is undervolted and doesn't have enough juice to turn the screen back on.
Search around.. it's on here somewhere. In the meantime, increase your min cpu speed.
maybe in here?
http://forum.xda-developers.com/showthread.php?t=1043118

Thanks, I had read about that prior to setting my phone up, and that had never caused an issue for months... I don't get why it would all of a sudden cause an issue?
Also, I couldn't even get to my desktop to change the min CPU speed... no matter how long I waited, the phone wouldn't wake/wouldn't let me unlock it...
I ended up having to wipe the phone clean and re-install a fresh install... in the new install I have the min cpu higher than it was before.

Screen keeps on turning itself on/off on stand-by

I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.

I would try a blur ROM first to make sure it isn't your phone. Then you can start thinking about hardware issues on the phone.
Sent with Tapatalk from my Blackberry Playbook

barry_ said:
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
Click to expand...
Click to collapse
Very weird, but I noticed a similar problem the last few days. While at work, my phone goes into airplane mode(no reception in the building). When I was on CM7 neutrino, I had an instance where the phone drained the battery completely.
Recently I switched to cm9 Turl v8, and at work I pulled my phone out...the screen was on, Bluetooth was on and my battery had went from ~85% to ~20% mind you, I hadn't turned Bluetooth on.
A few days later I noticed I pulled my phone out and the screen was on...showed the screen and phone had been awake for a few hours....while in my pocket.

thanks for the replies
I got lucky i guess? I decided to start deleting recent apps/themes and the first few I deleted (themes for GOsms) stopped the screen turning on ect, no idea why but hey ho at least it stopped the fault.

Do not restore any thing after a fresh install of cm7 (complete wipe and clean before installation) and ull sure face no problems, i also had these problems not any more.
barry_ said:
I have had this problem with successive rom's (all cm7 based)
recently I wiped EVERYTHING and clean installed CM7 weekly 6 and for a few days it was all good, then the problem started again?
Tried to wipe cache ect (anything but a clean install) but still the same issue (PHONE WILL BE ON STAND-BY AND THE SCREEN WILL JUST TURN ITSELF ON/OFF ON ITS OWN??)
I haven't done a reinstall over weekly 6 because I am thinking the problem will just keep on coming back'
is there anything I can do? anything I need to show that will pinpoint the problem?
thanks in advance.
Click to expand...
Click to collapse

[Q] Randomly rebooting phone even in recovery mode....

Explanation:
Tuesday afternoon I was getting out of my car and dropped my phone like I have done hundreds of times but this time my N4 with the official bumper fell face-up into a small stream of running water on the side of the street. I quickly picked it up and wiped it off and tested it and everything seemed ok but I turned it off to be safe. I came home about an hour later and put it in a container of rice and let it dry overnight with a fan blowing over it. I booted it the next morning and everything was working as it was the day before.
At this point I was stock everything, no root and never been rooted.
Fast forward 2 days laters my device has been plagued with random restarts and/or turning off. At this point I had not installed any new apps or changed any settings so I'm pretty confident it was some rogue app causing this trouble. So I had planned on doing a factory reset but 4.4 was out so I decided if I was going to set everything up again I might as well try the update. I decided to try http://forum.xda-developers.com/showthread.php?t=2507021 and everything worked fine. I cleared the cache and everything, a fresh start. I had no errors trying to install CWM or the ROM and KitKat worked on my phone just beautifully but then it started rebooting/turning off again.
So I went back to stock. Erased the whole device and flashed the radio, bootloader and 4.3 hoping/thinking it was 4.4 causing the trouble but still the same thing. I don't know what else to do so I have come to you XDA!
Weird behavior I have noticed
phone will boot when charger is plugged in
sometimes can't turn on phone without the phone charging - fastboot or normal boot
When I say turn off I mean like the battery has been pulled out of it
Reboots are completely random, sometimes vary from a few minutes to couple of hours of booting up. It happens when the phone is idle and it happens when I'm using the device in more apps that I can remember.
Scenarios & Outcomes
Full boot in 4.3 - Turns off eventually
Full boot in 4.4 - Turns off eventually
Safe mode boot in 4.3 or 4.3 - Turns off eventually
boot into fastboot - Restart the first time then it works as expected
boot into stock recovery - Restarts
boot into cwm recovery 6.0.4.3 - Restarts
Turn on phone - Reboots after google logo shows and boots normally only to turn off eventually by itself

Overclocked too high? Rice blocking cooling, maybe blow compressed through it? Good luck!
Sent from my MZ601 using XDA Premium HD app

Galaxy S5 with Lineage OS stuck in a bootloop

Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom

Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).
Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It
Oh If You Want To Know My ROM I'm Using : Resurrection Remix.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.

yerrag said:
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
Click to expand...
Click to collapse
Well, this worked for a while. Then, bootloop became more stubborn.
By then, I had already bought a phone to replace it, so I was in no hurry to fix this issue but still, I hate to see a good phone go. Still has a screen that stood the test of time, and at high res, and I love the size of the phone.
So, another Hail Mary. And it worked!
I put the phone, worked in tissue paper, then enclosed in bubble wrap, in the freezer overnight, surrounded by grains of rice in a plastic container, that had been vacuumed by a FoodSaver machine.
The following morning, removed the phone from the freezer and laid it bare, separating the battery from it, and wiped it clear of moisture, and let it sit to evaporate any more moisture from the temperature gradient.
Then started the phone, and the bootloop once again gone.
So, phone saved. But since it's no longer that reliable due to the recurring bootloop problem, it would be my phone to watch streaming movies from Amazon Prime or Netflix, but not my phone for receiving calls and text messages, or for Waze and all.
The lesson I got from this is that with this phone, the circuitry inside has become finicky. To open it up and fix it would be too bothersome, especially with the circuitry being composed of embedded modules. Probably somewhere inside there is a capacitor that has reached its reliable end of life, but still breathing and needing an occasional handholding. So, I just gotta learn to live with this quirk, and this quirk is tolerable for the use I have it for.
So, if you run across this problem, I hope I gave you a workaround for you to remain loyal to a workhorse that served you long enough.