dd: conv option disabled

I believe (but I may well be wrong) that the partition needs to be unmounted. ?
But it should be OK if the -N switch (or maybe the -n) is given (and it is working).

jaclaz

I have tried it with -n/N , its giving the same result.

Then maybe your install of busybox misses some files
http//android.stackexchange.com/questions/69629/fsck-auto-no-such-file-or-directory

Can you try the other test(s)

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//www.diskinternals.com/linux-reader/
like suggested here
http//forum.xda-developers.com/showthread.php?t=2450045

jaclaz

The size of Image is 8.1 GB
nd when I try to access it with linux reader it shows the directories but when I open them it shows ' There are no recoverable files here' or some folders don't get opened.

What if your target sdcard is bad ? It is supposed to be FAT formatted or is it ext4 ? If it is FAT, how can you save a 8.1GB image on it, since the 4GB file size limit ?!

What if your target sdcard is bad ? It is supposed to be FAT formatted or is it ext4 ? If it is FAT, how can you save a 8.1GB image on it, since the 4GB file size limit ?!

Well, how I can check that ? Is there any way to save the image directly to connected PC? will it solve my problem ? sd card is of 16 GB, so I don't think there is problem with size.

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.

You can't just move it like that, it's not a file, it's a device. You can read from it, write to it, but not copy or move it directly.

For busybox dd, are you sure you're using it as "busybox dd" instead of just "dd"?

Have you tried dumping it to PC directly, either via "adb root" and then "adb pull /dev/block/mmcblk0p22 c\mmcblk0p22_dump.img" (this rarely works, but it's worth a shot), or with a help of netcat, like here.

Well, how I can check that ? Is there any way to save the image directly to connected PC? will it solve my problem ? sd card is of 16 GB, so I don't think there is problem with size.

The problem is not with size of the SD card, the problem is with filesystem used for the volume inside the SDcard.
Quick recap

• FAT32 max file size is 4Gb (-1 byte)
• ext4 no such limit
• exFat no such limit
• NTFS no such lmit

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.

Re-format the SDcard as Ext4 or ExFat (Ext4 is the best choice, it is possible that ExFAT is supported but it's not probable, while surely there won't be NTFS support in Android/Adb) and try again the dd.

jaclaz

You can't just move it like that, it's not a file, it's a device. You can read from it, write to it, but not copy or move it directly.

For busybox dd, are you sure you're using it as "busybox dd" instead of just "dd"?

Have you tried dumping it to PC directly, either via "adb root" and then "adb pull /dev/block/mmcblk0p22 c\mmcblk0p22_dump.img" (this rarely works, but it's worth a shot), or with a help of netcat, like here.

Yeah I got that, I tried the command as fsck -N /dev/block/mmcblk0p22
Yes, I was using busybox dd, I re-installed it and now conv options are working fine with it. the problem is with image as it is creating images filled with zeros.

Yes ,I did but its giving error like
adb error Can't create "c\mmcblk0p22_dump.img" , no such directory.

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