yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T Guides, News, & Discussion] pmarotos:
Hello friends,

i've update from 4.0.2 to 4.0.3, and lost super su(root), and has appeared the dm-verity message.

What should i do to get rid of it?

The method above of enable or disable through fastboot, doesn't work anymore.

It says failed command.

Thanks.
[OnePlus 3T Guides, News, & Discussion] habylab:
What is the issue with this screen popping up anyway? Nice to remove, but only delays boot by a few seconds.
[OnePlus 3T Guides, News, & Discussion] brmbjn:
after flash twrp, dm-verity show again ?? why ? please help
[OnePlus 3T Guides, News, & Discussion] DonatoG16:
Hi,

I've got an error after doing: "fastboot oem disable_dm_verity".

I'm running OOS 4.0.3, Official TWRP, and last SuperSu.

Error:

"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem disable_dm_verity

...

FAILED (remote: unknown command)

finished. total time: 0.016s"
[OnePlus 3T Guides, News, & Discussion] casual_kikoo:
Your fastboot version might not be up to date.

You can download the latest version here (this contains only adb and fastboot package, not the whole SDK).

Edit

True that the OxygenOS 4.0.3 seems to have "fix" this, so not a SDK problem.
[OnePlus 3T Guides, News, & Discussion] DonatoG16:
I fixed by downgrading to OOS 4.0.2, fix dm verity and upgraded again to 4.0.3.

Sorry for my bad english.
[OnePlus 3T Guides, News, & Discussion] C4RP1ST:
thank you for this brilliant solution !

I was going to flash for nothing :good:
[OnePlus 3T Guides, News, & Discussion] SpasilliumNexus:
What? You say it like it's a bad thing.
[OnePlus 3T Guides, News, & Discussion] morphvale:
Most of us got the OP3 for it's modding abilities, not its security. Most of us run unlocked bootloaders. Most of us run different kernels.

That message only tells us verity has been breached, doesn't prevents the phone from booting if triggered, as per Google's design anyway.

You want security? Go get a Samsung or an iPhone.

So yes, from my point of view, and others for that matter of fact, it is a bad thing.
[OnePlus 3T Guides, News, & Discussion] brmbjn:
it no fix at my op3t

i try to use fastboot from your link. but still cannot complete fastboot oem disable_dm_verity ??

anyone have another solution ?
[OnePlus 3T Guides, News, & Discussion] Naprzod:
I made a new thread. Take a look at it!
[OnePlus 3T Guides, News, & Discussion] ashokmor007:
can you just tel how did you copy the file Steps?
[OnePlus 3T Guides, News, & Discussion] Regionella:
Hello. Where will i write this fastboot commands?
[OnePlus 3T Guides, News, & Discussion] pxrave:
tryd on latest op3 firmware

now i have freedom os 2.4 installed

does not work on my a3003

both commands

failed (remote: unknown command

finished total time ....

how to fix it?
[OnePlus 3T Guides, News, & Discussion] beyond291:
Thanks for the information.

But both of these commands I just get result with "FAILED (remote: unknown command)".

I am in stock recovery and Oxygen 4.0.3(the latest firmware) and I have try it with lock&unlock bootloader.

What OS version do you have?
[OnePlus 3T Guides, News, & Discussion] Naprzod:
https://xdaforums.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
[OnePlus 3T Guides, News, & Discussion] beyond291:
Thank you! I have fixed it.
[OnePlus 3T Guides, News, & Discussion] pxrave:
dude thats for op3t

i will create it for op3

https://xdaforums.com/showpost.php?p=71102839&postcount=132
[OnePlus 3T Guides, News, & Discussion] Naprzod:
We're on OP3T forum so....

I created for op3 too and they closed my thread becuase there was a comment in another thread with a similar solution.... :rolleyes:
[OnePlus 3T Guides, News, & Discussion] pxrave:
haha damn your right sry i didnt check my tabs in xda

worked fine ;) but iam searching for another solution to remove the annoying unlocked bootloader screen...

