With the latest TWRP 3.4 release, this bug has finally been fixed.Īpart from the ones mentioned above, there are several fixes and changes concerning the decryption, and much more. We already covered a solution to fix the sensors issue. This caused the corruption of the phone’s calibration data stored in the said partition, ultimately leading to non-working sensors like proximity, gyro, etc. Earlier, TWRP 3.3 used the ‘persist’ partition on devices to store the recovery’s cache and log files.
IFLASH DEVICE HD AUTHENTICATION FAILED UPDATE
There’s also a particular change in this update that I would like to point out.In addition to that, the “Reboot System” button now allows users to reboot their phone into different partitions after installing a ZIP file.
IFLASH DEVICE HD AUTHENTICATION FAILED ZIP FILE
The recovery now shows info about the ZIP file being installed to the inactive slot of an A/B device. There are also a couple of changes in TWRP’s ‘Install’ menu which is used to flash ZIP files.This should allow users to manually upgrade their phones using TWRP itself. This means users wouldn’t need to decrypt and convert the firmware package to a recovery-flashable ZIP anymore. Third, with the latest TWRP, users can now flash proprietary OZIP firmware packages on Realme and Oppo devices.
This includes devices such as the OnePlus 7T, OnePlus 8, and others. The new TWRP 3.4 Installer ZIPs also support recovery_a and recovery_b partitions on A/B devices that follow the 2-Stage-Init (2SI) System-as-Root layout. The installer ZIP file used to permanently flash TWRP on such devices has been rewritten using a more generic template and magiskboot, courtesy of developers arter97 and John Wu. The next major change is regarding Android devices that have the A/B partition layout.
With this latest update, TWRP supports automatic detecting of SAR, allowing the recovery to properly mount the /system partition for flashing ZIP files, backing up and restoring NANDroid backups, and more. A very detailed and simple explanation was provided by Magisk developer John Wu. This particular Android code implementation has added a series of roadblocks for both the developers and users of TWRP in the past.