Related
Hello
This is a TWRP recovery for Motorola Moto G5 Cedric for arm64 ROMS, with encryption support, backup support for persist and efs partitions and possibility to flash/backup logo boot image.
I need review and test, especially for the storage decryption and/with LineageOS fingers-crossed. I was able to test it on my device (XT1676 3Go).
It is my first ROM so it is possible that there are bugs.
- Be carefull, there are problems with the backup system :
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
- freeZbies
Click to expand...
Click to collapse
Changelog
TWRP 3.2.3-2
add sdcardfs
add FB2PNG for screenshot
fix brightness path and define it at 160
fix time zone error
fix incorrect lun path for USB
You can download it here :
TWRP 3.2.3-2 (md5: 0dbd3846593ae907d3391596876c1f35)
TWRP 3.2.3-1 (md5: 404b54d27653b5a1ec5b59023f53d3cb)
TWRP 3.2.3-0
Sources :
https://github.com/Akipe/twrp_android_device_motorola_cedric
https://github.com/Akipe/twrp_android_device_motorola_msm8937-common
Manifest :
https://github.com/Akipe/android_development_manifest
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Guttergorm said:
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I added the functions you wanted. Can you try and tell me if everything is ok?
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
mikefive said:
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
Click to expand...
Click to collapse
Thx for testing :good:
Akipe can u help us to build treble rom for cedric???
Works nicely, thanks.
I just tested it and it decrypts my internal storage normally.
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
Hello ! Thank you for your test and sorry for your backup
I will test the backup system and add a warning
freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Akipe said:
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Click to expand...
Click to collapse
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
freeZbies said:
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
Click to expand...
Click to collapse
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Akipe said:
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Click to expand...
Click to collapse
I was on stock oreo, so its arm, not arm64
freeZbies said:
I was on stock oreo, so its arm, not arm64
Click to expand...
Click to collapse
Oh ok, there are chances that's why the backup did not work .
This recovery is mainly intended for arm64 rom !
Just wanted to say that everything worked well for me in backing up and restoring the OmniROM, on both decrypted and encrypted phone.
Thanks @Akipe for the great job
Can you update it to latest TWRP?
Sent from my cedric using XDA Labs
forgot password to decrypt??
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
nurvus said:
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
Click to expand...
Click to collapse
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
TheFixItMan said:
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
Click to expand...
Click to collapse
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
nurvus said:
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
Click to expand...
Click to collapse
Backup efs if you want to preserve your current emei state or need to restore it in future
A question about decrypting your device, in this case Luisrom Android 10, but would most probably count for other roms too.
Did not try it already but would like to decrypt my device and would like a confirmation if the following is the right procedure without doing a new install:
Boot in recovery
Make a backup of /data to internal storage with TWRP
Make a backup of internal storage to my pc
Format data in TWRP
Copy internal storage back from pc to OP3(T)
Restore backup from /data with TWRP
Reboot with decrypted phone
I could do a dirty flash afterwards ofcourse, but because /system is not touched I think the steps above should be enough.
Could someone confirm if this is right?
Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!
Johan2020 said:
Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!
Click to expand...
Click to collapse
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based
nvertigo67 said:
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based
Click to expand...
Click to collapse
I am using CrDroid 6.4 Luisrom which is not enforcing encryption, just as most other custom roms.
I had enabled encryption though after installation to see if encryption was working already for installing CrD Luis on my work phone (where I want encryption).
After that I decided to go back to unencrypted, following the procedure above, which did not work.
Did not make the link between fbe and file based encryption, but ofcourse this is the same and not available on op3/t.
Must have been sleeping when I wrote that.
Based on what you wrote and my missing knowledge;
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?
Johan2020 said:
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?
Click to expand...
Click to collapse
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.
nvertigo67 said:
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.
Click to expand...
Click to collapse
Good point, did not try that unfortunately and just did a fresh install so.... not really eager to try it now
But I think indeed reencryption was triggered because of also restoring the encryption settings.
Will try it when I have some spare time and want to take the risc of a fresh install again
I am using the official TWRP (version 3.6) and I am currently on Evolution X 6.0 (Android 12). I am trying to reflash the ROM but whenever I try to wipe dalvik or data, TWRP fails to. Also internal storage contents are unreadable in TWRP. I have also been suggested to use MiFlashTool to go back to MIUI and then reflash evo x. The problem is MiFlashTool doesn't seem to be working (doesn't detect device, I have all firmware and Mi Unlock (bootloader unlocker) also detected the phone. Fastboot also detects it.
It would be helpful if someone can suggest a way to surpass these issues. A working MiFlashTool should work. Also, maybe, a TWRP that can decrypt data should also work (I have removed the screen lock).
Deleted
Try use SKK TWRP by Camerado (download from here), it's already support decrypt data A12 but make sure your rom before doesn't have/ already removed any security lock screen
JJeamy said:
Try use SKK TWRP by Camerado (download from here), it's already support decrypt data A12 but make sure your rom before doesn't have/ already removed any security lock screen
Click to expand...
Click to collapse
Thank you very much, it worked for me, I had the problem described in this thread, I went from miui eu 12.5 to 13, and I had the problem that with any recovery it appeared that it had the data encrypted and there was no way to decrypt it, I put the password and it did not it worked, it seems that the problem was android 12
My device: poco f3
pitufimanuel said:
Thank you very much, it worked for me, I had the problem described in this thread, I went from miui eu 12.5 to 13, and I had the problem that with any recovery it appeared that it had the data encrypted and there was no way to decrypt it, I put the password and it did not it worked, it seems that the problem was android 12
My device: poco f3
Click to expand...
Click to collapse
Were you able to go back to MIUI 12.5? If so, you did it via the recovery right? Also, can you let me know the exact steps?
I also have decrypt problem in my Poco F3 Android 12 in twrp. I tried the skkk twrp but the problem is not solved. When you go to decryp user, even if I give the correct pattern it says abut failed decrypt user.
Johnn78 said:
I also have decrypt problem in my Poco F3 Android 12 in twrp. I tried the skkk twrp but the problem is not solved. When you go to decryp user, even if I give the correct pattern it says abut failed decrypt user.
Click to expand...
Click to collapse
you must remove or delete any all of your screen lock (pin, password, fingerprint, pattern etc) from rom settings before reboot into skkk twrp, then you can see your internal storage in skkk twrp.
JJeamy said:
you must remove or delete any all of your screen lock (pin, password, fingerprint, pattern etc) from rom settings before reboot into skkk twrp, then you can see your internal storage in skkk twrp.
Click to expand...
Click to collapse
I had removed the lockscreen and now doesn't require to decrypt data in beginning but when I go to file manager then it doesn't show the internal data and in mount menu, it says decrypt data about internal data. Only if you connect mobile to pc then you don't see the internal data but appear it as empty drive in which you can transfer new files to the empty drive and it will appear them to file manager of twrp. In other words you can view only need transferred files and not the files which are already in data partition until to decrypt the data while I haven't put some code for unlocking phone.
Johnn78 said:
I had removed the lockscreen and now doesn't require to decrypt data in beginning but when I go to file manager then it doesn't show the internal data and in mount menu, it says decrypt data about internal data. Only if you connect mobile to pc then you don't see the internal data but appear it as empty drive in which you can transfer new files to the empty drive and it will appear them to file manager of twrp. In other words you can view only need transferred files and not the files which are already in data partition until to decrypt the data while I haven't put some code for unlocking phone.
Click to expand...
Click to collapse
what twrp you used..?, are you sure you're using latest skkk twrp version that download from here..? also did you use/ flash dfe to decrypt data..?, and what rom..?
JJeamy said:
what twrp you used..?, are you sure you're using latest skkk twrp version that download from here..? also did you use/ flash dfe to decrypt data..?, and what rom..?
Click to expand...
Click to collapse
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I have Poco F3 13.0.3.0. As many decrypt zip I i tried to flash, either the zip was failed to be flashed either was successful but the decreption was not disappeared.
What does it suppose that you can do with skkk version by comparing with official twrp version ? Does Skkk support Android 12 for decryption ? If (supposed) yes then you should have unlocked the mobile or it (is supposed) that work and with locked mobile such it happens in Android 11 ?
Johnn78 said:
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I have Poco F3 13.0.3.0. As many decrypt zip I i tried to flash, either the zip was failed to be flashed either was successful but the decreption was not disappeared.
What does it suppose that you can do with skkk version by comparing with official twrp version ? Does Skkk support Android 12 for decryption ? If (supposed) yes then you should have unlocked the mobile or it (is supposed) that work and with locked mobile such it happens in Android 11 ?
Click to expand...
Click to collapse
i don't fully understand what you write above..but i've never tried skkk twrp in miui 13 A12 rom, also i've never used dfe to decrypt
diff between official..skkk twrp indeed doesn't fully decrypted you A12 data partition...but at least it can showing your internal storage while you don't have / remove any kind of lockscreen set in your rom settings before, also without or don't need to use dfe to decrypt your A12 data to get showing your internal storage in skkk twrp (at least in aosp custom rom that i've using it from the first time)
You might need this.
JJeamy said:
i don't fully understand what you write above..but i've never tried skkk twrp in miui 13 A12 rom, also i've never used dfe to decrypt
diff between official..skkk twrp indeed doesn't fully decrypted you A12 data partition...but at least it can showing your internal storage while you don't have / remove any kind of lockscreen set in your rom settings before, also without or don't need to use dfe to decrypt your A12 data to get showing your internal storage in skkk twrp (at least in aosp custom rom that i've using it from the first time)
Click to expand...
Click to collapse
All the problem starts from the time which address to Android 12. Try it in Android 12 and check by yourself if you can view all the data of internal storage either your mobile is locked or not.
aero2zero said:
You might need this.
Click to expand...
Click to collapse
On instructions, says about formatting or wipe before flashing the dfe.zip. If I am on twrp and haven't the ability to view the data of my internal storage then the format is NOT solution because then I will lose all the data. And also via formatting, the decreption will be erased which means that the dfe may be useless except if it has other sense and I haven't understood well.
Johnn78 said:
All the problem starts from the time which address to Android 12. Try it in Android 12 and check by yourself if you can view all the data of internal storage either your mobile is locked or not.
Click to expand...
Click to collapse
I am..until now i'm still using skkk twrp and can view my internal storage with A12.1 rom (off course without any screen lock), else if i'm lazy to remove my lockscreen, i'm just doing adb sideload to flash updating rom or else, but i never using or flashing dfe to decrypt data partition, bcz always doing clean flash for migrate to diff rom, and majority have data already had backup in my pc
Johnn78 said:
On instructions, says about formatting or wipe before flashing the dfe.zip. If I am on twrp and haven't the ability to view the data of my internal storage then the format is NOT solution because then I will lose all the data. And also via formatting, the decreption will be erased which means that the dfe may be useless except if it has other sense and I haven't understood well.
Click to expand...
Click to collapse
Like i said above i never use dfe..but what i know about dfe is you must doing formatting data just for the first time of using dfe, next you migrating rom, you don't need to formatting data again, just need flash dfe after flashing rom, beside that you can refer to dfe thread or telegram to get more detail or asking how to using it properly
JJeamy said:
I am..until now i'm still using skkk twrp and can view my internal storage with A12.1 rom (off course without any screen lock), else if i'm lazy to remove my lockscreen, i'm just doing adb sideload to flash updating rom or else, but i never using or flashing dfe to decrypt data partition, bcz always doing clean flash for migrate to diff rom, and majority have data already had backup in my pc
Like i said above i never use dfe..but what i know about dfe is you must doing formatting data just for the first time of using dfe, next you migrating rom, you don't need to formatting data again, just need flash dfe after flashing rom, beside that you can refer to dfe thread or telegram to get more detail or asking how to using it properly
Click to expand...
Click to collapse
If you set lock screen, then can you view the content of internal storage on Android 12 ?
Johnn78 said:
If you set lock screen, then can you view the content of internal storage on Android 12 ?
Click to expand...
Click to collapse
Without dfe No, even with skkk twrp, except removing/ deleting first all of my lock screen
JJeamy said:
Without dfe No, even with skkk twrp, except removing/ deleting first all of my lock screen
Click to expand...
Click to collapse
With dfe and with lockscreen, you can view the internal storage ?
Johnn78 said:
With dfe and with lockscreen, you can view the internal storage ?
Click to expand...
Click to collapse
Just imo maybe...I can't sure 100% answer this..bcz like i said before, i'm never using dfe until now, so i don't have experience with dfe things.
JJeamy said:
Just imo maybe...I can't sure 100% answer this..bcz like i said before, i'm never using dfe until now, so i don't have experience with dfe things.
Click to expand...
Click to collapse
Ok because I asked you before if you can view the internal storage contents with lock screen on Android 12 and you answered "Without dfe no... " by implying that with dfe the answer is yes.
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Sqorpz said:
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Click to expand...
Click to collapse
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
If your device boots back to TWRP, it might be triggering Rescue Party. (click the 3rd button on the bottom of the screen to view the logs)
Fytdyh said:
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
Click to expand...
Click to collapse
I had installed twrp like this before and never had this type of error. But yes, the smart thing would definately be to always have backups. Lesson learned for next time!
Canny1913 said:
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
Click to expand...
Click to collapse
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Sqorpz said:
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Click to expand...
Click to collapse
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Canny1913 said:
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Click to expand...
Click to collapse
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Sqorpz said:
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Click to expand...
Click to collapse
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
T
Canny1913 said:
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
Click to expand...
Click to collapse
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Sqorpz said:
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Click to expand...
Click to collapse
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Canny1913 said:
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Click to expand...
Click to collapse
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Sqorpz said:
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Click to expand...
Click to collapse
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Canny1913 said:
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Click to expand...
Click to collapse
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Sqorpz said:
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Click to expand...
Click to collapse
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Canny1913 said:
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Click to expand...
Click to collapse
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Sqorpz said:
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Click to expand...
Click to collapse
Google One app can backup photos,SMS, phone call history and redownloads all of the apps (except apps that were installed from an apk file)
Pixel Experience actually bypasses the Google Photos storage limit so you can backup your entire gallery without problems.
For notes just use Google Keep, it syncs the notes to your Google account.
App data can be backed up by Titanium Backup or Migrate. (i suggest you test them before backing up your entire app data as suggested by Migrate developer)
I don't exactly recommend backing up Data as a whole since your only option is TWRP and TWRP loves to complain when it comes to backing up and restoring.
Thanks for the best wishes and i wish you all the best too. Have a good one.
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.
reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.
reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work
loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?
reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes