Setup: Windows 7 64 bit ultimate virtualboxing an android 4.0.4. That has no playstore, no terminal emulator.. and ohmygod I am so lost. lmfao.
Anywho - what i'm trying to do is install the play store and terminal emu onto this virtual ICS ROM... and adb is givin me ****. I rooted my samsung replenish with little/no problems.. but this is just beyond me in every aspect of the sense. It's seriously gotten to where ADB just hangs now upon any syntax commands.. adb will run the cmd list like it should - but now nothing of adb past that command will respond. Literally. "adb" is the only command that works.. lmfao.
BTW: I don't know that this got marked as a question - but it is. Apologies for any error that may be present and my general stupidity to linux systems.
Related
Alrighty, I am new to the linux world and I am trying to setup my beloved adb on my Ubuntu. Java is there, SDK in in /opt/androidsdk. Do I need something more? I read that people install Eclipse also but since I am not a developer I don't need it, do I? I only need to execute very simple adb commands like push.
With Windows I needed the HTC Hero drivers and then it worked like a charm. Do I need something similar here?
I tried to run adb devices while my phone was connected and I get a phone with ?????????? as a name.
Is adb going to work or do I miss something?
Thanks in advance!
Adb works fine on x64 Ubuntu. I know there is a guide for it on www.villainrom.co.uk/wiki, but then search "adb" and it should bring up the entry.
I'm installing Ubuntu again today anyway, so I can check it works (which it does btw)
theodore80 said:
Alrighty, I am new to the linux world and I am trying to setup my beloved adb on my Ubuntu. Java is there, SDK in in /opt/androidsdk. Do I need something more? I read that people install Eclipse also but since I am not a developer I don't need it, do I? I only need to execute very simple adb commands like push.
With Windows I needed the HTC Hero drivers and then it worked like a charm. Do I need something similar here?
I tried to run adb devices while my phone was connected and I get a phone with ?????????? as a name.
Is adb going to work or do I miss something?
Thanks in advance!
Click to expand...
Click to collapse
Try doing this.
sudo adb kill-server
sudo adb root
then do w/e you need to do. This worked for me.
Not sure if you need to sudo kill-server, if it doesnt kill it, try without
ante0 said:
Try doing this.
sudo adb kill-server
sudo adb root
then do w/e you need to do. This worked for me.
Not sure if you need to sudo kill-server, if it doesnt kill it, try without
Click to expand...
Click to collapse
I did this followed by adb devices and I now get the correct device name.
I guess that it works though I didn't try to push any app
Another question: how do I add adb to the path? I currently need to type in the full adb path. It is linux related but I am new into this exciting world!!
Thanks for helping me out!
Google "Ubuntu add to path" and it will tell you
When I put in the ubuntu, ubuntu, local host and 5900 in the vnc veiwer. I click connect and it gives an error message saying "connection refused"
What am I doing wrong?
Anybody? Im super excited to get ubuntu up and running, but ive been stuck here for 2 days now.
You have opened the terminal emulator, right?
The part where you type in "su" then CD to wherever you put the ubuntu files and start the shell?
If you are using the paid app you might want to contact the dev for support.
Crisis, yes I did that. Then pressed home, then opened up vnc, and typed all that good stuff in.
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.
I've tried on windows 7 and Ubuntu 12.10 and no matter what I do,no matter how many times I update the SDK or uninstall and reinstall the SDK,ADB version is still 1.0.29...tried killing server,restarting adb, etc.
Trying to ./extract files from cm10.1 for compiling CM but ADB must be updated to connect to JB devices...
Someone please help!!! I've googled for hours and tried everything..still getting nowhere.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
:SOLVED FOR ME:
so what i did (and i dont know why all of a sudden its working) but,
i opened up the terminal and did the following
lsusb
This should kick out a list of plugged in devices. Most likely the last one is the phone. There were references to Samsung and Galaxy so it was pretty easy to figure out. On that same line, there is an ID number in this format...xxxx:xxxx. Write that number down for reference.
Now a few more commands:
cd
sudo gedit /etc/udev/rules.d/99-android.rules
When the rules open, copy/paste the following with the id "lsusb" gave you:
replace the ####:#### in the above string of text with the number you got from "lsusb"
Then save and exit.
sudo service udev restart
sudo adb devices
# XXXXXXXXXXXX offline
sudo ./extract-files.sh
GOT THE WINDOW POPUP ON MY PHONE
check always accept from this computer
then everything went smoothly....hope this somehow or another helps someone...if it does,please hit thanks.
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
soham jambhekar said:
in Ubuntu, once you update the SDK , copy the adb file in SDK/platform-tools to /usr/bin
reboot Ubuntu and try .
i don't use windows sorry
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
just tried sudo cp ~/android-sdk-linux/platform-tools/adb /usr/bin
it seemed to have copied since the original adb there was like 577kb and the new one is 1.2mb but still same issue.. i dont care to get it working on windows anyways...just thought i was strange it wont work on either platform...any other suggestions??
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
sinner99 said:
just a mention if someone arrives due to google search and are having an issue updating adb version in windows..this thread only speaks of a fix in linux so here is what i found: somehow someway adb.exe along with a couple dll files found their way to my windows directory, even though i always had its installed path included in my systems environment variables!! first i simply renamed these 3 files and added the extension .old to them. immediately running adb version in a command prompt my version finally read properly as it should 1.0.31 and not 1.0.26. its self explanatory why. hope this helps someone!
Click to expand...
Click to collapse
I had to sign up for this forum just to tell you, THANK YOU!!!! For the life of me, it was ridiculous that I couldn't find just simple information on how to do stuff. This is my first time looking into this stuff, So I couldn't even figure out how to update individual tools like that, which is what I've been spending the last 2 hours or more trying to figure it out.
It really was those three files in the Windows directory this whole time. Now my device is online, and adb shows the right version. Amazing. It's absolutely pathetic that google has their program screw up the entire adb functionality by putting these broken versions of the tool in the Windows directory.
I had to add to the path variable the location folder of the appdata platoformtools abd.exe.
Okay. I have been trying to do other things with rooting other phones. I've rewritten a exploit so it will work on Mac. But this is a general problem. I deleted the Emulator and every single thing but the platform-tools on the windows side of my computer. So the only thing I have on my computer is the platform-tools folder (aka fastboot and adb) So I have tried what almost every forum has said. The adb kill-server. I restart it. Still there. I've tried to individually kill it still there. I've unplugged my device and ran adb still there. This is one reason that stopped me from rooting on a windows because this stupid emulator won't go away and it never has. I've never ran eclipse on the windows side or to say that never anything but the adb and fastboot. Only the Mac side have I done other things. Please if anyone could help that would be nice. It'd save me time from having to take the .bat files and changing them to sh files and opening with text edit, editing the file to work with terminal, then sh install.sh run the file and it not work then back to the drawing board which after rewriting some stuff over and over is a miracle to see it finally execute the exploit. Thanks for any help. I would gratefully appreciate it. Thanks. Sorry this kind of a off topic thing. O yeah that is the other reason from keeping me going s-off to. It's annoying and I would really love to fix the issue. I will take any advice. Just saying though the adb kill-server and a lot of other commands are not working and not doing the process. Please anyone who would like to help. Just put anything :$ Please and Thank you.