Ok so we all are annoyed about superuser app not remembering requested permissions. So i was just experimenting around and that part worked out for me Here is the solution:
First:Check If the superuser remembers granted and denied permissions to an app by launching a root app giving it root access. And relaunching it again if it shows a popup to show requests. If no then move to further step
Second Step: Download super su app(by the great chainfire) and check if it gives installation sucess. If no then move ahead
Third : Download Su update fixer from the Playstore
Fourth:Run the su update fixer app.If it asks for permission then grant it.Mostly it will force close. (Dont worry it should force close).Now if u observe on the device u might not see the super user app.Dont worry its natural.
Fifth:Now download superuser app from the market (mine is v3.1.3(46) ) try to get that one.After the download is completed run the app.
Sixth:Mostly it will force close.Reboot your device
Seventh: once the device is started. Run the superuser app.
Voila It will now remember all your permissions without fails
Incase it does not remember Use the super su app and when it prompts for the installation of binaries allow the superuser request
Supersu works flawlessly
NOTE:I am not responsible if any damage occurs to your device. I just shared it with you because it worked for me on CM9 CM10 and PAC roms
Adi1995 said:
Ok so we all are annoyed about superuser app not remembering requested permissions.
Click to expand...
Click to collapse
It solved for me, my set is Samsung Galaxy Nexus, Android 4.1.1, just root it recently via "Galaxy Nexus ToolKit".
However, the superuser will not remember, and keep asking.
Note: the superuser by ChainsDD, not install via play market, but install from "Galaxy Nexus ToolKit" (last update 21 Oct 2012) during root process.
SuperSU work great for me~
Related
Hello,
My Nook HD+ is currently running on verygreen's cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip. I did not make any other customization.
I tried installing an app called Quick Boot from Playstore which needs root access. However, I'm getting error "Superuser denied to QuickBoot". However, the root/superuser access is working fine with other apps like Titanium Backup, AdAway, ES Explorer, Terminal Emulator, etc.
Superuser Access - Automatic Response setting is set to "Prompt". Prompt does work for other apps but not for Quickboot. I just get a flash message that "Superuser denied to QuickBoot". I have also changed Automatic Response setting to "Allow" and tried, but even then I get the same error.
I downloaded the Superuser (by ChainsDD) app from Playstore and tried. I am getting the same error "Superuser denied to Superuser" for this app as well. Also, this app does not show me any App list with superuser access, I just get a blank screen.
I'd appreciate any suggestion to fix this issue.
Thanks in advance...
TheLabyrinth said:
Hello,
My Nook HD+ is currently running on verygreen's cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip. I did not make any other customization.
I tried installing an app called Quick Boot from Playstore which needs root access. However, I'm getting error "Superuser denied to QuickBoot". However, the root/superuser access is working fine with other apps like Titanium Backup, AdAway, ES Explorer, Terminal Emulator, etc.
Superuser Access - Automatic Response setting is set to "Prompt". Prompt does work for other apps but not for Quickboot. I just get a flash message that "Superuser denied to QuickBoot". I have also changed Automatic Response setting to "Allow" and tried, but even then I get the same error.
I downloaded the Superuser (by ChainsDD) app from Playstore and tried. I am getting the same error "Superuser denied to Superuser" for this app as well. Also, this app does not show me any App list with superuser access, I just get a blank screen.
I'd appreciate any suggestion to fix this issue.
Thanks in advance...
Click to expand...
Click to collapse
You are looking in settings at the superuser section? And Quick Boot is not listed in the apps or history?
Sent from my Nook HD+ running CM10.1 on emmc.
Superuser Denied to Quick Boot and Superuser (by ChainsDD) app from Playstore
leapinlar said:
You are looking in settings at the superuser section? And Quick Boot is not listed in the apps or history?
.
Click to expand...
Click to collapse
In Superuser section under Settings, Quickboot is showing as "Deny", Titanium Backup, AdAway is showing as "Allow". Log is showing the same. Also, the Superuser (by ChainsDD) app from Playstore is showing as "Deny" under superuser settings.
When I am trying to run the Quickboot app, every time I am getting a flash message for a second "Superuser denied to QuickBoot".
I'm not understanding why some apps are getting root access, some not. I tried clearing the app data and cache and re-installed the apps as well. But it did not help.
It would be really helpful if you please let me know a way to fix this issue.
TheLabyrinth said:
In Superuser section under Settings, Quickboot is showing as "Deny", Titanium Backup, AdAway is showing as "Allow". Log is showing the same. Also, the Superuser (by ChainsDD) app from Playstore is showing as "Deny" under superuser settings.
When I am trying to run the Quickboot app, every time I am getting a flash message for a second "Superuser denied to QuickBoot".
I'm not understanding why some apps are getting root access, some not. I tried clearing the app data and cache and re-installed the apps as well. But it did not help.
It would be really helpful if you please let me know a way to fix this issue.
Click to expand...
Click to collapse
It got denied because you did not respond quick enough when it asked the first time. Once denied, it stays that way until you somehow clear it. But I don't know how to clear it on this new CM10.1 setup. There is no superuser app, it is part of the operating system.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
It got denied because you did not respond quick enough when it asked the first time. Once denied, it stays that way until you somehow clear it. But I don't know how to clear it on this new CM10.1 setup. There is no superuser app, it is part of the operating system.
Click to expand...
Click to collapse
I am very sure that there was no prompt to grant Superuser access when I opened Quickboot for first time because I was waiting for the prompt to come up. But it never came.
Also, do you mean that I should not use any other Superuser App other than the one that came with the Operating System?
I have another question regarding the default Superuser App that came with OS. Why is there no option in settings to change "Deny/Allow" for an App? Is there a way around to enable the "Deny/Allow" option in the Superuser App Settings?
TheLabyrinth said:
I am very sure that there was no prompt to grant Superuser access when I opened Quickboot for first time because I was waiting for the prompt to come up. But it never came.
Also, do you mean that I should not use any other Superuser App other than the one that came with the Operating System?
I have another question regarding the default Superuser App that came with OS. Why is there no option in settings to change "Deny/Allow" for an App? Is there a way around to enable the "Deny/Allow" option in the Superuser App Settings?
Click to expand...
Click to collapse
Well, if it is showing denied, it got denied somehow.
I don't know much about this new superuser setup in CM10.1. You might try going to cyanogenmod's forum on their site. It is a generic issue that applies to all their devices so there may be some discussion on it.
Sent from my Nook HD+ running CM10.1 on emmc.
Can anybody please confirm whether they are getting the same "Superuser denied" issue with Quickboot? We will know if it is a generic issue with everyone or issue with my Nook only. If it is a generic issue, we can bring this to the notice of the developers. Quick Boot is available in Play store.
Also, if anyone can test the Superuser (by ChainsDD) app from Playstore.
TheLabyrinth said:
Can anybody please confirm whether they are getting the same "Superuser denied" issue with Quickboot? We will know if it is a generic issue with everyone or issue with my Nook only. If it is a generic issue, we can bring this to the notice of the developers. Quick Boot is available in Play store.
Also, if anyone can test the Superuser (by ChainsDD) app from Playstore.
Click to expand...
Click to collapse
Well, I can tell you I have no issue with Quick Boot and the verygreen 7/08 emmc ROM.
And I did have a problem with an old version of Root Browser not activating superuser. It was not denied, it just did not recognize the CM superuser. So I installed ChainsDD superuser and it recognized it and got activated. It was listed in the CM superuser as allowed then. Then I could uninstall ChainsDD superuser and Root Browser continued to work fine.
Sent from my Nook HD+ running CM10.1 on emmc.
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,
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.
Hey guys, so I'm trying to install BusyBox on my new Nexus 6 running stock 6.0, rooted. When I try to install via Stericson's installer I got from the Play store, I get:
"We could not verify the integrity of the binary selected..." flashes for a moment, then:
"BusyBox installer was not allowed root access. This may be an issue with Superuser, open Superuser and make sure that you are allowing root access. This application will not work without root access."
I've made sure that the app is allowed root access, and have also tried deleting it from SuperSu so it would prompt me and I could grant it access again, but still the same issue. I'm not sure what the deal is, it seems like I could be having root issues? I appear to have root since I am able to use TiBu, but something seems funky. For example usually when I open FKUpdater it says "FKUpdater has been granted super user access..." and then "Unable to acquire ROOT access." Other times it only says "Unable to acquire ROOT access." I haven't tried flashing a kernel with it because I don't want to at the moment while I figure this other issue out, so I'm not sure if it's falsely reporting the root error.
So, I looked into things further and it seems like I may have some sort of permissions issue. I tried using JRummy's BusyBox installer, but that fails also and just tells me to try installing a different version of BusyBox. It also includes a script for fixing permissions, and when I run it I get "error: only position independent executables (PIE) are supported" and "/data/user/0/com.crummy.busybox.installer/files/temp.sh[118]: sync: can't be executed: permission denied."
Permissions for /data/user/0/com.crummy.busybox.installer are set to drwxr-x--x, as is /system. Also /system is only showing 58 MB free but I don't think that's a problem...
Any ideas? I'm totally stumped...
set your SElinux to be permissive(via app or terminal command)
I am trying to run screen2auto on android auto and i need supersu ti verify that root permissions ar granted to thr various apps, so i installed supersu but it asks me for an update that doesn't happen automatically. I tried to use the apps eithout updating supersu, even granting permissions to rhe apps, these don't work in particular just activated super su Aa Io tweaker no longer works and shows a white screen. I hope that updating supersu solves the problem. Can someone help me?
Dude what are you saying? Did you ever have root?