[HOWTO] USB Unbrick

kdma

Senior Member
Aug 8, 2010
80
3
0
I had partial bricking problem with boot cycling and a lack of standard usb connectivity. Here is an overview of how I solved this problem.

Background
I rooted my unlocked Bell Canada Legend using the three guides by David Cogen at the unLocker: Downgrade the HTC Legend to 1.31 so It can be Rooted (12.13.10); How to Root the HTC Legend (Updated 12.13.10), and How to Load a Custom Rom on the Legend.

This involved, among other things, making a gold card, installing the Windows Android SDK, downloading the specified downgrading tool, flashing RRU_LEGEND_HTC_WWE_1.31.405.5 ... signed.exe, installing HTC Sync 2.0.33, getting Legend rooting tools, and Loading the excellent Keep it Simple rooted 2.1 ROM (This was before the KIS 2.2 Rom had been released). With some minor difficulties I got this going and the KIS rooted rom was excellent.

However, my real intention had been to install a rooted version of Android 2.2. However, it would not install as the HBOOT version was 0.30.

I tried using the "Howto Update HBOOT to 1.00 keeping your Legend rooted" but I deviated from the instructions and ended up with a semi-bricked Legend that exhibited the commonly encountered boot cycling problem.

After about 8 hours of deep anxiety if found a solution. I lost root capability but got an unbricked, functioning phone with the latest Android 2.2. Here's an overview that may be useful to some Android newbies like me.

PROBLEMS
Boot cycling: start booting process with a buzz, green HTC logo on a white screen for a while, then black screen and reboot, on so on. No access to a functioning system.

No usb connection with Android SDK. i.e.: command adb device showed on available device, HTC* offline.

At this point I though I had a brick. There are some solutions to this problem posted but they appeared way too complicated.
Fortunately, the fastboot menu (hold down return button while pressing power on switch) came up as did the hboot menu. However, I couldn't get to recovery in the hboot menu.

Solution.
On Windows PC used for this work I installed the unRevolkedmod USB drivers which allowed me to connect with the Legend connected via usb cable and in fastboot mode.

In a MSDOS command window in Windows XP I executed from the AndroidSDK subdirectory containing the fastboot executable (in my case C:\...android-sdk-windows\tools\) "fastboot oem enableqxdm 0" which enabled fastboot usb-plugin on the phone (see it com up in red text in the fastboot menu).

In another MSDOS command window I changed to the unzipped "r4-legend-root" directory and ran "fastboot-windows.exe oem rebootRUU" that allowed me to execute the latest RUU (either execute the RUU from this MSDOS command window or click on the file in Windows File Manager) and install the stock HTC 2.2 rom normally following the RUU menus. I used the available RUU_Legend_Froyo_S_HTC_WWE_3.15.405.3.....160328_signed.exe.

I now have a fully functional Legend with the stock unrooted HTC Android 2.2 with hboot 1.01.

Also, I tried the "Rooting with HBOOT 1.0" howto following the directions exactly, but couldn't get to work. I got as far as a functioning Android 2.1 but didn't/couldn't get the 2.2 rom to install as 2.1 wasn't rooted. I think I'll wait until the knowledge base improves. I just reinstalled the stock HTC 2.2 and it is running fine. Much better than a brick!

Although this is short on details, they are available in various threads. I trust that this may be of some help to others that are in the situation I was in. The answer is out there, it just takes a lot of digging!
thanks for your guide i have the same problem you had but i cant seem to solve it
After the procedure i get error 170 when trying to flash ruu even tough my phone get listed with "fastboot devices" am i missing something?

edit
fixed it my phone was using BOOTLOADER driver instead of my htc.
your guide rocks and i think i love you , been messing around for hours and i was ready to throw the phone
 
Last edited:

i4o

Member
Jun 10, 2008
36
2
28
Bourgas
Hi dudes, my friend have a problem.
When try to install FROYO 3.15, he receives error - Error:[110]
It only appears a black screen with htc logo and ends there.

Here is 'fastboot oem boot' log

