[EVO 4G Android Development] TrevE:
AMON HAS MADE US A NEW RECOVERY THAT FIXES THE BAD PARTITIONS IN RECOVERY - &postcount=27

THANKS AMON (everyone buy that guy a redbull)

Zikronix has updated his step by step tutorial on how to use this. - ?t=829045

Info below just for historical purposes

-----------------------------------------

My old evo died so zikronix and i have been messing around all day trying to get a new 003 evo with 2.02 hboot on it rooted.

What we have determined is that once you flash recovery partition and partitions get mounted in recovery half of the space disappears. It does not matter what recovery partition you are using (tried amons, clockwork, even the eng recovery part). We have tried a variety of different combos of boot.img and such.

This is what we are seeing:

before recovery flashed with 2.02 003 hardware

# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 212408 0 212408 0% /dev
tmpfs 212408 0 212408 0% /mnt/asec
/dev/block/mtdblock4 358400 272388 86012 76% /system
/dev/block/mtdblock6 436224 46208 390016 11% /data
/dev/block/mtdblock5 163840 2312 161528 1% /cache
tmpfs 8192 8192 0 100% /app-cache

after flashed eng recovery, pushed recovery files manually and did a mount -a (this is the same using any recovery)

# df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 202060 0 202060 0% /dev
/dev/block/mtdblock5 81920 1296 80624 2% /cache
/dev/block/mtdblock6 218112 12812 205300 6% /data
/dev/block/mtdblock4 179200 100608 78592 56% /system
/dev/block/mmcblk0p1 7753728 674112 7079616 9% /sdcard

============================================

Even /proc/partitions sees them as wrong. - on a working 003 2.02 hboot this shows:

cat /proc/partitions
major minor #blocks name

31 0 12288 mtdblock0
31 1 1024 mtdblock1
31 2 4608 mtdblock2
31 3 3328 mtdblock3
31 4 358400 mtdblock4
31 5 163840 mtdblock5
31 6 436224 mtdblock6

In recovery:

cat /proc/partitions
major minor #blocks name

31 0 6144 mtdblock0
31 1 512 mtdblock1
31 2 2304 mtdblock2
31 3 1664 mtdblock3
31 4 179200 mtdblock4
31 5 81920 mtdblock5
31 6 218112 mtdblock6

==============================================

/proc/mtd from 003 hboot 2.02 not in recovery:

dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"

==========================================

MTD layout on 2.02 hboot with 003 hardware from my post - &postcount=10

<5>[ 5.696319] Creating 7 MTD partitions on "msm_nand":
<5>[ 5.696411] 0x00003f300000-0x00003ff00000 : "wimax"
<5>[ 5.705780] 0x00003ff00000-0x000040000000 : "misc"
<5>[ 5.707000] 0x000004340000-0x0000047c0000 : "recovery"
<5>[ 5.710510] 0x0000047c0000-0x000004b00000 : "boot"
<5>[ 5.713043] 0x000004b00000-0x00001a900000 : "system"
<5>[ 5.951934] 0x00001a900000-0x000024900000 : "cache"

MTD layout on 0.76 hboot with older 003 hardware from zikronix post - &postcount=12

<5>[ 3.319244] Creating 7 MTD partitions on "msm_nand":
<5>[ 3.319366] 0x00003f360000-0x00003ff60000 : "wimax"
<5>[ 3.333801] 0x00003ff60000-0x000040000000 : "misc"
<5>[ 3.334991] 0x000004240000-0x000004740000 : "recovery"
<5>[ 3.341033] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 3.344421] 0x0000049c0000-0x00001a7c0000 : "system"
<5>[ 3.852111] 0x00001a7c0000-0x0000247c0000 : "cache"
<5>[ 4.036437] 0x0000247c0000-0x00003f360000 : "userdata"

My best guess is offsets changed which is why we are seeing the missing space and failed flashes in recovery. Any recovery image gurus out there?