I'm not exactly sure what happened, but when I first rooted, installed safestrap, and then Jelly Beans 106 on my Note 3, my phone would start up fine but then restart constantly. I would get my home screen, then immediately get notifications that various apps had crashed, and then the phone would reboot, but not fully though, it wouldn't go directly to the Jelly Beans boot animation, not through the full boot from the beginning with the samsung logo. From start up to reboot varies, but usually whatever app i was using would crash within a minute, and my phone would crash/lockup/reboot maybe 30 seconds to a minute later. It did not matter what app i as using or what I was doing. Actually I just noticed it somehow lost all my email settings, none of the accounts are there anymore.
If I booted into the stock rom from safe strap it seemed stable, but never with Jelly Bean. I had tried clearing the caches, wiping the phone, and a bunch of other fixes and nothing worked. In a last ditch effort I tried the process again, from the very beginning, I retooted my phone, reinstalled everything, and it worked, until three days ago when it started rebooting again. I had about three months of my phone being perfect, and then it just started rebooting randomly on it's own. The only thing that I can think that I did was decline some usage rights for the my magazine samsung app, that was the last thing I did before my phone went crazy.
I can't even get the stock rom to be stable anymore, it will do the same thing, whats' going on? I don't get why my phone was so stable, and then it went all haywire again. anybody have any idea of what I can do?
Related
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
Hello lads! The last few days I have been trying to fix a huge problem with my Galaxy S4 i9505. I had been using the Google 4.4 rom for almost a month without any problem. One day, when my phone was low on battery it shutted down and I plugged it in my charger to power it on again. When it turned on I was prompted to the screen you see when you use the 4.4 rom for the first time. I had all my apps but everything was resetted. Every setting, all the app data, messages, etc. I thought this was a one time thing so I used about an hour to get everything back to normal again. Then the next day, same happened again. Phone turned off because of low battery, and everything was reset. I tried to google it but with no luck, so I did a factory reset and flashed the newest Google rom (4.4.2) with a new kernel called Ktoonsez. Got everything back to normal again and used my phone for a couple of hours before it just suddenly shutted down once again, but this time with almost full battery. When i tried to turn it on I was stuck on the Google loading animation and had to reflash 4.4.2. It turned back on and this time I decided to let the phone stay stock to see if any of my problems was caused of my apps or settings. It lasted for 2-3 days before the same thing happened again... I tried to flash different modems, other roms and firmwares but nothing have helped so far. I am also prompted with a message each time I turn the phone on which tells me that com.android.phone has stopped working. I have tried several factory resets, wiped dalvik, wiped cache, but still has the same problem... I have now given up trying and wonder if anyone of you know what I can do to fix the problem? Any tip is much appreciated and I hope to hear from you! Thanks!
Fredrik
Completely stock, not rooted or bootloaded.
After my KK OTA came in I wanted to try ART for a while. Enabled it and then went through the reboot. On the Android is Upgrading screen it would get to a certain app being optimized and then freeze. I'd reboot and it would cut down the number of apps that are getting optimized until it got to just 1 of 1.
Now it just stops there and freezes after 15 seconds or so of being optimized. It won't go past that, I've spent the entire day today giving it time to sit and then try again or just let it fester frozen for anywhere from a few minutes to a few hours.
Question is, what do I do in order to reset my device in a way to past it.
Well, I have no idea how it fixed itself, I went to do a hard reset, couldn't get it go into the documented recovery mode, and then it worked.
Frustration.
64GB OnePlus Two running OxygenOS.
Backstory of the last time this happened:
A while back, I was on Snapchat when all the sudden my phone just froze. Didn't think it was anything special since it does that not too infrequently, but then the screen went black. Again, wasn't too concerned because it has done that before as well.
It began to reboot as normal, but right when it got to the final stage of the boot animation it froze and rebooted. This time it stopped toward the beginning the the animation and rebooted. On the third boot attempt, it showed the "optimizing apps" message like the Dalvik cache had been wiped. Again, up to this point it was nothing new (I had crazy problems with the latest OxygenOS before I rolled back to 2.2.0) so I wasn't horribly concerned.
But at about 120/160 optimized, it froze on that screen and crashed. And that's where I am right now. No matter how long I hold down any combination of buttons, the screen will not come on and it fails to otherwise respond, with two exceptions.
I tried the hard brick recovery method, but no amount of holding volume up would get it to show up in device manager.
When I went to bed last night I decided to give it one last shot. Held down the power button for a sec, and it vibrated and then powered on. Went through the whole "optimizing apps" routine and started up just fine. It was reallllly sluggish and laggy for a few minutes but now seems to work fine. Only thing I can guess is leaving it plugged in for a few hours had some effect. Oddly enough, it was at 98% to start and was plugged in doing nothing (that I could tell) for a few hours, but only showed 86% when it booted.
Well, it happened again. When it happened the last time, I rolled back from OxygenOS 2.2.1 to 2.2.0 since that seemed to be the only change I had made recently. I'd left it stock till now, but I decided I wanted root and Xposed so I flashed TWRP 3.0.2, SuperSU 3.65, and Xposed. When it rebooted after this, it froze during boot and shut off. Now it won't do anything. Holding volume up won't make it show up in device manager on my computer for the hard brick recovery, and leaving it plugged in for ~20 hours didn't help either.
Please help! I'm an extremely busy engineering student and finals are just about a week away followed by flying home. I really need to fix this ASAP.
Okay, I remembered that my phone sometimes reboots when it's dropped/set down sharply, so I rapped it a few good ones on the desk. And it booted. I'm thinking there's a loose connection inside? Should I RMA it?
Guess I spoke too soon. Froze and crashed again while booting.
I've used 2 different ROMS, AOSP extended and Pure Nexus. I've tried using custom kernels and with the default one that comes with the ROM. I've tried going into safe mode. But my phone still randomly reboots. I found that it restarts much more often when I open the Google Maps App, and sometimes camera app too.
Unlike other people, the phone can stay on for a long time if I don't touch it and just keep it in my pocket; it doesn't reboot.
Is it a software or hardware problem? Is it because I am trying to use Android 7 on it?
My phone rebooted during two consecutive nights, a few days ago. It happened between 6 and 7 in the morning, while the phone was lying on my desk, in flight mode. I always put my phone (and previous phones) in flight mode when I go to sleep. Battery usage showed how long ago the reboot took place. The first time my battery was drained from 50% to 20%, second time it didn't (stayed around 80%). I made a TWRP backup, and planned to restore a backup from a few weeks back. Due to lack of time I didn't do that. The reboots didn't happen after that.
The first reboot was after I installed GlassWIre in the afternoon. I uninstalled it after the first reboot. So far I have no idea what caused the reboots.
My phone is on stock 6.1 with january 2017 security patches, and is rooted.
This is a weird one.
No problems until I switched my SIM out (went to a different carrier) and since then any app that tried to access the GPS causes a reboot.
Read that I should change my APN type to "default,mms" so I did so and rebooted, have not had any issue since.