yashsingh1/xdaforums huggingface dataset:
[SuperSU] nathanchance:
Guys, seriously, can we stay on topic? The addition of analytics has been talked about here and here and the change in ownership has also been discussed ad nauseam (see my post here). You don't like it? Switch to one of the open source root solutions floating around. There's ALWAYS been risk when running root period, where it be open or closed source and regardless of ownership. It's escalated privilege on your phone that can disregard both Android's permission model and SELinux.

Chainfire has said several times he's still closely involved with the project as recently as yesterday (source) and he wants this thread to focus on fixing the issue (source), not complaining about things that can't be changed. Thank you.

The Flash

Forum Moderator
[SuperSU] micr0g:
Pixel user and I can confirm SuperSU-v2.80-20170525215916-bindfix works with adaway but not after the playstore 2.81 update.
[SuperSU] Chainfire:
Don't worrya bout it then :)

Please try specifically with v2.80 which can be found here: https://xdaforums.com/showpost.php?p=72429329&postcount=9810

v2.81 is an older version masking as a newer version, future updates will be based on v2.80.

I assume in one terminal you did and the other you didn't use su? Then it might be comparable.

I'm really not sure what is going here. I am sorry but this is not a priority for the next update (the root loss and bootloops are). I do want to get to the bottom of this though. Remind me next week if I haven't picked it up myself by then.

As for suhide, I have two different implementations fully operational, they just aren't released at this time. It's a long story I will post when I get ready to release.

Thanks, I will look into this.

Thanks, I will look into this.

Please try specifically with v2.80 which can be found here: https://xdaforums.com/showpost.php?p=72429329&postcount=9810

v2.81 is an older version masking as a newer version, future updates will be based on v2.80.

Busybox shouldn't matter, but sometimes it does. Nothing breaks root stuff like busybox does. Which busybox installer have you used ? Which version did you have when you bootlooped ? Maybe that is what's missing from my own Xperia Z tests.
[SuperSU] erfandl:
which version fixed xperia boot loop ?
[SuperSU] Chainfire:
Neither, we are still trying to find the problem. Though you could try either version and see if it helps.
[SuperSU] Chainfire:
Re: Analytics

Since people do keep bringing it up, I have conferred with the CCMT guys in Beijing to make sure we have all our facts straight.

There are two different builds of SuperSU, one for the Chinese market (which is used on dozens of non-Google-Play appstores), and one for the international market (Google Play, XDA, supersu.com, my own servers, etc).

The international version (the one we should all use), does not contain any analytics at this time. I was previously told it would be coming, but apparently it is back up for debate. If it will be coming, it will be based on Google Analytics / Firebase, and it will be announced before it is introduced (if ever).

Instead of analytics, we have the feedback screen (reachable from the bottom of settings), that allows the user to gather device information and screenshots to submit detailed information back in case of issues. This screen is for a large part responsible for the newly required permissions. Those permissions are under review, and we are considering an alternative for that screen altogether.

The Chinese national build does have some analytics, but I've been assured that it is a custom package (and not the package found by an Aptoide user and reported earlier in this thread) and it does not transfer any personal/identifiable information. You should be aware that various app stores (but not Google Play) add (unsanctioned) tracking packages to many of their downloads, and I would question the logic of being afraid of analytics yet downloading unofficial versions of packages like SuperSU from random places like Aptoide where its origins cannot be confirmed.

UPDATE: Starting v2.82 (Google Play release) the entire feedback screen has been removed, dropping the need for those permissions recently introduced.
[SuperSU] hbbxmjbb:
Something wrong happened when I flashed 2.81,I flashed 2.80 and the root came back.

cancro Lineage OS14.1-20170508nightly
[SuperSU] Strephon Alkhalikoi:
[MENTION=631273]Chainfire[/MENTION]: Aptoide is noted for hosting paid apps and allowing users to download those apps for free. But Aptoide isn't the issue. The issue has always been the Chinese connection and not trusting that connection. The change in app permissions is enough to send most people into a panic because they don't trust the people behind it. Honestly, I can't blame them. If it could make me pause and reassess things, then perhaps you should do the same and ask yourself, "is this what I really want?"
[SuperSU] hbbxmjbb:
Because some Chinese companies bought the good applications and did something bad.
[SuperSU] mauam:
Yeah, good old days when SuperSU belongs​ only to Master Chain:cool:
[SuperSU] Ps24u:
Ok, which one should I try, the "bindfix" build or the other?

My rom was pre-rooted so I cannot tell you which busybox build was used, sorry.

All I can say is that this Busybox says I have 1.22.1 installed to /sbin/ and that's it's prompting me to install 1.26.2 to /system/xbin, but I didn't do it.
[SuperSU] shoey63:
Not happy? There are alternative root solutions.
[SuperSU] mauam:
You can check which BusyBox you have with terminal app, typing su then press enter, then type busybox & press enter again.

---------- Post added at 12:53 ---------- Previous post was at 12:48 ----------

Yes not happy. Anyway I use magisk. Chill out mate & don't start the "fanboy thingy". Otherwise will be a clean up thread once more. Have a nice day.
[SuperSU] Coronado is dead:
Hmm, said binary needed updating this morning, update failed, lost root.
[SuperSU] Ps24u:
It says not found..

View attachment 4161970
[SuperSU] veez21:
Go a few pages back, that has been discussed and solved
[SuperSU] shaggyskunk:
Yeah and if you read Chainfire's post a couple before yours - You would have known not to Flash v2.81 ?

https://xdaforums.com/showthread.php?p=72434853
[SuperSU] starbase64:
[MENTION=631273]Chainfire[/MENTION]

v2.80 and 2.81 doesn't work for me, 2.79 r3 is latest working root

installer ends on patching sepolicy
[SuperSU] bbender716:
For what it's worth, 2.81 did not work on May stock Pixel but 2.80 with bindfix worked great.
[SuperSU] sash11:
2.81 zip did not work on my Oneplus2 with latest Lineage OS from recovery. During install I've seen one error, something to do with SELinux. After I booted into system, su was saying that it is occupied. I ended up installing 2.79 from recovery and updating from Google Play to 2.81
[SuperSU] koekoek91:
Could it be you are also running magisk?

The su being occupied message occured to me too and it was when I flashed SuperSU while also running magisk.

It was fixed for me by flashing the uninstall magisk zip in recovery.. then SuperSU worked normally without issues.
[SuperSU] tdunham:
To prevent confusion on version testing, I'm pretty sure we shouldn't be testing with the Google Play version.

Chainfire has requested only the versions (linked below) be used for testing and reporting.

Chainfire quote:

Please perform all testing with the attached SuperSU version, not officially released v2.80 or v2.81.

As this post will probably be updated with new files, please include the exact filename of the ZIP flashed in your reports.

https://xdaforums.com/showpost.php?p=72429329&postcount=9810
[SuperSU] queerquirks:
V2.80 Bindfix working great, Pixel 7.1.2
[SuperSU] bbender716:
Yes. That's the version I'm referring to.
[SuperSU] starbase64:
Tested zip files from this post

https://xdaforums.com/showthread.php?p=72429329

2.80 update works

2.81 not
[SuperSU] SAGI1:
V2.8.0 Bindfix worked for me also N7100

After flashing stable v 2.8.1 and got boot loop and than "Binary occupied" and "No Root detected"

I flashed v2.8.0 and it seems that everything is OK,

I just worry that v2.8.1 will be installed automatically via the play store update.

for conclusion

Note 2 N7100 t03g worked OK with v2.8.0 bindfix

tested on AICP ROM 26/05/17 nougat 7.1.2
[SuperSU] shaggyskunk:
Are people simply NOT reading the posts before they post??

https://xdaforums.com/showthread.php?p=72438254
[SuperSU] osm0sis:
Also, many people acting as though it's difficult to disable auto-updates for SuperSU in the Play Store until this is all sorted. :rolleyes:
[SuperSU] Ch3vr0n:
It is impossible (at least i havent found out how) to disable auto updates for JUST SuperSU. Afaik it's auto updates for either for ALL aps or for none at all
[SuperSU] tdunham:
PlayStore/Settings/Auto-update apps

Do not auto-update apps

Is it really that difficult to disable updates for a few days and selectively install if you REALLY feel the need?
[SuperSU] shaggyskunk:
I just have Store Auto Update turned OFF - And that way I can always see what updates are available and decide if I want to update all or just the ones I want to update.
[SuperSU] drewski_1:
this is a new phenomenon? :p
[SuperSU] andrei1015:
I have a Nexus 5 and after the last update to 2.80 I've lost rrot. This never happened before. I've tried reflashing the su_addon zip but no dice. What is wrong, any idea?
[SuperSU] osm0sis:
Not so. Go to the SuperSU app page in Play Store and uncheck the auto-updates box in the overflow menu.
[SuperSU] Nimueh:
Go to Playstore on your phone, SuperSu

3-dot menu

Untick "Auto Update"

Done :cool:

Edit: Ninja'd by [MENTION=4544860]osm0sis[/MENTION] :laugh:
[SuperSU] tdunham:
After testing thoroughly both 2.80 test files posted here, everything is working very well. I don't notice a difference with Adaway with/without the bind version.

https://xdaforums.com/showpost.php?p=72429329&postcount=9810

Bonus fix for us on the Samsung Note 5 though, the standalone installer no longer hangs at 'creating image' on either build so I guess the mount /dev bind issues have been addressed in these builds. :good:

---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------

What update? Play Store update is not valid right now. Please read back at least a page or two.

What addon zip? Same applies as above, there are multiple links to the VALID 2.80 test versions that Chainfire posted here recently to hopefully resolve some of these issue.

Edit: And for a clean install of SuperSU, you may have to also flash a clean kernel (stock or otherwise) to start over in case it cannot patch any 'already' patched kernel. [MENTION=1143630]osmosis[/MENTION] posted an UnSu uninstaller utility you can search for here as well that may prove useful.
[SuperSU] jcmm11:
Some may not be aware that's possible? For those that don't know it:

Go to the app description in the Play Store. 3 dot menu in upper right hand corner. Uncheck the box.

To globally stop auto-updates go into Play Store settings|auto update apps|do not auto update apps
[SuperSU] Ch3vr0n:
Hah such a simple thing, god knows how many times i disabled global auto updates. Never to old to learn something. Thx :)
[SuperSU] martyfender:
I solve that by tuning off automatic updates in the playstore. I always keep automatic updates off.

For example: I am using the bind fix which shows a version of 2.80. If I had auto updates on, the 2.81 available on the playstore would overwrite it. In addition, I sometimes alpha and beta test an app where the one on the app store is the beta or stable which would overwrite the alpha or beta. In this case lspeed.

Most people though, aren't Android enthusiasts like us an just want to use the phone and get a fix of their social media. They never want to worry about updates. They just want auto updates that work without problems.
[SuperSU] corkiejp:
It is also possible with TiBu, to detach apps from the market. But is only temporary, after a reboot they reattach again.

After posting on the 24th that 2.80 was available, I still haven't tried to update supersu. Because as far i could see they where no changes other than for devices on O!
[SuperSU] andrei1015:
Ah thatnk you, I will try this!
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], in addition to my last post (i had quoted above) i would like to add the following...

1) I had noticed that, after flashing the v2.80, an SU Binary File was present in both the "/system/bin" and the "/system/xbin" directories but, after, i had flashed the v2.79, the SU binaries were only present in the "/system/bin" directory.

2) I had performed a little testing of my own and had created a "binary update" flashable zip.

Please keep in mind that I've created these binary updates before on numerous occasions and have always had success with them (and other members stated so as well).

With these binary update packages, i only include the SU binary file and the SuperSU apk file (labeled as base.apk).

For testing purposes only, I had first successfully flashed the full SuperSU v2.78. Then I had successfully flashed a binary update file created with the Stable v2.79 SU binary file and the SuperSU apk file (renamed base.apk). Everything was golden and no issues. Then I had successfully flashed the full v2.79 SR3 with no problems. Then I had flashed a v2.80 binary update file, again with the SU binary file and SuperSU apk (renamed base.apk), then the same issues began as previously reported.

My reasoning behind this is to see if i can, somehow, isolate the issue in an "unconventional" way.

Based on what I've seen, I'm under the impression that the issues, I've previously reported/experienced, may be tied to either (though, I believe ultimately) the SU binary or the apk file itself (though i don't feel that this is the likely culprit).

I hope that you will find this helpful, even in a small way.

Thank you for your time and understanding!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Taomyn:
Here's a question. Why was the version uploaded to Play Store not tested here?

I was running SR4 without a single issue and then was prompted for v2.80 - one would think that without further betas that perhaps v2.80 was a release version of SR4, but that doesn't appear to be the case. If v2.80 had come out here first, none of this would have happened to non-testers.
[SuperSU] corkiejp:
As already stated that it was staged roll out and no problems where flagged on early devices.

No point rehashing the same point, that has already been brought up!
[SuperSU] Taomyn:
I was well aware of that. Still, a staged rollout to production of an untested application is not a test that should ever be performed first. Anyone developing knows that, and which is why we are here on this thread helping to test these things out before the general audience.
[SuperSU] milocj:
I have nexus6 with PureNexus rom 7.1.2 with BL4CKB1RD kernel 2.2.2. I flash supersu 2.8.bindfix.zip and all works fine. Before,i install update from PlayStore to 2.81 and crash supersu. Reflashed 2.80bindfix and all works.Sorry for my bad english

Enviado desde mi Nexus 6 mediante Tapatalk
[SuperSU] earlgrey_44:
Device : Nextbit robin

Rom/kernel: omni 7.1.2

The above su file successfully establishes root, root dependant apps all functional, (Including Adaway) no error messages or binary update requests seen.
[SuperSU] Danilo Pantelić:
Nexus 6P 7.1.2 android version.

Problem with 2.81, but UPDATE-SuperSU-v2.80-20170524085154.zip solved problem. [emoji106]
[SuperSU] mauam:
It means you have no busybox installed.
[SuperSU] Chainfire:
Try the bindfix version, see what happens.
[SuperSU] Ps24u:
Well, this system is rooted ok and all previous versions of SuperSU have worked flawlessly on it.
[SuperSU] bradmoss:
I could not find any problem with version 2.81, where should I look at?

Using Moto G 2015 and Samsung Galaxy Tab 3

Should I revert to 2.79?

Thank you!
[SuperSU] Wolfcity:
Flash one of the 2.8.0 files that [MENTION=631273]Chainfire[/MENTION] postet a few pages back if you're willing to test. Future updates will base on 2.8.0.
[SuperSU] bradmoss:
No, I am not willing to test right now, I want to know if it is safe to stay with 2.81
[SuperSU] Chainfire:
On my HTC10 (S-ON) running 2.28.401.9 / Android 7.0 / Nov 2016 security patch, v2.80-bindfix works without issue.

Downloading a newer firmware now, will test that and update this post with my results.

EDIT: Also works for me on 2.41.401.3 / Android 7.0 / Jan 2017.
[SuperSU] Chainfire:
If there's no problem, there's no problem, and no action is needed.
[SuperSU] bradmoss:
No problem that I can see hence my question
[SuperSU] Chainfire:
Thanks for the info and the kind words.

The truth is, sometimes problems seem like the end of the world on this forum, but SuperSU has dozens of millions of active users. The fraction of users these problems affect isn't all that big, but that still leads to a lot of reports.

