yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] ngundu:
I might be sounding lame or it might be actually lame but please explain on why we are flashing back OOS 3.5.4 firmware on top of OOS 4.0? Will i still have Android N even after flashing 3.5.4 firmware? :confused::confused:
[OnePlus 3T Guides, News, & Discussion] A Sad Napkin:
Gets rid of the dm vertiy error and yes you will still be on Nougat
[OnePlus 3T Guides, News, & Discussion] Dhairya:
any help in this :)
[OnePlus 3T Guides, News, & Discussion] djr4x4:
Thank you.. flashed 3.5.4 firmware/modem and no DM verity error on boot up..
[OnePlus 3T Guides, News, & Discussion] A Sad Napkin:
you have an unlocked bootloader hence the warning

No way to get rid of it unless you relock
[OnePlus 3T Guides, News, & Discussion] Dhairya:
well didn't had any issue with op2 seems something new this thing annoys

ssly no way :crying::crying:
[OnePlus 3T Guides, News, & Discussion] :
I'm just starting to dig in the dm-verity story. Since I don't use google pay, but use my devices rooted, I can't tell if this has any side effect on google pay. What I found out, is that rhe ugly red dm-verity warning (I don't call it an error, because my system was working with it - including twrp-3.0.3-0) comes from the bootloader itself. So my equitation is quite simple: I just flashed the oxygenos-3.5.4 bootloader. And you know what: it works (meaning: the annoying message is gone).

Disclaimer for attached zip as usual: you flash on your own risk.
[OnePlus 3T Guides, News, & Discussion] VR2014:
Confirmed! Many many thanks! I could flash back the 4.0 firmware and then flash the bootloader attached, and still no DM-Verify errors!
[OnePlus 3T Guides, News, & Discussion] frank the crank:
but is dm-verity working (android pay) or does it just hide the "bootmessage"?
[OnePlus 3T Guides, News, & Discussion] :
I don't know - and hate quoting myself: "Since I don't use google pay, but use my devices rooted, I can't tell if this has any side effect on google pay."

What I can tell is that: the N bootloader is checcking for dm-verity running in enforced mode (as far as I cann see, this includes a check, if the systempartition is modified - this matches with the finding of an other user, that this mesaage occurs as soon as you allow twrp to modify your system partition). The M bootloader does not check this. If google pay needs this check passed, this will propably NOT work, because M bootloader doesn't check, so the check can't be passed....

If I understand the google documentation for chain of trust, this EXCLUDES rooting and modified (stock-)system partition... But again (I still hating quoting myself): "I'm just starting to dig in the dm-verity story."

In the end do all the methods mentioned here do the same: downgrading the bootloader. I just tried to do it minimal inversive.

BTW: does anybody know, if google pay is working on [MENTION=4800121]Sultanxda[/MENTION]'s unrooted cm13 build (with M bootloader, of course ;) )?
[OnePlus 3T Guides, News, & Discussion] rbalfury:
No negative side effect to speak of, getting great speed, zero lag and awesome battery life from nougat

Tks
[OnePlus 3T Guides, News, & Discussion] Ed St John:
Did you flash that while on OOS 4.0?
[OnePlus 3T Guides, News, & Discussion] :
Yes.

BTW: Some oservations with nandroids: if you restore a nandroid (including formware)mwith twrp (3.0.3-0), the bootloader is NOT touched. If you want to change versions in twrp (i.e. going from 4 to 3.5.4 or vice versa), you need to dirty flash the rom after restoring the nandroid, to get it bootable again. While writing I wonder if it would be sufficient to flash the appropiate bootloader...
[OnePlus 3T Guides, News, & Discussion] jemeljsh:
I can confirm that re-flash of firmware and modem of the previous rom version does remove the DM verity error :good:

Before installing Oxygen OS 4.0 Stable - Android 7.0 (Complete Rom) from twrp my phone was running rooted Oxygen OS 3.5.3, so here are the steps I took.

1. Booted phone into TWRP (3.0.3.0)

2. Advance wipe (all but internal storage and USB otg);

