What is ADB [Explained] - Android General

When it comes to Android modding, most novice users are confused or left wondering by reference over reference to a certain “adb”. This is specially true when you are looking up something on modding your device, or root it in particular. ADB is the wonder toy of Android and everyone seems to love it, so lets have a look at understanding what it is and why you need it, and how you can get it.
What is ADB
ADB stands for Android Debug Bridge. It comes as a part of the standard Android SDK, which you can grab here. Basically, it provides a terminal-based interface for interacting with your phone’s file system. Since Android platform is based on Linux, command-line is often required to perform certain advanced operations on your device using root access.
While these things can be done directly on the device itself using some terminal emulator, it will be rather difficult to execute complex commands on such a small screen. ADB provides the bridge between your machine and your computer.
Read full post : http://dreamproject.asia/faq/terms-slang/what-is-adb/

Related

Console applications on Android

I plan on purchasing an HTC Dream within the next couple days (second hand, prior to rogers 911 update such that I can root and install with cyanogenmod).
I was wondering how development on porting CLI programs to android has been. Being a long time linux user, I am quite proficient with the shell and prefer it for many tasks. I have done some googling and searched these forums, but I was unable to come across very much information.
Are any of the following programs ported to android, how successful have these ports been, and what procedure is needed to proceed with installing the ports (if they exist at all)
-rtorrent
-elinks
-finch (ncurses based instant messenger client)
-units
-mpg123
-calc (or apcalc on some distributions)
-cal
-vi
Any assistance is appreciated.
I am bumping this. I there a better place to ask?
Why not download the Android SDK, emulate the device on your PC and have a hack about with it to see what works.
The standard unix stuff works ls ps and the like, but I can't vouch for the stuff you've mentioned.
Give it a go: http://developer.android.com/sdk/
None of the programs are installed, which surprises me, as nearly every *nix system has vi installed.
Now that I have received my phone, and installed cyanogenmod (which comes with busybox) I can state that vi is installed.
The other programs are not however, and they are unlikely to be ported, due to a difference in the C library for android and the full C library used for most programs.

How to use terminal?

I've read in a few threads which required the use of terminal/fast boot.
What exactly is this? Can anybody point me to a guide/tutorial on how to use it?
Thanks in advance!
P.S. - I am a newbie in playing around with the Android system.
bump bump bump
Terminal basically allows you to run certain commands directly on your device rather than having to be coupled to your pc.
Android Terminal Emulator
Description
This application lets you access your Android's built-in Linux command line shell. It emulates a Digital Equipment Corporation VT-100 terminal. You can use this application to run utility programs on your device.
What is this app good for?
This application lets you run Linux command line utilities on your Android phone. It is mostly useful for computer programmers. It might also be useful for people who want to explore the Linux internals of their Android phone.
Click to expand...
Click to collapse
Some Android basics - http://forum.xda-developers.com/showthread.php?t=619153
How to use ADB - http://forum.xda-developers.com/showthread.php?t=502010
Terminal commands - http://www.busybox.net/downloads/BusyBox.html

[Q] Imaging the File System

I am working on a project at working concerning the HTC Touch Pro (Fuze) running 6.1. We are looking to take a forensic image of the device from the file system up. Our traditional software for imaging other types of drives (hard, flash, etc.) can only see the existing files on the device. We want to be able to perform a full acquisition.
I know this is possible on Android devices, I've spent a lot of time doing it. On Android devices I am able to use Android SDK/ADB to copy the mmcblk files from the device to the host computer.
I have the Windows SDK in Visual Studio. Is there something similar to ADB for Windows? I basically just need a command-line interface with which to communicate with the phone.
Any information would be appreciated!
mpercy725 said:
I am working on a project at working concerning the HTC Touch Pro (Fuze) running 6.1. We are looking to take a forensic image of the device from the file system up. Our traditional software for imaging other types of drives (hard, flash, etc.) can only see the existing files on the device. We want to be able to perform a full acquisition.
I know this is possible on Android devices, I've spent a lot of time doing it. On Android devices I am able to use Android SDK/ADB to copy the mmcblk files from the device to the host computer.
I have the Windows SDK in Visual Studio. Is there something similar to ADB for Windows? I basically just need a command-line interface with which to communicate with the phone.
Any information would be appreciated!
Click to expand...
Click to collapse
I think MobilMon can monitor file system activity and allowing them to keep a log on device

[DEV][LIBRARY][2015-06-12] RootFW4 - An Android Root Shell Framework

RootFW4 - An Android Root Shell Framework
RootFW is a tool that helps Android Applications act as root. The only way for an application to perform tasks as root, is by executing shell commands as Android has no native way of doing this. However, due to different types of shell support on different devices/ROM's (Shell type, busybox/toolbox versions etc.), this is not an easy task. RootFW comes with a lot of pre-built methods to handle the most common tasks. Each method tries to support as many different environments as possible by implementing different approaches for each environment. This makes the work of app developers a lot easier.
RootFW is the largest of it's kind. It does not only provide a feature of connecting to a root shell and executing a few shell commands. It also provides a very large range of additional features and extra shell tools that are all build to make RootFW the most cross-device compatible library for Android, and very fast and easy to use in your app.
Besides the ability to connect and communicate with a shell, it provides tools for working with files, properties (Both registered and prop files), file systems, binaries, busybox, memory (RAM, SWAP, ZRAM etc), processes and so on.
Links
Source
Usage and Overview
Full Documentation
Reserved...
Thanks @dk_zero-cool. This looks interesting. I'm currently using Chainfire's SU library. I'll give it a try !
Edit: Just out of curiosity, Why LGPL ?
ukanth said:
Edit: Just out of curiosity, Why LGPL ?
Click to expand...
Click to collapse
GPL has got to much limitation on how and where. I use GPL most of the times, but for something like this, I think LGPL fits much better.

Surely This Wouldn't Work, Right??

