yashsingh1/xdaforums huggingface dataset:
[SuperSU] esgie:
P905 note pro 12.2 lte / 1.99r4

Issue of silent denial happens here, too, not sure however what was the first version with it, but it was present for sure in 1.99r1. I can confirm that it is somehow related with turning screen on/off, maybe selinux is reloading its policy or something? Btw I cannot set it to permissive by default, the constant for persistent enforcing mode has been compiled into the kernel binary.

Solution to get system-wide su access back immediately, without losing anything, in my case is:

1. Reboot to TWRP -> mount -> system (so I have mounted my cache data and system partitions), then advanced -> terminsl and type:

restorecon -R /system /data /cache

Guess CWM-based recovery users can do it in a similiar way.thru Aroma File Manager.

Above command will fix selinux context for all the files iin system and data, but it will results in broken su access system-wide. Su binary contex set during SuperSu zip installation is different than one set by restorecon command basing on default samsungs policy in /files_policy (which is u:object_r:su_exec:s0). Maybe it somehow happens automatically during screen-off on some conditions?

2. ....So flash SuperSu from zip (link [MENTION=225651]op[/MENTION] ).

Then everything returns to normal.

I also use greenify (2.4 beta 2 atm), as many people out there with the issue, I am not greenifying SuperSU, howeer that is also giving me an idea that maybe the issue discussed is somehow related to actions performed by greenify while screen-off causing a conflict? There were some updates related to screen off auto hibernation functionality recently afair...?
[SuperSU] edbertin:
[MENTION=631273]Chainfire[/MENTION] the scenario for silence deny happens randomly. When you turn on and unlock the screen you will see this msg attached.

Dunno what trigger this, but is common a bit. Franco Kernel, ES File Explorer, Log Cat, others app that requires root.

Ps.: I don't have greenify

Device: Nexus 5

Rom: Omni Rom lastest nightly 06122014
[SuperSU] simonbigwave:
Same here.
[SuperSU] JaMeVu:
Silently nightmare :(

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
[SuperSU] MassStash:
probably faux's fault
[SuperSU] Frank Westlake:
No silent denials on SM-N900T.

Frank
[SuperSU] goodoane:
I seen this once or twice when I unlocked my phone (note 2) all stock but... I use xposed framework. Did you guys use xposed framework?...
[SuperSU] GBP85:
People are indicating this issue without Faux software.

Yes, I'm running exposed. I've only seen it once and everything continues to work.
[SuperSU] Frank Westlake:
No silent denials on my SM-N900T.

No Xposed.

No Faux.

No Greenify.

No custom firmware except TWRP.

Frank
[SuperSU] frater:
I'm having these silent denials for all my apps. I saw them for titanium, and other apps.

My previous version was 1.94.

I'm now on LG G2 with mahdi 4.4.3 ROM
[SuperSU] mindmajick:
faux has addressed this accusation

http://xdaforums.com/showthread.php?p=51836646

-》Sent from my mind to your screen.
[SuperSU] egingell:
You know that post you linked to is over two months old, right?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] mindmajick:
and the reasoning is no less valid after two months.

kernel and root are unrelated.

-》Sent from my mind to your screen.
[SuperSU] adrman:
Just had my first silently denied on Trickster Mod. N5, running latest Rastakat, Uber kernel with Franco Sound.
[SuperSU] sushidog:
Let's celebrate with some champaign.

/// Samsung Galaxy S4 GT-I9505

/// Press "THANKS" if I helped you
[SuperSU] Bazilli:
I'm seeing the silently denied messages lot too. Usualy it pops up apps like: ES file Explorer, BBS And Titanium backup. I'm using Motorola Moto G XT1032, with stock Kitkat 4.2.2. I got Xposed and Gravitybox installed. I tried to uninstall xposed and gravitybox, but it did not help.

