Hi, happy owners of this phone.
I have problems when i upgrade from MIUI 11.0.7 Global (Pie) to MIUI 11.0.2 or 11.0.3 (10)... TWRP-based recoveries for our phones doesn't ask for password even though my partition is obviously encrypted.
I tried using the ''TWRP decrypt (password)'' command, but it seems like it can't decrypt Data partition. Any help with this? Thanks in advance
I have same problem with Mi10Lite5G, while upgrading to Android 11. Now sdcard looks garbled.
Can you recover it?
THanks
Related
Here is a quick review of what happened:
The phone was running well on Lineageos 14.1, encrypted with a pattern, with TWRP 3.1.1 as recovery. I’ve then been notified of an LOS update to 15.1 Oreo and got excited. Booted in recovery, entered my pattern to decrypt, took a full TWRP backup, flashed Oreo modem and firmware and dirty flashed (I know, bad idea) the LOS 15.1 zip.
It got stuck at boot logo. Even if I didn't have high expectations for it to work I just thought I would try the lazy way to see and use my fresh backup to restore in case of failure like I always did successfully since my Nexus One.
This time was different because as I rebooted in TWRP to restore, it didn't ask for my pattern. You guessed it, the data partition is encrypted, no access to my backup or anything on the external storage. I can mount data and see the weird encrypted file names but that's it. I tried different version of TWRP, but it never ask the pattern. Even the terminal command 'twrp decrypt *******' doesn’t work.
I then tried to wipe data and flash LOS 14.1 again but it gets stuck saying that android has no access to data partition because it’s encrypted and that I need to format. I pulled out my sim card and started to use my old oneplus one while waiting for the new version of TWRP 3.2.1.1 with the feb security patch support thinking it might then be able to decrypt but no luck still.
I can go without the phone for a while, I’ll buy another one if I have to because there is some precious data on that phone and I can’t make my mind that the data is there, I know the encryption key but I have no access to it. There must be a way, I just don’t have enough knowledge about how this encryption thing is working.
Any help would be appreciated, Thank you
jpitou said:
Here is a quick review of what happened:
The phone was running well on Lineageos 14.1, encrypted with a pattern, with TWRP 3.1.1 as recovery. I’ve then been notified of an LOS update to 15.1 Oreo and got excited. Booted in recovery, entered my pattern to decrypt, took a full TWRP backup, flashed Oreo modem and firmware and dirty flashed (I know, bad idea) the LOS 15.1 zip.
It got stuck at boot logo. Even if I didn't have high expectations for it to work I just thought I would try the lazy way to see and use my fresh backup to restore in case of failure like I always did successfully since my Nexus One.
This time was different because as I rebooted in TWRP to restore, it didn't ask for my pattern. You guessed it, the data partition is encrypted, no access to my backup or anything on the external storage. I can mount data and see the weird encrypted file names but that's it. I tried different version of TWRP, but it never ask the pattern. Even the terminal command 'twrp decrypt *******' doesn’t work.
I then tried to wipe data and flash LOS 14.1 again but it gets stuck saying that android has no access to data partition because it’s encrypted and that I need to format. I pulled out my sim card and started to use my old oneplus one while waiting for the new version of TWRP 3.2.1.1 with the feb security patch support thinking it might then be able to decrypt but no luck still.
I can go without the phone for a while, I’ll buy another one if I have to because there is some precious data on that phone and I can’t make my mind that the data is there, I know the encryption key but I have no access to it. There must be a way, I just don’t have enough knowledge about how this encryption thing is working.
Any help would be appreciated, Thank you
Click to expand...
Click to collapse
Try flash codeworkx TWRP ...
it should decrypt your data partition ...
https://downloads.sourceforge.net/project/cheeseburgerdumplings/15.1/cheeseburger/recovery/twrp-3.2.1-0-20180309-codeworkx-cheeseburger.img?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fcheeseburgerdumplings%2Ffiles%2F15.1%2Fcheeseburger%2Frecovery%2F&ts=1521806282&use_mirror=netix
PS-DEV said:
Try flash codeworkx TWRP ...
it should decrypt your data partition ...
https://downloads.sourceforge.net/project/cheeseburgerdumplings/15.1/cheeseburger/recovery/twrp-3.2.1-0-20180309-codeworkx-cheeseburger.img?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fcheeseburgerdumplings%2Ffiles%2F15.1%2Fcheeseburger%2Frecovery%2F&ts=1521806282&use_mirror=netix
Click to expand...
Click to collapse
I had tried it when it came out and I just tried it again. No difference!! It looks like twrp doesn't even see that my phone is encrypted. I've read a lot and tried many different things and I'm out of idea. All of the people I've seen with this problem have given up so they could get their phone back and running by formatting the partition, losing their data. This option is not one for me. I'd rather buy a new phone hoping for an eventual possible solution. I know the data is there, and I know the pattern key...... I mean, there's got to be a way......
As the tittle says, this is my current workaround for issues that happened after most people update their AOSP based ROMs after 3rd July 2018.
Decryption Unsuccessful
Q: Why does this happens ?
A: There's some weird issues with the latest AOSP based ROM that makes encrypted ext4 based data partition unable to be decrypted in both system and older version of TWRP if you're encrypted before (intentionally or unintentionally). This however doesn't apply to F2FS and unencrypted ext4 data partition.
Q: How do I solve this ?
A: There's 2 ways you can do to solve this issue.
The best way and the most recommended way is to repartition your data into F2FS. However it does require you to do a backup beforehand since this will wipe everything in your internal storage.
1. Backup your internal storage from TWRP (either to a SD card or PC via ABD)
2. Format it by going into TWRP and select Format and choose "wipe data"
3. Type "yes" and let the process end.
4. Flash your ROM and GApps.
5. Finish the setup without setting any screen lock so that it doesn't encrypt your data partition.
-Or-
The other way does is to install a custom kernel is made after 20 July 2018
List of kernel that can boot successfully without the need to wipe /data :
-Xenial b25x or newer
-Revolt EAS-R13
(Got kernel that works and doesn't show up here? TELL ME, I'll add it to my list for everyone's reference)
Link for the working TWRP that can detect Internal Storage :
Jairus' modded TWRP
https://androidfilehost.com/?fid=5862345805528049168
Or you can look up Orange Fox recovery
(link will be added soon)
Good Stuff Also This Happened to me while i was using the Android P DP3 i tried twrp and redwolf and was the same i flashed the Orange Fox and it worked
Does this twrp can flash both treble and non treble ROM?
eko_epe said:
Does this twrp can flash both treble and non treble ROM?
Click to expand...
Click to collapse
Yes, it does
AkmalWarrior said:
Yes, it does
Click to expand...
Click to collapse
Ok i'll try. Thanks
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
TWRP and redwolf too (find on telegram)
Envoyé de mon Redmi Note 4 en utilisant Tapatalk
DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
*Only in recovery, not in boot. The only way to fix decryption unsuccessful on boot is to either repartition data to F2FS or flash a custom kernel that's made after 20 July. List on working kernels is on main thread.
First I tried orange fox beta and it showed my internal storage
Then I flashed the RR endless
But the encryption was still there
Then I tried the twrp from this thread and flashed rom with latest xenial
And it worked no problem
Thank you
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk
antony felix said:
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk
Click to expand...
Click to collapse
Thanks,So i must format internal too,. It's ok but how if i want to comeback use nougat..? I hear who's downgrade after using oreo will get "encryption was interrupted" on any nougat los/aosp base rom,should be format internal for working back the devices..
I think by this thread shared we get solution for who's want to downgrade from oreo without facing encryption issue enytime for oreo back to nougat or vice
DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.
What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?
AkmalWarrior said:
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.
Click to expand...
Click to collapse
Finally i can confirm for fixed "encryption was interrupted" by changing data partition into F2FS, yes i think it's only way to get free from that, i'v been test it back to back from oreo down to nougat or vice, no worry anymore
Below screenshot for oreo left side and nougat in right
ngydna said:
What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?
Click to expand...
Click to collapse
Read the OP, the recovery only help you boot into recovery and format your data partition or flash a custom kernel to allow you to boot into system as this issue does affect some older version of TWRP recovery. The recovery alone can't help you boot into system.
I took out my sdcard and did format data on the internal storage and now i can't mount my sdcard. Didn't think about the fact that removing the encryption on the internal storage would make it unable to recognize the encryption on the sdcard afterwards. Is there any way to fix this? Or did I just screw myself?
---------- Post added at 01:53 PM ---------- Previous post was at 01:00 PM ----------
When I reinstalled the rom and tried to boot it still asks me for my password which still works even though I can't boot because it says that the data is corrupted. But the encryption key should still be stored somewhere apparently. There must be a way to use it to decrypt the sdcard.
Hi, I'll try to be as detailed as possible but just know that I am somewhat of an amateur with android and I only have surface level knowledge.
I have an Axon 7 that I successfully installed OrdenKrieger's unofficial LineageOS 16.0 a few months ago (build 20181114). I saw recently that there was a new build so I booted to TWRP to flash it, but found that I could not access my file system. I am able to select (in the mount menu) system, cache, and persist, but not data. I then tried to reformat my data based on a thread I found, but then I booted back to TRWP the same problem was still there.
If anyone could help me solve this it would be very much appreciated. I have a few other problems too with root installation and dac selection, but this I am just not able to figure out why is happening.
I am on a vendor partition, but I do not remember which tool I used, just that it was one of the first to come out after Lineage 16 was released for the Axon 7. My TWRP version is 3.3.1-0 and I am not sure which bootloader/modem I installed either.
Maybe try reformating/changing your vendor partition size
I have the same problem, installed LOS 16.0 recently and TWRP is unable to mount internal storage. Anyone have a fix for this? Have tried flashing the latest TWRP via fastboot but didn't help
I've just moved from MIUI 11 to custom Q roms recently and I faced the "Data partition is encrypted" error when I open recovery. I read that I should format the data partition and reboot recovery but I tried and after rom starts, I opened recovery and the error appeared again.
I tried:
Formatting data before installing new rom
Formatting data after installing new rom
Try another Q rom
But nothing changed.
I'm using OrangeFox recovery.
Any suggestions? Thanks in advance
ashvsmay00 said:
....Any suggestions? Thanks in advance
Click to expand...
Click to collapse
Most lavender ROMs will encrypt automatically an unencrypted device when booting up for the first time. This is for a very good reason - without encryption, some things (PIN/password, fingerprint) will not work on this device.
The only way you can prevent such automatic encryption is to format data, reboot OrangeFox, tick "Disable Forced Encryption" in the OTA settings page, and then flash the ROM. In most cases, this will be enough to prevent the ROM from encrypting the device. However, I would very strongly advise you to NOT do this (for the reasons stated above). Let the ROMs encrypt, and live happily with the encrypted device!
Good to know your solution.
I want my de vice encrypted. But what the purpose to have à encrypted phone without knowing the key pass?
We are not able to wipe cache and delvik, so we can't update the ROM version and get last security updates.
How can we encrypt the phone using a clean way?
what orangefox version you are using? and before you reply.....PLEASE UPDATE TO THE LATEST 10.1, because version 10.0.1 is obsolete at least three releases. (thats the only thing i can think of - solution for your problem)
deleted reply
Hi,
This is a continuation of my errands in magisk-support-2661and magisk-support-2662. I'm interested in the twrp aspect here, hopefully someone who knows twrp welll reads this.
Basically this is a Redmi 7A phone with stock MIUI 10.2.5 and twrp 3.3.1. Phone got messed after updating Magisk to latest version, and while trying to fix it i accidentally wiped data from within twrp. It says this preserves internal storage so I thought this would be ok, but internal storage is encrypted on this device and after doing this i can't access my files from twrp anymore (before it used to ask for my pattern). Files are still there encrypted, and looks like keys are still there in /data/misc so I guess all hope is not lost.
Any ideas on how twrp Wipe data functionality is supposed to work on encrypted storage devices, and how to get one's files back afterwards ?
Help appreciated before i mess things up further =)
lemonsqueeze said:
Hi,
This is a continuation of my errands in magisk-support-2661and magisk-support-2662. I'm interested in the twrp aspect here, hopefully someone who knows twrp welll reads this.
Basically this is a Redmi 7A phone with stock MIUI 10.2.5 and twrp 3.3.1. Phone got messed after updating Magisk to latest version, and while trying to fix it i accidentally wiped data from within twrp. It says this preserves internal storage so I thought this would be ok, but internal storage is encrypted on this device and after doing this i can't access my files from twrp anymore (before it used to ask for my pattern). Files are still there encrypted, and looks like keys are still there in /data/misc so I guess all hope is not lost.
Any ideas on how twrp Wipe data functionality is supposed to work on encrypted storage devices, and how to get one's files back afterwards ?
Help appreciated before i mess things up further =)
Click to expand...
Click to collapse
Before you wiped data, was TWRP able to decrypt? able to view what you call internal storage?
J.Michael said:
Before you wiped data, was TWRP able to decrypt? able to view what you call internal storage?
Click to expand...
Click to collapse
Yes, it asked for my pattern and was able to decrypt the files.