Did you try dd without optional parameters ? If it is a dd built for small memory, I would start like that.
Yes, I have tried that , but the resultant image is not readable by FTK and AUTOPSY both.
Well you have to see what is INSIDE the resulting file.
If both files are filled of (say) 00's and only differ for size, then the issue is with dd.
jaclaz
Well you have to see what is INSIDE the resulting file.
If both files are filled of (say) 00's and only differ for size, then the issue is with dd.
jaclaz
Its not all filled with 0s, It shows partitions but there is nothing inside them. like
"……..m.e.t.a.d.a.t.a…………………………………………………¢ Ðëå¹3D.Àh¶·&.Çø[Ö Þè.A.4.1..=7……..ÿ.U………….s.y.s.t.e.m…………………………………………………….¢ Ðëå¹3D.Àh¶·&.Ç»ÀðF'ò¶N¸/f@..ãm..U…..ÿÿa………….c.a.c.h.e………………………………………."
Its not all filled with 0s, It shows partitions but there is nothing inside them. like
"……..m.e.t.a.d.a.t.a…………………………………………………¢ Ðëå¹3D.Àh¶·&.Çø[Ö Þè.A.4.1..=7……..ÿ.U………….s.y.s.t.e.m…………………………………………………….¢ Ðëå¹3D.Àh¶·&.Ç»ÀðF'ò¶N¸/f@..ãm..U…..ÿÿa………….c.a.c.h.e………………………………………."
No.
What you posted shows NOTHING that you can call "partitions" (and BTW it is rather pointless to post a snippet of the "text view" of a binary/hex file).
Seemingly dd is working fine.
Either the tools you are using to open/inspect/parse the resulting file are not suited for it, actually very likely (again) you are imaging the "wrong" partition.
What is the output of the mount command in the shell, *like* here
http//
When you mount /data (or mount /userdata) it should show the filesystem (like Ext4 in the example) of the device, besides the actual /dev/block/mmcblk0p??.
jaclaz
I have done that mount it is partition with type ext4
but, I am using mmcblk0p22 bcz of this
Good ) , so it is the "right" partition, and it is - at least in adb - seen as an Ext4 filesystem.
Evereything seems "correct".
What happens if you run fsck -N on that partition?
Can you try mounting the /sdcard/test.img and try on it as well the fsck -N?
How big (in size, EXACT number of bytes) the resulting /sdcard/test.img?
I mean, it is not that you are hitting a file size issue on the (I presume FAT32 formatted) SD card?
What happens (on Windows) if you try acessing it with Linux-reader
http//
like suggested here
http//
jaclaz
I tried moving to both /dev/block/mmcblk0p22 and /dev/block/platform../userdata but its not allowing me to move to mmcblk0p22 and userdata both as it is displaying NOT A DIRECTORY message on screen.
I tried moving to both /dev/block/mmcblk0p22 and /dev/block/platform../userdata but its not allowing me to move to mmcblk0p22 and userdata both as it is displaying NOT A DIRECTORY message on screen.
What do you mean "moving to"? 😯
jaclaz
Its returning
fsck <busybox 1.24.2 stericson, TIME INFO>
fsck can't read /etc/fstab No such file or directory
[fsck.auto (1) – ] fsck auto /dev/block/mmcblk0p22