Caution, Nov update causes SystemUI FC if you use Substratum. - AT&T Samsung Galaxy Note 8 Questions & Answers

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

Related

"com.android.systemui has stopped"

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.

[Q] Apps Crashing Randomly After Xposed but that's just the beginning....

Hello there! i'm making my forum debut while extremely confused as to how to proceed with fixing my Verizon Galaxy S3, running the stock android JB 4.3. So there is no custom ROM.
I realize that this may or may not be similar to a plethora of posts about apps crashing around the time android 4.3 was released but i've upgraded to 4.3 less than a month ago. After diving through countless forums, i couldn't find one that addressed the same problems that my device had. They were all similar, but the solutions posed in those threads did not work with my device. Plus the problems i have are not isolated to one app.
I had just recently upgraded to android 4.3 which had unrooted my previously rooted device. After using Chainfire's method of rooting the SCH-I535, utilizing saferoot, i then installed the Xsposed Framework and that was really where my troubles began. A few days had passed while i was tinkering with a few modules like XBlast tools, XHaloFloatingWindow, Xposed Torch, and Wanam Xposed, and i had a good sense of what mods interfered with other mods and it was only last night when the problem first arose.
Without warning, a game that i play all the time stopped working. Literally in the time span of 6 hours (i was sleeping) something happened and the beginning of my problems started. Every time i would open the app, the app itself would close and i would get a message saying, "Unfortunately, Valkyrie Crusade has stopped." It was only a few hours later did i realize that Pandora, an app i use every day, suddenly stopped working and provided me with the same message. There was no error ID, and clearing the cache/data, reinstalling the apps, did not work. Once it became 4-5 apps that i normally use to get the message, i tried uninstalling the mods as well as the xposed framework but that also did not work. I also tried restoring the game as well as the other apps to a backup i'd made just the week prior with Titanium Backup but i still had the message coming up and the apps still did not work.
As a last resort i did a factory wipe/reset. During the initial set up, i opted to allow google to restore my apps (which i'm not sure i should have done) and after everything was restored, i tried using the apps, and i was met with the familiar message "Unfortunately, (app) has stopped.". I have run out of ideas. While i'm more tech savvy than most, i'm really just a novice when it comes to Android. How should i approach my next step? If anyone needs logs or anything like that, if you would be so kind as to walk me through the steps to get them.
Thank you, thank you, thank you in advance.
EDIT - 2/10/14
I have successfully resolved the issue (or at least, removed it) from happening. I bricked my phone but thankfully i was able to get into download mode.
Follow this guide! http://forum.xda-developers.com/showthread.php?t=2586319 - just be aware, this will delete all of your apps. backup all your propers and jump in.
This is the only method that i had success with. Other methods i tried are explained above and in the comments. Good luck and i hope everything works out!
If you had the Xposed frameware installed and you also installed Wanam xposed, this will help if you are experiencing apps crashing. I'm no expert, but i'm really glad to have resolved this as quickly as possible. I couldn't have done it without everyone! You guys literally kept my sanity healthy during this whole ordeal.
*NOTE* - The link to the guide above will lead you to a stock rom of android 4.3 for the SCH-I535. I'm not sure about other samsung devices but one user had success with a SCH-I605 (galaxy note 2) in the comments.
*ANOTHER NOTE*- i'm not in any way explicitly saying that the xposed framework and wanam xposed module are the cause of this glitch. Frankly i have no idea. But they seem to have been problems for a few people, myself included. If you want to explore this further, i'd suggest going to each of the respective forums. For me, i'm going to make sure i have a proper Nandroid before i do anything crazy. Lesson learned.
Again, Thank you!
PS- since i'm newer to this forum, i have no idea how to edit the title of this Q....haha if someone could let me know....that would be great.
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
daoist said:
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
Click to expand...
Click to collapse
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
awstuder said:
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
Click to expand...
Click to collapse
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
ATGkompressor said:
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think i'll try that next. I used to have TWRP but had to flash the stock recovery just to upgrade to 4.3. I'll try to get a clean copy of stock OS, flash and just start over from scratch. I'll be sure to let you guys know if i got it to work.
ran into a bump in the road. flashing a stock copy of android 4.0.4 did not work. Browsing through a few forums informed me that i'm unable to downgrade after i've taken the 4.3 upgrade. so next i tried to flash TWRP to boot into recovery mode and flash a rom from there. That didn't work either. I kept getting an authentification error.
As of now i can't get into download mode anymore. I get the yellow triangle saying Verizon detects unauthorized software. I'm able to get into recovery mode but i'm not sure what i can do with stock android recovery....
what can i do from here?
EDIT: I am able to get into download mode. I'm not sure why i wasn't before and now i am...
EDIT2: I have tried flashing the "official" stock android 4.3 but it fails everytime. I have also tried flashing twrp and cwm but i get a red Secure Check Fail: recovery. I suspect the bootloader has been locked. I'll look into ways of getting it unlocked again...
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
awstuder said:
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
Click to expand...
Click to collapse
Same here. Disabling all xposed modules didn't work. Disabling xposed entirely didn't work. Doing both and then uninstalling didn't work. My guess is that along the way either xposed or wanam xposed made some sort of change that it can't roll-back when it's disabled/uninstalled.
I resorted to taking a TiBu update of everything and reflashing.
Once I get my battlestation fully armed and operational I plan on taking frequent nandroids and seeing if I can replicate the issue. Once I do that, (if I do) I can compare the last known good nandroid to see what messed up.
BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't able to do this right away since had class in the morning but as soon as i got home, i did this and it fixed my soft-bricked phone.
thank you thank you!
Now back to the problem at hand......let's see if the problem still persists.
It's completely fixed! No apps (so far :fingers-crossed have crashed and i'm able to happily play my games again! sigh. that was refreshing.
Thank you to everyone! i will edit my first post to outline what i did and how i fixed it, finally....
during saferoot process your suppose to update SU then continue with finishing up the root process..took me several hours to figure this out..no errors now since I figured this out
Sent from my SCH-I535 using XDA Premium 4 mobile app
That... Actually makes sense. When I used safe root I didn't check for any other updates because I assumed the program took care of that for me. That and because when I opened su there were no notifications to update. So maybe that could be a solution as well.
Sent from my SCH-I535 using xda app-developers app

Reboots all the time since the latest OTA update

I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
You can try a factory reset.
ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?
I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.
Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.
Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.
fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.
Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.

Rooting LG Lucky (LGL16C)

Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Rooted LG Lucky
I rooted using kingroot version 4.8.0 I could use the stock Rom have no download if anyone could help thanks. Its a straight talk lg lucky running 4.4.2 kitkat I'm no computer whiz and I couldn't figure out how or what I needed phone works fine . now I just want to be able to do a factory reset safely if need be only deleted stock apps that I don't use nothing important I hope.
boct1584 said:
Can anyone verify that the method posted by Unjustified Dev in this thread will work the the indicated phone model?
Click to expand...
Click to collapse
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
STOCK firmware??
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
bonnis.phone said:
i got an lg lucky and its stuck in bootloop does anyone know how i could get stock firmware to flash? it goes to factory reset menu but freezes as soon as it starts to do its thing... maybe not fixable??
Click to expand...
Click to collapse
Depends on if yourlucky was rooted and if you deleted files you should have
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
I have obtained root on the device today. Ive read that some were able to do it with kingroot on the older versions but all have had no luck on the version with software version L16CV11a and build number KOT49I.L16CV11a. Well i managed to root it today with a certain methid...will post up a guide later after ive written it out...may see if i can further the progress now that ive rooted it.
Click to expand...
Click to collapse
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
2k73 said:
I have the newer Model LGL16C/4.4.2/Baseband version M8610B-AAAANAZM-1.0.6060/Kernel version 3.4.0+/Build KOT49I.L16CV11a/Software version L16CV11a/"Lucky". Service provider is Tracfone, aka Crapfone. Attempts to root with Kingroot as well as Kingoroot failed, including several apps which claim to root your phone. I paid less than $10 US dollars for this phone and rooting it isn't high on my priority list, however rooting the damn thing has presented a bit of a challenge.
A working guide to rooting this phone would be great.
Click to expand...
Click to collapse
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
REV3NT3CH said:
Give me a few days to write it out...basically if you have the knowledge...what I did was run kingroot while plugged into PC...was a tad tricky but I'll get further into it later...took a few tries
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
PizzaMaster said:
Hey mate,
I hate to be like a noodge, but would you be able to explain how you rooted? Would be so much appreciated.
Click to expand...
Click to collapse
Hey so i spent forever trying ro find a root that would work on this. Or a custom ROM anything really. Try going into McAfee Security, setting up an account, go to settings and disable the lock down device option. That was the problem for me at least McAfee was blocking any root from installing. From there i rooted my lucky with kingroot one click root. Hope this helps!
The Easiest Way To Root Your LG Lucky Without a PC
Easy way to install SuperSU on your LG Lucky
Just follow directions
Use KingRoot 4.5.0 app - google KingRoot apk all versions. Download and install apk.
Google replace kingroot with supersu. There will be a few sites popup, Mediafire is where the original .zip file is hosted. You can even search "how to replace/remove kingroot with supersu" here on XDA for more info.
Once you have downloaded the .zip file be sure to extract it to your INTERNAL sd, the script in the zip will not work from your external sd.
Open the extracted file and copy the mrw file to the internal storage, the path should look like /storage/emulated/0/mrw.
Now go to the play store, download and install Terminal Emulator. I use the one by Jack Palevich as it is only 551kb and easy to use.
Open the terminal emulator and type "su" in order to grant super user permission to the emulator,
On the next line type "/system/bin/sh - /storage/emulated/0/mrw/root.sh" and press enter.
Now the script will run and open up SuperSU automatically. Install binary when prompted with the "normal" option. Choose yes when it asks if you want to delete other superuser apps. (this removes kingroot).
Before rebooting phone, go into the settings of SuperSU and enable pro mode, change icon if you wish, enable survival mode, enable su during boot. I think you have to restart app at this point, can't remember as I did this months ago. Then restart the SuperSU app, go back into settings to Install SuperSU into system. Reboot phone,
When phone reboots, this is when Kingroot is finally uninstalled. Your phone will still be rooted with SuperSU. At this point you may wish to update SuperSU as this is version 2.46 and the newest version is 2.71 Beta. You can get the newest version of SuperSU from the thread here on XDA.
(thanks MrWolf for the script to make the change and thank you Chainfire for SuperSU, FlashFire, CF.lumen, etc...)
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
mikemc63 said:
LGL-16C successfully (so far) rooted using Kingoroot.exe (latest version). Had to change from mtp to camera on USB then was recognized. Have SuperSU 2.72, SuperSU Pro, BusyBox Pro, and Xposed installed with Xblast and Lucky Patcher running. No custom recovery or roms available and I have searched hi and lo. Was a Net10 $15 phone with nothing to lose, so...will try more stuff out another day and post again.
Click to expand...
Click to collapse
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
REV3NT3CH said:
Until any source is made there will be no recovery or ROM and tbh I don't have the time to dig into it currently.. The positive with rooting though is removing the bloat
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hi. Could you tell me how you installed supersu after rooting with kingroot? Thanks
Well I have root and supersu installed but it won't update binary. Any help out there? Thanks
Hey everybody. I did it!! Just root with kingroot 4.5 and replace kinguser with super sume. Worked great. All kingroot stuff is gone!! Ive rebooted 3 times to make sure and all is good.
Well if anyone is interested in looking at the source code, lg support has downloads available for nearly every phone they've ever made.
http://opensource.lge.com/osList/list?m=Mc001&s=Sc002
The file for the LGL16C is on page 2. Every thing seems to be listed alphabetically so it's easy to locate.
I still have my lucky and actually use it often although I no longer have it activated.
@ cecnwv,
Thanks for the link. Using Ares 11 and got "IP banned for 6 hours,try again later" after dbl tppng yellow icon. I did something wrong. Not at my PC. (unfortunately)
Thanks for any enlightenment,
michaeltheclyde
Two 10a LGL16C Tracfones, one free (recon from Tf) and one new $14.95 @ eBay from Best Buy, rooted with everything that has Google in the name frozen (TB) but no image to restore. (twrp)
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Apache Thunder said:
Has anyone made a complete backup of their system apps using Titanium Backup? Being that one can't use fastboot/download mode (this phone has it locked out and a special USB cable is required) so my backup options were limited. I thought I did a full backup with Titanium Backup, but apparently lost it as I only found a small partial one on my PC.
Issue is I had uninstalled some bloatware and integrated updates for a few apps. But after factory resetting the phone it is behaving a bit odd. The notification bar doesn't really work anymore (apps still able to use sound/vibration to make a notification, but nothing appears in the notification bar) and I am unable to call the phone because it never rings and it immediately goes to voice mail. So the phone app is borked too.
Plus soft button to the right of the home button (I forget what it's called) doesn't bring up the app history anymore so I can't close background apps. (the volume buttons also don't really do anything anymore. Normally using them causes the volume bar for ringtone to appear and if using a media app, the volume bar for media audio comes up instead. But now nothing happens).
The phone is in a pretty broken state and even doing app updates from Play Store doesn't work anymore. Was gonna try and look around if someone has some app/data backup of the system apps installed. This is a TracFone branded phone and is currently running Android 4.4.2 (Kernel version 3.4.0+). Which is the last Android update they made for this phone.
Perhaps there's a single service/app that is responsible for notifications/volume bar that is borked. But I have no idea which system app is broken so a full app restore is my next best option.
The first thing wrong I noticed after resetting it was that the intial setup screen would return everytime I rebooted the phone. (only way i could get that to stop was freezing it in Titanium Backup). So maybe related to that app somehow. I don't recall ever uninstalling/merging update data for that perticular app though so it's probably a side effect of a different app going haywire.
EDIT:
Ok looks like I resolved the issue. I just removed the LGStartupWizard.apk then did a factory reset via Volume Down+Power button combo. It boots straight to home menu now and everything works. I guess the LG setup wizard thing got borked somehow. No more setup wizard but verious things like google account and whatnot can be configured manually via settings so no real loss.
All the missing things like the app history button, lock screen, notification bar, etc are now working as a result of resetting after removing LGSetupWizard.apk.
Click to expand...
Click to collapse
Awesome, this worked for me too, though the issue wasn't exactly the same. When I got the phone it had already been rooted with Kingo at some point and I noticed after resetting it that I had similar problems (it may have had the issues before the factory reset too, I just didn't notice one way or the other). Anyway, I was getting slightly different misbehavior. No recents key, yes, but also no response from the Home key. Pull-down notifications bar was mostly working, but with no visible notifications and I couldn't press the Setup "gear" in top right. My volume buttons and Play Store were fine, though, but I'd noticed that when I tried further factory resets (from the menu, not via hard reset) that it wasn't "really" resetting, as any downloaded files/etc. remained on the phone. I'd tried freezing LGSetupWizard already, but as you noted, that doesn't fix it for whatever reason. Deleting altogether does. Yay. I do wonder what the hell is happening during the root or reset that triggers this problem, though. It behaves as if Setup Wizard was just never completed, so you remain "locked out" of most of the same functions that are unavailable during setup normally. Oh well.
Anyway, as old ten-dollars-or-less type phones go, this isn't the worst I've ever used by a long shot. Heck, it's arguably better than a few other slightly bigger/newer/pricier crap-phones out there! (Looking at you, ZTE Legacy/Quest...) FWIW, I had "ripped" all of the APKs from /system/app and /priv-app for some reason back when I first got this thing, so if they'd be of use to anyone I'll be happy to upload all or individual files. Hell, if anyone can tell me how to do a full ROM dump I'd be happy to do that too, because there's definitely still no official stock image available online that I could find a trace of. (Granted, I don't know if there'd be any way to utilize a non-official backup image anyway or turn it into a flashable KDZ, but that's not my point...)
Thank you, I got my lucky rooted! I'm wondering if anyone ever found any custom ROMs or recoveries for this device. It seems like this was never popular for any of that, but thought I'd ask. Thanks.

