Hey guys,
Hopefully someone can provide a bit of help or point me in the right direction.
Tonight I installed (what I thought was) an update but accidentally installed the original 6.0.0 image for my 6P (MDA89D).
I noticed that not much on my phone was working, discovered my error, and went ahead and updated to the latest image (MTC19X).
Most of the phone's functions remained unable to work using this image so I also tried the last image I was on before updating.
Now after trying to uninstall xposed, reinstall xposed, disable certain modules, etc I am unable to get certain functions of the phone to work.
The things I've noticed are: my recents button doesn't function, no notifications are popping up on my notification panel, I can't expand my notification panel to show quick settings, sometimes home button doesn't function at all. If it helps "vibrate on touch" was turned on for some reason after I updated the second time.
The first update I did was using FlashFire (undid xposed, installed update, reinstalled xposed), the rest of the updates were using fastboot to update everything but data.img.
Well I ended up finding the fix finally thanks to a little more googling.
running "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" and going through the setup ended up fixing it
Might as well leave this up in case anyone else needs help in the future
Requesting urgent help here.
After updating to the AT&T nav bar update, my phone seems to be stuck on a black screen with constant "System UI has stopped" popup dialogs.
I have tried running adb commands to uninstall Substratum which I feel is the culprit, but I recently reset my computer so my phone doesn't recognize it as a trusted device so I can't run any commands. I've also tried putting the phone into safe mode but the same black screen and "system ui has stopped" errors continue to show up.
Is there anything else I can do or will I have to factory reset?
Reservations said:
Requesting urgent help here.
After updating to the AT&T nav bar update, my phone seems to be stuck on a black screen with constant "System UI has stopped" popup dialogs.
I have tried running adb commands to uninstall Substratum which I feel is the culprit, but I recently reset my computer so my phone doesn't recognize it as a trusted device so I can't run any commands. I've also tried putting the phone into safe mode but the same black screen and "system ui has stopped" errors continue to show up.
Is there anything else I can do or will I have to factory reset?
Click to expand...
Click to collapse
Did u use any navbar changing mod ?
I'm having the same issue. I also have substratum installed, along with a navbar mod
XPLiiCiiT said:
I'm having the same issue. I also have substratum installed, along with a navbar mod
Click to expand...
Click to collapse
I had the same happen after flashing to u1 and rooting but I was chalking it up to ****ing it up.
Can you take a logcat of your phone booting up and share it or at least the systemui exception you are getting? I want to see if it matches mine.
wildermjs8 said:
I had the same happen after flashing to u1 and rooting but I was chalking it up to ****ing it up.
Can you take a logcat of your phone booting up and share it or at least the systemui exception you are getting? I want to see if it matches mine.
Click to expand...
Click to collapse
Dang sorry! I already did a factory reset.
Edit: It seems to have definitely been from a navbar mod. I installed the same mod I used to make my navbar smaller before I updated my phone and upon restarting the phone, I got the same black screen with the "SystemUI has stopped" message.
Somewhat relevant if someone checks on this thread for system UI issue and have Xposed installed.
Safe mode for xposed allowed me to peek at my device for a moment
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
conmonks said:
Somewhat relevant if someone checks on this thread for system UI issue and have Xposed installed.
Safe mode for xposed allowed me to peek at my device for a moment
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
Same issue! Applied update today and now can't even use the phone! System UI has stopped errors! Safe mode won't allow for the removal of overlays. Damn. I don't want to reset the entire phone! Any solutions!
Do you use systemui tuner?
Hi,
A few days ago I experienced a boot loop on my Nexus 10 with Lineage OS 13, build 20170909.
I broke it down to a recent update of Nova Launcher - going back to an older version and preventing Google Play automatic updates fixed it for me.
There are a number of reports of the same symptom pointing to Nova Google Companion, TeslaUnread, IFTTT, and Action Launcher.
I don't think this is an issue in those apps, but rather caused in the OS - an App should not be able to bring down the OS to a reboot (and even worse, due to the automatic restart of the launcher, causing a reboot loop).
any ideas of a fix in the OS? something else to prevent this from happening again?
Regards
sthones
I confirm the same. Constant bootloop with Nova Launcher
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
stephendt0 said:
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
Click to expand...
Click to collapse
I had the same problem with a Galaxy S3 running OctOS (CM13 based Android 6.0.1). The Nova Launcher update caused my phone to crash and reboot as soon as it was unlocked.
I was able to disable Nova in recovery (TWRP) using the built-in TWRP file manager. navigate to /data/app/com.teslacoilsw.launcher/ and delete base.apk. This will keep Nova from loading on startup but will not delete your data. My phone worked fine after that, albeit without Nova.
Thanks a lot, removing base.apk stopped the reboot loop.
My device has just started a bootloop too, but I don't even have Nova installed on it (though I do on my phone), just the stock launcher in CM / LineageOS.
I reset it to factory defaults and then it boots, but when it restores my old apps it starts looping again, so one of them is the cause. I didn't learn anything from the log via adb.
Any ideas?
I discovered it was one of my apps causing this. I removed it and it boots ok. https://play.google.com/store/apps/details?id=au.com.realestate.app&hl=en
hmoffatt said:
I discovered it was one of my apps causing this. I removed it and it boots ok.
Click to expand...
Click to collapse
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Happening to me now, ffs im on the latest nightly and thats not fixed it.
TheRealSmurf said:
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Click to expand...
Click to collapse
Same here.
daseddy said:
Same here.
Click to expand...
Click to collapse
Mine just started boot looping yesterday, but I hadn't installed any new apps in a while, and I have automatic app updating turned off (I also don't have any real estate apps installed, German or otherwise). Any hints on how to track down the culprit? Is there a boot log to look at?
Thanks!
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Same here. Started happening after it updated my apps yesterday. Removed nova launcher and all other Teslacoil software, problem remains. Can only start the tablet in Safe mode.
Seeing this on my device as well, except I am not able to remove the base.apk file because the app I installed somehow corrupted my bootloader such that I cannot get into recovery mode.
The culprit app? LinkedIn. Automatic app updates were turned off, and just before the bootloop started, the last thing I did was install that app. It finished, it rebooted, and hasn't stopped rebooting since.
When I put it into bootloader mode, it stops the continual rebooting and displays the "open panel" robot and "Downloading... do not turn off target". From there, all I can do is press power to start, then it goes back into rebooting. There is no way to get into recovery mode from there.
Also, attempting to keystroke into recovery mode just restarted the lineos infinite reboot.
Can't get into recovery, can't get the bootloader out of "Downloading" mode, and lineos continually reboots... Any wise sage souls have any ideas on this one? It looks like my device is bricked
It got me too - I don't have Nova Launcher installed. A few weeks ago the device started bootlooping with a build I had installed since september. I updated to one of the latest builds and had the same issue again. At the moment i got it working most of the time, but when i start certain apps it just reboots.
Seems to be independent to build version and can occur with different apps (at least thats what I've read here...).
Is this a Lineage Os 13 only thing or can I throw the device away now?
Greetings
I started having this issue this week as well. Oddly enough, I was still on CM12.1. In the middle of watching Plex and it rebooted, and has been boot-looping since. I did a factory wipe and while installing apps, it started looping again. I then installed the latest nightly of LOS13.1 and again, once it got part-way installing apps, it started boot-looping again. So this is not just a LineageOS thing, it seems to be an app update (I do have auto-update turned on).
I´m having the same problem without ever have the Nove Launcher installed. The bootloop started on my device several weeks ago. I tried to fix it by wipe partly or total and reinstall the latest nightly of los13 (20171126) and opengapps micro 27.11.2017 (and everything else).
As soon as I reinstall my apps, los goes back to bootloop. Sometimes, when I manually install only few apps, the system seems stable, until die next updates come by the play store.
So now I went back to stock rom until I´m getting aware of the problem beeing solved.
workaround, maybe
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Removing offending apps works
Thank you!
I did the same with your advice... removed some apps and it works. I went back to September ROM, then update to Nov ASB ROM and it works fine.
ShevT is on it, here https://jira.lineageos.org/browse/BUGBASH-1052
and here: https://review.lineageos.org/#/c/197386/
Hope it gets fixed and merged soon... as this has been a pain the neck for a while, possibly related to a similar problem earlier this year.
loveandmarriage said:
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Click to expand...
Click to collapse
I'm running CM13 and I have the same problem. I am not tech savvy with installing ROMs but managed to get to TWRP and did a reset to factory. Got part way thru optimising apps and the problem came back. I could only turn the tablet off via TWRP!
I don't mind going back to stock rom but not sure how to do it..best I look on here and start to educate myself..I'm 73yo so might not get finished before my time is up
Good afternoon boyz & girlz,
I've a problem with the update of teh System App.
If I start the update, it hang on Pause until I made a reboot and, after it, update starts.
I've forgot something like option or procedure to do?
Thank you in advance.
Regardz,
4 system apps updated today
Hello xda. i was using a custom for a long time and it was working pretty fine until few days back which i got error "system ui has stopped". I didnt thought it was a big deal and i thought i could do a format and everything will work fine. Well after lot of formatting and rom installing the error didnt go away. I decided to go back to stock system hoping that everything will work 100%. No it didnt. i got same freaking error again. at that point it was a dead end for me. So i thought maybe internet knows what the heck is causing this. im worried that phones motherboard is dying. hope its not that.
dont restore all of your apps at first and look for any recent change you did to customize interface like xposed modules or apps, if you are on a custom rom grab original system ui from /system/priv-app and replace it manually and after that you may need to delete "runtime-permissions.xml" from /data/system/users/0 to reset permissions and solve system ui FC (you can do this from TWRP file manager), let me know if you need more help