HDD GURU FORUMS

Hello,

I have an KLMBG2JENB-B041 eMMC that I need to recover contacts off of. Chip came from a Motorola Droid 2. I have removed the eMMC and currently have the chip in an All Socket EMMC153/169 adapter. I have X-Ways Forensics and R-Studio as software tools. I have created an image of the userdata partition, but it appears that the partition is corrupt. When I try to open the partition itself to view the files in R-Studio, I get an error message with "The selected disk does not contain a recognizable file system or the file system is corrupt".

I tried running the "Scan" command, and it proceeded for some time before stopping prematurely with a lot of error messages like "Read disk Generic- SD/MMC 1.00 at position 31234850304 failed after 1 attempts. The media in the drive may have changed (1110)".

I am still quite new to this level of recovery, so please keep that in mind. I am not quite sure where to go from here. I was thinking that perhaps running something like fsck on the partition to potentially repair corruption, but I am not certain if that is a wise idea or how to even go about doing that when I have the chip removed. I know you would normally boot into recovery and using adbshell you can run fsck, but how do I do that from an image created of the partition or directly on the chip itself? Would I make things more difficult by attempting an fsck in the first place?

All I need are contacts. If someone can help me with this, I would be most appreciative. Thank you.

I guess it could be an F2FS file system (but shouldn't be) which UFS Explorer.
Try UFS Explorer in demo mode.

However that error you are getting from RS means it is not 'physically' reading the data due to an error.
Try saving the image from the chip again.

Also eMMC chips are very sensitive to heat when doing the chip off, so its possible it could be damaged.
Or of course the phones failure may have caused the corruption.

Allsocket eMMC sockets use Windows drivers which are not always good - try to mount those under Linux and see how it's initialize or best use some programmer that will allows you to play with VCC/VCCq voltages as also connection frequency and bus width

That's a 32GB chip, so errors at 31.2GB may not be significant.

https://semiconductor.samsung.com/estorage/emmc/emmc-5-1/klmbg2jenb-b041/

As for the FS not being recognisable, could this be due to encryption?

ddrecovery wrote:I guess it could be an F2FS file system (but shouldn't be) which UFS Explorer.
Try UFS Explorer in demo mode.

However that error you are getting from RS means it is not 'physically' reading the data due to an error.
Try saving the image from the chip again.

Also eMMC chips are very sensitive to heat when doing the chip off, so its possible it could be damaged.
Or of course the phones failure may have caused the corruption.

Thank you for the UFS Explorer tip! It was F2FS and this software did read the filesystem. I was able to navigate to data\com.android.providers.contacts, but the contents of this folder are all "Unknown" and 0 bytes. Is this because there was never any contacts stored on the phone (i.e. the contacts were all cloud synced from Google or another online account) or because it's corrupt?

I attached a screenshot so you can see what I mean. Thanks again for the help.

techwiz wrote:I was able to navigate to data\com.android.providers.contacts, but the contents of this folder are all "Unknown" and 0 bytes. Is this because there was never any contacts stored on the phone (i.e. the contacts were all cloud synced from Google or another online account) or because it's corrupt?

Might be because the owner used a seperate app for contacts, or they may be stored in a different place in the file system. Or I guess the phone might have been factory reset.

RAISE (US$25) can handle F2FS:

https://www.raisedr.com/download/

It is produced by the same people as UFS Explorer.

fzabkar wrote:RAISE (US$25) can handle F2FS:

https://www.raisedr.com/download/

It is produced by the same people as UFS Explorer.

Thank you. I will check that out.

ddrecovery wrote:Might be because the owner used a seperate app for contacts, or they may be stored in a different place in the file system. Or I guess the phone might have been factory reset.

Supposedly it wasn't factory reset according to my customer, but you very well may be right. Do you know of any other locations in the file system that contacts might be stored in besides the location I already tried?

@techwiz: If you can outsource case upload it to somewhere and share link by priv - I can check this for free