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,
Related
Hi Guys, I'm having some issues with SuperSU and was hoping someone might know what is wrong or what I could check.
I recently deodexed my OG2 stock rom so that I could use arter97's port of the exposed frameworks. I used the following guide, which worked great by the way:
http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596
The only issue is the SuperSU no longer prompts me when apps request root permission. I verified all this with root checker. With SuperSU set to prompt, apps just hang waiting for root which is never granted because I'm not getting the pop-up. However, if I set SuperSU to grant all root requests by default, everything works properly.
Has anyone ever seen something similar to this before? I'd love to get it working properly again. Kind of nervous about having SuperSU set to grant root by default.
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.
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.
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
Hi all!
I might be asking a stupid question, so forgive me if I do.
The situation is the following... I have a TVBOX Q96 HOME 4K (cheap Chinese one based on RK3229) that is pre-rooted. All applications using root work fine. However, there is no "superuser" manager installed on it in order to disallow certain apps to gain root access. In the past I already had a similar situation with some other box and when I installed SuperSU apk the device hasn't boot anymore. I that case I got a stock firmware and could unbrick it, but now I can't find any ROM for this device in order to play with it.
So, the question is... is it possible to install Magisk Manager in order to manage access to the built-in su? Older version I tried correctly identify the device as rooted (with SuperSU 2.76), but do not offer me a Superuser menu where I could manage access to the su of the apps. Neither I get a prompt when an app is requesting access to su.
Any solution to my problem?
No, you will not be able to use the Magisk Manager to manage superuser access for SuperSU.
Any idea what might cause the device to not boot anymore after installing SuperSU.apk?
I compared the installed su binary with the one from chainfire's UPDATE-SuperSU-v2.76-20160630161323.zip (arm7), and they are identical. What does installing an apk alone to the system beside managing the access for the apps?
I have to admit I don't know exactly what happens "behind the scene".
I have absolutely no idea why installing the SuperSU apk would cause your device not to boot... Sorry.
Edit: Wait... You write "installing an apk alone to the system". You're not installing it as a regular app, but to the /system partition? If so, that's what might be causing issues.
Sorry to mislead you... I wrongly expressed myself.
I'm not installing it as a system app - I have installed it (on previous box) as an ordinary user app and as I said the system couldn't boot anymore afterwards (I had to reflash the ROM to unbrick it).
BTW... this is a known issue with these Chinese TVBOXes. There are couple of posts also here in XDA about it and nobody knows AFAIK what is the root cause.