yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] mrsim:
i am having similar issues as [MENTION=2911853]BillGoss[/MENTION] and [MENTION=6701770]uaiclout[/MENTION]

i followed all the steps to remove the dm-verity issue, (after triggering it), with your methods here in the OP worked great for 24hrs then i lost all telecom and data signals for a number of hours which obviously made me start flashing boot.img's and stock roms with TWRP and factory resetting through recovery as well now my issue is that i think that the device has become re-encrypted again after flashing these stock roms and boot.img's as it is showing 'encrypted' in settings/security and i now have the issue where booting into TWRP 3.2.1.0 or blue sparks TWRP,(which is now currently installed), i have to type in a pin to access the recovery and have issues seeing the sd card storage,so may i ask will i have to once again follow the steps to flash the dm-verity fix once again even though i do not see this message anymore when booting the device...am a little confused
[OnePlus 3T Guides, News, & Discussion] Xennet:
I didn't get your question....

From your query I understand that you have your device encrypted...

If you need a decrypted device, do follow procedure 2 in the OP...

And if you don't have DM Verity triggered now you don't have to follow the procedure to fix DM Verity again, just follow the procedure in the OP (not in post 2) so that you won't trigger it again..
[OnePlus 3T Guides, News, & Discussion] mrsim:
ok originaly my device was just stock...after deciding to root so as to use 'arise soundsystems' and perusing XDA OP3T threads i found that rooting and adding TWRP seems to trigger this 'dm-verity' thing whatever it is...so after unlocking the bootloader and flashing TWRP i also flashed superSU latest version onto my OP3T OOS 501 but forgot to reboot back into recovery first which i guess triggered this 'dm-verity' thing which as i understand superSU would have taken care of if i had remembered to reboot back into TWRP first...so that's when i followed the steps here in the OP to get rid of the 'dm-verity' thing which kept popping up whenever i rebooted the device,now correct me if i am wrong but all devices running android oreo are encrypted by default yes...?

and your fix helps unencrypt devices and remove the annoying 'dm-verity' message although what encryption has to do with 'dm-verity' i am still unsure of as i asumed that choosing to encrypt a device was a decision the user chose to do through the software, (which i have never ever done on any device ever),

yet my OP3T does show itself as encrypted in security settings

so now i am back to pure stock,unrooted and will attempt again to flash TWRP this time i will attempt to use magisk root instead of superSU as arise seems to work with it ok

the only other issue i had was that everytime i booted into eiter recovery or the bootloader i would lose my network signal....my IMEI would still show after *#06# no problem...i would then have to move my sim into the other slot, (OP3T is a dual sim device), and i would get signal in that slot but not the other slot wierd i know but this is android i suppose and sometimes different things happen to different devices even though things should all happen the same

so i come to my last question...now that i am back to stock OOS with an unlocked bootloader but no root or TWRP should i/do i still need to run any of this threads 'dm-verity' fixes or am i good to go with TWRP and magisk root and then arise...sorry for the long winded reply
[OnePlus 3T Guides, News, & Discussion] Xennet:
You can go with twrp and Magisk...
[OnePlus 3T Guides, News, & Discussion] mrsim:
thanks for your patience and help so far but i just need a little more...i am following the 2nd proceedure but my issue is after wiping the data partition my recovery reverts back to stock even after booting directly into recovery after flashing it with SDK...grumble,grumble,grumble...i have never had this much trouble with a oneplus device ever in my life and apart from the OP5 i have had them all and flashed,rooted and custom romed all of them too...this is the first time that i have ever had multiple issues with a oneplus device...it is most annoying...LOL

i will attempt again to flash TWRP and follow the 2nd proceedure but just wanted to ask...i have to re-flash the stock rom .zip before flashing the patched boot.img...would this be the full rom 1.46GB 'OnePlus3TOxygen_28_OTA_062_all_XXXXXXXXX' which i have downloaded or s there a link you could maybe update the OP with

thanks

p.s. forgot to mention the command 'fastboot wipe userdata' also wipes every file i have loaded into storage so how am i to then flash the boot patched.img file if it is now gone from storage...i mention this because as i connect my device to reloade the full stock rom for flashing before this patched file i notice that all the files i added previously the last time i tried this 2nd proceedure are now gone from storage and the only thing i did was to run that command in SDK

EDIT UPDATE: So finally got everything to run smoothly and am finally decrypted and no more 'dm-verity' issue just so the OP knows after running the command 'fastboot wipe userdata' all the files you previously added into the device are wiped also so it would be an idea to update the OP with this info and require users to do 2 things with which to continue

1) connect a device via USB OTG with the needed files on which TWRP can access

2) what i did....keep the device connected to the PC after running the command and copy'n'paste the files back into the device storage wher they can be accessed/used to carry on the proceedure

lastly THANK YOU [MENTION=7874870]Xennet[/MENTION] for this fix and for being patient and replying here in the thread all is working as it should and i will now attempt to get ARISE working as well
[OnePlus 3T Guides, News, & Discussion] elmer_fudd:
It might be a problem here with OB21. I'm decrypted and flashed OB21 + Force encryption disabler + SuperSU as always. Bootlooping.

Luckily I could restore using my backup. And I'm still decrypted.
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Yes the latest open beta seems to have issues with the noverity file. Something must have changed on their end
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
I'm assuming we'll need a new patched boot img for OOS Beta 21?

Or has anyone successfully rooted without triggering DM-verity? I don't feel like going through the hassle of reverting from DM-verity... Lazy I know.

Counting on you, [MENTION=7874870]Xennet[/MENTION] ! :fingers-crossed:
[OnePlus 3T Guides, News, & Discussion] Xennet:
Was out of station. Sorry guys...

Will get back from work and get it done...

Just wait.....
[OnePlus 3T Guides, News, & Discussion] Xennet:
[MENTION=6972080]elmer_fudd[/MENTION], [MENTION=5849248]Bundizle[/MENTION]

The fstab file in Open beta 21/30 is exactly the same as before. Downloaded the latest beta extracted and checked..There should be no problems with the disabler zip file...

Cant see why you guys are having bootloops...It can never cause a bootloop from the disabler zip end as the fstab files are exactly the same... no changes...

Is there some problems with your setup, check the md5 of the full rom zip? If you are using SuperSu, do unmount the system before flashing SuperSu. Mounting System and flashing SuperSu may cause bootloop.

Finally, check by flashing the disabler zip last after rooting just before rebooting to the system...If you are still having problems will look into it...

Since it was an emergency I worked it from my office as people were having problems...

For patched boot images wait till I get back home...
[OnePlus 3T Guides, News, & Discussion] Vuska:
yeah waiting bootimages patched.. [emoji5]

for safety.. what to backup in twrp incase of bootloop?
[OnePlus 3T Guides, News, & Discussion] BonnyBedlamBoy:
Cache
[OnePlus 3T Guides, News, & Discussion] Vuska:
You must be kidding.. thanks anyway
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Hello and many thanks. I did check the md5 like 5 times just to be sure. I even did the last step you recommended but my phone is still 5mins into the boot screen. I really dont know whats going on. My data partition is on ext4 might that be a concern? Also are you decrypted?
[OnePlus 3T Guides, News, & Discussion] Xennet:
That's weird....

If you have a backup, can you try booting with all other things exactly like before that's root and evrything without flashing disabler zip and report back...
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Will that not encrypt my phone?
[OnePlus 3T Guides, News, & Discussion] BonnyBedlamBoy:
the issue with OB21 is the same as it was with recent stable before you updated the OP with patched boot images. it's not a bootloop. it seems to boot properly but it doesn't come to an end. maybe boot image has to be patched again?
[OnePlus 3T Guides, News, & Discussion] elmer_fudd:
Yeah, maybe bootloop is not the correct word.... I't simply doesn't come to an end.
[OnePlus 3T Guides, News, & Discussion] Xennet:
That's why I asked whether you have a backup...in case it gets encrypted...

For that I will patch the boot images and upload in a few hours. Have to get home. At work...
[OnePlus 3T Guides, News, & Discussion] elmer_fudd:
Thanks, will try it in the evening here.
[OnePlus 3T Guides, News, & Discussion] Bundizle:
It booted fine without flashing dmverity file. Although it took a while to boot but also got encrypted ofcourse. Good thing I had a backup :good:
[OnePlus 3T Guides, News, & Discussion] Xennet:
Check the fstab file in system/vendor/etc and the fstab file in the disabler zip file..

Can you check the differences...

If you can ...

Which root method did you use?

Did you flash the disabler zip last and then boot and try?
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Yes there are some changes, small subtle differences in the fstab files...I use supersu sr5. No I did not flash the verity file because previously when I did that it did not boot. But yes there are differences in the files
[OnePlus 3T Guides, News, & Discussion] Xennet:
Deleted...
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Okay but first I have to format data. BRB
[OnePlus 3T Guides, News, & Discussion] Xennet:
Yes...

And flash the zip at last just before booting back to system...
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Still no luck endless boot. On the latest beta there is this wait,forceencrypt=footer,check....on the fstab file provided it reads wait,encryptable=footer,check one of the key differences. Doesnt boot @ all
[OnePlus 3T Guides, News, & Discussion] Xennet:
That's the change needed to keep the device decrypted...

I have incorporated everything in the v2 zip file....

No need to mount system...

Flash it last.....

Can you try with Magisk..
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Same story with magisk too. Damn
[OnePlus 3T Guides, News, & Discussion] Xennet:
Ok...this is really messed up...

That has to do the trick but don't know why...

One last time...

Try formatting...

Flash root...

Flash bluspark kernel and reboot...let me know the result...
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Without flashing the verity file?
[OnePlus 3T Guides, News, & Discussion] Xennet:
Yes...
[OnePlus 3T Guides, News, & Discussion] Bundizle:
I did not have to flash bluespark. I just flashed magisk and it booted okay. I also flashed supersu and also booted. So it has to be something in that noverity file
[OnePlus 3T Guides, News, & Discussion] Xennet:
No that's not it...

I wanted to see whether you stay decrypted by flashing the bluspark kernel because it too contains the same fstab file ....
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Okay reporting in a few
[OnePlus 3T Guides, News, & Discussion] elmer_fudd:
No luck, same result. SuperSU.
[OnePlus 3T Guides, News, & Discussion] Bundizle:
Well I successfully flashed bluespark and it booted. One problem though as it breaks wifi and also encrypts my device. fml
[OnePlus 3T Guides, News, & Discussion] Xennet:
Can you check the contents of the fstab file after flashing bluspark and booting and fstab in my v2 zip file...
[OnePlus 3T Guides, News, & Discussion] Bundizle:
I've gone out and I will be afk for a while. Maybe later in the day.
[OnePlus 3T Guides, News, & Discussion] Xennet:
The OP has been updated with the manually patched boot images disabled for Dm-Verity for Beta 21/30 for Oneplus 3T/3 respectively...:)

Warning:

Until I am 100% sure and post it here in this thread that the disabler file will keep your device decrypted I dont recommend you to use the disabler zip given in the OP for decryption on Beta 21/30 at present...
[OnePlus 3T Guides, News, & Discussion] akhilnarang:
From what I tested with the zip and manually editing the fstab, modifying the fstab is any way causes it to "clear " itself, i.e. it just becomes a blank file if I try to edit it, doesn't make sense, but that's probably the cause of it not booting
[OnePlus 3T Guides, News, & Discussion] Xennet:
[MENTION=5849248]Bundizle[/MENTION], [MENTION=6972080]elmer_fudd[/MENTION]

If you can try do the following steps exactly and reply back...

OP rewritten with updated method to stay decrypted...

Try and get back....
[OnePlus 3T Guides, News, & Discussion] Xennet:
That as you said doesn't make sense...

Then I think it's lost cause to get the device decrypted..

Some have reported the changes made to system being reverted if the DM Verity blob in dtb file is not patched in the boot image...

One last try will be to use the dtb patched boot image in the OP and then try flashing the patched fstab file and see...
[OnePlus 3T Guides, News, & Discussion] akhilnarang:
Yeah I'll try now with just oos+disabled verity, easier I did try with and without magisk(it disabled Verity too), will still try, I wanna stay decrypted :D
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
[MENTION=7874870]Xennet[/MENTION] So do you have to flash stock ROM after flashing TWRP before flashing patched boot, or can you manage without? I'm just going for no-verity.

No hassle really, but I though I'd ask... Cheers!
[OnePlus 3T Guides, News, & Discussion] Xennet:
That procedure was given above only for testing decryption...

For just disabling DM Verity flashing patched boot image after flashing twrp is only needed...if your flashing twrp for the first time...if you are upgrading OOS follow steps in the OP that is flash patched boot image immediately after flashing full ROM OOS zip and then only do anything.
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
Oh really?

The instructions in first post states to flash TWRP > stock ROM > patched boot.img > root
[OnePlus 3T Guides, News, & Discussion] Xennet:
That's for upgrading OOS...Like while you move on from one OOS version to another...

