With an sudden OTA few years ago my a2 lite went into a loop and no recovery could decrypt the internal storage. Immediately i made a EDL dump of all emmc partitions and left with a encrypted data. Is tehere any chance decrypt? No password nor FP or any lock was set. Since then force disable encryption forever.
Hope in alt rtoms was bit tainted by low success, basically only syberia now is able to run without loops... If i could get rid that AB syste...
Related
Need help after "encryption unsuccessful" trying to encrypt the internal memory.
Hi experts,
yesterday I tried to encrypt even the internal memory of my Xperia M5. After pressing the start button and thereafter asking for the unlock pattern the phone showed for a second the android logo, then went into a mode, showing only an animated startup-image. For 8 hours nothing more happened. Then I pressed all 3 buttons Power-VLM up&down to restart the phone running into the error meassage screen "encryption unsuccessful". The only option was to reset the phone erasing the internal memory. WTF went wrong?
Unfortunately I have no complete backup to restore the system. And worst is that I ran the system encryption for the sd-card since 12 month already with the effect that I cannot access my picture gallery any more now. Probably the encryption key was stored in the internal memory that was erased by the reset of the phone.
Is there any way how I can regain the previous key for the sd-card encryption? I even know the PIN that I had used for encryption.
Update: I found a backup with titanium backup. How can I restore the encryption keys from there?
Basically, is it possible to backup encryption keys somehow?
PS: Phone is rooted.
I`d appreciate any help. Thanks!!!
How do I fix this i decrypted it and now this what do I have to do?
Solution
[/IHi! So are you saying it is mandatory to "unencrypt" (hence format int. storage) in order to be able to install this ROM?
not to flash ROM. You can flash it while encrypted. But it will ask you for a password on first boot. And after that you are ****** because you will lose access to the internal storage, rendering the recovery useless at this moment... however you will still have access to the phone via bootloader. After that, the only way to decrypt will be via fastboot command "fastboot format userdata" (in which you lose all your data).
From my understanding, because of this command you may experience issues with your partition. At least I had a problem: my internal storage was "cut" in half on windows when I connected phone and checked and after booting first time finally thinking everything was solved disk info also reported that I had some 30gb used, with about high 20's gbs free. I was like wtf.
However, luckily, after formatting internal storage via fastboot command you gain access back to your storage, as the encryption (which was blocking you) is gone. This way you can format (yes, again) your storage through recovery (format, not wipe). It corrects the partition and your phone is read as having 64gb of storage again.
Bottomline, as I understand, had I been decrypted from the start ( which means, before flashing the DU ROM) I wouldn't have had any problems at all with booting ROM first time after installing it and gapps, because it wouldn't ask me for a password. So I wouldn't have to fastboot command to format storage, and wouldn't have problems with partition requiring a new format (this time through recovery).
tip: don't forget to check my comments in the previous page. And I advise you to unencrypt before flashing this ROM. There are tutorials on youtube and xda developers forum certainly. Maybe even here. Good luck every one. And I sincerely only recommend rooting your phone and flashing custom roms if you get the basics of a few commands at least on fastboot and know how to backup your stuff before in case something goes very wrong and your recovery goes to ****
edit: you can decrypt and not lose your data if you backup, move backup to pc, and then, after decrypting, move everything back to your phone.
*
Hi guys,
just today I've installed latest Dirty Unicorns v11.3, so I decided to enable encryption for more secure (like in OOS by default)... but the process ended with a bootloop.
At this point, I've geniusly done a full wipe, to keep encryption and reflash system... the system now is working even with encryption.
But I've noticed that only 24 GB are usable, because 30 GB are allocated by Android system.
According to TWRP, I'm having a 24 GB /data partition.
This is a "false trouble" until first boot (because storage will be properly seen as 53 GB), but now it's happening even after booting the system!
Can you help me?
Thanks in advance
The solution is much simple: the default encryption won't be touched until typing fastboot format userdata in Bootloader Mode.
When switching between different roms, I simply have to do all the needed wipe: encryption remains in any case without any trouble, and the storage is fully usable and recognized.
The thread is now closed.
I am coming from Moto G3. It didn't have any encryption by default.
I saw some people post that they were having trouble to see files in TWRP recovery because of encryption. Can someone explain to me what's the deal with it? Should I have my phone encrypted while rooting and flashing roms? What happens if I decrypt it?
Thanks!
To my knowledge nothing is going to happen as long as the device isn't multi user. I have my data partition encrypted and TWRP works for me (actually using the blu_spark version).
so if you are using TWRP and data partition is encrypted with fingerprint unlock also set, while booting to TWRP, it will ask you to enter your password
the password is the same you used when setting up your fingerprint
while entering it, it will decrypt the storage automatically letting you flash files from internal storage
that is all you need to know
alternative way is to set security to swipe and you will boot directly to TWRP without needing a password
gwolfu said:
so if you are using TWRP and data partition is encrypted with fingerprint unlock also set, while booting to TWRP, it will ask you to enter your password
the password is the same you used when setting up your fingerprint
while entering it, it will decrypt the storage automatically letting you flash files from internal storage
that is all you need to know
alternative way is to set security to swipe and you will boot directly to TWRP without needing a password
Click to expand...
Click to collapse
So TWRP decrypts internal storage when I enter it. Does that mean the next time I boot my device I don't have encryption and need to do it manually?
aayushgala said:
So TWRP decrypts internal storage when I enter it. Does that mean the next time I boot my device I don't have encryption and need to do it manually?
Click to expand...
Click to collapse
yes TWRP decrypts the data, but you need to password every time you boot in it
also TWRP does not remove encryption, unless you format the data partition
Let's just make sure we're using the correct terms. TWRP does not decrypt the data partition, it just uses the password provided to decrypt the master decryption key and then sets the correct credentials to access the encrypted data partition. So it stays as it is; you just make it accessible by putting in the correct password.
Dear forum users,
today I'm trying to recover some data on my neighbour's phone. His Nexus 5X went into random crashing and bootloops.
As my LG G2 recently failed with no warning and no backup, I bought a emmc reader. It works well, and I managed to also recover data from a dead Zenfone 2.
But today I'm facing a different challenge. I can see his userdata volume, but filesystem is not reconized. (from what I've read, it should be ext4).
My neighbour says he never run encryption on his phone.
So far, I've managed to make a raw image of his userdata volume.
LinusReader and Active Partition Recovery (I'm running win 10) doesn't show a filesystem info on this volume.
Does anyone knows how am I supposed to mount this volume to rewordrecover some files ?
Best regards,
dFx
By default the drive is encrypted, but with a default password of "default_password".
See https://source.android.com/security/encryption/full-disk.html
As the disk is encrypted, I must find the encryption key.
But I'm not familiar with java nor C, and I can't find where the key is stored.
Btw, decrypting this full drive feels way out of my reach :S
Or is there eventually a software that would take my key and decrypt my raw 10Gb bytes of encrypted data ?