[General Questions and Answers] Mouseboy007:
Hi Guys,

I've read through tons of posts and tried lots of things but my HTC Desire seems fairly bricked. Earlier I downloaded SPLHexEditor_111006.exe and created a hboot.nb0

I performed a fastboot flash hboot hboot.nb0 and it immediately rebooted to a black screen.

It's very frustrating as I can get into ADBShell and can get into Fastboot and run commands. I've tried flashing various roms and bits and pieces but I keep getting the same error when trying to re-flash a hboot.img:

sending 'hboot' (512 KB)... OKAY [ 0.089s]

writing 'hboot'... FAILED (remote: image update error)

If I perform a fastboot flash zip PB99IMG_stock.zip it runs through as follows

sending 'zip' (207 KB)... OKAY [ 0.045s]

writing 'zip'... INFOzip header checking...

INFOzip info parsing...

INFOchecking model ID...

INFOstart image[hboot] unzipping & flushing...

INFO[RUU]UZ,hboot,0

INFO[RUU]UZ,hboot,100

FAILED (remote: 51 partition update fail)

finished. total time: 6.664s

So from what I can see I get a "remote: image update error" and "remote: 51 partition update fail". Before I started messing around I was using an alpharev.nl hboot. I just got 'greedy' thinking I could get better use of space with a custom hboot.

Interestingly if I reflash the hboot.nb0 I created it seems to 'work' in so far as not throwing up errors:

sending 'hboot' (512 KB)... INFO[RUU]WP,hboot,0

INFO[RUU]WP,hboot,100

OKAY [ 0.216s]

writing 'hboot'... OKAY [ 0.185s]

finished. total time: 0.402s

...but then I reboot and the screen is still black and I can't 'reflash' either a full rom.zip or any of the hboot.img's from alpharev (which were okay before).

I did a nandroid backup and also have a colleagues Desire available to pull of a partition structure. I'm happy to manually edit the internal phone partitions if someone can advise me how?!

I did have S-Off before playing around trying to fix it - not sure if it is still S-Off or how I can check/ I'm also unsure how to check what the partition structure is at present internally.

Have I killed my phone or does the fact that I can run commands through adb shell and fastboot give me a chance to fix it? I've also got my CID and other relevant info from running a fastboot oem boot:

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E

08BCBC

INFOTAG:Ramdisk OK

INFOTAG:smi ok, size = 0

INFOTAG:hwid 0x0

INFOTAG:skuid 0x26A04

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 T-MOB005

INFOsetting.cid::T-MOB005

INFOserial number: HT09BPL00092

INFOcommandline from head: no_console_suspend=1

INFOcommand line length =382

INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.

INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa

INFO0.02_2 androidboot.cid=T-MOB005 androidboot.carrier=TMUK and

INFOroidboot.mid=PB9920000 androidboot.keycaps=qwerty androidboo

INFOt.mode=normal androidboot.serialno=HT09BPL00092 androidboot.

INFObootloader=0.35.2017 no_console_suspend=1

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

INFOaARM_Partion[6].name=crashdata

INFOpartition number=7

INFOValid partition num=7

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFO0

INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

FAILED (status read failed (Too many links))

finished. total time: 9.175s

If anyone can help I'll be hugely grateful!!!

Thanks!