SuperSU v2.82 Released on the Google Play Store
XDA Senior Recognized Developer Chainfire has announced that SuperSU is being updated to version 2.82. The latest app should be available on the Google Play Store already to most users, as the roll out began last week.
This comes after a few updates that caused a number of issues with some users. Chainfire and the CCMT company released a quick bug fix, but not all issues were fixed. SuperSU v2.80 caused a bootloop on some Xperia devices running the older version of Android. The version available in Play Store does not fix it. Users that still face the issue should flash the newest ZIP file available on Chainfire’s server, which we’ve linked below.
Otherwise, the new release contains a lot of bugfixes and improvements, with most changes focusing on stability for Android Nougat users. SELinux handling has been significantly reworked for Android 7.0+. The required ruleset has been reduced, and the binaries now live and execute commands in their own supersu context.
According to Chainfire, the latest version of SuperSU should work on some devices with Android O Developer Preview 2, though some devices (mainly the Google Pixel and Pixel XL) are not supported yet. Chainfire recommends waiting a little longer for version SR1 or SR2.
Boot image signing is not yet integrated but should find its place in the upcoming SR1 release. As a reminder, Google recently started requiring all boot images to be signed on the Google Pixel and Pixel XL starting with the release of the May security update. If you are planning on installing the latest SuperSU on your Pixel, you’ll have to flash the VerifiedBootSigner zip after flashing the SuperSU zip linked below but before rebooting.
Finally, the SuperSU team decided to drop the support for Android 2.1 Eclair and 2.2 Froyo. Android 2.3 Gingerbread is now the oldest supported device. Official statistics show that a small number of devices run these old versions of Android, so it makes sense for support to be dropped given how much time may be spent testing compatibility with each update.