[Q] Desire not booting and no recovery - Desire General

Hi guys/gals,
I have a Desire UK from Orange which I've been using happily rooted, running LeeDroid S-Off for quite some time. I decided the other day to switch to Oxygen... anyway, to cut a long story short I now have a phone that can get to Hboot and Fastboot but nothing else. Recovery or normal boot just displays the HTC logo for a while then a black screen with a white line either side and a "bling" noise. I've managed to shift Hboot from the dreaded 0.93 to 6.93 using the alphrev downgrader and the followed the guide here w?w?w?.mikesouthby.co.uk/2010/08/htc-desire-downgrading-hboot-and-installing-custom-froyo-rom/ (sorry, first post so I can't post links. Remove the ?'s)
I do have a goldcard made up, I do have a USB card reader, I do have two backups made from CWM on my PC, I really just need to get CWM up and running on my phone to restore the image.
Any guesses or advice (other than "you should have left it alone")?
Thanks,
Baz
Bravo PVT3 SHIP S-Off - Hboot6.93.1002 - Microp-051d - Touch Panel-SYMW0101 - Radio 4.06.00.02_2
A bit more info. I just ran "fastboot oem boot" it gives me an output showing the CID is being set to ORANG001 is it possible it has somehow become un-rooted? I've found a link on restoring the mtd0 so I'm looking in to that. :-/
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 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =463
(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) =ORANG001 androidboot.carrier=ORANGE-UK androidboot.mid=PB99
(bootloader) 20000 androidboot.keycaps=qwerty androidboot.mode=normal and
(bootloader) roidboot.serialno=SH09DPL01345 androidboot.bootloader=6.93.1
(bootloader) 002 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count
(bootloader) =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:861138 msec
FAILED (status read failed (Too many links))
finished. total time: 6.617s

You are using the r2 revision of a hboot. I do not know which, but I get this from the fact, you have the hboot version 6.93.1002 (old revision 0.93.1000). These hboots are locked, so they cannot be overwritten by ruu hboot. So you have to flash this downgrader first:
http://alpharev.nl/bravo_downgrade.img
MD5: 6c482ccfa6b7093de4ee1a5804ccbdfc - DO NOT FORGET TO CHECK!!!
Do this via fastboot, as you would flash a hboot:
Code:
fastboot flash hboot bravo_downgrade.img
Code:
fastboot reboot-bootloader
fastboot erase cache is not needed, because the downgrader deletets all partitions.
After this, flash stock hboot:
http://alpharev.nl/bravo_alphaspl.img
MD5: 7bd5234711364880de1fa982dcf3a2d6 - DO NOT FORGET TO CHECK!!!
Code:
fastboot flash hboot bravo_alphaspl.img
Code:
fastboot reboot-bootloader
Code:
fastboot erase cache
Now, download this stock ruu:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
MD5: 14d740a8ec68bd8cc830ff7c0905df72
Turn your desire off and put goldcard in your desire. After this, boot your desire in fastboot mode and run the downloaded exe. After following the instructions on screen, you have an unrooted htc desire running latest htc stock rom without any branding.

Thanks Mat! I'll give it a go and let you know what happens. Wish me luck

OK I just tried that and all seemed to go ok. All the MD5 hashes checked out, the flashing went without a problem, the RUU installed without a hitch... but it still doesn't work. Slightly different this time though. Last time I had a few black bars through the white background of the HTC logo and after a while it went black and played the "bling" noise. This time I get the HTC logo on the white screen displays perfectly but no "bling" noise and doesn't move past this. If I try to boot to recovery then I get the white screen with HTC logo followed by an ominous black screen with a little picture of a desire in the middle and a big red scary ! in a triangle.
Any more ideas you or anyone else have would be appreciated.
Thanks,
Baz

AH! A few reboots later and it's working! You're a star Mat! Thanks!

Related

[Q] Half way to brick...

