TWRP 3.2.0 Released with Better Support for Installing Android 8.0 Oreo Zips and More
TWRP is the most popular custom recovery on Android, and its popularity continues to grow as devices need to have TWRP support if users want to flash custom ROMs, kernels, mods, etc. Recently, we have seen TWRP support added to more devices including the Xiaomi Mi A1 and Asus ZenFone 4 variants. The Google Pixel 2 and the Pixel 2 XL first received an alpha release of the custom recovery, which was later upgraded to a beta.
Now, XDA Senior Recognized Developer Dees_troy has announced the release of TWRP 3.2.0 for most devices. The last version of the custom recovery—version 3.1.0—was released back in March with support for ADB backup, A/B zips, and more. Version 3.2 is still a point release, so there is no addition of any major features. However, the changes are still welcome, as they improve on user experience. The changelog states:
- Allow restoring adb backups in the TWRP GUI (bigbiff)
- Fix gzip backup error in adb backups (bigbiff)
- Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
- Better support for installing Android 8.0 based zips due to legacy props (nkk71)
- Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
- Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
- Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
- v2 fstab support (Dees_Troy)
- Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
- Various other minor bugfixes and tweaks
The most notable changes include allowing users to restore ADB backups in the TWRP GUI, as well as better support for Android 8.0 Oreo zips. The Pixel 2 gets support for decryption of synthetic passwords. (Previously, Dees_troy detailed the amount of work done on the Pixel 2 to achieve decryption). The custom recovery now has v2 fstab support, and it has been brought forward to the Android 8.0 AOSP base.
Dees_troy notes that a lot of devices failed to build TWRP 3.2.0. The build errors should be fixed in the coming weeks, and we’re sure to see more devices being given official support in the near future.
Source: Dees_troy [Google+]