Related
Now I know your first thought “I bet this tool didn’t even use Search like the rest of the shlubs on here”. Well you are mistaken. I have not only searched xda but even tried Google and Yahoo (just in case) as well. I have found numerous posts (like HERE and HERE and many others) with similar situations but haven’t seen a resolution. Here is the rundown:
Running JF’s 1.5 CRB21 ROM
Hard SPL (HSPL10.95.3000)
JF’s 1.43 Recovery Image
SDK 1.5_r1
Fastboot.exe placed in System32
Haykuro’s Updated Drivers placed in System32
Windows XP 2002 SP3
I have been able to flash nandroid backups without issue in the past but adb started intermittently not recognizing my phone when I flashed from JF’s RC33 to JF’s 1.5. I was able to restore a backup once but now adb will not recognize my phone at ALL. Tried different USB plugs and cables with no result. If I mount the phone to view the SD card via Windows Explorer it shows as “HTC Dream Composite ADB Interface” in Device Manager. However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order. I have deleted my SDK and drivers and re-downloaded/installed them and STILL cannot get adb to connect. It has to be something simple I am missing here right? Any idea why this would have worked without issue in the past and now not at all? Could it have been a Windows Security update? (That's about the only thing I can thing that has changed other than the newer ROM)
Thank you for your help.
Did you update you USB Drivers or try reloading them?
Also.... Settings > Applications > Development > USB debugging has to be checked....
and stop being a tool.
nah im jk.
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
gPhunk said:
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Click to expand...
Click to collapse
Repent .. Repent..
Did reloading the USB Driver work?.. Did for me =)
billc.cn said:
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
Click to expand...
Click to collapse
How do I know which one to install? (I am running Vista Home Premium 32bit)
Thank you for your help
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
ubernicholi said:
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
Click to expand...
Click to collapse
Thanks man - I was able to install the drivers but am still unable to view my device. It shows as "HTC Dream" in Device Manager but when I run "adb devices" in the command line, it yields a blank list. Further commands (I.e. adb shell) say "cannot find device. Running fastboot commands result in "waiting on device". This happens on both my laptop and my home pc so I am beginning to think it's the phone. Should I have something loaded on the phone? I have USB Debugging checked so that's not it. Any ideas?
possibly the problem is that ADB does not work in Bootloader mode, it is designed to work while the phone is running.
However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order.
Click to expand...
Click to collapse
Yuo are obviously trying this in bootloader mode, underline for emphasis.
try >fastboot devices
see if that shows you your phone
Otherwise try ADB while in the OS already.
I've finally getting around to rooting my x10a, but I'm having a problem with step2.cmd. It echos it's schpeel that select option 6 or whatever, without any error (except for the normal "device not found"). I know that it's supposed to come up with a screen that you should select the 6th option on, but it's not showing up!
If anyone is wondering I do have USB debugging on and I have installed all the drivers.
EDIT: I did include the deviceid txt files inside both of the folders.
Actually, "device not found" is NOT normal. It shouldn't say that if it's working properly.
Steps 2 and 3 (and 5 for X10a) use ADB. There are a few things to check (I'll list everything I can think of, including ones you may have already done):
1. ADB doesn't require DeviceID.txt (it's for X10Flash), so it's not that.
2. Make sure USB Debugging is enabled on the phone (under Settings > Applications > Development).
3. Unplug the USB cable and plug it back in. On the phone, the notification bar should show "USB debugging enabled".
4. Make sure that the SD card is NOT mounted to your PC. The notification should show "USB connected", NOT "Turn off USB". If it does say "Turn off USB", then click it to turn it off.
5. In Windows, double-click on the Safely Remove Hardware icon in the system tray. There should be a device called "adb01 ADB Interface Driver". Don't remove it, just make sure it's there. Hit Cancel/Close.
6. Open Task Manager (Ctrl-Alt-Del) and look for a process called "adb.exe". Click it and hit "End Process". Next time you start adb, it should load up the daemon again.
7. Have you tried rebooting your PC? How about your phone?
8. ADB connects using TCP. If you have a software firewall (e.g. ZoneAlarm, Eset Smart Security, etc.), it may be blocking access. Either make an exception, or just disable the firewall for now (don't forget to turn it back on later). No, a router doesn't count (the phone is connected through USB, not your network).
9. There may be a problem with your Sony USB drivers. Uninstall Update Service and PC Companion (if you have them), reinstall them, and then plug in your phone again so that the drivers are reinstalled. I had to do this to fix a different problem (that second USB Mass Storage device kept connecting and disconnecting).
Did you allow unknown sources?
Sent from my X10a using XDA App
Grospolina said:
5. In Windows, double-click on the Safely Remove Hardware icon in the system tray. There should be a device called "adb01 ADB Interface Driver". Don't remove it, just make sure it's there. Hit Cancel/Close.
Click to expand...
Click to collapse
I've done everything but that, which is not there, what should I do about that?
You know what, the laptop I'm using right now really sucks in the spec department, so it might just be that. Is there anyway to reflash it to rogers x10a?
is your laptop using vista 64? If it is follow this post to fix it. http://forum.xda-developers.com/showthread.php?t=713457
to get through step2, i had to install sony ericsson pc companion, it has the drivers which step2 depends on
carmatic said:
to get through step2, i had to install sony ericsson pc companion, it has the drivers which step2 depends on
Click to expand...
Click to collapse
You are a freaking life-saver, going to try that now.
Mod. edit: not dev related, moved to general
When I connect my Nexus 7 to my Windows XP (SP3) PC via USB, it's obvious the computer recognizes it and it tries to install ADB drivers. Whether I choose to install those drivers or not, I still can't locate my device in the Windows Explorer Tree. I checked Disk Management for the hell of it and nothing but my PC's harddrives were there. There's an attempt to install drivers for "MTP" but that fails and I'm pretty sure that's the cause; however, I'm unable to replicate it, even as I uninstall/reinstall applicable drivers from the device manager the MTP failure never happens anymore. I did some googling and found a thread with someone who had a similiar experience. In turn, I downloaded https://www.box.com/s/2c25e8bc42ecce400afd to try a different set of drivers. Same problem. Driver install is fine for ADB, but still unable to see my device in Windows Explorer. I'm able to successfully connect the device to the PC with PTP for the camera. I can access DCIM and cache which can serve as a work around, but I'm hoping you can provide any ideas you might have. Thank you!
edit - ***resolution***: Ok, I figured it out...I had to disable USB debugging. I don't know if this helped either, but I installed these drivers as an alternative to the drivers that were originally installed: https://www.box.com/s/2c25e8bc42ecce400afd
While connected to PC, I switched to PTP mode because I was about to give up and just use that
I then disabled usb debugging and switched back to MTP at which point the drivers successfully installed and I could now view my device in Windows Explorer. I also believe downloading the drivers in the link above helped since the first crack I took at this was unsuccessful with existing drivers.
install pdanet on pc and it will install drivers for u so it will be recognized
Ok, I figured it out...I had to disable USB debugging. I don't know if this helped either, but I installed these drivers as an alternative to the drivers that were originally installed: https://www.box.com/s/2c25e8bc42ecce400afd
Been battling with this on my XP machine since yesterday. I couldn't even get debugging to work until I installed NakedDriver. And even still, there seems to be no way to get MTP to work without turning debugging off. On my Win7 machine everything worked perfectly, both ADB and MTP, right out of the box. I have the Galaxy Nexus drivers installed on both machines (which I've read are compatible with the N7). I also have the latest version of Windows Media Player (I've read that some older versions have issues with MTP). Is anyone else able to run ADB and MTP on XP?
*edit*
A: Does PDAnet let you use MTP and ADB simultaneously? Because I really don't want to install it if I don't have to. I got rid of it ages ago (too many things starting up at boot time).
B: I have a Galaxy Nexus also, and I have no issues on the XP box.
I wouldn't bother with MTP, it's not always showing the contents of the internal storage properly when viewed in Windows Explorer.
Earlier today when I was trying to set up a backup profile for it, it didn't copy all the files off. On closer inspection I found folders like TitaniumBackup to be completely empty, which is not true according to ES File Explorer on the tablet.
I tried connecting MTP again, with USB Debugging on and off but this made no difference. Also I'm only seeing the Notifications folder instead of 36 folders on the internal storage now, really random how it's working.
asus site now has a usb driver for N7
try that
Nordendorf said:
asus site now has a usb driver for N7
try that
Click to expand...
Click to collapse
Updated with ASUS drivers, still doesn't view internal storage fully.
Salty Wagyu said:
Updated with ASUS drivers, still doesn't view internal storage fully.
Click to expand...
Click to collapse
Same here. No change with the Asus drivers. Still can't use MTP when ADB is turned on.
poo. how do I transfer my audiobooks to this stupid device without working drivers?
1. Please disconnect Nexus7
2. Remove drivers on PC.
3. Toggle ON : Settings->Wireless&Networkings->More->NFC.
4. Re-connect device
Good luck !
GotLoveForAll said:
poo. how do I transfer my audiobooks to this stupid device without working drivers?
Click to expand...
Click to collapse
1. Uncheck MTP, check the one next to it (Camera)
2. Unplug USB
3. Turn off USB Debugging (Uncheck it)
4. Plug in USB
5. Should say connected as camera, then a new window will pop-up allowing you to see your files.
Tell me if it works!
im having trouble too, is there any way to make the device to be recognised as a flash drive?
Internal memory partly invisible from Windows 7 Explorer
Salty Wagyu said:
I wouldn't bother with MTP, it's not always showing the contents of the internal storage properly when viewed in Windows Explorer.
Earlier today when I was trying to set up a backup profile for it, it didn't copy all the files off. On closer inspection I found folders like TitaniumBackup to be completely empty, which is not true according to ES File Explorer on the tablet.
I tried connecting MTP again, with USB Debugging on and off but this made no difference. Also I'm only seeing the Notifications folder instead of 36 folders on the internal storage now, really random how it's working.
Click to expand...
Click to collapse
Same observation here (a few months later) on stock Android 4.1.1 rooted.
It seems that new files in the internal memory remain invisible for a long time, but so far they have become visible eventually, sometimes a day or two later. I have no clue what could possibly cause this, and I have not found any trick or workaround that makes them visible, not even rebooting. Any hint is welcome.
SE4GT said:
1. Uncheck MTP, check the one next to it (Camera)
2. Unplug USB
3. Turn off USB Debugging (Uncheck it)
4. Plug in USB
5. Should say connected as camera, then a new window will pop-up allowing you to see your files.
Tell me if it works!
Click to expand...
Click to collapse
Didn't work. Just shows up as a camera with the limited folder access one would expect.
Workaround
I now use the following workaround.
Install SDrescan from Google Play.
Run it.
If you already had your phone connected to a computer as a media device (MTP) and are watching the contents of your SD card or internal memory in Windows Explorer, press F5 to refresh your view. If not, connect it now.
I'd be curious whether this works for you as well. If it does, press the THANKS button below.
Same issue with an old ibm x40 udated to windows xp pro SP3.
I've installed mtp driver, without success
I've "tried" to install asus driver, without success
I've tried to do as above with the help of the nexus toolkit, without success.
Everytime, the laptop recognize the device as android ADB interface.
Someone could help me?
Thank you in advance
mistershark said:
Everytime, the laptop recognize the device as android ADB interface.
Click to expand...
Click to collapse
Disable USB debugging in your phone.
Same problem with my moto xoom...files not showing in MTP using windows xp...still have not found any solution
hgmichna said:
Disable USB debugging in your phone.
Click to expand...
Click to collapse
+1 have to toggle USB debugging in winXP
hgmichna said:
I now use the following workaround.
Install SDrescan from Google Play.
Run it.
If you already had your phone connected to a computer as a media device (MTP) and are watching the contents of your SD card or internal memory in Windows Explorer, press F5 to refresh your view. If not, connect it now.
I'd be curious whether this works for you as well. If it does, press the THANKS button below.
Click to expand...
Click to collapse
It works! THANKS A LOT!!!
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto
Anyone else with problems seeing the storage after plugging into PC? adb command works and device drivers installed. Found another forum where turning the usb from MTP to charging and back under developer options does the trick. I have a non stock ROM and seeing if fresh out of the box experiences the same thing.
I have the same issue and can't seem to figure out how to get it to work. My work around has been to use ES File Explorer and open Remote Manager.
Edit: I just plugged it in again to see what I can find. I turned off USB Debugging and Developer Options. Plugged in and pulled the notification bar down, there is an option to change USB Settings to Charging, Power Supply, File Transfers (this works), Photo Transfer and MIDI. Give it a go!
rramey23 said:
I have the same issue and can't seem to figure out how to get it to work. My work around has been to use ES File Explorer and open Remote Manager.
Edit: I just plugged it in again to see what I can find. I turned off USB Debugging and Developer Options. Plugged in and pulled the notification bar down, there is an option to change USB Settings to Charging, Power Supply, File Transfers (this works), Photo Transfer and MIDI. Give it a go!
Click to expand...
Click to collapse
I am running to the exact same problem.
I have tried with USB Debugging off AND on, still no go. I think there's a problem with installing the drivers. Whenever I check the device manager, it still says the drivers weren't installed. I have tried installing the Google drivers. What do we do?!
Kandydish said:
I am running to the exact same problem.
I have tried with USB Debugging off AND on, still no go. I think there's a problem with installing the drivers. Whenever I check the device manager, it still says the drivers weren't installed. I have tried installing the Google drivers. What do we do?!
Click to expand...
Click to collapse
Need to get the drivers to install first and foremost. Even with USB Debugging on, I'm still able to pull down and change from charge only. Those drivers are key. I had to restart my computer before it was able to take the install.
rramey23 said:
Need to get the drivers to install first and foremost. Even with USB Debugging on, I'm still able to pull down and change from charge only. Those drivers are key. I had to restart my computer before it was able to take the install.
Click to expand...
Click to collapse
I'm able to get to the pulldown and change the setting from charging to MTP. Every time I do that, I get a window showing that I'm installing the drivers for Nexus 6P. Then it completes. I can do this over and over again. In the device manager, there's a little exclamation mark by the Nexus 6P and says these drivers weren't installed Code 28. I have exhausted Google to no avail!
Anyone find a solution to this?
Kandydish said:
I'm able to get to the pulldown and change the setting from charging to MTP. Every time I do that, I get a window showing that I'm installing the drivers for Nexus 6P. Then it completes. I can do this over and over again. In the device manager, there's a little exclamation mark by the Nexus 6P and says these drivers weren't installed Code 28. I have exhausted Google to no avail!
Anyone find a solution to this?
Click to expand...
Click to collapse
You chose to install the drivers manually instead of having the system do it for you? Right click the yellow exclamation .. update drivers .. allow me to pick .. choose the download file location see what that gives you.
zosimov21 said:
You chose to install the drivers manually instead of having the system do it for you? Right click the yellow exclamation .. update drivers .. allow me to pick .. choose the download file location see what that gives you.
Click to expand...
Click to collapse
When I choose the location, I see a bunch of options. The most relevant ones are ADB Interface and Android Device. Under Android Device there are several more options such as Android Adapter Interface, Android Bootloader Interface, and the such; no mention of MTP.
Kandydish said:
When I choose the location, I see a bunch of options. The most relevant ones are ADB Interface and Android Device. Under Android Device there are several more options such as Android Adapter Interface, Android Bootloader Interface, and the such; no mention of MTP.
Click to expand...
Click to collapse
Did you already download the google USB drivers?
Should just be able to choose the android_winusb.inf driver. It should allow MTP
zosimov21 said:
Did you already download the google USB drivers?
Should just be able to choose the android_winusb.inf driver. It should allow MTP
Click to expand...
Click to collapse
I have downloaded them. How do I specifically choose just that file? When I go through updating the driver, it asks for a folder location.
Go to dev options, switch the USB from ptp back to mtp and it works for me
xxsashixx said:
Go to dev options, switch the USB from ptp back to mtp and it works for me
Click to expand...
Click to collapse
Tried. Keeps trying to install the MTP drivers and it won't go through.
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
bartendersimon said:
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
Click to expand...
Click to collapse
I don't have any other drivers from any other devices. This is a clean install of Windows 8.1. I've only tried connecting my 6P, my OG 6, and my 9. All have the exact same problem.
Kandydish said:
I don't have any other drivers from any other devices. This is a clean install of Windows 8.1. I've only tried connecting my 6P, my OG 6, and my 9. All have the exact same problem.
Click to expand...
Click to collapse
You might wanna try installing Huawei Drivers and see if that help
HiSuiteSetup_2.3.55.1.zip
http://download-c.huawei.com/downlo...loadId=16205&version=90864&siteCode=worldwide
bartendersimon said:
You might wanna try installing Huawei Drivers and see if that help
HiSuiteSetup_2.3.55.1.zip
http://download-c.huawei.com/downlo...loadId=16205&version=90864&siteCode=worldwide
Click to expand...
Click to collapse
I installed that application and I was able to see my device, the apps, the contacts, everything. EXCEPT I wasn't able to access the device from Windows Explorer which means I am not able to transfer files.
Kandydish said:
I installed that application and I was able to see my device, the apps, the contacts, everything. EXCEPT I wasn't able to access the device from Windows Explorer which means I am not able to transfer files.
Click to expand...
Click to collapse
So when you change the option in the phone from charging to file transfer, did you check the device manager to see if there any unknown device showing somewhere?
bartendersimon said:
So when you change the option in the phone from charging to file transfer, did you check the device manager to see if there any unknown device showing somewhere?
Click to expand...
Click to collapse
Changing it from charging to MTP shows a MTP device in Manager with a yellow exclamation mark next to it. When looking into the details, it says that no drivers are installed. When I try "Updating Drivers", it says "Windows failed to install drivers. Code 28" or something along those lines. Code 28 MEANS that Windows failed to install drivers.
Thanks for nothing Microsoft.
Nexus 6p Connection to PC Issue - This Helped!
I had similar problems with PC not recognising my Device. I found http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/ which helped me solve my issues.
1. Downloaded and installed the Huawei Nexus 6p drivers. This installed a Huawei Task Manager which connection to pair was still not recognisable.
2. Deleted old drivers (acer, samsung, htc) from' Device Manager'. This actually helped PC recognise my device which showed up in the Device Manager>Other Devices>Nexus 6p, also in PC interface but once moved off charging to MTP, computer didnt recognise device.
3. Downloaded and installed the adb/fastboot installer. Followed instructions till step 10. My screen didn't show anything like Andoid ADB interface, it displayed MTP file install, which I installed. Just remember to refresh in My PC interface when changing over from charging to MTP, sometimes Nexus 6p will be hidden.
4. Uninstalled the Huawie Task Manager.
This has solved my problem with PC and Device connection. The instructions given are from what I can recall of the process I went through.
Credit to Sidharth Rathore from Technobuzz for this solution.
Hope this helps.
Later.
p.s. I have a windows 10 laptop if this helps.
bartendersimon said:
I was having the same issue with my computer not detecting the my phone storage but then i remove the drivers from my samsung in the device manager and then right away detect my nexus 6p, no only i can see the storage but if i select how i want to connect (MTP, File trinsfer) it will change the connection type and folder
MTP - shows the pics folder
File transfer - it shows the storage
Sweet
Click to expand...
Click to collapse
I was having the same issue until I uninstalled some other debugging drivers I had installed. So I would recommend crawling through your installed apps for any other android usb drivers and uninstalling them if you still have this issue.
Working on mine right now. Found that USB 3.0 ports will not recognize device. Once plugged into a 2.0, it is recognized. Might help your issue