Hello,
my problem:
< waiting for any device >

My setup:
Ubuntu 22.04.5 LTS
Pixel6a
Android security updates: 5.8.2022
Google Play: 1.7.2022
USB-C to USB-A cable: LogiLink USB 3.2 Gen 1 Cable (CU0167)

What I did:
CLI install guide
Developer options = OEM unlocking

export PATH="$PWD/platform-tools:$PATH"

fastboot --version
fastboot version 35.0.2-12147458
Installed as /home/user/platform-tools/fastboot

apt-cache policy fwupd
1.7.9-122.04.3

sudo systemctl stop fwupd.service

Booting into the bootloader interface
hold volume down button while the device boots
Fastboot Mode
...
bluejay-1.2-8893284
...
Device state: locked
Bootslot a

In chapter Connecting the device its said:

Connect the device to the computer. On Linux, you'll need to do this again if you didn't have the udev rules set up when you connected it.

I'm not sure if it needs to connect again the usb cable (when exactly?) , after the Pixel was shut down, to boot in Fastboot Mode?

fastboot flashing unlock
< waiting for any device >
What could be solution? Thank you.

PS: In the "CLI install guide", I didn't read to enabled "USB debugging". I'm used to do for flashing other custom roms.
"USB debugging" does not matter?

  • de0u replied to this.

    Maybe it does not matter, but
    adb reboot bootloader
    boots into "Fastboot Mode"

    But still:

    fastboot flashing unlock
< waiting for any device >

      Ok, just used a Fairphone with iodeOS and USB-C to USB-C cable and unlocking the Pixel6a via the Fairphone with Cromite (a Bromite fork) browser, it worked: https://github.com/uazo/cromite

      But "Obtaining factory images" didn't work.
      So back to CLI...
      Noticed, that in "every new"(?) terminal session, it needs to renew fastboot again(!) to version 35.0.2-12147458
      On my Ubuntu fastboot jumped back several times to fastboot version 28.0.2-debian.

      Obtaining openssh

      Flashing factory images
      bsdtar xvf bluejay-install-2025032100.zip
      ok

      Next problem:
      bash flash-all.sh
      Available devices:
      no permissions (missing udev rules? user is in the plugdev group); see [http://developer.android.com/tools/device.html] fastboot usb:1-4
      I tried again:
      sudo apt install android-sdk-platform-tools-common
      but it didnt solved the udev permissions problem.

      • de0u replied to this.

        Mixlee USB-C to USB-A cable: LogiLink USB 3.2 Gen 1 Cable (CU0167)

        I have never heard of "LogiLink", and a quick search turns up mixed reviews for this cable.

        Mixlee In the "CLI install guide", I didn't read to enabled "USB debugging".

        That is not in the instructions because it is not necessary.

        Mixlee Noticed, that in "every new"(?) terminal session, it needs to renew fastboot again(!) to version 35.0.2-12147458

        If fastboot is installed manually (which it should be for an old Ubuntu release) and the PATH change is made at the shell prompt then it must be re-done at the shell prompt whenever a new shell is launched.

        Has the web installer been tried on the Ubuntu system?

                Mixlee When running into trouble it may be prudent to try using the best ingredients. It is not clear LogiLink is the best cable; the CLI method is not recommended for most users; Cromite is not one of the recommended browsers.

                    I only have limited experience but I think that you are experiencing the same udev problem still. Only that one problem.

                    Personally I have never encountered the issue. I have always used one of the many debian-based live usb and downloaded fastboot, the image, checked the signatures, and so on. Only once I had an issue (I suspect it was the usb port on the computer).

                    From my experience with 'fastboot flashing unlock' command, all you need is to be in the bootloader interface. It won't time-out, and I am pretty sure that I attempted to connect and reconnect multiple times and it doesn't matter (assuming no udev issues). Then it will unlock once the command is run and reach the phone, which an udev rule seems to prevent right now. I never had USB debugging enabled and I have done it many times on a Pixel 7.

                    Again I don't have much experience with udev but my understanding is that if you had to change them, you would need to reconnect in order for that udev rule to take effect.

                    Fastboot is part of the stand-alone platform-tools downloaded with curl. While using different terminal sessions is not recommended in the instructions, the package you downloaded will/should remain and only the PATH need to be declared every times, and possibly the udev rule(s). If the version is not right it might means that you already have a different version of fastboot installed. GrapheneOS is a bit demanding on this and will not flash if fastboot is too old (from my experience). I had a clear error message about it.

                    It might be worth trying to log-off the X session and use a proper terminal session with Ctrl+F key, e.g. Ctrl+F3. It's possible that another running program interferes with fastboot I think.

                      de0u If fastboot is installed manually (which it should be for an old Ubuntu release) and the PATH change is made at the shell prompt then it must be re-done at the shell prompt whenever a new shell is launched.

                      That understanding helped. And I made a Ventoy Live USB Stick with Ubuntu 24.10, that worked well! (beside some workarounds because of "disk space"...)

                      de0u Has the web installer been tried on the Ubuntu system?

                      Yes Brave, in both:

                      1. Ubuntu 22.04.5 LTS, issues with web*** and how to disable the Brave "build in protection" because I needed first to study, how it is called in my language and that Brave cant be changed to English. :(
                      2. Live USB Stick with Ubuntu 24.10 Brave could not installed properly:

                      Install with one command
                      curl -fsS https://dl.brave.com/install.sh | sh
                      didn't work...

                      de0u the CLI method is not recommended for most users
                      I'm far from expert, but I'm used to use CLI for flashing custom roms...

                            tV0gr debian-based live usb

                            As written, yes that solved my problems... ;))