Related
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
Did you ever find this out, I'm having the same problem.
Just install the SDK and it should work?
Sent from my HTC Desire HD using Tapatalk
yes the drivers are included in the android SDK from google website
I installed the pdanet software to get it recognized in the fastboot mode.
thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
You sir, are my hero!
Thanks alot
Easiest way is through installing PDAnet, that's what I did.
Sent from my Galaxy Nexus using XDA App
On Windows 7 you go to device manager and select
Updated driver > Browse my computer... > Let me select... > Show all > Have disk
And then browse to the inf file in the android-sdk-windows\extras\google\usb_driver folder.
It's a pain but it works perfectly.
or get a mac
appelflap said:
or get a mac
Click to expand...
Click to collapse
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Eoinoc said:
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Click to expand...
Click to collapse
Agree, although developing on a unix based machine (mac or linux) is so much faster.
gambiting said:
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
Click to expand...
Click to collapse
Worked perfectly, thank you!
Can somebody help me. I have everything installed but it won't recognize my device
Sent from my Galaxy Nexus using xda premium
I'm new and not allowed to post links
Go to the Samsung Homepage of your Country/Language, go to support -> download center, enter galaxy and use the autocompletion for galaxy nexus, then download the usb driver
was not working for me so I force the use of google usb driver from Android SDK by:
- opening windows device manager
- right click -> update driver on the Other devices : Galaxy(exclamation mark)
- Browse my computer option
- Let me pick from my computer option
- click next on the Show All Devices upper selection
- click Have Disk and browse toward your android-sdk\extras\google\usb_driver
- select Android ADB Interface, Next and finish with the Yes
adb devices command reply correctly
I've done the same and flash succesfully my Gnex in fastboot (once you're in bootloader the driver to update in device manager is Android 1.0).
Adding new lines in the android_winusb.inf file from the extras\google\usb_driver leads exactly to the same result.
As it's not a conventional method there might be some issues
mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
Just wanted to say thank you as this has resolved my issue. I had installed Android SDK which didnt help.
Edit: I had to install the driver to DeskNotifier application would work with my Galaxy Nexus. After installing, it did connect fine. Strangely though, as soon as I sent a test msg from my phone to the PC, my computer became extremely sluggish. I am now rebooting
USB driver still won't install
Neither the USB driver from Samsung nor Google will work on my Win7 machine with my Galaxy Nexus. I have the device plugged in and in recovery mode. The device shows up as a Galaxy Nexus on the device manager, but is unable to install either one.
Thanks for your help.
http://forum.xda-developers.com/showthread.php?t=1626895, part A. It seems the device should be booted normally to install the adb drivers.
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
picklz said:
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
Click to expand...
Click to collapse
im having similar issues...im stuck in "waiting for device" in the bootloader.
I'm having the same problem and nothing I've found helps. Since I really want to unlock the bootloader, and doing so wipes the device, I'm stuck not being able to do anything with the phone until I get this worked out
I had this problem when I was unlocking the bootloader. I kept playing around with it and reinstalled the drivers multiple time. I would uninstall the driver and install the driver when the phone was in bootloader mode (I believe).
Make sure the drivers you're setting it to are new.
http://dl.dropbox.com/u/4174784/usb_driver.zip were the drivers I used. These are for GSM model, not sure if they work for the CDMA/LTE version!
Alternatively, you can install PdaNet for drivers.
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Some people also had luck by installing the windows pdanet which installs drivers that should work too.
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks buddy!
Worked for me, I thought it was due to my HTC/Motorola device drivers, so uninstalled all of those and re-installed the Samsung...but these steps worked. Thank you again (I did also hit the thanks button too FYI!)!
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
It worked for me. Thanks!!
i have no idea why but it is just not working :/ in that last set of instuctions above...i dont even have android bootloader interface lol which is weird cause ADB is reading my phone just fine...but when in bootloader mode it just says waiting for device. Does anyone have the fastboot drivers?
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
That method didn't work for me either. I'm running windows XP professional and do not see 'Android Device' in the list of devices... any other ideas anyone?
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
RMarkwald said:
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
Click to expand...
Click to collapse
I did,
Tried the PDAnet method as well. Adb works fine. Once I get into the boot loader the device isn't recognized. I get the Android 1.0 install prompt and cant install it.
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks! FWIW, I had to uninstall the Samsung driver and use the Google USB driver to find the Android Bootloader Interface one... if others are having trouble, try that.
Hi everyone,
I'm currently trying to upgrade my phone from Yakjudv to Takju/JB. Unfortunately I've run into some issues, and as they are quite different from the questions in my original thread, I thought it best to start a new one. I do apologise if this was the wrong thing to do! I just thought that an answer to this may be helpful for others, as my searching for an answer is coming up blank.
Before I found XDA forums, I had downloaded and installed Wug's toolkit, and used it to manually install drivers for my phone. This led me to being able to find my phone's serial number when I load toolkits or run adb devices tools.
I then tried to backup my ROM using the method here: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239
Unfortunately, I got an error saying 'can't mount SD Card' (presumably because the GNex doesn't have an SD Card). Being worried about this, I thought it might be a driver based issue, so I tried to uninstall my drivers by:
1. uninstalling them from device manager (including deleting the driver software);
2. disabling downloads of drivers in windows; and
3. uninstalling all entries related to Galaxy Nexus, Google and Samsung in UDBview
I restarted, plugged my phone in, and the phone suddenly reinstalled, finding drivers on its own. It showed Galaxy Nexus and Samsung ADB device as being installed. When I tried to manually install universal drivers from here:http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 , I was told by my PC that up to date drivers were already installed.
I don't seem to be able to uninstall the drivers, no matter what I do. I have even tried to uninstall the drivers using Galaxy Nexus Toolkit (I'm trying to avoid using this, but thought it might do the job).
Is this a problem?
If so, is there anything I can do to uninstall the drivers properly?
Thank you so much in advance, everyone!
paul-g said:
Hi everyone,
I'm currently trying to upgrade my phone from Yakjudv to Takju/JB. Unfortunately I've run into some issues, and as they are quite different from the questions in my original thread, I thought it best to start a new one. I do apologise if this was the wrong thing to do! I just thought that an answer to this may be helpful for others, as my searching for an answer is coming up blank.
Before I found XDA forums, I had downloaded and installed Wug's toolkit, and used it to manually install drivers for my phone. This led me to being able to find my phone's serial number when I load toolkits or run adb devices tools.
I then tried to backup my ROM using the method here:
Unfortunately, I got an error saying 'can't mount SD Card' (presumably because the GNex doesn't have an SD Card). Being worried about this, I thought it might be a driver based issue, so I tried to uninstall my drivers by:
1. uninstalling them from device manager (including deleting the driver software);
2. disabling downloads of drivers in windows; and
3. uninstalling all entries related to Galaxy Nexus, Google and Samsung in UDBview
I restarted, plugged my phone in, and the phone suddenly reinstalled, finding drivers on its own. It showed Galaxy Nexus and Samsung ADB device as being installed. When I tried to manually install universal drivers from here: , I was told by my PC that up to date drivers were already installed.
I don't seem to be able to uninstall the drivers, no matter what I do. I have even tried to uninstall the drivers using Galaxy Nexus Toolkit (I'm trying to avoid using this, but thought it might do the job).
Is this a problem?
If so, is there anything I can do to uninstall the drivers properly?
Thank you so much in advance, everyone!
Click to expand...
Click to collapse
Drivers
cyanogenmod wiki said:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Select "android_winusb.inf
Click to expand...
Click to collapse
Google USBDeview, and download the application. When you run the program, make sure to right click and "run as administrator". This will show you all of the drivers installed on your computer. Delete anything that says "Samsung" "Galaxy" or "Nexus". This will give you a clean slate to start with.
lowandbehold said:
Google USBDeview, and download the application. When you run the program, make sure to right click and "run as administrator". This will show you all of the drivers installed on your computer. Delete anything that says "Samsung" "Galaxy" or "Nexus". This will give you a clean slate to start with.
Click to expand...
Click to collapse
Thanks for the advice. I have tried to do this, and uninstalled all of the Google/Samsung/Galaxy/Nexus options, but the minute I plug my phone in, it all just reinstalls!
Originally Posted by cyanogenmod wiki
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Select "android_winusb.inf
Click to expand...
Click to collapse
Thanks for this. I have used it to install the drivers for when in fastboot mode, and I forced installation for the Samsung ADB Device that showed up in my Device Manager.
Do I need to do anything for the driver for the "Galaxy Nexus" device?
Thanks so much!
Paul
Hello,
I've been able to use ADB to install and test apps that I'm writing under the stock ROM for my Epic, as well as under CM9 (and I think an early CM10, not sure about that though). After installing the 20130101 build of CM10.1 (keeping the included kernel), I am having issues trying to deploy and debug apps from my any of my computer to the phone (all of which previously worked). I've verified that Android Debugging is still enabled on my phone.
In the device manager on my computer, "SAMSUNG Android USB Modem" and "Unknown Device" are both showing the "problem" icon. I've tried uninstalling and reinstalling various versions of the Samsung USB drivers, I've tried a few versions of Kies, and even a few third-party tweaked USB drivers. It doesn't seem like anything wants to recognize my phone now that is running CM10.1 (or CM10.1 in addition to something peculiar with my installation).
Additionally, if I have USB debugging enabled on my phone, even if I enable USB mounting, the computer won't recognize the mount until I disable debugging mode on the phone. Once I do that, then the volume will appear on my computer. Previously, when ADB debugging in general worked, I wouldn't have to disable debugging to get the USB mass storage mounting to work.
These problems happened at once on all three of my computers that I've been using for Android development, so I'm fairly convinced these issues are directly related to the ROM I'm running. I've attempted to search the forum and Google for others that may have had this issue and what the resolution/work-around might be, but so far I've not found anything. Surely other people are using CM10.1 and developing apps, which makes be believe it could be something unusual with my installations, but I've tried full wipe without a data restore and it didn't seem to have any impact. I've also tried searching to see if there were special drivers needed for CM10.1, and didn't find anything with that either. I know reverting back to an earlier ROM is an option to get ADB working, but I'm really hoping to get ADB working with CM10.1.
Does anyone have any suggestions on what I can check/do to get USB debugging working on CM10.1 (epicmtd)?
Thank you very much for your time
--James
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
I had the same problem, tried absolutely everything I could to get it to work and couldn't... had to roll back to a tw rom to get it to work (not a fan of the HUGE battery drain on cm9)
Edit- I know this doesn't help you, just wanted to point out you're not the only one with this problem....
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
jeffreyjicha said:
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
flastnoles11 said:
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
Click to expand...
Click to collapse
I've tried this with my previous uninstall/reinstall driver attempts, but tried it again anyway.
Unfortunately, it didn't' seem to have a positive impact. It looks like it reinstalled the mass USB storage driver, but it did not reinstall any other drivers (like the modem driver) so I'm still not able to do anything with ADB.
Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Have you tried manually installing the drivers?
Here is the .exe that I used to install the drivers for my phone.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Have you tried manually installing the drivers?
Click to expand...
Click to collapse
Hello again. Yes. I've tried installing various versions of USB drivers floating around the net as well as Kies (after uninstalling and deleting current drivers to try to avoid conflicts). Other versions of Epic ROMs (Stock, CM9, etc.) worked with ADB using my installed drivers until I installed CM10.1 (maybe starting with CM10) on my Epic.
As an aside, using ADB requires some additional (special) drivers beyond the drivers required for mass storage support.
I'm hoping one of the CM10.1 developers will chime in with what they did and/or installed to have ADB working with CM10.1 on Windows 7.
Thanks!
--James
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
jeffreyjicha said:
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
Click to expand...
Click to collapse
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
No problem.
samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
Activating through developer options doesnt help? just go to about phone --> tap build number 7 times
I just went to device manager, uninstalled the failed USB device, and then plugged the phone back to the computer via USB.
Boom, just like that, all was well.
i tried everything and could not connect to my htc rezound (w/ CM10.1) thru adb. then i tried the following:
1. download the android adk from google (i can't post links)
2. connect phone thru usb
3. on your computer's adk download folder, navigate to sdk\platform-tools\
4. press shift + right click on the window, open command window here
5. type "adb devices" in the command window w/o the quotes
6. there should be a window pop up on ur phone asking for USB debugging permission. say OK.
7. type "adb devices" again and you should see ur phone connected thru adb.
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse
isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good: