Develop Bugs

[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.

SOLVED___help needed with a friends HTC desire

hi,
I spent last 5 hours reading on XDA, on another forums, testing stuff, searching more on the web but I cant figure out what to do. Also this is not my device so I am little worried to do something wrong.
I am using HD2 so this approach to android and flashing is little new to me so please forgive my desire noobiness.
First here are some info on the device.
It is a Desire GSM (I guess since it does have SIM card).
Baseband 32.56.00.32U_5.17.05.23
Info from hboot:
BRAVO PVT3 SHIP S-ON
HBOOT 0.83.0001
MICROP-051d
TOUCH PANEL-SYNt0101
RADIO-5.17.05.23
While doing some stuff for usb brick I got this info from running "fastboot oem boot". Posting it in case it might be relevant.
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07E8CC
(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 empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT09RPL01076
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 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.17.05.23 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT09RPL01076 androidboot.bootloader=0.83.0001 no_c
(bootloader) onsole_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) mpu_nand_acpu_rw A1E 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:33155 msec
FAILED (status read failed (Too many links))
finished. total time: 4.823s
Click to expand...
Click to collapse
I got this device from a friend. Symptoms were stuck at boot. It had 2.3 gingerbread installed. At that time adb worked and soon by looking at logcat I realized that something is wrong with sdext and then with sdcard and both werent usable in recovery.
After finding the threads about usb brick I did
fastboot oem enableqxdm 0(unblock your sd-card)
fastboot oem eraseconfig(fix misc partition)
Click to expand...
Click to collapse
and installed some zip through recovery that was on that page and after that
sdcard worked and I succesfully booted into android.
Then I installed latest clockworkmod recovery through rom manager and flashed this rom, a2sd+ version.
After that following problems occured:
I cant get adb to work, and usb mount is not working neither in recovery nor in rom. In recovery when desire is connected windows recognize "unknown device" and when I click on USB mount it stays on "unmount" option but computer doesn't see anything different.
When I connect the device while in android windows recognize 3 devices without drivers named "Qualcomm CDMA Technologies MSM".
I installed htc sync 2.0.33, and uninstalled it so that htc driver remains.
SD card woks fine in external card reader.
And there is also problem with charging. If I disconnect the cable while charging and plug it again phone wont charge. But there is a usb connection since windows still sees 3 devices named above. Then I need to turn off the phone, remove and put back the battery and then when I boot into android and plug the cable again it charges fine. If I disconnect the cable again problem is there again.
Jut so point out that while I am in fastboot or in hboot windows sees the phone, fastboot works fine, no metter if I unplug the phone and plug the cable back.
This somehow looks to me like possible hardware problem, but then again it could be something I did wrong or didnt know what to do.
After that I wanted to put phone to stock 2.2 rom, downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe but when running it while in fastboot phone hangs after some time. Also I tried renaming this file to PB99IMG.zip and copy it to a freshly formated sdcard (fat32) but when i enter the bootloader it wont do anything.
Any hint or suggestion is most welcome. I am all out of options what to try next.

You did the right steps, and think you fixed it, you just broke it again using ROM MANAGER!! Stay away from that piece of SH*T application!
Have you tried using the USB Brick Fix again? It should do it for you. Once you've done that, return it to stock, S-OFF the phone (much easier to fix), flash 4EXT Recovery (automatic USB un-brick, installed via app from market), backup, full wipe, and flash a rom.
Then never use ROM Manager in your life.

bortak said:
You did the right steps, and think you fixed it, you just broke it again using ROM MANAGER!! Stay away from that piece of SH*T application!
Have you tried using the USB Brick Fix again? It should do it for you. Once you've done that, return it to stock, S-OFF the phone (much easier to fix), flash 4EXT Recovery (automatic USB un-brick, installed via app from market), backup, full wipe, and flash a rom.
Then never use ROM Manager in your life.
Click to expand...
Click to collapse
I did the usb brick thing few more time, althought sdcard work without problems in that time.
But I cant do the s-off because of 0.83.0001 hboot version and dont know how to update the hboot without usb connection. All the ways I tried didnt do anything.
I just saw one thing. This is some errors in logcat that I get after plugging/unplugging the usb cable while in android.
E/BatteryService( 1019): /sys/devices/platform/msm_hsusb/usb_cable_connect (No such file or directory)
E/BatteryService( 1019): read property /sys/devices/platform/msm_hsusb/usb_cable_connect failed
E/BatteryService( 1019): /sys/devices/platform/msm_hsusb/usb_cable_connect (No such file or directory)
E/BatteryService( 1019): read property /sys/devices/platform/msm_hsusb/usb_cable_connect failed
D/BatteryService( 1019): isUsbConnected() = false
D/UsbConnectedReceiver( 1220): action = psclient.intent.action.usb_status
Click to expand...
Click to collapse
So there is a connection between computer and phone but something is not letting the phone start charging again. No metter if its connected to a computer or a wall charger. I need to remove the battery so it can start charging again.
From my point of view and limited experience with the device it can be caused by....anything....maybe faulty hardware...something done wrong by whoever rooted/flashed this device before me.
Thanx for conformation I did good steps.
I would like to install a stock 2.2 or maybe 2.3 rom without s-off, root or anything to see if that will fix this issue. Then I will know that is probably hardware error.
But dont know how to do it.
I tried starting wwe ruu from fastboot, and the phone freezes after I click on update and with renaming that file and try from sd card but nothing also happened. That card had single fat32 partition with only that zip file on it.

Check if you renamed it right. It must be pb99img.zip and not pb99img.zip.zip.
Gesendet von meinem HTC Desire

muellersmattes said:
Check if you renamed it right. It must be pb99img.zip and not pb99img.zip.zip.
Gesendet von meinem HTC Desire
Click to expand...
Click to collapse
At first I named it PB99IMG.zip (uppercase). Just now tried it in lowercase after doing the usb brick thing again and as again when it enters the hboot after about 5 sec it lists some green text and says no image. I tried with 3 different sd cards.

I got another SD card, extracted the rom.zip from ruu, renamed it to PB99IMG.zip and I succesfully flashed 2.2 stock rom, but the usb cable issue still exists.
After I once remove the usb cable, end plug it again, computer only sees three "Qualcomm CDMA Technologies MSM" devices, no driver for it..
Phone doesnt react at all, it is not charging, no usb connection detected other then the errors in logcat I typed before (I got those from aLogcat app).
Meanwhile in fastboot connection works fine, now I have 0.93.001 hboot.
Can I achieve root and s-off without USB connection?
Also now when I go into recovery now I get a black screen with phone picture and red trigle with exclamation sign..

After found this article I did USB brick fix on non-rooted stock 2.2 rom, and after that USB mount and charging works fine.
I just did root and s-off with unvevoked3 app and reflashed newest radio.
I will try now to flash newer 2.3 rom and hopefully it will work...
thanx to everyone
edit:
everything works perfectly.

clyder said:
After found this article I did USB brick fix on non-rooted stock 2.2 rom, and after that USB mount and charging works fine.
I just did root and s-off with unvevoked3 app and reflashed newest radio.
I will try now to flash newer 2.3 rom and hopefully it will work...
thanx to everyone
edit:
everything works perfectly.
Click to expand...
Click to collapse
Glad to hear it, there was no need to update to 2.3 though if your friend will be rooting and using custom ROMs anyway.
For future problems, keep S-OFF and flash 4EXT recovery which has USB brick auto detection and fix, so you won't have to go through this lengthy process again

bortak said:
Glad to hear it, there was no need to update to 2.3 though if your friend will be rooting and using custom ROMs anyway.
For future problems, keep S-OFF and flash 4EXT recovery which has USB brick auto detection and fix, so you won't have to go through this lengthy process again
Click to expand...
Click to collapse
I installed Revolution 4.0 rom on it. This device is used by an older man so if he is used to sense android I dont want to confuse him for now.
Allthough I dont like sense Revolution works very fast and stable.
I did s-off and flashed 4ext allready. Thanx for the tip about that one.

[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.

[Q] Stuck in RUU [HELP PLEASE!]

Dear developers,
I got a problem, there were a lot of things I could help my self with but now i'm stuck.
My HTC Desire Z won't boot... I can't flash anything to my phone because the bootloader is locked and I can't find a official RUU that would help me out.
I tried to boot in fastboot and I get the HTC logo with in every corner an exclamation, when I disconnect the phone I get the following screen:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.51.26
eMMC-boot
Apr 11 2011,23:36:27
RUU
- no reboot possible
- screen says RUU (when plugged in, RUU USB)
- can't find device with adb devices
- can find device with fastboot devices
- not possible to make goldcard, because no adb connection
- running new RUU didn't work either (because I can't find a RUU for 2.42.405.5)
I have no solution, can someone please help me?
------- Update
I have a gold card using another phone
If I now just try to flash something on my phone I get a signature error

What happened around the time your phone stopped booting? Did you go to HTC website to get the latest ruu from them? Also boot back to fastboot and try
fastboot check_emmc_mid
Sent from my Nexus 7 using xda premium

On the HTCDev.com I can vind a RUU for software version: 2.42.405.2 but I have 2.42.405.5
Now I tried the command: fastboot oem check_emmc_mid and get the output:
...
(bootloader) Manufacturer ID, MID=45
(bootloader) eMMC should be Sandisk
OKAY [ 0.009s]
finished. total time: 0.010s
I don't understand anything about it, I hope you do
And I tried a the command: fastboot oem boot and than I get the output:
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: SH0BNRT08614
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =496
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.51.26 androidboot.c
(bootloader) id=HTC__E11 androidboot.batt_poweron=die_battery androidboot
(bootloader) .carrier=HTC-Dutch androidboot.mid=PC1011000 androidboot.key
(bootloader) caps=qwerty androidboot.mode=normal androidboot.serialno=SH0
(bootloader) BNRT08614 androidboot.bootloader=0.85.0013 zygote_oneshot=of
(bootloader) f kmemleak=off 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) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:27964 msec
FAILED (status read failed (Too many links))
finished. total time: 7.423s
And mij device gives a normal boot logo (the white one instead of the black one with the "!" in every corner)

