Related
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
FingerBlastJ said:
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
Click to expand...
Click to collapse
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
x714x said:
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
Click to expand...
Click to collapse
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
FingerBlastJ said:
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
Click to expand...
Click to collapse
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
FingerBlastJ said:
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
Click to expand...
Click to collapse
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
x714x said:
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
Click to expand...
Click to collapse
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
FingerBlastJ said:
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
Click to expand...
Click to collapse
odin isnt allowing me to flash that image, attached is a screen shot
What does the error say? I can't read it that small.
x714x said:
What does the error say? I can't read it that small.
Click to expand...
Click to collapse
it says vmware-host\shared folders\desktop\root files\root66 file ..... then all these special characters that look like boxes
i tried running a different launcher, and they work a lil better but touchwiz is by far superior but i still get the nfc stopped message and everything is much slower
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
x714x said:
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
Click to expand...
Click to collapse
im using a mac so im forced to use windows xp on VM
FingerBlastJ said:
im using a mac so im forced to use windows xp on VM
Click to expand...
Click to collapse
ok i just did a factory reset and i still have the nfc issue along with the com.android.phone issue and i cant get into the mobile networks, any ideas of what i can do?
this thread here says its an nfc fix i just dont know if it will ruin my nfc capabilities
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
please help.
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
x714x said:
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
Click to expand...
Click to collapse
by flashing you mean formatting? why would that do anything when it didnt do much the first time?
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
how?
jamespat93 said:
Yesterday I rooted my phone and put on Xposed and gravity box. Since then I've been downloading various things and trying out different customisation options. The last thing I download was MotoXposed and I made my navigation bar completely transparent, when I tried to disable the effect my phone just came up with the message 'unfortunately the process com.android.systemui has stopped'. Now I can't use my phone and the message keeps coming up everytime I turn it on. How can I fix this? or get my phone working again?
Don't worry I've fixed my phone completely now.
Click to expand...
Click to collapse
Can you tell me how did you solve it w/o reseting your phone?
BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
thnx
thnxx got it!
BlakeParker said:
Can you tell me how did you solve it w/o reseting your phone?
Click to expand...
Click to collapse
All I had to do was reboot my phone and luckily (even though the message was still coming up) I could still use the touchscreen. This allowed me to go to the motoXposed module that caused the problems and undo the options I changed.
Unfortunately the process com android.systemui has stopped. Xposed Installer
Does anyone has any clue about this:
I have been having the same issue with my Galaxy S5.
I am using the rooted stock ROm with touchwhiz.
The issue started after I installed Xposed Installer with Wanam Xposed.
The "unfortunately the process com android.systemui has stopped" message does not come on until I received phone call while the phone is active. If I receive a call when the screen lock is on, the phone behaves normally.
The other issue I'm having with Xposed Installer are
1) a noticeable increase in lagging
2) apps takes close to 10 minutes to install
3) It takes a long time for the computer to see the phone after connecting them with USB....sometimes up to 15 minutes. thereafter it was not taking as long, but it was still being delayed.
I have flashed the phone three times with roughly the same observation after each flashing (i.e. issues cropping up only after installing Xposed Installer and some modules)
I'm going to try system tuner now...
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
edwardciasico said:
Did you managed to fixed it? I have the same problem as well!
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
No I did not. I factory-reset the phone. Did not install xposed installer again and It's been working well since then. However, I'm still going to try it one last time...I'll keep you posted
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
jimnu said:
I resolved this by booting into recovery (TWM in my case) and then manually deleting the offending .apk file from /data/app.
Click to expand...
Click to collapse
Which offending apk please?
ekitiboy said:
Which offending apk please?
Click to expand...
Click to collapse
In my case it was motoxposed.apk but YMMV.
sry for doublepost
To fix the systemui-crash u need to disable the (new):
"Heads up notification" on Wanam !!!
Help
I recently rooted my phone with TWRP using Odin. I did a few small things in customizing (ie: font, rotate screen) and now I get this error message.I've tried to boot in recovery and it just constantly flashes the Teamwin logo screen and i get no where. Could really use some help here, cannot use my phone at the moment
i have this issue too
I have this with Orbot. Simply restarted the phone and made a speed-run to uninstall it. Works to me.
So, the main question is: why this happen?
marc_miranda said:
Boot into recovery and flash Xposed-Recovery-Framework located at /sdcard . This is assuming the problem was caused by an Xposed module in the first place. Not sure whether OP uses this
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm facing the same problem i'm unable to use my phone, kindly explain in details how to flash xposed recovery.
the problem appeared after installing an xposed mod.
I picked up an AT&T 4G LTE Note Pro (SM-P907a) yesterday and so far I am absolutely loving it. And though this is my first post, I am no stranger to XDA, I currently have Galaxy S4, Note 3, Note 10.1, and now the Note Pro, all are rooted running custom roms, minus the Note Pro. I have never hade to make a post before because I understand how to use the search function and have always been able to find the answersI have needed, until now. I am hoping someone can tell me if it is possible yet to root AT&T's version of the Note Pro 12.2, SM-P907A? Will CF auto root for the Verizon SM-P905 work? Or am I simply to ahead of the game and need to wait for root to become available? Thanks!
Same here. Just got mine. Want to use about 3 apps that require root. It's only been out one day. At&t probably didn't add anything to what Samsung did as far as locking the bootloader. All I really want at this point is root, I don't need a new room yet. Yet
Based on how long the Verizon variant users have been waiting. .. come back in September. In all seriousness though, I hope you folks don't have to wait that long...
Sent from my SM-P900 using Tapatalk
Have either of you tried to root with towel root?
Sent from my SM-N9005 using XDA Premium 4 mobile app
thanks
AboveAverage said:
Have either of you tried to root with towel root?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brilliant!!!! thanks. I am installing busybox as I type this :laugh:
EDIT: haha spoke too soon, SuperSU won't install. Do you know how to get a custom recovery on it when rooted this way?
I can confirm towelroot is working for AT&T P907a.
Steps I took.
1. Download and installed towelroot (towelroot.com)
2. Ran towelroot apk, device rebooted.
3. Downloaded SuperSU 1.99r4 (download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip)
4. Ran SuperSU apk, installed binaries, disabled Knox
5. Done!!
jmedlin said:
I can confirm towelroot is working for AT&T P907a.
Steps I took.
1. Download and installed towelroot (towelroot.com)
2. Ran towelroot apk, device rebooted.
3. Downloaded SuperSU 1.99r4 (download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip)
4. Ran SuperSU apk, installed binaries, disabled Knox
5. Done!!
Click to expand...
Click to collapse
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
phirestalker said:
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
Click to expand...
Click to collapse
Mine has been running smooth, no reboots no freezing nothing. And yes unzip the file and SuperuserSU.apk is inside.
phirestalker said:
has yours been freezing and rebooting?
EDIT: also all I could find in the zip file was Superuser.apk, is that what you meant?
Click to expand...
Click to collapse
Mine is. But it was actually worse before root.
during one of the reboots I've been having it actually showed custom aND a lock that is unlocked. now when I reboot it doesn't say that anymore. root checker shows that it is properly rooted so I'm not sure that there's a problem.has anyone else noticed this?
I've had a couple of reboots.. what is weird is that it flashes to the at&t logo the my lockscreen. When I unlock it its like it rebooted but it happens so fast.. I am not sure if its a system reboot or just the user session crashing...
phirestalker said:
during one of the reboots I've been having it actually showed custom aND a lock that is unlocked. now when I reboot it doesn't say that anymore. root checker shows that it is properly rooted so I'm not sure that there's a problem.has anyone else noticed this?
Click to expand...
Click to collapse
When I reboot now I see this custom android and unlocked logo at the bottom of the screen. What I am unsure of is if it had this before I rooted.
If someone who based rooted their 907a reads this please check if you get this on a bootscreen during a restart.
I would like to hear from a couple people how their tabs are doing after root. I'm thinking about doing it.
My AT&T Note Pro 12.2 keeps rebooting. My WiFi only 12.2 restarts when attempting towel root and never patches the necessary files. My AT&T Note 3 was flawless though. 1 out of 3 ain't bad I guess. Really just want the ad block ability. Is there an unroot so I can get my tablet to stay on more than an hour?
Me and my friend both got the att 12.2.
After rooting I've had reboot issues while he hasn't. So I've been slowly uninstalling programs that I use and he doesn't. Thinking it might be one program or another or a combo of programs. First I uninstalled Greenify to no effect. Next I switched back to the Samsung launcher from Nova Launcher Pro. So far its been two days without a reboot since switching back to the touchwiz launcher.
I ran Nova launcher fine before root.. And my friend with the exact tablet rooted the same way has had no issues..
Are you running a launcher different than Samsungs?
Ill report back.. but so far so good.
That's a very good point. I'm using the stock launcher still but I do have a ton of apps. I'll have to try deleting some see if that has any affect.
Ok, some added details on my "rebooting" although it doesn't show the samsung logo, so I don't think it is a full reboot.
I have noticed that the only time it happens is when I lock the screen or when it locks itself. Sometimes it has been locked for a while and it will randomly do it. I don't believe it has ever happened while I was using it. Oh, and a few times it happened while unlocking the screen. So it all seems to be related to the lock screen. I don't have any apps that add functionality to the lock screen. I have a pattern unlock and Smart Stay enabled (although this never worked for me, maybe my face is too weird to be detected? Lol). I am going through the process of turning off things to see what might be causing the problem. The first thing I disabled was the LastPass accessibility extension. I will give it a day or 2 but I have been playing around with locking and unlocking with various apps open as i write this and I haven't had a "reboot" yet.
I noticed that another poster had trouble with a different app and like him this trouble started after I rooted it. The LastPass accessibility extension worked fine before rooting. I will tell you what this extension does and maybe it will help us narrow down what area of the system has been changed to be incompatible with certain software.
The extension "watches" for password entries on apps and webforms and offers to autofill with saved passwords.
Sorry for the long post, hope it is helpful to someone.
I've been running Lastpass for months on my Wifi model so I doubt it is the cause. Good idea to systematically disable things though. I have problems since enabling a custom keyboard though. Perhaps try disabling all other input methods other than stock?
Sent from my SM-P900 using Tapatalk
muzzy996 said:
I've been running Lastpass for months on my Wifi model so I doubt it is the cause. Good idea to systematically disable things though. I have problems since enabling a custom keyboard though. Perhaps try disabling all other input methods other than stock?
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
You're right, after a while it started doing it again. I guess it didn't happen as often as I thought. I really hope someone comes along who knows how to diagnose crashes to find out what is causing them.
I've been getting reboots also every once in awhile on my sm-p907a it reboots.I also tried safe strap recovery for the at&t samsung galaxy note 3 version 3.75.It seems to be working I did a nanoid backup and it successfully worked but took awhile. I didn't do a restore because I don't want to mess anything up until there's a stock Odin firmware download to restore if something goes wrong.The dpi is of but u can c almost the whole recovery screen if anyone wants to play around with it
I for the life of me can not figure out why my push notifications do not work when running custom roms. I have tried everything in the book. Clean installs/different kernels/different modems/different modems/new sim card/new google account. I have also tried a custom kernel on the stock rom and that didn't seem to work so I'm left to believe something with a custom kernel is breaking the notifications. Anybody have any ideas why this is happening?
Lobster$ said:
I for the life of me can not figure out why my push notifications do not work when running custom roms. I have tried everything in the book. Clean installs/different kernels/different modems/different modems/new sim card/new google account. I have also tried a custom kernel on the stock rom and that didn't seem to work so I'm left to believe something with a custom kernel is breaking the notifications. Anybody have any ideas why this is happening?
Click to expand...
Click to collapse
im on a custom rom(rastakat) and a custom kernel(trinity) and get all my notifications.
simms22 said:
im on a custom rom(rastakat) and a custom kernel(trinity) and get all my notifications.
Click to expand...
Click to collapse
Yeah it's definitely an issue on my end, I just have no idea what! I forgot to mention I had google RMA me a new phone too!
Lobster$ said:
Yeah it's definitely an issue on my end, I just have no idea what! I forgot to mention I had google RMA me a new phone too!
Click to expand...
Click to collapse
have you tried just flashing the factory img and starting over? if all your notification settings are on, and have what you need syncing, id try flashing the factory img and starting over.
simms22 said:
have you tried just flashing the factory img and starting over? if all your notification settings are on, and have what you need syncing, id try flashing the factory img and starting over.
Click to expand...
Click to collapse
Will give it a try!
by chance, maybe you "greenified" them?
Nope, not even installed!
Are you restoring apps? I have issues getting some notifications if i restore an app with titanium backup vs download again from the play store.
Sent from my Nexus 5
sdmark said:
Are you restoring apps? I have issues getting some notifications if i restore an app with titanium backup vs download again from the play store.
Sent from my Nexus 5
Click to expand...
Click to collapse
Nope, never used TiBu.
So after that latest update, I kept getting systemui force closes's and I couldn't figure out why.. Well I narrowed it down to the Substratum themes I was using to modify the systemui.. I was only using the standard Samsung ones that we get to center the clock and change the icons to AOSP, but those were apparently enough to make it do that.. I tried multiple times to fix it but each time resulted in a hard reset and had to start from scratch..
Hopefully this saves some who haven't done the update yet..
Side note: I think it has something to do with Samsung Backup literally saving every little detail and modification we do within certain app's, and the security update didn't like something about that perhaps..
Same thing happened to me. Even after I uninstalled all the themes and substratum I still got the FC.
Sent from my SM-N950U using Tapatalk
How did you reset the phone after the system ui crash?
chaztro1892 said:
How did you reset the phone after the system ui crash?
Click to expand...
Click to collapse
Through recovery
Sent from my SM-N950U using Tapatalk
Circlel05 said:
Through recovery
Click to expand...
Click to collapse
Cool. Thanks. So none of the substratum themes will work I assume.
You have to uninstall all of the Substratum theme stuff before you do the OTA. Says so in the thread and in the play store description. Just an FYI.
ShrekOpher said:
You have to uninstall all of the Substratum theme stuff before you do the OTA. Says so in the thread and in the play store description. Just an FYI.
Click to expand...
Click to collapse
Can the themes be reinstalled after the update?
chaztro1892 said:
Can the themes be reinstalled after the update?
Click to expand...
Click to collapse
Yeah I am running swift black with no issues right now.
ShrekOpher said:
Yeah I am running swift black with no issues right now.
Click to expand...
Click to collapse
I'm running swift dark right now and it's fine but I was told by the developer not to theme the system ui because it could restart the FC's. Can you confirm if that's the case for you?
newguy15 said:
I'm running swift dark right now and it's fine but I was told by the developer not to theme the system ui because it could restart the FC's. Can you confirm if that's the case for you?
Click to expand...
Click to collapse
I never used the system UI technically that is not supported on any Samsung devices with out root. It worked before, but was never officially support.
My father just updated his S8 with substratum installed and now hes getting FC all the time. Is there a way of recovering for this without losing everything? Thanks.
eXtremeDevil said:
My father just updated his S8 with substratum installed and now hes getting FC all the time. Is there a way of recovering for this without losing everything? Thanks.
Click to expand...
Click to collapse
Use adb to uninstall the Substratum overlay apks. I think the system ui overlay apk is the most important one to uninstall.
Then it should reboot fine
I dont have adb
eXtremeDevil said:
I dont have adb
Click to expand...
Click to collapse
You can set it up on a PC really easily.
You could try booting into "safe mode" and uninstall ingredients the overlay apks that way.
I meant on the phone, activated. I do have adb on my phone and my computer.
Safe mode didn't work eigther.
I ended up performing a factory reset.
Thanks anyway to all
This happened to me last week. I called AT&T and they ran through all their BS, they didn't have a clue what was causing it so they had me take my phone to a Samsung Experience Store AKA Best Buy. The tech there was useless I knew more about Samsung phones than he did so I ended up doing a factory reset. After getting my phone all set up and my apps downloaded I rebooted my phone and the same, thing so I called AT&T and they sent me a new phone priority which took 7 days ?. I got my new phone set it up download my apps did the update yesterday and boom same thing. My first mistake was not coming to this forum and not doing a search.
(This 'Should' be common knowledge when using substratum or any third party overlay that interacts with system files.)
But you should always uninstall any system overlay before performing a software update.
Otherwise you risk facing the SystemUI Force close issue.
If you are rooted you can recover via recovery (TWRP)
if you are not rooted the only way to recover without loosing your data is to try this:
How to recover?
You will have to boot up in Safe Mode (comes default on every device)
Reboot your device
Hold down the Volume Down key while booting up
You are now in Safe Mode
Go into Settings -> Apps, then find the overlay you think is messing up and uninstall!
How to recover if the above doesn't work? (Credits to Evozi)
You will have to boot up in Safe Mode (comes default on every device)
Turn on screen and press power button. It will show "Shutdown", "Restart", "Emergency Mode"
Turn on "Emergency Mode", keep spam the checkbox so you can tick the checkbox to proceed the agreement. (phone is super lagging)
While you are in emergency mode, you have very limited access. Open any system app and go to recent task list.
Long press the app task, press the info icon and app detail page will appear.
Hit the back button and it will show your whole app list.
Find your overlay and remove all its storage and phone permissions.
Deactivate Emergency Mode and now you are back to TouchWiz.
Uninstall the overlay app.
Click to expand...
Click to collapse
I was testing new and old system overlays when the Note 8 first came out to see what worked and what didn't, the ones that didnt gave me this problem.
You will most probably find the first one does not work and the second is a pain to get working, but personally i have had the Emergency mode method work for me after a few trys. I gave up at one point and started downloading firmware files to be honest but i gave it another shot while waiting and it worked.
Hope this helps - Hit thanks so this post gets shown to other users coming here looking for help
jdmsohc22 said:
So after that latest update, I kept getting systemui force closes's and I couldn't figure out why.. Well I narrowed it down to the Substratum themes I was using to modify the systemui.. I was only using the standard Samsung ones that we get to center the clock and change the icons to AOSP, but those were apparently enough to make it do that.. I tried multiple times to fix it but each time resulted in a hard reset and had to start from scratch..
Hopefully this saves some who haven't done the update yet..
Side note: I think it has something to do with Samsung Backup literally saving every little detail and modification we do within certain app's, and the security update didn't like something about that perhaps..
Click to expand...
Click to collapse
Awesome thanks for the heads up. Literally just got the substratum 2 days ago and am loving it so far.
I ended up factory reseting for this very reason
Sent from my [device_name] using XDA-Developers Legacy app
Has anyone on ATT but bought their phone unlocked from Samsung? On here