All Common TWRP Recovery Errors and Solutions

If you are looking for solutions to common TWRP recovery errors, then you are at the right place in this post, we will help you with all common TWRP recovery errors and their solutions. Before installing TWRP recovery on your device, you need to have an unlocked bootloader. With the help of TWRP Recovery, you can install a custom ROM, root your device to try out modified applications, or install a custom OS like LineageOS, etc. Recovery like TWRP or CWM will always allow you to try most of the latest released Android OS on your phone before the official Stock ROM release.

However, you are required to have TWRP access before you can go ahead and root your smartphone. And for flashing the TWRP recovery image, you need to follow the guide properly to avoid errors. However, if you are getting errors, then, fortunately, in this post, we will give the solution to that issue. If you have a TWRP Recovery on any Android Phone, you can always try Custom ROM, Kernel, Xposed, Rooting, Mods, etc in a few simple steps. So, without any further ado, let us get straight into the article itself;

twrp featured

All Common TWRP Recovery Errors and Solutions

Before we head-on with the common problems and solution with TWRP recovery, let us know the advantages of TWRP recovery:

  • You can flash Custom ROM with TWRP Recovery
  • You can flash modding zip files to customize your phone
  • Easy to use Xposed Modules’
  • Easy to Root and Unroot using TWRP Recovery flashable zip SuperSU
  • You can always take FULL NANDROID Backup in case of any modding or flashing.
  • Easy access to restore the Nandroid Backup.
  • You can flash the image file using TWRP Recovery.
  • Can remove all bloatware using TWRP Recovery.
  • To underclock and overclock.
  • You can clean Wipe, Cache, and Data.

Fix the “Cannot Load twrp.img” Error

Installing TWRP on your device requires you to use a Fastboot command to overwrite the current recovery system. However, there will be times where the Fastboot command is unable to take up the TWRP image file or an error pops up stating that there is no such file in the directory. If you are also facing this issue then, follow the below steps to solve it:

  • Instead of typing the patch of the folder where you have downloaded the TWRP image file, simply drag and drop the twrp.img file into the command prompt.

Fix TWRP LineageOS OTA Update Modem Version Error

There will be times when you try to update the latest version of the LineageOS, the built-in updater pops up with an error that it was unable to install it. The error shows that it has an incompatible modem version or Updater Process Ended with ERROR: 7. This guide is basically for OnePlus devices. And if you are also suffering from this issue, then follow the below steps to fix it:

You need a few things before you can go ahead with the method.

Now once you are ready with the pre-requisites then, follow the below steps:

  • Download the latest version of OxygenOS for your device.
  • Extract the content in a folder on your PC.
  • Move the NON-HLOS.bin file to your ADB/Fastboot folder
  • Boot the smartphone into Fastboot mode.
  • Connect your device to the PC via a USB cable and grant USB debugging permission if prompted.
  • Open a command prompt on the same folder where you have extracted the ADB and Fastboot tools.
  • Execute the following command:
    fastboot flash modem NON-HLOS.bin
  • Hit the Enter key.
  • Wait for the Fastboot command to show Okay message
  • That’s it

Fix Error 70 While Installing Gapps

Error 70 means that there is insufficient storage space available in the system partition. This is one of the most common errors you will encounter while installing Gapps via TWRP recovery. One complicated solution for this issue is to the reformatting system partition and increase its size. However, this procedure is pretty tricky and might get your phone bricked. But there is an alternative solution that is very easy and for that follow the below guide.

  • Head to Opengapps.
  • Then you need to select the Pico Variant which includes Google Play Services and other Google apps. It is small and would be good enough to run all the Google services. Moreover, you can install other Google apps later.
  • Now select the appropriate Platform/Architecture of your system. i.e.
    – ARM: ARMv7 or armeabi.
    – ARM64: AArch64 or arm64.
    – x86: x86 or x86abi.

Fix: Unsupported Baseband Error While Flashing ROM

The flasher checks the updater-script before the installation of the baseband version and returns the error. And there is a simple fix if you wish to overcome the issue. To fix this, follow the below steps:

  • Copy the to your computer.
  • Extract the contents of the zip file.
  • Now head to META-INF\com\android and open the updater-script file using the NotePad application.
  • You need to remove the first two lines from the script and save the file.
  • Once the script has been saved compress the ROM as a ZIP and copy it back to your phone.
  • Reboot your device into TWRP recovery.
  • You need to perform quick wipe and then, flash the ROM.
  • That’s It!

Fix PIN Errors After Restoring from TWRP Android Backups

If the system that you are restoring to, requires a different PIN then the system that you are running might show some issues. And if your device is stuck with tow PINs or passwords then follow the below guide to solving it:

  • Go to Settings>>Screen Lock.
  • Tap on PIN or Password to set a new pin or password.

However, if you are not able to unlock the device at all then:

  • Boot back to the TWRP’s recovery.
  • It will ask you to enter the PIN or Password.
  • Enter the most recent working password or PIN that you remember.
  • In case you have never set a pin then type in the default password.
  • You will be taken to the home screen of TWRP Recovery.
  • Now head to Advanced > File Manager > /data/system folder.
  • Scroll down for finding two files with ‘.key‘ extension.
  • Delete all the files with word containing locksettings.
  • If you have deleted all the .key and locksettings containing files, reboot your device.
  • You will be asked to install SuperSU, if prompte then Do NOT install.
  • You will be prompted to enter a PIN or password. Enter the most recent one.
  • That’s it!

Fix TWRP “unable to mount data” Error and Internal Storage showing 0MB

  • Go to Settings > Security > Screen Lock.
  • Change screen lock method to either Pass or Pin and enter a new one.
  • Reboot your Android device to the TWRP recovery.
  • Enter the password or PIN if prompted.
  • TWRP will now decrypt device’s internal storage.
  • Reboot again into TWRP Recovery again.
  • Then head to Wipe>Advanced Wipe>Data>Repair or Change File System>Repair File System and check whether this fixes the issue.
  • If not then go to Change File System>Ext2>swipe to confirm.
  • Head back to TWRP menu>Mount menu and check now if your partitions can be mounted now.
  • Even now if the problem is not solved then you need to repair internal partitions i.e. wipe your internal storage.

Fix Magisk Install Error 1 in TWRP Recovery

When trying to flash incomplete zip file you will be treated with the Error 1 on TWRP recovery. If you are facing this issue as well then follow the below guide:

  • Put the “boot.img” file in your MicroSD card.
  • Reboot your device in Recovery mode.
  • Tap on Install.
  • Now tap on Install Image option which will be located at the bottom right corner.
  • Select the boot.img.
  • Now select the Boot Partition then swipe to confirm.
  • That’s it.

Fix Zip File is Corrupt Error in TWRP

If you are having this issue then no wiping can solve this issue.

  • You will be required to re-download the file.
  • Now check the checksum to see if anything is corrupted or not during the transfer.
  • Download the right Gapps compatible to the architecture of your mobile.
  • If every zip file is shown as corrupt then your storage is faulty.
  • Use the Repair function to solve this issue.

Fix Status Error 7 in TWRP Recovery

Error 7 arises in TWRP recovery when ROM’s updater script file does not contain the exact model of your phone or the phone model is available but the script is created for another device model. To fix this issue:

  • Firstly, copy the ROM file to your PC.
  • Extract the content of the zip file.
  • After extracting the content, you need to find META-INF folder.
  • Go the META-INF/com/google/android line.
  • In the last directory you will find two files called “update-binary” and “updater-script“. For this issue, we need the updater-script.
  • Now you need to rename “updater-script” to “updater-script.txt” and open it in any text editor.
  • Remove the line starting with “assert” to the next semi-colon.
  • You can find it in the first few lines or in the beginning of the text file.
  • Save the modified file.
  • Then rename “updater-script.txt” back to “updater-script“.
  • Update all files that you have extracted.
  • Copy the modified zip-file on your phone;
  • Reboot your Android device to recovery mode and try to update it again.
  • That’s it! Status Error 7 should be gone.

So, there you have it from my side in this post. Hope you guys liked this post and were able to overcome all the above-mentioned issue by following the steps above. Let us know in the comments below if you know the solution to any other errors in TWRP Recovery and also whether there is an issue with the above-mentioned solutions. Until the next post….Cheers!


  1. Hi,
    I use Samsung S10+ exynos
    Rooted with Magisk, TWRP recovery, Lineage 18.1
    I can’t make full ROM backup with TWRP.
    It stop about 55%…there is many “permission denied” warnings and one “can not create ‘data/media/0/TWRP’ folder (invalid argument)
    I’ve posted this question with all possible screenshots on:

    If you have solution or link to it please help.

    Thank you!

  2. I have a problem preceding this help page. Hopefully you can help. I have a Galaxy S5 900A.

    I use Odin to install TWRP and get a
    FAIL! (Auth)

    Complete(Write) operation failed.
    All threads completed. (succeed 0 / failed 1)

    I’ve tried multiple cables, 3 versions of Odin and multiple versions of TWRP (all klte date variations).

    Any suggestions?

  3. A strange problem. I flashed 18.1 and it seems to work (I can boot into a minimal system) but now I can’t get into TWRP Recovery even though I used it to flash 18.1 in the first place. The phone powers up fine but when I hold down Vol- and power, it does not boot into TWRP but boots into Lineagos. If I try ADB, then it sees the phone but it’s offline and I’ve tried all the tricks to get it back online.

    I also notice that when the android on his back is displayed, then Download Mode at the bottom is indicating Disabled.

    Any ideas, or is it completely stuffed?

  4. Hello…
    this is sure an helpful article… no doubt!
    Well, my problem’s this:
    I’m on moto g7 power, ocean. Flashed the correct recovery and its booting to it either… but its impossible to use the recovey coz its staying stack.. dead.. nothing happens. I’m lucky that I can still use the damn phone which I actually like.
    Any tips for help?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.