yashsingh1/xdaforums huggingface dataset:
[SuperSU] derpotato:
That's what I wanted to do, but backing up the data with titanium backup is impossible without granting root access. And to make things worst, I linked almost all my apps with link2sd and I can't get it unlinked without root access, so restoring back app data with application like android manager seems impossible because half of the app data is in the SD card, and nandroid backup does not include that data in the SD card. I'm in a bad position.
[SuperSU] bhiga:
AFAIK Tasker doesn't require root to launch apps. I went so far as to deny root to Tasker and it still worked.

I made a standalone app for you to try.

http://www.androidfilehost.com/?fid=23501681358543229

Be patient after launch, it took a few seconds before SuperSU came up on my phone.

-= this post enhanced with bonus mobile typos =-
[SuperSU] jazzruby:
Titanium Backup can restore your data:

-JR-
[SuperSU] derpotato:
Wow , you even made an app for that, thank you very much, I'll try that in few minutes (I already reflashed back to stock because I gave up, so I need to restore my nandroidbackup first). It worked without needing root on my reflashed stock ROM though. I'll report again after I restored.

---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------

I'll try that soon. Thanks.
[SuperSU] NZgeek:
Other options to try are...

# Clear the app data again, then boot into recovery and clear cache and Dalvik. This might be enough to kick things back into life and get the app to show again.

# Install Apex Launcher (free version should do), then long press (add to home screen) > Shortcuts > Activities > SuperSU > .MainActivity. This will create an empty icon labeled SuperSU, and you should be able to tap the space where the icon should be and launch the app.

# Boot into recovery and use adb to remove the apk file. The commands you'll need to use are:

su

rm /system/app/Superuser.*

The su command may or may not be needed, but should automatically succeed as there's no way to show a permission dialog.

Hopefully one of these works, and you won't need to resort to more drastic measures!
[SuperSU] :
Well, you can reflash SuperSU via recovery.....

Or you can update SuperSU from Play Store....

This will bring SuperSU back to the app drawer....

Btw, why did you delete the data of SuperSU for???

Here's the link for v1.97 flashable zip.... http://download.chainfire.eu/416/SuperSU/UPDATE-SuperSU-v1.97.zip

Hope this helps.... :good:
[SuperSU] boyheadkick:
Flashed 1.99 r4 on Archidroid 2.x experimental for i9300 based on Omnirom's 20140605 nightly 4.4.3 based...all good here

-aL

tapatalked from my super duper palm top computer
[SuperSU] derpotato:
Well I'm really unlucky this time, I should have waited for your solution before I restored back to stock. Because I linked all my application to sdcard with link2sd including the supersu, all the apps including the supersu is not available anymore, I even linked play store to sdcard so play store is gone too. And I couldn't relink apps with link2sd because I do not have root anymore. Because of that, every single trick is not working at all. Ah well, I'll reflash to stock again. Sorry for wasting your time.

But, I think you guys should post this to the first page so that everybody can see the other ways to unhide supersu . Especially that application you made, It seems to be working (I tried automatically denying root on my reflashed stock rom , and the application still opens supersu, amazing). That application would help anyone else who aren't as unlucky as I am, lol.

Thank you very much, I ran out of thanks today (max 8 thanks per day).

---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------

That didn't work out in the end because half of the application is linked to SD card with link2sd so it's invalid. It would work if I didn't use link2sd though.

---------- Post added at 03:32 PM ---------- Previous post was at 03:26 PM ----------

I did update supersu from play store, and it did nothing at all.

and I did reflash the supersu zip, and it did nothing at all, too.

I deleted the data of superSU thinking that the application would 'forget' that I hid it to make it reappear again... but no, it makes things worse.

So , if you want to mess with your friend's phone that has root, try to do it like mine, just borrow your friend's phone, and then silently hid your friend's superuser app then delete the app's data. That would make them really mad :laugh:
[SuperSU] :
LOL... :laugh:
[SuperSU] ma678:
I finally flashed 1.99r4 on my N7 2013.
[SuperSU] bhiga:
Tasker makes it easy to create simple macro-style apps (and complex ones too), credit really goes to its developer.

I also didn't know Apex launcher can create arbitrary shortcuts, great tips [MENTION=4163343]NZgeek[/MENTION]

I felt a great disturbance in the force... like a million SuperSU PINs being set then immediately forgotten...

