• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help System UI Crashing Constantly

JaronH

JaronH

Well-Known Member
Hello,

I can't find a solution to this problem on my own, so I'm asking you guys for help. SystemUI is crashing constantly for whatever reason. This started to happen a few days ago for no obvious reason, and no direct modification has been made to systemui.apk.

I've tried wiping the cache partition and deleting the app which I assumed was causing the problem (which was Snapchat, since it happened around the time I installed it), but my problem persists.

Is the only other way to fix this is a factory reset?

-Jaron

LG G Stylo
Rooted Android 6.0
 
Can you restore a backup? Maybe just wipe system and restore system only? That should leave the data partition intact.
That said. The data partition may be where the corruption is coming from.
Also, if you are using a custom ROM you could try a "dirty flash" but I have a feeling that will make it worse.
 
Bg260 said:
Can you restore a backup? Maybe just wipe system and restore system only? That should leave the data partition intact.
That said. The data partition may be where the corruption is coming from.
Also, if you are using a custom ROM you could try a "dirty flash" but I have a feeling that will make it worse.
Click to expand...
Not on a custom ROM (because of the two, um, "actively updated" ROMs made available to me).

The system backup is a good suggestion, but I'm not entirely sure because of the system-less modifications I made.
 
JaronH said:
Not on a custom ROM (because of the two, um, "actively updated" ROMs made available to me).

The system backup is a good suggestion, but I'm not entirely sure because of the system-less modifications I made.
Click to expand...

Systemless is getting outside of my realm of knowledge. I think eventually it will get to the point where it will just Bootloop.
So at this point your system is mounted read-only I assume?
I know there are some features built into TWRP. Fix permissions would be one.
There is also a file manager built in but it is laborious because only one file can be moved at a time.
Last suggestion. Backup Data partition, factory reset, restore data partition. Once again the data partition may be the cause of this in the first place........and you would just restore the issue:(
 
Bg260 said:
Systemless is getting outside of my realm of knowledge. I think eventually it will get to the point where it will just Bootloop.
So at this point your system is mounted read-only I assume?
I know there are some features built into TWRP. Fix permissions would be one.
There is also a file manager built in but it is laborious because only one file can be moved at a time.
Last suggestion. Backup Data partition, factory reset, restore data partition. Once again the data partition may be the cause of this in the first place........and you would just restore the issue:(
Click to expand...
Thanks for the help, man. I'll just backup and restore my data as suggested and see if this will serve as a fix... I'm only hoping it will.
 
You might get an idea of what is going on by viewing the logcat and/or the kernel log:

adb logcat -d > logcat.txt

adb shell dmesg > kernel-log.txt ​

(you'll have to control-c to stop the kernel log--let it run / capture for a while and then do the control-c or soon-ish after you've seen the issue occur; the above logcat will just dump the current log and then exit)
 
scary alien said:
You might get an idea of what is going on by viewing the logcat and/or the kernel log:

adb logcat -d > logcat.txt

adb shell dmesg > kernel-log.txt ​

(you'll have to control-c to stop the kernel log--let it run / capture for a while and then do the control-c or soon-ish after you've seen the issue occur; the above logcat will just dump the current log and then exit)
Click to expand...
Hmm... I'm getting an "Access is denied." on both of those commands.
 
JaronH said:
Hmm... I'm getting an "Access is denied." on both of those commands.
Click to expand...

Ah, sorry @JaronH, you typically run those from your PC where you've got access to the adb utility and USB connectivity to your Android device (I didn't establish what resources you might already have or have setup).

You should be able to run similar commands from a Terminal Emulator for Android app's command prompt instead if you don't have adb setup to connect your PC and device:

logcat -d > /sdcard/logcat.txt

dmesg > /sdcard/kernel-log.txt ​

(you might omit or modify the "/sdcard/" portion depending on where you want to send or save the output to...)

Also, I just realized you said "access is denied"...where are you actually seeing this (i.e., where did you type or paste the commands at)?
 
Also, when you say "system-less modifications", what did you mean by that?

I know what Chainfire's UPDATE-SuperSU-v#.##.zip can install root in a systemless mode (basically installs root in it's own partition, saves and them modifies your boot.img; but does not modify the /system partition).

What (recent?) changes have you made or things have you done to your device?
 
scary alien said:
Ah, sorry @JaronH, you typically run those from your PC where you've got access to the adb utility and USB connectivity to your Android device (I didn't establish what resources you might already have or have setup).

You should be able to run similar commands from a Terminal Emulator for Android app's command prompt instead if you don't have adb setup to connect your PC and device:

