yashsingh1/xdaforums huggingface dataset:
[Android Software Development] :
can i use this with lineage os official for land ?

will it help me to keep data not encrypted ?

what procedure should i follow while i update to next build?

will it work without flashing root(magisk) ?

thank you !
[Android Software Development] ScorpiusDLord:
I read many instructions about root xiaomi redmi k20 pro (chinese rom). There is an instructions to flash file Disable_Dm-Verity and then install the file Magisk, if not, it will bootloop. But there is an instruction just flash the file Magisk is enough.

I do not understand, I need to flash file Disable_Dm-Verity when I root redmi k20pro?

Sorry my bad english.
[Android Software Development] kidlerek:
If Universal DM-Verity Disabler doesn't work for me is there any way to reduce display time of message, which shows when I boot phone ?
[Android Software Development] daitalos:
this zip disable dm-verity and force-encrypt android security

You need the right twrp for your device

You must read carefully in OP > Instructions : see below & follow the instructions :

If you're currently encrypted (1234)

If you're not encrypted ....

sry for english
[Android Software Development] mipirakas:
I don't know but the purpose of this zip is not to disable the warning message at boot. Afaik as soon as you unlock bootloader, the warning message will be there with no way to remove it.
[Android Software Development] adrianogoes:
But you can replace logo.bin with an image that soften this warning... ;)

Try this logo.bin inside the zip I attached.

fastboot flash logo logo.bin
[Android Software Development] Joe333x:
Will this work to disable encryption on an SD card being used as adopted storage? I ask this because I am currently on a Galaxy S5 running Lineage OS 16 and I have encryption disabled but the SD is still encrypted when using adopted storage. This causes issues with booting into TWRP because of the encryption on the SD card it takes around 5 minutes for the recovery to boot since it needs to decrypt the card.
[Android Software Development] lRemainl:
Thank you so much, works perfect in a Redmi Note 7!
[Android Software Development] lRemainl:
Hi, i am facing a very frustrating issue. I have tested 2different Roms and patch work flawless. But when boot and add lock pattern/pin then i cannot unlock phone, it says my pin/pattern is incorrect. I've tried many times and it always even making a clean install. I wipe format data, reboot recovery, then advance wipe cache/Dalvik art, system, data, internal storage, vendor. Select sd card install ROM, install gapps (if available), install magisk, last DM verity, reboot system. Please help me.
[Android Software Development] kamikaze702k:
U need to format data it's not the same as wipe.

Format data

Wipe data

install this zip at the end after all your other files in the initial flashing process, no issues, what u described only suggests that it's still encrypted.

Just install the file zip as is, I personally don't rename anything

I personally don't wipe system or vendor either, I'm on aosip
[Android Software Development] lRemainl:
Hi, i did format data and I've been reading that some devices are not possible to full unlock, for that reason i am always having pattern/pin issues. I am using Redmi Note 7 with encryptation and no more issues.
[Android Software Development] Zackptg5:
Finally had the chance to take a closer look at it and fixed a few bugs (and updated ak3 and magisk binaries while I was at it) and I believe it's a working zip now (works for me at least). I posted it in the OP for now so let me know if there's any more problems and if not, I'll push it to my site
[Android Software Development] lRemainl:
Hi, thanks for the updated but I still facing pin/lock pattern issue. I used last updated zip. I think is Redmi Note 7 security.

I am currently using encrypted mode and pin works normally.
[Android Software Development] Zackptg5:
Since nobody complained of any bugs with the 10.20 zip, it's now the new stable - OP updated :)

Are you setting the pin during initial setup? Try going through initial setup without setting any security and then setting it after everythings setup.

Another thing is that even when you wipe data, the old pin can be left behind causing problems. In twrp, go to /data/system and delete the locksettings.db file and then try setting a new pin or whatever again
[Android Software Development] :
Haha, I love the QA methods. No one complained, so it's stable. ?
[Android Software Development] Zackptg5:
I considered it stable but since I try to make it as universal as possible, I wait for use feedback in case they l there device has different results. Not ideal, but works okayish :/
[Android Software Development] :
Oh it was more of an internal joke, I work for an international multi-million dollar organisation that deals with QA in the same manner.

It wasn't a criticism to you by any means, my company however....
[Android Software Development] chrcol:
works a treat thank you, I seen other zips and methods none worked reliably or at all, yours "just works"

I flashed it not for performance, but so TWRP backups work, TWRP is surprisingly pretty broken right now for my device, one of the bugs is related to FBE, and now I dont have to deal with that specific bug anymore.

Thanks.
[Android Software Development] Nubidubi23:
My phone is in RMM , and i cant go in TWRP after i flashed it because it just doesnt take inputs . What can i do?
[Android Software Development] lRemainl:
Hi, thank you so much for the effort you put to help me to find a solution and... yes I have already tried this method before. Put the PIN after setup then go to TWRP, Advanced -File Manager- data/system/ and delete db files and when I setup a new PIN/Patter is still failing. I gave up and I think is my device model. If another user has a Redmi Note 7 and could give us feedback would be great.
[Android Software Development] ninjakira:
Edit: it was a error on the users side that they werent telling us,
[Android Software Development] chrcol:
I dont see the point of magisk 20 on android8. just tell them to use 19.x or 17.x?
[Android Software Development] 4ncha72:
Can i use this zip to disable verify boot (like AVB) to flash gsi rom????

Thanx
[Android Software Development] andrea0807:
In what order should I flash the dm verity zip?

For example I flash rom, magisk, dm verity, gapps, zip of migrate?

Is this order ok?
[Android Software Development] mipirakas:
In the OP it says: "flash all of your stuff, then FLASH THIS ZIP LAST". I would recommend rom, gapps, magisk, (zip of migrate? Idk what this is), and finally this dm verity disabler.
[Android Software Development] andrea0807:
Migrate is an application used to restore apps after a reset, such as Titanium.

But do I have to flash the DM verity zip every time I update my Rom? (when I update my rom I don't do a clean install I only do Wipe Cache and Devilk)

Or should I flash it only when I change ROM then after a clean installation?

(When I change ROM I make wipe data and system)

Inviato dal mio MI 8 utilizzando Tapatalk
[Android Software Development] mipirakas:
Yes, every time you flash an update, you need to flash this zip again. Flashing an update restores the fstab files and your boot img and such.
[Android Software Development] aocboe:
oops
[Android Software Development] People11:
Not working on Android Q on Pixel 2

here is what i have done:

reboot to rec

format data

flash magisk

flash your zip(latest)

reboot

the phone reboot automaticly during booting

data encrypted
[Android Software Development] CrimsonSwordsman:
Hi, would like to ask.

Do I need to be rooted for this to work?

Flashed this in TWRP after fresh stock rom installation. Thanks for reply!
[Android Software Development] amg314:
While you are in TWRP, you have root privileges.

In particular, you can get a real root by flashing Magisk.
[Android Software Development] Zackptg5:
It's better to mention someone rather than quote the OP. No, you don't need root, just TWRP
[Android Software Development] ndt44:
After flashing the default dm-verity and encryption filename, my ulefone Armor 6E got stuck at the boot logo forever. I tried to restart twice and the phone stayed stuck at the logo.

I was forced to use fastboot to reflash my Magisk patched boot.img file then it started normally. The phone is rooted with Magisk and I was able to flash the Orange State away before I tried flashing the dm-verity file.

Is there a log that would help diagnose what may have gone wrong?
[Android Software Development] amg314:
After flashing in TWRP you can go to Advanced --> Copy log
[Android Software Development] ndt44:
I used Flashify to flash the dm-verity and encryption .ZIP file, and I didn't know there was a problem until my Armor 6E refused to boot.
[Android Software Development] ShadeTreeBiker:
Locked Bootloader

I have several questions about this.....so, first the specs.

ZTE Z3351S (Q-Link Wireless govt. phone,) Quest 5

Board Salable, MT6739

Android 9 with Security Patch 2019-07-05

Build Z3351SV1.0.0B04

64 bit ARMv8-A in 32 bit mode

ADB enabled, Fastboot (seems) to be present but computer cant talk to it in FB Mode

Developer enabled, and OEM unlocking enabled

BootLoader, locked...no fastboot commands work

Stock Recovery..has sideload from adb but nothing installs that way, so...

NO ROOT. (And plenty of bloat to remove...loads.)

Dont necessarily want to flash a custom ROM, and even a custom recovery wouldnt be a big deal, I dont think either are existent yet. BUT I DO want to back-up EVERY partition, (stock) for forensics in a VM.

Problem is ROOT has yet to be achieved with this unit. Ive looked EVERYWHERE, here, GOOGLE, duckduckgo, bing, etc. This device isn't found but in one post here...smdh.

MY QUESTIONS:

Do I need root to use this? And if so, will this solution (https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213) trigger the dm-verity or ANY other root detection routines?

IF I use the ZIP will I gain root, making the above solution non-relevant? AND I ASSUME it will install Magisk...and gain root this way. :D...

AND FINALLY, (THIS is the real BIG one) are there any more root detection devices/routines that will cause a bootloop? t

I kinda rely on this phone for a daily driver but do need the bloat GONE and maybe a Titanuim Backup or 2...

I sincerely appreciate any answers/guidance you folks can give. I'm not a newbie to Android hacking and rooting methods, but not an expert either...
[Android Software Development] HippoMan:
Did you find a solution to your boot-back-to-TWRP problem?

Also, I have a general question: I have a rooted OnePlus 7 Pro running 9.5.13.GMA21AA and the NoLimits Magisk-based ROM,

but the OS came from an OTA, and I don't have any OOS ROM to flash.

Is there any way to decrypt my device without finding a ROM to flash?

Thanks in advance.

PS: I found a TWRP-flashable 9.5.13.GMA21AA ROM, so my second question is now moot.

However, I'd still like to know whether there is a solution to the update problem described above.

Thank you very much.
[Android Software Development] HisEvilness:
Thanks for a great utility I used it when writing my guide for custom recovery and rooting found here:
[Android Software Development] HippoMan:
I keep seeing new ROMs via OTA before I see downloadable and therefore TWRP-flashable versions of these ROMs. For example, OOS 10.0.2 is now available for OTA installation on my GM1917.

This again raises the question of whether there is any way to decrypt via dm-verity without specifically flashing a ROM via TWRP as part of the process.

Does anyone know of a way to do this with an OTA-installed ROM, or am I out of luck?
[Android Software Development] reaper000:
I think you are out of luck. Here's why:

You cannot simply decrypt the data partition that's already encrypted by a ROM. Remember, formatting internal storage is MANDATORY before the dm-verity zip is flashed.

To use a metaphor, it's not like flashing the dm-verity zip will remove the lock (encryption) from the door (data partition). It's more like you have to create a whole new door without any lock (format internal storage, flash a ROM from external USB drive, flash dm-verity zip from USB drive) from scratch.

When an OTA upgrade is flashed, it will overwrite the dm-verity zip script that sidesteps the forced encryption of a new ROM upon initial boot. In other words, after an OTA update flashes, the next reboot will encrypt the ROM. That's the best case scenario if it even boots, because the more likely outcome is that it does not boot, encryption is screwed, and you're dumped into recovery...and not TWRP, because guess what? That too was overwritten by the OTA install and you're stuck in stock recovery!

Anyone who knows better, please feel free to correct me.
[Android Software Development] HippoMan:
Your explanation makes sense.

I now understand that when I OTA-flash a ROM, the filesystem starts out encrypted and the OTA also encrypts that filesystem. So if I want a decrypted filesystem, I therefore would have to decrypt that filesystem *before* installing a ROM, and this ROM installation cannot be done via OTA, because it will re-encrypt.

So, now I see that's why the ROM has to be installed directly via recovery (TWRP) *after* dm-verity has ensured that the filesystem is decrypted. This avoids the OTA-level re-encryption.

Thank you very much for clarifying this!

.​
[Android Software Development] sevensss:
after flashing this I'm not able to change lock method to pin or pattern etc also fingerprint option is gone

anyone have this problem?
[Android Software Development] HippoMan:
Is it possible to get rid of decryuption solely via Magisk?

I'm on a rooted OnePlus 7 Pro (GM1917) running 10.0.2 with xXx-NoLimits and Riru/EdXposed.

In my version of Magisk (v20.1), there is an "Advanced" section in which the following two items are selected:

Preserve force encryption

Preserve AVB-2.0/dm-verity

Can I remove my device's encryption simply by unselecting one or both of these items, and then rebooting?

.​
[Android Software Development] Johnny_Wishbone:
Moto XT1925-6, flashed magisk, then DM-Verity disabler, got bootloop

Hello people.

I've got a moto G6 (XT1925-6), T-Mobile (US), I updated to the latest OTA and security updates. I flashed Magisk 20.1, then the dm_verity disabler, zip named just as when it was downloaded, and I got a bootloop.

Recovery log is at

pastebin dot com/hvRGZ6jh

The forum won't let me post links, which is understandable, but I hate cluttering up the forum with long walls of text. And Pastebin gives you line numbers, which is nice.

Thanks for all your help!
[Android Software Development] reaper000:
No, Non, Nyet..!

I know you read my post on the last page, because you thanked me for it yesterday. To wit:

To use a metaphor, it's not like flashing the dm-verity zip will remove the lock (encryption) from the door (data partition). It's more like you have to create a whole new door without any lock (format internal storage, flash a ROM from external USB drive, flash dm-verity zip from USB drive) from scratch.

You MUST format internal storage to be permanently unencrypted. Remember, creating a new door..,! And when you format internal storage, you also wipe the filesystem of the onboard ROM, and you won't boot at all -- which is why after formatting internal storage, you have to flash a new ROM, and then flash the dm-verity zip last.

Let me see if I can make it easy:

"Running decrypted" or having an "unecrypted phone" is the RESULT of AVOIDING the Android standard of forced encryption upon an Android operating system's initial boot. How do you disable forced encryption? By flashing the dm-verity zip right before the initial boot of the OS...
[Android Software Development] HippoMan:
Yes, I read your other post and understand your metaphor. I just saw those entries under Magisk, and I wanted to know what they mean and whether they provide a different path to non-encryption that hasn't been discussed yet.

It's entirely possible that someone could write Magisk-installable software which encapsulates the dm-verity disabling procedure and intercepts the device's standard OTA methodology at a low level in order to automate this dm-verity-disabling process and inject the proper dm-verity disabling code at the correct step in the modified OTA process ... i.e., right before the initial boot of the OS. But I understand now that these Magisk options do not cause anything like that to take place.

Thank you.

.​
[Android Software Development] reaper000:
In other devices like the Samsung S7 and S8 that I used before, custom ROMs are already decrypted with integrated disable dm-verity, obviating the use of a separate dm-verity zip like this one.

However, even the OTAs for that device require preexistent decryption. My guess is that the encrypted data partition is the deal breaker, in that the OTA is flashing from storage that needs to be decrypted before the new ROM is flashed. Looks like a chicken and egg conundrum, because even if you inject dm-verity-disabling script right before flash, your data partition and the system files on it remain encrypted because there wasn't a format of internal storage. And if you did format internal storage, you would have deleted the OTA ROM file that you need to flash.

Not to rain on the parade or anything, but it's been 4 years since I've noted this with the S7, so while something totally ingenious might pop up, I'm not gonna hold my breath...
[Android Software Development] whc2001:
Seems like it's not working for my Lenovo L78071. When I boot into the system, the encryption screen still appears, and after reboot to recovery it still asks me for password to decrypt. Also the modified TWRP I am using (there is only one which is the custom building of TWRP available for this device) has a build in force encryption disabler, I tried and it worked, but just like someone reported in this thread, I am having screen lock issue after disabling force encryption.
[Android Software Development] abeloman:
This tool won't remove encryption; it'll avoid force encryption on first boot. If you're encrypted, you must format data to remove encryption, and after that, you can flash the zip
[Android Software Development] Zackptg5:
Looks like system didn't mount. Can you send me the link to your rom so I can check it out? Also, try the test build and post a recovery.log after like before

To everyone: New test build here, updated with workaround for android Q until TeamWin drops TWRP update for it
[Android Software Development] Mervingio:
But the encryption level is on hardware? OP6T this zip not work
[Android Software Development] swapyworld:
I tried flashing Xenon HD followed by this file and gapps and tried booting which resulted in bootloop.

Shifted to PE9 which booted fine but now shows device encrypted. I understand now format data needs to be to done but can anyone tell me what went wrong and how my device got encrypted?
[Android Software Development] HippoMan:
Double-checking dm-verity flash procedure

I am running 10.0.2 on my OnePlus 7 Pro (GM1917) with xXx-NoLimits and Riru/EdXposed. I also am running the Smurf kernel. Could someone confirm whether the following are the exact steps I must follow when flashing dm-verity under that configuration? ...

(1) Boot into recovery

(2) Format /data

(3) Flash the ROM. This is the exact, same ROM zipfile that I have flashed via System update->Local upgrade, namely OnePlus7ProOxygen_21.O.22_OTA_022_all_1911070323_2b888.zip

(4) Flash twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip

(5) Reboot into recovery

(6) Flash the same ROM zipfile again

(7) Flash the same TWRP zipfile again

(8) Reboot into recovery

(9) Flash Smurf kernel

(10) Flash Magisk-v20.1.zip

(11) Flash Smurf kernel again

(12) Flash Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip

(13) Boot to System

(14) Set up System

(15) In Magisk, flash xXx-NoLimits *** SEE QUESTION BELOW ***

(16) Reboot to System

(17) In Magisk, flash Riru and EdXposed *** SEE QUESTION BELOW ***

(18) Reboot to System

The question I have about Magisk is this: there are "Advanced" settings in the Magisk manager, and they are set by default to "Preserve force encryption" and "Preserve AVB-2.0/dm-verity". What should those "Advanced" items be set to when performing these Magisk-based flashes after dm-verity is set up as outlined above?

In general, I want to make sure that these are the precise steps that I must follow in that exact order. Also, I want to confirm that I can flash the same 10.0.2 ROM zipfile in this scenario that I have flashed via OTA. And finally, I want to confirm that the re-flashes and reboots to recovery that I list above are correct.

Thank you very much.

.​
[Android Software Development] Johnny_Wishbone:
Hey there. I'm changing the name to "Disable_ForceEncrypt.zip" because I only want to do that, but when I see the output in the TWRP terminal, the zip is still disabling DM-Verity, even though I removed that from the zip name. Am I missing something? Thanks.
[Android Software Development] topet2k12001:
Hello [MENTION=1751428]HippoMan[/MENTION]

Someone documented his steps and posted it as a separate thread (I was actually doing the same in the middle of trial-and-error)...someone apparently beat me to it. :) And the procedure he wrote worked for me. :)

https://xdaforums.com/showpost.php?p=81144885&postcount=11

Hope it can help you. :)
[Android Software Development] HippoMan:
It does help, thank you!! :)

It also raises the following questions:

(1) I am already running with 10.0.2 that was flashed via OTA, and then I flashed TWRP, Magisk, and Smurf. I'm guessing that instead of going back to 9.5.3, I can follow the procedure in that thread using the 10.0.2 ROM in all places where 9.5.3 and 9.5.4 are referenced. Is that correct? Or to be even more precise, I should format /data, then get to the point where I have 10.0.2 and TWRP both in slots A and B, and then go through the outlined procedure from there using 10.0.2 ... correct?

(2) I want no encryption. What changes to that procedure should be performed if I want to end up with no encryption?

(3) When I currently go into "Encryption and credentials" in my settings, it says that my phone is encrypted. However, I am never prompted for a password when booting, going into TWRP, backing up, restoring, or in any other case. What does this mean with regard to my phone's current dm-verity/encryption state?

.​
[Android Software Development] STALKER18:
[deleted]