[Q] I can't go into Recovery mode. Why?

godhamer

Member
Nov 1, 2009
41
11
0
I have the following problem, I can not go into recovery mode. I know how to do that.I have access only in fastboot menu.when i try to enter from fastboot menu to recovery mode i don't have connection with the PC , because the problem is DRIVERS to start the second step "step2-windows.bat" for rooting.
I HAVE GOLD CARD !!!!!! .I had all drivers before this problem drivers was added to the PC and the phone WAS rooted.
The problem is not in my Windows i try those step on ,Windows7, windows xp ,Linux Ubuntu 10.4. And errors are the same "unknown device" and is impossible to install drivers to ROOT the phone.
Before the phone can not detect the SD card.The problem is fixed now is working .Now the phone is with original ROM and is not rooted.May be I have to flash new bootloader or new recovery.img I don't know.
My cable is not damaged.
the reason that I want to enter in recovery mode is that i want to root the phone again.

!!!!!!!!!!!WHO CAN HELLP ME !!!!!!!!!!!!!

sorry for my bad english
 
Last edited:

BesFen

Senior Member
Mar 11, 2008
1,039
10
0
Surabaya
Strange.......... how it could be:
release your battery, push the power to release residual power , maybe 1 minute, in sert the battery and try go to recovery again
 
Last edited:

godhamer

Member
Nov 1, 2009
41
11
0
Strange.......... how it could be:
release your battery, push the power to release residual power , maybe 1 minute, in sert the battery and try go to recovery again
The same f**** message "device not recognized". And it start to search Drivers on windows 7 x86 (fresh installation before 30 min.).
"Android 1.0, Qualcomm CDMA technologies MSM " - searching for drivers .. and the message "device not recognized" or "unknown device"

:(
 
Last edited:

godhamer

Member
Nov 1, 2009
41
11
0
problem occurs when app2sd install and replace all programs to sd card.I enter into recovery mode and i wipe all options.After reboot my sd card was unmounted ........

may be this will be helpful
 

Firen89

Member
Jul 22, 2010
8
0
0
I've had a similar problem during the rooting-process of my legend

I have Win7 X86 and it also couldn't find any drivers for the legend.
Then I installed the HTC Sync application found on the HTC-Homepage

So i would suggest that you do the same
 

snakehult

Senior Member
Jun 8, 2010
369
60
0
It is not an usb driver issue.
The phone acting as different device depending of its mode normal/fastboot/recovery/usb mount etc



Boot to bootloader select fastboot

run on your computer "fastboot oem boot"

if you have any of thoose =1 you have to alter it to 0
where the bold down is of importance

Normal output is:
INFOTAG xxxxx

INFOCID is HTC__***
INFOserial numer: *********
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length = xxx
INFOactive commandline:
board_legend.disable_uart3=0
board_legend.usb_h2w_sw=0
board_legend.disable_sdcard=0
diag.enabled=0
board_legend.debug_uart=0
smisize=0
userdata_sel=0
androidboot.emmc=false
androidboot.baseband=7.08.35.21 (or other)
andriodboot.cid=HTC_XXX (different depending on serial )
androidboot.carrier=HTX-
androidboot.mid=
androidboot.keycaps=querty
androidboot.mode=normal
androidboot.serialno=xxxxxxxx
androidboot.bootloader=0.43.00001
no_console_suspend=1
console=null
aArm_partion[0].name=misc
aArm_partion[1].name=recovery
aArm_partion[2].name=boot
aArm_partion[3].name=system
aArm_partion[4].name=cache
aArm_partion[5].name=userdata
partition number=6
Valid partition num=6
mpu_nand_acpu_rw 8F2 1000
 
Last edited:

godhamer

Member
Nov 1, 2009
41
11
0
result is :


Code:
C:\android SDK\tools>fastboot oem disable_uart3=0
                              ... INFO[ERR] Command error !!!
OKAY [  0.016s]
finished. total time: 0.016s

C:\android SDK\tools>fastboot oem usb_h2w_sw=0
                              ... INFO[ERR] Command error !!!
OKAY [  0.000s]
finished. total time: 0.016s

C:\android SDK\tools>fastboot oem boot
                              ... INFOsetup_tag addr=0x60000100 cmdline add=0x9D
078D14
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: HT03YNX02877
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=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.
INFOmid=PB7610000 androidboot.keycaps=qwerty androidboot.mode=no
INFOrmal androidboot.serialno=HT03YNX02877 androidboot.bootloade
INFOr=0.43.0001 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 8F2 1000
FAILED (status read failed (Too many links))
finished. total time: 0.874s
the phone must be rooted main is not this is the problem and what this mean
FAILED (status read failed (Too many links))
 

snakehult

Senior Member
Jun 8, 2010
369
60
0
this is your problem:

board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1

The FAIL string at bottom is normal.


So you tell us that you have succeed with unrooting and lock usbcontroller.
Umm, sounds like and bad combination.

I had the uart3=1 probleb but still rooted and could insert new mtd0.img

have you tested to replace this two files?

http://www.shadowchild.nl/mtd0legend.img
http://www.shadowchild.nl/flash_image

download to your sdcard direct or with other usb/sdcard writer.
install terminal
open run
su
to check if it it still rooted
if so

chmod 755 /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0legend.img > /data/mtd0.img
/data/flash_image misc /data/mtd0.img

and reboot
 

godhamer

Member
Nov 1, 2009
41
11
0
this is your problem:

Board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1

the fail string at bottom is normal.


So you tell us that you have succeed with unrooting and lock usbcontroller.
Umm, sounds like and bad combination.

I had the uart3=1 probleb but still rooted and could insert new mtd0.img

have you tested to replace this two files?

http://www.shadowchild.nl/mtd0legend.img
http://www.shadowchild.nl/flash_image

download to your sdcard direct or with other usb/sdcard writer.
Install terminal
open run
su
to check if it it still rooted
if so

chmod 755 /data/flash_image
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0legend.img > /data/mtd0.img
/data/flash_image misc /data/mtd0.img

and reboot
thank you !!!
 

ilos

Senior Member
Jun 17, 2007
1,523
244
0
Saint Priest
do exactly what he does :

http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/

after unbricking your usb , install a stock rom not a custom coz you need a clean system.img.

If you don't do that, usb bricking will come again after flashing with a custom rom...

You can install a new stock rom ( like 2.03 etc... ) and use the thread "how to downgrade to 1.31" and root your legend again.

Another solution :
If the rom is not rooted and you can't follow unbrick instructions try this ( it's what i've done but not sure if result will be the same for you... ) :

Go to recovery mode ( power + volume down ) , select fastboot and try step 1 of rooting process, that will push 1.31 rom + some necessary tool to root the rom.

if all succeded , you will have a 1.31 rom apparently not rooted... but ! yes but ! after installing "connectbot" from market and select "local" and type 2 time "su" i got root access ! if not try step 1 of rooting process under fastboot mode.

If all is ok and you have ( like me ) root acces ( after typing 2 times "su" you will past from $ to # at the beginning of the line... ) , follow unbrink process .

Code:
if your phone can't even see the memory card, enable first with:

fastboot oem enableqxdm 0

Do the above step in Recovery mode.
Once the memory card is visible, transfer the files "flash_image" and "mtd0.img" to the memory card
howevor is possible.

Restart the phone, and install connectbot from the market.

Open connectbot, and through terminal (local) issue the following commands:

su [B][U](2 times)[/U][/B]
cat /sdcard/flash_image > /data/flash_image "then press enter"
cat /sdcard/mtd0.img > /data/mtd0.img "then press enter"
chmod 755 /data/flash_image "then press enter"

[B][U]and to finish process type the following command 2 times[/U] :[/B]

/data/flash_image misc /data/mtd0.img "then press enter"

It will give you 2 errors, on the last command, but ignore it and restart the phone
It should be fixed.
after that i had upgraded to an official stock rom to get back a clean system.img and boot.img. oh yes... phone again unrooted... ok... downgrade to 1.31 and root again :)
 
Last edited:

Kame_boy

Senior Member
Jun 1, 2010
60
7
0
THANK YOU!!!!

My phone lost the ability to read SD-cards and this thread helped me tremendously. I was just about to sell it or go and buy a new one or something.

Hugs to all!
 

bestdaniel20

Senior Member
Jun 8, 2010
123
126
0
Targu Ocna
heelp me

Very very much please help me fix my htc my legend. I do not see sd card, I can not root them anymore, can not find drivers. I do only step 1, you want to put up two do not communicate with the PC. Do not know much about Android, where I do not know the commands to be written, please help me. TeamViewer eventually get through to my PC. My address is [email protected] messenger. I pray a lot.