3. Install of Oxygen OS 4.0 Stable - Android 7.0 (Complete Rom) ;

4. Rebooted into system with DM verity error;

5. Downloaded modem and firmware matching my previous ROM (3.5.3.) from this thread -> https://xdaforums.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015

6. Booted phone into twrp;

7. Installed both modem and firmware of 3.5.3.;

8. Rebooted into system with

no

DM verity error;

9. Great success.
[OnePlus 3T Guides, News, & Discussion] kpenny:
I tried the exact same process but still have the dm-verify message.
[OnePlus 3T Guides, News, & Discussion] Zegnalabel:
Hi, if I unlock bootloader and flash TWRP but set TWRP to "read-only" and no system modification, will I still trigger dm verity? No intention to root after that.
[OnePlus 3T Guides, News, & Discussion] :
Overflashed in two ways: firmware zips contain modem, so you flashed it twice; it's absolutly sufficient to flash aboot - all other files are not neccessary to replace by the older versions. So just flashing aboot is the minimal, fastest and least invasive method.
[OnePlus 3T Guides, News, & Discussion] aaronc_98:
Why does that work and any performance downgrade in the radio and firmware?
[OnePlus 3T Guides, News, & Discussion] A Sad Napkin:
No idea haha. But it does. I didn't notice any difference lol
[OnePlus 3T Guides, News, & Discussion] chas123:
You can get the files here:

http://www.androidbrick.com/download/oneplus-3t-qualcomm-hs-usb-qdloader-9008-unbrick-fix/

also if stupid ass megaupload gives you any ****

---------- Post added at 08:15 PM ---------- Previous post was at 08:02 PM ----------

It's the boot image. That's all you need. Put the boot.img from the 3.x zip in your adb folder, boot into fast boot, then

fastboot flash boot boot.img

That should get rid of the dm-verity warning
[OnePlus 3T Guides, News, & Discussion] jemeljsh:
You're right. The suggested solution was not clear enough + i did not know that firmware contains modem. Nonetheless, its already irrelevant as I erased it all and went back to complete stock with locked bootloader ;)
[OnePlus 3T Guides, News, & Discussion] v014nd:
yup! This method work for me. Thanx!
[OnePlus 3T Guides, News, & Discussion] joakimbo:
Flashing boot image from 3.5.4 would mean you're using the kernel from marshmallow. Guess that's not ideal using an old kernel version, in regards of performance and battery..
[OnePlus 3T Guides, News, & Discussion] 23Six:
Can I just ask, why do you guys care so much to remove the dm-verity screen? I have it and Android Pay/SafetyNet works completely fine as before using Magisk Hide. There is virtually no benefit of the attempting to removing the screen as far as I'm aware because there is no drawback to it
[OnePlus 3T Guides, News, & Discussion] Xenthalon:
I'm finally on 4.0.1, SuperSU 2.79-SR2 no DM-Verity issues without flashing an older bootloader.

After going through quite the ordeal yesterday trying to upgrade to 4.0.1 I thought I'd share what I did.

In retrospect I already went wrong last week trying to upgrade from 3.5.4 rooted to 4.0.0, this triggered dm-verity and somehow also locked TWRP out. Trying to flash the 4.0.1 upgrade and booting into system always threw me back into recovery. Flashing full 4.0.1 also just resulted in a bootloop.

1. So I did a full system reset, following the OnePlus 3T unbrick tutorial, which brings you back to 3.5.1, fully resetting the device, bootloader, recovery etc back to stock. (I did not need to install the driver linked in the thread, Windows 10 already had it from somewhere)

2. I then booted into the system, did the initial setup, and updated to 4.0.1 using the built-in updater.

3. Rebooted the device, enabled developer mode and OEM unlocking from there.

4. Rebooted into bootloader, unlocked the device (fastboot oem unlock)

5. Directly flashed TWRP 3.0.2 (fastboot flash recovery twrp.img)

6. Directly booted into TWRP from fastboot (fastboot boot twrp.img), enabled system write, triggering dm-verity

