yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Ecthelion3:
Hi, I am using LOS 16 on a Lenovo Tab 4 Plus. Installation on this device works fine when using the Disable Force Encryption zip as last file during the flashing process. So I did the same for flashing LOS 17.1, i.e. first the LOS zip, then the gapps zip, then the Disable Force Encryption zip. But after the reboot in this case it did not reboot the system but ended up in fastboot mode. A reboot then always ends up in fastboot. Is there something different with the patched files for Android 10, so that the Disable Force Encryption zip does not work with Android 10 or so?

I could successfully revert back to Android 9 by dirty flashing LOS, gapps and the Disable Force Encryption zip and it booted nicely. FYI, installing LOS 17.1 without the Disable Force Encryption zip lets the device try to start the system, i.e. not fastboot mode, but this Lenovo device is known to need the Disable Force Encryption, otherwise the LOS start will take forever (which was also the case when I tried). So I need the Disable Force Encryption zip for installing the system, but it does not seem to work with LOS 17.1 in my case.

Any help is appreciated. Thx

---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------

Hi, I am using LOS 16 on a Lenovo Tab 4 Plus. Installation on this device works fine when using the Disable Force Encryption zip as last file during the flashing process. So I did the same for flashing LOS 17.1, i.e. first the LOS zip, then the gapps zip, then the Disable Force Encryption zip. But after the reboot in this case it did not reboot the system but ended up in fastboot mode. A reboot then always ends up in fastboot. Is there something different with the patched files for Android 10, so that the Disable Force Encryption zip does not work with Android 10 or so?

I could successfully revert back to Android 9 by dirty flashing LOS, gapps and the Disable Force Encryption zip and it booted nicely. FYI, installing LOS 17.1 without the Disable Force Encryption zip lets the device try to start the system, i.e. not fastboot mode, but this Lenovo device is known to need the Disable Force Encryption, otherwise the LOS start will take forever (which was also the case when I tried). So I need the Disable Force Encryption zip for installing the system, but it does not seem to work with LOS 17.1 in my case.

Any help is appreciated. Thx
[Android Software Development] mad4some:
+1 I have the same tablet and have just tried the same thing. And now, if I format data and boot the system again (LOS 16) the tablet just re-encrypts again......:eek:
[Android Software Development] Ecthelion3:
FYI, I just tried a clean flash using the aforementioned files, but the result is the same. After the reboot the tablet starts in fastboot mode. I would guess that it has something to do with the Universal Disable Force Encryption zip that I am flashing in the last step, because without this it does not start in fastboot but normal mode. But in this case the system shows the LOS loading animation forever and won't finish the startup, which is why I was using the Universal Disable Force Encryption zip. Installing LOS 16 using this procedure works fine, but I have no idea how to upgrade to LOS 17.1. To me it looks like the Universal Disable Force Encryption zip is patching some file, fstab, in an incorrect way, so that it gets corrupted, resulting in a "fallback" of the device into fastboot mode.

Help would still be appreciated.
[Android Software Development] hoshang.govil12:
In Custom ROM, This flashing isn't required then Why U all are flashing. Just Flash ROM and Gapps and reboot first.
[Android Software Development] Ecthelion3:
As I mentioned in my first message, for this device the Universal Disable Force Encryption zip needs to be used because otherwise the device won't boot. I tried already without the Universal Disable Force Encryption zip. It did not work.
[Android Software Development] jayant0010:
My Redmi device stopped working. Please Help!

Hey!

I own a Xiaomi Redmi 7, I Flashed TWRP into it using adb through fastboot. Then I installed the lineage OS .zip package and G-apps package followed by your DM-verity package. Then, I hit reboot on the TWRP screen. Now The lineage OS wont even boot (It used to earlier even though it would get stuck in a bootloop). I am stuck with a "Redmi by Xiaomi" screen repeating again and again. I am pretty new to this scene, I really have no clue what to do. Please help :)
[Android Software Development] matstory:
Thanks! :o
[Android Software Development] Cyberavater:
Device stucks after installing it

Hello, Device stucks after installing it, More info here; https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/issues/13

Can anyone at least suggest to me how can I manually patch my boot image?

Boot image link attached. I already tried Using Carliv Image Kitchen, but the ramdisk is empty.

Please, any help is appreciated, Thanks in advance!

https://anonfiles.com/b8t7Nf6eob/boot_img
[Android Software Development] alecxs:
check /vendor/etc/fstab.mt6763
[Android Software Development] Cyberavater:
Thanks, I was looking in the wrong direction all this time!

But here is a thing it say's here to change it to 'encryptable' while mine is already 'encryptable'

https://xdaforums.com/showpost.php?p=57223278&postcount=2

I found another one that says to "delete ",fileencryption" " which again is not available here

https://xdaforums.com/android/general/guide-how-to-remove-force-encryption-dm-t3843728

fstab.mt6763 link attached. Should I remove ",encryptable=userdata" instead?

https://anonfiles.com/h2m0197do4/fstab_mt6763

Again, thank you so much for your attention! I really appreciate it.

Also, is there any unpack and repack tool for windows for vendor.img? (I extracted the file using 7-zip and tried Carliv Image Kitchen and ASSAYYED_KITCHEN they don't seem to have support for vendor.img.)
[Android Software Development] Zackptg5:
Ya, wipe - format data
[Android Software Development] mipirakas:
Thanks i'll try in a few days :).
[Android Software Development] Zackptg5:
Zip would be enough
[Android Software Development] Amanpreetsingh:
When you tap on wipe you will see format data on the bottom of the right side. Before going to advanced wipe It will appear there. I have op5t and no issue with decryption.

I have mi a1 and it has a/b partition and there was no special zip for mi a1 to decrypt. Anybody help with that ??
[Android Software Development] radz_:
[MENTION=6037748]Zackptg5[/MENTION]

Been using this zip and everything works great!

I'm just posting this to suggest add a zip version in your thread title. V1.4 or a date of latest version.

I never knew you already had 1.4.[emoji4][emoji4]

Thanks for your work.
[Android Software Development] Zackptg5:
Since this uses magisk functions as the backbone, this zip should work fine with a/b

Done :)
[Android Software Development] ashish1989:
Thanx bro worked on my samsung j500f model
[Android Software Development] ADDICTED777:
[MENTION=6037748]Zackptg5[/MENTION]

Hey, Your zip is working flawlessly.... Awesome work brother....

Just a confusion ...

I installed it with a custom kernel... Now if i want to change to another kernel i have to flash stock kernel then... Custom kernel then this zip and atlast magisk... So, the question is :

magisk had backup the old kernel things so when i will flash magisk again after your zip... Does it restore any thing from the old one???? :confused:
[Android Software Development] Zackptg5:
Magisk will restore the backed up kernel if the boot img was already patched with magisk. So you may need to reflash this zip again after all of that. You can flash this zip as many times as you want and it won't break anything regardless
[Android Software Development] Runeza:
Hey currently i am using Asus Zenfone max pro m1

My Rom is AEX official and i already install custom kernel magisk and decrypt.zip

Can i just instal the zip in recovery mode ?

Will this zip make me bootloop ?

Thanks in advance
[Android Software Development] SteevoM:
Hi, I'm currently using a Galaxy S8+.

After I flashed the zip file, my phone's touchscreen doesn't work. Not a frozen screen, the phone itself is fine but the screen just doesn't recognize my fingers touching the screen.

Can't even reboot because, you know, you have to "press" the reboot button on screen..

But if I flash TWRP via Odin again, the touchscreen works fine but it goes back to 0mb internal storage (don't know if its "went back to 0mb" or "still 0mb" cuz I wasn't able to reboot in recovery and check).

Any help?
[Android Software Development] Sam Nakamura:
Just a suggestion, long pressing power button would force a reboot regardless of a working touch screen this way you should be able to boot to recovery by the corresponding button combination...

No need to use the touch screen really to boot to recovery!
[Android Software Development] chooks06:
To add on to [MENTION=7125933]Sam Nakamura[/MENTION].. Hardware buttons does the trick, or else, plug in a mouse or even a wireless mouse.

I'm just curious.. So how did you get to Odin download mode eventually seeing that you can't reboot?

Edit - PS I'm not familiar with Samsung anymore but if in TWRP, see c if you can mount internal storage.

If your greeted with the data is encrypted thingy when you get into TWRP, it's likely due to the Forced Encryption.

To overcome this, use the Wipe menu in TWRP and select format data option .. At the next screen, type YES..BUT DO NOTE ALL DATA IS LOST.

After that mount Data and you should see the internal storage.

I'm not responsible for your losing data or bricking your device.
[Android Software Development] SteevoM:
Oh my bad. I got confused while writing this comment. Yes I was able to go to download mode by pressing buttons you know, like vol+, bixby, and power button.

I don't know why but after flashing this zip I just couldn't go to recovery mode even with all the button pressing, it just boots into system and the touchscreen would never work.
[Android Software Development] SteevoM:
I'm just curious though, what part of this zip file could possibly mess up the touchscreen-system (or whatever its called) ?

All I did was

1. Flash Stock Rom

2. Format data in TWRP

3. Install custom rom (Renovate Ice 13.1) via TWRP

4. Flashed this DM-verity zip file via TWRP

5. Reboot, then the problem begins
[Android Software Development] chooks06:
Sorry, I just edited my post.

Would you be able to reflash TWRP? That will give you the recovery mode
[Android Software Development] SteevoM:
Yeah thats what I've been doing for like forever.

reflash TWRP and the phone would work fine, but the "internal storage 0mb" is never gonna fix.

So whenever there's a custom rom update or else that needs zip flashing, I have to do the whole [backup data -format data-install zip-restore data] procedure again.

So I've tried flashing unofficial TWRPs like codeworkz or bluspark but they both caused bootloop.

Tried a Data Mount fix from

https://xdaforums.com/galaxy-s8/sam...-mount-fix-s8-twrp-oreo-t3769254#post76036701

ㄴ also caused bootloop.

Then I found this thread, but then touchscreen issues. I'm really getting tired of this 0mb problem lol
[Android Software Development] chooks06:
I

I assume you did a clean install for the custom ROM, meaning wiping system as well?

I really can't nail down the cause for the bootloop.

When I flashed the DM verity file, I usually reboot to recovery via TWRP before proceeding with rooting.

Maybe check out the custom ROM first before going further ? Just a thought.

---------- Post added at 09:05 AM ---------- Previous post was at 08:57 AM ----------

Oh dear.. My apologies..

I guess we're both replying at the same time and hence i didn't see your reply till after I posted mine and it seemed out of sync.

I guess due to the Forced Encryption thingy, each time we install TWRP, we'll come to the screen that tells is Data is encrypted like.

Edit ... I'm running stock ROM on a cheap China phone . End of edit

If the custom ROM runs fine, and you be can root successfully, don't need to install this zip. This zip helps me if I'm rooting with Magisk. With Chainfire's Super SU, I can't get it to work.

Edit again ... Usually for custom ROM, dirty flash should do the job. However, a clean install would require going through the whole works again. Just my thoughts.
[Android Software Development] SteevoM:
Just figured out there's a way to flash zip files without using install zip feature it TWRP (adb sideload)

Well then I guess internal storage 0mb won't bother me that much after all lol.

Anyways Thanks for the help.
[Android Software Development] chooks06:
You're welcome mate..

I'm happy if I managed to help in any small way.. Was just sharing, actually.:p

Have fun and have a great week ahead!

Cheers!
[Android Software Development] alecxs:
for /data replace forcefdeorfbe= with encryptable= and delete verify flags from /system + /vendor
[Android Software Development] Cyberavater:
Thanks again for your help <3. I need your help a little bit more plz, can you recommend any unpack and repack tool for windows for vendor.img? (I extracted the file using 7-zip and tried Carliv Image Kitchen and ASSAYYED_KITCHEN they don't seem to have support for vendor.img.)

Thanks in advance.
[Android Software Development] alecxs:
this goes ot here now...

use unetbootin to install xubuntu on bootable usb flash drive

install android-tools-fsutils or android-platform-system-extras and decompress with simg2img (or with brotli + convert with sdat2img.py) into ext4 disk image. loop mount the image to any folder
[Android Software Development] Cyberavater:
So, in other words, no way to do it in windows? [Sorry for going off-topic, I'm new to this you can probably tell.]
[Android Software Development] Cyberavater:
I've Hex edited my boot.img and my device was dead, So, I would recommend anyone not to hexpatch if they don't know what they are doing.

Fixed it by flashing stock img using SP Flashtool.
[Android Software Development] Nightshadex543:
Thanks for those threads.
[Android Software Development] tecs.ottawa:
I have a Blackview BV9800 Pro and I can't figure out why disabling verity keeps also disables the touch screen. When I use the disabler, it flashes the zip just fine and then boots, but like some of the other posters on here, the phone setup doesn't work because I can't touch the buttons. A mouse or keyboard doesn't work as well. It's not frozen because the "vision settings" lights up sometimes.

I couldn't find how any of them fixed their issue and I really need to be able to back up my userdata.

Any help would be greatly appreciated!

Thanks
[Android Software Development] jahidinbedod:
[MENTION=6037748]Zackptg5[/MENTION]

latest 3/4/2020 didn't work on op5 (ext4 decrypted) custom rom paranoid android quartz 3
[Android Software Development] tpetris:
Verity oem partition

Hi guys, i'm having trouble writing to the /oem partition, i gues it's a Verity issue. Small issue description:

- I've unlocked an LG V40 EBW with LG unlock;

- Extracted boot_a, boot_b image from latest kdz ( 20f) in a Linux VM

- Installed Magisk Manager, patched boot_a with Magisk Manager

- Booted in ADB from magisk_patched.img

- Installed magisk_patched.img in Magisk Manager on slot 1

I have obtained permanent root on the stock rom. I want to keep stock rom.

I'm trying to edit vo_config.xml from /oem/OP/OPEN_EN_DS/config for VoWiFi/VoLTE.

It seems this is mounted on /dev/block/dm-0.

I have already:

HEX edited magisk_patched.img "judypn androidboot.product.lge.op_verity=0" and flashed it in ADB and it didn't solve my problem.

I have already remounted the partition.

setenforce 0.

I consider:

Flashing the whole patched oem image, is it possible?

Running a Magisk module, if it's availabe.

I would flash this zip, but it seems it needs custom recovery, which i would like to avoid ( maybe creates issues with the custom rom, updates etc) . Can it be used from booting TWRP witouth actually installing TWRP?

How could this be done without TWRP or custom rom? I'm on Android 9, stock rom ( judypn 20f)

Help would be appreciated.
[Android Software Development] tpetris:
Update

Something strange happening:

I have booted TWRP, didn't install it.

Mounted OP Configs partition as read write, it's where the vo_config.xml resides.

Used ADB Shell , then navigated to the vo_config.xml. If i do a cat command, i can see the changes I've made with root access previously: < info mmc="226" mnc="05" etc.

If i boot normally, navigate to the vo_config.xml and do a cat command i still get the original file: < info mmc="226" mnc="10" etc.

Somehow there are 2 files somewhere, with TWRP read/write it opens the edited one, without TWRP it opens the default one.

Any thoughts?
[Android Software Development] 1equals2:
This sounds like the same problem I was having with my Moto G7 (and someone else had with their G6). I didn't get a response before I returned the phone, so I haven't tested anything out, but someone did respond to my thread with what looks like helpful information. Maybe it will be relevant to you too.

https://xdaforums.com/moto-g7/help/how-persist-changes-to-oem-folder-t4089479
[Android Software Development] fergusc:
Can someone host a mirror of the zip? His site is very slow and the download fails before I reach 200 kB.
[Android Software Development] WoKoschekk:
https://mega.nz/file/guhniKrZ#pvd9HjhxuAfd1i1W5zC02KwrbZdg6GWdB3aDBxBoVyw
[Android Software Development] Medicina200401:
Hi. I need to solve the problem of partition data 0 Mb in TWRP to be able to make full backups.

My phone is a samsung J7 2016 Android Pie original root with magisk and twrp 3.2.1

I have read this thread and since my knowledge of English is not good, I do not understand if what is spoken here is the solution to my problem.

To solve this problem, what should I disable?

I also do not understand how I should install the zip? should i change the name?

I hope you can understand my English. Thank you

Alexander
[Android Software Development] hoshang.govil12:
Wipe data partition and Flash ROM, Gapps and don't flash this Zip. This is meant for mostly Stock ROMs.
[Android Software Development] Harainss:
fingerprint was nowhere to be found in settings when flashing this zip. Like always whatever ROM I flash. My device is redmi note 7. Tried not installing this zip and fingerprint option came back! Any remedy to this issue?
[Android Software Development] glurak888:
Same and PIN and password is ALWAYS wrong. Even after a neccessary factory reset, i repeated and set it to 1234 and locked the device, 1234 wasnt the "correct" code. Same with the Unlock pattern!
[Android Software Development] amn1987:
What to do when Magisk fails to be installed inspite of no errors while flashing it? In that case DFE obviously didn't work and storage became encrypted. Flashing Magisk from Magisk Manager after booting to ROM did work. Is there anyway to check beforehand that Magisk wasn't actually installed? The ROM (AEX Pie) itself force encrypts. I came across this issue after a long time, more than a year IIRC.
[Android Software Development] lmentor:
I get bootloop on oneplus7Pro H2OS Beta15.
[Android Software Development] Xvistak:
I'm problem this script not end work.

Dm=false

Force=false

Quata=true

Format Data,Reboot fone start not work rill,navbar,kaybord.Wallpaper is blak(mayby safe mode android).

I'm use old version ZIP disabler

Nau start Normal mode,i'm info as setting"Yor Device is Not Crypted".I'm test bacup info twrp,format,restore....Fone Bricke.....One test backup recovery,boot,system....Not Work two test backup all parytion(6500GB i'm compress backup)....Restore not Work....

---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
[Android Software Development] TheK0tYaRa:
Can that be flashed with Odin? Device is Samsung Galaxy M21, wishing to participate in testing!
[Android Software Development] vooks:
This is not working on my Note 8 SM-950N
[Android Software Development] hartdaddy:
Confirm changes

Hi,

Is there a way to confirm ForceEnc and DM-Verity are disabled? I am on a OnePlus 7T running build HD1907_14_200519, rooted, with TWRP recovery. Is there an easy test or an app?

H
[Android Software Development] WoKoschekk:
force encrypt = your device is not encrypted anymore

You can see it in your settings app > security > encryption
[Android Software Development] enotar:
Including in a Rom Script

Hey Zackptg5, Thank you so much for your fantastic job. I am flashing a custom Rom rooted with magisk for Samsung Tablet T830, after flashing process finish I flash the Encryption Disabler from this thread and reboting all works fine even going in recovery with TWRP internal partition is mounted. No problem

But I want to include the encryption in the Rom script to have it flash after magisk, well that doesnt work. It doesnt flash the encription anywhere I put it in the script after magisk. What should I do? Is it possible?

Can you help ?

Thank you so much
[Android Software Development] WoKoschekk:
What exactly are you trying? Do you want your /data be encrypted or decrypted?
[Android Software Development] enotar:
Decrypted
[Android Software Development] WoKoschekk:
Magisk checks (EDIT: during installation!) your system wheather it's encrypted or decrypted and your device boots up accordingly. If you try to decrypt with Magisk already installed, it will result in a conflict. Magisk wants to boot an encrypted device which is decrypted.

Solution: Decrypt first and then install Magisk.
[Android Software Development] enotar:
Will try

Thanks

Update I tried inserting at the end of the script the flash of the encryption disabler, It flash ok but still not working after reboot data is not mounting. What puzle me is that when I do manuly flash the rom and when flash finishes I flash imediately the disabler on this case that works.

Any idea
[Android Software Development] andy_light:
Hello. Please help. I have Poco F2 Pro, I got an error after installing Dm-Verity & ForceEncrypt Disabler

Failed to mount '/odm' (No such file or directory)

Something gone wrong? Or I can forget this error?
[Android Software Development] lovemytab:
Thank you.
[Android Software Development] almightysiman:
I am having bootloop issue on oneplus7pro with OOS openbeta 17 after flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip,it was working on openbeta16,anyone here facing the same issue?
[Android Software Development] extremeinside:
I have the same problem with oneplus 7 pro on open beta 17
[Android Software Development] WoKoschekk:
On some devices it isn't possible to disable dm-verity by flashing this tool. You will need some extra steps to remove verity. But this is different for each manufacturer and/or model.

As you can see in the OP you can set some options for what should being patched when flashing this tool. It might be helpful to try some options.

Why do you need this tool? Only for dm-verity, disabling fec or both?
[Android Software Development] alecxs:
please note due the compatibility changes regarding (FBE) two years back (FDE) forceencryption can no longer be disarmed, instead encryption is completely disabled with this zip

Furthermore (fec) forward error correction is a very restrictive form of dm-verity which (according to page 90 45) can't be disabled, yet
[Android Software Development] WoKoschekk:
I meant forceencryption instead of fec. Used the wrong term.
[Android Software Development] hypergp:
I just need this to stay decrypted
[Android Software Development] H4X0R46:
Yeah same here too. I hope there's a solution for this soon because I only run my 7 Pro unecrypted because I like the freedom of flashing stuff and not ever worrying about the security patch level on my device. [MENTION=6037748]Zackptg5[/MENTION] any official word? Thanks man!
[Android Software Development] lndiana:
I was facing the same problem too, so I loaded the zipfile to PC, copied it to internal memory of the phone, installed it from there, flashed twrp installer,rebooted to twrp, flashed magisk, and done...