yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] zen15:
yup..., look like USB Brick

here's the exlanation i copy from here http://xdaforums.com/showthread.php?t=691187

How to recognize a USB-Brick?

Symptoms:

* Unable to connect your phone using USB when booted into Android.

* Unable to connect your phone using USB in Custom/Pushed Recovery.

* FM Radio Malfunction.

* Bluetooth Malfunction.

* Wall charging doesn't start immediately.

* Radio Malfunction. (Fix below)

* SD Card Malfunction. (Fix below)

so you can try to flash update.zip or fastboot oem eraseconfig

via fastboot mode (if you have s-off phone)

read couple back post..., there's alot method to unbrick your phone

good luck
[Desire Android Development] earthbellybutton:
Simptom?! Usb Briked....:(

I desperately i need sombodys help, wich is close to Newcastle or to Harlem, Amsterdam! First of all I have my desire rooted with S-on, i use to have Starbust Rom on it, i did have AmonRa recovery, so i did partitioning my sd in this way. But the phone starts to be a bit unstable, like luggy, and black screen. So i back up the rom, did a full wippe, then try to resstore. I got more backups, so i back up a wrong one, then i did the right one, without wipe, then the phone, starts to have a randomly boot loop with " quietlly briliant" i try to install another rom from sd, but the message is coming out : "can't mount /dev/block/mmcblk0p1(or/ dev/block/mmblk0)" (no such a file directory) .For me is sounds like "mathematic" formula....the main problem is, i'm a bit newbee, and i dont have a computer to folow the steps from the Op :( , and i dont have a stable adress to send it in service, cause one day i'm in England North Shields, one day i'm in Ijmuiden Amsterdam ( my job is so). But i was thinking maybe some one nice and with good heart can help me to fix my problem, and it wont be for free. I will pay for it! So please help me some how...buhuuubhuu:(((
[Desire Android Development] earthbellybutton:
Preaty please! Nobody?!
[Desire Android Development] zen15:
Hehe... really sorry man...., if i'm living near one of those place you mention, i will do it for free man....

I suggest to find a computer (a friend's...maybe? ) and trying to fix radio cellular and sd card first, it's not that hard man....
[Desire Android Development] earthbellybutton:
Thank you for suport! But how you whant me to do radio update or something else, when i can't go foward then recovery?! And beside of that, is sound so easy when you say it.....
[Desire Android Development] nbicho:
I had the usb brick problem too, no usb and no BT and all seemed so complicated to fix it, but with this simple command all is ok now! :D

Thanks!!
[Desire Android Development] zen15:
err...maybe it's not so easy as i said....:D (i'm a noob too, just trying to help man.....:rolleyes: cos' i know how it feels when got bricked for the first time:D)

1st, you should set up your computer/laptop with HTC driver (i done it a long time ago, when i root my phone) the tutorial is somewhere in this forum...

2nd, setup an ADB driver and command here's the link: http://xdaforums.com/showthread.php?t=532719

after every setup is done, connect your phone via fastboot (back key + power and no need recovery) and do the command in the 1st post

'fastboot oem enableqxdm 0' this shall enable/fix your radio and sd card functionality (at this step, you can use your phone as usual, but minus BT and USB connectivity with computer)

I think that's for the first thing to do....

fyi..: i'm caring my brick phone for almost a month, trying to fix with all option that i can read and learn from this forum but no hope....:D

till i can manage to sort it out...:p
[Desire Android Development] earthbellybutton:
Hello mate..( zen15) ...good news for me :D , solved with a few euros to a repair centre, tomorow " my heart beat" is coming back :) so keep your finger cross for me. Thank you for the advice! But the problem was not so easy to handel for me , even thouse i will losse the root:(.
[Desire Android Development] zen15:
Glad to hear that.....

Don't worry about root thing....

After everythings setup and kicking.... you can start to root your phone again man....:P hahaha

Cheers....
[Desire Android Development] thighood:
I read a lot here.

it seems USB brick happened when we tried to root the device...

but I know one friend, he didn't root his device, once he update his device from 2.1 to 2.2 (OTA) then he faced this problem...

if he could not use this method (not rooted) what he suppose to do?
[Desire Android Development] zen15:
No.... not exactly like that, i got bricked after doing a nandroid backup... and then flash the custom rom

Your friend can take it to claim the warranty, cos it's not rooted, if not... I've read somewhere in this thread a guy that flash official RUU to his bricked device, assuming that RUU can bring back it alive, but unfortunately his lost his rooted with still in brick...., but he can sort it out..... in a lot of pain in the a** ways.....:p

damn... can't find the link......
[Desire Android Development] Lawrence7:
i cant understand step 3.

what exactly do i have to do ?

when i enter adb devices it only says devices listed and i cant see anything, but when i enter fastboot devices then i get ht and some numbers and i dont know what to do now plz help me what can i do.
[Desire Android Development] Terepin:
I got this from "fastboot oem boot":

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07F9F0
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 not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT08VPL00987
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =428
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.14.05.17 androidboot.cid=H
INFOTC__032 androidboot.carrier=HTC-EastEurope androidboot.mid=P
INFOB9920000 androidboot.keycaps=qwerty androidboot.mode=normal
INFOandroidboot.serialno=HT08VPL00987 androidboot.bootloader=0.9
INFO3.1000 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:31208 msec
FAILED (status read failed (Too many links))
finished. total time: 7.794s

Also, phone rebooted to Android after executing command.

So my questions are:

1. Is my log normal?

2. Is my phone's behavior after executing command normal?
[Desire Android Development] zen15:
yes..., it seems normal, mine like that too..

you got you CID: HTC__032

put it on the link in the OP #1 post, to generate you mtd0.img image.

but let me suggest you before you do that.., have you tried this command:

Boot your phone into fastboot mode and run this:

fastboot oem eraseconfig ? this saved a lot step to unbrick you device, there's a lot of people report success to fix their mtd partition with just that command...

hope it can help
[Desire Android Development] SeaWaLK:
You saved my phone! I was going thru all sort of method and i decided to listen to u are try your method. And my sdcard is mountable again!
[Desire Android Development] gafi:
Had a dead BT and USB.

fastboot oem eraseconfig - FIXED!

Thanx!
[Desire Android Development] rajverma3135:
question about detailed solution of restoring USB function on ur bricked desire

Hi there

I had sd card n usb problem

sd card problem has ben sorted now, but usb has still problem

i followed this post n

had results like this

Microsoft Windows [Version 6.0.6002]

Copyright (c) 2006 Microsoft Corporation. All

rights reserved.

C:\Users\verma>cd..

C:\Users>cd..

C:\>cd androidsdk

C:\AndroidSDK>cd tools

C:\AndroidSDK\tools>fastboot oem boot

... INFOsetup_tag

addr=0xA0000100 cmdline add=0x8E

07F9F0

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 H3G__001

INFOsetting->cid::H3G__001

INFOserial number: SH09HPL01826

INFOcommandline from head:

no_console_suspend=1 msmsdcc_sdioirq=

INFO1 wire.search_count=5

INFOcommand line length =460

INFOactive commandline:

board_bravo.disable_uart3=1 board_bravo.

INFOusb_h2w_sw=1

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.09.05.30_2

androidboot.cid

INFO=H3G__001

androidboot.carrier=COMMON

androidboot.mid=PB99200

INFO00 androidboot.keycaps=qwerty

androidboot.mode=normal androi

INFOdboot.serialno=SH09HPL01826

androidboot.bootloader=0.93.0001

INFO 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:26441 msec

FAILED (status read failed (Too many links))

finished. total time: 5.064s

C:\AndroidSDK\tools>

but I am not sure how to update the mtd0.img

i tried to follow the link where need to put

INFOCID is H3G__001

INFOsetting->cid::H3G__001 and rom version number but I could not find the rom number as I am using Miui rom and tried to put that number but i needs 10 digits number

as well I am not sure how to amend/modify mtd0.img file

I will be grateful if you could describe it in depth.

cheers

Raj
[Desire Android Development] PTelad:
Guys, I hope you can help me.

My desire is USB bricked, I'm trying the fix but I'm stuck at step 1

I don't have a CID, my desire is Super CID.

check my my oem boot:

c:\adb>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A12
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 empty
INFOsetting->cid::11111111
INFOserial number: HT0CJPL02818
INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq=
INFO1 wire.search_count=5
INFOcommand line length =455
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 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=1
INFO1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
INFOdroidboot.keycaps=qwerty androidboot.mode=normal androidboot
INFO.serialno=HT0CJPL02818 androidboot.bootloader=0.93.0001 no_c
INFOonsole_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
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:149600 msec
FAILED (status read failed (Too many links))
finished. total time: 5.055s

what should I do.

I've tried flashing the update.zip from same thread over at MoDaCo, but nothing.

Help me plz :(
[Desire Android Development] PTelad:
OMG! It actually worked!

I've created a custom mtd0.img with the code "SuperCID" and it worked!

Full usb functionality and BT!

Tnx alot you guys! ^_^
[Desire Android Development] zen15:
in my case.., i've flashed back to any HTC Sense rom, get the rom number and generate the mtd0.img file

but have you tried this...: fastboot oem eraseconfig in fastboot mode????
[Desire Android Development] yreham:
hello, i need some help, i bricked my usb connection but it seems that i cant connect to adb either, i put the phone in fastboot usb launch command promt but can never find my sdk folder. i have cm7, s-off.myu phone sees the sd card but my pc doesn't, thank you for your help. are all cid the same?d

hey, i just discovered that when i switch off debugging windows finally sees my sd card ok
[Desire Android Development] rajverma3135:
Bricked USB problem on HTC DESIRE

Hi Everyone

I have usb bricked and i followed the step mentioned in this post and could not find the solution. I will be grateful if anyone could help me to sort out this prob.

As requested in post if could not find solution then upload the boot log

Please find attached the flash file n mtd0.img file( i could not download it) but i used the CID generator my CID is H3G__001 and serial no was 2.25.771.1

C:\Users\verma>cd..

C:\Users>cd..

C:\>cd androidsdk

C:\AndroidSDK>cd tools

C:\AndroidSDK\tools>fastboot oem boot

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

07F9F0

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 H3G__001

INFOsetting->cid::H3G__001

INFOserial number: SH09HPL01826

INFOcommandline from head: no_console_suspend=1

INFOcommand line length =422

INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.

INFOusb_h2w_sw=1 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.09.05.30_2 androidboot.cid

INFO=H3G__001 androidboot.carrier=COMMON androidboot.mid=PB99200

INFO00 androidboot.keycaps=qwerty androidboot.mode=normal androi

INFOdboot.serialno=SH09HPL01826 androidboot.bootloader=0.93.0001

INFO 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:407265 msec

FAILED (status read failed (Too many links))

finished. total time: 4.898s

C:\AndroidSDK\tools>

I will be grateful if you could help me to sort this out

Cheeers

Raj
[Desire Android Development] rajverma3135:
Thanx everyone problem has been solved.

Cheers
[Desire Android Development] ReyTech:
@professor

can i follow this mehod of yours for my bricked desire which was with 2.32 rom!

1. i hva a hboot 0.93 bricked by flashing a pb99img.nbh _froyo 2.29_signed .zip?

2. i dont hve usb connection with my phone!

3. but i hve recovery and sd card support!

4. when i try to flash the update.zip with sd card to mny device i get

" E:failed to verfiy whole-file signature

e: signature verification failed

installation aborted"

5. and i cant boot into fast boot (with back + power) only Hboot and then fastboot is this ok?

and if there's any other way to fix this problem! can i flash the same as pb99img.zip? pls do shed some light

WBR

ReyTech.
[Desire Android Development] rajverma3135:
Hi

Yesterday I followed the following 2 links n my same problem on HTC desire has been solved

http://xdaforums.com/showthread.php?t=857444

http://xdaforums.com/showthread.php?t=691639

Follow these thoroughly

Good luck
[Desire Android Development] ReyTech:
thanks for replying! i wanted to add this as well that;

1. iam not rooted

2. i cant fast boot

3. how do i find my CID when i cant fastboot? any way around?

4. can i just anyhow flash the same 2.32 ruu the phone was on thru the sd card (p99img) method or i have to follow this guide for usb brick?

5.THANKS

WBR

ReyTech.
[Desire Android Development] ReyTech:
@rajverma3135

thanks for the tutorials and the links! but is it possible to fix a completely bricked desire (which only boots in HBOOT 0.93.10) when i press the power button! and which is also a usb brick (no usb connectivity to comp) and no (back+ poweron fastboot mode)but with sd card support and possiblilty to go to original android recovery(volumne down key + power then recovery then volumnekey up + power)? if yes!

then can i copy the files to sd card and flash the phone with adb shell in (hboot then fastboot usb?) and so what will the commands be and can i use the same files? or is there anything more to add? pls help me out! i need to fix my phone or else endup paying for this phone!

and how do i do TEMP root? PLEASE!

WBR

ReyTech.
[Desire Android Development] ReyTech:
thanks for your help ive revived my phone! just with the first command (fast boot oem) the phone is working! but now the problem is when i switch off the phone and try to switch on it again! then it goes in HBOOT mode? shall i continue to follow the guide where i have to fix the partition or just RUU and that should fix my problem? pls advice!

WBR

ReyTech.
[Desire Android Development] sretlow:
I also had bricked my phone but got it almost fixed with adb commands. I did a nendroid restore and got it all back only...bluetooth is not working anymore. Wenn I try to switch it on it will turn off itsself. So I can't activate bluetooth anymore. Rest seems to be working fine.

I have GingerVillain as rom.
[Desire Android Development] bates060:
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:

'cat /sdcard/flash_image > /data/flash_image'

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

You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)

These commands arent working for me its just says no such directory?

Any help Will be much apreciated

;)

Bates060
[Desire Android Development] sretlow:
I now know what triggers my USB Bricking. After I do a nandroid backup in the recovery mode it bricks my phone. The backup is fine but after a new start the SD card can't be mounted and bluetooth, phone network and so on doesn't work anymore. It happened to me twice now
[Desire Android Development] bates060:
When reading through the entire thread many people say errors of 'no such file or directory' this is because you havent extracted the flash_image out of the zip

Hope this helps...

I do the whole process and all ok but no fix. It thinks its charging through use when connected to action wall charger... any help?

:-)
[Desire Android Development] zen15:
Hi all..., i just trying to help.......