Just wanted to se which emmc you had as one is prone to failure, you do have a good one though!
Now its all about finding the right bit to flaash for you which may be a bit hard as unrooted and bootloader locked phones only allow new os versions to be flashed. I won't be near a computer for a while but when I get back ill try to dig up a file for you
Sent from my SGH-T839 using Tapatalk 2

if you would like to do I'd be very grateful!

yeah seems like you have the latest version right now other than the latest g2 ruu but you dont have super cid so you wont be able to flash that either
do you remember what happened when your phone stopped working? may help figure this out.
also just for fun what output do you get when you type this in fastboot
fastboot flash system system.img
dont worry that there is no image, im more concerned if your current bootloader will allow you to do this, i doubt it but why not
also check this
fastboot oem partition_test all

Like evry other flash I try:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
and the output of the partiton test:
(bootloader) [ERR] Command error !!!
I think the phone does not flash because the bootloader is locked? (S-ON)
I do not know how the device can not work anymore, I've bought via ebay ...'m a bit ripped off because it said that the phone worked

yeah a bit ****ty of whomever sold it to you, id try for a refund!
i take it you tried the basic stuff like booting to recovery and doing a factory reset?
this is real annoying too being without knowing the cause and having such limited access its hard to fix this thing, one of those deals where if i had it in front of me i think i could figure it out! but really you are going to need an updated ruu signed by htc to get this thing up and running if all the simple fixes havent worked... i guess you can see if debugging will work in recovery mode? if so then should still be fixable...

