Also, turn OFF KingRoot Auto Update after you are rooted and prior to running this. If you do NOT see SuperSU after the process is complete, go to the Playstore and install it and then open it. The version numbers are to be kept the same to reduce the effectiveness of people trying to upload the test releases to app stores outside of Google Play, as most non-Play stores do not accept a version number already present.It is not advisable to uninstall this after KingRoot removal, because this fights for root in case KingRoot tries to reinsert itself again after a reboot, etc. The next test release would be using the same main version number as the current stable release, meaning that v2.78 SR1 would have been called v2.79 Beta otherwise. With this update, SuperSU is moving from BETA to Service Release naming scheme. ZIP/Systemless: Give su.d 60 seconds to execute (from 4 seconds)Īpart from this, this v2.78 SR1 also brings a change to the versioning system used by SuperSU.supolicy: Fix parsing allowxperm with multiple sources/targets in a single definition.supolicy: Ensure zero-on-alloc for new rules.subinary: In systemless mode, ensure PATH contains /su/bin and /su/xbin.

subinary: Fix possible NPE in LD_PRELOAD sanitization.

subinary: Adjust Zygote PID detection to prefer 64-bit.subinary: Adjust app_process detection with manipulated mount namespaces.Hence, it is recommended to update SuperSU by flashing the SuperSU zip as the apk update would not be sufficient in this particular instance.

Nonetheless, it is a vulnerability, which is now fixed in this release. Chainfire mentions that the exact combination required for this vulnerability make the chances of its exploitation very slim.

Super sume pro xda