Windows 10: Android Data Bridge Drivers

I've tried every Android Data Bridge Driver on the net and get a Code 10 error as if the device isn't connected. I'm on W10 Pro v1607 but have v1703 on a WTG drive and neither work. In W7, the Device Manager shows the ADB Interface entry as working correctly.

:)

 

Lumia 950 XL and Android apps

But how do you use the Android Bridge?

 

windows 10 update also supports android apps

Windows 10 does not support Android apps. Microsoft are working on a platform making it easier to port Android apps to the Windows store, but it is up to the app developers to decide whether to do that or not. Furthermore there will be no support for Google
Play services.

Later this year, Microsoft will release the Windows Bridge for Android (previously called “Project Astoria” or “Project A”). This bridge enables you to build Windows apps for phones and small tablets by reusing your Android code.

With the Windows Bridge for Android you’ll be able to:

• Build Windows apps for phones and small tablets with few code changes
• Use a Microsoft interoperability library to integrate Microsoft services into your app with very little effort
• Test and debug your app from your preferred IDE
• Publish your app and get paid through the Windows Store

More details
HERE

 

Go here for an overall install of ADB, you can either install the whole thing or just platform-tools which is needed for ADB.

How to Install Fastboot, ADB and Google USB Drivers on Windows - Tutorial / Guide

For USB Drivers, go here:

Download Google USB Drivers - Windows 10, Windows 7 / 8 / 8.1

 

Thanks but it did look familiar but I did try them anyway. Like all the rest, driver installs but returns a code #10.

I did find out since my post that although the W7 device manager shows the device as working, it doesn't! I'm trying to set this up in Linux as well but one is building a driver by either editing a file or what has been the case creating a new one. Fastboot easily shows the device but ADB doesn't but you are dealing with manufacturer ID's, product codes and not simple. In fact, the product code that Linux returned at first isn't the same as it does now!*Huh I don't know that could have or would have changed on me.

 

How about booting W7 into safe mode, expanding dev manager and pull all or any instances of the USB and or ADB devices if possible?

Unfortunately I've never had a problem getting drivers for my phone (Nexus 6) or prior for use with ADB, and getting the drivers setup is the hard part. after that ADB is easy ... Did my June Sec updates yesterday on this laptop in fact.

One last thought, are you trying the device in a USB 3.0 port? Don't. Try a 2.0 port instead ...

 

There is this nice free app from NirSoft: View any installed/connected USB device on your system for looking at USB devices that makes that easy so yes, I've tried that also.

Yes, at times I did uses a USB 3.0 port on a legacy BIOS system but using a USB 2.0 port made no difference. I just found one mistake in my Linux set up after reading something again.

How does your ADB show up in the device manager? In Le Mobile or a separate Android? As a ADB Composite Interface or just ADB interface? The Nexus 10 has different device ID for all of them. That's what change on me. First time I got a 4e40 which is actually listed in the INF as for a Nexus 7 then a 4ee0 which is a Nexus generic code but both are for a Single Boot Loader Interface but that's only for Fastboot commands or at least I think so. I was using the 4e40 for stuff I had to add to the Android Rules for USB detection.

I did put the N10 into another mode by accident. Power & down volume goes into the Boot Loader with alert of, don't turn off target, downloading. You can't cycle through the options but Start works. Don't remember that from way back, not sure what it is?? That creates two USB events with the NirSoft app named Samsung.

 

My phone when plugged in is listed as Portable devices with a subheader of Nexus 6. That's it with USB debugging on for the phone, not in bootloader at that point.

Running adb devices from platform-tools dir gives me the serial and device as the response, which is good.

Try connecting while not in bootloader, you can always command it into bootloader thru the command prompt.

 

That's actually a hint at my mistake!*Sick I was using Linux Mintmate 18.1 and wonder what the device ID would show with the N10 ON not in the bootloader mode. It showes 4ee2 which is the ADB Composite Interface although it shows a Nexus 4 (debug). Huh? Debug? Looking at the N10 screen there was a prompt to okay debugging mode and the N10 now showed up.

So ADB mode is like MTP mode with the ADB enabled. I probably knew this three years ago which probably the last time I used ADB mode.

I booted into W10, installed the ADB driver but at first I got a Code 10 but I had two ADB Composite entries, uninstalled one, no more code 10, command line "adb devices" showed it offline, tried that again, the N10 showed up and one or the other I got the screen prompt to okay debugging.

Well, at least I learned a little bit more of Linux! *Biggrin Have to go back and see what I can remove/delete from my wild goose chase.

Thanks for your help!*Thumbs

 

Cool!

Yup,you should be good to go now, the hard part is over *Smile

Glad to assist.

 

Funny, I've yet to find any video, etc. that actually showing ADB use, only installing drivers. I guess that was probably covered when the Nexus 10 was a newly released device.

 

I'd go here:

Android Debug Bridge | Android Studio

to the source hehehe ....

 

Good link, I bookmarked it.

Although in the Note:, you have to "assume" what they aren't saying, meaning they don't mention the holding two buttons to boot so they "must" just mean boot it normally to see the alert pop up for the RSA.