New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot decrypt data partition #247

Closed
Nirudha opened this Issue Dec 26, 2013 · 83 comments

Comments

Projects
None yet
@Nirudha
Copy link

Nirudha commented Dec 26, 2013

I'm on a Nexus 5 running the 4.4.2 derived Cataclysm ROM. I have Android encryption enabled and in the past have had no issues accessing the data partition from TWRP. However I used the following tool to change the decrypt password and unlink it from the screen unlock PIN.

https://play.google.com/store/apps/details?id=org.nick.cryptfs.passwdmanager

Now TWRP cannot decrypt the partition though Android itself has no issue and boots fine using it. Last log file is at https://drive.google.com/file/d/0B_-eQ07F2l3iVnZiOWpnaTRBdUU/edit?usp=sharing

The error just states that the password is incorrect.

@kogir

This comment has been minimized.

Copy link

kogir commented Dec 29, 2013

I'm using an HTC One Developer Edition converted to the Google Phone Edition. It's on 4.4.2.

I used the same utility to change the password on 4.4, and it worked fine in TWRP. On 4.4.2, nothing works, even when the passwords are in sync (reset by changing the PIN). I'm guessing something changed between 4.4 and 4.4.2 with respect to encryption, key derivation, or however you check for success.

Please let me know if there's any other information I can provide that might help.

@kogir

This comment has been minimized.

Copy link

kogir commented Dec 29, 2013

Actually, ro.crypto.scrypt_params=16:3:1 in build.prop leads me to believe they switched from PBKDF2 to scrypt.

@kogir

This comment has been minimized.

Copy link

kogir commented Dec 29, 2013

Oh, neat, the details are here: https://android.googlesource.com/platform/system/vold/+/android-4.4.2_r1/cryptfs.c

I'll try my hand at submitting a patch.

@Nirudha

This comment has been minimized.

Copy link

Nirudha commented Dec 29, 2013

Hi Nick,

I just double checked now by resetting the pin and twrp does decrypt the
partition once I do. I'll check my build prop settings.

Thanks.
On Dec 29, 2013 6:22 AM, "Nick Sivo" notifications@github.com wrote:

Actually, ro.crypto.scrypt_params=16:3:1 in build.prop leads me to
believe they switched from PBKDF2 to scrypt.


Reply to this email directly or view it on GitHubhttps://github.com//issues/247#issuecomment-31308508
.

@gumbi2400

This comment has been minimized.

Copy link

gumbi2400 commented Jan 3, 2014

I am having this issue as well. I did attempt to change the pin with no effect. I'm suspect its due to the switch to script on 4.4.2. I'm using TWRP 2.6.3.1 (the latest available for my d2vzw). The relevant log is:

Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:Unable to mount '/external_sd'

If I'm missing something please let me know.

@Nirudha

This comment has been minimized.

Copy link

Nirudha commented Jan 4, 2014

I reset the crypt fs password to a new one which is NOT the pin code and
TWRP was able to decrypt it. So perhaps it was the password itself. Maybe
some of the characters were not being entered properly with the TWRP
keyboard.
On Jan 3, 2014 11:00 PM, "gumbi2400" notifications@github.com wrote:

I am having this issue as well. I did attempt to change the pin with no
effect. I'm suspect its due to the switch to script on 4.4.2. I'm using
TWRP 2.6.3.1 (the latest available for my d2vzw). The relevant log is:

Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:Unable to mount '/external_sd'

If I'm missing something please let me know.


Reply to this email directly or view it on GitHubhttps://github.com//issues/247#issuecomment-31538295
.

@gumbi2400

This comment has been minimized.

Copy link

gumbi2400 commented Jan 5, 2014

Tried resetting password separately and together. Still no luck. I guess I'll be wiping my data partition. Sad day...

@ldanicel

This comment has been minimized.

Copy link

ldanicel commented Feb 9, 2014

Any updates here ? I have 4.4.2 and experience the same issue... if you need logs or testing I can provide since I'm stuck with my phone encrypted and not being able to flash/update my firmware :)

@gumbi2400

This comment has been minimized.

Copy link

gumbi2400 commented Feb 9, 2014

Unfortunately, no update for me. I eventually had to wipe everything and start over again. It was not fun. If you do go that route. Make sure you have a full backup from something like Titanium Backup.

@ldanicel

This comment has been minimized.

Copy link

ldanicel commented Feb 9, 2014

I'd prefer seeing this fixed. I just finished setting this up from a fresh install and will definitely not go through it again :)
Are there no devs around ?

@cyber25

This comment has been minimized.

