yashsingh1/xdaforums huggingface dataset:
[Android Software Development] AshhRED:
How about

1. ROOT-ESSENTIALS

2. FLASIFY
[Android Software Development] RogerSilva:
Does it sill work?

I tried to flash it with Resurrection Remix 6.0.0.0, but it puts my device into bootloop in recove mode.

https://xdaforums.com/nexus-9/development/rom-resurrection-remix-v5-8-2-t3573120/
[Android Software Development] aarem:
Hello, I have a locked Sprint XT1766 (Moto E4). I was wondering if it is possible to use dm-verity disabler to get around the SIM lock so that it can work with a GSM SIM. I have no experience with this hence asking: I am running LOS 14.1 *unofficial* build from 03/05/2019. Thanks in advance for reading my naive question.
[Android Software Development] Kenan07:
hi i installed this to my redmi note 8 now its stuck in infinite boot screen how can i fix this i can acsses to twrp so can i unistall this?
[Android Software Development] Zackptg5:
No, verity and sim locking are different things. You usually need to go through the manufacturer for sim unlock unless someone found an exploit
[Android Software Development] VeRkNxT_lOvE_cUsToM_RoMs:
works fine on xiaomi mi 9t was already rooted with magisk but rooted again after flashing *for everyone like me that get's magisk error (additional setup required) skip it and go to install > direct install > reboot* and magisk will work! :)
[Android Software Development] luiz_neto:
Tried on my Moto G7 Plus XT1965-2, but put my device in bootloop. Please, see into my logs here.
[Android Software Development] greenleaves:
Note 8 - N9500-TGY can't Magisk root

Hello, I have samsung Note 8 - N9500 with latest stock ROM 12/9/19 can't Magisk root. TWRP installed well without looping. Here is what I did:

1. N9500-TGY stock ROM odin installed

2. Flash TWRP, then Format data, then reboot to TWRP again

4. Flash magisk 20.3, then Disable DM-versity zip. Reboot to system.

Reboot to system failed, it kept looping. Without flashing Magisk, TWRP reboot to system is working fine. Wonder what's wrong?

Appreciate any help.

Thank you.
[Android Software Development] alecxs:
use older zips Magisk-v19.3.zip + Disable_Dm_Verity_ForceEncrypt_5.21.2019.zip
[Android Software Development] greenleaves:
Tried Magisk-v19.3.zip + Disable_Dm-Verity_ForceEncrypt_01.19.2020.zip that didn't work as expected.

Where can I get Disable_Dm_Verity_ForceEncrypt_5.21.2019.zip?

Thanks.
[Android Software Development] :
I have the essential phone, running Android P, rooted with magisk..if I want to disable encryption, I should be able to make a nandroid, copy my internal to computer.then format data, restore backup, flash your encryption disabler zip, then magisk and should be decrypted... correct?
[Android Software Development] Zackptg5:
I've never done it that way before, maybe but if something goes wrong, you'll know why. I always suggest a clean flash when formatting data

Edit: Updated dmverity-re disabler to v1.3. Main changelog: changed forceencrypt abbreviation to fe, added disabling of dm_verity on devices that use 'avb' flag in fstabs

[MENTION=5842226]anupritaisno1[/MENTION]

Whipped up a disk quota disabler, check the OP. All it does is remove quota from the fstabs. Also updated the zips and stuff to change fec to fe or just spell out forcencrypt
[Android Software Development] janneriiki:
I did try that when you mentioned it but that didn't work either. I flashed the .zip in both A and B partitions. Any other ideas?
[Android Software Development] Zackptg5:
Well you have 3 options at this point. Either study the script in that zip and apply it to yours manually, flash the vendor img recommended with the rom your on, or flash a rom that matches your vendor version
[Android Software Development] janneriiki:
Alright I did study the script and manually changed build.props accordingly, which did not remove the issue.

