Database Info

[Q]Xperia Miro not showing up in adb devices !! Need help

Hello all,
I have installed android sdk, google usb drivers etc. I am using windows Xp. My phone is upto date as per the Sony PC companion installed in windows. When I try to connect my phone in usb debugging mode to adb, its not showing up. when I give adb devices it doesn't list any devices.
when I give adb shell, it says device not found. I tried all methods like kill-server, start-server and killing adb.exe etc. after I went thru the existing threads in this forum. Nothing works !!
And the interesting thing that I could not figure out is about the device manager. After I try all methods it says drivers not installed. I try to install google usb drivers as well by browsing the folder in my android sdk . It was displaying like 'nothing found to install'
Any ideas please ??

One update.
Google usb drivers were not being installed correctly. When I update driver and browse to the Android SDK folder where the Google USB drivers present (My case .... Android SDK-> Extras-> Google -> usb_driver) it says 'nothing to update'
Then I edited android_winusb.inf file there and included my device ID (as showing up in Device manager). And it installed the drivers.
Then I opened adb again. And gave 'adb devices' and finally I could see my device listed !!!!
But still one major problem exists. That the device is getting disconnected continuously from adb and each time I would have to restart the adb and this makes it useless....
Not able to figure out why ...

Try using this: adbdriver . c o m
If it does not work try flashtool's drivers

[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.

"error: no device/emulator found" in fastboot

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..).

bootloader is wiped|

hello, i am in a bootloop with my oneplus 6. wiped everything.
since then i tried using the msmdownload tool, but it's not recognizing the phone.
in the device manager the phone is currently being recognized under "kedacom usb device" as android bootloader interface. I tried doing an update to the drive and installing a quallcom drive, but always get an error message "The folder you specified doesn't contain a compatible software driver for your device. if the folder contains a driver, make sure it is designed to work with your computer". i downloaded a few windows program to force installation with no success. tried signing the .inf file of quallcom driver - same errorwhen i try again. when i write in cmd 'fastboot oem unlock' - it says that the device is already unlocked. when i try the command 'fastboot twrp.img' or fastboot boot it also fails. i even downloaded tool-all-in-one - doesn't help. when im making an uninstall of the android bootloader interface, after connecting the phone again - it automatically installs this driver again, even though i marked in the settings not to do that. all i get is a bootloader screen, nothing else.
p.s. new here so sorry if the thread is in the wrong place or something.