C:\Documents and Settings\NEW>fastboot oem boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9D
07B198
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
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: HT03ZNX05896
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =445
INFOactive commandline: board_legend.disable_uart3=0 board_legen
INFOd.usb_h2w_sw=0 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.08.35.21 androidboot.c
INFOid=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.m
INFOid=PB7610000 androidboot.keycaps=qwerty androidboot.mode=nor
INFOmal androidboot.serialno=HT03ZNX05896 androidboot.bootloader
INFO=1.01.0000 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
FAILED (status read failed (Too many links))
finished. total time: 0.938s
Problem is solved.
 
Last edited:

Gorbayov

Member
Nov 21, 2010
12
0
0
magically works !! that was pretty easy used free hex editor neo for hex and terminal emulator for the terminal and used ES File Explorer to copy files to phone through wifi
thank you very much
 

eepunk

Member
Aug 24, 2010
42
2
0
Also bricked, unbrick didn't help.

Same with me. The phone itself got stucked in a boot loop and i am unable to do anything at this point. HELP me guys please.
Follow the instructions from earlier in this thread; http://forum.xda-developers.com/showpost.php?p=9889284&postcount=60

Make sure you've got a gold card in.

I too am USB bricked. I have successfully completed the recovery process listed at the beginning of the thread but it has not improved the situation.

log;
Code:
C:\Android\android-sdk-windows\tools>fastboot oem boot
                              ... INFOsetup_tag addr=0x60000100 cmdline add=0x9D
07B198
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
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__038
INFOsetting->cid::HTC__038
INFOserial number: HT043NX02726
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =440
INFOactive commandline: board_legend.disable_uart3=0 board_legen
INFOd.usb_h2w_sw=0 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false  androidboot.baseband=7.13.35.05 androidboot.c
INFOid=HTC__038 androidboot.carrier=HTC-India androidboot.mid=PB
INFO7610000 androidboot.keycaps=qwerty androidboot.mode=normal a
INFOndroidboot.serialno=HT043NX02726 androidboot.bootloader=1.01
INFO.0000 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
FAILED (status read failed (Too many links))
finished. total time: 0.902s
 
Last edited:

~BSOD~

Senior Member
Nov 3, 2010
122
36
0
Bangalore
Ok i got it. Gone other way round. But at last from a boot looping bricked legend, i am now having a equally rooted and custom ROMed legend. Thanks everybody here to help in this matter out and also to help me think in a new way to pass this problem of unbootable bricked legend.

Cheers :):D
 
Sep 30, 2010
19
1
0
C:\sdk\tools>fastboot oem boot
< waiting for device >
... INFOsetup_tag addr=0x60000100 cmdline add=0x9D078D14
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
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: SH087NX00355
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =435
INFOactive commandline: board_legend.disable_uart3=0 board_legen
INFOd.usb_h2w_sw=0 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.05.35.26L androidboot.
INFOcid=11111111 androidboot.carrier=ALL androidboot.mid=PB76***
INFO** androidboot.keycaps=qwerty androidboot.mode=normal androi
INFOdboot.serialno=SH087NX00355 androidboot.bootloader=0.43.0001
INFO 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
FAILED (status read failed (Too many links))


Pls help my one is super CID
 
Sep 30, 2010
19
1
0
thanks for your guide i have the same problem you had but i cant seem to solve it
After the procedure i get error 170 when trying to flash ruu even tough my phone get listed with "fastboot devices" am i missing something?

edit
fixed it my phone was using BOOTLOADER driver instead of my htc.
your guide rocks and i think i love you , been messing around for hours and i was ready to throw the phone
Hi i am also getting error 170 when i am using RUU , anybody can help how to solve the issue
 

Spafey

Member
Nov 22, 2010
35
15
0
Hi there,

I have completed the process and have successfully got my phone unbricked (thank you), however, whenever I flash -anything- else the phone reverts back to its bricked status (although what I flashed remains on the phone).

*** Even just booting into recovery breaks this ***

Fortunately all this requires is to re-enable the SD card and do the final 2 connectbot commands (as the files are already in /data/) to fix the problem.

However, this is required after EVERY flashed ROM which is becoming a pain in the arse very quickly.

I have also noticed that windows still will not install the drives for the phone. Is my case special (totally buggered) or is this the case for everyone?

