yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ne0t:
and which partition do I need to backup incase of bootloop.

Does this zip file (Disable_Dm-Verity_08.02.2019.zip) works on encrypted phone?, I just want to disable DM-Verity on my phone, I want to keep the encryption.
[Android Software Development] zzzhead:
Could you share more details on this, for my own understanding?
[Android Software Development] Zackptg5:
The OP answers both of those questions
[Android Software Development] ZeroKool76:
If you decrypt the 6T, your security features, like password/pin/FP etc. will not work.
[Android Software Development] H4X0R46:
This zip should be able to remove the encryption flag on newer A/B devices that use an fstab file in /vendor right? Specifically a OnePlus 7 Pro in mind here.
[Android Software Development] zzzhead:
Based on lots of searching, that seems to be the case.

I'm not quite clear though on the technical level, could you elaborate a little on this?
[Android Software Development] H4X0R46:
I have heard this too! I had a 6T before my 7 Pro, and now I'm wondering if the same is true for the 7 Pro? Anyone here with a 7 Pro have insight on this?
[Android Software Development] thoiloidainhan:
If you are decrypted with a custom recovery like twrp, you've already given up on pin/pass screenlock because anyone can delete your pin/pass in twrp. So it's not like OnePlus is crippling the device any further if you choose the decrypted path. I don't know how severe the "not working" fingerprint is tho, is it completely disabled on decrypted system or u can still use your fingerprint to unlock phone?
[Android Software Development] Namolas:
You can still add fingerprints, pins, patterns etc to securely lock your OnePlus 7 Pro when its in a booted state. The only difference is it no longer asks for a pattern/pin when you boot to TWRP.
[Android Software Development] thoiloidainhan:
Thx so the situation hasn't changed since op5. The other user made it like things have changed for the worse with decryption lol. Of course everyone knows decryption will make your device less secure
[Android Software Development] ZeroKool76:
Nah, it's only the 6T users they fukd over. The 6 and pro decrypt fine. The funny part is, people forget things like that and continue to buy from them anyways. SMH
[Android Software Development] H4X0R46:
Thanks! Yeah I had the 6T before this 7 Pro and that's what kept me from decrypting that phone. Well I'm gonna try that then! I like being able to try roms and just scrap them if I don't like em, encryption makes that a headache.
[Android Software Development] Zackptg5:
Dropped an update:

Update to latest AK3 - huge shoutout to [MENTION=4544860]osm0sis[/MENTION] for figuring the mounting stuff out (the variance between TWRP's made this way more complicated than it should be)

Final fix for system_root devices
[Android Software Development] DEVILOPS 007:
Sorry about the delay, phone was being weird. I flashed everything as normal and copied logs to sdcard.
[Android Software Development] Zackptg5:
Hmm, log looks fine except it didn't detect any fstabs in vendor. Do you have any in vendor/etc?
[Android Software Development] DEVILOPS 007:
Alright, I may be stupid [MENTION=6037748]Zackptg5[/MENTION]. If the above log had nothing about the fail then this one must.
[Android Software Development] DEVILOPS 007:
No file or folder called fstab in that directory.
[Android Software Development] Zackptg5:
I mean like an fstab file. For example, fstab.qcom. Regardless, I'm not seeing any errors in either log so I'm not sure what the problem is. Have you tried just flashing the rom and this mod without anything else?
[Android Software Development] DEVILOPS 007:
Yeah same problem. Excuse my noobiness but I'm still unclear on what exactly you mean by the fstab file. Still not sure why I get this problem.
[Android Software Development] Amanpreetsingh:
It will work on miui ??
[Android Software Development] vickyw288:
THE IMEI IS LOST after installing this zip

can any one fix it?:(
[Android Software Development] Zackptg5:
So i've recently encountered a few oreo roms where the fstabs are located in the ramdisk rather than in vendor/etc. So naturally, I added their detection and modification to this zip. Version 1.2 is up at the download link!
[Android Software Development] DEVILOPS 007:
Ooh, I wonder if that will fix my problem due to me having no fstab in vendor/etc. Thank you?
[Android Software Development] DEVILOPS 007:
Hey [MENTION=6037748]Zackptg5[/MENTION] It works amazingly on OmniDragon OP5T. Thank you for your hard work. I've been hoping you'd figure out the problem with some devices and roms. May I ask though, can I untick the box in the screenshot below and if so what does it really do? I've never really thought about it until now:laugh:
[Android Software Development] Zackptg5:
Haha, that's the exact rom I had in mind and tested this on. The check boxes do nothing. In the future, when you flash again, flash this zip before magisk. The .magisk file it creates tells magisk to not check those boxes

Edit: updated the OP with better instructions
[Android Software Development] anupritaisno1:
But I love my verity and forced encryption sire!

Anyway can I know what advantages this has over the already existent bypass methods provided by SuperSU, magisk as well as jcadduono's bypasser?

---------- Post added at 06:25 ---------- Previous post was at 06:22 ----------

Also forced encryption cannot be abbreviated as "FEC"

"FEC" is a feature of dm-verity/AVB to handle errors on a verified partition. FEC means "forward error correction", not "forced encryption"
[Android Software Development] Zackptg5:
Well the OP explains it pretty well. It basically is magisk removal + jcadduono + fstab patching in ramdisk (not present in any current method as far as I know). I haven't looked into exactly what SuperSU since it hasn't been updated in a while and chainfire is gone.

Magisk patches dtb and ramdisk.cpio (but not the fstabs in it curiously, or at least not for my op5t) in the boot img

Jcadduono patches default.prop in nougat or older and vendor fstab in Oreo and newer

So my aim was to combine those and improve upon them. It also allows rootless users to run decrypted.
[Android Software Development] anupritaisno1:
Interesting. Can you also make a zip that disables disk quotas?
[Android Software Development] Zackptg5:
Maybe but I'm not too familiar with it. Why do you want it disabled?
[Android Software Development] anupritaisno1:
It wrecks up older TWRP versions and prevents downgrading to nougat

Refer https://source.android.com/devices/storage/faster-stats
[Android Software Development] janneriiki:
Is there any way to get rid of this message?

"Android System

There's an internal problem with your device. Contact your manufacturer for details."

I have tried to google for solutions but the only answer I got was that "/system/build.prop" and "/vendor/build.prop" fingerprint values do not match.

I checked fingerprint values for build.prop and they match in both /vendor and /system.

Any idea on how to just silence, block or remove that particular message?

Thanks in advance!

Device: OP6

ROM: Stock 5.1.6

Kernel: Stock

root method: Magisk 16.4
[Android Software Development] Zackptg5:
Flash the zip from here: https://xdaforums.com/nexus-9/development/zip-universal-build-fingerprint-fix-t3173557
[Android Software Development] Zackptg5:
Fair enough, I'll whip one up later today and rename the verity fec zip to something else. Just fstab patching for this right?
[Android Software Development] Sandy._.12:
OK, from what I could make out of the OP is that you have to wipe data before flashing the zip. Problem is I can't decrypt my data and therefore can't mount it. When I try to wipe it from twrp, it says can't mount data and the process fails. I was on Havoc ROM with a working pin, when suddenly my device stopped accepting my pin in os as well as in twrp. Any advice? BTW, I'm on OnePlus 7 pro.
[Android Software Development] Namolas:
Been there. I usually MSM tool HERE back to stock and be done with it. But I have seen it said that after 3 or 4 times trying to wipe in TWRP like you are already doing and it will finally work. Not verified by me but it may work.

Does changing slots yield any better results? Its been several weeks since the same happened to me on HavocOS OP7P so I'm trying to recall what options I tried then...

Alternatively you could boot the stock recovery HERE and wipe everything from there. :good:

Or you could fastboot erase userdata.

Or flash-all.bat the stock fastboot rom posted in the OP7P section HERE.

You have several options. :good:
[Android Software Development] Zackptg5:
Are you formatting data? It's different from wiping. There should be a button in advanced wipe that says format data
[Android Software Development] Sandy._.12:
Yes, I'm talking about the button, where it asks you to type "yes" to continue. It used to give me error 1.

I don't know why and how but the 10th time (maybe) worked as a charm, I was able to format it!

Thank you all for the help.
[Android Software Development] fede91it:
Doesn't work on Bq Aquaris X Pro with TWRP and LineageOS 16 with Magisk
[Android Software Development] ScorpiusDLord:
Thanks .
[Android Software Development] H4X0R46:
Do you still have to remove all passwords and security before making a TWRP backup on a decrypted 7 Pro?
[Android Software Development] Namolas:
You still have to remove it. Or delete locksetting.db etc after restoring.
[Android Software Development] sonic997:
I want to have root for my S7 G930F

Could I use custom kernel and magisk for successful encryption from the official system setting in android 7.0 ?

Or...could I use stock kernel and magisk for successful encryption from the official system setting in android 7.0 ?

The reason for doing so is to hope for root and then successfully encrypt the device.

Thanks~
[Android Software Development] H4X0R46:
Cool thanks man! :good:
[Android Software Development] exodius48:
Download link not working
[Android Software Development] Zackptg5:
Ya, server maintenance by my hosting provider. Cpanel jacked their rates up so it's getting switched to directadmin or whatever. It should be back up later today, sorry!
[Android Software Development] WoKoschekk:
After formatting /data you get a warning by TWRP. You have to reboot recovery to mount /data correctly after formatting!
[Android Software Development] Gleanfast:
Yes
[Android Software Development] ZLYWXD:
why:confused:
[Android Software Development] abalam:
I am on custom rom encrypted. When I wanne decrypt is must I do a format data and flash OOS first, twrp and than this .zip for dycrypted? Finaly flash custom twrp dm.zip and magisk. Can give someone me advice? Tnx
[Android Software Development] amg314:
I think that most interesting part of installation log on your screenshot is invisible((

You better simply show this log in txt form.
[Android Software Development] paatha13:
That's the steps im doing all time 2 months now with the oneplus 7 pro for clean install

Format data,reboot twrp,factory reset,flash rom ,flash twrp ,flash dm verity.

Reboot again twrp

flash again rom,twrp,dm verity

Reboot twrp

flash gapps(when nedded)magisk(im using 19.4) flash dm verity.

Reboot system.

If you want to upgrade the rom you already have you follow the same guide,except don't format data/factory reset but do all the others steps and wipe dalvik at the end before reboot system.

As for restore backup rom we have already taken just don't forget before reboot system flash dm verity first.
[Android Software Development] smk513:
I have oos decrypted via disable force encrypt! (op7pro) :D

This instructions :

1. reboot to twrp, format data

2. Flash latest full OOS -> TWRP

3. reboot to recovery

4. Flash Magisk -> Disable Force Encryption

Done. flawless working.

and.. today,, following process to update

1. Flash full OOS -> twrp

2. reboot to recovery

3. Flash Magisk -> Disable Force Encryption

Done..

:crying:

Rebooted, but back to TWRP.. (my data decrypted, but moved /sdcard/0/mydata..)

Is there a problem with my process?

Any advice would be appreciated...
[Android Software Development] sga999:
[MENTION=6037748]Zackptg5[/MENTION], someone above said this:

"As for restore backup rom we have already taken just don't forget before reboot system flash dm verity first."

I have done twrp restores many times but never do the dm-verity flash first. Is that necessary? I do not seem to need it.
[Android Software Development] ltth:
Thanks! I followed your guide works without any problem. How to confirm the installation was fully installed and correct?
[Android Software Development] H4X0R46:
Is this expected to work with Android 10? Specifically OOS beta 2 for OnePlus 7 Pro?
[Android Software Development] Mervingio:
But this work on OP6T? I read somewhere that can't because OP6T can't decrypt because partitions a/b
[Android Software Development] abalam:
Op6 also a and b and that works, not?
[Android Software Development] Mervingio:
Not sure but this drive me crazy everything is wipe and die
[Android Software Development] Zackptg5:
You tell me :)

Google changed the partition layout a bit in 10. Based on what I saw, I think it should be fine but if it doesn't work, that would likely be why. If it doesn't work, can you grab a log like outlined in the OP and send me a link for the firmware you're on so I can look at the partition layout?

Does op6/6t have issues or not? I'm getting mixed messages here lol
[Android Software Development] Pvt WhoOkid:
Works fine for me. OnePlus 7 Pro.
[Android Software Development] Mervingio:
Not sure last time I flash I lost all and need be start from scratch maybe you can help us here
[Android Software Development] jahidinbedod:
[MENTION=6037748]Zackptg5[/MENTION]

magisk stable 19.4 already update

https://github.com/topjohnwu/Magisk/releases/tag/v19.4
[Android Software Development] Zackptg5:
Thanks for the heads up :)

This zip is no longer dependent on magisk. I use a custom magiskboot binary so it's independent now
[Android Software Development] H4X0R46:
That happened to me too on Android 10. Not sure if it was this zip or another factor, because people have said this works with the open beta builds for 7 Pro, but the same happened to me last time I tried to flash a beta build. Gonna try and flash the new beta build with this zip later today and I'll report what happens.

---------- Post added at 09:54 AM ---------- Previous post was at 09:53 AM ----------

Are you on open beta 1 or 2? Or stable builds?
[Android Software Development] Pvt WhoOkid:
Beta 2.
[Android Software Development] H4X0R46:
Alright, my issue is unrelated to this zip then, that's a good point in the right direction. Thanks!
[Android Software Development] rakesh0kumar:
[MENTION=6037748]Zackptg5[/MENTION] , I disabled dm-verity and force encypt using your patch..I am very thankful to you for this..but after flashing the patch my flashlight and camera and not working..I dont know what to do , any solution you can offer..?
[Android Software Development] Zackptg5:
Best to search the thread, this has been brought up many times and so far as I know, there's no way to fix it other then switch roms
[Android Software Development] ZeroKool76:
YOU CANNOT DECRYPT THE OP6T WITHOUT BREAKING SECURITY, i.e. fingerprint,pin,password and pattern will no longer unlock your device. And you can't use the password removal zip, because that will leave you on the "phone is starting" screen. Your only option is to format and allow it re encrypt your device. Hopefully this is clear enough for those who were unsure. Has nothing to do with the A/B format, since the 6 and pro decrypt with no issue. This is a big part of why I won't be buying another OP device..
[Android Software Development] Mervingio:
Thanks for this I'm thinking this too no more OP Devices OP5T no have the damn partitions a/b and you can decrypt without issue
[Android Software Development] :
I don't think this is an issue on A/B partitions. My OP6 with A/B partitioning had been decrypted just fine.
[Android Software Development] rakesh0kumar:
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
[Android Software Development] Zackptg5:
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?
[Android Software Development] rakesh0kumar:
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
[Android Software Development] 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
[Android Software Development] Mervingio:
im not expert but this partitions things Google fu***ed more Android no need to have two damn partitions
[Android Software Development] Zackptg5:
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
[Android Software Development] :
Yes A/B partitions have mixed opinions among our community. But to the general public, the benefits of A/B partitioning scheme is good.
[Android Software Development] Zackptg5:
If you remove the check flag, do the camera/flashlight/whatever problems you were having return?
[Android Software Development] rakesh0kumar:
Nothing changed by removing ',clear' everything is working fine.. I don't know why I added that ?
[Android Software Development] sonic997:
I afraid that I didnt catch your meaning. Which zip i am different? thanks
[Android Software Development] 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.
[Android Software Development] Zackptg5:
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
[Android Software Development] Zackptg5:
[MENTION=7581986]rakesh0kumar[/MENTION]

Try this build (Updated ak3 and magisk tools stuff)
[Android Software Development] rakesh0kumar:
Working as expected, there is neither any encryption nor any camera or flashlight related problem. ?
[Android Software Development] Zackptg5:
Awesome! Can you encrypt in security settings if you want to or does that not work?
[Android Software Development] 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?
[Android Software Development] 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.
[Android Software Development] People11:
does it work on Android Q ?

You know we cant mount system as RW on Android Q
[Android Software Development] adrianogoes:
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!
[Android Software Development] 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
[Android Software Development] Mervingio:
OP 6T?
[Android Software Development] DessertArbiter:
splash screen bootloop

when i flash Disable_Dm-Verity_ForceEncrypt_10.09.2019.zip on my Moto G6 (ali) on the newest firmware (August 1 security patch, PPSS29.55-37-4-3) i get stuck in a bootloop of endless splash screen followed by black screen and repeating, the last build of this zip that i know works on my phone is the May 21 build, that one works flawlessly
[Android Software Development] kidlerek:
I tried without install twrp but it doesn't help me ( https://youtu.be/6cPNUbZUgG8 )
[Android Software Development] adrianogoes:
Nope, Moto G6 (Ali) XT1925-3 (Brazil).

---------- Post added at 11:35 ---------- Previous post was at 11:32 ----------

Did you unlocked your bootloader as the first step of all?
[Android Software Development] Zackptg5:
Due to issues with the latest zip, I pulled it and restored the older version (8-18). I put the new build in the OP as a test build in the mean time until I can figure out why it's having issues with some devices. Sorry!
[Android Software Development] adrianogoes:
Hi! First of all, thank you for your work! :)

Would you help me with these questions:

- some people say that flash your zip before Magisk and it works, what do you think?

- when Magisk is updated do I have to flash your zip again?

- what issues in 10.09?

Thank you very much.
[Android Software Development] Zackptg5:
I always keep OP updated with flashing instructions (always flash this zip last)

Nope

Some devices wouldn't boot
[Android Software Development] 1Ton1886:
Once dm verity and force encrypt has been disabled using your zip, how do I re-enable dm verity and force encrypt using the flashing a zip folder method through TWRP? My device is stuck in a boot loop so I want to re-enable dm verity and force encrypt using the zip folder method through TWRP.
[Android Software Development] Zackptg5:
You need to restore your backup or reflash your rom