Develop Bugs

[Q] EVO Unrecognized - WTF??

Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.

buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App

EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...

perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes

Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.

Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.

Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...

What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.

try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST

Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.

I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.

Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever

It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.

buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip

No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.

**BUMP**
Anyone care to take a shot??

Possibly bricked Kindle Fire....help needed, and appreciated!

A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!

Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.

soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.

soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.

soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?

soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.

Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.

kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.

Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail

I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.

You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.

kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?

Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.

soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.

soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?

Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.

soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....

I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.

That will work. Download Ubuntu 10.4

driver question

I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam

samwage123 said:
I posted another thread with problems with odin and my ace 2. I uninstalled all the samsung driver's, I then reinstalled the samsung driver's and i get all these missing bluetooth driver's and 2 android driver's on my device manager. I can assume this is why odin is not working can anyone help please ? I have attached an image of my device manager. Also the samsung ADB interface driver only pops up when my device is plugged into my computer.
Thanks
Sam
Click to expand...
Click to collapse
I don't know about the bluetooth drivers but indeed Android adb driver should work. So here is what I suggest.
Go to the Samsung Android Phone tab, and uninstall these 2 drivers in there, restart laptop, then go and download the ace 2 drivers from here and see if it works, ah btw let the phone connected during the whole process.

Thanks for the advice i followed your advice, uninstalled both the samsung and ADB then restarted my computer. I then reinstalled the drivers you provided with my device plugged in, while they were installing. I got the bluetooth drivers popup again, Also theres a new thing under my portable devices tab i will post more screenshots this is really boggling me :/

Also this popped up when installing the drivers to do with the bluetooth.....

looks like MTP won't work either eh? Well let's see if it's the phone or the pc
Firstly follow those instuctions to do some troubleshooting.
1) Go to http://www.microsoft.com/en-us/downl....aspx?id=19153
3) Download the file
6) Run it
7) Follow the instuctions (NextNextNextNext)
That's it, now the MTP devices should work correctly.*
(ALSO Try de-selecting usb debugging)
If this won't work then I guess it's a problem with the phone.I read somewhere in a thread that some dude with the same problem on a samsung phone did factory wipe, wiped dalvik, and installed another ROM, then the usb drivers problem got fixed.
Good luck.
EDIT: Also check this site here it seems to have solution regarding the bluetooth peripheral thing.

none of those links work It has also stopped coming up as mtp it now just says GT-I8160. Also i noticed when i start up my computer it fails to start until i unplug it and plug it in again (attached pictures)

Also there is no android adb anymore its just the samsung one.... is this right? i appreciate your help
I am also using a 64bit version of windows 7 if that makes any difference.

Have you tried connecting the phone to some other pc just to know which one is the problem?
I've ran outta ideas...well the problem seems to be with the device itself and if not then it's probably the usb port,maybe insert to another port or try your luck on google, search for something like "windows failed to recognize android phone"or smth similar. I'll do some more research and try to help y'out tomorrow
Sent from my GT-I8160 using xda app-developers app

I tried disabling usb debugging also i tried the drivers on my netbook. I am having really strange problems on there with odin i plug it in and odin wont pick it up and as soon as i unplug it it says added then removed very weird :/ thats only when the phone is in download mode....

Im thinking its either the cable or the phone. Im not sure though..

Remove all Samsung related drivers.
Restart pc
Use cccleaner to clean the registry
Reboot pc
Use the drivers that i have provided in the s advance forum in my all in one guide. Install the drivers without connecting the phone.
After the drivers are installed, turn off internet connection and then connect the phone.
Sent from my GT-I9070 using xda premium

Thanks for the new idea shaaan I have succesfully followed steps 1 and 2. But I am struggling to find your all in one guide would one be kind to link me ? I did a forum search with no luck. Also I am using a galaxy GT-I8160 would using the s drivers matter? and thanks for the help mojito0 I would like to think it isn't the cable or phone, as I have literaly owned them for 8 days (just over a week). I can always see if i can borrow another cable of my friend today though
edit: I found your all in one guide I am now going to attempt what you said

After removing all the samsung related drivers and restarting I get all these devices come up? The device is not plugged in either.

I dont know if this helps atall, but I finished doing what you said ignoring the drivers.... Then went to flash using odin, Put the phone into download mode and noticed that after a couple of seconds of being stuck on setup connection. It then says the GT-I8160 cannot start, Also the mtp and adb android driver is still displaying that yellow explanation mark :/ I am a newbie to android here and dont know the difference betwene the samsung adb and the android one as listed do they both need to be working?

Remove all the displayed devices from other devices, also remove that Samsung adb thingy and also there will be one Samsung related device in the usb section! Remove them all and then follow my steps.
As for your driver query, the drivers are universal for a specific range of devices. The driver version 2.0+ should work for all devices which were released in 2012
Sent from my GT-I9070 using xda premium

Stuck in mini pooploader (Blue Screen)

I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there

Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567

wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...

I meant to say that I found that thread after being stuck in mini poop mode.

9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.

plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now

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!