MID8024 partition information

Discussion in 'Coby Generation 2 Technical' started by tfurrows, Aug 16, 2011.

  1. tfurrows

    tfurrows Member

    Joined:
    Jun 15, 2011
    Messages:
    58
    Likes Received:
    11
    Trophy Points:
    72
    Location:
    Phoenix AZ
    Tablet / Device:
    SYTAB10MT
    I hadn't been able to find this information anywhere, so I thought i'd go ahead and post it in case it's useful to anyone.

    The Kyros MID8024 NAND is partitioned into 6 sections. You can view them with a simple 'cat /proc/mtd' (obtain soft root via psneuter and adb as described in many other places). Here is the output:

    Code:
    # cat /proc/mtdcat /proc/mtd
    dev:    size   erasesize  name
    mtd0: 00080000 00020000 "misc"
    mtd1: 00800000 00020000 "recovery"
    mtd2: 00600000 00020000 "kernel"
    mtd3: 00400000 00020000 "logo"
    mtd4: 06b00000 00020000 "rootfs-combin"
    mtd5: 00200000 00020000 "param"
    I have dumped the contents of each of these partitions, you can do the same with the following commands (with output):

    Code:
    # dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
    dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096
    2048+0 records in
    2048+0 records out
    
    
    # dd if=/dev/mtd/mtd2 of=/sdcard/kernel.img bs=4096
    dd if=/dev/mtd/mtd2 of=/sdcard/kernel.img bs=4096
    1536+0 records in
    1536+0 records out
    
    
    # dd if=/dev/mtd/mtd3 of=/sdcard/logo.img bs=4096
    dd if=/dev/mtd/mtd3 of=/sdcard/logo.img bs=4096
    1024+0 records in
    1024+0 records out
    
    
    # dd if=/dev/mtd/mtd4 of=/sdcard/rootfs-combin.img bs=4096
    dd if=/dev/mtd/mtd4 of=/sdcard/rootfs-combin.img bs=4096
    27392+0 records in
    27392+0 records out
    
    
    # dd if=/dev/mtd/mtd5 of=/sdcard/param.img bs=4096
    dd if=/dev/mtd/mtd5 of=/sdcard/param.img bs=4096
    512+0 records in
    512+0 records out
    You can determine the size of each partition with the data above, but here is what the file system shows after copying them over to my PC:

    Code:
    misc.img - 512KB
    recovery.img - 8,192KB
    kernel.img - 6,144KB
    logo.img - 4096KB
    rootfs-combin.img - 109,568KB
    param.img - 2,048KB
    If you examine these (With a hex editor, PSPad Hex or the like) you find:
    1. The "misc" partition is entirely full of data. No ASCII or anything else recognizable, no padding.
    2. The "recovery" partition is almost entirely full, with maybe the last 10% padded.
    3. The "kernel" is about 75% full, 25% padding (these are rough estimates folks)
    4. The recovery and kernel images are VERY similar in the first portion of the partitions.
    5. You can open the logo.img partition dump in GIMP, it is a bitmap of the Coby logo. The partition has about 25% padding, but it opens in GIMP anyway.
    6. The "param" partition mentions "softmac" and has a mac address, almost entirely padding other than that.
    7. The rootfs-combin partition is exactly as you would expect for a root file system.
    I haven't tried doing anything else with these files. Hope the info comes in handy for someone.
     
    Last edited: Aug 16, 2011
    • Like Like x 4
  2. tfurrows

    tfurrows Member

    Joined:
    Jun 15, 2011
    Messages:
    58
    Likes Received:
    11
    Trophy Points:
    72
    Location:
    Phoenix AZ
    Tablet / Device:
    SYTAB10MT
    I should add this from dmesg concerning the NAND and mtd partitions:

    Code:
    <4>[    1.413574] S3C NAND Driver is using hardware ECC.
    <6>[    1.418176] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    <5>[    1.426744] Creating 6 MTD partitions on "s5pv210-nand":
    <5>[    1.432022] 0x000000080000-0x000000100000 : "misc"
    <5>[    1.438423] 0x000000100000-0x000000900000 : "recovery"
    <5>[    1.445377] 0x000000900000-0x000000f00000 : "kernel"
    <5>[    1.449639] 0x000000f00000-0x000001300000 : "logo"
    <5>[    1.453861] 0x000001500000-0x000008000000 : "rootfs-combin"
    <5>[    1.489050] 0x000001300000-0x000001500000 : "param"
    <5>[    1.491708] UBI: attaching mtd4 to ubi0
    <5>[    1.491752] UBI: physical eraseblock size:   131072 bytes (128 KiB)
    <5>[    1.491811] UBI: logical eraseblock size:    129024 bytes
    <5>[    1.491862] UBI: smallest flash I/O unit:    2048
    <5>[    1.491907] UBI: sub-page size:              512
    <5>[    1.496372] UBI: VID header offset:          512 (aligned 512)
    <5>[    1.502173] UBI: data offset:                2048
    <5>[    2.292769] UBI: attached mtd4 to ubi0
    <5>[    2.292810] UBI: MTD device name:            "rootfs-combin"
    <5>[    2.292864] UBI: MTD device size:            107 MiB
    <5>[    2.292912] UBI: number of good PEBs:        855
    <5>[    2.292956] UBI: number of bad PEBs:         1
    <5>[    2.293821] UBI: max. allowed volumes:       128
    <5>[    2.298445] UBI: wear-leveling threshold:    256
    <5>[    2.303027] UBI: number of internal volumes: 1
    <5>[    2.307446] UBI: number of user volumes:     1
    <5>[    2.311872] UBI: available PEBs:             0
    <5>[    2.316285] UBI: total number of reserved PEBs: 855
    <5>[    2.321137] UBI: number of PEBs reserved for bad PEB handling: 8
    <5>[    2.327117] UBI: max/mean erase counter: 14/3
    <5>[    2.331456] UBI: image sequence number: 0
    <5>[    2.335555] UBI: background thread "ubi_bgt0d" started, PID 1048
    
    and this:

    Code:
    <3>[    6.842725] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
     
    Last edited: Aug 16, 2011
  3. flxrms

    flxrms Senior Member Developer

    Joined:
    Mar 23, 2011
    Messages:
    365
    Likes Received:
    52
    Trophy Points:
    102
    Location:
    Manila
    Tablet / Device:
    epad
    i was able to get those img files but i cant unyaff them..image error or something..any chance you can extract "kernel and rootfs-combin" them..then zip or rar and share to us? really appreciate that :) so i can combine them to my modified c8lean rom for 7024/8024.
     
  4. tfurrows

    tfurrows Member

    Joined:
    Jun 15, 2011
    Messages:
    58
    Likes Received:
    11
    Trophy Points:
    72
    Location:
    Phoenix AZ
    Tablet / Device:
    SYTAB10MT
    I don't think the raw partition dump is going to be in Yaffs or another format as you might expect, they would likely take some work to use. I suspect this work has been done before though, no use re-inventing the wheel. Someone in the know would likely already have these dumps and be working with them; found this info that might shed some light as well for those interested:

    HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki
     
    Last edited: Aug 17, 2011
    • Like Like x 2
  5. eldade

    eldade Member

    Joined:
    Aug 21, 2011
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    60
    Location:
    Brazil
    Tablet / Device:
    Coby MID8024
    Hi guy, can you send me a original backup of your kyros? (.img)

    Actually my is bricked.

    Tank's
     

Share This Page