FORUMS
Remove All Ads from XDA

[HELP][Surrendered :( ] Fix Or Decrypt /data in order to retrieve files

14 posts
Thanks Meter: 0
 
By danoussh, Junior Member on 24th November 2019, 02:29 PM
Post Reply Email Thread
Hi,

My phone is stuck at boot stage where the rom logo animation (CrDroid rom) is animating, so no freeze. The phone never goes further than that.
I can boot into either bootloader, Fastboot (Secure boot: enabled, Lock State: unlocked) and recovery. I also have access to ADB/Fastboot from PC. I've managed to init a shell but /sdcard is empty
When I enter recovery (TWRP 3.3.1-hh), this is the content of recovery log/terminal:

Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Failed to mount '/cache' (Invalid argument)
Updating partition details...
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TRWP/.twrps
MTP Enabled
What solution do I have in order to retrieve my data? I think I encrypted the phone with a SIM PIN code, but I'm not sure because I do it sometimes when I flash a ROM, but this time I may have decided not to do it. I can't remember for sure. The other reason for my doubt is if I understand correctly, some recent versions of Android are forced encrypted, though I thought that was only valid for stock ROM which is not my case.

I found this topic (https://forum.xda-developers.com/one...-roms-t3838643) that seems to describe a process in order to get encrypted files back by flashing a ROM, but it's for OnePlus6. Do you guys think this can work for me?

Help would be much appreciated.
Best regards,

Specs: Nexus 5 (LG-D821), TWRP 3.3.1-HH, crDroidAndroid-9.0-20191014-hammerhead-v5.8 (https://forum.xda-developers.com/goo...-v5-4-t3931587)


EDIT: I gave it up in the end
28th November 2019, 11:00 AM |#2  
OP Junior Member
Thanks Meter: 0
 
More
Bump,
Anyone that can help?
30th November 2019, 08:06 AM |#3  
lulli1's Avatar
Senior Member
Thanks Meter: 827
 
More
Quote:
Originally Posted by danoussh

Hi,

My phone is stuck at boot stage where the rom logo animation (CrDroid rom) is animating, so no freeze. The phone never goes further than that.
I can boot into either bootloader, Fastboot (Secure boot: enabled, Lock State: unlocked) and recovery. I also have access to ADB/Fastboot from PC. I've managed to init a shell but /sdcard is empty
When I enter recovery (TWRP 3.3.1-hh), this is the content of recovery log/terminal:



What solution do I have in order to retrieve my data? I think I encrypted the phone with a SIM PIN code, but I'm not sure because I do it sometimes when I flash a ROM, but this time I may have decided not to do it. I can't remember for sure. The other reason for my doubt is if I understand correctly, some recent versions of Android are forced encrypted, though I thought that was only valid for stock ROM which is not my case.

I found this topic (https://forum.xda-developers.com/one...roms-t3838643) that seems to describe a process in order to get encrypted files back by flashing a ROM, but it's for OnePlus6. Do you guys think this can work for me?

Help would be much appreciated.
Best regards,

Specs: Nexus 5 (LG-D821), TWRP 3.3.1-HH, crDroidAndroid-9.0-20191014-hammerhead-v5.8 (https://forum.xda-developers.com/goo...v5-4-t3931587)

You can't decrypt files on n5.
There are 2 types of encryption:
FBE - File Based Encryption
FDE - Full Disk Encryption
We don't have fbe. When you press the encrypt button in Rom settings. You will get fde. I don't know crdroid but if you encrypted your disk, than sorry afaik no chance to rescue your files here. Go and start with formatting data partition or flash stock 6.0.1 and flash another rom again.
The Following User Says Thank You to lulli1 For This Useful Post: [ View ] Gift lulli1 Ad-Free
2nd December 2019, 10:42 AM |#4  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by lulli1

You can't decrypt files on n5.
There are 2 types of encryption:
FBE - File Based Encryption
FDE - Full Disk Encryption
We don't have fbe. When you press the encrypt button in Rom settings. You will get fde. I don't know crdroid but if you encrypted your disk, than sorry afaik no chance to rescue your files here. Go and start with formatting data partition or flash stock 6.0.1 and flash another rom again.

Thanks for the reply. I really hoped there was a way by installing a new rom above which would allow full disk encryption to be unlocked again.

EDIT: Before I give up, here is some extra info.
I can navigate through the TRWP file manager on system through folders, I see files and folders. Is that a clue that my phone is not full disk encrypted, or is full disk encrypted only for user data and the full system?
Also here is a dump I did via ADB shell.


Code:
~ # [6ncat /proc/partitions
major minor  #blocks  name

 179        0   15388672 mmcblk0
 179        1      65536 mmcblk0p1
 179        2       1024 mmcblk0p2
 179        3        512 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5        512 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7       2048 mmcblk0p7
 179        8       1024 mmcblk0p8
 179        9        512 mmcblk0p9
 179       10        512 mmcblk0p10
 179       11        512 mmcblk0p11
 179       12       3072 mmcblk0p12
 179       13       3072 mmcblk0p13
 179       14        512 mmcblk0p14
 179       15      16384 mmcblk0p15
 179       16      16384 mmcblk0p16
 179       17       3072 mmcblk0p17
 179       18      22528 mmcblk0p18
 179       19      22528 mmcblk0p19
 179       20      22528 mmcblk0p20
 179       21       3072 mmcblk0p21
 179       22        512 mmcblk0p22
 179       23        512 mmcblk0p23
 179       24        512 mmcblk0p24
 179       25    1500000 mmcblk0p25
 179       26      30720 mmcblk0p26
 179       27     265375 mmcblk0p27
 179       28   13404138 mmcblk0p28
 179       29          5 mmcblk0p29
 179       32       4096 mmcblk0rpmb
~ # [6n

------------------------------------------

~ # ls -la /dev/block/platform/msm_sdcc.1/by-name/[J
__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!
drwxr-xr-x    2 root     root           620 Jan  5 21:43 .
drwxr-xr-x    4 root     root           700 Jan  5 21:43 ..
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 abootb -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 crypto -> /dev/block/mmcblk0p26
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 grow -> /dev/block/mmcblk0p29
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 imgdata -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 laf -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 pad -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 rpmb -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 sbl1b -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 system -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Jan  5 21:43 tzb -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Jan  5 21:43 userdata -> /dev/block/mmcblk0p28
~ # [6n
2nd December 2019, 01:45 PM |#5  
OP Junior Member
Thanks Meter: 0
 
More
I gave up and decided to reinstall android.

For those who may have trouble flashing because of /data not wanting to format, try to flash new TWRP recovery (latest one for your device.). You should be able to boot back into recovery and then you can format/wipe /data.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes