[Stoney Mason]

I was trying to root my brother's phone but got stuck on a waiting for device message during the fastboot command. Turns out htc sync isn't recognizing my phone as when I plug it in to the computer the usb port comes up with unknown device and it won't sync. Kinda stumped as to how to proceed and fix this issue. Any help would be appreciated.

This is a stock phone I believe with the ice cream ota update. It was unlocked and locked in the past though.

This should certainly have been posted in the rooting section. HTC Sync should be turned off(or even better, removed) when trying to use fastboot.

Well at first I didn't have sync installed and after entering the fastboot command I got the waiting for device prompt where it just sat there. I then was reading on htcdev.com and got the (mistaken I guess) impression that I needed that htc sync installed. So I can uninstall that but I guess I'm still stuck then where it sits at the waiting for device line.

[majorpayne]

Did you enable usb debugging?

[Stoney Mason]

Yes.

Although maybe it still has something to do with the computer not recognizing my phone maybe? When I plug it into the computer it lists unknown device in the device manager. I'm pretty sure it didn't do that a few months ago.

[NoYankees44]

What does it say when you type in "adb devises"

Sent from my ADR6425LVW

[orgelbau]

Have you tried booting into bootloader, plugging the phone into a usb port, and choosing fastboot from the bootloader menu? If it shows FASTBOOT USB on the phone after that then you can do everything from a command prompt on your PC. Also, are you sure you are running the latest HTC Sync drivers on your computer? I had a similar issue and it turned out that I needed updated drivers before the computer recognized the phone--even though I had installed the latest version of HTC Sync. Sorry, I don't have a link for the latest

[Stoney Mason]

What does it say when you type in "adb devises"

Sent from my ADR6425LVW

Where and when do I type this. I'm not super knowledgeable on this stuff

---------- Post Merged at 10:04 PM ---------- Previous Post was at 10:03 PM ----------

Have you tried booting into bootloader, plugging the phone into a usb port, and choosing fastboot from the bootloader menu? If it shows FASTBOOT USB on the phone after that then you can do everything from a command prompt on your PC. Also, are you sure you are running the latest HTC Sync drivers on your computer? I had a similar issue and it turned out that I needed updated drivers before the computer recognized the phone--even though I had installed the latest version of HTC Sync. Sorry, I don't have a link for the latest

I'll try this in the morning and report back.

[NoYankees44]

Open a command prompt. Change the directory to whey you have your fastboot stuff. Plug the phone in. Type that command. If it is connected properly it will give you back a serial number

Sent from my ADR6425LVW

[MrSmith317]

If you have the full AndroidSDK installed, check your device manager for an unknown device. If you find one that's supposed to be your phone, update the driver and use the driver in SDK directory\extras\google\usb_driver . If that still doesn't work, make sure you don't have HTC Sync running on your computer. It will hose the entire deal.

[Stoney Mason]

Open a command prompt. Change the directory to whey you have your fastboot stuff. Plug the phone in. Type that command. If it is connected properly it will give you back a serial number

Sent from my ADR6425LVW

Was that "adb devises" or "adb devices". I tried both.

adb devices

C:\AndroidSDK\platform-tools>adb devises
Android Debug Bridge version 1.0.29

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)

adb restore <file> - restore device contents from the <file> backup
archive

adb help - show this help message
adb version - show version num

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

C:\AndroidSDK\platform-tools>

adb devices

C:\AndroidSDK\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached


C:\AndroidSDK\platform-tools>

[majorpayne]

Ah your PC is not even seeing the Phone

[Stoney Mason]

If you have the full AndroidSDK installed, check your device manager for an unknown device. If you find one that's supposed to be your phone, update the driver and use the driver in SDK directory\extras\google\usb_driver . If that still doesn't work, make sure you don't have HTC Sync running on your computer. It will hose the entire deal.

I have htc sync uninstalled. Although I've tried it both with it installed and uninstalled. I believe I have the Android SKD installed. So when I plug in the phone with the usb cable to the computer I get the following message.

"One of the usb devices attached to this computer malfunction and windows does not recognize it". If I then go to the device manager there is unknown device listed there with an exclamation point in a yellow triangle. If I try to update the driver software for that device by searching online it says the best driver software for your device is already installed. If I try to do it manually by pointing it to C:\AndroidSDK\extras\google\usb_driver it says the same thing.

Also under the unknown device properties for device status it says:

Windows has stopped this device because it has reported problems. (Code 43)

---------- Post Merged at 11:10 AM ---------- Previous Post was at 11:03 AM ----------

Ah your PC is not even seeing the Phone

Yeah that's what is confusing me. This whole unknown device thing wasn't like this a few months back. I'm sure it had something listed when I plugged it into the computer. Is there anything that could be causing this that is sort of general knowledge type stuff?

