Official TWRP for Google Pixel and Pixel XL Updated with Android Oreo Data Decryption Support
TWRP is widely regarded as the Swiss army knife of the Android modding scene, and it’s available in a wide array of devices. The world-famous custom recovery distribution was officially released for the Google Pixel and Google Pixel XL in November 2016, shortly after its launch, however, the installation process had been kind of wonky because of the A/B partitioning scheme of the Pixel phones. This, however, has not stopped people from using custom ROMs and rooting the Pixel phones, and TWRP also receives some Pixel-specific improvements every once in a while. One of the said improvements, Android Oreo decryption support, has now made its way to Pixel builds.
One of the greatest perks of TWRP is that it can successfully decrypt data from encrypted Android devices, however, this feature was broken for the Pixels after updating to Android 8.0 Oreo. This issue, which affects all Pixel phones on Android Oreo, has been fixed on September 25th by TWRP lead developer DeesTroy. Said fix is included on the newest Google Pixel and Google Pixel XL recovery images, which can be found here and here.
Also, SuperSU and its SafetyNet-hiding companion app, suhide, have received an update specifically for the Pixel and Pixel XL as well. As announced in a Google+ post, v2.82 SR5 version of SuperSU can be properly flashed again on Android Oreo devices with TWRP 3.1.1 flashed. This SuperSU update also allow devices with file-based encryption to properly boot up with an unencrypted data partition. The suhide companion has been properly updated as well with minor fixes as well. You can download the latest SuperSU here, and the latest suhide here.
These updates should fix most issues Pixel users with Android Oreo were having while dealing with encryption. If you’d like to read more about said updates, you can have a scoop at both Google+ announcements here and here. As always, we are looking forward to more updates coming soon.
Source: Google+
0 comments:
Post a Comment