The root loss is (mostly) contained to devices that haven't seen an official update longer than your M8; the bootloops appear to be contained to Sony Xperia; and the AdAway issue only affects some 6.0+ devices, and most users affected may not even notice before the fix is released.

There is virtually no major SuperSU release deployed without a hitch, but this time the problems are somewhat bigger than usual. Such is life.
[SuperSU] NLBeev:
Play store - <app name> - 3dots ( right above ) - uncheck Auto-update
[SuperSU] rickysidhu_:
Just wanted to quickly confirm that the bindfix version of 2.80 works on my Pixel XL running PureNexus and EX Kernel

So far so good!

Apologies if someone else has already confirmed this, but hopefully this post is of some help:)
[SuperSU] Chainfire:
I've added v2.82 to the test versions post.

This is the same code as v2.80-bindfix, but I changed the version code so Google Play doesn't auto-update to v2.81.

( https://xdaforums.com/showpost.php?p=72429329&postcount=9810 )
[SuperSU] corkiejp:
Am i still right in thinking that the 2.8x versions have only updates that deal with O code and devices that support that?

So no real benefit updating from 2.79-SR3 on older devices/rom, at this time?
[SuperSU] Lord_Flaya:
Just flashed UPDATE-SuperSU-v2.82-20170526223454.

Seems to be as good as it gets on my Nexus 5x running on 7.1.2 with Franco kernel.

Great work as always [MENTION=631273]Chainfire[/MENTION]
[SuperSU] kevtrysmoddin:
Has any one on android o been able to update su through the play store??
[SuperSU] wetxxx:
Guys please give me a post Numer where is 2.8 bindfix version. I have free evening and Can try it :) Now I have 2.79 but I have one reboot when I use Google maps

"Live long and prosper"
[SuperSU] rickysidhu_:
Confirming that 2.82 works on my Pixel XL!
[SuperSU] Ch3vr0n:
how about you read a few posts above yours where chainfire links to it?
[SuperSU] Chainfire:
Not really, but if everything is working fine, everything is working fine :)

Probably not. Try v2.82 linked a few posts above.

The post is linked 4 posts above yours...
[SuperSU] corkiejp:
Chainfire posted the link a few posts above yours. Linked above in the quote as well!
[SuperSU] habylab:
The 2.82 release that avoid Play Store updating works fine on my OnePlus 3, on stock OOS 7.1.1 ROM.

Adaway works, no loss in functionality.
[SuperSU] koekoek91:
[MENTION=631273]Chainfire[/MENTION]

In my previous post here: https://xdaforums.com/showpost.php?p=72435265&postcount=9877

I forgot to mention that I have also tested the SuperSU-v2.80-20170525215916-bindfix.zip that you posted here: https://xdaforums.com/showpost.php?p=72429329&postcount=9810

Both versions worked fine on my Xperia XZ (F8331).

Wish I could be of more help to get the problems sorted out for other Xperia users.

Im confident you will figure it out though, hopefully with the help of other Xperia users who do have the issues ;)

Good luck to all :good:
[SuperSU] Wolfcity:
Agree for Moto G titan running Aosp Extended 7.1.2.

SuperSu 2.82 working, no problems.
[SuperSU] Ps24u:
Is there an apk version of 2.82 to test somewhere?
[SuperSU] Ch3vr0n:
Inside the zip. Other than that no
[SuperSU] chazall1:
Thanks all functioning as expected on UPDATE-SuperSU-v2.82-20170526223454.zip

Great Job
[SuperSU] wptski:
All three versions work the same as v2.79 on a Google Nexus 10 which I went back to, I have root but the SuperSU app doesn't show up in the list from the desktop but does from Setting>Apps. I can't uninstall the app first as mention elsewhere because I can't get ADB to work, maybe never did with this 3 1/2 year old ROM which might be user error! :D
[SuperSU] danilo_scala:
Thanks friend, work in Xperia z5 Premium su 2.82
[SuperSU] bush911:
Thank you dude.