PS. The first unbricking happened when I clicked partitioning in Clockworkmod recovery (An older version before the 'partition menu' option). I clicked on of the options (probably ext2) but decided I didn't want to do this any more, so set the first option as 0MB and then it allowed me to abort. After rebooting my phone was bricked...

I am currently using a new SD card (despite the old one still working perfectly) and am baffled as to how the phone got bricked because of this...
 

amamr

Member
Aug 15, 2010
13
0
0
Penang.Malaysia
first I tried, it didnt work.

but I figured out you have to be in fastboot usb mode (red writing).

somehow it worked with the RUU provided
can help me?
it seems it stuck during the initialization...
when i plug off the phone from the usb then only the installation continue to next step
but then it stuck at rebooting into bootloader..

i did as mention but still cant make it

help me
:(
 

Salsation

Member
Apr 9, 2009
37
2
0
How can one tell if it worked ?

I followed the instructions on the first page with my rooted legend and it seemed like it worked (I only had to rename the flash_Image.txt to "flash_image" without extension for the CAT command to work...and I think that's where the problem is :(

INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
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 VODAP021
INFOsetting->cid::VODAP021
INFOserial number: SH0BMNX02391
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =446
INFOactive commandline: board_legend.disable_uart3=1 board_legen
INFOd.usb_h2w_sw=1 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.05.35.26L androidboot.
INFOcid=VODAP021 androidboot.carrier=VODA-Australia androidboot.
INFOmid=PB7610000 androidboot.keycaps=qwerty androidboot.mode=no
INFOrmal androidboot.serialno=SH0BMNX02391 androidboot.bootloade
INFOr=1.01.0000 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
FAILED (status read failed (Too many links))
finished. total time: 0.875s
Also, when I try with ADB commands i get:

C:\AndroidSDK\tools>adb shell
error: device not found
My head is playing, I'm not sure where my problem is, with the USB unbrick procedure or HTC ADB drivers (which one should i be concerned with first?)
The card works on the phone and with a card reader on PC (althought not when i use the legend as a USB drive)
 

FORCOMM

Member
Aug 9, 2004
35
1
0
everything good until last step

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

i get this :-
ÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ error 36
 

Caifan09

Senior Member
Aug 2, 2010
310
46
0
Morelia
I can not get the first step. when i apply in adb C:\AndroidSDK\tools> fastboot oem boot

I ge a system error " the program cant start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I got my Android SDK from this site. Im running gingerbread 2.3.3 from ogo2 rom with sense
http://developer.android.com/sdk/index.html


It is 12:04 am here so im get some sleep, and ill talk to you guys in a bit
 

Caifan09

Senior Member
Aug 2, 2010
310
46
0
Morelia
OK it worked thanks a lot, but now my execute fastboot oem boot , i keep getting wating for device. It seems that my pc is not reading my phone in fastboot usb mode, what can i do to fix this

how can i activate usb fastboot mode is my pc is not recognizing my phone.
 
Last edited:

virus54

Senior Member
Dec 24, 2010
54
1
0
I tried this guide about 10 times and it don't work for me
C:\>cd androidsdk\tools

C:\AndroidSDK\tools>fastboot oem eanableqxdm 0
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s

C:\AndroidSDK\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0x60000100 cmdline add=0x9D078D14
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x22F00
(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__K18
(bootloader) setting->cid::HTC__K18
(bootloader) serial number: SH0BGNX01349
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =437
(bootloader) active commandline: board_legend.disable_uart3=0 board_legen
(bootloader) d.usb_h2w_sw=0 board_legend.disable_sdcard=0 diag.enabled=0
(bootloader) board_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=false androidboot.baseband=7.13.35.13 androidboot.c
(bootloader) id=HTC__K18 androidboot.carrier=COMMON androidboot.mid=PB761
(bootloader) 0000 androidboot.keycaps=qwerty androidboot.mode=normal andr
(bootloader) oidboot.serialno=SH0BGNX01349 androidboot.bootloader=0.43.00
(bootloader) 01 no_console_suspend=1 console=null
(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 8F2 1000
FAILED (status read failed (Too many links))
finished. total time: 0.780s

C:\AndroidSDK\tools>
Here the errors on the terminal
 

Attachments

Last edited: