The Custom Droid

Android Tutorials, Tips and Tricks

Custom Recovery

[Download] Latest TWRP 3.5.1 Recovery w/ Ability to Flash Magisk APK, New Features and more

•Updated
4 Comments
Download Latest TWRP 3.5.0 Recovery for All Android Devices

As we enter 2021, TWRP 3.5.1 has been released officially. This latest update of the most popular custom recovery adds improved support for flashing the new Magisk APK via TWRP, new features, and more as the developers prepare for Android 11 support.

Advertisement

Through this page, you can download the latest official TWRP 3.5.1 recovery for all officially supported Android devices. Further, you can follow the provided instructions and learn how to install the latest TWRP on any Android device using fastboot or Odin. If you’ve already got TWRP installed on your device, we will also show you how to update it to version 3.5.1 easily.

For those who are new to modding, TWRP (or “Team Win Recovery Project”) is an open-source custom recovery that allows Android users to install third-party firmware like custom ROMs, kernels, or mods and root their devices. Further, it also facilitates taking full system backups, formatting/erasing device partitions, and do much more.

Advertisement

What’s new in TWRP 3.5?

Since its last major release (TWRP 3.4), a lot of new changes, improvements, and bug fixes have been merged into the latest version of TWRP.

TWRP 3.5.1 Changelog

According to the release post by lead developer bigbiff, following the complete changelog for TWRP 3.5.1.

Android 9:

  • Fixes
    • Build compilation in 7.1 tree
    • SAR: Don’t follow symbolic links for block devices
    • SAR Update script name for clarity

Android 9 and Android 10:

  • Wrappedkey support running only on FBE devices
  • TWRP App log information reduced
  • Refresh details after system wipe and adb sideload
  • Chinese translation updates
  • Support keymaster 2
  • Add tzdata to TWRP for timezones
  • ParitionManager: support delayed adopted storage mount
  • Support to start terminal from file manager directory
  • Nano support
  • Add nano support to open files from file manager
  • Include new magisk apk support to be installed by TWRP
  • Add support to change directory name where TWRP stores backups
  • Add bash support – not the default shell
  • ORS support to format data
  • Add support to flash both slots when flashing an image
  • NL translation updates
  • Cleanup
    • Installation cleanup – remove dupe PackageExtractFn
    • Remove logd-reinit service
  • Fixes
    • Restore system root context
    • Only include keymaster 2 if tree supports it
    • Strip lines containing ‘–‘ in language_helper.py
    • Unlocalized string fix

You’d observe that the list of changes, new features, and bug fixes is quite stretched. And a lot of these wouldn’t make sense if you’re not a developer. So below, we will walk you through the major changes in TWRP 3.5 that you should know of as an average user.

Ability to Flash Magisk APK

With Magisk v22, developer John Wu merged the Magisk Manager companion app into core Magisk. Following this change, the release process now includes a single Magisk APK file which is also (magically) a flashable ZIP.

Up until now, you’d need to download the Magisk APK and change its file extension from .apk to .zip in order to flash it through TWRP.

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.

And thanks to that, you can now flash the official Magisk APK file directly through TWRP recovery. Isn’t it great!

Improved Android 10 Support

The first most notable change is that TWRP 3.5 now offers better support for devices running Android 10.

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. A lot of these changes have posed new problems in TWRP development and real-time usage. The team’s lead developer dees_troy also published a post to give the users an update about TWRP and Android 10 support.

These limitations have finally been dealt with in this latest version of TWRP, all thanks to the dedication and effort of some really talented developers including CaptainThrowback, Mauronofrio, AndroiableDroid, and Noah Jacobson.

Support Branches

Official support for devices has been split into two major Android branches with this release. This change was made in light of the new changes in the AOSP Android 10 release.

TWRP for legacy devices that were released with Android 9 Pie or below will be based on the android-9.0 branch. While those released with Android 10 will be built from the new android-10.0 branch. This change is aimed more at the developers.

New Naming Scheme

Based on the above change, TWRP builds compiled from the android-9.0 branch will now be suffixed by the number “9”, like 3.5.0_9. And those built over the android-10.0 tree will be suffixed with the number “10”, like 3.5.0_10. Further, any updates made to the device will further carry a final suffix like 3.5.0_10-1, 3.5.0_10-2, and so on.

What about Android 11 Support?

This brings us down to the latest version of Android at the moment. Lead developers bigbiff and Dees_Troy are now working on bringing up support for devices launched with Android 11, starting off with the Pixel 5. If you’re into development who wants to contribute, the android-11 branch is now live on Github. You could also follow the changes in the official Gerrit instance.

Update: Within the 3.5.1 release post, the developer mentions that it is a mini-release before TWRP adds support for Android 11. So, it shouldn’t be far before you would be able to enjoy your favorite custom recovery on your device running Android 11.

Others

Apart from everything we just shared, there are few more things we want to bring to your attention.

First, TWRP 3.5 can now be used to flash OZIP firmware packages on Realme and Oppo devices. So, users wouldn’t need to go through the trouble of decrypting the OZIP and then converting it into a recovery-flashable ZIP file. This should allow users to manually upgrade their phones using TWRP itself.

Earlier, TWRP 3.3 used the persist partition on devices to store the recovery’s cache and log files. 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. We already covered a solution to fix the sensors issue. With the latest TWRP 3.5 update, this bug has finally been fixed.

Another minor yet useful feature introduced in TWRP 3.5.1 is the ability to flash supported partition image files to both “a” and “b” slots. This is extremely convenient as you wouldn’t need to go through the hassle of flashing image files to both the slots seperately.

Related Article: How to take a NANDroid backup of your phone via ADB

Download Latest TWRP 3.5.1 Recovery

Below, you will find the links to download the latest TWRP 3.5.1 recovery image for all supported Android devices, along with the Installer ZIP files for devices that support the A/B partition scheme.

There are 400+ officially supported devices from different OEMs (manufactures) including but not limited to Asus, Google, HTC, Huawei, LG, Motorola, Oppo, OnePlus, Realme, Samsung, and Xiaomi. However, the latest TWRP 3.5 builds could take some time before they are released for each and every device.

Another quick way to download the official recovery for your device is by installing the official TWRP app from the Play Store. If the app isn’t available for your device, you could download it from the official page and install the APK on your device.

Tip: The list of supported devices is quite long. To quickly find the download link for your device, press the Ctrl + F key of your keyboard and search for your device’s name, model, or codename.

Asus

Barnes & Noble

BQ

Elephone

Ergo

Essential

Fairphone

Google

HTC

Huawei

Infinix

IUNI

LeEco

Lenovo

LG

LYF

Meizu

Micromax

Motorola

Nextbit

Nokia

Nubia

Nvidia

OnePlus

Oppo

Oukitel

Razer

Realme

Samsung

Sony

UMIDIGI

Vivo

Wileyfox

Xiaomi

How to Install TWRP 3.5.1 Recovery?

Installing TWRP on your Android device is quite an easy task. But before you begin, make sure to enable OEM Unlocking and unlock your Android device’s bootloader. Without an unlocked bootloader, flashing anything to your device, including TWRP would not be possible.

Further, you will also need to install your Android OEM USB drivers and set up Android SDK platform-tools on your PC. The platform-tools include the Fastboot tool that you’ll be using to flash TWRP.

If you own a Samsung Galaxy smartphone or tablet, then you’ll need to download and use Samsung’s Odin Flash Tool instead of Fastboot.

Once you have fulfilled these requirements, the instructions in the tutorial linked below will take you through the installation process in detail.

How to Update to TWRP 3.5.1 from an Existing Version?

In case you already have a previous version of the TWRP custom recovery installed on your device, you can easily update TWRP 3.5.1 through the recovery’s interface itself. To do this:

  1. Download the latest TWRP recovery image (.img) file for your Android device and transfer it to your phone’s internal/external storage.
  2. Boot your device into TWRP recovery mode using the buttons sequence, or by issuing the “adb reboot recovery” command from your computer.
    How to Update to TWRP 3.4 from an existing version of TWRP
  3. Press “Install” in TWRP and tap the “Install Image” button at the bottom-right of the screen.
  4. Navigate to your device’s storage and select the TWRP 3.5.1 recovery image file that you transferred earlier.
  5. Choose “Install Recovery Ramdisk” when prompted to select the target partition.
  6. Finally, swipe the button on the bottom of the screen to flash the image and update TWRP to 3.5.0.

Once the file has been flashed, go to the “Reboot” menu of TWRP and press the “Recovery” button. This will reboot your Android device into the updated and latest version of TWRP recovery.

Now that you have the latest TWRP installed on your Android device, you can use it to flash custom ROMs like LineageOS or Paranoid Android. You can also install mods like ViPER4Android or root your phone by flashing the Magisk zip.

There you go! You have just downloaded the latest TWRP 3.5.1 for your Android device and learned how to install/update it. With the major limitations that came with Android 10 now been dealt with, it will be exciting to see support for Android 11 being rolled out in the future. If you have face problems installing the recovery on your device or have any other questions, let us know.

Source: twrp.me

About the Author

Founder and Editor-in-Chief

Dhananjay has more than 11 years of experience in Android software customization and development, and has spent the past 10 years writing about it. He spends most of his prime time reading, learning and writing about Android and other open-source projects. He is also a community-taught web developer. Apart from that, he loves mountain biking and playing video games on his PlayStation.

Comments 4 Comments

  1. Hello
    Is there an identical tutorial for a Oneplus 8.0 Pro device with OxygenOS 11 updated to OTA (11.0.10.10) and TWRP version 3.6.0?
    Thank you very much for the information and all your work.
    Best regards

    Reply

  2. No 3.5.0.10 for Xiaomi Mi10 and Mi10Pro yet? (UMI & CMI)
    Would you have any ETA for TWRP for those devices?
    Thanks a lot for your hard work!

    Reply

    1. Laurens, the credits go to the original TWRP team for this. I just did the bare minimum to cover the update and download links on this page.

      The Mi 10 series isn’t supported officially. You will need to opt for the unofficial build available on XDA-Developers. Make sure that you through the replies on the last few pages of that thread, it includes some important info about compatibility.

Leave a Reply

Comments are moderated, and published only if they are relevant to the topic and add value in a constructive way. If you disagree with something, please be polite and respectful. We suggest you read our comment policy before commenting.