I recently set up Ubuntu Karmic on my laptop's second hard drive, and I finished setting up Eclipse and the Android SDK yesterday. I set up ADB to work directly from the terminal without changing to the SDK Tools directory, and it works... kind of. I can get some ADB commands working, but most others won't. The only things that really work are "adb help" and "adb devices" at the moment. "adb install", "adb push" / "adb pull", and other similar commands seem to register, but then nothing happens after that- the terminal freezes, and inputting keys shows other characters. ]]^A and stuff like that. Can anyone help?
Ubuntu 9.10x64 adb works with sudo
$ sudo adb push...
I usually make sure the first adb command I use is sudo'd so it starts the daemon as root.
adb help - does not send any data to your droid. It's internal
adb device - shows which devices are on the USB bus.
The other adb command need to talk to the devices and depending on how your udev protections, device protections, and your personal group memberships are... it may not work.
sudo works for me always.
Ehud
I have a LG Thrill 4G. I rooted the phone using superonelick, root checker says it is rooted. Downloaded ROM Manger and flashed clockworkmod. I cannot click boot into recovery, it just restarts the phone. I have tried to reboot into recovery by pressing 3d button, down volume, and power and it boots me into the android recovery but not clockworkmod, so I can not find anyway in to download the new rom from the zip file. Has had any other people had trouble with this? I have spent over 2 days searching the internet but I cannot find any similar problems, is there anyway to get into the recovery mode to install the new ROM without it just restarting the phone?
LG Thrill 4G ClockworkMod Installation (correct method)
1) You need to have ROOT access at the least (see link below)
It will also be good to have ADB (and hence LG Thrill drivers) installed properly
http://forum.pandaapp.com/thread/2/11/20110919/4e77f603d22632913-1.html
2) Get the recovery image from here and keep it on your PC in a folder accessible by ADB.
OR (if no ADB then) directly put it on your LG Thrill SDCard root
http://forum.xda-developers.com/showthread.php?t=1257588
4) If you have ADB then follow the instructions in the first link above to push the recovery image to your phone.
OR
if no ADB then open Terminal Emulator (install it from Market) and type su and click allow if the prompt comes up
5) Now you can follow instructions in the first link (far above) again, starting from the 'dd if=...' step. But instead of rebooting you could just power off
6) Clockwork recovery should now be flashed. To enter recovery, keep the 3D button, Vol-down and Power button pressed until you see the LG logo
Thank you for getting back with me. I tried to follow these steps and when I am in the Terminal Emulator and type adb push recovery.img /data it comes back with adb: not found. I have redownloaded the recovery file that you have attached to the SD card, same error, and then I tried to copy to the phone itself and same error. I can do any of the other prompts for the emulator but nothing that has to do with the recovery file it will not work. I am guessing maybe this is the problem because if it cannot find the recovery file, I cant do much of anything else. Do you have any suggestions of why the file still cannot be found on my phone?
connect adb through tcp
Try this:
1. If you are using terminal emulator to access adb then try downloading the app called remote adb. This tool will allow you to connect your device via tcp. Take note of the ip adress and port number. Usually the default port is fine.
2. Now open sshdroid, connectbot, terminal emulator and start an ssh session with the adb shell. You must have the correct public ip and port entered in to access the adb via tcp.
3. Once you have made the ssh connection between what ever emulator you are using and remote adb, start a shell as su.
4. Type the commands mentioned earlier.
This should let you run the whole thing from within your phone.
Alternatively...
1. start remote adb on your device.
2. start a terminal or cmd prompt on your cpu.
3. cd to androidSDK\platform-tools
4. type ---> adb start-server
The server then sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a connection to that port.
Note that each emulator/device instance acquires a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections. For example:
Emulator 1, console: 5554
Emulator 1, adb: 5555
Emulator 2, console: 5556
Emulator 2, adb: 5557 ...
As shown, the emulator instance connected to adb on port 5555 is the same as the instance whose console listens on port 5554.
Once the server has set up connections to all emulator instances, you can use adb commands to control and access those instances. Because the server manages connections to emulator/device instances and handles commands from multiple adb clients, you can control any emulator/device instance from any client (or from a script).
5. type --> adb forward tcp:5554 tcp:5555
5. type ---> adb devices. In response, adb prints this status information for your device. If there is no emulator/device running, adb returns no device, and you have not made a tcp connection.
6. Take note of the serial number listed. You will use it later to direct commands to device.
7. Type --> adb shell
8. Type --> su
9. Use commands from other post to achieve whatever you need.
10. once finished with shell, type --> exit twice to leave the shell
11. Finally, type --> adb server-kill
Hope that helps. Seems like you were having issues making the connection from device to adb, so that is what I focused on. If I can help anymore, just ask. We are all continually learning and the only stupid question is the one never asked.
B^)
Hi All,
I am a newbie here. I issue following "adb shell getprop" adb command to retrieve device properties. This just hang out no output printed on the terminal or no prompt appears.
I then kill it at send "adb shell getprop ro.build.version.release" but it also just hang out.
I am working on ubuntu12.04. adb devices list one device which is connected.
Please help, how can I read device properties from adb (such as OS, model, manufacturer etc..)
My device is not rooted.
Many thanks!
IUA
NON ROOTED PHONE
I am trying to create to backup of all application in android but I don't want the users to connect to USB even for the first time.
okay let me first explain what happens when we connect our phone with USB to ADB client
0. USB Debugging mode is enabled in the phone.
1. The phone is connected to PC using a USB cord.
2. We run
Code:
adb tcpip 9999
command from cmd with ADB already installed.
The above command helps now switched the abd demon (adbd) inside the android phone to listen through TCP-IP protocol
3. now we can disconnect the phone from the PC
4. using a terminal emulator application we can now fire the commands
a)
Code:
adb connect localhost:999
b)
Code:
backup -all -f /sdcard/dev/bck.ab
now a backup pop-up will open up, you can simply click backup button.
Now we can anytime execute the command in 4.a and 4.b util the user restarts the phone or
but the problem is I wish to execute
Code:
adb tcpip 9999
without PC. Can someone suggest me how to approach this problem. From where should I start reading or there is some existing application that can do this on a non-root phone.
I need to manually root a lot of devices in as short a time as possible. I would like to do this with ADB but I don't know how to use ADB to perform the same commands on more than one device at a time. I found this Stack Overflow (that I'm not allowed to post the link to) and this Github (that I also can't post a link for call adb-wrapper) so I've been trying to use these shell scripts in Ubuntu (I am a complete noob at Linux). I wrote a simple little "Hello World" shell script and ran it from CMD prompt just to see how they work. And I managed to get the Stack Overflow script to work (I think) to call ADB devices and engage the debugging authorization on 5 devices at a time. That was great! I just copied the script into the Ubuntu Bash and called it in CMD Prompt and then ran the command: ADB devices. But when I tried adb reboot-bootloader I got the more than one device is attached warning. So I tried implementing the Github one and I just can't get it to work. I was close but my $ANDROID_HOME path was wrong and when I tried to fix it I think I just broke everything. Now whenever I run adb (anything) it just prints out ADB guidelines like commands to use and what they do. I'm at the point where any bug I Google is returning nothing useful.
I need to run the following ADB commands in parallel:
adb reboot-bootloader
fastboot oem unlock
fastboot boot recovery.img
Help?
run adb command in parallel
jaynesbluewish said:
I need to manually root a lot of devices in as short a time as possible. I would like to do this with ADB but I don't know how to use ADB to perform the same commands on more than one device at a time. I found this Stack Overflow (that I'm not allowed to post the link to) and this Github (that I also can't post a link for call adb-wrapper) so I've been trying to use these shell scripts in Ubuntu (I am a complete noob at Linux). I wrote a simple little "Hello World" shell script and ran it from CMD prompt just to see how they work. And I managed to get the Stack Overflow script to work (I think) to call ADB devices and engage the debugging authorization on 5 devices at a time. That was great! I just copied the script into the Ubuntu Bash and called it in CMD Prompt and then ran the command: ADB devices. But when I tried adb reboot-bootloader I got the more than one device is attached warning. So I tried implementing the Github one and I just can't get it to work. I was close but my $ANDROID_HOME path was wrong and when I tried to fix it I think I just broke everything. Now whenever I run adb (anything) it just prints out ADB guidelines like commands to use and what they do. I'm at the point where any bug I Google is returning nothing useful.
I need to run the following ADB commands in parallel:
adb reboot-bootloader
fastboot oem unlock
fastboot boot recovery.img
Help?
Click to expand...
Click to collapse
Hi jaynesbluewish,
I too want to run adb commands in parallel. Can you let me know if you have found the solution to this..
Please share the steps you followed..