Hi, I restored miui's efs and modem trying to get volte finally working on resurrection remix but once I rebooted android said it's unable to decrypt data though the password is correct. If I reboot in recovery now, password seems wrong even if it's correct and I'm not able to recover the efs and modem backup I did for rr... What gone wrong? Is there any hope to get data back?
Related
Recently, I've been experimenting with increasing the security of my phone which was recently migrated to CM (12.1) and TWRP (2.8.5.0). Let's just say that it did not go well.
First, I tried enabling a password for my TWRP backups. I set the password/encryption option and the backup seemed to complete fine.
Problem 1:Next I tried encrypting my phone. The encryption worked fine, but once the phone was encrypted, I noticed that TWRP lost the ability to create a nandroid backup. As soon as I enabled encryption, TWRP now prompts for a password automatically when it is launched. However, when I typed my passphrase, it says "Password Failed, Please Try Again".
Problem 2:Given that I've lost the ability to do a nandroid backup, I decided to revert the decision to encrypt the phone. Which basically means wiping the phone and restoring my latest nandroid phone. The wipe went fine and the restore proceeded without error. However, upon booting up the phone, it acted as if it just went through a factory reset. (e.g. a cleared /data partition). Just as an experiment, I tried restoring a week-old TWRP backup that was not password-protected. Once I rebooted the phone, its state was identical to how it was when I backed it up. I tried going into TWRP to restore the more-recent password-protected backup, but this time I purposely typed the wrong passphrase. It said that the password was incorrect. So I typed the actual passphrase, restored the backup, and once the phone rebooted, it was back to the factory-reset mode.
Conclusions:
TWRP 2.8.5.0 cannot back up an encrypted phone. At least my M8.
TWRP 2.8.5.0 cannot restore password-protected backups.
While an encrypted phone and encrypted nandroid backups are a good idea from a security perspective, they appear to just not work. The fact that the features are advertised as working is frustrating.
Questions:
Will a newer TWRP version address either of the problems? I installed 2.8.5.0 as I had heard of some issues with newer versions.
If TWRP doesn't work for this, is there another recovery image that will both backup encrypted phones as well as support the creation and restore of password-protected/encrypted backups?
Note that I tried the latest 2.8.7.0 build of TWRP: https://twrp.me/devices/htconem8gsm.html . Although the title in that page says "all variants", the URI includes "GSM" which my phone is not. However, I can't imagine why there would be carrier-specific builts of TWRP in the first place. 2.8.5.0 is the latest Verizon-specific build of TWRP for the M8: https://twrp.me/devices/htconem8verizon.html
Anyway, when I try to do an encrypted backup with 2.8.7.0, I get:
createTarFork() process ended with ERROR=255
Which apparently has been reported by others:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/452
I get the impression that this stuff isn't close to ready for prime time.
Although I suppose that erroring at backup time is better than backing up w/o error and then only noticing that there's a problem at restore time (when you really need it). For what it's worth, looking at an encrypted TWRP file (e.g. data.ext4.win400) that was created by 2.8.5.0, it does indeed look to be encrypted. It has high entropy and magic bytes of "OAES". But something about the restoration of such a backup fails. It's not clear at this point if the two issues are related.
I'm running an encrypted OnePlus One. I went in to recovery, did a nandroid backup, then did a wipe data to test something. The phone booted fine after the wipe. Then I went back in to recovery and restored my nandroid. Now the phone won't decrypt and says I need to factory reset. Says something like "Your password is correct but decryption failed" ... Is there a way to recover my data, or am I screwed?
Got a Note 4x Mido with twrp 3.1.1-0. Did a full backup, checked every box, and transferred it over to my laptop. Tried some custom roms and wanted to go back to my previous backed up rom. Did a wipe and transferred the backup back to my phone but when I tried to restore it EFS and Firmware were causing error, everything else worked fine, booted up the phone, no wifi, bluetooth, imei gone, provably hard to fix... Tried wiping in all kinds of ways but the EFS and firmware just don't want to be restored.
EFS throws:
Unable to find file system (first period).
Unknown restore method for '/efs2'
EDIT: Tried some different versions of twrp and it worked (only EFS)
Firmware throws:
extractTarFork() process ended with ERROR: 255
Thanks in advance for the help
Try with this procedure and let us know if it worked for you:
https://forum.xda-developers.com/showpost.php?p=73770600&postcount=12
Hi guys,
I am on latest LOS for Nexus 5x (bullhead) and everything was good. I kept the phone up to date with official download from the settings. This morning I tried to flash a new kernel but just before a created a backup with TWRP (never know). I flashed the kernel -> faild. The phone was not able to boot. No problem as I created a backup...
During the restoring process -> error. There is un issue with the system partition.
I tried to flash the latest LOS updated stored in \data. No error during the install but the phone is still not able to boot, stuck on Google Logo.
Now, if I tried to boot in recovery mode and when I enter my password it tells me the password is wrong !
I flashed the latest twrp img but same issue. Not able to decrypt.
How can I access to my data ? I want at least to save what is on my sdcard..
I don't care about apps.
Thank you a lot.
Hello!
Yesterday, I updated my phone from A10 to A12 with full OTA and applied magisk on inactive slot.
After rebooting, all seems to work, no bootloop, android was optimizing apps... so far so good, I reached the point where my patter was asked. There was no problem with it.
The problem appeared when trying to open any APP and the android answer was (for any app) "Failed to read the app data. Cannot start the app"
Okay, I tried to go to settings and was unable to do so. After putting phone in airplane mode, settings worked but clearing apps cache or data did not help.
Trying to fastboot boot twrp.img did not work until I found https://github.com/rabilgic/twrp_device_oneplus_hotdogb/tree/Android-12.1 by another xda user.
Even being another device it worked (afaik they were unified twrp so they should work for both). However, once booted, the first problem appears. Inserting my patter did not decrypt the data in twrp... Booting into system removing pattern and try TWRP again and nothing changed...
Checking in twrp the data/data lead see all folders and files encrypted there... So this is probably why any app is working...
After reading, I saw that fbev2 was applied to A12 so this might be the problem. My guess was that flashing a A11 rom might save my data since the encryption should be the same older one v1. However, I am unable to flash ROMS with TWRP... Tried with OTG or sideload, but both failed. I would like to know if there is a way to flash an older rom (A10 whcih was my original one or A11) to decrypt the data or make the A12 decryption work to recover all my apps and data.
I do not know if flashing any further (of if I had already) lost the decryption keys or what is going on.
I had extracted the .img from a full A10 OTA (OOS) and I am hesitant of flashing all 32 images to the phone or if that will wipe data partition.
How can I proceed if possible without losing data with a flash, or how can I decrypt the data to make it work with A12?