7. Transfered SuperSU 2.79-SR2 and flashed it

8. Rebooted into system, device restarted twice

9. é voila, back in clean 4.0.1 environment rooted without dm-verity issues, most current bootloader.

I just hope someone figures out an easier upgrade path that does not trigger dm-verity soon, always fully resetting the device is definately not viable. Maybe by uninstalling supersu from system, then flashing the upgrade in recovery, and directly flashing supersu again.
[OnePlus 3T Guides, News, & Discussion] wism84:
Hi,

can you explain step by step how you did a full system reset? I haven't a bricked phone. I have tried but I failed. Thank you very much.
[OnePlus 3T Guides, News, & Discussion] tdamocles:
I was on 4.0 with twrp 3.0.3.0beta1 with no dm-verity error and wanted to flash the 4.01 with the twrp beta1 and supersu and when I did it triggered the dm-verity error again. How to get rid of it? I want to stay encrypted.

I tried to restore a backup 4.0 with restoring modem, bootloader and I still get the dm-verity error. What the!!!!
[OnePlus 3T Guides, News, & Discussion] MrMeeseeks:
For me, I don't want to deal with it and the unlocked bootloader warning. I can deal with one but I don't feel like messing with pushing it twice or waiting an extra 15 seconds to wait for both to time out just to boot.
[OnePlus 3T Guides, News, & Discussion] tdamocles:
Since I'm on 4.0 and wanting to go to 4.01, will flashing the 4.0 bootloader take the dm-verity error away?
[OnePlus 3T Guides, News, & Discussion] CraigUK87:
I can confirm this has worked with my device. Weirdly.... But hey, that's tech for you. 4.0.1 perfectly running with no DM Verity error. Winner.
[OnePlus 3T Guides, News, & Discussion] 2015Ducatimulti:
same here on 4.0.1 with TWRP 3.0.3-1beta, flash the 3.5.4 boot image and the warning message was gone.:good:
[OnePlus 3T Guides, News, & Discussion] tdamocles:
Bootloader? Boot image? Firmware? So many different words being used..... so which one am I supposed to flash?
[OnePlus 3T Guides, News, & Discussion] 2015Ducatimulti:
this zip file attached, I flashed through TWRP like any other zip file.
[OnePlus 3T Guides, News, & Discussion] wozn:
anyone have an reason why i shouldn't run the old bootloader? i get that dm-verity message also. I mean will it casue any issues with 4.0.1 or future updates

ffs i never had the problems i am having now with my old OnePlus One.
[OnePlus 3T Guides, News, & Discussion] Bionic Toad:
I flashed this zip and it did indeed get rid of the dm-verity error screen. I am on 4.0.2 and TWRP RC1 for oneplus3t
[OnePlus 3T Guides, News, & Discussion] kamikaze2112:
Flashed this and the message went away also. No noticeable side effects as of yet.
[OnePlus 3T Guides, News, & Discussion] mohawahba:
It did not work, just reporting
[OnePlus 3T Guides, News, & Discussion] Sykojoe:
Thanks, just flashed 4.0.2 last night and was already annoyed with the extra warning.

Flashing the zip removed it.
[OnePlus 3T Guides, News, & Discussion] :
Strange! On 4.0.1 and 4.0.2 I havn't expirienced the dm-verity error. On openbeta2 it was there again, and flashing aboot from 4.0.2 didn't help. Restoring all the bootloader files from 4.0.2 fixed it. Then I was curious: I clean flashed 4.0.2 and had NO dm-verity error. Then I clean flashed openbeta2 (try before waa dirty flash openbeta2), and dm-verity was greating again... No clue what' going on here... Now I'm back to 4.0.2 without any dm-verity error...

Anyway: I'm happy the zip helped!
[OnePlus 3T Guides, News, & Discussion] Sykojoe:
I had flashed it over rooted 3.5.4 no wipe and then rooted. After that it was there.

Can't remember if it showed up after I upgraded TWRP to 3.0.3-1 or just after the flash of OTA 4.0.2
[OnePlus 3T Guides, News, & Discussion] v014nd:
Hey bro, i flash your zip and it work perfect, dm-verity was gone.

But!

I think today i cant update via OTA because that old bootloader, i have stock recovery, no root, and closed bootloader. When i flash your zip i think in future i can update os via ota, but it was not)

Is any idea gow can i update my device? Update from local folder with full rom 1.4Gb doesnt work also, just "Install failed" in recovery.
[OnePlus 3T Guides, News, & Discussion] :
If you are stock in the first place, there wouldn't be any dm-verity error. dm-verity is triggerd if you swipe right on twrps question to modify system.

If you expirience dm-verity, you are not stock, but have modified something.

If system is modified, incremental otas can't work any more, since they contain binary patches, which require system to be byte by byte the original unmodified image.

In this case just dirty flash (or sideload) the full ota.

If you expirience dm-verity error with completely stock, I have no clue at all what's going on or how to fix it.
[OnePlus 3T Guides, News, & Discussion] v014nd:
Thanx for reply, after buying device a had an hydrogen os, trying to update to oxygen, i install all the possible soft including twrp, and have dm error.

When i finally got oxygen4 i want to back to stock recovery for ota updates, i flash stock rec, lock boot. And then i find your post with old bootloader zip for dm-verity. i flash it and think i finally got full stock Oxy4 without dm-verity error. But in fact, now i cant get update with ota, and i think it is because that bootloader from android6.

Do you have (or know where it is) zip with stock bootloader for oxy4?
[OnePlus 3T Guides, News, & Discussion] nebulah:
As soon as I pushed stock recovery it asked for my PIN. After which it began "Decrypting", the progress bar moved to 99% and has stopped completely. Any ideas?
[OnePlus 3T Guides, News, & Discussion] :
If you want to completely return to stock and nothing from the guides & news section (or q&a section) works for you, try the unbrick tool. Sorry, but reverting to stock is not my topic... (no wish to do so - boring... ;) )

Good luck, cross my fingers!

(EDIT: just realised I have never seen stock recovery - I switched it on, updated from 3.5.4 to 4.0 and rebooted to fastboot mode... I'm really not the one, you should ask for returning to stock. My mantra is: Who never bricked a device - has not flashed hard enough! ;) )
[OnePlus 3T Guides, News, & Discussion] th3g1z:
the dm-verity error was annoying me too :P this seemed to do the trick without having to flash anything.. TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.

fastboot oem disable_dm_verity

fastboot oem enable_dm_verity
[OnePlus 3T Guides, News, & Discussion] rtp20in:
Wow. That was easy. Worked like a charm. Thank you so much.:good::good:
[OnePlus 3T Guides, News, & Discussion] dbabaev21:
Try this guide: https://xdaforums.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/

Even though it's for OnePlus 3, I think it should work for OnePlus 3T.
[OnePlus 3T Guides, News, & Discussion] zni3h:
That was easy, thanks man
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Do these steps work if LineageOS is installed and I want to get rid of the dm-verity notification ?
[OnePlus 3T Guides, News, & Discussion] gebla:
How did you input these commands? I tried a terminal but it did not work, fastboot was not recognized.
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
You need the SDK installed or the platform tools, you can find the latest Windows tools here:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip
[OnePlus 3T Guides, News, & Discussion] th3g1z:
Yes
[OnePlus 3T Guides, News, & Discussion] shiznig:
I guess it's true, some things in life is that simple.

Thanks so much good sir. :angel:
[OnePlus 3T Guides, News, & Discussion] gebla:
Yes this worked for me as well. Thanks for sharing!

Guides I used to ensure I can enter the fastboot commands:

How to install adb: https://xdaforums.com/showthread.php?t=2588979

How to get into fastboot: https://tektab.com/2015/10/31/android-bootloaderfastboot-mode-and-recovery-mode-explained/
[OnePlus 3T Guides, News, & Discussion] Stefa.:
Hi guys,

thanks for sharing all this usefull information.

I have TWRP and un-encrypted device (I flashed the dm-no-verity file before rooting); the thing that I have not understood completly is: what is going to cause the dm-verity issue?

I ask this because, starting from my primary ROM (Oxygen 3.5.4 so Android 6.0.1) I would like to flash a 7.0 ROM as secondary one. What are the scenario in which you experienced this error?

Thanks in advance for your answers ;)
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Worked for me, thanks.
[OnePlus 3T Guides, News, & Discussion] spida_singh:
Does this affect Android Pay in anyway? Ill check myself later when back form work either way.
[OnePlus 3T Guides, News, & Discussion] kpenny:
Do I need to input both commands for this to work?

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

