I'm using a windows 7 laptop with the normal drivers installed, and i have recently worked on an htc m9 and an m8. adb works fine on all my other devices. i reboot to bootloader and the computer instantly detects the connection and fastboot works. as soon as i boot into twrp, the usb disconnected sound goes off, and there is no mtp or adb. same thing with the os (newest stock system image). what the hell is going on?
Sieger179 said:
I'm using a windows 7 laptop with the normal drivers installed, and i have recently worked on an htc m9 and an m8. adb works fine on all my other devices. i reboot to bootloader and the computer instantly detects the connection and fastboot works. as soon as i boot into twrp, the usb disconnected sound goes off, and there is no mtp or adb. same thing with the os (newest stock system image). what the hell is going on?
Click to expand...
Click to collapse
can you confirm that "fastboot devices" returns your unit's serial number?
while "an htc m9 and an m8" work you still need Nexus-specific driver
please quote the USB's VID/PID from W7 device manager while in TWRP and/or OS
alternatively, post UsbTreeView_report
yes, fastboot works fine. i had to reflash the newest system image several times while trying to figure out why the tablet kept bootlooping after deleting bloatware off of the system partition (the google app doesn't like to be frozen or deleted anymore). the problem is that the n7 isn't even detected via USB outside of the bootloader. I'm assuming that the proper nexus driver is installed, but i cant just "update driver" with the official google drivers, because the tablet isn't detected by windows.
Related
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed
I finally got around to trying to install a custom recovery and root my HTC M8 (Verizon, KitKat 4.4.4).
I had previously unlocked my phone with SunShine - and have S-Off.
I tried installing adb/fastboot/drivers downloading from this thread:
http://forum.xda-developers.com/showpost.php?p=48915118
On my phone I turned off fastboot, enabled developer mode, and enabled USB debugging.
I connect my phone, it says USB debugging connected - and my PC (Windows 7) recognized the device.
However, when I try fastboot devices it does not recognize my phone - it returns nothing.
I realized that I had previous versions of adb/fastboot installed on my PC (From HTC Syanc & the WugFresh Nexus toolkit). I uninstalled them and reinstalled the drivers from that link, but still no adb/fastboot.
One thing I noticed is that (unlike the tutorial video on the link) in Device Manager my phone is not recognized under Other devices/ADB interface, but rather appears under Android USB devices / My HTC. I tried following the tutorial and tried to update the driver software, but it was not possible to use the downloaded Google drivers.
I tried unistalling the My HTC driver. The phone then appears for time under Other Devices / Android phone and then it re-installs the My HTC driver.
The PC recognizes it as an MTP/Media Player device, but not as an ASB one.
Any suggestions?
edit: Never mind. Arg, stupid me - I forgot to put the phone into fastboot usb mode.
Yeah....
ADB commands only work in a booted O.S or recovery
FASTBOOT commands only work in the bootloader
I am already rooted and on xposed using a win8.1 laptop. Followed the root guide by Heisenberg (sdk and adb drivers etc), however, on my desktop running windows 7 64 bit, I am not above to get my phone to show up with MTP. The option PTP however has no problem.
ADB is recognized in windows, but fastboot and adb are not recognized when in bootloader mode
Switching over to Win8.1, I have no such problems. Tried searching for win 7 updates and drivers but not much luck there, still cant get device manager to show the nexus 5x.
I prefer using the win7 as it is my main desktop versus the win8.1 which is a laptop that I leave mainly in the office.
Bump for this, Windows 7 users help!
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
alvinhochun said:
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
Click to expand...
Click to collapse
I tried this, now I can fastboot but no adb in bootloader mode. Nexus 5x device still not showing under computer drives.
queerquirks said:
I tried this, now I can fastboot but no adb in bootloader mode. Nexus 5x device still not showing under computer drives.
Click to expand...
Click to collapse
Well, you can't use adb in bootloader mode because that has never been a thing.
adb is available only in Android system and recovery mode.
All you can do in bootloader mode is to use fastboot to unlock bootloader, flash images and wipe partitions.
alvinhochun said:
Well, you can't use adb in bootloader mode because that has never been a thing.
adb is available only in Android system and recovery mode.
All you can do in bootloader mode is to use fastboot to unlock bootloader, flash images and wipe partitions.
Click to expand...
Click to collapse
Ah yes for the adb, i forgot about that. Tried mounting storage in twrp, device does not show up too.
I had a nexus 4 which showed up in win7 but not 8.1. Now nexus 5x is showing up in 8.1 but not 7, wth.
queerquirks said:
Ah yes for the adb, i forgot about that. Tried mounting storage in twrp, device does not show up too.
I had a nexus 4 which showed up in win7 but not 8.1. Now nexus 5x is showing up in 8.1 but not 7, wth.
Click to expand...
Click to collapse
Have you tried "uninstalling" the device in device manager when in TWRP too?
alvinhochun said:
Have you tried "uninstalling" the device in device manager when in TWRP too?
Click to expand...
Click to collapse
Ok just done it. Damm, at least 1 problem is solved
I followed your instruction and uninstalled the Google Adb Interface in device manager (didnt tried it at first as this was installed properly) and reinstalled it pointing the path to the sdk drivers, now I got fastboot in bootloader and adb in recovery respectively. In recovery mode, my nexus 5x shows up as a storage drive in my computer which allows file transfers However upon reboot, adb is not detected in android system and 5x not showing up in computer drive still.
queerquirks said:
Ok just done it. Damm, at least 1 problem is solved
I followed your instruction and uninstalled the Google Adb Interface in device manager (didnt tried it at first as this was installed properly) and reinstalled it pointing the path to the sdk drivers, now I got fastboot in bootloader and adb in recovery respectively. In recovery mode, my nexus 5x shows up as a storage drive in my computer which allows file transfers However upon reboot, adb is not detected in android system and 5x not showing up in computer drive still.
Click to expand...
Click to collapse
How about...
Have you tried "uninstalling" the device in device manager when in Android system? (Are you not noticing something... like... a pattern?)
alvinhochun said:
How about...
Have you tried "uninstalling" the device in device manager when in Android system? (Are you not noticing something... like... a pattern?)
Click to expand...
Click to collapse
What I had was
Android>Google Nexus ADB Interface , this works fine for adb and fastboot
Instead of Portable>Android, I had Unknown Devices with a exclamation instead hence the uninstall and reinstall would not show it as Portable android, only as unknown device.
Solved:
Solution for me would be clicking the notifications in the bottom left. saw that a Nexus 5x was still attached as a hardware even though the storage was not shown under computer.
- Uninstall the unknown device, 5x is still shown as attached in notifications
- Right-click the "safely remove hardware.."> open devices and printers and double click 5x
- Choose Update device drivers and point the path to the universal usb drivers ( android sdk)
5x mtp storage is now showing under computer drives but adb does not work in android system, only recovery. Good enough for me
Thanks alot for your help and time!!
alvinhochun said:
Have you tried "uninstalling" the 5X device in device manager?
After that re-plug the phone and it should reinstall the driver.
Do this for both in Android and in bootloader.
Click to expand...
Click to collapse
Just what I needed to do thanked
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.