Hello,
I was wondering how to go about troubleshooting random restarts. Is there a way to enable logging to track down what is causing the restarts? I have tried multiple custom roms but they seem to linger on.
In the meantime I'm going to revert back to full stock and no root to see if the reboots return.
Related
All right, so here's my scenario:
I've been running CM10 builds for a while now, and for the last week or so I've been getting more and more freezes, random reboots, and full shut-downs. I finally today was sick of it and decided to give up and go back to stock. I ran into no end of problems getting into recovery mode and couldn't do so consistently or reliably, but managed with the Nexus toolkit to go back to stock rooted. But I started having crashes and reboots even during setup after this. So then I reflashed to stock without rooting and had similar issues, plus some apps wouldn't install with various unspecific errors. I finally took it all back to stock with LOCKED bootloader and I'm still having random crashes, reboots, boot loops, and apps that refuse to install.
Is there anything else I should be trying before I go to ASUS and turn it in under warranty?
TurboFool said:
All right, so here's my scenario:
I've been running CM10 builds for a while now, and for the last week or so I've been getting more and more freezes, random reboots, and full shut-downs. I finally today was sick of it and decided to give up and go back to stock. I ran into no end of problems getting into recovery mode and couldn't do so consistently or reliably, but managed with the Nexus toolkit to go back to stock rooted. But I started having crashes and reboots even during setup after this. So then I reflashed to stock without rooting and had similar issues, plus some apps wouldn't install with various unspecific errors. I finally took it all back to stock with LOCKED bootloader and I'm still having random crashes, reboots, boot loops, and apps that refuse to install.
Is there anything else I should be trying before I go to ASUS and turn it in under warranty?
Click to expand...
Click to collapse
Yes, you should try to return back to stock unrooted.
If the problem persists, then you know it is not a software glitch.
To do so watch: youtube.com/watch?v=-E-EF0QC0Gc
anoperson said:
Yes, you should try to return back to stock unrooted.
If the problem persists, then you know it is not a software glitch.
To do so watch: youtube.com/watch?v=-E-EF0QC0Gc
Click to expand...
Click to collapse
Yes, as I mentioned I already took it back to stock unrooted and then even went so far as to relock the bootloader. I was just trying to confirm that there was nothing further for me to try before assuming that meant I had fully ruled out all software influences or possible self-remedies. So yeah, if that's that, then I guess it's time to contact ASUS.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks
I've been getting reboots semi randomly for the last week or two and I was wondering if I could get some help on trying to figure out why.
Going back two weeks ago I was having some pretty poor battery life compared to some other users so I tried to do a full purge and restart. I went through the file manager on twrp and deleted any folder for any app that I wasn't using in a possibly misguided attempt to curb any file conflicts. After I did this I did a fresh install of cataclysm and Franco. After running into some reboots I tried with Kylo kernel and had the same issue. I then tried full wipe with Ubermallow and Kylo and had the same issue. Then I did a full lock, unlock, flash stock, root and recovery, and fresh install of chroma and Franco aaaaaand it still reboots.
I've had reboots randomly while listening to music but only 3-5 of them and in every install I've done I've had the same two apps do it. Starbucks app will reboot when using auto fill to log in, either through swiftkey or last pass, and Lyft will reboot the phone seemingly randomly.
What I want to know is whether or not this could be a hardware issue and if not how to get this to stop or if anyone else has had the same issue. It's seems so random yet specific and it's happened on so many different installs that I have no idea. I have been rooting my phones since the OG Droid so I have a pretty good idea of what I'm doing but I have never had an issue like this that lasts through so many installs of so many different things.
Info
Gil Smash said:
I've been getting reboots semi randomly for the last week or two and I was wondering if I could get some help on trying to figure out why.
Going back two weeks ago I was having some pretty poor battery life compared to some other users so I tried to do a full purge and restart. I went through the file manager on twrp and deleted any folder for any app that I wasn't using in a possibly misguided attempt to curb any file conflicts. After I did this I did a fresh install of cataclysm and Franco. After running into some reboots I tried with Kylo kernel and had the same issue. I then tried full wipe with Ubermallow and Kylo and had the same issue. Then I did a full lock, unlock, flash stock, root and recovery, and fresh install of chroma and Franco aaaaaand it still reboots.
I've had reboots randomly while listening to music but only 3-5 of them and in every install I've done I've had the same two apps do it. Starbucks app will reboot when using auto fill to log in, either through swiftkey or last pass, and Lyft will reboot the phone seemingly randomly.
What I want to know is whether or not this could be a hardware issue and if not how to get this to stop or if anyone else has had the same issue. It's seems so random yet specific and it's happened on so many different installs that I have no idea. I have been rooting my phones since the OG Droid so I have a pretty good idea of what I'm doing but I have never had an issue like this that lasts through so many installs of so many different things.
Click to expand...
Click to collapse
What about complete stock ROM (official firmware + kernel)? OR CyanogenMOD?
If your phone fine with stock or CM so it s the ROM/Kernel bug u installed and need to report to its developer
:good:
Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .
*bump*
I have the same problem. Help would be highly appreciated. : )
*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?
Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...
I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1
[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.
The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!
Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart
Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!
Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.