Hi There,
I'm attempting to recover the data from my adopted storage sdcard.
My phone is corrupted and TWRP is the only way I can access it, my usb port is broken has no data connectivity. I'm lucky that I can still charge it. The phone is old and not really worth repairing.
I've followed the instructions (https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html) on how to mount an adopted SDCARD in a linux machine. I found the /data/vold/expand_*.key file and used it to run the dmsetup command.
However the resulting block device is not decrypted properly, I'm guessing due to an invalid key (might also explain why the booted marshmallow can't see it either). TWRP mounts the device correctly, so the correct key is on my phone somewhere.
Does anyone know how TWRP determines what the key is for the Adoptable storage?
Thanks Heaps.
Mark
I discovered that I was using the wrong byte order for the key. Maybe the key is read differently depending on the native format of the CPU (I've no idea what byte order a HTC M8 is anyway) but reversing every 2 bytes of the key file has allowed me to mount my SDCard on a linux machine.
Related
OK, so the DNA has support when booted into the OS for USB OTG cables/thumb drives... is it a pipe dream getting the same feature in recovery?
I've tried with both TWRP and CWM to no avail. When in the phone's OS, the mount point is located at: /storage/USB but that doesn't appear in either recoveries.
My reason for asking is simple: Considering the DNA's weakest feature is the storage space (both the relatively small amount and lack of SD Card slot), it would be beneficial for many to enable it so that when performing nand backups, ROM/Mod/Script flashes, etc. in recovery, one could actually store all of those items on the Thumb Drive rather than the internal storage. I'm finding it very painstaking to have to perform these types of items, having to copy/paste/move/delete them on and off the phone's "SDcard" folder... it's also somewhat of a risk if your phone somehow gets hosed and you didn't move your files off of the phone prior to the hosing.
HTC may not have given us more storage options (dare I say like the iPhone, where you can get 32/64gb+ space), but with USB OTG we can use a thumb drive as our sdcard.
WorldOfJohnboy said:
OK, so the DNA has support when booted into the OS for USB OTG cables/thumb drives... is it a pipe dream getting the same feature in recovery?
I've tried with both TWRP and CWM to no avail. When in the phone's OS, the mount point is located at: /storage/USB but that doesn't appear in either recoveries.
My reason for asking is simple: Considering the DNA's weakest feature is the storage space (both the relatively small amount and lack of SD Card slot), it would be beneficial for many to enable it so that when performing nand backups, ROM/Mod/Script flashes, etc. in recovery, one could actually store all of those items on the Thumb Drive rather than the internal storage. I'm finding it very painstaking to have to perform these types of items, having to copy/paste/move/delete them on and off the phone's "SDcard" folder... it's also somewhat of a risk if your phone somehow gets hosed and you didn't move your files off of the phone prior to the hosing.
HTC may not have given us more storage options (dare I say like the iPhone, where you can get 32/64gb+ space), but with USB OTG we can use a thumb drive as our sdcard.
Click to expand...
Click to collapse
Have you tried poking around in /dev or similar folders for the drive?
I have an S3 whose external SD card failed and it won't mount. I had most of the data backed up, but a few things I'm really trying to get to. Unforunately, to add insult to injury, the SD card was also encrypted.
When I remove the SD card and place it in a Linux computer, I can see the files by correct (cleartext) filename. I can download them. However, when I try to open a jpg or play a video, I get an error that it's not a recognized file type. I believe this is due to eCryptfs file encryption, but I'm not sure.
I was able to recover the key file from the root of the phone, but I'm still unable to decrypt the files.
Can anyone provide a brief overview of the type of encryption on this device (ie, confirm or not confirm that external SD cards are encrypted with eCryptfs) and provide general settings as to how it's encrypted? I think I have all of the raw tools to decrypt the data and rescue whatever I can, but I'm not sure I have the settings right or even the right encryption type (could it be dm-crypt?).
Any help appreciated.
Please can anyone offer some simple answers and advice for me and my situation
Due to poor advice I optioned to get over a "Damaged Memory" screen by choosing the 'Reset' button, the advice said all files could then be recovered by various 'recovery software tools' available. Now I find that my version of Android has no option to float the 'internal' memory to a PC as 'removable storage' only the irritating MTP transfer thing!
So my question is...
Is there any simple way to enable UMS for the INTERNAL drive on the phone?
BTW I should say I have tried a UMS re-enabling apk but this only makes good UMS for EXTERNAL drives, NOT INTERNAL.
The only thing I can I think of is to take the firmware back to before the 'wizards' at Samsung removed the UMS option, though to be honest I don't know if the internal drive was ever mountable in Windows as a 'removable drive'.
FYI My device is not rooted.....yet!
Thanks
Steve
PS: I did try the DR.Fone for Android recovery software, which seems perfect but it couldn't connect via UMS so found nothing.
Internal is an emulated memory, cannot be mounted as UMS regardless of root.
dxppxd said:
Internal is an emulated memory, cannot be mounted as UMS regardless of root.
Click to expand...
Click to collapse
Sorry I need to be completely clear here......
Are you saying there is ABSOLUTELY no way of recovering ANY data from the factory reset INTERNAL memory?
It is possible to dump the entire partition to your pc, go search and read those who have tried.
Trying to find the files afterward is like trying to unscramble eggs, but software on your pc would be able to access the partition at least.
Sent from my GT-I9300 using Tapatalk
Hi all,
I've bought Le Max 2, which supposedly failed during OTA Update, and bootlooped. What I got, is totally Bricked phone with TWRP 3.0.2, which was already installed, when the phone arrived.
This would be no problem for me if the device mounted at least once. I am a native linux user, so the drivers were never an issue for me. However Windows 10 also doesn't detect the device in any mode (TWRP -> Mount, fastboot, ADB Sideload). It shows however "The device cannot be recognized" notification. In the device manager the phone is shown as "Unknown device (device descriptor cannot be read)". The Linux Mint 18.1 does not detect it at all.
I've also tried to copy the ROM on Vfat and ExFat formatted pendrive, but the pendrive's diode doesn't even flash once, so I doubt TWRP doesn't mount it due to wrong filesystem type.
I would suspect damaged USB-C port, but the device charges normally.
I've also noticed, that the system partition is formatted.
Another curiosity: when I try to mount /data from TWPR->Advanced->Terminal, it returns an error: device or resource busy - always. If I try to mount /system, it does it.
What do You think? Would it charge, if only one pin in the USB-C was damaged? That's my best guess. Or maybe is it software-related? Somebody deleted too many things from partitions?
I just do not want to buy new bottom board, and change it only to find out, that I didn't know something about this phone (Yaay! It's first LeEco in my mobile service! ).
It appears, that the bottom board / usb charging board was damaged. After replacing the device mounts as expected.
resolved it by flashing the cuocos fastboot rom and after that power off the device and attach the usb otg...and ur done this worked for me i hope it also work for you
I've been using LineageOS on my phone for months without issues, until yesterday when I got an error message at boot: "Can't load Android system. Your data may be corrupt", etc. In the end I had to format and reinstall everything, but I'm worried that the internal flash memory could be getting defective or something.
Is there a way to check if there are "bad blocks" with the internal storage? (I mean physical issues, not the filesystem, like chkdsk or smart for hdds)
My phone is not rooted, so I've tried booting into recovery and launching adb shell, but I don't know how to proceed from there. Any help would be appreciated.
There is no way? with adb or with any other method?