Earlier I also dirtyflashed the full OTA package for my OOS 5.1.6 version and did also try the relevant vendor.img but without any success.

My solution (even if it doesn't completely eliminate the error) was to use the xposed app "AppOpsXposed Re" and disable "SYSTEM_ALERT_WINDOW" for Android System. I am sure that this will also prevent other warning windows from Android System, which I am fine with at the moment. So temporarily until further solution, this definitely prevents my OCD from being triggered.

There are probably some people out there whom think that this way of getting rid of the warning window is not the way to go, since it will most likely not allow windows as "Allow USB debugging?" etc to show. That's alright, one can always enable "SYSTEM_ALERT_WINDOW" when/if needed.

Thank you for the assistance!

Much love to the xda-community and all the helpful people here!
[Android Software Development] jonthn41:
hi, i have this tablet that has an "automatically re-locking 'enable oem unlock' switch"" (sorry im pretty noobish) I believe it switches off upon reboot because, it is a verizon device, and from what ive been reading, verizon does not allow you to unlock your bootloader. My device has a Software upgrade and repair tool (pcsuite.iso) that can be installed on windows via an option in usb-settings., ie. MTP,pcsuite, charge-only, etc. I can get to fastboot by issuing adb reboot fastboot command. fastboot devices returns something like device:????????? . Ive tried fastboot oem unlock, flashing unlock, flashing unlock_critical, fastboot oem 'anything' returns unknown command or something like that. although once i was able to get it to respond with the bootloader type i believe, but i dont remember the command.. anyways. i was able to get a .zip from a url i found when searching the pcsuite files. it contains many files (Boerne_DIAG.mdb.txt

boot.img

cache.img

CP6X_version.txt

DTim.CP

DTim.Primary

DTim.Recovery

EDEN_LWG_M09_B0_CP6X_DSDS_SKL_Flash.bin

HL_LWG_DKB_B0.bin

HL_LWG_DKB_B0_CP6X.bin

HL_LWG_DKB_B0_CP6X_MDB.bin

HL_LWG_DKB_B0_CP6X_MDB.txt

HL_LWG_DKB_B0_DIAG.mdb

HL_LWG_DKB_B0_MDB.bin

HL_LWG_DKB_B0_NVM.mdb

HL_LWG_M09_B0_SKL_Flash_B0.bin

IR7_PXA1928_B0_Trusted_eMMC_Elpida_lpddr3_2g_pop_EDFA232A2PD.blf

IR7_PXA1928_B0_Trusted_eMMC_Hynix_lpddr3_2g_pop_H9CKNNNBJTMPLR.blf

modded

nvm.img

obm_trusted_tz_auto.bin

obm_trusted_tz.bin

obm_trusted_tz_force.bin

obm_trusted_tz_secure.bin

obm_trusted_tz_secure_force.bin

persistent.img

primary_gpt

primary_gpt.i64

recovery.img

ReleaseNote_modem.txt

ReliableData.bin

secondary_gpt

Skylark_LWG_B0.bin

Skylark_LWG_B0_CMCC_CP6X.bin

Skylark_LWG_B0_EU_CP6X.bin

Skylark_LWG_B0_NA_CP6X.bin

system.img

teesst.img

tee_tw.bin

tim_eden.bin

tim_eden._recovery.bin

u-boot.bin

userdata.img

wtm_rel_eden_RealOTP.bin

) but i dont think this is an actual firmware zip.

I was able to push the boot.img to my device and patch with magisk. pull magisk-output boot.img, and modded the default.prop using abootimg* then adb reboot fastboot, fastboot flashing unlock, fastboot flashing unlock boot, fastboot flash boot modded-magisk-output_boot.img , fastboot reboot bootloader. the device boots with magisk root.. BUT!!!! upon reboot i get a messege "Modified" at the bottom of the splash and device will only boot into stock recovery. then I have to repair using pcsuite.. I have been able to flash boot, then dd stock-boot.img while booted, and uninstall Magisk using magisk.apk. which upon rebooting i get the same "Modified" messege, device reboots, the messege is gone, and device boots normally, without root. BUT all my data still intact. i was wondering if there was anything I could do to maintain persistent root without the risk of bootlooping to recovery. any information would be highly appreciated.. Thank You.
[Android Software Development] Zackptg5:
The modified message may be because of dm_verity (although I thought it was more for modifications of the system, not the boot img but don't quote me on that). If you want to test it, download this zip, unzip it it, open common/boot_patch.sh, then change the KEEPFORCEENCRYPT=false on line 60 to true. Then rezip it and flash it after fastbooting your magisk patched boot img.

If it doesn't work, you'll need to restore boot and vendor partitions (if you don't have a vendor partition, system).

However if it's because of a locked bootloader, I can't help you there :(
[Android Software Development] jonthn41:
[MENTION=6037748]Zackptg5[/MENTION]

by "this zip" i assume you mean from the op.. thanks for the reply.. I will give it a try right now, and let you know how it goes.. just a quick question though, when u say flash it after fastbooting magisk, do you mean using custom recovery, (because I do not have a custom recovery for my device), or were you thinking something like flashfire or something like that? any recommendations? THANKS AGAIN FOR ALL YOUR HELP..
[Android Software Development] Zackptg5:
Oohhh, I didn't think of that. I meant after flashbooting the magisk boot img but since you don't have a custom recovery, you could try flashfire. I have absolutely no clue what'll happen though as I've never tested it on flashfire (don't know why it wouldn't work though)
[Android Software Development] jonthn41:
one more thing? does it matter that my device is 64-bit???
[Android Software Development] wrkerr:
This worked great on my Nexus 9 with Lineage OS. Thank you!
[Android Software Development] ninjakira:
So I have the moto g6 play on boost Mobile on Android oreo stock and right now I'm rooted but there's an ota I want but i don't wanna lose my root. the person that usually patches the stuff for us has been quiet for about 2 weeks now So I'm wondering how I could do this. I'm currently on a patched boot Img but in order to update we need to repatch the boot Img from update. Any help would be great.
[Android Software Development] Zackptg5:
What's the boot img patched for? Flashing order is on the op
[Android Software Development] Zackptg5:
Updated both zips - minor update: fixed unlock blocks for boot img flashing (turns out magiskinit is needed for this stuff so I added it in)
[Android Software Development] radz_:
Hey man, if I update from custom kernel, do I need to reflash this zip?
[Android Software Development] Zackptg5:
Probably not but it depends on the kernel. It can't hurt to flash this zip again after flashing the kernel update (it's what I usually do)
[Android Software Development] mipirakas:
Hello,

I'm having a really hard time decrypting my OP5 on the latest open betas with treble support. I used to be decrypted just fine before the treble builds but since then i haven't been able to decrypt.

My procedure is as follows:

1)wipe everything (internal storage included)

2)transfer rom over and flash it

3)wipe internal again

4)flash magisk (v16.7) and this no-verity file (i tried this one and a bunch of others and i also tried flashing the no-verity files before magisk)

5)wipe internal again

6)reboot

But nothing works. It just doesn't boot if i flash magisk with no-verity or if i flash this no-verity only. And if i only flash no-verity (other versions) my device stays encrypted.

If someone could point me in the right direction i would really appreciate it.

