yashsingh1/xdaforums huggingface dataset:
[SuperSU] dirtyreturn:
Woops. The clockworkmod one is free and I *don't think* there is an unlock key. *Maybe* open source??
[SuperSU] jorceshaman:
I could be wrong but I believe that the free version includes everything that the Clockworkmod version does. The Pro unlock key is completely optional for some additional features and to show support.
[SuperSU] Dan1234567890:
I think that the main difference is not in functionality, but in fact that Superuser can be more "incorporated" into rom (in system setting or so, showing customised confirmations for granting root, etc), and SU can't. So Superuser is more "opened".

But I do not think we should discuss different apps here, since it is OT and disrespectful to the dev. [emoji106]
[SuperSU] simonbigwave:
Pls do NOT call the Omega ROM developer stupid, especially if it is you who does not know how to root. Suggest you Google "how to use Odin to root Android SuperSu".
[SuperSU] Naddict:
^^^this ^^^

Members are reminded that respect is a mandatory requirement when posting.
[SuperSU] egingell:
Also, if you think so highly of the ROM and/or its dev, why are you still using it?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] kuromusha38:
because I can't be bothered to find out about other roms.

ps. don't bother replying, I've unsubbed this thread.
[SuperSU] t3chwizard:
What a jerk wow
[SuperSU] simonbigwave:
Please Buddy you really need to read again what you have said and what you are saying. Not to be rude but I almost fell off my chair laughing.

Anyhow for the avoidance of doubt here is instructions/one way on how to install supersu

"ODIN flashable devices

BASIC INSTRUCTIONS

All downloads contain*.tar.md5*files flashable in ODIN as PDA.

Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included*Odin3-v1.85.exe*file, press the PDA button, select the*.tar.md5*file, and click*Start. You can find more detailed instructions and assistance at XDA.

A modified recovery and cache partition will be flashed, which will install (only)*SuperSU, thenclean-up the cache partition and re-flash the stock recovery.

For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.

UNLOCK BOOTLOADERS

If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will*usually*automatically "OEM unlock" and*wipe your data !"

If you want free advice I suggest you READ a bit more before complaining that a Rom developer is 'stupid' . the kind developer puts alot of time into his/her development for us users And users like us get the ROM (and superSu) for..Free.

Just in case here is Chainfire's original URL i found with a quick search on xda so suggest you please READ carefully http://autoroot.chainfire.eu/
[SuperSU] Frank Westlake:
Frank
[SuperSU] Cookie Ninja:
It takes all kinds to make this world, some good, some so-so amd some like him...

Dead Cookies leave no trails...
[SuperSU] Chainfire:
Please do not feed the trolls. Thank you.
[SuperSU] IIMaxII:
Hahaha, wow. I can't help but laugh at how someone can actually post something so ignorant.
[SuperSU] theboywonder:
so i rooted tonight...and opened SuperSU and it didnt auto update.

im on v.1.93. is that OK? any easy way to update?

thank you.
[SuperSU] Pons:
Flash the update zip linked in the OP.
[SuperSU] cableghost:
Survival Mode JB to KK

Any experiences with Survival Mode, going from JB 4.1.2 to KK 4.4.2?
[SuperSU] aavvaallooss:
I didn't make any change from 4.4.1 to 4.4.2. Root survived
[SuperSU] cableghost:
I've seen a few replies herein that had root survive from 4.4.x to 4.4.2...am I to assume that there would be no coding difference in going from 4.1.2 than from 4.4.x? I understand the logic...if 4.4.x survived root, earlier builds should as well, but is that the case?

Also, I heard that although root survived, you still lose R/W capability...can you confirm either way?
[SuperSU] antivirus1:
its saying that am rooted but then its saying I am missing a binary file HTC One mini Android 4.3 Sense 5.5
[SuperSU] LeftyGR:
You didn't by chance just switch su apps, did you? That has happened to me in the past by doing that.

Try flashing the install zip in recovery. It's pretty thorough in removing the parts of other su programs and installing the new set cleanly.

<Note3>

---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------

Wow... is cleanly even proper English? Jeesh...

<Note3>
[SuperSU] kingy9000:
Why, Yes It Is!

Cleany as defined by Merriam-Webster :silly:
[SuperSU] quack3d:
Any news on this? I have the same issue.
[SuperSU] Chainfire:
v1.97 released

v1.97 released - this is not a Play release (yet), more of a beta for AOSP/4.4.3 changes, please see the release notes here: https://plus.google.com/+Chainfire/posts/ZtXAhw164QD and spread the word.
[SuperSU] 089man:
This new version is only for 4.4.3? I'm pro user since long time...

I9100 Tapatalk 4, C-Rom 4.4. 2
[SuperSU] egingell:
Do you *really* need an updated version for 4.3 and older?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] 089man:
Smile, no... Never 4.3 the new version is for 4.4.3 or higher... My question was can i used this 1.9.7 also with 4.4.2 kitkat or is this build only for new kitkat 4.4.3.....you understand what i mean?

Never I ask for 4.3 or older, smile

I9100 Tapatalk 4, C-Rom 4.4. 2
[SuperSU] boyheadkick:
4.4.3 isn't even out yet..so 1.9.7 being out already means that it should be ok to flash for 4.4.2
[SuperSU] aavvaallooss:
So far so good with SuperSU 1.97 on Nexus 5 4.4.2 (Stock)
[SuperSU] brunodu91:
I prefer wait the green! Fire by chainfire....lol

Envoyé de mon S4, via tapatalk 4 Vip .

Slimkat 4.4.2 v5.0 stable, Kernel stock , buzz launcher , modem ET bootloader NC4.
[SuperSU] boyheadkick:
I just opened all of my root apps and all opened with out any errors or problems..so far, all good

-aL

Tapatalked from my BoefflaDroid i9300
[SuperSU] brunodu91:
I will tested tommorow......thx and good night!

Envoyé de mon S4, via tapatalk 4 Vip .

Slimkat 4.4.2 v5.0 stable, Kernel stock , buzz launcher , modem ET bootloader NC4.
[SuperSU] JulianJenner:
Works normally. Thanks!

CARBON ROM HD ⁴.⁴.² (2014.05.15.) by Nasheich / LG OPTIMUS L9 P760 / TAPATALK PRO ⁴.5.²
[SuperSU] t3dpott3r:
Confirmed working on Note2 SGH-T889 running deoxed, deknoxed, stock Samsung 4.4.2 TouchWiz N7105.

First boot was a little laggy for about 10 minutes, fixed on next boot. Opened all root apps installed including xposed and no bugs yet.

Thanks!
[SuperSU] MatroxD:
Working normally on note 3 4.4.2 nc2 biggins rom.
[SuperSU] muniz_ri:
I realize this is only intended for aosp roms but tried it on i337 running stock tw NC1 4.4 build and received no binary msg. Flashed back supersu v.1.94 and all is well again.
[SuperSU] -CALIBAN666-:
Works perfect on kitkat and gingerbread.

GREEEETZ FROM TEAM-OPTIMA!!!
[SuperSU] Everhez:
Not Working, binary SU not installed, go back v.1.94

OS: Android 4.4.2 KitKat

ROM: C-Rom 6.5

Enviado desde mi Moto G mediante Tapatalk
[SuperSU] sanketss84:
I have a small query.

If I install supersu from playstore or flash via cwm on my current rom. later factory reset, cache wipe, dalvik wipe and install a new Rom.

Will supersu app stay and it's su binary also stay or will it be over written by the new flashed Rom ?

Sent from my GT-I9300
[SuperSU] egingell:
Flashing a ROM overwrites everything on the system partition including the su binary and Superuser app.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] chteh2008:
Not Working, binary SU not installed, flash back to v1.94

HTC One X with stock ROM Android 4.2.2 and CWM touch recovery v6.0.4.8
[SuperSU] sub1287:
Working fine on my nexus 4 running Velocity ROM & kernel.

accelerated [mako]
[SuperSU] WR3CCKL3SS:
Flashed Update v1.97 through TWRP and booted up, then went into Su App and it gave me an error, saying su binary not installed and it couldn't install it itself. Flashed back to v1.94 and everything went back to normal. Just giving a heads up.
[SuperSU] Chainfire:
Seems I have none of these devices to test on, so keep the error submissions coming - sooner or later we'll hit a device I can test and fix on!

Are any of you running quoted below running Xposed or other non-standard softwares? (please note your modules if you are running Xposed)

Moto G ?

No, it is good that you are testing it on non-AOSP. It needs to work on all!

Which device, firmware, and TWRP version?
[SuperSU] FastGas:
SuperSU 1.97 works on my S4mini rooted, from supersu 1.94 and recovery philz touch 6.26.6
[SuperSU] WR3CCKL3SS:
Here's a screen shot. Running the latest version of Xposed and using a modified version TWRP made by ktoonsez
[SuperSU] WR3CCKL3SS:
Hope this helps in any way
[SuperSU] Chainfire:
Thanks - I know this is a major hassle, but could you bother trying it with the latest official TWRP and without Xposed, and see if that makes a difference?
[SuperSU] WR3CCKL3SS:
No problem. Will report back in a few.
[SuperSU] WR3CCKL3SS:
Completely removed Xposed and flashed v1.97 through the latest TWRP 2.7.0.1. It still gave me the same error.
[SuperSU] josechufa:
Binaries

No binaries and updates the terminal when ROOT v1.94 app combines agree ok, GlassRom 4.1.2 v18, Thanks
[SuperSU] FlanjeUK:
Just flashed on my i9505

Works perfect here :D

SlimKat latest weekly

Alucard Kernel

No Xposed (I use ART)

Old pre-knox bootloader

Flashed via CWM 6.0.4.7

EDIT: Just flashed ROM update and Survival Mode still working too :)
[SuperSU] quack3d:
[MENTION=631273]Chainfire[/MENTION] Is this fixable or do I have to stick with v1.80? If not, is there a SuperSU version that is not linked to Google Play? It's pretty annoying that I cannot update all apps with one tap because SuperSu is in the update list.

Thanks.

EDIT: I'm using a nightly Cyanogenmod 11 on a Galaxy S4.
[SuperSU] simonbigwave:
Flashed SuperSUv1.97 on i9505 (new bootloader)

Via PhilZ Touch 6.40.0

On CM11 518 nightly w/ART

SuperSUPro working all fine here so far. Thanks again Chainfire
[SuperSU] Chainfire:
Find a replacement app if you need it ... I'm not going to change SuperSU because of some obscure abandoned app.
[SuperSU] quack3d:
Unfortunately there is no replacement for it, but thanks for responding nevertheless.
[SuperSU] CamoGeko:
It doesn't need to be changed. Works perfectly fine on my HTC One M7

Sent from my baked potato with blue cheese
[SuperSU] Frank Westlake:
Installed and root verified on:

SGH-I717 4.3.1 I717UCLD3 AoCP 6.4 SELinux Permissive

SM-N900V 4.3 N900VVRUBMI9 SafeStrap/stock SELinux Permissive

SM-N900T 4.3 N900TUVUBMI7 TWRP2.7/stock SELinux Enforcing

On the 900T, I did not set it to Enforcing and I don't know if it was that way before installing 1.97.

Thank you.

Frank
[SuperSU] ragz:
Working great on SGH-I337M

TWRP 2.6.3.1 jfltecan

SuperSU v1.97

4.4.2 touch wiz rom

NC1 bootloader (knox)

(XPosed installer v 2.6 installed as well)

Thanks for your hard work.

Sent from my SGH-I337M
[SuperSU] brunodu91:
Working great on i9505 jfltexx slimkat 4.4.2!

Envoyé de mon S4, via tapatalk 4 Vip .

Slimkat 4.4.2 v5.2 stable, Kernel stock , buzz launcher , modem ET bootloader NC4.
[SuperSU] WR3CCKL3SS:
I hope you come up with a quick fix for all of us wanting to update to v1.97... We all know you will, just gotta be patient... Keep up the great work and continue to bless us with all your talents in getting ROOT for all devices.

AT&T SAMSUNG GALAXY S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] Chainfire:
Just noticed one of the other guys posting it didn't work was also running C-ROM ... hmm!
[SuperSU] WR3CCKL3SS:
So it could be rom related? Should I try it with another rom?

AT&T SAMSUNG GALAXY S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB

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

If need be, I will flash a different rom just to check

AT&T SAMSUNG GALAXY S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] mdprfsr:
Working perfectly. MultiRom xposed on stock firmware with Code Blue kernel and paranoid saberdroid
[SuperSU] diegons49:
Working great! Moto X unlocked, 4.4.2 stock.
[SuperSU] chteh2008:
Device: HTC One X

Firmware: Stock Rooted ROM 4.19

Android: 4.2.2

Recovery: CWM touch recovery v6.0.4.8
[SuperSU] Chainfire:
If you have the time to spare, then yes please. If it ends up being the ROM, I'll find a version of it for one of my own devices, and see if I can replicate the problem.
[SuperSU] gothicasshole:
It honestly depends if the official ota patched the kernel as was the case with samsung 4.3 too 4.4.2
[SuperSU] elesbb:
Hey [MENTION=631273]Chainfire[/MENTION],

You truly rock. I wanna thank you so much for keeping android what it is, a user based OS. You allow us to use things like xposed, ROMs, and recoveries and such things like that. Without you, XDA wouldn't be the same. So thank you so much dude. Always on top of the game too! You are a legend. :)
[SuperSU] WR3CCKL3SS:
I'll give it a try... Give me a few and I will report back asap

AT&T SAMSUNG GALAXY S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] Hälftebyte:
Working great on official Samsung N7105 TW 4.4.2!

Gesendet von meinem SAMSUNG-SCH-I605 mit Tapatalk 2
[SuperSU] WR3CCKL3SS:
Any rom you could recommend I try on? I was thinking about trying on latest Slimrom, which I've used and been on before I came to C-RoM.

AT&T SAMSUNG GALAXY S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] kvevand63:
1.97 working great on Galaxy S2 running clean flashed Vanir 4.4.2 AOSP nightly, ART enabled. I did receive the update binary message originally when I installed 1.97 zip over 1.94, then decided to clean flash the ROM and flash 1.97 at the same time, did not receive the update binary message. Question; I notice that chattr.pie did not install to /xbin or /bin. Does this mean that 1.97 did not install correctly? So far, I havent encountered any root related issues. Thank you for the update!
[SuperSU] cableghost:
Survival Mode JB > KK

I'm looking for any experiences of using SSU Survival Mode, going from JB to KK, specifically, 4.1.2 to 4.4.2. I have read root will survive this update, however, will lose R/W capability...can anyone confirm this, or otherwise?

---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------

How may I discover this?

My Phone:

Moto Droid RAZR M

Stock ROM, rooted

4.1.2 / 98.30.1.XT907

Verizon Network
[SuperSU] edgarf28:
What's the proper way to integrate SuperSu (1.97) in an updater-script's rom file?

I've now this part in my rom's updater-script file:

set_perm(0, 0, 0777, "/system/bin/.ext");
set_perm(0, 0, 06755, "/system/bin/.ext/.su");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 0755, "/system/xbin/daemonsu");
set_perm(0, 0, 0755, "/system/xbin/sugote");
set_perm(0, 0, 0755, "/system/etc/install-recovery.sh");
set_perm(0, 0, 0755, "/system/etc/init.d/99SuperSUDaemon");
set_perm(0, 0, 0644, "/system/etc/.installed_su_daemon");
set_perm(0, 0, 0644, "/system/app/Superuser.apk");

run_program("/system/xbin/su", "--install");

Is that enough?

Or should I add more things? (Like the Ch_con and/or chattr parts)
[SuperSU] jazzruby:
chattr(.pie) is only used in the recovery/install process to remove the immutable bit set on the su related files.

The app itself has chattr (assets) which sets (applies) the immutable bit for protection from change/deletion of su files.

-JR-
[SuperSU] Chainfire:
Correct, but changing the file contexts (chcon) is certainly needed!
[SuperSU] edgarf28:
Can someone tell me how to properly integrate the chcon part in an updater-script's rom file please?

EDIT: Is this the right way?

set_perm(0, 0, 0777, "/system/bin/.ext");
set_perm(0, 0, 06755, "/system/bin/.ext/.su");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 0755, "/system/xbin/daemonsu");
set_perm(0, 0, 0755, "/system/etc/install-recovery.sh");
set_perm(0, 0, 0755, "/system/etc/init.d/99SuperSUDaemon");
set_perm(0, 0, 0644, "/system/etc/.installed_su_daemon");
set_perm(0, 0, 0644, "/system/app/Superuser.apk");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/xbin/su");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/bin/.ext/.su");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/xbin/daemonsu");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/etc/install-recovery.sh");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/etc/init.d/99SuperSUDaemon");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/etc/.installed_su_daemon");

run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/app/Superuser.apk");

run_program("chcon", "u:object_r:system_file:s0", "/system/xbin/su");

run_program("chcon", "u:object_r:system_file:s0", "/system/bin/.ext/.su");

run_program("chcon", "u:object_r:system_file:s0", "/system/xbin/daemonsu");
run_program("chcon", "u:object_r:system_file:s0", "/system/etc/install-recovery.sh");
run_program("chcon", "u:object_r:system_file:s0", "/system/etc/init.d/99SuperSUDaemon");
run_program("chcon", "u:object_r:system_file:s0", "/system/etc/.installed_su_daemon");
run_program("chcon", "u:object_r:system_file:s0", "/system/app/Superuser.apk");

run_program("/system/xbin/su", "--install");
[SuperSU] meatboy371:
Everything working good so far with v1.97.

Using Nexus 4 + SlimKat 5.0 + TWRP 2.7.0.0 + latest Xposed Framework

Enviado de meu Nexus 4 usando Tapatalk
[SuperSU] adrman:
Working fine on hammerhead and grouper, running the latest Rastakat (aosp). The hammerhead has Trinity kernel.
[SuperSU] TDSJR:
Working fine on LG-D801, Mahdi R1, ART using Twrp 2.7.
[SuperSU] WR3CCKL3SS:
Changed ROM to Slimkat and then flashed v1.97. And opened the SuperSu app to a pop-up saying binary needed to be updated, so I pressed the twrp/cwm way of installing it and after it finished... I went back into the app and everything worked.... No pop ups at all....so now I've restored back to C-RoM
[SuperSU] leninke:
Working fine so far, Mako, Omnirom, ART, Twrp 2.7 You are the man [MENTION=631273]Chainfire[/MENTION]
[SuperSU] edgarf28:
On the S5 (G900F) seems 1.97 doesn't work correct... When an app wants root permissions it doesn't ask.

But when I set 'Default access' in the SuperSu app to 'Grant' then the root permissions in all the apps are working.

Installed SuperSu 1.97 with the flashable zip.

And when I flash 1.94 back then it works ok.
[SuperSU] stef_ladefense:
1.97 not work su update with sm-t520 tab pro 10.1

Ok with 1.94 after cf-auto-root appli

With 1.97, the binary not update, with reboot or not

Stef
[SuperSU] Frank Westlake:
The two SM-N900s are single-user mode.

Regarding the failure to ask for permission to give root access, I 'forgot' both ConnectBot and vxConnectBot and then ran 'su' in each; SuperSu requested permission for ConnectBot but not for vxConnectBot. Both are at GitHub.

ADDED:

Disregard the above. vxConnectBot was set to use ConnectBot -- I cleared the defaults and all is normal. Sorry for the noise.

Frank
[SuperSU] josechufa:
binary

Xposed installer removed , checked with my update.zip and integrated Custom Rom, 4.1.2 XXMH1-XXMF6-PHE-.GlassRom_Blue_AC!D_Sound and still giving the same error binary upgrade, even restarting the terminal, greetings..
[SuperSU] 777.300:
1.97 working fine on ParanoidAndroid 4.3 Beta 4 with Franco Kernel and latest Xposed Framework.

Only issue is that the app does not show up in the app drawer but I believe it is an ParanoidAndroid issue.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Voltaine:
Not working on nexus 4 with latest mahdi rom

Philz recovery 6.41.6

Kernel Hellscore #2 R9

1.94 working flawlessly

With 1.97 i get many fc's (one of them was com.system.android.acore stopped or something like this, made it impossible to use the phone)
[SuperSU] 4D3:
i have same issue
[SuperSU] meekrawb:
Works: Flo running Slimkat 5.0

Doesn't work: Hercules running Carbon 05/16
[SuperSU] Thomas_BA:
Flawless on Moto X with KitKat.
[SuperSU] WR3CCKL3SS:
[MENTION=631273]Chainfire[/MENTION] Any luck on duplicating the issue and finding a fix for some of us?

AT&T Samsung Galaxy S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] Chainfire:
It's not related to the G900F specifically, it works fine on mine. It's probably your ROM - you are running the one from your signature? (I need to know for testing purposes)

Interesting - can you get me logcats of the errors?

I have not had a chance to try yet - expect this to take several days at least. And that's only if the problem doesn't lead to the discovery of a design issue of the new code, in which case it could take significantly longer to fix.
[SuperSU] WR3CCKL3SS:
By all means take your time to get some of us that fix and thanks for the hardwork and dedication. If you need anymore help on my end on duplicating the issue, I'll be more than willing to help with whatever I can. I'm just a message away. Thank you once again.

AT&T Samsung Galaxy S4 I337

ROM: C-RoM v6.5

KERNEL: KT-SGS4 v7.1

FIRMWARE: I337UCUFNC1

BOOTLOADER: I337UCUAMDB
[SuperSU] ma678:
I couldn't flash it on my Nexus 7 2013 running stock kk 4.4.2, while I did it successfully on my Nexus 4 running stock.

Both have TWRP 2.7 installed.
[SuperSU] farisyi1:
Worked perfect on SGS2 running OmniROM and [MENTION=4217277]Gustavo_s[/MENTION] kernel TWRP 2.7.0.0 with latest xposed enabled! Thanks [MENTION=631273]Chainfire[/MENTION] :)
[SuperSU] nick123ablxx32:
can't update SU binary

GT-I9505

CM11

SU 1.97

i selected TWRP/CWM and it got into TWRP and finished up but when I booted I got the same message flashing back to 1.94 for now
[SuperSU] VivaErBetis:
Testing 1.97. Works flawlessly in nexus 4 and nexus 10 under stock 4.4.2 Kit Kat.
[SuperSU] edgarf28:
Yes, running my own ROM from my signature.

Please tell me what I have to change.
[SuperSU] bobo1704:
Works perfectly on S4 Mini Duos.
[SuperSU] 78Staff:
Similar as others have reported, zip appears to install fine, updating binary fails in both normal and TWRP/CWM methods. Reverted back to 1.94 with no issues. ATT S4, rom/kernel particulars below...
[SuperSU] dabenaute:
hi all, updated my phone with the new XEF-N7100XXUFNE1 but supersu 1.94 or 1.97 doesnt work:update binary failed,..(using philz 6.26)
[SuperSU] simonbigwave:
minor update: having flashed supersupro1.97 OK on CM 11 518 nightly via philz 6.40.0 on jfltexx

then, i updated to CM 520 latest nightly today, and noticed lost SupersuPro1.97 (even in survival mode) and Chainfires Supersu app icon also gone. only the CM Rom supersu. had to reflash SuperSu1.97 again in philz touch, and that fixed it and all running ok now with SuperSu1.97 again.
[SuperSU] tamingsarix:
Hii...su 1.97 not work for me i guess.. Always ask to update binary. Although many time i update...back to 1.94
[SuperSU] 777.300:
Solved problem by using the re-install from play store command from within the app. Re-booted N4/N7, re-booted again in recovery, flashed SuperSU 1.97 and finally back to normal and SuperSU app visible again as an user app.

Great.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Chainfire:
All of you, please try UPDATE-SuperSU-v1.99.zip and see if it solves your problems.
[SuperSU] edgarf28:
Still having the same problem on my rom, it doesn't ask for root permissions.
[SuperSU] tamingsarix:
Same prob...geting error like this..' Super su needs to update binary' when me update and close app, and open again. Its still has error like this
[SuperSU] bigfoot.kom:
Hello. I have d2att/att s3. Using latest slimkat weekly 5.2, flashed 1.97. Have all root privileges! All is well. Thank you!