Develop Bugs

Help GNex has no OS and won't connect to a PC!

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:

Device not detected.

Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.

C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.

mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.

C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )

wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.

No ADB. No TWRP. No Magisk. Am I screwed?

Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!

This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.

As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.

I'd tried Fastboot already, will try again momentarily though.

D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.

For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.

D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.

Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?

Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!

Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.

Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.

Pixel 2 XL isn't detected on my PC [help]

After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared).
Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks

If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!

simplepinoi177 said:
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
Click to expand...
Click to collapse
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"

blancheSX said:
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
Click to expand...
Click to collapse
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?

I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU

I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked

I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!

If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions.
You can find the latest version linked in the 9x guide in my signature.
Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC.
There is also a basic troubleshooting guide in the same link in my sig.
Best regards!

simplepinoi177 said:
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
Click to expand...
Click to collapse
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now

dallas90733 said:
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
Click to expand...
Click to collapse
i tried those tuturial and ended in error code : 10, device cannot started.

SageWilliams said:
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
Click to expand...
Click to collapse
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.

blancheSX said:
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
Click to expand...
Click to collapse
blancheSX said:
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
Click to expand...
Click to collapse
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly.
*One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…)
If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands
Code:
adb devices
and
Code:
fastboot --version
.
Hopefully, if you do all of these things, it might get things reset and working from a stable established set up.
If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out...
Let me/us know how it works out, good luck, and hope this all ends up being helpful…

simplepinoi177 said:
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Click to expand...
Click to collapse
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much

blancheSX said:
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
Click to expand...
Click to collapse
Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding...
If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......

Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit.
Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.

My tablet is stuck as an unrecognised USB device by Windows 10.

Hi there. Sorry if I sound dumb. I'm new to this whole thing and this was supposed to be my first experience with flashing custom ROMs and stuff like that. I was planning to get ready to install LineageOS on my Nexus 7 using a Windows 10 PC. Unfortunately, things quickly went south.
My first roadblock was the tablet not being recognised by fastboot. I checked online for a bit and from what I could gather, the solution was to install the Google USB drivers using device manager. I went into device manager, right clicked my Nexus 7 in "portable devices", selected "update driver" and chose the Google USB driver I downloaded from the official Android developers website. I'm not sure if this is relevant but the tablet was in fastboot mode when I did this. From that point on, my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode, and regardless of which USB mode I choose.
I tried uninstalling the driver, factory resetting, WugFresh NRT, and using different cables and USB ports. I checked for all sorts of solutions but they either didn't help or they require an unlocked bootloader (which was the very first thing I tried to do before finding out I needed to install the driver for fastboot to recognise the Nexus 7). Does anyone here know of a solution to get this working again? I'm completely stumped on what to do.
EDIT: I tested with a Chromebook and an old Windows 7 PC I had lying around. Neither could detect my Nexus 7 and the W7 PC even said it failed to install the driver as soon as I plugged it in. It seems that the driver update screwed up my tablet somehow and I have no idea how to fix it. I really don't understand how this could have happened considering I followed Google's own instructions for updating the driver.
Does anyone perhaps have a copy of the OEM driver for the 2013 N7 Wi-Fi (flo) model? ASUS don't distribute the driver on their website anymore and I'm out of ideas.

BenSkylake said:
my tablet is no longer recognised and it just keeps saying "device descriptor request failed" whether it's in fastboot or normal mode
Click to expand...
Click to collapse
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root

k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
Thanks for the response. I don't think I'll have enough time to try this today but I might as well ask. Do any of these fixes work without needing a USB connection to a PC, or if they do, do they require adb and fastboot to work? Because if so, I won't be able to use them since my USB data connectivity is completely busted no matter what I plug my Nexus into.

k23m said:
Review this thread and the solutions.
After you have fixed it, you can easily install a new custom ROM with two steps:
RESTOCK - installs USB drivers and unlocks it, latest official stock ROM
CROSS - various custom ROMs, 1-click installation, TWRP, incl root
Click to expand...
Click to collapse
I just ran the RESTOCK 1 script and it worked wonders! My tablet's USB connectivity has been fixed and as an added bonus, my bootloader is now unlocked. I'll be continuing the process in Linux on my Pixelbook since it doesn't require any driver installations as far as I know. Thank you so much! You're a life saver!