logcat -d > /sdcard/logcat.txt

dmesg > /sdcard/kernel-log.txt ​

(you might omit or modify the "/sdcard/" portion depending on where you want to send or save the output to...)

Also, I just realized you said "access is denied"...where are you actually seeing this (i.e., where did you type or paste the commands at)?
Click to expand...

No, I did run those through ADB on my PC, and "Access is denied." is what ADB returned to me when I input any of those commands. USB debugging is on and everything.
 
JaronH said:
No, I did run those through ADB on my PC, and "Access is denied." is what ADB returned to me when I input any of those commands. USB debugging is on and everything.
Click to expand...

Oh, that is really odd--I've never gotten a permission error in Windows when using adb...do you need to start-up the Windows Command Prompt in Administrator mode perhaps?

edit: or wait--is that your Android's shell that is reporting that? Those commands have always worked (for me) and never required root (su) access...

Lemme poke around some more...
 
Last edited:
scary alien said:
Oh, that is really odd--I've never gotten a permission error in Windows when using adb...do you need to start-up the Windows Command Prompt in Administrator mode perhaps?

edit: or wait--is that your Android's shell that is reporting that?

Lemme poke around some more...
Click to expand...
It returned nothing and I found the .txt in the Program Files, so that did it. I've also got another app running in case I do something I wouldn't want to do. [emoji28]

And I have root and Xposed running in system-less mode so I'll bypass root detection by some apps.
 
Last edited:
JaronH said:
It returned nothing and I found the .txt in the Program Files, so that did it. I've also got another app running in case I do something I wouldn't want to do. [emoji28]
Click to expand...

Okay, wait a sec--perhaps you are getting the "access is denied" because you're local directory on your PC is c:\Program Files?

Try cd'ing to or making a "temp" or "tmp" folder on your C:\ drive and issue the commands from there. Like this:

c:\Program Files>cd \
c:\>mkdir tmp
c:\>cd tmp
c:\tmp>adb logcat -d > logcat.txt
c:\tmp>adb shell dmesg > kernel-log.txt
c:\tmp>dir
Volume in drive C has no label.
Volume Serial Number is 843C-52A5

Directory of c:\tmp

11/26/2016 10:48 PM <DIR> .
11/26/2016 10:48 PM <DIR> ..
11/26/2016 10:48 PM 120,387 kernel-log.txt
11/26/2016 10:48 PM 558,624 logcat.txt
2 File(s) 679,011 bytes
2 Dir(s) 214,232,870,912 bytes free

c:\tmp>​
 
scary alien said:
Okay, wait a sec--perhaps you are getting the "access is denied" because you're local directory on your PC is c:\Program Files?

Try cd'ing to or making a "temp" or "tmp" folder on your C:\ drive and issue the commands from there. Like this:

c:\Program Files>cd \
c:\>mkdir tmp
c:\>cd tmp
c:\tmp>adb logcat -d > logcat.txt
c:\tmp>adb shell dmesg > kernel-log.txt
c:\tmp>dir
Volume in drive C has no label.
Volume Serial Number is 843C-52A5

Directory of c:\tmp

11/26/2016 10:48 PM <DIR> .
11/26/2016 10:48 PM <DIR> ..
11/26/2016 10:48 PM 120,387 kernel-log.txt
11/26/2016 10:48 PM 558,624 logcat.txt
2 File(s) 679,011 bytes
2 Dir(s) 214,232,870,912 bytes free

c:\tmp>​
Click to expand...
No, I wasn't getting access because I didn't run as an administrator. I use Minimal ADB, so it installed itself in Program Files, and that's where it placed logcat.txt.
 
JaronH said:
No, I wasn't getting access because I didn't run as an administrator. I use Minimal ADB, so it installed itself in Program Files, and that's where it placed logcat.txt.
Click to expand...

Cool...yeah, a non-admin launched adb won't be allowed to write into the Program Files folder--glad you got that sorted and hopefully you'll be able to catch some info to give context to allow you to figure-out what is causing the core issue.

:)
 
I had the same issue with my Lg Leon. I flashed a different kdz and it did the trick. Also try the logcat with no -d you will need to control + c to stop it to read the screens. Make sure you run it in the ADB directory
 
mswift23 said:
I had the same issue with my Lg Leon. I flashed a different kdz and it did the trick. Also try the logcat with no -d you will need to control + c to stop it to read the screens. Make sure you run it in the ADB directory
Click to expand...
I know reflashing will do the trick, I just don't WANT to. [emoji23]
 
You must log in or register to reply here.
Back
Top Bottom