I am trying to flash TWRP into my Samsung Galaxy A8 (2018) based on official instructions from: https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-roms-kernels-recoveries--other-development/recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201 I have followed the instructions carefully and repeated several times. I initially tried things on linux with adb and heimdall, however heimdall was failing to flash, so I returned back to the exact Windows instructions using Odin3 v3.13.1. When I try to flash twrp-3.4.0-0-jackpotlte.img.tar into my Samsung Galaxy A8 (2018) aka SM-A530F, Odin fails consistently with this log: Added!! Odin engine v(ID:3.1301).. File analysis.. Total Binary size: 35 M SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. NAND Write Start!! SingleDownload. recovery.img RQT_CLOSE !! Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1) Removed!! I believe my phone is not RMM locked because I see Developer Options in my settings. I tried the process with OEM unlocking enabled and disabled in my phone Dev Options. No success yet. I googled the issue for a few hours, however people mostly report seeing RQT_CLOSE when phone is RMM locked, which I believe is not my case. Maybe this is related to the recent Android update I installed yesterday. Phone software: Android 9 Baseband version: A530FXXUECTH1 Kernel version: - 4.4.111-19323942 - #1 Mon Aug 3 15:36:52 KST 2020 Build number: PPR1.180610.011.A530FXXUECTH2 Security patch level: August 1,2020 Security software verion: - ASKS v3.1.1 Rlease 20200120 - ADP v3.0 Releasae 20191001 - SMR Aug-2020 Release 1 What does RQT_CLOSE actually mean? Could you please help investigate?

With TWRP, on almost every operation I get > Failed to mount '/preload' (Invalid argument) My device currently can not boot, and this may have something to do with it, /preload is currently in /etc/fstab, I can see the entry here with /dev/block/mmcblk0p16 /preload ext4 rw 0 0 When I try to mount it, I get mount preload/ mount: mounting /dev/block/mmcblk0p16 on /preload failed: Invalid argument Is there anyway to fix this problem? From my recovery.log, I have /preload | /dev/block/mmcblk0p16 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Primary_Block_Device: /dev/block/mmcblk0p16 Display_Name: preload Storage_Name: preload Backup_Path: /preload Backup_Name: preload Backup_Display_Name: preload Storage_Path: /preload Current_File_System: ext4 Fstab_File_System: ext4 Backup_Method: files I'm trying to flash LineageOS, but I'm really just curious about resolving this error message.

Is there a way to decrypt the system? Poco x6 pro I installed a custom recovery, but I can't find the system files. The encryption type is fbe.

Working on Ubuntu 20.04. I want to root my device to uninstall some apps (.apk) and possibly also install Ubuntu Touch. I want to uninstall almost all Google apps because I don't have a Google account and I don't want to. Without a Google account, you cannot use most Google applications (Gmail, YouTube, Drive...). A few months ago when I bought the device, I unlocked the bootloader, but I didn't have time to root it. Now I want to root it. I followed these TWRP for Xiaomi Mi A3 instructions and cannot flash or boot the TWRP.img. 1. I downloaded: twrp-installer-3.4.0-0-laurel_sprout.zip and twrp-3.4.0-0-laurel_sprout.img renamed it to **twrp.img** and **twrp-installer.zip**. 2. I copied the files to the device in **/sdcard** ---- adb devices adb push ~/Downloads/twrp.img /sdcard adb push ~/Downloads/twrp-installer.zip /sdcard adb reboot-bootloader ---- fastboot devices ---- fastboot flashing unlock ... FAILED (remote: Device already : unlocked!) finished. total time: 0.000s ---- fastboot flashing unlock_critical ... OKAY [ 0.026s] finished. total time: 0.026s ---- fastboot flashing get_unlock_ability ... (bootloader) get_unlock_ability: 1 OKAY [ 0.000s] finished. total time: 0.000s ---- fastboot boot twrp.img downloading 'boot.img'... OKAY [ 1.174s] booting... FAILED (remote: unknown command) finished. total time: 1.175s ---- fastboot flash recovery twrp.img target reported max download size of 804261888 bytes sending 'recovery' (39892 KB)... OKAY [ 1.172s] writing 'recovery'... FAILED (remote: (recovery_a) No such partition) finished. total time: 1.174s ---- Did I do something wrong? How can I root the device? To recover the device follow this instructions: https://c.mi.com/oc/miuidownload/detail?guide=2
--EDIT-- fastboot getvar current-slot current-slot: a finished. total time: 0.002s ---- fastboot --set-active=b Setting current slot to 'b'... OKAY [ 0.039s] finished. total time: 0.039s ---- fastboot flash boot twrp.img target reported max download size of 804261888 bytes sending 'boot_b' (39892 KB)... OKAY [ 1.181s] writing 'boot_b'... OKAY [ 0.207s] finished. total time: 1.388s Press and hold **volume up button** on device and enter the command **fastboot reboot**
Back in Fastboot ---- fastboot --set-active=a Setting current slot to 'a'... OKAY [ 0.039s] finished. total time: 0.039s Press and hold **volume up button** on device and enter the command **fastboot reboot** Do not press any key boots in Android-OS