I have done through all this process with no go....

until i can sorted it out by myself....

i'm following this thread after that...and read that a lot of people got brick but can fix in the easy way...:D

here's the step by step:

1. ADB knowledge is required here

2. Boot your phone in fastboot mode

3. Connect USB cable between phone and computer

4. Open Command prompt (windows) or terminal (linux)

5. Navigate to ADB directory

6. Do fastboot oem eraseconfig command

7. Reboot into android, and check all those dead functions (BT, USB etc)

lot of people report that with this simple command everything back normal again, try it and please report back here, so everybody can read if its succes or not.

hope you guys can understand my english...:p

i do these step too, but never work for me..., no matter how i tried, it doesn't work.....:mad:
[Desire Android Development] Terepin:
Need help. Our fellow member visited me in hope I'll fix his Desire. The symptoms indicates it's just USB-Brick but as it turned out it is way beyond USB-Brick. Desire can't mount SD card and trying to do any fastboot command resulted into phone freeze. Because of that even RUU isn't working. Trying to execute fastboot oem enableqxdm 0 resulted into this (after manual unplug):

C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
FAILED (status read failed (Unknown error))
finished. total time: 295.761s

Any help will be appreciated.
[Desire Android Development] rraaka:
Zen, its nice to see you posting and helping out but i think one needs to be s -off for your solution to work ? is that so ?
[Desire Android Development] zen15:
Hmmm... yeah..maybe, i'm not so sure....
[Desire Android Development] sieempi:
Yes, S-OFF needed..
[Desire Android Development] bates060:
Ok so i managed to move all the files needed to /data and when i un the flash command i got an error something like " 00x000000 : not enough space