Yes, both commands take away the dm_verity message, but the unlocked bootloader message remains. Anyway to get rid of that?
[OnePlus 3T Guides, News, & Discussion] rohitjaiswal:
you have to flash full oos 3.5.4 first

You have to flash full OTA OOS 3.5.4 first once it booted successfully then you can upgrade to Nougat and that issue will be get solved by install OOS 3.5.4.
[OnePlus 3T Guides, News, & Discussion] Bentso:
Thanks!
[OnePlus 3T Guides, News, & Discussion] Diabollon:
Thanks ! Is working for me easy fine.
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
Edit: Deleted, sorry wrong thread.
[OnePlus 3T Guides, News, & Discussion] Explorer23:
[MENTION=3878912]th3g1z[/MENTION]

Thanks!

Can confirm it also works for OP3.
[OnePlus 3T Guides, News, & Discussion] byAidan:
Thanks for sharing th3g1z, worked great :)
[OnePlus 3T Guides, News, & Discussion] E66666666:
Thanks, this works perfectly! Do you know what it actually does? Also how'd you find it? Dumping aboot?
[OnePlus 3T Guides, News, & Discussion] th3g1z:
Yes, pretty much, hexdump of aboot. I still am curious where the bit that gets flipped resides but haven't had the time to cross check. If anyone feels like it.. dd the partitions included in firmware while the warning is there and do it again after you remove it and diff the files.. It would at least tell us what partition is modified.
[OnePlus 3T Guides, News, & Discussion] sjaak1234:
Are you rooted? I'm wondering if this method would work for those that don't want root but do want to modify the system partition.

E.g. Stock rom, flash twrp.img, boot into twrp, swipe right to enable modifications and change whatever you want to change. Then boot into fastboot, run those two commands and reboot. Would that mean no DM error and a working phone?
[OnePlus 3T Guides, News, & Discussion] th3g1z:
If you have modified your kernel to disable dm-verity (ie flashed SuperSU or similar) then it should, I believe.
[OnePlus 3T Guides, News, & Discussion] sjaak1234:
Okay so on the stock rom you'd probably still need to flash the dm-verify.zip.
[OnePlus 3T Guides, News, & Discussion] the_rooter:
So i am confused a bit. why do we have to do both why not just disable dm verity
[OnePlus 3T Guides, News, & Discussion] BIGWORM:
So I ran into this error coming from Resurrection Remix MM AND N. I decided to give stock rooted a try. So I downloaded and installed the full OTA through TWRP 3.0.4 and flashed SuperSU in the same session. I'm still getting the dm-verity error upon boot up, but it's letting me boot into system. Is there anyway to get rid of that? I tried the fastboot commands from above before flashing OTA but they didn't work. Should I try again?

*edit*

Re-running the fastboot commands again worked for me. Error is gone. In all my years of playing with android phones I'm finally running stock rooted lol!
[OnePlus 3T Guides, News, & Discussion] null0seven:
Works fine on OnPlus 3.

Thank you.
[OnePlus 3T Guides, News, & Discussion] Stefa.:
Can you please kindly help me on this?

Thanks in advance for your answers!
[OnePlus 3T Guides, News, & Discussion] avalx:
Done on my 1+3 - thanks! :cool:
[OnePlus 3T Guides, News, & Discussion] jocaboss:
Amazing! You are the man
[OnePlus 3T Guides, News, & Discussion] weakenfalls01:
Hey guys,