After OTA Update on Unlocked US Settings Crashes

After performing the new OTA update for the Unlocked US version my settings just crashes. I have re-enabled packages disabled. I was also hiding the status bar and navigation bar using adb commands but I reverted back but still no luck. It allows me to open settings but when I click on anything aside from device maintenance it crashes over and over. Anyone have any ideas on how to fix this?
GallardosEggrollShop said:
After performing the new OTA update for the Unlocked US version my settings just crashes. I have re-enabled packages disabled. I was also hiding the status bar and navigation bar using adb commands but I reverted back but still no luck. It allows me to open settings but when I click on anything aside from device maintenance it crashes over and over. Anyone have any ideas on how to fix this?
Click to expand...
Click to collapse
I have the unlocked US version S8+ G955U1EU1 and received the update yesterday (or day before) and installed it. Everything is running well, I have not noticed any abnormality. Not sure if it makes any difference, I have not used adb commands for anything.
I had the same issue,system ui crashed.I was using substratum,with a few other theming apps.I had to do a factory reset,everything is fine now.Although the changelog for the update mentioned theming background colors,I see no options for that.
djmouse said:
I had the same issue,system ui crashed.I was using substratum,with a few other theming apps.I had to do a factory reset,everything is fine now.Although the changelog for the update mentioned theming background colors,I see no options for that.
Click to expand...
Click to collapse
Yup that was it. I had substratum installed and sfte rthe update things got screwy. I did a factory reset as well and everything is working fine now. Also for some reason I have even better battery life now which is strange but can't complain hahaha.
Sent from my SM-G955U1 using Tapatalk
You can uninstall the overlays from substratum. Go to overlay list and select them all and uninstall them. Then you'll go through the process of uninstalling the overlay apps. Reboot. Worked for me and I didn't have to factory reset lol
Saythis said:
You can uninstall the overlays from substratum. Go to overlay list and select them all and uninstall them. Then you'll go through the process of uninstalling the overlay apps. Reboot. Worked for me and I didn't have to factory reset lol
Click to expand...
Click to collapse
Yeah I went the nuclear option because it didn't click until later lol
Sent from my SM-G955U1 using Tapatalk

Categories

Resources