Cellebrite and SGH T139

I haven’t tried that particular phone but it happens now and again. It is due to the fact that dumping the phones memory modules are not related to the phones files system. Think of it like when you remove a hard drive from a computer and imaging it just because you have an exact copy of the hard drive does not guaranty that you can understand the file system on the hard drive. It is the same here.

I guess you could try to manually run some of the scripts on the bin file or throw it in a program like filejucier or foremost.

Have you tried programs like FTK or EnCase?

I've run into that a few times with my UFED but have had luck opening and deconstructing the dump with my computer forensic software. I use ILookIX, which just treated the dump like any other acquisition. Of course there's more work in looking through the files, since they're not broken down into pretty little categories like in PA. )

Thanks for the input. I haven't tried FTK or Encase yet because of what's Dave describes with the unprettty categories, Was hoping Ron Sarver might jump in with some type of patch before I have to manually work through it.

I wanted to make a quick post to let everyone know that Ron Sarver from cellebrite did contact me and went above and beyond to help me with the problem. Not sure where else you could go to get better tech support than that. Thanks Ron.

Hello!

I use our UFED Touch Ultimate to aquire/analyse mobilephones.

Had the same problem after making physical image of a samsung GT-E1182.

I just can see the image, but no analysed data (checked several plugins - no chance).

But in the aquired image hexview in Physical Analyzershows that there are datas like phone numbers…

Solution? Thanks in advance

greets from austria