I am unable to get USB connection working with my phone for development purposes. I have turned on the USB debugging and connected the device with USB cable and it does detect file transfer capabilities, but I am unable to get the ADB connection working.
I am running Windows XP SP3
It says it has found a device 'Galaxy' but is unable to install drivers for it.
What I have tried:
sdk/extras/google/usb_driver directory
I tried installing PdaNetA302.exe
I tried installing Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
I selected 'install from specific location' -> choose a driver -> 'Android Phone' but it had none listed and the aforementioned driver directories did not work either when I selected them as 'Have Disk' options.
I also tried uninstalling all related devices and do the whole connecting thing again, but without success.
Help please?
SOLUTION
Apparently HTC drivers got in the way. After I removed all HTC drivers from my Windows XP, restarted and connected the device, the Samsung drivers kicked in and made it work.
To remove unused drivers from Windows XP you can follow this guide.
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
PdaNet
waylo said:
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
Click to expand...
Click to collapse
I had no end of problems getting adb and fastboot working for GN due to the usb driver problems.
After much Google-ing...
I installed PdaNet on my laptop and this installed all required drivers in the process of installing, you can then un-install PdaNet and the required drivers are still on your system.
I now have adb and fastboot working for both my Nexus One and Galaxy Nexus phones on my Windows 7 x64 laptop.
Hope this helps!
Thanks to XDA member el3ctrik for this tip!
Thanks, figured it out just after you posted. The PDANet drivers were the trick, in #3 below (don't need to actually run the installation in this case).
You'd think after 1.5 years of playing/hacking/unhacking/fixing and refixing the N1 I'd know how this is supposed to work.
A couple of comments, since some tutorials are based on older installations.
1. Installing android sdk. I went through a crapload of unnecessary trouble in trying to reinstall these, thinking that the usb drivers, adb, and fastboot needed to be updated. NO.
1a. In fact, in trying to reinstall the android sdk, you have to install the Java SDK. THEN, with the latest revision, R15, FASTBOOT IS MISSING! Need to pull that from a r13 zip.
2. You need the CORRECT samsung drivers. The ones mentioned above are the correct ones. I installed some limited half-ass versions which did not do the job.
3. You need FASTBOOT drivers. These were found from this post http://forum.xda-developers.com/showpost.php?p=9919944&postcount=1
which states:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
The #2 drivers let ADB see it when ICS is running, #3 (and probably #2 too) are needed while in fastboot. To get #3 installed, I had to go to device manager in Win7, hit update driver (next to the error exclamation mark device), and direct to these files.
That is all <whew!>
Glad you got it sorted out buddy, I was in exact same boat, years of Nexus One fastboot and adb use, but still had problems!
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Windows 7N USB driver issues
First post on this forum, so please bear with me.
I struggled for a few weeks trying to connect my new Samsung Galaxy Nexus (Rogers) to a 32-bit Windows 7 Ultimate N machine. The system wouldn't accept the drivers from Samsung - failed to recognize, driver software not successfully installed, etc. Tried all variety of proposed fixes, manually selecting the driver (have disk), downloading SDKs and ADB drivers.
Finally fixed it based on a very old suggestion from several years ago from an HTC user. The USB driver wasn't recognized in the absence of Windows Media Player being installed on the machine (a quirk of Ultimate N). Found the Patch from MS for WMP for 7 Ultimate N and the system immediately recognized and installed the Samsung driver and thus the Nexus is now connected.
Download my toolkit (ROM-Less), it will assist you in that manner!
It has easy instructions, and it will do most of the work itselff!
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
AMoosa said:
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Click to expand...
Click to collapse
Check this, it has all neccesary info/drivers for your device, including fastboot drivers!
Beatsleigher root helper (My toolkit) check it out
Related
So, I've found an array of guides both on and off the forums and I've followed a host of them. I am trying to obtain root and Superuser via Kindle Fire Utility. I've installed the drivers a number of ways including through the Android SDK, KFU and by unplugging and plugging it back in. Apparently the drivers are installed correctly because when I check in the device manager, the Kindle is listed as Android Phone and then under the dropdown as Android ADB Interface. However, no matter what I do, when I run the run.bat file in KFU the device is listed as offline and whenever I try to do the adb list the Kindle isn't showing up there either. I believe it is because I get a syntax error whenever I launch KFU before the actual KFU screen up saying that the location C:\User\.android doesn't exist. So, I'll list all the steps that I can remember I've done over the past 16 hours or so.
1) Downloaded the Android SDK and Java JDK (I think it's called...either way, I have updated JRE and DK)
2) Unplugged the Kindle Fire which is firmware 6.3.1 which was listed as Kindle in device manager and ran the install_drivers.bat file.
3) Confirmed via device manager that the fire is actually listed as Android ADB Interface
4) Did an adb kill
5) Deleted drivers once confirmed KFU couldn't find the device online
6) Reinstalled drivers via the KFU drivers folder
7) Repeated steps 3-5 then reinstalled the drivers via the Android SDK provided USB driver file
8) Repeated steps 3-5
And now I'm at a loss, I have no idea what else to do. I've rooted multiple phones as well as gotten homebrew running on Wii's and PSP's but this one is stumping me. Any advice or assistance would be greatly appreciated. Also, please don't kneejerk response and send me back to the thread explaining how to get the drivers running via KFU because I've done every step of that to no avail and I honestly believe the problem lies somewhere in the syntax error I get referring to the lack of a C:\User\.android folder.
Thanks in advance for your help
That's because your drivers are incorrect it should be android adb composite interface... sounds like your using xp and its the complete worst for driver installs...
my suggestion is this build your own little system with this http://forum.xda-developers.com/showthread.php?t=1850038 then do the task manually all you need to do is have twrp and fff the rest is entirely obsolete if you intend to just flash a rom anyway.. for the purposes of learning what to do and how to do it read these http://forum.xda-developers.com/showthread.php?t=1552547 http://forum.xda-developers.com/showthread.php?t=1638452 they will give you some needed insight.. jcase`s manual rooting tutorial can be found here but like i said flash a rom all roms are rooted http://forum.xda-developers.com/showthread.php?t=1568340
Thank you for the response, I am not using XP, I am using Windows 7 Home Premium.
I don't have Linux although I suppose I could use a USB drive or USB Hard drive to dual boot with Linux. Thanks again, I'll have to wait until my brother brings the Kindle back over to try this, until then I'll look over it all.
ok well usually running the install.bat for the drivers on windows 7 is enough but for some it isnt regardless drivers are you main issue and you certainly dont want to have any issues with them in the process it will only produce very bad results..
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
also your syntax error can be causing the issues as you say you need that .android folder to make it work...
post #2 has a ton of info on the driver thing http://forum.xda-developers.com/showthread.php?t=1552547
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/
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
@Istvan_86,
We should move the discussion for your problem here.
cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.
Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?
Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.
cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.
Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.
What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.
Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
@clockcycle,
This solution works 100% too. https://www.ubuntu.com/
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Let windows download the fastboot drivers from the network.
boot into fastboot, connect to pc
open up
win-r
devmgmt.msc
right click the 5x device and search network for drivers (or wherever that option is)
It'll come it with something like marshall london bootloader interface. That is fine, it works, it is for different phone that is also android based. The bootloader interface is the same.
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the very same problem when I first received my 5X. I tried every damn think on to get Windows 10 to see the device, including all listed here and manually installing the drivers downloaded from Google and various other sites. Installed various Windows 10 packages. Even LG driver packages. I believe the issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer. I'm willing to bet it would work just fine on 7 (did on every machine I tried). Eventually adb and fastboot magically started working but I still could not use MTP. The ONLY thing that got it working was, strangely enough, a reinstall of Windows 10 (chose to kept files/documents) and then updating with the Anniversary Update). I know that is like the LEAST desirable option.
Windows 10 is really just not great for this sort of thing.
stmims1124 said:
The issue lies in Windows 10 and I think perhaps maybe compounded by other drivers installed on the computer.
Click to expand...
Click to collapse
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
sfhub said:
I don't know if google fixed it, but the 11.0 Google USB drivers don't have the fastboot USB IDs for the 5x but most people wouldn't notice because win10 is probably configured to get drivers automatically from net.
I noticed because I don't have that enabled.
On a win10 box that is configured to get drivers from net, for 5x, adb, mtp, and fastboot work without installing any extra drivers.
Click to expand...
Click to collapse
Yeah, that's exactly how it's worked every other android device I've owned too-only had issues with this device and this particular Windows 10 machine. This machine is configured to get drivers automatically, but for whatever reason I just couldn't get this to work. Of course, this was just my experience but there have defintiely been other folks out there with similar (maybe not exactly the same) problems. It was infuriating!
I can't really comment intelligently regarding what Google may have done to fix this. I'm shaking my head to hear that their drivers for Nexus devices is missing the fastboot USB ID's for a Nexus phone lol
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
---------- Post added at 10:45 PM ---------- Previous post was at 10:34 PM ----------
Simone_ASR said:
I can not use fastboot on my pc with Windows 10 to flash something on my Nexus 5X.
I've installed Ubuntu and adb/fastbook works correctly. With Ubuntu I've installed TWRP and SuperSU.
On Windows 10:
- Adb works.
- I've Android Studio with the latest platform-tools.
- I've tried with 15 seconds ADB Installer v1.4.3.
- I've tried with this answer.
- I've already removed all usb-driver (as Nexus Root Toolkit suggest) and retry all.
What can I do?
Click to expand...
Click to collapse
I had the same problem, I got mine working this way..... I used an older version of the driver..... Open device manager, click on the kedacom usb device, android bootloader interface, click the driver tab, click update driver, browse computer, let me pick from list, there I had a few versiond listed, I picked the verion 9.0 dated 2014, click next....next.... it will install, should be good to go....
Thanks to all, I've solved with Google -> Android Bootloader Interface and it seems it works.
So, I have found a couple other posts on this issue but none of their solutions have worked for me.
Ill start with the set up I am currently on:
-Stock Official Android N (US Unlocked)
-Firmware 2.28.617.8
-T-Mobile with CID changed to run US unlocked
-S-off and unlocked
-Using windows 10 with ABD Fast boot file (not sdk)
So I have the drivers installed. Originally I was just using the HTC sync software drivers but moved to drivers I found in a forum post here, which unfortunately did not work.
USB Debug is checked.
My phone shows as connected and I can run ADB Devices and see it in the list until I ADB reboot bootloader. Once it is booted into bootloader ADB no longer sees the phone. Checking device manager shows that the phone is connected with no exclamation mark or question mark next to it.
I have restarted and reinstalled several times with no luck. I even run a usb bootable copy of Linux Mint hoping that it may just be an MS issue but I have the same problem on Linux whether I sudo or not.
Since I have had the phone ADB has worked whether in fastboot or not. It was only until I ran the official RUU and upgraded to Android N that it has stopped working. If I am not mistaken, in MM there was a popup when you had USB Debug enabled and connected to a pc that asked if you wanted to use that pc (or something like that). I am not seeing that pop in N.
Any help would be greatly appreciated as I would really like to get twrp installed and rooted.
Thanks all.
I have spent the past couple hours fiddling around with this and thought I would add and update.
I downloaded and installed Android SDK, updating everything and adding the Google USB drivers. Unfortunately this did not work. Same result.
I did however just find that if I go to the stock recovery and select the Apply update from ADB option, the device is recognized again in my cmd window.
Am I missing something. Is there a new procedure for flashing things like twrp with command lines? All the forums still show Fastboot as the method.
Anyway, that is it for my feeble brain for the night.
Sometimes it helps to use the usbdeview tool. It removes the link to drivers and gives you a clean start. Worked earlier for me. File is attached.
@Ludolf71
I gave that a try but it doesn't seem to help. Looking through the list of drivers there doesn't seem to be any driver conflicts and the only instances that show up on the list relating to my phone are the vendor drivers and the port that the phone is on.
At this point I am lost. I have spent hours reading forums and searching around for a solution. I am not sure what might have changed between running MM and updating to the current HTC RUU. Prior to installing the current RUU everything worked fine.
Looking though dev options there is an option to revoke USB debugging authorizations, is there a way to see the list of authorized devices? Also, I swear that in MM when I had debug on I had to authorize my pc when I plugged it in the first time after a fresh flash. Is that not the case anymore or is that option somewhere hidden that I am missing?
Has anyone put together an adb zip specific to the HTC 10 and the current firmware? Do to changes in the Android N firmware could this be the cause?
I tried Andoid SDK last night but I have to admit I am not very well versed in their software so I may not done it correctly. I have been modding and flashing custom rom since the poorly name MyTouch but have so far gotten by without having to use Google software suite.
Thanks all for the help.
Tried installing the HTC Sync Manager? That shall provide you with the correct drivers.
Yeah, I have installed and reinstalled the Sync manager several times. Like I said the phone is recognized using ADB devices while booted to OS but the second I adb reboot bootloader it is no longer seen.
I keep coming back to authorizations and i think this may be the issue. I see the option to revoke but I am not getting any options to authorize the PC I am using.
Solved: I was using the wrong command line as pointed out by xunholyx in another thread. Thanks @Ludolf71 for helping as well. Felling pretty dumb about this one
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
---------- Post added at 06:40 PM ---------- Previous post was at 06:40 PM ----------
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.