Please see the thread linked below for further details.Īs with all SR releases, you are supposed to update them by flashing the ZIP, not by installing the APK. Please see the thread linked below for further details. This can be tricky and cumbersome to do, so I've created an AROMA package to make this easier. Most users never need to change any of SuperSU's advanced flashing options, which is normally done by setting variables in /data/.supersu. These boot images will fail to boot when patched. Some boot images out there are using older variants and may not support decompressing the newer variant. It should be noted that lz4 uses the v1.5.0 format when recompressing. The following compression formats should now be supported for kernel binaries and ramdisks: This will require FlashFire v0.58 (to be released shortly) to work properly. Some changes have been made to improve FlashFire compatibility in SBIN mode. This issue has finally been found and fixed in this update. Some Samsung users (running primarily CyanogenMod/LineageOS-based ROMs) have been reporting loss of (external) sdcard access since v2.80. The advised busybox installation path is /sbin/supersu/xbin. In non-root shells, binaries stored there will not be available (without referencing the full path). From SR3 onwards, /sbin/supersu/bin and /sbin/supersu/xbin will be on the PATH again, but only inside root shells. Some users complained that the XBIN folder they used in the past to store busybox (among other things) had disappeared from the PATH. Among other weirdness, for some users that meant the SIM was not detected on SR2, which is of course fixed now. Some formatting may be lost, links may be dead, and images may be missing.Ī number of issues with SBIN mode have been fixed that prevented proper operation on some devices. NOTICE: This content was originally posted to Google+, then imported here.

Super sume pro xda