Develop Bugs

HTC Desire Stuck on HTC Logo (Different Problem)

Guys,
I have read all the thread but all the described solutions are not working. My HTC Desire is stuck on htc logo, it came from a friend and i don't know what he has done on it. Its Hboot is 0.93 . Iam thinking this is an SLCD model , i don't have the box with me and my friend have also thrown away the box.
When even i start the phone, it vibrate 7 time and then only shows HTC Logo. I have put the phone is boot-loader mode using power+back button and flash an RUU exe but the phone again boots to the HTC logo and gets stuck ( no error on computer, successful flashing). Then i tried PB99IMG method using hboot, the process successfully complete but still same problem , not getting passed the HTC logo screen and vibrating 7 time. Let me describe more, the phone has HBOOT and FASTBOOT Accessible but RECOVERY goes back to the HTC logo and gets stuck. I dont know that it came with HBOOT 0.93 out of the box but currently it has HBOOT 0.93. The fastboot information is as follows.
07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
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__001
INFOsetting->cid::HTC__001
INFOserial number: HT049PL04482
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =423
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
INFOTC__001 androidboot.carrier=HTC-WWE androidboot.mid=PB992000
INFO0 androidboot.keycaps=qwerty androidboot.mode=recovery andro
INFOidboot.serialno=HT049PL04482 androidboot.bootloader=0.93.000
INFO1 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
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 236 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:129664 msec
FAILED (status read failed (Too many links))
finished. total time: 24.478s

i've same problem here..
it was succsessful to flash PB991IMG.zip (renamed from shipped-rom)
but the problem still there..
Please help..

Probably a faulty motherboard. Send it to htc for repair under warranty.
Sent from my Desire HD using XDA App

Could it be the SD card? If its been rooted it might be missing the ext3 partition which some Roms need to boot.
Just a guess. ;-)
Sent from my HTC Desire using XDA Premium App

richardmugford said:
Could it be the SD card? If its been rooted it might be missing the ext3 partition which some Roms need to boot.
Just a guess. ;-)
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
flashing a RUU also does not fix this. stock rom does not need ext partition
it is not the fault.

Try a modded ROM and see if that boots.
I couldn't get a stock ROM to work either.
Sent from my HTC Desire using XDA Premium App

I had that problem too, try wipe all data, cache and dalvik cache and install different kernel.
Sent from my HTC Desire using Tapatalk

You need to flash RUU to fix this

[Q] Phone won't boot system, neither recovery. Only Fastboot available

Hello.
I have the following Problem:
Today I rebooted my phone and suddenly it wouldn't boot anymore and got stuck in a bootloop.
So I tought first that I could just reflash the ROM.
But as I tried to launch the Recovery it wouldn't boot either.
So I tried to reflash Recovery via Fastboot with "fastboot flash recovery" and the recovery.img I downloaded (Amon Ra 2.0.1 and Clockworkmod 3.2.0.1) but I wasn't still able to boot into Recovery.
So the problem now is that I only have Fastboot and I don't know how to proceed, because I have no idea from where the error comes.
Please help me, I'm really desperate right now
Has anyone an Idea what I could do?
Some Informations:
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
Rom was RCMix S v 2.1 test 4 with CM7 Partition Layout

fastboot erase recovery
fastboot flash recovery recovery.img
Go to recovery, do full wipe/factory reset & dalvik wipe and reflash ROM.
I suggest to use recovery from my signature.
If you want to go back stock, flash stock hboot then downgrader from alpharev website, and run RUU while you're in fastboot.
Sent from my HTC Desire using XDA App

U can also use fastboot commander if u don't like typing in the commands
Sent from my HTC Desire using XDA App

Yeah, like I said, I already tried to flash different recoveries.
It doesent boot the one you have in your signature either...
It is stuck at the Alpharev "Why so serious" bootscreen
EDIT: And the Problem is that I have no GoldCard. Can I just launch an RUU executable while connected in Fastboot?

Is ur phone branded
Sent from my HTC Desire using XDA App

Also does it recognize your phone with "fastboot devices" ?
When you was flashing recovery in fastboot, it doesn't give you any errors?

It is T-Mobile branded.
Yes it recognizes the device and no errors when flashing recovery.

Flash an RUU - plenty of information out there if you are sure you cannot flash recovery - which I don't know why you can't??
You say it recognises your phone etc.... are you sure your commands are flawless?

