Develop Bugs

[MIUI Device Team]Custom Recovery TWRP 3.0.0 (Build 20160304-CN) for Mi 5

http://en.miui.com/thread-245756-1-1.html
but maybe there is also an english version of TWRP ?!

p1nky said:
http://en.miui.com/thread-245756-1-1.html
but maybe there is also an english version of TWRP ?!
Click to expand...
Click to collapse
TWRP 3 supports themes & you can change language with the themes.......
http://forum.xda-developers.com/android/themes/theme-twrp-3-0-0-0-dark-stock-colors-t3310235

I hope to see an AOSP or CM for MI 5 one day.

I tried this version, but still mi5 have full data encryption by default you will not be able to read any partition with that recovery.
You should try this one who ask the encryption password :
https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api
Your 1st lockscreen password (in some case) is the password. PIN should work too.
If you had set a Pattern, you are in the ****.
Personally, I can't perform a backup because I don't know my password, and I didn't find a way to disable the encryption.
By the way, all version of twrp 3 are multilingual.
You don't need any theme.
Any ideas?

nesquix said:
I tried this version, but still mi5 have full data encryption by default you will not be able to read any partition with that recovery.
You should try this one who ask the encryption password :
https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api
Your 1st lockscreen password (in some case) is the password. PIN should work too.
If you had set a Pattern, you are in the ****.
Personally, I can't perform a backup because I don't know my password, and I didn't find a way to disable the encryption.
By the way, all version of twrp 3 are multilingual.
You don't need any theme.
Any ideas?
Click to expand...
Click to collapse
The Chinese guys have two TWRP one by GanFan and one by cofface.
I liked GanFan's version more, he also has additional files on his baidu cloud, have a look at it.
更新了V7.2.7用的禁止强制加密data和sdcard分区的补丁
Click to expand...
Click to collapse
Google translated: Updated V7.2.7 patch used to encrypt data and the prohibition of forced sdcard partition
Translating Chinese 1:1 isn't the best approach; but with some imagination that sentence could mean: updated 7.2.7 to prevent enforced sdcard partition encryption.
If you have time it might be worth to look into GanFan's work.
Link: http://www.miui.com/thread-3837936-1-1.html
---------- Post added at 10:37 AM ---------- Previous post was at 10:29 AM ----------

Do you think that I should be on 7.2.7 ROM to get this twrp perfectly working or the dev ROM 6.3.17 is good too? I'm on the 6.3.17 now with Unlocked BL.
Can you access sdcard files with GanFan recovery?
Thanks.
Edit :
I think yes, your link is for the same recovery that I shared with you on GoogleDrive. So, when I boot in, I cancel the password request, I can see that the recovery recognize all my partition when I try to make a backup, but all functions failed. No way to flash a file.
He can't read the SD card. So I think you should be on 7.2.7.2 to get this working. (GLOBAL ROM)

nesquix said:
If you had set a Pattern, you are in the ****.
Click to expand...
Click to collapse
i am in the same situation now. passwort is a pattern. not shure what i should enter as password
also i have not a real bootloader?!?! If i press volume_ up+power i only get a picture with a phone and connected or disconnected cable, but no option to boot recovery. Any Idea

Hi to all,
I have flash the cofface TWRP recovery, but I don't see the sdcard, and unable to mount data
Can someone help me?!
Regards
Ivan

Always is going back to Chinese, the English setting is not permanent.
Sent from my MI 5 using Tapatalk

spavian said:
Always is going back to Chinese, the English setting is not permanent.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Same happened to me. The first few times it went to chinese then all of a sudden it stuck

Yeah, same to me, after I disabled encryption it's stayed on English.
Trimis de pe al meu MI 5 folosind Tapatalk

If I try to enter the twrp Recovery I always come to the screen where I see a Smartphone and a cable. The only way I can access the twrp is the command in fastboot Mode "fastboot boot *.IMG" Has anyone an idea how to enter twrp with vol+ and power?

