I installed sdk android-sdk_r07-windows.zip and also tried with android-sdk_r06-windows.zip.
When I do "adb devices" the list of connected devices is empty. My phone is a Huawei U8230.
The USB debugging mode is enabled. I can also see the files inside the phone in a Windows Disk Drive.
Any sugestion on how to get the device listed?
A bit stupid... But your phone is running android ?
You can try to search your phone drivers if there were somes, didn't it ?
Fixed it.
1. First Installed the SDK (all components including usb drivers).
2. Then Enable USB debug mode on the phone.
3. Then connect the phone.
4. Then a CD Drive is detected -> run setup from that drive.
5. Last restart adb.
Fiuuuuuuuu that costed a lot!!!!!!
Related
Okay, I know there are lots of posts about getting adb drivers to work on the g tablet but I can't seem to get to step 1. When I plug in my USB cable, my PC doesn't ask me to install anything. It just seems to assume that it is a USB drive. I tried to force the install via Install Hardware and pointed it to my modified android_winusb.inf file. When I did that it came up with three different options (Android ADB Interface, Android Bootloader Interface, and Android Composite ADB Interface). I tried all three but none of them will start successfully.
My cable connects to the mini-USB port (I have a keyboard connected to the full size USB port). I can't imagine that would make a difference, though.
I can copy files over to the g tablet from my PC; I just can't get ADB to work. What am I doing wrong?
First, you need to install the Android SDK on your computer. ADB shell is a program contained within the Android SDK. If you install the latest version, you also need to install "Android SDK Platform-tools" (launch the SDK and AVD Manager, then select the "Android SDK Platform-tools" package). You can connect the miniusb cable to your tablet and use adb shell, but I prefer to use adbwireless (free app in market); for some reason my computer won't recognize my tablet when connected via the cable. Then just open up cmd.exe (if you're using windows) and go from there. You'll need to locate the actual adb executable file, so you can run it in the command window. You'll also have to learn the commands as to how to do things, but lists of common commands can be found with a simple search.
I had problems with getting the debug usb drivers to install on a win7 dev machine. So I just installed adb wireless onto my gtab from the market. On my win7 box I just use 'adb connect x.x.x.xort' to use adb over the wifi.
It's pretty handy.
I figured it out. For others that run into this, I had to uninstall the drivers with USBDeview. I only uninstalled the one with a description of NVIDIA Tegra 2 USB Device. The second half of this YouTube video shows what to do for a phone:
youtube.com/watch?v=1UF5w1dKe2U
Then disconnecting and reconnecting the USB cable installed the drivers correctly. Weird.
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
Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH
Hello guys,
i spent the last 3 days with my problem:
I want to use my Samsung A40 for debugging in Visual Studio but it doesnt show up. I plug in, install Samsung ADB Drivers and it shows me a working "Samsung Android Interface" in the Device Manager. I can also access the data through windows explorer without any problems. But when i use command "abd devices" i get an empty list.
What i did:
- enable USB Debugging
- Change Protocols
- Install ADB drivers
- Different cables
- Different USB Ports
- Deleted adbkeys
- Created adb_usb.ini with Vendor IDs
and so on...
I got it to work on my private computer and on another computer at work without any problems. But here it just doesnt want to pop up.
Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all
BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.
follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",