NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.
Roll-out started on the new Play release last week, and by now it should be distributed to most users on Play.
This release contains a lot of bug fixes and improvements, as well as increased compatibility with many recent devices and Android versions. Most changes focus on Nougat, though there are numerous O-Preview related fixes as well.
Support for Android 2.1 Eclair and 2.2 Froyo has officially been dropped - Android 2.3 Gingerbread is now the oldest supported Android version.
SELinux handling has been significantly reworked for Nougat and up: the required ruleset has been reduced, and the binaries now live and execute commands in their own supersu context.
More O fixes are coming; though SuperSU works with ODP2 on some devices already, you'll have to wait for SR1 (maybe SR2) for ODP2 support on all of them (especially the Pixel, which is being characteristically difficult to work with). More on that in a different post.
There was some trouble with the roll-out initially, and again we apologize for the inconvenience caused to the affected users. I will go into more (technical) detail about what exactly happened in the forums.
For the moment all I would like to point out is that the Play release still has an issue with many Xperia devices running older Android versions, as well as some other devices if SuperSU is running in system mode. These are already fixed in the linked ZIP.
Boot image signing is not yet integrated (coming in SR1), though the Pixel and Pixel XL require it from the May update onwards. Until integration is completely, you need to flash the VerifiedBootSigner ZIP after flashing the SuperSU ZIP, and before rebooting - https://forum.xda-developers.com/android/software-hacking/signing-boot-images-android-verified-t3600606
(advised source for update)
Discussion thread on XDA:
And for BETA releases:
Changelog (since v2.79's Play release)
(zip linked above only)
supolicy: Newer libsupol version used
su: Fix sdk parameter not always being passed to supolicy in system mode
(zip and Play)
su: Fix su.d scripts running in the wrong mount context (introduced by ODP sdcardfs fix)
CCMT: Update language files
CCMT: Update guide screen
CCMT: Updater: remove 4.3 and 5.0 specific upgrade messages, replace with generic; and detect if root must be manually updated
CCMT: Drop support for Android 2.1 and 2.2. Minimum is now 2.3 (SDK 9, up from 7)
su: Update mount namespace separation code to improve sdcardfs compatibility
su: Fix kernel panic on ODP1/2 on 5X/6P
su: Fix ODP1 compatibility on Pixel (XL)
launch_daemonsu: Revert previous ODP1 work-around
sukernel: Add option to patch out optional /data encryption (encryptable)
suinit: cleanup /boot
ZIP: Get boot image from fstab last-effort
ZIP: Add REMOVEENCRYPTABLE flag to force disable encryption on newer Samsung firmwares
ZIP: Fix slow /dev/random on some devices, apparently freezing install at "Creating image"
ZIP: Fix LD_LIBRARY_PATH for hex-patch execution
supolicy: Fix applying deferred allow rules
supolicy: Fix setting impossible XPERM causing policy corruption
supolicy: Add policies for ODP1
launch_daemonsu: Work-around kernel panic on ODP1 on 5X/6P. Forces service mode for ODP1 on all devices.
Fix erroneously deleting SuperSU's copy of app_process on 6.0 since 2.79-SR1
GUI: Fix app_process requirement detection when supersu context used
Fully eliminate sugote binary, no longer needed due to SELinux handling improvements in earlier versions
Support /system/xbin/sush as default shell
Adjust LD_PRELOAD filtering to exclude suhide's libraries
ZIP: Motorola: default to systemless mode
supolicy: fix some segfaults(NPEs) in pre-7.0 sepolicy handling
ZIP: write boot block device once instead of twice (@_alexndr)
(c) 2017 + CCMT
Expand Samsung detection
GUI: reworked portions to work with 'supersu' context on 7.0+
GUI: fix binary update notice when superuser disabled by user in some cases
su: reworked portions to work with 'supersu' context on 7.0+
su/GUI: improve responsiveness when device busy on 7.0+
sukernel: fix cpio restore failure with very short filenames
sukernel: no longer patches file_contexts(.bin)
sukernel: revert force seclabel (no longer needed with 'supersu' context)
supolicy: add "create", "auditallow", "auditdeny" policy commands
supolicy: support "*" for permission/range parameter of "allow", "deny", "auditallow", "auditdeny", "allowxperm" policy commands
supolicy: ~~-live/--file no longer apply default patches if custom patches are supplied~~
supolicy: ~~-sdk=X option added (required for 7.0+)~~
supolicy: reworked all SELinux rules for 7.0+, run as 'supersu' context
ZIP: Separate slotselect and system_root logic
ZIP: Adjust system/system_root device and mount-point detection
ZIP: Fix minor errors in documentation
ZIP/frp: Explicitly label /su
Freaking Awesome ????????. Keep up the great work ??? Nexus 6P still working .. yes ??
Super wszystko działa 2.82
Na Go CLEVER Insygnia 550i
Many thanks for all your work. You are the base for everyone, also for others root tools. Without your studies the Android world would be worst that the IOS world. Considering all the last restrictions and the power abuses of this shit companies. Thanks.
It seems not to be working for me . Tried installing from the play store and tried flashing. SU binary needs to be updated but unsuccessful when I try . Help guys ?
I'm guessing this is CodingCode using Chainfires G+ account? Am I right?
Really started off on the wrong foot guys. I'm honestly not sure how much I can trust you. Dodgy updates and introduction of some (a lot) new permissions that you say are for feedback, but still seems really suspect. I hope you're not selling information or worse.
Good points +Madaliso Kaunda. I'm skeptical as well.
ممكن روت هواوي جي 7 للمارشملو L11 وشكراً
+Steve Sheppard Your assumption is totally wrong!
You may want to read this:
My Sony Xperia T2U it was sucessful install supersu V.2.82, but after reboot my phone it was reboot again and again. it failed to my phone this new supersu V.2.82, Hope by will fix this.
+Chris Alcoseba which version did you use? Read the post to find the correct one
+Eddy Witkamp My stable supersu is V.2.81. I have twrp recovery. So My phone back to normal.
I don't get root access with Nova Launcher for Screen off. S8 + Stock Nougat 7, S7 Edge Stock Nougat 7
Better paranoid as an iPhone
+Michael Gonzalez it does work when you sideload it, it's just not visible in the Play Store.
And yes, this trend will continue as Google provides developers the tools to block users when they are not compliant.
For some reason busybox pro is not recognizing root permission and is unable to install... please can someone help with this?
I remain skeptical about updating also because of these coding code people, but if +Chainfire talks then I listen.
it creates a bootloop with optimize app from ..... on android 5.1 helio x10. this is a major BUG!
+Eddy Witkamp Yeah, works when you sideload it... for now.
Can Google play service remove to system of Android. Coz sometimes I'm playing Online games. And keeps me remaid that Google play service not corresponding.
Whats this for? I see it in my device, just sitting there. sometimes it opens the door to some applications. thats about it.
+mito . . . I mean this app supersu? Sorry I'm quite dumb when it comes to smart phones ?
+Rupinder Sra oh yes.... in a nutshell, SU is an interface that allows full and unrestricted access to the resources of the host deviçe.
+Cory Not paranoid about security. I am just concerned about the new company that now owns SuperSu. That is all. The moment they officially took over and Chainfires ceased collaborating/working with them, it all went tits up. A programme that applies root, losing root is pretty much the complete opposite of what you want don't you think? Also, the sudden addition of pretty much every permission is enough to raise an eyebrow. I understand that allowing root access is less secure, but if the app allowing the root access (the gate keeper so to speak) is compromised, well it couldn't be much worse, could it??
So yeah, I was concerned. Chainfire built a good reputation. Codingcode does not benefit from his hardwork and actually tainted it a little when he fully let go of the reigns. They need to now prove that they can be trusted, especially considering I and others are paying customers.
I want the Chainfire version of SuperSU instead of CCMT
+Cory Errr. Yes they do (owe those who paid). I don't know about how consumer laws work in your country but if you purchase something in mine (specifically a licence to use software in this case) then it should work as intended and advertised. If not, then you are entitled to a full refund and/or compensation.
Also I realise that an app like this could do all sorts without permission, but that would mean it was malware/spyware (malicious software) and would be an illegal app. If it asks for permissions and you grant them, then you are granting them permission to do what they want. There is a big difference. One would be completely illegal (according to Google Plays terms and conditions) and the other isn't.
I'm waiting this one out until I can ascertain how trustworthy the new Dev company is. I have heard rumours that they are a Chinese based firm, which incase you didn't know aren't the best software companies to share info with. They still have their business address set to America, but that could be a satellite or a complete untruth. Who knows?
+Cory Possibly and my tin foil hat is fully glued on?. I'm just sticking with a previous release. I trusted chainfire (for many years) and I am yet to give the new company any level of trust. If I find out they are a Chinese company it is unlikely I will stick with SuperSU. Just my opinion.
+Steve Sheppard What I do not understand is: CCMT has been working with Chain Fire and SUpersu for 2 years now.
Yes maybe now it is more forefront and public, and yes maybe now there is a clear interface as to who is at the helm of the (play store) app, but finding out 2 years after the fact that you have been happily using something that you thought was different does not all of the sudden make it a bad thing.
If it was bad before, then yes it is bad now... but if it was fine before, what changed?
Anyways, as Chainfire says you have options. I am not going to collect my (presumably Canadian company) Tim Horton's receipts and ask for a refund because I find out after the fact that the company is now American. You got what you asked for regardless of the transparency (or lack of) of the company driving the app in the background, or the permissions it requires.
(but playing devil's advocate, I also do a double take before dealing with Chinese companies. Some are quite trustworthy and ethical; many are not - looking at you BLU, for example. And this goes well beyond phones and software. Many buildings in my area had to be swept for bugs because Chinese competitors installed cameras were found during government office retrofitting. This does not mean that just because a company is Chinese in origin does not make them bad - that is very stereotypical, and painting everyone with the same brush)
+Ross L.B. Laugher I did know that chainfire sold the company 2 years ago. I read an article in 2015 (i think it was on xda). He was going to continue working with them as a Dev until he thought it time to leave. What I don't understand is that the moment he leaves, they break the app and apply loads of permissions. That to me just doesn't sit right.
Chinese company's have a bad rep, but they have that "bad" rep for a reason. Especially when it comes to root applications.
+Steve Sheppard The permissions thing: yeah...
Broke as soon as he left? That didn't happen. And he is still involved
+Ross L.B. Laugher It lost root for a lot of users, including me. If a piece of software is designed to give you root and instead doesn't, that to me is broken.
What source do you have that he is still involved? I'm sure I read that he has now left.
+Steve Sheppard posted yesterday (implies he is involved):
And this is not the 1st SU "headed" by CCMT (in fact the one I use on my N6 is post CCMT takeover - which is what I meant by it did not brake as soon as he left, because he "left" awhile ago). Anyways... you have choices, the world does not bend for you or I just because we want it to.
Just Loving It
As far as I'm concerned as long as chainfire's been the maintainer of Super SU, it just gets better, keep up the good work awesome work Chainfire, don't ever stop, super SU is running smooth like bacon on my OnePlus One, awesome job once more.
I have observed that a folder named "supersu" always gets recreated after each boot, even if I delete its contents or its folder. I checked this using Aroma File Manager (Philz Touch CWM). The following files keep on generating: 1. 99SuperSUDaemon 2. [install-recovery.sh](http://install-recovery.sh) 3.Superuser.apk [4.Su](http://4.Su) Note - Officially, my root status is negative. Rootchecker says root isn't properly installed or Working.