e: SuperSU is latest v1.99r4
[SuperSU] kien_vip:
1.99r4 get fore close popup on my android 2.3.6, l3 e400 tiny phone. but it seems still working.
[SuperSU] Pons:
Could you capture a logcat?
[SuperSU] Chainfire:
Re: silently denied

Don't blame other apps for this. Seems to be a SuperSU bug. I finally have semi-reproducable case, I hope to be able to trace and fix it today.

There are a few other minor issues that need fixing in SuperSU, but I'm going to push for a proper update (including Play) ASAP, as a new root was released using v1.99r4 su binaries that doesn't actually include the APK (doh) and installing the v1.94 Play version over it can cause issues.

Hopefully I'll have an r5 in a few hours, please stand ready to test it :)

Yeah this has been on the to-do list for some time. It'll come - not sure when. Maybe next update, maybe months from now. Long story, but UI updates for SuperSU are especially painful to do compared to most apps.

Please provide a logcat of the crash!
[SuperSU] coolkoushik07:
1.99r4 working on xperia z1 compact running latest cm11 nightly

Sent from my Xperia Z1 Compact
[SuperSU] coolkoushik07:
Update : I dont know if its related to supersu or not but after installing i.99r4 my battey starts draininh first and android os was on top of the list.. For now i have reverted back to 1.94.. Will notice if the same happens again or not

Sent from my Xperia Z1 Compact
[SuperSU] Bright09:
thanks chainfire maybe I can update supersu binary when its up just rooted my i535 insurance replacement with new root method :D
[SuperSU] Bright09:
update: forgot that I could just install apk from zip silly me
[SuperSU] MatroxD:
Thanks chainfire!
[SuperSU] WR3CCKL3SS:
Thanks [MENTION=631273]Chainfire[/MENTION] for the hard work and dedication... Ill be ready to test as soon as you upload... I, too, have been plagued with the silent denial so anything you put out to fix any bugs is something I'm quick to get and support...

Rockin' SuperSu since 2010...4 years and going
[SuperSU] Chainfire:
v1.99r5 is now available from here: http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip

Please let me know if this gets rid of the "silently denied" issue ASAP.

Still some release-stoppers on my to-fix list, so no Play release just yet, but I hope to fix those issues while you guys figure out of the silently denied issue is gone.
[SuperSU] mag01:
[MENTION=631273]Chainfire[/MENTION]

Now I'm not getting any "silently denied" notifications at all - even not the valid ones.

Nexus 5, Stock Android 4.4.3, Linaro kernel r54t1
[SuperSU] G.M.L:
LG L3 E400 ics 4.0.4 and me not getting" silently denied" after update

G.M.L._V7

http://pasakalis.blogspot.gr
[SuperSU] darkrevlis:
GT-I9505

FIRMWARE: I9505XXUGNE8

SUPERSU: v1.99r5

if I try to install from CWM or TWRP, back to the message I need to reinstall binaries.
[SuperSU] Chainfire:
I certainly still get the valid ones, but they are now subject to "notifications" being enabled under Settings - in case you had turned that off.
[SuperSU] Frank Westlake:
Isn't the solution for that to wipe cache?

Frank
[SuperSU] darkrevlis:
you say install from cwm or TWRP and then wipe cache too?

if that's what you mean then I'll try and give my results. thanks

Edit: Not solved. when I install SuperSU and start the device doesn't need the binaries, but when I run Wanam exposed to have permisive selinux, then open SuperSU and I need binary. if I try a normal installation fails. if I try to install by CWM or TWRP I return to the same loop.
[SuperSU] mag01:
Oh well, I've got these notifications disabled. So now to see these "silently denied" ones I have to enable all of them, alright.

Anyway, after enabling them and checking they display correctly I no longer get those false ones for the scenario I was getting them previously.

So this issue seems to be solved (at least in this case).

By the way, do You think it will be possible to do anything with the phone being woken up on each su attempt that triggers the authorization popup? That's the main cause of the battery drain. Instead, I could imagine these su attempts might be rejected right away (or with the specified timeout but without any popup being shown) or something...
[SuperSU] sndrdg:
Flashed over v1.99r4. No issues / No update binary message / No silent denials (yet). One thing strange though - there is now an entry in my application list for ADB Shell - which I don't remember adding or approving? Is this entry now required?

Doug

Sprint SGS4 / Stock 4.3 / Philz
[SuperSU] darkrevlis:
I can't get permissive selinux with Wanam xposed. back to supersu v1.94 and everything works correctly again.
[SuperSU] 78Staff:
So far not seeing any silently denied errors with r5- but am having problems with some apps not starting with 199r5 that work fine with 1.94. Two apps in particular, same dev so may be issue with the apps themselves - I will post in the app thread also...

SSDroid (And FTPDroid) - App loads, but will not allow SSH daemon to start, nor will it allow app log to start writing... Only logs I can pull are from SuperSU, and are the same errors as listed before with r4 so I am just reusing those screenshots.

I'll uninstall/reinstall and also play with a few other SSH apps I have to see if it persists...

EDIT - found "Rooted SSH/SFTP Daemon" that works fine with 1.99r4/r5 - not sure of issue with the above apps but I did post in the dev's app thread, so maybe he will take a look.

https://play.google.com/store/apps/details?id=web.oss.sshsftpDaemon
[SuperSU] :
Sorry guys, I've got two n00b questions :confused:

I've flashed official TWRP on my condor and then flashed the SuperSU v1.94 zip file through recovery and successfully rooted....

After that I had successfully installed SuperSU as a system app...

Now, if I factory reset my device from recovery will I lose root and need to flash TWRP and SuperSU again???

If not, will resetting remove SuperSU from system app??? If not, will the app data and cache of SuperSU get cleared???

In short what would happen? I plan on factory resetting my device soon....

And if I want to buy SuperSU Pro to support development, will installing the pro key from Play Store turn my SuperSU flashed through recovery into Pro??? Or do I need to install/update SuperSU from Play Store???

Thanks in advance....
[SuperSU] Pons:
No, and no. And probably (depends on where SuperSU stores its data; too tired to look right now).

Factory resetting removes user apps and user/system data, but not system apps.

Yes. Just install Pro and reboot. Although factory resetting will delete Pro key, you'll just have to reinstall (not repurchase if you use the same Gmail account) it.
[SuperSU] :
Thanks very much. But can you please say whether resetting will remove SuperSU app data/clear cache....

And I had installed BusyBox binaries in /system/bin through the BusyBox installer by Stericson and after installing had removed the installer...

So after hard resetting my device, do I need to install BusyBox binaries again???
[SuperSU] Chainfire:
Not sure what your issue is...

I just did a fully clean install of UGNE8 with v1.99r5, installed Xposed and set SELinux to permissive through Wanam, and everything is working fine here...

Have you enabled the options to use su during boot, and trust system user? I believe both are required for Wanam Xposed.

Are you running the latest TWRP ?
[SuperSU] Chainfire:
Is this issue still current? It appears to be working fine for me, and gets root ...
[SuperSU] darkrevlis:
Thanks Chainfire for your quick response. Did what you suggest and now everything works in v1.99r5 and without silent denial. :good:
[SuperSU] AndroidDeveloperLB:
I have no idea. I now use what's on the play store, yet when I update CM rom, and run SuperSu, it says it needs to re-root the device , and then, after it does it via TWRP, root is back.

I don't know if it's because of CM or SuperSu, or even TWRP ....
[SuperSU] Chainfire:
Here's a test version specially for you: BETA-SuperSU-v1.99r5-SSHDroid.apk

EDIT: The file is called .apk, it is however a recovery flashable .zip, please rename it (doh)

Let me know if this fixes your issue with both SSHDroid and FTPDroid. I tested SSHDroid myself, and it was a bit of a drag to reproduce the issue at all. That apps doesn't work right on a fair number of firmwares regardless of root access and SuperSU version. I did ultimately find a bug in SuperSU that could prevent it from working on a firmware where it would possibly normally work on, but not sure if that's the one that was troubling you. Please let me know at your earliest convenience.
[SuperSU] darkrevlis:
Hello chainfire, I know this is beta version to test it 78Staff, but the apk is corrupted. thanks
[SuperSU] 2545:
I have Wanam. SU is disabled on boot which is the default setting. I've been running it like this for some time and don't recall having any issues. Do you recommend this be enabled on boot? Why is default setting set to disabled?
[SuperSU] Chainfire:
I don't recommend anything - that recommendation is in the description of the Wanam Xposed module.

There is an exploit possible if your device has adb debugging enabled AND you are connected to an untrusted computer AND that computer manages to gain adb shell access before the Android UI is loaded. That is why it is disabled by default. On many devices this isn't even possible due to USB recognition being too slow compared to UI load time, but it's still possible on some.
[SuperSU] 78Staff:
CF,

Did not fix the issue... Same result from the app, ie starting, gaining root, and flashing the "Starting... message, but does not actually start and does not populate anything in the app logs. The second SuperSu log entry (killall) is no longer present, instead replaced by "exec id | uid=0(root) gid=0(root)"

Please don't spend a lot of time on this if you see the app has issues - I have found a replacement that works fine (Rooted SSH/SFTP Daemon) and not to dump on anyone's work, but the app(s) have had issues in the past with rom upgrades ie GB > JB > KK - I think the dev moved to a multi-architecture design for his apps after 2.x and seems to have issues with various upgrades since. I actually kept a pre 2.0 version saved off for some time to use in such cases. I've posted the original errorinfo in the app thread (as have a few other users I believe) so I'm sure he will look at it at some point.

Thanks very much for looking at these though :) :good::good:
[SuperSU] GreyGhostRos:
[MENTION=631273]Chainfire[/MENTION]

Update Regarding this issue:

A workaround seems to possible.

1. After opening root privileges I installed SuperSU 1.45 by extracting the apk from the zip (found here http://download.chainfire.eu/343/SuperSU/UPDATE-SuperSU-v1.45.zip )

2. It updates the SU binary with success (Normal method).

3. Without reboot I directly update to SuperSU 1.99r5 (Again apk extracted from the recovery flashable .zip). It asks to update SU binary which I allow by Normal method and it succeeds.

4. And now even after a reboot it does NOT loose root and SuperSu seems to be working fine!

NOTE:

1. I have tried this upgrade method only from 1.45 to 1.99r5 (Let me know if you need me to try some other version as well)

2. Trying to directly install 1.99r5 fails to retain root after reboot as described previously.
[SuperSU] culson_35:
Flash superSu 1.99r5 everything OK Rom stock with Ktoonz kernel
[SuperSU] Blac Caesar:
Never had problems with r4.. but just flashed r5 anyway to test. It's running perfect here; latest PA-RC2, Trinity 4.4.3 kernel, Xposed Framework, Xposed GELs, Winam Kit. No silently denied issues so far.

#KCCO.. PARANOID four.Four.Two Nexu5
[SuperSU] gridflash:
Any recommendations on which version of SU is best with the new towelroot?
[SuperSU] chrisnz1947:
HTC One M8 developer and rooted applications

I have the above phone which is rooted with Supersu pro v1.94.

I am having issues with some rooted apps, Namely Busybox Pro , Andriod Tuner(V3c), BusyBox X (the latter as a test).

All of these are causing the phone to reset either during install (Busybox Pro and BusyBox X) or when I attempt to use some of their functions.

I have Titanium Backup and Root explorer installed and these are giving me no issues.

Whilst I am not saying this is a SuperSU issue the common factor is these apps require root.

I have stopped installing any additional rooted apps until I can isolate the problem.

Phone details and software levels.

Model HTC One M8

Android 4.4.2

HTC sense 6.0

Software 1.54.1540.9

HTC SDK API level 6.17

would you have any suggestions what i could do to get more info re what may be happening, ie logs etc so I could direct the issues at the appropriate people.

Thanks in advance
[SuperSU] Chainfire:
v2.00 released - https://plus.google.com/113517319477420052449/posts/e76eC7tY372
[SuperSU] shaggyskunk:
Does this make any sense?

I've downloaded the supersu zip.... I can't find it?

I searched with esExplorer & root explorer.... It says that it's downloaded.... But where?

There's nothing in the notification... Nothing shows up as downloaded?

Edit: weirdest thing... For some reason, the search thought that the sd card was not mounted.. I rebooted the phone, searched again... Found it :confused:
[SuperSU] denzel09:
Thanks :)
[SuperSU] dimebagdan65:
You really DON'T want permissions to stick when the app changes, it's a security hole. That's why when an app changes, it needs to be granted access again
[SuperSU] bsoplinger:
Could this be perhaps why I get prompts for an app that I've already had in the SuperSU apps settings that said do not prompt but grant and then it seems OK for awhile then I get the prompt again? That is no prompt per settings then suddenly a prompt but just once or twice then no prompt for awhile the suddenly a prompt again because there were 2 app updates in that sequence?

