Develop Bugs

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

root problem after update to beta 19

hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?

You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process

what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery

Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.

I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files

Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve

I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help

Which version of TWRP do you have? Try eng.stk's latest version.

I tryied 3.1.1-2
The eng.stk is not available anymore

Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .

how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back

Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228

Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.

I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help

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

Albus failed rooting, need help - SOLVED

Solved. Just install as described in https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
(before that I restored recovery, sys and boot from backup)
Still TWRP doesn't work... but who cares
Hi,
I tried to root my Moto Z2 Play but I somehow failed.
I can still boot into fastboot and boot twrp from there. but that's all that works.
I tried booting into recovery from twrp which was booted via
Code:
fastboot boot twrp.img
but this results in "no command".
Everything else just shows "your device has been unlocked and can't been trusted". Cannot turn off phone.
I followed this guide
https://devsjournal.com/how-to-root-moto-z2-play.html
but the downloads linked were down, so I tried to replace with more official looking downloads (see below)
I did these steps:
- unlock bootloader - I think this succeeded
- temporary boot twrp from fastboot
- wipe dalvik, data and cache
- backup everything except what I wiped
- other than the guide said, I did not install anything as I didn't have the files on the SD card
- I accidentally rebooted and the device started encrypting again
- I booted fastboot and flashed twrp-3.2.3-0-albus.img (by Junior Passos) into recovery
- I tried around with booting and finally was in TWRP again
- wiped again because of encryption (twrp said is was able to decrypt with standard password?)
- installed universal-dm-verity-forceencrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- installed Magisk 20.4 from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- after that booting did not work any more
- installed https://www.themefoxx.com/dm-verity-forced-encryption-disabler/ version 6.0 (guide mentioned version 5.1 from a different download) in the hopes this would solve the problem, but no.
Any idea how to recover? how to successfully root and TWRP?
Which partitions did the install-zips modify, so which backups should I restore?
thanks