Already flashed an RUU just this morning, wouldn't boot either
I am really getting desperate right now.
Short resumee of the current situation:
- Wanted to reboot my desire yesterday but it got stuck in a bootloop
- Then wanted to boot into recovery but got stuck at the logo
- Reflashed different recoveries, but every one of them stucks at logo
- Tried to restore a Nandroid Backup of a friends desire that he did for me with a fresh CM7 installation, flashed Alpharev CM7 r2 before, wouldn't boot either
- Restored the stock partition layout with Alpharev stock (using fastboot)
- Tried to flash the official Gingerbread RUU from developer center using the PB99IMG.zip method -> still no boot
- Now flashed "RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed", first edited it because of SLCD (removed "hbootpreupdate:2" from Android-info.txt, deleted hboot_8x50_0.80.0000_xxx.nb0 and replaced recovery.img and radio.img with the ones from the "2.12.110.2-1.21.110.4_release3uop1mw9unpc376h" OTA Update)
flashed the resulting CustomRUU.zip with:
fastboot erase system -w
fastboot oem rebootRUU
fastboot flash zip CustomRUU.zip
fastboot reboot-bootloader
Still no boot, neither system, nor recovery
/*********** Edit ***********/
Well, managed to get it S-On and Stock Hboot etc. now with the Gingerbread Update, but still can't boot, so I think I will send it to HTC.
Anything I should do so that they don't recognize I flashed etc.?
Phone still can't boot and so they should not see which Rom is on right?
This is the output of "fastboot oem boot", maybe it helps?
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E0800C4
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A12
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB101
INFOsetting->cid::T-MOB101
INFOserial number: HT0C3PL01561
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =449
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.17.05.23 androidboot.cid=T
INFO-MOB101 androidboot.carrier=TMD androidboot.mid=PB9920000 an
INFOdroidboot.keycaps=qwertz androidboot.mode=normal androidboot
INFO.serialno=HT0C3PL01561 androidboot.bootloader=1.02.0001 zygo
INFOte_oneshot=off kmemleak=off 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
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:12194 msec
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))

theres a chance you just voided your warranty with the new update.. so if they're bastards they'll make you pay (usually they're really good though )

Oh man, this is no good news :/
Thought it would be better to have an S-On and unrooted phone if I send it to them, but didn't think about the fact that the Gingerbread update is really new.
Any advice what I can do about that they don't get I flashed this?
I doubt that it is still possible to flash an older T-Mobile Ruu now that the phone is S-On and unrooted and still doesen't boot?

it's too late now, they'll see the new Hboot... try not to worry about it they're usually really laid back.. they know that the forsaken ones (owners of the desire) have been pretty much trampled on so they *should* fix it for you...

[Q] RUU fails (remote: 51 partition update fail)

After flashing RUU fails with
Hi,
I'm just trying to get my Desire back to stock so I can sell it but the RUU that I have used in the past has failed. I've run the downgrader and flashed the stock ROM from Alpharev but now when I try to re-apply the RUU I get the black HTC screen with 4 warning triangles in the corners of the screen. If remove the USB an dreconnect then I get this....
---Alpharev----
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNW101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
RUU
1 Bootloader - Bypassed
2 Radio V2 - FAIL-PU
3 RADIO CUST - OK
4 BOOT - OK
5 RECOVERY - OK
6 SYSTEM - OK
7 USERDATA - OK
8 SPLASH1 - OK
9 SPLASH2 - OK
Partition update fail!
Update fail!
If I run fastboot oem boot then I get this...
C:\AndroidSDK\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is ORANG001
(bootloader) setting->cid::ORANG001
(bootloader) serial number: SH09DPL01345
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =423
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=O
(bootloader) RANG001 androidboot.carrier=ORANGE-UK androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=SH09DPL01345 androidboot.bootloader=6.93.100
(bootloader) 2 no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:423443 msec
FAILED (status read failed (Too many links))
finished. total time: 99.905s
I've got a gold card in. I'm not sure if I'm missing a partition or if my goldcard needs recreating. Oh, and I have tried various RUU's but no luck with any of them.
Does anyone have any ideas? Let me know if you need any more info.
Many thanks,
Baz

Did you flashed Stock Hboot partition table before downgrader?

I did bravo_downgrade.img followed by bravo_alphaspl.img and then the RUU.
Is there another one I have to do?

have you tried to run the RUU again while on the four-triangle-screen? that solved it for me.
Sent from my HTC Desire using xda premium

Don't open two threads about the same problem.
SwiftKeyed from CyanogenMod with Transparent XDA App

@Tillus - I had tried re-running the RUU but with no luck. I've also tried various other RUU's but can't get anything.
@MatDrOiD - Sorry, I think that's a forum screw-up because I was safely tucked up in bed at 12:48am. In response to your post on the other thread, I have flashed bravo_downgrade.img As far s I know that's the hboot downgrader, no?

Looks like a radio brick to me. You can try a,few things but you may end up contacting HTC
Sent from my HTC Desire using XDA App

I did bravo_downgrade.img followed by bravo_alphaspl.img and then the RUU.
Is there another one I have to do?
Click to expand...
Click to collapse
Why did you flash the stock after the downgrader?
First Flash the stock, then the downgrader.
That's why the bootloader is bypassed and radio can not be updated.

Exactly.
First you have to flash the partition table image, and then run the downgrader... if you do it backwards results might be unpredictable.

You do not have to flash stock, downgrader is enough. After downgrader run RUU and it will succeed.

Thanks Dave, I'll give that a go as soon as I've had a cup of tea. I did things that way round because I had an issue once before and someone said that was the way to fix it and it worked so this time I just did the same again. I'll get back to you and let you know how things went.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

OK, I flashed stock followed by the downgrader and then ran the RUU. My fault has changed to something that strikes me as being rather more serious. I have a feeling I was lead to the wrong RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) as after I ran this my screen went off and hasn't come back on at all so I'm thinking this might be a RUU for the led version of the Desire. Also I no longer have Super CID which seems to be preventing me from doing any further flashing. I'm just looking into reflashing misc to see if that might help.
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/

