Database Users

How to troubleshoot logs of a bootloop failure

I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?

Lost app settings on Rebooting?

Hi,
I've just rooted my s7 edge international variant SM-935FD with TWRP custom recovery, wiped internal data etc
However I notice no matter what ROM's I'm flashing (tried Renovate r13, TEKXnesis v4.5, Superman 1.4.1), once I've configured all my apps...and used it for some time, then perform a reboot, some of my apps are restored to initial state ie. lost settings. Not sure what is causing this but it's really frustrating
I've disabled some apps in the process but the apps are mainly S Health, Gear VR, Internet Browser etc, didnt mess much with other system files, and never installed Xposed or the likes.
Anyone experience this strange behavior? It seems like everytime it clear app caches on reboots.
Thanks

Ok I think I figured it out....it was a zip that I flashed causing all this mess : (

Thinking it's time to upgrade to Nougat but...

So, with the realization that Xposed, etc. are likely dying a slow death I'm coming to the realization more and more that it's time to just get used to using a phone without that stuff and go ahead an upgrade to Nougat. I've been holding off because of the lack of xposed.
My question is...is there anything out there (on the Play Store or downloadable APKs) that will do the same things as these modules and is a legit app and not some junk?
1) Greenify (I know this will work without xposed but some features won't work - is there anything better?)
2) XInsta (download Instagram photos and videos)
3) SnapPrefs (I primarily only use this for typing more text in Snapchat and sharing 20 second videos which are longer than stock, I don't need the other features)
Anyone know of anything that I can download to replace those?
Also, as far as rooting 7.1.1 it's just a matter of applying the latest SuperSU I already am using (I updated my N6P regularly) after flashing the 7.1.1 stock images?
Any pointers will be appreciated.

IlyaKol said:
So, with the realization that Xposed, etc. are likely dying a slow death I'm coming to the realization more and more that it's time to just get used to using a phone without that stuff and go ahead an upgrade to Nougat. I've been holding off because of the lack of xposed.
My question is...is there anything out there (on the Play Store or downloadable APKs) that will do the same things as these modules and is a legit app and not some junk?
1) Greenify (I know this will work without xposed but some features won't work - is there anything better?)
2) XInsta (download Instagram photos and videos)
3) SnapPrefs (I primarily only use this for typing more text in Snapchat and sharing 20 second videos which are longer than stock, I don't need the other features)
Anyone know of anything that I can download to replace those?
Also, as far as rooting 7.1.1 it's just a matter of applying the latest SuperSU I already am using (I updated my N6P regularly) after flashing the 7.1.1 stock images?
Any pointers will be appreciated.
Click to expand...
Click to collapse
Hi... I can't answer all your questions, only 2...
About greenify. I used to have it on my N6 running marshmallow. When I upgraded to the N6P, I thought I'd try without, just to see how battery performs. With stock 7.1.1 or PureNexus, the battery drain is negligible. Also, you can install a custom kernels and use custom profiles which tends to help with battery consumption (this is more for screen on usage though).
If you still want to save more juice... There's Franco's naptimes app that forces doze as soon as the screen goes off. I don't use it, so you may try to find more infos by yourself.
I don't use Xinsta, nor SnapPrefs, so i'll pass on this.
For root, flash your stock firmware, flash TWRP with fastboot, reboot to TWRP, then flash SU of your choice. Latest SuperSU is SuperSU 2.79 SR3. Don't reboot to system before the SU install or TWRP will be overwritten by stock recovery and you'll have to reflash it, etc... Starting with 7.x firmware it has to be done this way...
Good luck...

5.1 said:
Hi... I can't answer all your questions, only 2...
About greenify. I used to have it on my N6 running marshmallow. When I upgraded to the N6P, I thought I'd try without, just to see how battery performs. With stock 7.1.1 or PureNexus, the battery drain is negligible. Also, you can install a custom kernels and use custom profiles which tends to help with battery consumption (this is more for screen on usage though).
If you still want to save more juice... There's Franco's naptimes app that forces doze as soon as the screen goes off. I don't use it, so you may try to find more infos by yourself.
I don't use Xinsta, nor SnapPrefs, so i'll pass on this.
For root, flash your stock firmware, flash TWRP with fastboot, reboot to TWRP, then flash SU of your choice. Latest SuperSU is SuperSU 2.79 SR3. Don't reboot to system before the SU install or TWRP will be overwritten by stock recovery and you'll have to reflash it, etc... Starting with 7.x firmware it has to be done this way...
Good luck...
Click to expand...
Click to collapse
Thanks!
Yeah, I used Elemental right now on my N6P with 6.0.1. So I'm already tweaking that, and I did read about Naptimes just like 5 minutes ago as I was doing further research. Can also run Greenify in basic mode to get some of those benefits back as it doesn't require Xposed for all features.
Really curious about the other two, if anyone knows of any other apps.
Thanks again!

IlyaKol said:
Thanks!
Yeah, I used Elemental right now on my N6P with 6.0.1. So I'm already tweaking that, and I did read about Naptimes just like 5 minutes ago as I was doing further research. Can also run Greenify in basic mode to get some of those benefits back as it doesn't require Xposed for all features.
Really curious about the other two, if anyone knows of any other apps.
Thanks again!
Click to expand...
Click to collapse
Hey... I don't see any issue as far as I remember that could prevent from using greenify. I don't know how much apps you have installed that could stay running in the background. Doze has been pretty well improved on 7.x compared to marshmallow. Give it a try, you can still install it afterward.
Good luck...

OGinstagram+ can download pictures and videos, it's here on XDA. It's not updated regularly (doesn't get bumped up for each little play store update to Instagram) but it works just fine. No idea about anything for Snapchat or greenify.

On newer versions of Snapchat you can type unlimited captions without Snapprefs. Videos are still stuck at 10 seconds, though.

Face_Plant said:
On newer versions of Snapchat you can type unlimited captions without Snapprefs. Videos are still stuck at 10 seconds, though.
Click to expand...
Click to collapse
Ahh! Didn't know that! I can probably deal with the video limit. Good to know, thank you!

RoyJ said:
OGinstagram+ can download pictures and videos, it's here on XDA. It's not updated regularly (doesn't get bumped up for each little play store update to Instagram) but it works just fine. No idea about anything for Snapchat or greenify.
Click to expand...
Click to collapse
Thanks for that suggestion. :good:

Well, I think I have enough to ditch XPosed and go to Nougat...gonna back the phone up first and get to work flashing.

Settings App Manager Crashing Regardless of Root?

TLDR: App Manager crashes Settings on selection in all scenarios tried, both rooted and unrooted. Solutions or explanations?
So it's basically as described there. App Manager is crashing on a new Moto G4 XT1625 no matter what I do. I am at a loss. It crashes while rooted with Magisk, crashes when Magisk is uninstalled, crashes when I do a fresh flash of the Motorola stock ROM. I've even rooted and gone into Titanium Backup and ensured nothing is frozen, and it crashes.
I can long press apps on the drawer to reach individual app settings, but I cannot get into the App Manager itself. I've tried clearing the cache via this entry into the settings app info, and I've cleared the cache via TWRP. Neither has seemed to affect the crash either.
The only common denominator I can think of between all attempts is that the bootloader is obviously unlocked, but I can't connect that to the crash in my head.
At a loss here - any ideas? What am I missing, or what else might I try? Thanks for any education.

got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.

libralibra said:
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
Click to expand...
Click to collapse
Indeed I have, which makes it all the more confusing as to what could remain unchanged and still affect it. Although, it is something that you encountered it under the same general environment (twrp, marshmellow, rooted). I disabled a few apps when I first rooted, and assumed that was the cause as you saw, but no idea why the flashing did not fix it...

Unable to load webpages

As stated in the title, I can't load any web pages in Chrome, Firefox, and several other browsers. My wifi is fully functional, but I can't load anything related to web pages. So using the XDA App, I can browse the fourms fine, but if I were to open a link to Google or anything, it will crash and return to the XDA App. This occurs when I try opening links from apps like Facebook as well.
At first, I thought this was a ROM problem or something to do with my apps, so I format and decrypted my phone and clean flashed OOS 5.0.4. It seems to work well for some time, but returned a good hour later. Restarting each time it happens seems to fix it for a short while, but I am quite annoyed of constantly restarting because of this.
I've searched around and it doesn't seem like anyone else has this particular problem with their OP5s so I'd like to fix this up if I can.
I am still on OOS 5.0.4, but now with NewKernel 1.29 from the OP5T thread. I'm also rooted with Magisk beta v16.2 and have the Pixel 2 Oreo WiFi v4, OnePlus Camera M, NotoColorEmoji Patch Modules along with a systemless font module installed.

@StarzSkyz have you tried another network like mobile or other wifi?

strongst said:
@StarzSkyz have you tried another network like mobile or other wifi?
Click to expand...
Click to collapse
Yeah, each time it happens I try swapping from WiFi to data, but no difference. I'm currently trying to see if it was due to restoring a certain backup from Titanium Backup. I did recently find a post speaking of the problem, but for the use of debloater somehow affecting it. So it may also be due to the loss a system app.

StarzSkyz said:
Yeah, each time it happens I try swapping from WiFi to data, but no difference. I'm currently trying to see if it was due to restoring a certain backup from Titanium Backup. I did recently find a post speaking of the problem, but for the use of debloater somehow affecting it. So it may also be due to the loss a system app.
Click to expand...
Click to collapse
You said you did already a clean installtion. So clean install again without any restore of settings and 3rd party apps not provided by the rom :good:

strongst said:
You said you did already a clean installtion. So clean install again without any restore of settings and 3rd party apps not provided by the rom :good:
Click to expand...
Click to collapse
I feel like an idiot for not remembering about doing that.
I've clean flashed and left all the apps enabled and the problem hasn't appeared again. After taking a TWRP backup of that (just in case I mess up something again) I rooted without any modules other than the WiFi Mod(which I did feel like it being one of the causes, but it helped with connection speed) and the systemless font module and tried restoring only user app data(so a fresh install from the play store and then a app data restore, not touching system apps at all) and thankfully it didn't cause any problems, so I got to restore some data back.
Thank you for the advice of actually just clean flashing again, cause I was actually slowly uninstalling and restoring my apps. I apologise for not posting as soon as I found the fully clean installation working, as I really couldn't help myself and try see if it was due to having root and my user apps. Once again, thank you for your help with my problem here. If it appears again, I'll probably post here again if it happens again (hopefully it doesn't).