Related
I'm going crazy here. I'm good with all this type of stuff but nothing is working. I want to return my phone to stock so I can exchange it for a new one at verizon. I keep getting the waiting for device error in fastboot. I had this problem a lot with trying to unlock it too. I'm not sure how I ever got it to work. I've downloaded and installed the drivers multiple times and still nothing. Can someone help me figure out what I'm doing wrong please?
I'm using windows 7 64bit. The drivers aren't right in device manager.
The drivers are fishy in windows 7 64bit. Download PDA net to your computer. It will install drivers correctly. Sounds weird but it works.
Sent from my Galaxy Nexus using xda premium
I've certainly noticed that they are pretty messed up on Windows 7. Unfortunately I've already done that and it still doesn't work.
Reboot your computer and plug the phone in and let the drivers try to install automatically, worked for me.
So I installed the driver a different way and it worked fine this time. I'm not really sure why I never tried that way before or why that way worked differently but it did! Thanks for the suggestions.
In what way did you install it? I'm having the same problem and it would be nice for search purposes.
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
cancerouspete said:
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
Click to expand...
Click to collapse
That is also what I did that finally worked.
cancerouspete said:
i had issues with drivers on win7 64x, first, it would take for ever once the phone was plugged in, for windows to initially auto-install the drivers (after installing the ones from samsung)....a very long time. but, even after 3/4 of it installed correctly, i hadn't noticed that the Android 1.0 drivers didn't install at all. If you goto control panel->system->device manager, see if there is an alert next to 'Android', if so, open it, choose to manually install the drivers, but don't select a location on your hd, use the list of available drivers already on the computer, find 'samsung', and select the drivers that come up (again, had to download samsung drivers from their site and install that First)
this fixed the issue for me. and nothing like a good ol' reboot too to fix random windows issues : )
Click to expand...
Click to collapse
thank you!
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5
Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...
Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done
I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?
i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.
Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?
Solution:
If you were like me, you couldn't get ADB working no matter what you did with the drivers. As it turns out, I was plugging it into a USB 3 port on my motherboard. I have the USB 3 drivers installed, but there seems to be an adb issue with USB 3 ports. be warned, my issue is now fixed (I probably don't even need them bootleg drivers either). Thank You XDA.
Alright, so I just picked up a Galaxy Nexus (coming from Thunderbolt) today only to find out that my sdk will not detect my phone in adb devices. Now, I have the Thunderbolt and Eris working fine with it, but the NExus seems a little stubborn. Here are the steps I have taken:
1. Plug in phone, wait for win7 (x64) to install all the drivers... Success
1a. MTP and PTP both installed, using MTP for the rest.
2. Turn on debugging on my phone one more driver... Success
3. Went to the GNex Samsung support page to download and install that driver... Success
4. Go into Device Manager, everything is A-OK, drivers all happy
5. Open up my sdk prompt and type adb devices and 1 device is found, offline
6. Type it in again, nothing, maybe a glitch?
So there is nothing wrong in Device Manager, no Windows Updates, SDK works fine, but no device under adb devices. This is honestly the strangest thing ever.
If you have any special instructions regarding drivers, please be specific, stating "update your driver" doesn't really help.
Oh, and this is my first post I believe.
Update your drivers :laugh:
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it.
Srsly though...
If that doesn't work...try the PDAnet option.
My sig has a link.
Install PADnet and plug your phone in.
Then check that the new driver is the one in use.
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
efrant said:
@ OP, did you restart your PC after installing the drivers? If not, that may cause an issue. As well, you could always restart the ADB daemon. Type:
adb kill-server
adb start-server
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Noob question, but how do I install those drivers?
epicrevolt said:
Noob question, but how do I install those drivers?
Click to expand...
Click to collapse
Is that a joke?
efrant said:
[snip]
As for drivers, I personally would not recommend using any package that installs crapware other software along with the driver (such as the PDA drivers). Chance are if the package comes with an .exe extension, it contains other software. 1wayjonny has packaged the driver by itself here. Those are clean drivers with nothing extra to cause any issues. I recommend those, but (as with anything that works well) you need to manually install it, i.e., right-click on the device listed in Device Manager and select update, and browse to the location where you unzipped the driver. This needs to be done TWICE: once when your device is booted in fastboot mode, and once when booted normally.
Click to expand...
Click to collapse
Alright, so I have done the following:
Uninstalled all Samsung Drivers through Device Manager
Unplugged phone
uninstalled those official Samsung drivers for the GNex (available for download on their site)
Plug phone back in, both MTP and Nexus unknown
install the 1wayjonny driver... Success (It's now under Android Device in Device Manager)
adb still doesn't work... f*ck
reboot phone into fastboot (vol +/- & power)
install 1wayjonny driver... success
fastboot device recognized by 'fastboot devices' and commads work.
I believe the issue is with the MTP device as it is not recognized so therefore I can't access the phone storage. So far the only way I can get MTP working is by using the official Samsung driver, but that overrides the ADB driver by 1wayjonny (no way around it, even through uninstallation and choosing the 1wayjonny driver, Samsung one is more 'recent').
In the attachment you can see that the MTP device has no driver and therefore is unavailable.
Thank you so much for the help so far.
UPDATE: MTP Driver downloaded through Windows Update, divice still not showing up in adb. Actually when I first run adb devices after kill-server it finds the device as offline, but as soon as I type 'adb devices' again, it's gone. poof.
Hello,
I have searched the forums and Google, and was not able to find anyone else with this issue, so here I am.
I'm on Windows 7 x64 with a stock Canadian Galaxy Nexus 4.0.1 (yakjuux.)
I am trying to install GNex Toolkit and am unable to get past the first step. No matter what I try to do, any time I plug in the phone, it installs the default drivers.
Device installation settings are set to "never install drivers from Win Update." Phone is in development mode, I have removed Google Nexus from my devices (and checked the "delete drivers" box, though it doesn't even appear anymore), there is nothing for Samsung in Programs and Features, I have used USBDeview and there is nothing for Samsung/Nexus. I've tried using PDANet to no avail (I get error 103). I tried using "uninstall drivers" with GNTK, no dice (it seems to just remove a registry entry).
Any other ideas on how to make my PC install the drivers I want and not the default ones?
Thanks.
Read part A of this post.
efrant said:
Read part A of this post.
Click to expand...
Click to collapse
I have read that entire post and Bourne-nolonger's guide. Instead of showing up as "Android 1.0" device in Device Manager, my phone always shows up as Galaxy Nexus, with no yellow triangles or any other issues. (Yes, developer mode is enabled, and it seems to make no difference to how my computer responds.)
From Bourne-nolonger's guide:
"As soon as you enable this Windows will pick up a new device and it will attempt to install a driver - this will fail (or hopefully it will)." - mine never fails, it always installs drivers from somewhere. When I attempt to install new drivers to the Google Nexus device using UNK 0.7, Windows tells me that I already have the newest drivers.
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Scarf Face said:
[snip]
Should I be restarting my PC after every install/uninstall of drivers? That's the only thing I can think of....
Click to expand...
Click to collapse
Absolutely.
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
edit: tried doing the same in fastboot mode; the Device Manager recognized it as Fastboot mode, but did not let me install the proper drivers, saying that I already have the newest ones.
Scarf Face said:
Here is the sequence I followed:
- phone plugged in
- USB debug mode on
- uninstall phone from Device Manager
- USB debug mode off
- uninstall phone from Device Manager
- reboot
- reconnect phone, it installs with no problems
- enable USB debug mode while plugged in
- phone installs again, exactly like the previous time, with Galaxy Nexus in Portable Devices
So it appears my computer doesn't care if it is in USB debug mode or not. It sees them as two separate devices/states of device, but installs the same drivers for both.
Click to expand...
Click to collapse
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
efrant said:
This is what I would do:
1) Unplug your device from your PC.
2) Go into Device Manager and in the View menu at the top, select show hidden devices.
3) Uninstall every driver related to the GNex/Samsung/Android/etc.
4) Reboot your PC.
5) Make sure your Device Installation settings are set to never download drivers from Windows Update (as per bourne-nolonger's post).
6) Make sure USB Debugging is enabled in your GNex's settings.
7) Plug your GNex into your PC.
8) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
9) Reboot your device in fastboot mode.
10) In device manager you should see Android 1.0 with a yellow "!". Right-click on that and update the driver from where you downloaded 1wayjonny's driver.
Click to expand...
Click to collapse
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Scarf Face said:
Done, with no luck: instead of Android 1.0, I get a normal GNex install; with fastboot I did get it to show Android 1.0, and installed Samsung Galaxy Nexus Fastboot Interface using the downloaded drivers.
When I am uninstalling GNex from Device Manager, it never asks me to delete the driver as well; it asked me once and I can't get it to do that again. With fastboot, it did ask me, and that seems to be the only difference in the process.
Click to expand...
Click to collapse
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
At least you got the fastboot driver installed properly.
I'm out of ideas for the ADB driver though.
Click to expand...
Click to collapse
Seems to be a problem with my PC, so I will try it with a different machine. Thanks for your help!
Ignore this. Wrong thread.
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: