yashsingh1/xdaforums huggingface dataset:
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=55993466&postcount=6743
[SuperSU] egingell:
"Still" implies that people did at one time.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] cafarel:
2.13 is OK on OPPO Find7a [X9006] with stock ROM (ColorOS 2.0.3i) only rooted. Installed apk file extract from zip file.

2.13 is OK on Samsung Galaxy S+ [GT-I9001] with CM11, flash zip file from TWRP recovery.

Many thank for the work.

Inviato con Tapatalk da Oppo Find7a | X9006 | COS 2.0.3i
[SuperSU] d34thbl00m:
Having an issue with 2.13...when the prompt pops up for me to grant or deny su access the window freezes and I cannot click anything until it times out. Any suggestions on how to fix this?
[SuperSU] fubo73:
2.13 is ok on S2 with Slimsaber 0928 and PA GApps 1011.
[SuperSU] kingvortex:
Are you using an app that puts a filter on the screen? If so, the new tapjack protection is probably stopping you clicking on the popup.
[SuperSU] svbarbosa:
It is also happening with me. But only when running Call Master app. The same with Slim, Temasek or DU roms running on a Note 3 N9005

If I go back to SuperSU 2.02 it works fine.

Anyone knows a way to make 2.13 work changing settings or anything else?
[SuperSU] egingell:
Turn off tapjacking protection or quit using apps that make overlays on the screen.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Taomyn:
I haven't updated to 2.13 on my N5 yet, but reading about the tap-jacking can I assume this may clash with Lux Auto Brightness? I believe this uses a filter for very low brightness control and not sure if it's "alternate" mode will help either.

Is it possible to include a white-list in SuperSU or can it not detect what is causing the filter? Just a thought as I suppose I can just make sure to not be in the dark when SuperSU prompts.
[SuperSU] Pkt_Lnt:
Lux has a whitelist that will do this.
[SuperSU] Taomyn:
Of course, I'd forgotten about that thanks. Have added SuperSU to the list in preparation.
[SuperSU] aartjebakkert:
Working great! On my rom!

Just 4 2 Day
[SuperSU] Chainfire:
All these app's dev's should be informed that it is actually possible for SuperSU to inform the app when they need to hide the overlays because of the SuperSU popup. No whitelisting necessary.

Point them at this link: http://su.chainfire.eu/#updates-tapjacking
[SuperSU] CynoMan:
Thanks Chainfire, the latest update(2.13) is flawless!

Working perfectly on GT-S7582 (api level 17)
[SuperSU] captaindoobers:
No auto-rotation?

Just updated to 2.13, and after updating the binaries & rebooting, my screen won't auto-rotate any more. I checked the system settings & my launcher settings (Nova) and they are both enabled. This happening to anyone else? Not sure how to fix it...
[SuperSU] dimebagdan65:
Lmfao XD
[SuperSU] shaggyskunk:
Hey, I posted your avatar in the themes forum :p

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] sparksco:
Aw I was wondering why I was getting a "error parsing package" message for restores. I tried wiping data for TB and no luck, I'll try this thanks!
[SuperSU] shaggyskunk:
Hope it works for you, but I wasn't getting a parsing error... I was just getting something like... Check to see if you have root & busybox installed.

Edit : & that was just to even open TB.

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] Hairo The Blue Mage:
Just joking... great app, keep it up!!! :)
[SuperSU] wackygoose:
I have Superuser by ChainsDD but I want to replace with this one. Is there any special procedure? Or I can Just install this one then uninstall Superuser by ChainsDD ?!

Thanks in advance!
[SuperSU] sparksco:
Flash the CWM from the OP and it will replace it for you. I would also recommend wiping cache and dalvik-cache when installing a new system app ;)
[SuperSU] wackygoose:
Thanks for the quick reply! And it is good to know it as simple as that hehe!
[SuperSU] thedan55:
Quick question for you lads. I'm on the HTC one x with android revolution hd 3.1 and it has super su and I have the pro version and works like a dream and the latest update to titanium backup works a dream.

One thing, I use Barclays ping it and it can't be run with root. So what I did was try to use the disable mode,but no go. So told super su to uninstall and then ping it worked fine but obviously lost root.

So I installed it back from the market but super su said that the binary was not found and the only way to get root back was to flash through CWM and then all good.

My question is, is there an easier method as its allot of work just to use one app lol

Thanks chainfire for all your apps. Chainfire 3d had helped me many many times along with your other apps :D
[SuperSU] Chainfire:
Use the function to clean for market/play re-install, then re-install from market/play, then try simply disabling root in the preferences (temp-unroot) and see if Barclays works.

Most root detections detect both the binary, and check for /system/app/Superuser.apk, the latter does not exist with a Market install, only with CWM install and "baked into ROM", the former is hidden when you use that checkbox.
[SuperSU] BeatB:
everytime i open supersu i get: The su binary needs to be updated. continue?

then i click continue. >> installation failed!

How do i update? i cannot find a binary.zip file on your homepage. had this suee with superuser abb by ChainsDD but then i downloaded the latest binaries form his hp and flashed it in recovery.

how to get rid of this issue with your programm?
[SuperSU] vlt96:
You need data when installing it, do you have it? And keep the other SU when doing it;)

Seek the signature below the line;)
[SuperSU] BeatB:
thanks for the reply.

but what do you mean with data? i have a data folder on the sd card, also on ext4 partition, and also i have data turned on if u mean this.

this supersu app is a system app. it came with redux2 zm rom. so i cant keep the old superuser app.
[SuperSU] theone10:
You need to have internet connection (data)
[SuperSU] vlt96:
Data, mobile data, internet connection, wifi, anything;)
[SuperSU] BeatB:
lol of course i had this turned on everytime
[SuperSU] vlt96:
And older SU installed? Do apps with root work?

Try reinstalling normal SU binary
[SuperSU] BeatB:
no i dont have older su installed. and yes apps with root work without any problems. everytime i open the supersu app it says i need to update my binaries.

if the other su app is installed i still have the same issue with supersu. dont know i think i need only the latest binaries.zip.

can i download the su binaries and flash in recovery?: su-bin-3.0.3.2-efghi-signed.zip from http://androidsu.com/superuser/ or isnt it allowed to have from another app the binaries?
[SuperSU] sparksco:
The su binary is in the CWM zip in the First Post
[SuperSU] thedan55:
CHAINFIRE YOU ARE THE MANNN!!!!! thank you so much for your help. How do I give you more money? Just tell me! Do you need a kidney cuz you know I got 2, :D:D:D
[SuperSU] tammerlane:
I'm having an issue, but I am not sure it's with SuperSu. I rooted/unlocked my sprint HTC one m8 with SunShine last night. This morning I installed SuperSU from Play, then launched it and got the binary is missing error. So, I uninstalled it, rebooted, then reinstalled it. I'm getting the same error. I installed TWRP this morning too, but oviously it's not working at the moment, either. I need some help in getting this sorted. I think I covered all the pertinent info, but let me know if there is anything else I need to provide.

thanks!
[SuperSU] BathroomTile:
I always read OPs and try to follow the latest, but if a thread thousands of posts, I sometimes happen to miss the latest happenings.

I missed this post from the OP, so thanks for pointing it out but no need to be snarky.
[SuperSU] Mike B.:
This is extremely unlikely to have anything to do with SuperSU. Since you don't give any details about which device/ROM you use it's anybody's guess but in general a sudden failure of autorotation can be traced to an inadvertently deleted essential library: "/system/lib/libgnustl_shared.so". I've attached a version that should work with recent 4.x armv7 ROMs (coming from a Touchwiz 4.4.2 system) but if you can find the original for your device in your backups, use that instead. Copy/restore the file, set its permissions to rw-r--r--, and reboot.
[SuperSU] FryedPigBacon:
1744

So I just rooted and unlocked bootloader installed twrp my nexus 5 4.4.4

I tried to install superSu and something went wrong no binaries updated and it just spins in any of the UI expect settings.

Tried to uninstall for a clean version so could restore and the uninstaller just spins indefinitely as well.
[SuperSU] captaindoobers:
I've got a T-Mobile LG G3 running ZoneROM. I checked the original ROM zip & that file isn't listed in there either. I'll probably just reflash & see if that fixes it. Thanks for the suggestion though!
[SuperSU] Murshad007:
Perfectly working...

Sent from My LG Optimus G F180L Sling 2.2.2 stock 4.4.2 rooted
[SuperSU] BoneWithABeagle:
@

Chainfire

: I've got a problem with SuperSU on a LG E-460 (aka LG Optimus L5 II, Stock 4.1.2 ROM, only rooted)...

SuperSU updated itself to 2.13 from the Play Store and after the update it prompted about the su binary needing to be updated. I went with "Normal" and the "Installation failed." (Note: SuperSU 2.01 was installed previously and there's no custom recovery flashing possible).

So I connected via ADB, pulled the su binary out of the 2.13 update ZIP, copied it over to the sdcard (adb refuses to let me push directly into /system/xbin - gives "permission denied"), put the su binary (the "arm" one) into /system/xbin, chmod 06755, chown root:root ... and ... it still asks about "Binary needs to be updated" (and fails at attempting though /system is already remounted "rw" from the adb shell).

Is there any way by which I can resolve the problem? Losing root would be a pain in the rear as the device is a nightmare to root in the first place.

Thanks for any suggestions to rectify the situation.

EDIT 1: Just tried the su binary from the "armv7" directory (the 2.13 update ZIP) ... same Problem with "need to be updated" / "Installation failed.", though the binary seems to work. Trying adb shell and running /system/xbin/su - to directly call it - works.

EDIT 2: Okay, I downgraded to SuperSU 2.01 (installed the APK pulled out of the 2.01 update ZIP, putting the "su" binary into /system/xbin, doing the chmod/chown stuff) and letting it update the su binary ... this worked (did you chance anything in 2.13 that may cause the problem?). For the time being I set SuperSU/Pro in the Play Store to not auto-update.
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION] Any plans for including Material Design in SuperSU??? :confused:
[SuperSU] wanxu:
Can someone share a mirror for the apk file? I need it for a device non connected to the internet...
[SuperSU] power2top:
Updation issues with 2.13 from google playstore

I have got exactly same problem as [MENTION=5460432]BoneWithABeagle[/MENTION] as with hundreds of posts on the internet saying that 2.13 is not working for them. I already had CWM+SuperSu working since a long time. Saw update and as usual went to update. Post updation from Google Play store, I got message 'SuperSu binaries needs to be updated"-CWM->On Reboot, it asked be disable flashing recovery rom, I said yes, Then it prompt me, fix Root access, I said yes, it reboots. Phone starts well but again post restart, supersu is giving same message, that SuperSu Binaries needs to be updated. Anyone know what wrong and how to fix this issue?
[SuperSU] BoneWithABeagle:
If you still have root you could do as I did to fix the problem for the time being until we hear back from Chainfire...

- Get the SuperSU 2.01 update ZIP and unpack it.

- Copy the "Superuser.apk" (inside the "common" directory) and the "su" binary (either "arm" or "x86" depending on your device) onto your device - the SD card would be perfect.

- Open Play Store, select "My Apps", find "SuperSU", tap it, in the menu disable "Automatic updates" (or it will update to 2.13 again!)

- Open your File-Manager and install the APK

- Copy the binary into /system/xbin and run a "chown root:root /system/xbin/su" and "chmod 06755 /system/xbin/su" (without the quotes).

- Start SuperSU and let it have its way to update the binary (no idea why it wants to update _again_ though the corresponding binary was just put into place).

- Restart your device.

That's a bit of a "how you doin'" solution, but I managed to preserve root access that way.

If you have CWM or TWRP on your device spare yourself the trouble from above and just flash it in the recovery; the 2.01 update ZIP that is.

In case you need the ZIP (seems like Chainfire has no "old versions" downloads on his website) simply PM me and I'll pass you the ZIP.

EDIT: If you have 2.13 installed and you downgrade by flashing via CWM, you need to uninstall the update so you default to the "system" version!
[SuperSU] Chainfire:
Which exact firmware and kernel are you running? How did you update? "Normal" or CWM/TWRP?

The installation is quite a bit more complex than just pushing the su binary. If you can reinstall 2.13, select "normal" when it asks to update the binary, wait until it succeeds (or fails), then generate an adb logcat and post that, that would be a start.

Seems a number of people are suffering from this issue, but virtually no one is actively helping to solve it at the moment.

The very best would be if you could find me on IRC and we could debug this issue live.

My first priority is getting everything working and everyone rooted. Yes, I would like to implement Material Design, but I suspect it will be a while before I have the time.

The APK is inside the ZIP in the common folder.

Oh wow, hundreds of posts - out of about 50 million users. SuperSU is a very invasive complicated app (especially now with 4.4 / AOSP / L modifications), if think massive changes to an app like that to dozens of millions of users across thousands of different device models and firmwares is going to go without a hitch ... that's a bit much to expect.

Now, there are at least three things you did wrong:

(1) You are using CWM, which is outdated and broken, while you should be using the latest TWRP version, and if not that, at least a recent PhilZ.

(2) You allowed CWM to "fix" root access. Contrary to the description, this actually breaks root.

(3) You allowed CWM to disable flashing recovery rom. This deletes the startup script for root, so it breaks root.
[SuperSU] BoneWithABeagle:
D'OH! Looking into logcat for any errors totally escaped me... I was more worried to resolve the situation and not lose root. Take my word that rooting the device is a mess which involves rooting the thing in Windows with some obscure Chinese exploit and then getting rid of the Chinese "KingSU" and even more obscure Chinese app market (read: replacing it with your, tried-and-trusted, Superuser app).

Anyway, now that I have a procedure to revert back I will try a 2.13 update later the day to get you the logcat once it failed the installation of the binary (though I find it still somewhat strange that 2.01 doesn't have that problem).

On a losely related note, SuperSU 2.13 updated fine on our other devices running CM11 M10/11 - it's just the one LG that seems to have a issue with it.

I'll post a new reply as soon as I have the logcat for you.
[SuperSU] Chainfire:
You might have missed it from the reply earlier as I just edited it, but if we could debug live over IRC (or hangouts, or skype, or whatever) that would be the most helpful outcome.
[SuperSU] beany>:
I agree with you. I and many others are sincerely grateful to you for SuperSU (Pro) and I would like to say "Thank you". :)
[SuperSU] BoneWithABeagle:
I sent you a PM.

It'll be my pleasure to try a live debug with you, especially if that really helps you.
[SuperSU] :
Thanks for your reply.... Good to know material design is on the agenda!!! :victory:
[SuperSU] BuddyP1952:
borked on gs3, stock other than root

Same problem, different device (gs3)

I opened a shell, su'd, chdir'd /system/xbin, ls -l su, wut? date on su is foobar, 1971-02-27 (almost the unix epoch [1-jan-1970], but not quite), touch su, date set to now. Clear notifications, try to run supersu, still wants to update binary :(

su binary size is 71532, owner root:root, permissions are setuid and setgid.
[SuperSU] Chainfire:
Which firmware and Android version ?
[SuperSU] Chainfire:
Which Android version? Can you provide the output of "adb logcat -d" and "adb shell ls -lZ /system/xbin" ?
[SuperSU] Chainfire:
Give this version a shot and let me know: http://www65.zippyshare.com/v/36818848/file.html
[SuperSU] BuddyP1952:
sorry, I forgot that there's a bunch of different gs3s, and that some of them got OTA updates

Mine's a VZ gs3 (sch-i535), firmware is the original touchwiz, android 4.1.2, baseband I535VRUCML1, kernel 3.031-1152558 se.infra@R0710-11 #1, build number JZ054K.I535VRBMF1. As you can tell, I never installed the 4.2 OTA but I updated the baseband manually

hope this helps
[SuperSU] ironia.:
just updated through play, normal mode, everyting seems ok

stock kk on nexus 5

is really needed 'reboot after binary update'??

tnx
[SuperSU] Chainfire:
Try this version here and let me know: http://www65.zippyshare.com/v/36818848/file.html

Strictly speaking, no. It is advised, not required. There's usually some leftover zombie processes from su killing it's own processes. In case of any issues, reboot, if not, well then there isn't that much to worry about.
[SuperSU] BuddyP1952:
Worked! Thanks, you're the best!
[SuperSU] Dr Goodvibes:
Xperia C1905 Android 4.3

Xperia C1905 with locked BL running Android 4.3 with root access.

Updated the latest SuperSU via Google Play Store. (15-OCT)

SuperSU then requested a binary update.

Binary update completed.

SuperSU then requested a reboot.

The phone is now in a boot loop and restarting just after the Sony logo with only a few seconds of the swirling rainbow animation of startup.
[SuperSU] Chainfire:
How was this device rooted initially, which method was used ?

Have you succesfully updated binaries before on this firmware ?

Is it possible to reach adb shell before the reboot ?

Is this device/firmware known for having /system write protections ?

Do you have access to a custom recovery ?
[SuperSU] egingell:
Works. Except...

It seems to take forever for anything to acquire root access if at all - and eventually causes SuperSU to crash followed shortly by the phone. I can't get any logs.

I cleared dalvik and SuperSU's data with no success.

I disabled Xposed via is "safe mode" with no success.

I tried uninstalling ("cleanup" in SuperSU settings) before it could freeze. SuperSU asked for root while uninstalling, which is weird by itself, and caused SuperSU to crash.

Every settings change also causes SuperSU to crash.

This could very well be my phone. I'm working on a solution.

Still can't get logs.

Edit 1: I uninstalled SuperSU (updates) by force (recovery) and am downloading and reflashing the system to get a clean slate at which time I will reinstall the the "working" v2.13.

Edit 2: Working now. My best guess: remnants of "pro" (different Google account) still lingering and interfering. Still seems like it's taking an unreasonable amount of time to grant root.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] markusb68:
APK ?

Where can I find the latest (2.14) APK. There's only a link for the ZIP in the OP.

Play Store is offering still V2.01 to me, but pretends it has been updated today (15. October 2014).

Thanks

Markus
[SuperSU] Fra8:
I have version 2.02, I go in the app I click reinstall, I go to TWRP flash zip 2.14 but when I reboot I still have the 2.02, because? where am I wrong?
[SuperSU] zadigre:
you don't have to do the reinstall thing... just flash the 2.14 in twrp and you will be fine.

---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

you can find the apk in the zip file... yes, it's that easy!
[SuperSU] Fra8:
I tried to do that too, but should not be
[SuperSU] markusb68:
Cool. Saw the APK in the ZIP, but was confused about the file date of 29th Feb. 2008

Thanks

Markus
[SuperSU] zadigre:
if you can open the zip file, apk is in the "common" folder.

There's not mirror for the apk... so if you are not able to extract it from the zip file, you will have to wait for the update on the play store.
[SuperSU] Fra8:
Thank you, everything ok! ;)
[SuperSU] tammerlane:
Android version is 4.4.3, it's stock, I only ran Sunshine. I'm working on the logcat and the adb shell part, I've never run these before so it's taking a minute to learn...

Edit: I tried version 2.14, still have the issue. I downloaded Catlog, but its not working since it can't gain root access. Installing adb right now on my desktop.
[SuperSU] Dr Goodvibes:
[MENTION=631273]Chainfire[/MENTION] Thank you for your reply.

Currently have Locked Bootloader on C1905 with firmware 15.4.A.1.9 (Android 4.3)

Rooted via FramaRoot v1.6.1 using Android 4.1.2

To Root Android 4.3, I had to install system.ext4 via a windows PC after, firstly getting root access on Android 4.1.2 using Framaroot.

Then use Flash Tool to install The 4.3 fw excluding system as it's already applied with root access.

Has been working Ok rooted via this way for over six months.

Yes, I believe so. I've been using SuperSU on this device since October 2013.

I do have previous SuperSU apk backed up so should be able to rebuild C1905.

No, doesn't seem like it. (I have limited knowledge on this)

An adb logcat or adb shell just state:

error: device not found

On the adb shell I did get the following once or twice:

error: device unauthorized. Please check the confirmation dialog on your device.

I have seen this before when the phone was operational and I was attempting to access the phone via adb shell

Operationally with Android up and running I've not notice any /system write problems

I have Link2SD installed and often use it to move 'system apps' into the /system/app folder.

Have an old Andoid v2.2 system which does have /system write problems and have to use Google Play "Root Explorer" to set write access first, BUT this doesn't happen on the C1905.

Oddly SuperUS v2.14 is fine on my old Android v2.2 TV box and my Sony Xperia S phone. :)

Sadly no. Haven't been able to port CWM to a C1905 with locked bootloader yet.

I'll re-install the fw with SuperSU v2.14 the first cab off the rank and see if I can get a clean boot.

Update

Reinstalled root access on my Xperia C1905.

Installed and rooted Android 4.1 and then upgraded SuperSU to latest version.

Rebooted phone.

Then updated SuperSU binary and rebooted.

All OK.

Then proceeded to upgrade to Android 4.3

Upgraded BusyBox and SuperSU to latest versions and rebooted.

After reboot I then upgraded the SuperSU binary and again rebooted.

Phone reboots fine now(this time)

Installed SuperSU Pro and Link2SD and still all OK after reboot.

So now I continue the restore and install FolderMount and etc.

Probably with a large collective of system focused apps and a SuperSU binary update, someone stepped on someones toes at boot time when I upgraded the first time with a fully configured application environment.

All good now (fingers crossed).

Thank you Chainfire for your proactive customer care and your continued support for SuperSU on Android phones.
[SuperSU] shadow322:
Still doesn't update binary on SGS3 T999 :( gets stuck at installing when it asks to update the binary
[SuperSU] farisyi1:
Worked fine on SGS 2 & SGS 3 with OmniROM Nightly thanks [MENTION=631273]Chainfire[/MENTION] [emoji106]
[SuperSU] cdaarif:
1+ every boot it wanna update bianary bt it failed by normal n don't install by twrp/cwm. I9100 1st rom netrom super light n 2nd rom cm 11 nightly 10-10-14.

Sorry for my bed English-speaking.
[SuperSU] vadim-zh:
After 2.14 apdate the issue with binary absence is still remaining. Rolled back to 2.01 - working fine. HTC ONE XL, 4.2.2, UrDroid 5.08.111.2 FW (from here), TWRP 2.3.3.0
[SuperSU] moom999:
Why Play Store still offering V2.01?