Hi,
I'm looking for adb for mips-linux. I want to execute adb commands from my mips based router over wifi and avoid having to run adb from pc.
Unfortunately I was unable to find a binary and any make files posted several years ago like here:
GitHub - karfield/adb: a standalone-built version of android adb
a standalone-built version of android adb. Contribute to karfield/adb development by creating an account on GitHub.
github.com
and
Build adb for Loongson(MIPS) – Hev's Blog
don't work on the current version anymore.
I need a adb version that is capable to work via adb wifi as the current version of the adb binaries for windows and Linux do.
Anyone has made an adb binary for mips and could release it? I want to avoid having to compile the whole android source code just to use 2 mb of files from it.
Thanks!
Related
I installed ubuntu 9.10 and fedora
apt-got openjdk and then ran android sdk to download and unpack platform-tools in the right place..
Is there a way to use adb and fastboot so I won't need my laptop to connect to my other android devices? or is it impossible on the ATP?
I get "cannot execute binary files" from terminal..
thanks!
I'm unaware of any adb client binaries that are built for use on an ARM platform, but if you happen to find one, please share.
I have notes on setting up the android sdk on the TF's, problem is where to find source for aapt and porting it to Linux/ARM. Eh, well disregarding renderscript...
Adb will be the same case as aapt afaik.
Sent from my Transformer Prime TF201 using Tapatalk
adb is in system/bin of the device..
I can share it if you need it
now it's fastboot that I want... aaaarrrm...
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needing a PC).
So..... Would it be possible?
This would fare better in the Android Q&A forum. I'll flag it to the forum mod and ask them to move it
Done, and Thank You Sir.
adb
pokepal101 said:
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needinig a PC).
So..... Would it be possible?
Click to expand...
Click to collapse
I want to start by saying I'm no expert, but to the best of my knowledge, this is how it works.
adb runs native on android, the android property is ro.secure=1 this is found in the default.prop file. ADB is run in user privilege mode with this property setting. Not all of the adb shell commands will work with the device in this mode. With ro.secure=0 property setting, adb will run with root user privileges and all adb shell commands will function. There is an adb comand that when issued will return the value of the setting, but off the top of my head I could not tell you it. The file default.prop is part of the boot.img and will load every time the device is booted, so to edit the file the boot.img would have to be unpacked, edited, repacked, and pushed to the device boot partition.
I don't know why you would want to connect two smartphones using adb and don't know if it is even possible. It is probably best to run the binary with a script on the device where you want it installed. Good Luck with your project.
Sorry, I don't think I quite understand....
fdaconta said:
Not all of the adb shell commands will work with the device in this mode
Click to expand...
Click to collapse
I'm sorry if I'm not making myself clear, but I'm talking about running the ADB client/server on an android phone (normally done on a development computer), not the ADB daemon.
fdaconta said:
It is probably best to run the binary with a script on the device where you want it installed
Click to expand...
Click to collapse
That's also not possible, as the script involves running some complicated ADB-ish things like "adb restore" and running while device #2 is turned off - hence the need for device #1.
I am looking for updated ADB binaries for ARM. I've only been able to find the binaries for Android 4.4.2. I want to be able to use ADB/fastboot from my tablet or phone to communicate with another Android device. Yes both are OTG enabled. You can do this by placing the binaries in system/bin on rooted devices. I just need binaries that are up to date. Where might I get those?
Operating System in use:
Debian GNU/Linux 9.4 (stretch)
Linux 4.9.0-6-amd64
Telephone model to be used: ZTE Z5s mini NX406E
Processor: Qualcomm Snapdragon 400/410 1,21 GHz
Android 4.4.4 KitKat
I try to make a backup using the adb, using the command:
adb backup all or adb backup -all
example:
[email protected]:/home/life/adb# adb backup -all
Now unlock your device and confirm the backup operation...
I go to the phone screen, I enter the password and the copy continues, Hard pains about 3 seconds this, I only create a file of barely weighs about 549 bytes, when I review the adb versions, performing the following steps:
[email protected]:/home/life/adb# adb version
Android Debug Bridge version 1.0.36
Revision 1:7.0.0+r33-1
[email protected]:/home/life/adb# adb shell
[email protected]:/ $ adb version
Android Debug Bridge version 1.0.31
[email protected]:/ $ exit
Question # 1: They are different versions, for that reason I can not make the backup?
Question # 2: I need to have in Debian the same version that has the phone to make the backup, is it the only way if I want to use the adb?
Question # 3: How can I locate and install version 1.0.31 of the adb in my debian?
Question # 4: Can I have different installed versions of the adb at the same time in my debian without having any kind of problems?
Note: I am learning to disarm ROM, to study them and start creating new ones.
Thanks in advance for any assistance.
sorry my bad english, I use google translate
Question.
I forced myself to use Windows 7 to be able to have part of the answers I'm looking for, even though using Windows 7 I was able to make the copies, having the same version of the mobile in Windows 7, I am interested in knowing in what way using Debian I can do it. I know at least that if the versions are different there are limitations. But Windows is easy to have a folder with each version of adb, however in Linux is not so easy, at least for those who do not have much experience in this field.
Thanks in advance for any assistance.
sorry my bad english, I use google translate
---------------
My Question is:
How do I go about using the "adb keygen" command to generate a key pair for each device. AND where do I move those keys so that the devices can connect to each other via the ADB command line interface?
---------------
Currently, my PC is out of order. So I have no way to use ADB via a PC. What I have managed to accomplish so far is rooting my Galaxy Tab 3 [Magisk], Galaxy S5 [SuperSu], and Galaxy S3 [SuperSu]. The devices are running Resurrection Remix Oreo , Lollipop, and Kitkat 4.4, respectively.
***
*** I want to use my tablet [Galaxy Tab 3] as the ADB Host for all my other androids to connect to. This way I can issue ADB commands over the network from my tablet's Termux environment. And I know my current issue has to deal with the ADB_VENDOR_KEYS, as well as "Step 5/6" in connection handshake outlined in the screenshot from "cstyan's adb documentation" on github.
Now each device is equipped with a Terminal Emulator or Termux, and an ADB binary compiled for the ARM architecture. [Android Debug Bridge version 1.0.36
Revision e25a9312d628-android]
I can connect to ADB over the network. I've already gotten the GS5 to connect to Tab3's ADB server. I can run the "adb devices" command after successfully connecting to a specific IP address, but the command always lists the device as "unauthorized". This is shown in my screenshot from my CLI. I'm being tripped up by oversight here because this is typically done automatically, not manually.
Do I need to keygen a pair on the tablet and copy that key-pair to my other devices? Or does each device need a copy of each other device's adb key? This should work. I should just have to do the legwork manually, since this isn't the standard way. On normal Linux/Windows the adb key is stored in the User's profile root in the ".android" folder, but where is the counterpart on the device itself? I already have my Tablet's private key in "/data/misc/adb/adb_keys"
I feel I am on the last step here. Where do I place the public keys on the device? All I need to do is authorize the device using my manually generated adb key. Everything else works, and then I wouldn't need to have my PC so high on my priority list. Can someone please help clarify the step or two that I am missing here please?