any found a solution?
[OnePlus 3T Guides, News, & Discussion] Naprzod:
I'm glad it worked. No, there is no solution to remove the unlocked bootloader warning and probably there won't be.

I left you a message in this post: https://xdaforums.com/showpost.php?p=71102839&postcount=132 . Take a look at it. It bothers me a lot when someone take the credits for just reuploading the files and make a video.
[OnePlus 3T Guides, News, & Discussion] guardian76:
Hi,

I have op3t with 4.0.3, twrp and root. I see this screen after I have flash the 4.0.3 full FW, I try this two commands in fastboot mode but I receive

...

FAILED (remote: unknown command)

finished. total time: 0.007s

Where I'm wrong?

Thks
[OnePlus 3T Guides, News, & Discussion] zeRONY:
please help.. this happened to me too..
[OnePlus 3T Guides, News, & Discussion] xpissio:
It doesn't work for me, when I enter "fastboot oem disable_dm_verity" it says: FAILED (remote: unknown command).
[OnePlus 3T Guides, News, & Discussion] guardian76:
Follow this guide https://xdaforums.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094

I have solved !

Thks
[OnePlus 3T Guides, News, & Discussion] nirh216:
for some reason I'm getting FAILED. unknown command

USB Debug ON

enable oem unlocking ON

What am I missing?
[OnePlus 3T Guides, News, & Discussion] Naprzod:
You missed reading the two last post. READ!!!!!!!!!!!!!!!!
[OnePlus 3T Guides, News, & Discussion] nirh216:
I did follow the post above, but once I flashed the 4.0.3 and reboot, saw that message again....
[OnePlus 3T Guides, News, & Discussion] two5boy:
Work on mine. Thanks for the efforts.
[OnePlus 3T Guides, News, & Discussion] ‬1‬:
Fixed the issue. Thanks.
[OnePlus 3T Guides, News, & Discussion] mohawahba:
error

hi, thanks for your work. however, I'm stuck here with error unknown command.

N.B: I have done it before on the same phone and it worked. but today i backed up everything with twrp then factory reset it, installed hydrogen (which basically triggered dm verity back) then i restored again the backup image. sadly, I tried the two lines again and gives me the attached error.

Any idea?

Thanks
[OnePlus 3T Guides, News, & Discussion] MartinMo:
I've got the same error on my OP3T running 4.0.3.
[OnePlus 3T Guides, News, & Discussion] Naprzod:
https://xdaforums.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094/page10
[OnePlus 3T Guides, News, & Discussion] vinnik:
Hey I have another question: what if I flashed the firmware zip for the dm varity fix before (I think I took the one from the official oneplus forum guide to unlock bootloader etc.) How can I "unflash" it and have it clean with the commands without having flashed?

Also I was wondering if the dm varity resets everytime you clean flash a rom? Or is it deeper in the Phone itself?
[OnePlus 3T Guides, News, & Discussion] MrWilsonxD:
Thanks, this worked perfectly for me with my oneplus 3. I had went from Freedom OS ce 2.5 to Experience and somehow tripped dm-verity. Followed the instructions and it worked flawlessly.
[OnePlus 3T Guides, News, & Discussion] SyS62:
any idea for remove dm-verity warning on 7.1.1?
[OnePlus 3T Guides, News, & Discussion] Naprzod:
There is a thread for it.
[OnePlus 3T Guides, News, & Discussion] bkr32:
link please
[OnePlus 3T Guides, News, & Discussion] SyS62:
https://xdaforums.com/oneplus-3t/how-to/4-0-3-flashable-firmware-modem-t3553707
[OnePlus 3T Guides, News, & Discussion] ddaharu:
So flashing the latest firmware gets rid of the dm-verity warning on 7.1.1? Not really seeing anything saying that in the thread.
[OnePlus 3T Guides, News, & Discussion] Akash1739:
Is there a problem if it stays?

Because i have tried like 50 time booting into fastboot mode and it still stays....can u tell me if there is a problem if it stays?
[OnePlus 3T Guides, News, & Discussion] kunal1540:
No there is no problem functionality wise, it's just an annoyance that's it and that too you can skip by just pressing power button
[OnePlus 3T Guides, News, & Discussion] biorpg:
When you boot your phone into fastboot mode, what response does typing 'fastboot devices' give on your computer?
[OnePlus 3T Guides, News, & Discussion] suhaibahmad:
i cant root my s7edge , the latest nougat february patch installed ? am i the only one ? i untick the auto reboot in odin and manually boot into twrp after flashing it but its stucked there, it is the latest twrp hero2lte 3.1.0
[OnePlus 3T Guides, News, & Discussion] timobayl:
I think you are a little big wrong here.

Better ask in the s7edge section, here is OnePlus 3(T).
[OnePlus 3T Guides, News, & Discussion] siva986:
not working in my One plus 3. It says unknown command.

please help me fix this issue
[OnePlus 3T Guides, News, & Discussion] Naprzod:
Search and read.

A mod should close the thread.
[OnePlus 3T Guides, News, & Discussion] timobayl:
A few more infos are helpfull.

You are in fastboot when use the commands and did you start adb terminal?
[OnePlus 3T Guides, News, & Discussion] siva986:
Yes I was in fastboot and I did run the adb terminal. But when I run the command it says unknown command.
[OnePlus 3T Guides, News, & Discussion] timobayl:
Sure you have no typo.
[OnePlus 3T Guides, News, & Discussion] siva986:
I didn't understand. Make it clear.
[OnePlus 3T Guides, News, & Discussion] timobayl:
It is wrong on the pc side. Maybe you have written it wrong or adb is not installed. Nothing mobilephone related.
[OnePlus 3T Guides, News, & Discussion] m4.p3:
I'm on the same boat, stock OOS 4.0.3 and locked bootloader:

C:\adb>fastboot devices

5d61f60c fastboot

C:\adb>fastboot oem disable_dm_verity

...

FAILED (remote: unknown command)

finished. total time: 0.011s

C:\adb>fastboot oem enable_dm_verity

...

FAILED (remote: unknown command)

finished. total time: 0.004s

thanks for any solutions
[OnePlus 3T Guides, News, & Discussion] timobayl:
I think it is because locked bootloader.

You can to nothing to fix the DM-verity
[OnePlus 3T Guides, News, & Discussion] veroby:
Same here, unknown command. Im OpenBeta4, bootloader unlocked.

How could he possibly get the dm-verity with a locked bootloader. It is not possible to have twrp with a locked bootloader "no".
[OnePlus 3T Guides, News, & Discussion] m4.p3:
Hi guys, i foud a solution:

- go into (stock) recovery and wipe cache;

- flash OOS 4.0.2 with adb sideload;

- come back again to OOS 4.0.3 with OTA update.

DM Verity message is now finally gone.

Hope this can be helpful.
[OnePlus 3T Guides, News, & Discussion] veroby:
Try flashing su and see if it comes back. Always comes back for me.
[OnePlus 3T Guides, News, & Discussion] veroby:
Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the 4.03 firmware in TWRP. Problem solved. The firmware files are found here https://www.androidfilehost.com/?w=files&flid=145813
[OnePlus 3T Guides, News, & Discussion] Dr. Krieger:
I'm on OP Beta 4, shouldn't I flash the OB4 firmware after the fastboot commands?
[OnePlus 3T Guides, News, & Discussion] veroby:
Yes i had thought you stated you where on 4.0.3
[OnePlus 3T Guides, News, & Discussion] Dr. Krieger:
That's because I'm not the guy you quoted initially. :D

Thanks btw, stupid question but wanted to ask just to make sure.
[OnePlus 3T Guides, News, & Discussion] timobayl:
How he should do this with stock recovery and locked bootloader.
[OnePlus 3T Guides, News, & Discussion] veroby:
Yeah thats what i had thought but how can you get that problem while on stock recovery.
[OnePlus 3T Guides, News, & Discussion] timobayl:
I don't know. Never came a answer when this was asked.

