Arch linux adb fastboot

If you using archlinux and want to develop android application. Then you must install Android SDK. To install manually you can download the package from android sdk website.

About Android SDK:
The Android SDK provides you the API libraries and developer tools necessary to build, test, and debug apps for Android.

For the easy way to install, Android SDK & Platform Tools is available on AUR.
Note if you using Archlinux 64bit: You must enable multilib repo, to be able install the required packages.

1. Android SDK

$wget https://aur.archlinux.org/packages/an/android-sdk/android-sdk.tar.gz
$tar -xvzf android-sdk.tar.gz
$cd android-sdk
$makepkg -s
$sudo pacman -U *.pkg.tar.xz

2. Android

$wget https://aur.archlinux.org/packages/an/android-sdk-platform-tools/android-sdk-platform-tools.tar.gz
$tar -xvzf android-sdk-platform-tools.tar.gz
$cd android-sdk-platform-tools
$makepkg -s
$sudo pacman -U *.pkg.tar.xz

Done, all files installed on /opt/android-sdk/
To be able to use adb, fastboot, ddms, other commands you must create symbolic link to executable file manually. For this example:

and so on for other binary/executable files.

To run Android SDK, on LXDE is available on Programming Menu, then choose Android SDK. If android SDK not running. Same as above

Now try again to running Android SDK, if still not running try run on terminal

That’s some application on Android SDK & Platform Tools, now you can develop android Apps on Archlinx.

For Installing ADB only you can install android-tools

Источник

Android Debug Bridge

The Android Debug Bridge (ADB) is a command-line tool that can be used to install, uninstall and debug apps, transfer files and access the device’s shell.

Installation

ADB is part of the Platform-Tools SDK package and the android-tools package.

Usage

Connect device

For some devices, you may have to enable MTP on the device, before ADB will work. Some other devices require enable PTP mode to work.
Many devices’ udev rules are included in libmtp , so if you have this installed, the following steps may not be necessary.
Make sure your USB cable is capable of both charge and data. Many USB cables bundled with mobile devices do not include the USB data pin.

To connect to a real device or phone via ADB under Arch, you must:

You might want to install android-udev if you wish to connect the device to the proper /dev/ entries.
plug in your android device via USB.
Enable USB Debugging on your phone or device:
- Jelly Bean (4.2) and newer: Go to Settings > About Phone tap Build Number 7 times until you get a popup that you have become a developer. Build number may be under a menu called Software info on newer Android OS versions. Then go to Settings > Developer > USB debugging and enable it. The device will ask to allow the computer with its fingerprint to connect. Check allowing it permanently option will copy ~/.android/adbkey.pub to the target phone’s /data/misc/adb/adb_keys location.
- Older versions: This is usually done from Settings > Applications > Development > USB debugging. Reboot the phone after checking this option to make sure USB debugging is enabled.

If ADB recognizes your device ( adb devices shows it as «device» and not as «unauthorized» , or it is visible and accessible in IDE), you are done. Otherwise see the instructions below.

Figure out device IDs

Each Android device has a USB vendor/product ID. An example for HTC Evo is:

vendor id: 0bb4 product id: 0c8d

Plug in your device and execute:

. Bus 002 Device 006: ID 0bb4:0c8d High Tech Computer Corp. .

Adding udev rules

If your device is not included in android-udev (or android-udev-git AUR ), use the following template to create a custom udev rule by replacing [VENDOR ID] and [PRODUCT ID] with the IDs of your device.

/etc/udev/rules.d/51-android.rules

SUBSYSTEM=="usb", ATTR=="[VENDOR ID]", MODE="0660", GROUP="adbusers", TAG+="uaccess" SUBSYSTEM=="usb", ATTR=="[VENDOR ID]", ATTR=="[PRODUCT ID]", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR=="[VENDOR ID]", ATTR=="[PRODUCT ID]", SYMLINK+="android_fastboot"

Detect the device

After you have setup the udev rules, unplug your device and replug it.

List of devices attached HT07VHL00676 device

If adb still does not detect the device after plugging your device back in, kill and restart the adb server as root and check devices again:

# adb kill-server # adb start-server $ adb devices

If adb devices still shows unauthorized next to your device, make sure that that device has debugging permission allowed on the device itself. A Allow USB Debugging? dialog should be presented when you physically connect the device. Select Always Allow. , then tap OK. If the dialog was never presented, try Settings > Developer Options > Revoke USB Debugging Authorizations, then tap OK, and repeat the steps in this section. If you still do not see the Allow USB Debugging? dialog, and the device is listed as unauthorized, then enter the Developer Options on the device and first uncheck USB Debugging and then check it again.

Transferring files

You can now use adb to transfer files between the device and your computer. To transfer files to the device, use:

$ adb push what-to-copy where-to-place

To transfer files from the device, use:

$ adb pull what-to-pull where-to-place

Backup and restore

You can also backup and restore your device with adb. Moreover, no root is required to follow the process. The commands below led to backup your device to a single file which can also be successively restored.

The command to create a backup is:

$ adb backup -apk -shared -all -f backupFileName.ab

The command parameters list is:

adb backup [-f ] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] []

Then confirm the process on your device’s display and provide a password whether a backup password has been set before.

The command to restore a previous backup is:

$ adb restore backupFileName.ab

Note: Remember that restoring operation will replaces your device contents with the backup contents.

Tools building on ADB