Hello fellow forum go-ers of the Security section!!!!
This is my favorite area on this site & always makes me start thinking outside the box so to speak.
So i was thinking about Ubuntu & the ability to run a SU shell within it (not sudo but an actual SU shell by typing 'su' & providing your set password)
Would I be able to launch ADB commands from this SU shell & in turn run commands as any form of top tier user on my unrooted Android device???
Any responses appreciated!!! I really would like some input here on why this would or wouldn't be possible & how well the translated binary performs.
Thanks
No; but Yes. To some extent. This is why, in the *very* early days on Android, many XDA'ers had Terminal Emulator installed on our G1s. We could do build prop edits, push apps to install as system apps, "pull" backups, etc, etc.
These days I'm not sure, since I haven't experimented. However, I've got Kali on my tablet & a terminal app that lets me open either a Kali or Android command line either as a regular user, or as su.
I'm not sure if I helped here... Or if I just muddied the waters even more.
equi_design said:
No; but Yes. To some extent. This is why, in the *very* early days on Android, many XDA'ers had Terminal Emulator installed on our G1s. We could do build prop edits, push apps to install as system apps, "pull" backups, etc, etc.
These days I'm not sure, since I haven't experimented. However, I've got Kali on my tablet & a terminal app that lets me open either a Kali or Android command line either as a regular user, or as su.
I'm not sure if I helped here... Or if I just muddied the waters even more.
Click to expand...
Click to collapse
Little bit of both but that's fine as Kali is a small download! lol, thank you by the way, as my first device was an s2 skyrocket & I remember when it was literally almost all Unix/Linux & much more simple . More or less it killed me by falling out of the computer changes in tech while I caught up on the mobile side.
Again thank you!! as now im closer to certain that i haven't been wasting my time.
LilAnt530 said:
Hello fellow forum go-ers of the Security section!!!!
So i was thinking about Ubuntu & the ability to run a SU shell within it (not sudo but an actual SU shell by typing 'su' & providing your set password)
Would I be able to launch ADB commands from this SU shell & in turn run commands as any form of top tier user on my unrooted Android device???
Click to expand...
Click to collapse
Your android device has an operating system, which gets to make the rules about root. So does your computer. So, being root on your computer is not going to make you root on any other device -- that is, not unless the operating system on the other device is set up to really trust your computer a whole lot (or screws up).
So we might ask: why isn't it configured this way? Well, by way of analogy, imagine if anybody could get into your car and drive away, so long as they had the keys to some car! Or, to make that a slightly more fair analogy: imagine that your car would automatically assume that anyone who drives up in some other car, should be trusted and allowed to drive yours. Sounds like a bad policy, right?
As you may have noticed, some locks -- quite a lot of them, really -- actually do work that way: anybody with any key can unlock them. But those are not the kind of locks you want protecting your valuables while you're away
anonywimp said:
Your android device has an operating system, which gets to make the rules about root. So does your computer. So, being root on your computer is not going to make you root on any other computer -- that is, not unless the operating system on the other computer decides that it really trusts your computer a whole lot (or screws up).
We might ask: why isn't it configured to trust you? Well, by way of analogy, imagine if anybody could get into your car and drive away, so long as they had the keys to some car! Or, to make that a slightly more fair analogy: imagine that your car would automatically assume that anyone who drives up in some other car, should be trusted and allowed to drive yours. Sounds like a bad policy, right?
As you may have noticed, some locks -- quite a lot of them, really -- actually do work that way -- anybody with any key can unlock them. But those are not the kind of locks you want protecting your valuables while you're away
Click to expand...
Click to collapse
But theoretically in the real world i would just pop your cars hood, link up a NAPA BlueFuel On Board Diagnostics Tool (costs about $80 on Amazon) to your cars CPU, then proceed to unlock the doors with a button or simple OBDT terminal command. Then I could Jump Start your vehicle (after i stuck any similar models key into your ignition) & proceed to drive your car wherever i wanted just as if it were my own.....
What enabled me to do this? Having a similar models keys & some in depth administrative authority over your vehicle
For the sake of comparison those keys (Linux Kernel) and the Administrative Authority (The OS used to build the phones platform) should give me the same results (in my mind)
LilAnt530 said:
But theoretically in the real world i would just pop your cars hood, link up a NAPA BlueFuel On Board Diagnostics Tool (costs about $80 on Amazon) to your cars CPU, then proceed to unlock the doors with a button or simple OBDT terminal command. Then I could Jump Start your vehicle (after i stuck any similar models key into your ignition) & proceed to drive your car wherever i wanted just as if it were my own.....
What enabled me to do this? Having a similar models keys & some in depth administrative authority over your vehicle
For the sake of comparison those keys (Linux Kernel) and the Administrative Authority (The OS used to build the phones platform) should give me the same results (in my mind)
Click to expand...
Click to collapse
Actually, this is very often how Windows Domains work. Just "run as Administrator" and you have rooted your whole organization. Obviously that's not how it's intended to work and this would represent a mis-configuration of your Domain if your IT department intended to maintain administrative control. But, for whatever reason, this really does happen; it's not even all that rare.
anonywimp said:
Actually, this is very often how Windows Domains work. Just "run as Administrator" and you have rooted your whole organization. Obviously that's not how it's intended to work and this would represent a mis-configuration of your Domain if your IT department intended to maintain administrative control. But, for whatever reason, this really does happen; it's not even all that rare.
Click to expand...
Click to collapse
Okay Windows is not based on the Linux Kernel, you have no SuperUser capabilities as described on Ubuntu,
The main points of this disccusion were to point out the similarities in platforms & then again in the SU Binaries used on each specifically, thus (hopefully) creating a gap we could bridge, allowing for previous "unrootable" devices to gain root .

Categories

Resources