yashsingh1/xdaforums huggingface dataset:
[SuperSU] power2top:
Hi [MENTION=631273]Chainfire[/MENTION],

I installed 2.14 from playstore after I already reported that 2.13 did not work for me due to the notorious binary update issue. Then I did the same stuff you mentioned and quoting you:

As given by you above, I selected 'No' for both disable recovery rom and 'fix' permission/root access in CWM and on phone start, I dont see 'Su binary needs to be updated' error BUT when I go to SuperSu app, the app fails with the error message: 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'

What to do now?
[SuperSU] GT9070:
Dear Support, I have installed SuperSU version 2.14 and I will test them. I have one question:

I have notify that if I execute the command

su -v

via terminal emulation the output show 2.13 instead 2.14. If I click on the SuperSU icon I view 2.14.

Let me known.

Rgs Joe
[SuperSU] commencal661:
Probably because the binary wasn't updated, but the app was.
[SuperSU] Giobio:
I notified the same of gt9070. Do you know what to do to put in place that?

Thanks
[SuperSU] commencal661:
Let me rephrase myself: binary (probably) wasn't updated, because it (most likely) works as it should. The app had problems installing that binary, that's why Chainfire updated only the app. But I might be wrong.
[SuperSU] Giobio:
When I update to v. 2.14 I had no problems with update so i thought to have it. I read last posts and I think they're talking on to that issue but so technic for my knowedge....
[SuperSU] commencal661:
Then you probably shouldn't mess with the root.
[SuperSU] Giobio:
Noooooooooooooooooooooooooo don't tell me that!!! :)

The only steps I took was to install SU with this zip file: Root_SuperSU.0.98-Busybox.1.20.2-signed and then updated with UPDATE-SuperSU-v2.14.

Usually I use the chainfire store app but not last time. Could be that the reason?

And more averytime I use recovery, before restart the device I have to fix root(/system /xbin /su)...
[SuperSU] commencal661:
Does it work? Yes? Then why do you care about the version number?
[SuperSU] occtec:
Because that's what this thread is all about my friend. Test & Report ;)
[SuperSU] Giobio:
Yes, it seems to work for me, but as gt9070 said emulator gives v. 2.13 but I installed v.2.14

I'd like to put an image from my pc but I don't know how
[SuperSU] GT9070:
Hi, I have update the 2.13 to 2.14 via Playstore on 2 mobile phones (GT-I9300 & GT-I9070) W/o issue and performed also the reboot at the end.

If I perform the command

su -v

I receive 2.13 instead of 2.14.

Maybe is a bug on the new version that does not update correctly the version.

Let me known.

Rgs Joe
[SuperSU] zadigre:
same here... but if SuperSU app says 2.14 and it does not ask you to update the binaries, you are perfectly fine.

2.14 probably has the same binaries that 2.13 had...
[SuperSU] Giobio:
I don't know how to say more than you already know. I used the terminal ( su -v) because you wrote down it and checked on mine. I hope somebody from the brave soul will post the answer....
[SuperSU] khairulez:
Try wipe cache and dalvik-cache via recovery then reboot.
[SuperSU] jesssiii:
Me too, but all works well.
[SuperSU] kiorio:
Hello everyone. I found a strange bug in the latest version ... I use a program AutomateIt-Automate You Droid and when he was set SuperSU V2.01 everything worked, but when I install SuperSU V2.14, then you restart AutomateIt disappears from the list of applications in SuperSU.

I'm sorry for my english)))
[SuperSU] kingvortex:
To all complaining the binaries aren't version 2.14. If you search/read back in the thread, you will find this post by Chainfire that states the only difference between 2.13 and 2.14 is something to do with installation. So it's highly likely that the binaries were not altered. For what it's worth, su - v returns 2.13 on my device also, so it seems normal.

In any case, multiple posts aren't needed on this. If there's a problem, Chainfire already has enough people reporting it by now. :)
[SuperSU] USBhost:
O sorry will delete my past post
[SuperSU] Giobio:
same here....

---------- Post added at 07:07 PM ---------- Previous post was at 07:03 PM ----------

Tried but still v.2.13 and not 2.14

I think kingvortex is right.
[SuperSU] ramjet73:
I actually thanked your last post because you had some valid feedback but I see nothing useful this time.

Auf Wiedersehen!

ramjet73
[SuperSU] tuilalnvinh:
Exactly same for me with EasyTouch app.With v 2.14, after I granted the supersu for easytouch to show reboot menu, i restarted my phone (G3 f460s). then I checked the app list of supersu, easytouch entry item disappeared, which do not happen in supersu v2.01,and i have to regrant the access after every reboot phone
[SuperSU] lagunriv:
SuperSU in my future ROM

How can i root my ROM?... i mean, before to flashing?...
[SuperSU] kingvortex:
Go to your device forum and ask/read around.
[SuperSU] galaxyvn1411:
same issue here. anyone know how to fix or work-around?
[SuperSU] mcnaught82:
Uncheck Re Authentication. That worked for me
[SuperSU] mike69290:
I need support in the support topic please:

http://xdaforums.com/showpost.php?p=56147531&postcount=10
[SuperSU] kingvortex:
First, there's no need to cross post questions. People are in different time zones and may not answer immediately. ;)

The post you quoted in that thread actually gives you the answer in any case. If letting CWM "fix" root actually breaks it, then what do you suppose you should choose? :D
[SuperSU] Chainfire:
If these apps are installed to the sdcard, disable re-authentication. If these apps are *not* installed to the sdcard but you still have this option, please say so, because then there is a problem (might still be fixed by disabling re-authentication, but I need to know about it!)

Also, each of you, which Android versions, device and firmware ?
[SuperSU] USBhost:
NVM
[SuperSU] kiorio:
Thanks Chainfire, for your attention!

Application AutomateIt installed in the internal memory + disable re-authentication = after reboot everything is fine.

Application AutomateIt installed in the internal memory + included re-authentication = after reboot disappears from the list of applications.

P / s

device: HTC Butterfly S

Android version: 4.4.2Stock ROM version: 4.10.708.1 + S-OFF + BusyBox
[SuperSU] amardeep434:
su binary missing

I updated my super su app to latest version from playstore after that i lost my root access. When i opened super su it showed no su binary installed and supersu cannot install it.

My device :- mmx a110q

Rom :- xperia z2

Android v4.4.4
[SuperSU] Wh1t3Rose:
Reflash the zip

sent from my Lollipopped N5
[SuperSU] tuilalnvinh:
FYI

Thanks [MENTION=631273]Chainfire[/MENTION], for your quick response! Same symtom from my case:

EasyTouch app (long-touch screen-off icon to show power menu, which trigger supersu prompt) installed in the internal memory + disable re-authentication = after reboot everything is fine.

EasyTouch app installed in the internal memory + included re-authentication = after reboot disappears from the app list.

FYI:

My buddy: LG G3 cat6 F460S

Android version: 4.4.2 Stock

ROM version: F460S10K + xposed FW + greenify + BusyBox

:confused:
[SuperSU] Chainfire:
I completely missed this report. This is a bad crash! Still happening I assume? We must debug.
[SuperSU] Rintenfinten:
I installed the Pro Version for my Samsung Galaxy Note N9005 via Playstore. However, I only get version 2.01, not 2.13/2.14 as stated here. What is the reason for this?
[SuperSU] kingvortex:
The latest version is on a staged rollout. This means only a certain percentage of users get offered the latest version. See this post by Chainfire.

A staged rollout is usually used to minimise possible problems with an update. When/if the update has been successfully rolled out to however many users Chainfire decided on without problems then I'm sure it will be rolled out to everyone.

In the meantime, you can install it manually with the zip linked in the first post. :)
[SuperSU] Rintenfinten:
OK, thanks for the quick the answer.

I think however that I cannot install the ZIP version from here. Reason is that my N9905 is rooted with Towelroot and still has Knox 0x0. So I have no custom recovery to install this zip because this would trigger my Knox counter to 0x1.
[SuperSU] zadigre:
the apk is in the zip... extract zip, look into the common folder... you will be able to install the apk manually.
[SuperSU] jesssiii:
I'd wait for the update. But if you really need the latest version, you could use Flashify from the Play store to install it.
[SuperSU] mindmajick:
nvmd
[SuperSU] USBhost:
Yep its still happening
[SuperSU] Chainfire:
Which exact device / ROM / kernel / etc, when does the crash occur exactly, etc. Need more details.
[SuperSU] USBhost:
Nexus 7 2012 wifi

ROM CarbonROM

kernel M-kernel 3.1.10

T Mobile note 3 nf9

kernel Colonialx 3.4.103

ROM tweaked

you can also look at my signature

When I do su / something

That Crash happens
[SuperSU] amardeep434:
Dude i reflashed the zip and the super su app disappeared and if i redownload iy from playstore then it shows the same error again
[SuperSU] amardeep434:
:3 meme's plz tell me solution.
[SuperSU] ^tyrant^:
Stuck trying up to update binary, its just sitting at "installing please wait"..

I have rebooted and tried it a second time, and still nothing, and after rebooting i can no long see my apps list or logs i just get a spinning wheel.

I can get into setting part, thats about all i can do.
[SuperSU] netfortius:
" Happy" to see someone with identical issues, in regards to apps and logs parts (see my previous post on this thread). At least I was able to update to 2.14app/2.13 binary.
[SuperSU] Chainfire:
I have not been able to reproduce this crash, after going through the trouble of replicating your Nexus7 setup with CarbonROM and F2FS and everything. It is familiar though, but it should have been fixed some time ago. Any more info you can give me?

Did find a binary update issue with permissive systems if they were booted as enforcing and only switched to permissive later, though, so that's something.
[SuperSU] Chainfire:
Please provide the logs as requested (read the OP) in this thread: http://xdaforums.com/apps/supersu/support-update-failures-t2907365

So many people complaining, nobody willing to do the work.
[SuperSU] netfortius:
Sorry. Missed that thread. Will produce logs over the weekend.
[SuperSU] ^tyrant^:
Here are logs prior to trying to update the bin.

I have tried to update the bin after doing a factory reset and then rerooting with CF auto root again, and it still had the same issue. so i did another reset and started reinstalling all my apps.

Device:	Samsung Galaxy note 10.1 (2014) sm-p600 Rooted with cf auto root

Android:	4.3

Kernel:	3.4.39-2040736

se.infra@R0301-06 #1

Fri Nov 1 15:07:36 KST 2013

SuperSU 2.14

Tried updating bin via in app normal mode.

I will try to update the bin again later today, and will post logs from that.
[SuperSU] ^tyrant^:
Ok so i went ahead and tried to update the bin. Update failed let it sit for the 5 mins, did not reboot, ran all the adb commands to make new logs.

After rebooting, installed root checker to check to see it root still worked, when it tried to run the box came up asking to grant it root, i did and root check fails, same with titanium backup they both say no root.
[SuperSU] USBhost:
I made a screen shot

Im not the only one

because I made an app using that su / function

I stayed on v 2.02 on my note and everything works fine
[SuperSU] Chainfire:
what is "su /" supposed to do? its not a supported command or syntax. if it does anything, that's by accident, not by design.
[SuperSU] USBhost:
Su / allowed me to execute a command as root once and it gave an flash message saying which command was executed

So using su /

I made sudo = su / "$@"

so it made my phone/ tablet more Ubuntu like

If it was by accident

can you put it back
[SuperSU] Chainfire:
Use su 0 command or su -c command instead of su / command
[SuperSU] USBhost:
awesome thank you!!
[SuperSU] Chainfire:
v2.15 posted: http://xdaforums.com/showpost.php?p=56226364&postcount=293

binary update / installation / loading issues fixes only. no feature updates
[SuperSU] jowilk:
Hi Chainfire, this question is off topic but since there aren't any post for note 4 at&t, I was just wondering if you have a time frame for rooting at&t note 4. Please no flames. Btw, your apps & the best. Thank you for them.
[SuperSU] Chainfire:
AT&T == Verizon == locked bootloader. I don't do locked bootloaders. Pray for someone to find an exploit that works. Could well be it will never get root.
[SuperSU] okidokiss:
Installed 2.15 trough TWRP recovery, over 2.14.

Seems to work OK on my phone, as 2.14.

Now the CLI su -v gives SuperSU 2.5 as output
[SuperSU] Celestial Fury:
Installed 2.15 beta and it updated the binary and also installed as system app without problem.

However, the previous grant/deny request for one app in particular still persists upon every reboot. The app is Hotspot Shield VPN. Full logging in SuperSU shows only one line (attachment 1). It's installed to INTERNAL SD Card.

I'm using VpnDialog XPosed module (attachment 2) if this is a factor.

Disabling re-authentication works in that grant/deny request no longer shows up but it now shows a persistent app denied SuperSU toast for that app upon every reboot even though notifications are set NOT to show in SuperSU.

If all is working as it is then it would mean that com.anchorfree.service is reinstalling/upgrading itself upon every reboot which is detected by SuperSU.

Actually, come to think of it, VPN needs to be re-enabled after every reboot, by design? Not sure if SuperSU is meant to catch this. Disabling re-authentication isn't a solution as I want to re-authenticate for actual reinstalls/upgrades.

Funny thing is, my VPN still functions even after denying com.anchorfree.service.

My details in sig and attachment 3.
[SuperSU] Chainfire:
Unfortunately, I have not yet been able to replicate this internal sdcard issue. I did make some changes to this system in the upcoming release, though. So please do test again after I release the new update later today or tomorrow.

If you move the app to main storage, is root still forgotten? This is an important, not all these forgotten apps are due to being on sdcard, but some are.

Can you look real closely at the denied notification? Is it a normal notification, or does it say something like 'these apps have been silently denied...' ?
[SuperSU] tsow:
audax rom 10.9 SU can't grant clean master app.

I have a grant problem on audax rom 10.9 note 3 the SU app can't grant clean master

app.Sorry for my bad English.
[SuperSU] pycxe-01:
SGS4 & SetCPU & SuperSU v2.14

I am having issues with SuperSU v2.14 & SetCPU apps. Namely, ever since the update to v2.14 the "com.mhuang.overclocking.ProfilesService" is requiring re-authentication again and again, and again. As I understand from the comments herein, it has something to do with the binary update of the latest SuperSU v2.14. Just in comparison SuperSU v1.80 worked as a charm on my Samsung Galaxy S4! Please fix!
[SuperSU] Celestial Fury:
Main storage? Sony Xperia Z1 doesn't support moving apps to external SD Card. When I said internal SD Card previously I meant installed on phone (SD Card 0).

It looks like a normal denied notification (attachment 1).

hotspotshield.android.vpn is the actual vpn service (attachment 2, toast by VpnDialog XPosed module).

However, it doesn't show up in SuperSU's app list or log at all. I can't remember if this service was granted SuperSU permission previously but I think VPN needs root to function (note: Hotspot Shield is not an Xposed module, it probably needed to have been granted SuperSU permission previously).

I don't know what com.anchorfree.service is supposed to do but denying it root permission doesn't affect vpn.

In short:

com.anchorfree.service isn't needed but shows up in SU app list & log and keeps wanting permission upon every reboot.

hotspotshield.android.vpn is needed, probably has root permission but DOESN'T show up in SU app list & log.
[SuperSU] Bexton:
Fyi: The init_shell domain was removed from AOSP master:

https://android.googlesource.com/pl...37d6b57138f485c5c128c07a2d7b6011d2ac3a4^!/#F0
[SuperSU] Scipizoa:
so am I to understand I'm not the only one not having luck getting titanium to work with supersu 2.14 and 2.15 running android 5.0? or am i doing something wrong here.

p.s super SU never asked me to update binaries what so evers
[SuperSU] timeToy:
I also never got a prompt to update the binaries with both 2.14 and 2.15
[SuperSU] Scipizoa:
[STABLE][2014.10.15] SuperSU v2.14

I wonder if that's why titanium is failing to access root. Despite root checker saying i have it
[SuperSU] ridobe:
What version of TiBu are you using? Are you using the beta L version?

Link: https://www.dropbox.com/s/xwjv9pvj0h6vx6l/TitaniumBackup_6.2.0-test6_r343_Market.apk?dl=0
[SuperSU] Scipizoa:
[STABLE][2014.10.15] SuperSU v2.14

Oh oops. No. Lenme try that.. Sorry

Ok beta version works, thanks
[SuperSU] egingell:
Ideally, if you flash SuperSU via recovery, you will not get a prompt.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Scipizoa:
I didnt know they lol sorry for being bothersom
[SuperSU] GT9070:
SuperSU 2.15

Dear All, I have installed SuperSU version 2.15 and the issue notify in topics #7001

su -v was showing 2.13 instead 2.14 is now fix with 2.15 and now I receive 2.15

Rgs Joe :)
[SuperSU] Bright09:
Could someone help me I can't get system uid to grant it won't let me and I'm running stock 4.3 i535 stock recovery had it done before I had to wipe my phone the other day
[SuperSU] MrKaon:
I have a question guys:

If final version of lollipop stays same as latest preview L regarding root situation once it released to other handsets by manufacturers then for having root every handset model must be flashed with specifically modified kernel?
[SuperSU] Chainfire:
v2.16 beta released - http://xdaforums.com/showpost.php?p=56257257&postcount=318 - some fixes and some L lovin'
[SuperSU] Bright09:
Can someone help me get my system grant working
[SuperSU] CamoGeko:
Did anyone post the SuperSU 2.16 zip link here? I didn't find it by searching. :(

Sent from my N⁴ running Android L
[SuperSU] beany>:
Link two posts before yours...
[SuperSU] CamoGeko:
Oh sorry, that was me being a bafoon. Maybe because I've just woken up lol

Thanks for the heads up!

Sent from my N⁴ running Android L
[SuperSU] It_ler:
Maybe your eyes are getting older ? [emoji12]

No issues for me on latest SuperSU so far ?

My tapatalk signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v5.4

Kernel:

Stock G900FXXU1ANG2

Recovery:

TWRP

Modem:

G900FXU1ANG7

If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.

... for the SGS5, just ask in the Noob friendly S5 All in one support thread

If you need general help/assistence, please go to XDA-Assist.
[SuperSU] Chainfire:
FYI, I'm upgraded 2.16 to stable... as in, it's going to roll out on Play to everyone who had previously been updated by Play to 2.14. It's still a staged rollout, though.
[SuperSU] Ritvars:
Updated SuperSU through the Play Store and then it asked to update binaries, which I did. Of course, it asked for a reboot, which I did also, and I got stuck in a bootloop. Good thing I had a nandroid backup from ages ago (it will take days to restore everything I had). The only downside was that I didn't have a backup on my apps which is a bummer. I don't want to believe that this is because of SSU. Now I'm afraid to update it again as it shows on my store that an update is available. Interesting.
[SuperSU] egingell:
I'm fairly sure he has a separate thread for issues related to updating. Bring logs.

P.S. You probably only needed to restore the system partition (Advanced Restore as I recall).

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] juggies:
Does this L support include the current build?
[SuperSU] =dgim=:
I've updated to 2.16 (installed by twrp 2.8.0.1 on Optimus 1.4), I'm still have inactive buttons (permission/deny) in SuperSU app. When any app prompt to root access I can't set it at all, I don't know why.
[SuperSU] egingell:
That question has been answered numerous times. Either uninstall overlay apps or turn off tap jacking protection.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Ritvars:
It somehow updated itself and I risked and rebooted after binarie updating and this time everything was fine. Idk what happened before.
[SuperSU] =dgim=:
Turn off tap jacking protection solved my issue. Thanks
[SuperSU] Murshad007:
Installed through google play over V2.14.

Perfectly working

Sent from My LG Optimus G F180L Sling 2.2.2 stock 4.4.2 rooted
[SuperSU] samuele94:
Both installed on samsung galaxy next turbo (gt-s5570I) and on Lg g2 (D802) through play store and it works perfectly on both phones,thanks Chainfire
[SuperSU] Wimmme:
nevermind. Delete plz

Edit: might as well use this post to report 2.16 working fine on my Lg G2.

Big thanks !
[SuperSU] netfortius:
[MENTION=631273]Chainfire[/MENTION] - as I was planning to send all the logs ref the "spinning wheel" problem in apps and log tabs, on ver 2.14, I thought about trying 2.16. Happy to report that the problem was solved!! Thank you for an invaluable app and latest fix!
[SuperSU] Dr Goodvibes:
Sony Xperia C1905 Android v4.3 and SuperSU v2.16

Chainfire, happy to report my Sony Xperia C1905 Android v4.3 is working fine with SuperSU v2.16

Had problems with SuperSU v2.14 where phone went into a boot loop after SuperSU v2.14 binary update.

Xperia M (C1905) OK now after rebuild

After a new re-build/re-root I could install SuperSU v2.14 and binary update without problems.

However, SuperSU v2.14 introduced a setCPU application root permission request on each power-on with SetCPU application displaying numerous toast notifications.

Happy to report the SetCPU root request on phone power-on is gone now with SuperSU v2.16 (this is good) .

Did get a root request on the first power-on of the phone after the upgrade, which looked pretty ugly by it's nature, but see no more requests now after numerous power-on reboots.

[IMG="SetCPU root request"]http://xdaforums.com/attachment.php?attachmentid=2985294&stc=1&d=1414291096[/IMG]

Still get the odd toast notification which is no biggie and not causing any problems

SetCPU[UID] has been granted supersuer

Permissions for an interactive shell.

Thank you Chainfire for your support and helping us out (which is probably more like trying to herd cats, with the way we act :D)
[SuperSU] sheikhramnuj:
is it safe to flash this latest version on twrp? it wont cause any problems? Btw im using Lg g2 d802 running optimusg3 1.4 with the latest twrp version 2.8.0.1. Thanks for your answers!;)
[SuperSU] CyberpodS2:
Since you can flash stuff you can most likely do a nandroid right? Just do s back up and if it goes south restore and no harm done. But if it goes well, report back here that all is good or what is wrong. :)
[SuperSU] Sky007FR:
Google play version ? 2.01 or 2.16 ?

Hi everyone,

I have two Nexus 5 with two different google accounts (mine and my wife account).

On my main phone, I can only see 2.01 version on google play. On the other one, I see the 2.16 version.

Is this normal ?

If I use the 2.16 apk to update the 2.01 version from google play, can it be later updated automatically on google play ?

Sorry if the question was already asked before... :angel:

I am not a pro in "rooting", I only use basic rooting stuff (Titanium backup, Stickmount) with official ROM .

Thank you ! :good:
[SuperSU] zadigre:
Yes this is normal. Yes you can take the apk to install

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[SuperSU] jesssiii:
Yes, I have the Verizon version of the LG G2 and the same twrp. Flashed this and it's great.
[SuperSU] sheikhramnuj:
Ok. i will flash this one. Thanks!
[SuperSU] simonbigwave:
i updated to SuperSuPro2.16 via playstore update, on CM 1024 nightly GT-I9505. all ok but I cannot grant supersu access for Pryfi app. the supersu toast notification comes up, but cannot click grant or deny buttons.