UPDATE-SuperSU-v2.80-20170524085154.zip works fine on Pixel.
[SuperSU] Caltinpla:
UPDATE-SuperSU-v2.82-20170526223454 works fine on Nexus 6P running latest PN 7.1.2 with Franco kernel.
[SuperSU] elhennig:
The 2.82 release works fine on my LG G3 (D855) running ResurrectionRemix 5.8.3.
[SuperSU] guitardoc64:
2.82 is working on PureNexus 7.1.1 and Adaway is working as well.
[SuperSU] amitroutray:
Can u plz share me the link. Want to use it in my Redmi Note 4 mido :)

Triggered from rn4
[SuperSU] guitardoc64:
https://xdaforums.com/showpost.php?p=72429329&postcount=9810

There you go.
[SuperSU] hjjiang:
2.82 works for me with rr 2.8.3 on axon 7
[SuperSU] Chezbel:
UPDATE-SuperSU-v2.82-20170526223454 is working on HTC 10, Android 7, firmware 2.41.401.4, s-off, LeedDroid ROM. Adaway and TiBu appear to be fine.
[SuperSU] snovvman:
Anyone running GSam and 282, please report. I noticed that 2.80 caused GSam in root mode to stop reporting data on Pixel/XL.
[SuperSU] ALIGATOR26:
I confirm v2.82 is working on Samsung Galaxy S7 stock rom with root! Thank you [MENTION=631273]Chainfire[/MENTION]!

Trimis de pe al meu SM-G930F folosind Tapatalk
[SuperSU] amitroutray:
Thanks :) working fine :)

Triggered from rn4
[SuperSU] swagie:
[MENTION=631273]Chainfire[/MENTION]

Can confirm v.2.82 is working on xperia z5 e6653 with stock rom and kernel patched with rootkernel.

Adaway and root explorer work fine.
[SuperSU] wetxxx:
HTC 10 S-ON Android 7.0 2.41.401.4 - SuperSu 2.82 is also working good.

"Live long and prosper"
[SuperSU] ulxerker:
UPDATE-SuperSU-v2.82-20170526223454.zip is also working fine on Nexus 5 X Android 7.1.2 May patch.
[SuperSU] starbase64:
2.82 works fine
[SuperSU] dtriguero:
Flashed fine and all seems to be working as it should on my LG G3 VS985 running RR 5.8.3 N 7.1.2
[SuperSU] martyfender:
[MENTION=6726362]vickybonick[/MENTION]:

"Apps2SD binds all folders using the mount script which runs in init context so mount namespace separation doesn't affect the binds. But for newly bound folders or folders which were not bound by the mount script mount namespace separation must be disabled otherwise System/other apps will not see the bind (only the process which binds the folders will be able to see it)."

What are your thoughts on this statement? Is there any harm for the rest of the system if mount namespace is disabled?

Thanks
[SuperSU] AlinDT:
v2.82 now working fine on LG G5 (H850) stock ROM (20D), root loss no more.
[SuperSU] Chainfire:
This statement is only partially correct. The mount script should run in the master mount namespace (regardless of init context), which can be reached in SuperSU by using 'su --mount-master' from SuperSU v1.93 onwards. This should allow it to propagate to all apps, even when mount namespace separation is enabled. As documented here: http://su.chainfire.eu/#how-mount

Harm is a big word. Mount namespace separation prevents some race conditions for root apps that modify the files in ramdisk or system, and allows them to privately mount resources. It's not an issue until it is - probably for 9 out of 10 users, you would never encounter a problem with this. But this is the case with most security features!

You will probably be fine. But it would be better if apps2sd worked even when mount namespace separation was enabled.
[SuperSU] amitroutray:
It is also working fine with my second device Nexus10.

Triggered from Nexus 10
[SuperSU] pr0xyzer:
2.82 works great on Galaxy S6 with Stock Rom!