Google released Android O Developer Preview 3 on Thursday. Now there’s word that one of the most popular third-party superuser management tools, SuperSU, has released a new version that will work with at least some of the devices that officially support Android O.
Chainfire, the developer behind SuperSU, announced his plans to support Android O in a Twitter post Thursday. He stated he had SuperSU working with the Nexus 5X, the Nexus 6P and the Pixel XL phones from Google.
A few hours later, Chainfire posted on his Google+ account that the beta version of SuperSU v2.82 SR1 has now been released. The lengthy post goes over, in highly technical detail, all of the changes and fixes that are included in this new version. It makes for good reading if you understand the finer points, but here is the summary change log for the new release:
- ZIP: Detect AVB signature on input boot image, and sign output image accordingly (force with SIGNBOOTIMAGE, custom keys in /tmp/avb)
- ZIP: Samsung/7.0+: if /data is not currently encrypted, disable encryption (unless KEEPFORCEENCRYPT or REMOVEENCRYPTABLE are set)
- ZIP: Detect TWRP UI slot switch (Pixel/XL: 3.1.0-RC2+)
- ZIP: Further improve /system device detection
- ZIP: Support compiling sepolicy from split CILs
- ZIP: Kernel patch: support LZ4 compressed kernels (new format only)
- ZIP: Mount /vendor
- ZIP: Add /vendor/lib to LD_LIBRARY_PATH
- ZIP: Initial Pixel+ODP2 support
- ZIP+APK: Fixes in boot partition detection
- sukernel: Allow cpio-add of 0-byte files
- sukernel: Add dtb (in-kernel only) related features
- suinit: Improve logging
- suinit: Support pre-mounting /system and /system_root (ODP2+)
- sukernel+suinit+ZIP: Reduce system_root footprint by dynamically importing entries at boot
- supolicy: Adjustments for ODP3
You can go ahead and download the beta of SuperSU v2.82-SR1 at the button below. If you need some help flashing the tool on your phone, you can head over to Chainfire’s site to get the full instructions. Do note that Chainfire noted some problems flashing SuperSU through TWRP, later sharing fastboot boot-to-root images on XDA Developers to sidestep the problem.