M
Mixlee

  • 7 days ago
  • Joined 9 days ago
  • In CLI install < waiting for any device >

    tV0gr debian-based live usb

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

    • In CLI install < waiting for any device >

      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...

          • In CLI install < 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.
            • In fastboot waiting for device

              redacted echo 0 | sudo tee /sys/bus/usb/drivers_autoprobe
              After installing, you can undo this by rebooting or by running the following command:

              echo 1 | sudo tee /sys/bus/usb/drivers_autoprobe

              Hi,
              $ echo 0 | sudo tee /sys/bus/usb/drivers_autoprobe
              0
              didn't solve it on my Pixel6a (if someone could have a look at my Pixel6a posting). Also didn't work on a Pixel 8a. :(

              Thank you.

              • In CLI install < waiting for any device >
              • In CLI install < waiting for any device >

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

                But still:

                fastboot flashing unlock
< waiting for any device >
                • In CLI install < waiting for any device >

                  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.