Develop Bugs

[Q] help, bricked phone

Hi all, I followed the usb brick fix by the professor but it didnt work. the phone has a black screen with white htc. also i was s-off running cm7 r2. can't get into bootloader.this is my fastboot oem boot
c:\android-sdk-windows\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 empty
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: SH09APL12956
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =421
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=1 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=H
(bootloader) TC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=PB992000
(bootloader) 0 androidboot.keycaps=qwerty androidboot.mode=normal android
(bootloader) boot.serialno=SH09APL12956 androidboot.bootloader=6.93.1002
(bootloader) 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:526368 msec
FAILED (status read failed (Too many links))
finished. total time: 13.261s

And why don't you boot into fastboot with back + power button?
And remember one thing: If your phone still reacts, it's not bricked.
TouchPaled from Oxygen with Transparent XDA App

bricked is so over used.... you can access fastboot?? So what have you tried to fix the problem?

It all satrted when i backed up my rom with nandriod and then tried to flash a wifi n kernel, i then got boot loop, i then removed the battery and got to into recovery to flash backup only to realise that i could access my sd card. i then tried to flash back to my stock ruu without changing my hboot partitons (big mistake) thats when i could access any options on my bootloader, all it says is alpharev cm7 r2, radio and kernel, under all that where it should have fastboot recovery so on all it says is ruu. then when i plug usb cable in i get black screen with white htc and triangles in all 4 corners with exclamation marks in them.
i tried this usb brick by the professor guessing thats the problem, i have no idea what the correct terminology for what has happened is so i'm guessing after numerous google searches that its a usb brick. I generated my mtd0.img with the cid generator and move the mtd0.img and flash image to sdcard, but got stuck after that.
I hope this all makes sense to someone and you can help me through this.
Thanks very much guys

Was ROM manager involved in any way?

No rom manager involved.

The screen with the exclamation marks is fastboot-if you connect with your USB cable you should be able to enter fastboot commands with your PC.
You need to flash a ROM suitable for your hboot using fastboot commands.
You may also have overwritten your recovery partition which can be reflashed with fastboot.
I've only done the above a couple of times so may be wrong!

Ok.
Well going back to what BigMrB asked, can you boot into fast boot still? (Back + power from off)?
If you can, then check if when you plug in the USB cable, it changes to "Fastboot USB" please

Hey if you had taken backup of your rom then go to recovery by pressing volume down and power button then select recovery there go to back and restore and restore to the backup you had taken. Even i get my device not working while flashing new things there is nothing to worry you can always do the same.
Hope this helps you
Sent from my HTC Desire using XDA Premium App

iain2510 said:
The screen with the exclamation marks is fastboot-if you connect with your USB cable you should be able to enter fastboot commands with your PC.
You need to flash a ROM suitable for your hboot using fastboot commands.
You may also have overwritten your recovery partition which can be reflashed with fastboot.
I've only done the above a couple of times so may be wrong!
Click to expand...
Click to collapse
Sorry I didnt see your post. Fastboot should be white screen, but if he uses back and Power and gets the exclamations, it can still be used as fastboot.
What I am concerned about is the screen says "RUU" on it which sounds like a RUU was used and failed at some point (edit, yes OP said that)
A RUU would fail if he has CM7 Hboot.
I would personally recommend flashing the downgrader hboot via fastboot and then completing whatever RUU process was started.
I would also recommend people askign questions before jumping in and trying anythign they can to fix their issues, or guessing what issue they have

rootSU said:
Sorry I didnt see your post. Fastboot should be white screen, but if he uses back and Power and gets the exclamations, it can still be used as fastboot.
What I am concerned about is the screen says "RUU" on it which sounds like a RUU was used and failed at some point (edit, yes OP said that)
A RUU would fail if he has CM7 Hboot.
I would personally recommend flashing the downgrader hboot via fastboot and then completing whatever RUU process was started.
I would also recommend people askign questions before jumping in and trying anythign they can to fix their issues, or guessing what issue they have
Click to expand...
Click to collapse
Does he have to run the downgrader? Thought he could just flash a different hboot but i might be wrong...
Can you not just flash recovery again and just restore the nandroid? If not i would THEN use the RUU and start from fresh

BigMrB said:
Does he have to run the downgrader? Thought he could just flash a different hboot but i might be wrong...
Can you not just flash recovery again and just restore the nandroid? If not i would THEN use the RUU and start from fresh
Click to expand...
Click to collapse
He doesn't have to, he can flash a stock hboot, then flash recovery and a rom, but Id rather he RUU, which would require the downgrader

I get the black screen with the exclamations which can be used as fastboot.
How do i go about downgrading my hboot? will it revert my phone back to stock with the stock partitions?
thanks guys

mizdel said:
I get the black screen with the exclamations which can be used as fastboot.
How do i go about downgrading my hboot? will it revert my phone back to stock with the stock partitions?
thanks guys
Click to expand...
Click to collapse
Either download the adnroid flasher from the desire dev forum here, or follow my fastboot faq in my signature to do it manually. Download the downgrader from alpharev.nl (Redeirects sometimes to revolutionary.io so may have to click the alpharev link once redirected to the revolutionary page) and flash it.
It willput your phone in a state where a RUU will work woth the stock partitions but shouldnt be used as a hboot in iots own right so if you decide not to RUU, you would be better just flashing the stock hboot.

I'd recommend learning some basic fastboot commands regardless of which option you take.... They come in handy for situations just like this one

BigMrB said:
I'd recommend learning some basic fastboot commands regardless of which option you take.... They come in handy for situations just like this one
Click to expand...
Click to collapse
+1, its always good to understand a bit of what you are doing. Some of my other faq's may be helpful too.

i flashed downgrader to my hboot and now it says rebooting and nothing is happening. how long do i wait or do i have to flash stock ruu now?

How did you flash it? It should just say:
writing....
done
If you used fastboot flash hboot blahblahblah.img

i used android flasher and attached downgrader to flasher at hit begin

Well if its still in the same state, there's not a lot you can do but pull power
Sent from my HTC Desire using XDA App

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

Trying to fix my daughter's HTC Desire

My daughter gave me her HTC Desire & told me she thought 'something wasn't right' with it
The handset is locked to Three, & as far as I know was running fine until this problem.
Apparently, she had 'just deleted some apps' & it sounds like somehow it ended up in a boot loop. She passed it to a 'friend' who 'knows about phones & stuff' & now it goes to a black screen with a triangle in each corner at switch on. She says she thinks her 'friend' tried to reinstall Android, but I'm guessing it didn't go to plan I've had a trawl through google, & the only thing I've found which gives me any sort of output is
C:\Android>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 0x26A12
(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 H3G__001
(bootloader) setting->cid::H3G__001
(bootloader) serial number: SH0BAPL06571
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =420
(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.14 androidboot.cid=H
(bootloader) 3G__001 androidboot.carrier=COMMON androidboot.mid=PB9920000
(bootloader) androidboot.keycaps=qwerty androidboot.mode=normal androidb
(bootloader) oot.serialno=SH0BAPL06571 androidboot.bootloader=6.93.1002 n
(bootloader) o_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:576595 msec
FAILED (status read failed (Too many links))
finished. total time: 6.727s
Click to expand...
Click to collapse
Any help greatly appreciated.

check bortaks troubleshooting guide in my sig, answers for u problem is there
Sent from my HTC Desire

problems

3c3adu said:
problems
Click to expand...
Click to collapse
wtf?

jmcclue said:
check bortaks troubleshooting guide in my sig, answers for u problem is there
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for the reply jmcclue. I had a good read through all the links in your sig.
I'm not sure exactly what you were suggesting may be the solution to the problem, but I tried extracting rom.zip from RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed.exe, renaming it to PB99IMG.zip & then tried updating via fastboot, but I got the following
C:\Android>fastboot update PB99IMG.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '╣ü┼02ıa6åfïlAþQ=┘qµ┘mìl♣2
çn►5╗ÿM█l(M,ÐøXó7▒Do÷XuþÜ¢¿IG♦ÃB¯òÇ[Öù☺Rò░wNy/Ó▓└⌂↔úÐKá↔■Ä▒8þo├¬ÊAÈXö7iF ê┌'³EQ^Ó/¸¼ðï0║å║Î☺ÞP×WWôìªçB
ƒþf╚û©ÜÞàõ»åÞ_‗*‗↓ȯ┘µÇU*+¥!Ûe↑q(ä⌂╬¾┴PyÁ3ML¨═◄R:
àı├XЦ▼N'
Click to expand...
Click to collapse
Is this what you where suggesting I do? If so, what have I done wrong?

Just download and run 2.3 ruu.
Sent from my HTC Desire using Flashes and Thunders

dreamonn said:
androidboot.bootloader=6.93.1002
Click to expand...
Click to collapse
Thats a alpharev hboot. You will have to downgrade hboot first before running 2.3 RUU. Only run 2.3 RUU.
Chapter 4 of Bortaks troubleshooting thread is relevant for you. Before the RUU do downgrade hboot. Its in my signature.Go there

handy5876 said:
Thats a alpharev hboot. You will have to downgrade hboot first before running 2.3 RUU. Only run 2.3 RUU.
Chapter 4 of Bortaks troubleshooting thread is relevant for you. Before the RUU do downgrade hboot. Its in my signature.Go there
Click to expand...
Click to collapse
Thanks handy5876
If I pull the usb lead after I hear the phone connect, it goes from the black screen with a triangle in each corner to what looks like a fastboot screen with the following info
Code:
AlphaRev Unlock
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.9999
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:18
RUU
I had a read through [4] of Bortaks guide. As you said to downgrade hboot I downloaded the bravo_downgrade.img from AlphaRev & also Android Flasher 2.2.0.5. When I run Android flasher with the phone showing the black screen with triangles, I click the 'Bootloader' button & browse to the bravo_downgrade.img, but when I click 'Flash' I get an error that says
Code:
error: device not found
& a pop up window which says
Code:
Error, your phone is not plugged in or drivers aren't installed
. If I check the 'I'm already in fastboot' box & repeat the above, Android Flasher just says 'Please wait while your phone is flashed.' but nothing happens.
I can issue a
Code:
fastboot oem boot
from a command window & get a response from the phone so I'm guessing there are drivers installed, & the fact that it replies to a fastboot command means I'm in fastboot so I'm a little confused.
Any ideas what I'm doing wrong?

Run 2.3 ruu from bootloader/fastboot.
Sent from my HTC Desire using Flashes and Thunders

dreamonn said:
Code:
AlphaRev Unlock
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.9999
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Aug 10 2010, 17:52:18
RUU
Click to expand...
Click to collapse
Do as nlooooo says. Your bootloader is saying Alpharev Unlock. That means it has been downgraded and safe to run the 2.3 RUU.

nlooooo said:
Run 2.3 ruu from bootloader/fastboot.
Sent from my HTC Desire using Flashes and Thunders
Click to expand...
Click to collapse
Hi nlooooo
Can you just confirm what you mean - do you mean to run the ruu.exe or push the ruu from fastboot? If you mean to push the ruu from fastboot, what commands do I issue?

Just run it from PC, you can do that with phone in both bootloader or fastboot.
Sent from my HTC Desire using Flashes and Thunders

Success!!
Successfully flashed & now back up & running.
Thanks for all you help

:thumbup:
Sent from my HTC Desire using Flashes and Thunders

nj!

[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