yashsingh1/xdaforums huggingface dataset:
[SuperSU] Mike B.:
The PRO unlocker is just an apk like any other and while you need to go to the Play Store or Amazon to purchase it, once it's installed it will add the PRO functionality to your installed SuperSU whether that store is still enabled or not. You would only need to reinstall/enable the store you bought it from to download the occasional unlocker updates.
[SuperSU] jesssiii:
I'm fairly sure for apps purchased from Amazon store you must have the store installed to function. Which is why I stopped using Amazon apps. Things could have changed in the last couple years though.

VZW LG G2
[SuperSU] jwds1978:
It's up to the publisher whether or not to use their DRM wrapper.
[SuperSU] StratOS_HTC:
Just a question. In 2.46, 2.47 and 2.48 the binary is v2.45 ?

Or I'm doing or asking something wrong, it's just a app SuperSu version, couse binary su is only 2.45.

Need some feedback for it.

Galaxy Core 2 G355HN

Regards.
[SuperSU] Mike B.:
As mentioned countless times, the 'su' binary is updated much less often than the superuser.apk. The binary corresponding to the current SuperSU 2.46 is indeed version 2.45. If you wish to discuss beta versions, it's best to do so in the Beta thread. Note that if you use the UPDATE-SuperSU-vxxxx.ZIP files, the correct binary is always included.
[SuperSU] jibmunk:
I'm using Supersu pro on a rom that already had a superuser app. The settings for the built-in app are integrated in the system settings, as well as a setting in Developer Options where you can choose between enabling root acces for Apps, ADB, or Apps and ADB. While using Supersu instead of the built in app, is it better to disable the other Superuser settings, or should I leave them enabled? Also, should I ebable/disable them from the Superuser menu under Settings, or from Developer Options? Which would be safer? I searched around already and couldn't find a similar question.
[SuperSU] Pkt_Lnt:
When you flash SuperSU, it deletes superuser. As you said in your first sentence, "had a superuser app".
[SuperSU] egingell:
Someone should suggest to [MENTION=631273]Chainfire[/MENTION] to add a dummy class which is the same name as the class that Settings option links to, which is hidden from the app drawer, that redirects to SuperSU.

Oh, I guess I just did. :)

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] NeoLogY:
You are right. Just the app, binary on v2.46 2.47 2.48 still using 2.45. Every one get the same. No problem with that. :)

Sent from here to there
[SuperSU] jibmunk:
That didn't fully answer my question. Or were you implying that because it deletes the original Superuser.apk, it makes absolutely no difference whether or not I enable/disable the original superuser? I remember reading somewhere that you're supposed to disable superuser access from settings if you use supersu, I just can't remember where I read that. Another question: is it normal that my SuperSu has the old icon (the emblem) as opposed to the blue-green icon shown in the Play Store? I got it from Google Play so its strange that by default the icon is different. Tried redownloading a few times and no change. Same thing happens with the icons of the addons for FX File Explorer, those too are different from the ones in the store.
[SuperSU] Pkt_Lnt:
How can you disable something that does not exist? The blue green icon is material design, only on lollipop. Change it in SuperSU settings.
[SuperSU] shinra00:
Quotes ..."In the SuperSU settings, there is a setting called something like "Respect Cyanogenmod Settings". Uncheck that."...

and

..."in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).

after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done."...
[SuperSU] Pkt_Lnt:
Thanks, but you quoted the wrong person. You quoted the helper, not the one with the question.
[SuperSU] puterboy:
Is this an error?

I am running rsync under su and having some occasional hangs (which may or may not be related to supersu). Technically, because of issues with sshdroidpro, I am running:

ssh -q -x -l u0_a400 <android> su -c path-to-rsync <rsync-args>​

Once, when running 'ps', I randomly saw the following:

app_process /system/bin com.android.commands.am.Am broadcast --user 0 -a eu.chainfire.supersu.NativeAccess --es su_appname app_user_10500 --ei su_fromuid 10500 --ei su_access 2 --ei su_touid 0 --es su_cmd /data/jjk/bin/rsync --server --sender --numeric-ids - perms --owner --group -D --links --hard-links --times --block-size_2048 --recursive --checksum-seed_32761 --one-file-system --omit-dir-times . /data/ --ei su_code 942721 --ei su_uid_mismatch 1 -n eu.chainfire.supersu/.NativeAccessReceiver​

Is "su_uid_mismatch 1" an error?

Is this all something I should be concerned about or is this a "normal" internal broadcast message that I just happened to randomly catch when running 'ps'?

Thanks
[SuperSU] Cheps01:
Hello,

I tried with these steps but the result is the same, the system reboot and stay in the logo start minutes and minutes....and not finish...

Is normal that spend more than 10 minutes to start??

Thanks.

Regards.
[SuperSU] Pkt_Lnt:
Try beta 2.48, the beta thread is linked in post 1 and you can download from there. It has solved the install bootloop for some.
[SuperSU] MIchel2503:
I will get black screen

I will get black screen now. Nothing happen. Do you know what i need to do right now?
[SuperSU] intruder666:
I have a car head unit device (ARM Cortex A9 MST786) with Android 4.1. And currently there is a ClockworkMod Superuser app installed as a root manger and it works fine. Also there is BusyBox 1.2x installed. My goal is to replace Superuser with SuperSU. An important thing to note is that there is no recovery available on this device, so it's not possible to install SuperSU via recovery. When I run SuperSU and it says su binary needs to be updated - I grant root permission to SuperSU with Superuser app, but SuperSU fails to update su binary with "Installation failed!" message. Is there a way to find out what exactly causes this error and fix it? Are there some logs written by SuperSU so I can check what exactly goes wrong?

Thanks.
[SuperSU] AvgPhoneUser:
I really do not think you can replace it without recovery... But CWM superuser is pretty nice tho.

I think there are logs in CWM superuser, though I am not sure. And if there are, try to see what did supersu try to do. Enable logging>full content if there is such an option.

Also, it is a car device so i am not sure why you would need supersu for it, CWM superuser is enough for a car device :)
[SuperSU] intruder666:
I didn't find such functionality in CWM Superuser (this is one of the reasons why I want to switch it to SuperSU).

Well, CWM Superuser's popup has too big height to nicely fit into display, and it also has those unconfigurable 3 seconds delay for clicking "Allow" button, and it doesn't log the full commands. And also I'm just curious why if SuperSU gets root permission it still can't succeed in updating binary and making all other things it requires to become root manager on a device. I know that on many smartphones SuperSU successfully updates su binary of CWM Superuser without using a recovery.

Don't know whether it's important, but originally the device was rooted using Baidu Root app. After that, CWM Superuser was installed and it was able to update su binary. SuperSU was not able to properly update su binary neither of Baidu nor when CWM Superuser took over. I even tried to manually replace su binary to the one I've got from inside of SuperSU apk file, but this was obviously not enough to make SuperSU work properly and capture root requests.

Maybe the author of SuperSU may shed some light on this situation.
[SuperSU] khairulez:
At my side,that step to flash SuperSU always successfull.sorry if that method not successfull to you.
[SuperSU] NeoLogY:
Not sure if this help, but you might want to look at Kingo(1 of the One Click Root method). It root by exploit and install SuperSU as root admin. Not sure it will successfully reroot your device, but if it do, will be much easier to update recent SuperSU instead of trying to replace CWM Superuser with it.

But if [MENTION=631273]Chainfire[/MENTION] himself kick the ball, I believe will be easier for you to reach your goal

Good luck.

Sent from here to there
[SuperSU] Johnny424:
maybe i am blind but i do not see the link in the op as stated above for the 2.48 beta version. i did find the 2.48 apk beta version but does anyone have the 2.48 cwm/odin version? i am a m9 user and cant get this biiaaattcchhh to install for the life of me :D

Edit.. got it
[SuperSU] Mike B.:
This is the thread for the STABLE releases. The links to the BETA versions are in the

BETA thread

!
[SuperSU] PresidentMcCain:
SuperSU 2.46 stopped working on CM12.1 after syncing today. Getting "no su binary" error when opening the app after flashing new ROM and then UPDATE-SuperSU2.46.zip as I usually do. I also tried flashing BETA-SuperSU2.48.zip and the symptoms are identical.. i.e. no go.

What did work was flashing the rom without flashing SuperSU, enabling built-in root, then using SuperSU app to re-root with SuperSU... but then SuperSU broke again once I re-flashed the BETA-SuperSU2.48.zip with the same error indicated above. This would make future rom upgrades a huge pain.

Not sure what's causing this. I really don't want to use the superuser derivative that's built-in to CM12/.1.

Could it be this commit that broke it? http://review.cyanogenmod.org/#/c/95454/
[SuperSU] dickenam:
I can confirm this.

Sent from my A0001
[SuperSU] fmc000:
Some users in the bacon rom thread said that the same happened with gapps. CM pulled the today's update, probably because of that.
[SuperSU] sigeuner:
noob Samsung S3 i9305 supersu stopped working

—------------------------------------------------------

I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.

Please help.

I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:

Root access not properly configured or granted.

Superuser Application Status

Installed: SuperSU by Chainfire - version 2.46

System Files Status

Standard Location

Command: ls -l /system/xbin/su:

Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su

Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.

Standard Location

Command: ls -l /system/bin/su:

Result: /system/bin/su: No such file or directory

Analysis: File /system/bin/su does not exist.

Alternative Location

Command: ls -l /sbin/su:

Result: /sbin/su: Permission denied

Analysis: File system permissions restricted and denied access.

Alternative Location

Command: ls -l /system/xbin/sudo:

Result: /system/xbin/sudo: No such file or directory

Analysis: File /system/xbin/sudo does not exist.

User Account Status

Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1

Optional: ADB Shell User Status

Non-Root Shell User

Setting stored in /default.prop and configured as: ro.secure=1

Additional: System Environment PATH Status

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

_----------------------

So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.

Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.

Made sure no double superuser programs running.

Got rid of Knox.

Tried to custom install Supersu update, says invalid certificate.

I extracted SuperSU.zip and tried to copy the .su file to \bin but also didn't work.

I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.

Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.

I uninstalled Superuser and Kingroot, but think their .bin files are still there. Can't get them deleted.

Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix. Any help will be appreciated this is the first time I have rooted.

PS. If this post is in the wrong place please advise where itshould be.

Thanks
[SuperSU] coup3z:
Hi there,

I have a problem with my rooted device and I hope you can help me. I have a OnePlus One runnign COS 12.

I have rooted my oneplus one using the bacon root toolkit by WugFresh, but i cannot automatically toggle "mobile data" (neither through built in apps profiles, nor through trigger app). In the SuperSU log I get:

service call phone 97; exit

Result: Parcel (0000000 00000001 '....................')

I want to add that I downloaded the toggle data 5.0 by cygery and the widget worked. It's like it has some super root function.

Any ideas how to solve my problem?
[SuperSU] Cheps01:
Pkt_Lnt,

Thanks for the help but I didn't success because the result is the same, no start. I don't the reason.

Is possible intall the supersu by apk file, not by recovery??.

Regards.
[SuperSU] andy hall:
i think the apk is insde the zip file.
[SuperSU] B@sti:
It is. Common folder.
[SuperSU] Cheps01:
Thanks to both!!!
[SuperSU] priyam basak:
My problem was some what similar yo you. I rooted my phone root checker said i am rooted but there was no su app so i downloaded it from playstore and run it.

To my surprise when i run it,it said su binaries not detected now what i did is Reboot in recovery 'uncheck' the option signature verification and then flashed the stable zip of superSU and now am rooted.
[SuperSU] flamix:
Problem still persist

