I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
The issue I was having was due to the fact that I wasnt pressing Volume Up+Volume Down+Power, so I wasnt even in fastbook, but a screen similar to it
schwartzman93 said:
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
Click to expand...
Click to collapse
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
efrant said:
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
Click to expand...
Click to collapse
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
schwartzman93 said:
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
Click to expand...
Click to collapse
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
FastBoot Driver- Xperia Neo
efrant said:
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi,
I am using sony sricsson neo .587. I tried to connect my phone in fastboot mode. I connected in fastboot mode. I am not able to install drivers for that.
Steps I Followed
1. I updated google usb driver
2. Replaced "android_winusb.inf" file which is provided by Sony official
3. Connected phone in fastboot mode
4. It asked for drivers
5. I selected usb driver folder to install drivers
But It fails...
I am doing these all things on Windows 7 64 bit
Please help...
Related
Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!
Try with a different USB cable if you can.
I had the same issue (device not being found) using the cable that came with it, so I swapped it for the one that came with my Desire and it worked fine.
Worth a shot.
Cheers! I'll give it a try!
Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?
lexarjump said:
Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!
Click to expand...
Click to collapse
If you run "fastboot devices" and there's nothing found, then you need to install the fastboot drivers (these are not the same as the USB debug drivers from the zip).
I've found the easiest way to get the drivers is to install pdanet - as part of the installation process you install all needed drivers. You can then uninstall pdanet (or in my case, have the installer crash), leaving just the fastboot driver for you to carry on your rooting
lexarjump said:
Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?
Click to expand...
Click to collapse
mybe, you can try fastboot devices and check if the device is found.
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
Honestly, not willing to check this one after spending today setting up my device, and no custom recovery available yet.
But given it's a Nexus device, and noting the ease with which we can unlock, then I'd say it's a pretty surefire bet that relocking will be just as easy.
Thanks alot! It worked
I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?
rock7632 said:
I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?
Click to expand...
Click to collapse
I think PDAnet should be sufficient
Proyoyo said:
I think PDAnet should be sufficient
Click to expand...
Click to collapse
okay thanks
I tried all day yesterday to unlock bootloader with no success. I installed the latest sasmsung usb drivers for mobile (released on 31/10/2011). This allowed the PC to recognise the phone installing the drivers properly. But then starting the phone in recovery mode (power+up+down bottons) I get the android 1 not recognised in device manager.
I then saw this thread and decided to install pdanet 3.02 client on the pc. I couldn't complete that step as pdanet cannot see the phone.
I gave up in the end. If you manage to do it successfully could you please tell me the step you did?
I am going to try tonight on my mac as apparently on mac you do not have this drivers issue. Will post with my results.
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
By the way the latest samsung usb drivers can be found here:
http://forum.xda-developers.com/showthread.php?t=961956
---------- Post added at 11:39 AM ---------- Previous post was at 10:41 AM ----------
Forget my previous post.
Installing pdanet and saying no to install the usb drivers (as part of pdanet install) everything should be fine.
Done mine and working fine.
Thanks.
braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
yes
fastboot oem lock will lock it
Hey I seem to be having some troubles as well,
windows 7 recognizes it as an ADB device and when I use - adb reboot bootloader
it takes me to the fastboot screen that it should.
but once I'm there it doesn't recognize any fastboot devices.
And yes I have reinstalled the SDK, Samsung drivers, and Android ADB driver
Would it matter that I had previously done a bunch of messing around with my ASUS transformer on this computer?
under device manager it says:
ASUS Android Devices - Android ADB Interface
I'm going to try it on another computer tomorrow but I'm curious if that should make a difference.
The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...
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"?
I did the stupid mistake of deleting everything on my phone from my pc, and i can't remember correctly but i did something else, now my phone is not recognized by my PC. I have a rooted samsung galaxy nexus. and i installed the driver for my phone. My pc recognizes the device on the device manager but i can't find it on my computer unfortunately. there is an entry in the device manager says (Android device 1.0 with an exclamation mark).
Thanks in advance.
Sounds like your fastboot driver may not be installed. Try uninstalling and reinstalling them. If you are using a Windows 8 machine it seems like there's also an extra step. efrant has it here.
http://forum.xda-developers.com/showthread.php?t=1812959.
Sent from my Galaxy Nexus using xda premium
Pierceye said:
Sounds like your fastboot driver may not be installed. Try uninstalling and reinstalling them. If you are using a Windows 8 machine it seems like there's also an extra step. efrant has it here.
http://forum.xda-developers.com/showthread.php?t=1812959.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Still nothing, i followed the steps in this and nothing, I can boot the phone to recovery nothing more, I just need to see my phone in My Computer that's all.
Unplug your phone from the PC. Power down and reboot to fastboot(power+volume up+volume down) then plug it into the PC again. Does the "Android 1.0" designation change to "Galaxy Nexus?"
Sent from my Galaxy Nexus using xda premium
Pierceye said:
Unplug your phone from the PC. Power down and reboot to fastboot(power+volume up+volume down) then plug it into the PC again. Does the "Android 1.0" designation change to "Galaxy Nexus?"
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If i am in boot loader screen, there is (Android device), and under it samsung galaxy nexus bootloader interface.
But if i go so recovery mode it changes to samsung android ADB interface no exclamation marks. Still nothing on My computer
ErMaX83X said:
If i am in boot loader screen, there is (Android device), and under it samsung galaxy nexus bootloader interface.
But if i go so recovery mode it changes to samsung android ADB interface no exclamation marks. Still nothing on My computer
Click to expand...
Click to collapse
It won't show up under my computer *face palm*, you need to use fastboot or adb to interact with the filesystem.
No exclamation mark means a driver is installed. You don't have fastboot driver installed. Reboot to recovery, use adb. Reboot to bootloader, use fastboot.
Sent from my i9250
bk201doesntexist said:
It won't show up under my computer *face palm*, you need to use fastboot or adb to interact with the filesystem.
No exclamation mark means a driver is installed. You don't have fastboot driver installed. Reboot to recovery, use adb. Reboot to bootloader, use fastboot.
Sent from my i9250
Click to expand...
Click to collapse
Now i have (Portable devices) MTP USB device (with exclamation mark) which is the problem. i am new to those stuff and from what i understand my PC can not communicate with my phone because of that. Please the drivers can not install the MTP section.
Hello everyone, been a while since I have been on this site.
I am in a dilemma which I hope you guys can help me with.
I have a samsung galaxy nexus, and I just wiped the phone. But there is no recovery, so I have no OS atm.I have tried the Android Toolkit, however, everytime I try using it I get problems. It says , " waiting for adb mode" . I downloaded SDK and have runned the adb.exe file, but a command prompt pops up, and a bunch of stuff pops up and scrolls down, and then it closes. It does nothing.
I have read that my drivers for ADB are not installed properly or whatever. So I tried uninstalling them from " device manager" and I tried reinstalling them. That didnt work. I tried uninstalling again and than downloaded a samsung galaxy nexus usb adb driver, which also did not work.
I just want to be able to place a ROM on my phone from the computer. If I can get that far, I can install it from recovery mode. But I cant even get it fully detected on my computer. Whenever I plug in the USB, it detects it, but drivers fail.
Also, in device manager, the universal serial bus controller, SM bus controller, and ethernet controller all have a yellow triangle over them. They always fail to install..
I have tried updating them from the device manager. But that has failed aswell..
Please someone help me. I am at a dead end and unsure what to do.
-Andrew
Try a different cable or different drivers. And please learn to use adb yourself and stop using toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app
Can you enter in bootloader?
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
I can go into bootloader and recovery mode. I also tried a different computer and usb. It looks like its a bit better now because it actually says Galaxy nexus, instead of android device. However, I still cant go into ADB mode.
Everywhere I go, people say you need to enable debugging....but I dont have an OS. I am stuck in recovery or fast bootmode.
In the meanwhile, I tried installing zip file via sideload using Android Toolkit by skipsoft.( option 16) ....it looked like it was going to actually work...but it didnt. It says i dont have a recovery for TWRP or any of the other options.
You need to install fastboot drivers, and download 4.3 (or any you like) Google factory image for maguro. Flash that image, and install prefered custom recovery
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
andrewb71 said:
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
Click to expand...
Click to collapse
Enter bootloader on phone and connect it to PC. Phone probably wont be recognized. After that go to Device manager and find your phone ( as I remember it will say Android 1.0 or something similar), right click on it and press Update driver. In new dialog it will ask you whether you want to automaticly find drivers or manually. Press manually and select that usb_driver folder.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
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: