I know it's a bit odd to use win2003 server as desktop. And I know there's no support for windows 2003 from Android.
But still...I think it is worth to ask
kqueenc said:
I know it's a bit odd to use win2003 server as desktop. And I know there's no support for windows 2003 from Android.
But still...I think it is worth to ask
Click to expand...
Click to collapse
I can't think of any reason why it won't work.
Have you actually tried it yet?
pharrisee said:
I can't think of any reason why it won't work.
Have you actually tried it yet?
Click to expand...
Click to collapse
Yes, i did.
First, HTC Sync is not able to be installed.
Then I manually update driver for "adb devices" in device manager(I download usb driver by using android sdk manager), it can not even recognize the driver.
It works perfect under my netbook, which has win7 running on it.
which driver are you using? I mean there aren't any drivers for the hero for win2k3 and what does adb says when you want to start?
Seelbreaker said:
which driver are you using? I mean there aren't any drivers for the hero for win2k3 and what does adb says when you want to start?
Click to expand...
Click to collapse
On my win7 pc, there's no need to install any driver manually. After I install HTC sync and copy tools/ folder to the PC and run "adb shell" (or any other command under the folder), it works.
But since I can't install HTC sync under 2003, I download "usb driver" by using "Android SDK and AVD manager", but the driver does not help.
On 2003, I run "adb devices", it says "adb server is out of date, restarting the daemon. Devices is not connected"(can not remember the exact message, but something like that.)
Is it a 64bit OS? In Win7 64 bit I have to install the 64 bit usb drivers from HTC.
You can find them here:
http://handheld.softpedia.com/progDownload/HTC-Hero-Drivers-Download-81097.html
Can you install the HTC sync in compatibility mode?
pharrisee said:
Is it a 64bit OS? In Win7 64 bit I have to install the 64 bit usb drivers from HTC.
You can find them here:
http://handheld.softpedia.com/progDownload/HTC-Hero-Drivers-Download-81097.html
Can you install the HTC sync in compatibility mode?
Click to expand...
Click to collapse
Mine is Windows 2003 server enterprise edtion, it can support up to 32GB memory, but still I don't think it is a 64 bit OS.
No. I can't install htc sync under compatibility mode.
Any other suggestion?
kqueenc said:
Mine is Windows 2003 server enterprise edtion, it can support up to 32GB memory, but still I don't think it is a 64 bit OS.
No. I can't install htc sync under compatibility mode.
Any other suggestion?
Click to expand...
Click to collapse
Install through a virtual machine.
If the OS supports 32gb ram, then its 64 bit. It is imposible for a 32 bit os to access any more than 4gb of ram because of the limitation in the length of number you can store in 4 bytes, or 32 bits.
So try the 64 bit drivers. If all else fails, stick ubuntu in a VM and try with the linux drivers
CyberWalrus said:
If the OS supports 32gb ram, then its 64 bit. It is imposible for a 32 bit os to access any more than 4gb of ram because of the limitation in the length of number you can store in 4 bytes, or 32 bits.
So try the 64 bit drivers. If all else fails, stick ubuntu in a VM and try with the linux drivers
Click to expand...
Click to collapse
that 4gb limit for a 32 bit os is not strictly true.
Lot's of 32 bit server os's support more than 64gb through a mechanism called PAE (http://en.wikipedia.org/wiki/Physical_Address_Extension), and it looks like win2k3 supports pae (http://support.microsoft.com/kb/283037).
Not saying that's the case here, but it could very well be.
pharrisee said:
that 4gb limit for a 32 bit os is not strictly true.
Lot's of 32 bit server os's support more than 64gb through a mechanism called PAE (http://en.wikipedia.org/wiki/Physical_Address_Extension), and it looks like win2k3 supports pae (http://support.microsoft.com/kb/283037).
Not saying that's the case here, but it could very well be.
Click to expand...
Click to collapse
Could well be, good call.
*on topic* so yes, id try 64 bit version (no harm in trying)
I agree with pharrisee. Way back to win2k time, win2k enterprise edition can already support more than 4gb, and there was no 64bit thing at that time. It is this PAE thing.
But anyway, I just tried both drivers of x64 and x86. It says can not find proper driver when I point to the folder.
Strange thing is, the unrecognized device called "Android phone".
I thought it suppose to be "adb device" or something like that.
) Problem Solved.
Instead of using search of driver, I manually installed "Android phone" as a "ADB interface", and applied 32bit usb driver on it.
After restarting computer, and now "adb shell" works again!! Amazing.
Well, HTC Sync is still not working, but as long as adb can connect to the phone, I don't really care.
Thanks, every one.
Related
My little gift to the community, who don't happen to have driver hacking experience
Here's the adb drivers modified with the new ADB device ID.
For both x86 and amd64
Let me know if it works, as I only tested on amd64
Regards,
P
EDIT: Oh, should mention how to use these.
You need to extract the ones you are after (x86/amd64) and point device manager to the folder when it shows the "Android Phone" with unknown drivers.
This is great, I've been looking for this the past 2 weeks.
But.....
I get an error message that WinUSBCoInstaller.dll is missing. When I add the file from the android 2.2 sdk, my machine is asking for WdfCoInstaller01007.dll. Your zip contains 01005.
I'm on Win XP 64.
Azkabor said:
This is great, I've been looking for this the past 2 weeks.
But.....
I get an error message that WinUSBCoInstaller.dll is missing. When I add the file from the android 2.2 sdk, my machine is asking for WdfCoInstaller01007.dll. Your zip contains 01005.
I'm on Win XP 64.
Click to expand...
Click to collapse
Hmm. I don't know about XP x64 (it's rarely supported btw), but try renaming the file to what it needs. I had no issues installing it straight in.
And this is needed why?
My ADB works like a charm? Even with the new 2.1 ROM's.
ltraddical said:
And this is needed why?
My ADB works like a charm? Even with the new 2.1 ROM's.
Click to expand...
Click to collapse
You're lucky then. They changed the device ID of the adb driver on this release today. Maybe newer drivers are better, but I don't know... I used SDK 1.5 drivers from November btw.
how would i go about using this? do i place them the in drivers folder in the sdk folder?
info5i2002 said:
how would i go about using this? do i place them the in drivers folder in the sdk folder?
Click to expand...
Click to collapse
Yeah, go to device manager and update the drivers of the unrecognised Android Phone. Use these.
anon2122 said:
Yeah, go to device manager and update the drivers of the unrecognised Android Phone. Use these.
Click to expand...
Click to collapse
alright, that's great! thanks.
ltraddical said:
And this is needed why?
My ADB works like a charm? Even with the new 2.1 ROM's.
Click to expand...
Click to collapse
Same here. Others probably didn't install the drivers right.
jaymac407 said:
Same here. Others probably didn't install the drivers right.
Click to expand...
Click to collapse
Nah. I think it's age of drivers. I installed them fine, but a long time ago. I guess they have been updated since then, but I'm not the only person to have had this issue. I think adwinp had the problem too, although he's been going for longer than me on the hero, so has likely got old drivers too...
I did the exact same thing, but it's nor working, when I selecht the map it says that it can't install it.
"There are no devices to be found"
Since I installed an 2.1 ROM i can not go into adb anymore.
anon2122 said:
You're lucky then. They changed the device ID of the adb driver on this release today. Maybe newer drivers are better, but I don't know... I used SDK 1.5 drivers from November btw.
Click to expand...
Click to collapse
My adb stopped working 4 days ago. So I reinstalled HTC Sync from HTC's website. This fixed it and still it works after flashing Pauls ROM. So I guess an easier fix is to just install the latest HTC Sync.
The latest offical Android SDK drivers do not work with 2.1 Hero so far (device is not recognized).
However, installing the (old) HTC Sync includes all the necessary drivers for our Hero, even with 2.1 installed!
So no need for anything else.
Does not work with Win7x64
any chance of you making the Linux version of adb compatible with 2.1 as well?
Umm. It's working fine here on 7 x64 (that's where I was having the issue).
Also, adb is running on my ubuntu x64 machine fine, although i downloaded the 2,2 SDK for it
anon2122 said:
Umm. It's working fine here on 7 x64 (that's where I was having the issue).
Also, adb is running on my ubuntu x64 machine fine, although i downloaded the 2,2 SDK for it
Click to expand...
Click to collapse
ahh, yes I used the old 1.5 adb. I forgot they had released the 2.2 sdk. the updated version works great. well thanks for reminding me
You don't need any new sdk.
This is the way to do it:
If you have a linux workstation, great. Otherwise, popin a bootable CD, boot into the system, open a terminal, plugin your HTC, and do a:
# dmesq | tail
You'll get a pcid in the format of 0bb4:xxxx where xxxx is the new pcid you need to replace in the adb usb driver inf.
That's it.
Here's a sample output:
[ 5144.934366] usb 2-1.3: Product: Android Phone
[ 5144.934367] usb 2-1.3: Manufacturer: HTC
[ 5144.934369] usb 2-1.3: SerialNumber: HT999L903279
[ 5145.681192] usb 2-1.3: USB disconnect, address 16
[ 5145.863757] usb 2-1.3: new high speed USB device using ehci_hcd and address 17
[ 5145.962591] usb 2-1.3: New USB device found, idVendor=0bb4, idProduct=0c98
[ 5145.962596] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5145.962599] usb 2-1.3: Product: Android Phone
[ 5145.962600] usb 2-1.3: Manufacturer: HTC
[ 5145.962602] usb 2-1.3: SerialNumber: HT999L903279
works on xp 64
Got this fully working on Windows XP x64 with HTC Hero running Android 2.1. Thanks alot, I've tried many ways to debug my device on XP 64 and all of them ended with "adb devices" showing nothing.
I had to expand "amd64\android_usb.inf" a little bit.
Following lines at the end of [Google.NTamd64] section:
Code:
; HTC Hero
%USB\VID_0BB4&PID_0C98.DeviceDescRelease% = androidusb.Dev, USB\VID_0BB4&PID_0C98
%USB\VID_0BB4&PID_0C98&MI_01.DeviceDescRelease% = androidusb.Dev, USB\VID_0BB4&PID_0C98&MI_01
Following lines at the end of [Strings] section:
Code:
USB\VID_0BB4&PID_0C98.DeviceDescRelease="HTC Hero"
USB\VID_0BB4&PID_0C98&MI_01.DeviceDescRelease= "HTC Hero Composite ADB Interface"
If you have something else than HTC Hero or HTC Dream — just replace "VID_0BB4&PID_0C98" with your device IDs.
Lendarel said:
Got this fully working on Windows XP x64 with HTC Hero running Android 2.1. Thanks alot, I've tried many ways to debug my device on XP 64 and all of them ended with "adb devices" showing nothing.
Click to expand...
Click to collapse
I hope you realise that if you download the latest HTC Sync it installs x64 drivers correctly and then you just have to start using adb for it to work. The guide linked in my signature also shows you how to set it up to run every time you start your computer so that you can run it from any command prompt without having to change location. This thread is more or less dead.
I have been looking with no avail for the past hour to find a Windows 7 32 bit ADB driver for my EVO.
I just Got a new netbook and its got Win7. Can anyone point me in the right direction. All i can find is tuturials for win7 64 bit drivers.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Here you go...
Did you try downloading the drivers from the Android SDK site, along with the SDK itself? Should include them, then install just like Win 7 x64. Speaking if which, why not upgrade to 64 bit? Same license keys, and there's not much reason to be using 32bit these days with the advent of virtualization.
--Swyped from my EVO using XDA App.
i have search, read, re-read and tried a lot of different things..... i can not for the life of me get the android driver to install. i'm trying to root my phone and it just won't install at all.
i'm running windows 7 64 bit. if anyone could help that'd be great.
DualSportDad said:
i have search, read, re-read and tried a lot of different things..... i can not for the life of me get the android driver to install. i'm trying to root my phone and it just won't install at all.
i'm running windows 7 64 bit. if anyone could help that'd be great.
Click to expand...
Click to collapse
you need to manually install the driver. look right above comment section in attatchment to install htc diag driver....
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
it still won't install. i go to android 1.0, update driver, chose the folder, "failed". if i say "i have disk" and point it to "sndroidusb" it says the driver is not compatible with my device.
DualSportDad said:
it still won't install. i go to android 1.0, update driver, chose the folder, "failed". if i say "i have disk" and point it to "sndroidusb" it says the driver is not compatible with my device.
Click to expand...
Click to collapse
download and use the HTC DIAG driver 64bit point to that driver.
Here ya go
thanks i'll try that when i get home. funny thing is i tried to get a driver to install on my vista 32 bit laptop and i can't do it on here either. there is obviously something i'm doing wrong. i think with the 64 bit i might have found the problem.... the 64 bit driver that someone supplied me said that it wasn't signed or something like that. i have read up about the problem and supposedly i need to boot into test mode in windows. i might have to try that as well if the above driver doeesn't work.
thanks again for all the help.
ps i think the problem with the vista 32 bit computer is simpular to my desktop problem. when the computer is looking for a driver to install it wants a .inf file and the supplied drivers are .dll files.
choose / update driver - browse my computer for device drivers - let me pick from list of drivers.. show all [click next] then select "have disk" browse to folder w htc diag driver, select driver....that's it.
here's x86 & x64 diag drivers
you are using the drivers from the HTC website correct?
just in case : http://member.america.htc.com/download/Driver/HTC EVO (Sprint)/HTC_Sync_2.0.40.exe
did you install HTCSync?
I am using windows 7 pro x64 and my computer cannot install the driver when I check USB tethering on the OTA.
I know it is not my phone since my linux machine works fine with usb tethering.
However on my windows machine, it fails to install right away and my device manager has a "Android phone" that is not installed.
Is there something I am missing on my windows machine to not let it finish installing? If I remember correctly on my old setup it would install the NDIS remote driver, but that doesn't happen for me.
Any suggestions?
EDIT : Just tried roommate's computer which is also win7 pro x64 and it failed as well. Is windows 7 pro missing this NDIS driver? If so does anyone know a solution?
The link below is to PDAnet's download page. Just pick the one for you and it'll install the drivers.
If you don't know the bit size to your computer click start, right click my computer, properties, and it should say there.
The problem isnt PDAnet, I prefer not to use a 3rd party software when I can use the native 2.2 usb tethering. The problem is windows 7 pro not detecting the NDIS server driver. I confirmed it working for linux but I do not have a computer around me that uses other versions of Windows 7 besides pro
EDIT: Just tried my G1 on cm 6.1 and it found the NDIS driver for the G1.
Hmmm I'm running out of ideas, Ill try and find someone with windows 7 home or ultimate
mr_roboto said:
The problem isnt PDAnet, I prefer not to use a 3rd party software when I can use the native 2.2 usb tethering. The problem is windows 7 pro not detecting the NDIS server driver. I confirmed it working for linux but I do not have a computer around me that uses other versions of Windows 7 besides pro
EDIT: Just tried my G1 on cm 6.1 and it found the NDIS driver for the G1.
Hmmm I'm running out of ideas, Ill try and find someone with windows 7 home or ultimate
Click to expand...
Click to collapse
You don't have to use pda net, it just has the drivers you need in the software. Once you install pdanet, the drivers will allow win7 to recognize your phone. then you can uninstall pdanet. I had to do the same thing.
Chuckmoney said:
You don't have to use pda net, it just has the drivers you need in the software. Once you install pdanet, the drivers will allow win7 to recognize your phone. then you can uninstall pdanet. I had to do the same thing.
Click to expand...
Click to collapse
Thanks. I've been trying to tell people this over and over. No one listens.
Installed pdanet on my computer, which it also installed onto my phone but no luck. It still fails the driver install when i check usb tethering.
It did however install PDAnet's own "network driver", but device manager still sees "Android phone" as an unknown device when i check usb tethering. Not to be confused with the adb driver which I have already have up and running
I still have not had a chance to try another operating system besides linux :/
I have been searching for several hours, and I am absolutely unable to get ADB to recognize my phone using Windows XP 64 bit. I have uninstalled and re-installed the Unrevoked modified drivers several times to no avail. All I get is "Error: Device Not Found". Does anyone know a trick to getting ADB working on XP 64? I appreciate any and all help.
Thanks!
EVO HW 0003
HBOOT 2.10
MIKFROYO 4.4
Make sure the rom your using has adb functionality included/enabled in the rom.
And make sure usb debugging is enabled under settings/applications
Swyped from a galaxy far far away......
I have connected to the same phone with another computer. All settings are confirmed correct on the phone itself.
I know a trick, but I haven't tried it with the Evo or XP! I bet it works though. I used it to get my hero working with win7 last march, and it worked great.
install PDAnet.
It is a tethering program and has the ADB drivers, should set them up for you.
Also installing HTC sync is supposed to get the drivers working.
Thanks I will give that a shot and report back.
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Windows sucks and 64 bit XP is a pain in the ass. You need a usb driver or linux.
sixspeeder said:
PDANet didn't work but I found an HTC driver for 64 bit windows 7 that did the trick.
Thanks for your help.
Click to expand...
Click to collapse
can u post the driver.?
Here it is. Be sure to uninstall any other drivers. I used USBDeview to uninstall the old drivers. Extract this zip and use the driver inside for Android 1.0 when prompted. It will not show up as Android ADB in Device Manager (showed up as My HTC Phone or something on mine) but ADB connected immediately once I installed this driver.
I doubt that it will work
Works for me!
Been looking at this for two hours now...
Running 64-bit XP - Installed the drivers manually by connecting the device, then selecting not now.... navigated to the drivers, installed BOTH .ini files - not sure if was really two different drivers or not - restarted, reconnected and device showed up.
The name my device function says "Desire" but it seems to work so far (only one sync)