New Radio..

This little program helps to get an idea what driver is working through your USB.

USBDeview - View all installed/connected USB devices on your system

If you scroll waaaaaaay down you can pick for 32 or 64-bit OS. IIRC (on my other PC), it will tell you when you're plugged in that it's an adb device.

Otherwise, I believe if you go into your sdk/tools folder in your command prompt and type "adb devices" it should find your phone, and if it does, you're still plugged in?

Although adb isn't always necessary. Files can be moved in disk drive mode and still flashed just the same, recovery boot is power/home, etc.
 
So i actually updated everything and still no luck :(

I tried adb devices and no devices were found..

Going to restart compy and restart phone and hope that magically fixes everything =/
 
So i actually updated everything and still no luck :(

I tried adb devices and no devices were found..

Going to restart compy and restart phone and hope that magically fixes everything =/

It has been known to somehow help.Also have you tried
adb kill-server
sudo adn shell
 
It has been known to somehow help.Also have you tried
adb kill-server
sudo adn shell

yea it didn't help lol

here is what i got when i ran those commands:

C:\Android_Stuff\SDK\android-sdk-windows\tools>sudo adn shell
'sudo' is not recognized as an internal or external command,
operable program or batch file.

C:\Android_Stuff\SDK\android-sdk-windows\tools>

edit: maybe will help..running vista on comp
 
Last edited:
yea it didn't help lol

here is what i got when i ran those commands:

C:\Android_Stuff\SDK\android-sdk-windows\tools>sudo adn shell
'sudo' is not recognized as an internal or external command,
operable program or batch file.

C:\Android_Stuff\SDK\android-sdk-windows\tools>

O sorry your on windows.Try it without sudo then.
That was a error on my part adb not adn,sorry
 
O sorry your on windows.Try it without sudo then.

edit:

C:\Android_Stuff\SDK\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

P.S. good catch on the adb, i should have known also, but it is the stupid little mistakes that get me lol
 
Last edited:
edit:

C:\Android_Stuff\SDK\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

P.S. good catch on the adb, i should have known also, but it is the stupid little mistakes that get me lol

Yeah i can't beliave i miss spelled that i type adb about a million times a day.Just to make sure usb debugging is on when your plugged into cp?
 
Yeah i can't beliave i miss spelled that i type adb about a million times a day.Just to make sure usb debugging is on when your plugged into cp?

yup =/ The weird part is before it would never pop up when i plugged my phone in, but now it does so as soon as i plug it in. So i tried turning it off and turning it back on to make sure it was working properly
 
yup =/ The weird part is before it would never pop up when i plugged my phone in, but now it does so as soon as i plug it in. So i tried turning it off and turning it back on to make sure it was working properly

Well son of a beach, im running out of ideas,does the cp see your phone when you plug itin and choose disk drive?
 
Well son of a beach, im running out of ideas,does the cp see your phone when you plug itin and choose disk drive?

So i actually figured it out! I just went into device manager and when installing the drives selected from a list of known drivers (instead of searching through the android_stuff folder) and it seemed to work!

No clue why this initially happened but updated radio here i come :) :)

Thanks for the help everyone :)

edit: still doesn't load into the flash menu... but it does find the adb devices lol
edit: when i run adb shell ..it goes into the # sign like i should ..positive sign lol
 
Last edited:
So i actually figured it out! I just went into device manager and when installing the drives selected from a list of known drivers (instead of searching through the android_stuff folder) and it seemed to work!

No clue why this initially happened but updated radio here i come :) :)

Thanks for the help everyone :)

edit: still doesn't load into the flash menu... but it does find the adb devices lol

are you talking about like you type adb reboot recovery and it don't go to recovery it just reboots?
 
are you talking about like you type adb reboot recovery and it don't go to recovery it just reboots?

I am just talking about when i rebooted the phone and held down home/power it just ended up rebooting, but it seems like all the drivers should be fine now
 
I am just talking about when i rebooted the phone and held down home/power it just ended up rebooting, but it seems like all the drivers should be fine now

If you do
adb shell you get # then
adb reboot recovery Don't unplug or close command til it either reboot or goes into recovery menu.If it reboots let me know.
 
Sorry if i asked this one do you ahbe htc sync on your cp?

you haven't actually. I do not have htc sync. Never needed to sync with windows so never bothered to install it =/

BTW thank you so much for helping me... i would be really lost right now lol
 
you haven't actually. I do not have htc sync. Never needed to sync with windows so never bothered to install it =/

BTW thank you so much for helping me... i would be really lost right now lol

Just a little trick i ahd to use for my other cp.Install sync then go into the cp files and find the htc sync files copy the driver file to somewhere you will remeber then you can delete it andthen just tell cp togo to that file when it needs drivers for phone.I just thought of this if you download pdanet and install on your cp you shouldn't have problems connecting to phone pdanet will give you all the drivers you need.