The Custom Droid

Android Tutorials, Tips and Tricks

Download Latest TWRP 3.4 Recovery for All Supported Android Devices & Installation Guide

TWRP 3.4 Recovery - Download & Installation Guide

TWRP 3.4.0-0 has been released officially. This latest update of the recovery adds better support for legacy devices running Android 10, System-as-Root, a new template for TWRP Installer ZIP files, allows flashing of OZIP firmware on Relme/Oppo devices, and also fixes the dreaded sensors bug caused by TWRP.


Through this page, you can download the latest official TWRP 3.4 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.

For those who are new to modding, TWRP (Short for “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.

What’s new in TWRP 3.4?

Since the release of TWRP 3.3 a year ago we have observed some of the most drastic changes in the Android ecosystem. From the new System-as-Root implementations to dynamic partitioning system in Android 10, a lot of these changes have posed new problems in TWRP development and real-time usage.

TWRP 3.4 is possibly one of the biggest updates to the custom recovery considering the large variety of changes it brings. So before you head over to download links and installation instructions, let us discuss these first.

Major Changes & Features

If you’re interested, you can find the complete changelog of this latest version on the official website. 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.

But there are a handful of major changes in TWRP 3.4 that you should know of as an average user. These are as follows.

  1. The first most noticeable change is that TWRP 3.4 now has better support for devices using the new System-as-Root (SAR) layout. This particular Android code implementation has added a series of roadblocks for both the developers and users of TWRP in the past. A very detailed and simple explanation was provided by Magisk developer John Wu.
    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.
  2. The next major change is regarding Android devices that have the A/B partition 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 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. This includes devices such as the OnePlus 7T, OnePlus 8, and others.
  3. Third, with the latest TWRP, users can now flash proprietary OZIP firmware packages on Realme and Oppo devices. This means users wouldn’t need to decrypt and convert the firmware package to a recovery-flashable ZIP anymore. This should allow users to manually upgrade their phones using TWRP itself.
  4. There are also a couple of changes in TWRP’s ‘Install’ menu which is used to flash ZIP files. The recovery now shows info about the ZIP file being installed to the inactive slot of an A/B device.
    In addition to that, the “Reboot System” button now allows users to reboot their phone into different partitions after installing a ZIP file.
  5. There’s also a particular change in this update that I would like to point out. 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.4 release, this bug has finally been fixed.

Apart from the ones mentioned above, there are several fixes and changes concerning the decryption, and much more.

What about support for devices running Android 10?

Earlier last year, the team’s lead developer dees_troy published a post to give the users an update about TWRP and Android 10 support. Some users might ask that there are several devices running Android 10 and already have a fully-working TWRP.

Well, it’s not exactly Android 10 that poses the problem, but the new changes that are introduced with it, which are applicable to devices that ship with Android 10 as their original version. This includes phones like the Pixel 3, Pixel 4, and future devices that will come with Android 10 out-of-the-box.

The most notable change, and the one that poses the biggest problem with TWRP development is the new dynamic/logical partitioning system. Android 10 devices now use a super partition, instead of dedicated partitions like system, vendor, etc. This in turns make it really hard for TWRP to mount the system partition. Which makes it extremely hard to flash ZIP files like ROMs, GApps, etc since the /system is read-only and couldn’t be mounted easily.

The developers are constantly working to find a proper solution for implementing TWRP to handle the super partition. However, the ETA is yet unknown. But what we do know for now is that TWRP 3.4 doesn’t support devices with the dynamic partitioning system, at least not yet. At the same time, it is also worth noting that other non-Pixel devices shipped with an older Android version (Android Pie, Oreo, etc) and received upgrades to Android 10 are not affected by this.

Considering the amount of dedication the developers have put into it, we are quite certain that they will surely find a way to get TWRP to support the dynamic partition system at some point in the future. It’s quite similar to the challenge the developers faced back when the A/B partition scheme was introduced with the original Google Pixel devices back in 2016.

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

Download Latest TWRP 3.4 Recovery for Supported Android Devices

Update (14 January 2021): TWRP 3.5.0 has been released with improved Android 10 support, a new naming scheme, and more.

Below, you will find the links to download the latest TWRP 3.4 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.4.0-0 builds could take some time before they are released for each and every device.

Since the list is very long, you can use Ctrl + F in your browser and search for your device name, model, or codename.


Barnes & Noble

































How to Install TWRP 3.4 Recovery?

Installing TWRP is quite an easy task. But before you begin with the instructions, it is required to enable OEM Unlocking and unlock the bootloader of your Android device. That is because without an unlocked bootloader, flashing anything to your device, including TWRP would not be possible.

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

Once you have fulfilled these requirements, you can follow the instructions in the guide linked below to install TWRP 3.4.

How to Update to TWRP 3.4 from an Existing Version of TWRP?

In case you already have a previous version of the TWRP custom recovery installed on your device, you can easily update TWRP 3.4.0-0 or above through the recovery’s interface itself.

To do this, download the latest TWRP recovery image (.img) file for your Android device and transfer it to your phone’s internal/external storage. Once transferred, boot your device into TWRP recovery mode using the buttons sequence, or by issuing the “adb reboot recovery” command from your PC.

How to Update to TWRP 3.4 from an existing version of TWRP

Now, tap on “Install” in TWRP’s main screen and press the “Install Image” button at the bottom-right of the screen. Then navigate to your device’s storage and select the TWRP 3.4 image file that you transferred earlier. As soon as you select the file, you’d be prompted to select the target partition, choose “Install Recovery Ramdisk” and swipe the button on the screen to flash the image file.

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 Dolby Atmos Port or root your phone by flashing the Magisk zip.

There you go! You have just downloaded the latest TWRP 3.4 for your Android device and learned how to install/update it. If you have any problems regarding the installation process or the custom recovery itself, then please let us know.


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 1 Comment

  1. Great information. Lucky me I recently found your blog by accident (stumbleupon). I have saved it for later!|

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.