yashsingh1/xdaforums huggingface dataset:
[SuperSU] nicholaaaas:
Are you the developer's cousin or what? In all seriousness root explorer does exactly what it's designed to do. Explore the root. I checked out ES and it was cool, but I don't have a legitimate use for most of what it does. So basically for me and probably others the extraneous features are nothing but a memory/battery drain. People have their own preferences, so let's stop hijacking this thread to talk about it
[SuperSU] Teddybear2:
Google Play 3.5.15 seems to cause problems with apps

Here is the answer to the Titanium problem:

Google Play 3.5.15 did cause it. Titanium suggested to uninstall Titanium Backup Pro key and reinstall it. Did it and so far no problems. App does not freeze anymore!
[SuperSU] felix1234:
Hi, I'm using SuperSU 0.87 on Acer Iconia A501

I like the idea of per-app notification

But SuperSu is way too slow.

For example, I'm using Hide Bar. With Superuser, Hide Bar gets root immediately. With SuperSU, it lags for quite a few seconds before it hides the bar. Can you take a look please?

The rom is Moscow Desire's Android 3.2.1 Alexandra III Ver 1.1.
[SuperSU] Qqqxxxzzz:
Bug:

If I choose full logging, es file manager doesnt get root access.

Sent from my u8800-aurora-ICS using tapa 2-4
[SuperSU] shaggyskunk:
I tried it with full logging, at first it seemed to freeze the phone, but backing out... Then trying again & esExplorer worked fine.. Not particularly smooth accessing it mind you?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] Qqqxxxzzz:
After enabling full logging:

/data is empty

But Es root access is enabled(I did it before enabling full logging), I disabled and tried re-enabling, but it freezes at this screen:

And says: you need root access

Sent from my u8800-aurora-ICS using tapa 2-4
[SuperSU] shaggyskunk:
Don't know... But it works just fine for me...

I have just done the market install for supersu, I didn't flash it... so I don't know if that makes a difference?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] dimebagdan65:
No, just an advocate for saving money. Don't see why anyone should have to pay for an inferior product. RE does its job well, as I said, but ES has it beat. Check my website, I just like to educate and help when I can and if I can save one person some cash that could go to a more worthy dev, my job is done. If I was the developers cousin, I'd be saying you should donate for ES, as is, I'm just a dude trying to point out a superior no cost alternative to this dogmatic drivel known as Root Explorer. And that's all I got to say about thay-ut (in my best Forrest Gump lol)
[SuperSU] shaggyskunk:
I'm a newb, in spite of the number of posts... (still don't understand why XDA gives you a rank based on the number of posts?),

I have both esExplorer & the free version of root explorer... The free version of root explorer will NOT do what esExplorer can my Two cents.

Peace :)

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] carburano:
Added it to my rom instead of su... Great work mate:-)

Inviato con il mio P990 DjangoManouche!
[SuperSU] stokholm:
I'm new to rooting and I'm a little unsure about some of the terms used in SuperSU. Specifically:

1) What does it mean to install SuperSU as a system app? When will I need to do that?

2) When will I need to allow SU requests during boot? Will all SU request be accepted? Will it be logged?

Can someone help me understand? Thanks. :)
[SuperSU] CoolApps:
1. It means by placing it in /system/app which makes the app uninstallable unless you of course delete it via an app, use SuperSU itself or do the manual way of deleting via file manager which all need root. You don't have to make it a system app if you don't want to but I would recommend making it a system app IF you are using a custom rom which does not have root by default.

2. Not unless they are new or you have allowed them to have root access temporarily (a few minutes or next time), if you allow them permanently then you will not get such prompts after every boot. By default logging is on, you can always disable it in the settings.

---------- Post added at 03:50 PM ---------- Previous post was at 03:47 PM ----------

Yeah, since around ICS I assume this touch-outside-the-dialogue-box-to-dismiss feature was added, this feature can be really irritating at times either depending on what app you are using or you accidentally touching the other part of the screen. :P

The funny thing is that I accidentally did it today while setting up Omnirom, so I agree with you in many ways. :P
[SuperSU] stokholm:
I think I understand your answer on 1, so thank you very much.

But on 2 I'm still not getting it. When would I need su to be enabled doing boot?
[SuperSU] CoolApps:
SuperSU will be start on boot so any apps which requires root which starts on boot will be granted root access if you have set that app to be granted root.
[SuperSU] dserodio:
SuperSU icon gone

I have a Nexus 5 and I'm running Stock Android 4.4.2. I unlocked the bootloader, rooted and installed SuperSU using CF-Auto-Root and everything was fine.

Then I installed Clockworkmod Touch, backed up the current ROM, and when it asked whether it should prevent the stock recovery from being automatically restored by the ROM, I chose yes (from what I've read later, this was my error). Next, when I ran SuperSU again it said the phone wasn't rooted, and running "su" from the adb shell didn't work either, so I installed CF-Auto-Root again (skipping the bootloader unlock part).

Now the SuperSU app icon is gone, but I can't reinstall it because the Play Store reports it as already installed. Running "su" from adb shell works. How can I reinstall the SuperSU app?

Thanks in advance
[SuperSU] Mittaa:
Even if Play Store say it installed, you can still install it ... !

Have you tried to un-install and then install?

Alternatively side load and flash from Phone.

If everything fails ... use Odin PC or recovery to flash CF-Auto-Root and SuperSU
[SuperSU] cmstlist:
The error you made is because:

- Android OTA updates include a file that reverts you to stock recovery on boot. Hence for years custom recoveries have looked for this file and flagged it to the user as an error.

- From 4.3 onwards, the root method became a bit more complex and required that the "revert to stock recovery" file be hijacked as a means of tricking the system into running scripts that grant you root. However custom recoveries written with the older logic will still flag that file and "fixing" it will unroot you.

The stupid thing is, this has been part of Android since before the Nexus 5 launched. There is no excuse for CWM Touch including this old logic on a Nexus 5 release! I can verify that the latest TWRP versions handle this correctly and do not give a bogus warning. In fact TWRP will offer to auto root if it doesn't detect any root components (but if you have some components left over from a botched unroot it might not offer).

In any case, download the latest SuperSU zip to your internal storage. Boot into CWM Touch again. Install the zip. IGNORE the warning this time and then reboot into system. You should have root again.
[SuperSU] dserodio:
Thanks for the detailed explanation, I followed your procedure and it worked.
[SuperSU] cybhunter:
Not sure if this a new problem or not,

I have been running team EOS4 version of 4.2 for over a year and decided to jump up to their version of 4.4 . The problem I was noticing was I couldn't (in android terminal) run 'su reboot' (busybox installed), it would claim 'No such tool'. Looking under catlog the entry is

886 Package Manager (W) Not granting permission.REBOOT to eu.chainfire.supersu (protectionLevel=18)

. I didn't encounter this problem in 4.2
[SuperSU] Upstreammiami:
Having issues with cm11 on the note 3 I flash the zip even tried the play store version... I get the app but when I open a rooted it app says I lost root... I tried with newest version and. 76 ver and same issues
[SuperSU] Prufta:
Try going on SU settings/Cyanogenmod/Respect CM Root Settings if its checked the option unchek it. It would work, that happened to me when I flashed Quantum release 3.12
[SuperSU] atamig:
SuperSu (1.86) problem with CM11

I have a problem with SuperSu and CM11 (see screenshot ). A reboot fixed the problem for short time.

The CM11 SU settings (Cyanogenmod/Respect CM Root Setting) are unchecked. What can I do to solve the problem?
[SuperSU] jorceshaman:
Did you flash or install from the Play Store? I had that error every time it updated but haven't had it since I started flashing.
[SuperSU] atamig:
I flashed it with twrp
[SuperSU] petesimon:
yay ^_^

Success on Chinese phone Jiayu G4A MTK6589T! Thanks! I really prefer SuperSU. "Superuser" was already in my ROM, but randomly flaky unresponsive and then it disappeared one day after I installed some apps from play store, and rebooted. I got a 'update' zip file another site and flashed this zip file in CWM (or similar) recovery mode. Now I can update SuperSU anytime. :cowboy:

My build.prop and a hardware-info text are attached. Those are also on pastebin here and here.

*EDIT* v1.89 update zip

http://d-h.st/Ivz

and

http://download.chainfire.eu/376/SuperSU/

v1.86 update zip

http://d-h.st/b1d

v1.65 update zip

http://download.chainfire.eu/351/

v1.30 update zip

http://d-h.st/9WL

yeah, like other people say: flash a zip file from the link above in recovery mode.
[SuperSU] theresident:
hi there, im trying to work with the latest 0.224 kitchen.. everything for now its ok, except the Supersu. Says that SuperSu its installed But not the binary file. Ofcourse its ok after i flash the update zip from chainfire, but my problem its WHY i cant root good my device from the start (with the kitchen)?

Any help is welcomed
[SuperSU] pizzaman79:
heads up about KNOX

I saw a video which promised rooting without tripping knox so i tried it

Galaxy S3, i9305, official 4.3 firmware.

Reboot into download mode: everything said official

Installed through Kingo_Android_Root_117.exe.

When opening SuperSU i got a warning "Unauthorized access has been blocked" in the statusbar and a "SuperSU has stopped" popup

Downloaded .apk, ran that through Astro. It reainstalled and now i had root

SuperSU asked to disable KNOX, i chose yes.

Used the remove root option of Kingo Root

It seems to hang for a few minutes, this is normal

(during which i got a call :-/)

"Remove root succesfull"

Reboot into download mode

Still says

Custom binary count: Yes (1 counts)

Current binary: custom

System status: custom

KNOX WARRANTY VOID: 1

Maybe i did something wrong

tl;dr: be careful of methods that promise to root without breaking KNOX
[SuperSU] Pons:
I don't know what the kitchen does, so... Crack open the flashable zip, look at the update binary, and do what it says, as far as adding stuff to the appropriate locations.
[SuperSU] CZ Eddie:
Galaxy S4 AT&T on 4.3 and 4.4.

For at least the last several months, on various clean wipes & various ROM's, I have one issue that has continued throughout.

When I go into SuperSU settings and tell it not to notify me every time it grants permissions to an app that already has permissions, it still notifies me anyways.

Anyone know how to make it stop doing that?

Drives me nuts that it has to tell me it granted TitaniumBackup and all my other apps, permissions, every time I open those apps. :)
[SuperSU] theresident:
Case closed.. I found modified kitchen with the latest supersu update. Works perfect now. SuperSu is the best, txh for your answere btw!

---------- Post added at 10:31 PM ---------- Previous post was at 10:25 PM ----------

Your phone didnt have knox before 20-30 days. If you did ota update its your falt that you are stuck now. But you can reset the binary counts with Triangle Away

... we all have 0x1 knox; but we dont care
[SuperSU] pizzaman79:
Woah, take it easy there. I'm not pointing any fingers. Just giving a friendly heads up to people who expect this method to not void their KNOX warranty. Triangle away won't restore this. For the moment i don't mind the knox status is tripped, but who knows what future consequences it may have.
[SuperSU] polobunny:
Did you use the fix permissions script? That's what broke it for me in the past.
[SuperSU] CZ Eddie:
Well, I use the fix-permissions in TWRP and also ROM Toolbox.

Dangit. Is there a way to un-break it?
[SuperSU] polobunny:
Chainfire and I looked into it, but couldn't really find anything. fix permissions is a freaking huge script that proves to be not all that needed and that ends up breaking more things than fixing.

I simply wiped everything and restored my Titanium Backup and never used it again. Without any issues.

You can try to find the culprit if you feel like it. :p
[SuperSU] Pkt_Lnt:
nevermind - replied without reading replies below
[SuperSU] u50r:
Hi Guys,

I'm having a bit of an issue I was hoping someone could help me resolve. So my root access has been a bit wonky for a few months now, it passes rootchecker and everything but some apps that need root tell me I don't have it.

Was trying to get one to work today and I think I narrowed the problem down to superuser, I had noticed that superuser hadn't logged anything for months and it wasn't adding any apps to the allow list. I uninstalled it and installed SuperSU hoping that would fix the issue but it brought to light a new one.

When I start up SuperSu it asks to update the binaries, I select Continue and then I chose "Normal" from the update methods, it then tells me that "INstallation Failed @" then exits when I hit OK.

This has gotta be whats causing my root to be wonky, if anyone could help me get this fixed I would really appreciate it.
[SuperSU] Pons:
[MENTION=5089020]u50r[/MENTION] Tried flashing the update zip via recovery, listed in OP?
[SuperSU] u50r:
+Unfortunately I don't have a microSD card kicking around.
[SuperSU] Pons:
I guess this depends on your device. Mine doesn't have a micorSD, and relies on internal storage/emulated microUSB. I'm guessing yours doesn't have this?
[SuperSU] u50r:
It has internal storage but don't know how you flash something from there, only method for flashing I know of is to put the zip on a sd card, where would I put it in the internal storage for it to be used for flash during boot?
[SuperSU] Chainfire:
For those running the Android 4.4 leak for the SGS4: https://plus.google.com/113517319477420052449/posts/BpEHngdaFEn
[SuperSU] Pons:
Nice, a quick fix. Now that's fast service. I'll test it out on my completely different device and ROM, to make sure nothing broke. And I love the disclaimer: "(Subject to change on my whim, of course)﻿" I did chuckle a little at it.
[SuperSU] guerouig:
in the list of supported devices (signature) i don't see s4 canadian version sgh-i337m. is there a different su version for those?
[SuperSU] Pons:
You're talking about the list of devices in Chainfire's signature? Pretty sure that's a list of devices he owns, not just devices supported by SuperSU.
[SuperSU] L.F.B.:
How about mobile odin? Ever root is workig with gs4 kitkat leaked rom?
[SuperSU] Mittaa:
Currently using CM11 ... wondering the same :o
[SuperSU] nexusmaniac:
Just to confirm, it's completely pointless to flash this on any other device? Thanks :)
[SuperSU] eLCruz:
Smooth update, as usual, on SGS2 T989 :thumbup:

Sent from Gallifrey using a Sonic Screwdriver via Tardis #5 :confused:
[SuperSU] Pons:
Sounds like it to me:
[SuperSU] cb0gus:
Checksums?

Thanks for SuperSU - works just fine with this Nexus 4 here.

I know, xmas is already over, but...could you provide checksum (MD5/SHA1) for these .zip files you release here?

For example, for the latest release I have:

MD5(UPDATE-SuperSU-v1.89.zip)= 9cfdf7032ef3f45abaa83f03fa7995a1

SHA1(UPDATE-SuperSU-v1.89.zip)= 74e508938e0afa71ec5bcbd9bee840df5241b80a

I assume I got the correct one, but it would be nice if you could post these checksums for your releases :)

Thanks.
[SuperSU] eddietah:
My playstore still show v1.86 is the latest.

There is no v1.89
[SuperSU] Pons:
Please see Chainfire's G+ post on this (the link is only the previous page).
[SuperSU] xI mEzMeRiZe Ix:
So how does this work when I update my ROM? I'm using CM11 and SuperSU seems to work a lot better than the built-in Superuser. Do I just flash the SuperSU zip after every ROM update or is that not necessary?
[SuperSU] spankymo:
you can go to the supersu settings and click Install SuperSU Backup Script under CUSTOM ROM. this way, supersu will survive ROM flashes.
[SuperSU] xI mEzMeRiZe Ix:
Will just flashing the SuperSU zip after an update take care of it?

Sent from my LG G2
[SuperSU] Pons:
Yes, but why flash two zips, when you can flash?
[SuperSU] xI mEzMeRiZe Ix:
I use Cyandelta so it does it automatically.

Sent from my LG G2
[SuperSU] spankymo:
sure, it's your choice. but as the other guy said, why flash 2 zips when you can skip flashing one of them each and every time (regardless of whether it's done automatically or otherwise)?
[SuperSU] xI mEzMeRiZe Ix:
Well if I ever have a major issue with SuperSU, I can always flash my ROM zip to wipe it out. If I used the method suggested here, SuperSU would always survive a ROM flash and I would have to wipe to rectify it. The way I will do it allows me to keep supersu and have the ability to get rid of it easily if I ever need to.

Sent from my LG G2
[SuperSU] Pons:
No, you'd just delete the script in /system/addon.d then reflash the ROM or superuser. How many times have you or do you uninstall SuperSU? But it's your choice.
[SuperSU] spankymo:
sounds like a plan.

or, you can just delete /system/addon.d/99-supersu.sh before flashing a ROM zip so supersu won't get restored.
[SuperSU] xI mEzMeRiZe Ix:
Not often, it'll just be a method that allows for a fail safe. Easier than remembering the file to delete and works if any issues are preventing the OS from running properly.

Sent from my LG G2
[SuperSU] doncaruana:
Is it possible to get a set of the 1.86 binaries other than pulling from the market? Or maybe the flash able zip version?

Edit: nevermind - Found it on chainfire's site.
[SuperSU] gpvecchi:
Guys, I can't install this on CM... May someone help, please?

I flash from recovery, I find superSU in drawer, but if I open an app that requires root it says that I don't have root...

If I check SuperUser in settings I still have all the authorized apps...
[SuperSU] jorceshaman:
Exactly why I just spend the extra 5 seconds to flash the zip each time. It only adds like 10 seconds or less to my update time.
[SuperSU] mjsztainbok:
I just updated my Note 2 to a rooted stock 4.3 ROM and since updating I find that the daemonsu process is nearly always at 100% on one core, making my phone slow to use and draining the battery quicker.

I saw earlier in the post that some people were getting this with Adaway. However I'm not running this so it is something different.

The only rooted apps I have installed with permissions granted are:

- Titanium Backup

- ES File Explorer

- FolderMount

- Build.prop Editor

- FasterGPS

Any thoughts how to fix this and what the cause of it is?
[SuperSU] Phil3759:
What exactly does this command that cannot be done through installer shell script?

