[General Questions and Answers] cjyar:
Short version:

My HTC Wildfire gets into HBOOT, but no farther. If I try to load recovery or boot the normal system, it hangs on the normal HTC boot screen. I managed to flash it using RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe, and the new version numbers are reflected in HBOOT and fastboot getvar, but it still won't boot. What else could be messed up on my phone that would prevent it from loading the system? Can I get diagnostic messages via USB as it loads secondary bootstrap, kernel, etc.?

Long version:

Got Wildfire. Rooted using unrevoked3. Installed CyanogenMod. Everything was great for about a month. Multiple reboots, did some backups with Titanium, installed some seemingly innocent apps.

Friday, I got a new retractable USB cable for my laptop. Plugged it in to the laptop, then the phone. Immediately, the screen went dark. (This was just after updating the Google Maps app.) Phone wouldn't respond to any buttons, so I removed the battery, replaced it, and powered it back up. Ever since, it won't boot anything past HBOOT. If I try to load recovery, or if I try to boot the system normally, it locks hard and I have to remove the battery again.

I've tried loading a PC49IMG.zip from SD, and I tried making a goldcard, but it says, "No Image!" regardless. When it's sitting in HBOOT, I can detect it using fastboot, but not using adb. Fastboot lets me query variables, but nothing jumps out at me as obviously wrong. Of course the phone won't boot a kernel via "fastboot boot ..." either.

I eventually got tired and tried flashing it with the image named above. The RUU claims it worked, and HBOOT gives new version numbers corresponding to what's in the RUU. But the phone still won't boot. (Sadly, it's now HBOOT-1.01.0001.)

After messing around a bit more, I tried flashing the same RUU again, and this time it claims I have the wrong CID. Fastboot says my CID is HTC__038. Here's output of "fastboot oem boot":

... INFOsetup_tag addr=0xBC900100 cmdline add=0x9C0734CC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x1
INFOTAG:skuid 0x2490B
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__038
INFOsetting->cid::HTC__038
INFOserial number: [removed]
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =489
INFOactive commandline: board_buzz.disable_uart3=0 board_buzz.us
INFOb_h2w_sw=0 board_buzz.disable_sdcard=0 diag.enabled=0 board_
INFObuzz.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=
INFOfalse androidboot.baseband=3.35.20.10 androidboot.cid=HTC__
INFO038 androidboot.batt_poweron=good_battery androidboot.carrie
INFOr=HTC-India androidboot.mid=PC4910000 androidboot.keycaps=qw
INFOerty androidboot.mode=normal androidboot.serialno=HT0CSPY021
INFO94 androidboot.bootloader=1.01.0001 zygote_oneshot=off no_co
INFOnsole_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFODelay 99994(us) for dpram command before goto AMSS...
FAILED (status read failed (Too many links))
finished. total time: 1.073s

...so, is there any to tell what's going wrong when it tries to boot?