I was looking at the [Newbie Guide] adb/fastboot/bootloader/android 101 and I am a bit confused on how to do adb. I am new to Android and Linux but am trying to learn. How do you really do the adb commands? I am running Windows and I do understand you have to mount the device through the USB cable. But I am not understanding how to do the commands after that.
phenixdragon said:
I was looking at the [Newbie Guide] adb/fastboot/bootloader/android 101 and I am a bit confused on how to do adb. I am new to Android and Linux but am trying to learn. How do you really do the adb commands? I am running Windows and I do understand you have to mount the device through the USB cable. But I am not understanding how to do the commands after that.
Click to expand...
Click to collapse
Once you have the usb drivers installed correctly, and have adb/fastboot/etc added to you system PATH, then in a command prompt type "adb devices". If it shows your device ID, then you have adb working correctly. Otherwise, you should check to make sure usb drivers are installed correctly. If it did work, then type "adb" and it should list most of the commands. Most common ones are: "adb remount", "adb shell", "adb lolcat", etc.
Also, for future reference, please post in the correct sub forum
Related
Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
chicojd said:
Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
Click to expand...
Click to collapse
Do a search for an Ubuntu SDK guide, there's a really good one floating around. You need to create a couple of text files to get it to register the USB device, the guide tells you how to do that.
Search for ubuntu udev android. You should be able to find it that way...
You have a problem with ADB on your (X)Ubuntu? "ADB not found", "No Device connected" even you set USB debugging?
I got the same problems when I started to play around with Xubuntu.
So I wrote a tutorial how to get ADB running properly under my Xubuntu installation.
Maybe it helps some people.
ADB on (X)ubuntu
I've enabled "USB debugging" under Settings-->Applications-->Development.
And when I directly connect the USB cable to my Ubuntu machine "lsusb" shows nothing.
I also get no USB icon in notification area on my tablet.
What am I doing wrong?!
Please help!
Worked beautifully
Thanks for the adb tutorial. I am running xubuntu on an old Dell Inspiron 1318.
Some tips I found help:
1. I used leafpad to create the 51_android... File
2. I added both "0x1949" and "1949" vendor IDs
3. As soon as I did this adb recognized my device in TWRP with a regular usb cable.
4. I had to execute each adb command with the "./" prefix, state such as "./adb devices"
5. I side loaded cm10 zip and rebooted in TWRP
6. Then I side loaded gapps zip and rebooted
Voila!
Thanks Hascode, PowerPoint 45, and others!
I rooted my NC and fixed the USB and ADB drivers. After NC is connected to WinXP system, everything works fine. There are two devices showing up. One is USB mass storage, the other is "composite adb interface".
But I can only remove USB mass storage devices safely. When try to remove "composite adb interface", it says "the device android composite adb interface cannot be stopped because a program is still accessing it".
It must be the process adb.exe that is using the device. How to safely stop it and remove the NC?
go to command prompt and type adb kill-server
DizzyDen said:
go to command prompt and type adb kill-server
Click to expand...
Click to collapse
it works. thanks
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
Code:
$ lsusb
Bus 002 Device 014: ID 19d2:0306 ZTE WCDMA Technologies MSM
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0306", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",ATTRS{idProduct}=="0306",SYMLINK+="android_adb", GROUP="adbusers"
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
Code:
$ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
6f7f7da7 unauthorized
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
unrealpowerz said:
Hey all,
I just wasted a few hours getting my axon 7 to connect to my pc running ArchLinux without luck.
lsusb gives me the following:
I think I've tried just about every combination of udev rules I could find on the internet. At the moment they are:
My user is a member of 'adbusers' and my phone is in USB debugging mode, also the USB thing is set to MTP.
Still, adb devices gives the following:
The phone also never asks for confimation or anything like that.
Has anyone here encountered something similar or know what I'm missing?
Thanks in advance
Click to expand...
Click to collapse
I had the same problem in Windows when using a custom rom. Enabling 'adb over network' solved it for me (the 'Allow USB debugging' window came up). even though it's seemingly unrelated
If that doesn't work try adb while phone is in TWRP (if you have it)
Hey fellow arch user here, (pacman ftw)
I had this same problem earlier with adb and fastboot. The solution is to run adb and fastboot commands as superuser. ie sudo fastboot ..... and sudo adb ......