Discussion in 'Samsung Galaxy Nexus' started by dezymond, Jan 21, 2012.
I wouldn't think that matters. What version of Windows are you using?
Windows 7 Ultimate. Maybe I need to install all the updates first? I literally just got done reformatting the minute I posted earlier and didn't install any updates.
I don't think this will help since you're on Win7 but...I had a seemingly similar problem getting my XP work computer to recognize my phone. That Galaxy Nexus box would pop up and then it would fail to find drivers. Tried to manually install every driver I could find with no luck. Ended up Google searching the error message that it gave me and found that someone had got around it by updating Media Player. Seemed crazy to me but I was a version behind on Media Player. Updated it and boom, found my Nexus immediately. May as well run the updates and see if that helps.
Hmmm might help.
I just updated Windows Media Player after a restart, hopefully that helps....Report back in a bit
edit: Yeah didn't work. Maybe I'll install all the windows updates and just try it again. This is getting really frustrating....about to do plan B and just use the market tool for touch CWM.
edit 2: It does say "List of devices attached" when I put in the command adb devices, but nothing shows up. "Galaxy" driver still can't be found and installed, but "Galaxy Nexus" installs fine. In 'Device Manager" Android Phone doesn't show up, but "Galaxy" does, but won't let me update the driver.
Good news FINALLY!
Looks like it's working. When I type in adb device a serial number shows up. Seems like I finally got it working, thanks bhfd for Wug's method. Now I gotta find the touch version of CWM and flash it. It should just overwrite the current CWM I have right?
Does your PC recognize your phone as mass storage? You might try the manual method I linked earlier. The SDK Tools exe file installs the ADB driver somewhere along the way. It probably isn't the same one that your phone is trying to install automatically. You could also try to seek Wug's advice if you're still trying to use his tool. He's always good about troubleshooting within his thread.
Awesome! Yeah it will just overwrite your current recovery. Does Wug's tool automate flashing of individual components? Like just a recovery?
I'm not sure to be honest.
This should work right?: Install Touch Based ClockworkMod Recovery On Galaxy Nexus [How To]
Yep that's exactly how I've done it. I just set up the SDK Tools manually rather than with Wug's toolkit but if ADB and fasboot see your device then it should be all good.
Alright. Well I did all those steps and did the test recovery and it's been stuck at <waiting for device> for awhile. In fastboot mode and no button inputs work. Been about 5 minutes? Great new problem
That's another common one. Mujibar and I both ran into that. Installing the PDA Net drivers is supposed to fix it. The ones listed in that unlockr.com guide I linked earlier worked for me, and Muji got his from XDA somewhere.
I'll give PDAnet a shot then.
edit: After installing PDAnet and I connect while in fastboot it now asks for Android 1.0 , but it doesn't properly install. When I connect while the phone is booted up it's connected as SAMSUNG Android phone and adb recognizes the device. For the record I had to use the Samsung Kies method to get the right drivers...
you need the clean samsung drivers dont just install the EXE since the drivers wont install correctly. Let me find you link and I will edit this post with link
[GNex TOOLKIT V4.1] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH MORE [GSM] - xda-developersr
[ADB/FB/APX Driver] Universal Naked Driver Beta 0.5 - xda-developers
So at this point I should uninstall the current drivers I guess.
yes, and I edited the post.. I used the second link to fix the driver issue the 1st oone should be useful as well
It's still definitely a driver issue. I didn't uninstall anything when I ran the PDANet exe. Where did you get PDA Net? I know the one in the unlockr.com guide fixed my waiting for device issue but didn't fix Mujibar's. He ran down a different version somewhere. Maybe what King has will work too. These things are so picky about drivers.
Got PDAnet from the site you provided. Guess it's not good anymore? I would imagine that since I got adb working with the Samsung Kies drivers, that's where the conflict is. I'm going to try 713King's drivers that he linked. Hopefully that works.
Drivers are pickier than toddlers:frown:
Yea I installed the whole Pdanet crap and nothing worked until I tried the second link and used the clean driver and computer recognized device every time
Would the drivers in the toolkit be the same as the "universal naked" drivers?
Samsung Drivers.zip here are the naked drivers if you want, I just uploaded them since megaupload is down
Separate names with a comma.