[MrSmith317]

If the phone is in HBOOT, you won't see "adb devices", you should use "fastboot devices" instead. Basically ADB works while you're in Android or Recovery. Fastboot works when you're in HBOOT.

[Stoney Mason]

If the phone is in HBOOT, you won't see "adb devices", you should use "fastboot devices" instead. Basically ADB works while you're in Android or Recovery. Fastboot works when you're in HBOOT.

Tried it but when I typed that in nothing happened. No text appeared. Nothing visible happened on screen in the command prompt.

[Bebeb18]

i have the same problem, do you guys have a way to fix it now??

[nile ellis]

I am also having this problem :S
I would die of happiness if we could figure this out.

I am no geneus but I have tried lots of stuff and I have had no luck at all yet

[KreemN]

Try:
adb reboot-bootloader
Once the device is in bootloader mode, it should appear in fastboot devices
fastboot devices

[MiketheChap]

I've been messing with this for the last several hours. KreemN, your suggestions at least allowed me to move forward a little. While in recovery, the adb reboot-boatloader command rebooted the phone into the bootloader. But, the Fastboot devices command still doesn't do anything. Nor do any of the fastboot commands: they only yield the report, Waiting for Device.

Any more ideas? So frustrating. I do appreciate the suggestion you made.

[Jasaa]

I'm having the same problem, & I've successfully rooted my evo before. I'm actually pretty spiffy on the whole unlocking/relocking/unlocking the bootloader thing. (this is replacement phone #5 I'm trying 2 root >.< ) I've got the same setup I had when I've done it sucessfully before, that didn't work so I uninstalled, reinstalled, updated, & rolled back the drivers & sync manager. Something I've noticed that was specific to this phone is when the phone is turned on & I plug it in to the pc the pc is having issues when I change connection type. It doesn't matter if I start out in sync mode or disk drive mode, it never recognizes the phone when I switch it while plugged in. None of the other 5 have had this issue. The pc acts the same way when I plug the phone in to unlock the bootloader as it does when I switch modes when it's not in bootloader. Not sure if this will help diagnose what's going on or not :/

[Jasaa]

Ok, so this may sound stupid, but have you tried changing the usb port you're using & make sure you're using the right type of cable? I'm kinda feeling like an ***** atm, but at least it worked lol

[Billy Jim]

I solved the problem

1) Open device manager in windows

2) Connect usb cable to your phone pushing volume up button(for xperia sola)

3) Device manager will show you fastboot device for 2-3 sec (before the phone go to charge mode) Right click on fastboot device and install drivers from C:\Android\sdk\extras\google\usb_driver

4) Reconnect usb cable pushing volup button

[virinchi23]

I also have a similar problem. I have a HTC explorer.
While rooting the device, after unlocking bootloader, I immediately relocked it by mistake. Now I'm not able to either root the device nor am i able to unlock it again.
Whenever I try to unlock it, it says waiting for device in command prompt..

[lucca kareem]

love youuu.

[babycake_geeh]

yeah same here except I have and unlocked HTC Evo 4G
It was weird because I unlocked my device, rooted it and I thought evrything was great and it was....for a while untill my super user failed to gain root access! so here I am trying to re-root my HTC Evo but when my fastboot is set to FASTBOOT USB It DOES NOT connect to my computer! I was trying this method of rooting my phone again, which told me to enter things on the command prompt, when I realized my computer isnt detecting my Androids drive at all through FASTBOOT USB! If this helps, these are some of the things I typed in the command prompt:

C:\Users\Carlos>cd c:\

c:\>cd c:\android-sdk

c:\android-sdk>cd c:\android-sdk\platform-tools

c:\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached


c:\android-sdk\platform-tools>fastboot devices
HT16XHL11334 fastboot

c:\android-sdk\platform-tools>fastboot flash recovery recovery.img
error: cannot load 'recovery.img': Unknown error


c:\android-sdk\platform-tools>fastboot devices
HT16XHL11334 fastboot

c:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found

c:\android-sdk\platform-tools>fastboot-windows oem unlock
'fastboot-windows' is not recognized as an internal or external command,
operable program or batch file.

c:\android-sdk\platform-tools>fastboot devices
HT16XHL11334 fastboot

c:\android-sdk\platform-tools>fastboot devices

c:\android-sdk\platform-tools>cd e:\
The system cannot find the drive specified.

c:\android-sdk\platform-tools>

I stopped there because I just gave up. Help? ANYONE?

[wolfe333]

THAT WORKED!!!! Bang on BRO!

[nickgofly]

wolfee, can you make a video or describe better what to do to fix this.
its extremely frustrating.