adbfs-rootless-gitAUR – mount an Android device connected via USB.
adb-sync-gitAUR – a tool to synchronize files between a PC and an Android device using the ADB protocol.
androidscreencast-binAUR – view and control your Android device via ADB from a PC.
logcat-colorAUR – a colorful and highly configurable alternative to the standard adb logcat command.
scrcpy – display and control your Android device.
qtscrcpyAUR – Android real-time display control software.

Troubleshooting

Empty device list

A possible cause for your device not showing up is not having enabled USB debugging on your device. See enable USB debugging.

No permissions error

If the device shows up with a «no permissions» label, it probably has a different vendor/product ID with respect to the ones collected by android-udev .

This can happen for instance when the device uses a custom ROM, or when it is switched from MTP to USB tethering mode, sideload and/or fastboot mode. Verify the actual device’s ID with lsusb and #Adding udev rules.

Источник

Arch Linux User Repository

@zblissbloom @SamLukeYes I got the same error when building this package. And I solved this problem by replacing gradle with gradle6 .

simona commented on 2021-05-10 15:26 (UTC)

SamLukeYes commented on 2021-05-08 02:40 (UTC)

I also had trouble building this package, so I made xiaomi-adb-fastboot-tools-bin , which uses the official jar directly.

zblissbloom commented on 2021-05-06 15:41 (UTC)

EgidioCaprino commented on 2021-04-27 17:42 (UTC)

Should the jre11-openjdk be java-environment instead? What if you use another JDK rather than OpenJDK?

RogueGirl commented on 2021-04-25 01:11 (UTC)

can you please change jre11-openjdk to jre-openjdk ?

niva commented on 2021-02-02 20:10 (UTC) (edited on 2021-02-02 20:24 (UTC) by niva)

* What went wrong: java.lang.UnsupportedClassVersionError: org/openjfx/gradle/JavaFXPlugin has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 > org/openjfx/gradle/JavaFXPlugin has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime nly recognizes class file versions up to 52.0

The same error krackpipe got. Does not matter if I install jdk11-openjdk or jdk-openjdk.

archcid commented on 2020-11-07 19:29 (UTC)

aur/xiaomi-adb-fastboot-tools 7.0.3-1 -> 7.0.3-1

theopouris commented on 2020-10-29 08:52 (UTC)

Hi krackpipe, I updated the dependencies so it picks only jre11, as the option «>=11» did not seem to work. I can see that you are using an older version of Java.

krackpipe commented on 2020-10-28 17:34 (UTC)

Thanks for maintaining this application. I noticed java version problems with compiling lately. No errors with downloading, with Gradle, or any initialization, but compiling fails java checks.

$ uname -r 5.9.1-arch1-1 $ java -version openjdk version "1.8.0_265" OpenJDK Runtime Environment (build 1.8.0_265-b01) OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode) $ yay -S xiaomi-adb-fastboot-tools [snip] FAILURE: Build failed with an exception. * What went wrong: java.lang.UnsupportedClassVersionError: org/openjfx/gradle/JavaFXPlugin has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 > org/openjfx/gradle/JavaFXPlugin has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Linux for us

To change or install custom ROM on an Android device, you must be in possession of ADB and Fastboot tools.

Under ArchLinux / Manjaro, ADB and Fasboot are in deposits together in one package. In Debian / Ubuntu, according to the freshness of the distribution, they are present in deposits or through the addition of a PPA.

ADB and Fastboot install in ArchLinux & Manjaro

ADB and Fastboot come together in a single package, available on the repo Community: android-tools

ADB and Fastboot install on Debian / Ubuntu / Linux Mint

5 commentaires:

Linux For Us: How To Install Adb And Fastboot On Archlinux / Manjaro And Debian / Ubuntu >>>>> Download Now

Linux For Us: How To Install Adb And Fastboot On Archlinux / Manjaro And Debian / Ubuntu >>>>> Download LINK

Linux For Us: How To Install Adb And Fastboot On Archlinux / Manjaro And Debian / Ubuntu >>>>> Download Full

Your File is Very Usefull File. 100% working. Thanks For Uploading. Please More File Uploading.

Please Visit Our Website,Mobile Flash tool,,FastBoot Frp Remover Tool,Country Unlock Tools,iPhone Unlock tools,PC Software Download,
Usb Flash Tool Mtk,Spd,Qualcoumm,Samsung, ADB Tool Free Download,Iphone Unlock Tool Download,
All Flash Box Driver Download, Android BackUp Software Tool, Mobile flashing Tools , Android Data Recovery Tools,Cracked Box,EMMC Rom Read And Write Tool Download,Huawei Frp Tool Download,Iphone Icloud Download,
LG Root Tools Download,LG FRP Unlock TOOL,Motorola Frp Unlocker, Nokia unlock tool Download, Oppo Unlock Tools Download,Qualcomm IMEI Repiar tools,
Qualcoum cpu frp tools Download,Android Root Software Download,Samsung FRP Tools Download,Box Setup File Download,
Spd Imei Repair Tools, Xiaomi Unlocker Tools ,Xiaomi Usb Drive Download, Etc File Tool Free Download BY www.AndroidtipsBD71.xyz
Répondre Supprimer

Linux For Us: How To Install Adb And Fastboot On Archlinux / Manjaro And Debian / Ubuntu >>>>> Download Now

Linux For Us: How To Install Adb And Fastboot On Archlinux / Manjaro And Debian / Ubuntu >>>>> Download LINK

Linux For Us: How To Install Adb And Fastboot On Archlinux / Manjaro And Debian / Ubuntu >>>>> Download Full

Источник