Database Develop

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.

[Q] PC won't mount Nook/SD card

I don't know what happened but neither my Win7 x64 nor my Win7 x32 machines will mount my disks on the NC.
I am rooted with market access and I think it was working after I ran the "auto config script" but, not sure?
When I plug in to USB port the PC's load the drivers correctly and I see it in "adb devices" but the Nook never goes into USB MODE and no disks show in Explorer?
Any help on this before I do a full reset would be appreciated.

Try this:
http://forum.xda-developers.com/showthread.php?t=865345&highlight=usb

Thanks! moving to that thread

[Q] Need a little help with ADB on honeycomb

Hey guys, Im sure this is on here, I just cant seem to find it. Im running HC v4 on a SD card and when I try to ADB into it to install the market ADB doesnt see the device. I have usb debugging turned on, and ADB worked on my stock rom. Any suggestions?

Search for the nook color usb drivers on google. That worked for me at the following thread here on XDA: "[SCRIPT] Nook Color USB Drivers and ADB Setup (WinXP&7)"

I just worked through this the other day in my honeycomb .03 rooted nook. Follow the detailed directions on nookdevs (search "nookdevs: nook usb drivers"). Make sure you are admin on a windows PC while you do this. One other detail is to make sure to install the honeycomb labeled items in the SDK tool. You may not need them but they are in there so you might as well.

Are drivers always the cluprit?
I've been having similar problems with ADB not seeing my Nook. I did root it (Autonooter 3.0) and verified that USB Debugging shows to be on...and then downloaded the ADB set I found on XDA-Dev that had the full zip (adb and all) and another with just the USB drivers. But issuing the ADB command to list the devices found it still shows nothing in the list.
Are the right Nook USB drivers always the problem, since that seems to be the one thing everyone suggests trying/changing?
My ADB install never did try to use Windows Update to search for drivers (which we were warned about), and just to be safe I reran the second file to reinstall just the drivers. But at this point I'm at a loss what to try. So if it's invariably a problem with the USB drivers, well, I'm looking for pointers on a next step.
Thanks,
JTT

I am having this issue too, but USB drivers for Windows can't possibly apply as I'm running Snow Leopard (Mac OS X 10.6).
I'm guessing it has something to do with the version of ADB I'm running but I just did a fresh install of the SDK release 10, so I doubt that that is it too unless there is a particular ADB I need for Honeycomb?
Any help would be appreciated.

Guys try the same over wifi. Linky

try going into cwm recovery, go to "mounts and backups", and click the first option "mount system". then plug in the NC and, in a command prompt on the computer/laptop, kill the server, restart the server and look for devices again. also, make sure no other adb devices are connected to your computer/laptop (i.e. your phone)
i followed the directions on nook devs (mentioned above by bike4food) and all was like it said it should be by the end. unfortunately, the laptop still wasn't recognizing my NC. when i mounted the system like i described above, it recognized it.
good luck!

[Q] Whats causing my cappy to freeze windows 7?

Just made the switch from ubuntu 10.10 to windows 7, didnt have issues using my cappy as a mass storage device on ubuntu
On win7 x64 if I try to transfer a file thats just more than a few mb's either from the cappy to the pc or vice versa, the transfer just gets stuck, the loading bar is flashing but it doesnt get anywhere. I have to unplug my phone from the computer in order for it to go away, this causes windows explorer(not the internet browser) to restart as well.
-my other usb devices work without a problem
-have tried all six usb ports on my computer, same thing
-even weirder, i reformatted, installed win7 x86 just to see, transfers work fine on it. Reformatted again and installed x64 with fingers crossed, transfers didnt work on it again.
-I have tried transferring files with no windows updates installed on x64 as well as all updates installed, file transfers still get stuck both ways.
-im using the x64 captivate drivers from the odin3 thread on xda. running andromeda3 ROM.
anyone know what this could possibly be?

JBLogic said:
Just made the switch from ubuntu 10.10 to windows 7, didnt have issues using my cappy as a mass storage device on ubuntu
On win7 x64 if I try to transfer a file thats just more than a few mb's either from the cappy to the pc or vice versa, the transfer just gets stuck, the loading bar is flashing but it doesnt get anywhere. I have to unplug my phone from the computer in order for it to go away, this causes windows explorer(not the internet browser) to restart as well.
-my other usb devices work without a problem
-have tried all six usb ports on my computer, same thing
-even weirder, i reformatted, installed win7 x86 just to see, transfers work fine on it. Reformatted again and installed x64 with fingers crossed, transfers didnt work on it again.
-I have tried transferring files with no windows updates installed on x64 as well as all updates installed, file transfers still get stuck both ways.
-im using the x64 captivate drivers from the odin3 thread on xda. running andromeda3 ROM.
anyone know what this could possibly be?
Click to expand...
Click to collapse
sounds like bad drivers from samsung or windows is not using the newest driver version, maybe downloading drivers from samsung and manually installing would help
32 bit version of windows will have different drivers

I installed .net 4 and that seems to have fixed my problem, if that makes any sense.

makes sense. i keep forgetting about that but it is something you should have for alot of things in windows, thought it was one of the required things for adb and odin as well. not sure though

JBLogic said:
Just made the switch from ubuntu 10.10 to windows 7
Click to expand...
Click to collapse
I'm lucky enough to have a roomate with a dual boot ubuntu/windows so I can keep my Ubuntu and borrow his windows machine when I need it. Definately sounds like driver/ .net 4 issues though.