Ok after some hours of trial and error Im able to read and write to my one with qpst. I'll share my setup.
I'm on windows 8 64bit
I've attached the build of qpst I used as well as the driver.
If your on windows 8 or 7 you will have to disable the signed driver check
open command prompt by running as an administrator, then issue this command
bcdedit /set {globalsettings} advancedoptions true
reboot.
Once windows restarts choose option 7 to disable driver check.
Connect your phone with the usb cable and enter diag mode by press ##3424#
Two drivers should fail to load
Htc diag
Htc diag9k
Right click on the htc diag9k driver and click on "update driver software"
select "browse my computer for driver software"
Then "let me pick from a list of device drivers on my computer"
click have disk and navigate to where you extracted the driver files
and choose Qualcomm HS-USB Android Diag 9018
Click next till it is installed and you should be ready to open qpst
you will need your msl/spc code but there is a thread on a easy way to retrieve that.
The archives you attached are corrupt.
ProfessorAnomaly said:
The archives you attached are corrupt.
Click to expand...
Click to collapse
I Think actually it was my drop box, try them now
wranglerray said:
I Think actually it was my drop box, try them now
Click to expand...
Click to collapse
still not working,. corrupt
jcwxguy said:
still not working,. corrupt
Click to expand...
Click to collapse
It worked for me.
They're corrupt. I tried downloading multiple times, using different browsers on my PC as well as using different software to open the archives.
jkt97401 said:
They're corrupt. I tried downloading multiple times, using different browsers on my PC as well as using different software to open the archives.
Click to expand...
Click to collapse
I had no problem d/l and getting this installed. I am not doubting you, just odd that it works for me ok.
Corrupt for me as well
Sent from my HTCONE using XDA Premium HD app
Why not just use cdmadevterm?
What about CDMA workshop and qxdm?
Sent from my SGH-T889 using xda premium
Useful info
Just to let everyone know...
I just loaded the normal HTC Diag drivers I have been using for years for the diag9k. Was able to access it in QPST , CDMA WS (paid version) , and DFS . (The regular htc diag wouldn't respond to any of the commands sent to it with using the normal drivers, I will try with the ones posted but I am thinking that we really should only need to work with the 9k). Same thing applies with any htc phone of recent years, if you want acess to NV folder, create a folder called "open sesame door" in the main directory while using efs explorer in qpst or in DFS read EFS2 and create the folder. Reboot the phone and the folder will be accessible. QPST is the better option since when in DFS it doesn't show some of the key files you need to work with *cough cough*. Same HTC supercode works and cdma WS is able to find the SPC just fine. Another fun fact for people to know. The one does function for calls text and internet without the sim card , just no lte , which for some this might be helpful ( >=) ). Always some fun menus to change settings under ##3282# as well. Hope this helps some people out!
I would love to get QPST working with my Sprint HTC One. So far everything I have tried hasn't worked.
The linked drivers are corrupt for me as well (tried WinRAR and 7-Zip). Any new links possibly?
The attached files are actually HTML. I just changed the extension to "htm" and loaded it in a browser. It opens the Dropbox download page.
I'm working on the driver signing issue now.
Richard
My QPST screen
I now have the attached drivers installed. I still get exactly what I was getting with several other HTC diag drivers.
It looks like something is found, but the phone isn't recognized.
Any thoughts?
Richard
Hello i cant install the drivers since it says that the drivers are not digital signed, can some one tellme how can i install them? i already tyed the comand prompt, and other ways, but allways says that theres an error installing them... Tahnx
Thanks!
wranglerray said:
Right click on the htc diag9k driver and click on "update driver software"
select "browse my computer for driver software"
Then "let me pick from a list of device drivers on my computer"
click have disk and navigate to where you extracted the driver files
and choose Qualcomm HS-USB Android Diag 9018
Click next till it is installed and you should be ready to open qpst
you will need your msl/spc code but there is a thread on a easy way to retrieve that.
Click to expand...
Click to collapse
Thank you...
I tried the instruction exactly as posted but could not get the Diag9k drivers to work. The drivers do get installed but there is a yellow triangle showing and an error massage comes up stating that the drivers are not compatible with the device. Can somebody let me know how to install the drivers correctly?
championwaqas said:
I tried the instruction exactly as posted but could not get the Diag9k drivers to work. The drivers do get installed but there is a yellow triangle showing and an error massage comes up stating that the drivers are not compatible with the device. Can somebody let me know how to install the drivers correctly?
Click to expand...
Click to collapse
Try this
http://www.cricketusers.com/showthread.php?t=85426
Sent from my HTCONE using Tapatalk 4 Beta
I made my own driver and got full qpst... I can configure my cell and note it's working...
Sent from my HTCONE using xda premium
cciemd said:
I now have the attached drivers installed. I still get exactly what I was getting with several other HTC diag drivers.
It looks like something is found, but the phone isn't recognized.
Any thoughts?
Richard
Click to expand...
Click to collapse
Upgrade your qpst versions. Work for me
Sent from my HTCONE using xda premium
Thx its works
Yes Thx u very much now its work on my computer Macbook pro 15 windows 8 with QPST ,
cciemd said:
I would love to get QPST working with my Sprint HTC One. So far everything I have tried hasn't worked.
The linked drivers are corrupt for me as well (tried WinRAR and 7-Zip). Any new links possibly?
The attached files are actually HTML. I just changed the extension to "htm" and loaded it in a browser. It opens the Dropbox download page.
I'm working on the driver signing issue now.
Richard
Click to expand...
Click to collapse
Related
SO recently got a nexus one and for some reason i cant get it to be recognized by adb, i have tried everything, updating drivers, reinstalling adb, trying diferent usb cables, different usb ports, but for some reason no matter what i try adb doesnt recognize any device. it recognizes my atrix just fine, but not the nexus. and the nexus is also rooted and has cwm but somehow the bootloader says ship s-on. it all seems prtty wierd. any ideas?
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
baseballfanz said:
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
already tried that driver and same thing
Theshawty said:
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
Click to expand...
Click to collapse
still nothing with reinstalling
gunna try restoring stock firmware and see what happens
not even going back and flashing stck firmware will let it connect to adb
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Aceyo said:
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Click to expand...
Click to collapse
as i told the other 2, it is not a driver issue, it turns out the guy i got it from had work done on it before it was shipped, thinking something internal is the issue
I'm fairly new to android and i was wanting to root my htc vivid but it will not connect to my computer. I first plugged it in and the windows device manager installed a driver that just said unknown device. so i went and downloaded the htc sync software but even that won't recognize the vivid. I'm at a total loss and need direction.
Drivers at htc
Did you try the drivers at developer.htc.com ?
Page 4 from "Kernel Source code"
Download ADB http://developer.android.com/guide/developing/tools/adb.html
Choose Connection Type
When you connect your Vivid to the PC via the USB cable, you should see a screen asking what type of connection you want - charging only, disk drive, sync, etc. If you are not trying to actually sync data, just select disk drive and the tap the Done button at the bottom. You can then see the internal storage (and the "external" SD card if you have one installed). This can be done even if HTC Sync does not work.
If you don't see the connection type screen, go into Settings and tap on Connect to PC. Check the Ask Me box so you will be prompted the next time you plug in the USB cord.
As to HTC Sync, see my posting elsewhere in this forum about HTC Sync not working. In my opnion, it's not a very good program.
As for the driver, you may need to uninstall the driver if you can. Then uninstall and re-install HTC Sync to get the correct driver.
gubbels214 said:
I'm fairly new to android and i was wanting to root my htc vivid but it will not connect to my computer. I first plugged it in and the windows device manager installed a driver that just said unknown device. so i went and downloaded the htc sync software but even that won't recognize the vivid. I'm at a total loss and need direction.
Click to expand...
Click to collapse
I had similar issues trying to install the ICS update. Some searching lead me to this post that had just the drivers I needed.
-Brett.
I've tried the drivers from that post before and still no dice. And when I connect my phone it never asks for connection type even when I have it checked. I'm still in the same boat
Sent from my HTC PH39100 using XDA
zzoinks said:
I had similar issues trying to install the ICS update. Some searching lead me to this post that had just the drivers I needed.
-Brett.
Click to expand...
Click to collapse
Exactly what he said, Windows Vista didn't tell me any drivers were required (in charge only mode), but I had to install the XP drivers from that link before the RUU would proceed past the very first step. After I did that it worked fine.
Just unzip the drivers to a folder and when Windows tells you it can't find drivers, tell it to look there.
Ok I have the same issue but windows doesn't tell me it can't find drivers it just sits there. So how di I get it to accept the drivers?
ransack said:
Exactly what he said, Windows Vista didn't tell me any drivers were required (in charge only mode), but I had to install the XP drivers from that link before the RUU would proceed past the very first step. After I did that it worked fine.
Just unzip the drivers to a folder and when Windows tells you it can't find drivers, tell it to look there. I have the files downloaded to my root directory (Win 7)for now.
Click to expand...
Click to collapse
I found the drivers for windows by going thru the at&t website... Then once I installed the HTC sync software (yes I know it doesn't work) and ran it... It told me there was a new version... I installed that and like magic it finally knew it was there...
Sent from my HTC PH39100 using Tapatalk
HTC has new drivers that work when the old drivers did not. HTC SYNC from htc.com Load in Windows7 and they will run in the background.
read the posts above to set your phone correctly and you should be good to go. Gary
Please don't troll, my first post
So, my Nexus 7came a few days ago, and since then I've been playing around with it a lot.
Yesterday I decided I was going to root the beautiful tablet.
I plugged it into my laptop (Windows 7 64bit) and then I saw an error whilst it tried to install the drivers.
It had two crosses by the two drivers it was trying to install.
I plugged it into another laptop (Windows Vista 32bit) and it installed the drivers perfectly and quickly.
I understand that I have to have the Nexus 7 plugged in to root it, and so now I am highly confused and annoyed.
My laptop doesn't recognize it and it doesn't appear in Computer.
Any ideas?
Thanks.
If you need anymore information, just let me know! (=
Works fine for me after about 10 minutes of searching and reading. No need to add to the thread clutter.
RajanB said:
Please don't troll, my first post
So, my Nexus 7came a few days ago, and since then I've been playing around with it a lot.
Yesterday I decided I was going to root the beautiful tablet.
I plugged it into my laptop (Windows 7 64bit) and then I saw an error whilst it tried to install the drivers.
It had two crosses by the two drivers it was trying to install.
I plugged it into another laptop (Windows Vista 32bit) and it installed the drivers perfectly and quickly.
I understand that I have to have the Nexus 7 plugged in to root it, and so now I am highly confused and annoyed.
My laptop doesn't recognize it and it doesn't appear in Computer.
Any ideas?
Thanks.
If you need anymore information, just let me know! (=
Click to expand...
Click to collapse
Follow instructions in the Nexus 7 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1766475
Remember to scroll all the way down in each individual window of the guide to setting up the drivers. I drove myself crazy before I realized that I had missed something important. Also if your desktop is 64bit, you have to use the 64bit drivers. Good luck!
RajanB said:
Please don't troll, my first post
So, my Nexus 7came a few days ago, and since then I've been playing around with it a lot.
Yesterday I decided I was going to root the beautiful tablet.
I plugged it into my laptop (Windows 7 64bit) and then I saw an error whilst it tried to install the drivers.
It had two crosses by the two drivers it was trying to install.
I plugged it into another laptop (Windows Vista 32bit) and it installed the drivers perfectly and quickly.
I understand that I have to have the Nexus 7 plugged in to root it, and so now I am highly confused and annoyed.
My laptop doesn't recognize it and it doesn't appear in Computer.
Any ideas?
Thanks.
If you need anymore information, just let me know! (=
Click to expand...
Click to collapse
Have you downloaded these yet they are new out.
http://forum.xda-developers.com/showthread.php?t=1796165
Install the android sdk. Go to device manager and find your nexus, right click and update driver software. Search computer, select all locations (or something like that) then have disk and browse to your installation. Uh underneath extras there is a folder with the driver you're going to select.
I'm at work so that's a general idea, Google "cyanogenmod adb driver install" and skip the part about replacing the file with a custom one since the nexus is included by default.
Sent from my LG-P999 using xda app-developers app
mi7chy said:
Works fine for me after about 10 minutes of searching and reading. No need to add to the thread clutter.
Click to expand...
Click to collapse
Sorry. Where did you search and read apart from Google? Links please?
Ok, so I done what you guys recommended, in order of when you posted, and non of the suggestions worked.
A screenshot of what happens is attached.
Thanks.
The image didn't attach :S
Wow... user has 4 total posts, all in this one thread and saying nothing worked.
Did you try
Rock-&-Roll-Hedgehog said:
Have you downloaded these yet they are new out.
http://forum.xda-developers.com/showthread.php?t=1796165
Click to expand...
Click to collapse
That will get your the ASUS drivers which will should work on your computer.
All of the root kits also include drivers and they are not that hard to install.
krelvinaz said:
Wow... user has 4 total posts, all in this one thread and saying nothing worked.
Did you try
That will get your the ASUS drivers which will should work on your computer.
All of the root kits also include drivers and they are not that hard to install.
Click to expand...
Click to collapse
Yep. Tried that aswell... if it had worked I wouldn't of come back to ask if anyone had any other ideas as to why it doesn't work..
I thought it was possible to ask questions on here without people saying stuff like that...
clearly you are doing something wrong because the drivers work.
If you need help, you need to provide more details on what you are trying and what the issue is when you try to install... Not just an image of what happens when you plug the device in. That part is obvious that you don't have the drivers installed.
So of the various methods of getting drivers, which ones did you try and what did they say when you tried loading them?
krelvinaz said:
clearly you are doing something wrong because the drivers work.
Click to expand...
Click to collapse
Ok, let me run you through what I'm doing here...
I opened up the zip containing the files.
These are the files that I am greeted with;
amd64
i386
android_winusb
androidwinusb86
androidwinusb64
source.properties
Now what? (=
Those are the drivers... now you need to load them.... Not using Vista for many years... did a simple google search and found...
Code:
Windows Vista
To install the Android USB driver on Windows Vista for the first time:
Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
Select Locate and install driver software.
Select Don't search online.
Select I don't have the disk. Show me other options.
Select Browse my computer for driver software.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.) As long as you specified the exact location of the installation package, you may leave Include subfolders checked or unchecked—it doesn't matter.
Click Next. Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
When Vista asks if you'd like to install the Google ADB Interface device, click Install to install the driver.
Or, to upgrade an existing Android USB driver on Windows Vista with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane.
Locate and expand ADB Interface in the right pane.
Right-click on Listed Nexus 7 Device, and select Update Driver Software.
When Vista starts updating the driver, a prompt will ask how you want to search for the driver software. Select Browse my computer for driver software.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.) As long as you specified the exact location of the installation package, you may leave Include subfolders checked or unchecked—it doesn't matter.
Click Next. Vista might prompt you to confirm the privilege elevation required for driver installation. Confirm it.
When Vista asks if you'd like to install the Google ADB Interface device, click Install to upgrade the driver.
Change the location in the instructions to where you unloaded those USB drivers and you should be on your way...
Try pdanet drivers, just Google pdanet install the proper one(can't remember if they have a 32 bit or 64 bit)
I used their drivers to root the n7. If they don't have asus drivers just.click I don't know. Don't remember exactly the installation step by step, but.its easy enough to get through
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Try pdanet drivers, just Google pdanet install the proper one(can't remember if they have a 32 bit or 64 bit)
I used their drivers to root the n7. If they don't have asus drivers just.click I don't know. Don't remember exactly the installation step by step, but.its easy enough to get through
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Tried that. It all installed correctly, it just won't show up in Computer so I can view my files.
I have unlocked my bootloader... if that helps, which means that Nexus Root Kit 1.5.2 can detect that the Nexus 7 is plugged in.
RajanB said:
Tried that. It all installed correctly, it just won't show up in Computer so I can view my files.
I have unlocked my bootloader... if that helps, which means that Nexus Root Kit 1.5.2 can detect that the Nexus 7 is plugged in.
Click to expand...
Click to collapse
So your having an issue with mtp stuff. Go into setting then click on storage then hit the three dots on the top right corner. Just make sure media device is checked.
Reboot the computer and try a different USB port. These are just so basic steps just do that and see what happens
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
So your having an issue with mtp stuff. Go into setting then click on storage then hit the three dots on the top right corner. Just make sure media device is checked.
Reboot the computer and try a different USB port. These are just so basic steps just do that and see what happens
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ok. Done all that, still the same.
And it now comes up with what you can see in the attached image.
RajanB said:
Sorry. Where did you search and read apart from Google? Links please?
Click to expand...
Click to collapse
search and read the same forums you posted your question in. try the nexus 7 development forum to start.
Sent from my Nexus 7 using xda premium
RajanB said:
Ok. Done all that, still the same.
And it now comes up with what you can see in the attached image.
Click to expand...
Click to collapse
ok seriously..... search these forums for nexus root toolkit 1.5. install that and follow the prompts for installing drivers
Sent from my Nexus 7 using xda premium
uberNoobZA said:
ok seriously..... search these forums for nexus root toolkit 1.5. install that and follow the prompts for installing drivers
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The driver he is having issues with is mtp. This might be a windows error.
I sent you a pm OP
Sent from my Nexus 7 using Tapatalk 2
Am I the only person having trouble with having a computer recognize the phone? The driver install fails. I have tried different computers and different cables. The computer knows that it is there but I cannot use chainfires auto root because I keep getting a message that says please connect via usb cable, which it already is. Can somebody please help?
I had the same problem
I guess I can't post URLs yet so take the space out between http and : below.
Then manually install the driver. The only way I could get my phone to connect in bootloader
Here is the link to Nexus 6
http ://developer.android.com/sdk/win-usb.html#
So frustrated,
McRiderGeek said:
I guess I can't post URLs yet so take the space out between http and : below.
Then manually install the driver. The only way I could get my phone to connect in bootloader
Here is the link to Nexus 6
http ://developer.android.com/sdk/win-usb.html#
Click to expand...
Click to collapse
I tried to follow the directions to the T but am still having trouble and do not know what I am doing wrong. I was so excited to finally get my hands a Nexus device and am having more trouble with this phone than any other that I have previously owned. At this point, Id be happy to keep my Note 4 is somebody could come up with a root. I wonder if it could be because I am on a computer at work that is on a network?
Domain rights
If you login to a network computer the domain user rights may have a group policy to not allow driver installation.
On my computer I right click computer and go to manage
Click on "device Manager"
My device showed up under unknown or other device it was named shamu
Right click on shamu and choose update driver software
Then choose browse my computer for driver software
Click the browse button and find the folder you downloaded from the link on the previous post and pick the usb_driver folder and click OK then click next
It should then install the driver if you have permissions on that computer to install drivers
These steps are for Windows 7
O had a similar issue. Drivers installed but the device was never seen. In device manager is was listed as like an altec or something..
I did right click, update driver, then install from computer, pick from list. From the list I just chose the USB composite device. Boom solved for me.
Sent from my Nexus 6 using XDA Free mobile app
perseverance!
McRiderGeek said:
I guess I can't post URLs yet so take the space out between http and : below.
Then manually install the driver. The only way I could get my phone to connect in bootloader
Here is the link to Nexus 6
http ://developer.android.com/sdk/win-usb.html#
Click to expand...
Click to collapse
Holy ****! I was expecting to have this thing rooted in about 2 minutes! Only took two days!!! Thanks for the help.
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.