Database Develop

dm-verity related question, issue with custom recovery?

Hi,
I got a new OP3T, I wanted to root the phone and install custom ROM on it. After searching on internet I came to know the device has dm-verity feature which may cause issue once I flash custom recovery.
I wonder if I install TWRP, and supersu/root but skip dm-verity and keep the phone encrypted will this action prevent me to boot into system (note that I'm currently on Oxygen OS 4.1.6) ?
Thanks.

Most custom ROMs/kernels and root solutions will disable dm-verity and forced encryption. You can still keep your device encrypted even though the forced encryption have been disabled.

Didgeridoohan said:
Most custom ROMs/kernels and root solutions will disable dm-verity and forced encryption. You can still keep your device encrypted even though the forced encryption has been disabled.
Click to expand...
Click to collapse
Thanks.

Swipe to allow modifications. TWRP 8.0 OOS5

Hi guys,
I have flashed Oxygen OS 5 onto my OnePlus3T and am rooted with Magisk.
Everything is working fine however when I boot into TWRP I get a message to keep system read only and swipe to allow modifications.
My understanding is that if I swipe to allow modifications then I won't be able to boot Oxygen OS5, and I read a guide which said to flash a dm-verity and forced encryption disabler zip.
I do not want to loose what is on my device so I am worried that if I swipe to allow modifications then I will be forced to format data on my device.
How can I allow modifications on my device but not be forced to format data?
Thanks

If you've already flashed Magisk, then it shouldn't be problem as the Magisk zip will disable dm-verity anyways. If you're really worried, you can swipe to allow modifications, then dirty flash OOS 5.0 and Magisk in the same session before rebooting.

Anova's Origin said:
If you've already flashed Magisk, then it shouldn't be problem as the Magisk zip will disable dm-verity anyways. If you're really worried, you can swipe to allow modifications, then dirty flash OOS 5.0 and Magisk in the same session before rebooting.
Click to expand...
Click to collapse
Thats what I thought so im confused why im getting the message in TWRP.
So if I swipe to allow modifications and the device doesn't boot I can go back to TWRP and dirty flash or once I allow to boot and it fails then i'll loose all data?

ceanth said:
Thats what I thought so im confused why im getting the message in TWRP.
So if I swipe to allow modifications and the device doesn't boot I can go back to TWRP and dirty flash or once I allow to boot and it fails then i'll loose all data?
Click to expand...
Click to collapse
If you swipe, dirty flash ROM + Magisk, then reboot and dm-verity prevents you from booting, then it means you've tripped it before. In that case, flash an old version of the bootloader (OOS 4.0 or earlier), manually disable and re-enable dm-verity through fastboot, and dirty flash ROM + Magisk again. There's a guide on how to do it somewhere in the forums. Either way, regardless if you trip dm-verity or not, it shouldn't delete any of your data.

Dm verity triggered oxygen OS 5.0.0

I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.

Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.

do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?

przemcio510 said:
Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.
Click to expand...
Click to collapse
I cant find the proper files. Can you please link me a thread from which i can follow the step and find the files.

Bradl79 said:
do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?
Click to expand...
Click to collapse
Yes

FOLLOW THIS GUIDE TO DISABLE DM-VERITY
READ POST 2 IN OP, I HAVE ALSO DESABLED DM-VERITY FOLOOWING THE GUIDE BELOW:
You will need to reinstall custom ROM+gapps package if you are using custom ROM but if your are using official oxygen OS or oxygenOS based OS like theOne3t, you will not need to reinstall the full ROM at the end of process.
Have a look and carefully proceed. It works..........
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748

usually happens when u install stock OxygenOS without root or no_dmverity, u can install 4.0.2 fw via twrp and go to fastboot and type via cmd
Code:
fastboot oem enable_dm_verity
then u can reflash current fw of what u r on.

malikahmed205 said:
I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.
Click to expand...
Click to collapse
dm-verity should not (in itself) prevent the update from installing. I have dm-verity tripped (warning screen on boot) and have updated many times (maybe 5-6 updates) with no problems at all. I suspect something else is going on. What version TWRP, and how big is the update file?
When you try to update, how are you doing that, following the notification when the phone is booted to OS? Or are you in TWRP, and try to flash the update?

This happened to me as well when trying to root.
If you are getting warning that dm-verity is not enforcing, then see this thread: https://forum.xda-developers.com/on...e-red-warning-dm-verity-t3727959/post75022331
I also had to use the latest version of Magisk (15.3) for rooting to work properly.
Sent from my OnePlus3T using XDA Labs

Encryption on AOSP

Hi,
as I couldn't find an answer, here is my question.
Is it possible to encrypt a device with AOSP? And how?
Thanks

Yes, install miui fastboot Rom and wipe data, then flash the desired aosp. If stated in the thread, wipe system too.

I used to flash with TWR. Does it make a difference?
Right now I'm on Xiaomi.eu Beta 9.8.1& encrypted.
When I wipe data and flash havoc for example, it does not work. The Rom does not boot. Are there any additional steps necessary?

rum0s said:
I used to flash with TWR. Does it make a difference?
Right now I'm on Xiaomi.eu Beta 9.8.1& encrypted.
When I wipe data and flash havoc for example, it does not work. The Rom does not boot. Are there any additional steps necessary?
Click to expand...
Click to collapse
If your data is encrypted you must do format data before you install another rom. There is a difference between wipe data and format data.

mar.ur said:
If your data is encrypted you must do format data before you install another rom. There is a difference between wipe data and format data.
Click to expand...
Click to collapse
Thats right, but how do I keep the encryption or encrypt again? Because when I start the encryption from within the Rom settings in any AOSP Rom, it does not work.

rum0s said:
Thats right, but how do I keep the encryption or encrypt again? Because when I start the encryption from within the Rom settings in any AOSP Rom, it does not work.
Click to expand...
Click to collapse
You can use LOS or AOSIP if you wont to keep encryption.

OK, but in LOS didn't work either. After starting encryption from rom settings it took a longer time voting after until a message occured that system UI isn't responding. After that the screen turned black.

rum0s said:
OK, but in LOS didn't work either. After starting encryption from rom settings it took a longer time voting after until a message occured that system UI isn't responding. After that the screen turned black.
Click to expand...
Click to collapse
You have something wrong. You don't have to encrypt manually. It is encrypted already. Do you flash disable force encryption?

mar.ur said:
You have something wrong. You don't have to encrypt manually. It is encrypted already. Do you flash disable force encryption?
Click to expand...
Click to collapse
Thanks, that's interesting!
Here the steps I took:
- Wiping everything (data, system, dalvik, cache)
- Format data
- reboot
- installing the rom (gapps, magisk)
- no dm-verity and no disable-force-encryption
EDIT: I'm one step further. I used Orange Fox Recovery and disabled Disable DM-Verity and Disable ForceEncryption in the MIUI OTA Menu.
Now some AOSP Roms are encrypted after first boot, except for HAVOC - seems not to be supported right now?!

rum0s said:
Thanks, that's interesting!
Here the steps I took:
- Wiping everything (data, system, dalvik, cache)
- Format data
- reboot
- installing the rom (gapps, magisk)
- no dm-verity and no disable-force-encryption
EDIT: I'm one step further. I used Orange Fox Recovery and disabled Disable DM-Verity and Disable ForceEncryption in the MIUI OTA Menu.
Now some AOSP Roms are encrypted after first boot, except for HAVOC - seems not to be supported right now?!
Click to expand...
Click to collapse
Most of these heavily customizable roms are ugly anyways, I'd rather use GravityBox Xposed Module for customizations.

rum0s said:
Now some AOSP Roms are encrypted after first boot, except for HAVOC - seems not to be supported right now?!
Click to expand...
Click to collapse
Yes, I was trying to encrypt Havoc and PE and failed. Idk wether Syberia support encryption. I just stoped to switching between roms and stayed with LOS. It supports encryption and selinux is enforcing.

Ok thanks guys for your help!
I'm thinking about staying on miui beta or try one of the lighter roms.

Question How to flash a Android 12 ROM without decryption problem?

I've been struggling to flash Android 12 without my internal storage to be unaccessible by TWRP... I simply can't decrypt my data and the only way to fix it is to format data and revert back to a Android 11 ROM.
Did anyone manage to flash Android 12 successfully? How?

Well I gotta tell you sadly, decryption does not work for any Android 12 system currently. So you gotta have to live with it, until we get decryption support.
And don't try to fiddle with disabling encryption, I did it and I quickly regretted it.
Also, you always have to format data after flashing a ROM to remove encryption, except if you update your current ROM.

ADB Sideload is the answer.
If you have TWRP installed already then as you know when you go into recovery you cant see any data. User ADB Sideload instead and it will flash it the same way

KashMiester said:
ADB Sideload is the answer.
If you have TWRP installed already then as you know when you go into recovery you cant see any data. User ADB Sideload instead and it will flash it the same way
Click to expand...
Click to collapse
ADB sideload isn't the answer, because that's already what I use to flash a Android 12 based ROM. Doesn't change that TWRP can't decrypt data

meirioon said:
ADB sideload isn't the answer, because that's already what I use to flash a Android 12 based ROM. Doesn't change that TWRP can't decrypt data
Click to expand...
Click to collapse
That is because their no recovery that will decrypt A12, just not possible yet. Sideload is the way for now, it works fine. Decryption isn't available yet and hopefully someone cracks it soon

Not towards achieving decryption, however after flashing A12 ROM, and clicking on format data, I get numerous errors with TWRP. Any solution? Is it related to recovery or some issue with data partition? Thanks!

Many people have issues with TWRP. Flash Orangefox recovery in TWRP, boot into it and try.
sujju said:
Not towards achieving decryption, however after flashing A12 ROM, and clicking on format data, I get numerous errors with TWRP. Any solution? Is it related to recovery or some issue with data partition? Thanks!
Click to expand...
Click to collapse

I'm having the same issue but how can I revert back to a Android 11 ROM if my internal storage is inaccessible?

I did it just by flashing Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip after flashing the rom.
You can search for this file in the web.

bizzaro87 said:
I did it just by flashing Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip after flashing the rom.
You can search for this file in the web.
Click to expand...
Click to collapse
Does NOT work at all on Android 12 roms having just tried it

try these scripts

Anybody try these scripts ^? Just sideload them?

I used disable dm verity force encrypt and a12 worked without a problem, I can access image and more! My recovery is orangefox. It worked really great with a12. No problem until now!

patricktech said:
I used disable dm verity force encrypt and a12 worked without a problem, I can access image and more! My recovery is orangefox. It worked really great with a12. No problem until now!
Click to expand...
Click to collapse
@meirioon
+1
For OSS attached

I used disable dm verity force encrypt
Click to expand...
Click to collapse
At which installation stage did you flash it under OrangeFox? Before or after A12 installation?

akapune said:
At which installation stage did you flash it under OrangeFox? Before or after A12 installation?
Click to expand...
Click to collapse
After A12 and magisk.
Directly after DfE don't forget to format data.

Laptapper said:
After A12 and magisk.
Directly after DfE don't forget to format data.
Click to expand...
Click to collapse
that means, that you don't update your rom to a new version without loosing data.
you are always doing a clean install.
or am I wrong?

gorillaz_gr said:
that means, that you don't update your rom to a new version without loosing data.
you are always doing a clean install.
or am I wrong?
Click to expand...
Click to collapse
No, if you're decrypted with DFE once and formated with yes, you can flash new ROM and DFE without formating. Means dirty install without loosing internal data. Or you make clean by only wiping data and in this case also your internal SD stay as before without loosing your personal files.

Laptapper said:
No, if you're decrypted with DFE once and formated with yes, you can flash new ROM and DFE without formating.
Click to expand...
Click to collapse
Do I have to flash DFE again after each OTA update?

akapune said:
Do I have to flash DFE again after each OTA update?
Click to expand...
Click to collapse
Yes but don't format