Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!
MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?
MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?
MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder
Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.
Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)
Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.
When I first plugged my A9 into my computer I was immediately given a prompt to allow the computer to be used for adb, and proceeded to reboot to download to make sure everything worked before I attempted to unlock the bootloader using HTCdev. With the phone still plugged in the USB debugging symbol is no longer there and I've tried unplugging it, and plugging the cable back into the phone as well as the computer. Tried both ports on my computer, disabled USB debugging and re-enabled it but no dice ?. I'm not sure what to do now, adb devices shows up as empty.
Sent from my SCH-I545 using Tapatalk
65vdub said:
When I first plugged my A9 into my computer I was immediately given a prompt to allow the computer to be used for adb, and proceeded to reboot to download to make sure everything worked before I attempted to unlock the bootloader using HTCdev. With the phone still plugged in the USB debugging symbol is no longer there and I've tried unplugging it, and plugging the cable back into the phone as well as the computer. Tried both ports on my computer, disabled USB debugging and re-enabled it but no dice . I'm not sure what to do now, adb devices shows up as empty.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
This happens to me from time to time, especially when I'm swapping different devices out a lot.
Go to Device Manager
You should have Android USB Devices > My HTC (this is the ADB device) and Portable Devices > HTC One A9 (this is the MTP device).
You likely only see the MTP device. If so, right-click on it and select "Update Driver Software"
Click on Browse my computer for driver software
Navigate to your HTC device driver folder (in my case it's C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click Next
If you get a message that the best driver is already installed, then click the back button
Select "Let me pick from a list of device drivers on my computer"
If you have a device listed as My HTC select that
If you don't, you'll kind of have to play with different things from here. Try unchecking show compatible devices and see if it shows any Android USB devices. You might need to browse for your device drivers again.
Will try that when I get home, thank you very much ☺
Sent from my SCH-I545 using Tapatalk
I have a new, unrooted, bootloader-locked F8332 Xperia XZ to which I am trying to connect via adb from my Windows 7 computer so that I can attempt an 'adb restore' of the applications and data from my current device. I already have the Android SDK installed and downloaded the XZ adb and fastboot drivers from the Sony developer site. However, I have not been able to install the drivers. When I connect the XZ (with USB Debugging enabled) and look in the Windows Device Manager, I get "Xperia XZ" listed under Portable Devices and nothing related to adb shows up. If I try to update the drivers and point Windows to the downloaded drivers for the XZ, it tells me that no drivers were found. With the XZ connected, I can run 'adb devices' and what I get is a blank list. I can connect the XZ set up for fastboot and it will show up in Device Manager as an Unknown Device. Attempting to install the drivers there also fails with a similar "no driver found" error.
My current device is a rooted Xperia TX. In order to get that device to show up with 'adb devices' I have to set its USB Storage Mode setting to Mass Storage, otherwise it will not work. The XZ, however, does not let me change the storage mode from MTP because whatever I choose (e.g. PTP) gets reverted to MTP immediately. So the questions is how do I get the XZ to be seen by adb or in a configuration that will allow me to install the relevant drivers? I am probably missing something simple because the threads in the forum relating to adb stop at "install the adb drivers" with no additional details. Any help would be appreciated.
Did some more playing around and figured out how to get the ADB interface to show up in Windows. As with my Xperia TX, the issue is related to the USB Configuration setting under Developer Options. For anyone who might run into this situation, it seems that USB Configuration has to be set to MIDI for ADB to work.
I had tried changing that setting to PTP, but it would not stick, it would always change back to Charging Only. Thinking that perhaps PTP would not stick because I did not have an SD card on the phone at the time, I put in an SD card and tried again, but the result was the same. Thinking that it would not actually work since what I was attempting had nothing to do with music, I set USB Configuration to MIDI and to my surprise the setting stuck. I plugged the phone into my computer and the Windows Device Manager showed a new "ADB Interface" entry with an exclamation mark. Right-clicking on ADB Interface and selecting Update Driver allowed me to choose the driver I downloaded from the Sony Developer Site. Windows accepted the drivers (with a prompt about the drivers being unsigned) and the Device Manager entry changed to "Sony sa0115 ADB Interface Driver." The XZ gave me a prompt about allowing the computer to have debug access, which I accepted. At this point I could go to a command prompt, run "adb devices" and the XZ showed up in the list, as expected.
The "adb restore" that I was attempting was (mostly) successful in transferring my applications and their data to the XZ. I still don't know why the PTP setting will not stick, or if that is normal.
Felix1701D said:
Did some more playing around and figured out how to get the ADB interface to show up in Windows. As with my Xperia TX, the issue is related to the USB Configuration setting under Developer Options. For anyone who might run into this situation, it seems that USB Configuration has to be set to MIDI for ADB to work.
I had tried changing that setting to PTP, but it would not stick, it would always change back to Charging Only. Thinking that perhaps PTP would not stick because I did not have an SD card on the phone at the time, I put in an SD card and tried again, but the result was the same. Thinking that it would not actually work since what I was attempting had nothing to do with music, I set USB Configuration to MIDI and to my surprise the setting stuck. I plugged the phone into my computer and the Windows Device Manager showed a new "ADB Interface" entry with an exclamation mark. Right-clicking on ADB Interface and selecting Update Driver allowed me to choose the driver I downloaded from the Sony Developer Site. Windows accepted the drivers (with a prompt about the drivers being unsigned) and the Device Manager entry changed to "Sony sa0115 ADB Interface Driver." The XZ gave me a prompt about allowing the computer to have debug access, which I accepted. At this point I could go to a command prompt, run "adb devices" and the XZ showed up in the list, as expected.
The "adb restore" that I was attempting was (mostly) successful in transferring my applications and their data to the XZ. I still don't know why the PTP setting will not stick, or if that is normal.
Click to expand...
Click to collapse
i tried what your mentioned and succeed,but i really want my 'mobile device' （a blue screen phone）show in my ‘file manager’。is there any method？
by the way,are all these mtp problem due to unlock bl?
Confirmed on my Xperia ZX F8331. I have to select MIDI interface to access to the ADB interface.
Btw, I'm rooted and the bootloader is unlocked.
Thanks for your report!
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).