# Android image: cannot define file system type **URL:** \ **Category:** Autopsy Help\ **Created:** [May 19, 2020, 1:04pm UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709 "2020-05-19T13:04:19Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Fred\_Diziel](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/fred_diziel/32/956_2.png) [@Fred\_Diziel](https://sleuthkit.discourse.group/u/Fred_Diziel)\ **Post date:** [May 19, 2020, 1:04pm UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/1 "2020-05-19T13:04:19Z")
Hello, I’m trying to add a full image of my redmi note 4 phone (that has been rooted) to autopsy, but every time I tried to, a lot of the image volumes will be unallocated due to autopsy cannot define file system type, aside from the few that is actually ext4, which I think is the factory default of some sort? The files that autopsy gets from ext4 partitions looks like the default system icons and the such. ![errors](https://global.discourse-cdn.com/free1/uploads/sleuthkit/original/1X/870059708fa840ce1b6231504002546f0981ffec.png) So out of curiosity, I tried to check the device partition using sleuthkit mmls, here’s the result ![mmls result](https://global.discourse-cdn.com/free1/uploads/sleuthkit/original/1X/00cb677b2c8aec7a05de380c08a3d17c6e541f0d.png) With mmls result in mind and googling around, the viable conclusion that I could think of is that the partition that I need (mostly userdata) is probably formatted in file system that is not available in autopsy, possibly f2fs. If that is correct, are there any ways to make autopsy able to see the partitions? I’ve been looking up on reformatting the image with mkfs but I think that would destroy the existing data right? Thank you for your attention and help ---
**Author:** ![atdt0](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/atdt0/32/202_2.png) [@atdt0](https://sleuthkit.discourse.group/u/atdt0)\ **Post date:** [May 20, 2020, 1:28pm UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/2 "2020-05-20T13:28:25Z")
Hello. You are correct that Autopsy doesn’t understand those filesystems which is what throws the errors on ingest. In regards to your ‘userdata’ partition, can you look at the first sector (10748944) via blkcat or hexdump to determine the filesystem? If it is non-encrypted f2fs one possible option is to mount the filesystem with f2fs-tools, tar or zip the contents, then feed that extraction into Autopsy. ---
**Author:** ![Fred\_Diziel](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/fred_diziel/32/956_2.png) [@Fred\_Diziel](https://sleuthkit.discourse.group/u/Fred_Diziel)\ **Post date:** [May 20, 2020, 3:04pm UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/3 "2020-05-20T15:04:33Z")
Hello, thank you for your reply! Here are the result for blkcat, though I think I might do it wrong ![cannot determine](https://global.discourse-cdn.com/free1/uploads/sleuthkit/original/1X/e8f66d6a04618ef41c32cf21b03d6da208a5374f.png) After googling around, I found that I should try to check what filesystem is that partition from my phone, so I went and check it with diskinfo, and apparently, the userdata partition is ext4 but encrypted, and the program said there’s a decrypted block of the same userdata. So I went ahead and images that block and now autopsy can find and extract several things with that image, the size is also the same as my userdata block only image, so I guess this problem is solved for my case then, thank you again for your reply and information! ---
**Author:** ![asparatu](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/asparatu/32/805_2.png) [@asparatu](https://sleuthkit.discourse.group/u/asparatu)\ **Post date:** [May 26, 2020, 6:56am UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/4 "2020-05-26T06:56:46Z")
@Fred_Diziel What program did you use to make the image of your android device? ---
**Author:** ![Fred\_Diziel](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/fred_diziel/32/956_2.png) [@Fred\_Diziel](https://sleuthkit.discourse.group/u/Fred_Diziel)\ **Post date:** [May 28, 2020, 5:12am UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/5 "2020-05-28T05:12:05Z")
Hello, sorry for the late reply I used dd for imaging my device and then copy it over with nc ---
**Author:** ![asparatu](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/asparatu/32/805_2.png) [@asparatu](https://sleuthkit.discourse.group/u/asparatu)\ **Post date:** [May 28, 2020, 6:40am UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/6 "2020-05-28T06:40:04Z")
Hello, Not a problem. I suggested dd in another post to make image of an android device. Shane ---
**Author:** ![Dan\_Sorensen](https://yyz2.discourse-cdn.com/free1/user_avatar/sleuthkit.discourse.group/dan_sorensen/32/1213_2.png) [@Dan\_Sorensen](https://sleuthkit.discourse.group/u/Dan_Sorensen)\ **Post date:** [November 24, 2020, 3:24pm UTC](https://sleuthkit.discourse.group/t/android-image-cannot-define-file-system-type/1709/7 "2020-11-24T15:24:59Z")
@asparatu, are you using a specific emulator or something to make an image of an android device or where specifically are you creating the android image?