How To Disable Force Encryption ? - Xiaomi Redmi Note 7 Questions & Answers

So, Everytime Whenever I Flash A Custom Rom,My Device Gets Encrypted Automatically & Sometimes Roms Fails To Decrypt Data Even If I Type Right Password,if i flash another rom without formatting data. I tired dm-verity,force encryption & lazy flasher also but that doesn't woks,if there is anyway to fix it so pls help me out!

Now, I may not be much of help, but I think the encryption thing happens because you don't remove your saved fingerprints from the phone... OR it might be a TWRP bug, as the same thing happened to me when I wanted to switch from LOS back to MIUI; had to format /data & lose everything from the internal storage as no passwords worked in TWRP :crying:

Add pin as screen lock
jaxx08 said:
So, Everytime Whenever I Flash A Custom Rom,My Device Gets Encrypted Automatically & Sometimes Roms Fails To Decrypt Data Even If I Type Right Password,if i flash another rom without formatting data. I tired dm-verity,forece encryption & lazy flasher also but that doesn't woks,if there is anyway to fix it so pls help me out!
Click to expand...
Click to collapse
I had the same problem but when I set pin as screen lock the TWRP was able to decrypt my storage and everything is working!

From a telegram support group for redmi note 7:
// Encryption In Lavender //
Encryption is the process of translating plain text data (plaintext) into something that appears to be random and meaningless (ciphertext), when your device gets encrypted, it will ask for random password on startup and recovery, you cant access your internal storage and the only way to fix it is by formatting the data (doing this will also wipe your internal storage)
1) Changing from AOSP/LOS/CAF/GSI to MIUI or vice versa would almost certainly require formatting data
2) Changing from one custom ROM to another custom ROM may or may not require formatting data - see point number 3 below
3) On this device, there are different Pie encryption protocols, and they are not always compatible with each other. If you move from a ROM using a different encryption protocol from your current ROM, you will need to format data, because the pin/password will always be considered to be "wrong" by the new ROM. Some ROMs will just cheerfully format and encrypt without telling you, and you will have lost all your internal storage.
Conclusion - Never change your ROM without first backing up your precious data
Click to expand...
Click to collapse
The only workaround that I've found and that seems to work is to flash magisk just after the rom without rebooting to system, in this way I noticed that generally password is not required

The only workaround that I've found and that seems to work is to flash magisk just after the rom without rebooting to system, in this way I noticed that generally password is not required
Click to expand...
Click to collapse
Thats what I have found too, but am not 100% sure if there is an issue with TWRP as the PIN I use is always wrong and it kills the process. Very frustrating as I cannot mount data so cannot perform a backup

its due to dm-verity which is a "security" android feature and depends whether it is enabled or disabled. It also depends on if your recovery properly supports decryption. typically dm-verity can be disabled by flashing your rom and then flashing magisk BEFORE rebooting or a specific dm-verity disable patch if you wish to not install magisk. If you happen to have a encrypted partition and can got get in due to wrong password or non properly supported recovery ...then you are forced to format the partition thereby losing your data.

Can't you set password for screen lock after disabling force encrypt on your phone?
Edit: Never mind, it doesn't work in case of lavender.

XeoNoX said:
its due to dm-verity which is a "security" android feature and depends whether it is enabled or disabled. It also depends on if your recovery properly supports decryption. typically dm-verity can be disabled by flashing your rom and then flashing magisk BEFORE rebooting or a specific dm-verity disable patch if you wish to not install magisk. If you happen to have a encrypted partition and can got get in due to wrong password or non properly supported recovery ...then you are forced to format the partition thereby losing your data.
Click to expand...
Click to collapse
Thus, "typically dm-verity can be disabled by flashing your rom and then flashing magisk BEFORE rebooting".
I tried in the following steps
- flashing the full stock rom;
- reflashing the Orangefox recovery (since stock recovery replaced Orangefox);
- installing Magisk inside Orangefox.
Spoiler: Screenshot 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Furthermore, I checked two boxes below
- Disable DM-Verity;
- Disable Forced Encryption;
in the Orangefox settings both before and after flashing the full stock rom.
In addition, in fastboot mode, I flashed a Magisk-patched boot.img (that had been patched, before flashing the full stock rom, in a previously installed same stock rom).
All the above steps were performed before booting into system.
Finally, the data partition remained encrypted...
Would it be still possible to disable dm-verity?
Thanks.

Disable Forced Encryption cannot remove encryption, it can only disable forced encryption. to remove encryption, format data.

Related

Samsung Galaxy S7 bootloop

I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, i just tried a factory reset and that fails too. Unable to mount /data.
k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp
Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)
I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.

Stuck at Password Screen! Please Help

So I’ve tried many ROMs and am on the latest version of TWRP but I keep getting stuck at the password screen after rebooting. I have tried many factory resets and complete wipes and nothing has worked. I am also getting “encryption” errors and twrp errors about decrypting data...asking for a password and then telling me my password is incorrect. Is this the end of my 6P? Thanks for any help!
Password is linked to user data partition, a full wipe with TWRP doesn't wipe this partition, so it won't remove it. So to remove your password and fix this issue, you need to wipe the user partition, which will remove anything on your phone.
notstevek said:
Password is linked to user data partition, a full wipe with TWRP doesn't wipe this partition, so it won't remove it. So to remove your password and fix this issue, you need to wipe the user partition, which will remove anything on your phone.
Click to expand...
Click to collapse
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
videotape74 said:
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
Click to expand...
Click to collapse
Also, not to be rude, but you do know if you set a password, the twrp password is the password you're using for your lock screen? I don't mean to belittle you, just wanted to make sure you knew his. If you make your lockscreen password pin 1234, that's what you do in TWRP, if pattern, use that pattern, if regular password, type that.
What I mean by data is in TWRP you have the option to wipe phone (factory wipe) which does "data, cache, system", but that is not the data I am referring to. If you click advanced wipe, you have the option of formatting "internal storage" that is the user data I am referring to that holds the password. That's the portion you save stuff to like picture, the other data partition is where system apps get installed. If you can boot into the rom and use it normally, remove the password, does TWRP still ask you for a password? What about changing password, or changing from password to pin or pattern? If you've done all that I recommend manually downloading stock nexus 6p update, using fastboot, format each and every partition and flashing (including recovery) stock firmware. Nexus 6p is known for bootloop, this is something entirely different. Can you please verify that you can:
Boot into phone and use it(what rom?)
Remove password(if this doesn't work, see below)
Change password
Change to different type of password (go to pin if pattern, pattern if pin, password if pin/pattern)
Formated internal storage (which you need to backup and again is not the same as doing a "swipe to factory reset" in TWRP, you need to click advanced wipe and hit wipe internal storage.)
If none of that works, I again suggest trying to use fastboot, format each partition manually then flashing a full stock firmware including internal storage, and recovery, then install TWRP and rom, and see if that fixes it.
P.s. I don't want you to think I'm treating you as if you're clueless I am just trying get as much information and be 100% clear and on the same page regarding everything you try and make sure we're talking about the same stuff (i.e, regarding formatting Data) so we're on the same page, and so I can help you out to the best of my ability to.
notstevek said:
Also, not to be rude, but you do know if you set a password, the twrp password is the password you're using for your lock screen? I don't mean to belittle you, just wanted to make sure you knew his. If you make your lockscreen password pin 1234, that's what you do in TWRP, if pattern, use that pattern, if regular password, type that.
What I mean by data is in TWRP you have the option to wipe phone (factory wipe) which does "data, cache, system", but that is not the data I am referring to. If you click advanced wipe, you have the option of formatting "internal storage" that is the user data I am referring to that holds the password. That's the portion you save stuff to like picture, the other data partition is where system apps get installed. If you can boot into the rom and use it normally, remove the password, does TWRP still ask you for a password? What about changing password, or changing from password to pin or pattern? If you've done all that I recommend manually downloading stock nexus 6p update, using fastboot, format each and every partition and flashing (including recovery) stock firmware. Nexus 6p is known for bootloop, this is something entirely different. Can you please verify that you can:
Boot into phone and use it(what rom?)
Remove password(if this doesn't work, see below)
Change password
Change to different type of password (go to pin if pattern, pattern if pin, password if pin/pattern)
Formated internal storage (which you need to backup and again is not the same as doing a "swipe to factory reset" in TWRP, you need to click advanced wipe and hit wipe internal storage.)
If none of that works, I again suggest trying to use fastboot, format each partition manually then flashing a full stock firmware including internal storage, and recovery, then install TWRP and rom, and see if that fixes it.
P.s. I don't want you to think I'm treating you as if you're clueless I am just trying get as much information and be 100% clear and on the same page regarding everything you try and make sure we're talking about the same stuff (i.e, regarding formatting Data) so we're on the same page, and so I can help you out to the best of my ability to.
Click to expand...
Click to collapse
went back to stock fully after formatting partition, phone booted up fine, updated my apps and restarted my phone...now I'm getting a screen saying "Decryption Unsuccessful". i enter the correct password and it says I have to factory reset...i do, set up everything again and the same thing happens! pic below...thanks for any/all help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
videotape74 said:
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
Click to expand...
Click to collapse
videotape74 said:
went back to stock fully after formatting partition, phone booted up fine, updated my apps and restarted my phone...now I'm getting a screen saying "Decryption Unsuccessful". i enter the correct password and it says I have to factory reset...i do, set up everything again and the same thing happens! pic below...thanks for any/all help.
Click to expand...
Click to collapse
Oh this explains it ok. You need to format the internal storage. I'm not sure what that button does in regards to resetting but I recommend you using fast boot to wipe everything to factory rom. Go here: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and follow #11 in the second post. Add the command "fastboot format userdata" to that set of instructions. This will wipe your phone to factory, as if you just bought it. Once this is done, setup the phone, make sure it boots and works. If it does, download TWRP again from https://dl.twrp.me/angler/twrp-3.2.3-0-angler.img.html use the command "fastboot flash recovery twrp-3 2.3-0angler.img" to reflash TWRP. Try rebooting into twrp a few times to see if you can get the same error, if you can't you fixed it. If you can, your phones flash memory is probably shot. Let me know if you need anymore help and how it goes.
notstevek said:
Oh this explains it ok. You need to format the internal storage. I'm not sure what that button does in regards to resetting but I recommend you using fast boot to wipe everything to factory rom. Go here: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and follow #11 in the second post. Add the command "fastboot format userdata" to that set of instructions. This will wipe your phone to factory, as if you just bought it. Once this is done, setup the phone, make sure it boots and works. If it does, download TWRP again from https://dl.twrp.me/angler/twrp-3.2.3-0-angler.img.html use the command "fastboot flash recovery twrp-3 2.3-0angler.img" to reflash TWRP. Try rebooting into twrp a few times to see if you can get the same error, if you can't you fixed it. If you can, your phones flash memory is probably shot. Let me know if you need anymore help and how it goes.
Click to expand...
Click to collapse
I followed your steps exactly and now I'm getting the below error...I guess my flash memory is done.
I appreciate all the help you've given me!
videotape74 said:
I followed your steps exactly and now I'm getting the below error...I guess my flash memory is done.
I appreciate all the help you've given me!
Click to expand...
Click to collapse
I'm sorry to hear that. So to confirm you completely reflashed to stock firmware, reflashed TWRP recovery, and it's still giving you the error? Maybe someone else has some idea of what's happening but only thing I can think of is flash memory is shot. Try maybe older version of twrp??
Something similar happened to me, I will explain my situation and how to solve it, I had the stock ROM 8.1.0 installed and out of curiosity I put a start block that starts with a password and all right up there, then install the twrp and I prepared to put a Custo ROM to be specific CRDroid and everything was installed correctly nothing unusual, the problem came to insert my SIM card and see that I had no signal review the imei and had disappeared was blank and had not made rest of the SAI so I turned pale, then started twrp and asked for the password I had put with the stock ROM and accept it I made an advanced deletion and still still without imei, I reinstalled the latest version of stock ROM home, I asked for the password ,I was. security and I removed all kinds of security, I returned. do the process of installing the Custon ROM and the imei turned MIA CONCLUSION by changing the ROM and better to disable absolutely all kinds of blocking tank can bring signal or encryption conflicts

[GUIDE] Twrp Remove decryption password Xperia XZ

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for your twrp to recognize your internal memory and the available memory that is in it since we all face this problem that presents twrp in internal storage.
Warning: This procedure will erase all the data of your device such as google accounts, messages, root, that is to say it will remain factory mode, so you will need to reconfigure the device, I add images of the steps so that it is as comprehensible as possible to understand.
When you install twrp and start it for the first time we will get the following information we just need to confirm the action Swipe to Allow Modifications.
So we visualize the following menu with the options offered by twrp, we will only focus on the option Wipe.
We choose the option Advanced Wipe.
Check the Data box and we choose the option Repair or Change File System
We choose the option Change File System
We choose the option EXT4
We choose the option Swipe to Change, When confirming the action your device will erase all your data stored in the internal storage
Twrp will recognize your internal storage and capacity
Warning: You must re-flash Drm-fix.zip. magisk.zip to be root on your device
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
omaison said:
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
Click to expand...
Click to collapse
No you have do it again after fresh installation
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
omaison said:
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
Click to expand...
Click to collapse
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
awadnisar said:
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
Click to expand...
Click to collapse
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
omaison said:
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
Click to expand...
Click to collapse
Means updating OmniROM is wiping data partition?
awadnisar said:
Means updating OmniROM is wiping data partition?
Click to expand...
Click to collapse
Not automatically. But it seems that I don't have the choice to format it manually to have the possibility to flash the new version of the ROM.
Otherwise TWRP generate an error with saying that the data partition is encrypted.
I will try again on the next week when the new version of the OmniIROM is released.
redundant

TWRP : Bootloop after restoring SYSTEM on A205F

I was debloating my phone and some deleted wrong file in the system. And now when I restored System using Skyhawk TWRP Recovery my phone got stuck into a bootloop. I had to flash the ROM again and got all the bloatware back.
Is there any way to get this fixed? None of the tutorials have helped me so far.
Hello, Have you seen this?
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Buckythereporter said:
I was debloating my phone and some deleted wrong file in the system. And now when I restored System using Skyhawk TWRP Recovery my phone got stuck into a bootloop. I had to flash the ROM again and got all the bloatware back.
Is there any way to get this fixed? None of the tutorials have helped me so far.
Click to expand...
Click to collapse
Use TWRP / OrangeFox in the future. I recommended TWRP but I use OrangeFox because of password protection feature.
sercari said:
Hello, Have you seen this?
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Click to expand...
Click to collapse
I have everything working right now. But the phone goes into a bootloop if I restore the System. I used to just flash the rom again if something goes wrong. This was the first time I tried to restore a system backup.
Recovering Data partition works properly tho.
KineSight said:
Use TWRP / OrangeFox in the future. I recommended TWRP but I use OrangeFox because of password protection feature.
Click to expand...
Click to collapse
Does the backup and restore feature work for you? Do I need to flash something else to restore the System?
Buckythereporter said:
Does the backup and restore feature work for you? Do I need to flash something else to restore the System?
Click to expand...
Click to collapse
Yes. Backup's and Restore's work perfectly for me. I highly doubt either one can restore the other's backup data. (Yes, OF is based on TWRP.)
KineSight said:
Yes. Backup's and Restore's work perfectly for me. I highly doubt either one can restore the other's backup data. (Yes, OF is based on TWRP.)
Click to expand...
Click to collapse
So no one fixed this even in modded recoveries. Maybe they didn't face any issue and it's only my phone.
Just found this guide here, trying this.
Backup and Restore - a Hybrid Method (Android 9) | XDA Developers Forums (xda-developers.com)
restoring system.img is not recommend since it might trigger dm-verity. they say it better to flash the full stock rom
ineedroot69 said:
restoring system.img is not recommend since it might trigger dm-verity. they say it better to flash the full stock rom
Click to expand...
Click to collapse
Doesn't flashing a GSI do the same?
Buckythereporter said:
Doesn't flashing a GSI do the same?
Click to expand...
Click to collapse
here's the list of partition that is supposed to be dm-verity protected https://source.android.com/security/verifiedboot
"to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions"
my phone has already dm-verity trigger i don't see much difference except i need to deal with 2 boot animation on start lmao
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ineedroot69 said:
here's the list of partition that is supposed to be dm-verity protected https://source.android.com/security/verifiedboot
"to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions"
my phone has already dm-verity trigger i don't see much difference except i need to deal with 2 boot animation on start lmao
Click to expand...
Click to collapse
Seems like there's no permanent solution for this. Buying Mi next time.
Buckythereporter said:
Seems like there's no permanent solution for this. Buying Mi next time.
Click to expand...
Click to collapse
if you can start twrp get dmesg.log upload that file see if we can help you.

Problematic Xiaomi MI 9T - can't flash due to encrypted partition

Hi everyone, I just bought myself a MI 9T davinci global version. I wanted to make it so that it is nethunter, but It just doesn't work. I try everytime to flash recovery first then image, but when I try to copy images for flashing this **** comes up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't copy anything inside. I am looking for any image of a ROM but when I choose MIUI 11 for 9T, the official one, just so I can flash it somehow I can't do it, becuase Chinese little hands did something unexpected, I have to LOG IN to flash MY hardware with software I want.
What the f is going on? I can't flash dm-verify because I can't put it on the phone anywhere, I can't flash ****. What can I do? I have currently MIUI 12.4 I think.
johan.drykke said:
Hi everyone, I just bought myself a MI 9T davinci global version. I wanted to make it so that it is nethunter, but It just doesn't work. I try everytime to flash recovery first then image, but when I try to copy images for flashing this **** comes up.
View attachment 5668491
I can't copy anything inside. I am looking for any image of a ROM but when I choose MIUI 11 for 9T, the official one, just so I can flash it somehow I can't do it, becuase Chinese little hands did something unexpected, I have to LOG IN to flash MY hardware with software I want.
What the f is going on? I can't flash dm-verify because I can't put it on the phone anywhere, I can't flash ****. What can I do? I have currently MIUI 12.4 I think.
Click to expand...
Click to collapse
Very simple. When you open TWRP, it should ask you for the PIN. You have to enter the same PIN/Pattern you use the same for unlocking the screen in Android
Use the latest official TWRP from TWRP.me
It's nothing specific to Mi 9T or Xiaomi, it's a very good protection enforced by Google couple of years ago with A10 - TWRP cannot decrypt your Internal memory data without your pin.
Just consider your phone gets lost and somebody boots to TWRP - would you like him to be able to see your photos, documents, etc
The thing is, I had pin, 1234, I flashed twrp official through fastboot, It didn't ask for it, partition is still encrypted. Whet next? I tried wiping **** out of sdcard putting image there and flashing it, PicselExp, bootloop willkomen. Nothing is working, I am glad I flashed recovery though.
Please stop moralizing, I bought this phone because I want to play with it, not to store DEFCON 2 documents on it.
EDIT1: Sorry for beeing harsh, just I think that this 'davinci' is different than other 'davinci' and for the love of God, I hate TiVoization.
johan.drykke said:
Please stop moralizing...
Click to expand...
Click to collapse
I'm not noraluzing, I wanted to help, now I don't care anymore. Google will be your friend, everything relevant can be found there
Good luck
use fastboot to flash stock ROM (fastboot ROM). then from stock removeall safety patterns, fingers, go to flashing twrp with fastboot, boot to twrp, format data, flash whatever you want
be polite or get the f...out of this forum
Hi!
I'm having a somewhat similar yet kind of different problem : long story short I was able to flash a ROM once last week, it bricked my device and the internal storage got encrypted just like that, I somehow managed to manually flash a stock ROM from ADB and now my device boots properly on a stock MIUI.
The issue is I have no lock pattern anymore and the internal storage is still encrypted so I still can't flash from recovery.
Am I doomed to rock MIUI until my device dies? At what point should TWRP ask me for a pattern?
can't you format data in recovery?
wipe everything in recovery, try to install desired ROM. Hope you have made a backup before encryption
I have not tried yet, does wiping data remove encryption and "read only" ?
I had not backed up before encryption but as long as I have fastboot I have a stock MIUI I could flash with adb, it's kind of tedious but better than nothing.
Crikripex said:
I have not tried yet, does wiping data remove encryption and "read only" ?
I had not backed up before encryption but as long as I have fastboot I have a stock MIUI I could flash with adb, it's kind of tedious but better than nothing.
Click to expand...
Click to collapse
There are two things:
- Data and Internal memory are FBE encrypted:
File-Based Encryption | Android Open Source Project
source.android.com
- System As Root (SAR) = System, Vendor, Product are Read-only
Do not mix/mess-up one with another
---
Format Data does not remove one or another
FORMAT - not Wipe, there are two different buttons in TWRP.
And Format Data only (not System, etc)
After that, reboot to Android, setup your screen unlock pin
Then reboot to TWRP, it must ask you for pin - enter that same pin you did set in Android for screen unlocking
The TWRP (by the FBE mechanism) will be able to decrypt Data and Internal storage.
On a folder or file by file base - just like it works in Android (seemless for you)
Same way you have to enter your pin every time when you reboot to Android - samw you have to enter the pin every time you reboot to TWRP
Because FBE ancryption cannot decrypt without your pin
And that's a good feature (enforced by Google, since Android 10). I don't understand why people are 'afraid' or whatever of that. Thinking it's something strange, unwanted, whatever
If your phone is stolen and the thief reboots to TWRP, he will see scrambled files and folders. If he copies the files to PC - your photos and documents, etc will be scrambled and of no use for him
Without FBE, the thief reboots to TWRP (he cannot to Android since not knowing our pin) and he could copy your files to PC and open them
And things work seamlessly for you, hence no problem at all
---
Read only SAR is something totally different. System filesystems are read-onl and you cannot make any (hard) changes. Even not with Magisk/root
But Magisk privides Systemless mechanism - where every time while booting and initializing Magisk, Magisk mounts the changes asked by Magisk modules.
That way once you are booted, your System appears as it was changed (AdAway hosts file, debloating, Viper4Androud, etc).
Hence again, things work for you seamlessly.
But if you disable/uninstall Magisk module(s) or Magisk itself (or you just reboot with stock Boot img - without Magisk), then you have clean/not changed/not affected System - and since that you have no problem with OTA, etc
No Xiaomi 'features' but things enforced by Google and you will find them in all new phones with new Android versions
Actually, started with Android 10 or so, hence present already for 3 years out.
No more times of KitKat, Open Bootloaders, etc
yes, format data wipes encryption and all of your data.
Without decryption you won't be able to restore data.
Boot to miui, make a backup if that's possible and then boot to recovery, format data and do everything to i stall desired ROM
zgfg said:
There are two things:
- Data and Internal memory are FBE encrypted:
File-Based Encryption | Android Open Source Project
source.android.com
- System As Root (SAR) = System, Vendor, Product are Read-only
Do not mix/mess-up one with another
---
Format Data does not remove one or another
FORMAT - not Wipe, there are two different buttons in TWRP.
And Format Data only (not System, etc)
After that, reboot to Android, setup your screen unlock pin
Then reboot to TWRP, it must ask you for pin - enter that same pin you did set in Android for screen unlocking
The TWRP (by the FBE mechanism) will be able to decrypt Data and Internal storage.
On a folder or file by file base - just like it works in Android (seemless for you)
Same way you have to enter your pin every time when you reboot to Android - samw you have to enter the pin every time you reboot to TWRP
Because FBE ancryption cannot decrypt without your pin
And that's a good feature (enforced by Google, since Android 10). I don't understand why people are 'afraid' or whatever of that. Thinking it's something strange, unwanted, whatever
If your phone is stolen and the thief reboots to TWRP, he will see scrambled files and folders. If he copies the files to PC - your photos and documents, etc will be scrambled and of no use for him
Without FBE, the thief reboots to TWRP (he cannot to Android since not knowing our pin) and he could copy your files to PC and open them
And things work seamlessly for you, hence no problem at all
---
Read only SAR is something totally different. System filesystems are read-onl and you cannot make any (hard) changes. Even not with Magisk/root
But Magisk privides Systemless mechanism - where every time while booting and initializing Magisk, Magisk mounts the changes asked by Magisk modules.
That way once you are booted, your System appears as it was changed (AdAway hosts file, debloating, Viper4Androud, etc).
Hence again, things work for you seamlessly.
But if you disable/uninstall Magisk module(s) or Magisk itself (or you just reboot with stock Boot img - without Magisk), then you have clean/not changed/not affected System - and since that you have no problem with OTA, etc
No Xiaomi 'features' but things enforced by Google and you will find them in all new phones with new Android versions
Actually, started with Android 10 or so, hence present already for 3 years out.
No more times of KitKat, Open Bootloaders, etc
Click to expand...
Click to collapse
yaro666 said:
yes, format data wipes encryption and all of your data.
Without decryption you won't be able to restore data.
Boot to miui, make a backup if that's possible and then boot to recovery, format data and do everything to i stall desired ROM
Click to expand...
Click to collapse
Thank you both so much for your time, help and explainations!
I finally understand what was happening, I had a hard time pinpointing exactly what made my partition encrypted but it does make a whole lot of sense.
I managed to successfully flash ArrowOS 12.1 using sideload after formating. I now know both that my system is naturally encrypted and that it is completely normal and not a result of a flashing error
Last time I flashed a ROM the newest and flashiest android was 9.0 so it's all new to me.
Thanks again!
There is a TWRP (TWRP 3.6.2+ - UNOFFICIAL | Android 12.) specially made to work with android 12 enryption. (The version from Adi is only needed for his supported roms. Otherwise always use the TWRP 3.6.2+ if not declared differently)
Could be useful if you want to OTA update your rom. Otherwise you could be forced to sideload over adb or even make a complete clean flash again.
Selfquote:
[RECOVERY][3.4.0-10][davinci]Official/Unofficial TWRP for Xiaomi Redmi K20 (Stable)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com

Categories

Resources