Cannot find Supersu tool in Settings menu - SuperSU

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?

Related

Root acces not working on cm9 help

Hi everyone I just bought an HP touchpad from Craigslist and it was already dual boot for cm9 and webos. I thought that once you had cm9 you could have root access if you turn it on in the settings . I did that but still no root access not working . I've looked for an answer on how to re-root it but I didn't find it .. I would love your help.. so I can do the hulu fix
if you dont have superuser app in your applications then redownload it from the google play store app.
I do have super user but it denies all apps and when I run root checker it sais that its not rooted. I can see the log and everything. I turned root on and off from the settings but nothing.
kipster3001 said:
Hi everyone I just bought an HP touchpad from Craigslist and it was already dual boot for cm9 and webos. I thought that once you had cm9 you could have root access if you turn it on in the settings . I did that but still no root access not working . I've looked for an answer on how to re-root it but I didn't find it .. I would love your help.. so I can do the hulu fix
Click to expand...
Click to collapse
In webos, enable debugging, there's a code you type in, that gets you root.
Look around the webOS nation forum, there are good tutorials there that will help you out.
chicle_11 said:
In webos, enable debugging, there's a code you type in, that gets you root.
Look around the webOS nation forum, there are good tutorials there that will help you out.
Click to expand...
Click to collapse
Will it then let me have root access when I boot cm9 . I know the code is webos20090606.
Let me try it..
kipster3001 said:
Will it then let me have root access when I boot cm9 . I know the code is webos20090606.
Let me try it..
Click to expand...
Click to collapse
It should. It did for me. And that is the code.
chicle_11 said:
It should. It did for me. And that is the code.
Click to expand...
Click to collapse
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in android.
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Just flash the first zip in the post above to get root in Android
Enabling Developer Mode in webOS will have no effect on Android Root Access.
Make sure you go to CM Settings and make sure for Developer Options, Root Access is set to Apps and ADB
Also open the Super User app and look at the "Default Action" property and settings and make sure it isn't set to deny.
I'm about to go try this thank you
haxin said:
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in andro
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Click to expand...
Click to collapse
When I try to flash the zips it said it can't open install aborted
kipster3001 said:
I'm about to go try this thank you
Click to expand...
Click to collapse
haxin said:
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in android.
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Click to expand...
Click to collapse
kipster3001 said:
I'm about to go try this thank you
Click to expand...
Click to collapse
I just downloaded the zip files and there is something wrong with them. I can't open them. Either way, why don't you go into the Google Play Store on your Touchpad and then uninstall the SuperUser app. Then re-install it. After that double check to make sure that you have latest su binaries.

[Q] problem whit root

hello
i root me dvice whit this Guide: How to Root the HTC One (International, Sprint, AT&T, T-Mobile) on youtube
and when i open the su app it say
"there is no su binary installed and supersu cannot install it. this is a problem!"
help me pls
have you flashed the root file in the recovery?
yonatan_brach said:
hello
i root me dvice whit this Guide: How to Root the HTC One (International, Sprint, AT&T, T-Mobile) on youtube
and when i open the su app it say
"there is no su binary installed and supersu cannot install it. this is a problem!"
help me pls
Click to expand...
Click to collapse
Ok do this, lets start fresh here and uninstall that su app. Now, go to THIS thread and download supersu v1.86 and flash it in recovery. once booted go to the su app and if it happens to tell you to update the subinary, click on "normal". It will now install and tell you you need to reboot device then do just that. you should have root now, also while you're in there you can grant permission for apps too instead of prompt.
piimp said:
Ok do this, lets start fresh here and uninstall that su app. Now, go to THIS thread and download supersu v1.86 and flash it in recovery. once booted go to the su app and if it happens to tell you to update the subinary, click on "normal". It will now install and tell you you need to reboot device then do just that. you should have root now, also while you're in there you can grant permission for apps too instead of prompt.
Click to expand...
Click to collapse
thanks work

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,

SuperSu 2.67 missing icon in launcher

I installed SuperSu v2.67 on a Nexus 5 running stock Marshmallow 6.0.1, and SuperSu works great for me so far!
The only (minor) issue I've encountered thus far is that the SuperSu icon seems to be missing from the Google Now launcher home screen and app drawer.
I can still launch SuperSu by searching for it in the Google Play store and clicking "Open", and it still pops up when an unauthorized app is requesting root access.
I've tried to do a complete unroot + reinstall, change the SuperSu icon from the app's settings etc. - without success.
Has anyone else encountered this? Is there any way to get SuperSu icon to show up?
Thanks in advance.
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Edit:
Correction! Found the icon. It was buried in the app drawer all along. What threw me off was that for some reason, when I write "SuperSu" or any prefix of the name in the search box at the top, it doesn't find SuperSu, like it does pretty much any other app. Weird.
Anyway, thanks for the help and sorry about the false alarm.
Chainfire said:
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Click to expand...
Click to collapse
I'm having a similar problem as the OP except that 2.6.7 binaries don't install on a T-Mobile Note 4 (SM-910T3) in either Lollipop or Marshmallow using either the Normal or TWRP methods. 2.6.5 and 2.6.6 binaries install properly, however.
I tried the command in recovery and got the following error:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Chainfire said:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Click to expand...
Click to collapse
You're right I didn't explain things right. My ROM comes preinstalled with SuperSU 2.6.6 and I have the same issue as the OP as the app doesn't appear in either app drawer and I can't launch it from the Play Store either. I'll try adb uninstall properly.
The 2.6.7 failed install is a separate issue. Do I start another thread here in the same forum? What info do you need?
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
thereassaad said:
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
Click to expand...
Click to collapse
Thanks. I got it to uninstall and was able to reinstall, but it still wouldn't show up in app drawer or open from the Play Store.

[SNAPDRAGON][EXYNOS] ViPER4Android [ZIP][FLASHABLE]

Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Paradoxumical said:
Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Click to expand...
Click to collapse
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Works perfectly on my T-Mobile N950U! Thanks!
Sent from my SM-N950U1 using Tapatalk
xxx42069 said:
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Click to expand...
Click to collapse
If you have a Snapdragon device, SafetyNet is already tripped due to the nature of the rooting process.
But if you have an Exynos device, by all means, use the Magisk module. This ZIP was intended for the Snapdragon variant (since that's what I have), but works on Exynos variants as well.
i flashed it n nuthin,i cant even find the in-app u wrote about
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
Yeah, I used the old busybody version. I just went back to stock after a few hours of messing around with no results. My main reason for root and accepting the 80% battery limit is viper but since I can't get it working I went back to stock for now. Will try again once there is more development. Let me know if you do get it working.
mister_propa said:
i flashed it n nuthin,i cant even find the in-app u wrote about
Click to expand...
Click to collapse
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Paradoxumical said:
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Click to expand...
Click to collapse
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
lilviet93 said:
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
Click to expand...
Click to collapse
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning: it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Paradoxumical said:
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning:it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Click to expand...
Click to collapse
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
That is the strangest thing, I can't imagine why the ViPER apps wouldn't show up. The only thing that comes to mind is... If you ran the fsck script after rooting, did you?
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I had the same issue, but then in FlashFire, under settings I disabled Emulate framebuffer.. Now Viper4android is installed and working.
Does anyone who has this installed get freezes after reboots from time to time?
kirschdog1 said:
Does anyone who has this installed get freezes after reboots from time to time?
Click to expand...
Click to collapse
It freezes up all the time, even when requesting SU.
Sent from my SM-N950U using Tapatalk
Does anyone on Snapdragon have this and FM Radio working together? Unfortunately, I'm finding I can't run both. I don't know if it's my Viper settings or what. Any input would be appreciated as I don't want to have to choose between the two features if I don't have to
For those who had trouble on snapdragon try using latest Sam fail v2 if possible it works perfect on here if you follow directions. Few key things, disable emulate framebuffer in flashfire and when flashing enable mount read and write system, also make sure you install drivers in both v4a apps to enable root as root access is need for v4a to work properly after unistalling drivers and granting root reflash zip in flashfire to restore drivers and profit
I have problem with viper4android hifi can't read root access
jomolocco said:
I have problem with viper4android hifi can't read root access
Click to expand...
Click to collapse
If I remember correctly, there was something that said if you had this trouble, open app, uninstall the driver, Grant the permission, then re-flash the app.

Categories

Resources