[FIX] Device-Mapper-Verity fix for Oxygen OS Nougat Rom ( 4.0.1 and Open Beta's)

[groshnack]

You need to flash Oxygen OS to reset variables in bootloader . ( it will think that the system image is not modified ) with trustred Oxygen Recovery and Wipe data , Dalvik and all the 3 options .
then Simply when DM verity is gone simply flash your Custom ROM and Enjoy ( prior Flashing TWRP of your Choice )

Basically Allow Modifications (TWRP Swipe , basicallly triggers this dm verity ) when On Oxygen OS ( if done before First Boot )

OK that is clear now. Thank you!

 

[cpt.macp]

So in other words. If you used the phone just for hobby, example flashing ROMs and mods, it's no problem. Do you use it for real personal matters such as banking, corporate emails etc can we best carry out this operation. I just think if you root the phone you it certainly should not be used for business stuff! But just as a hobby in my case, we do so not to worry about the message, or am I wrong?

Indeed It is not any problem for Root Users who know what they are doing .


For information aided people it can be a disaster ( data can be stolen and more ) as in the history of Android Security there had been lot of exploits and the New SE-Linux making it more difficult to gain root access even after unlocking bootlaodaer just for the sake of information aided people. and making it difficult for lots of developer

 

[abalam]

Indeed It is not any problem for Root Users who know what they are doing .


For information aided people it can be a disaster ( data can be stolen and more ) as in the history of Android Security there had been lot of exploits and the New SE-Linux making it more difficult to gain root access even after unlocking bootlaodaer just for the sake of information aided people. and making it difficult for lots of developer

Basically it's just a warning from Google saying that you must be careful that you are rooted. Wow something new. I do know for sure that the majority here knows where you have to watch it if you're rooted. I think Google scare people tried to do with this warning so they go rooting the device less quickly and not use go making mods and ROMs.

 

[cpt.macp]

Basically it's just a warning from Google saying that you must be careful that you are rooted. Wow something new. I do know for sure that the majority here knows where you have to watch it if you're rooted. I think Google scare people tried to do with this warning so they go rooting the device less quickly and not use go making mods and ROMs.

I would say Yes for most of the part . But its a necessary evil , thing which google is doing as Android's past history with Exploits is not good

 

[abalam]

I would say Yes for most of the part . But its a necessary evil , thing which google is doing as Android's past history with Exploits is not good

But without such notification if you have root you walk risks.
With MM you will not notice if you were rooted but when you walked risk

---------- Post added at 09:14 AM ---------- Previous post was at 09:13 AM ----------

With MM you will not notice if you were rooted but when you walked risk

 

[heisenberg33]

The best and fastest method to fix Device-Mapper-Verity
boot to FASTBOOT and type this commands one after another
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity

 

[abalam]

The best and fastest method to fix Device-Mapper-Verity
boot to FASTBOOT and type this commands one after another
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity

Ah sure.....???

 

[heisenberg33]

Ah sure.....???

yes

 

[abalam]

yes

Unbelievable here, all performing operations and now you come with one simple line terminal and dissolved.[emoji16] [emoji16] [emoji16] [emoji16]

 

[philidor]

The best and fastest method to fix Device-Mapper-Verity
boot to FASTBOOT and type this commands one after another
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity

OK it works.... only two command lines! :good:

 

[abalam]

Gif this man a beer ???

 

[TNSMANI]

Only one command is enough, the 'enable' command. Not my finding, posted elsewhere and tested by me.

 

[cpt.macp]

fastboot oem enable_dm_verity works with Updated Nougat bootloader
so it wont work with Old Open Beta's and Old Community builds having dm verity issue.

and only fastboot oem disable_dm_verity is sufficient

 

[JohnHorus]

Can these screens be removed without flashing back to stock?

Just flashed lineage and I just find these screens really annoying. I don't see any problems yet, but I was just wondering if there was a way to flash something blank or otherwise disable the screens. I had a Moto X Play before this and there was a similar message on the boot screen, I found a custom boot screen to flash over it that was the same as stock, but just removed the warning text. Anyone know if such a thing would be possible for the OP3?

 

[siankatabg]

Just flashed lineage and I just find these screens really annoying. I don't see any problems yet, but I was just wondering if there was a way to flash something blank or otherwise disable the screens. I had a Moto X Play before this and there was a similar message on the boot screen, I found a custom boot screen to flash over it that was the same as stock, but just removed the warning text. Anyone know if such a thing would be possible for the OP3?

You can remove the second screen using this thread:
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339

But there is still no way for removing the first one.

 

[daviss101]

using either of the commands didnt remove the DM verity on boot up. Im on experience ROM 10.1.

edit - just the enable one worked for me. thanks.

 

[audinak2]

Thank you, It worked :highfive:

 

[EdHicks]

I'm trying to understand how dm-verity works.

I'm thinking that it is a particularly dumb process in that it doesn't take the system partition and compare it to what it found at last boot. Instead, there are events that trip a flag. At boot, the flag is checked and nothing else. So we can go in and make changes to the system partition as long as we reset the flag before we boot again.

Have I got the concept?

 

[Gerjannn]

The best and fastest method to fix Device-Mapper-Verity
boot to FASTBOOT and type this commands one after another
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity

Wow you have no idea how happy I am this fixed it for me!! Thanks

 

[[email protected]]

Help! I need somebody HELP!...

People HI!
I stack with ADB Sideload step.
First, i have toruble with read of .ZIP, solve it trought update of drivers and ADB.
Now, i'm allowed to sideloade it, all time have a "Installation failed" message on stock recovery "install from ADB" screen and no any error mssg from ADB terminal, only "Total xfer: 1.00x".
I'm not are the +85lvl developer, or hard-core modifier of android ROM`s, only adult user, but i stack so strong first time... Anybody help?
*'i'm allready trying sideload OOS 4.0.2, OOS 4.1.1 with same result. Install failur on 47% of serving zip.
What i'm allready do:
-Wipe ALL (sys, dalvic, cashe, media EVERYTHING) via TWRP(BlueSpark)
*for that moment, i have NOTHING on board of my OP3, recovery only
-Flash Stock recovery via fastboot (so, i think, now i have completely nothing from prevision ROM)
-Wipe everything (all 3 options) via stock recovery
-reboot to stock recovery
-trying to flash OOS 4.0.2 trought fastboot
- STACK again on 47%
*i'm allready trying to sideload via TWRP, it`s showing more informative logs, but... 47% of ADB serving ZIP, TWRP showing progress bar for loading ZIP as 100%, no any error mssg`s. Not working again.
Also, i got DM_verity warning again and -for that time- script, wich one i use before (fastboot oem disable_dm_verity) not working anymore. Flashable NO_VERITY.zip also not help with my problem....

Anyone has any idea?
P.S. i'm posted here a first time, so please, don't LOL around, ok?

SO, AFTER LONG-TIME SHAMAN DANCING:
Finaly, i flash it by sideload with OOS 4.1.6, to do that i make totaly wipe again from TWRP,
then i flash script from this tread:https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094;
then i disable dm-verity via fastboot;
then install stock recovery, but get again dm-verity warning, make factory reset and reboot again to stock recovery;
then, using stock recovery i choose ADB install and exec sideload of OOS 4.1.6.zip to body.
Now it seem like OK. Working, no Verity warning, all stock...

Probably, root of my trouble was in incorrect data partition file system type. It was f2fs (don't ask me - why?), after i change it back, all gone.

Everybody thanks for attention.