I've Google'd the topic and all the comes up are my own post in the Dev sections where I asked how to create/get a logcat. I can "adb logcat" to a text file, then it shows "waiting for device". Now what's the procedure or setup on the S7 end? I've turned On adb debugging options in the S7. Can/ls this done by USB? The "adb devices" command while plugged into the USB shows nothing. I can connect in Fastboot mode and "adb devices" shows nothing also. Or is more of the Android SDK package needed for this?
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
giveen said:
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, since I've never used adb commands in the past, maybe not! Are they installed from a EXE file or in a INF fashion?
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
giveen said:
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
Click to expand...
Click to collapse
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
wptski said:
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
Click to expand...
Click to collapse
Um....no?
http://d-h.st/592
giveen said:
Um....no?
http://d-h.st/592
Click to expand...
Click to collapse
Yep, that's a link to the page but where's a link to actual file download? I think the third comment on the page mentions this.
If I'm not missing the driver files, I wonder if it might be that I NVflashed CM10 again but didn't allow it to reboot before restoring a TWRP backup?
All the old links to files have been changed since the DNS problems but I found a link to the old files at StreakDroid and the DNS issued is fixed. Download, unzipped, nothing looks any different to what I already have. I still tried the package anyway and it still can't find it's driver. Next I'm going to NVflash CM10 again and let it boot up fully and try it then before restoring my TWRP backup.
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
jamezz98 said:
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
Click to expand...
Click to collapse
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
wptski said:
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
Click to expand...
Click to collapse
Its because I was testing some things out in init.streak7.usb.rc
giveen said:
Its because I was testing some things out in init.streak7.usb.rc
Click to expand...
Click to collapse
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
wptski said:
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
Click to expand...
Click to collapse
It works just fine.
I'm stumped!
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
wptski said:
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
Click to expand...
Click to collapse
Restored my ICS-B4 backup, ran into the exact same issue and used the same solution to install the ADB drivers.
Related
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
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
Ouya SuperScript
By TehCrucible
v0.1
INTRODUCTION
So I originally wrote this batch script to simplify and combine some of the most frequently used tweaks on the forums for my own sake, to speed up my tinkering with the Ouya but I've decided to clean it up and upload it in case anyone else wants to use it.
This script is designed as a "one-click" modification tool for a stock Ouya on the latest firmware. Please read this guide carefully.
I ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSS. This script is built on the work of many others much smarter than myself and be sure to check the credits.
SO WHAT DOES IT DO?
In a nutshell:
- Install Clockworkmod Recovery
- Root Ouya
- Install Xposed Framework
- Install Google Play Store
WHAT DO I NEED?
- A Windows PC. I have included drivers for both x86 and x64.
- A Micro USB cable.
INSTALLATION OVERVIEW
1. Update your Ouya to latest stock firmware
2. Install ADB drivers
3. Run the script
4. Play some games!
There's a more detailed step-by-step in the included README.txt file.
KNOWN ISSUES
- None
CREDITS & THANKS
WonderEkin
mybook4
elmerohueso
fatesausage
DOWNLOAD
Here
Thanks a lot for this. A lo of people have been asking about an automated method to get the play store running on the OUYA...
Great works. I just think of root my ouya....
A quick update:
It's working. I'm on the latest firmaware which is JZO54L-OUYA, kernel version 3.1.10-g780994a. Completely stock, but I had already rooted my OUYA.
Anyway, I enabled the Wireless ADB which will instantly show you the ip and port, installed the drivers for 64bit. Then open CMD and type: adb connect "iport"
Then I ran the superscript and everything went fine.
Hope this helps. I didn't even have to connect with a wire.
But I guess if you wanna install the CWM recovery you should be connected with a wire...
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
Did you install the drivers right? If yes, then you should open the folder where you extracted your files and right click while holding shift then choose open CMD here. Then write: adb devices
If your device is there, it will give you an output of the IMEI and name of device
From there, you can then tell us what the error is and hopefully we can resolve it...
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
that happened to me yesterday, but I overcame it by have my computer plugged into the Ouya then reboot the ouya and as soon as the computer recognized it started the script and it worked.
but I have an issue too
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesnt recognize the ouya....
unkoil said:
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
Click to expand...
Click to collapse
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
TRMB said:
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesn't recognize the ouya....
Click to expand...
Click to collapse
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.[/QUOTE]
I have tried both from my windows 7 computer and 8.1 laptop. It showed up just as you said "missing driver", sent it to the drivers part of SS to get the driver, it said it installed but when i run the SS and hit option "1" it comes up blank...
ahmadshawki said:
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
I am having the same issue but not only with this method, I have also tried to install CWM with oneclicks auto and manual method to no avail.....
any suggestions?
Click to expand...
Click to collapse
always says it installed but will only boot into stock recovery
TRMB said:
always says it installed but will only boot into stock recovery
Click to expand...
Click to collapse
I can see from your posts that you tried everything and I'm so sorry that I'm just a user and not a developer or something. May be you can try sideloading terminal and try CWM manually (if you haven't already) or sideload ROM Toolbox and try the flash recovery option.
That's all I got. But if I were you, I won't bother about the CWM at all. It's useless.
As for the Play store, try the mod that I attached in my reply and let me know if this one works for you...
Unfortunately the link is not working. Is it possible to update it, please?
What I do if my micro usb is broken :/. I only have wireless adb
.. nice .. now my ouya will run again .. thanks
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
vinirockman said:
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
Click to expand...
Click to collapse
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
vinirockman said:
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
Click to expand...
Click to collapse
.. CWM need wired usb keyboard no navigate .. i don't remember if it can do it via bluetooth
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.
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
laticola said:
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
Click to expand...
Click to collapse
You should download the official Google drivers.
elong7681 said:
You should download the official Google drivers.
Click to expand...
Click to collapse
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Which version of platform-tools do you have? You should only be using v33.03. I would also encourage you to use the Pixel Flasher Thread 'PixelFlasher for Google Pixel 7 Support Thread.' https://forum.xda-developers.com/t/pixelflasher-for-google-pixel-7-support-thread.4505289/
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
I suggest you follow the advice I gave and the other member ended up doing quoted below from another thread (his experience is fairly similar to yours and/or achieving the same things would get to the same end result -- might be worth reading through the whole thing) -- it seemed to work out for him...
simplepinoi177 said:
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Click to expand...
Click to collapse
GodieDan said:
SOLVED! thanks especially to @simplepinoi177 for cracking the case!
In case someone has this same problem in the future, here's the solution:
1. Open device manager and locate the misbehaving driver. If it's not obvious, plug and unplug the USB cable and watch for the appearing and disappearing entry.
2. Right-click the driver > click properties from the drop-down menu > select the driver tab > driver details
3. To be safe, use the snipping tool or something to take a picture of the file directories. Before you change anything in a system file it's always good to keep a record of how things were, but also you'll need to know the directories for the next step.
4. Unplug the device from the computer. As the directory list vanishes, use the screenshot to locate the .dll files.
5. Again to be safe, don't just delete the .dll files; instead just cut and paste into a backup folder somewhere. Also save the screenshot of the directories in the same folder, so you will know where to put them back if you need to. I didn't, and who knows, maybe I could be overcautious, but best practices and whatnot
6. Open device manager and again plug your android in. This time the driver will probably have a different name. Locate it as you did in step 1.
7. Right-click and select "uninstall device." Tick the box and say OK
8. Unplug the phone and reboot the phone and the computer both
9. Plug it back in
I have also determined the cause of my problem: Drive Booster, a program designed to automatically update drivers. It's not an unsafe program, but it is bad at installing the correct driver. I uninstalled it.
Thanks again!
Click to expand...
Click to collapse
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Why do you think fastboot and recovery are the same? I haven't been in recovery for a bit but fastboot is available once connected to the computer but is recovery mode supposed to as well? Don't make me go into recovery mode please. But I thought recovery mode was device only.
I'm using platform tools v34.0.1, and I worked through the steps simplepinoi177 suggested for the drivers. I then discovered that my problem was something very basic: I was mistakenly using files for a Pixel 7 Pro instead of a Pixel 7 (my actual device). Once I flashed the correct boot, dbto, and recovery for my device, I was fine.
Apologies for the error, and thanks so much for the help. You all rock! And I will read up on Pixel Flasher.