RockyGothyBaz said:
OK, I flashed stock followed by the downgrader and then ran the RUU. My fault has changed to something that strikes me as being rather more serious. I have a feeling I was lead to the wrong RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) as after I ran this my screen went off and hasn't come back on at all so I'm thinking this might be a RUU for the led version of the Desire. Also I no longer have Super CID which seems to be preventing me from doing any further flashing. I'm just looking into reflashing misc to see if that might help.
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
Click to expand...
Click to collapse
why if you have dozen of ruu available, newbie always choice the damn old one??? U have to choice the damn last one! What wrong with the latest? How you can flash a such old ruu?
The next time, ask a confirmation before flash an ruu.

RockyGothyBaz said:
Current problems: No Super CID, No display, only boots into fastboot.
...oh bugger :-/
Click to expand...
Click to collapse
IF it boots into fastboot, you can flash a newer RUU, try the latest one, not one of the oldest

Hey guys,
I've also got a device from a mate who completely screwed it up. I also tried to flash the latest RUU but it failed.
My understanding is that with the device blocked at the HTC with 4 triangles boot, my only option is to use a Goldcard because of S-ON.
However my understanding is that to create a Goldcard you need to do this from your device whilst its working. Is it possible to create a goldcard without the device?
Thanks.

makcrellon said:
Hey guys,
I've also got a device from a mate who completely screwed it up. I also tried to flash the latest RUU but it failed.
My understanding is that with the device blocked at the HTC with 4 triangles boot, my only option is to use a Goldcard because of S-ON.
However my understanding is that to create a Goldcard you need to do this from your device whilst its working. Is it possible to create a goldcard without the device?
Thanks.
Click to expand...
Click to collapse
Read my thread.

[Q] writing 'zip'... FAILED - BRICK Ufter RUU Install

I brick my htc desire after a failed RUU installation.
The Display become black with /!\ on the 4 corners
With the help of bortak in this 3d we had try to fix it but without success.
At the moment, when i try to run the RUU (2.3 or 2.2) it show 155 error image. If i try to flash (from cmd) rom.zip, it show this message
sending 'zip' (164913 kb)... OKAY [24.279s]
writing 'zip'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
The strange thing is that when i unplug my phone (after RUU abort) it show this
--alpahrev--
BRAVO PVT4 SHIP S-OFF
HBOOT-6 93.1002
MICROP-051D
TOUCH PANEL SYNT0101
RADIO-5.11.05.27
aug 10 2010, 17:52:18
Fastboot
Click to expand...
Click to collapse
and if click VOL-, then appears the other voices like bootloader, etc.
Also, at this point, i try to run again RUU, but it show another problem
version main failed (status read failed too many links)
Click to expand...
Click to collapse
If i click however "update" the software doesn't recognize the phone and the pc too. The phone shows fastboot usb screen, but it is blocked and I have to remove the battery
I post this new 3d at the suggestion of bortak, whom I thank.
Any Idea?
Sorry for my bad english!

