UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Failed to install os on Google Pixel 3a

    Scheduled Pinned Locked Moved Solved
    Support
    2
    9
    488
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • rthR
      rth
      last edited by arubislander

      Completely new to Ubuntu Touch and Android, but I have more than 20 years of experience as a Linux user/developer/sysadmin (once I built the LFS :P)

      A completely new Google Pixel 3a was bought to install Ubuntu Touch. I download a fresh installer (app image, ubports-installer_0.10.0_linux_x86_64.AppImage) from the official website. My main computer runs PoP_OS! I diligently followed instructions but ended up in recovery mode. Several attempts to reinstall OS did not work. I screen-recorded the last attempt.

      I might do something silly, but I can't find a way out. I stuck into fastboot mode or, just after installation, in recovery mode (see video).

      What did I do wrong?

      MrT10001M 1 Reply Last reply Reply Quote 0
      • MrT10001M
        MrT10001 @rth
        last edited by

        @rth If you did that before and it didn't work, then start again. Also you shouldn't have to mess with the slots, unless you had another Android based ROM that required it.

        Xiaomi Redmi Note 7.... And more...
        I have too many devices...

        rthR 1 Reply Last reply Reply Quote -1
        • MrT10001M
          MrT10001 @rth
          last edited by

          @rth You have installed the correct ROM as stated in the instructions - this is a must?
          You have the latest ADB and Fastboot drivers installed?
          The Device is picked up in Terminal under Fastboot and ADB when the device is in recovery?
          Don't run the UT installer from Terminal or with Sudo. Sudo causes issues, but I have also found occasionally opening the installer in terminal doesn't always work (Ubuntu 22.04) (experiences may vary).
          Install Stable first and get the device up and running, the others (dev and RC) may have issues that won't allow boot.
          I have put the correct ROM on using the Android Recovery Tool with Chrome Browser - IT HAS to be Chrome, it won't work on other browsers. This has always worked for me on the Pixel Phones. Fastboot should work, but doesn't always when getting to the correct ROM. When the correct ROM is installed, set up Android first before attempting a UT install.

          Xiaomi Redmi Note 7.... And more...
          I have too many devices...

          rthR 1 Reply Last reply Reply Quote 0
          • rthR
            rth @MrT10001
            last edited by

            @MrT10001 Thank you for looking in my problem!

            • ROM: Hm, I don't know! The installer (1) detected the device correctly, (2) instructed me how to get to the developer mode on android, enable OEM, enable USB debugging, (3) instructed me how to disable boot lock, (4) did it magic. How can I check that the installer installed the correct ROM?
            • ADB and Fastboot drivers: the same. How can I check that they are the latest?
            • The installer picks the device and said that it flash boot, then installer reboots the device and asks to turn into rescue mode and says it installing the main OS (see video)
            • I'm running it from a terminal, but without sudo. At first run, the installer asked for the root privileges to install drivers and correct udev rules - i allowed.
            • as you can see from the video, I'm installing 20.04 (stable)

            @MrT10001 said in Failed to install os on Google Pixel 3a:

            I have put the correct ROM on using the Android Recovery Tool with Chrome Browser - IT HAS to be Chrome, it won't work on other browsers. This has always worked for me on the Pixel Phones. Fastboot should work, but doesn't always when getting to the correct ROM. When the correct ROM is installed, set up Android first before attempting a UT install.

            Sorry I don't get that. Where did you put it and how to install the correct ROM?

            Thank you again

            rthR 1 Reply Last reply Reply Quote 0
            • rthR
              rth @rth
              last edited by

              @MrT10001
              OOPS! Sorry, I missed the link to the video.
              Here is the recording

              Note: I skipped the drivers and rules installation because they were installed at first launch of the installer

              rthR MrT10001M 2 Replies Last reply Reply Quote 0
              • rthR
                rth @rth
                last edited by

                P.S. I installed the deb package and ran it from the menu (not from a terminal), the result was the same.

                P.P.S After installation the phone in UBports Recovery with options reboot, Advance, and Factory reset. lsusb sees the device

                Bus 003 Device 016: ID 18d1:d001 Google Inc. Nexus 4 (fastboot)

                However, if I press reboot, it stuck in the fastboot screen and doesn't move in any way.

                1 Reply Last reply Reply Quote 0
                • MrT10001M
                  MrT10001 @rth
                  last edited by MrT10001

                  @rth 9.0.0 (PQ3B.190801.002, Aug 2019) is the correct ROM to install.

                  Download from here.

                  Install this ROM and set Android up on the device, this is a must or you will experience this issue. Also check this out - it may/may not be something.

                  If you have issues like this it is prudent to start from scratch to ensure you haven't missed something.

                  I would install the Stock ROM using Google Chrome Android Flash Tool, ensuring these:
                  So reinstalled the stock ROM following the instructions:
                  Force flash all partitions - ticked
                  Disable verification - ticked
                  Disable verity - ticked                  .

                  Then I would set Android up, enable Developer Options, USB debugging and try with UT again.

                  And as a side note, I unplug the device, boot it into recovery, plug it back in and then hit continue on the installer.

                  Xiaomi Redmi Note 7.... And more...
                  I have too many devices...

                  rthR 1 Reply Last reply Reply Quote 0
                  • rthR
                    rth @MrT10001
                    last edited by

                    @MrT10001 Let me try!
                    Can I just use CLI?

                    adb reboot bootloader
fastboot --slot=other flash bootloader **correct-mmage.img**
fastboot set_active other
fastboot reboot bootloader
fastboot set_active other
fastboot reboot bootloader
fastboot reboot
                    MrT10001M 1 Reply Last reply Reply Quote -1
                    • MrT10001M
                      MrT10001 @rth
                      last edited by

                      @rth If you did that before and it didn't work, then start again. Also you shouldn't have to mess with the slots, unless you had another Android based ROM that required it.

                      Xiaomi Redmi Note 7.... And more...
                      I have too many devices...

                      rthR 1 Reply Last reply Reply Quote -1
                      • rthR rth has marked this topic as solved on
                      • rthR
                        rth @MrT10001
                        last edited by

                        @MrT10001, my deep respect! It worked!

                        Thank you so much!

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post