my moto g3 with cm 13 nightly doesnt appear on windows explorer on my windows 10 pc and it doesnt appear on command window when i write {fastboot devices } . so does any one know how to fix this problem
Install drivers, set charging mode to data transfer in notifications
i already installed drivers and its read on command window but doesnot appear on windows explorer please replay if you know how to fix this
When the phone is in fastboot, it won't appear on pc via file explorer.
If it's not showing up as a media device, connect it to pc, press windows key+X and select device manager. See if moto g3 icon has a yellow triangle, that would mean that some drivers are missing or not installed properly. You will need to install them again.
Sent from my Moto X Pure using Tapatalk
i have connected my phone to pc and opened device manger and there is no moto g3 tag but there is an unknown device in section called other devices
and i already installed the device drivers and prove of that is when i write fastboot devices in command window the device serial appear
so can you help me
Then the MTP drivers are not installed properly. Check if adb devices command recognizes your phone. If yes, then adb and fastboot drivers are fine and only MTP driver is not properly installed. Go to start>seach for 'devices and printers' open it, it should open a control center page. Check if the phone appears there, and if it's there, check for a yellow triangle. If there is a yellow triangle present, just right-click and select remove device. Then reboot the PC and reconnect the phone, it should install all the drivers again.
Sent from my Moto X Pure using Tapatalk
yes as you said the mtp drivers arenot installed and tried the meathod that you wrote it but iam still facing the same problem is there any meathod to install mtp drivers manually
You try searching on the internet for .inf driver files for android mtp. Or try this : http://www.driverscape.com/download/android-mtp
Broadcasted from Zeta Reticuli
Related
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
Hi all,
I was having a strange problem with my USB dropping out when using the NEWER recovery (TWRP and Philz). Which meant I couldn't push files via ADB or Sideload. Here is my solution....
Before starting
I am using Windows 7
Download Google USB driver
Make sure you have TWRP 2.7.1.1 loaded as your recovery
You may have slightly different devices show up maybe, but this is what mine showed...
Open device manager
Plug phone in and power up to bootloader
Device manager should show 'Android Device' or similar
Open recovery
**This is where my USB was dropping out**
Make sure TWRP 2.7.1.1 loads
Look at device manager and should show 'One Mini' with a yellow exclamation mark
I tried updating the drivers automatically and browsing to the Google USB folder that we downloaded above but just kept saying 'device driver loading failed'.
The only way I found worked was
Right click 'One Mini' and update driver
Browse my computer for driver software
Let me pick from a list of device drivers
If you have Android device listed click that, if not choose Portable device.
Click 'Have disk' and locate the Google USB Driver folder and should be able to load the .inf file.
Click from the list ADB USB device and click ok.
This should load your device and install properly.
You shoud now be able to use ADB and Sideload in Recovery now.
Let me know if this works or not as there are a couple of bits that I can't replicate as the driver is already there!
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
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
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.