[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]

[Zackptg5]

Thanks for the reply..by the way i found the solution by myself. As your patch changes the forcencrypt flag to encryptable..what i did is i removed the whole text 'forceencrypt=footer' and changed it to 'check'..i just applied this change to vendor fstab .qcom....voila camera and flashlight is working now...thanks for the patch anyway

Interesting. My OP5T has the check flag in addition to the forceencrypt=ice flag so if you just remove the forceencrypt=footer completely (and the ',' next to it if needed), does it still work?
Maybe it's a bug with vold or something

If it works, I can add an option to completely remove the flag rather than setting to encryptable. I'm also assuming that you can't encrypt at all now with the flag removed?

 

[rakesh0kumar]

Interesting. My OP5T has the check flag in addition to the forceencrypt=ice flag so if you just remove the forceencrypt=footer completely (and the ',' next to it if needed), does it still work?
Maybe it's a bug with vold or something

If it works, I can add an option to completely remove the flag rather than setting to encryptable. I'm also assuming that you can't encrypt at all now with the flag removed?

i didnt had an an additional 'check' so i additionaly added it..anyway it worked for me..it needs to be confirmed by someone else with the same problem, then you can add an option on your patch to remove it

 

[sonic997]

May i have the changelog for no-verity-opt-encrypt-6.1 versus 6.0 ?

Since my S7 updated to the lastest version of ESG5 bootloader, it seems cannot boot after flashed TWRP...
even I flashed no-verity-opt-encrypt-6.0 in TWRP.

I just also wonder how to gain the Magisk root for this version of my S7

twrp-3.3.1-0-herolte

AP_G930FXXS5ESG5_CL14843133_QB24881129_REV00_user_ low_ship_meta.tar
BL_G930FXXS5ESG5_CL14843133_QB24881129_REV00_user_ low_ship.tar
CP_G930FXXS5ESG5_CP13334970_CL14843133_QB24881129_ REV00_user_low_ship.tar
CSC_OZS_G930FOZS5ESG5_CL14843133_QB24881129_REV00_ user_low_ship.tar

 

[Mervingio]

I don't think this is an issue on A/B partitions. My OP6 with A/B partitioning had been decrypted just fine.

im not expert but this partitions things Google fu***ed more Android no need to have two damn partitions

 

[Zackptg5]

May i have the changelog for no-verity-opt-encrypt-6.1 versus 6.0 ?

Since my S7 updated to the lastest version of ESG5 bootloader, it seems cannot boot after flashed TWRP...
even I flashed no-verity-opt-encrypt-6.0 in TWRP.

I just also wonder how to gain the Magisk root for this version of my S7

twrp-3.3.1-0-herolte

AP_G930FXXS5ESG5_CL14843133_QB24881129_REV00_user_ low_ship_meta.tar
BL_G930FXXS5ESG5_CL14843133_QB24881129_REV00_user_ low_ship.tar
CP_G930FXXS5ESG5_CP13334970_CL14843133_QB24881129_ REV00_user_low_ship.tar
CSC_OZS_G930FOZS5ESG5_CL14843133_QB24881129_REV00_ user_low_ship.tar

This zip is completely different from the one you mention (which is also by different ppl). I explained what makes this zip unique in the first post

 

[GuestD2559]

im not expert but this partitions things Google fu***ed more Android no need to have two damn partitions

Yes A/B partitions have mixed opinions among our community. But to the general public, the benefits of A/B partitioning scheme is good.

 

[Zackptg5]

i didnt had an an additional 'check' so i additionaly added it..anyway it worked for me..it needs to be confirmed by someone else with the same problem, then you can add an option on your patch to remove it

If you remove the check flag, do the camera/flashlight/whatever problems you were having return?

 

[rakesh0kumar]

If you remove the check flag, do the camera/flashlight/whatever problems you were having return?

Nothing changed by removing ',clear' everything is working fine.. I don't know why I added that ?

 

[sonic997]

This zip is completely different from the one you mention (which is also by different ppl). I explained what makes this zip unique in the first post

I afraid that I didnt catch your meaning. Which zip i am different? thanks

 

[rafaelsarilho]

Good afternoon!
I have a problem.
I installed rom Pixel Experience 10 on my Xiaomi Mi 8, on TWRP installation, I flashed the ROM ZIP and DM-Verity ZIP (filename Disable_Dm-Verity_ForceEncrypt_08.18.2019).
After the installation, I tried to downgrade installing MIUI 10 (Android 9) by TWRP, it worked, but I am unable to configure a pin or register my fingerprint on the previous Android, when I open the configuration screen, there is the force- close
From what I've seen, I need to change the file name to get back to the default settings, but I don't understand that much.
Does anyone know how to fix this?
Sorry for my bad english.

 

[Zackptg5]

Nothing changed by removing ',clear' everything is working fine.. I don't know why I added that

Can you try this test build with your original fstabs? Should remove entries now rather than change to encryptable. I'm also curious if you can still encrypt afterwards or if that capability is gone now

Edit: Removed build

 

[Zackptg5]

@rakesh0kumar

Try this build (Updated ak3 and magisk tools stuff)

 

[rakesh0kumar]

@rakesh0kumar

Try this build (Updated ak3 and magisk tools stuff)

Working as expected, there is neither any encryption nor any camera or flashlight related problem. ?

 

[Zackptg5]

Working as expected, there is neither any encryption nor any camera or flashlight related problem. ?

Awesome! Can you encrypt in security settings if you want to or does that not work?

 

[Pupet_Master]

Hey sorry but i need a little of more info.
If i flash it after i flash my ROM, would it disable decryption?

---------- Post added at 20:38 ---------- Previous post was at 20:38 ----------

Hey sorry but i need a little of more info.
If i flash it after i flash my ROM, would it disable decryption?

 

[kidlerek]

It should be work with motorola g6? I flashed it by twrp and dm-verity message still appear .... I have Android 9.0 and pps29.55-37-4-3 compilation. I tried 10.01.2019 version and 08.18.2019.

 

[People11]

does it work on Android Q ?
You know we cant mount system as RW on Android Q

 

[adrianogoes]

It should be work with motorola g6? I flashed it by twrp and dm-verity message still appear .... I have Android 9.0 and pps29.55-37-4-3 compilation. I tried 10.01.2019 version and 08.18.2019.

Hi, I'm with the same version as you and it's all working great.

What I did?
- Using RSD Lite, I flashed stock using flashfile.xml (because servicefile.xml does not erase everything);
- Wait for the first boot to occur (it will take a while) and power off the device when the first setup dialog appear;
- Boot to bootloader (VOL - and POWER)
- Don't flash TWRP (use 3.3.1.0 version) because it can cause you problems. Instead, boot with TWRP (use once with fastboot boot twrp.img);
- Hit cancel when prompted for password (it will take a while for the dialog to appear);
- Format DATA (it is different from WIPE) typing yes when needed;
- Reboot to bootloader and boot with TWRP again (fastboot boot twrp.img);
- Format DATA again typing yes when needed;
- Reboot to bootloader and boot with TWRP again;
- Flash Magisk (use the latest beta 19.4);
- Flash Universal DM Verity (use the latest 08.18 version);
- WIPE Dalvik, Cache and Internal Memory (make sure to delete Android folders in your external SD card).

Best of luck!

 

[Zackptg5]

New build is here! It's the same as the last test build so changelog:
Remove entries rather than replace them (fixes weird issues with flashlight and stuff on some devices oddly enough)
Update to latest AK3
Update to latest magiskboot/policy binaries
Add kernel cmdline patches for some android 10 roms

 

[Mervingio]

Hi, I'm with the same version as you and it's all working great.

What I did?
- Using RSD Lite, I flashed stock using flashfile.xml (because servicefile.xml does not erase everything);
- Wait for the first boot to occur (it will take a while) and power off the device when the first setup dialog appear;
- Boot to bootloader (VOL - and POWER)
- Don't flash TWRP (use 3.3.1.0 version) because it can cause you problems. Instead, boot with TWRP (use once with fastboot boot twrp.img);
- Hit cancel when prompted for password (it will take a while for the dialog to appear);
- Format DATA (it is different from WIPE) typing yes when needed;
- Reboot to bootloader and boot with TWRP again (fastboot boot twrp.img);
- Format DATA again typing yes when needed;
- Reboot to bootloader and boot with TWRP again;
- Flash Magisk (use the latest beta 19.4);
- Flash Universal DM Verity (use the latest 08.18 version);
- WIPE Dalvik, Cache and Internal Memory (make sure to delete Android folders in your external SD card).

Best of luck!

OP 6T?