Database Develop

SuperSu not granting automatic permissions anymore

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,

Confused and frustrated with this "SuperSU" thing

Why are there 3 different versions of this app on play store and which one do I need and why is the one on my phone unable to be uninstalled and why can't I click the "grant access" pop-up so I can use my apps? And why does the SuperSU update app say there is no supersu even installed on my phone?
Sent from my HTC One_M8 using Tapatalk

juntjoo said:
Why are there 3 different versions of this app on play store and which one do I need and why is the one on my phone unable to be uninstalled and why can't I click the "grant access" pop-up so I can use my apps? And why does the SuperSU update app say there is no supersu even installed on my phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You have to download the one that says "SuperSU" by @Chainfire. There is also a license file by Coding Code, to which @Chainfire is handing over the reins of SuperSU. SuperSU cannot be uninstalled from the stick Android package manager due to its non ability to uninstall system apps. The dialog not responding is caused by the "Enable Tapjacking Protection" option. Just disable it and you should be good to go. If it says anything like that, it WILL also show you an option to update the su binary. Just select the normal (or TWRP/CWM if you prefer that) and your device will reboot and all your problems.
Sent from a Cool Phone stuck with crappy KingUser

SuperSU in CM13 and CM13 based ROMs

Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.

Squall88uk said:
Is there any way to use SuperSU in CM13 or CM13 based roms such as Resurrection Remix? In particular on a Nexus 6P?
I ask because I have been using RR for quite some time now but until recently never really noticed the limitations of CM's privacy guard. SuperSU pro has always seemed like a better implementation of a Root management app to me when I've used it in the past on previous devices.
I had considered just disabling root access from the setting in developer options and then updating the binary from the SuperSU app via TWRP and hoping that SuperSU would take over root management after that but I have read that a few people have bricked/bootlooped their devices after doing that and I don't want to have to deal with fixing that.
Many thanks in advance for any help you can provide.
Click to expand...
Click to collapse
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

Ibuprophen said:
After disabling the root option within the Developer Options, when you open SuperSU and go to the Settings, do you leave the option for "Respect CM root settings" unchecked?
With CM/LOS, when you disable the root option, in SuperSU, you need to keep the "Respect CM root settings" unchecked or SuperSU will default the root to Disabled.
Many individuals don't know that.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs

Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I am in the same boat. I am using the the latest RR FROM which is awesome, but I'm not wanting to use magical. Have always used super SU and stick Mount for my next SD. Would like to know the process for disabling manual and cm/Los root mgmt. To use Super SU. I can't use stick Mount with root explorer without super SU. WHEN I try to update binary it fails and if I try to flash in recovery, I get stuck in boot loop and have to restore backup.

Having a similiar problem on Galaxy S2 with RR 5.8.2 - installed SeperSu and it fails to update its binary when I choose 'normal'. Tried Cwm/Twrp option on a stock rom once and the phone got softbricked. Converting SuperSu to system app doesn't help.
---------- Post added at 05:05 AM ---------- Previous post was at 04:48 AM ----------
Squall88uk said:
I don't see that option at all after installing the SuperSU app. I have SuperSU pro too in case it makes a difference.
When I load SuperSU it keeps asking me to update the su binary through TWRP but my concern is that if I do this it will lead to bricking/bootlooping my Nexus since I already have CMs su binary installed as part of CM13/RR.
Do I need to perform the update before I can see the option? Also will it cause bootlooping if I replace CMs su binary with SuperSUs?
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
No such option appears in SuperSu after disabling root access in dev options here also.

There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***

Ibuprophen said:
There was a time a while ago that I had asked something similar to to one of the CyanogenMod Team Developers.
I was told that when the Superuser option (in the Developer Options) is set to disabled, that means that the CyanogenMod systems Superuser access is left open. When one of the other options are set, that means that the CyanogenMod system is set to manage Superuser access that is seen by the new access to the Manage Root Access option below it.
So in short, disabled means root access is left open and CyanogenMod doesn't manage it.
If you use another root management app, like SuperSU, and leave the Root Access on disabled, then SuperSU takes on managing Root Access.
I've never had a problem with SuperSU and always left the Root Access disabled.
I hope i had explained it okay...
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
Click to expand...
Click to collapse
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?

kikot said:
Disabled Root access in developer options, rebooted phone and started Supersu, it tries ro update its binaries and fsils again. Then I look for the "respect CM root settings" option but don't see it.
Some people are having success flashing the Supersu.zip through TWRP but isn't there a risk of replacing the RR bundled recovery and ending in bootloop? Is it possible to flash TWRP zip from RR recovery without causing more issues?
Click to expand...
Click to collapse
I attached an image of where in SuperSU the setting is but, I leave it unchecked...
Try flashing the SuperSU zip since flashing it also installs the binaries too.

Issue with SuperSU app - prompt mode

hi,
I rooted my Yotaphone 2 (MM 6.0.1) with SuperSU (2.79 SR3, systemless mode) from TWRP.
If I set SuperSU app in mode "grant", everything works correctly, all apps receive root permission (root explorer, root checker, etc..).
But if I set SuperSU app in mode "prompt", no prompt appears and the application requiring root access hangs waiting or says that there is no root; and the list of apps on SuperSU remains empty.
What I already tried without success:
re-install SuperSU from scratch (using the options for clean / reinstall in the application)
reinstall SuperSU (using UnSU.zip to clean current installation from TWRP)
clean Delvik/Cache
install SuperSU 2.79 stable
convert SuperSU app to system app
use other apps to control root
try SuperSU 2.79 System mode
In all cases I still have the same issue (except with SuperSU System mode, in which case I have bootloop).
Do you have any clue on how to solve the issue?

I'd be interested to know what might be causing that. That happened when we root our Samsung Galaxy S7 (G930P) phone. But there have been scripts out for tweaks and such and along the way SuperSU will start promoting. But would love to know what would cause the prompts to not appear.
I thought it was just our phones trying to get root the weird way we have to do it. Interesting to know others are running into the same sort of glitch (?) On other hardware.
Sent from my SM-G930P using Tapatalk

Cannot find Supersu tool in Settings menu

I cant find supersu in settings..im running on cm11s on OPO.
But im getting root access. When i search in settings, it shows a superuser tool. bt i cant access it through the settings.
plz give me your valuable points..screen shorts are attached below for ur clarification. please help me..

cjl bny said:
I cant find supersu in settings..im running on cm11s on OPO.
But im getting root access.....
Click to expand...
Click to collapse
Suggestion: uninstall su - reboot - reinstall su.
Go to the play store and select superSu. Hopefully you see the Uninstall button.

I tried to reinstall supersu many times. does not appear in the menu and does not have an open button in settings.
Yes I have verified I have root access. Using Android x86 7.1.2
How do I run this app?