I tried a lot, can't boot to recovery because there is no.
it automaticly boots into RUU mode and if i try to boot it in to bootloader, system or recovery it stuck at the HTC logo.
How can I debugg the device? I know how to debug C# applications with Dot Net but a simple android phone is a lot harder
I could send my phone to your house if u think that would help?

Problem solved! partially i used a RUU from asia with a higher Version

dont send me the phone i live far away, send it back to whoever sold it to you and get the refund. hell ill sell you one that does work!
by debugging i meant to see if it were turned on on the phone, this is what allows for adb to work where you do the debugging. adb wont work in bootloader/fastboot mode, only in os and recovery. but again the problem is you can flash a recovery or os being you have a locked/shipped bootloader, the only thing to do at this point is to work with the limited fastboot commands you have or install a PC10IMG.zip, again the problem with this is they have to be signed by htc and be of a new version then your phone thinks you have installed... kinda stuck without some nicer options

Oh, I had forgotten that "adb" for android debugging bridge stands.
I do not have adb access only fastboot access, and a PC10IMG.zip does not work,like you already said it needs to have a htc signature.
Sending my phone to you was a joke.
But it is now almost entirely successful. I have an official RUU software used with a higher number, I had 2.42.405.5 and I have set up a foreign RUU and it worked "HTC Asia WWE 2.42.707.3"
I now have at least access to the HBoot, now I'll have to see how I can get S-OFF. flashing and "get_identifier_token" are still not working

Awesome news! So as of right now you have a stock ROM/Hboot/recovery?
If that is the case go right over to the xda wiki for the vision and root your phone with gfree!
Do it now before anything else brakes! Once you root (only use gfree method laid out in wiki) then everything else will be easy! Let me know how things go or if you need a hand!
*can't believe I glossed over that ruu!
Sent from my Nexus 7 using xda premium

He does not work well, he gets stuck on the normal boot logo.
If I run fastboot reboot bootloader he walks onto the boot screen. Install another RUU does not work, it stuck on "wait for bootloader"
Now the option "Image CRC" is added to the HBOOT menu, and I ran a factory reset that fails, that is what crashed my phone

can you post everything on your new hboot screen here? also everything that image crc says or any other options that may have appeared. also does it let you boot to a recovery?

Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
crc output:
7 times vibrate
Code:
calculating... please wait
osbl: 0x7EE4ED8C
amss: 0x0
hboot: 0x887F7ABB
boot: 0x0
recovery: 0x0
system: 0x0
Press power key to go back.
I could get into recovery but after I did the factory reset (what went wrong) I can't. I can only get into the bootloader by "VOL-" and "POWER" but if I from fastboot reboot-bootloader command doing he stack onto the HTC logo.

well according to this you have no system, kernel or recovery installed right now just a locked bootloader with all security flags on.
can you try another ruu, or flash the same one again? also look in here nipqer made these and they may help you out... actually he or ghul would be very helpful on this unless you can wait longer, i have some things im working on right now and i can look this over again tonight when i have some more time.
see if you can find them or another helpful one at FREENODE make a name and join #g2root

Yeah, yesterday I was @ the chat on freenode, they told me to try the asian RUU (a) I'll try the DZ_PC10IMG.zip form your link and if that doesnt work I'll wait for the next option
Thanks a lot!

I can't flash any RUU because after the command "reboot bootloader" he keeps waiting for the bootloader but the device gets stuck on the htc logo and doesn't boot to the bootloader, even if I set it from "VOL UP" + "POWER" to the bootloader the RUU installer status remains: "Waiting for bootloader"
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
And I tried to flash a stock recovery but than I got a Signatue failure.

Try taking the pc10img off SD card or removing SD altogether
Then of will boot into fastboot, the in fastboot mode type
fastboot OEM rebootRUU
Sent from my Nexus 7 using xda premium

Htc Desire Stuck on HTC logo, no recovery, ruu install succesfully

Hello. I've got desire, stuck on htc without recovery. I find ruu wich flash succesfully but nothing happen. Fastboot works. I've got this log from phone and i've got:
--- AlphaRev ---
s-off
hboot - 6.93.1002
microp 051d
radio 4.06.00.02_2
what can i do?
C:\fastboot-win>fastboot oem gencheckpt
...
(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 0x21F04
(bootloader) TAG:hero panel = 0x0
(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 empty
(bootloader) setting->cid::HTC__622
(bootloader) serial number: HT05PPL02709
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =467
(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=4.06.00.02_2 androidboot.cid
(bootloader) =HTC__622 androidboot.carrier=Asia-HK-CHT androidboot.mid=PB
(bootloader) 9920000 androidboot.keycaps=qwerty androidboot.mode=recovery
(bootloader) androidboot.serialno=HT05PPL02709 androidboot.bootloader=6.
(bootloader) 93.1002 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_c
(bootloader) ount=5
(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:106364 msec

czajnik said:
Hello. I've got desire, stuck on htc without recovery. I find ruu wich flash succesfully but nothing happen. Fastboot works. I've got this log from phone and i've got:
--- AlphaRev ---
s-off
hboot - 6.93.1002
microp 051d
radio 4.06.00.02_2
what can i do?
C:\fastboot-win>fastboot oem gencheckpt
...
(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 0x21F04
(bootloader) TAG:hero panel = 0x0
(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 empty
(bootloader) setting->cid::HTC__622
(bootloader) serial number: HT05PPL02709
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =467
(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=4.06.00.02_2 androidboot.cid
(bootloader) =HTC__622 androidboot.carrier=Asia-HK-CHT androidboot.mid=PB
(bootloader) 9920000 androidboot.keycaps=qwerty androidboot.mode=recovery
(bootloader) androidboot.serialno=HT05PPL02709 androidboot.bootloader=6.
(bootloader) 93.1002 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_c
(bootloader) ount=5
(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:106364 msec
Click to expand...
Click to collapse
Try installing 4ext recovery from the fastboot way?
Sent from my HTC Desire using XDA Free mobile app

lilsafbig said:
Try installing 4ext recovery from the fastboot way?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
sure, i try twrp, 4ext and cwm, nothing happen, i can try again, do You suggest any version of 4ext recovery?

czajnik said:
sure, i try twrp, 4ext and cwm, nothing happen, i can try again, do You suggest any version of 4ext recovery?
Click to expand...
Click to collapse
So u can't get into recovery?
Sent from my HTC Desire using XDA Free mobile app

Yes, even if i flash it it won't boot

czajnik said:
Yes, even if i flash it it won't boot
Click to expand...
Click to collapse
Maybe is u do usb unbrick it might work. In 4ext
Sent from my HTC Desire using XDA Free mobile app

czajnik said:
sure, i try twrp, 4ext and cwm, nothing happen, i can try again, do You suggest any version of 4ext recovery?
Click to expand...
Click to collapse
czajnik said:
Yes, even if i flash it it won't boot
Click to expand...
Click to collapse
- How are you flashing the recovery? Should be done by flashing the recovery.img using fastboot commands. Does it give a successful message?
- When you say "it won't boot", do you mean the phone or recovery? What happens when you select recovery from the bootloader?
- If you can't get into any recovery, try the 2.3.3 GB RUU, no other RUU. Refer to bortak's troubleshooting guide at the top of Q&A

eddiehk6 said:
- How are you flashing the recovery? Should be done by flashing the recovery.img using fastboot commands. Does it give a successful message?
Click to expand...
Click to collapse
Yes. Writing succesfull
eddiehk6 said:
- When you say "it won't boot", do you mean the phone or recovery? What happens when you select recovery from the bootloader?
Click to expand...
Click to collapse
Phone and recovery
eddiehk6 said:
- If you can't get into any recovery, try the 2.3.3 GB RUU, no other RUU. Refer to bortak's troubleshooting guide at the top of Q&A
Click to expand...
Click to collapse
i downloading it now. i check it
After update 2.3.3 official RUU it loop in restarts on htc logo

Strange that recovery doesn't even boot
What does it now say in bootloader?
S-ON / S-OFF?
Has radio version upgraded? Noticed in your first post 4.06.00.02_2 is an ancient eclair version I believe.
I would try:
- Flash latest radio.img using fastboot from here
- Flash downgrader.img from alpharev.nl
- Flash 2.3.3 RUU using the PB99IMG.zip method, Step 7 in bortak's guide
Just want to get everything completely stock, s-on and up to date, hopefully it will boot. Output any error messages when the RUU is flashing.

Now i've got 5.17.05.23 radio
S-OFF.
fastboot flash radio radio.img ?
from alpharev i must download bravo_downgrade.img ?
okay, i've doing borak's [7] and
[P1/STEP2]- Download the Alpharev Downgrader PB99IMG (MD5: 6c482ccfa6b7093de4ee1a5804ccbdfc - check MD5 matches with MD5 checker, link below)
PB99IMG and it won't flash from sd. I flaash bravo_downgrade.img from fastboot but i've got s-off still. hboot changes at 6.93.9999
i've try now flash rom.zip from ruu renamed to PB99IMG and that also won't flash
ok i'm again run ruu. now i'm s-on
hboot - 1.02.0001
radio 5.17.05.23
but still not booting nothing, recovery and phone

czajnik said:
Now i've got 5.17.05.23 radio
S-OFF.
fastboot flash radio radio.img ?
from alpharev i must download bravo_downgrade.img ?
okay, i've doing borak's [7] and
[P1/STEP2]- Download the Alpharev Downgrader PB99IMG (MD5: 6c482ccfa6b7093de4ee1a5804ccbdfc - check MD5 matches with MD5 checker, link below)
PB99IMG and it won't flash from sd. I flaash bravo_downgrade.img from fastboot but i've got s-off still. hboot changes at 6.93.9999
i've try now flash rom.zip from ruu renamed to PB99IMG and that also won't flash
Click to expand...
Click to collapse
- You don't need to flash another radio.img as you now already have the latest.
- Flashing the downgrader.img does not make it S-ON, it just allows it to become S-ON after you flash an RUU.
- If you flashed the downgrader.img from fastboot successfully, I believe it should say 'Alpharev Unlock' at the top of the bootloader screen.
- You definitely extracted the ROM.zip from the RUU, not simply renamed the RUU? Exactly as in Step 7 of the guide?
- Make sure the file is renamed exactly to "PB99IMG.zip", and not "PB99IMG.zip.zip"
- When you say won't flash, be specific. Is the PB99IMG.zip detected in bootloader at all? Or does it try to flash but with error messages? Can you try with a different sdcard if it doesn't detect it?

eddiehk6 said:
- If you flashed the downgrader.img from fastboot successfully, I believe it should say 'Alpharev Unlock' at the top of the bootloader screen.
Click to expand...
Click to collapse
after ruu from pc alpharev dissapear, i've got s-on
eddiehk6 said:
- You definitely extracted the ROM.zip from the RUU, not simply renamed the RUU? Exactly as in Step 7 of the guide?
Click to expand...
Click to collapse
yes
eddiehk6 said:
- Make sure the file is renamed exactly to "PB99IMG.zip", and not "PB99IMG.zip.zip"
Click to expand...
Click to collapse
i'm sure
eddiehk6 said:
- When you say won't flash, be specific. Is the PB99IMG.zip detected in bootloader at all? Or does it try to flash but with error messages? Can you try with a different sdcard if it doesn't detect it?
Click to expand...
Click to collapse
No image or wrong file at all. Yes i can check it on other sd card.

czajnik said:
after ruu from pc alpharev dissapear, i've got s-on
yes
i'm sure
No image or wrong file at all. Yes i can check it on other sd card.
Click to expand...
Click to collapse
Did u put the pb99img.zip in the root of your sd card?
Sent from my HTC Desire using XDA Free mobile app

sure, i'm not so lame as you think

czajnik said:
sure, i'm not so lame as you think
Click to expand...
Click to collapse
Just to be sure:
http://forum.xda-developers.com/showpost.php?p=45298337&postcount=21

czajnik said:
sure, i'm not so lame as you think
Click to expand...
Click to collapse
Haha we just have to make sure.
Been around here long enough, and seen both errors several times.
I'm certain you can rescue your phone somehow though. Let us know what you try, and write out any error messages exactly

eddiehk6 said:
Haha we just have to make sure.
Been around here long enough, and seen both errors several times.
I'm certain you can rescue your phone somehow though. Let us know what you try, and write out any error messages exactly
Click to expand...
Click to collapse
haha ;d you can trust me, i know a android basics
in attachment picture of errors. other sd tried and still the same,
I try flash couple of recoveries, 2-3 ruu and at last 2.3.3 ruu gb. And things in this topic, lastest radio, hboot, downgrader etc

czajnik said:
haha ;d you can trust me, i know a android basics
in attachment picture of errors. other sd tried and still the same,
I try flash couple of recoveries, 2-3 ruu and at last 2.3.3 ruu gb. And things in this topic, lastest radio, hboot, downgrader etc
Click to expand...
Click to collapse
Looks like you've gone back to stock but its searching for that pb99img file to change hboot? You can flash 4ext recovery that way too.
Sent from my HTC Desire using XDA Free mobile app

i try flash 4ext now from fastboot but signature veryfication fails

czajnik said:
i try flash 4ext now from fastboot but signature veryfication fails
Click to expand...
Click to collapse
Cos ur s on that wont work until ur s off but idk what to do?
Sent from my HTC Desire using XDA Free mobile app