If your are rooting for the first time...after unlocking the boot loader, flash twrp, swipe to allow system modifications and immediately flash patched boot image to stop triggering DM Verity.
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
Oh, my bad then.. :silly:

Just FYI it doesn't technically say that in OP, so if you're a noob like me and is already on target OS, you might misinterpret it. :p Not that it really matters though...

Thanks for everything!
[OnePlus 3T Guides, News, & Discussion] Vuska:
so with OOS beta 21 from OOS 5.0.1 stable.. i just flash Rom 21 then patch boot image beta20 only right?

for now dont flash verity. zip right?

sorry, still learning
[OnePlus 3T Guides, News, & Discussion] akhilnarang:
So it seems a lot of guys who flashed OB21/30 have 0bytes free on /system, that might explain this :D

Some others have like 5-6mb free, not sure how.
[OnePlus 3T Guides, News, & Discussion] Xennet:
If you are encrypted flash only the patched boot image and not the disable encryption zip file..
[OnePlus 3T Guides, News, & Discussion] Xennet:
This is getting more and more weird...

Even after a clean flash???
[OnePlus 3T Guides, News, & Discussion] Vuska:
Where to see?

right now with 5.0.1, i already done all step in page 1 and work... including Force Encryption disabler.. at post 2.

is that mean I'm encrypted?
[OnePlus 3T Guides, News, & Discussion] Xennet:
See settings, security, encryption...
[OnePlus 3T Guides, News, & Discussion] Vuska:
Ok... Encrypted...

then i just clear cache and dalvick.. and flash beta 21 then Bootimages Patches Beta 20 and Magisk.. like page 1 right.

thank you...

and offcourse still waiting for Force Encryped disable

but... i confused.... is it good to have security Encrypted or Decrypted.?

[emoji848]

or it doesn't matter?
[OnePlus 3T Guides, News, & Discussion] Xennet:
You are right.

Better is encrypted
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
A somewhat off topic question.

Anyone having issues editing or copying files in system after update to open beta 21? Using Magisk 15.

Trying to change a line in build.prop and won't let me save the file. nor will it allow me to copy an edited version into system.

Can't do it in TWRP either, copying a file returns error 1.
[OnePlus 3T Guides, News, & Discussion] akhilnarang:
Yep

So I just deleted some apps that I don't care about, like Duo, then edited fstab, and all fine, I'm on it and decrypted.
[OnePlus 3T Guides, News, & Discussion] Xennet:
The OP has been updated to accommodate the changes and rewritten steps to achieve decryption in the latest OOS Betas..

And thanks [MENTION=5854483]akhilnarang[/MENTION] for pointing out that the failure of fstab decryption process was indeed due to less of free space in the system partition...
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
Well, I seem to have found the reason. The system partition is 100% full, 0 bytes free.

That can't be very good right?
[OnePlus 3T Guides, News, & Discussion] Xennet:
Yes there is something fishy with this beta build...

To flash the disabler zip you need to free some space...

Don't know whether a partioning error or system space allocation error .... By the way what is your system partition size?
[OnePlus 3T Guides, News, & Discussion] Xennet:
This is how my system partition looks on OOS 5.0.1 Stable even after installing Magisk, Arise Magnum....

There is enough free space...

But Beta 21 messes it up...
[OnePlus 3T Guides, News, & Discussion] aktersnurra:
I can't even edit the build.prop file since theere is not enough space :silly:
[OnePlus 3T Guides, News, & Discussion] Xennet:
Think this beta has major flaw and should be given up..
[OnePlus 3T Guides, News, & Discussion] elmer_fudd:
I'm up and running OB21 now. Dirty flash. Still decrypted using the Force Encryption v2 and rooted with SuperSU.

564 MB free on system.

I had to delete some apps first to be able to boot.
[OnePlus 3T Guides, News, & Discussion] anttaz:
Everytime I perform an update I follow this method like today from OB20 to OB21 and always loose everything:

1. Format DALVIK, CACHE and then only Flash the Full Rom Oreo Beta OOS zip file in TWRP.

2. DON'T REBOOT

3. Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip.

4. DON'T REBOOT TO SYSTEM

5. REBOOT TO TWRP

6. Flash "Force Encryption Disabler For OOS Oreo v2.zip" in TWRP. (No need to mount system. The v2 zip file does it automatically)

6. Reboot back to TWRP

7. Done.

8. Reboot to System.

NB: 1) Don't use any root methods....you can root later going back to TWRP after booting to system and confirming that you are decrypted....

It sticks on boot logo so I follow next step:

2)If you have bootloop go back to TWRP by keep holding the power button to power off and powering on and rebooting to TWRP via the volume buttons, mount system, go to file manager and free some space in system by deleting some unwanted apps (in system/app folder like duo, google drive, hangouts,etc. which you can later reinstall via google play as it is not mandatory for them to run as system apps) and reflash the disabler zip and reboot..It is due to low space on your system partition that fstab file flashing fails resulting in blank fstab file.

Which I can not do as unable to decrypt and all is lost so I have to clean flash???

How to update without losing everytthing?
[OnePlus 3T Guides, News, & Discussion] Xennet:
You should format SYSTEM, DALVIK AND CACHE as written in OP...

NOT JUST DALVIK AND CACHE...This beta has issues as it fills the entire space in system..As the entire space in system is used up the fstab was not replaced...

Hope you have a backup..then start afresh is the only way..

Or else...Try entering default_password as password in twrp for decryption...
[OnePlus 3T Guides, News, & Discussion] Xennet:
The OP has again been modified with rewritten steps to decrypt your device.

Steps to check your free space in system partition by using "df" command in TWRP terminal has been added so that prior to flashing the Force Encryption Disabler zip you can be sure that the fstab file will get flashed and you wont end up in a bootloop...

It was hectic Yesterday...That's it...

Thank you Guys!!!:)
[OnePlus 3T Guides, News, & Discussion] KforHorizon:
Still can't get in and I followed the exact steps you've mentioned in the OP. Thank you for your efforts though.

I'll try again though!

Update : BootLoop FTW after following the steps in the OP to the T.
[OnePlus 3T Guides, News, & Discussion] anttaz:
OB21 Clean flash following all steps in OP I get encrypted every time?
[OnePlus 3T Guides, News, & Discussion] TristanLee:
Hi. I updated to OOS beta 21 and then my phone is decrypted, now i need password to get into twrp (i tried default_password, no use), and when i boot up, the screen shows “encryption unsuccessful”. I've got very important files on my phone, please tell me if there is a way to fix it without losing my data, thank you in advance.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Did you recheck that your system partition has enough space before flashing the decryption zip???

If yes, then...

After flashing the zip file before booting to system connect the phone to the computer. Via twrp copy fstab file in system/vendor/etc folder in the phone to the root of your sdcard...Now try to copy this file to your computer.. Now check whether this fstab file is exactly the same as the one in the disabler zip file....
[OnePlus 3T Guides, News, & Discussion] anttaz:
I fixed issue by flashing Magisk before final boot to system after ten tries following OP
[OnePlus 3T Guides, News, & Discussion] KforHorizon:
Yes I rechecked if my system partition had enough space and it did have.

The fstab file was exactly the same one.

Flashing SuperSU 2.82 SR5 after flashing the decryption zip worked great! Boots right in! Update your OP I guess? :)
[OnePlus 3T Guides, News, & Discussion] Siddk007:
I having the same issue as Mr Q

DM Verity not triggered but still shows encrypted even after flashing zip. Used SuperSU 2.82 sr5 for root
[OnePlus 3T Guides, News, & Discussion] Chuck Bartowski:
Works for me :)

1) Full wipe

2) Flash ROM

3) Mount system

4) Flash SuperSu 2.82 SR5

4) Mount system again (if it is not mounted already)

5) Flash "DM-Verity and Force Encryption Disabler For OOS Oreo.zip"

6) Enjoy
[OnePlus 3T Guides, News, & Discussion] Hinoy:
Fixed... almost

Ok so basically I did a bunch of stuff and got lucky (along the lines of what you said but with 4.1.6 firmware so it was harder), my phone is back on Orea 8.0 with full stock (still unlocked bootloader) working great.

But it's encrypted

If I try to flash your dm-verity fix it stays encrypted.

If I flash your dm-verity and try to format data it fails because "data is busy" (something along those lines) and I have to factory reset because my phone lacks half of the things it needs but is still half encrypted.

It then goes back to encrypted Oreo. Any idea why ?

EDIT : Tried Chuck's way but after I full wipe when I try to flash OOS Beta 16 it fails to update system image.
[OnePlus 3T Guides, News, & Discussion] Xennet:
Finally someone..If it works for one it should work for others..

I think it's because of system mounting...flashing my zip without mounting system will not copy the fstab file...