Develop Bugs

Need help getting Pixel C recognized in ADB / Fastboot

Got my USB-C to USB-A cable today, so I'd like to unlock the bootloader on my Pixel C. The problem is, when I hook it up to my PC, it does recognize it in Windows as the Pixel C - I can see it and browse through the drive and folders - but when I try to run an ADB Devices command, it does not see anything.
I think I have all the latest drivers - I grabbed the Marshmallow and USB drivers from the links on this page:
http://www.androidbeat.com/2015/10/how-to-unlock-nexus-6p-bootloader/
But I'm still not getting anything. I've tried using different USB ports on my computer, both USB 2 and USB 3 ports (although I've always had success with the USB 2 ports in the past), but still no dice. I did notice when I go to Device Manager, that there is an ADB Interface Device that is unrecognized, but I've tried updating the drivers (no luck), as well as uninstalling and then rescanning for hardware changes (just get the same unrecognized ADB device as I started with).
For reference sake, I'm using a Windows 10 Pro 64bit PC.
I'm at a loss as to what to do, so any help I can get here would be greatly appreciated.

Nevermind, I was able to get it straightened out. Used the download/instructions found on this XDA thread to get everything squared away:
http://forum.xda-developers.com/showthread.php?t=2588979
Device is now unlocked and I can go ahead and set it up properly while waiting for root access to become available.

What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.

regime2008 said:
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
Click to expand...
Click to collapse
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.

Geese1 said:
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Click to expand...
Click to collapse
Funny thing is, I have tried all of those steps, and still no luck. I have deleted all of the drivers completely. Reinstalled them, and still get code 10. It seems several people are getting this issue in the thread you linked in your second post.

My Pixel C got an invalid pin error so tried to do a factory reset through android recovery but that ended to a bootloop and the tablet is simply useless. Thought I'd try to install OS again see if that would bring it back but I can't even get it recognised in the pc. I've put it in fastboot mode and it won't even acknowledge I've connected anything. Nothing shows up on Device Manager. Am I doing something wrong here? I'm out of ideas

HELP! Lumia 640 Device Not Recognized - Device Descriptor Request Failed

So lately I've been having more and more issues with my Lumia 640, such as random reboots, data switching, and slow downs. I decided that since I haven't preformed a hard reset since about 2 builds ago, it was time for it. I went ahead and reset, and everything appeared to be working better. It was when I plugged my phone into the laptop to dev unlock and deploy tools that I ran into trouble. As soon as I plug it in, I get the device connected sound followed by USB Device Not Recognized error, a Phone charging slowly message on the phone, and then a device unplugged sound from the laptop. I tried it on my desktop and get the exact same results. Both my computers are running Windows 10, and my 640 is on latest 10586 build.
I've tried everything I could think of/find online including
-Soft reset the device while plugged
-Using different Usb cable
-Uninstalling the device (read below)
-Rebooting the PC and letting it turn the phone on with it
-Uninstall all Usb Root Hubs
Unplug PC power cord/battery and Usb devices and wait 10-15min
-Developer Mode on/off
-Hard Reset phone again
I really don't know what else to do. When I plug it in and get the not recognized error, it's a Descriptor Request Failed, and then the device disconnects. In Device Manager it shows under Universal Serial Bus (as an Unknown device with the Descriptor Request Failed next to it) until it disconnects itself, then it disappears. Using Show Hidden Devices and a command to enable showing every device ever connected (plugged in or not), I see it show but it's greyed out and it's properties page says it's disconnected. While showing all hidden devices, I uninstalled the phone under Portable Devices as it used to work, along with my wife's phone.
Nothing I've done has gotten me anywhere. It just connects with the error and immediately disconnects. It used to work with both the laptop and desktop before I hard reset. The only thing i believe could be causing it was the fact that before the reset my phone was being faked as a Lumia 1520. But I've uninstalled that in the hidden devices of Device Manger.
Any help would be greatly appreciated. As it stands, I can't developer unlock, deploy tools, or even copy my pictures!
Edit- just tried plugging it into 2 other computers with WinXP (. I know it's not supported), and also get the device not recognized and charging slowly. So... Either the firmware/os git messed up, or the Usb jack is messed up.

I have also have same problem. If you find the solution. Pls let me know. problem is you cannot roll back to 8.1 without connection to PC
---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------
probably this can help
http://mobifaq.com/why-can-t-i-connect-my-lumia-640xl-to-my-laptop/t9893/

Does device charge properly using AC? Based your trouble shooting so far it seems like it be the Usb port acting up.. I am assuming the Usb cables were 6ft and under? Did you flash any non stock rom to the phone? And what do you mean faked as a 1520? If the phone acts weird while charging it definitely could be the phones Usb port. If not you can put the phone in flash mode and use thor2 list device connection list to see if and how long the phone is being detected by windows.

OP, you have interopunlocked phone with FS acces?

augustinionut said:
OP, you have interopunlocked phone with FS acces?
Click to expand...
Click to collapse
as a matter of fact yes, to both!
anubis23 said:
Does device charge properly using AC? Based your trouble shooting so far it seems like it be the Usb port acting up.. I am assuming the Usb cables were 6ft and under? Did you flash any non stock rom to the phone? And what do you mean faked as a 1520? If the phone acts weird while charging it definitely could be the phones Usb port. If not you can put the phone in flash mode and use thor2 list device connection list to see if and how long the phone is being detected by windows.
Click to expand...
Click to collapse
charging is perfectly fine. I also suspected the Usb port, but after an online chat with Cricket Support, they assured me it was a software issue.
animesh_shah said:
I have also have same problem. If you find the solution. Pls let me know. problem is you cannot roll back to 8.1 without connection to PC
---------- Post added at 02:54 PM ---------- Previous post was at 01:56 PM ----------
probably this can help
http://mobifaq.com/why-can-t-i-connect-my-lumia-640xl-to-my-laptop/t9893/
Click to expand...
Click to collapse
the thing is, I couldn't even restore to 8.1 with my issue. The phone would not stay connected long enough to be identified by the OS let alone the Recovery Tool.
However, I have good news. I did finally solve the problem. When I had realized that connecting the phone while in the boot loader got it to detect and install as Lumia BootMgr, I opened up the Recovery Tool and sure enough it was detected. I let it start downloading the ROM, and about 1/2 way through I heard the device disconnected sound and thought oh great this isn't going to work either. However, the download kept going, and when it finished I clicked the start install button, but it gave an error saying the device was not detected. So with the phone still plugged in, I preformed a soft reset and continued holding Volume down to boot back into the boot loader. When I came to the ! screen and the phone was detected again as Lumia BootMgr, I clicked Retry in the Recovery Tool and it actually copied over the ROM, which thankfully is a very quick process.
Once 8.1 had finished setting up the phone was detected and installed perfectly on the computer. Last night I updated back to W10 and it's still detecting without an issue. I'm for sure not enabling the Full Filesystem Access hack again. Before this problem started I was already tired of waiting up to 30 minutes at a time for it to connect. Only reason I did it was to copy the custom HOSTS mod file to block ads, which I'd love to do again, but it's just not worth it.

So, if FS acces, enter device manager on pc, disable windows phone, enable windows phone.... wait a minute...voila

augustinionut said:
So, if FS acces, enter device manager on pc, disable windows phone, enable windows phone.... wait a minute...voila
Click to expand...
Click to collapse
Are you referring to the problem I was having? If you are, then reread my OP. You'll see that Device Manager would not even display the phone because the phone would immediately disconnect after the USB Device Not Recognized error popped up. There was simply nothing to disable, or enable for that matter.
If your saying to disable and enable AFTER applying the FS access hack to affect the detection time, then please, elaborate on that.

Erase driver, reinstall driver, try with another pc, sell the phone....

@x_orange90_x
http://forum.xda-developers.com/win...de-filesystem-access-sftp-windows-10-t3185766

augustinionut said:
Erase driver, reinstall driver, try with another pc, sell the phone....
Click to expand...
Click to collapse
you obviously did not reread the OP.. I tried all of those with the exception of the last with no sucess.
And I think you've missed my point entirely.. I solved the issue already. Hopefully the other member that posted in here with the same problem can fix it by following what I did.

You right.. disable full fs access....

You still active Mr. Orange

Unknown Device in Windows 10, not showing up in Odin

Hey all, I have a pretty brand new Note 8 that Windows 10 is reporting as Unknown Device (Device Descriptor Request Failed). Because of this, Odin can't see it. This only happens in download mode. I've tried:
- the original USB-C cable (had never been used prior to this)
- another known good USB-C cable
- all the ports on my PC
It still won't work. Is my only option to try another PC? I don't have one readily available and I'm pretty far from home, so just wondering if anyone had any tips or suggestions before I try to hunt down another PC to use.
Thanks!

eww7633 said:
Hey all, I have a pretty brand new Note 8 that Windows 10 is reporting as Unknown Device (Device Descriptor Request Failed). Because of this, Odin can't see it. This only happens in download mode. I've tried:
- the original USB-C cable (had never been used prior to this)
- another known good USB-C cable
- all the ports on my PC
It still won't work. Is my only option to try another PC? I don't have one readily available and I'm pretty far from home, so just wondering if anyone had any tips or suggestions before I try to hunt down another PC to use.
Thanks!
Click to expand...
Click to collapse
Did you install the Samsung drivers?

Thanks for the reply. Great question, and sorry I left that part out. I did install what I believe to be the latest Samsung drivers, yes. I’ve restarted the device and PC since doing all of this, with no change.

You probably need to try to grab android sdk and install android usb from there... or look for the usb drive online and install it manually...

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.

slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)

150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.

slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

Post SS of the device manager after connecting the phone to the PC

150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.

@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...

Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722

slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode

150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.

nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.

150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?

nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.

150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.

Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?

slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?

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!