I rebooted the ohine and now all i get is a normal boot up but screen flickers blue and i have no radio reception or sd functionality or usb

I know its a big dream but can anyone help me further or just to get rid of the blue flickering screen - i can access root files and there is no mtd0.img file in data is this the reason for the screen flicker?

I Cant connect to the Sdk ADB either i have correct Drivers Installed but still no device found, even device manger doesnt pick anything being connected to the computer but the phone is in debugging mode?

Would really apreciate any fix for this and i will be will to donate to my savour ;)

Thanks in advance Bates060

EDIT: Ok so i got the android SDK working and everything but device isnt found and my computer doesnt do anything when connecting to it nor show anything in device manager
[Desire Android Development] abz54:
hi guys,

I decided to try to change my rom today after being with auratxsense hd, i am using recovery 3.0.05r3 as the other always resulted in sd brick for me, i went down the logical route of backing up and everything went fine, i then restarted the phone and it has been sd bricked again, but this time i cant get the fastboot command to work because it wont find my device even though it is listed in the device list as working with the correct drivers (it comes up as android 1.0, under unspecified in windows 7 x64) When I try the adb shell command it instantly comes up with error: device not found

Does anyone know of a fix to this, if i could get the phone connected through adb i should hopefully know what to do from there on
[Desire Android Development] bates060:
Go into device manager and right click Android 1.0 and click update.

Search for drivers manually

and go into your android Folder Example - C:\Program Files\Android\android-sdk\extras and it will install the correct driver then try again.

Hope this helps

;)
[Desire Android Development] abz54:
Hi,

sorry for not mentioning it but i have tried every driver that is available, i am not a very experienced user but i am not new to this either as i have solved the usb brick on many occasions before, the only thing stopping me from doing this now is the driver as when i type in the adb shell command it returns with no device found, but it does respond to fastboot commands
[Desire Android Development] bates060:
in sdk manager download go to available packages and then third party add-ons

Google Inc.

Google usb driver pakage download then do the steps i said again

Hope this helps

;)
[Desire Android Development] abz54:
Ive already tried that and every other driver that i can come across, under the device list it is my htc which are the latest drivers and older drivers that have worked for me before dont seem to be working
[Desire Android Development] bates060:
Do you have HTC Sync installed? If so uninstall it and try again.

Sorry for the long process but elimination is required.

Make sure USB Debugging mode is enabled before rebooting into fast boot aswell

Hope this helps,

;)
[Desire Android Development] abz54:
still no luck, it still comes up with no device found, which is puzzling me because i can use fastboot commands without a problem

edit: i have no access to anything besides bootloader