Facing the same problem in my OnePlus One. Root access vanished when i updated my cynogen nightlies 5.1 (18-21/4 nightlies). Not sure why? However if i recover back to the old version (17/4) i have back my root access. Though you have to re flash back SuperSu and Gapps.

CONFIRMED

The problem relates with the CM night-lies.

Download 17/4 and flash both SuperSU and Gapps, and its would be back on.
[SuperSU] PresidentMcCain:
I'm on my 4/21 sync of CM12.1, SuperSU is working again!
[SuperSU] flamix:
It's works with the new update. I'll vouch to that.
[SuperSU] j_schipper:
Made a clean install from on an opo build 12.1-22/4 and had no problems getting root access. :D
[SuperSU] flamix:
Guys. I is there any xposed applicable for Cynogenmod 5.1. I tried running the latest xmod 08/03 and it didn't work.
[SuperSU] shaggyskunk:
You'd be better off asking in the Xposed thread - SU has nothing to do with your question ?
[SuperSU] priyam basak:
Yes there is a alpha build but many modules are not working.

Head over to xposed thread.
[SuperSU] anhtu_1990:
i using xperia E3 root with lock bootloader. i cant update the binary file, in the setting it said the version is 2.46free. could you help me. thank you.
[SuperSU] Cheps01:
Hello,

I tried install from the apk from Common folder but when I execute SuperSU appear the error:

SU executable is not installed and SuperSU can not install it.

Any solution??

Many Thanks.

Regards.
[SuperSU] priyam basak:
You need to flash the update.zip firat in order to execute the su.binary files.

Or manually copy it to xbin folder.
[SuperSU] egingell:
Merely installing the SuperSU apk will not root your phone. The only time you should ever install the apk directly is if you're already rooted and are just updating.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] gilbert666:
Same here with cm12.1-20150423 nightly on a Samsung S4 :(
[SuperSU] priyam basak:
Flash supersu.zip file via custom recovery to gain root access.

But it is not same for all phone models.
[SuperSU] phomuabay:
yeah. i was flash it. and my device (s4) rooted . but it not full root. i can't use sb game hacker (error Root privilege is need )
[SuperSU] priyam basak:
Some rooted apps need busybox to work properly install busybox from playstore and sb game hacker will work.

Am not 100% sure but give it a try.

By flashing that zip we gain root access but for some apps busybox is needed.
[SuperSU] papperlapapp:
Hello,

I run SuperSu pro with Kitkat on a Xperia device.

I like to know, will Supersu survive an update to Lollipop using PC Companion? Or is survival mode only made for OTAs?

Thanx
[SuperSU] cschmitt:
If you use PC Companion to update then the entire system partition is flashed and su / SuperSU will be lost. It may survive an OTA update, but don't count on it.
[SuperSU] Morthawt:
I read that ghost mode is supposed to hide the fact that you are rooted or something? I installed an app from Sky TV and it said rooted devices are not supported, then exits. Is there some setting I need to enable ghost mode? (I have pro) or am I missing something about ghost functionality? I would appreciate some clarification on this.
[SuperSU] EVObastard:
Is there a list of devices that survival mode works on? I would like to update my Sprint Note 4.

Thanks.
[SuperSU] Dhs92:
Flashed SuperSU v2.49 this morning with Fire Flash. After completing the flash my phone tried booting up but kept on hanging on boot. I pulled the battery after about 25 minutes and tried again. After an hour I just pulled the battery and left it out.

I am on an I337, OC3 base using GoldenEye v51
[SuperSU] baanne:
hi, where i can find the link to download the version v2.26 zip file? cause i've installed the update but i cant get the root back on my phone
[SuperSU] Boopie11:
Hi, yesterday I was using Wakelock Detector and I found out this:

Today I flashed a new Rom and all I did was configuration stuff and install some basic apps such as facebook, twitter etc. and donation greenify (not xposed module) greenifying NOT system apps

After 3h it caused screen wakelock during 7 minutes

BTW I amb on stock lollipop 30b

Is greenify incompatible? is supersu broken?
[SuperSU] khairulez:
Hello...is it me you looking for?https://download.chainfire.eu/629/SuperSU/BETA-SuperSU-v2.26.zip
[SuperSU] baanne:
so... i've installed this and get a bootloop, gonna re-install the v2.29 to get my phone back to normal
[SuperSU] TASOSUSER:
No root functions

Hi there.

I've just updated Supersu from Google play store on my rooted phone SAMSUNG GALAXY GRAND NEO PLUS GT-I9090.

Since then "Titanium back up" and other apps than need rooting do not work any more.

For example "titanium backup" stacks with "REPLY FOR ROOT ACCESS..." error message.

I also can't find the SuperSu app in order to " (1) search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU." as described in Google Play page.

Please note that my phone has aready an older SUPERSU Ver. 1.93 installed after rooting progress I suppose witch I'm not able to locate through my phone's Applications list. Is there a solution please to update Supersu and regain root rights back?
[SuperSU] shaggyskunk:
Flash the zip from the OP
[SuperSU] dkonect:
V2.49 works like a charm (like all previous release) on note 3 touchwiz (Dr ketan note 4 port) and GT I9300 (qs-kitkat 4.4.2)
[SuperSU] donpippo:
Hi, only Pro version log full commands?

I'm trying to understand why

https://play.google.com/store/apps/details?id=eu.chainfire.stickmount

mount fine my NTFS usb pendrive instead using

su -c ntfs-3g -oro,gid=1028 /dev/block/sda1 /sdcard/OTG

show empty folder when looking with normal apps (solid explorer, mxplayer, etc). Root can see all the files.
[SuperSU] xunholyx:
It's in the OP.

Here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
[SuperSU] Super_Dork_42:
that's the link to 2.46, not 2.26, but I assume you just change it to the version you want and it would work?

EDIT - nope, the number changes, so you can go to https://download.chainfire.eu/xxx and just change the xxx to different numbers and look around and you should be able to find 2.2.6 just fine. I was trying out a bunch of numbers and I think 629 goes to version 2.2.6.
[SuperSU] khairulez:
Yep..that version is 7 post above you ;)
[SuperSU] Mike B.:
Old SuperSU versions