I'm currently running oxygen os 4.0.2 with TWRP beta1 and SuperSU 2.79

Now my issue is that I can't restored my backup for some strange reasons.

Can anyone assist with that ?

Thanks!
[OnePlus 3T Guides, News, & Discussion] 2428lu:
Very troublesome, but really effective, damn five seconds tips finally gone:svetius:
[OnePlus 3T Guides, News, & Discussion] prabs99:
Does it wipe data?
[OnePlus 3T Guides, News, & Discussion] Doc Sniper:
On my phone it only removed the dm-verity notification, nothing else. :)
[OnePlus 3T Guides, News, & Discussion] ddaharu:
Can someone help this guy out? He did us a huge favor. Its the least we could do.
[OnePlus 3T Guides, News, & Discussion] Eilkh:
Thank you very much !!!
[OnePlus 3T Guides, News, & Discussion] Ashtrix:
Thanks to the XDA portal we are done now.

Who the fck is that dumb enough to store corporate data on a Bootloader unlocked device ? The second exploit which isn't an exploit ffs it's a damn flag in the Bootloader giving control to the end user just like most of the XDA users wanted, damn it man It needs physical access and not a vulnerability at all in any case....We are going to see all that nag screen again on all Nougat Bootloaders.
[OnePlus 3T Guides, News, & Discussion] johndogless:
Was working on 4.02

This worked great on 4.02. Got the same error on 4.03. Also now ADB not working properly, can't get fastboot oem commands to work.

Could a flashed zip file fix this?
[OnePlus 3T Guides, News, & Discussion] Regionella:
How could i do fastboot and write this commands?
[OnePlus 3T Guides, News, & Discussion] MoHed:
+1 for a TWRP flashable zip from any of our nice devs

fastboot oem disable_dm_verity and fastboot oem enable_dm_verity do not seem to work on OOS 4.03.

Also SuperUser 2.79 does not seem to patch the dm_verity in 4.03.

Any other (easy) solutions.
[OnePlus 3T Guides, News, & Discussion] MrMeeseeks:
This worked for me. Grab the no-verity-opt-encrypt-5.1.zip. Credit to [MENTION=5672995]jcadduono[/MENTION] for the zip.

Edit: I'm not sure if it will get rid of the warning if it is already present. It worked for me though flashing it in TWRP before booting into the system. You should do that if you swipe to allow modifications or mount /system and make any changes before booting back into system.
[OnePlus 3T Guides, News, & Discussion] alopez426:
Very simple fix

Just fixed this issue on my OnePlus 3 with the following command:

fastboot oem enable_dm_verity

No more dm-verity error, found the answer here (had to add spaces to the domain as it would not let me add links with a new account):

forums. oneplus. net/threads/oneplus-3-dm-verity-verification-failed-when-i-boot.476968/page-3#post-15708958
[OnePlus 3T Guides, News, & Discussion] uudruid74:
ekl@Taro ~/Programming/OnePlus3T % fastboot devices :(

4b729b8a	fastboot

ekl@Taro ~/Programming/OnePlus3T % fastboot oem enable_dm_verity

...

FAILED (remote: unknown command)

finished. total time: 0.019s
[OnePlus 3T Guides, News, & Discussion] fbf2201:
OOS 4.0.3 ?
[OnePlus 3T Guides, News, & Discussion] uudruid74:
Yes ... I think the OP needs to be edited as it links directly to the post I quoted, but there is no warning that if you updated to the latest OOS, you are DOA.

I followed the steps from the OnePlus site to root (after doing a full OTA) and now its just stuck at the boot animation. I'm unsure of the issue, but the that thread (especially) and this are starting to get a bit outdated. It looks like the unreleased twrp is the one to get (which I didn't find anywhere before now for the obvious reasons) and who knows if I can get this stupid error message off my screen when I power on.

I'm about to flash the full OS and see if I can at least get a booting system, then I'll try again! I just want root! This used to be so easy on my One!

Oh - is it safe to relock the bootloader after rooting and installing SU? Maybe that will make the message go away?