You are not logged in.
Pages: 1
Topic closed
I have a dual boot setup with Windows. The problem is that fastboot is not working on Arch Linux.
I'm using the same cable to test it. I'm sure the phone is in fastboot mode. I'm using the android-tools package. I don't think it matters, but I have a Xiaomi Mi6 with MIUI 10 Global, with unlocked bootloader.
fastboot devices
This command initially returned:
no permissions; see [http://developer.android.com/tools/device.html] fastboot
It worked with root permission, but I later found a better solution that involved a udev rule (lsusb gave some useful information) that could have helped to make it work entirely.
Bus 001 Device 011: ID 18d1:d00d Google Inc.
/etc/udev/rules.d/51-android.rules
------------------------------------------------------
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
sudo udevadm control --reload-rules && udevadm trigger
Anyway, when I try to do ANY other operation the problem persists: it gets stuck, with no response. Examples:
fastboot reboot
fastboot flash recovery /media/hdd/twrp-3.2.1-1-sagit.img
The same commands, with the same exact files (shared volume), are working on Windows.
What the hell is going on? I'm posting here because the same problem, posted by another user, didn't get much attention on xda, and after all, it's a linux problem.
Thanks in advance
EDIT: Grammar
Last edited by supremecoconut (2018-06-21 12:10:34)
Offline
I have added my user to the 'adbusers' group and these rules in /etc/udev/rules.d/51-android.rules:
# Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="adbusers"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
# Nexus 9
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", SYMLINK+="android_fastboot"
Offline
Is there any information printed in dmesg that might point towards a reason, after attempting to execute a command?
Offline
I have the same issue.
`fastboot devices` lists the xiaomi mi 8 lite, but no actual commands work. dmesg says nothing at all. not even `fastboot get all` works. just gets stuck forever. this happens on 2 arch machines. one is up to date, another is 2 weeks old. my sony z5c fastboot works just fine
interestingly, fastboot works fine with the xiaomi on windows.
Last edited by eimis (2019-06-27 18:39:13)
Offline
Have you tried installing android-udev as specified in the note at Android#Fastboot?
Offline
Please note that you are digging out a three year old thread.
https://wiki.archlinux.org/title/Genera … bumping%22
Closing.
Offline
Pages: 1
Topic closed