su --install
[SuperSU] Narenji89:
How did you figure out that daemonsu process is always running?
[SuperSU] mjsztainbok:
By using SystemPanel
[SuperSU] Chainfire:
Uninstall them one by one and reinstall them, one by one, with a few hours in between, and rebooting, and checking if the problem comes back, so you know which app it is ... maybe then we can find out what the issue is.

At the moment it takes care of hooking startup on Samsung 4.4 ROMs, but (when I have time) I will be moving more and more of the install script into the binary, as the installer code is currently duplicated about 5 times across different projects.
[SuperSU] Chainfire:
http://xdaforums.com/showthread.php?t=2607273

I was waiting for Substrate to be updated to SELinux Enforcing to build this. Seems somebody beat me to the (non-Enforcing) punch. I'm not dropping this from my to-do list though.
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION]: I just want to tell you: THANKS. I really hope god will bless you for all this awesome work and heart blood you put into your projects. You're one of my idols and most respected members here. Never give up, keep your pimp hands strong! :cowboy:
[SuperSU] BrokenWish:
The same way if u were putting it on your sd card...you ll c a folder called sd card n the a download folder just throw it in there
[SuperSU] Frank Westlake:
Chainfire is trying to not point the finger but I'll be less gentle. The high CPU usage is probably one application which is using 'su' in a seperate process and that process got stuck in a loop. These seperate process don't die when the application stops so you need to uninstall the applications one at a time (reboot after each) and use the device for a day or two to find out which one is the problem. Then let us know which.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] ValenteL:
PDA: N9005XXUENA6 CSC: N9005OXXENA5 MODEM: N9005XXUENA2 XEO

New Rom KitKat 4.4.2 Note 3 to Poland rooted alright whit UPDATE-SuperSU-v1.89.zip

Good work. Thank You [MENTION=631273]Chainfire[/MENTION]
[SuperSU] Pianoman144:
What cwm recovery are you using? Link maybe? Thanks..

Gesendet von meinem SM-N9005
[SuperSU] ValenteL:
This n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar from HERE.

Link: http://d-h.st/users/xiaolu/?fld_id=31400

EDIT 20.01.2014 : Updated SuperSU to v1.91 today.

Also new CWM recovery on that Thread.
[SuperSU] hotcell:
Anyone tried to upgrade Xperia ZR C5503 stock .67 (4.2.2) successfully rooted with Bin4ry v33 tool (in mode 0; i.e. LB, no recovery) to 4.3 builld .569 via OTA so that root remains utilizing v1.89 SuperSU Survival mode?
[SuperSU] simonsalo:
Compatible with new i9506 Galaxy S4

Is SuperSU compatible with the new Snapdragon 800 version of the S4 - i9506?
[SuperSU] marbulas:
I think 1.89 loses su permission itself.

If I turn on my phone and keep turn on about few hours, I can't do anything via su permission. Popup window for requiring su permission and Popup message when su permisssion granted doesn't show on screen.
[SuperSU] xI mEzMeRiZe Ix:
Can't seem to get this to work on CM11. When I install it from the Play Store, it asks for superuser access and installs just fine, but when I reboot and use an app that requires root, it acts like it can't find root. Same thing happens when I flash the zip to install it.
[SuperSU] Frank Westlake:
Since a couple of issues have been reported I'll add that I've had no trouble with 1.85, 1.86, and 1.89 on my vzw Note 3(MI9/dlV). I'm writing an application which holds 'su' for multiple tasks and I spend a lot of time in ConnectBot and the jacpal terminal while writing it.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] kingston73:
Same thing happening here.
[SuperSU] xI mEzMeRiZe Ix:
I think it has something to do with changes in the recent nightlies. Before today, SuperSU always worked fine and I only needed it because certain apps wouldn't work with the built-in Superuser app, but now SuperSU won't install and the built-in Superuser works with everything.

Sent from my LG G2
[SuperSU] Chainfire:
I'll look at it within a few days. (Note to self, use the S3)

EDIT: problem confirmed, but I gtg, will look at a fix when I can
[SuperSU] H3llstorm:
I'm using SuperSU v1.86 and sometimes I get notifications that I'm not rooted.

Sometimes I close & re-open the app and it works. Sometimes my phone locks up I have to reboot.

Should I update to v1.89 or wait for the next update?
[SuperSU] Frank Westlake:
If it's only one application then maybe it doesn't know how to check for root access, or maybe it's having trouble managing external processes.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] boyheadkick:
wow, and i thought it was just because of some of the tweaks i do, but i got it the same problem too..i tried reflashing the zip flashable file but same thing, so tried reinstalling SuperSU from Playstore and it works fine now