Okay, so my AT&T Galaxy s4 has been rooted for 5 months, never had a problem. I rebooted my phone today and a message pops up and says "Unfortunately, System UI has stopped" No idea what happen plus it keeps on popping up. I tried to flash it with odin, and it failed. I can't do anything! Does anybody know what i can do?
Are you flashing the correct firmware? It's has to be the same as you were on.
Related
Hi!
Today I got a notification that there was an OTA ready. After installing the OTA my S4 keeps rebooting. It only works for 5-10 seconds and then it reboots. Not a complete reboot though, I don't have to type my pin again I just get the blue-purple ring and the samsung logo.
I've tried booting into recovery and did a factory reset but it still reboots:crying:
My S4 is the international version and it is completely stock and not rooted.
What do I do?
Thanks
EDIT: I started from scratch without importing apps and settings from google at it seems to have done the trick
So my phone was acting really laggy, I mean really laggy. So I decided to reboot my phone, and once it loaded up the lock screen, it came up with an error stating "Unfortunately, the process com.android.systemui has stopped."
Just a fair warning, I didn't root my Galaxy S4, but installed 4.4.2 Kitkat via Kies. Since then, I have not rooted either.
OT, but before I updated to 4.4.2 via Kies, I tried on my phone to see, and it says "Your phone has been modified...." and that it can't update it.
So anyways, could this have just been a fluke? Should I worry about it happening all the time?
I have been getting this error non stop since I updated to lollipop. I can barely do anything on the phone because it pops up so quickly and repeatedly. This is a stock LG G2. Any ideas?
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
durantala said:
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
Click to expand...
Click to collapse
Did you try to just uninstall supersu and redownload it from the play store?
Lennyz1988 said:
Did you try to just uninstall supersu and redownload it from the play store?
Click to expand...
Click to collapse
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
durantala said:
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
Click to expand...
Click to collapse
Right now I don't see any other choice than flashing a stock rom.
Or you could try reflashing the recovery.
Make sure you are using the back USB ports and the original cable. Odin is quite sensitive with this.
Unlocked boot loader, installed DK S7 Edge/Note 5 INSTALL THREAD SMS/MMS Rom.
Rom is great but getting error When someone calls me or when the call is ended. I get the following error "unfortunately the process com.android.phone has stopped"
I've force stopped the phone app...all 3 of them, clear cache and data..and rebooted,, still the same.
Appears to be common right from verizon when the took the S7 and updgraded it to 6.0.1
http://forums.androidcentral.com/sa...ly-process-com-android-phone-has-stopped.html
http://thedroidguy.com/2016/05/fix-...ocess-com-android-phone-stopped-error-1059365
Didn't know if someone else had these concerns as well as a fix.