You are not logged in.
My issue is widely reported on internet, but I couldn't find an answer (except a poor quality cable). Here is my issue.
I have GrapheneOS rom installed on my device, and /etc/udev/rules.d/51-android.rules installed by arch linux.
I can run the following basic commands:
% adb devices
List of devices attached
29231JEGR05502 device
% fastboot devices
29231JEGR05502 fastboot
% lsusb
Bus 002 Device 036: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)there is no issues with the above commands. Now, when in fastboot mode, I want to flash an OTA zip.
% export ANDROID_PRODUCT_OUT=extracted <-- extracted is a folder in my current directory
% ls -al extracted
total 1.6G
drwxr-xr-x 1 gabx gabx 152 Dec 9 04:47 ./
drwxr-xr-x 1 gabx gabx 120 Dec 9 06:21 ../
-rw-r--r-- 1 gabx gabx 22 Dec 9 04:47 android-info.txt
-rw-r--r-- 1 gabx gabx 64M Dec 9 04:47 boot.img
-rw-r--r-- 1 gabx gabx 278 Dec 9 04:47 fastboot-info.txt
-rw-r--r-- 1 gabx gabx 1.5G Dec 9 04:47 system.img
-rw-r--r-- 1 gabx gabx 8.0K Dec 9 04:47 vbmeta.img
-rw-r--r-- 1 gabx gabx 64M Dec 9 04:47 vendor_boot.img
% fastboot flashall --skip-reboot
< waiting for any device >and this message will stay for age until I stop the command.
Cany anyone help me to solve this issue? Why the fastboot flashall command can't find the device?
Last edited by gabx (2025-12-09 07:48:10)
Offline
sanity check: is the phone actual in the fastboot menu?
what happens when you manual reboot the phone into fastboot and only connect the cable when fastboot waits for it? IIRC last time I did a flash (years ago, windows) I was prompted to attach the cable only after a specific point so the flash could hook right into the initialization
Offline
The content of the extracted folder was far from being completed, thus the impossibility for fastboot to flash and its wait status
Offline