New SuperSU and suhide Updates Bring Minor Bug Fixes

New SuperSU and suhide Updates Bring Minor Bug Fixes

While many of us were enjoying our weekend off from the stress of our daily lives, Chainfire was busy wrapping up two small bug fix updates for two of his applications. We aren’t to expect any big features or changes in these updates, but  SuperSU as well as suhide both received new updates that bring some small but important updates. These updates are both now available to the public and it brings SuperSU up to version 2.82-SR5 while suhide is now up to version 1.09.

We’ll start off with the SuperSU update that is now available as version 2.82-SR5. The first change in this update has to do with the recent change we saw with TWRP for the Google Pixel and the Pixel XL. This custom recovery was recently updated with proper support for Oreo but flashing the new TWRP image with an older version of SuperSU ended up breaking TWRP. You were able to boot TWRP and then flash SuperSU just fine, but if you wanted both on the same device then you ran into issues with the last version.


Along with that fix, this new version of SuperSU also resolves an issue dealing with Oreo and file-based encryption. If you have a device running Android 8.0 Oreo and it also used file-based encryption, then it would refuse to boot if the /data partition was unencrypted. So far, the Pixel phones are the only devices that meet this criteria, but it’s certain that this issue will pop up more and more as times goes by. So this new version of SuperSU adds a workaround for this issue.

suhide is another application from Chainfire that received an update this weekend. This new update brings it to version 1.09 and it simply hides a few more “left-overs” than it had before. This includes, but is not limited to, the changes that we just saw added to the new version of SuperSU. You can find discussions about these two updates in our SuperSU forum right here.

– suinit: Fix (flashed) TWRP 3.1.1 compatibility on Pixel (XL)
– FBE: allow FBE devices to boot unencrypted (unless KEEPFORCEENCRYPT is set)

– Remove ODM and OEM mounts
– Setpropex: set multiple properties
– Cleanup: remove /boot

Source: +Chainfire

About author

Doug Lynch
Doug Lynch

When I am passionate about something, I go all in and thrive on having my finger on the pulse of what is happening in that industry. This has transitioned over the years from PCs and video games, but for close to a decade now all of my attention has gone toward smartphones and Android.

We are reader supported. External links may earn us a commission.