yashsingh1/xdaforums huggingface dataset:
[SuperSU] osm0sis:
Nothing to worry about. It's just this:

https://github.com/CyanogenMod/andr...mmit/da36597955e30b8139f2c64ecb9687fac898c1b2

or the one before it here:

https://github.com/CyanogenMod/andr...mmit/1153ae5ad9a25198e4edfa7ff9b0bce7f9d40220

The SuperSU zip doesn't even have a real binary, just a shell script, which is probably why it triggers the warning. Either way, using an older one (or being seen as such) gives it wider compatibility so it should stay as it is. :)
[SuperSU] Rangs641:
Hello All, I maybe asking a stupid question, but I will ask it anyway! I have a rooted galaxy S3 running neat rom v7.6. My question is related to ram usage by supersu. I see that supersu runs all the time in the background. So if I kill supersu using advanced task killer, it releases around 30mb of ram. But after some time the process comes back to life. Is this normal? Will the process run all the time in the background?? Is there anyway to make it not do that?

P.S. I have the latest version of Supersu installed.
[SuperSU] Pkt_Lnt:
Unroot your phone and remove all root apps to stop it from running. It has to run to control root access, the only way to stop it is to remove it.
[SuperSU] Rangs641:
I guess it really was a stupid question. Using an android without root is like using a p.... that doesnt e....! Where's the fun in it!!! :D Thanks for the reply pal.
[SuperSU] andrei1015:
I've had some problems since v2 (or maybe 4.4.4). Everything is on infinite loading. Anything I try to change or to view, doesn't load 90% of the time. At least I can authorize apps.

What do you make of this? Yes I tried v2.0.1.
[SuperSU] Chainfire:
v2.01 released

v2.01 released - RELEASE NOTES
[SuperSU] karlad:
:thumbup:
[SuperSU] osm0sis:
Great stuff! I've been following your documentation/updates on context switching, and was wondering if it'd be possible to implement that with the su interactive shell.

I'd like to execute "su --context u:r:untrusted_app:s0" and have a # prompt where all my entered commands execute under that context. Currently it seems to just hang.

Thanks for your consideration. :)
[SuperSU] Chainfire:
There's no terminal access that way. Have you tried simply typing "id"<enter> and seeing if it outputs anything?
[SuperSU] antigone:
Hi chainfire, I've just rooted my Vega A880 using towelroot. But after I installed Su from PlayStore, it keep telling me to update binary and always fail. What can I do? I've searched for solution but none worked for me?

TIA for the help!
[SuperSU] osm0sis:
The $ prompt has an untrusted_app context, but the # prompt has an init context. Is there any way to change the context of the root (#) prompt? If not, could there be? :fingers-crossed:
[SuperSU] gpvecchi:
So 2.01 works even for L or do I still have to use the specific version? Thanks!
[SuperSU] James62370:
I believe the 2.0.1 update was specifically for Android L compatibility so you should be good.
[SuperSU] joel.bourquard:
Some experiments on Android L dev preview

Hi Chainfire,

How are you?

I'm experimenting with some code on Android L dev preview (Nexus 5) + SuperSU 2.01:

Process myProcess = new ProcessBuilder("/system/xbin/su", "--version").start();
InputStream is = myProcess.getInputStream();
StringBuilder result = new StringBuilder();
int c;
while ((c = is.read()) != -1)
result.append((char)c);
is.close();
Log.i(tag, "Output of command = " + result.toString());
myProcess.waitFor();

