USB brick/rickrolled/b0rked -> FIXED!

[Guest encrypt]

Just few points...

I've never bricked my desire, I sucessfully rooted my device and flashed Modaco's ROM. USB, Bluetooth... everything was working, just when I used USB Storage Mode... it was working, but it was strange... it just disconnects sometimes... but overall it worked.

I decided to try and apply the USB brick fix... and guess what, I did it and now everything is working... it isn't disconnecting from time to time no more!

[Guest Drell0w]

Hi,

I have some weird issues with my USB connectivity. I have only proper USB connectivity in the recovery mode. So I can't find my CID. Does anyone have a solution for such a problem?

[Guest biker200]

thanks

was brick and solved now.

[Guest MinhQuang]

solved...

Edited June 8, 2010 by MinhQuang

[Guest IEFtm]

Hi,

I have some weird issues with my USB connectivity. I have only proper USB connectivity in the recovery mode. So I can't find my CID. Does anyone have a solution for such a problem?

You don't have USB in fastboot mode? I mean, you should be able to install the correct drivers at that point.

And that's also how you find your CID. (by using 'fastboot oem boot')

Otherwise, you can dump your MISC partition in recovery mode. This should normally contain your CID.

Edited June 8, 2010 by IEFtm

[Guest Pavelol]

while i'm doing step 3 i enterd this command 'cat /sdcard/flash_image > /data/flash_image'

and i'm geting an error: can't open /sdcard/flash_image : No such file or directory.

when i enterd the second command 'cat /sdcard/mtd0.img > /data/mtd0.img'

i dont get any response, should i get any? :\

[Guest jullejul]

how to flash it`shud i go to recoverymode?

[Guest jullejul]

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Lundh>cd /r5-desire-root-alt

C:\Documents and Settings\Lundh\r5-desire-root-alt>fastboot oem boot

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E

07D944

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 not super CID

INFOCID is HTC__Y13

INFOsetting->cid::HTC__Y13

INFOserial number: HT045PL05198

INFOcommandline from head: no_console_suspend=1 console=null

INFOcommand line length =436

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=4.06.00.02_2 androidboot.cid

INFO=HTC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=PB9920

INFO000 androidboot.keycaps=qwerty androidboot.mode=normal andro

INFOidboot.serialno=HT045PL05198 androidboot.bootloader=0.80.000

INFO0 no_console_suspend=1 console=null

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

INFOmpu_nand_acpu_rw A1E 1000

INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:70213 msec

FAILED (status read failed (Too many links))

finished. total time: 7.188s

C:\Documents and Settings\Lundh\r5-desire-root-alt>

[Guest xTc is loVe]

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Lundh>cd /r5-desire-root-alt

C:\Documents and Settings\Lundh\r5-desire-root-alt>fastboot oem boot

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E

07D944

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 not super CID

INFOCID is HTC__Y13

INFOsetting->cid::HTC__Y13

INFOserial number: HT045PL05198

INFOcommandline from head: no_console_suspend=1 console=null

INFOcommand line length =436

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=4.06.00.02_2 androidboot.cid

INFO=HTC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=PB9920

INFO000 androidboot.keycaps=qwerty androidboot.mode=normal andro

INFOidboot.serialno=HT045PL05198 androidboot.bootloader=0.80.000

INFO0 no_console_suspend=1 console=null

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

INFOmpu_nand_acpu_rw A1E 1000

INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:70213 msec

FAILED (status read failed (Too many links))

finished. total time: 7.188s

C:\Documents and Settings\Lundh\r5-desire-root-alt>

Try to do a Factory Reset!

[Guest GhostR1der]

Anyone can help me with the .img file? I use the Amer_bravox_v2 ROM (MCR 3.1 based)

Here is the log:

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D944

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 not super CID

INFOCID is HTC__405

INFOsetting->cid::HTC__405

INFOserial number: HT042PL06563

INFOcommandline from head: no_console_suspend=1 console=null

INFOcommand line length =436

INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.

INFOusb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=1 boa

INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e

INFOmmc=false androidboot.baseband=4.06.00.02_2 androidboot.cid

INFO=HTC__405 androidboot.carrier=HTC-ITA androidboot.mid=PB9920

INFO000 androidboot.keycaps=qwerty androidboot.mode=normal andro

INFOidboot.serialno=HT042PL06563 androidboot.bootloader=0.80.000

INFO0 no_console_suspend=1 console=null

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

INFOmpu_nand_acpu_rw A1E 1000

INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:246684 msec

ERROR: usb_read failed with status e00002ed

FAILED (status read failed (No such file or directory))

Edited June 9, 2010 by GhostR1der

[Guest jullejul]

how to run the flash? shud i make it to a zip file???

where to run it? in adb, cmd, recovery , fastboot?

[Guest andy76q]

how do i backup my present mtd0.img? and do i have to backup more files? I recent got my desire back due the brick problem so now i want to be prepared for any future troubles.

[Guest jolehacker]

hmm? i don't think it was it was ment to be done this way but i did it.

first i bakup everything

then i fix a mtd0_img and flash_image,

then i made them to an update.zip and flash them on recovery mode, if it dosen't was suppose that way it's mabey another what to fix it, but if it was suppose that way pls tell me :) P.S i did get a error on the cid part but it seem to work out anyway :)

Edited June 10, 2010 by jolehacker

[Guest pina]

I bricked this Desire and I copied the 2 files to my SD.

Then I used the commands in terminal emulator:

su

cat /sdcard/flash_image > /data/flash_imago

cat /sdcard/mtd0.img > /data/mtd0.img

Got no error messages, and rebooted several times, entered the same commands several times and still no unbrick :/

I tried the the chmod command chmod u+x /data/flash_image but got the message: 'bad mode'

chmod 755 /data/flash_image results in no error messages... but still no unbrick... anyone ?

[Guest AsayWat]

I bricked this Desire and I copied the 2 files to my SD.

Then I used the commands in terminal emulator:

su

cat /sdcard/flash_image > /data/flash_imago

cat /sdcard/mtd0.img > /data/mtd0.img

Got no error messages, and rebooted several times, entered the same commands several times and still no unbrick :/

I tried the the chmod command chmod u+x /data/flash_image but got the message: 'bad mode'

chmod 755 /data/flash_image results in no error messages... but still no unbrick... anyone ?

er you forgot to flash the misc image!

reread the 1st post.

[Guest pina]

er you forgot to flash the misc image!

reread the 1st post.

ow how do you mean? I see this in the 1st post:

"/data/flash_image misc /data/mtd0.img"

Do I have to input this command in the terminal emulator on my desire?

like this: cat /data/flash_image misc /data/mtd0.img

?

[Guest Rudolfje]

In the terminal, yes, with the 'cat' part, no.

/data/flash_image misc /data/mtd0.img

[Guest jolehacker]

I bricked this Desire and I copied the 2 files to my SD.

Then I used the commands in terminal emulator:

su

cat /sdcard/flash_image > /data/flash_imago

cat /sdcard/mtd0.img > /data/mtd0.img

Got no error messages, and rebooted several times, entered the same commands several times and still no unbrick :/

I tried the the chmod command chmod u+x /data/flash_image but got the message: 'bad mode'

chmod 755 /data/flash_image results in no error messages... but still no unbrick... anyone ?

send me your

flash_imago

mtd0.img

i can fix so it be and update.zip that you applying in recovery mode.

P.S make a Nandroid bakup first, and i'm not 100% sure it work but i think it work :) we can give it a try

[Guest pina]

send me your

flash_imago

mtd0.img

i can fix so it be and update.zip that you applying in recovery mode.

P.S make a Nandroid bakup first, and i'm not 100% sure it work but i think it work :) we can give it a try

it's not necessary anymore. Sigh, I just forgot to perform the last 'misc' command :)

thnx anyway for the help!

Edited June 12, 2010 by pina

[Guest nikosrs4]

how many of you who bricked your phone, have you ever used a 2nd pc except your everyday pc??

today I bricked my phone and that happened when I plugged it to my usual pc for the first time after I have plugged it to another pc.

Edited June 13, 2010 by nikosrs4

[Guest Snarkasm]

Nope; always on my desktop.

[Guest maja]

Hello all,

Now I see the "new" method in the first post...I download the update.zip and I decompress it for see what's new.

The update.zip contain "newcid.img" I edited with a hexeditor and the surprise is in the first line with "11111111" and not with a "valid CID" [eg. HTC__001]... why??

[Guest Nicke]

Hello all,

Now I see the "new" method in the first post...I download the update.zip and I decompress it for see what's new.

The update.zip contain "newcid.img" I edited with a hexeditor and the surprise is in the first line with "11111111" and not with a "valid CID" [eg. HTC__001]... why??

When you run the script on the phone, the script will "open" newcid.img and search for "11111111" it will then replace the ones with YOUR cid and then it writes the file to the phone.

Look in the file "killrecovery.sh" to see what it does.

It's quite hard for the script to know what cid you have before you run it on the phone. :)

Edited June 15, 2010 by Nicke

[Guest maja]

When you run the script on the phone, the script will "open" newcid.img and search for "11111111" it will then replace the ones with YOUR cid and then it writes the file to the phone.

Look in the file "killrecovery.sh" to see what it does.

It's quite hard for the script to know what cid you have before you run it on the phone. ;)

Thank's :(

[Guest NoiSe_NOR]

Hello noob her.

I installed the update.zip and reboot. Now my desire is at 1.15 firmware and i want to update to 1.21, but when i press search for update(or wahtever the button is called in english) its says no updates aliveble for this device. I have updatet to 1.21 before. there is a huge batterilife diffrence between 1.15 to 1.21 on my device so i would like to have 1.21 again ;) without installing a new rom and reconfigure the phone again >.<

sorry for my bad english, not very fit at the moment