I'm not quite sure why anybody would want those ancient versions but if you're not happy using either the current stable build or the beta builds, here are the links for most public SuperSU incarnations:

SuperSU 1.x:

UPDATE-SuperSU-v1.00.zip

UPDATE-SuperSU-v1.01.zip

UPDATE-SuperSU-v1.02.zip

UPDATE-SuperSU-v1.04.zip

UPDATE-SuperSU-v1.05.zip

UPDATE-SuperSU-v1.10.zip

UPDATE-SuperSU-v1.20.zip

UPDATE-SuperSU-v1.25.zip

UPDATE-SuperSU-v1.30.zip

UPDATE-SuperSU-v1.32.zip

UPDATE-SuperSU-v1.33.zip

UPDATE-SuperSU-v1.34.zip

UPDATE-SuperSU-v1.41.zip

UPDATE-SuperSU-v1.43.zip

UPDATE-SuperSU-v1.45.zip

UPDATE-SuperSU-v1.50.zip

UPDATE-SuperSU-v1.51.zip

UPDATE-SuperSU-v1.55.zip

UPDATE-SuperSU-v1.60.zip

UPDATE-SuperSU-v1.65.zip

UPDATE-SuperSU-v1.69.zip

BETA-SuperSU-v1.72B.zip

BETA-SuperSU-v1.73B.zip

UPDATE-SuperSU-v1.75.zip

BETA-SuperSU-v1.76.zip

UPDATE-SuperSU-v1.80.zip

UPDATE-SuperSU-v1.85.zip

UPDATE-SuperSU-v1.86.zip

UPDATE-SuperSU-v1.89.zip

UPDATE-SuperSU-v1.89.zip