Thank you
[Android Software Development] Zackptg5:
In addition to wiping everything, you need to specifically format data (it's a different option in twrp).

Also, flash this zip before magisk rather than after

Oos can be weird. I recommend flashing oos, rebooting into recovery, then flash this zip followed by magisk
[Android Software Development] mipirakas:
So ticking all the boxes in the wipe menu is not enough? Where do i need to format data? Is it the first menu in the wipe section?
[Android Software Development] alecxs:
[MENTION=6037748]Zackptg5[/MENTION] i see "segmentation fault" whereever toybox is used in newer TWRP therefore i recommend to rely on busybox by including binary and using explicit prefix, until toybox become more stable (its basically a one man show)

edit: you already do so but not everywhere in your scripts. and the osm0sis build is still not complete, use the YashdSaraf sel build (it is used in gapps for example)
[Android Software Development] Zackptg5:
Topjohnwu actually just figured out the selinux issue with busybox - next build will include those and won't rely on toybox anymore, can't tell you when though, got a lot going on currently.

That's odd though cause the installer should only use system toybox for 1 command and bundled busybox for everything else
[Android Software Development] greenleaves:
Thanks for the heads up. Will keep our fingers crossed. :):):)
[Android Software Development] alecxs:
True, you just forgot here and there. can do the changes on github if you're busy (minor fixes)
[Android Software Development] str8str:
Why does flashing this to stay decrypted always bork my data WiFi switching always have to hit airplane mode to enable data after being on WiFi. Any rom if the same. Don't happen if encrypted
[Android Software Development] nespresiii9999:
Answer

Wish to know
[Android Software Development] :
Hi @Zackptg5,

Last night I attempted to flash the the 01.19.2020 version from FKM/EXKM, however it failed to mount /dev/block/sda15 on /odm due to device or resource busy.

This was not an issue in previous versions around December, if I recall correctly.

As an alternative, I have been flashing via TWRP, however don't generally run with a custom recovery solution.

Is this to be expected, or a potential bug?

Things I have tried

- Restarting and reattempting, did not work

- Using an alternate kernel manager to flash, did not work

Things I have not tried

- Reverting back to stable Magisk, only as I have not been in a recoverable environment recently due to work.

System

Encryption: Decrypted

Magisk: 20.4-20200200101-ianmacd

OS: OxygenOS OB 29

Device: OnePlus 6

FKM Logs: pastebin.com/wyk65sYQ
[Android Software Development] Zackptg5:
Yup, it's twrp only
[Android Software Development] Zackptg5:
[MENTION=7285913]aIecxs[/MENTION] [MENTION=3327454]greenleaves[/MENTION]

Updated the zip. Changelog: updated ak3 template, use selinux supported busybox so no need to rely on rom binaries anymore
[Android Software Development] greenleaves:
Hi, here is my attempt for the 2/2 update. It failed to boot up again.

Did a clean fresh of the stock ROM, then TWRP, format data, reboot to fresh magisk 20.3, then Disable-versity, then reboot to system. It failed to boot up and kept looping.

Here are the logs:
[Android Software Development] Zackptg5:
No errors from the mod so it likely did what it was supposed to. What rom are you on?
[Android Software Development] greenleaves:
It's Samsung Note 8 TGY latest stock N9500ZHU6DSK2 with Dec 2019 security patch.

https://www.sammobile.com/samsung/galaxy-note-8/firmware/SM-N9500/TGY/download/N9500ZHU6DSK2/306898/
[Android Software Development] alecxs:
check /system/vendor/etc/fstab.qcom it seems magisk breaks encryption. also for samsung there are special instructions i don't think you can just flash a zip from recovery
[Android Software Development] greenleaves:
It looks like this is the case and has to do with magisk, the way it roots. Thanks
[Android Software Development] alecxs:
[MENTION=4544860]osm0sis[/MENTION] anykernel "still" rely on TWRP toybox (in context previous page 79). this is fine for know but bear in mind to test syntax on both (busybox and toybox)

edit: nevermind, it is working with PATH="$AKHOME/bin:$PATH" home=$AKHOME ZIPFILE=$ZIPFILE $BB ash anykernel.sh $2; (btw i would do export PATH instead but guess you have a reason for)

[MENTION=6037748]Zackptg5[/MENTION] the current problem is another (not sure whom to address issue?)

#sed -i "
# s/forceencrypt=/=/g
# s/forcefdeorfbe=/=/g
# s/fileencryption=/=/g
# " "$i"
sed -i "
s/forceencrypt=/encryptable=/g
s/forcefdeorfbe=/encryptable=/g
" "$i"

just a quick fix haven't checked for more issues

edit: have opened issues at github
[Android Software Development] Zackptg5:
Anykernel has nothing to do with toybox, it uses in built BusyBox for the environment. This mod specifically used /system/bin/toybox for ls -Z command because it required selinux support during compiling which BusyBox and twrp include box doesn't have. Topjohnwu cracked the puzzle and figured out how to compile BusyBox with selinux support so I use that BusyBox now (it has all the osm0sis patches too)

So long story short, the update I dropped yesterday switched to the selinux BusyBox so this issue is gone now
[Android Software Development] alecxs:
[MENTION=6037748]Zackptg5[/MENTION] i did notice and corrected my post, seems your reply was against original post, sorry for inconvenience!

However, the issue still persist. Kindly ask you to read my post again. If you don't believe me, make your own test. Download Magisk Manager 7.5.1 and patch this boot.img against forceencrypt. expected result is encryptable=/dev/.../metadata but instead the flag is gone, which breaks at least FDE (not sure about FBE). Same issue with your current zip, don't know who's glorious decision it was nor the reason for it, but it looks intentionally to me because it's the same bug in both projects.

apologizing to osm0sis for first addressing anykernel (was posting this from mobile while on the highway and the responsible script is named anykernel.sh, didn't have time to fully understand but meanwhile i do)
[Android Software Development] Zackptg5:
That was an intentional change to magisk a while back (I followed suit with the vendor fstab patches). When changed to encryptable, there was a lot of weird behavior on many roms such as camera not working, wifi going in and out, all sorts of goofy stuff. Most of that stopped since this change. Encryption should still work if you choose to use it though but best thing to do if you're planning on encrypting is to just rename the zip to remove the ForceEncrypt part from it to just not disable force encrypt in the first place
[Android Software Development] alecxs:
sorry for beeing noobish but most of the issues you claim are most likely caused by the fact that test users running custom roms without encryption at all, and just deleting forceencrypt flag definitely breaks FDE

at least, you should undo forceencrypt. regarding fileencryption i was wondering from the very beginning if this is replaceable with same flag (there is no chance to differ between FDE and FBE afterwards). For FBE it may work just deleting this flag completely (i don't know), but things will change again when it comes to (inline) FBE+Metadata encryption when keystore is at metadata partition

https://source.android.com/security/encryption/metadata

in any case i can barely see the benefit of deleting this flag without proper replacement, it's more like a cheat than a fix

btw i am using busybox-sel in my scripts since two years.. it is built against uclibc comes with multiarch installer and building bot. i even compiled libsepol libselinux for myself (just failed on cross-compiling so did on arm device) so it's not a big deal, no need to re-invent the wheel ;)
[Android Software Development] alecxs:
[MENTION=6037748]Zackptg5[/MENTION]

i can see now you have additional protection in util_functions.sh and as result the sed is never executed for encrypted userdata, so luckily your zip doesn't break encryption, it "just" removes the availbility to encrypt.

but side effect is, user MUST keep everything in right order 1. format userdata 2. disable forceencryption. otherwise fstab won't patched if userdata is currently encrypted

edit: its not a protection.. misunderstood "Encrypted data, keep forceencrypt" as override but it's just default setting when undefined :(

guess the same is true for magisk, except for the additional pitfall when Magisk Manager is used on unencrypted spare phone trying to patch against forceencrypt any boot.img from other phone - assuming it is an older device with fstab in boot in this rare case it breaks encryption :(

as workaround we should always set -> Advanced Settings -> Preserve force encryption (until next release fixed this)
[Android Software Development] Brun0ls:
Hello! Please, help me understand something...

I own one Xperia XZ1, currently using Stock everything, on 9.0.

I installed TWRP, and then magisk, and then AdAway apk, and after rebooting AdAway to apply the hosts file, I got bootloop. I went to TWRP to flash this patch here from this topic, but nothing helped.

Then, I flashed Sony's stock ROM again, TWRP, Magisk and this patch (Disable DM-Verity ForceEnc), and installed AdAway and now it applyed the Hosts file and everything works.

That's the expected result? Disable Dm-Verity and ForceEnc disables something that was causing bootloop after AdAway changed something?

By the way, I see to flash Disable DM-Verity and ForceEnc as the last flashable zip. But what if later I want to flash some other .zip? Will I need to flash this patch again?

Thanks!
[Android Software Development] alecxs:
wrong settings in AdAway. you have modified a system file (hosts), this prevents dm-verity from booting. AdAway has a systemless mode for this, it does overlay it's own hosts file without actually changing system hosts file (bind mount)
[Android Software Development] Brun0ls:
Thanks, this is Very interesting... I searched for my issue (bootloop after adaway) and i couldnt find nothing, so I guessed It was something about dm-verity.

Do you have any answer for my other questions? I find your reply Very valuable, and I found that setting about magisk you told.

Thanks
[Android Software Development] alecxs:
your guesswork was right it was dm-verity. it's about root in general - any change of system files should be avoided that's the main purpose of a systemless root method. this zip and magisk are redundant (regarding dm-verity and encryption), both changes are initial and permanent (once disabled it can not be activated), no need to install again (except you reversed back to initial state aka OTA-update)
[Android Software Development] Brun0ls:
You mean, I dont need this zip if I have magisk or what?

And oh, I got bootloop after wiping some built in apps with Titanium Backup... Why? Shouldnt I be abble to mod anything with no issues because I have this zip flashed?
[Android Software Development] amg314:
Titanium Backup is for backup primarily. To clean the system, call SDMaid.
[Android Software Development] alecxs:
[MENTION=5544288]Brun0ls[/MENTION] previous versions was a little more aggressive than Magisk and Magisk Manager can not patch files in vendor. AFAIK Magisk zip does not patch force encryption when you forgot to format encrypted data. That's why you may flash this zip afterwards

boot loops might not related to dm-verity because some system apps are required. you can figure out if dm-verity is the reason: instead of deleting apk you can pm hide --user 0 <pgkname> this way it will disabled
[Android Software Development] Technical:
I've renamed the zip file to just Disable_Dm-Verity.zip because I want to encrypt my phone afterwards.

I came from an encrypted phone, follow exactly the OP instructions and flash an AOSP rom over the stock one of Mi A3 phone.

The log into TWRP says:

Chosen/Default Arguments:

Keep ForceEncrypt: false

Keep Dm-Verity: false

Keep Disc Quota: true

I was expecting Keep ForceEncrypt: true (not false).

Now, when I try to encrypt the phone, it shows an android figure for 1-2 seconds, reboot into system, and nothing happens.

How can I encrypt my phone back?
[Android Software Development] alecxs:
have you patched your boot.img with magisk manager? then you must set -> Advanced Settings -> Preserve force encryption. try again with stock boot.img
[Android Software Development] Technical:
If patching is flashing Magisk, I've tested both situations: tried to encrypt without Magisk and after. Both failed.

When I enable the Preserve force encryption option in Magisk and reboot, the option is automatically disabled.

With stock, phone is encrypted. However, if I flash any AOSP ROM I need to disable dm-verity or I can't boot.

The problem though, is that when I can't encrypt the phone anymore.

Isn't renaming the zip file the way we should go for just disable dm-verity? Why it isn't working?

Many thanks for your help.
[Android Software Development] alecxs:
if keep ForceEncrypt: false once is done by AOSP, Magisk or this zip, it can't be undone. you must manually restore your fstab aka flash stock rom