Develop Bugs

Stuck in TWRP Recovery Mode

Tried updating to Beta 10 from Beta 9 and that was a royal screw up. Now can't get myself out of TWRP recovery mode. If I try to restore to my only Nandroid Backup it freezes at 100% and if I restart the phone it becomes stuck on the android/OP logo.
Can someone please walk me through how to revert back to any version of the OS? I downloaded both SuperSU 2.79 and I have the patched TWRP version for Beta 9.
Thanks!!!

SoCalUnique said:
Tried updating to Beta 10 from Beta 9 and that was a royal screw up. Now can't get myself out of TWRP recovery mode. If I try to restore to my only Nandroid Backup it freezes at 100% and if I restart the phone it becomes stuck on the android/OP logo.
Can someone please walk me through how to revert back to any version of the OS? I downloaded both SuperSU 2.79 and I have the patched TWRP version for Beta 9.
Thanks!!!
Click to expand...
Click to collapse
option 1
in twrp wipe everything (system cache/Delvim and system), then flash beta 10 again followed by superSU and TWRP again, then reboot to system...
option 2
if that doesn't work, you'll have to do 1 of 2 things, either convert the data partition back to EXT4 and then wipe everything and flash an MM rom, or flash the new oneplus stock recovery v2 and sideload beta 10, this must work.
if it boots twice after you try the 1st option it's normal supersu causes the double boot

theduke7 said:
option 1
in twrp wipe everything (system cache/Delvim and system), then flash beta 10 again followed by superSU and TWRP again, then reboot to system...
option 2
if that doesn't work, you'll have to do 1 of 2 things, either convert the data partition back to EXT4 and then wipe everything and flash an MM rom, or flash the new oneplus stock recovery v2 and sideload beta 10, this must work.
if it boots twice after you try the 1st option it's normal supersu causes the double boot
Click to expand...
Click to collapse
Option 1 didnt work, with option 2, I tried a tutorial where mounting was necessary, but I wasn't able to mount my system, what can I do?

SoCalUnique said:
Tried updating to Beta 10 from Beta 9 and that was a royal screw up. Now can't get myself out of TWRP recovery mode. If I try to restore to my only Nandroid Backup it freezes at 100% and if I restart the phone it becomes stuck on the android/OP logo.
Can someone please walk me through how to revert back to any version of the OS? I downloaded both SuperSU 2.79 and I have the patched TWRP version for Beta 9.
Thanks!!!
Click to expand...
Click to collapse
just flash stock recovery and sideload ob9 full zip and boot to system
then again boot to stock recovery and sideload OB10 full zip or (flash ota file from internal memory ) then boot to system after full setup
boot to bootloader and flash twrp28 using adb fastboot flash and boot to twrp recovery and flash SU2.79 and boot to system.

SoCalUnique said:
Option 1 didnt work, with option 2, I tried a tutorial where mounting was necessary, but I wasn't able to mount my system, what can I do?
Click to expand...
Click to collapse
go to one plus site
download 1- the recovery
2 download full 3.2.8 rom
now on twrp convert data to ext4 (make sure it's converted
flash stock recovery from TWERP or fastboot it...
reboot to stock recovery
press english > press install via adb >congirm it>
you'll be represented by a screen tilling you it's waiting for the adb sideload
make sure you have the correct drivers on PC
on the same folder you have the 3.2.8 rom open command prompt and enter
Code:
adb sideload <Rom Name>.zip
it will take sometime to sideload, after it's finished your device should be working fine
if you still want beta, instead on 3.2.8 sideload the beta you want.

Cannot update 3.2.8 to 4.0.1 without getting dm-verity warning

So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again

Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.

Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups

install beta 7 firmware

Don't bother! It's not worth it! It's just a stupid message!

I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.

It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .

cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.

bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip

Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks

Android 8 update with FlashFire breaks TWRP or TWRP boot-loop

Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh

I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.

Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.

Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards

I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.

Redmi Note 5 Pro Not Rooting

Hello There,
I have Redmi Note 5 Pro with unlocked bootloader. But unable to root it no matter what.
Let Me Explain The Situation.
1. After flashing TWRP, it asks for "decryption password" which is nowhere to be found on internet. But in order to decrypt it i had to format the phone. GOOD Now Storage is Detected in TWRP.
2. But if i boot phone in System and again boot it in Recovery then TWRP is replaced with Stock Recovery.
1 & 2 are in INFINITE LOOP now.
3. So OTG...... OTG is not even recognizing by TWRP, but OS is detecting it.
4. TWRP "Enable MTP" also not working.
So Let Me Know If I am Forgetting Something.
Please Help Me To Root IT.
PS : I have past experience of Rooting/ Flashing rom / Unlocking Bootloader etc.

I guess the main problem you're having is that your phone keeps replacing TWRP with the stock recovery once you boot into system. I've had same problem on different devices. To prevent this from happening you should not boot into system immediately after flashing twrp, rather you should boot directly into twrp recovery (try "fastboot boot recovery.img" command after flashing twrp - I'm assuming that your twrp img is saved as "recovery.img") and flash Magisk before booting into system. By flashing Magisk before booting into system your phone would no longer replace twrp, and then your phone would be rooted as well. At least that worked for me.

And also use orangefox rather than twrp on this phone

TWRP logo bootloop and inability to install system

Hello,
I have a strange problem with Galaxy A5 2017 after installing twrp + lineage 18.1. I will explain the problem in sub points.
1) in January on stock software I installed (according to instructions from XDA forum) root, twrp (via ODIN) and bypass with memory decryption. Then I installed Lineage 18.1, Gapps, Magisk and debloater on it to remove unnecessary apps.
2) The phone worked fine until mid-April. Some update was installed and the phone died.
3) The phone wouldn't boot up after the update and only the TWRP logo was looping (logo kept flashing).
4) the phone couldn't boot up, but after I found the only way to get the system to boot up was to enter command "adb reboot bootloader" from windows console. The system booted, but after another reboot unfortunately it was the same thing - the TWRP logo was looping.
5) I managed to upload Lineage Recovery via ODIN, but unfortunately this didn't change anything. Phone was booting to recovery only (but it was working). I tried to update via ADB Sideload from recovery - also without success. Interestingly, the only way to fix it was to fully format with the system partition from recovery and re-upload the system. This worked, and Lineage booted into the android interface, but on the next reboot I unfortunately only had the Lineage loading logo visible for 10-15 minutes - then a reboot into recovery. I had to repeat the formatting and re-upload the system.
6) Interestingly, when I used the combination - lineage recovery, full format, twrp 3.6.1 (via ODIN) - TWRP booted normally and I could install LineageOS. The system would only boot once, and after the next reboot the TWRP logo would loop again.
7) The last problem I noticed is that if I load Lineage system, gaaps package and magiska via TWRP or Lineage Recovery, the system will never boot - either it will loop the logo (if using Lineage Recovery) or the phone will not load the system, it will reset and loop the TWRP logo indefinitely (if using TWRP recovery).
Does anyone know a solution how to restore the phone? Will it still work or for example NAND memory is dead and nothing can be done? Best regards