-= this post enhanced with bonus mobile typos =-
[SuperSU] simonbigwave:
Just to confirm on CM11 605 nightly Jflte w/ART via Philz6.40.0, installed SU1.99r4 all good. no problems at all.
[SuperSU] derpotato:
Well, many friends of mine who uses superuser doesn't set SuperSU PINs (neither do I). That also means that alternatively, you can just set SuperSU PINs randomly in your friend's phone :laugh:
[SuperSU] :
[MENTION=4659499]derpotato[/MENTION]

I also hid the SuperSU app just because i was curious.. :silly:

tried like every thing already posted here and 10 more.. but couldn't get it back :eek::eek::eek:

then i did these.. and now it's back

booted to recovery and deleted files and folders (don't remembe the exact names) like... /system/app/Supersu.apk, /data/data/eu.chainfire.superuser, /cache/dalvik-cache/@system...supersu.dex

installed supersu.apk and it showed up on my launcher.

EDIT: I just converted it to system app.. and now it's gone again.. but this time i didn't hid it.. o__O

oh well. it does says in the prompt that it may not appear at all after boot.. gonna install again.. :|
[SuperSU] derpotato:
Well, it's too late for me :(

I think there should be a thread for unhiding supersu without needing root , so people won't be as unlucky as me , and people wouldn't need to ask about it again :D
[SuperSU] porga:
Dear friends,

I have one question about supersu.apk or superuser.apk and I would like to get your help.

Is it possible to have root without that application installed on the phone, so all superuser permissions are automatically granted.

Thank you.

EDIT: In short, I need phone to have superuser access, without SuperSU.apk, automatically granting permissions, without logging changes.
[SuperSU] :
No, of course you need a superuser app like SuperUser or SuperSU to grant root access to root apps....

Without this app you won't be able to use apps which require root even if your phone is rooted...

Hope this helps...:good:
[SuperSU] nick123ablxx32:
well even if you have a rooted ROM without an interface for apps to use the xbin/su (I think that's what it's called) command then you can't accept or deny an app root permissions

---------- Post added at 03:22 PM ---------- Previous post was at 03:17 PM ----------

.....works great on CM11 Danvandh Edition no prompt to update SU binaries ..... thanks CF
[SuperSU] or.green:
Perfect! Solved my problem, thanks.
[SuperSU] porga:
The thing is that i would like app to accept su permission automatically, without asking user or logging. Is that possible?
[SuperSU] shekinahsmoke:
I started getting the same "silently denied" messages on 1.99r4 for apps like Titanium Backup and Trickster... scary
[SuperSU] iamnotkurtcobain:
Me too... :/

Gesendet von meinem GT-I9505 mit Tapatalk
[SuperSU] nick123ablxx32:
only noticed now "root validator silently denied" ? :confused: :silly: :eek:

---------- Post added at 04:31 PM ---------- Previous post was at 04:26 PM ----------

yes it is simply go into SuperSU settings go into >Default access> Grant (wouldn't recommend)

for logging go to logging section and select> none
[SuperSU] farisyi1:
1.99r4 worked perfect with OmniROM 4.4.3 on SGS2 :D

Thanks [MENTION=631273]Chainfire[/MENTION] [emoji106]
[SuperSU] Summer Son:
Yes, you can. I'm not sure how the things are with SELinux and enforcing, but in older Android versions (pre 4.3) you just had to set ro.secure to 0, or smth like that. I'm sorry I don't really remember, you can Google for it, it was however always considered as a rude way to root as it turns down all the security. Imagine any app (or maybe virus) can do whatever they want with your phone. But if you really trust your system and have 2-3 apps you know what they do on your phone, that could be wise. I still think you can do it now on 4.4, and avoid running all those daemons fooling SELinux enforcing.
[SuperSU] edbertin:
Confirmed here too. Omni Rom
[SuperSU] brunodu91:
It's ok on i9505 jflte

Envoyé de mon S4, via tapatalk 4 Vip .

Slimsaberkat 4.4.2 v5.6, alucard Kernel , buzz launcher , modem ET bootloader NC4.
[SuperSU] Pianoman144:
Is that normal that the 1.99r4 has a size of 5,7KB? I can't flash that file. It is a little to small isn't it?

Gesendet von meinem SM-N9005
[SuperSU] wetxxx:
I have a HTC One M8 and a newest SuperSu. I feld that dont have a file permision to RW. I change platform.xml like other post, but nothing. I have a 1.54.401.10 Stock rom version. I dont have a S-off, becouse i have difrent memory chip so actually Firewater desnt helps me :)

Maybe I should unistall superSU from TWRP and install again? How do it?
[SuperSU] yethz:
Corrupt download maybe..

Device: Google Nexus 4 ( LG-E960 )

ROM: SlimKat 4.4.2 ( Build 5.6-4577 )

Kernel: Stock Kernel ( 3.4.91-SlimKat_4.4_3.3 )

Recovery: PhilZ Touch CWM ( Advanced-Edition for Mako )
[SuperSU] Chainfire:
If you remove all traces of the APK (from /system, from /data/app, from /data/dalvik-cache) and the data folder (/data/data/eu.chainfire.supersu), the su binary will in fact behave exactly in that way.
[SuperSU] sub1287:
Its not safe running superuser access like that though.

accelerated [mako]
[SuperSU] :
Nope, that's most probably a corrupt download... The original file size is 1.2 mb....
[SuperSU] evildog1:
i have found some bugs on SuperSu 1.99r4

Du battery saver: I granted root access but it does nothing with root, it just run normal way like non-root. And sometime it keep asking root access.

GL to SD: After i use for 1 week, it does not mount /Android/OBB anymore even it say it is mounted. It requires reflashing ROM and SuperSU

My device is Galaxy S3 mini and running CM11 Android 4.4.2

I had no problems before i had updated SuperSu to 1.99r4

---------- Post added at 10:14 AM ---------- Previous post was at 10:10 AM ----------

use another browser that supprort advanced downloading. Opera Classic is the best downloader, it does support Mediafire, Rapid, Deposit, Zippyshare, and more file hosts and can download file from unsupported file hosts. Stock browser have some issue with downloading.
[SuperSU] :
Sorry for a n00b question, but is there any changelog for v1.99 releases???

I can't seem to find one....
[SuperSU] occtec:
Hey guys I'm still on 4.4.2 using Franco kernel test boot r54 on my Nexus 5, currently I'm using SuperSU v1.94 is there any benefit upgrading to v1.99??

Thanks in advance!!
[SuperSU] 089man:
1.99r4 works great with namles 4.4.3 rom for s2 device.

Great that now the superSU included in rom system settings and replace the standard superuser.

Great Work. Used pro version.

I9100 Tapatalk 4, Nameless-Rom 4.4. 3
[SuperSU] Pkt_Lnt:
They are experimental versions trying to fix bugs. Changelogs exist for stable releases. Use the 1.99 releases to solve bugs or assist in testing.
[SuperSU] asferican20:
MobileOdin Pro is now working with 1.99r4 on Galaxy Note 10.1. :good:
[SuperSU] evildog1:
i have the same problem too. this problem only happen on v1.99r4, it needs to be fixed.
[SuperSU] kingvortex:
Then help out by providing detailed information on device and rom version and capture some logs and attach them here.

If you don't want to do that, then revert to the stable version from the Play Store as the version you're using is for testing.
[SuperSU] evildog1:
My device: Samsung Galaxy S3 mini

ROM: CM11 Android 4.4.3 by Maclaw

i won't collect logs becuase the file size will be huge if i let it run in 1 hour. it only happens when i lock my phone.
[SuperSU] kyrillos13:
I also have the silently denied su issue with SuperSU v1.99r4. It happens sometimes after screen on. Catches a screenshot , I will try to catch a good logcat too.

Sent from my GT-I9195 Black Edition
[SuperSU] sushidog:
Why the he'll are you greenifying SuperSu?! :eek:

/// Samsung Galaxy S4 GT-I9505

/// Press "THANKS" if I helped you
[SuperSU] shekinahsmoke:
Dudes are pure n00b... It boggles me
[SuperSU] gorilla p:
1.99r4 working perfectly with C-Rom on NeXuS⁴. (Slim-Rom based). 4.4.3

Maybe I'll try Greenifying SuperSU and save some battery life! [emoji23]

via Mental Telepathy
[SuperSU] 78Staff:
Well I may have spoken to soon, I also have started experiencing the silent deny issue with a few apps on 1.99r4 - SSH and FTP apps that I have noticed. Reverting to 1.94 corrects the issue. I will try to re-produce and supply some log info...
[SuperSU] USBhost:
Nexus 7 2012

CarbonRom android 4.4.3

1.99r4

My problem is:

It messed up system permissions

Made system read only and yes I made it r/w

Used up a good amount of ram 150mb+. That's strange?

Did some strange things to google services

broke busybox. Now that's vary strange!
[SuperSU] Haidary.T:
Look at CF's 1.99r4 post. Read it and you'll see that it is meant to be and not actually a problem.
[SuperSU] 78Staff:
Well yes and no - the toast is expected when it occurs (denial during screen off), but r4 appears to be silently denying apps that have already been granted access when the screen is off - unless I mis-understood, which is very possible. :) I am currently re-applying r4 and attempting to reproduce...