After all it does make sense that if the app changes that even if I've said grant always for that app that for security I need to affirm the new, changed version is valid.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[SuperSU] dimebagdan65:
That's about my understanding of the situation :')
[SuperSU] pdppdp:
Delete post.
[SuperSU] qzem:
Can a pro version keep root access even when updating trough odin, from pc? And does it matter where Supersu is installed? i've put it from /data/app/ to /system/app/, casue before supersu I've use superuser and it was in /system/app/.
[SuperSU] DarkhShadow:
I don't think it survives a Odin flash because it wipes /system first

Sent from my ice cream powered Nexus S
[SuperSU] qzem:
Is there any other way, like pre-root files for flashing?
[SuperSU] DarkhShadow:
Doesn't Odin have a auto-root option?

Sent from my ice cream powered Nexus S
[SuperSU] qzem:
Not the version I have:confused:. If there is such Odin, please someone give me a link or something...
[SuperSU] shaggyskunk:
There's Mobile Odin, maybe that's what he's thinking about? But as far as I know.. It's not for our phone at the moment.
[SuperSU] junkmail9:
Thanks, Chainfire. SuperSU is working great on my Kindle Fire. I can unroot, reboot and use the Amazon streaming without any problems. Actually, after booting unrooted, you can re-root (after boot) and still stream video. However, if I reboot while rooted, the streaming is disabled (until rebooting while unrooted...)
[SuperSU] morg01:
@chainfire

I did send you an email via the market link, but thought I'd mention it here as well

Basically a couple of apps that seem to have issues acquiring root privileges

cache mate, and sd maid

Cheers!
[SuperSU] DarkhShadow:
SD maid works fine for me, dark3n asked a few days ago if anyone had the issue with not being able to get permissions on the thread

EDIT: here

Sent from my ice cream powered Nexus S
[SuperSU] morg01:
Strange :confused:

I've uninstalled and reinstalled the app, but it just hangs at 'checking root'

and if you go into supersu logs it has the red hash sign next to the app, but super su never prompts me for allowing access?, and incidentally if you select the log in ssu (the one with the red hash) no info is shown just a close button . . .
[SuperSU] DarkhShadow:
Contact Dark3n

Sent from my ice cream powered Nexus S
[SuperSU] morg01:
Thought it might be a busybox issue behind the scenes (i don't normally update the installed version with the kernel)

but also busybox doesn't seem to be able to gain root access for me either . .

Could this be a custom kernel issue?

Edit :

Yeah i think its a compatibility issue between speedmod kernel install which installs su and then having ssu installed

Uninstalled ssu and the previously mentioned apps all started working correctly
[SuperSU] Kurupt1:
+1 same issue here with multiple apps hanging at root.

Cm9 4.0.4
[SuperSU] shaggyskunk:
Sd maid works fine on stock for me.....? FYI.

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] josechufa:
SuperSu v2.00

Finally, thanks for your work and insistence, implemented and updated binaries in my CustomRom-GlassRom_Blue_V18_AC! D_Blue-Sound_JellyBean_4.1.2-XXEMH1-CSC-PHEEMF1-Official Firmware.instalado V2, 00 without any problem stuck the apk in the ROM and Binary updated OK, Thanks again master, greetings. :good:

[/IMG]
[SuperSU] Fatal_Enigma:
So I received the update via Google play and after opening super su again it prompts me to update the binary, which I tried to do via the normal method.

It hang on installing for more than 5 minutes so I did as instructed and rebooted, when I opened the app again it never prompted to update so I was thinking maybe the binary wasn't properly updated and tried to clean up the installation for reinstallation via google play, but now it appears to have hung on uninstalling.

I have a nexus 4 on 4.4.3, what would be the next steps I should take to ensure superSU is installed properly?
[SuperSU] WR3CCKL3SS:
If you have a custom recovery... Flash the v2.00 zip file and your good to go. No problems here after flashing zip file. Link to zip file in [MENTION=631273]Chainfire[/MENTION] post above.
[SuperSU] Fatal_Enigma:
Cheers, it seems to be working fine.

I just wasn't sure if the zip was smart enough to clean up a perhaps incomplete installation but it seems it was.

Thanks [MENTION=631273]Chainfire[/MENTION] for your awesome work!
[SuperSU] Ripshock:
Thank you OP
[SuperSU] 089man:
Flash the new zip, all works fine. Thanks for great work..

I9100 Tapatalk 4, Spirit-Rom 4.4. 3
[SuperSU] a029159:
Update impossible on Zopo zp998

SuperSU update via Google Play involves: impossible update normally or via TWRP. I've Aldo triés tout installé ZIP file with TWRP: dame résultats...Please Help ! For tour information, my ROM is not a custom one, it's the last official ROM from ZOPO
[SuperSU] PapaDocta:
Same thing here binary won't update.. Rooted using towelroot, verizon galaxy note 3
[SuperSU] Christiancs1969:
900f 'v2.00 installed.. Updated binary. Working a. Ok thanks

Sent from my SM-G900F
[SuperSU] exodius48:
[MENTION=631273]Chainfire[/MENTION]

I got this message after update and always get this message when update from 1.99r1 > ...>r5 then 2.00

Is this normal?
[SuperSU] Pkt_Lnt:
This is not a SuperSU problem, but a CWM error that has been discussed before. You need to talk to CWM dev.
[SuperSU] sushidog:
CWM bug. Install TWRP.

/// Samsung Galaxy S4 GT-I9505

/// Press "THANKS" if I helped you
[SuperSU] VALYYYY:
Wanam

Updated SuperSu v2.0 via Google Play. After that, Wanam Xposed do not change anything. Now, my phone looks like a stock firmware.

Samsung Galaxy S4-I9505

Android 4.3 - MJ7

VRoot method & Root de la Vega
[SuperSU] Chlorophyll:
hey coool

hey buddy ..coool nothing to worry..jus click YES

THATS IT
[SuperSU] bill1clinton:
I am still getting the "binary needs to be updated" message. I have tried all the recommended methods:

- normal install

- cwm install

- flash supersu through cwm

Can someone assist me with this? Thanks.
[SuperSU] USBhost:
Working 2.00

Note 3 n900t

Andoid 4.4.2

NE6

TWRP 2.7.1.0
[SuperSU] Blac Caesar:
v2.00 working perfectly

Nexus 5

PA-RC2 4.4.3

Trinity Kernel 4.4.3-Hybrid

Xposed Framework stuffs lol

#KCCO.. PARANOID four.Four.Three Nexu5