Fastboot devices not working?
As you still s-off flash recovery with USB unbrick function via pb99 method
Unbrick your phone
Flash alpharev downgrade hboot (instruction on alpharev.nl)
Then you can flash ruu
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium App

Sorry, but i don't understand. Do You suggest to flash downgrade? or to use pb99 method?
Thanks

god2pac said:
Sorry, but i don't understand. Do You suggest to flash downgrade? or to use pb99 method?
Thanks
Click to expand...
Click to collapse
You do not need the downgrader, keep S-OFF for now, it may be beneficial.

What i don't understand is why it writes recovery, hboot etc, but don't writes rom.zip

Did you tried this:
Rename the rom.zip that you pulled from the RUU to PB99IMG.zip
put it on the root of your sdcard and boot to fastboot. Does it recognize it and can you flash it that way?

drnizeguy said:
Did you tried this:
Rename the rom.zip that you pulled from the RUU to PB99IMG.zip
put it on the root of your sdcard and boot to fastboot. Does it recognize it and can you flash it that way?
Click to expand...
Click to collapse
I have access on bootloader and then on fastboot only if i run (without success) RUU and plug out the phone. BUT, if i try to put sdcard, the bootloader screen try to loading PB99DIAG.img forver :-D
I don't know if it is important, but if i write "fastboot oem boot": the phone shows htc white screen; the cmd shows this message "[ERR] image doesn't exist"

well it should not take forever, but it can take up to a minute of 5..
but do you have a PB99diag zip then? you should only try it with PB99IMG.zip

Did you try to boot from a recovery image to recover from a backup?
If you have a complete backup you could put it on the sdcard to
/clockworkmod/backup/ while using the recovery.img from this backup to boot the phone.
fastboot boot recovery.img
to try to recover the backup afterwards.

drnizeguy said:
well it should not take forever, but it can take up to a minute of 5..
but do you have a PB99diag zip then? you should only try it with PB99IMG.zip
Click to expand...
Click to collapse
I'll try it again, waiting over 5 minute. Yes I put only PB99IMG.zip
But to do this, i should run RUU and then plug out the phone... i'll try.
About backup recovery, i don't try it. I hope i have saved recovery, but i'm not sure.
But, why i'm not able to write image? and why image doesn't exist? Is it regular that Ruu give me 155 error?
Thanks to all

Might have missed this if Bortak already asked, but you've definitely got AlphaRev Stock hboot? As think 155 error also occurs if RUU won't fit.

beachcomber said:
Might have missed this if Bortak already asked, but you've definitely got AlphaRev Stock hboot? As think 155 error also occurs if RUU won't fit.
Click to expand...
Click to collapse
i think yes. i flash bravo_stock with android flasher and with fastboot command

