[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Well, I looked through this entire thread.

The thing which stands out in my mind from the original installation log that you posted is this:

The thing which stands out about this is that the above error follows this:

Normally, the format operation (called from META-INF/com/google/android/update-script) wipes the entire partition - /system in this case.

For the installer script to run out of room in /system - after it has already wiped it clean, there are really only 3 possibilities:

- you have a crapload of bad blocks which reduces the effective maximum size of the partition.

- the currently booted (recovery) kernel mysteriously does not use the correct flash memory (MTD) device partitioning sizes (this seems pretty unlikely)

- other, unknown.

The other thing which is notable about that log you posted is this:

calling command format
Formatting SYSTEM:...
mtd: not erasing bad block at 0x00020000
mtd: not erasing bad block at 0x00040000
...
mtd: not erasing bad block at 0x06d60000

You get a (possibly spurious) "bad block" message every 0x20000 bytes (64 Nand size pages of 2048 bytes)... yet mysteriously, these messages peter out at 109 MB - even though the /system partition is supposed to be 170 MB.

Note that the normal MTD layout looks like this:

(dmesg output)

Creating 6 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000002c60000-0x000003160000 : "recovery"
0x000003160000-0x0000033e0000 : "boot"
0x0000033e0000-0x00000dde0000 : "system"
0x00000dde0000-0x000015fe0000 : "cache"
0x000015fe0000-0x00001ff60000 : "userdata"

(or, alternately from cat /proc/mtd)

dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache"
mtd5: 09f80000 00020000 "userdata"

Computed either way, the system partition is supposed to be 0xaa00000 bytes - 170 MB.

Here is what I would advise: the vast majority of brickings that have been reported for the Eris involve the use of ClockWork Recovery. I honestly don't know why that is - but that is the history that has been observed.

That means that while your phone is still booting into either HBOOT or Clockwork recovery, it is nevertheless in a very precarious place - the modal experience of others that have preceded you is to create a brick with further fooling around.

If it was my phone, I would try to replace Clockwork recovery by installing the engineering bootloader, and then using fastboot to flash Amon_RA's (v1.6.0.2 Eris) recovery. Doing things this way minimizes further use of Clockwork.

The way to achieve that with a minimum of flashing is to apply the ROOT PB00IMG.ZIP (HTC Engineering ROM) using Toastcfh's "Battery Pull Trick" during the HBOOT-PB00IMG.ZIP flashing operation; this installs ONLY the bootloader, and does not touch any other partitions. ( A tutorial example with pictures that shows where this occurs is given here )

Unfortunately, you have the 1.49.0000 bootloader, so you will first need to modify the "misc" partition using jcase's procedure to over-write the misc partition ( Note: there is an error in the fourth "adb" command in his instructions - the corrected instructions are given in post #14 of that thread. )

I don't know if Clockwork recovery has a command shell available via adb (I haven't used it) - but if it does, you should be able to modify the sequence of commands to flash the "misc" image using the "flash_image" executable.

After the 1.49.2000 S-OFF bootloader has been installed, you can use fastboot directly from the PC to flash the Amon_RA recovery, as in:

(Power up your phone with Send+End to put it into fastboot mode, and then)

fastboot devices
fastboot flash recovery recovery-RA-eris-v1.6.2.img

where the first line ("fastboot devices") is just to verify that you are connected to your phone via fastboot.

Well, that's a start. If I was in your position, I would do everything humanly possible to avoid using Clockwork recovery any further. If it has an adb root shell available, you can do that.

bftb0