yashsingh1/xdaforums huggingface dataset:
[Android Software Development] icecandle0:
Using Tools ALL IN ONE, I succeeded in decryption, but no apps can access /sdcard (probably this situation https://xdaforums.com/oneplus-6/help/oneplus-6-lost-access-to-internal-t3941351) I flashed OOS, TWRP, rebooted into twrp, then flashed magisk 19.4, radioactive kernel, dm-verity. I think the SD card is corrupted, I can only move files from my computer in recovery mode, and they are in /storage/emulated/ (no 0 folder)
[Android Software Development] Aussiegeek420:
Hi would i need to use this every time i flash new firmware and wanna root phone or once i use this I'll never need to use again?
[Android Software Development] death_jax:
Yes, every time you flash a firmware you have to flash both root and, only at last, zip in the OP.

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] death_jax:
This is what is described in the OP:

In my experience with my phone, my advice for your request is that you should first of all format data and internal storage, flash ROM (in TWRP or stock recovery, based on your phone model) and nothing else, then perform a full reboot until you are on the Android start screen (language selector, wifi, etc.), once there reboot the phone and then follow the following steps.

Based on your phone model, if your phone can boot TWRP img from fastboot:

- from fastboot, fastboot boot TWRP img

- flash TWRP installer zip

- format data and internal storage (NOT the wipe option, it's different!!)

- reboot to TWRP

- flash everything, kernel, root (better latest Magisk v20.4 instead of v19.4), etc.

- at last flash the zip in the OP

- reboot and wait

If your phone model can't boot TWRP img from fastboot :

- from fastboot, flash recovery TWRP img

- reboot to TWRP

- format data and internal storage (NOT the wipe option, it's different!!)

- reboot to TWRP

- flash everything, kernel, root (better latest Magisk v20.4 instead of v19.4), etc.

- at last flash the zip in the OP

- reboot and wait

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] icecandle0:
Thank you! I have some questions, I've seen cases where people flash OOS and TWRP twice in other guides. What's good about doing that? Also what exactly does Format Data erase?

Edit: I followed your instructions, and I can't see the unicode characters (Pretty critical because I can't receive any important news rn). I put rom in /sdcard, but it is not detected by local upgrade. I cannot delete/save anything on storage in system, rebooted the phone to find out installing apps has become impossible
[Android Software Development] death_jax:
For this question I don't know, you may ask in the forum section about your phone model.

Wipe option only erases all files inside a partition (without formatting it); format option, instead, formats the partition (recreate the structure), obviously erasing all inside it, but this step helps in order to recreate/remove data encryption; it depends on the steps you will follow.

What did you mean that you can't see unicode characters, and where?

However, for the reason I described above, why you put ROM into sdcard?! Haven't you the external SD card slot?

When you followed the steps to format data (that is /data partition) and then internal storage (that is /data/media), this one will exactly format sdcard!! You should first of all put ROM and other zips into external microSD, and then start again all steps from the very beginning.

My advices now are that you should flash the ROM, FORMAT data and internal storage and perform a full reboot until you are on the Android start screen (language selector, wifi, etc.), reboot and then follow next steps described in my last message. I advice you to do this because, in this way, the system recreate the encryption that you are going to remove following the next steps.

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] icecandle0:
https://xdaforums.com/oneplus-6t/help/strange-emoji-issue-op6t-android-10-t3996671/amp/ like this but for every unicode character.

I adb pushed all the zips before flashing, I have no idea what's the 'external sd card' you are talking about
[Android Software Development] amg314:
After data area formatting via TWRP all pushed zips are gone. You should push them to external microSD card (if it any)
[Android Software Development] icecandle0:
OnePlus 6 does not have microSD card slot, so I copied flashable zips to my phone after formatting to flash them
[Android Software Development] death_jax:
Ok, for this reason I ask you if you have external microSD slot or not.

In your case, I advice you to start from very beginning sideloading ROM through adb in order to install it, format data and perform a full reboot until you are on the Android start screen. Then reboot to TWRP, format data, reboot to TWRP and flash only the zip in the OP, without flash Magisk or other zip in that moment and perform a full reboot until you are on the Android start screen. Then reboot to TWRP, copy your zips in the sdcard and flash it, kernel, others, etc., then Magisk 20.4 and, at last, the zip in OP (yes, again).

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] amg314:
One can also use OTG card)
[Android Software Development] death_jax:
Obviously, if he have an OTG adapter and knows how to perform the steps with it, he can use it in substitution of external microSD card.

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] icecandle0:
If the partition structure is re-created when formatting the data, wouldn't OOS or TWRP be erased? Rebooting to twrp after format only worked once for me, and I don't understand what the principle is.
[Android Software Development] death_jax:
There are many partitions on a phone, not only one!! Boot partition, recovery partition (some newer phones, like mine, have recovery incorporated into boot partition), data partition, system partition, etc.

If you flash OOS or other ROMs they will be flashed into correct partitions, but not in random ones or in data partition; will be flashed in boot, system, etc.

If you flash TWRP img to recovery (or boot, like me), means that you flash that file to recovery partition (or boot, like me).

Data partition containing data, for example: if you reset your phone to fabric when you are in Android settings, do you have to flash ROM again? NO!! It is the same thing as formatting data partition, but we format it when we are in TWRP because only in this way we can remove force encryption from our phone!!

In simple words, if you format data will not lose ROM or TWRP, but only their configurations!!

I hope it is clearer now :)

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] icecandle0:
My guess is that as I format the data, all the files inside the sdcard are gone, causing the problem I mentioned earlier (no files can be downloaded). And there were times when TWRP and OOS were gone, so I had to flash them again.
[Android Software Development] death_jax:
Maybe you didn't follow exactly step to step the guides and hints in previous posts, or maybe you should ask live help from those with more skills, because I think you did not understand well what I wrote in that guides :(

Inviato dal mio Nokia 7 plus utilizzando Tapatalk
[Android Software Development] icecandle0:
Okay, thanks for trying to help me anyway
[Android Software Development] vadimkara:
Realme X2 Pro Android 10/Q stock ROM

1. Flashed TWRP

4. Install your Zip (definitely the last to flash)

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

Got any idea with this?

Thank you in advance
[Android Software Development] fabrizio b92:
Questions guys:

1)Works on htc u12+ with pie stock, twrp and magisk 20.4?

2)instruction flash:Backup(optional), (custom)rom, magisk and last this script right?

3)after flashing this script it could create problems with NFC payment(Googlepay)?

I use several time my smartphone to pay via contactless and i don't want give up paying in this way

Thanks a lot
[Android Software Development] yoda_dmitry:
Turning on the encryption

Hi. Is it any way now to turn on the encryption without loosing the phone data? Because I need to ecnrypt external SD-card, but android does not start the real encryption, just showing the checking SD-card message for many hours.

Samsung A40
[Android Software Development] rumcum:
Congratulation

After hours of work, you helped solve my problem. You deserve a lot of credit. Now I'll be able to upload a new twrp and make an upgrade to AOSP10 in my good Xperia xz.

Thanks a lot. :victory:
[Android Software Development] greeneyez15o:
???I've been using that same one on all my devices, no issues yet.???
[Android Software Development] fabrizio b92:
Thank you for your reply

So confirm no poblerm with google pay nfc payment?

Thank a lot :o:D
[Android Software Development] Zackptg5:
That's all about paying safety net. There's separate thread on that cause it's a complicated topic but currently, if you use magisk, you'll probably be fine
[Android Software Development] WololoadRaider:
TLDR: Hi, should this work on a Xiaomi Redmi Note 5 to disable DM Verity and disable enctryption?

I own this Redmi Note 5 Pro with with MIUI 11.0.3.0 and was able to do this without problem before. I'm trying to use the Smali Patcher utility to generate a module but I constantly keep on getting errors. First, with debugging enabled and having selected TRANSFER FILES before rebooting the phone when connected it to the PC before entering Fastboott, I got this:

"fOmey @ XDA

Patcher version: 0.0.6.7

==> Detected java: 1.8.0_251

!!! ERROR: No ADB devices found."

I asked in the post of the utility and got advice to try to copy the framework folder so someone else could use the Smali for me but couldn't even get through the first step as I get no device attached when checking with "adb devices" so "adb shell" gives me "error: no devices/emulators found" either at fastboot or at TWRP mount with Cache and System mounted (a detail is that I see no "data" to mount). When I check "adb devices" I get "adb version (41) doesn't match this client (39); killing".

Also, as soon as I boot into TWRP, i get asked for a password.

I had installed the adb drivers and I had tried my phone screen unlock pin, and also disabling the screen lock without luck. Also tried already wiping and formating data, that allows me to mount data but still no luck with Smali.

Tried to copy the framework folder but I can't find the internal storage to copy it to because the data encryption doesn't allow me.

After that, I just tried using an external SD card to transfer the framework folder from TWRP, and I got this response..

"""Failed to decrypt data.

Unable to decrypt with default password. You may need to perform a Format Data.

Updating partition details...

...done

Unable to mount storage

Failed to decrypt data.

Full SELinux support is present

Unabe to mount /data/media/TWRP/.twrps cd "/system/framework" && cp -R "/system/framework" "/external_sd" process ended with ERROR: 1"""

To mount data I get an encryption password that it asks for everytime. I have formated the data partition many times in these attempts as it only works if I try to do anything with it instantly. If I boot to system, boom, encrypted again without any reasonable password to decrypt it.

Also tried to copy the framework folder right after a data format but got the same "ERROR: 1" as before.

The latest response I got on that forum was that...

"If that is the case, you need to flash a file to disable dm-verity and force encryption before booting. Search in your device forum."

I got an old DM verity zip from 2018, I tried using that after data format and got the same ERROR 1. Do I need a new one or do I need a new one which also decripts? Help, I'm completely lost already
[Android Software Development] alecxs:
use Orange Fox it works with encryption

https://xdaforums.com/showthread.php?t=4064291

https://miui.blog/redmi-note-5/flash-orange-fox-whyred
[Android Software Development] PRInCEI7:
Why can't I edit ROM Amazon fire hd 8 8gen {karnak] Lineage-16.0. v p pic 9 Android

By the way when installing any program inside a path /system/priv-app/ not boot the device ?

By the way I used

Universal DM-Verity, ForceEncrypt

And

Magisk

I mean when I move any apk app to /system/priv-app/ .. device boot loop

link

recovery.LOG

http://www.mediafire.com/file/2f0uy5jrsv72ceh/recovery.LOG/file
[Android Software Development] PRInCEI7:
[MENTION=6037748]Zackptg5[/MENTION]

I need help ?

---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------

[/COLOR [MENTION=6037748]Zackptg5[/MENTION]

I need help ?
[Android Software Development] Uvneshkumar:
[MENTION=6037748]Zackptg5[/MENTION], Flash error in Realme X2 Pro, Realme UI.

Here is the recovery log https://pastebin.com/N5ML4xdy
[Android Software Development] vegetaleb:
Should I follow the same steps for oneplus 7 Pro?
[Android Software Development] Ronnie_180808:
I have decrypted Oneplus 7(latest beta OOS) and I've understood the use of this zip pretty clearly. I just have one query; say I rebooted to recovery without any purpose of flashing any sort of zips or without the purpose of changing slots(which I know is, anyway, not recommended unless upgrading), in short without any purpose at all; hence afterwards do I need to flash this dm verity zip before booting back to system so as to maintain decryption?
[Android Software Development] m-Khadem:
I do all things on my zenfone 4 ze554kl but still on fastboot loop (used several options when installing this zip file, I mean encryption and not encription options).

can anyone help me to fix my device? it is on fastboot loop after reset all settings and data from inside of android !!!

note:

- I have access to fastboot surely

- I can install twrp 3.1.1 'Shakalaka'

- I can erase all things via fastboot

- I can install original recovery

---------- Post added at 10:56 PM ---------- Previous post was at 10:56 PM ----------

I do all things on my zenfone 4 ze554kl but still on fastboot loop (used several options when installing this zip file, I mean encryption and not encription options).

can anyone help me to fix my device? it is on fastboot loop after reset all settings and data from inside of android !!!

note:

- I have access to fastboot surely

- I can install twrp 3.1.1 'Shakalaka'

- I can erase all things via fastboot

- I can install original recovery
[Android Software Development] Determination Filled:
The Redmi K30 Pro or Poco F2 Pro can't stay decrypted, any solution please?

---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------

The Redmi K30 Pro or Poco F2 Pro can't stay decrypted with the Disabler, any solution please?
[Android Software Development] death_jax:
If you decrypt MIUI you may have various problems, better to stay crypted.

Inviato dal mio Mi 9T Pro utilizzando Tapatalk
[Android Software Development] Determination Filled:
I need that to avoid sometime a bricked device caused by the ROM Dirty flash Update, my K20 Pro runs on MIUI eu with DM-verity Disabler to stay decrypted, works perfectly on that matter
[Android Software Development] TapaSte:
is there way to test if a given Android system is crypted or decrypted ?

Sent from my Redmi Note 8T
[Android Software Development] death_jax:
What is you device, the Redmi Note 8T?

For me (MIUI 11) is in:

Password and Security -> Privacy -> Encryption and credentials -> Encryption

Once there, there is the item "Encrypt Phone" and under it you can see Encrypted or Decrypted (or maybe Not Encrypted).

PS: I have italian UI, sorry if some menu items name may differ from my translation.

Inviato dal mio Mi 9T Pro utilizzando Tapatalk
[Android Software Development] TapaSte:
I'm running on MMX... and have found it in a similar submenu.

p.s. I'm Italian, too, even my ROM is set on English language, only because the translation is not so good. ;)

Sent from my Redmi Note 8T
[Android Software Development] HippoMan:
I want to make sure that I am properly understanding everything, so that I end up doing the right thing for my device.

My goal is for my phone to end up being non-encrypted, so that if I take nandroid backups and reflash my device with a new ROM or have to unbrick it via the MSM tools, I could still restore my backups and get back to my original ROM, if I choose.

Could someone confirm that all of my following assumptions are correct? ...

I have a OnePlus 7Pro, which I believe would be considered a "Slot device", to use the terminology that I have read here.

Correct?

On my device (a GM-1917 which is currently running OOS 10.3.3 and is currently rooted with Magisk 20.4), in Settings -> Encryption & credentials, in the ENCRYPTION section, it states

Encrypt phone
Encrypted

Therefore, I assume that that my phone is indeed currently encrypted. Correct?

I assume that I would then have to take the following steps in order to un-encrypt my device:

1. In TWRP, take a nandroid backup of boot, system, and data.

2. Save this backup to somewhere off of the device, such as my PC.

3. Format /data

4. Reboot back to TWRP

5. Flash my current ROM again.

6. Reboot into TWRP.

7. Flash Magisk.

8. Flash the kernel I'm using: Smurf

9. Flash this zip, with "forceencrypt" added to the name.

Are these all of the correct steps?

And another question ...

In step 1, above, will that nandroid backup be restorable after I complete steps 2 through 9? That backup will be taken on an encrypted device, and so I'm concerned that it will be unreadable if I decide to restore back to my current state after a reflash or after reinitializing via MSM tools. Is that correct? If so, then how should I take the backup in step 1, so that I can actually restore it, if needed?

Thank you very much in advance.

.​
[Android Software Development] alecxs:
correct. But basically you just have to format userdata and flash the zip (disabler or magisk). the zip will detect and decide encryption state itself

1. backup boot+system+vendor for ROM + data for apps. if you restore this backup it will undo steps 2-9. backup itself is not encrypted (at least if twrp decrypted userdata successful)

2. don't forget adb pull -a /sdcard (pictures not included in backup)

5. not necessary. advanced restore only /data + /sdcard instead

8. not necessary if already running custom kernel

9. not necessary because magisk already does the same patches against encryption and dm-verity
[Android Software Development] HippoMan:
Thank you very much. This is very helpful!

I have some follow-up questions ...

When you say "flash the zip (disabler or magisk)", are you talking about the same zip file ...

Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ?

Or is that only TWRP-installable, and is there perhaps a different module to flash via Magisk?

Also, concerning item #1: how do I know if TWRP's decrypted userdata is successful? How can I check this?

In my settings, it states that my device is encrypted, so I am guessing that my userdata is currently encrypted (i.e., not currently decrypted).

But when I now go into TWRP (before performing any of these outlined steps), is TWRP itself already somehow managing the userdata in a decrypted manner?

I've always been confused about this point.

For item #5, how do I perform an "advanced restore only /data + /sdcard"?

I don't see such an option in TWRP, but I could easily be missing something.

Could this simply be a restore in TWRP of only /data from my recent backup, followed by an adb push to /sdcard of everything that I previously saved via adb pull -a /sdcard ?

Thank you again for all your help!

UPDATE:

In Magisk under "Advanced Settings", I see that "Preserve force encryption" and "Preserve AVB 2.0/dm-verity" are checked by default.

Is it the case that I just need to uncheck both of these instead of flashing the disabler zip in TWRP?

If so, where in the series of steps outlined above should I do this?

.​
[Android Software Development] alecxs:
#1: be aware of the terms encrypted decrypted unencrypted then it becomes more clear. the only way you can check is try&error. boot into TWRP and browse your files with advanced - filemanager. if you can see plain files in /data/data your TWRP does support encryption and has successful decrypted your encrypted userdata. you can backup files but device remains encrypted. the only way to become unencrypted is to format userdata (and restore files) ;)

#5: exactly

UPDATE: exactly, but this concerns Magisk Manager. steps are for Magisk (install button in TWRP) therefore not related. use Magisk Manager for devices without TWRP

#9: AFAIK Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip will ask you for the same and you can select with Volume Buttons. Magisk-v20.4.zip will autodetect. it does not harm if you flash both because Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip is based on Magisk-v20.4.zip and does the same patches (but without actually installing Magisk)
[Android Software Development] HippoMan:
Thank you again, very much. I think I mostly understand now. So could you confirm whether these are indeed the correct steps?

1. In TWRP, take a nandroid backup of boot, system, vendor, and data.

2. From my PC, do an adb pull /sdcard/ my-saved-sdcard-data. This will also download the TWRP backup I just took, since the TWRP directory resides in /sdcard.

3. Format /data

4. Reboot back to TWRP.

5. From the PC, do an adb push my-saved-sdcard-data /sdcard/. This will restore my sdcard as well as the TWRP backup.

6. In TWRP, do a nandroid restore of the backup I took, but only restore the /data partition.

7. Reboot into TWRP.

8. Flash Magisk

9. From the PC, do an adb push Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip /sdcard

10. From TWRP, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from /sdcard.

Also, in TWRP, I have just now gone into Advanced->Terminal and examined some files on /sdcard. I am indeed able to properly see and read them, so I can deduce that TWRP has successfully decrypted the encrypted userdata ... correct?

Now, one last question. Suppose I screw something up and my device gets bricked. Once I can get my device back to a clean state with a usable TWRP installed, can I simply do the following to restore myself back to the state I was in before I started any of this? ...

1. From the PC, do an adb push my-saved-sdcard-data /sdcard/.

2. That step will restore the TWRP subdirectory of /sdcard along with everything else under /sdcard, so then simply do a nandroid restore of the entire backup that I took originally (which contains boot, system. vendor, and data from my original configuration).

I just want to make sure that I have a path back to my current device configuration, in case I mess things up.

Thank you again for all your help.

.​