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.
Related
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~
After rooting my KFHD with QemuRoot (which was successful according to Qemu) I tried running Root Check Pro.
The message I get.
Root acces is not properly configured or was not granted.
Detailed Results:
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - versions - 0.96 - is installed!
System File Properties for Root Access:
Standard Location
Check command: Is -i /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permission restricted and denied access.
Click to expand...
Click to collapse
What does this mean exactly? That I'm not actually rooted, or not rooted correctly?
Solved! I'll post the solution soon!
Please do, I also have this problem though I think I used a different root method. I know I am rooted as I have Superuser and I am using Google Play now with other customizations but apps like Titanium Backup are not working because of the root thing.
cull3n said:
After rooting my KFHD with QemuRoot (which was successful according to Qemu) I tried running Root Check Pro.
The message I get.
What does this mean exactly? That I'm not actually rooted, or not rooted correctly?
Click to expand...
Click to collapse
In the most simple way to do it, open up the app listing and tap on Superuser to initialize the daemon. That's it. Once the daemon starts, root access will manifest in those little boxes with the permission.
seokhun said:
In the most simple way to do it, open up the app listing and tap on Superuser to initialize the daemon. That's it. Once the daemon starts, root access will manifest in those little boxes with the permission.
Click to expand...
Click to collapse
Please excuse my noobness, but do you mean go to settings then applications? Thx In. Advance
Hello all,
A friend gave me his Droid 3 which was successfully rooted (Superuser version 3.13 is installed). When I look at the log I can see many past "Allowed" entries. However, I attempted to install Safestrap (version 3.05), and it was denied Superuser access (can see the denial in the log). I then attempted to grant other apps Superuser permissions and I get a "[App Name] has been denied Superuser permissions" message (and it shows "Denied" in the Superuser Log).
The really odd things are that (1) it doesn't prompt to allow or deny (despite the setting saying to prompt), and (2) if I select Superuser funcitons within the Superuser App, it will allow them. For example, if I select "temp unroot", it says "Superuser has been granted Superuser permissions".
I know I can SBF the phone and start over, but there are lots of paid Apps on the phone and I just assume try to work on getting Superuser working again if it's possible.
Please help!
Try setting to always allow
Sent from my DROIDX using XDA Free mobile app
Solved! Ok, with the device connected to my computer and playing around in adb, I noticed that the permissions for the SU binary were all goofed up. So I issued the command: adb shell "chmod 6755 /system/bin/su" and that solved the problem. Hope this helps someone else.
Shadow: Thank you sir for your reply. I should have mentioned in my original that I did try "always allow" in addition to prompting and it didn't make a difference. However, I solved it by changing the su binary's permissions (see above). Thanks again for takinig the time to reply.
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,
Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).
have you enabled Developer Options?
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".
Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse