how to dump your zio

---

I wrote this up in another forum and it also got lost in the 1.6 thread. Thought I'd pull it out.
---------

Instructions on how to dump your image manually:

Note: Everything in green is a command to type.

Pre)You installed the Kyocera USB drivers that came with the phone.
Kyocera ZIO - Downloads
Direct: http://www.ziobykyocera.com/download...USB_Driver.zip

Also, on the phone: Menu->Settings->Applications->Development->USB Debugging [selected]

Steps:

1. Root your phone:
   [APP] [ROOT] 1-click root for N1 (Latest ver: 1.6.2 beta 5) - xda-developers
   Direct: xda-developers
   
2. Install Android SDK for windows:
   Android SDK | Android Developers
   Direct: http://dl.google.com/android/android...07-windows.zip
   Extract that somewhere convinient, for ex: c:\
   
3. You'll need dump_image to get the img, find it here:
   My Brain Hurts: Porting Clockwork Recovery to New Devices
   Direct: http://koush.tandtgaming.com/test/dump_image
   Copy that to the root of your sdcard, we'll use it later.
   
4. Lets connet to your phone.
   Plug it in to the usb, make sure it is not mounted for reading the sdcard. On the phone, in the notification window tap the 'usb connected' notice and select "don't mount".
   Now in windows, click Start->Run and type cmd.
   
   cd \android-sdk-windows\tools\
   adb.exe devices
   
   It should list your device if all has gone well.
   adb.exe shell
   It should have connected to the phone and you have a "$" prompt.
   su root
   Now look at the phone, the Super User program (was installed after 1-click-root) should have popped up and asked if you want to allow root access, allow it.
   Now you are at a "#" prompt.
   
5. Installing dump_image:
   dump_image should be on the root of your sdcard from step 3.
   Copy it to your bin directory:
   cat /sdcard/dump_image > /system/bin/dump_image
   Give it executable permission:
   chmod 6755 /system/bin/dump_image
   
6. What to dump:
   cat /proc/mtd
   You're going to want to copy the output of that to the forum.
   There should be a number of lines begining with mtd#
   and the last name column has the name we'll need in quotes.
   
7. The dump:
   mkdir /sdcard/dumped
   dump_image boot /sdcard/dumped/boot.img
   
   That just pulled the boot image. We need to do that for all the other images now:
   dump_image name_here /sdcard/dumped/name_here.img
   There could be 6-8 of them. Total will take a couple hundred megs.
   
8. Final:
   Now we have it all, so zip up the files in /sdcard/dumped and put it on megaupload.com or something like that and post a link and the output from "cat /proc/mtd"
   

And that's it

Simple, yeah?

Some of those partitions that were listed in /proc/mtd are probably not needed, but I'm not certain as to which ones those are. I'm guessing "cache" and "userdata" probably aren't needed.

There was some issues with using the dump_image on yaffs2 partitions. For those the yaffs2 utility is useful. Here's some more info that was in the 1.6 thread:

Get it here:
http://jiggawatt.org/badc0de/android...fs2.arm.tar.gz
(I attached it as well since that's the only place I could find an actual working version)
There's also a utility to extract the yaffs2 image (source)
You can also google for "mkyaffs2image" which is for something I can't recall.

Kind of shows how to use it in the middle of this section:
http://jiggawatt.org/badc0de/android/index.html#dynamic

adb push mkfs.yaffs2 /data/misc/mkfs.yaffs2
adb shell
# cd /data/misc
# ./mkfs.yaffs2 /system /system.img
# exit
adb pull /system.img ./system.img

Other useful info:

#cat /proc/mtd
dev:    size   erasesize  name
mtd0: 01080000 00020000 "fota_amss"
mtd1: 00400000 00020000 "boot"
mtd2: 06780000 00020000 "system"
mtd3: 011e0000 00020000 "flex"
mtd4: 00500000 00020000 "recovery"
mtd5: 0ba60000 00020000 "userdata"
mtd6: 00600000 00020000 "fota_boot"
mtd7: 06780000 00020000 "cache"
mtd8: 000c0000 00020000 "misc"

#mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock2 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /data/FLEX yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

So

boot		not yaffs2
system		yaffs2
recovery	...most likely yaffs2
userdata	yaffs2
cache		yaffs2
misc		...no clue

I've also tossed a bug in clockworkmods ears -- maybe if enough people request, we can get a fully supported recovery through rom manager.

dump_image data /sdcard/data.img
can't find data partition

is this a yaffs2 partition?

edit: mkfs.yaffs2 allows me to dump the partition, dump_image will not.

Could you clarify, ftr, what filesystem each of the partitions are?

I added more info the the second post about the yaffs2 and partitions.