dd: conv option disabled

I am not sure to understand the reason for actually using those "conv options", WHY exactly would you want to use them?

http//stackoverflow.com/questions/20526198/why-using-conv-notrunc-when-cloning-a-disk-with-dd

A plain dd without any conv option normally works fine.

jaclaz

Maybe, but its not working fine for me ?
Its all or max filled with zeros and I am suppose to take image and then analyze it for further research.

Maybe, but its not working fine for me ?
Its all or max filled with zeros and I am suppose to take image and then analyze it for further research.

Well, the idea is (maybe was) that you had an issue and that you tried following a troubleshooting path following given advice, not doing other things or doing them without need or without a reason.

It is difficult to try and assist you if there are communication problems and you don't do the suggested tests (or fail to report about them).

The plain dd evidently worked (at least partially) since the Linux Reader was capable of (at least partially) access the image.

You were asked to verify the filesystem in use on the volume on the SDcard, did you do it?

Which filesystem is used on it?
It's not a difficult question to answer, it may exclude one of the possible reasons for the issue and we could go forward trying other things.

There may be timing reasons of some kind and you might need to make a series of partial images, as an example.

jaclaz

Check the filesystem on the SDcard volume, if it is a FAT32 filesystem you CANNOT have a properly indexed 8.1Gb file on it, what you get is a "partially indexed" file which the Linux Reader can open but obviously only partially.

jaclaz

I tried and it returnds FUSE as filesystem.

I tried and it returnds FUSE as filesystem.

I know, that's already in the screenshot you posted, that's normal since quite a few Android versions, there is a fuse overlay in the mounting.

Depending on the phone and the Android version, you may find the device "underneath", but it won't be easy, the good Google guys made a mess of storage, in order to make it simple they made it over-engineereed and senselessly complicated, JFYI
http//www.all-things-android.com/content/review-android-partition-layout

IMHO simpler
1) Switch off the phone.
2) Remove the SD card.
3) Connect it to the PC through a reader.
4) Check which filesystem is on the card volume.

jaclaz

IMHO simpler
1) Switch off the phone.
2) Remove the SD card.
3) Connect it to the PC through a reader.
4) Check which filesystem is on the card volume.

jaclaz

Its FAT32

Its FAT32

Good.
So you cannot store files bigger than 4Gb (-1 byte) on it.
https://en.wikipedia.org/wiki/File_Allocation_Table#FAT32

So you have two alternatives
1) you dd the partition to several chunks (let's say a little less than 4 gb each) by using skip= and bs= and count= and then you re-assemble the image on your PC
2) you re-format the SD card with a filesystem that allows files bigger than 4 gb and dd the whole thing to a single file.

Example
dd if=/dev/block/mmcblk0p22 of=/sdcard/test1.img bs=1024 count=4100000
dd if=/dev/block/mmcblk0p22 of=/sdcard/test2.img bs=1024 count=4100000 skip=4100000
dd if=/dev/block/mmcblk0p22 of=/sdcard/test3.img bs=1024 skip=8200000

Then on the windows machine
COPY /B test1.img+test2.img+test3.img fulltest.img

Will it work? ?
It has to be seen.

jaclaz

Any chances of data missing or anything alike while moving image by chunks , and what if tool failed to recognize it properly

Any chances of data missing or anything alike while moving image by chunks , and what if tool failed to recognize it properly

Naah, it is dd
http//www.linuxquestions.org/linux/answers/Applications_GUI_Multimedia/How_To_Do_Eveything_With_DD

it is a simple sector-by-sector, byte-by-byte copy.

jaclaz

Naah, it is dd
http//www.linuxquestions.org/linux/answers/Applications_GUI_Multimedia/How_To_Do_Eveything_With_DD

it is a simple sector-by-sector, byte-by-byte copy.

jaclaz

Thats great, let me try then I'll tell you.

Followed the first option and it worked D
Finallyy , able to open the image perfectly in FTK Imager )

Thank you !! !