A lot of these changes have posed new problems in TWRP development and real-time usage. When Android 10 was launched by Google in 2019, we saw some major new changes like the new System-as-Root implementations and dynamic partitioning system.
The first most notable change is that TWRP 3.5 now offers better support for devices running Android 10. Isn’t it great! Improved Android 10 Support Right after the release, a patch was submitted to TWRP Gerrit to allow the flashing of the Magisk APK file through TWRP and it was merged into the code on February 15.Īnd thanks to that, you can now flash the official Magisk APK file directly through TWRP recovery. Up until now, you’d need to download the Magisk APK and change its file extension from. Following this change, the release process now includes a single Magisk APK file which is also (magically) a flashable ZIP. With Magisk v22, developer John Wu merged the Magisk Manager companion app into core Magisk. So below, we will walk you through the major changes in TWRP 3.5 that you should know of as an average user. And a lot of these wouldn’t make sense if you’re not a developer. You’d observe that the list of changes, new features, and bug fixes is quite stretched.
Only include keymaster 2 if tree supports it.Installation cleanup – remove dupe PackageExtractFn.Add support to flash both slots when flashing an image.Add bash support – not the default shell.Add support to change directory name where TWRP stores backups.Include new magisk apk support to be installed by TWRP.Add nano support to open files from file manager.Support to start terminal from file manager directory.ParitionManager: support delayed adopted storage mount.Refresh details after system wipe and adb sideload.Wrappedkey support running only on FBE devices.
SAR: Don’t follow symbolic links for block devices.
0 kommentar(er)