dennis1401 said:
If I try to enter the twrp Recovery I always come to the screen where I see a Smartphone and a cable. The only way I can access the twrp is the command in fastboot Mode "fastboot boot *.IMG" Has anyone an idea how to enter twrp with vol+ and power?
Click to expand...
Click to collapse
I just hold vol up and power and it goes to twrp. Another way is to do it from the update app. There is an option to boot to recovery

An update to the TWRP has been posted here:
http://en.miui.com/thread-245756-1-1.html

dennis1401 said:
If I try to enter the twrp Recovery I always come to the screen where I see a Smartphone and a cable. The only way I can access the twrp is the command in fastboot Mode "fastboot boot *.IMG" Has anyone an idea how to enter twrp with vol+ and power?
Click to expand...
Click to collapse
The xiaomi mi5 factory recovery don't have interface , only a image of a smartphone and a cable.
You are already on recovery but is not usable, you need twrp .
They disabled the recovery interface for security reasons...

Guys, here you can find the official twrp for our Mi5, no bug sobfar, because the last one was still buggy with the touchscreen, here you can backup a lot of secret partition... ( almost 30+), and when you wanna make a backup of your data, he read correctly what he need to backup, not the entire SD... just try.....
https://www.androidfilehost.com/?fid=24499762636006354

This one still could not decrypt my data partition.

[Guide][Mi 8 Lite](Global) how to install TWRP + root with Magisk

