Related
Since i'm bored, i wanted to experiment with ADB, i know what it is, and what happens on it.
I've never used it, but i want to start
i just downloaded android SDK
idk what else to do, i searched ADB on the windows search thing, but i get 3 results, 1 is from something else, and another when i try to open says adbwinapi.dll is missing from your computer. try reinstalling the program to fix this problem.
i can't find adb on the folder i downloaded, whats wrong?
can someone tell/link me to a step-by-step instruction?
Sorry nobody got back to you sooner.
ADB is usually hidden in the android-sdk-windows\platform-tools folder.
I'm not sure which file you extracted yours to, but I extracted mine to C:Android so my path in cmd looks like C:Android\android-sdk-windows\platform-tools>
Once in there type adb and hit enter for a list of commands. Connect your phone and type adb devices to see if it can find it etc.
Good luck. You can really F stuff up with adb.
Not sure where else there are tuts but I learned from the ADB for dummies tut in the G1 development section (when I had my G1).
I would link but I'm on my phone and can't figure out how/if it can can be done w/ the app. Just go to the informative links sticky. Theres lots of basic android info there. Some translates to vibrant some doesn't. But good reading nonetheless.
Good luck
XDA Mobile
Can use terminal emulator to run adb commands.
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Digi.Gram said:
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Click to expand...
Click to collapse
The SDK Drivers are not for Galaxy Ace , Google for the drivers , they should be easy to find
Sent from my Ultma Weapon using XDA App
It seems that my problem begins with our Proxy server.... As the SDK manager and I had a quarrel about authentication, I downloaded some of the packages directly and forced the manger to use them instead of those on Google. With this, I accidentally downloaded an outdated adb, which had problems specifically with the Galaxy line of phones.... Downloading the correct package now, will see if it works better
Maybe I must just stop before I think of continuing I installed the newer r06 version, and my device is picked up, but now adb shell gives me this:
Code:
:~$ adb devices
List of devices attached
S58300c017faf device
:~$ adb shell
sh: applet not found
Any ideas where to look for the applet? Maybe I must continue tomorrow, new day new ideas.
Do you have Debugging turned on? And is the device rooted with Busybox? I assume yes since you're running a custom ROM but double checking.
If you're having trouble, I'd either: a) run a VM with XP SP3; b) head to the Android Q&A board here.
mmm, I never though of looking at that, since I figured they do say busybox is installed on this ROM, but thanx for nudging me into that direction, I found this post from ketut.kumajaya so I'm looking into that. Had some issues with not abling to get rw access, but my only problem there was a spelling error in the terminal.
I still get the error with the sh: applet not found, even after I tried the advice on that link. I tried installing all 3 versions shipped with BusyBox Installer on all 3 locations, still nothing. Just had an idea I'll try, if you invoke sh in linux you get a new shell, when I invoke sh I get the applet not found error. Maybe I should upgrade my sh or something. Worth a try
I am running a VM for the VB programming I do at work, but that doesn't have USB support (to much trouble to reinstall Virtual Box now just for USB support). Last night I tested on Windows 7 (first time since I started using this ROM) and it failed with the same error. I'm sure it's the sh that's broken or something. Will test on my wife's phone tonight (running the same ROM).
Thanx for your ideas so far. That's what I love about an online community, even if you don't exactly know what's wrong, people sling ideas around that nudge you in the right direction. One error message at a time
Solved thanx to Ketut
Thanx for all your help guys.
Well, after many searches both here and on google, I can't seem to find anything referring to my specific problem, so if this has been answered before, I apologize.
I am attempting to teach myself how to use adb in Ubuntu. I have it all set up, have updated the sdk, etc., thanks to many wonderful guides both here and elsewhere, and I have a 99-android.rules in /etc/udev/rules.d with the proper Vendor ID for the EVO 3d, and adb added to my path. Howerever, when I use adb devices, it shows no devices installed. I checked lsusb, and noticed that my phone is showing as High Tech Computers Desire/Hero with the wrong Vendor ID, which is obviously wrong. I was wondering if anyone knew what might cause this and how it can be resolved. The contents of my 99-android.rules are as follows:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Also, I am fairly new to linux, so if there is some command line magic involved, could you please explain what the commands are doing so I can understand what I'm fixing, instead of just doing a copy/paste?
Thank you in advance.
darthstewie said:
Well, after many searches both here and on google, I can't seem to find anything referring to my specific problem, so if this has been answered before, I apologize.
I am attempting to teach myself how to use adb in Ubuntu. I have it all set up, have updated the sdk, etc., thanks to many wonderful guides both here and elsewhere, and I have a 99-android.rules in /etc/udev/rules.d with the proper Vendor ID for the EVO 3d, and adb added to my path. Howerever, when I use adb devices, it shows no devices installed. I checked lsusb, and noticed that my phone is showing as High Tech Computers Desire/Hero with the wrong Vendor ID, which is obviously wrong. I was wondering if anyone knew what might cause this and how it can be resolved. The contents of my 99-android.rules are as follows:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Also, I am fairly new to linux, so if there is some command line magic involved, could you please explain what the commands are doing so I can understand what I'm fixing, instead of just doing a copy/paste?
Thank you in advance.
Click to expand...
Click to collapse
On the 100% stock Ubuntu 11.10 64 bit system, should be able to simply plug in the device and access it via adb. Only caveat will be, you'll need root access w/o setting up the udev rules. Simple command: sudo ./adb devices from the sdk/platform-tools directory should list the device.
The only issue I've had is when using VirtualBox, by default, it grabs USB connections and forwards them to the Virtual Machine which results in the linux side of ./adb devices showing nothing.
Hope that might help!
Thanks for that, but I do know how to use adb. My problem is that adb is showing no devices listed, and when I lsusb so that I can see what linux is reporting as being listed to my ports, it is showing up as being a desire/hero with the wrong vendor id, which is what I think is causing adb not to see it.
Try this
reboot your pc/laptop.
Then boot your phone into recovery and plug it in. Then from command line
./adb kill-server
Then to enabled it
./adb start-server
Then
./adb devices
See if that helps any.
Locked & Loaded
""shooter on Deck""
Actually, I think I figured it out. Whenever I reboot my phone, it switches from being ok to adb not seeing it and the wierd lsusb reporting. If I reboot without it connect via usb, everything is fine. I'm thinking it's in the ROM and/or kernel I'm using.
Hi, I hope I am posting in the right section? I found the site really difficult to navigate having never used the site before. If its in the wrong place please can a mod move it.
Ok so I have an Android Set Top Box (STB) and I am trying to extract all the data from it. It is an mxp pro 4k. I don't want a backup of the data I want to extract full images of the device for analysing with forensic tools. The problem is I can't seem to communicate with it. I have the full SDK that is up to date, once navigated to the platform tools folder I opened a command line and typed
Code:
adb devices
after plugging in a USB cable to the OTG port. No prompts appeared on the screen to trust any connections like my iPhone does when I connect it. Adb devices returns no results. So I tried wireless adb, I typed
Code:
adb connect 192.168.x.x
and it said connected. Then when running the devices command I had the ip and port then the word device. I then get a shell by using
Code:
adb shell
Which i then elevate to root by using
Code:
su
. Then when i try an adb pull or adb backup I get a message saying error device offline.
Im new to Android so not even sure I am doing it right. I have done a lot of reading and research but seem to be stuck with the basics. To confirm USB debugging is turned on.
Hello, I hope someone can help.
I have downloaded ADB for windows but cannot for the life of me get it to work. When I connect my phone (Samsung s6) and type ADB DEVICES, I get an error, cannot connect to daemon.
I have searched for solutions but none work. I have tried, kill-server, start server, I have tried re-installing ADB, the latest version and version 1.4.3, which I found on this site , as it had an installer. I have enabled USB De-bugging on the phone etc. I disabled my AV and firewall and also allowed ADB through windows defender, just in case it was that, as someone said that worked for them. None of the above worked for me...
I did get to a point where my phone asked me to allow debugging, I say yes but then again it says Daemon did not ACK.
I am so frustrated with this that I think, I am going to start a campaign to destroy Google. The world doesn't need them.
I know this issue has been posted on before but forgive me, nothing I have found so far works, on this site or any other.
I signed up to this site in the hope that there is someone who can help.... Cheers in advance..
Steve..
The ADB Daemon ( adbd ) is the counterpart on Android device of ADB Server ( adb.exe ) on Windows computer. Their versions must match in order ADB gets working.
Run this command sequence
Code:
taskkill /F /IM adb.exe
adb devices
jwoegerbauer said:
The ADB Daemon ( adbd ) is the counterpart on Android device of ADB Server ( adb.exe ) on Windows computer. Their versions must match in order ADB gets working.
Run this command sequence
Code:
taskkill /F /IM adb.exe
adb devices
Click to expand...
Click to collapse
Thanks for your reply, it was actually very helpful...
Many thanks.