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.
Related
[FIXED]
For some reason Toolkit didnt work for me and i used this method to unlock bootloaders and root it.
http://forum.xda-developers.com/showthread.php?t=1362957
Also installed CWM recovery
------------------------------------------------------------------------
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
sukyman said:
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
Click to expand...
Click to collapse
I was facing lot of driver issues when connecting my GNex for the first time to the laptop on WinXP. Installing the drivers through the GNex Toolkit also did not work for me.
Finally what worked for me was, installing the latest version of Android SDK with the additional package of Google USB drivers, and then manually selecting the drivers after connecting my phone instead of asking Windows to look for drivers automatically.
I had trouble when first connecting my GNex too. However, these drivers worked for me (plus work with many many other android devices):
http://forum.xda-developers.com/showthread.php?t=1379875
If you have several android devices you'll find that you don't have to install multiple drivers for adb, fastboot, etc. for each of the devices.
Taken from post#3 of the ToolKit thread:
Note 1: If the driver doesnt install automatically then double click on the Android 1.0 item, then click on the driver tab and select 'update driver'. Select 'browse my computer' and then 'Let me pick from a list'. If no items appear in the list then untick 'Show compatible hardware' and find the Android adb driver or Samsung adb driver.
Try that as they may be on your pc and just not installing.
Mark.
Got them working now but i have problem when rooting, using GNex toolkit 5.6
It boots into android, i set usb debugging but when the phone is suppose to boot back to fastboot it gives error device not connected.
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.
Hi
ADK is working fine with my other devices, but my PC can't seem to install the drivers for Huawei Watch. The devices is in the device manager, but a little yellow triangle at the side, which means the device drivers are not installed.
I have tried Google, but the guides just say install the devices drivers but clicking update in Device manager with the xx file I downloaded, but windows can't see the file.
Thanks in advance
only pdanet drivers works for me for adb but in twrp i cannot connect to pc . how have you solved the issue i have same problem in device manager. tried more than 6 ways after googling pc
i've tried pdanet drivers 64bit on my win7 64bit version.
but the installation cannot continue.. did u success installing pdanet ? what version of your windows u have ?
why is this marked as solved because i dont see the solution. i just received my watch today and cant seem to get device manager to recognize any drivers.
PDAnet doesnt fully install because i cant install drivers
Minimal ADB and fastboot dont recognize any devices attached
Universal Naked driver 0.73 doesnt work even after modifying the android_winusb file
I even installed the Google USB driver from the SDK Manager, but i dont see anything on my machine.
ive had this watch for 2 hours and already frustrated as hell lol. can someone provide assistance?
thanks!
PS. im running this on Windows 7 64 bit and the watch is at LCB43B already
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
hendry said:
same problem with me.. attaching usb cable into charger dock, detect huawei watch in device manager but drivers cannot be installed..
what's the problem ? which drivers can be used ?
Click to expand...
Click to collapse
i was trying all day on my work computer which runs windows 7 x64 with no luck, but the watch was detected immediately on my windows 10 machine at home. strange.
Success!
I fixed my issue! I had the same issue everyone here mostly had. I could unlock the bootloader, but I couldn't get the Fastboot recovery to work because the drivers were not detected by Windows 10, or my other Windows 7 machine. Both machines installed a standard version of Google Android device drivers and boot loader drivers, but they were not detected by ADB commands once in the bootloader.
First I went here to download all the drivers, but got stuck:
http://www.thecountrycaller.com/37260-how-to-unlock-huawei-watch-bootloader-and-flash-twrp-recovery/
So what I did was ran the commands to reboot to bootloader, then flash commands for the recovery, left my device plugged in. Then I went into the Windows Device manager, and looked for the Android or Adb drivers loaded. I double clicked the driver, and clicked on uninstall driver, and told windows to delete the drivers. I then unplugged my device (still in bootloader mode), plugged it back and in windows instantly detected the ADB flash commands and boom, TWRP recovery completed.
Hope this helps some of you.
this did not solve my issue ive installed the drivers and nothing over and over can someone help me with the drivers please
thanks
running windows 7
tried to install every driver possible
Weird as it may be, I managed to get Hwatch to connect to ADB via USB by installing the watch as a Motorola Android Sooner Composite ADB Interface - in device manager-update driver-select from PC-select from device list-android usb device-motorola
Is there anything what i can do when my classic watch is NOT recognized on both pc and notebook? I hear no sound, i can´t see anything in device manager...any help?
Hi I`m using the huawei 2 LTE version - can I take the same driven from here or will that cause problems ?
---------- Post added at 08:11 AM ---------- Previous post was at 08:09 AM ----------
Is this may be a real help https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
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.
I have tried everything including installing drivers and updating the Android SDK on Windows 10 but I cannot recognize my Nexus 5x 16GB. When I inspect devices on chrome nothing shows up.
This comes after getting the 5X back from LG after the infamous bootloop issue. They claimed they fixed the flash memory but didn't bother ensuring the phone booted up properly with an OS. I can get to the bootloader and I can get to stock recovery but ADB and Fastboot cannot communicate with the phone.
Any thoughts from the experts, I'm pulling my hair out. If I dont respond right away its because tonight my wife's father in-law is visiting. But I'll do my best.
Finally got Fastboot back. I had to uninstall everything again, not just drivers but apps listed. I then used the tool from this post: http://forum.xda-developers.com/showthread.php?t=2588979 and installed everything, basically hit Y for it all. I also had to run this admin.
Then once the phone was plugged in while in the bootloader I had to update the driver to composite. This shows up when you uncheck compatible drivers. Finally it worked. Now to unbrick my phone!