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.
Related
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Chrono7x said:
Hi there, I have an Axon 7 with LineageOS that was working like a charm until I rebooted it today. It was in the normal lineage OS boot animation with the blue circle moving from right to left, except it never stopped. Now after trying a few more times, it just keeps playing the animation except the phone will vibrate slightly every several seconds. The phone is encrypted but that hasn't been a problem. When I reboot to TWRP, it says Unable to mount storage.
I tried wiping Cache and Dalvik / ART Cache, but this didn't help. Finally, I do have a backup from 7-20-2017 but I'd rather not have to go back to that...
Any recommendations?
Click to expand...
Click to collapse
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Choose an username... said:
So you can't see the internal storage from TWRP? I'm guessing encryption actually plays a part here. Formatting data is probably the best course of action, though you should flash magisk or superSu if you do, to get rid of encryption. But you obviously lose everything that's on the internal storage.
Maybe make a system and boot backup and clean flash Lineage. Like, wipe system and caches, then flash the bootloader, modem, LOS and whatever else you flash
Click to expand...
Click to collapse
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Chrono7x said:
Is it easier to just use the backup I have currently? If so, what are the steps necessary for that (sorry for newb questions, haven't messed with it in a while)
EDIT: Also, TWRP claims decryption is successful when it is loading up.
Click to expand...
Click to collapse
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Choose an username... said:
Again. Can you see the internal storage?
Don't restore the backup. Your problem is basically either on /system (clean flash of the ROM will do) or on /data (complete format of data is needed). So try the non destructive one first
Click to expand...
Click to collapse
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Chrono7x said:
I don't see any storage folder. So if I want to install the latest LOS and frankly just start from scratch, can I follow the guide here https://wiki.lineageos.org/devices/axon7/install#installing-lineageos-from-recovery starting from "Installing LineageOS from recovery"? Will I still need to install something to wipe the encryption?
Click to expand...
Click to collapse
What? No... That's for normal phones. How did you manage to install LOS without knowing that you need the univ. bootloader and modem?
So, you can't access the internal storage via the file manager on TWRP i'm guessing.
Wipe - Format data, after that flash the Universal bootloader, modem, LOS, Magisk, GApps. Magisk takes care of dm-verity and disables encryption. Don't try to uninstall it though or your internal storage will get encrypted as soon as you do. But if you want to change ROMs you can just fpash it before booting and it won't ger encrypted.
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......
Something recently broke Twrp so now I cant touch my /data partition, ive read that I need to format my phone to fix this issue, the problem is that a recent update from Lineage OS is what broke it I believe, and I updated from within LOS (check for new updates download and install) which auto restarted, so when I went to go back into TWRP to reflash Magisk I started getting the issue
So now I have no root, and no twrp abilities that I know off, which means I cant use a decent backup program
can anyone help?
EDIT: I don't know if they has any relevance but ADB does have root permissions,
EDIT 2: I found out that I can reinstall magisk VIA ADB Sideload from within TWRP, as such I now have root again
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
AnonVendetta said:
@foxtrotdragon: If you can get into TWRP then reflashing Magisk shouldn't be a problem. However, if /data is encrypted then Magisk may not flash, it needs to be able to place some files there. You'll lose everything on internal storage, but formatting /data is the only way forward.
If you can't boot into TWRP then the obvious solution is to reflash recovery from a PC.
Click to expand...
Click to collapse
Getting into twrp is no issue, the issue is that TWRP cannot read the internal storage, it can read external fine, but fails to read internal storage, which means i cant flash anything, an reflashing twrp does nothing
im fine with reformatting the phone, but i need to backup my stuff first, which i can not do since no root
@foxtrotdragon: Unfortunately for you, backing up the contents of your internal storage is no longer possible, unless you can think of some ingenius method to decrypt without formatting. Formatting /data is your only option. In the future, you should make backups *BEFORE* disaster strikes.
Hi.
I have huge problem. I have Redmi Note 7 with xiaomi.eu (Last stable MIUI 10 version). Today I decided to update it to latest version (MIUI 11). Before it, I made backup via TWRP and then perform update. Update successfull. I thought that I prefer MIUI 10 so in TWRP perform wipe dalvic and cache and make restore backup. Backup succesfull. But... System wont boot up. In TWRP I cant see internal storage (0MB), TWRP ask for decryption password but the password from unlocking phone doesnt work. I dont know what to do. I dont want to lose my data. I found info that OrangeFOx recovery could be helpful so I flashed OrangeFox recovery. But it also ask for password.
Help please.
mcichy10 said:
Hi.
I have huge problem. I have Redmi Note 7 with xiaomi.eu (Last stable MIUI 10 version). Today I decided to update it to latest version (MIUI 11). Before it, I made backup via TWRP and then perform update. Update successfull. I thought that I prefer MIUI 10 so in TWRP perform wipe dalvic and cache and make restore backup. Backup succesfull. But... System wont boot up. In TWRP I cant see internal storage (0MB), TWRP ask for decryption password but the password from unlocking phone doesnt work. I dont know what to do. I dont want to lose my data. I found info that OrangeFOx recovery could be helpful so I flashed OrangeFox recovery. But it also ask for password.
Help please.
Click to expand...
Click to collapse
You're out of luck. You need to format your data partition - and you will lose your data and all the contents of your internal storage.
DarthJabba9 said:
You're out of luck. You need to format your data partition - and you will lose your data and all the contents of your internal storage.
Click to expand...
Click to collapse
Is there any way to backup storage eg. via adb or something and try later to restore it?
EDIT
I performed wipe, install latest android. Data is gone. I found some windows apps to restore data after factory reset via adb. I'll try this in next week
mcichy10 said:
Is there any way to backup storage eg. via adb or something and try later to restore it?
Click to expand...
Click to collapse
No.
mcichy10 said:
EDIT
I performed wipe, install latest android. Data is gone. I found some windows apps to restore data after factory reset via adb. I'll try this in next week
Click to expand...
Click to collapse
Good luck!
PS: if your original MIUI 10 backup included /data, then you should be able to restore the data after formatting, flashing a fresh copy of the MIUI 10 ROM, booting the ROM, and then, booting back to recovery and restoring the data backup. But the content of your internal storage is gone forever (if you didn't back it up before).
Unfortunately I lost all my data (mainly photos). I'll buy microsd to store data and backups.
Hi Guys,
It's all in the title really, I have tried rolling back from the latest MIUI stable rom 20.1.9_v11-10 to my previously run V11.0.2.0 , this got my phone (mi9t) stuck in a bootloop. After going into recovery mode, I have realized the internal storage folders are all messed up, with the folders names showing in an odd combination of number and letters (Something like: 9KJJGDKJ).
The phone still mounts via USB to the laptop, by I'm unable to transfer any files to the internal storage. And as such, I'm currently unable to flash it with a ROM.
I'd appreciate any advice on this, hopefully one that would also help me salvage the files and data I have on my internal storage.
Hi
Abu-7abash said:
Hi Guys,
It's all in the title really, I have tried rolling back from the latest MIUI stable rom 20.1.9_v11-10 to my previously run V11.0.2.0 , this got my phone (mi9t) stuck in a bootloop. After going into recovery mode, I have realized the internal storage folders are all messed up, with the folders names showing in an odd combination of number and letters (Something like: 9KJJGDKJ).
The phone still mounts via USB to the laptop, by I'm unable to transfer any files to the internal storage. And as such, I'm currently unable to flash it with a ROM.
I'd appreciate any advice on this, hopefully one that would also help me salvage the files and data I have on my internal storage.
Click to expand...
Click to collapse
For backup have you tried running adb command "adb pull /sdcard _(here specify any location in your pc such as C:\x\) from CMD when in TWRP? And for flashing ROM you can use "adb push (ROM zip location and destination such as C:\x\anyrom.zip /sdcard/)" and flash ROM .zip from your sdcard root in TWRP AFTER factory reset and wipe system from TWRP. Remember factory reset will erase your internal storage. Hope it helps. Good luck.
Abu-7abash said:
Hi Guys,
It's all in the title really, I have tried rolling back from the latest MIUI stable rom 20.1.9_v11-10 to my previously run V11.0.2.0 , this got my phone (mi9t) stuck in a bootloop. After going into recovery mode, I have realized the internal storage folders are all messed up, with the folders names showing in an odd combination of number and letters (Something like: 9KJJGDKJ).
The phone still mounts via USB to the laptop, by I'm unable to transfer any files to the internal storage. And as such, I'm currently unable to flash it with a ROM.
I'd appreciate any advice on this, hopefully one that would also help me salvage the files and data I have on my internal storage.
Click to expand...
Click to collapse
Well, it looks like you phone is encrypted and the only way is to format data, and did you format data before doing the downgrade?
Do you have TWRP?
You need to format data, internal memory encrypted.
Boot to TWRP
Format DATA
Reboot to TWRP
Transfer xiaomi.eu rom and flash
Reboot
Abu-7abash said:
Hi Guys,
It's all in the title really, I have tried rolling back from the latest MIUI stable rom 20.1.9_v11-10 to my previously run V11.0.2.0 , this got my phone (mi9t) stuck in a bootloop. After going into recovery mode, I have realized the internal storage folders are all messed up, with the folders names showing in an odd combination of number and letters (Something like: 9KJJGDKJ).
The phone still mounts via USB to the laptop, by I'm unable to transfer any files to the internal storage. And as such, I'm currently unable to flash it with a ROM.
I'd appreciate any advice on this, hopefully one that would also help me salvage the files and data I have on my internal storage.
Click to expand...
Click to collapse
I would try another recovery, sounds like something is corrupt with the twrp version. Have you tried Orangefox?
I had the same problem. Only thing that works is formatting data. A different twrp wont work. I tried 3 different versions all the same.
Thanks guys, already formatted my sd card yesterday and then I was able to re-flash the Android Q update.
My data is lost tho. Thank you all for your input here.
Sent from my Redmi K20 using Tapatalk