Troll or on twrp with DM-verity - flash stock recovery - lock bootloader. :eek: :rolleyes:
[OnePlus 3T Guides, News, & Discussion] MrWilsonxD:
April fools......? ?
[OnePlus 3T Guides, News, & Discussion] m4.p3:
No trolls, I was on DM Verity message so I flashed OOS 4.0.3 and then stock recovery, in the end I locked again bootloader and unfortunately I had a persistent DM Verity message. To resolve I made the previous procedure that I wrote.

Here April fools has gone.
[OnePlus 3T Guides, News, & Discussion] veroby:
But if yoou had relocked bootloader it would have wiped your phone completely hence you would then have to sideload a rom. Following this there is no way you can have a persistent dm message. :rolleyes:
[OnePlus 3T Guides, News, & Discussion] m4.p3:
I had. No jokes.
[OnePlus 3T Guides, News, & Discussion] veroby:
What country/time zone you in. Is it still April 1
[OnePlus 3T Guides, News, & Discussion] m4.p3:
Ahahah, no man.

Anyway now I'm completaly stock without any kind of messages.
[OnePlus 3T Guides, News, & Discussion] falcon26:
Trying this on my 3T. Unlocked stock recovery and OOS 4.03 I get the Fail remote command. Will not work.
[OnePlus 3T Guides, News, & Discussion] timobayl:
Hm you have stock recovery? How you flash the other firmware? How you get DM-verity?

You have one with yellow letters or one with yellow and one with red?
[OnePlus 3T Guides, News, & Discussion] twoxa:
For the 1000th time I can't figure out why my fastboot doesn't wotk after installing adb drivers and oneplus 3t drivers. Can't see the phone.
[OnePlus 3T Guides, News, & Discussion] sakumaxp:
Do you have USB debugging enabled? And does your computer see the phone? If not after you enable us debugging, pull down the notification drawer and click on the USB debugging option and it should give you a list of options that you want to do with your phone
[OnePlus 3T Guides, News, & Discussion] twoxa:
Yup. Both. Still can't see the phone in bootloader with command window.
[OnePlus 3T Guides, News, & Discussion] Darkther:
getting an error "FAILED (remote: unknown command)"

I have adb and fastboot installed properly (I think). Any help?
[OnePlus 3T Guides, News, & Discussion] timobayl:
What shows up when you use" fastboot devices" with connected phone in fastboot mode.

If you see nothing it is a driver problem.
[OnePlus 3T Guides, News, & Discussion] Darkther:
Got it working. It wasn't the driver problem. This method seems to be working only when you are on Firmware version 4.0.2, I downgraded to this version entered the command then again flashed the 4.1.1 firmware and voila, the dm verity warning is gone.
[OnePlus 3T Guides, News, & Discussion] ravims:
I see this
[OnePlus 3T Guides, News, & Discussion] commoonist:
I'm having a problem where when I try to run this command, I get a

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem disable_dm_verity

...

FAILED (remote: unknown command)

finished. total time: 0.016s

and I have no clue what to do to fix this. When I check fastboot devices, my phone is recognized, but I'm not sure what to do beyond this in terms of problem-solving. Any help would be greatly appreciated! Thanks.

---------- Post added at 06:25 AM ---------- Previous post was at 06:02 AM ----------

Just realized someone else on this thread had a solution. I should read around a little more, whoops. Thanks anywho.

---------- Post added at 07:08 AM ---------- Previous post was at 06:25 AM ----------

This was exactly what I needed! I've been looking for a solution for about a week now, and this worked like a charm! Thanks a ton!
[OnePlus 3T Guides, News, & Discussion] speak51:
Gonna give it a go!

Thank you for the post! Honestly this whole dm-verity thing is stupid anyway. Back IN MY DAY with the OnePlus One you had to TWRP your way to Oxygen OS, and NOW all the sudden they're hindering users' ability of easily flashing TWRP/Customizations? DUMB! ANYWAY I'm gonna give it a whirl in a bit!
[OnePlus 3T Guides, News, & Discussion] jamiexx:
Can anyone with 4.0.2 and root dump the aboot partition and post it here? Thanks.
[OnePlus 3T Guides, News, & Discussion] Kyrluckechuck:
Hey there,

**ignore this part

So I've got a weird issue with following this. I flash the 4.0.2 firmware + modem, and have even tried the entire system via the recovery-twrp-oneplus-3t-t3507308 thread, but have had no luck getting the fastboot oem commands trick to work (although every time after I run this command the first time my phone boots it goes to the battery charging screen until I turn it off and on)...

Anything I could provide that could help debug this?

***edit

So after hours of messing around, I finally found a solution on the dm-verify-started-enforcing-mode-t3590187 thread -- adb reboot "dm-verity enforcing".

No idea why it worked, it shouldn't have, especially not on 4.1.3, but it worked and now my phone is booting with just the one stupid 5-second delay like usual :)

* Also have tested rebooting a few times to make sure it wasn't a one-off, including cold-boots.
[OnePlus 3T Guides, News, & Discussion] Krustak:
can you please write down exact command? Im trying adb reboot "dm-verify enforcing" and adb reboot dm-verify enforcing , nothing works

thank you
[OnePlus 3T Guides, News, & Discussion] zaworka:
Hey Krustak, after reading the thread that [MENTION=8282279]Kyrluckechuck[/MENTION] mentioned, I figured it out.

You have to enter the command 'adb reboot "dm-verity enforcing" ' when in recovery mode. I have used the TWRP 3.0.4.-1 and it worked like a charm. Not sure whether it is important which version to use.

Have fun being rid of the dm-verity screen ;)
[OnePlus 3T Guides, News, & Discussion] Krustak:
Nothing, like everything else I have tried before

Im on OOS 4.1.3

latest Blu spark TWRP

typing in command adb reboot "dm-verity enforcing"

phone reboots, but anoying DM-verify message is still there :/
[OnePlus 3T Guides, News, & Discussion] zaworka:
Thats weird...I am on OpenBeta 16 (OP3). Maybe try it with the TWRP version that I linked. If you are eager to use BluSpark's version I suggest typing in the command using 3.4.0-1 and reflashing BluSpark's after you can confirm whether it worked for you or not.

Also keep in mind, that the "dm-verity warning" refers to a second 5sec delay screen. You can not get rid of the first one, but of the second one. Just to clarify, if it should just be a misunderstanding =)
[OnePlus 3T Guides, News, & Discussion] Krustak:
Im not talking abou first screen about unlocked bootloader, Im talking about second about DM-VERIFY not being enforced :)

ok, I'll try your TWRP and let you know

---------- Post added at 11:19 AM ---------- Previous post was at 11:05 AM ----------

so no, its still same, even with diferent recovery
[OnePlus 3T Guides, News, & Discussion] zaworka:
Then I guess it is either related to the Beta Version of OOS or maybe the adb version you use. I am currently running adb version 1.0.32. You can check it by entering "adb version". If you are using an older version, try updating it to latest.

Else, I guess, you would need to flash another OOS version as it would be the only difference between our setup (assuming you are using an OP3 not OP3T though I would guess that should not make any difference).

I have just got one last idea: are you using a custom kernel? If so, try flashing the stock kernel (just reflash your current firmware) and typing in the command. I am not sure where the adb commands that are recognised by the device are stored. They might be part of the kernel and thus miss in custom kernels (just a lucky guess, no idea if any of this is correct ;) )
[OnePlus 3T Guides, News, & Discussion] Krustak:
ADB version 1.0.32

I have OP3T, thats the only difference i see here

Yes I have OOS 4.1.3 with latest blu spark kernel

anyway, thank you for advices
[OnePlus 3T Guides, News, & Discussion] zaworka:
Alright, I would give the stock kernel a try then. Or just settle with the dm-warning but you know...never settle :laugh:
[OnePlus 3T Guides, News, & Discussion] Kyrluckechuck:
Hmm, unfortunately repeating my process may be a bit of a PITA as there were a lot of flashes of various firmwares and full-file-packages's

For perspective though, I am using OOS 4.1.3 (7.1.1) on a OnePlus 3T.

Have you tried doing the normal method here of downgrading your firmware to 4.0.2, running the commands, them being ignored on your next reboot (still seeing the dm-verity screen), flashing 4.1.3, and then when your phone fully boots up, running the adb command? I think that was roughly the order, though I also tried flashing the no-verity-opt-encrypt-5.1.zip available below (as recommended in a few of the various guides) after flashing 4.1.3 and booting up once...

https:\/\/build.nethunter[dot]com/android-tools/no-verity-opt-encrypt/ (noobie limitation here or else I would just post the link)
[OnePlus 3T Guides, News, & Discussion] Krustak:
Im starting to ignore it :D
[OnePlus 3T Guides, News, & Discussion] Krustak:
I tried literally everything I have found. One time I thougt I have it, phone rebooting and no dm-verify, but after another reboot I got it back....

For now I'm going to ignore this stupid thing, but thank you
[OnePlus 3T Guides, News, & Discussion] The_Fry_Guy:
The way I got rid of DM Verity warning was not by any of these methods cause none of them work... It was by erasing system through fastboot then formatting system through fastboot then wiping EVERYTHING through TWRP and clean installing ROM. DM Verity is never to be seen again.
[OnePlus 3T Guides, News, & Discussion] maddler:
This works for me every single time:

https://xdaforums.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094

Did you try it as well?
[OnePlus 3T Guides, News, & Discussion] Kyrluckechuck:
Just following up, did you ever find a solution that worked for you?

For reference, my recovery environment is TWRP 3.1.1-0, may work on Stock/others

This was what worked for me after I encountered the error returning with my previous method not being enough (after doing a full-file dirty-flash upgrade to 4.1.5 & now 4.1.6):

(Things italicized I'm not sure if were necessary but I did them for good measure -- If people have success without some of the steps, please let me know and I'll update this)

Download all needed upgrade files (if doing an upgrade) and, *importantly*, download and copy v5.1 to your phone from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

Do the full-zip dirty-flash upgrade (after backing up obviously, and only if you're doing an upgrade)

Do the normal process for fixing dm-verity (i.e. flash down to 4.0.2 (firmware/modem only), do the fastboot commands, flash to 4.1.3/4.1.5/4.1.6 (firmware only).

In Recovery, flash the no-verity-opt-encrypt-5.1.zip, perform a dalvik+cache wipe, reboot.

Perform this command once it boots your device: adb reboot "dm-verity enforcing"

I hope that can be of some help!

Edit:

For any who don't already have the tools installed, the adb and fastboot commands should be run once you have downloaded and extracted the Android platform tools (in a terminal/shell/command prompt navigate to the containing folder if you didn't have an option to install them/chose not to)
[OnePlus 3T Guides, News, & Discussion] shackled:
This definitely works. Thanks!!!
[OnePlus 3T Guides, News, & Discussion] Shyonnu:
for newbies

Perform this command once it boots your device: adb reboot "dm-verity enforcing":

what is exactly the last command in fastboot/step 5

Thanks in advance
[OnePlus 3T Guides, News, & Discussion] arefin_sajib:
I executed the commands, they didn't work.

they said,unknown command, failed.

Then I got fixed by following,

flashed a stock recovery (open beta 6 recovery from official site) via fastboot.

then installed stock 4.1.3 OS from adb sideload.

rebooted and it's gone.
[OnePlus 3T Guides, News, & Discussion] Krustak:
Finally OOS 4.1.5.

executed this command adb reboot "dm-verity enforcing" and its gone
[OnePlus 3T Guides, News, & Discussion] despeh:
Finally for OOS 4.1.6 as well.

After upgraded to 4.1.6, IF it revert back to DM-verify with stock recovery image, perform the step below:

1) return to fastboot and flash the twrp recovery image.

2) flash the no-verity-opt-encrypt-5.1.zip, perform a dalvik+cache wipe, reboot.

3) Perform this command once boot up successfully. At command type: adb reboot "dm-verity enforcing"

it will restart the phone and the DM-verity warning is gone.