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.
This update focuses primarily on SELinux changes for Nougat:
-
SuperSU will now use it's own 'u:r:supersu:s0' context to run in, rather than reusing the 'u:r:init:s0' context. This can prevent some conflicts from occurring, but it may also cause some root apps (or complete firmwares) to suddenly stop working. Please report these in the BETA thread on XDA. In time this feature may be ported back to Marshmallow as well.
-
SuperSU no longer modifies file_contexts[.bin]. This modifications caused issues on some firmwares, though why this happens exactly has not been identified. Regardless, it has been refactored away.
On app-heavy devices SuperSU may have been slow to grant root access, especially right after boot, when the device is very busy, or when it needs to popup a confirmation dialog. This should now be much better on Nougat firmwares, where the problem was most apparent. It has also improved for older firmwares, but not as dramatically - it will take some more work to backport the full patch.
Compatibility with the latest TWRP on the PIxel has also been fixed, and various other small changes are listed in the changelogs below.
CF-Auto-Roots have been needing updates for a while now, but it will have to wait some more, as I'm trying to push a FlashFire update out first. For the devs among you, I have slightly updated the How-To SU docs.
Links
Download flashable ZIP: http://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip
SuperSU BETA thread on XDA: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
How-To SU:
Changelogs
-
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
Thank you for all your amazing work!
Thanks man appreciate all your hard work.
Spectacular work, as usual. Keep it up.
Now take the rest of the year off. :)
Samsung Galaxy S4 (Android 5.0.1): After Install (with TWRP) Boot hang on Samsung sign. Device don't boot. Same after delete Dalvik/Cache...
:(
+René Bour delete the system partition, flash Rom then root.
Thanks for the update did you take a look about the OnePlus 3 problem intalling Super SU when on F2FS?
+René Bour Marshmallow? So you're running a ROM? If you're running a ROM like CM don't use SuperSU it won't boot! LOLOLOLOLOLOLOLOL! It may work fine if you remove both SU binaries from the system.
+Linux Rox Haha… Thx, but i'm not at home until 29.12. I can't Flash everything, my wife kill me…. :(
+Düdmæng Brøssøvítçh NO is original Samsung ROM… lololol idiot…
and SuperSU runs perfect since years until original 2.79.
+René Bour I was completely unaware that even existed! I flashed CM13 on mine because I thought Samsuck dropped support for it! Jeeze. Sorry. Also, I have noticed some Stock ROMs don't like to boot fresh with SuperSU. Maybe try booting first then after setup is done try flashing? Dunno, good luck to you though. Maybe XDA can help you out?
+Düdmæng Brøssøvítçh Ok, your sorry is accepted. I test the new 2.79 SR1 on my own device (S5) and it runs perfect. Second I install it on my wife's S4 and the device hangs at boot. (BOTH original Firmware) Gives a chance to "repair" without any PC equipment? (No flashing from a PC is possible at this time, but the TRWP recovery is available.)
Problem solved...
Installed "old" 2.79 from SD-Card via TWRP and the Device (S4) boot again...
uff... I think will be alive the next days.... ?
... But this 2.79 SR1 is crap for Galaxy S4 (original ROM). ?
hi man can I ask you some help on my device. it supports otg but when I plug it the device didn't respond and I tried stick mount and doesn't worked. my device is archos 50 c neon. I wish you can help. thanks any way .....and keep going
Danke danke.....
Not work Redmi note 3 pro (MIUI8 6.12.22).
SuperSU-v2.79-201612051815.zip version works
+Chainfire .. ?? you are Awesome ?????.. keep up the great work ??
Thank you
Zygote dies with 2.79 SR1, xposed .87 installed, socket permission denial resulting in boot loop on emotion 6.0.1...posting on xda also
There is a little glitch in the su gui. When changing from log tab to settings tab and switching back to log tab, the icons for refresh and clear log are gone. The only way to get them back is restarting the app. Thank you for all the efforts you are putting in maintaining and improving this essential tool! Really appreciate it.
+Kjell O . . When in doubt , use the Play Store .. ???? I bought the paid version ..
Thanks for your hard work. Everyone loves the speed.. ?
Binary update error ... please help .... install using twrp on asus ZenFone 2 laser ze500kl ...
Tanks
2.79 SR1 not installed with twrp on CM13 on galaxy s4
+Kjell O oh now i understand
Thank you bro
+Crissy K yes it works perfectly
i want to flash it in 6.1.1 is it okay ? (s7 edge)
No use 2.79 not 2.79 SR1 ok
i have this version of supersu UPDATE-SuperSU-v2.78-20160905010000
is it ok that i flash this zip in recovery in s7 edge ?
+Crissy K welcome
+Tayeb CW maybe
I know in the beginning, this process needed to be done from Fastboot but now in the newer updates I only see the Flashable ZIP. I hadn't read anywhere the process changed but can I assume the process has changed? I just need to boot into bootloader, then recovery mode and flash this??? Thanks in advance!
thanks for the update,
Got lucky and picked up a 7.1 Pixel from VZ yesterday, new TWRP and SuperSU installed per instructions without hitch. Thanks for all the hard work, happy 2017.
Continued here: