I was able to install the ADB and fastboot drivers for my Galaxy Nexus no problem (using both manually installed INF files and device manager, an the wugfresh toolkit), but when I do the same thing with the N72013, it just never recognizes my device in CMD or with the wugfresh ADB/fastboot test
Any idea what's happening here? I've tried in both Windows 7 and Windows 8
I've used the Google USB driver from the Android SDK, open SDK Manager and scroll to the bottom, check it to install.
- Sent from my Galaxy S3
Related
i installed the sdk on my windows machine and set the path. when i put adb in it does the same thing as in the tutorial so i am assuming I did it all right. problem is my computer does not recognize my phone when I am in fastboot mode. i have installed the drivers 3 different times but when i am in fastboot it says i need the android 1.0 drivers and it cant find them. I am trying to lock my bootloader and using the command fastboot oem lock and it just says waiting for device. I guess i need to know how to get my vista machine to recognize the phone or try to do this all on my mac running leopard which is pretty confusing to me. any help will be apreciated
Drivers need to be I stalled TWICE: once when your device is booted normally and once when booted in fastboot mode. Use 1wayjonny's universal drivers in the Dev section. When you see the android 1.0, right-click on it and update it manually with the driver.
Sent from my Galaxy Nexus using Tapatalk 2
I need help install android driver on windows 8. I put phone into bootloder and a pop in windows says usb devices not recognized. in device manager, there is item called android 1.0. I used toolkit 9.1 install driver, it only has option for windows 7. the result says the resource loader cache doesn't have loaded MUI entry. I downloaded naked driver 0.7, install from device manager, I get error says 'windows encountered error install the driver' Samsung galaxy nexus bootloader interface.
what should I do ?
citrix80 said:
I need help install android driver on windows 8. I put phone into bootloder and a pop in windows says usb devices not recognized. in device manager, there is item called android 1.0. I used toolkit 9.1 install driver, it only has option for windows 7. the result says the resource loader cache doesn't have loaded MUI entry. I downloaded naked driver 0.7, install from device manager, I get error says 'windows encountered error install the driver' Samsung galaxy nexus bootloader interface.
what should I do ?
Click to expand...
Click to collapse
Wrong section, Your question should be in Q&A.
Download Android SDK to install Google USB driver,
citrix80 said:
I need help install android driver on windows 8. I put phone into bootloder and a pop in windows says usb devices not recognized. in device manager, there is item called android 1.0. I used toolkit 9.1 install driver, it only has option for windows 7. the result says the resource loader cache doesn't have loaded MUI entry. I downloaded naked driver 0.7, install from device manager, I get error says 'windows encountered error install the driver' Samsung galaxy nexus bootloader interface.
what should I do ?
Click to expand...
Click to collapse
i use these drivers.. http://forum.xda-developers.com/showthread.php?t=1379875
PS- next time post in the correct section
I had the same issue with Win8.
If u select the manual driver option within the toolkit there is a link to pdanet (or something similar).
I downloaded and installed that (with nexus disconnected), it looked like the installer failed but the driver must have stuck because the next time I connected via fastboot it had the correct driver.
Hope that helps
Sent from my Galaxy Nexus using xda premium
On a different thread, which is basically the same as this one
cdexsw said:
Another post about this topic has already exists.....
forum.xda-developers.com/showthread.php?t=1959203
But I manually installed the Samsung drivers from their site and it works great with Windows 8..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
"The toolkit only has windows 7"
And because of that, you dont know what to do/to try. Just great.
Remove all drivers, reboot. Boot Nexus to bootloader, connect usb, go to device manager, manually update the driver by right click on android 1.0 or whatever the device name is, choose the driver that you previously extracted (naked drivers). Reboot. Should work.
// offtopic : windows 8 has got to be the worst windows yet.
Sent from my i9250
I have installed android SDK and google USB driver is installed. I also downloaded naked driver 0.7 and manually install driver from device manger item called android 1.0, choose folder from naked driver. still get the same error.
Uninstall all drivers, try the ones in the samsung website for windows 8.
Jeez, you need help with drivers go to a windows forum, i'm sure it exists such a thing and google knows about it.
Sent from my i9250
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
rbmako69 said:
I've been trying to access my GNex in fastboot mode, but my computer doesn't recognize it when it is in fastboot. I have tried to install the samsung adb drivers, but not matter what I try, I cannot get my computer to connect using the adb when the device is in fastboot. Any help would be appreciated.
I am running window 7 x64 btw.
EDIT: When my device is connected and I am not in fastboot mode, i am getting the "SAMSUNG Android ADB Interface" listed in device manager. So I am assuming I have the driver installed correctly.
EDIT 2: When I use
Code:
adb reboot bootloader
the device goes from recognized to Android 1.0, and if I try to
Code:
fastboot oem unlock
I get
Code:
<waiting for device>
Click to expand...
Click to collapse
After 'adb reboot bootloader', and device being recognized as "Android 1.0", just manually update the driver: its the same driver that you used for adb. Windows is dumb.
Use search or browse the forums, read the stickies, this has been covered over and over again.
Sent from my i9250
If all else fails get mskips galaxy nexus toolkit v10.x, see xda thread or google skipsoft, and let it sort out drivers and adb, it has easy options and a good help section, should get the job done.
Btw if you are having driver issues you should try the driver download pack from samsung official website's manuals and downloads, its a tad under 30mb, run it then reboot computer then plug in gnex and any missing drivers should auto install, be patient, windows is a retard so it may take a coupla minutes
sent via xda premium from starkissed noozxoide maguro gnex paranoid beta9.5
This worked for me:
rootzwiki -> Google/Nexus Devices -> Galaxy Nexus -> "Galaxy Nexus Root Procedure - (broken) ADB Method Dont USE" -> page 3, second to last post on the page (by litso):
"EDIT: Scratch that, was able to use the PDANet drivers. Install PDA Net, reboot into bootloader, open device manager, manually select the directory "C:\Program Files (x86)\PdaNet for Android\usbwin". Fastboot will then recognize the device and allow you to unlock."
I can't post a link because I am a 'new user' due to low number of posts, but that is the path to your solution. I literally just went through this yesterday.
It's basically what bk201doesntexist said in the above post. I used the pdanet driver, but I'm sure the normal Samsung driver should work.
I installed Unified Toolkit V 7 on my windows 7 operating system. The installation went okay. I started Toolkit and downloaded and installed the drivers for my T-mobile Galaxy S 3. The drivers installed okay. When I looked at my devices in windows, it show my Samsung driver, an icon SGH-T999. However, when I use Unified Toolkit to root my phone, I noticed that the driver icons goes off and on only when I put the cell into the debugging mode. As a result, Toolkit fails to continue and root my phone. The Driver icon goes off and on, until I take it out of the debugging mode. I tried rebooting my computer and cell. I also tried reinstalling the drivers. Please help!
Ronnie
My friend downloaded and installed the SDK package, and added the environmental variables. The drivers appear to be installed, but the device won't show up under "ADB devices". He is using Wug's Toolkit and went through all the steps, but ADB still won't recognize his device. Only other thing I can think of is to install PDANet. What do you think? Is it still necessary to download the java development kit?
He is using Windows 7. I remember having driver issues as well, I just can't remember how I fixed it.