What is vox-eas? dm-verity ? - OnePlus 3T Questions & Answers

Some noob questions to which i can't find answers here
1)What is vox and eas? I see it on many ROM titles..
2) what is this dm-verity issue? Is it just a warning message that appears if you enable system partition amendment in twrp? Or this dm-verity issue makes the device unbootable ?
3) what is blob? Is it the same as firmware?
I hope i am not sounding stupid.. I am new to opt3...

google.com knows it
Sorry, but these questions are answered so many times here on XDA and on other sites

phoberus said:
google.com knows it
Sorry, but these questions are answered so many times here on XDA and on other sites
Click to expand...
Click to collapse
I tried google before posting here..
Read many threads on xda.. But i can read each and every post of every thread..
And instead of typing that reply, you could have typed the answer.. Thanx anyways...
Sent from my Redmi Note 3 using XDA Labs

EAS: https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/
Vox: Read first few posts from the supported Roms, example: https://forum.xda-developers.com/showpost.php?p=71394499&postcount=4
(about both you can read much in threads)
dm-verity issue: newer had this. I think this is if twrp can't decrypt your phone
blobs: parts of the firmware

phoberus said:
EAS: https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/
Vox: Read first few posts from the supported Roms, example: https://forum.xda-developers.com/showpost.php?p=71394499&postcount=4
(about both you can read much in threads)
dm-verity issue: newer had this. I think this is if twrp can't decrypt your phone
blobs: parts of the firmware
Click to expand...
Click to collapse
Thanks a lot.. That solved my doubts..
Only doubt left is dm-varity thing...
Sent from my Redmi Note 3 using XDA Labs

a.broken.star said:
Thanks a lot.. That solved my doubts..
Only doubt left is dm-varity thing...
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
You know, there's a pretty good search feature right here on XDA: https://forum.xda-developers.com/sitesearch.php?q=dm-verity
The first hit should be an article (pretty old, but still relevant) about dm-verity and the implication it has for those of us who like to tinker with our devices.
Most custom kernels and root solutions disable dm-verity. Otherwise there are zips around you can use as well.

Dm verity is a security measure that check the os and kernel for any tamperments ,it is usually triggered by Twrp or by rooting process as they changes the default recovery with different one ,in some cases DM verity won't let your mobile boot ,in order to prevent the unauthorized tamperment to run in os ,but DM verity and force encryption can be disabled by flashing DM verity remover zip ,but it leaves the red warning message

smarter than newton said:
Dm verity is a security measure that check the os and kernel for any tamperments ,it is usually triggered by Twrp or by rooting process as they changes the default recovery with different one ,in some cases DM verity won't let your mobile boot ,in order to prevent the unauthorized tamperment to run in os ,but DM verity and force encryption can be disabled by flashing DM verity remover zip ,but it leaves the red warning message
Click to expand...
Click to collapse
I read that if you give the permission that's asked when you first load twrp "allow system partition modification", then that triggers dm-varity.. But if flash supersu in the same session in twrp, it makes the dm-varity issue OK... But if it's just a warning message just like unlocked bootloader warning, then i am OK with it....
Sent from my Redmi Note 3 using XDA Labs

a.broken.star said:
I read that if you give the permission that's asked when you first load twrp "allow system partition modification", then that triggers dm-varity.. But if flash supersu in the same session in twrp, it makes the dm-varity issue OK... But if it's just a warning message just like unlocked bootloader warning, then i am OK with it....
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
But you need to remove the force encryption in order for device to boot properly or else it may need to reset your data including SD storage ,To force remove the encryption you can flash azip file and you can also remove the DM verity warning using adb commands

smarter than newton said:
But you need to remove the force encryption in order for device to boot properly or else it may need to reset your data including SD storage ,To force remove the encryption you can flash azip file and you can also remove the DM verity warning using adb commands
Click to expand...
Click to collapse
Okay.. I found the zip file and adb commands.. Thanx a lot...
Sent from my Redmi Note 3 using XDA Labs

phoberus said:
EAS: https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/
Vox: Read first few posts from the supported Roms, example: https://forum.xda-developers.com/showpost.php?p=71394499&postcount=4
(about both you can read much in threads)
dm-verity issue: newer had this. I think this is if twrp can't decrypt your phone
blobs: parts of the firmware
Click to expand...
Click to collapse
exactly

Use Magisk, you can stay encrypted.

Galactus said:
Use Magisk, you can stay encrypted.
Click to expand...
Click to collapse
So..
Unlock bootloader
Flash twrp
Flash magisk
Reboot...
No problems related to encryption and passwords etc?
Sent from my Redmi Note 3 using XDA Labs

a.broken.star said:
So..
Unlock bootloader
Flash twrp
Flash magisk
Reboot...
No problems related to encryption and passwords etc?
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Yep, same steps I took. I did have to delete my password key files in twrp the first time I rebooted after flashing magisk, but it's a simple fix. Been good ever since.
Currently running OOS 4.1.3, magisk V12 rooted, Franco kernel, encrypted, no issues.

a.broken.star said:
Okay.. I found the zip file and adb commands.. Thanx a lot...
Click to expand...
Click to collapse
You're welcome

Related

How to root 3T on OOS4.0 ?

Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.
So, with oxygen 4.0.1 the procedure will be the same?
TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.
bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it

Questions regarding dm-verity and OOS 4.0.x

Hey there.
I got my 3t in the day, 4.0.0 was released. So I unlocked my bootloader after upgrading.
At the time, dm-verity was new to me and so I ignored it.
By now I read up on it and guess I get it. What doesn't fit to what I read is the fact, that I modified my system in many ways. By flashing TWRP, by modifying system with super su and things like ad blockers (hosts file) and pixel launcher.
Yet I never installed the verity fix. I also use encrypted data partition.
How can that be?
My only guess is, I never installed a custom kernel yet or another Rom. But then again verity should be triggered way earlier. Did 4.0 not fully implement it?
mad-murdock said:
Hey there.
I got my 3t in the day, 4.0.0 was released. So I unlocked my bootloader after upgrading.
At the time, dm-verity was new to me and so I ignored it.
By now I read up on it and guess I get it. What doesn't fit to what I read is the fact, that I modified my system in many ways. By flashing TWRP, by modifying system with super su and things like ad blockers (hosts file) and pixel launcher.
Yet I never installed the verity fix. I also use encrypted data partition.
How can that be?
My only guess is, I never installed a custom kernel yet or another Rom. But then again verity should be triggered way earlier. Did 4.0 not fully implement it?
Click to expand...
Click to collapse
They say (in twrp thread and in oneplus forums) if you flash supersu, you are fine...
ram4ufriends said:
They say (in twrp thread and in oneplus forums) if you flash supersu, you are fine...
Click to expand...
Click to collapse
When am I not fine? Protection only triggers if kernel is exchanged?
It's not that I don't want to flash it, but I am eager to know.
*bump* - trying a last time, to see if anyone knows details
The whole point of dm verity is to make sure phone is not rooted or modified in any way that could compromise app security, luckily it doesn't work quite 100% as we can still root without triggering it, even though it should.
I guess, the answer to my question is, TWRP automatically applies the dm-verity patch on first install. I overlooked that feature to be honest, but it makes total sense to do so and protect custom recovery users from locking out of your phone
I have this questions too. And I can't decrypt Data even if I input the right password. I can't use recovery anymore with TWRP or the stock rec.
Here is some details about the dm-verity. https://source.android.com/security/verifiedboot/verified-boot.html
I only know Android N will encrypt Data by using f2fs file system.........
If you have some effective methods, please tell me. Thanks a lot!
mad-murdock said:
I guess, the answer to my question is, TWRP automatically applies the dm-verity patch on first install. I overlooked that feature to be honest, but it makes total sense to do so and protect custom recovery users from locking out of your phone
Click to expand...
Click to collapse
It's my understanding that SuperSU applies the dm-verity patch when it's installed.
napetost said:
I have this questions too. And I can't decrypt Data even if I input the right password. I can't use recovery anymore with TWRP or the stock rec.
Here is some details about the dm-verity. https://source.android.com/security/verifiedboot/verified-boot.html
I only know Android N will encrypt Data by using f2fs file system.........
If you have some effective methods, please tell me. Thanks a lot!
Click to expand...
Click to collapse
flash TWRP 3.0.3-1-beta1 and try again
I have found the right way!
First, you should flash back to OOS3.5 6.0, then set the pin password. And then copy OOS4.0 to /sdcard ,then using system update.Then you will update to OOS4.0 and you won't see any dm-verity problems.
napetost said:
I have found the right way!
First, you should flash back to OOS3.5 6.0, then set the pin password. And then copy OOS4.0 to /sdcard ,then using system update.Then you will update to OOS4.0 and you won't see any dm-verity problems.
Click to expand...
Click to collapse
That's one way. Using the TWRP beta is another. It's in the TWRP post, page 55, bottom. Post 550. Actually the last few pages of that post discuss this issue right now. Might be worth reading.

Afraid, I will start to hate my newly oneplus 3t due to this encryption/decryption th

Afraid, I will start to hate my newly oneplus 3t due to this encryption/decryption thing. Had to format userdata two times and lost already vital data since fone could't get decrypted after rom installation. What is the safest method to avoid this serious issue and I believe many users like me suffering with the same.
Hope somebody can help.
Thnx
Sent from my ONEPLUS A3003 using Tapatalk
ayyan84 said:
Afraid, I will start to hate my newly oneplus 3t due to this encryption/decryption thing. Had to format userdata two times and lost already vital data since fone could't get decrypted after rom installation. What is the safest method to avoid this serious issue and I believe many users like me suffering with the same.
Hope somebody can help.
Thnx
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
read read read read and read.
the_rooter said:
read read read read and read.
Click to expand...
Click to collapse
Where exactly?? ??
Sent from my ONEPLUS A3000 using Tapatalk
nano303 said:
Where exactly?? ??
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Xda-developers.com threads for said device. Google.com is also your friend.
Could u b precise and share few links. I have done a lot research before wiping my data.
Sent from my ONEPLUS A3003 using Tapatalk
the_rooter said:
read read read read and read.
Click to expand...
Click to collapse
the_rooter said:
Xda-developers.com threads for said device. Google.com is also your friend.
Click to expand...
Click to collapse
Nice useless garbage to fill your post count.
ayyan84 said:
Could u b precise and share few links. I have done a lot research before wiping my data.
Click to expand...
Click to collapse
I've spent the entire day dealing with the similar situation trying to get Magisk to work properly, and ended up removing the encryption.
TWRP 3.0.4-0 and newer may fix the issue now, but if it doesn't, either flash the disable forced encryption zip using the Toolkit, or the one from the TWRP thread, or flash a custom kernel which disables it, like ElementalX or blu_spark, all located in the Android Development sub-forum. I don't use custom ROMs so I won't know if they disable it in theirs. Read and ask them about it.
Then using a PC and fastboot, run "fastboot format userdata" then "fastboot reboot". This will WIPE YOUR DATA so back everything on internal storage up!
You won't be running encrypted anymore, and encryption can be re-enabled in Settings > Security.
Spasticdroid said:
Nice useless garbage to fill your post count.
I've spent the entire day dealing with the similar situation trying to get Magisk to work properly, and ended up removing the encryption.
TWRP 3.0.4-0 and newer may fix the issue now, but if it doesn't, either flash the disable forced encryption zip using the Toolkit, or the one from the TWRP thread, or flash a custom kernel which disables it, like ElementalX or blu_spark, all located in the Android Development sub-forum. I don't use custom ROMs so I won't know if they disable it in theirs. Read and ask them about it.
Then using a PC and fastboot, run "fastboot format userdata" then "fastboot reboot". This will WIPE YOUR DATA so back everything on internal storage up!
You won't be running encrypted anymore, and encryption can be re-enabled in Settings > Security.
Click to expand...
Click to collapse
so if flash the dm-verity and format userdata to remove encryption, that is a one time thing right? i don't have to deal with the issues whether a custom rom or a kernel is compatible?
Spasticdroid said:
Nice useless garbage to fill your post count.
I've spent the entire day dealing with the similar situation trying to get Magisk to work properly, and ended up removing the encryption.
TWRP 3.0.4-0 and newer may fix the issue now, but if it doesn't, either flash the disable forced encryption zip using the Toolkit, or the one from the TWRP thread, or flash a custom kernel which disables it, like ElementalX or blu_spark, all located in the Android Development sub-forum. I don't use custom ROMs so I won't know if they disable it in theirs. Read and ask them about it.
Then using a PC and fastboot, run "fastboot format userdata" then "fastboot reboot". This will WIPE YOUR DATA so back everything on internal storage up!
You won't be running encrypted anymore, and encryption can be re-enabled in Settings > Security.
Click to expand...
Click to collapse
Thanks for elaboration to avoid encryption but once u r caught into encryption, I think there is no way to decrypt but wiping data which is painful..
I m so still confused about the decryption password..
I have never registered any password for encryption
Sent from my ONEPLUS A3003 using Tapatalk
lpiratel said:
so if flash the dm-verity and format userdata to remove encryption, that is a one time thing right? i don't have to deal with the issues whether a custom rom or a kernel is compatible?
Click to expand...
Click to collapse
Yes. Flashing it once, followed by formatting via fastboot will remove encryption, and that's all you'll have to do.
As for Roms and kernels, as long as the devs have it disabled, you are fine. From a quick lookup on GitHub, ROMs here such as Official Resurrection Remix, Unofficial Unified LineageOS, and Unofficial CM have it disabled. The kernels listed in my other post have it disabled too.
ayyan84 said:
Thanks for elaboration to avoid encryption but once u r caught into encryption, I think there is no way to decrypt but wiping data which is painful..
I m so still confused about the decryption password..
I have never registered any password for encryption
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Well, you can't lock a door without a key, and if no key is made by you the system will have to use a default key created the the encryption libraries, and this is the reason recovery should use the ROMs encryption libraries both for using the correct encryption certificate and default encryption key if the user didn't enter one.
The default encryption key and certificate difference between 3.x, 4.x and other ROMs is the reason for the confusing situation on this phone, and as long as this is the case, my phone will stay unencrypted. ?
Spasticdroid said:
Yes. Flashing it once, followed by formatting via fastboot will remove encryption, and that's all you'll have to do.
As for Roms and kernels, as long as the devs have it disabled, you are fine. From a quick lookup on GitHub, ROMs here such as Official Resurrection Remix, Unofficial Unified LineageOS, and Unofficial CM have it disabled. The kernels listed in my other post have it disabled too.
Click to expand...
Click to collapse
thanks, that's really answer my question and confusion after reading other posts.

do i need to install dm verity if I'm installing custom rom

do i need to install dm verity if I'm installing custom rom
No
sakumaxp said:
No
Click to expand...
Click to collapse
So i just unlock bootloader, install twrp and boot it, and just do a full wipe then install my rom. So dm verity is for oos only?
I mean DM verity doesn't do much really, it's just an extra push of the power button or extra 5 seconds.
You really should learn a little more before diving down the rabbit hole. You'll save yourself some trouble (and probably some money too) if you learn what it is you're doing before you make a mistake and break your phone.
DM-verity is a security feature implemented by Google to verify the integrity of the system before it allows the device to boot. While it's a little more complicated than that, that's dm-verity in a nutshell. The reason Google implemented dm-verity is because of Android Pay. If dm-verity is triggered, then it may allow a device to boot, but it will disable Android Pay among other things for security reasons.
HampTheToker said:
You really should learn a little more before diving down the rabbit hole. You'll save yourself some trouble (and probably some money too) if you learn what it is you're doing before you make a mistake and break your phone.
DM-verity is a security feature implemented by Google to verify the integrity of the system before it allows the device to boot. While it's a little more complicated than that, that's dm-verity in a nutshell. The reason Google implemented dm-verity is because of Android Pay. If dm-verity is triggered, then it may allow a device to boot, but it will disable Android Pay among other things for security reasons.
Click to expand...
Click to collapse
I just want to flash a bunch of roms when my phone gets delivered, but before flashing my first rom should i flash the dm verity zip? or do you only flash that zip with oos.
Rebel7022 said:
I just want to flash a bunch of roms when my phone gets delivered, but before flashing my first rom should i flash the dm verity zip? or do you only flash that zip with oos.
Click to expand...
Click to collapse
Like I said, do some reading. There are more than a couple threads dealing with dm-verity in the Guides, News, and Discussion subforum. You don't have to flash anything to do with dm-verity in order to flash roms.
I promise you, eventually you'll do something you shouldn't if you don't educate yourself and familiarize yourself with these things. Save yourself the trouble and read, read, read!!! If you still have questions, then ask. You'll get better responses if you at least take the time to understand these things just a little bit.
HampTheToker said:
Like I said, do some reading. There are more than a couple threads dealing with dm-verity in the Guides, News, and Discussion subforum. You don't have to flash anything to do with dm-verity in order to flash roms.
I promise you, eventually you'll do something you shouldn't if you don't educate yourself and familiarize yourself with these things. Save yourself the trouble and read, read, read!!! If you still have questions, then ask. You'll get better responses if you at least take the time to understand these things just a little bit.
Click to expand...
Click to collapse
I've been reading pages of forums for two days now, I'm coming from a oneplus two, I like to flash roms allot. I'm trying to educate my self. So i install twrp and my rom and forget dm verity? So if I never plan to run oxygen I never have to worry about dm verity? thanks for your help,
You don't have to worry about it all, really. Unless you use Android Pay, then ignore it.
Install dm-verity and download more ram.
Sent from my OnePlus 3T using XDA Labs
dustin_b said:
Install dm-verity and download more ram.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
how do you download more ram?
dude, just get yourself an iphone.. you've missed the boat.. roflmao
Apparently, you guys forgot how awkward you were when you first started rooting your phones. Give the noobie a break.
Sent from my ONEPLUS A3000 using Tapatalk
Jr173 said:
dude, just get yourself an iphone.. you've missed the boat.. roflmao
Click to expand...
Click to collapse
Bro I'm not a noob I just want to know can i skip installing the dm verity zip if I'm gonna install a custom rom as soon as I can boot twrp for the fist time, or do i install that dm verity zip and then install custom rom? I'm waiting for my phone in the mail. I'm not a noob don't ever call me that again . lol I'm just playing.. lol :fingers-crossed:
Rebel7022 said:
I've been reading pages of forums for two days now, I'm coming from a oneplus two, I like to flash roms allot. I'm trying to educate my self. So i install twrp and my rom and forget dm verity? So if I never plan to run oxygen I never have to worry about dm verity? thanks for your help,
Click to expand...
Click to collapse
And also buy yourself an otg cable and a USB flash drive in case your get encrypted and have to wipe your full system like, at least you'll have a back up or firmware you can flash
sakumaxp said:
And also buy yourself an otg cable and a USB flash drive in case your get encrypted and have to wipe your full system like, at least you'll have a back up or firmware you can flash
Click to expand...
Click to collapse
You can backup over MTP on your computer with TWRP 3.1.0-1. Much more convenient IMO.

Installing LineageOS and dm-verity

Hi everybody. I need some help to understand what will happen on my 3T if I'm going to flash LineageOS.
In the past I've flashed different ROMS on my OPO, no problem at all. Now, I read there is this thing called dm-verity on Oneplus 3/3T. I currently have the last BETA but I've never flashed unofficial ROMS on my device.
What will happen if I flash TWRP and then LineageOS +gapps? Will this trigger dm-verity?
And what if I come back to official OS?
Thanks for helping
Steelstar said:
Hi everybody. I need some help to understand what will happen on my 3T if I'm going to flash LineageOS.
In the past I've flashed different ROMS on my OPO, no problem at all. Now, I read there is this thing called dm-verity on Oneplus 3/3T. I currently have the last BETA but I've never flashed unofficial ROMS on my device.
What will happen if I flash TWRP and then LineageOS +gapps? Will this trigger dm-verity?
And what if I come back to official OS?
Thanks for helping
Click to expand...
Click to collapse
You won't trigger dm-verity if you flash LineageOS.
Getting back to stock OS without triggering dm-verity is fairly straightforward.
And, if you do trigger it, this thread will show you how to get rid of it: https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
Sent from my OnePlus3T using XDA Labs
BillGoss said:
You won't trigger dm-verity if you flash LineageOS.
Getting back to stock OS without triggering dm-verity is fairly straightforward.
And, if you do trigger it, this thread will show you how to get rid of it: https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I also have a similar problem
I want to flash Nitrogen OS but do not want to root. Will flashing the ROM trigger dm-verity?
ahmedbatty said:
I also have a similar problem
I want to flash Nitrogen OS but do not want to root. Will flashing the ROM trigger dm-verity?
Click to expand...
Click to collapse
No it won't. No custom ROM triggers dm-verity.
Sent from my OnePlus3T using XDA Labs
I think most folks make a much bigger deal about dm-verity than they should. Even if you trigger dm-verity, all that means is a second warning screen after the bootloader unlocked warning screen, which only appears when you power-on or reboot the phone. Just wait 5 seconds, or press the power button to bypass either warning screen.
Dm-verity warning screen, you can make go away (never appear) as suggested above. The bootloader unlocked warning screen is mandatory (no way to defeat it) as long as the bootloader is unlocked. And if you want to run the phone modified at all (TWRP, root, custom ROM) you need to leave the bootloader unlocked.
Honestly, I've known how to remove dm-verity from the beginning (when I got this phone), but never bothered doing it.

Categories

Resources