yashsingh1/xdaforums huggingface dataset:
[Android Software Development] n.p.:
Can someone explain why flashing this fails?

__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
Starting TWRP 3.1.1 by Jemmini on Sat Sep 3 02:23:40 2022
(pid 236)
I:=> product model: 'T10(E3C5)'
I:=> using device id: 'T10E3C5'

[...]

I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/external_sd/system/Disable_Dm-Verity_ForceEncrypt-20201102.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.

Archive: /external_sd/system/Disable_Dm-Verity_ForceEncrypt-20201102.zip
inflating: anykernel.sh
inflating: banner
creating: META-INF/
creating: META-INF/com/
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: README.md
creating: tools/
inflating: tools/ak3-core.sh
creating: tools/arm/
inflating: tools/arm/busybox
inflating: tools/arm/futility
inflating: tools/arm/keycheck
inflating: tools/arm/magiskboot
inflating: tools/arm/magiskpolicy
creating: tools/avb/
inflating: tools/avb/verity.pk8
inflating: tools/avb/verity.x509.pem
inflating: tools/boot_signer-dexed.jar
creating: tools/chromeos/
inflating: tools/chromeos/kernel.keyblock
inflating: tools/chromeos/kernel_data_key.vbprivk
inflating: tools/util_functions.sh
creating: tools/x86/
inflating: tools/x86/busybox
inflating: tools/x86/futility
inflating: tools/x86/keycheck
inflating: tools/x86/magiskboot
inflating: tools/x86/magiskpolicy
"*************************************************"
"* DmVerity,ForceEncrypt, and DiscQuota Disabler *"
"* By: Zackptg5 *"
"* Heavily based on the work of: *"
"* TopJohnWu and Jcadduono *"
"*************************************************"

AnyKernel3 by osm0sis @ xda-developers

Installing...
ash: /dev/block/platform/soc/11230000.mmc/by-name/boot: unknown operand
ash: /dev/block/platform/soc/11230000.mmc/by-name/boot: unknown operand
/dev/BOOT

- Chosen/Default Arguments:
Keep ForceEncrypt: false
Keep Dm-Verity: false
Keep Disc Quota: true

- Detecting Root Method...
No Magisk or SuperSu detected!
- Unpacking boot img...
dd: /dev/BOOT: Invalid argument
Parsing boot image: [/tmp/anykernel/boot.img]

Dumping/splitting image failed. Aborting...
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 1 second(s).
Error installing zip file '/external_sd/system/Disable_Dm-Verity_ForceEncrypt-20201102.zip'
Updating partition details...
I:Data backup size is 0MB, free: 54822MB.
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'auto'
...done

Thank you in advance.
[Android Software Development] nation888888:
There's no decryption for Android 12 yet. My question could this work for expanding my system partition by having no disk quota?
[Android Software Development] ZAHIDx:
Work MIUI vendor?
[Android Software Development] RMX3370:
For People who are still looking for a viable alternative

See This

