SuperSU Not saving settings - SuperSU

Hi
I have just rooted a S6 Edge running Nougat and installed SuperSU. Can someone please explain to me why when I make changes to SuperSU settings it all gets reset if I change the sim or even restart the device?
Its driving me insane!!!
Apologies if I have posted this in the wrong place.
Thanks

I just ran into the same problem with a Nexus 5x. Mine wouldn't even remember the settings after I closed the app. I went in to the settings and did the cleanup for reinstall and then​ installed again from the play store. It asked to install binaries, which was successful, and then it started remembering settings. Seems like an obvious thing to try first and maybe you already have but I hope it works out for you.

Related

Root - Superuser crashes / gets terminated

Hello community,
I was a reader of the site for long time. So I decided to register here, because I have some troubles with my new rooted Xperia Z.
Unfortunately all apps with root permissions are working a bit strange. Root Checker and Root Explorer are working after several crashes of Superuser. By opening these apps, I always get a message prompt, that Superuser has been terminated.
SuperSU doesn't work and quits while trying to install the in-app update.
I also changed the owner and the chmod permissions for these apps, but nothing changed at all.
It seems to me, that something went wrong during the root procedure. I completely followed the guide written by DooMLoRD(http://forum.xda-developers.com/showthread.php?t=2186368). The only different part was, that the service menu opened automatically. After that, I fixed the NFC issue. Hopefully, I don't have to reset the device.
Firmware build: 10.1.A.1.434
Do you have any suggestions for me?
Thanks a lot!
Fabowski said:
Hello community,
I was a reader of the site for long time. So I decided to register here, because I have some troubles with my new rooted Xperia Z.
Unfortunately all apps with root permissions are working a bit strange. Root Checker and Root Explorer are working after several crashes of Superuser. By opening these apps, I always get a message prompt, that Superuser has been terminated.
SuperSU doesn't work and quits while trying to install the in-app update.
I also changed the owner and the chmod permissions for these apps, but nothing changed at all.
It seems to me, that something went wrong during the root procedure. I completely followed the guide written by DooMLoRD(http://forum.xda-developers.com/showthread.php?t=2186368). The only different part was, that the service menu opened automatically. After that, I fixed the NFC issue. Hopefully, I don't have to reset the device.
Firmware build: 10.1.A.1.434
Do you have any suggestions for me?
Thanks a lot!
Click to expand...
Click to collapse
Try re-rooting the device
I already did a second try. Nothing changed, I've only got the message, that superuser app has been already installed.
Or do you mean, I have to reset the device and re-reoot it?
Any more suggestions here?
Sorry guys, I'm not a fan of bumping this topic, but before I try it with a factory reset, does anybody has a suggestion on this problem?

[Q]Home button/Notifications/Quicksett. not working after activating Xposed framework

Hi,
A few days ago I flashed to Carbon ROM 4.4.4 from Novafusion.
Everything went smoothly until I tried to install/activate Xposed framework. (Without any modules active at that moment)
After the reboot, al my settings were set to default, the home button registers touches but does not redirect me to the homepage, the quick settings button doesn't react and my notification panel stays empty, whether there are notifications or not.
I performed a factory reset via TWRP and everything was back to normal. But Xposed framework had to be activated again. Tried it a second time, same results. So, is there a way to have a factory reset while keeping Xposed framework activated? Knowing never being able to use Xposed again would make me very very sad.
I looked into other threads concerning similar issues, but the only solution would be a factory reset, and that doesn't help me any further. Also, I haven't found a similar case wherein the issue was caused by activating Xposed framework.
Any help would be kindly appreciated.
coeurdefleur said:
Hi,
A few days ago I flashed to Carbon ROM 4.4.4 from Novafusion.
Everything went smoothly until I tried to install/activate Xposed framework. (Without any modules active at that moment)
After the reboot, al my settings were set to default, the home button registers touches but does not redirect me to the homepage, the quick settings button doesn't react and my notification panel stays empty, whether there are notifications or not.
I performed a factory reset via TWRP and everything was back to normal. But Xposed framework had to be activated again. Tried it a second time, same results. So, is there a way to have a factory reset while keeping Xposed framework activated? Knowing never being able to use Xposed again would make me very very sad.
I looked into other threads concerning similar issues, but the only solution would be a factory reset, and that doesn't help me any further. Also, I haven't found a similar case wherein the issue was caused by activating Xposed framework.
Any help would be kindly appreciated.
Click to expand...
Click to collapse
Are you using ART? Because Xposed isn't compatible with it, yet.

[Q] Issue with Root Duration

Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Sorry I don't have a solution but I just wanted to bump this thread because I'm having the same issues as you. Wakelock detector also gets stuck on loading screen and supersu fails to open.
vahx129 said:
Hey guys, I didn't see anyone ask this question explicitly but if it has been stickied somewhere and I just overlooked it I apologize.
Basically I've flashed several different root images using Mofo root and they work for the most part minus one small aspect. After some duration of time (I'm not sure exactly how long but maybe from an hour to a few hours), root apps will basically stop functioning. If I go into supersu, I just get a loading circle that never gets anywhere. I've tried force closing it and disabling/reenabling superuser but that hasn't worked. Some apps continue to function (Gravitybox custom tiles, WiFi Tether, Seeder) but others do not start up properly (TiBackup for example gets stuck at the loading screen where it says asking for root privileges and tasker secure setting profiles return an error). Only a hard reboot will properly restore root but then the same issue occurs where after a while I have to continue to hard reboot once root stops functioning.
Any help would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I also had the same issue. I am using the image with busy box and Xposed framework installed. After a an hour or so super user said that the binary was not installed, and most of my root apps stopped working. Root checker said my Turbo was not rooted, though gravity box and a few other Xposed modules continued to work. I rebooted the phone, but had the same problem. I turned notifications for the supersu app back on, and after about a minute it said the binary had to be updated, and I had root again. I'm not sure what is going on, but I will come back if I find anything
I'm not having any issues. I would reboot the phone into recovery and wipe the cache there. Hope that helps.
Glad I saw this thread...I'm having the exact same issue!
A hard reboot will solve the problem every time...but its quite annoying...
I'm going to try a factory reset and see if that helps
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Seems to have resolved itself
I just wanted to mention that between clearing the cache and flashing a different rooted image this issue appears to have resolved itself.
I will update after some time to see if this fix maintains or if anything else pops up. Thanks for the suggestions!
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
What cache did you clear? I tried to clear the cache from the recovery, but my phone freezes and I have to reboot. Then I loose root a while later.
ahaynes42 said:
Clearing the cache seems to have solved this for me. I haven't lost root in a few days.
Click to expand...
Click to collapse
I cleared cache in recovery...didn't help...gonna have to try a factory reset

Unable to unlock my lock screen after installing xpoosed.

Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk

A71 Data & Root Issues

Hello,
The last couple of months and completely out of no where my 4g data randomly stops working. The status bar icon shows that it's stuck on upload and won't download any data. The only way I've found to fix it outside of restarting the phone is to change the cell band type from auto to wcdma then back.
Anyone have any ideas on how to fix this?
Second issue is with Magisk and I know this is for Samsung but I figure why not ask anyway. As of yesterday after a reboot I lost root. Magisk apps shows I need to install magisk and install the app even though I'm in the app. Also a bunch of my apps are acting like I've never uzed them before and they need to be setup again. I haven't installed any updates so I'm not sure what caused it.
I've tried completely uninstalling Magisk and reinstall and that didn't do anything. The install went through fine but after launching the app it still says no root.
Any ideas?
Thanks
Hi, I think it has been updated and Magisk is useless due to new layers of security. I guess we'll wait until a new rom is made for the new update, including stock. I don't know if Magisk can release a new version and overcome this.
Thanks.
Reflashing the custom firmware then also Reflashing Magisk did get it working for me again.
I've since updated to the newest firmware, flashed OneOS and Magisk and it's been working fine until a little while ago when Magisk randomly shows as not installed again after a reboot.
I take it no one else has had this issue still?
Thanks

Categories

Resources