Supersu auto update failed on android 7.1.2 bought eith root permissions but without twrp and cwm. Help me please - SuperSU

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?

Related

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,

Bluestacks , cant update supersu- su binaries.

I have been using a rooted bluestack in windows.
But it app comes with pre rooted with SUPER USER app.
when tried to use lucky patcher, it said to install SUPERSU
so i installed from playstore and i granded root access for SUPERSU via SUPERUSER
after this, SUPERSU suggested to remove SUPERUSER. so i uninstalled via SUPERSU
problem starts aftr this. now i cant update SU binaries from SUPERSU
so now i have no root access.
PLEASE HELP
same problem

[Q] SuperSU issues after deodexing stock ROM

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.

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

SuperSU no longer prompting for root access

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.

Categories

Resources