[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Disable Force Encryption Native Early Override (DFE NEO v2) | Disable encryption /data | userdata

Brief description: Disabling encryption without direct modification of system files. Mount method, i.e., RW not required. Supports EXT4(RO/RW), EROFS, F2FS(RO/RW). Description: DFE-NEO v2 is a script designed to disable forced encryption of the...

xdaforums.com

It works with newer devices which have non writable system and vendor i.e, Dynamic/Super Partition device with erofs
[Android Software Development] lyyyne:
kind of worked on Samsung J6 2018 with TWRP and Magisk, just bootlooping
[Android Software Development] Sutan99:
working good, but this makes my redmi 6 camera not working 😥
[Android Software Development] ashish1989:
But it says format data is necessary after flashing it
[Android Software Development] alecxs:
format data is always necessary to remove encryption
[Android Software Development] footbook:
Nowadays Magisk is recommended installing by patching the stock boot.img... How can Magisk's boot patching deal with the already patched boot.img of Universal DM-Verity, ForceEncrypt, Disk Quota Disabler?

Will Magisk overwrite the patched boot.img?
[Android Software Development] WoKoschekk:
Patching a boot.img means to manipulate some kind of executable code inside the image. A boot.img is nothing more than a container holding the kernel, ramdisk and device tree files. All of them are mandatory components in a Linux environment. But for devices running with Android they are summarized as a boot.img.

As long as no components of a boot.img are replaced by patching it (e.g. installing a TWRP's ramdisk) neither Magisk nor the 'Universal DM-Verity, ForceEncrypt, Disk Quota Disabler' won't overwrite any previously made patches. In addition to that the core functionality of the "disabler" tool is part of Magisk's code. But it offers more options and is more detailed. So no conflicts can arise when using both tools.
[Android Software Development] footbook:
But Magisk will patch the

Stock

boot.img.

How can I make Magisk patching the boot.img that is already patched by Universal DM-Verity, ForceEncrypt, Disk Quota Disabler?
[Android Software Development] WoKoschekk:
Same way as the stock boot.img. Magisk will not give any error message when using an already patched image. You can use every boot.img and every recovery.img you want. You can also use aa already magisk patched image. You can patch an already patched image as many times you like e.g. a 100-times-patched image.
[Android Software Development] footbook:
boot into TWRP

$ adb pull /dev/block/mmcblk0p21 boot-noverity.img

reboot into Android

installed Magisk

Magisk patched the boot-no-verity.img

$ adb reboot bootloader

flashing Magisk patched: fastboot flash boot boot-noverity-magisk.img

bootloop

Reflashing back: fastboot flash boot boot-noverity.img

boots OK

Am I doing something wrong here?
[Android Software Development] WoKoschekk:
Why TWRP? You can use ADB in running system.

Obviously when you're ending up in a bootloop.

Try this:

- patch your current stock boot.img by Magisk App

- start TWRP and install the magisk-patched_boot.img on your boot partition

- flash the disabler tool

- restart system
[Android Software Development] footbook:
It worked! Thank you! ;)
[Android Software Development] alecxs:
you probably forgot factory reset. due an unsolveable conflict how fstab must patched against FBE it was no longer possible to provide FDE encryptable= flag (refer to page 40) therefore after patching device can't boot on encrypted userdata partition.
[Android Software Development] WoKoschekk:
/data was already unencrypted on his device but he didn't install Magisk.
[Android Software Development] Paresh Kalinani:
Read a lot on this thread and I'm assuming the answer is no but I'd still take a chance...

Anyone manged to decrypt OnePlus 6T permanently, maintaining basic device security?

A lot of posts on this thread complain that if 6T (not 6) is decrypted, you lose basic security of the phone (PIN/password lock, etc.) because it says password is incorrect, once you set it on a decrypted phone.

Any 2022 update? Or does anyone, who understands the problem with 6T, can comment whether DFE-NEO would work? :

[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Disable Force Encryption Native Early Override (DFE NEO v2) | Disable encryption /data | userdata

Brief description: Disabling encryption without direct modification of system files. Mount method, i.e., RW not required. Supports EXT4(RO/RW), EROFS, F2FS(RO/RW). Description: DFE-NEO v2 is a script designed to disable forced encryption of the...

xdaforums.com

Edit : Seems it was my turn to try. Tried on OnePlus 6T, Android 13 -

1. Flashed ROM to both slots

2. Flashed Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip

3. Formatted data

4. The system is not bootable, the recovery is not bootable. Phone just boots to fastboot.

5. Booted to TWRP img using fastboot

6. TWRP did not ask me for a decrypting PIN to decrypt the internal storage.

7. Flashed UPDATE-sdcard.Fix.Permissions-signed.zip

8. Reboot to recovery, it did not ask me for a decrypting PIN to decrypt the internal storage.

9. However, I couldn't copy anything to the phone via PC.

10. Went ahead and did a "Format Data" - typed 'yes'.

11. Reboot to fastboot, booted to TWRP img (just in case...), no PIN needed to decrypt.

12. Phone connected to PC and I could copy files to it easily.

13. In TWRP, earlier I saw the option to "Decrypt Users" in settings, which wasn't found not. Apparently confirmed that the device is decrypted.

13. But the 4th point didn't solve!! I still couldn't use the apparently decrypted phone (ROM doesn't boot)

What I understand here is... the phone could be decrypted and then the system couldn't access the internal storage or something went wrong on those lines?
[Android Software Development] wenyendev:
After the zip sideloaded in recovery, newly flashed rom was running smoothly so far on my device (Redmi S2, ysl).

Just when you

adb shell getprop ro.crypto.state

unsupported

rather than "unencrypted".

You need just flash it before booting into system. Otherwise, it could be stuck on splash screen when booting into system.

Maybe whether it worked fine or not depends on your device model.
[Android Software Development] gurtnyi:
Wow!

Thanks a bunch, man!
[Android Software Development] 120503:
hi, may i ask a stupid question? how to disable dm-verity but keep the phone encrypted? thanks
[Android Software Development] sjamie:
I do not believe that is possible.
[Android Software Development] alecxs:
you can use flashfire for this
[Android Software Development] jult:
Doesn't work, because Magisk 14 will fail on the Note 9.
[Android Software Development] atvator:
my phone xiaomi redmi 6a (mtk mt 6765) android 8.1, miui 10.2, magisk 17.2.

I change in my fstab file words forceencrypt to encryptable. - encryption was turned off and the communication(radio) module firmware was unavailable (sim1 & sim2 lost imei).

after restore original fstab all working good((radio) module firmware -OK (sim1 & sim2 - enabled imei)), but encryption was turned on.

our kernel is checked for integrity by the hash from Preloader or LK ... and if the hash does not match, then the loading of the kernel is blocked ... when the boot loader is unlocked, you can boot into Non-valid kernels, but the modem is blocked before the kernel is loaded

How can I fix this problem?
[Android Software Development] alessio89g:
Need I to reflash it when I update my ROM?
[Android Software Development] mipirakas:
Yes absolutely! When you update your rom your boot partition is replaced with a new unpatched one.
[Android Software Development] alessio89g:
Is it also compatible with Treble ROMs?
[Android Software Development] Zackptg5:
Yes
[Android Software Development] ncandroid84:
will this be a solution to the bootloop that is giving xposed in the Motorola with Android 8.1 ???
[Android Software Development] n19htmare666:
Same problems here, install them install magisk and SIM not recognised until restore a twrp backup. Would love to get this working
[Android Software Development] Zackptg5:
Did you follow the instructions in the OP to decrypt first?

Are you on a stock rom? Some roms will do that if you're decrypted (I don't know how to fix that/if it can be fixed)
[Android Software Development] Alan90:
Good idea

But I don't like Magisk I always thought of the SuperSu as a more secure solution to root with I might want a newer version of this when it comes to the rooting the latest android in the future too because viper and dolby or xposed can already be done with this.
[Android Software Development] DEVILOPS 007:
You're one in a million buddy.
[Android Software Development] Alan90:
Supersu gives me a clean secure boot flag Magisk does not so I want my secure root back in newer android versions by introducing an idea I need created make a new open source version of supersu auto root and use aroma zip to pick system or systemless root before booting it up so I can use it like I did Kitkat for example I know new android is built on kk ideas with the SD I'm not one in a million many people want to say **** magisk or lineage su I want my chainfire bought back in an open source version
[Android Software Development] folusmile:
I dont really like magisk either at first I jst hv to force myself to. No option left and magisk is doing pretty good. SuperSU didnt think of his users before he sold his pretty work to CCMT., so painful
[Android Software Development] The Analog Kid:
He's "two", actually. Which doesn't make much difference, anyway...

---------- Post added at 06:27 PM ---------- Previous post was at 06:15 PM ----------

Something tells me such a transaction was made with the sole purpose of making SuperSU disappear... However, perhaps using Chainfire's own Aroma installer for SuperSU could help making it last a bit longer at least. There's still people looking for a "simple" and reliable solution. That's SuperSU. I'm also assuming this [MENTION=6037748]Zackptg5[/MENTION] universal fix could actually help using SuperSU, as well...
[Android Software Development] madbat99:
Ever since lollipop and especially nougat and newer systemless root is necessary. System root is no longer possible as it was in KitKat. So no matter what from here on out on newer versions of Android you're going to have to use a systemless root which modifies the boot image. Nothing more can be said about that.
[Android Software Development] Alan90:
boot image modifications can be used to give system root like kk did

permissive system can be modified in Android 6 to do system mode su like kitkat but android 7 or higher have to disable verity too
[Android Software Development] johnny_netwrock:
THANK YOU

Some phones like Mi Mix 2 are immune to lazyflasher, but this ...worked flawless .
[Android Software Development] :
It didn't work on Lineage 15.1 for land (latest build as on for today) with new clean install !
[Android Software Development] alecxs:
Linage has no fstab in boot.img therefore it can not fix fstab
[Android Software Development] WoKoschekk:
Did you read the OP?
[Android Software Development] WoKoschekk:
alternatively you could flash the zip how it is and afterwards you restore /vendor/etc/*fstab*
[Android Software Development] 120503:
sorry, i didn't read it carefully

and if i don't wanna root the phone but disable dm-verity, what should i do?
[Android Software Development] WoKoschekk:
Why do you want dm-verity to be disabled? You just need it to modify the system.
[Android Software Development] 120503:
confused...

you mean, to modify the system, don't need to disable dm-verity?
[Android Software Development] WoKoschekk:
1. You can only flash this tool (or any other flashable zip) either with a custom recovery like TWRP/Orange Fox or with Magisk App.

2. dm-verity = check the integrity of system partitions with checksums. Any changes on that partitions would generate another checksum and the verification would fail

- is your bootloader unlocked? Are you using a custom recovery?

- why do you want to disable dm-verity?
[Android Software Development] 120503:
i know about 1 and 2.

bootloader unlocked of course.

just want to remove some unwanted system apps with TWRP/Orange Fox's file manager. so, don't need to disable dm-verity?
[Android Software Development] WoKoschekk:
To modify /system you need to disable dm-verity on the most devices. But I don't know your device.

info:

Be careful! Don't delete system relevant apps or your device may not boot!

System apps save their updates (if any) in /data/app/*. You have to delete them, too.

After deleting the apps you have to wipe /data/dalvik-cache. It will be rebuild when your phone gets restarted. But without the data of the deleted apps.
[Android Software Development] 120503:
a

all right, i know. thanks
[Android Software Development] m0byn:
Hello everyone, or anyone? :)

Hopefully, some people are still active, read my post, and probably can help me out!

I am trying to flash LineageOS on my Samsung Galaxy Tab S4. In a post I read that it is necessary to use the Dm-Verity disabler zip. First, I tried:

Flash LineageOS 20 GSI and then Dm-Verity disabler zip => boots up until LineageOS bootlogo, but keeps hanging there.

Flash LineageOS 17 GSI and then Dm-Verity disabler zip => boots up and works fine. Afterwards, it is possible to flash LineageOS 20, which also works fine!!

Flash LineageOS 17 GSI and then patched boot.img => boots up, proceeds to LineageOS bootlogo, but crashes shorty after.

Since everything works with option 2 I could just start using it and proceed. However, I would really like to use encryption, which I was not yet able to work out how.

To keep encryption enabled I tried to remove forceencrypt from the disabler zip before flashing it. But no matter how I remove it, it always sets "Keep ForceEncrypt false", patches the fstab entries, hence, disables encryption. What am I doing wrong that it does not take the filename into account? As far as I know it should do that...

In the case of the Dm-Verity disabler keeping encryption enabled, does it actually do anything different than what I did with flashing a patched boot.img? I read something else in the log in TWRP...

Would it help if I try to send a log (not sure if it is the recovery one mentioned in OP)?

Also, if it is not possible to keep encryption while installing the GSI, would it be possible to add encryption afterwards?

I would truly appreciate if anyone could help me out!
[Android Software Development] alecxs:
you wanna keep encryption, use no-verity-opt-encrypt
[Android Software Development] m0byn:
Do you mean a different file or should the filename be no-verity-opt-encrypt.zip?
[Android Software Development] WoKoschekk:
try this here

GitHub - Zackptg5/Disable_Dm-Verity_ForceEncrypt: Disables dm-verity and forceencrypt

Disables dm-verity and forceencrypt. Contribute to Zackptg5/Disable_Dm-Verity_ForceEncrypt development by creating an account on GitHub.

github.com
[Android Software Development] WoKoschekk:
You flashed a GSI (generic system image). Those GSIs come as a single image of /system. That's not a fully custom ROM. It was build as a universal image being able to run on many different devices from different manufactures to offer them an option to try new Android versions in an easy way. Since it's very difficult for many devs to get encryption working on a single device and much more on a Samsung device, you'll never ever find a common GSI that supports encryption for all devices. That's not possible.
[Android Software Development] m0byn:
Thank you for your answer. Encryption actually works on my Samsung Galaxy Tab S6. I am trying to make it work on my Tab S4 as well :)
[Android Software Development] m0byn:
@alecxs I suppose the file is the one referenced by @WoKoschekk ?

I will have a read at these pages. You mean I cannot use it anyway?

Just for clarification: do I really need to adapt the script and figure out all the information regarding kernel and so on? On first read this was a bit overwhelming for me...Or is it also possible to download one of the no-verity-opt-encrypt.zip files found in the web? There exist 6.1 versions I think. Will this be compatible, or do I need to create the .zip by the script?
[Android Software Development] alecxs:
@m0byn for preservation of forced encryption rename Zackptg5's zip Disable_Dm-Verity_enfec_11.02.2020.zip

for disabled forced encryption with optional encryption support, use another zip that is able to replace the forceencrypt= flag with encryptable= flag (not in this thread)

https://xdaforums.com/t/deprecated-...uota-disabler-11-2-2020.3817389/post-80361061

https://xdaforums.com/t/deprecated-...uota-disabler-11-2-2020.3817389/post-86455963
[Android Software Development] m0byn:
Thank you very much for your answer. I will have a look at it tonight.

One question for clarification:

In the case of the Dm-Verity disabler keeping encryption enabled (hopefully it works with renaming as you specified), does it actually do anything different than what I would achieve with flashing a patched boot.img in which the verity blocks are set to zero?
[Android Software Development] adryyy:
Can confirm this still works.

Tested using Xiaomi Mi 6, LineageOS 20.0, Android 13.

Result -> Encryption Disabled. 😀

I need this for chroot, as I get Required key not available with the encrypted /data partition.
[Android Software Development] naagiovanna:
hi, If I format the data, is it still decrypted? or do i need to flash this zip again?
[Android Software Development] alecxs:
The modifications (needed to be done to disable encryption) and the (to be formatted) userdata partition (to remove encryption) are

different

locations, if it's that what you're asking ;)
[Android Software Development] WoKoschekk:
If it was previously decrypted, it will still be decrypted after formatting /data. You would need to modify /vendor to change the decrypted to an encrypted state.
[Android Software Development] an_i__rudh:
Thanks a lot mann. It worked like charm.was trying to install custom recovery for over a week . Downloaded many different dm disabler file encryption disable blah blah . But this file .it did the job in a single try after flashing it in the end . I now have the orange fox installed and loaded

Once again thank you
[Android Software Development] bongo6:
Can confirm this works with twrp-3.7.0_11-0-x1s.img.tar (S20 Exynos)

God bless you brother
[Android Software Development] lupin 3rd:
does is still work on android10 with twrp? Can I use only dm-verity disable without forceencrypt?
[Android Software Development] TheFilthyMongol:
Is there any way to install this without TWRP? I have a Nord N200 5G and, according to fastboot, it doesn't have a recovery partition. My phone is rooted.
[Android Software Development] WoKoschekk:
your recovery is part of boot.img
[Android Software Development] gurtnyi:
You can still install twrp on it, but you need a boot image with twrp. Perhaps there's something like that on the net. It's probably an mtk-based phone, that's why everybody sucks with them. :sad_face:
[Android Software Development] Smigde:
i got the error failed to mount /odm (no such directory exists)
[Android Software Development] diehard2013:
sm-t860

android 12

magisk 26.3

twrp 3.7.0

things appear to be working fine and stable, except for the error shown in screenshot 1.

SCREENSHOT 1

also, SCREENSHOT 2 below keeps returning after a reboot, no matter what option I choose.

SCREENSHOT 2

is dm-disable-verity still needed for android 12?

thanks.
[Android Software Development] diehard2013:
how do I tell if a given partition is encrypted?