Related
hey guys i have one problem with supersu.
i installed clean master and do cleaning **** and startup cleaning things and after reboot all apps that have granted root permission( foldermount, gmd gestures, lightflow, etc), these apps shows no toast popup after boot and to make them grant permissions i have to open them. Same thing when i installed boot manager and did not do anything but boot and again no supersu toast popups about root permissions after boot.
is there a way to keep the root grants after the boot? ( i have checked default acces to grant in supersu app)
I'm having problems with clean master working with SuperSu too.
clean master is so powerfull that disables supersu permissions.
They probably change some file permissions that SuperSU frowns at.
Chainfire said:
They probably change some file permissions that SuperSU frowns at.
Click to expand...
Click to collapse
i want to maintain supersu permissions after every boot no matter what. is there some option in supersu to be activated for that?
i'm on note 3 rooted with stock tw.
''enable supersu during boot''
please explain to me for what is this option
thx :good:
bump
dancapitan said:
''enable supersu during boot''
please explain to me for what is this option
thx :good:
Click to expand...
Click to collapse
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
3c said:
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
Click to expand...
Click to collapse
You should turn this into a proper bug report in the proper thead (either the beta or its own new thread) with all the useful information you think may be relevant. There is no email support, all support is here.
The option itself is for apps that run before Android is fully up and running, or su from adb shell during a bootloop, etc. I thould not influence apps running su from bootcomplete receivers, and if it does, then that needs to be investigated.
Is there currently any way to enable this feature via ADB on a boot looped phone? I really wish I would have known about this! I wouldn't be stuck where I'm at if I had only checked this option. Device is stuck at LG logo, no download or recovery, but has access to ADB. SU was installed, but I don't have root via ADB since the phone isn't finished booting...thus I'm not able to copy over the proper system.img or change the recovery/laf. Dang!
I have the problem too, when I install Fake Wifi, the automatic SuperSU granted is not working. Please help some advance. Thank's.
Hey guys why root required apps request for root access after installing super su
I have the same problem, have to add a task in tasker, auto open supersu and root granted apps once after boot,
Quick question: why does my Privacy Guard in CM12.1. not show any root access settings at all?
Hi, just bought Amazon Fire Tablet 7", updated to 5.1.1., and installed CM12.1. with SuperSU. Everything worked. However, I decided to switch to CM's built-in root enabler (because it's open-source), so I ditched SuperSU through SuperSU's "Switch superuser apps" feature in SuperSU settings. SuperSU was automatically uninstalled, then I enabled the root privileges through Developer Options and this method too worked like a charm.
However, my Privacy Guard does not show the root access settings, so I have no control whatsoever on which application can or cannot have the root privileges, except turning root off altogether. A few root applications, e.g. AdAway, are working without problem but I was never prompted to grant them the root access in the first place. I've installed new applications, such as Greenify, but it too can access to the root without me explicitly granting the permission. I've also checked if Privacy Guard works at all, and it does, when I disabled locations service, I was prompted to enable it.
I did a factory reset within CM12.1. but to no avail. Any ideas or suggestions? If possible I'd like to get this sorted and try every solution before reverting back to SuperSU. Cheers.
himgil said:
Quick question: why does my Privacy Guard in CM12.1. not show any root access settings at all?
Hi, just bought Amazon Fire Tablet 7", updated to 5.1.1., and installed CM12.1. with SuperSU. Everything worked. However, I decided to switch to CM's built-in root enabler (because it's open-source), so I ditched SuperSU through SuperSU's "Switch superuser apps" feature in SuperSU settings. SuperSU was automatically uninstalled, then I enabled the root privileges through Developer Options and this method too worked like a charm.
However, my Privacy Guard does not show the root access settings, so I have no control whatsoever on which application can or cannot have the root privileges, except turning root off altogether. A few root applications, e.g. AdAway, are working without problem but I was never prompted to grant them the root access in the first place. I've installed new applications, such as Greenify, but it too can access to the root without me explicitly granting the permission. I've also checked if Privacy Guard works at all, and it does, when I disabled locations service, I was prompted to enable it.
I did a factory reset within CM12.1. but to no avail. Any ideas or suggestions? If possible I'd like to get this sorted and try every solution before reverting back to SuperSU. Cheers.
Click to expand...
Click to collapse
Don't have a definitive answer; there are various bug reports from users who have dabbled with SuperSU and the integrated CM12.1 root manager. Thoughts:
- reinstall SuperSU as it is well respected and will likely restore app level access permissions with minimal effort/fuss/risk
- if you prefer to stick with the integrated root manager I would suggest clean flashing CM12.1
- however, since your devices bootloader is likely > 5.0.1 you'll need to use a tool like FlashFire which carries increased risk (albeit small)
- developers tend to test/validate rom updates with SuperSU - a possible consideration moving forward
Davey126 said:
there are various bug reports from users who have dabbled with SuperSU and the integrated CM12.1 root manager.
Click to expand...
Click to collapse
Exactly what I am thinking; something is probably broken along the switching process. Cheers anyway.
Trying to use Secure Tools to disable volume warning Samsung S5 running Marshmallow. I installed everything and ran adb command. No error, but when I search for Secure Tools it says Not Installed. Then I read this doesn't work on Marshmallow?
My phone is NOT rooted. Any help would be much appreciated.
Thanks - Frankie
Frankie-o said:
Trying to use Secure Tools to disable volume warning Samsung S5 running Marshmallow. I installed everything and ran adb command. No error, but when I search for Secure Tools it says Not Installed. Then I read this doesn't work on Marshmallow?
My phone is NOT rooted. Any help would be much appreciated.
Thanks - Frankie
Click to expand...
Click to collapse
I'm confused. What app are you referring to? "AutoTool's secure settings" or the app "Secure settings" or something else that I'm missing?
TASKER and AUTO TOOLS
I guess I forgot to mention that I'm user Tasker to do this... Thank you.
Be very specific what you are using and what you are trying.
Trying to disable high volume warning on Samsung S5
Using Tasker Auto Tools to run a command on my phone that will allow me to override the Volume High Warning on the Samsung S5 phone. It's supposed to enable WRITE SECURE SETTINGS with this command - and the command runs fine but it's not working for me. But when I go back to the app and look for Secure Settings, it's not there.
adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS
Auto tools is a plugin to tasker.
The "adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS" is one of two steps required to give the type of system level OS access this tool needs. The first thing that should be done is to enable "allow modify system settings" for AutoTools.
From the AutoTools Secure Settings page:
To use this, AutoTools needs to be granted permission to change secure settings on your device
If you're on Android 6 or above click here to grant AutoTools the first Settings permission
Then follow these steps to grant AutoTools the Secure Settings permission:
Enable Developer Mode: Go to Android Settings -> About Phone and look for the Build Number option. Touch it multiple times until developer mode is enabled.
Enable USB Debugging: Go to Android Settings -> and look for the Developer Options option. In there, enable the USB debugging option.
Install ADB on your PC: Check here for a quick way to do it.
Connect device to PC: Connect your device to a PC and look on your phone. A prompt should show up asking you to allow your phone to be debugged by your PC. Accept this.
Grant permission: Open a command line on your PC and write
adb shell pm grant com.joaomgcd.autotools android.permission.WRITE_SECURE_SETTINGS
Congratulations, AutoTools should now be able to use the "Secure Settings" action!
Click to expand...
Click to collapse
Once those things are done ( I typically reboot for no good reason ☺ ), then go to tasker, add an action in a task, then: plugin -> Auto tools -> secure settings (scroll down the list) you'll end up in a screen where you can configure the AutoTools secure settings action.
WOW! I think I did it.. I just hope I can do it again - this was my "test" phone. I think I was messed up by doing the "search" for secure settings because it said it wasn't installed.. Yet I had looked for the secure settings option and didn't find before - although I had already done all the steps. Somehow I got on to a screen that said the app (I forget the exact words) didn't have permission to change the settings, and to press NO if I wanted to allow the permissions - and I pressed no! I had already created the task to disable the warning - but it's been so long, I'm not sure how I did that - but the bottom line is I think it's working.. I had found several sites that said this wouldn't work with Marshmallow unless the phone was rooted, and my phones are not rooted.. so that makes me skeptical, but I did a reboot, and the warning didn't come back. Thanks a ton for your help.. Let's hope I can re-create on the phone that really needs it.
In case this is found by someone else, many of those "how to use secure settings" posts from lollipop and marshmallow predate the (awareness of the) approach used by AutoTools. People spent a lot of effort trying to force an unsupported, outdated app (the original secure settings) to work in a systemless root environment.
I'm sad to say this did NOT work on my test phone.. It looked like it did, but it didn't.
Hey guys,
I am editing a stock rom for a MT6570 based device. I have patched the boot image and rooted the device successfully. I can add MagiskManager in the /userdata partition so that it is installed on first boot after flash, but I still have to manually configure settings for su before my apps work.
Is there a way to grant my apps su permission or, worst cast, automatically grant su permission on first boot? I would also like to turn off notifications.
Thanks
Chris
chrisfraser said:
Hey guys,
I am editing a stock rom for a MT6570 based device. I have patched the boot image and rooted the device successfully. I can add MagiskManager in the /userdata partition so that it is installed on first boot after flash, but I still have to manually configure settings for su before my apps work.
Is there a way to grant my apps su permission or, worst cast, automatically grant su permission on first boot? I would also like to turn off notifications.
Thanks
Chris
Click to expand...
Click to collapse
That sounds like a bad idea.
If your ROM requires root for something extra to function, you have plenty of ways to run your code as root without involving Magisk.
If you really want to preconfigure Magisk to allow root for some apps, you can always alter its settings directly. The su rights are held in a SQLite db. Or patch Magisk for your ROM.
You'd be on your own supporting that however.
Like I said, if the default action is prompt, an app seeks root access and there is no prompt to grant it. If I change to grant as default, everything works. Root Checker, for instance, will fail to detect root in prompt mode but does so in grant mode. Same for Root Browser and, most importantly, Xposed.
I've tried reinstalling SuperSU. Didn't help. I have systemless root on a Moto X Pure and SuperSU 2.82.
I really don't want to leave it with grant as the default action. Not safe. I've been able to find a few other posts with a similar problem but they don't lead to solutions. This is a new behavior. Prompt used to work. About a week ago, I installed the latest version of Sensible Android Auto in Xposed. It worked twice and then stopped. My guess is that is the time when SuperSU stopped granting root. Everything that needs root can get root but ONLY if root is granted automatically to anything that asks for it.
Just rooted my Kyocera Event and deduced it to have the same problem. SuperSU 2.8.2 was not providing prompts and thus not granting root access, however changing to grant default did provide root. I tried installing SuperSU 2.7.9 rc4 but had the same result. I'm now just waiting for a definitive fix while looking for an alternative solution.