UPDATE-SuperSU-v1.91.zip

UPDATE-SuperSU-v1.93.zip

UPDATE-SuperSU-v1.94.zip

UPDATE-SuperSU-v1.97.zip

UPDATE-SuperSU-v1.98.zip

UPDATE-SuperSU-v1.99.zip

UPDATE-SuperSU-v1.99r2.zip

UPDATE-SuperSU-v1.99r3.zip

UPDATE-SuperSU-v1.99r4.zip

UPDATE-SuperSU-v1.99r5.zip

SuperSU 2.00 - 2.39:

UPDATE-SuperSU-v2.00.zip

UPDATE-SuperSU-v2.01.zip

UPDATE-SuperSU-v2.02.zip

BETA-SuperSU-v2.03.zip

BETA-SuperSU-v2.04.zip

BETA-SuperSU-v2.05.zip

BETA-SuperSU-v2.06.zip

BETA-SuperSU-v2.07.zip

BETA-SuperSU-v2.08.zip

BETA-SuperSU-v2.09.zip

BETA-SuperSU-v2.10.zip

BETA-SuperSU-v2.11.zip

BETA-SuperSU-v2.12.zip

UPDATE-SuperSU-v2.13.zip

UPDATE-SuperSU-v2.14.zip

BETA-SuperSU-v2.15.zip

BETA-SuperSU-v2.16.zip

UPDATE-SuperSU-v2.16.zip

BETA-SuperSU-v2.17.zip

BETA-SuperSU-v2.19.zip

BETA-SuperSU-v2.22.zip

BETA-SuperSU-v2.23.zip

BETA-SuperSU-v2.25.zip

BETA-SuperSU-v2.26.zip

BETA-SuperSU-v2.27.zip

BETA-SuperSU-v2.30.zip

UPDATE-SuperSU-v2.35.zip

UPDATE-SuperSU-v2.36.zip

UPDATE-SuperSU-v2.37.zip

BETA-SuperSU-v2.38.zip

BETA-SuperSU-v2.39.zip

SuperSU 2.40 - 2.49:

UPDATE-SuperSU-v2.40.zip

BETA-SuperSU-v2.41.zip

BETA-SuperSU-v2.42.zip

BETA-SuperSU-v2.43.zip

BETA-SuperSU-v2.44.zip

UPDATE-SuperSU-v2.45.zip

UPDATE-SuperSU-v2.46.zip

BETA-SuperSU-v2.47.zip

BETA-SuperSU-v2.48.zip

BETA-SuperSU-v2.49.zip

Use wisely as I highly doubt [MENTION=631273]Chainfire[/MENTION] will give you any support for anything but the current SuperSU releases. BACKUP, BACKUP, and BACKUP!

For the terminally curious: this is simply the output from "curl -# https://download.chainfire.eu/[300-750]" gently massaged by grep and sed ;)
[SuperSU] Promybrainz:
Good work
[SuperSU] Taani_ghost96:
i got problem with titanuim it says i cant accquire toot access can i get help from you guys ??
[SuperSU] shaggyskunk:
What device and Rom?
[SuperSU] ss1969:
Why su returns 1 in console, and superuser app tells me there's no binary found. Do put su & apk in right place, and set correct rights.

not flash the zip because recovery doesn't support.

here's the detailed info：http://xdaforums.com/android/software-hacking/running-su-result-1operation-permitted-t3097582
[SuperSU] Taani_ghost96:
Note 3 n900 and pekaka rom v3.0
[SuperSU] shaggyskunk:
a) Did you Flash the SuperSU zip?

b) Did you enable Root Access in Developer Options - Apps and ADB?
[SuperSU] Taani_ghost96:
Im on the latest version of supersu and its already enabled but not working :/
[SuperSU] shaggyskunk:
If you tried to open an app which requires root - BEFORE you enabled Apps and ADB - Just Reboot and it should be fine
[SuperSU] Taani_ghost96:
Man can u contact because i did all what u said and its not working at all :confused: