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 to SuperSU brings SBIN mode (details below) and various fixes to Pixel support. The latter patches have been available as a test version on XDA ('PixelFix') for some time now.
Traditionally, SuperSU's systemless mode used an ext4 image (/data/su.img) that was mounted to the /su path. It was done this way to bypass some root restrictions (mostly Samsung's).
SBIN mode stores its files directly on the /data partition, and makes su available through /sbin. The forementioned root protections have now been circumvented in other ways.
For most root apps, this really shouldn't make any difference. Some very specific ones (like FlashFire) will need to be updated to cope. Apps that need access to SuperSU specific files and paths should refer to /sbin/supersu and /sbin/supersu_link, rather than finding the files on /data manually.
SBIN mode is the default mode for Android O and newer, but is supported on Nougat and Marshmallow as well. To enable it on N and M, you need to execute the following command in ADB shell before (re-)flashing the SuperSU ZIP:
Users are encouraged to try it on N and M as well as O, and report any issues they may encounter to the BETA thread on XDA. Upcoming SuperSU features will require SBIN mode.
As with all SR releases, you are supposed to update them by flashing the ZIP, not by installing the APK.
BETA discussion thread on XDA:
Pixel (XL) users, I advise to 'fastboot boot' this modded TWRP to flash the ZIP:
ZIP: Support order-swapped /etc/recovery.fstab
ZIP: Cope with /system being a symlink to /system_root/system
suinit: Fix remount /system r/w issue on Pixel(XL)+OPreview
sukernel: Fix pre-patched ramdisk detection for reduced system_root footprint
ZIP+suinit: Fix recovery going to ramdump on Pixel(XL)
Added "BIND SBIN" mode, mounts files in /sbin instead of /su, stores files directly in /data instead of su.img (new default for O+)
Systemless: all file contexts are restored at boot, see /path/to/su/mount/file_contexts
Thanks a lot for all the great work.
You are one of the android masters.
Working good here on Nexus 6P on 8 DP4.
Is it possible to flash a Samsung TV with another development.
Tizen has to be the worse possible system to put on a T.V in my opinion and is the Achilles heel of the device.
I would clearly need root access and was looking for a tutorial if anybody can direct me?
Has anyone got adb/fastboot working on Windows 10? Still unable to get adb to recognize/ see my device. It continues to say "waiting for device". How do I get adb/ fast working on Windows 10?
sounds like you don't have the drivers installed properly. the best way to have adb and fastboot installed system wide:
https://forum.xda-developers.com/showthread.php?t=2588979 Here is a system wide installer, although I have never used it with Windows 10. confirm that your device is listed in the device manager as adb and when booted into bootloader mode as fastboot. You may need to get the proper driver for your device from the manufacturer's site, also. in addition, you may need to allow for an unsigned driver to be installed.
+Cleveland Stamps do you have USB debugging turned on? I know, simple question, but worth asking. Also, what device are you using?
+Nick I forgot to mention that and the fact that you must approve the security prompt on your android device when it pops up.
+Cleveland Stamps you need to download and install adb and fastboot to pc then it will work.
+Marty Fender works great on win.10. I use it myself.
Only question I have is, is this compatible with Moto g4 play? And do I still need to flash the su fixer before it?
What about Sony devices? Can I safely update from 2.79?
Just wondering, does the old BINDSYSTEMXBIN still work with newer SU?
Benifits of sbin mode?
L.m. kkjkk k jokkk k j kl
LM kkkmp m km
LPM m k m. .m.m.pm.pmllmpmmmompmmllkkkkk
ADB shell actually means any shell. You can use the terminal in TWRP for those commands. Or just create a text file containing the string "BINDSBIN=true" (without the quotes) using any method you please. Push the file to /data/.supersu and give it permissions of root:root 644 (in actuality permissions probably don't matter because of the way it'll be accessed. Root can read anything no matter what permissions there are - that's why it's root)