Related
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.
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Raistlin1158 said:
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Click to expand...
Click to collapse
Thanks for the quick reply.I did that and it was set to mtp + adb...
When I then connected it it tried installing the driver and I got..
Driver device software was not installed.
Please consult with your device manufacturer for assistance getting this device installed
MTP USB Device X Failed
I tried updating the MTP drivers again from device manager but this time got
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
SAMSUNG Mobile MPT Device
This device cannot start (code 10)
From what I'm reading it's a computer error not the phone. Can anyone suggest a new set of drivers to download (that doesnt involve Kies) as I've had issues with picking up harmful software from random sites when I've been struggling to find drivers.
I tried using the suggestion at the bottom of here r.e.Portable Devices and deleting the Upperfilters string Link but also to no avail.
Oh, and yes I've tried different ports and cables.
Well that's me done for the evening! I've tried everything mentioned in this thread including updating java and windows media player and all the afformentioned stuff but still no dice.
Could it be the actual drivers or a random windows 7 setting that I haven't yet tweaked since my clean install of windows??
http://d-h.st/YpV
Here are the correct drivers, install then reboot your pc.
Raistlin1158 said:
Go here for drivers.
---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------
http://d-h.st/YpV
Here sre the correct drivers, install then reboot your pc.
Click to expand...
Click to collapse
Sorry,I know I'm tired but I can't see a link on your post...
Highlighted in red
The newer drivers don't really wwork with the 9305 so find some older drivers. That works for me
Sent from my GT-I9305 using xda app-developers app
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
woldranger said:
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
Click to expand...
Click to collapse
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
Cheers, yeah, I was going to try them but I wasn't at my pc at the time I wrote that. I've downloaded the exe package but now it seems there are still drivers to uninstall - I uninstalled the drivers through device manager and went into my C drive and removed the SAMSUNG folder with the USB drivers in it. I'll restart the pc and hope that helps with the removal....
woldranger said:
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Click to expand...
Click to collapse
Having the same problem. but I am on 4.3 rom using carbon rom a few days then transferred to pac man rom. My cellphone is not detected in my computer but it is being detected in the safely remove usb options. I tried to use a usb otg cable and a flash disk. No notification is seen on my phone but I can access the files on the flash disk (using usb otg cable) in the file manager. Tried the *#7284# but error occurs and says connection problem or invalid MMI code. I found that MTP udb device says failed
Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
woldranger said:
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
Click to expand...
Click to collapse
Just got the same problem. But my problem is already solved. Just flash a new rom. In my instance, I flash ripper rom
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'm not to sure what to call this problem exactly but i'll explain it to the best of my ability. Recently on my HTC One (m7), which I bought from HTC website. I've been having problems moving files from my phone to PC. I used to transfer all my music files easily but now I get this error message saying " A device attached to the system is not functioning ". Also when I try to paste music files or folders my computer tab freezes up. My phone works perfectly fine, there seems to be nothing wrong with it. There is a system update that won't complete on my phone. I'm pretty sure the update has nothing to do with this problem but then again I don't completely know. My phone is rooted. I have clockworkmod touch & SuperSU. I am unsure what to do as I need to copy my music files so if something happens to go wrong with my phone, I have backups. If anyone has a solution to this problem it would be extremely helpful and greatly appreciated.
lnfamous313 said:
I'm not to sure what to call this problem exactly but i'll explain it to the best of my ability. Recently on my HTC One (m7), which I bought from HTC website. I've been having problems moving files from my phone to PC. I used to transfer all my music files easily but now I get this error message saying " A device attached to the system is not functioning ". Also when I try to paste music files or folders my computer tab freezes up. My phone works perfectly fine, there seems to be nothing wrong with it. There is a system update that won't complete on my phone. I'm pretty sure the update has nothing to do with this problem but then again I don't completely know. My phone is rooted. I have clockworkmod touch & SuperSU. I am unsure what to do as I need to copy my music files so if something happens to go wrong with my phone, I have backups. If anyone has a solution to this problem it would be extremely helpful and greatly appreciated.
Click to expand...
Click to collapse
It sounds like you need to update your drivers ~ read thru nkk71's post #2
The reason the OTA will not complete is it is looking for the stock recovery and you have a custom recovery installed.
majmoz said:
It sounds like you need to update your drivers ~ read thru nkk71's post #2
The reason the OTA will not complete is it is looking for the stock recovery and you have a custom recovery installed.
Click to expand...
Click to collapse
My drivers for my HTC One are fully up to date and this problem still exists. It just happened a few days ago, before that it was transferring files normally.
lnfamous313 said:
My drivers for my HTC One are fully up to date and this problem still exists. It just happened a few days ago, before that it was transferring files normally.
Click to expand...
Click to collapse
This definitely sounds like a driver problem, they may be up to date but that doesn't mean they are installed correctly.
Check your Device manger on your pc while the phone is connected to your usb, in device manger your phone should be listed as "MY HTC" if it's not see the post linked by @majmoz
It's not uncommon for this to happen especially if you frequently connect your phone to different usb ports on your pc.
Danny201281 said:
This definitely sounds like a driver problem, they may be up to date but that doesn't mean they are installed correctly.
Check your Device manger on your pc while the phone is connected to your usb, in device manger your phone should be listed as "MY HTC" if it's not see the post linked by @majmoz
It's not uncommon for this to happen especially if you frequently connect your phone to different usb ports on your pc.
Click to expand...
Click to collapse
Ok I checked my device manager, but I'm confused. I tried to change it but it still isn't working in fact it works worse now. I uninstalled the drivers & re-installed them, which also didn't help me much. I checked the majmoz gave me, and I tried to download an earlier version of drivers but it said they were already installed and blocked me from installing. I'm not quite sure what to do now.
lnfamous313 said:
Ok I checked my device manager, but I'm confused. I tried to change it but it still isn't working in fact it works worse now. I uninstalled the drivers & re-installed them, which also didn't help me much. I checked the majmoz gave me, and I tried to download an earlier version of drivers but it said they were already installed and blocked me from installing. I'm not quite sure what to do now.
Click to expand...
Click to collapse
You need to uninstall the drivers from Control Panel > Program & Features then reboot the computer. Now install the drivers again.
lnfamous313 said:
Ok I checked my device manager, but I'm confused. I tried to change it but it still isn't working in fact it works worse now. I uninstalled the drivers & re-installed them, which also didn't help me much. I checked the majmoz gave me, and I tried to download an earlier version of drivers but it said they were already installed and blocked me from installing. I'm not quite sure what to do now.
Click to expand...
Click to collapse
Try this, Linux will eliminate any driver issues. :good: http://forum.xda-developers.com/showthread.php?p=54272479
lnfamous313 said:
My phone is rooted. I have clockworkmod touch & SuperSU. I am unsure what to do as I need to copy my music files so if something happens to go wrong with my phone, I have backups. If anyone has a solution to this problem it would be extremely helpful and greatly appreciated.
Click to expand...
Click to collapse
Maybe there is an issue with the internal storage.
If you can install the terminal emulator app, you could try to rewrite /data/media/0
In Terminal Emulator type:
su
restorecon -FR /data/media/0
Than reboot and see if it was helpfull.
I have had issues like this before. While the phone is booted as normal and plugged into pc, go into developer options and disable and then re-enable usb debugging.
Sent from my HTC One using XDA Free mobile app
/data/media/0
NLBeev said:
Maybe there is an issue with the internal storage.
If you can install the terminal emulator app, you could try to rewrite /data/media/0
In Terminal Emulator type:
su
restorecon -FR /data/media/0
Than reboot and see if it was helpfull.
Click to expand...
Click to collapse
Ok, I did some problem solving and eliminated some possible problems. It's definitely not the security on my phone, and all my drivers work properly. But I found that on my phone there is not a file called /data/media/0. I think it might have somehow got deleted but I'm not sure. Does anyone know how to get an extra copy of this file?
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.