Develop Bugs

is my evo bricked?

This is my first Android phone and it is (was) awesome compared to my iPhone. And this site is an awesome source of info!! With that being said i think i bricked my phone or at I am missing a step or file somewhere along the way.
When I turn on my phone - it freezes at the HTC screen. (if i plug in the usb cord the device is found by windows and then drops and continues the cycle endlessly)
When I go into Hboot - I can see the phone via fastboot however I can not access the phone through ADB?? Nor can i get to the clockwork mod recovery screen.
HBOOT 0.79.0000 w/ 1.47.651.1 by calkulin
Radio 1.39.00.04.26
cid: SPCS_001
I had successfully rooted using Parts 1 & 2 by toastcfh (and i had flashed a ton of roms - so recovery did work successfully)
WHAT I HAVE TRIED SO FAR:
1. back to the basics and tried toastcfh's method again - "main version older"
2. fastboot - tried flashing images via fastboot - "signature check fail"
3. fastboot - fastboot erase - "FAILED (remote: not allowed)"
4. fastboot -supercid mode - "INFO[ERR] Command Error !!!!
5. revert back to OEM via RUU's - "ERROR[140]: BOOTLOADER VERSION ERROR"
I am putting phone into fastboot and then running executables
RUU_Supersonic_Sprint_1.06.651.4_Radio_1.20.00.03.09_146812.exe
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe
all failed same error message - and if i look at the ruu logs i get see the same error message "remote: 43 main version check fail"
Not sure if this is helpful - from fastboot oem boot - (FAILED (status read failed (Too many links)))??:
C:\sdk\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07DAEC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x23301
INFOTAG:hero panel = 0x1
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is SPCS_001
INFOsetting->cid::SPCS_001
INFOserial number: HT05NHL12163
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =493
INFOactive commandline: board_supersonic.disable_uart3=0 board_s
INFOupersonic.usb_h2w_sw=0 board_supersonic.disable_sdcard=0 dia
INFOg.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata
INFO_sel=0 androidboot.emmc=false androidboot.baseband=1.39.00.
INFO04.26 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_
INFObattery androidboot.carrier=COMMON androidboot.mid=PC3610000
INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb
INFOoot.serialno=HT05NHL12163 androidboot.bootloader=0.79.0000 n
INFOo_console_suspend=1 console=null
INFOaARM_Partion[0].name=wimax
INFOaARM_Partion[1].name=misc
INFOaARM_Partion[2].name=recovery
INFOaARM_Partion[3].name=boot
INFOaARM_Partion[4].name=system
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOpartition number=7
INFOValid partition num=7
INFOmpu_nand_acpu_rw D3E 2000
INFODelay 99998(us) for dpram command before goto AMSS...
INFOjump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:284665 msec
FAILED (status read failed (Too many links))
finished. total time: 7.225s
***
Where do i go next? Besides back to the sprint store to buy another EVO?
Thanks ahead of time!

You need to use one of the OTA root methods

Connect the phone to pc and try the command "adb reboot recovery". I had a similar issue, adb devices showed nothing but issuing that command somehow forced it back into my recovery.

lol... its tough to do an OTA update when my phone is stuck at HTC screen

adb doesnt work b/c android isnt loading: "error: device not found"

If you rooted using toast's method, then your hboot should be 0.76 not 79. What you can try is reflashing the pc36img.zip from toasts method. You can use/acquire a card reader to connect your sdcard up directly to your computer and copy the pc36img onto it. Then boot into hboot and it should scan and find the image on your card.
Sent from my PC36100 using XDA App

jwterminator said:
If you rooted using toast's method, then your hboot should be 0.76 not 79. What you can try is reflashing the pc36img.zip from toasts method. You can use/acquire a card reader to connect your sdcard up directly to your computer and copy the pc36img onto it. Then boot into hboot and it should scan and find the image on your card.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Good info!

i noticed the difference in the hboot also - i went back to square one and tried to flash the pcm36.zip from my sdcard first and i keep getting the "main version older" error.

Ok, the indication here is that you've lost root access by having installed the sprint ota update. Are you unable to get to recovery via hboot? If you can get there, you might be able to restore a nand backup
Sent from my PC36100 using XDA App

mikeinghilterra said:
i noticed the difference in the hboot also - i went back to square one and tried to flash the pcm36.zip from my sdcard first and i keep getting the "main version older" error.
Click to expand...
Click to collapse
Go here and start @ step 2 and complete it http://forum.xda-developers.com/showthread.php?t=701835
If your NAND is still unlocked then after completing the above your hboot will have been downgraded. Please report back so that I may know if I did point you in the right direction.

nunyabiziz said:
Go here and start @ step 2 and complete it http://forum.xda-developers.com/showthread.php?t=701835
If your NAND is still unlocked then after completing the above your hboot will have been downgraded. Please report back so that I may know if I did point you in the right direction.
Click to expand...
Click to collapse
I am going to resurrect this thread because I have the EXACT SAME issue as the OP here but I don't seem to be NAND unlocked. (S-ON)
Going back to toast's method, I get the "main version older"
Any ideas?

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Reboots in fastboot, can't acces recovery

Hi all,
Bravo PVT4
HBOOT 6.93.1002
RADIO 5.17.05.23
I've been using different roms for many time (trying new ones), a few days ago I tried to remove everything and flashed a RUU rom, everything went fine, no errors of any type.
Now I'm trying to get back my root and s-off and can't acces recovery, I used revolutionary to get s-off which I achieved without any problem BUT can't acces recovery so I can't flash another rom and it's stucked in fasboot mode everytime I switch mobile on.
I've flashed nearly every recovery I've found on this forum (amon-ra, clockwork and 4ext) no luck with any of them this is what I see when I use "fastboot oem gencheckpt" command and then phone reboots in fastboot mode.
Code:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A02
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is HTC__304
INFOsetting->cid::HTC__304
INFOserial number: SH12NPL07686
INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq=
INFO1 wire.search_count=5
INFOcommand line length =461
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.17.05.23 androidboot.cid=H
INFOTC__304 androidboot.carrier=HTC-SPA androidboot.mid=PB992000
INFO0 androidboot.keycaps=qwerty androidboot.mode=recovery andro
INFOidboot.serialno=SH12NPL07686 androidboot.bootloader=6.93.100
INFO2 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:429007 msec
FAILED (status read failed (Too many links))
finished. total time: 5.135s
I used 4ext and clockworkmod without problem before, don't know what seems wrong so if anyone comes with any idea would be greatly appreciated.

Checked bortak's troubleshooting guide (see my sig)?

Thx for your answer and yes I already double checked on that guide, right now it seems to work recovery (Amon-ra) and I've managed to install a rom, it seems something wrong with hboot because doesn't seem to recognize which one I've got installed (data++ atm) when installing ICS rom from Sandvold and it used to recognise it perfectly.
Could it be there's a problem there? Only thing there might be on the guide it's the ipvt4 erasesize 40000 but i checked and it says 20000 on my config.
Is there any way to make sure everything on the phone is deleted to start from scratch? Maybe it's only based in sensations but it seems there some problem there in partition table.

Hi, if you have goldcard try copy file below to root and follow instruction for unroot.
I'm describing the whole boot process below for Reference, though.
Hboot mode (Vol- & Power key. Key them pressed for a 5-6 secs
FOR INSTALLING ANY RUU AS PB99IMG.ZIP
Press Vol- , then w/o releasing it, press Power button + Vol –
After 3-4 secs, the following screen shows up momentarily:
· Fastboot
· Recovery
· Clear Storage
· Simlock
This shows the above few options for 2-3 seconds, and then directly checks for PB99IMG.ZIP. It displays:
SD Checking…
Loading…
PB99DIAG.ZIP
Pb99DIAG.nbh
PB99IMG.ZIP
When it finds PB99IMG.zip, it starts to load it (13 secs after you press the Vol- & power key)
It gives the next options after 2min 20seconds (for the WWE 2.29 RUU) from the initial key press of Vol- and Power key.
Parsing………………….[SD zip]
1. Bootloader
2. Radio V2
3. Radio_Cust
4. Boot
5. Recovery
6. System
7. Userdata
8. Splash1
9. Splash2
Do you want to update device?
<Vol Up> Yes
<Vol Down> No
So, net key sequences involved:
· Back+Power
· Power again
· Vol Up
If we chose No, next option:
Do you want to reboot device?
<Vol Up> Yes
<Vol Down> No
If you pressed Yes, then:
Update is in progress..
Do not power off your device.
1. Bootloader -OK
2. Radio V2 -OK
3. Radio_Cust -OK
4. Boot -OK
5. Recovery-Unzipping/Updating
6. System
7. Userdata
8. Splash1
9. Splash2
It cycles through each of these in turn. For me, it took exactly 2 min 17 secs for time when I chose to apply update, to when update was completed.
(Note: At times, it may update the bootloader and reboot. If you have an SLCD screen, when the device reboots, you may not see anything onscreen (black). At this point, it is notable that the device boots to Fastboot instead of Bootloader, so you will need to press Power button again to get it to resume the update process. Once it completes, you will be presented the options to reboot the device. So you just need to Press Vol + after some time)
It displays:
Update complete
So you want to reboot device?
<Vol Up> Yes
<Vol Down> No
Click to expand...
Click to collapse

I'll do it tomorrow morning and tell you results, not sure to understand why do it through goldcard and not directlly with RUU.exe, apart from getting root acces anything else done to phone to justify doing it this way?

This file doesn't unroot your phone, but flash custom recovery. That is reason why not use RUU.exe. This way you can flash radio, hboot, splashscreen and etc as well. Personally, I am using this method, because I don't like fastboot and it's PCfree.

Ok, everything seems to be running ok now, not sure how it suddenly started wroking, tried your method too but a few others before so don't know for sure if yours was better than the others but thanks anyway.
Right now I'm working to get ICS slum version working on my device but seems there's some problem with boot.img (no only for me, a few others reported it too),

I am glad if I can help....

albertronic said:
Ok, everything seems to be running ok now, not sure how it suddenly started wroking, tried your method too but a few others before so don't know for sure if yours was better than the others but thanks anyway.
Right now I'm working to get ICS slum version working on my device but seems there's some problem with boot.img (no only for me, a few others reported it too),
Click to expand...
Click to collapse
You've applied the engineering`s solution (turn off and on). Which ICS will you install?

After 2.3 update, constant boot loop

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

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

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

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

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

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

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

Q - Sd Card Problem not USB brick

Hi there
I have tried everything I can find here but no luck at all solving the sd card problem. I am pretty sure is some softward related, but no idea how to solved it... I see the problem is very common but as this is not a USB brick.. do you have any other idea? Thanks!
This is what i get when i do a "fasboot oem boot" :
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is VODAP001
INFOsetting->cid::VODAP001
INFOserial number: HT04KPL10473
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =421
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=V
INFOODAP001 androidboot.carrier=VODA-UK androidboot.mid=PB992000
INFO0 androidboot.keycaps=qwerty androidboot.mode=normal android
INFOboot.serialno=HT04KPL10473 androidboot.bootloader=6.93.1002
INFOno_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:32606 msec
FAILED (status read failed (Too many links))

What is the problem with sdcard? Thats not clear. If you are not able to access sdcard have you tried Bortaks thread no 13

Problem basically is that i cannot access to the Sdcard at all... And the problem is in the desire... The sd card works perfect in other android devices or PC.
I had it in a mildwild rom and seem to work well. I swap over cyanogenmod and I still could get access to the sd card. But something is wrong as some times I could get access other times i couldn't... i decided to get back to the stock rom and now I cannot get access at all... I have tried everything and no luck. But the sd slot looks like in perfect conditions.... not sure really what to do, as the phone now is useless....

Did you try these commands from the thread I quoted
fastboot oem enableqxdm 0
fastboot oem eraseconfig

handy5876 said:
Did you try these commands from the thread I quoted
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Click to expand...
Click to collapse
I am now really surprised... i tried the above hundred of times and it did not work. Now, I just tried with the last line "fastboot oem eraseconfig" and i see the Sdcard!! Brilliant! I got usb brick after that but not bother at all, my sd slot is alive and that is a great start! Hopefully for good... let see...

If usb brick u should try 4ext recovery and has a usb unbrick option in recovery. Never tried it but a lot of people said it works perfect.
Sent from my HTC Desire

I am start thinking that the phone is having hardware issues...
After everything working perfect, I managed to root, add recovery and install a rom (ICS BETA 0.18.2.1 rom that worked flawlessly), then the sd card and wifi stopped working...
My happiness only lasted 2 hours... Do you know if the wifi antenna is near the sdcard slot? I think is a heating problem... but even when the phone was cold, both did not worked... i tried to wiped data but the same...
Any hope?

Sergiales said:
I am start thinking that the phone is having hardware issues...
After everything working perfect, I managed to root, add recovery and install a rom (ICS BETA 0.18.2.1 rom that worked flawlessly), then the sd card and wifi stopped working...
My happiness only lasted 2 hours... Do you know if the wifi antenna is near the sdcard slot? I think is a heating problem... but even when the phone was cold, both did not worked... i tried to wiped data but the same...
Any hope?
Click to expand...
Click to collapse
use a different rom, not ICS
Sent from my HTC Desire

I will... once my sdcard issue dissapear for a while...