My phone does not overheat while in Android because it has the kernel modifing stuff. It's maximum is almost 50 degrees(never reached that hot).
But when in recovery and I'm restoring a backup, the CPU temperature raises drastically, and if the process takes long, it even raises up to 90 degrees and the phone shuts down(to prevent damage to the chip, like on PCs).
I was thinking to limit my 4 CPUs to only 1 when using the recovery so it might not overheat. Is there any way to do that?
I'm using Multirom TWRP recovery.
Don't use charger when you use Twrp. It will make your CPU temp raise. If your phone is still in high temperature, try to shut down for short time.
judy4302 said:
Don't use charger when you use Twrp. It will make your CPU temp raise. If your phone is still in high temperature, try to shut down for short time.
Click to expand...
Click to collapse
My problem is that for some reason, when I enter recovery, the temp raises up drastically. It's automatically at 40+ celsius which is absurd.
And when I start a backup or a restore, it goes up and up, until it reaches 90 and it restarts, without finishing the process and it won't get past the Sony logo. I turn it off, let it cool, and everything works again. I was thinking of installing the Dualrecovery as this happens only in Multirom TWRP. I can backup with the app "Online Nandroid Backup" without any problems. Temp does not go beyond 45 celsius. Only in recovery.
Also I can't seem to install the Dual recovery while being on Lollipop. The phone just simply does not boot. It stucks at the Sony logo, and it keeps my Multirom...
I'll try entering recovery without a charger, and I'll report back, but I still accept any ideas as to why this only happens inside recovery...
Related
I have a one X unlocked international version which I had rooted and set up a recovery. I then went on to try to flash over ARHD after super wiping, and did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery. Anyways, from here this is where it goes bad. After restarting it goes into a boot loop and ends up getting kicked back into bootloader. After this I try to factory reset to no avail. After trying to reflash the rom a couple times using recovery, recovery just died and won't even load anymore. In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Any suggestions on how to fix this and get it back up and running, or am I forced to send it to HTC the moment they bring in parts for it. (right now HTC says there is a wait on parts as they do not have any in stock as its a new phone and their texas facility has diddly on hand)
Any suggestions are welcome as to fixing this predicament.
phil.W said:
did a battery stat reset since I had flashed at around 30% and figured it would reset the calibration on the battery.
Click to expand...
Click to collapse
How did you wipe batterystats, from CWM? As the recoveries are new I suppose it's possible something went wrong if you did it that way, but it seems unlikely.
However, though probably not the root of your problem, there's no point in wiping batterystats.bin, as all that file holds in information on what processes have been using battery since your last unplugged your charger. This was one of those android myths (I used to do it too ) that was officially put to bed early in the year:
http://www.xda-developers.com/andro...g-battery-stats-does-not-improve-battery-life
In addition to this I can't get the battery to hold a charge as each time I plug it in it reboots and loads then says 0 battery and dies instantly. I can get to bootloader and fastboot but can't flash anything through fastboot because it says the battery is too low.
Click to expand...
Click to collapse
I'm pretty sure I've seen others with this issue, have a search around the forums. Have you tried turning the phone from the bootloader screen, and leaving it plugged in to charge for a while?
Try this:
1. Boot into bootloader
2. Select Fastboot menu
3. Select "Power off" to shut down the phone
5. Plug in charger
Leave it for a while. From what I've read, the power LED may flash at first, but should settle after a few mins to a solid red. I'd leave it till it's green and fully charged then try again.
If that works, and you can get into recovery again, try restoring your backup of the stock ROM if you have one, to check the phone boots okay. (If you didn't take a backup first, you will next time. ) Otherwise try re-flashing the ROM, or if that fails you might have to re-flash stock recovery, re-lock your bootloader and then run the relevant RUU for your device to flash the stock firmware back. You'll have to unlock and root again in that case.
Good luck, hope it works for you!
So my phone was sitting here on my desk at work, the display was on (very, very low brightness + super dimmed because of that setting in CM9) and it was downloading (via 3G) a ~300mb file for the Mass Effect game that's on sale in the play store today.
Suddenly I looked over at my phone and it was powered off... charging. The only thing I did notice was that it was VERY warm.
I tried to boot my phone up and it got all the way to the lock screen then it shut off. I let it charge for 20-30 minutes then tried again, would not get past the boot animation. I booted into recovery and wiped cache & dalvik in case something crashed... didn't help. Still won't get past the boot animation.
I'm letting it charge for an hour or so then I'll try to boot it up again. If not I'm going to go into recovery and try a complete wipe/flash.
I was running CM9 + franco (ondemand, no OC or UV)
Has anyone had anything like this happen?
Will report back in an hour or so.
Ryjabo said:
So my phone was sitting here on my desk at work, the display was on (very, very low brightness + super dimmed because of that setting in CM9) and it was downloading (via 3G) a ~300mb file for the Mass Effect game that's on sale in the play store today.
Suddenly I looked over at my phone and it was powered off... charging. The only thing I did notice was that it was VERY warm.
I tried to boot my phone up and it got all the way to the lock screen then it shut off. I let it charge for 20-30 minutes then tried again, would not get past the boot animation. I booted into recovery and wiped cache & dalvik in case something crashed... didn't help. Still won't get past the boot animation.
I'm letting it charge for an hour or so then I'll try to boot it up again. If not I'm going to go into recovery and try a complete wipe/flash.
I was running CM9 + franco (ondemand, no OC or UV)
Has anyone had anything like this happen?
Will report back in an hour or so.
Click to expand...
Click to collapse
try reflashing the rom.
the CPU does have a set limit for how hot it can get. My guess is downloading that amount over 3G on the charger (my god what were you thinking) made it shut down. Although once cooled down it should have booted right back up.
Sent From My Sprint Galaxy Nexus
ÜBER™ said:
My guess is downloading that amount over 3G on the charger (my god what were you thinking) made it shut down. Although once cooled down it should have booted right back up.
Click to expand...
Click to collapse
I download lots on 3G. Regularly. 10gb over the last two weeks, in fact. This has never happened to me.
Ryjabo said:
I download lots on 3G. Regularly. 10gb over the last two weeks, in fact. This has never happened to me.
Click to expand...
Click to collapse
same here, i download lots all the time. my guess is that your phone crashed, and since fsync is off by default in franco kernel, your rom or a partition corrupted. if reflashing your rom doesnt help, youll have to flash the factory system image
simms22 said:
same here, i download lots all the time. my guess is that your phone crashed, and since fsync is off by default in franco kernel, your rom or a partition corrupted. if reflashing your rom doesnt help, youll have to flash the factory system image
Click to expand...
Click to collapse
I just booted into recovery and flashed a completely different ROM (AOKP). Now it's not going past the "Google" logo (with the lock at the bottom).
I'll wipe and reflash CM9 to see if that helps.
I just noticed something I've never noticed before... after flashing the ROM it says this:
Finding update package...
Opening update package...
Installing update...
Fixing fs_size in crypto footer...
Install from sdcard complete.
Click to expand...
Click to collapse
What in the world does that mean?
I reflashed CM9 again and now it is booted up.
The battery showed at 5% ...maybe I was a little impatient >.<
I figured 20-30 minutes+ on USB charging would be fine... maybe I was wrong.
Ryjabo said:
I reflashed CM9 again and now it is booted up.
The battery showed at 5% ...maybe I was a little impatient >.<
I figured 20-30 minutes+ on USB charging would be fine... maybe I was wrong.
Click to expand...
Click to collapse
sweet
Happens to me once when my kid are playing where's my water. Phone get to bootloop and first i try to wipe caches but no luck, reflash rom without data wipe -> no luck, luckily i have 1 day old nandroid backup i restored it and it started to work.
I quess your phone warms so hot that it needs to reboot and there is some data write at same time so it got some data loss.
jnr21 said:
I quess your phone warms so hot that it needs to reboot and there is some data write at same time so it got some data loss.
Click to expand...
Click to collapse
That's a likely explanation, but this has never happened to me before so I was panicking.
Good times.
Ryjabo said:
That's a likely explanation, but this has never happened to me before so I was panicking.
Good times.
Click to expand...
Click to collapse
My phone has booted itself many times also, but only once it got data loss.
I think that disabling fsync in kernel increases risk of data loss...
So CM9 is running just fine. This time I didn't flash Franco, probably won't, don't necessarily need to. And holy dogballs... Titanium Backup is truly, truly amazing. I wish I could give the creator a hug.
Anyway, I have noticed that the bars (signal/3G/wifi) have yet to turn "blue" like they normally are. What does this mean?
Hi all, so I was trying to test some under volting and my phone randomly shut off. When i turn it back on, the phone goes into a boot loop. Besides the boot loop I can still access recovery and Odin. What is the safest way to revert back to original settings? Thanks!
Looks like I fixed it. Please close this thread.
What did you do to fix it?
Also, remember, when playing with CPU parameters it is important to not have anything set at boot until you have tested it for a good while in order to make sure it is stable.
With under volting .... breast way to find good values is to keep dropping it down.... in 25mv intervals, until you have issues (such as reboots) then add 50mv to that setting.
I'm having a weird problem. Yesterday I was using my phone as I normally do-- texting, playing simple puzzle games, etc.-- when I noticed the battery was at about 2%. I wasn't very concerned so I tried to send one last text before it died. Shortly afterward it died with the usual "Powering Down" alert. I thought absolutely nothing of it and once I had access to a charger, I did what I normally do: I turn on my phone, wait for it to get past the LG splash screen, and I plug it in once it gets to the boot animation. I do this so my phone will turn on instead of going into charge only mode. Also, like usual, my phone's screen dimmed seconds after the boot animation began (I assume from my automatic light sensor settings), and I could feel it vibrating a little (also something it typically does upon boot).
However this is as far as it got. I was very confused when about an hour later, the phone still hadn't completed boot. I removed the battery, inserted it again, and tried once more telling myself that I would wait as long as I could instead of just an hour. Booting the second time gave me identical results-- everything is normal (light sensor response and vibration indicating the phone is powering on) yet it gets stuck. The only difference is that this time I got to see the entire bootloop.
After the boot animation screen has run for a while, I get the usual "Android is starting.... Optimizing app ## of ##" (#= actual numbers). Once it finishes, instead of booting my phone, it begins the boot animation again. If left alone it will cycle between the boot animation and the "Android is Starting" screen indefinitely.
TL;DR:
1. ) Caught in bootloop between boot animation screen and "Android is Starting... Optimizing app ## of ##" screen.
2. ) The screen still dims and there are little vibrations that usually tell me the phone is about to turn on.
I have tried:
- a hard reset- this yields only a slightly stronger vibration and it starts the bootloop again.
- Download mode- this does the same as the hard reset
- Removing battery for a while- no results
- Full charge to completely dead to full charge again on charge only mode- no results
I am running CM13 Nightlies from late February (not completely sure which exact date). Which I flashed without issue about a month ago. I do have Xposed and run various modules, but I was using nothing at the time and hadn't for about a month. My computer recognizes my phone as an LG G3 Device, but refuses to access any files.
Any help would be greatly appreciated!!
Phone not starting.
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
jit1108 said:
First remove phone battery, insert it again, do not start phone. Connect your phone to original charger and charge it, while charging with the charger start your phone. Your phone should start if yes/no report me immediately. Your phone battery is failing to start your phone (Due to Low Voltage in battery). Replace with original battery.
Click to expand...
Click to collapse
Alright, I removed the battery, reinserted it (without turning the phone on) plugged it into the wall charger (seeing the charge only battery animation), and attempted to turn it on. Whenever I try to turn my phone on after plugging it in, I get the LG splash screen followed by the battery charging animation. It never reaches the boot animation. I'll let it charge for a while and try again.
Thank you for the advice!
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
musiceas66 said:
Okay, I let the phone charge completely and attempted to turn it on whilst plugged into the wall charger again. Unfortunately I had the same issue. The phone shows the LG splash screen and then the battery charging animation again-- no boot animation.
Click to expand...
Click to collapse
just start with a full reflash , if it doesnt boot up its simply broken
Jhinta said:
just start with a full reflash , if it doesnt boot up its simply broken
Click to expand...
Click to collapse
Yeah, I'm trying to avoid a full reflash/data wipe. Since I haven't messed around with any Xposed modules or root apps, I also haven't backed up anything for quite a while. No abnormal apps were running before the battery died, which leads me to believe this can be solved somehow without a full wipe.
Also, I tried to use my boyfriend's battery to boot up my phone. I thought it might be a bad battery-- as some people on-line have mentioned. Unfortunately, it still refused to boot and it produced the same bootloop.
You see , if and not and this and that dont help . te only way to save files is to get acces by recovery or boot, you cant boot but possible you have recovery so start saving your files you need. when you have or dont have your files . you stil need your system to boot for that to happen, it needs to work. so flashing a default rom with wipe sould work if it doesnt you flash original if that doesnt work its dead
Verstuurd vanaf mijn LG-D855 met Tapatalk
I think I forgot to mention, I cannot access recovery mode. I have the latest TWRP installed, but attempting to boot into recovery gives me the same results-- endless bootanimation/ "Android is Starting" bootloop.
So no acces at all . so what do you do ? Read above! Anyway good luck
Verstuurd vanaf mijn LG-D855 met Tapatalk
Solved
I fixed my problem. It turns out I was being an idiot and got the method of entering recovery mode on the LG G3 confused with my Samsung tablet. I should be able to fix the bootloop on my own now. Thanks everyone for your help! Cheers to idiocy.
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
simon710 said:
Hey, I have the exact same issue right now. Did you solve your problem, and how? I tried removing the battery and charging with original charger to 100%. I connected it to my PC, went into Download mode and clicked "Restore Upgrade Errors" in LG PC Suite. It successfully flashed the firmware update, then it said "Android is starting.... Optimizing app ## of ##". But after that it restarted into bootlop again. Also I noticed that sometimes it vibrates, and my LED (light sensor) doesn't light up anymore.
Any advice? I haven't tried replacing the battery yet.
Click to expand...
Click to collapse
Hi i have the same problem with my lg g3 d855, after a reflash hi is start and do android optimazig after the tel is start and do this over and over. help please
Hi, the solution that worked for me was to
1. install drivers
2.install LGUP
3.flash "LGD855P_D855P10a_04" - found here https://drive.google.com/file/d/18tlmVNK_ba0jIapJy-Sz5wamxbIXh8xH/view
Wanted to seek some clarity on whether my phone is HW bricked. Here're the conditions:
Rooted/Unlocked Bootloader/Custom ROM/Stock Kernel
Randomly found the phone not responding last night, no software updates or heavy usage that day.
Have to long press power to get to turn on. Typical bootloader unlocked warning message then Google screen, then phone turns off. No screen content when charging (battery indicator or booting).
I can get to fastboot with power/vol down and interact with from Nexus Toolkit but attempting to boot to anything including TWRP just produces the same sequence: boot warning, google logo then complete shutdown. Tried booting recovery, wiping, etc from toolkit, nothing.
Occasionally it'll loop once or twice but most of the time it just shuts right off.
Phone is in the freezer now, will try heating solder later. Am I looking at a new phone here? Anything else I can try before heading to the store?
Same issue
Did the freezer trick work?
I have the same issue.
Nexus 5X
Rooted/Unlocked/TWRP/Stock ROM
Randomly turned off, Long press to get back on. Turns off during boot. Managed to access Recovery the first time but havent been able to since, just shuts off.
Google chat thinks it hardware issue.. still under warranty, but would be nice to back up the userdata from it some how...
Surprisingly enough the freezer trick allowed the device to boot into recovery.. unfortunately it wasn't long enough to recover any data and now the phone won't turn on at all :/