Hi!
I need some help!
I want to sell my phone, so I want to go back to stock rom.
I downloaded wwe rom ruu installer and started the update process.
Something wrong is happened and my phone now is on half way the stock and rooted.
The bootloader and the fastboot is accesibble, but the phone is doesn't boot.
Recovery not accessible and the security is on. (S-ON)
I tried to repeat the ruu install, but it doesn't succesfull. Error 155 Unknown Error.
I tried to install many ruu versions, but nothing.
I copied out from the ruu installers the rom.zip and I put to sdcard renamed PB99IMG.zip.
The bootlader read the zip file and then checking but after go back to normal menu. No option for update.
I read lot of forums, but I can't find the solution. I don't have more ideas.
Somebody can help me?
Atesz
Atesz79 said:
Hi!
I need some help!
I want to sell my phone, so I want to go back to stock rom.
I downloaded wwe rom ruu installer and started the update process.
Something wrong is happened and my phone now is on half way the stock and rooted.
The bootloader and the fastboot is accesibble, but the phone is doesn't boot.
Recovery not accessible and the security is on. (S-ON)
I tried to repeat the ruu install, but it doesn't succesfull. Error 155 Unknown Error.
I tried to install many ruu versions, but nothing.
I copied out from the ruu installers the rom.zip and I put to sdcard renamed PB99IMG.zip.
The bootlader read the zip file and then checking but after go back to normal menu. No option for update.
I read lot of forums, but I can't find the solution. I don't have more ideas.
Somebody can help me?
Atesz
Click to expand...
Click to collapse
If you have a goldcard then flash the latest RUU, if you haven't follow this process to create the goldcard:
boot into fastboot, then type:
Code:
fastboot oem gencheckpt
this will reboot the phone into recovery,
then type:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1*/cid
This will give you a CID, which you need to copy down meticulously.
Then once you have the number, follow this guide. (you will obviously have to skip the bit of the guide where he is getting the CID - because you already have it)
NOTE: Because the flashing process didn't complete, there is a chance that the phone will not boot into recovery as it may be damaged, and it will not be possible to create a goldcard.
If it does work however, once you've got the goldcard flash the latest WWE RUU
Thank you for your answer!
This is the output of the fastboot oem gencheckpt:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe oem gencheckpt
< waiting for device >
...
(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 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 not super CID
(bootloader) CID is HTC__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number: HT05XPL05483
(bootloader) command line length =409
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=4.08.00.09 androidboot.cid=H
(bootloader) TC__032 androidboot.carrier=HTC-EastEurope androidboot.mid=P
(bootloader) B9920000 androidboot.keycaps=qwerty androidboot.mode=recover
(bootloader) y androidboot.serialno=HT05XPL05483 androidboot.bootloader=0
(bootloader) .83.0001
(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 23A 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:4197 msec
FAILED (status read failed (Too many links))
finished. total time: 5.070s
After that the phone is trying the recovery boot, but no picture on the phone just something muddy thing. I see something green color, maybe this the old clockworkmod recovery.
I have warranty for the phone, but the alpharev starting picture is still on the phone
Atesz79 said:
Thank you for your answer!
This is the output of the fastboot oem gencheckpt:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe oem gencheckpt
< waiting for device >
...
(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 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 not super CID
(bootloader) CID is HTC__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number: HT05XPL05483
(bootloader) command line length =409
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=4.08.00.09 androidboot.cid=H
(bootloader) TC__032 androidboot.carrier=HTC-EastEurope androidboot.mid=P
(bootloader) B9920000 androidboot.keycaps=qwerty androidboot.mode=recover
(bootloader) y androidboot.serialno=HT05XPL05483 androidboot.bootloader=0
(bootloader) .83.0001
(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 23A 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:4197 msec
FAILED (status read failed (Too many links))
finished. total time: 5.070s
After that the phone is trying the recovery boot, but no picture on the phone just something muddy thing. I see something green color, maybe this the old clockworkmod recovery.
I have warranty for the phone, but the alphacrew starting picture is still on the phone
Click to expand...
Click to collapse
did you try the next command after the oem gencheckpt? (have to wait a few seconds for phone to boot into recovery +/- 10 secs.. wait about 20 just to be sure)
doesn't matter if you don't see anything... as long as adb works
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell cat /sys/cla
ss/mmc_host/mmc1/mmc1*/cid
error: device not found
oh dear :/ well that was my idea.. sorry dunno what else I could say.. you just need to find the right RUU.. if your phone is branded try the latest RUU for your phone from http://shipped-roms.com/index.php?category=android
The phone is not branded, so I don't understand why I can't install the latest stock rom. I tried all of the downloadable ruu roms.
I think, I'm done with phone rooting
Thank you for your help!
Atesz79 said:
The phone is not branded, so I don't understand why I can't install the latest stock rom. I tried all of the downloadable ruu roms.
I think, I'm done with phone rooting
Thank you for your help!
Click to expand...
Click to collapse
sure it's unbranded? if you're in Europe try the HTC_Europe RUU
Sure, HTC_032 WWE East Europe from Official HTC Store.
I tried this roms
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684.exe
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe
Atesz79 said:
Sure, HTC_032 WWE East Europe from Official HTC Store.
I tried this roms
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684.exe
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe
Click to expand...
Click to collapse
OH... okay.... lol eerrmmmm maybe we could try and push the RUU manually...
Extract the rom.zip from the latest WWE RUU
Once you have copied it to your desktop shutdown the RUU
in c:\ click create new folder and name it RUU
put the rom.zip in the RUU folder
plug your phone in and open command prompt and type
Code:
fastboot oem gencheckpt
wait until phone boots recovery
Code:
adb shell reboot oem-78
fastboot erase cache
fastboot flashzip C:\RUU\rom.zip
fastboot reboot
strong chance it won't work with s-on
adb shell: error: device not found
If i boot to fastboot and then fastboot flashzip: signature verify fail
There is a way to go back to s-off?
Atesz79 said:
adb shell: error: device not found
If i boot to fastboot and then fastboot flashzip: signature verify fail
There is a way to go back to s-off?
Click to expand...
Click to collapse
not entirely sure it's possible to S-OFF from bootloader, AFAIK you need to be booted into a ROM.. ahh this is a pain in the butt
Yes this is...
If you have any more idea don't hesitate write to me...
Thanks bortak!
not possible to S-OFF if you're not booted into a ROM
[22:27] <bortak> is it possible to S-OFF through fastboot, without being booted up into a ROM?
[22:29] <@hyuh> bortak: no it is not possible.
[22:29] <bortak> thanks, that's what I thought
Click to expand...
Click to collapse
Ok, I understand.
Can I delete the apharev logo if I'm not booted into a ROM? (Why so serious-Joker)
Atesz79 said:
Ok, I understand.
Can I delete the apharev logo if I'm not booted into a ROM? (Why so serious-Joker)
Click to expand...
Click to collapse
You can with RUU (but y'know...) or with fastboot (but y'know...) so I don't thnk you can at this stage
Ok, thank you!

[Q] Desire stuck at HTC screen with exclamation marks at 4 corners

I just got this htc desire in this condition and the back cover branded says Orange. The phone powers on and black screen appears with HTC logo in the middle and exclamation marks in a triangle at all 4 corners of the screen. I somewhere read that its kind of veiled recovery screen or something. Pc detected the phone when I connected via usb cable but nothing happened on the phone but when I unplugged the cable the screen changed and I can see this;
Bravo PVT1 ship S-on
hboot-0.93.0001
micorp-051d
touch panel synt0101
radio-5.11.05.14
RUU (in red)
I searched for Orange stock RUU and found this.
OTA_Bravrange_CH-FR_2.22.71.2-1.19.72.3_P_release8xcr7nx2a68060l7.zip
Now I want to root it, S-off and flash a custom rom. But not sure if its the right RUU and don't have idea how to get started. I previously unlocked the bootloader of my HTC Explorer, rooted it and successfully flashed Jaggy's Rom. That's all I know of android world so far. Searched around the forum and found a similar thread. Someone suggested a few things but links were dead. So any help with the links of required stuff please.
Thanks.
Check bortak's troubleshooting guide.
Sent from my toaster
yea...my username sucks...deal with it...
well I tried bortak's tutorial but didnt work for me. Made a goldcard tried running the given WWE RUU, starts fine but then freezes at "Sending". It says to wait till 10 minutes and waited for like an hour but still nothing. Then read somewhere to force boot the corrupted ruu but "fastboot oem boot" but didnt pass the Telstra boot screen, had to pull out the battery. Now again stuck at 4 triangles. Got a query... could it be the bad goldcard? I mean is there anyways to check it? Or if its not the goldcard is there anyway to fix my device?
here is what i got when tried "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 0x21F04
(bootloader) TAG:hero panel = 0x2
(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 HTC__622
(bootloader) setting->cid::HTC__622
(bootloader) serial number: HT05PPL02709
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =425
(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) TC__622 androidboot.carrier=Asia-HK-CHT androidboot.mid=PB99
(bootloader) 20000 androidboot.keycaps=qwerty androidboot.mode=normal and
(bootloader) roidboot.serialno=HT05PPL02709 androidboot.bootloader=0.93.0
(bootloader) 001 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) 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:31799 msec
Use the 2.3 gb upgrade from HTCDev. U dont need a goldcard
Sent from my HTC Desire
jmcclue said:
Use the 2.3 gb upgrade from HTCDev. U dont need a goldcard
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for your help but still now luck Downloaded 2.3 gb ruu and now stuck at error 155. So far it seems like its not the correct ruu for my device (just googled so correct me if I am wrong). Its an Orange branded device, dont know anything about its previous status whether it was ever rooter or s-off or anything. The guy just told me he tried to run Telstra ruu from htc website and successfully booted once and then stuck at this. When I unplug the usb the 4 /!\ disappears and I get this;
Bravo PVT1 ship S-on
hboot-0.93.0001
micorp-051d
touch panel synt0101
radio-5.11.05.14
RUU
Any further help???
There is no ruu for orange network. 2.3 gb upgrade is ment for all. Check bortaks guide in my sig
Sent from my HTC Desire

DesireZ doesn't get past the htc logo screen

Hello XDA,
I know this is my first post but I have a problem with my cousins' htc desire z. When i try to power it on it just freezes at the htc logo.
My cousin had the phone for about 3 years and was never tempered with (no custom recovery, no bootloader unlock, no custom rom, no nothing).
If i hold volume down + power button i am able to get into hboot.
I can get into fastboot and can issue commands from my pc (will post details below).
If i get into recovery however, after 4-5 seconds the phone makes 7 short vibrations and then shuts down.
If i try to do a factory reset from hboot, the phone freezes.
hboot screen
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 20122, 23:36:27
HBOOT USB PLUG
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
I tried to do a 'fastboot erase cache' but got:
erasing 'cache'...
FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
other info:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.2
(bootloader) serialno: SH16TRT02882
(bootloader) imei: xxx
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3829mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
fastboot oem boot
...
(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 0x25202
(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__405
(bootloader) setting->cid::HTC__405
(bootloader) serial number: SH16TRT02882
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(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.04.03_M androidboot
(bootloader) .cid=HTC__405 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-ITA androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 16TRT02882 androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff 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:121268 msec
FAILED (status read failed (Too many links))
finished. total time: 8.602s
Click to expand...
Click to collapse
Is the phone bricked? Can i somehow flash a RUU and get it working?
I tried running "RUU_Vision_HTC_WWE_1.72.405.2_Radio_12.28e.60.140f_26.04.02.17_M2_release_160660_signed.exe" but i saw the version was older but i gave it a go ...
also tried "RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_12.56.60.25_26.10.04.03_M_release_224299_signed.exe" but got stuck during "rebooting to bootloader" (the phone was in hboot > fastboot when i tried to flash. The phone froze also ...
After 10 minutes i decided to get into bootloader myself so i took out the battery and booted while holding down volume down.
I got an error shortly after about the usb connection (error code 171 i think).
I am thinking of putting a PC10IMG.zip and try flashing this way but i don't know which one ... can you plese help me out with this?
(As far as i know, the phone is from the UK)
Any other solutions/suggestions are also welcomed ...
Thank you! I am really trying to get this thing to work, My cousin is young and can't afford a new phone but i fear it might be a hardware fault ... If someone could help we would be forever grateful!
additional info:
- i don't know what android flavor she had before, nor does she
- there is no memory card in the phone right now because i tried booting without it.
donload LATEST RUU HERE rename StockRom.zip, now boot into fastboot mode
fastboot oem rebootRUU
now
fatboot flash zip StockRom.zip
when complete
fastboot reboot
truthfully i dont think you will be able to do this as you have the signs of a fried emmc but its worth a shot.
oh if you have the desire z see if there is a version available that is newer than yours on htc website as without super cid you can only flash newer roms then current version as well as ones coded to your phones firmware.
goodluck!
demkantor said:
donload ... rename StockRom.zip, now boot into fastboot mode
fastboot oem rebootRUU
now
fatboot flash zip StockRom.zip
when complete
fastboot reboot
truthfully i dont think you will be able to do this as you have the signs of a fried emmc but its worth a shot.
oh if you have the desire z see if there is a version available that is newer than yours on htc website as without super cid you can only flash newer roms then current version as well as ones coded to your phones firmware.
goodluck!
Click to expand...
Click to collapse
Thanks for the suggestion but unfortunately it didn't work. When i try to "fastboot oem rebootRUU" the phone freezes.
Rebooting doesn't seem to work on the phone. I tried previously with other tools/RUUs too, the phone hangs.
I guess the emmc is fried :/
Thanks for the help though
More than likely but where your at right now its hard to know for sure, you can always take the back off and see if its made by samsung or sandisk (samsung being the bad one)
Sent from my HTC MyTouch 4G Slide using xda premium

Frozen after a storm. No way to access recovery

Hello, I'm a poor noob and I'm in trouble with my Htc Desire
I have CM7 on it (s-off, of course)
After being surprised by a storm while I was on my scooter, the device got wet and turned off. I've waited a long time and when I've tried to turn it on, it got stuck on "Are you serious?" screen.
I can access fastboot mode, but vol buttons are unresponsive.
Neither I can access recovery mode.
So I've tried to flash everything with adb/fastboot via prompt screen.
No way to flash any recovery on it, when I use fastboot boot recovery.img, it remains frozen on Are you serious sceen.
Every time I try to flash a Rom I got errors messages.
For example, with CM10 I got this in response
sending 'zip' (169346 KB)... OKAY [ 25.989s]
writing 'zip'... FAILED (remote: not allowed)
while with fallout 5 rom or Viper
sending 'zip' (443849 KB)... FAILED (remote: data length is too large)
What am I missing?
These are infos on hboot screen
SPL/hboot version: 6.93.1002.
Radio version: 5.14.05.17.
Main software version: 2.29.405.5.
cid: htc__405.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
Please, save my dear cell!
powhatan said:
Hello, I'm a poor noob and I'm in trouble with my Htc Desire S.
I have CM7 on it (s-off, of course)
After being surprised by a storm while I was on my scooter, the device got wet and turned off. I've waited a long time and when I've tried to turn it on, it got stuck on "Are you serious?" screen.
I can access fastboot mode, but vol buttons are unresponsive.
Neither I can access recovery mode.
So I've tried to flash everything with adb/fastboot via prompt screen.
No way to flash any recovery on it, when I use fastboot boot recovery.img, it remains frozen on Are you serious sceen.
Every time I try to flash a Rom I got errors messages.
For example, with CM10 I got this in response
sending 'zip' (169346 KB)... OKAY [ 25.989s]
writing 'zip'... FAILED (remote: not allowed)
while with fallout 5 rom or Viper
sending 'zip' (443849 KB)... FAILED (remote: data length is too large)
What am I missing?
These are infos on hboot screen
SPL/hboot version: 6.93.1002.
Radio version: 5.14.05.17.
Main software version: 2.29.405.5.
cid: htc__405.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
Please, save my dear cell!
Click to expand...
Click to collapse
ok, I've managed it to flash cwm 2.5.0.7
powhatan said:
ok, I've managed it to flash cwm 2.5.0.7
Click to expand...
Click to collapse
This is Desire only (bravo). Post in Desire S section.
Sent from my HTC One using Tapatalk 4 Beta
dvsk69 said:
This is Desire only (bravo). Post in Desire S section.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sorry, ctrl-c ctrl-v error
My device is Desire, I'll edit first post.
I'm trying to flash a custom ROM, but i'm stucked on partitioning SD. I've used both g-parted and easeus PM, but after creating any kind of ext partition it returns to be unallocated. Maybe I have a damaged SD?
New sdcard. Partition ok, this time. Water isn't good for SDs...
Cooldroid installed, waiting for first boot. I think it will take up to 15 mins, isn't that?
Yes that's normal
Sent from my HTC One using Tapatalk 4 Beta
dvsk69 said:
Yes that's normal
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
No sign of life. Still stuck on why so serious screen...
I'm starting to be concerned...
I come from cm7, do I have to change kernel?
Kernels are incorporated into ROM zip, no need to worry about that.
It might not boot if you have inappropriate hboot table for the ROM, since you're coming from cm7 you could have cm7r2 hboot, try ROM which will fit in that or change hboot to stock and try again, take care tho, changing hboot on unstable phone might be dangerous.
If you're on stock or decide not to change, then try different ROM and see what happens. You could also try to make a log through adb and see what's going on.
Hope that water didn't damage your hardware.
freebird24h said:
Kernels are incorporated into ROM zip, no need to worry about that.
It might not boot if you have inappropriate hboot table for the ROM, since you're coming from cm7 you could have cm7r2 hboot, try ROM which will fit in that or change hboot to stock and try again, take care tho, changing hboot on unstable phone might be dangerous.
If you're on stock or decide not to change, then try different ROM and see what happens. You could also try to make a log through adb and see what's going on.
Hope that water didn't damage your hardware.
Click to expand...
Click to collapse
Now I've a different problem.
Looking for a solution about my broken microsd I've done a ruu flashing. Now when i boot phone it remains stuck in 4 triangle htc black screen.
I've tried to reflash CM7 and now I can only boot with fastboot boot oem command. How can I get rid of this?
Try to look my theader: http://forum.xda-developers.com/showthread.php?t=2371018
sterver1 said:
Try to look my theader: http://forum.xda-developers.com/showthread.php?t=2371018
Click to expand...
Click to collapse
I don't see connection with my troubles... My phone is bootable, but only with this strange trick (fastboot boot oem)
Devices infos are now these:
SPL/hboot version: 6.93.9999.
Radio version: 4.06.00.02_2.
Main software version: 2.29.405.5.
cid: htc__405.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
Wi.fi not working, still stuck at 4 triangles black screen and when I unplug it from usb a white screen shows upo with this basically the same things
Alpharev Unlock
Bravo PVT-1 SHIP S-OFF
H-BOOT 6.93.9999
MICROP 031D
TOUCH PANEL SYNT0101
RADIO 4.06.00.02_2
RUU
This is fastboot screen when I boot
C:\Program Files (x86)\Minimal ADB and Fastboot>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 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 HTC__405
(bootloader) setting->cid::HTC__405
(bootloader) serial number: HT04KPL02768
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =461
(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__405 androidboot.carrier=HTC-ITA androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=HT04KPL02768 androidboot.bootloader=6.93.999
(bootloader) 9 no_console_suspend=1 msmsdcc_sdioirq=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) 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:10402 msec
FAILED (status read failed (Too many links))
finished. total time: 11.700s
powhatan said:
I don't see connection with my troubles... My phone is bootable, but only with this strange trick (fastboot boot oem)
Devices infos are now these:
SPL/hboot version: 6.93.9999.
Radio version: 4.06.00.02_2.
Main software version: 2.29.405.5.
cid: htc__405.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
Wi.fi not working, still stuck at 4 triangles black screen and when I unplug it from usb a white screen shows upo with this basically the same things
Alpharev Unlock
Bravo PVT-1 SHIP S-OFF
H-BOOT 6.93.9999
MICROP 031D
TOUCH PANEL SYNT0101
RADIO 4.06.00.02_2
RUU
This is fastboot screen when I boot
C:\Program Files (x86)\Minimal ADB and Fastboot>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 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 HTC__405
(bootloader) setting->cid::HTC__405
(bootloader) serial number: HT04KPL02768
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =461
(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__405 androidboot.carrier=HTC-ITA androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=HT04KPL02768 androidboot.bootloader=6.93.999
(bootloader) 9 no_console_suspend=1 msmsdcc_sdioirq=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) 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:10402 msec
FAILED (status read failed (Too many links))
finished. total time: 11.700s
Click to expand...
Click to collapse
gmaps unresponsive and other gps application don't start correctly...
Seems like a radio problem...
Trying to flash radio to 5.17.05.23
Seems to flash via recovery mode, but when I print device info, still old radio version... I'll try fastboot command...
what results?
http://forum.xda-developers.com/showthread.php?t=687464
trey32 said:
what results?
http://forum.xda-developers.com/showthread.php?t=687464
Click to expand...
Click to collapse
Latest radio link dead, trying from http://www.mofirouz.com/wordpress/2011/03/htc-desire-radios/
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash radio radio.img
sending 'radio' (26112 KB)...
OKAY [ 3.794s]
writing 'radio'...
OKAY [ 31.945s]
finished. total time: 35.746s
In boot phase it vibrated 4/5 times, now is in htc white screen (after fastboot oem boot, which is only way I can boot)
powhatan said:
Latest radio link dead, trying from http://www.mofirouz.com/wordpress/2011/03/htc-desire-radios/
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash radio radio.img
sending 'radio' (26112 KB)...
OKAY [ 3.794s]
writing 'radio'...
OKAY [ 31.945s]
finished. total time: 35.746s
In boot phase it vibrated 4/5 times, now is in htc white screen (after fastboot oem boot, which is only way I can boot)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43014587&postcount=4919 try this
trey32 said:
http://forum.xda-developers.com/showpost.php?p=43014587&postcount=4919 try this
Click to expand...
Click to collapse
The question is, how long do I have to wait to complete the flashing process? I'm still with white htc logo screen and yet I don't want do a pull battery...
powhatan said:
The question is, how long do I have to wait to complete the flashing process? I'm still with white htc logo screen and yet I don't want do a pull battery...
Click to expand...
Click to collapse
Pull battery done. Radio upgraded
SPL/hboot version: 6.93.9999.
Radio version: 5.17.05.23.
Main software version: 2.29.405.5.
cid: htc__405.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
still no wi-fi... and GPS not responding
trey32 said:
http://forum.xda-developers.com/showpost.php?p=43014587&postcount=4919 try this
Click to expand...
Click to collapse
What exactly am I supposed to do with this link? Is it a stock rom?
Meanwhile gmaps is vanished and I can't install it, same thing for Ingress app.
powhatan said:
What exactly am I supposed to do with this link? Is it a stock rom?
Meanwhile gmaps is vanished and I can't install it, same thing for Ingress app.
Click to expand...
Click to collapse
Even better! Tried to ruu and now...
S-on, hboot 0.75 and ERROR 140!
powhatan said:
What exactly am I supposed to do with this link? Is it a stock rom?
Meanwhile gmaps is vanished and I can't install it, same thing for Ingress app.
Click to expand...
Click to collapse
yes, it will flash all stock so the phone should boot normal with all its functions....

[Q] Can I revive my G2 or is it bound to eternal sleep?

A while back I had posted about my problems with my G2.
"For a while now I've been running a MIUI ROM without problems.
Today, the phone didn't want to wake up from sleep (tried using trackpad and power button).
I pulled the battery and started the phone back up but after the boot animation it went to black screen and wouldn't do anything from there.
I wiped cache and rebooted, went through the app checking but somewhere in the process crashed and went to black screen.
After several failed tries of pulling the battery and trying to reboot but only getting black screen, I did a full wipe and tried installing a new ROM but have not been able to boot into it.
According to the ROM installation everything went fine, but when I boot the phone up it starts trying to boot the MIUI boot animation then goes to black screen even though I did a full wipe and flashed a new ROM.
After doing various full wipes and sdcard formats, the phone doesn't seem to want to boot into anything even if I flash a rom, and recovery keeps loading up in Safe Mode due to a problem with /cache."
After trying many different ways, I gave up and fired up my trusty G1.
I decided after almost a year to give the G2 another try and for some reason now it was working fine and let me flash a rom and boot into it.
Unfortunately soon after, errors kept popping it to the point that I rebooted into recovery to try to flash a different rom and see if it fixed the problem.
Apparently, all it did was make things worse.
Phone got stuck on bootscreen and since then won't boot into rom or recovery.
The only thing I can get it to do, aside from getting stuck on the white screen with "htc" then going black, is booting into the bootloader.
From there I can use fastboot and look at the system info but if I try to boot into recovery from there it flashes the white htc screen then screen goes black and nothing happens.
From bootloader:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 9 2010, 15:56:38
From SYSTEM INFO:
SN-SH0C2R200230
LCD-SO
TOUCH PANEL-ATMELC12_20aaT
Commit-adbd7a75
OS Ver.-1.19.531.1
CID-11111111
eMMC-Sandisk 2151MB 4407295sectors
Is there anything I can do that will possibly save my phone?
Thanks in advance for any help.
Bootloader info looks good, you have the better of the two emmcs that were put in these phones
What I would do is flash all new firmware through fastboot
http://forum.xda-developers.com/showthread.php?t=2348266
At the bottom of the first thread in this link there is some info on "debricking" these phones. There will be a link in one of those threads for a PC10IMG.zip I made that may help you out, but if it doesn't work you may have dead nand... Hopefully not
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for the reply!
I started to go through some of the steps to recover with no luck yet.
I did run the "fastboot oem jump" and got this:
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 2
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(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 T-MOB010
(bootloader) setting->cid::T-MOB010
(bootloader) serial number: SH0C2R200230
(bootloader) commandline from head: no_console_suspend=1 androidboot.seli
(bootloader) nux=permissive
(bootloader) command line length =494
(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.02.01.15_M2 androidboo
(bootloader) t.cid=T-MOB010 androidboot.batt_poweron=good_battery android
(bootloader) boot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keyc
(bootloader) aps=qwerty androidboot.mode=normal androidboot.serialno=SH0C
(bootloader) 2R200230 androidboot.bootloader=0.84.2000 no_console_suspend
(bootloader) =1 androidboot.selinux=permissive
(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:94512 msec
There's a few errors right at the beginning but not sure what those mean.
It also just sits at the white htc screen and never does anything.
Went through the next step of erasing recovery and flashing the one included in the post but still no luck.
I then entered the "fastboot erase system -w" command and it seemed to be fine erasing everything but i saw some errors with formatting.
If you need any other information that could possibly help understand my problem more just let me know.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1728208
See post 30
If it doesn't work for you I'm afraid your phone is toast
Sent from my Nexus 4 using XDA Premium 4 mobile app

Categories

Resources