EDIT - app is SSHDroid - has been granted root, but will not start successfully - eventually I will get a silent denied toast, but it's hard to capture... Not sure if this helps any...
[SuperSU] evildog1:
Nevermind. the problem is stopped by itself
[SuperSU] Chainfire:
I'm interested in this silently denied issue - I have not see it happen myself, so please be as detailed and provide as much information as possible for me to reproduce.

The strangest thing is, the code that triggers this is only present in the prompt screen, so the app (even if previously granted) must still be generated the prompt for some reason (which is odd by itself).

You aren't greenifying SuperSU as well, are you? All bets are off when Greenify is used.

Could be the data shown in the popup is left-over from earlier, might need to look at that as well.

Either way, I think this is the only potential issue reported on 1.99r4 so far, which is good...
[SuperSU] Elluel:
Flashed r4 on my build of Carbon 4.4.3 and I had a couple silently denied toasts, went away now though.

Kernel tweaker, Greenify and Android Firewall were being "silently denied". And no, I did not Greenify SuperSU

Sent from my Nexus 5
[SuperSU] The Gingerbread Man:
Iv seen the silently denied toast a couple of times using fku kernel updater by fransicofranco using nexus 5. If I recall I saw it where I had to turn off the screen for some reason and saw the toast when I turned the screen back on. I don't recall if I was in the middle of changing a kernel setting or something and had to leave it to deal with something at work or something. If I catch it again I'll see I can get get logcat and a screen shot of supersu log. That's the only application where I have seen it. Other than that everything seems fine and dandy. Also just to edit and add to that I don't use greenify or anything else that should interfere with fku app.
[SuperSU] kyrillos13:
Su binary works fine and I have disabled SuperSU toast notifications (following "protip" from OP). Logging works even if SuperSU is greenified, so I don't see any good reason to not greenify it. No problems at all.

[MENTION=631273]Chainfire[/MENTION], I cannot confirm, but I think that this issue didn't exist in 1.99r3.

Sent from my GT-I9195 Black Edition
[SuperSU] gadgetguy08:
I had just installed SlimKat 5.8 (4.4.3) and SuperSU 1.99r4.

I ran textdroider_dpi from the Play Store (changes screen density) and SuperSU asked for superuser permissions.

I granted it, made the change and then exited out.

At that point I went to do one more thing before rebooting, but before I did that I got the "silently denied" message.

I continued and rebooted and there were no problems.

SuperSU still shows textdroider_dpi with permissions, so no issues with that.

[Greenify not used for SuperSU.]

Thanks for the app and your continued efforts.
[SuperSU] mag01:
See my post http://xdaforums.com/showpost.php?p=53182241&postcount=5632 - it contains steps to reproduce for at least one case.
[SuperSU] GreyGhostRos:
Hello, First of all thank you for SuperSU.. It is great!!

I'm having a problem with SuperSU installation.

Device: Meizu MX3 (Just in case: http://www.gsmarena.com/meizu_mx3-5679.php :P)

They run a custom ROM called Flyme OS.

SuperSU used to run great until Flyme used 4.2 (1.94 from Playstore was working atleast). Recently they have started test builds for 4.4.2 and since then problems have started :(

1. Flyme lets users root by selecting an option in their settings. And it has a built in SU permission manager which is very basic (Only has allow and deny)

This is the what we have with default root:

2.

3.

I'm don't really know much about all this but just in case it is relevant:

1. getenforce: Returns Deisabled

2. /default.prop has ro.secure=1

Let me know if I can provide with any other information. Thank you!
[SuperSU] sirxdroid:
Seeing the silently denied issue too. On a Nexus 5, running stock 4.4.3 ROM & kernel, SuperSU 1.99r4. It randomly happens when I start ES File Explorer. What's strange is that there is no entry in SuperSU for ES File Explorer and it's not prompting me to add one but ES File Explorer root functionality still seems to work.

FWIW, I used to have 1.94 while using stock 4.4.2, then did the OTA upgrade to stock 4.4.3 and flashed SuperSU 1.99r4
[SuperSU] GBP85:
I too have seen that denied toast message. However, I only saw it once with FauxSound. It still showed it was allowed when I went into the app. I'm using Nexus 5 on stock 4.4.3. I'm also using Faux Kernal.
[SuperSU] juliatan:
Is Ota Survival Mode with SuperSu Pro already working with stock Android (and stock bootloader/recovery) on Nexus 7 2013 going from Android 4.4.2 to 4.4.3 ?

Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk
[SuperSU] MikeRL100:
Speaking of silently denied, I've seen it several times myself, but it's kinda hard to catch it considering that it usually happens shortly after I turn my screen back on. I wish I could log it for you. Perhaps make a special debug version with verbose logging that automatically saves logs to a file. V 1.99r4 to be exact, at least got my case. I'd say it's worth fixing before a release to Play.
[SuperSU] Spiricore:
I'm having the exact same issue with my Galaxy S4 on Carbon 4.4.3 (6/9 and 6/10 nightlies) with r4. I've only caught it right after turning my screen on with apps I'm sure have allowed access. I've tried toggling reauthentication and Trust System User with no effect. I will report back if I come across any additional information, as I'm still recovering from a clean wipe.

Sent using Tapatalk from a Carbon Galaxy four, four away.
[SuperSU] MikeRL100:
I'm on Nexus devices and having these issues. Running OmniROM based off 4.4.3. Does this issue persist across Android versions? Chainfire should consider producing a debug version.
[SuperSU] AndroidDeveloperLB:
Hello all,

I was sure my app had an issue working with SuperSu, as it failed to gain root over and over, even when the SuperSu doesn't have it on its list of apps. It was really frustrating as I was sure my app has a bug (it worked fine before).

Now I've noticed that there are many posts about "silent denial". I assume this is it.

I've even tried flashing "CWM-SuperSU-v0.94.zip" .

Does anyone know of a workaround for this? Or at least which version had it working fine?

My device is SGS3 (I9300) , and it runs on CM11 (Android 4.4.3) BTW.

I also wish to ask a technical developer question:

How did you add the feature to change the app's icon? If you wish, you can PM me instead of writing it here.
[SuperSU] sushidog:
As far as I know is only happening after 1.94 version. Someone correct me if I'm wrong.

/// Samsung Galaxy S4 GT-I9505

/// Press "THANKS" if I helped you
[SuperSU] botski:
hi guys! i have a problem. i had a note II e250k dn3 beta 2 installed rom. binary is not installed. this is the first time encountered this. pleAse help!
[SuperSU] botski:
problem solved thanks guys!
[SuperSU] GreyGhostRos:
Chainfire has done a tutorial on it in his blog here:

www.chainfire.eu/articles/133/_TUT_Supporting_multiple_icons_in_your_app/
[SuperSU] AndroidDeveloperLB:
I see. So it enables&disables activities with the icon it wants, and then it kills the launcher so that it will refresh itself, assuming it will refresh fetching of the icon.

Is there a way to do this programmatically, instead of having the icons built into the app?

Or maybe such a thing requires altering the APK itself ?
[SuperSU] WhosAsking:
Possible Feature Request

Nothing big here, just a potential feature adjustment.

In the main settings, you currently have an option for Re-Authentication, which means you have to re-grant root for an app after it updates. Thing is, this option only applies globally. I am proposing you add this re-authentication to the per-app permissions. I've found that the occasional app works better this way because they both (1) can be auto-updated by Play and (2) have automated tasks (the two that spring to mind are Titanium Backup and AdAway). So what happens is that, for example, Titanium Backup gets updated in the background so I don't know it's happening, then when it performs its scheduled update, I again don't know this, so SuperSU gets a prompt timeout and the task fails.

I don't wish to disable Re-Authentication on a global basis just to stop this occasional hiccup, and I feel a good solution would be to allow exceptions on an app-by-app basis. What do you think?
[SuperSU] MikeRL100:
It happens with a variety of root apps. As soon as the screen comes back on. My guess is it has to do with SuperSu being requested when the screen is off.
[SuperSU] JaMeVu:
What is this silently denied ????

Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi