[HD2 General] Photoelectric:
Thank you very much. Here's a relevant portion of the log up to the installation of the new ROM. Looks like this phone has some bad blocks. The other phone must be worse off. The current partition is 350M in size, I believe.

Starting recovery on Thu Feb 27 21:13:46 2014

framebuffer: fd 4 (480 x 800)

ClockworkMod Recovery v3.0.0.5

recovery filesystem table

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

0 /tmp ramdisk (null) (null)

1 /boot yaffs2 boot (null)

2 /cache yaffs2 cache (null)

3 /data yaffs2 userdata (null)

4 /misc mtd misc (null)

5 /recovery yaffs2 recovery (null)

6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0

7 /system yaffs2 system (null)

8 /sd-ext auto /dev/block/mmcblk0p2 (null)

I:Completed outputting fstab.

I:Processing arguments.

mtd: successfully wrote block at 0

I:Set boot command "boot-recovery"

I:Checking arguments.

I:device_recovery_start()

Command: "/sbin/recovery"

ro.secure=0

ro.allow.mock.location=1

ro.debuggable=1

persist.service.adb.enable=1

ro.build.id=FRF91

ro.build.display.id=GRH78

ro.build.version.incremental=eng.aaron.20110107.002533

ro.build.version.sdk=9

ro.build.version.codename=REL

ro.build.version.release=2.3.1

ro.build.date=Fri Jan 7 00:26:07 GMT 2011

ro.build.date.utc=0

ro.build.type=userdebug

ro.build.user=aaron

ro.build.host=aaron-iMac

ro.build.tags=release-keys

ro.product.model=HTC Desire

ro.product.brand=htc_wwe

ro.product.name=htc_bravo

ro.product.device=bravo

ro.product.board=bravo

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=HTC

ro.product.locale.language=hdpi

ro.product.locale.region=

ro.wifi.channels=

ro.board.platform=qsd8k

ro.build.product=bravo

ro.build.description=2.10.405.2 CL226611 release-keys

ro.build.fingerprint=htc_wwe/htc_bravo/bravo/bravo:2.2/FRF91/226611:user/release-keys

ro.sf.lcd_density=240

rild.libpath=/system/lib/libhtc_ril.so

ro.ril.ecc.HTC-ELL=92,93,94

ro.ril.ecc.HTC-WWE=999

ro.ril.enable.a52.HTC-ITA=1

ro.ril.enable.a53.HTC-ITA=1

ro.ril.enable.a52=0

ro.ril.enable.a53=1

ro.ril.enable.dtm=1

ro.ril.gprsclass=12

ro.ril.hsdpa.category=8

ro.ril.hsupa.category=5

ro.ril.hsxpa=2

wifi.interface=eth0

wifi.supplicant_scan_interval=15

ro.telephony.default_network=0

ro.ril.enable.prl.recognition=1

ro.ril.def.agps.mode=2

ro.opengles.version=131072

dalvik.vm.heapsize=32m

ro.media.dec.jpeg.memcap=20000000

keyguard.no_require_sim=true

ro.com.android.dateformat=MM-dd-yyyy

ro.com.android.dataroaming=true

ro.config.notification_sound=OnTheHunt.ogg

ro.config.alarm_alert=Alarm_Classic.ogg

ro.config.ringtone=DonMessWivIt.ogg

ro.rommanager.developerid=cyanogenmod

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.clientidbase=android-google

ro.com.android.wifi-watchlist=GoogleGuest

ro.setupwizard.enterprise_mode=1

ro.ril.enable.managed.roaming=1

ro.ril.oem.nosim.ecclist=911,112,113,115,117,999,000,08,118,120,122,110,119,995

ro.ril.emc.mode=2

ro.modversion=CyanogenMod-7.0.0-RC0-Desire-KANG

ro.kernel.android.checkjni=1

ro.setupwizard.mode=OPTIONAL

dalvik.vm.dexopt-flags=m=y

net.bt.name=Android

net.change=net.bt.name

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.factorytest=0

ro.serialno=

ro.bootmode=unknown

ro.baseband=unknown

ro.carrier=unknown

ro.bootloader=unknown

ro.hardware=htcleo

ro.revision=0

init.svc.recovery=running

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

mtd: successfully wrote block at 0

I:Set boot command ""

-- Wiping data...

Formatting /data...

mtd: erase failure at 0x00e80000

mtd: not erasing bad block at 0x04440000

mtd: erase failure at 0x0be20000

mtd: erase failure at 0x185c0000

mtd: erase failure at 0x1a960000

mtd: erase failure at 0x1b300000

Formatting /cache...

Formatting /sd-ext...

I:Formatting unknown device.

rm: can't remove '.' or '..'

rm: can't remove '.' or '..'

Formatting /sdcard/.android_secure...

I:Formatting unknown device.

rm: can't remove '.' or '..'

rm: can't remove '.' or '..'

Data wipe complete.

mtd: successfully wrote block at 0

I:Set boot command ""

-- Wiping cache...

Formatting /cache...

Cache wipe complete.

mtd: successfully wrote block at 0

I:Set boot command ""

rm: can't remove '/data/dalvik-cache': No such file or directory

rm: can't remove '/cache/dalvik-cache': No such file or directory

rm: can't remove '/sd-ext/dalvik-cache': No such file or directory

Dalvik Cache wiped.

mtd: successfully wrote block at 0

I:Set boot command ""

-- Installing: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip

mtd: successfully wrote block at 0

I:Set boot command "boot-recovery"

Finding update package...

I:Update location: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip

Opening update package...

Installing update...

about to run program [/sbin/umount] with 2 args

umount: can't umount /system: Invalid argument

run_program: child exited with status 1

about to run program [/sbin/erase_image] with 2 args

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

DARKSIDE.SUPER.WIPE

SGSII SGH-T989

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

..A DARKSIDE DEVELOPMENT..

[*] Preparing Device...

[*] Running DARKSIDE.SUPER.WIPE...

> Wiping SYSTEM partition

mtd: erase failure at 0x0b8e0000

mtd: erase failure at 0x0c160000

mtd: not erasing bad block at 0x0e300000

Need size of filesystem

format: make_ext4fs failed (1) on /dev/block/mmcblk0p24about to run program [/sbin/umount] with 2 args

> Wiping DATA partitionumount: can't umount /data: Invalid argument

run_program: child exited with status 1

about to run program [/sbin/erase_image] with 2 args

mtd: erase failure at 0x00e80000

mtd: not erasing bad block at 0x04440000

mtd: erase failure at 0x0be20000

mtd: erase failure at 0x185c0000

mtd: erase failure at 0x1a960000

mtd: erase failure at 0x1b300000

Need size of filesystem

format: make_ext4fs failed (1) on /dev/block/mmcblk0p25about to run program [/sbin/umount] with 2 args

> Wiping CACHE partitionabout to run program [/sbin/erase_image] with 2 args

Need size of filesystem

format: make_ext4fs failed (1) on /dev/block/mmcblk0p26> Aligning disksminzip: Extracted file "/tmp/superwipe/e2fsck"

minzip: Extracted file "/tmp/superwipe/mkfs.ext4"

minzip: Extracted file "/tmp/superwipe/superwipe.sh"

minzip: Extracted file "/tmp/superwipe/tune2fs"

minzip: Extracted file "/tmp/superwipe/wipe.sh"

about to run program [/tmp/superwipe/superwipe.sh] with 1 args

umount: can't umount /system: Invalid argument

umount: can't umount /data: Invalid argument

umount: can't umount /cache: Invalid argument

mke2fs 1.41.14 (22-Dec-2010)

mkfs.ext4: No such file or directory while trying to determine filesystem size

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p24

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p24

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p24

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: need terminal for interactive repairs

e2fsck 1.41.14 (22-Dec-2010)

/tmp/superwipe/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p24

Possibly non-existent device?

mke2fs 1.41.14 (22-Dec-2010)

mkfs.ext4: No such file or directory while trying to determine filesystem size

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p25

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p25

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p25

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: need terminal for interactive repairs

e2fsck 1.41.14 (22-Dec-2010)

/tmp/superwipe/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p25

Possibly non-existent device?

mke2fs 1.41.14 (22-Dec-2010)

mkfs.ext4: No such file or directory while trying to determine filesystem size

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p26

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p26

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p26

Couldn't find valid filesystem superblock.

tune2fs 1.41.14 (22-Dec-2010)

e2fsck 1.41.14 (22-Dec-2010)

e2fsck: need terminal for interactive repairs

e2fsck 1.41.14 (22-Dec-2010)

/tmp/superwipe/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p26

Possibly non-existent device?

about to run program [/sbin/e2fsck] with 3 args

> Checking filesystems/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p24

/dev/block/mmcblk0p24:

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

run_program: child exited with status 8

about to run program [/sbin/e2fsck] with 3 args

/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p25

/dev/block/mmcblk0p25:

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

run_program: child exited with status 8

about to run program [/sbin/e2fsck] with 3 args

/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p26

/dev/block/mmcblk0p26:

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

run_program: child exited with status 8

about to run program [/sbin/busybox] with 4 args

script result was [0.000000]

[*] Cleaning leftovers...

Done!

:: DARKSIDE ::

Install from sdcard complete.

mtd: successfully wrote block at 0

I:Set boot command ""

mtd: successfully wrote block at 0

I:Set boot command ""

-- Installing: /sdcard/HD2_NDT_MIUI_GINGER_2.3.7_STABLE_V6.0_MAGLDR.zip

mtd: successfully wrote block at 0

I:Set boot command "boot-recovery"

Finding update package...

I:Update location: /sdcard/HD2_NDT_MIUI_GINGER_2.3.7_STABLE_V6.0_MAGLDR.zip

Opening update package...

Installing update...

The latest I've read is that I should try adding an EXT4 partition to my SD card for swap / app data to help with stability?