Database Develop

USB Tethering: How ?

The cyanogen rom 4.2.3 has USB tethering support, but I can not get it to work, mainly because of missing information/documentation.
In 'settings' 'wireless controls' there is a nice 'Internet tethering' option to switch it on. When I switch that on then my Windows XP PC shows an unknown device 'Andriod Phone' and would like to install drivers for it. Where can I get these drivers from ?
Markus

I would also like to know how the usb tethering works for a mac as well. Didnt find any information on that. Thanks in advance.

You may need to get the drivers from the Android SDK, but with regards to USB tethering, your phone should be recognised as an NDIS based network device and installed automatically by Windows. Not sure about XP, but it installs automatically on Vista and 7

Under Ubuntu Linux (from an end-user perspective), when a G1 is connected with USB tethering enabled, network manager connects as if the phone were a standard, ethernet connection.

Shane2 said:
You may need to get the drivers from the Android SDK, but with regards to USB tethering, your phone should be recognised as an NDIS based network device and installed automatically by Windows. Not sure about XP, but it installs automatically on Vista and 7
Click to expand...
Click to collapse
I have the Android SDK (1.6r1) and I point the driver install wizard at the usb_driver directory when he wants to install the device. Despite this the 'Found new Hardware' Wizard come up with 'Cannot install this Hardware'.
Markus

markusb said:
I have the Android SDK (1.6r1) and I point the driver install wizard at the usb_driver directory when he wants to install the device. Despite this the 'Found new Hardware' Wizard come up with 'Cannot install this Hardware'.
Markus
Click to expand...
Click to collapse
For xp you have to install drivers from htc sync software. Just google 'htc sync'. Should have been asked in q&a.

Nothing happens on Mac OS X 10.5.8 neither on 10.6.1

dumfuq said:
For xp you have to install drivers from htc sync software. Just google 'htc sync'. Should have been asked in q&a.
Click to expand...
Click to collapse
Isnt this Q&A? but I think this is it.... http://handheld.softpedia.com/progDownload/HTC-Sync-Download-81096.html
Im trying to get this to work also

I couldn't get it to work on my Windows XP SP2 computer at work. I get a code 10.

Guys, don't forget to use search! I've seen these issues brought up in at least 3 or 4 threads, and tons of posts.
bassderek said:
If you're running windows XP the driver isn't included on your computer. Some people have installed HTC Sync to get the drivers, personally I got them from this post:
http://forum.xda-developers.com/showthread.php?t=445436
I can confirm that the driver from that post works, I am using tethering with my laptop right now to write this post!
Click to expand...
Click to collapse

bassderek said:
Guys, don't forget to use search! I've seen these issues brought up in at least 3 or 4 threads, and tons of posts.
Click to expand...
Click to collapse
The search doesnt always give you what your lookin for if you dont word it a certain way man................
I think im gonna need a step by step.... I got the file... the computer recognizes the device.... But it doesn't register as a connection....

To everyone that is having problems tethering:
I was having the same issues. At first I wasn't able to get it to install, and then it would just keep saying the device couldn't start.
i found a very simple solution. I went into device manager, uninstalled all of my usb ports, and restarted my computer.
When it restarted, it automatically installed the usb drivers, and the tethering has worked ever since.

I could not get this to work either, finally after 3 days of messing with this on my work pc, I got it to work. First download htc sync from here http://www.htc.com/uk/SupportViewNews.aspx?dl_id=631&news_id=270 then unzip and install to your pc. Next tick on the option to usb tether while the phone is plugged in. It will say found Android phone Sdk or something like that. I did this on my xp pc at work that had no htc drivers previously installed. Next I went to my device manager and under network adapters you will see the yellow exclamation point, right click on that and update driver, 1st install from a specific location, 2nd Don't search I will choose driver to install. 3rd Have disk, 4th browse to C/program files/htc/htc driver/driver files/xp_86x then hit open and click ok. It might give a "stop warning" ignore it and continue. When its done installing you should be ready to go.....

badaphooko01 said:
I could not get this to work either, finally after 3 days of messing with this on my work pc, I got it to work. First download htc sync from here http://www.htc.com/uk/SupportViewNews.aspx?dl_id=631&news_id=270 then unzip and install to your pc. Next tick on the option to usb tether while the phone is plugged in. It will say found Android phone Sdk or something like that. I did this on my xp pc at work that had no htc drivers previously installed. Next I went to my device manager and under network adapters you will see the yellow exclamation point, right click on that and update driver, 1st install from a specific location, 2nd Don't search I will choose driver to install. 3rd Have disk, 4th browse to C/program files/htc/htc driver/driver files/xp_86x then hit open and click ok. It might give a "stop warning" ignore it and continue. When its done installing you should be ready to go.....
Click to expand...
Click to collapse
I'm so frustrated with this whole process. I've done every step you've outlined, and I still get a code 10 - cannot start the driver. And I still don't have USB tethering. What am I doing wrong?

nmw407 said:
I'm so frustrated with this whole process. I've done every step you've outlined, and I still get a code 10 - cannot start the driver. And I still don't have USB tethering. What am I doing wrong?
Click to expand...
Click to collapse
I had the same problem with Windows XP SP2. I installed SP3 and it started working flawlessly. What are you using?

Binary100100 said:
I had the same problem with Windows XP SP2. I installed SP3 and it started working flawlessly. What are you using?
Click to expand...
Click to collapse
eeepc 901 nlited XP SP2.
I'll try and push SP3 and retry again tonight. Thanks for the heads up.

nmw407 said:
eeepc 901 nlited XP SP2.
I'll try and push SP3 and retry again tonight. Thanks for the heads up.
Click to expand...
Click to collapse
That's your problem then. Yeah update to sp3 and you will be good. I promise.

I'm running into the same tethering trouble, but appear to meet all the criteria mentioned in this thread and other threads i've come across. the bottom line is i can connect with ADB access and mount my phone's SD card via the usb connection, but tethering doesn't work under several versions of Cyanogen on my laptop. currently I have CM 4.2.12.2 on my rooted Dream. I have windows SP3 installed (installed it twice because problem persisted). I've uninstalled all the USB ports per an above post, rebooted and plugged my phone in. The laptop reinstalls the USB ports, and finds the phone as an "ADB Interface" named "HTC Dream Composite ADB Interface". I can update the drivers with the google SDK USB drivers which makes the device an "Android Phone" named "Android Composite ADB Interface" instead. With either set of drivers installed, once I go to Settings on my phone and enable tethering, the device under windows goes away and instead i get yellow question mark "Other Devices" named Android Phone. I can try to force it to use the same USB drivers but it won't install them.
With tethering turned off, i can successfully type "adp devices" on my laptop console and see that my phone is there. once i turn tethering on, the same command shows no devices.
The Dream works with tethering just fine on my windows pc and shows up as a "Network adapter" named "Windows Mobile-based Internet Sharing Device".
My laptop is a compac presario in case that matters. what do i need to do on it to make tethering work?

just found the solution. a lot of posts were talking about installing microsoft active sync. sounded pointless considering it's an android phone, but it ends up being that the drivers for "windows mobile-based internet sharing device" are part of the active sync installation. i installed active sync, plugged in my phone, enabled tethering and then the laptop installed the correct drivers and it all worked without a hitch. hope this helps others!

hamx0r said:
just found the solution. a lot of posts were talking about installing microsoft active sync. sounded pointless considering it's an android phone, but it ends up being that the drivers for "windows mobile-based internet sharing device" are part of the active sync installation. i installed active sync, plugged in my phone, enabled tethering and then the laptop installed the correct drivers and it all worked without a hitch. hope this helps others!
Click to expand...
Click to collapse
+1
This is totally the problem. I spent hours trying different ways then finally googled it and came here

trouble with ADB

I've been following mrkite38's nice guide here:
http://forum.xda-developers.com/showpost.php?p=5096501&postcount=17
I understand it completely, and have done similiar operations before. However I cannot get my phone to popup in device manager in any form. I here the bell that tells you a device has been connected, but nothing ever shows up, no notification, nothing.
Any ideas? thanks guys

Is USB debugging enabled inside android?

mrkite38 said:
Is USB debugging enabled inside android?
Click to expand...
Click to collapse
Yes and also stay awake

I've never had any luck with ADB also. I'm running Win 7 64 bit. I've tried all types of things LOL

Reddog80p said:
I've never had any luck with ADB also. I'm running Win 7 64 bit. I've tried all types of things LOL
Click to expand...
Click to collapse
same - maybe it's win7 is the problem. I've had problems with it on winmo as well. I'll try my parents pc sometime (xp)

i cant get it to work right on vista either. never have.

does your device ever show up in device manager? I can't even do that...

