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...
Related
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 : (
First thread here
I used cf auto root specifically for my device from the autoroot chainfire website just to delete bloatware like galaxy apps, S health. I didn't delete Touchwiz
Everything was fine and dandy for a few days until my phone starts crashing when browsing youtube, facebook etc.
recovery screen said it was due to 'dm-verity verification failed'
Browsing the forums, apparently flashing it with the stock rom should solve the issue. It didn't though
I flashed it and rooted it again and the problems persist
I'm lucky I backed up my data. It's just annoying having to restore everything once my phone boot loops.
What seems to cause it?
Because it's not clear from your thread, I've got a question:
After you flashed the ROM and rooted it again, did you remove the bloatware again, just as before?
Vygravlil said:
Because it's not clear from your thread, I've got a question:
After you flashed the ROM and rooted it again, did you remove the bloatware again, just as before?
Click to expand...
Click to collapse
Yes
I deleted Galaxy apps, penup, s health etc.
muaddibzero said:
Yes
I deleted Galaxy apps, penup, s health etc.
Click to expand...
Click to collapse
So the problem is caused by removing the bloatware. Because of the programming of the bloatware and the ROM itself (they are kinda "linked" to each other), it can brake your system, just as in your case.
How did you remove the bloatware? Did you use an app? Maybe we can find a way removing it without killing your system.
Vygravlil said:
So the problem is caused by removing the bloatware. Because of the programming of the bloatware and the ROM itself (they are kinda "linked" to each other), it can brake your system, just as in your case.
How did you remove the bloatware? Did you use an app? Maybe we can find a way removing it without killing your system.
Click to expand...
Click to collapse
I used titanium backup to delete it
Update
Bloatware doesn't matter now though
I reflashed my phone with stock rom again, this time without rooting. My phone still suffered from boot loops. What's happening here? Do I have to do a factory reset?
muaddibzero said:
I used titanium backup to delete it
Update
Bloatware doesn't matter now though
I reflashed my phone with stock rom again, this time without rooting. My phone still suffered from boot loops. What's happening here? Do I have to do a factory reset?
Click to expand...
Click to collapse
Did you flash the proper stock ROM for you device? Where did you get it from? I guess that something went wrong while flashing. A factory reset could solve it, but flashing the stock ROM should have resolved the issue already if the bootloop was caused by removing the bloatware - that's what surprises me.
Vygravlil said:
Did you flash the proper stock ROM for you device? Where did you get it from? I guess that something went wrong while flashing. A factory reset could solve it, but flashing the stock ROM should have resolved the issue already if the bootloop was caused by removing the bloatware - that's what surprises me.
Click to expand...
Click to collapse
Hi sorry for necroing and leaving a late reply
I used the Singapore starhub android 6.0.1 rom the device came with
I reflashed it and did a factory reset 3 weeks ago
Replaced battery as well
Worked fine for the time being
Then out of a sudden a boot loop occurred while I was on data
What's the cause of this?
I'm frankly tired of having to reflash the rom over and over again as well as restoring backups
I'd go for a full, clean install of stock (format /data from TWRP. Yes, a full format! Make sure you backup your media as this will erase absolutely everything.) and then flash stock with Odin.
Test it out see if it still has problems or if it's stable.
DO NOT RESTORE APPS FROM TITANIUM BACKUP
Re-download them from scratch.
I've noticed that I used to get random re-boots after restoring backed up apps from Titanium Backup.
Went ahead and started the phone over from absolute 0 and it seems my problem went away.
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).
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.
Hello, I have a strange problem, after every reboot of the phone, some apps are not working anymore, they either stuck at the loading screen or force close. For example, Genshin Impact (game) gets stuck, Faceapp force closes, other apps like a banking app and a local provider app are also affected. Clearing cache/data does't help, only reinstalling fixes this.
Open bootloader, rooted, stock rom 11.0.2.2IN11BA, stock kernel, no magisk modules, upgrade from 11.0.1.1 didn't fixed it. Model IN2023, when I got the phone it had the global rom and I installed the eu after rooting. Any ideas what the problem could be?
Perpatoura said:
Hello, I have a strange problem, after every reboot of the phone, some apps are not working anymore, they either stuck at the loading screen or force close. For example, Genshin Impact (game) gets stuck, Faceapp force closes, other apps like a banking app and a local provider app are also affected. Clearing cache/data does't help, only reinstalling fixes this.
Open bootloader, rooted, stock rom 11.0.2.2IN11BA, stock kernel, no magisk modules, upgrade from 11.0.1.1 didn't fixed it. Model IN2023, when I got the phone it had the global rom and I installed the eu after rooting. Any ideas what the problem could be?
Click to expand...
Click to collapse
Are you indeed still rooted? I get this issue if I turn on systemless and then don't reboot.
Or if I lose root if I haven't actually installed the patched image after booting the patched image.
Check to see if you're actually still rooted.
If you are then turn on systemless.
dladz said:
Are you indeed still rooted? I get this issue if I turn on systemless and then don't reboot.
Or if I lose root if I haven't actually installed the patched image after booting the patched image.
Check to see if you're actually still rooted.
If you are then turn on systemless.
Click to expand...
Click to collapse
Hello, thank you for your answer, I still have root, just checked. What do I have to do to turn on systemless? Just press on "systemless hosts" in magisk settings?