Disclaimer :
YOU are choosing to make these modifications
and YOU are the only one responsible for any damages done to your device
==== Notes/Prerequisets/Links ====
* you should have already unlocked your bootloader (if not then start the process as soon as possible because it's going to take a while).
* backup your stuff, make sure you have sufficient charge just in case anything went wrong.
* download the unoffical TWRP port from Here (get the latest version)
* get the latest magisk from Here
* install device usb drivers
* set up fastboot properly Method A, Method B (using chocolaty)
- - - - - - - - - - - -
instructions :
1- shutdown your device completely.
2- enter fastboot mode by pressing and holding the Vol Down + Power Button button until you see xiaomi's mi bunny with a blue "fastboot" text underneath it.
3- connect your device to your pc via usb cable.
4- on your pc check if you have fastboot configured properly and your device recognized by typing:
Code:
fastboot devices
if it's detected then you're good to proceed to the next step.
5- flash the twrp recovery image by using the usual fastboot commands.
Code:
fastboot flash recovery recovery.img
in our case it should look something like:
Code:
fastboot flash recovery recovery-TWRP-3.3.0-0517-XIAOMI8LITE-CN-wzsx150.img
6- unplug usb cable and hold the Vol up + Power Button (don't let go of the buttons untill the devices vibrates) and let it boot to the twrp recovery you just installed.
7- if you rebooted successfully, you should be at TWRP splash screen, if greeted with a slider slide it and continue.
8- in the main menu of TWRP, go to "Install" choose the magisk zip file you downloaded and flash it, when done reboot the device.
9- congratulations friend, you're now rooted and have TWRP as your recovery Happy Flashing :highfive:
- - - - - - - - - - - -
Optional : install Orange Fox Recovery from Here (Supports Encryption and MIUI OTA updates).
- - - - - - - - - - - -
2020-02-25 Last upated and working on MIUI Global Stable 11.0.8 Pie

just in case

Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!

antonioli84 said:
Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!
Click to expand...
Click to collapse
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/

malek_anas_97 said:
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/
Click to expand...
Click to collapse
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.

antonioli84 said:
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.
Click to expand...
Click to collapse
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting

malek_anas_97 said:
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting
Click to expand...
Click to collapse
Thanks for the reply.
What method did you use to change build.prop?

Can't find a similar guide for the Mi 8, is it the same process as for the lite ?

antonioli84 said:
Thanks for the reply.
What method did you use to change build.prop?
Click to expand...
Click to collapse
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop

webvan said:
Can't find a similar guide for the Mi 8, is it the same process as for the lite ?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=YI2CtIIPVaI

malek_anas_97 said:
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop
Click to expand...
Click to collapse
Thank you man. I would like to know if anyone can do the trick without root. I've bought a Mi 8 Lite for my wife and it would be nice to her receive the updates from Xiaomi and use the GCam the same way she receives in Mi A1.

malek_anas_97 said:
7- if you rebooted successfully, you should be at TWRP splash screen
you will be greeted with a slider slide it and continue
Click to expand...
Click to collapse
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.

Official Xiaomi Mi 8 Lite (Platina) telegram group 24/7 support and latest ROM news posted here first!
Rules :
1 - English only.
2 - Be polite.
3 - Don't spam.
Gp Link : https://t.me/joinchat/DXcdlA0r5XYI-ooJlO8IlQ
Please Join

chan200606 said:
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.
Click to expand...
Click to collapse
to this point i don't really understand how encryption works on this device
it's on by default i guess
so what i finally did the other day to be kinda sure of what's happening
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
get it from here https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
(make aure to read the first post)
then formatted data
after that the booted up and i set it up normally
and then booted to twrp again to flash latest magisk
now when i check if my device is encrypted using this adb command "adb shell getprop ro.crypto.state"
i get "unencrypted"
so i guess it works? i don't know lol

malek_anas_97 said:
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
Click to expand...
Click to collapse
It looks like your phone was not encrypted (or was encrypted with MIUI's default password) when you flashed TWRP, as you had clean flashed stock then set up without setting security. That you could start TWRP to flash "dm versity and encryption disable", without being asked to input a password first, shows that TWRP was able to handle the default encryption (or no encryption) of the clean MIUI install.
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
In hindsight I should have just done the minimum setup after the phone was wiped by the bootloader unlocking process before installing TWRP. I guess that unless there is another version of TWRP out that can handle the screen PIN encryption, my only option is to wipe clean the phone so that I can repeat what you did. However, now that I have reinstalled everything on the phone, I am a bit reluctant to do this just to get root. I think I will wait until there is an AOSP ROM available and do the wipe/format at the time of switching. Hopefully I don't have to wait too long!

chan200606 said:
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
Click to expand...
Click to collapse
An update: I've now got over this encryption thing. It is indeed the screen PIN that was causing me problems. While I had tried removing the PIN and all fingerprints last time, I had powered down the phone immediately after removing the PIN and booted into fastboot mode. Today I thought I better try it one more time: after removing the PIN, reboot the phone to system first before powering it down and restarting in fastboot mode. This cycles the phone system at least once without the PIN so hopefully any traces of the PIN would really be wiped. And indeed it works - the booted TWRP (i.e. not flashed to phone) has no problems reading my phone and I could install Magisk.
So I now have stock recovery + Magisk on my Mi8 Lite, which is the minimum I wished to do to it. Maybe at a later date I would flash TWRP onto the phone as well.

i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?

Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.

kax001 said:
i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?
Click to expand...
Click to collapse
i really have no idea why this is happening to you
i searched online and it seems like you're not the only one having this

vonclutch said:
Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.
Click to expand...
Click to collapse
yeah i know there's no problem in turning the phone off then rebooting manually with the buttons
but i was talking about using "fastboot reboot recovery" command to reboot to recovery from fastboot directly
anyways glad everything worked for you friend : )

OP3T : Why boot twice each startup ?

Hi,
I have a friend who buy a oneplus 3T (second hand), and I have a oneplus 5.
I noticed a strange difference between these both devices. Indeed, when oneplus 5 is booting, there is the oneplus logo, then the oxygenos logo, then the lockscreen (normal).
But when the oneplus 3t is booting, there is the oneplus logo, then the oos logo, then we need to enter password, then there is oxygenos logo again, and finally there is the lockscreen and we need to re-enter the password (pin).
Futhermore when open twrp on the OP3T, we need the password, then we can read "fail to mount storare" and twrp boot up and works fine after that.
Both of them are secure with pin and sim card pin are disabled.
OP 3T : oos 5.0.7, magisk 18.0, encrypted
OP5 : OB22, magisk 18.0, encrypted
So I dont understand what goes wrong on the 3T, is it normal or do I need a factory on something else?
Sorry for my bad English,
Thanks

Androrax said:
So I dont understand what goes wrong on the 3T, is it normal or do I need a factory on something else?
Thanks
Click to expand...
Click to collapse
Perfectly normal.
OP3/T uses Full Disk Encryption (FDE). OP5 uses File Based Encryption (FBE). The latter is also known as Direct Boot, and for good reason. As the name implies Direct Boot allows you to get straight to the Lockscreen before having to enter any security. That's because with FBE the files needed to Boot the phone don't need Decrypting. As you can see, it's more convenient that way and the startup procedure is less janky.
With FDE on the OP3 you can't do anything until security is entered so you get the Boot prompt to Decrypt and then a Fingerprint on the Lockscreen to unlock the device. (You'll notice on the OP5 you always have to enter a PIN/Password on the Lockscreen after a reboot. That step is on Boot with the OP3).
For Encryption to be secure with the OP3, you have to have your security, whether a PIN or Password, set to prompt you at Boot. This is an option during the Initial Setup of the device when you set your security stuff. It always prompts you to add that security at Boot. Same too if you now remove your PIN in settings and set a new one. You obviously said yes to this prompt as you have on-boot security.
If you had said 'No' you would Boot straight to the Lockscreen, same as the OP5, and would have to enter PIN/Password instead of just Fingerprint on the Lockscreen. It's a big security hole that way though as someone could remove your Lockscreen security from TWRP and gain full access to your phone. This is why you need on-boot security with FDE.
With TWRP:
OP5 - You should get prompted for security by TWRP when you try to load it. If not, something is wrong.
OP3 - With on-boot security:
You will have already entered your security so you are decrypted and TWRP will then load without additional prompt.
OP3 - Without on-boot security:
TWRP will use default_password to decrypt and load automatically. This is a problem as anyone with physical access to your device can use TWRP to remove your Lockscreen security and boot into your phone.
TL;DR:
1) On-boot security is essential when using FDE, even if the bootup sequence is horrible.
2) FBE is superior in that you can boot straight to Lockscreen and TWRP is protected if someone boots to Recovery.

Wow, thank you very much for this very comprehensive answer.
I am reassured now

Phone stuck in Fastboot after wiping data from MIUI 10

Hi, new to the forums.
I downloaded MIUI 10 recovery rom (based on Android 9) and flashed it with TWRP. It booted to MIUI as normal, but I changed my mind and wanted to flash MIUI 11 recovery rom (still based on Android 9) instead. I normally set a pattern lock before rebooting into recovery but this time i forgot. This time it rebooted into MiRecovery3.0, then I wiped data from that menu thinking it would bring me to TWRP...now Im stuck with MiRecovery and cant even load MIUI 10 rom. All id like to do is to get TWRP back and flash my MIUI 11 then flash Magisk like I always do.
I tried
HTML:
.\fastboot.exe flash recovery twrp.img
but I keep getting FAILED (write to device failed(unknown error))
Then I realized I normally set the Pattern lock AND turn on USB debugging...but this time I wiped data before either of these things could be done...bad move ugh
Unlocked bootloader before all this happened but some threads say I might have relocked it?
I tried everything, please someone help!
My device is Global Rom.
Adrian

voidturbulence said:
Unlocked bootloader before all this happened but some threads say I might have relocked it
Click to expand...
Click to collapse
Check with:
>> fastboot oem device-info
"fastboot" is equivalent to "./fastboot.exe"

I did that earlier and it said error too many threads or something similar and immediately kicked my device out of fastboot. I can double check when I wake up if needed?
And surprise, I left it on the charger and it booted back into MIUI all by itself . I checked developer settings and it says bootloader already unlocked with the greyed out slider. However, I still get the same unknown error when flashing twrp..
I did .\fastboot.exe devices and it detects the device but it just kicks me out of fastboot with that unknown error when I try flashing hope I can get twrp back
Edit : this time as soon as I saw MIUI I turned on USB debugging and set a Pattern lock! But still got the error after

voidturbulence said:
I did that earlier and it said error too many threads or something similar and immediately kicked my device out of fastboot. I can double check when I wake up if needed?
And surprise, I left it on the charger and it booted back into MIUI all by itself . I checked developer settings and it says bootloader already unlocked with the greyed out slider. However, I still get the same unknown error when flashing twrp..
I did .\fastboot.exe devices and it detects the device but it just kicks me out of fastboot with that unknown error when I try flashing hope I can get twrp back
Edit : this time as soon as I saw MIUI I turned on USB debugging and set a Pattern lock! But still got the error after
Click to expand...
Click to collapse
I don't know why you need a Pattern lock - I absolutely never use it and flash from Fastboot or use TWRP with no problem (fingerprint, pin or nothing)
Ofc, USB debugging must be enabled

just tried the oem unlock command in fastboot, I got unknown error again, then kicked me out of fastboot.
i set the pattern lock cause i remember one time i didnt set one, so when I went to TWRP to flash a rom, folders were encrypted and i couldnt find the rom file. and i didnt have an otg adapter at the time. when i set the pattern i could enter the pattern in TWRP and view my decrypted folders and find the rom easily. now that i think of it does encryption actually stop me from pushing the rom with adb and somehow flashing it?
still new to all of this
edit: my only saving grace is the USB 2.0 hub arriving at my house today, and this thread... fingers crossed

voidturbulence said:
just tried the oem unlock command in fastboot, I got unknown error again, then kicked me out of fastboot.
i set the pattern lock cause i remember one time i didnt set one, so when I went to TWRP to flash a rom, folders were encrypted and i couldnt find the rom file. and i didnt have an otg adapter at the time. when i set the pattern i could enter the pattern in TWRP and view my decrypted folders and find the rom easily. now that i think of it does encryption actually stop me from pushing the rom with adb and somehow flashing it?
still new to all of this
edit: my only saving grace is the USB 2.0 hub arriving at my house today, and this thread... fingers crossed
Click to expand...
Click to collapse
For unlocking Bootloader you need to use their miflash_unlock PC program, not fastboot oem unlock command
So you mean pin/password, not the (graphical) pattern
If you disable pin/password, TWRP will not ask you but it should still know 'default' one to properly read/write to Storage

zgfg said:
For unlocking Bootloader you need to use their miflash_unlock PC program, not fastboot oem unlock command
So you mean pin/password, not the (graphical) pattern
If you disable pin/password, TWRP will not ask you but it should still know 'default' one to properly read/write to Storage
Click to expand...
Click to collapse
sorry i meant i typed oem device-info and I still got the unknown error and got kicked out
edit: also do you mind clarifying default, cause all i saw was the random numbers and letters as folder names and i know that once I entered my pattern in TWRP the issue was gone...did you mean storage/emulated/0?

voidturbulence said:
sorry i meant i typed oem device-info and I still got the unknown error and got kicked out
edit: also do you mind clarifying default, cause all i saw was the random numbers and letters as folder names and i know that once I entered my pattern in TWRP the issue was gone...did you mean storage/emulated/0?
Click to expand...
Click to collapse
USB 2.0 hub worked !! Android 9 based MIUI 11 rooted with Magisk on 84hz refresh rate...mindblowing.
Thanks for the help

voidturbulence said:
USB 2.0 hub worked !! Android 9 based MIUI 11 rooted with Magisk on 84hz refresh rate...mindblowing
Click to expand...
Click to collapse
Glad that you fixed.
Do you really see a difference with 84hz - and you downgraded because of not working with MIUI 11/12, Android 10?
voidturbulence said:
edit: also do you mind clarifying default, cause all i saw was the random numbers and letters as folder names and i know that once I entered my pattern in TWRP the issue was gone
Click to expand...
Click to collapse
Screen unlock Pattern is graphical one (see a screenshot), aren't you talking about pin/password
Data partition is File Based Encrypted (FBE) with ICE:
https://www.qualcomm.com/media/documents/files/file-based-encryption.pdf
You can see that if you open /vendor/data.qcom (textual file but root required)
Even if you don't set screen unlock protection, ICE still uses a key unique for your device and TWRP can also decrypt Storage on boot with 'default' password - see a photo from TWRP

zgfg said:
Glad that you fixed.
Do you really see a difference with 84hz - and you downgraded because of not working with MIUI 11/12, Android 10?
Screen unlock Pattern is graphical one (see a screenshot), aren't you talking about pin/password
Data partition is File Based Encrypted (FBE) with ICE:
https://www.qualcomm.com/media/documents/files/file-based-encryption.pdf
You can see that if you open /vendor/data.qcom (textual file but root required)
Even if you don't set screen unlock protection, ICE still uses a key unique for your device and TWRP can also decrypt Storage on boot with 'default' password - see a photo from TWRP
Click to expand...
Click to collapse
Yes, when i used the graphical screen unlock it then showed me all the proper folder names, but before that it was all encrypted. if what youre saying is true then i might have not even entered phone setup far enough to skip screen unlock protection? i might have just immediately restarted to recovery while skipping usb debugging entirely...long nights i am sleepy lol
and 84hz is amazing, the phone feels so much more premium. I would do Android 10 based MIUI 11 but after seeing posts about getting bootloops with 84hz or other glitches I was scared off. once i go 84hz couldnt go back. also want the latest softwares with 84hz, but Android 9 based MIUI 11 seems to be farthest i can go. 84hz MIUI 12 Android 10 is the dream of course

Question How to Permanently decrypt mi 11x?

When I Use Twrp the data folder automatically locks itself and I tried many passwords but it won't open. Then I delete all the data and flash new rom with decrytion file flashing but still the decrytion is temporary and whenever I update my custom rom it strucks in boot loop... I want permanent Decryption someone please help to decrypt my Mi 11x.

AFAIK there is no way around this. You must flash DFE (Disable-Force-Encryption) after every update to avoid bootloops/encryption.
(in my experience, if I forget to re-flash DFE after an OS update, it just doesn't start anymore, only bootloops.)
This is because OS Updates replace system-files, including the text-file which, by default, contains the line for AES-encryption.
I think the DFE-Mod sets the system to read-write (if it's read-only), and removes the AES-encryption argument in a specific text-file.

cyanGalaxy said:
AFAIK there is no way around this. You must flash DFE (Disable-Force-Encryption) after every update to avoid bootloops/encryption.
(in my experience, it just doesn't start anymore, if I forget to re-flash DFE after an OS update)
This is because OS Updates replace system-files, including the text-file which, by default, contains the line for AES-encryption.
I think the DFE-Mod sets the system to read-write (if it's read-only), and removes the AES-encryption argument in a specific text-file.
Click to expand...
Click to collapse
Is there any way to know my data encryption password because if I know it I do not need to decrypt it using file anymore?

Ishan.Sharma said:
Is there any way to know my data encryption password because if I know it I do not need to decrypt it using file anymore?
Click to expand...
Click to collapse
Oh yes, I remember now. You are using Android 12, yes?
Use "TWRP skkk", it's a special version that supports Android 12's Encryption.
I think OrangeFox also has a version that supports Android 12's Encryption...
YouTube Video:
Download Link for unofficial TWRP skkk: https://dl.akr-developers.com/?dir=skkk/TWRP/A12
I found both the video and the download link from here: https://forum.xda-developers.com/t/...p-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463/
I use it myself and it works.

cyanGalaxy said:
Oh yes, I remember now. You are using Android 12, yes?
Use "TWRP skkk", it's a special version that supports Android 12's Encryption.
I think OrangeFox also has a version that supports Android 12's Encryption...
YouTube Video:
Download Link for unofficial TWRP skkk: https://dl.akr-developers.com/?dir=skkk/TWRP/A12
I found both the video and the download link from here: https://forum.xda-developers.com/t/...p-3-6-0_11-v2-9-3_a11-alioth-skkk-is.4373463/
I use it myself and it works.
Click to expand...
Click to collapse
Ok thanks

I bought my poco few months ago and it is still locked, with my old phone i removed the encription simply formatting (not wiping) the internal storage with TWRP. Is this still working with the poco?

massima said:
I bought my poco few months ago and it is still locked, with my old phone i removed the encription simply formatting (not wiping) the internal storage with TWRP. Is this still working with the poco?
Click to expand...
Click to collapse
No, Android encrypts the data-partition using AES-algorithm on first boot, unless before the first boot you flash a script that removes the Encryption-argument.