berardi said:
does your device ever show up in device manager? I can't even do that...
Click to expand...
Click to collapse
I got it to work on win 7 64 bit. It was a pain, actually I only got it to work on my laptop and not my desktop both with win 7 64 bit.
So normally when you plug in the android phone, 2 things pop up in device manager as Android phone, however one of them always trys to load a driver of a disk drive (probably set up to transfer stuff) however whenever that device is enabled with the driver adb wont work. So what I had to do was, especially b/c win 7 is a bit odd for automatically installing any driver it want with out input from up I had to disable that.
Start run gpedit.msc
in there go to Admin Templates > system > Driver installation > Driver instillation restriction. Enable both "Allow admin to override device installation restriction policies" and "Prevent installation of devices not described by other policy settings"
Ok after doing that you want to get rid of the drivers it tried to put in, so in device manager uninstall them, also download and run usbdeview, and remove the HTC drivers from there too. Might have to restart?
Now the drivers i used for adb was from proxoid, there are 32 bit and 64-bit versions there for you and it seemed to work
So d/l that, plug you phone in and in device manager manually set the drivers, you know right click deceive, update drivers, let me choose, choose form list, have disk etc.
Now the only pain with this method is that when you plug in another device, you have to go to device manager and install the driver from there either by using windos update or manually. If you take off those policies we changed earlier, windows in its great wisdom will reinstall non-working drivers.
Like i said worked on 1 comp not the other.
Good luck.

[Q] Nook, ADB problems

For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud

Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080

anyone have problems in ubuntu 10.04 can't get it :'(

I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk

I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.

[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.

If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs

I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps

Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.

Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave

I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.

[Q] ADB Problems installing on W7x64 (Composite Driver wont show)

HI,
I've had success installing my other android devices on my windows 7 x64 computer, have even used my (ADB) Nook Colour on a windows 7 32Bit laptop fine.
Problem: Android Composite ADB Driver wont install/ isn't found, Device is Auto Nootered on 1.1 using rooted stock firmware.
Tried:
I have the .android folder in my user profile dir with the device ID in it
Followed various wikis and guides (that worked for the 32Bit version)
Watched the driver load/unload in device manager as I tick 'Development Mode (enable ADB)'
Tried various driver packs from here and googles latest offering, still only matches up with Android ADB Driver not the Composite (wont even show me the composite one)
Wireless ADB works and is disabled, worried about installing CWM using wireless for some reason USB feels safer to me
Thinks I noticed:
Hardware ID is listed as USB\VID_2080&PID_0002 which matchs up with %SingleAdbInterface% in the ini file for the driver, composite aka %CompositeAdbInterface% has &MI_01 on the end. Not sure if that means its not getting the right hardware ID from the device when ADB/ Development mode is enabled of if having the wrong driver loaded on it shows up the wrong Hardware ID.
Things I havent tried, enabling ADB on the Nook using sqlite3 method, but if it works on another coputer didn't think it would be a good idea.
Plan:
Install CWM, flash CM7 or similar to device.

I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.

ouldsmobile said:
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
Click to expand...
Click to collapse
Same here!

This one is weird...
I'm on win7x64 and I *have* got adb to work at times. When I was first rooting my new NC (1.1.0), I fiddled with it and I had it running over usb fine. But now, when I plug in the usb and I either get that the device is unrecognized or it goes into usb sync mode. Haven't quite figured that out...
But, ultimately, I just use adb wireless for any adb stuff, although it's "not recommended". It's worked perfect for me all along.

Check this link
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.

loupnook said:
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
Click to expand...
Click to collapse
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently

UR Welcome and USB Automount?
NewZJ said:
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
Click to expand...
Click to collapse
Glad to help. What do you mean USB Auto Mount? I kind of thought that should happen?
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I've installed DropBox but it keeps asking for an SD card, which isn't a big issue, just i haven't found the time to go buy one. Is there a way to use db without an SD card?

unfortunately no, db requires external storage. if you opened the apk to recode its default directory maybe but im not sure its possible
usb auto mount I can disable in nook tools but its a persistant system that defaults every reboot, I dont like to see it popup while using the nook when I plug it in just one of many peeves

Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.

GateheaD said:
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
Click to expand...
Click to collapse
I thought that as well and flashed back to the EC 1.0.1, sideloaded 1.1 update and repartitioned, used cw to add HC back and all that, and still had the same issue. Came down to the ini file not having a NookColor section.
Did you check the link http://forum.xda-developers.com/showthread.php?t=987409

I'm no stranger to drivers, I could force it to use the driver by changing the ini files but it still wouldn't appear in ADB Devices.
Flashed Nooky FroYo and now the device driver states the hardware ID has the missing '&MI_01' which means the composite driver works out of the box.

I used IOMonsters Easy USB installer and it seems to have installed the drivers for Windows 7 64Bit Fine
After running the install .exe I also had to execute the Inst64.exe

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?

@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Thanks for the reply. Unfortunately that seems to have done nothing

I'd go w/ uninstall all other drivers first, change cables and see what happens.

Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.

morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?

cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...

efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.

OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.

morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk

FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.

Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.

Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?

Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?

Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.

Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.

Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452

Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.