As described in [this answer by @irfan-latif](https://android.stackexchange.com/a/203913/18559) , I am trying to boot (without flashing) my Google Pixel 3a into TWRP via the following command: fastboot boot twrp-3.5.2_9-0-sargo.img This failed with the following messages:

Sending 'boot.img' (65536 KB)                      OKAY [  2.028s]
Booting                                            FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed

The only things I found on this topic are: * [A thread on Reddit](https://www.reddit.com/r/Pixel3a/comments/ga7l5h/twrp_not_booting_in_android_p/) which wasn't really solved as they moved from booting to flashing which eventually worked for them, but I'm interested in booting only at this point. * [A thread on XDA Dev](https://forum.xda-developers.com/t/attempted-to-boot-twrp-error-verifying-the-received-boot-img-invalid-parameter.4019469/) which basically ended with ["TWRP for Pixel 3/3XL on Adroid 10 does not work and will not until they release a compatible version"](https://forum.xda-developers.com/t/attempted-to-boot-twrp-error-verifying-the-received-boot-img-invalid-parameter.4019469/post-81198795) . Note also that this may not apply to me as I have Android 11 (RQ3A.210605.005 to be precise) and a newer TWRP version. * [A Github issue](https://github.com/TeamWin/android_device_google_crosshatch/issues/5) from 4 Sep 2020, closed with the message "android 11 is not supported yet." (though this is for a slightly different device). What caused the error, can it be resolved, and if so, how? ## P.S. Further details:

$ adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
$ fastboot --version
fastboot version 31.0.2-7242960

* I have unlocked the bootloader. * I also tried booting the LineageOS recovery which appears to work, but continues starting Android normally instead of TWRP:

$ fastboot -v boot lineage-18.1-20210608-recovery-sargo.img
Sending 'boot.img' (65536 KB)                      OKAY [  2.004s]
Booting                                            OKAY [  7.085s]
Finished. Total time: 9.156s

I have OnePlus 3 (A3003). I installed a custom ROM. Since then, I can't get to recovery mode. If I try booting into it, my phone gets stuck on the OnePlus logo. I tried flashing it with fastboot,

C:\...\Android\android-sdk\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 442499072 bytes
sending 'recovery' (18964 KB)...
OKAY [  0.580s]
writing 'recovery'...
OKAY [  0.144s]
finished. total time: 0.726s

And also I tried flashing it with the TWRP app, it gave me an error telling me that I have already installed it. What is the problem?

So I was going to root this (previsouly healthy) BQ A4.5. Unlocked the bootloader and flashed [TWRP from here](https://twrp.me/bq/bqaquarisa45.html) :

$ fastboot oem unlock
(bootloader) Start unlock flow

OKAY [ 32.954s]
Finished. Total time: 32.960s
$ fastboot flash recovery downloads/twrp-3.3.1-0-dendeone.img
target reported max download size of 134217728 bytes
Sending 'recovery' (11342 KB)...
OKAY [  0.378s]
Writing 'recovery'...
OKAY [  0.335s]
Finished. Total time: 0.727s
$ fastboot reboot bootloader
rebooting into bootloader
OKAY [  0.003s]
Finished. Total time: 0.058s
$ fastboot reboot
Rebooting...

Finished. Total time: 0.058s

The first reboot to bootloader didn't do anything. Now it's on a bootloop which states:

Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

Pressing _Volume Up + PowerOn_ used to work for recovery (that's how I got into fastboot mode). Now, pressing _Volume Up/Down/Up+Down + PowerOn_ doesn't do anything, fastboot stands indefinitely `, and adb always responds with error: no devices/emulators found` regardless of when it's run. If I press _Volume Up+Down_ it turns off. Plugging in USB it turns on. Nothing else seems to respond. dmesg states:

[32774.364937] usb 2-7: new high-speed USB device number 59 using xhci_hcd
[32774.514434] cdc_acm 2-7:1.0: Zero length descriptor references
[32774.514450] cdc_acm: probe of 2-7:1.0 failed with error -22
[32774.554519] cdc_acm 2-7:1.1: ttyACM0: USB ACM device
[32777.142205] usb 2-7: USB disconnect, device number 59

The disconnect happens before the bq logo appears. Trash bin time?

So, I'm making a little batch script to be able to automate the whole process of flashing new roms for my Galaxy S6. Since its screen is broke, I have to do everithing manually from the adb shell, and since i'm having so many troubles with all the roms, I decided to make a little script to make my life easier. This is what I got so far: @echo off setlocal enabledelayedexpansion REM Factory settings echo Formatting to Factory Defaults adb reboot recovery adb wait-for-usb-recovery adb shell twrp wipe cache adb shell twrp wipe dalvik adb shell twrp wipe data adb shell umount /sdcard adb shell umount /sdcard adb shell umount /data adb shell umount /data adb shell mke2fs -t ext4 /dev/block/platform/15570000.ufs/by-name/USERDATA adb shell reboot recovery adb wait-for-usb-recovery REM Rom Flashing Section set argCount=0 for %%x in (%*) do ( set /A argCount+=1 set "argVec[!argCount!]=%%~x" ) echo Wiping /system adb shell twrp wipe /system for /L %%i in (1,1,%argCount%) do ( adb wait-for-usb-recovery echo Flashing "!argVec[%%i]!" adb shell twrp sideload adb wait-for-usb-sideload adb sideload "!argVec[%%i]!" echo "!argVec[%%i]!" flashed echo. ) REM Debug enable adb wait-for-usb-recovery echo Enabling USB Debugging adb shell mount system adb shell "echo '' >> /system/system/build.prop" adb shell "echo '# Enable ADB' >> /system/system/build.prop" adb shell "echo 'persist.service.adb.enable=1' >> /system/system/build.prop" adb shell "echo 'persist.service.debuggable=1' >> /system/system/build.prop" adb shell "echo 'persist.sys.usb.config=mtp,adb' >> /system/system/build.prop" adb push C:\Users\ffpp2\.android\adbkey.pub /data/misc/adb/adb_keys REM Booting system echo Rebooting into system... adb shell reboot echo waiting for phone to boot up adb wait-for-usb-device echo Launch scrcpy "D:\Users\ffpp2\Documents\Celus\zeroflte\scrcpy-win64-v1.25\scrcpy.exe" Now, I want to be able to evaluate every adb shell ... return code, so if anything happens mid way I can stop execution and I can get to fix what didn't work. I havent been able to find anything regarding if adb shell forwards error codes back to the windows command prompt. Take a look at this: D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell mount /system mount: mounting /dev/block/sda15 on /system failed: Device or resource busy D:\Users\ffpp2\Documents\Celus\zeroflte>echo %errorlevel% 0 D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell ~ # mount /system mount: mounting /dev/block/sda15 on /system failed: Device or resource busy ~ # echo $? 255 ~ # exit D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell cat asd cat: can't open 'asd': No such file or directory D:\Users\ffpp2\Documents\Celus\zeroflte>echo %errorlevel% 0 D:\Users\ffpp2\Documents\Celus\zeroflte>adb shell ~ # cat asd cat: can't open 'asd': No such file or directory ~ # echo $? 1 ~ # As you can see, no error code was returned. And, in theory, it should be returned, since I didnt used the -x argument: Android Debug Bridge version 1.0.41 Version 34.0.0-9570255 Installed as C:\Program Files (x86)\ADB and Fastboot++\adb.exe ... shell: shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...] run remote shell command (interactive shell if no command given) -e: choose escape character, or "none"; default '~' -n: don't read from stdin -T: disable pty allocation -t: allocate a pty if on a tty (-tt: force pty allocation) -x: disable remote exit codes and stdout/stderr separation emu COMMAND run emulator console command ... Has TWRP anything to do with this?

I have Samsung Galaxy M11 (SM-M115F/DS). I want to install TWRP in it. But I can't unlock the bootloader or go to download mode. I already enabled OEM Unlock. I saw on some sites that on this device I have to press both volumes up and down to go to download mode or unlock the bootloader but actually, nothing happens. It only goes to recovery mode with power and volume up. There it has a "Reboot to Bootloader" option. When I go there, I get this When I give the options to start, I return to recovery mode.

Trying to flash boot.img but it says Size of image is larger than target device (no target size specified). How to determine boot partition size in TWRP?

I am following this guide: [\[GUIDE\] Unlock/Root/Flash for Nexus 6P][1] The bootloader is already unlocked. Now I'm trying to flash the **TWRP recovery**. (Section 2). As the device runs Android N, I first flashed the modified boot.img (like in the guide, also tried it with stock boot.img) and then I flashed the **TWRP recovery** like this: username@my_pc:~/Android/Sdk/platform-tools$ ./fastboot flash boot '/home/username/Downloads/boot.img' target reported max download size of 494927872 bytes sending 'boot' (12272 KB)... OKAY [ 0.333s] writing 'boot'... OKAY [ 0.185s] finished. total time: 0.518s username@my_pc:~/Android/Sdk/platform-tools$ ./fastboot flash recovery '/home/username/Downloads/twrp.img' target reported max download size of 494927872 bytes sending 'recovery' (16932 KB)... OKAY [ 0.453s] writing 'recovery'... OKAY [ 0.251s] finished. total time: 0.704s Then I rebooted to the **bootloader** again, and then booted to the **recovery mode**, like explained in the guide: >Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable. However, it just hangs at the TWRP splash screen: The phone still works and can successfully boot to Android N. I know the bootloader is unlocked because of the unlock symbol at boot logo, and I rooted it (same guide) on Android Marshmallow. About phone (click for larger image):

I have a Samsung Galaxy S4 Mini (GT-I9195) and successfully installed CyanogenMod 13 with the CM 13 Recovery on it. Now I am stuck with the installation of GApps by means of TWRP. I have tried to follow this tutorial to install TWRP (3.0.1 or 2.8.7): 1) App Install Method: it tells me that something went wrong and it does not boot the recovery, indeed. What seems wired to me is that when I have to choose an image it shows me the device code **serranolteusc** and **serranoveltexx** for my S4 Mini rather than **serranoltexx**, like on the website of CM 13. Is this normal? (I even tried Flashify instead of the TWRP manager, but it did not function!) 2) Since I am on Linux and have no Windows, I cannot use the Odin method. But I tried Heimdall via heimdall flash --RECOVERY twrp.img --no-reboot to no avail. 3) I tried the dd Install Method via dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery, but it still does not boot into recovery mode. Is it possible that there is an issue with the path in of=/dev/block/platform/msm_sdcc.1/by-name/recovery? Is it possible that there is no TWRP for **serranoltexx** available?

Before we start, just want to make it clear that I am aware how easy it is to brick this device, and have decided to go ahead rooting and installing a custom ROM anyway. My goal currently is to use twrp to install magisk and root the phone, but I cannot get the thing to boot into twrp. In case it matters, I'm running Miui 12.0.8.0 Global with Android 10 (4/01/21 patch) on a Global phone. My device is a 6GB/64GB variant with plenty of storage available. I've grabbed the required twrp image from the link in the XDA developers guide (https://forum.xda-developers.com/t/guide-begonia-unlock-bootloader-flash-twrp-and-root-proper.3995919/) as well as a vbmeta image for a Redmi Note 8 because I couldn't find one for the pro variant. I wouldn't expect that's an issue because they run the same OS, but because mine has a mediatek SOC I won't rule it out; if someone has the right vbmeta for me, it would be appreciated. My procedure is as follows: - Boot phone into fastboot, open minimal fastboot/adb from the guide. - Make sure twrp.img and vbmeta.img are in the fastboot directory - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - fastboot erase recovery - fastboot flash recovery twrp.img - Hold power and volume up to try to boot recovery. At this point, as long as I keep holding power+vol up the phone will make it to the "REDMI" splash screen, show me the unlocked bootloader icon, and power off. A few seconds later, it will try again to the same result. This will loop indefinitely until I stop holding volume up, at which point it happily boots into Miui; I've let it loop 5 times to be sure. If I hold just vol up (no power) once the phone turns on, like the guide says, it will pass the splash screen and simply shut off. I've tried multiple twrp and vbmeta images to the same result. The next thing to try was to boot directly to the image. I erased recovery, flashed vbmeta, and ran 'fastboot boot twrp.img." The phone hung on the fastboot screen for about 90 seconds before shutting off, and frustratingly then rebooting into *Miui* like nothing happened. If I try to boot to recovery after successfully booting Miui, it works, but I get the stock Xiaomi recovery, which will not help me root my phone. I'm running out of ideas on how to get this thing into the custom recovery. Still a little suspicious it's an AVB related issue, or some form of anti-rollback protection kicking in. Anyone here got any better ideas?

How can I extract individual files from a backup created with TWRP? I’ve come across this answer , which is about extracting an APK from the system partition. However, I want to extract files from /data, which gets split across several files in the backup.

I am trying to boot twrp.img on my LG G6 ThinQ using adb and fastboot. I reboot into fastboot mode and do:

boot ../users/******/downloads/twrp.img

and then it says

downloading 'boot.img'...
OKAY [  0.500s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.524s

My phone doesn't have root or bootloader unlocked and platform-tools is version r26 Note:

-c "lge.kcal=0|0|0|x" boot ../users/******/downloads/twrp.img

also doesn't work

I installed Lineage OS 16.0 on my Moto x4 using TWRP. I reboot and installed GApps. While installing there were no errors. But then after restart the Phone it stays in start sequence and after ca. 10 min it goes back to TWRP. When I only install Lineage OS it works fine, but without GApps. So I tried a few variations of combine these versions: TWRP: twrp-3.3.1-0-payton, twrp-3.3.0-1-payton Lineage OS: lineage-16.0-20200219-nightly-payton-signed, lineage-16.0-20200223-nightly-payton-signed GApps: open_gapps-arm64-9.0-pico-2020019, open_gapps-arm64-9.0-pico-2020028, open_gapps-arm64-9.0-pico-20191017 Can you please help me? Did someone know what I am missing or doing wrong? Edit: I found that I start in Slot A and installed Lineage there, but after reboot I am in Slot B but installing GApps works without shown error beside that main problem. When I go back to slot A and install GApps there it breaks with error code 64.

I was experimenting (more specifically, trying to flash ROMs) with my Samsung Galaxy J1 Ace (rooted). It was all going well until I tried flashing the TWRP recovery mode. I followed all the steps mentioned on various XDA forums, but a red exclamation mark appears at the top left of the screen when I try to turn it on along with the Samsung logo, and the phone just hangs. When I go to the Download mode, it shows "MDM Download Block: 0". I tried flashing, using ODIN, other versions of the TWRP for my phone model, but the same error persists. Is my phone soft-bricked? How do I fix it? I am trying to restore the original stock Samsung firmware now.

I am trying to root my Xiaomi MI A2 phone with **Android 10**. I followed the steps to install **TWRP** which was successfully done. After that, I tried installing **Magisk** to get root access. After following the installation guide and performing patching images, I am now stuck in a fastboot/TWRP loop where I can switch between fastboot and recovery using the volume up and power button only. My PC cannot detect the device in either mode, although it had no issue detecting it before. I also alternated between A and B partitions. How do I get out of this loop so I can do a fresh installation of ROM?

I recently destroyed the screen of my OnePlus One and had to send it in for repair. I used TWRP to make a Nandroid Backup before packing the device. Yesterday, I received a new device, obviously not having my apps and data. So I moved my backup onto the device, but when I try to restore it, I get errors. When restoring the data partition, it will get to 79% and then say E:extractTarFork() process ended with ERROR=255. I tried it multiple times with the same result. Unfortunately, I obviously cannot try creating a new backup. All other partitions restore without trouble. According to the log files, the file causing the issue is //data/dalvik-cache/arm/data@app@com.instabridge.android-2@base.apk@classes.dex. What can I do? I thought it might help to delete the file as the Dalvik Cache is just a cache that will be recreated, but how do I delete files or folders from a Nandroid Backup?

If we install our TWRP in ramdisk, which button combination do we need to boot again into the TWRP? In Xiaomi Poco M4 Pro 4G, there is no recovery partition, but there is a recovery software which we can access with the default button combination. I don't know in which partition the default recovery is stored.