Copy link

cyber25 commented Feb 10, 2014

Few days ago updated my HTC One to 4.4.2 rom (Elegancia) and got the same problem... Resetting password don't help. Tried TWRP v2.6.3.3 & 2.6.3.4. As result - cannot install OTA update :(

@edoardocomar

This comment has been minimized.

Copy link

edoardocomar commented Feb 12, 2014

Same issue here.
Galaxy Note 2, custom 4.4.2 ROM is Unofficial CyanogenMod11-Linaro
TWRP 2.6.3.1 - but have tried also 2.6.3.0, 2.6.1.0 ...

init.svc.adbd=running

I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Is encrypted, do decrypt page first
I:Switching packages (TWRP)
I:Set page: 'decrypt'
I:Set page: 'trydecrypt'
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sdcard
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Set page: 'trydecrypt'
Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Cannot find file /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Cannot load settings -- encrypted.
I:Switching packages (TWRP)
I:Set page: 'reboot'
I:Set page: 'rebootcheck'
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 2.6.3.1 on Wed Feb 12 13:09:28 2014
BOARD_HAS_NO_REAL_SDCARD := true
I:Internal path defined: '/data/media'
I:External path defined: '/external_sdcard'
I:Mount: Unable to find partition for path '/data'
SP1_NAME := efs
SP2_NAME := modem
RECOVERY_SDCARD_ON_DATA := true
TW_NO_USB_STORAGE := true
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/devices/platform/s5p-dsim.0/s6evr02/backlight/panel/brightness
Starting the UI...Pixel format: 720x1280 @ 32bpp
Pixel format: BGR_565
framebuffer: fd 4 (720 x 1280)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/efs'
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/modem'
I:Processing '/cache'
I:Processing '/system'
I:Processing '/data'
I:Can't probe device /dev/block/mmcblk0p16
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p16', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p16
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p16', current file system: 'ext4'
I:Backup folder set to '/data/media/TWRP/BACKUPS/4df1e6ef53f58fe3'
I:Settings storage is '/data/media'
I:Processing '/external_sdcard'
I:Created '/external_sdcard' folder.
I:Processing '/usb-otg'
I:Created '/usb-otg' folder.
Updating partition details...
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sdcard
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unmounting main partitions...

....

/data | /dev/block/mmcblk0p16 | Size: 10880MB
Flags: Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p16
Length: -32768
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: emmc
Fstab_File_System: ext4
Backup_Method: dd

@Dees-Troy

This comment has been minimized.

Copy link
Member

Dees-Troy commented Feb 12, 2014

4.4 Kit Kat introduced a few changes to the way that Google handles encryption / decryption so we had to update TWRP. I just did fresh encryption on 4.4.2 stock AOSP ROM on my Nexus 7 2012 grouper and the latest TWRP decrypts it fine. Make sure you're on the latest TWRP for your device. Some devices may still need to be updated to support 4.4 decryption and hopefully we'll be rolling out updates soon.

Samsung devices present a special challenge for us. TouchWiz decryption code needs to be updated to support AOSP 4.4 decryption, so as of now, it's kind of one or the other. You can have TouchWiz decrypt OR AOSP 4.4 but not both. I'm not a big fan of Samsung in general and I currently only have one Samsung TouchWiz phone in my device stable. Ideally I would like to have 2 Samsung devices -- one encrypted with TouchWiz and the other with AOSP so that I can test and ensure that both forms of encryption are properly supported with the same code.

Last I checked the HTC One's Google Edition ROM was NOT using AOSP encryption. Instead it uses whatever HTC uses in their Sense ROMs. I've not got the time or proper resources to figure out what HTC's methods are so its encryption methods are not supported by TWRP.

I consider decryption support in recovery to be a "luxury item". Most users don't use encryption and it's very time consuming to develop for and support it especially across multiple devices and versions of Android. My main goal will be to support decryption on Nexus devices. Some other device makers' stock ROMs seem to stick to AOSP's encryption routines (Sony, Asus, LG maybe). Others don't (Samsung, HTC). We also don't own or have access to many of the devices we support making it impossible for us to test and ensure that decrypt works for each device. Our source code is public and others are welcome to download it and improve the decryption routines to support their devices and hopefully push their changes up to mainline TWRP.

@Dees-Troy Dees-Troy closed this Feb 12, 2014

@kogir

This comment has been minimized.

Copy link

kogir commented Feb 12, 2014

As I mentioned in an earlier comment, Google changed both how they calculate the keys from the user's password and the format of the encryption header on disk:

