TWRP: adb devices works in recovery but fails in sideload mode

I want to install a custom rom (LineageOS with microG) on My Asus Zenfone Max Pro M1. I followed every steps detailed in the tutorial (enable debugging, unlock bootloader, run fastboot, flash TWRP, reboot in recovery, backup then wipe the system with TWRP).

My problem is when I want to sideload the custom rom. So, adb devices works and detects my phone in recovery mode. However, as soon as I lauch the sideload mode in TWRP, adb devices is not able to detect my phone anymore and the command adb sideload xxxxxx.zip fails because it cannot see any device.

I’m running TWRP 3.2.3, my computer runs on GNU/Linux (Xubuntu 18.04), I have the latest version of the Android SDK.

It is the same question as here from 2015: Device disappears from ADB devices when entering sideload but there was no answer.

Thanks in advance

How to fix TWRP bootloop caused by an OTA update attempt on rooted phone without losing any data (including apps’)?

My wife, unfamiliar with rooting, agreed to update my rooted Moto C Plus when it requested an update. Needless to say, that didn’t turn out well. As a result, now my phone is booting only to TWRP.

I would like to get it to boot normally again with all my data intact…meaning: everything the way it was (including my Google account) prior to this problem. Is it possible? How?

Phone: Moto C Plus (xt1723) 2GB Ram 16 GB Internal memory

OS: Android 7

Flashing tool: MediaTek SP Flash tool v5.1644.00

Cannot install TWRP

So I am trying to install TWRP on my android phone. My problem is that when I try to flash the img file the download starts but it doesn’t get all the way through and just throws command failed at me. Any idea why this might happen?

By the way I do have an unlocked bootloader, I have spelled the img file name correctly and Ihave checked that the device is connected before flashing with adb devices

My phone is the Huawei Honor 8 (FRD-L09) and I am using the SDK platform tools to flash the recovery

The commands are:

adb reboot bootloader, fastboot flash recovery img file

and then it fails

Tell TWRP to decrypt for ota

Old versions of TWRP would prompt for the password to decrypt the phone prior to performing an ota, however new versions are able to apply otas without requiring decryption. This is great in practise but does mean that magisk is removed by the ota (when decrypted it would run some scripts after the ota installed, this doesn’t happen when the phone is still encrypted) Is there anyway to tell TWRP I want it to always decrypt the phone?

Edit: the feature was added in twrp 3.2.2)

Running Lineage 15.1 and magisk v18.0 on a op3t

Device boots old version after update TWRP

Out of the blue, my tablet (Samsung Galaxy Note 10.1 wifi) made a reboot and got stuck in the loading screen. So I tried to install a new ROM (sideload), but noticed that I can’t because then the installer says

installing zip file '/sideload/package.zip' error executing updater 

Then I thought, well maybe I should update TWRP to a newer version. So I did, at least, I thought I did. This is the most annoying android hell I’ve ever been in. I updated TRWP from 2.8.6 to 3.2.3, but when I reboot directly into recovery mode, which I did manually because I unchecked reboot option in Odin, I found out that the stupid Device is still loading 2.8.6. Next, I tried the same update from within TRWP itself. The flash succeeded, Reboot into recovery again and.. nope. Still 2.8.6. What the hell?

So then I tried pushing a simple test file to the filesystem /sdcard and /tmp and a custom /dl directory using adb commands. Then I reboot, aaand gone are the files. It seems my whole device is stuck in a permanent state. I can’t change anything.

I gave up now. I’m working on this hell for 3 days and there is absolutely no positive movement at all. Why does Odin say flash passed, TRWP flash succeeded and when I reboot, I still get the old crap? How can I flash my device from here on? It seems I’m stuck with it now forever. It doesn’t update.

Other things I noticed:

  • When I load into TWRP I can use ADB commands from my Win 10 PC.
  • When I load into Fastboot mode, I can not use Fastboot commands. The device is not seen when using fastboot devices command.
  • I can not see any file inside /data seems to be empty folder?
  • When reloading TWRP theme, /data/media/0.. seems to be inexistent.
  • I got the Samsung Android USB drivers installed on my windows 10 pc. Device manager shows ADB device when I boot into recovery. But no Fastboot device when I boot into fastboot.

What is going on here? How can I fix this?

Cant exit twrp (reboot system doesn’t work)

Using TWRP, I just installed new ROM (ResurrectionRemix-M-v5.7.4-20160922-libra) and OpenGApps (open_gapps-arm64-6.0-pico-20180830) on my Xiaomi Readmi 4c. Both of them were flashed successfully (or at least that’s what the twrp said :D), there was no error or anything.

Then I went to “reboot system” and it returned back to the TWRP menu. I cannot boot into the newly flashed ROM.

Please help me solve this problem.

Thanks

TWRP: Failed to mount ‘/data’

When I try to install a ROM with TWRP, I get

Could not mount /data and unable to find crypto footer. Failed to mount '/data' (Invalid argument) Unable to recreate /data/media folder. Updating partition details... Failed to mount '/data' (Invalid argument) ...done Unable to mount storage Failed to mount '/data' (Invalid argument) Full SELinux support is present Unable to mount /data/media/TWRP/.twrps 

Then when I try to “Factory Reset” under TWRP Wipe, I get

/sbin/e2fsck -fp /dev/block/sda18 process ended with ERROR: 8 Unable to repair Data. Failed to mount '/data' (Invalid argument) Error changing file systems Repairing Data using e2fsck... 

I am using a Samsung Galaxy S7.

Correct TWRP Build for Samsung J7 (SM-J727U)

I have a boot loop issue similar to this post, and would like to try to flash TWRP on to my device with Odin. The TWRP site has four variations of the J7. I’m pretty sure that based on this specs data I have an Exynos processor, which narrows it down to two TWRP options:

1. Samsung Galaxy J7 (2016 Exynos) (j7xelte) TWRP page
This one has a link to XDA that indicates it is only for various SM-J710xx models.

2. Samsung Galaxy J7 Exynos SM-J700 (j7elte) TWRP page
The changelog on that one references exynos7580 which doesn’t match the processor number specified on that specs link I found for my phone.

My current recovery screen shows:

Android Recovery samsung/j7popelteue/j7popelteue 7.0/NRD90M/J727UUEU3ARB1 

Does anyone know what the correct TWRP build would be for this model of phone?

Attempting to flash TWRP on Samsung Galaxy Tab S2 8.0 simply doesn’t work

I’m attempting to flash and boot into TWRP to install LineageOS, but try as I might the process described on the LOS website simply doesn’t work. My first step is to attempt to flash TWRP via Heimdall. I boot into Download Mode, and run the following command:

 heimdall flash --RECOVERY twrp-3.2.3-0-gts28vewifi.img --no-reboot 

It’s not really clear whether this works. Heimdall claims it was 100% successful, but a progress bar shows up with what looks like 1% remaining, that never completes. If I shut down here and attempt to reboot into recovery mode by holding Power + Volume Up + Home, the device just hangs at the splash screen that says Samsung Galaxy. I’ve tried literally dozens of different guides and nothing works.