Failed to Connect to Server - TouchPad Q&A, Help & Troubleshooting

Keep getting this message in Command Prompt when trying to install CM9 on my touchpad.
Yes I have cd to the right directory in command prompt
Yes it does show up in Device manager as Palm Novacom (bootie) under the tab Palm Novacom Modules.
Yes drivers are installed
Yes I did re install all drivers after removing them.
Tried different USB cables
Will not show up in Adb either.
My computer does recognize it, in both WebOS Recovery mode, and in Mass storage mode.
What does this message mean? Am I missing something?
Appreciate any help.
Thank you.
Edit: Solved!
Thanks to Scifan on IRC for his help!

I've got the same exact issue... i have a feeling it has something to do with win 7 64bit, im seeing alot of people with the same issue with that setup.

Reinstall novacom using this this installer
http://universal-novacom-installer.googlecode.com/files/UniversalNovacomInstaller.jar
Than in your type this (services.msc) in your windows start bar. Look for Palm Novacom in the services.
If its not there, try installing novacom drivers again while looking at the services menu. It worked for me like that, not sure why. But this was my problem.
I had reinstalled novecom drivers a few times trying to get it to work, and that some how did the trick for me. Was pretty weird.
My net book is running windows 7 32bit. Dont know if 64bit is going to have problems as I cannot test.
Good luck!

Related

USB Tethering: How ?

The cyanogen rom 4.2.3 has USB tethering support, but I can not get it to work, mainly because of missing information/documentation.
In 'settings' 'wireless controls' there is a nice 'Internet tethering' option to switch it on. When I switch that on then my Windows XP PC shows an unknown device 'Andriod Phone' and would like to install drivers for it. Where can I get these drivers from ?
Markus
I would also like to know how the usb tethering works for a mac as well. Didnt find any information on that. Thanks in advance.
You may need to get the drivers from the Android SDK, but with regards to USB tethering, your phone should be recognised as an NDIS based network device and installed automatically by Windows. Not sure about XP, but it installs automatically on Vista and 7
Under Ubuntu Linux (from an end-user perspective), when a G1 is connected with USB tethering enabled, network manager connects as if the phone were a standard, ethernet connection.
Shane2 said:
You may need to get the drivers from the Android SDK, but with regards to USB tethering, your phone should be recognised as an NDIS based network device and installed automatically by Windows. Not sure about XP, but it installs automatically on Vista and 7
Click to expand...
Click to collapse
I have the Android SDK (1.6r1) and I point the driver install wizard at the usb_driver directory when he wants to install the device. Despite this the 'Found new Hardware' Wizard come up with 'Cannot install this Hardware'.
Markus
markusb said:
I have the Android SDK (1.6r1) and I point the driver install wizard at the usb_driver directory when he wants to install the device. Despite this the 'Found new Hardware' Wizard come up with 'Cannot install this Hardware'.
Markus
Click to expand...
Click to collapse
For xp you have to install drivers from htc sync software. Just google 'htc sync'. Should have been asked in q&a.
Nothing happens on Mac OS X 10.5.8 neither on 10.6.1
dumfuq said:
For xp you have to install drivers from htc sync software. Just google 'htc sync'. Should have been asked in q&a.
Click to expand...
Click to collapse
Isnt this Q&A? but I think this is it.... http://handheld.softpedia.com/progDownload/HTC-Sync-Download-81096.html
Im trying to get this to work also
I couldn't get it to work on my Windows XP SP2 computer at work. I get a code 10.
Guys, don't forget to use search! I've seen these issues brought up in at least 3 or 4 threads, and tons of posts.
bassderek said:
If you're running windows XP the driver isn't included on your computer. Some people have installed HTC Sync to get the drivers, personally I got them from this post:
http://forum.xda-developers.com/showthread.php?t=445436
I can confirm that the driver from that post works, I am using tethering with my laptop right now to write this post!
Click to expand...
Click to collapse
bassderek said:
Guys, don't forget to use search! I've seen these issues brought up in at least 3 or 4 threads, and tons of posts.
Click to expand...
Click to collapse
The search doesnt always give you what your lookin for if you dont word it a certain way man................
I think im gonna need a step by step.... I got the file... the computer recognizes the device.... But it doesn't register as a connection....
To everyone that is having problems tethering:
I was having the same issues. At first I wasn't able to get it to install, and then it would just keep saying the device couldn't start.
i found a very simple solution. I went into device manager, uninstalled all of my usb ports, and restarted my computer.
When it restarted, it automatically installed the usb drivers, and the tethering has worked ever since.
I could not get this to work either, finally after 3 days of messing with this on my work pc, I got it to work. First download htc sync from here http://www.htc.com/uk/SupportViewNews.aspx?dl_id=631&news_id=270 then unzip and install to your pc. Next tick on the option to usb tether while the phone is plugged in. It will say found Android phone Sdk or something like that. I did this on my xp pc at work that had no htc drivers previously installed. Next I went to my device manager and under network adapters you will see the yellow exclamation point, right click on that and update driver, 1st install from a specific location, 2nd Don't search I will choose driver to install. 3rd Have disk, 4th browse to C/program files/htc/htc driver/driver files/xp_86x then hit open and click ok. It might give a "stop warning" ignore it and continue. When its done installing you should be ready to go.....
badaphooko01 said:
I could not get this to work either, finally after 3 days of messing with this on my work pc, I got it to work. First download htc sync from here http://www.htc.com/uk/SupportViewNews.aspx?dl_id=631&news_id=270 then unzip and install to your pc. Next tick on the option to usb tether while the phone is plugged in. It will say found Android phone Sdk or something like that. I did this on my xp pc at work that had no htc drivers previously installed. Next I went to my device manager and under network adapters you will see the yellow exclamation point, right click on that and update driver, 1st install from a specific location, 2nd Don't search I will choose driver to install. 3rd Have disk, 4th browse to C/program files/htc/htc driver/driver files/xp_86x then hit open and click ok. It might give a "stop warning" ignore it and continue. When its done installing you should be ready to go.....
Click to expand...
Click to collapse
I'm so frustrated with this whole process. I've done every step you've outlined, and I still get a code 10 - cannot start the driver. And I still don't have USB tethering. What am I doing wrong?
nmw407 said:
I'm so frustrated with this whole process. I've done every step you've outlined, and I still get a code 10 - cannot start the driver. And I still don't have USB tethering. What am I doing wrong?
Click to expand...
Click to collapse
I had the same problem with Windows XP SP2. I installed SP3 and it started working flawlessly. What are you using?
Binary100100 said:
I had the same problem with Windows XP SP2. I installed SP3 and it started working flawlessly. What are you using?
Click to expand...
Click to collapse
eeepc 901 nlited XP SP2.
I'll try and push SP3 and retry again tonight. Thanks for the heads up.
nmw407 said:
eeepc 901 nlited XP SP2.
I'll try and push SP3 and retry again tonight. Thanks for the heads up.
Click to expand...
Click to collapse
That's your problem then. Yeah update to sp3 and you will be good. I promise.
I'm running into the same tethering trouble, but appear to meet all the criteria mentioned in this thread and other threads i've come across. the bottom line is i can connect with ADB access and mount my phone's SD card via the usb connection, but tethering doesn't work under several versions of Cyanogen on my laptop. currently I have CM 4.2.12.2 on my rooted Dream. I have windows SP3 installed (installed it twice because problem persisted). I've uninstalled all the USB ports per an above post, rebooted and plugged my phone in. The laptop reinstalls the USB ports, and finds the phone as an "ADB Interface" named "HTC Dream Composite ADB Interface". I can update the drivers with the google SDK USB drivers which makes the device an "Android Phone" named "Android Composite ADB Interface" instead. With either set of drivers installed, once I go to Settings on my phone and enable tethering, the device under windows goes away and instead i get yellow question mark "Other Devices" named Android Phone. I can try to force it to use the same USB drivers but it won't install them.
With tethering turned off, i can successfully type "adp devices" on my laptop console and see that my phone is there. once i turn tethering on, the same command shows no devices.
The Dream works with tethering just fine on my windows pc and shows up as a "Network adapter" named "Windows Mobile-based Internet Sharing Device".
My laptop is a compac presario in case that matters. what do i need to do on it to make tethering work?
just found the solution. a lot of posts were talking about installing microsoft active sync. sounded pointless considering it's an android phone, but it ends up being that the drivers for "windows mobile-based internet sharing device" are part of the active sync installation. i installed active sync, plugged in my phone, enabled tethering and then the laptop installed the correct drivers and it all worked without a hitch. hope this helps others!
hamx0r said:
just found the solution. a lot of posts were talking about installing microsoft active sync. sounded pointless considering it's an android phone, but it ends up being that the drivers for "windows mobile-based internet sharing device" are part of the active sync installation. i installed active sync, plugged in my phone, enabled tethering and then the laptop installed the correct drivers and it all worked without a hitch. hope this helps others!
Click to expand...
Click to collapse
+1
This is totally the problem. I spent hours trying different ways then finally googled it and came here