https://android.googlesource.com/platform/system/vold/+/android-4.4.2_r1/cryptfs.c

Note commit c4c70f1 at https://android.googlesource.com/platform/system/vold/+log/android-4.4.2_r1/cryptfs.c

The latest TWRP for my device, 2.6.3.3, does not support scrypt key derivation.

I understand the changes, and would be happy to submit a patch that supports the new header format and key derivation, and doesn't auto-upgrade the on-disk header on non-4.4.2 devices.

The problem I ran into is that it's not clear which repo to fork, and which branch to patch. Should I ask for guidance on IRC? Should I try to merge only this change or all changes from 4.4.2?

@edoardocomar

This comment has been minimized.

Copy link

edoardocomar commented Feb 12, 2014

@Dees-Troy
you said "I just did fresh encryption on 4.4.2 stock AOSP ROM on my Nexus 7 2012 grouper and the latest TWRP decrypts it fine. "

what is your latest TWRP ?

TWRP 2.6.3.1 - the latest for t03g (Galaxy Note 2) - does not decrypt an AOSP 4.4.2 ROM (CM-11) encryption.
I even tried 2.6.3.7 for t0lte - same error.

@edoardocomar

This comment has been minimized.

Copy link

edoardocomar commented Feb 12, 2014

@Dees-Troy "I consider decryption support in recovery to be a "luxury item"."

well I think it is essential for those who run a custom recovery, isn't it?
else anyone grabbing hold of the device can slurp all the user data by restarting the phone in recovery and connecting via adb . Googling a bit looks you can even get hold of the google account credentials http://kyleosborn.com/android/AndroidPhySec.pdf

@ldanicel

This comment has been minimized.

Copy link

ldanicel commented Feb 12, 2014

@Dees-Troy - This feature is an essential basic security feature for any mobile out there.
If you don't have what it takes to fix it then what costs you to guide @kogir through the patch submitting process so that we can all benefit off this feature ?
Closing issues doesn't make them go away.

@rmenessec

This comment has been minimized.

Copy link

rmenessec commented Feb 13, 2014

Encryption is really a must-have for me. I wouldn't have installed OmniROM and TWRP2 if I had realized that I wouldn't be able to use encryption on 4.4.2. Please add this very necessary support.

@edoardocomar

This comment has been minimized.

Copy link

edoardocomar commented Feb 13, 2014

bigbiff made a build that I could test and worked :
http://forum.xda-developers.com/showpost.php?p=50278711&postcount=1181

@Xoib

This comment has been minimized.

Copy link

Xoib commented Feb 16, 2014

This issue should be re-opened ! Indeed in the Nexus 4 stock 4.4.2 and TWRP 2.6.3.3 the problem is still present.

@Dees-Troy

This comment has been minimized.

Copy link
Member

Dees-Troy commented Feb 20, 2014

I merged the fixes for 4.4 decrypt a while back (see link below). When we finish with TWRP 2.7 and do another full roll out most devices should be fixed. If you need it sooner, feel free to compile your own from the sources available in Omni.
https://gerrit.omnirom.org/#/c/1638/

While decryption support in recovery may be critical for those that want to run custom ROMs, I still firmly believe that most users do not encrypt their devices. I don't. TWRP is free open source software. We don't charge for this software and we don't get paid for the work that we do on it, so be careful what you request and be careful about how demanding your are when you request it. We do what we can but this is just a hobby for us, not a full-time job.

@ldanicel

This comment has been minimized.

Copy link

ldanicel commented Feb 20, 2014

My problem was solely with the fact that you closed the issue.
Anyway, thanks ;)

@Xoib

This comment has been minimized.

Copy link

Xoib commented Feb 20, 2014

It was the same thought than @ldanicel. Thanks @Dees-Troy !

@edoardocomar

This comment has been minimized.

Copy link

edoardocomar commented Feb 25, 2014

In 2.6.3.2 just released for the t03g (n7100, galaxy note 2) the decryption works :-)

@ldanicel

This comment has been minimized.

Copy link

ldanicel commented Feb 25, 2014

I confirm that. issue got fixed in 2.6.3.2.
Thanks @Dees-Troy !

@Xoib

This comment has been minimized.

Copy link

Xoib commented Feb 25, 2014

Ok. I hope mako will not be forgot during the next build run. By the way for mako it will be 2.6.3.4.

@gumbi2400

This comment has been minimized.

Copy link

gumbi2400 commented Mar 29, 2014

Just updated to TWRP 2.7.0.0 on my d2vzw (verizon galaxy s3). Encrypted again, and attempted to decrypt. Same error in the logs:

Warning: crypto footer minor version 2, expected 0, continuing...
Error temp mounting decrypted block device
E:Failed to decrypt data.
I:Set page: 'decrypt'

Am I missing something obvious here?

@h-2

This comment has been minimized.

Copy link

h-2 commented Apr 6, 2014

I have just updated to TWRP 2.7.0, I still cannot decrypt my data partition. The device is a Asus TF700t.

@bill-mcgonigle

This comment has been minimized.

Copy link

bill-mcgonigle commented Aug 8, 2014

Thanks for clarifying @Dees-Troy! Your strategy sounds right - not just because it'll benefit my 4.4.4 (CM11) device, but also because AOSP encryption finally seems to have "gotten it right" and manufacturers will probably move to it as they can, now and especialy with L. And the older images will still be there for people with stranded older devices. I wrote up a workaround for users needing to do updates in the meantime:
https://www.bfccomputing.com/updating-cyanogenmod-11-kitkat-milestones-on-encrypted-devices/

@jcwenger

This comment has been minimized.

Copy link

jcwenger commented Aug 19, 2014

Thank you very much for the info, @Dees-Troy.

Is there an alternate option available?

I understand that backup s of /data itself is obviously off the table. How about installing a flashable zip?

Can I use USB OTG? Is there any specific gotcha with Dev L + N5 + USB OTG?

@boeleman

This comment has been minimized.

Copy link

boeleman commented Aug 19, 2014

One option would be to check whether CWM Recovery supports your device. Then you'll have access to MiniVold in recovery mode and you can mount encrypted partitions through adb. I prefer the TWR method of just typing in my password, but as long as that does not work on my Galaxy S3, this does:

adb shell

setprop ro.crypto.state encrypted
vdc cryptfs checkpw 'your passphrase here'
mount /dev/block/dm-0 /data

and when you're done backing up/installing a zip

umount /data

@vsht

This comment has been minimized.

Copy link

vsht commented Aug 20, 2014

The 2.7.1.0 version can indeed decrypt Galaxy Nexus which was previously encrypted by AOKP or Cyanogenmod. This was not possible with 2.7.0.0. Thanks for fixing :)

@konjiki7

This comment has been minimized.

Copy link

konjiki7 commented Aug 30, 2014

"Android L decrypt is currently NOT supported. We will probably add support for this when L is finalized and all the source code is published."

Running Pure-White Android L build right now and can't wait to get the support... For now finding a means of doing a backup image without recovery....fun

@altexdim

This comment has been minimized.

Copy link

altexdim commented Sep 21, 2014

(copy from #269)
I've found a way to mount encrypted partition on HTC ONE with the latest android version 4.4.3
It's a python script, that can extract decrypted key from encrypted header and footer, so you can unterstand the algorythm.
I've got original python script from https://github.com/santoku/Santoku-Linux.git and hardcoded support for the HTC ONE (basicaly changed key size to 32, iv size to 32, aes_128_cbc to aes_256_cbc).
Here it is http://pastebin.com/TAeA6rSw
So, can i ask you @Dees-Troy to implement HTC ONE encryption into your TWRP project based on the algorythm in my script?

@bgcngm

This comment has been minimized.

Copy link

bgcngm commented Oct 21, 2014

@Dees-Troy, any words on the above comment? Could we expect support for HTC's storage encryption?

@SuperBoy22

This comment has been minimized.

Copy link

SuperBoy22 commented Oct 23, 2014

@Dees-Troy Could you please comment on the above post? Thanks

@aTanCS

This comment has been minimized.

Copy link

aTanCS commented Oct 31, 2014

LG G2 Stock ROM, TWRP 2.8.0.1, encrypted /data, can't mount. So I can't even wipe dalvik cache.

@generalmx

This comment has been minimized.

Copy link

generalmx commented Nov 23, 2014

First I'd like to thank @boeleman for his suggestion, as now I can actually decrypt my SGS3 on KitKat. I've posted a link to here with an explanation on all the SGS3 forums in xda-developers.

Starting in Android 5.0, device encryption will no longer be opt-in, instead opt-out. Perhaps instead of supporting myriad crypto libs you could try including minivold like CWM does, and provide an interface to scripts to use with it? As minivold works beautifully for me on CWM with my SGS3 encrypted by AOSP KitKat, but TWRP hasn't since pre-KitKat, and going back to pre-KitKat isn't an option anymore due to bootloader updates.

I'm going to go ahead and try the minivold binary from CWM while in TWRP, see if that works. Not sure if it needs explicit kernel support that's in TWRP's d2lte kernel already or not. But if it is a matter of just needing the binary, maybe at least some scripts could be provided to help us interact with it.

@h-2

This comment has been minimized.

Copy link

h-2 commented Dec 26, 2014

TWRP 2.8.3.0 now successfully decrypts my partition on every try [Asus TF700t]. Whatever it was, whoever fixed it: thanks a lot!

@bsilvertab

This comment has been minimized.

Copy link

bsilvertab commented Mar 11, 2015

Any updates on this issue for the M8? Running Android L and unable to decrypt E: due to to OS encryption being enabled.

@Naddiseo

This comment has been minimized.

Copy link

Naddiseo commented Mar 11, 2015

@bsilvertab, works for me. Using M8 + cm-12 (Android L).

@bsilvertab

This comment has been minimized.

Copy link

bsilvertab commented Mar 12, 2015

What kind of lock screen are you using? I'm on a numeric pin and entering that 4 digit code in twrp gets rejected. I'm on the GPE rom for the m8.

@oneleft

This comment has been minimized.

Copy link

oneleft commented Mar 28, 2015

@bsilvertab, Sense ROMs and GPE ROMs use a variant of FDE which is not supported by twrp at the moment and likely wont be anytime soon.

@bsilvertab

This comment has been minimized.

Copy link

bsilvertab commented Mar 30, 2015

@oneleft What is fundamentally different about encryption between the different ROMs? Is that not a function of Lollipop?

@bk10287

This comment has been minimized.

Copy link

bk10287 commented May 5, 2015

htc one m8 dev edition leedroid on 5.1 with twrp 2.8.6 is failing for me right now. tried 2.8.5, no luck as well.

@oneleft

This comment has been minimized.

Copy link

oneleft commented May 5, 2015

@bk10287 I wouldnt expect support for FDE in TWRP anytime soon.

On Tue, May 5, 2015 at 12:52 PM, bk10287 notifications@github.com wrote:

htc one m8 dev edition leedroid on 5.1 with twrp 2.8.6 is failing for me
right now. tried 2.8.5, no luck as well.


Reply to this email directly or view it on GitHub
#247 (comment)
.

@bk10287

This comment has been minimized.

Copy link

bk10287 commented May 19, 2015

@oneleft why not?

@garvdd

This comment has been minimized.

Copy link

garvdd commented May 24, 2015

What should I do with the m8 I have all these apps and nothing works and it's making the phone run improper,should I factory reset it

@gerroon

This comment has been minimized.

Copy link

gerroon commented Jun 4, 2015

2.8.6.0 on Mondrian SM-t320 Android 4.4.4, password failed to decrypt data. I cant go into recovery ;(

@prisriya

This comment has been minimized.

Copy link

prisriya commented Oct 25, 2015

OK. I notice from the thread that there's a challenge with 4.4.2 and Samsung Touchwiz. However, I have an encrypted phone with that combi. I have rooted it, installed TWRP. Now TWRP backup is failing because of this error - unable to mount /data... Can you please recommend how to get past that problem.

@gerroon

This comment has been minimized.

Copy link

gerroon commented Oct 25, 2015

@prisriya

You have to disable "data" portion of the backup. TWRP cant decrypt the data portion because it is encrypted. So your backup will only contain the system files.

@prisriya

This comment has been minimized.

Copy link

prisriya commented Oct 26, 2015

Thx. I will give that a try.
Q: If there's a problem when I flash a new ROM, I can only recover the system - but not the data that went along with it right?
OR
Q: If I have a backup using Titanium, can I restore the apps and the data, after restoring the system (in case there's an issue after flashing the new ROM).

Your response will be highly helpful

@Xoib

This comment has been minimized.

Copy link

Xoib commented Oct 26, 2015

@prisriya : The answers is yes for the two questions.

@prisriya

This comment has been minimized.

Copy link

prisriya commented Oct 27, 2015

Thx. @Xoib

@gerroon

This comment has been minimized.

Copy link

gerroon commented Oct 27, 2015

How about me? I answered you too ;)

@prisriya

This comment has been minimized.

Copy link

prisriya commented Oct 27, 2015

@gerroon my apologies for missing out earlier... thank you. All you folks have been instantly helping and responding... Thanks again!

@c3ph3us

This comment has been minimized.

Copy link

c3ph3us commented Dec 1, 2015

vdc cryptfs checkpw
CANNOT LINK EXECUTABLE: cannot locate symbol "__register_atf
page record for 0xb6f6002c was not found (block_size=32)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment