Database Info

[Q] ADB Installer Issue - USB Connection

Hello, another question in quick succession.
I have used the installer featured in this topic: http://forum.xda-developers.com/showthread.php?t=2588979 - to install all the necessary drivers so I can connect my phone through USB and hopefully install Android 5.1 onto my phone.
I went through every step in the topic and ADB Composite Device appear listed. My phone is also definitely connected as I check for 'adb devices' in command prompt. However, when connected in fastboot mode, it still asks to Connect to USB Device. USB Debugging has been enable on my device, also.
Help would be much appreciated! I'm new to this so it's a teensy bit of a rigmarole.

Could really do with help here, I'm stalling on it and it's bugging me - wanna get it sorted.

[SOLVED] Computer Does Not Recognize Phone

Not sure what happened, but all of a sudden whenever I plug in my Blu Studio X+ into either one of my computers with USB Debugging enabled I get a pop up saying the USB device is not recognized, and it shows up in the Device Manager as an Unknown Device. I've tried updating the driver manually, but every time I navigate to an INF file in the driver installation dialog it tells me the specified file contains no information on the device. Doing an "adb devices" command returns nothing, and "adb shell" returns "error: device 'null' not found".
Sent from my STUDIO X PLUS using XDA-Developers mobile app

Already check your cable?maybe your cable does not support to transfer data beetween your phone and PC.
Make sure you have connect as a 'MTP' or Try to connect as a 'USB Mass Storage'
If you have tried all the ways,the last way is to backup your phone and do factory reset,or it will be BETTER if you bring your phone to serviceperson,because maybe there is an issues on your hardware.

jasonmerc said:
Not sure what happened, but all of a sudden whenever I plug in my Blu Studio X+ into either one of my computers with USB Debugging enabled I get a pop up saying the USB device is not recognized, and it shows up in the Device Manager as an Unknown Device. I've tried updating the driver manually, but every time I navigate to an INF file in the driver installation dialog it tells me the specified file contains no information on the device. Doing an "adb devices" command returns nothing, and "adb shell" returns "error: device 'null' not found".
Sent from my STUDIO X PLUS using XDA-Developers mobile app
Click to expand...
Click to collapse
You seem to have a lot of driver problems considering the number of threads you made
Go to device manager with your phone plugged in and uninstall every driver that has to do anything with your phone.
Unplug phone.
Reboot your PC.
Now plug phone back in and wait for the automatic driver installation to complete (doesn't matter if it succeeds or not).
Click here to download the latest driver (download it even if you have already).
Disable USB debugging and enable it again and wait for the automatic driver updater if it opens.
Open device manager and manually select the .inf file for your device.
If you don't know which device is your phone, unplug the phone and plug it back in and watch which devices disappear and then reappear again.
Also updating to Ubuntu, as your profile picture suggests, should ease the ADB driver installation and reduce ADB problems

Got it figured out. Wiped all ADB drivers and reinstalled, then downgraded my system-wide ADB from 1.4.2 to 1.3.
Sent from my LG-D415 using XDA-Developers mobile app

Fastboot will not detect my device while rooting

I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.

Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.

ADB not detecting Xperia XZ

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!

Cannot recognise device in fastboot

Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?

Sorted the driver issue... didn't install it properly...

Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)

Win 10 seems to have problems. I downgraded to win 7 all sorted.

I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave

funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.