Lost ADB after installing HTC Sync 2.0.4

I can't seem to figure out what happened to my ADB driver. I installed HTC Sync to use USB tethering and found that ADB no longer worked. I checked the drivers and found that the ADB driver is missing. I uninstalled HTC sync and the driver, plugged in my phone and the phone automatically installs the driver for HTC Sync. Tried to perform "adb remount" and it gives me "error: device not found".
I am running Windows XP SP3 on my computer. Cyanogen 4.2.3.1 with the Buuf theme. If somebody could help me get ADB back I would appreciate it.
Anybody? Any Suggestions?
ccunningham83 said:
Anybody? Any Suggestions?
Click to expand...
Click to collapse
YOu have to reinstall the driver but don't let it choose the driver for you tell WIndows that you'll do it manually and select the win32 driver in the SDK tools.
That being said you aren't going to be able to use HTC Sync anymore.
Thanks for the reply. How can I manually install the driver? I uninstalled the HTC sync driver, plugged my phone in, and the driver automatically installs. It never gives me a chance to browse for a different driver. If there is some way I can force the driver to install without connecting the phone, that would probably do the trick. I would much rather have ADB than USB tethering anyway.
Nevermind. Next time I will google before I ask how to do something.
If anybody else has a similar problem, just google how to install drivers manually and manually install the ADB driver.

trouble with ADB

I've been following mrkite38's nice guide here:
http://forum.xda-developers.com/showpost.php?p=5096501&postcount=17
I understand it completely, and have done similiar operations before. However I cannot get my phone to popup in device manager in any form. I here the bell that tells you a device has been connected, but nothing ever shows up, no notification, nothing.
Any ideas? thanks guys
Is USB debugging enabled inside android?
mrkite38 said:
Is USB debugging enabled inside android?
Click to expand...
Click to collapse
Yes and also stay awake
I've never had any luck with ADB also. I'm running Win 7 64 bit. I've tried all types of things LOL
Reddog80p said:
I've never had any luck with ADB also. I'm running Win 7 64 bit. I've tried all types of things LOL
Click to expand...
Click to collapse
same - maybe it's win7 is the problem. I've had problems with it on winmo as well. I'll try my parents pc sometime (xp)
i cant get it to work right on vista either. never have.
does your device ever show up in device manager? I can't even do that...
berardi said:
does your device ever show up in device manager? I can't even do that...
Click to expand...
Click to collapse
I got it to work on win 7 64 bit. It was a pain, actually I only got it to work on my laptop and not my desktop both with win 7 64 bit.
So normally when you plug in the android phone, 2 things pop up in device manager as Android phone, however one of them always trys to load a driver of a disk drive (probably set up to transfer stuff) however whenever that device is enabled with the driver adb wont work. So what I had to do was, especially b/c win 7 is a bit odd for automatically installing any driver it want with out input from up I had to disable that.
Start run gpedit.msc
in there go to Admin Templates > system > Driver installation > Driver instillation restriction. Enable both "Allow admin to override device installation restriction policies" and "Prevent installation of devices not described by other policy settings"
Ok after doing that you want to get rid of the drivers it tried to put in, so in device manager uninstall them, also download and run usbdeview, and remove the HTC drivers from there too. Might have to restart?
Now the drivers i used for adb was from proxoid, there are 32 bit and 64-bit versions there for you and it seemed to work
So d/l that, plug you phone in and in device manager manually set the drivers, you know right click deceive, update drivers, let me choose, choose form list, have disk etc.
Now the only pain with this method is that when you plug in another device, you have to go to device manager and install the driver from there either by using windos update or manually. If you take off those policies we changed earlier, windows in its great wisdom will reinstall non-working drivers.
Like i said worked on 1 comp not the other.
Good luck.

nexus one Driver problem

