Related
[Q] Please help! "unfortunately the process com.android.systemui has stopped"
I have a rooted nexus 5 running CM11. I kept getting this message before and I didn't know why so I posted here and someone told me to wipe my data so I did. That fixed the problem for about 2 weeks but it's back again. It happens so frequently now its very frustrating. It happens when I open an app, update an app or uninstall an app. Not every time but most frequently when updating. Why is this happening?! Please help and thanks in advance!
Just reflash your ROM or flash a different ROM and your problem should be fixed
Sent from my Nexus 5 using Tapatalk
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
CitizenLee said:
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
Click to expand...
Click to collapse
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
lilfil3 said:
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
Click to expand...
Click to collapse
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
CitizenLee said:
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
Click to expand...
Click to collapse
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
lilfil3 said:
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
Click to expand...
Click to collapse
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
CitizenLee said:
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
Click to expand...
Click to collapse
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
lilfil3 said:
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
Click to expand...
Click to collapse
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
CitizenLee said:
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
Click to expand...
Click to collapse
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
lilfil3 said:
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
Click to expand...
Click to collapse
You can change all that stuff in GravityBox and XGEL so might be best to just use those instead
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
thank you. this helped me today.
woke up with the error. assuming its gravitybox and xblast causing an issue. will remove xblast.
i9o said:
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
Click to expand...
Click to collapse
Xposed does not actually "touch" or change SystemUI in any way. Xposed puts a couple of "files" in system which allows intercepted commands to be changed, without changing the actual code.
When you updated the ROM via a toolkit (PLEASE don't use toolkits by the way) you would have overwritten these Xposed files.
The simplest fix is to just remove the Xposed files
Sent from my Nexus 5 using Tapatalk
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
did you do any other system modifications? change kernels?
I'd just dirty flash 4.4.3 and call it a day.
Zepius said:
did you do any other system modifications? change kernels?
Click to expand...
Click to collapse
Nop, unless apps like titanium backup or file manager (only other apps that require root) change something. :/
Lokke9191 said:
I'd just dirty flash 4.4.3 and call it a day.
Click to expand...
Click to collapse
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
OTA is more complex if you're rooted.. There's more flashing involved if you have / want a custom recovery (which all rooted users should aim to have)
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes, boot recovery, flash, re-flash recovery, re-root
Rooted stock = boot recovery, flash
No brainer really. Flashing an OTA if rooted is a fool's errand
Sent from my Nexus 5 using Tapatalk
oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
lmao, its FAR from the most simple method. most simple method would be to dirty flash a 443 stock/rooted rom and call it a day, without over complicating anything.
oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.
marleyfan61 said:
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.
Click to expand...
Click to collapse
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises
oshera said:
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises
Click to expand...
Click to collapse
Glad it worked for you. For future reference, do read this sticky - http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
(along with the other stickies in that forum)
Title. Any ideas what might be the problem and solutions?
Are you running exposed framework or are you rooted? If so, wipe and re-install your ROM. Make sure not to root or install exposed until after you've installed Snapchat and logged in. That's how I fixed the issue.
Sent from my Nexus 5 using Tapatalk
Spring Roll01 said:
Title. Any ideas what might be the problem and solutions?
Click to expand...
Click to collapse
Nah, he doesn't have to wipe his whole phone..
JaymzTA said:
Are you running exposed framework or are you rooted? If so, wipe and re-install your ROM. Make sure not to root or install exposed until after you've installed Snapchat and logged in. That's how I fixed the issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If you are running xposed framework.. just flash the xposed uninstaller zip, reboot your device and log in your Snapchat account. And then you can just reflash xposed framework if you want to. Snapchat doesn't get blocked due root access, it just tries to prevent you to run any modules if you have xposed installed.
Snapchat doesn't work with rootcloak and rooted phones anymore.
Does anyone know how to get snapchat working with a rooted phone. I have already tried removing XDA Framework and using rootcloack and it didn't.
I refuse to remove root.
racing121 said:
Snapchat doesn't work with rootcloak and rooted phones anymore.
Does anyone know how to get snapchat working with a rooted phone. I have already tried removing XDA Framework and using rootcloack and it didn't.
I refuse to remove root.
Click to expand...
Click to collapse
Hello and welcome to xda-assist,
we actually don't do technical support, we're here to guide you to the most suitable board on xda
So and ask here again
http://forum.xda-developers.com/android/help
I don't use snapchat myself but know from other people that it's working on rooted devices when
A) you install snapchat and login on a unrooted device and then apply root, it seems to work fine when you root a device when snapchat is already running
OR
B) use magisk su, you can download magisk manager from Playstore and depending on your set-up you can flash the necessary files from within the app or flash a zip from recovery in addition to the app from Playstore, magisk has a hide option and is able to make rooted devices pass safetynet, therfore snapchat is working, see here:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Try to hide google pay app with "magisk hide" in magisk app
Edit:
Google Pay is working with my OP6 [email protected] and TWRP
Google pay is working fine for me too also rooted with magisk
Some people have begun to have issues with Magisk and safetynet tripping over the past few days, we're trying to figure it out in the Magisk forums. This appears to have coincided with the Android Pie release and it's possible modifications have been made to safetynet. John Wu is looking into it. There are a few additional modules you can try along with Magisk Hide. Some work for some people. I've had no luck yet personally.
ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
Busybox always makes me fail safety net, even systemless. Make sure you haven't installed a magisk module with it or a custom rom with it. I think recent Google versions check for it.
ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Yesterday 12:27 PM
Pundy
Try to hide google pay app with "magisk hide" in magisk app
Edit:
Google Pay is working with my OP6 [email protected] and TWRP
Click to expand...
Click to collapse
thanks for the tip but i already have it hidden.
Yesterday 11:25 PM
yldlj
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Click to expand...
Click to collapse
i Tried this as it sounded promising, but no joy, i still can't get it to work, thanks for the help though so far everyone, but nothing has worked.
texasaggie1 said:
Busybox always makes me fail safety net, even systemless. Make sure you haven't installed a magisk module with it or a custom rom with it. I think recent Google versions check for it.
Click to expand...
Click to collapse
Unfortunately removing BusyBox didn't change the fail
fireguy0306 said:
Unfortunately removing BusyBox didn't change the fail
Click to expand...
Click to collapse
Have you tried using the island app ?
Also you know you have to wipe/reset Google Play before you check again correct?
once you fail safety net it will always fail no matter what until you reset Google Play
yldlj said:
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Click to expand...
Click to collapse
i clear all data every time i change anything as standard practice, but thanks for the idea
texasaggie1 said:
Have you tried using the island app ?
Also you know you have to wipe/reset Google Play before you check again correct?
once you fail safety net it will always fail no matter what until you reset Google Play
Click to expand...
Click to collapse
i don't know what the island app is, but as above i wipe all data as standard everytime i change something, i'll look inti island, but i'm starting to thing this is just a bug
Have the problem as well..
I have the same problem. Running OP6, Android P Developer Preview 4, TWRP recovery and magisk (v16.7).
Magisk hide is enabled for GPay as well as many other banking apps. I know for sure its something to do with GPay, since the other apps that initially complained and triggered safetynet, started running as soon as I enabled Magisk hide for those apps.
ClassicRando said:
i clear all data every time i change anything as standard practice, but thanks for the idea
i don't know what the island app is, but as above i wipe all data as standard everytime i change something, i'll look inti island, but i'm starting to thing this is just a bug
Click to expand...
Click to collapse
Google pay issue with rooted oneplus 6 (PIE)
Hi all,
Try the steps as advised in the video, it worked for me
https://youtu.be/lyC1SpDWMNA
Thanks
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
android_smater said:
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
Click to expand...
Click to collapse
This worked for me thank you
Websterwjc said:
This worked for me thank you
Click to expand...
Click to collapse
Welcome...
ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
I finally found the route cause of gpay not working, it was my WiFi, I found the answer purely by accident when I was in a shop and had forgotten my wallet, so I did a last ditch attempt to set up gpay again with my mobile data and it worked first time, when I got home i deleted the app and reinstalled while trying to set up via WiFi again and I got the same error message, switched to mobile data and it set up perfectly.
I have no idea why my WiFi was stopping gpay from getting set up, but that was the cause, 100% certain.
android_smater said:
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
Click to expand...
Click to collapse
yes, this works.
Hi,
It was working before for me until 15th March, and now it completely stopped working. I've tried to re-add my card, but then it complains about the device is rooted or altered. I could keep device certification, and safetynet check passes. Tried these methods, nothing.
Does anyone has any suggestions?
Thanks
antivirtel said:
Hi,
It was working before for me until 15th March, and now it completely stopped working. I've tried to re-add my card, but then it complains about the device is rooted or altered. I could keep device certification, and safetynet check passes. Tried these methods, nothing.
Does anyone has any suggestions?
Thanks
Click to expand...
Click to collapse
Update Magisk to v19 and clear data of the app, hide it in Magisk Hide and try to re-add it
I have a fix I u didn't have one, First of all hide all Google apps from Magisk hide.
Then goto setting, apps, permission and disable telephone permission of google play services. That's it.