Shared publicly  - 
SuperSU v2.01, Android L Preview

I am back from I/O, where many new people have been introduced to me, all of whom no doubt now have me on their douchebags-to-avoid-in-the-future list. I enjoyed myself either way :)

I have the worst case of jetlag I've ever suffered from (perhaps I am getting old ?) so I have not done nearly as much work as I had hoped today, and I hope what I did do doesn't break, and this post is not as incoherent as I expect it to be :)

SuperSU was updated to v2.01, and may already be rolling out to some via the Play Store. The flashable update ZIP is available from this permalink as always: . This version does not require a binary update for those running v2.00.

All *CF-Auto-Root*s have been updated as well to install this version (previously v1.94, if I'm not mistaken), so the Nexus 5 and 7 CFARs should root your L just fine.

I have only played with SuperSU on the L preview on my Nexus 7 for an hour or two, just to make sure the base functionality works. No doubt some cases will be found where it still breaks. That being said, I don't plan on spending too much time on compatibility with the L preview, as I'm sure some security related stuff will change before 'retail' release.

As it is, not all the things I have previously written or talked about have come to pass yet on the L preview (though I expect most of them to be present in the full release). Right now the two most obvious changes are:

- PIE: dynamically linked executables need to be PIE. For further information see this post:

- Restriction of the unconfined domain executing files from /data. As described in my previous post here: . See the SELinux section of my How-To SU ( ) guide for how to use SuperSU's --context parameter to work around this. If a root app is breaking for you on L, there's a fairly big chance this is the cause.

Curiously, the u:r:recovery:s0 context is present in the L preview, which (as I recall) was only added to SELinux a very short time before they killed writing to /system completely from AOSP in normally booted Android. I do expect the latter to be present in the full L release, which will then require us to patch all kernels' SELinux policies, simply disable SELinux, or require all apps to modify /system to do so via custom recoveries (yikes!)

In the L preview though, remounting /system read-write and actually writing to it (just remounting it will probably stay available) still works.

If you have issues with SuperSU itself, be sure to visit the thread on XDA:
Full firmware flashing straight from the device itself and ROOT in the process ! Never be without ROOT again ! SuperSU. The best Superuser access management available ! DSLR Controller. Control your Canon EOS DSLR from your phone ! PerfMon. The Performance Monitor that floats on top of all your ...
郑科's profile photojayachandra tallapaka's profile photoLiudas Survila's profile photohussien ali's profile photo
Your the man mate
Glad you had fun. Great things are coming for Android enthusiasts. 
As always it was a great time hanging out with you. Until next time.....
I still get "no su binary installed" :(
Android "L", I forgot to mention.
Way to upset the natural order.. Good job!!
Also, +Jim DeArras did you flash the ZIP from a custom recovery?  If so, is the recovery up to date?
installed 'l' with the adb tools and flash-all.bat.  then flashed TWRP.  Used TWRP to flash your zip.
that twrp looks a little stale. downloading
That was for Nexus 5.  I cannot locate any later Nexus 7 2013 twrp images.  :(
found it.  that was the problem, thanks!
zi can
can‘t root fqrouter2 (ROOT not working)
Thanks for your great work and for your detailed posts.
Have you come across this? Happens with SuperSU 2.0, but not always. Intially it works, then breaks at some point. Either the SELinux policy is updated dynamically at some point, or "upgraded" when you enable managed profiles and/or disk encryption. Looks like access via abstract sockets is forbidden.

I/auditd  ( 6064): type=1400 audit(0.0:87): avc:  denied  { connectto } for  comm="su" path=0065752E636861696E666972652E73757065727375 scontext=u:r:shell:s0 tcontext=u:r:untrusted_app:s0 tclass=unix_stream_socket

Haven't tried w/ 2.01 yet, because no recovery can currently handle the new disk encryption format. 
It definitely breaks after encrypting, with 2.01 as well. Also this: 

I/auditd  ( 4676): type=1400 audit(0.0:92): avc:  denied  { sys_ptrace } for  comm="daemonsu" capability=19  scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=capability
Very crude fix: add 'setenforce 0' to init.rc. (Because androidboot.selinux=permissive doesn't work anymore on production builds)
I rooted my phone and I keep losing it why, I have T-Mobile s4, running on kitkat
Scratch that, androidboot.selinux=permissive still works, abootimg was somehow messing the kernel cmdline.
AOSP to root users: "Go to L!" 😝
Je bent een baas man! Top werk! Mijn inziens ben je een van de belangrijkste mensen van de Android community!
+Nikolay Elenkov I think that audit happens regardless of encryption. Not sure what the actual problem is, but I doubt it's just that quoted audit. Abstract socket access fails in various circumstances since the recent SELinux changes, and SuperSU employs other methods of connecting to work around this when needed.
Evertime I got this su blocked and never returned (called from shell). 
Confirmed +Chainfire. You are on my douchebags-to-avoid-in-the-future list. ;) Good times man. Glad we got to party together, can't wait until we can do it again! Thanks for the chats about the future of root.
I removed +Chainfire from douchebags-to-avoid-in-the-future list to put +Derek Ross back on.

It was nice to finally meet you in person Jorrit! 
For you guys who are having intermittent/strange root problems, try asking SuperSU 2.0.1 to "forget" the app and then let it re-authenticate. For me it resolves this kind of issue!
Just an FYI, I know there are still some issues. ART and AM and some other Android internal crashes. Figure them out eventually... Or they may just be resolved in the 'retail' release of L.
jetlag secret. dont eat until the first morning at your destination. fasting in this way helps reset your body clock.
+Chainfire This update is giving me reboot after 10 seconds of every boot up on HTC Desire 816. Please fix this. After uninstalling latest version, it works fine.
Edit: Works fine after flashing through recovery
Just wanted to take the time and say,Thanks so much for the dedication and hard work. I will continue to support your work as you definitely deserve it.
HI superSU is great But i have a problem.
Everytime i start my device, Galaxy note 2 N7100 and Knox disabled, a popup show me this lines: SuperSU is stopped, then i have to update it every time to 2.01 version in order to use it. Is there a fix ?
Hello. I am facing reboot issues on HTC Desire 816 running Android 4.2.2. I didn't have any issues with any version of SuperSU below v2. Now after update to v2.01, my device constantly reboots after few seconds of loading!!
Hey Chainfire pls help me rooting the lenovo s660. Framaland does not work. I can find nothing to do it. I did the sduos earlier. Now that I changed my phone I need to Root this too.
I use Tasker and every time it askes for granting root access, it crashes and reboots. I am using v2.01 on my N7 2013 Preview L. All the other programs have no problem. 
I don't know what is happening but I my superSu pro is unresponsive now for over 3 days+ and also I can't access wifi or phone settings? ? On Su app I get a message saying that Su is not responding same with settings. ....Any ideas on what is going on? Please advise, thanks
Hi +Chainfire, not worked on Nexus 4. Every time lunch the app, it going to crash and every time restart the smartphone. it install 5 upgrade but not worked. Bye
+Chainfire, I currently have a Galaxy S 5 G900H International version. When I root with CF-AutoRoot, everything seems to work perfectly but when I run Root Checker Pro it states that it's rooted halfway.. How may I fix that? Thanks! [I'm running Android 4.4.2 and I've tried countless times to root it but failed]
+Chainfire I'm having the issue yes root xbin su fix how do I get rid of that comes up after every back up
+Chainfire, I'm trying to root a nexus 7 deb/razorg. Should I use flashed through TWRP or CF Auto Root flashed through terminal? I'm not planning on installing a new ROM.
Different guides, different methods. What exactly is the difference?
+Rholand Bucci sorry for my stupid question...after CF autoroot did u install SuperSU?when u use root checker you must give to it the root permissions so a SuperSU pop up must come out asking you "root checker request root permission" so you have to select the option to guarantee the permissions.
+Stefano Bianchi it's not a stupid question given that you have no way of knowing. The steps I take are: 1. Flash Official Stock (Paraguay) Unbranded firmware. 2. Flash CF-Auto-Root-k3g-k3gxx-smg900h.tar.md5 3. Wait for the install and auto-reboot. 4. Install SuperSU and update the binaries hitting NORMAL 5. Flash philz_touch_6.48.4-k3gxx.tar
The problem is that when I use Root Checker Pro it states that I don't REALLY have root, that the root I have is superficial.
When I go to Terminal Emulator, I get root access and when I type in "whoami" the result is "unknown UID 0". It should be "ROOT UID 0"
Supersu is root??? Buth why not permenantly:8.5

Rholand Bucci do your nave the supersu pro installed?
I wanna to understand if my supersu is updated??? I don't know why but everytime that i open supersu i have an update...the problem is that I don't know if the procedure that I done is finished successfully
thx u so much for the auto root for my tablet and smartphone. Greetz from germany
Add a comment...