drnizeguy said:
well it should not take forever, but it can take up to a minute of 5..
but do you have a PB99diag zip then? you should only try it with PB99IMG.zip
Click to expand...
Click to collapse
No doesn't work. It show loading... screen forever
I don't have clockworkmod dir backup (it is empty), but nandroid dir. Is it same? Which should i flash via fastboot? boot.img, cache.img, data.img, system.img or android_secure.tar?
Thanks
Edit 1:
restore failed. When i flash system it show image error (can't update)
Really i don't know...

I hope that this info could help to better understand the porblem:
C:\Users\Carmine>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 6.93.1002
INFOversion-baseband: 5.11.05.27
INFOversion-cpld: None
INFOversion-microp: 051d
INFOversion-main: 2.29.405.5
INFOserialno: MBxxxxxxxxx6
INFOimei: 35xxxxxxxxxxxxxxxx16
INFOproduct: bravo
INFOplatform: HBOOT-8x50
INFOmodelid: PB9920000
INFOcidnum: HTC__405
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: dirty-365c78d6
INFOhbootpreupdate: 11
all: Done!
finished. total time: 0.013s
Click to expand...
Click to collapse
Please...

Now i ave try to flash recovery and then run it from cmd. This is the result:
C:\Users\User_name>fastboot oem gencheckpt
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A02
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is HTC__405
INFOsetting->cid::HTC__405
INFOserial number: MB15XXX2XXX6
INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq=
INFO1 wire.search_count=5
INFOcommand line length =461
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
INFOTC__405 androidboot.carrier=HTC-ITA androidboot.mid=PB992000
INFO0 androidboot.keycaps=qwerty androidboot.mode=recovery andro
INFOidboot.serialno=MB15XXX2XXX6 androidboot.bootloader=6.93.100
INFO2 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
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
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:62058 msec
FAILED (status read failed (Too many links))
finished. total time: 13.089s
Click to expand...
Click to collapse
Another thing, what are hboot driver? that because fastboot command works fine, while adb command not (in hboot)
i flash with success everything (boot, recovery, etc) but not system or rom.
Really mad!

Hmm, I think I had a familiar problem before with an other Desire.
Some how your phone is stuck in the RUU update.
Well, It sounds silly and I dont what excactly happend, But I tried and tried pushing the RUU (on the black HTC screen, tried to install it, then unplugged and tried it in fastboot, reconnected so it become back on the black HTC screen, and so on). I cant tell you what happend, but suddenly the phone rebooted, and it worked. What I think (at least in my case) that the complete ROM is allready there in your phone, only some it needs to be triggert to boot.
I understand, it is strange and I cant tell you what to do and why it worked for me, but I think that is all you can try.
ps: I think you should remove your IMEI and serial number from your post.

Thanks to everyone for patience and help.
I'll try it again and again...
Only 2 think:
1) which drivers should i use for bootloader mode? Unrevoked drivers? At the moment PC shows android 1.0
2) After RUU, when plug out the phone, it shows fastboot screen. If i go to bootloader screen the first line "Bravo PVT-4 Ship S-OFF" became "Bravo Unknow Ship S-OFF" Is it important?
Thanks again!

do you use cwm recovery or amonRa because its an PV4T Desire.
or does the problem with cwm and pv4t desires not longer exist?
I know bad english -.-
Sent from my HTC Desire using XDA

i have used Amon_Ra recovery and than ext4 touch.

After 2.3 update, constant boot loop

Hi!
I have tried to upgrade S-ON, not rooted Desire to Stock 2.3. After that Phone constantly restarts at white HTC screen. I can get into fastboot, but can't downgrade to 2.2. I can only flash the same 2.3 rom from shipped roms and the end result is the same.
The phone was 2.2 before upgrade, here are the details:
Code:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E0800C4
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A0D
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is VODAP102
INFOsetting->cid::VODAP102
INFOserial number: SH0A7PL00394
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =458
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.17.05.23 androidboot.cid=V
INFOODAP102 androidboot.carrier=VODA-Germany androidboot.mid=PB9
INFO920000 androidboot.keycaps=qwerty androidboot.mode=normal an
INFOdroidboot.serialno=SH0A7PL00394 androidboot.bootloader=1.02.
INFO0001 zygote_oneshot=off kmemleak=off 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
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:77022 msec
Any help?
Thanks!

Have you whipped the dalvik cache? Boot into recovery, advanced and while dalvik cache, it should be ok after that
Sent from my HTC Desire using xda app-developers app

I think he has stock recovery. He wont have the options to wipe dalvik cache. He will only have option to wipe data and cache. If he wipes data he will lose all his apps.

I don't have recovery, as handy guessed and I really don't care about data in the phone, just want to return it to working condition. It was 2.2 stock, S-ON when I tried to upgrade it to 2.3. Now I have boot loop and don't know what to do. Did factory reset from fast boot, but it didn't help. Still boot loop.

Well you are in stock territory. Not too many options.
- wipe cache and data and retry boot.
- wild guess remove sdcard and boot
- run ruu as per instructions. That is run the exe from pc with phone in fast boot mode.
- last resort use the revolutionary.io path
Sent from my HTC Desire

handy5876 said:
Well you are in stock territory. Not too many options.
- wipe cache and data and retry boot.
- wild guess remove sdcard and boot
- run ruu as per instructions. That is run the exe from pc with phone in fast boot mode.
- last resort use the revolutionary.io path
Sent from my HTC Desire
Click to expand...
Click to collapse
How can he use revolutionary?? Ur phone has to be booted and working for revolutionary to work. Clear storage in bootloader and try the latest ruu in bortaks guide and create a goldcard
Sent from my HTC Desire

Guys, thanks for your help, but it looks like hw fault. I have put the phione in the fridge (yes, I know, crazy but....) for about 20 min. After that phone booted and worked for a couple of mins and started rebooting. Again in the fridge and it works....
Looks like a MB fault.....
Thanks for your help, I know it's not my mistake now.
WBR!