Hey, i have had this problem for a bit now, but it is really starting to bug me.
I have a dual boot computer, one is fedora, the other windows 7. When i decided to root my nexus one, i did it through windows, so i got the SDK, installed the drivers and rooted the phone.
Some time later (after flashing and restoring from desire rom back to CM 5) my computer can no longer recognise the device properly Windows will say it fails to recognise the device (code 43), and will not let me re-install the drivers. Saying they are up to date even after i uninstall the drivers then re-install them.
I have given up on fedora too, since no command ever seems to work on fedora beyond yum install xxx. Trying to get "fastboot devices" in fedora brings up "command not found" or something to that effect.
I wouldn't be too worried, but not everything comes as an update.zip, and i would like to try out the undervolted kernel some time.
Note: i can still mount the SD card fine.
EDIT: i can Mount the SD on Fedora, but not windows.
Things you can try out:
1. Completely uninstall and remove the driver from the system and connect the phone and install the drive when prompted. (try in safe mode as well)
2. Try other USB ports.
3. Try turning off USB debug, connect the phone and then turn on USB debug.
4. Try on another PC and rule out any problem with ur phone.
5. Reinstall Windows!!!
Thanks for the suggestions, i tried everything there short of re-installing windows.
As soon as i plug in the device windows will bring up the error message, it will not call it a nexus one, an unknown device. Any attempt to install the new drivers and windows will say that better drivers are already installed.
I also figured out that it will not work on fedora because it is not configured, but the only guide to fastboot and linux i have found is for ubuntu, and some of the commands wont work on fedora.
I tried it on another computer, an XP, it would not install on there either, i tried to use my mums N1 afterwards to see if it would install, it didn't but there are a number of reasons why it may not.
Any other suggestions? or could someone point me to a fedora guide for fastboot?

[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S

Team,
For those of you having trouble finding drivers here are some links.
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
For Linux and Mac the Android SDK drivers should work fine.
The standard Samsung USB driver that PDAnet had listed for the Samsung Moment worked for me as well, will give these new ones a try on my other system.
thank you
I added a link to this thread in the sticky
EDIT: Nevermind the n00b question. I was able to get the drivers installed and I am good to go.
cant get my cpu to recognize my phone after installing drivers... im on windows 7 64 bit any ideas??
skater4690 said:
cant get my cpu to recognize my phone after installing drivers... im on windows 7 64 bit any ideas??
Click to expand...
Click to collapse
have the same problem. i'm on 7, 32bit
did you enable USB debugging?
Gunnman from Galaxy S
yes of course. first thing I did after I rooted
I'm drunk so bear with me. go into device manager and browse for the driver manually ,include subdir. point to programfiles\samsung.
if that don't work use the 64bit drivers on 32bit windows. don't run setup just browse to the extracted dir from the unknown device in device manager. it worked for me at work. good night
Gunnman from Galaxy S
since i had issues w/ the 32bit driver exe, i extracted it and zipped it up incase others have the same issue.
http://rapidshare.com/files/408470448/Samsung_Usb_Drivers_x32.zip
this thread should be stickied since W7 doesn't come with the drivers, it seems.
How exactly do you update the drivers with win7? It keeps saying my drivers are up to date but I still can't get adb to recognize my vibrant
Beast84 said:
How exactly do you update the drivers with win7? It keeps saying my drivers are up to date but I still can't get adb to recognize my vibrant
Click to expand...
Click to collapse
Anyone?? I can't get get adb to recognize my device for the life of me
Try both 32bit and 64 bit drivers. At work I have 32bit win7 and the 64bit drivers fixed it up. Dont run setup just go through device manager chosse the unknown device and point it to the 64bit driver directory and check include sundirs.
Try using correct drivers for your win version but turn the phone off, connect and then power up while connected....worked fine for me after messing with both lots of drivers first and no luck
Make sure you select "USB debugging" for ADB to work folks.
Where can I get the mac driver..i looked everywhere please help
this thread is legit!
thanks for all of your help so far guys.. BUT i still cannot get my laptop to sync up with the phone properly (win xp pro, sp3)...
I've downloaded and installed both drivers and the computer is recognizing the external drives, but they are showing as removable disks E: and F:. when i double click to open, it is telling me to insert a disk? i feel like i'm almost there, but there is somethign i'm missing!
usb is mounted and usb storage is off. usb debugging enabled.
any help would be appreciated.
Windows drivers issue
Have you tried mounting the drives. Same thing happened to me when you have it connected to the computer drop down the usb notification and mount. The your drives should be accessible.

Categories

Resources