Someone with more knowledge please help me.
I can not, for the life of me, get my computer to recognize my watch.
I've tried everything, I've tried installing the driver package another user posted.
I've enable usb debugging in dev settings.
I have adb working correctly but when I type adb devices it's blank.
The only glimmer of hope is I successfully connected my watch via bluetooth debugging and got a debugging dialog on my watch.
I've tried on two computers as well
I really need a detailed guide on how to get my computer to recognize this damn thing
Thanks - A very frustrated novice
Me too. Exact same situation. It was like i read my problem. Also i manage to unlock the device in fastboot mode. Adb in that mode is comunicating with the watch. Please help us. I dont know what to do anymore.
Sent from my SM-N910F using Tapatalk
The watch has no driver compatible with w8. I try pdanet and nO result. Please advice?
Sent from my SM-N910F using Tapatalk
Just managed to get my watch into fastboot mode but I still can't connect or recognize device in adb
Are you trying to connect while the watch is unlocked (screen on, not in ambient mode or off)?
brizey said:
Are you trying to connect while the watch is unlocked (screen on, not in ambient mode or off)?
Click to expand...
Click to collapse
No. The watch is awake
NxWorries said:
No. The watch is awake
Click to expand...
Click to collapse
Does your PC react at all when you plug in the USB cable? (Sorry if this is too basic.) Just wondering if its a bad charging cable.
brizey said:
Does your PC react at all when you plug in the USB cable? (Sorry if this is too basic.) Just wondering if its a bad charging cable.
Click to expand...
Click to collapse
Yes, my pc makes a noise and in my device manager the watch is identified as a Marshall London device. I think that's due to one of the many drivers I attempted to install. Thanks for your help by the way
NxWorries said:
Yes, my pc makes a noise and in my device manager the watch is identified as a Marshall London device. I think that's due to one of the many drivers I attempted to install. Thanks for your help by the way
Click to expand...
Click to collapse
Nevermind. It's identified as HUAWEI watch under the other devices section. I can't find a compatible driver
https://drive.google.com/open?id=0B6OEA3csBCnQU2dZSXVMTm9STDA
NxWorries said:
Nevermind. It's identified as HUAWEI watch under the other devices section. I can't find a compatible driver
https://drive.google.com/open?id=0B6OEA3csBCnQU2dZSXVMTm9STDA
Click to expand...
Click to collapse
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
I manage to install manualy usb driver from sdk directory. You have to update driver with those drivers.
https://youtu.be/RDA8PpPSFuk
https://youtu.be/FZu4GDf963M
Sent from my SM-N910F using Tapatalk
The watch was only recognize the first time.
On my case the phone are not recognized and the error message indicate:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
I must say that i´ve also that problem on pc and notebook running windows 10. usb port plugged in an nothing happen, no device recognition or something else. tried different usb ports, different machines, nothing...
Any ideas?
I have some problem how to solve??Any one have solve?
Thx
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
SirRobin78 said:
I must say that i´ve also that problem on pc and notebook running windows 10. usb port plugged in an nothing happen, no device recognition or something else. tried different usb ports, different machines, nothing...
Any ideas?
Click to expand...
Click to collapse
I know it's been a long time but were you able to find a solution ? I'm having the exact same problem.
Related
"USB Device Not Recognized"
I have searched for so long trying to figure out what's wrong. I'm out of idea's on how to fix it, nothing will recognize my Evo.
Tried on 4 different computers, two of them running 7, one running xp, and last running vista, all say the same thing, computers not the problem.
Downloaded htc sync, disabled/enabled usb debugging, restarted the phone many times, restarted computers, and even changed the default usb connection to HDD and HTC sync.
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
b1indsided said:
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just tried that and still not recognizing it.
Which HTC Sync did you try? I think the latest is 2.0.40
http://www.htc.com/us/support/evo-sprint/downloads/
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
http://kenshinjeff.18jan.us/2009/06/12/adb-error-device-not-found-android-phone/
or here
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
stratman71 said:
Which HTC Sync did you try? I think the latest is 2.0.40
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
Click to expand...
Click to collapse
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
guesswhatimevan said:
"USB Device Not Recognized"
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Click to expand...
Click to collapse
Did you do the 3 click method?
guesswhatimevan said:
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
Click to expand...
Click to collapse
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Philosuffer said:
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Click to expand...
Click to collapse
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Sorry but bump, i relly need help with this.
It still says unknown device when i try to connect my phone in recovery mode.
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Mast3rpyr0 said:
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Click to expand...
Click to collapse
Just tried that and it's a no go, still the same problem, Also tried another cable today and that didn't help either.
I have light leakeage at the bottom of my phone, so i think i'm going to take it in for that and just get a replacement.
guesswhatimevan said:
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Click to expand...
Click to collapse
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Philosuffer said:
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Click to expand...
Click to collapse
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
guesswhatimevan said:
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
Click to expand...
Click to collapse
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Philosuffer said:
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Click to expand...
Click to collapse
It shows up in usb controllers instead of other devices as he shows in the guide. If i try to update the driver it just tells me it's already up to date.
>Sorry yea it does say unknown device in device manager.
Gotta bump, would really love to just fix this instead of driving 30 mins to a sprint store.
So i followed the guide for installing apb drivers, but even in recovery mode my phone still shows up as unknown device in device manager.
Ok, well I just ran into this myself on my secondary computer. Have you tried a different USB port on your PC?
My front ones were giving me unknown device, but as soon as I plugged it into one of the ports on the back of the mobo ADB showed right up in device manager.
Factory reset it and get it exchanged.I belief is the SD card failure issue.
Sent from my PC36100 using XDA App
I have the same problem and posted this question on 3 forums including the HTC support forum and nobody has been able to find the correct solution.
I know the cable and the port is good because I can connect my Samsung Moment to it and it works perfectly. On the Evo, I've downloaded the latest HTC Sync from the official HTC site, tried the one on the microsd card, checked and un-checked USB debugging, and still it doesn't connect.
The Evo won't connect to my Win 7 computer at home, Win XP at work, but it will connect to my daughters computer which is running Win XP also (all 32 bit).
I bought this Evo from Best Buy exactly 28 days ago today. Do they give you 30 days to return it, or is that only the Sprint store?
They do give u 30 day trial.go get it exchanged or...........
Sent from my PC36100 using XDA App
Hello all!
First: I promise I searched the forums and google as hard as I could!
I'm running AOKP JB with CWM, although the problem was present on stock ICS from T-Mobile.
Symptoms: Computer and phone will refuse to acknowledge any connection (nothing shows up in Device Manager), except the phone will still charge. If I do the "remove the battery with USB plugged in" trick, the first time I do it, it will recognize an unknown device, but kies and adb won't recognize it. If I unplug it and plug it back in, it'll go back to not acknowledging any connection.
I previously programmed it (when I was still running stock ROM) via ADB via WiFi, but I need to be able to use ADB via USB. Besides, I can't seem to get ADB over WiFi anymore.
When I plug it into a different computer (Win7), it will, however, recognize my phone.
Earlier this year, before I ever tried programming via WiFi, it connected to my Win8 machine with no problem. I don't think it's a problem with the wifi setup though because the ROM was reinstalled and of course I've restarted ADB in USB mode in the months since...
What I've tried:
Reinstalling Kies
Reinstalling Samsung USB drivers
[^]Restarting the ADB server
Updating ADB
Trying different USB cables
Trying different USB ports
Toggling USB debugging
Toggling MTP mode
The UART thing from the dialer
Restarting the phone and the computer (of course)
Checking to see if my computer's USB drivers need to be updated
The android terminal command "setprop persist.sys.usb.config mass_storage,adb"
Pulling and replacing the battery while connected via USB
Crying in a corner
If anyone can help me, it'd be greatly appreciated! I'm all out of ideas and Google is no longer helpful =/
try to uninstall the drivers that are present anything samsung related to your drivers ... then connect the phone and let the process do its thing if you have the samsung drivers saved on your PC and the drivers still aint working update the drivers and then manually click where the drivers are to install them and hopefully it will work and when you tried MTP is it the only option it gives you no storage or anything ??... and is usb debugging on when you are trying all this ??
krazierokz said:
try to uninstall the drivers that are present anything samsung related to your drivers ... then connect the phone and let the process do its thing if you have the samsung drivers saved on your PC and the drivers still aint working update the drivers and then manually click where the drivers are to install them and hopefully it will work and when you tried MTP is it the only option it gives you no storage or anything ??... and is usb debugging on when you are trying all this ??
Click to expand...
Click to collapse
I tried on my work computer that didn't have any samsung drivers and when the "unknown device" dialog popped up it didn't do anything or install anything, nor did it show up in Device Manager. Unplugging and replugging it back in did not reproduce the dialog box. Togged USB Debugging and still no dialog box saying it recognized it.
The thing with the samsung drivers is that they're self installing so even if it popped up in Device Manager, I wouldn't be able to manually update the drivers =/
I tried MTP both with and without USB Debugging, although it also gives the option for PTP.
At this point do you think I should unroot and go back to stock? It's not been recognized on three computers now! =[
Are you using the stock cable? My computer wouldn't recognize mine without it.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
foltz61 said:
Are you using the stock cable? My computer wouldn't recognize mine without it.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Both the stock cable and a generic cable.
Similar problem
Similar problem as the OP. And hi guys, it's nice to be on these forums.
My device, when I plug it in using the stock cable, doesn't even charge. It doesn't show up in device manager, nor does it give me a notification, or say it's unsupported and bear that yellow icon. I have tried using different USB ports, I have tried the toggling USB debugging, I have tried restarting phone, computer, and taking out battery. I have tried that PDA/MODEM dialer trick. I am using 4.1.2 Jellybean, not rooted. (that WAS my goal,, until I hit this roadblock) I have not connected it to the computer in the past, it's relatively new. I'm thinking the cable is bust.
Any suggestions would be appreciated. It charges fine through a wall outlet plug, be it generic or stock.
so guys ive come to a conclusion i think its something in the samsung usb cables try getting yourself a blackberry usb cable , TRUST ME !!! ever since i got my phoness etc... tablet and yadi yadi samsung usb cables have always seemed to give me problems i think its because they are multi data/charging cables and when using the blackberry usb cable i have never ever once encountered a problem with any of my phones sd/storage problems do yourself a favor and pick up one of those cables and you will be golden !! if not then i guess im the only lucky one :LOL here you go http://www.amazon.com/Blackberry-Travel-Adapter-Micro-Cable/dp/B004VMVSYK/ref=pd_sim_cps_2 5 bucks!
Edit also one more test boot into recovery and click in the advanced menu and see if mount usb works for you in recovery mode ??
FIX (try using a generic cable)
I actually solved it on my own! After borrowing a generic cable from a friend it booted up! The Samsung cable was just not doing its thing.
yeah im telling you those cables they provide are JUNK!!! i only use my samsung to charge because they do that well but data they are str8 CRAP!! glad you got it up and going
OP
Hope OP will have the same luck as me...pray to the Android gods...
Lol:thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Friends,
I've searched through all the threads here and on zentalk but still no good.
I have a ze551 with Superzen, phone works fine however I cannot get it to detect in Windows.
Nothing shows up in device manager, I've tried USB Debugging, MTP and PTP. I've tried 3 different computers (2 x W10 and 1 x W7) and still no good.
The only detection I manage to get is a split second of MOOREFIELD showing up when powering the phone on.
I want to flash MM but cannot adb sideload due to this USB detection issue, any ideas?
What drivers did you install? When I first connected the phone to a pc I installed the Asus drivers but nothing worked. Everything began to work after installing the Intel drivers
h0mbre_au said:
Friends,
I've searched through all the threads here and on zentalk but still no good.
I have a ze551 with Superzen, phone works fine however I cannot get it to detect in Windows.
Nothing shows up in device manager, I've tried USB Debugging, MTP and PTP. I've tried 3 different computers (2 x W10 and 1 x W7) and still no good.
The only detection I manage to get is a split second of MOOREFIELD showing up when powering the phone on.
I want to flash MM but cannot adb sideload due to this USB detection issue, any ideas?
Click to expand...
Click to collapse
try to revoke all usb debugging authorizations from developer options. then disable usb debugging and disable developer option and enable again. now enable usb debugging again. now connect to computer. now run command "adb devices" and authorize from phone.if u still have issue try changing usb cable.
I've tried the Intel drivers., the problem is the phone doesn't even get detected by windows, there's nothing showing up in device manager.
I do however get charging from USB.
I've tried USB 2.0 and 3.0 ports in 3 different computers, no detection.
It used to work fine, now it has just stopped working. Maybe the USB chip is fried or something.
h0mbre_au said:
I've tried the Intel drivers., the problem is the phone doesn't even get detected by windows, there's nothing showing up in device manager.
I do however get charging from USB.
I've tried USB 2.0 and 3.0 ports in 3 different computers, no detection.
It used to work fine, now it has just stopped working. Maybe the USB chip is fried or something.
Click to expand...
Click to collapse
may or may not. may be usb cable broke down data wire, may be connector issue. have you tried above said tips?
Hey,
I got the same problem, and the quick charging takes 7 hours or so, but I should mention previously that in my case the USB port was damaged, so I changed the whole dock. After change tried all other cables including the Asus official cable, still no joy. It looks like some updates made a big fuss in the phone or ... the motherboard is burnt? I tried on different computers with and without Android Intel USB drivers installed, but the problem is the computer cannot see the phone - I'm getting the message that the phone is not sending its designator. I have not rooted my zennfone, but when I try adb to see if the phone is mounted it's not. I was planing to root it now, but it looks like I cannot do anything. I'm affraid that there is something wrong with the hardware. I did started also SMMI test and it loops testing bluetooth, so definitely there is something wrong, but yet I have not figured out.
sukhwant717 said:
try to revoke all usb debugging authorizations from developer options. then disable usb debugging and disable developer option and enable again. now enable usb debugging again. now connect to computer. now run command "adb devices" and authorize from phone.if u still have issue try changing usb cable.
Click to expand...
Click to collapse
Hey mate, thanks for the tip.
I tried this and it did not work.
Still only getting MOOREFIELD if I hold volume down+power but no other detection what so ever
h0mbre_au said:
Hey mate, thanks for the tip.
I tried this and it did not work.
Still only getting MOOREFIELD if I hold volume down+power but no other detection what so ever
Click to expand...
Click to collapse
did you installed intel isoc driver??? if so uninstall it and install intel android usb driver
sukhwant717 said:
try to revoke all usb debugging authorizations from developer options. then disable usb debugging and disable developer option and enable again. now enable usb debugging again. now connect to computer. now run command "adb devices" and authorize from phone.if u still have issue try changing usb cable.
Click to expand...
Click to collapse
sukhwant717 said:
did you installed intel isoc driver??? if so uninstall it and install intel android usb driver
Click to expand...
Click to collapse
I have tried all drivers, the phone was working fine on my windows install and suddenly stopped.
I believe this is not a driver issue, it is hardware issue with the port or with the rom (superzen).
I will try to flash other rom as I have custom recovery and see if it fixes otherwise the port is busted.
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Evnul000 said:
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Click to expand...
Click to collapse
Windows drivers 100%.
null0seven said:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Click to expand...
Click to collapse
I have tried it on both my PC and laptop with both windows 10. Does not work. My PC also has windows 7 still seems to not work. Are there any other drivers i might be missing?
i have also done some research that you should update your drivers from device manager. I dont see anything related to my device. i went to portable devices nothing and i dont have a other devices section in device manager. Any help?
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
null0seven said:
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
Click to expand...
Click to collapse
i am on the latest twrp. will blu-spark help fix it?
ive also found out theres no kedcom driver when i go to fastboot. i even reinstalled adb drivers to insure its there but it does not pop up.
You'll need to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
I once have kind of youre problem connecting to my laptop (win.10). But, at work, on that laptop, connection was ok (win.7).
I reinstal windows 10 and connection works fine, since.
I allways use latest TWRP & version of rom. I can't tell for sure what it's goin on with youre phone.
If i was in youre situation i format my phone (this will erase ALL in youre phone). And if PC still does not see the phone reinstall windows.
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
dentman said:
You'll bed to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
Click to expand...
Click to collapse
What are the driver links if you have? I already installed the OnePlus drivers.
ninjeratu said:
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
Click to expand...
Click to collapse
I used the OnePlus cable and another cable.
Driver issues win 10
Find the excellent tutorial here on drivers.
For some reason my phone didn't show up but was able to receive commands. It was frustrating because I wanted to use the all in one XDA product but couldn't.
Even if you installed drivers they can be broken!
Do drivers from scratch per xda tutorial. Don't forget reboot!
Try different cables and usb ports! My front ones never seem to work!
Don't just try fastboot commands also try adb. Like I said mine wasn't seen properly yet it took the commands.
Unless your windows is a years old install it shouldn't require reinstall.
Factory phone reset might help.
Best of luck!
I have no idea what I do wrong, but this is what I tried:
I enabled adb mode on my Chinese watch
The watch is in fastboot mode
I installed all drivers, pdanet didn't work (no usb connected)
Once I put my cable in my laptop and it said: USB error, try again later or something like that?
no adb response in the commands. just blank... in the devices list, there is no sign of my watch...
It charges normally. I could really use your help
Somehow I found the chinese wear OS so I can use it. at least that is something. Is there any way to get in in English or Dutch without adb?
My other laptop seems to see a 'unknown usb device'. no adb device found...
I have no idea... maybe it's due to the unofficial cable?
I bought an expensive cable, the original, but no laptop can see the watch (windows 10 and windows 7)
The old cable is some sort of ok with the windows 7. I get an error 43 in devicemanagement.
Please help... I have no idea what I can do now...
https://forum.xda-developers.com/showpost.php?p=73472794&postcount=15
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71653349&postcount=12
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
i am also bugged with this.
the win7-pc says unknown usb device detected. i turned dev mode and adb on.
then i tried to manually install the driver from the android sdk. when i try to select the driver windows says there were no driver found (but the driver is there) and i should make sure that the driver is written for x64-systems. WTF?
and even the watch does not charge wenn via usb 2.0 or 3.0 connected - but its connected cause of the message from the pc.
in the device manager the watch is listed as unknown device.
that's exactly my problem...
I have done everything. I'll try to connect it to my linux pc, I got an old laptop with ubuntu or something like that (haven't used it in ages)
maybe that will do the trick. I installed everything manually. my win10 can see an unknown device as well... but that's about it...
maybe dev mode is not working on some watches even when its enabled. or it has something to do with the 2.0 Version auf AW and it affects not every watch.
Its funny. I've been trying to get my HW1 watch to connect to my PC for a year now. Have tried numerous different cables and the original that came with my watch didn't work. Different PCs haven't worked either. Unless I'm that unlucky with all these OEM cables or the ADB debugging toggle really doesn't work for USB connections. It works just fine for bluetooth and wifi, neither of which allow you to unlock the bootloader. Guess I've got to wait for the next update manually and try again.