Develop Bugs

[SOLVED] Semi-bricked Desire: No SDCard, No USB - Learn Fastboot Ninja Skills?

Hi all,
I have an interesting problem that I have now given up on solving on my own.
I was following this guide (phone was already rooted): t-mod.org/182-2/desire-tutorial/
I got through unrevoked fine, alpharev fine, sd partition fine, radio flash fine and system rom fine - all was going well.
I then got the all-too-familiar boot looping (forgot to clear one of the caches probably?), so I rebooted into recovery, factory reset, wiped cache/dalvik/data, reapplied the ROM and rebooted again.. .same story.
Now this is where it veers off course and becomes like no other rom-flash stuff-up I've ever done before (I re-rom every couple of weeks... I get bored easily). I enter recovery mode again and it can't read my SD card (32gb):
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
Error mounting /sdcard/!
Click to expand...
Click to collapse
Thinking it was a potential SD card formatting ****-up I put the card into my pc and loaded it up - it was perfect, my computer showed me exactly what was on the card (system rom and radio rom). Thinking there could some harm done that the phone dislikes I insert another SD card (16gb only ever used with the Desire) and the same error happens, I get yet another SD card (1gb), same thing.
In between scratching my head and tearing my hair out, I jump into the fastboot command line, reflash my NANDroid backup and start my phone - WIN. My phone boots, I have a working original rom and can place calls etc. Still no SD card functionality though. Not too phased and thinking I can fix it anyway I look into a few more solutions to my problem and one revolves around re-Alphareving. So I reboot the computer, phone attached, Alpharev boots up and then fails to find my phone. I check usb debugging and it's on. I then notice that the phone isn't receiving usb power from the computer. So now I have a phone without a working SD card slot and with no usb functionality except at fastboot... what the hell did I do?
I wanted to go back to my original RUU and start fresh, but without usb debugging access I'm screwed.
Is there a way that I can use fastboot to sort out something like the mtd0.img solution (which requires terminal access form phone and usb / sdcard)?
Am happy to sling over some technical details, but let me begin with the commands that have so far had no effect:
fastboot -c "board_bravo.disable_sdcard=0 board_bravo.disable_uart=0" reboot
fastboot oem enableqxdm 0
fastboot -c board_bravo.usb_h2w_sw=0
fastboot -c board_bravo.disable_uart=3
Click to expand...
Click to collapse
Of note however, is that I ran:
fastboot oem sdtest
Click to expand...
Click to collapse
and the sucker returned:
C:\>fastboot oem sdtest
...
(bootloader) [SD]power_addr=0xB1400000
(bootloader)
(bootloader) [SD]clk_addr=0xB1400004
(bootloader)
(bootloader) [SD]mclk_md_addr=0xA86003DC
(bootloader)
(bootloader) [SD]mclk_ns_addr=0xA86003E0
(bootloader)
(bootloader) [SD]SDC4_BASE_PHYS=0xA0600000
(bootloader)
(bootloader) [SD]SDC4_BASE_virt=0xB1400000
(bootloader)
(bootloader) sdc_ns_reg value=0xFFF60B59
(bootloader) sdc_ns_reg value=0xFF9E0B58
(bootloader) Cmd5 CMD_TIMEOUT
(bootloader) sdcc_poll_status(): status=4 i=1966
(bootloader) Cmd5 polling status timed out
(bootloader) SD: CMD5 fail, rc=2 ..
(bootloader) sdc_ns_reg value=0xFF9E0B58
(bootloader) SD_CMD8.resp[0] =0x1AA
(bootloader) SD_ACMD41.resp[0] =0xFF8000
(bootloader) SD_ACMD41.resp[0] =0xC0FF8000
(bootloader) HC card
(bootloader) SD card mfr_month=2011 mfr_year=2
(bootloader) sdcc_init_memory_device done
(bootloader) sdc_ns_reg value=0xFFF60B59
(bootloader) card_type = 6......................
(bootloader) SD enable 4 bit mode
(bootloader) read/write test:
(bootloader) SD Read/Write Test OK!!
OKAY [ 1.167s]
finished. total time: 1.167s
Click to expand...
Click to collapse
What does all this mean?!

