Run adb and fastboot in Termux without root permissions!
This is a modified version of adb and fastboot which enables debugging of one Android device from another via USB cable. It should work with any USB-C male-to-male cable or the corresponding OTG adapter cable in case of micro USB.
- install Termux from mediafire click the image π
- install Termux:API from F-Droid click the image π
- in Termux:
https://youtu.be/uYIxucVW1Xw?si=k16dl0M5IqCYM1W9
https://www.mediafire.com/file/ol1bgomiymum5yu/Termux_0.118.0%2Bbe66cff.apk/file
https://f-droid.org/repo/com.termux.api_51.apk
pkg update
curl -s https://raw.githubusercontent.com/Gtajisan/termux-adb/master/install.sh | bash
$ curl -s https://raw.githubusercontent.com/nohajc/termux-adb/master/install.sh | bash
intsall these file https://github.com/Gtajisan/termux-adb/archive/refs/tags/0.2.0.zip
ls
unzip termux-adb-0.2.0.zip
ls
cd termux-adb-0.2.0
ls
./install.sh
termux-adb version
termux-adb devices
aging
termux-adb devices
termux-adb reboot bootloader
check device aging
termux-adb devices
follow YouTube video step exist on termux open aging termux
termux-adb devices
termux-adb flash recovery [ past you're file location ]
termux-adb flash recovery
boot recovery and aging you're recovery located
termux-fastboot boot
- this will add
termux-adb
apt repository and install the corresponding public gpg key - latest version of
termux-adb
andtermux-fastboot
will be installed - any future upgrades will be done as part of
pkg upgrade
Both termux-adb
and termux-fastboot
are drop-in replacements for the original commands so the usage is exactly the same.
The commands were only renamed to avoid collision with the official android-tools
Termux package (which contains more tools beside these two).
The official termux-packages build environment is used (forked to add the termux-adb
package).
For more information, please refer to the Termux documentation:
- https://github.com/termux/termux-packages/wiki/Build-environment
- https://github.com/termux/termux-packages/wiki/Building-packages
Using termux-usb
and querying device serial number with libusb
tends to be slow. That's not a problem for adb which runs as a daemon and scans USB devices periodically. However, it is quite noticable for termux-fastboot
commands because fastboot doesn't use any background service. This can potentially be improved in a future release.
Termux has the android-tools
package which contains adb
and fastboot
but it normally works on rooted devices only.
This is mainly due to filesystem permissions required by adb when enumerating USB devices (traversing /dev/bus/usb/*
).
There is, however, Android API exposed by termux-usb
utility which gives you a raw file descriptor of any connected USB device after manual approval by the user.
Of course, adb
by itself doesn't know anything about termux-usb
nor it can take raw file descriptors from command-line or environment.
If it cannot access /dev/bus/usb
, it just won't detect any connected devices. This is where termux-adb
comes in.
Both adb
and fastboot
are patched to scan for USB devices using the termux-usb
command. Furhtermore a Unix Domain Socket is used to transfer the obtained file descriptors from child process to the parent (i.e. termux-adb
runs termux-usb
for every detected device which in turn runs termux-adb
in a special mode that will only send USB file descriptor to the UDS file descriptor provided by environment variable).
This way we don't complicate the user experience and we can work with any number of devices connected at once (e.g. if you have a USB hub connected to the OTG adapter).