Database Users

"Unfortunately, System UI has stopped" won't stop popping up. So frustrating.

"Unfortunately, System UI has stopped" won't stop popping up. So frustrating.
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new

Factory reset?

309041291a said:
Factory reset?
Click to expand...
Click to collapse
I guess that's my last resort. Damn
Edit: How would I even factory reset it? I literally can't use the phone. It's bricked. And in the recovery mode menu there is no option to factory reset. (tried pressing power and volume up)

If your phone is still locked, save the data (if needed) via adb and unlock it. But there could be easier way.
Sent from my Nexus 4 using xda premium

go to gmail account settings and sync everything. Google play will have your apps backup but not app data. Save all music, pics and files that you dont want to lose to your computer. Then just go to backup and reset in your settings menu and select Factory Data reset.
if that doesnt solve your problem you might have to use fastboot to reinstall the Jellybean.

neotekz said:
go to gmail account settings and sync everything. Google play will have your apps backup but not app data. Save all music, pics and files that you dont want to lose to your computer. Then just go to backup and reset in your settings menu and select Factory Data reset.
if that doesnt solve your problem you might have to use fastboot to reinstall the Jellybean.
Click to expand...
Click to collapse
I've had something similar to this on my G2x at one point; Android keeps popping up with errors and you can't do a single thing but reboot...which ends up erroring the same way when you're back in in an endless loop.
OP, you'll have to wipe and reinstall. If you've rooted it and enabled USB debugging then you're golden. If not, you'll have to go through several hoops to flash a factory image.
This link should help. http://forum.xda-developers.com/showthread.php?t=2016395
Several users have managed to invoke ADB commands.

Launcher
Smitty50 said:
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Click to expand...
Click to collapse
I have go launcher. After changing a wallpaper it starts the system ui loop pop up.
So after the restart I went to settings to come back to default launcher.
No more pop up
Tell me if it works with you...

cadiutori said:
I have go launcher. After changing a wallpaper it starts the system ui loop pop up.
So after the restart I went to settings to come back to default launcher.
No more pop up
Tell me if it works with you...
Click to expand...
Click to collapse
This thread is 4 months old. I'm sure he fixed it already lol
Sent from my Nexus 4

time and space don't exist
spaceman860 said:
This thread is 4 months old. I'm sure he fixed it already lol
Sent from my Nexus 4
Click to expand...
Click to collapse
maybe useful for someone else

cadiutori said:
maybe useful for someone else
Click to expand...
Click to collapse
Yes. Maybe he didn't restore the default keyboard before removing.

Hey, thread is old but have not found soultion for fixing "unfortunately systemUI has stopped" for PAC-man V05.. The ROM has all the options within it to customize without adding a theme and yet the friknnnnnn thing does this.. I went all the way back to flashing 4.1.2 again, rooting, formatted all storage... And even gave a 2gig partition for ROM(safestrap) still get error, sad cause has been my daily Rom for quite some time.. Just started out of the blue?? Suggestions??
XT912 RaZR SpYdEr CDMA

1droidmod said:
Hey, thread is old but have not found soultion for fixing "unfortunately systemUI has stopped" for PAC-man V05.. The ROM has all the options within it to customize without adding a theme and yet the friknnnnnn thing does this.. I went all the way back to flashing 4.1.2 again, rooting, formatted all storage... And even gave a 2gig partition for ROM(safestrap) still get error, sad cause has been my daily Rom for quite some time.. Just started out of the blue?? Suggestions??
XT912 RaZR SpYdEr CDMA
Click to expand...
Click to collapse
Flash factory image
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
Flash factory image
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
He doesn't have a nexus. He's in the wrong place
From my BLACKED OUT N4

Sorry.. Googled topic, brought me here, did not realize... And i did fastboot the firmware, still systemUI issue but only with PAC-man... Handful of others I tested no issues.. I read on github (after i posted here) is a Know issue for PAC and why!!! Just strange, V05 was released weeks ago, why sooo long for issue to submerge... And no issues with V01-V04
XT912 RaZR SpYdEr CDMA PAC-manVO5

I am having this situation right now for my Nexus 4 (running stock 4.2.2 and installed Quick Settings mod from kevdliu, use the ROM for a long time and one day want to wipe all, after wiping, and reboot system I got this) and I think I figured out the solution: Wait until the battery is exhausted and automatically turned off, then put it into the charger for some time. Then pull it out of the charger, press volume up + down + power to get into fastboot. From here, we can wipe all and flash a new rom, or restore to stock rom, or do anything fastboot can do.

nubhihi219 said:
I am having this situation right now for my Nexus 4 (running stock 4.2.2 and installed Quick Settings mod from kevdliu, use the ROM for a long time and one day want to wipe all, after wiping, and reboot system I got this) and I think I figured out the solution: Wait until the battery is exhausted and automatically turned off, then put it into the charger for some time. Then pull it out of the charger, press volume up + down + power to get into fastboot. From here, we can wipe all and flash a new rom, or restore to stock rom, or do anything fastboot can do.
Click to expand...
Click to collapse
why install quick settings when stock 4.2.2 comes with its own form of quick settings? I'm willing to bet that's your problem!

hp420 said:
why install quick settings when stock 4.2.2 comes with its own form of quick settings? I'm willing to bet that's your problem!
Click to expand...
Click to collapse
you haven't used stock 4.2.2 have you? Its quick settings is so frustrating, it always takes me to Settings to turn on or off Wifi. I want a quick Settings that takes only one click to turn on or off Wifi, so I have to install that mod. Btw, I'm still waiting for the battery to die
_______________________________________
Update: Just to confirm, it works as I expected

hey i know this thread was already answered but i found that this messaged popped up after changing some settings for the navigation bar at the bottom of the screen. i didnt want it on my screen because i kept clicking either the back button or the home button which was very frustrating. so i tried to turn it off..that didnt work so instead i set all of the buttons to empty and the visibility to 0% and only after tracing back the steps i took (having to click the ok button for the stupid message about 80 times) i finally managed to find out that the navigation bar was the problem. hope you guys are able to fix your problem as simply as i did without doing anything drastic.

cjleven4 said:
hey i know this thread was already answered but i found that this messaged popped up after changing some settings for the navigation bar at the bottom of the screen. i didnt want it on my screen because i kept clicking either the back button or the home button which was very frustrating. so i tried to turn it off..that didnt work so instead i set all of the buttons to empty and the visibility to 0% and only after tracing back the steps i took (having to click the ok button for the stupid message about 80 times) i finally managed to find out that the navigation bar was the problem. hope you guys are able to fix your problem as simply as i did without doing anything drastic.
Click to expand...
Click to collapse
I recently had this issue and determined also that it must be something with my status/notification bar as it seemed to resize the screen to show the bar and then immediately resized it again as it displayed the System UI message. I use both Wanam and XBlast and disabled those as well as all Xposed modules. I also disabled Nova Launcher as default and rebooted. Re-enabled all and rebooted again and problem was resolved. Hopefully this will help others as well.

Same thing happened to my phone - Huawei Ascend y511. System UI has stopped Help!!!!!
Smitty50 said:
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Click to expand...
Click to collapse
Hi I have huawei ascend y511 and after disabling google keyboard i turned off phone and put it back on. This happened. Help me please, How do I get it back to normal? If I factory reset, will it work? Or should I let the battery drain out and do something. I can't do anything on my phone now because I can't even press anything because of the really frequent pop out of "system ui has stopped" . Help please.

Wanam or xposed Bootloop issue GRRRRRR

This is the 3rd time i format my phone and until i install wanam i have no issues, but when i do i always get bootloops. Whats happens is i install wanam and reboot to apply settings and then it boot normally, i see the lockscreen and the it turns off and boots directly to samsung letters and hangs there, could hang there for 5, 10, 20 minutes, then it boots back into the lockscreen and then hangs on samsung letters again. Tried clearing cache, nothing. I'm giving up on this wanam...anybody knows how to troubleshoot the issue?

polish_pat said:
This is the 3rd time i format my phone and until i install wanam i have no issues, but when i do i always get bootloops. Whats happens is i install wanam and reboot to apply settings and then it boot normally, i see the lockscreen and the it turns off and boots directly to samsung letters and hangs there, could hang there for 5, 10, 20 minutes, then it boots back into the lockscreen and then hangs on samsung letters again. Tried clearing cache, nothing. I'm giving up on this wanam...anybody knows how to troubleshoot the issue?
Click to expand...
Click to collapse
have you installed xposed installer

jaythenut said:
have you installed xposed installer
Click to expand...
Click to collapse
of course:silly:
EDIT: i actually think my issue might be with xposed because i was able to boot back in OS and uninstalled wanam, rebooted and i still have the same issue

polish_pat said:
of course:silly:
Click to expand...
Click to collapse
updated it and ticked wanam

jaythenut said:
updated it and ticked wanam
Click to expand...
Click to collapse
i actually think my issue might be with xposed because i was able to boot back in OS and uninstalled wanam, rebooted and i still have the same issue. xposed is at latest version
Weird thing, xposed works fine until i install wanam

polish_pat said:
i actually think my issue might be with xposed because i was able to boot back in OS and uninstalled wanam, rebooted and i still have the same issue. xposed is at latest version
Weird thing, xposed works fine until i install wanam
Click to expand...
Click to collapse
somethings dont work on wanam maybe one of them is bootlooping i know [fake system status] will bootloop

jaythenut said:
somethings dont work on wanam maybe one of them is bootlooping i know [fake system status] will bootloop
Click to expand...
Click to collapse
yes, fakesystemstatus was the first thing i activated...i will try to reinstall everything and not touch that

Alright so i started theming, basically just changing a few colors here and there and the same issue happened once again! It hangs on Samsung letters

So the issue is with wanam, i've been running xposed and a few of its modules for the past couple days with no issues, but as soon as wanam goes on, things get problematic

I had both wanam and gravity box running for almost a week with no problem. Last night I thought there were quite a few overlapping settings and maybe I should just stop using one of those two modules. So I unticked wanam in the installer and rebooted.... WAH!! all hell broke loose and the phone just kept rebooting. It must be at least 10 times before it just stopped by itself and stayed on. I quickly went into xposed installer and uninstalled wanam. After that it didn't reboot itself any more. I'm just worried that something might be messed up and I'll need to wipe it clean. Let's hope that it won't be necessary.
So if you're trying to get rid of wanam after reading this thread, just be warned that what happened to me might happen to you too. Then if nothing works, you can always wipe and start again in recovery, stock or cwm.
I just need to mention gravity box here because it does most of what wanam can do and some more. There is even a mod to toggle flash led on the lock screen with the home key, instead of using the volume up key. Also most of the settings are activated without rebooting. Give it a try and you won't regret it.

ioneng said:
I just need to mention gravity box here because it does most of what wanam can do and some more. There is even a mod to toggle flash led on the lock screen with the home key, instead of using the volume up key. Also most of the settings are activated without rebooting. Give it a try and you won't regret it.
Click to expand...
Click to collapse
GB is meant for AOSP-based roms - stock Android, or close to it - TouchWiz is definitely not that. Wanam is essentially the TW-equivalent of GB.

Well that's why I installed wanam first, then I read here someone was using it on his note3 and it works alright. So I tried it too and it's been problem free so far.
Sent from my SM-N9005 using Tapatalk

I have xblast toolls installed. Same problem here with bootloop after install.
I have 5 Modules installed and it seems there's a bootloop for every mod installed. I think it reboots after the mod is run and then moves on to the next mod. It eventually boots into lock screen and stays there but it can take a while...

I have 2 modules installled, wanam and greenify. Every time i change a setting in wanam and reboot, it get bootloop. Left it there for 2 hours yesterday and it never booted back in OS. Although i have found that clearing dalvik and cache maked it loop only once and then it boots back in OS
Sent from my SM-N900T using Tapatalk

Strange. No issues here. I installed xposed, updated and then rebooted. Then played a lot with wanam, rebooted for like 10 times. No issues.
Sent from Note 3 (The beauty & beast)

Why is my rooted phone lagging?

A couple of weeks ago i rooted my phone and it was all good, i installed Adaway, Camera sound off, uninstall and titanium backup. But then my phone started lagging, every few minutes my phone just laggs.
It doesnt matter what app i'm in or how many apps i've opened, the screen just laggs and the touchscreen doesnt respond for a few seconds and then it stops and returns in a few minutes.
Any ideas what may cause this?
*edit*
I also installed xposed and the extended snappchat module
(i have the sm-n910f)

fcbmootje said:
A couple of weeks ago i rooted my phone and it was all good, i installed Adaway, Camera sound off, uninstall and titanium backup. But then my phone started lagging, every few minutes my phone just laggs.
It doesnt matter what app i'm in or how many apps i've opened, the screen just laggs and the touchscreen doesnt respond for a few seconds and then it stops and returns in a few minutes.
Any ideas what may cause this?
(i have the sm-n910f)
Click to expand...
Click to collapse
Did you install xPosed? Some people have reported lagging when using xPosed on their Note 4's.

jpbl1976 said:
Did you install xPosed? Some people have reported lagging when using xPosed on their Note 4's.
Click to expand...
Click to collapse
Yess, i installed it and used the extended snappchat module. Then i deleted them both, could it still be somewhere in my system?

I too installed it and now every few mins screen just lag even after deleting it.....

fcbmootje said:
Yess, i installed it and used the extended snappchat module. Then i deleted them both, could it still be somewhere in my system?
Click to expand...
Click to collapse
after i installed xposed i had same lag and freezes i uninstalled xposed but still had lag so i unrooted su but the phone wouldnt reboot after that it looped on samsung logo so i had to reflash stock firmware to get it up and running so be careful...

There are thread here where the solution to this problem is solved. It has once happened to me and I already fix it but I didn't remember which of the thread. You need to just search the forum, am sure your phone will be fine

fcbmootje said:
A couple of weeks ago i rooted my phone and it was all good, i installed Adaway, Camera sound off, uninstall and titanium backup. But then my phone started lagging, every few minutes my phone just laggs.
It doesnt matter what app i'm in or how many apps i've opened, the screen just laggs and the touchscreen doesnt respond for a few seconds and then it stops and returns in a few minutes.
Any ideas what may cause this?
*edit*
I also installed xposed and the extended snappchat module
(i have the sm-n910f)
Click to expand...
Click to collapse
HI ,
i also have N910F ,rooted , xposed etc . i found that the lag was caused by xposed .
I followed this post #22 and post #32 re , " angelky " advice and the lag was sorted out ..my Shealth is working fine and private mode( which gets broken with root, is working) ( wanam /settings Security hacks then tick Disable Secure Storage.)
http://forum.xda-developers.com/note-4/help/xposed-t2904937/page3
good luck

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?

Nexus 10 (manta), Lineage OS 13, bootloop with Nova Launcher

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