It would seem I sorted it out...
I did a Fastboot recovery flash using the s-off recovery image from here: http://forum.xda-developers.com/showthread.php?t=1039954
fastboot flash recovery recovery-clockwork-3.2.0.1-bravo.img
Click to expand...
Click to collapse
I can use the SD-card again, but for some reason I can't mount it in recovery mode and transfer files - but I suspect this is a Windows driver issue (comes up as unknown device) and doesn't stop me from copying files directly to the SD.

Install hboot and htc sync drivers and you should be able to copy files to sd card.
SwiftKeyed from Oxygen with Transparent XDA App

[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

HTC Desire Z hangs at boot screen logo

Hi,
All of a sudden my HTC Desire Z switched off yesterday and I tried rebooting it, but it just hangs at the white screen with the green HTC logo. This kept happening continuously, so I took the battery out and left it out for a while, I then put it back in and turned the phone back on using the hard reset and the boot menu appeared.
When I chose the recovery mode, the phone rebooted and displayed a phone image with a green sign and then a couple of seconds later it displayed a phone image with a red triangle. The phone then switched off after a few seconds. This kept happening every time I tried.I then tried the factory reset option and after doing this the phone went into factory reset mode with the grey/white animated stripey completion bar, but then it froze and stopped animating for a few minutes and then started to animate again but then the phone turned off. This kept happening every time I tried.
Also what is strange is that my phone only charges after I have left the battery out for a while and put it back in. I even left my phone on charge overnight. The red light appeared showing that the phone is charging, but in the morning when I woke up the light had disappeared, but it should've been green to show that charging was complete. I have ordered a new battery as I think this could be the problem. If it is the battery, do you think my phone will have got damaged? My phone is not rooted.
Thanks in advance.

ah a bootloop. did you change anything in the system?

Hi, I haven't done anything to the system. When I plug my USB adapter into the phone and into the PC, HBOOT changes to HBOOT USB PLUG at the HBOOT menu and when I go into recovery mode, it tries to mount some files which fails and it tries to clear data as well.
E: Can't open /cache/recovery/command
E: Can't mount /data/data/recovery/log
E: Can't open /data/data/recovery/log
E: set_bootloader_message_block : emmc_read_data fail!
Is there any file that I can put on my SD card to reinstall android, in the same way that you would reinstall the operating system on a PC? In the recovery mode option, there is an option to select 'Apply update from sd card'.
Thanks,

jp1986 said:
Hi, I haven't done anything to the system. When I plug my USB adapter into the phone and into the PC, HBOOT changes to HBOOT USB PLUG at the HBOOT menu and when I go into recovery mode, it tries to mount some files which fails and it tries to clear data as well.
E: Can't open /cache/recovery/command
E: Can't mount /data/data/recovery/log
E: Can't open /data/data/recovery/log
E: set_bootloader_message_block : emmc_read_data fail!
Is there any file that I can put on my SD card to reinstall android, in the same way that you would reinstall the operating system on a PC? In the recovery mode option, there is an option to select 'Apply update from sd card'.
Thanks,
Click to expand...
Click to collapse
i could only think of a factory reset. there is a way to do a hard reset and restore eveything, search for it if you can

You are showing all the signs of a fried emmc, being you are not rooted and have a locked bootloader there is little you will be able to do aside from trying to warranty it. You could attempt flashing the latest ruu via a pc10.img through bootloader but your chances are slim
Log on to freenode #g2root (just google it) here you can get real time help
Sent from my HTC Vision using xda premium

Were you ever able to get this fixed? Since I can't get into ADB because the device won't boot not sure what I can do. I have download the stock .zip file and it fails also.

If its under warranty then its probably best to send it back.
If it stuck in bootloop, it could be the ROM
tho without root, i dont think it is possible to reflash a ROM or the ROM

bob232149 said:
If its under warranty then its probably best to send it back.
If it stuck in bootloop, it could be the ROM
tho without root, i dont think it is possible to reflash a ROM or the ROM
Click to expand...
Click to collapse
Not sure if it's under warranty or not I'd probably have to call HTC. It does have S-OFF and the CID shows 11111111 but I can't flash any type of recovery or stock recovery. I can get as far as putting the one shipped ROM file rename it it PC10IMG.zip and it asks to start the update but won't go past the bootloader it just stays at "updating".

check and see which emmc you have
Sent from my HTC Vision using xda premium

demkantor said:
check and see which emmc you have
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Not sure if this helps but in the bootloader menu it says eMMc-boot Apr 13 2011, 14:51:54
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D08981C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25200
(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 super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: SH12RR212562
(bootloader) commandline from head: no_console_suspend=1 wire.search_coun
(bootloader) t=5
(bootloader) command line length =513
(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.13.04.19_M androidboot
(bootloader) .cid=11111111 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=ALL androidboot.mid=PC10***** androidboot.keycap
(bootloader) s=qwerty androidboot.mode=normal androidboot.serialno=SH12RR
(bootloader) 212562 androidboot.bootloader=0.82.0008 zygote_oneshot=off k
(bootloader) memleak=off no_console_suspend=1 wire.search_count=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) aARM_Partion[6].name=devlog
(bootloader) partition number=7
(bootloader) Valid partition num=7
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:25961 msec
FAILED (status read failed (Too many links))
finished. total time: 7.781s

try taking out sdcard
boot into recovery
open adb on computer
Code:
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
of course if you cant get into recovery then this wont tell us anything

demkantor said:
try taking out sdcard
boot into recovery
open adb on computer
Code:
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
of course if you cant get into recovery then this wont tell us anything
Click to expand...
Click to collapse
It will go into recovery but I can't get adb to see the device. When going into recovery I have the options there and at the bottom is where i have
E:Can't mount /cache/recovery/command
E:Can't mount /data/data/recovery/log
E:Can't open /data/data/recovery/log
E:set_bootloader_message_block: emmc_read_data fail!

these are signs of a bad emmc, hopefully you just have a curropt data partition. what recovery are you using? and you have used adb in the past with this phone?
Sent from my HTC Vision using xda premium

demkantor said:
these are signs of a bad emmc, hopefully you just have a curropt data partition. what recovery are you using? and you have used adb in the past with this phone?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Stock recovery and the phone was never rooted in the past at least that I know of but it is stock recovery for sure.

GrandMstrBud said:
Stock recovery and the phone was never rooted in the past at least that I know of but it is stock recovery for sure.
Click to expand...
Click to collapse
not being ever rooted, having stock recovery and spl means you are probably sol even if it isn't a fried emmc. you can try the latest ruu (found on htc.com) but I'm thinking your out of luck. if you want to keep trying log onto #g2root on freenode
Sent from my HTC Vision using xda premium

demkantor said:
not being ever rooted, having stock recovery and spl means you are probably sol even if it isn't a fried emmc. you can try the latest ruu (found on htc.com) but I'm thinking your out of luck. if you want to keep trying log onto #g2root on freenode
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I can't seem to find the stock RUU. I have found the Rom.zip files but they fail with signature verification. I'll keep looking today unless someone knows off hand where to get the RUU

I don't think you will be able to downgrade to stock, the latest update should be avalible on their website, this want an ota unless you already flashed it from their site this may be your best chance. an older ruu will fail and give an error like "radio is older than current" or something.
Sent from my HTC Vision using xda premium

demkantor said:
I don't think you will be able to downgrade to stock, the latest update should be avalible on their website, this want an ota unless you already flashed it from their site this may be your best chance. an older ruu will fail and give an error like "radio is older than current" or something.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I gave it back to them I think it's shot also so unless it's under warranty they are SOL. Thanks for the help though

This happend to me as well 2 days ago, was updating the rom and after that, won't boot anymore. I've tried to re-flash it a couple of times with different roms, but no luck... It just hangs at the boot screen of the phone. I can access hboot and clockwork recovery, but that ain't of any help really. Tried the "Fix Permissions" from clockwork recovery but that doesn't help.
Any other ideas I could try, or at least verify the fried emmc?

demkantor said:
try taking out sdcard
boot into recovery
open adb on computer
Code:
adb shell
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
of course if you cant get into recovery then this wont tell us anything
Click to expand...
Click to collapse
this ^
Zimeon said:
This happend to me as well 2 days ago, was updating the rom and after that, won't boot anymore. I've tried to re-flash it a couple of times with different roms, but no luck... It just hangs at the boot screen of the phone. I can access hboot and clockwork recovery, but that ain't of any help really. Tried the "Fix Permissions" from clockwork recovery but that doesn't help.
Any other ideas I could try, or at least verify the fried emmc?
Click to expand...
Click to collapse
Sent from my HTC Vision using xda premium

[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 in fastboot

I searched, I searched, searched some more and tried probably everything there is, but the phone seems really bricked. In the bortak's troubleshooting guide, it falls under advanced boot problems, first with S-OFF, now it's in S-ON state.
I got this phone for free, I don't know what the previous owner did. I got it stuck in fastboot mode with alpharev logo (joker).
1) There is no ADB access, only fastboot is available, no matter what I do, so goldcard cannot be made.
2) When turned on, phone boots into fastboot mode, displaying black screen with HTC logo and four triangles in the corners
3) It used to have alpharev hboot with S-OFF, now it's with stock HBOOT with S-ON
4) Tried various WWE RUU, they all fail at Radio-V2 Fail PU, all other points are a success. Image update returns always error 152. Radio version does change however, when checked in vars
5) The phone does not recognize any zip file I put in root of 1GB FAT SD card, so that option is out as well.
6) "fastboot oem boot" gets stuck in white screen with HTC logo. I remove batt and it boots again into fastboot.
7) I am able to flash boot and recovery with fastboot, but it does not make a difference. It won't boot into recovery or anything other than fastboot..
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0001
(bootloader) version-baseband: 5.11.05.27
(bootloader) version-cpld: None
(bootloader) version-microp: 031d
(bootloader) version-main: 2.29.405.5
(bootloader) serialno: HT03YPL00391
(bootloader) imei: <edited>
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4172mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: a7cdbe26
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.191s
Do I have a genuine brick?