The above code works (ie: it logs a line containing SuperSU's binary version).

But if I replace the first line with:

Process myProcess = new ProcessBuilder("/system/xbin/su", "-c", "/system/bin/ps").start();

Then I don't get any output. In other words: is it even possible to communicate thru stdout/stdin between a root process and an app on that ROM? :eek:

Edit: WOW! The system suddenly rebooted, rebuilt its dex files and now it works magically! That ROM is definitely *not* stable enough in order to draw conclusions right away!

Edit 2: And after un-installing & reinstalling the test app, the problem is back! It seems to be a problem with freshly installed apps, until a dex rebuild (or something else) is triggered, after which it works.

Edit 3: Seems to be a SuperSU bug! Asking SuperSU to forget the app and letting it ask for root access again resolves the problem. So if you have root half-working with an app, just ask SuperSU to forget and let it re-authenticate. I notified Chainfire about the problem.
[SuperSU] rayQ111:
HI CHAIN FIRE

Bro

thank you for all your GR8 and awesome work

bro i have a question please answer ?

in your 1st post you said the phone needs to be rooted ? right

so SU wont root my phone ? :(

how can i root my OPPO FIND 7 QHD international version ?

please explain

thanks in advance
[SuperSU] Chainfire:
Yeah there are still some issues with L and SuperSU, I know.

Seems to be a bit of crashing going on inside ART, needs more investigation.

As one example, try calling "su" in a semi-fast loop, after a few dozen calls, the system explodes.
[SuperSU] Pons:
I don't know much about your device, but you need a custom recovery which allows /system read-write access. If you don't have that, then no, SuperSU won't do anything for you, nor grant you this.
[SuperSU] joel.bourquard:
Thanks for your response :)

I think the "re-authentication" issue (ie: root working strangely after un-installing & reinstalling a root app) happens if (and only if) that app's UID changes. From what I recall, it might happen on earlier ROMs too - but it's more systematic on Android L. For me it happens everytime, and goes away by telling SuperSU to forget that app.

Another way to bomb the system is to run something like "pm uninstall somepackagename" from an app. The system never recovers :D
[SuperSU] xunholyx:
There's a guide for rooting it with links to the zips you will need at the Oppo Forums site.

http://www.oppoforums.com/threads/guide-how-to-install-coloros-2-0-gapps-root-on-find-7-x9077.17084/
[SuperSU] esoomenona:
Is it necessary to remove my current SuperUser? Will anything conflict?
[SuperSU] knightnz:
Did SuperUser Elite actually do anything in the end, or was it basically just a "Donate" option?

Thanks for the app Chainfire.
[SuperSU] DarkhShadow:
SuperUser elite adds a number of features

And kudos to you chainfire!

Sent from my ice cream powered Nexus S
[SuperSU] Chainfire:
No, apparently you don't. Because those log files also only state that error 0 has occured and that the installation has been aborted. If you've ever had error 0, you'd know that.

As long as you don't use it, you can keep it on there as well. It only becomes a "problem" when it reinstalls its own binary (which it does not do automatically). You'd then be using Superuser again instead of SuperSU. Launching SuperSU and letting it install its binary in turn switches you back to SuperSU.

I think it does unlock some options, yeah.
[SuperSU] crachel:
Flashed via CWM 5.8.0.2 on my Nexus S (4.0.3 AOSP userdebug) and everything went smoothly and is working beautifully

One very minor thing is the "Upgrade to Pro" button crashes the app if no Android Market is installed
[SuperSU] retnuh:
Originally Posted by retnuh:

Installed SuperSU from the Play Store. It is the current version. I am rooted and running stock GB on my AT&T SGS2. Now TB Pro is stuck on "Asking for root rights". Also, Root Checker stopped working. I uninstalled SuperSU and everything is still screwed up. Was this app not released for my phone and rom?

Originally Posted by Chainfire:

Yeah try reinstalling SuperSU. Then start Superuser, go to preferences, and let Superuser update it's binary. Then uninstall SuperSU.

Superuser shows there is an update for the binary; however, when it tries to update, it fails at "Gaining root access". Will not get past this point.
[SuperSU] Chainfire:
So... I've now tested SuperSU on about 20 different phones and tablets, on anything from Eclair to ICS, and I simply cannot get the crash or "no root access" problem to occur.

If anybody has any ideas whatsoever, let me know. At one point I had somebody on the chat who had this problem, but it somehow sorted itself out and didn't occur again.

It's maddening! :D

@retnuh: any chance we can talk live on IRC or gtalk ?
[SuperSU] retnuh:
Thanks Chainfire. But I am uneducated in all of this I don't even know how to use IRC or Gtalk.
[SuperSU] DarkhShadow:
I haven't had any app fail to get root access, only problem I have had is root explorer spazzing out and not working(guessing they need to update it?)

Sent from my ice cream powered Nexus S
[SuperSU] sparksco:
I only had one little glitch on reboot with avast installed as root. The 10 second prompt didn't pop up fast enough for me to allow permissions. I fixed it by going into SuperSU and selecting "Grant" as it selects deny by default. Is there a way to allow more then 10 seconds for all the apps to load after a reboot?
[SuperSU] dbus08:
Has anyone had to opportunity to attempt to use this app on a Motorola Droid X and accept the .621 OTA (new GB build for droid x), and remain rooted?

Just wondering because my headphone jack is broken on my X and when I eventually return it because its under warranty i would like a way back to ICS.

But great work.
[SuperSU] Chainfire:
I've not seen a problem with root explorer ... :)

No, at the moment there isn't.
[SuperSU] DarkhShadow:
Must just be me, when I open it it fc or it won't let me open any folders, like /system(it just says they don't exist)

Sent from my ice cream powered Nexus S
[SuperSU] Benzoman:
Stupid question alert... how do I uninstall original superuser?

Option not available in settings or the market/play store.

I'm tired and the answer is probably right in front of my face. :(
[SuperSU] housry23:
I have had a problem with Root Explorer. Only app I have had a prob with :). When I start Root Explorer it just has a black screen for about 15 seconds and then it tells me it couldn't get root permission and to restart the app. In the log it has a red # while everything else has green.

Thanks for all you do Chainfire. I love your mobile Odin Pro app! Anyway, just wanted to let you know there is a 2nd person having issues with Root Explorer. I have an app called Rom Toolbox by JRummy and I have no problem using it's root file manager, so Root Explorer is really not needed.
[SuperSU] DarkhShadow:
You need a root explorer and to delete it from /system/app

Sent from my ice cream powered Nexus S
[SuperSU] Benzoman:
Thanks. I think thats even posted already... told you I was tired ;)
[SuperSU] Moon Shadow - NM:
Chainfire,

jsgraphicart in the DX2 section posted a link to your new SuperSU app. Here is the post I made back on that thread. I'm cross-posting it here. I'd like to work with you to see if we can get this working on CM7DX2. The only issue I can foresee is the original Superuser APK seems to remain persistent, and I think it may be due to our 2nd-init. I'm not 100% sure, and I will be talking with dragonzkiller, the developer for CM7DX2 about the original Superuser APK.

Here is my post in it's entirety:

Thanks! Ciao!
[SuperSU] virus786:
Very nice. ;-)

Will give this a few days to mature then I'll give it a go.

Also, does logging and notifications use a lot of cpu cycles?
[SuperSU] bombadier:
Installed the app to test then uninstalled,have reinstalled and when I open SuperSu I get an error "There is no SU binary installed,and SuperSU cannot install it.This is a problem!" Thing is, it is installed, had no problems when I first installed it,any ideas how to fix? cheers
[SuperSU] junkmail9:
Both SD Maid and Cache Cleaner are working fine for me on Kindle Fire. No apps hanging up so far.
[SuperSU] voryzen:
working awesome here. thanks vm
[SuperSU] nexus.prime:
https://play.google.com/store/apps/details?id=com.funkyfresh.samba

Samba Filesharing got FC :(
[SuperSU] hadi_rena:
In my case Samba File Sharing running slower than usual. When it's enable or disable file sharing android pop up whether to wait or force close.

Choosing Wait then everything is OK.
[SuperSU] Kurupt1:
Fixed for me everything working great thanks chainfya
[SuperSU] lukeborn:
I have wondered this as well I installed this on the gingerbread revolver ROM and suddenly lost all root, did I do something wrong? I mean obviously unless it was a zip file to flash I need root access to install right?
[SuperSU] voryzen:
You can remove the old one. It's just an app, that handles your root access.
[SuperSU] sparksco:
When you flash the CWM zip posted in the OP it will remove superuser if present so no need to remove it! Just flash and reboot, simple!
[SuperSU] webdroidmt:
Been using this on my TouchPad with CM9 for 3+ weeks without issue. But this morning when I powered up, I wanted to go into SuperSU settings and I was greeted with the spinning load icon that wouldn't stop. All root functions for my apps were fine, including No Frills CPU, which gets applied at startup.

I was able to back out of the spinning load icon, so I just rebooted but upon reboot, still couldn't get into the SuperSU app. Again, all root privilege functions seemed to be working. This time I cleared data, rebooted and I was able to get into the app. I really like the app and this was just a minor hiccup but I figured I'd report it.

I very rarely went into the app for anything since I installed it, so I'm not sure if this was some sort of anomaly, or it's consistent. I'll keep an eye on it over the next little while. I wanna' thank Chainfire for creating this app, looks good and works good as well.

Mike T
[SuperSU] Grevane:
Problems with SuperSU Pro "Full Content" logging

Hi all,

I've discovered that with some apps there are issues if you switch on "Full Content" logging instead of the "Access Only" default option, if you've purchased SuperSU Pro.

The workaround is easy, just switch back to the "Access Only" option (for both the "Global Default" under settings or any apps you've specifically switched the "Full Content" logging option on for).

I found Root Explorer became extremely slow with "Full Content" logging on, the /sbin folder for some reason could take up to 45seconds to open. And with the Global Default set to "Full Content" logging, some apps struggled to acquire root the first time, I guess within the allotted 9 seconds.

Other than that, SuperSU seems to work great.
[SuperSU] segv11:
Also terminal emulators don't echo your commands correctly with "full content". This is presumably because the shell sees a pipe instead of a pty on STDIN, and decides that it is not interactive. Again, not a surprising side effect, and an easy work-around.
[SuperSU] benslgdroid:
I am on an optimus v running backside iho and just installed your app which is great but I can't find temporary unroot. Can you please help me? Thank you.
[SuperSU] theone10:
Just unchech enable superuser
[SuperSU] Pons:
I have a request/improvement: in the app list, how about order them alphabetically?
[SuperSU] Grevane:
+1

Any options to sort alphabetically/root date/install date/size etc...would be great!
[SuperSU] k2trill:
Instead of lying to everyone like every app that we try doesn't work except when u try it like wifi tether and telling us the devs need to make their apps that have been around compatible with your newer app, why not just make ur app and binaries compatible with however their apps manage root???? So far no real developers wanna touch this because it takes too long to prompt and half the apps won't work with it! U should at least make it work seamlessly with wifi tether since 50% of rooters root just for that feature. It's not cool that you keep telling us to "contact the dev" and "it worked for me" like ALL OF US R DOING SOMETHING WRONG! It does NOT work with WiFi Tether! YOU should contact the devs since YOU are the one selling the app! I wish I knew it didn't work for real before I spent my money on it.....:mad:

EDIT: even the uninstall/cleanup feature doesn't work!!!
[SuperSU] theone10:
Root explorer is working great for me with supersu. I dont use wife tether app. Since the phone comes it with one from the maker.
[SuperSU] k2trill:
I bought this the day it was released because he is supposed to be from a "recognized developer" but I should have known better since I have gotten ZERO use from Chainfire 3D Pro....
[SuperSU] dimebagdan65:
To second CF's response... you're doing it wrong lol works for me no problem. Haven't found a single app that has issues with it
[SuperSU] Chainfire:
An issue has been found, identified, and hopefully fixed regarding performance in some cases - including Root Explorer (finally succeeded in replicating the problem). It's currently in the hands of some users and the Root Explorer developers for testing.

I'm not sure whether it could be related to the Samba issue and/or issues with other apps, but if you have one of these problems be sure to re-check with the next updated version. (and comment here about if the problem is or isn't fixed).

EDIT #1: The Root Explorer guys claim the issue is fixed :)

EDIT #2: Other testers also report this issue should now be solved. Expect an update soon.

@k2trill

You misunderstand me when I say it works for me. I'm not denying there could be a problem with SuperSU, but as long as I cannot reproduce the issue, I cannot fix the issue.

That being said, obviously you are unhappy with SuperSU. I'd be happy to refund your (or anybody else who feels the same) purchase. If you find the transaction in Google Checkout/Wallet, there's an option to request a refund.

@all

I don't comment much here, but don't make the mistake of thinking I'm not following or reading the thread.
[SuperSU] sportscrazed2:
Is it safe to have cyandelta flash the zip with each update? The normal install doesn't work for me so I find myself having to use the recovery method anyway after each nightly. I'm assuming its probably a good idea to turn off auto updates in the play store as well?
[SuperSU] D3LTA9:
First I would like to thank you for all the excellent work you have done for the android community.

Second, I seem to be having an issue with root and titanium backup on the Android L dev preview. Root seems to be fine with all other apps I have tried like root explorer and terminal emulator. But on titanium backup I get error saying it could not acquire root using the /system/xbin/su command. Superuser is prompting me like normal and I allow root access but then get this error.

Have I missed something? or is this just a issue with Android L atm?

Thanks for any help.
[SuperSU] osm0sis:
It's TiBU's issue, not SuperSU's. If you switch from their included busybox to the system one you get past the root check just fine. Then it'll eat **** completely because it's looking for Dalvik, wipe the ART cache in the process and send you to a hung bootani. TiBU tweeted that they're aware and are working on ART support.
[SuperSU] D3LTA9:
ah I see, initially thought it likely would be something to do with ART but then I did not see it in the thread of apps not working properly on the dev preview of L. oh well, hopefully Titanium Track releases an updated working version soon.
[SuperSU] ChungHung.Chen:
I'm using CyanDelta to upgrade CM11 nightly for my XT910(umts_spyder).

And I have SuperSU zip in settings for every flash w/o any problem.

BTW, I'm used to disable all auto-update in play store.
[SuperSU] Breezer23:
Anyone have 1.94 available for download?
[SuperSU] ikslawlok:
http://bit.ly/1vuoEFS
[SuperSU] Breezer23:
Flashable zip isn't helpful or I would have used it already.
[SuperSU] ikslawlok:
So tell it in your ask ;)
[SuperSU] rowdyw:
[MENTION=631273]Chainfire[/MENTION], after updating to v2.01 if I change the SuperSU app icon in the settings, the icon is removed from my homescreen after reboot.

The icon still appears in the app drawer, but it disappears from any homescreen it is on.
[SuperSU] osm0sis:
... Unzip?
[SuperSU] andrei1015:
Anyone else?
[SuperSU] joel.bourquard:
I've never seen this kind of issue. Did you check out the log for anything suspicious?
[SuperSU] remotehugger:
has always happened to me after changing icon too - just have to add it back to your home screen - :)

From my Giddy Thrive
[SuperSU] The Gingerbread Man:
I have 1 thing to add to this, slightly off topic but might be helpful to others. I primarily use titanium to back up WiFi network / SMS / call logs using the back up / restore XML featue. This actually works on L even though titanium cannot find root. I used titanium to restore all these features from a kit kat build to a clean flash on L.
[SuperSU] nilanko:
How to disable the onscreen notification "[app] has been granted super user permission for an interactive shell"?
[SuperSU] Pons:
Uncheck Show notifications.
[SuperSU] visceralpsyche:
This time around that's not working. It continues to disappear on reboot.
[SuperSU] Chainfire:
I've seen this happen once yesterday. Are you on 4.4.4 now or on L? ART or Dalvik?

I think it's related to another issue I've seen, which causes an internal VM crash sometimes, but not sure yet. Can you adb shell, manually kill -9 the eu.chainfire.supersu app and restart it from the launcher, see if it works then? That did solve the issue for me. Or does it just never work, even not after reboots?

I don't know what's going on, but I do know this is not a v2.01 specific thing, as nothing has changed that could influence that.
[SuperSU] osm0sis:
So is this a possibility, or too difficult to extend at the moment?:

There are some definite usage cases where this would be handy for binary execution on /data, we could just specify the context when calling the prompt, like "su --context u:r:untrusted_app:s0". su could just check to see if there's another argument (like -c) after --context; if so execute the supplied command, and if not then open the interactive # shell with the specified context. That would be slick. :cool: :)
[SuperSU] nilanko:
thanks
[SuperSU] andrei1015:
Nexus S 4.4.4 always latest nightly. And I'm on Dalvik. The last time I tried changing to ART my phone died. And running adb shell kill -9 eu.chainfire.supersu returns /system/bin/sh: kill: eu.chainfire.supersu: arguments must be jobs or process IDs and since I haven't used this ever, I have no idea why it's not working. However, I did try adb shell am force-stop eu.chainfire.supersu and it didn't work. Managed to get the backup script installed which is a win. Thank you for your support :D
[SuperSU] 白い熊:
Bumping this, still present.

Anyone have an idea what's the problem?

--

白い熊
[SuperSU] Chainfire:
The below is not an answer to the above. Possibly making this post and your last two post redundant.

Either something is not working, you don't know what you're doing, or I don't understand what you're saying.

su --context u:r:untrusted_app:s0 will generally give you a silent terminal. i.e. what you type is being executed, and you get to see the results. However, you don't see what you type and do not get a prompt. So just typing "id" followed by pressing enter in here should show you output.

su --context u:r:untrusted_app:s0 -c id will execute the command "id" as untrusted_app and return.

If either of these things does not work as described, then there is something wrong.
[SuperSU] osm0sis:
Ah, my apologies. I didn't catch your meaning! Okay, great, it actually does work! Output of id is untrusted_app from the silent terminal, like you said. Thanks! :D

So I guess my real request should have been: any way to change context for the interactive shell and still have the terminal not silent, e.g. "root@flo:/data/local/ #" like normal? :)
[SuperSU] Chainfire:
Use system_app :) Maybe sometime I'll port this to untrusted_app but it's a ****load of hassle for very little gain
[SuperSU] osm0sis:
Haha perfect! Works! I notice "su --context u:r:system_app:s0" outputs this though:

sh: No controlling tty: open /dev/tty: No such device or address
sh: warning: won't have full job control

Any worries/things to fix there? :)
[SuperSU] justforreply:
Disable cm root manager.

Hi, I want to completely disable cm root manager and install supersu in my rom based on cm 11, what i have to do ?
[SuperSU] Pons:
Flash the zip linked to in the OP.