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: http://download.chainfire.eu/supersu
. 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: https://plus.google.com/113517319477420052449/posts/ZtXAhw164QD
- Restriction of the unconfined domain executing files from /data. As described in my previous post here: https://plus.google.com/+Chainfire/posts/Lyhjzu1z9s1
. See the SELinux section of my How-To SU ( http://su.chainfire.eu/
) 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: http://forum.xda-developers.com/showthread.php?t=1538053