Unfortunately you have the "Radio-V2 Fail PU". Pretty much a radio brick which is the worst kind.
You can keep trying to run an RUU (try the 2.3.3 GB RUU, use the PB99IMG.zip method), and it may eventually flash. I've seen the 'freezer trick' (genuinely) on these forums where you put the phone in a bag in a freezer for a few minutes, then try the RUU. It may increase the chances of success, but even if it works, it's likely to brick itself because it's a hardware related issue.

eddiehk6 said:
Unfortunately you have the "Radio-V2 Fail PU". Pretty much a radio brick which is the worst kind.
You can keep trying to run an RUU (try the 2.3.3 GB RUU, use the PB99IMG.zip method), and it may eventually flash. I've seen the 'freezer trick' (genuinely) on these forums where you put the phone in a bag in a freezer for a few minutes, then try the RUU. It may increase the chances of success, but even if it works, it's likely to brick itself because it's a hardware related issue.
Click to expand...
Click to collapse
Thanks, I know you are not joking about freezer - I had a friend that hacked PICs by freezing them to certain temp and then heating them up. I will certainly give it a try.
PB99IMG.zip method did not work for me, I never get a prompt to install anything from SD card.

zdravke said:
Thanks, I know you are not joking about freezer - I had a friend that hacked PICs by freezing them to certain temp and then heating them up. I will certainly give it a try.
PB99IMG.zip method did not work for me, I never get a prompt to install anything from SD card.
Click to expand...
Click to collapse
I only did the PB99IMG.zip method once, but found it easiest since it avoids USB or driver issues.
-Make sure it's named "PB99IMG.zip" exactly, not "PB99IMG.zip.zip"
-Then put it on the root of the SD card, not in any folder
-Boot into bootloader (volume down + power), not fastboot. Wait a few seconds for it to find the file, then follow instructions to flash.
Hope you can get it back to life somehow though...

eddiehk6 said:
I only did the PB99IMG.zip method once, but found it easiest since it avoids USB or driver issues.
-Make sure it's named "PB99IMG.zip" exactly, not "PB99IMG.zip.zip"
-Then put it on the root of the SD card, not in any folder
-Boot into bootloader (volume down + power), not fastboot. Wait a few seconds for it to find the file, then follow instructions to flash.
Hope you can get it back to life somehow though...
Click to expand...
Click to collapse
I believe I cannot make it boot to bootloader, it's always fastboot. It's either black screen with four triangles, or white screen with several lines of params in the top lef corner and with RUU as the last line, as soon as I pull the USB cable out. Battery out then power and volume down always takes it to black HTC screen.