When it comes to development, users usually need an unlocked bootloader and then a custom recovery to flash ROMs, kernels, root their devices, and more. In the world of custom recoveries, TWRP is one of the most popular choice as it offers unmatched functionality and is available for a wide variety of devices. Without TWRP or other custom recoveries, it is difficult to even root modern devices as Android has adopted security features such as dm-verity. As such, devices which do not have a port of TWRP are mostly out of luck when it comes to development, as one of the first hurdles cannot be cleared.
With that said, the development community has proven that it can overcome challenges. For example, the first-generation Google Pixels received official TWRP support, even though developers faced problems with the A/B partition system in Android Nougat at the beginning.
TWRP has recently been made available for more devices. An alpha port was recently made available for the Google Pixel 2 and the Pixel 2 XL. Now, the roster of supported devices of TWRP has increased, as official ports are now available for the Xiaomi Mi A1 as well as some models in the Asus ZenFone 4 series such as the ZenFone 4, the ZenFone 4 Pro, and the ZenFone 4 Selfie Pro are all now supported. All of these devices use dm-verity. This means that modifications to the stock system will prevent the ROM from booting. To prevent this from happening, users need to install a custom kernel or ROM which has dm-verity disabled.
In the case of the Mi A1, users feared that its use of the A/B partition system would hinder development for the device. Now that the device has official TWRP support, we hope that this leads to an increase in development. Development community contributions such as custom ROMs and kernels will certainly make the device more attractive for enthusiasts, and give them a long life in terms of software and security updates.
Users can download TWRP for the devices from the following pages:
Source: TWRP Via: Android Police
from xda-developers http://ift.tt/2hmZkaF
via IFTTT
Aucun commentaire:
Enregistrer un commentaire