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

    No luck installing on my Pixel 2 (walleye)

    Scheduled Pinned Locked Moved Google Pixel 2/2 XL
    59 Posts 9 Posters 13.5k Views 4 Watching
    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.
      • L Offline
        ljrichards1066 @flohack
        last edited by

        @flohack I've got a working knowledge of it from messing around with rooting and Android roms. I'd certainly be willing to try. πŸ‘

        1 Reply Last reply Reply Quote 0
        • A Offline
          agates
          last edited by agates

          @Flohack I'm able to reproduce what @ljrichards1066 is saying with getting stuck on the Google logo. On first boot I had a ubports "installing update" screen and then it rebooted into this state.

          Also have no network connectivity to it, but I'm comfortable with the CLI I'll assist in debugging as needed πŸ™‚

          EDIT: FYI I flashed build PQ3A.190801.002 for walleye first, as instructed by the installer.

          1 Reply Last reply Reply Quote 0
          • flohackF Offline
            flohack
            last edited by

            Ok guys can you try the following:

            • Let it boot & fail
            • Long-press Vol-Down & Power to enter fastboot
            • select Recovery with up/down-key and power
            • Let it boot into recovery and execute the following command on your host: adb pull /sys/fs/pstore/console-ramoops

            Post this file to a pastebin and ping me back πŸ˜‰

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              agates @flohack
              last edited by

              @flohack Unfortunately, I don't have /sys/fs/pstore/console-ramoops. The pstore directory is empty πŸ˜•

              These were the logs I found, listed in the recovery, however:
              last_kmsg
              recovery.log
              system-image-upgrader.log
              ubuntu_updater.log

              In addition, rebooting into the recovery is extremely finicky. I had to re-flash the recovery to get in one time, and after the next install I rebooted into it successfully. I'll see if I can reproduce and get the error from the bootloader again.

              flohackF 2 Replies Last reply Reply Quote 0
              • flohackF Offline
                flohack @agates
                last edited by

                @agates Wait a second how did you flash recovery? The device should not even have a recovery partition...

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                A 1 Reply Last reply Reply Quote 0
                • flohackF Offline
                  flohack @agates
                  last edited by

                  @agates can you boot into recovery (Is it UBports recovery at least?) and then adb shell into it. Can you:

                  • mount /system_root
                  • ls -la /system_root, it should have a typical Linux appearance
                  • ls -la /system_root/var/lib/lxc/android, it should show android-rootfs.img

                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                  A 1 Reply Last reply Reply Quote 0
                  • A Offline
                    agates @flohack
                    last edited by

                    @flohack Apologies, I'm likely using the wrong term. I used the first part of the ubports installer to install the bootloader etc then quit.

                    However i was able to reproduce the same behavior without having to do that, also.

                    flohackF 1 Reply Last reply Reply Quote 0
                    • A Offline
                      agates @flohack
                      last edited by

                      @flohack Yes, all of those commands return as expected πŸ™‚

                      root@walleye:/ # mount /system_root                                                                                                                                                          
                      root@walleye:/ # ls -lh /system_root
                      total 56K
                      drwxr-xr-x   2 root  root   4.0K 2021-06-10 08:04 android
                      drwxr-xr-x   2 root  root   4.0K 1972-06-26 01:54 bin
                      drwxr-xr-x   2 root  root   4.0K 2016-04-12 20:14 boot
                      lrwxrwxrwx   1 root  root     14 1972-06-26 01:54 cache -> /android/cache
                      lrwxrwxrwx   1 root  root     13 1972-06-26 01:54 data -> /android/data
                      drwxr-xr-x   3 root  root   4.0K 1972-06-26 01:54 debian
                      drwxr-xr-x   4 root  root   4.0K 1972-06-26 01:54 dev
                      drwxr-xr-x 115 root  root   4.0K 1972-06-26 01:54 etc
                      lrwxrwxrwx   1 root  root     16 1972-06-26 01:54 factory -> /android/factory
                      lrwxrwxrwx   1 root  root     17 1972-06-26 01:54 firmware -> /android/firmware
                      drwxr-xr-x   3 root  root   4.0K 1972-06-26 01:54 home
                      -rwxr-xr-x   1 root  root   9.4K 2021-04-13 21:11 init
                      drwxr-xr-x  20 root  root   4.0K 1972-06-26 01:54 lib
                      drwx------   2 root  root    16K 1972-06-26 01:53 lost+found
                      drwxr-xr-x   2 root  root   4.0K 2021-06-08 22:33 media
                      lrwxrwxrwx   1 root  root     17 1972-06-26 01:53 metadata -> /android/metadata
                      drwxr-xr-x   3 root  root   4.0K 1972-06-26 01:54 mnt
                      lrwxrwxrwx   1 root  root     12 1972-06-26 01:54 odm -> /android/odm
                      drwxr-xr-x   3 root  root   4.0K 1972-06-26 01:54 opt
                      lrwxrwxrwx   1 root  root     16 1972-06-26 01:54 persist -> /android/persist
                      drwxr-xr-x   2 root  root   4.0K 2016-04-12 20:14 proc
                      lrwxrwxrwx   1 root  root     16 1972-06-26 01:53 product -> /android/product
                      drwx------   2 root  root   4.0K 1972-06-26 01:54 root
                      drwxr-xr-x  12 root  root   4.0K 1972-06-26 01:54 run
                      drwxr-xr-x   2 root  root   4.0K 1972-06-26 01:54 sbin
                      drwxr-xr-x   2 root  root   4.0K 2021-06-08 22:33 srv
                      drwxr-xr-x   2 root  root   4.0K 2016-02-05 09:48 sys
                      lrwxrwxrwx   1 root  root     15 1972-06-26 01:54 system -> /android/system
                      drwxrwxrwt   2 root  root   4.0K 2021-06-08 22:42 tmp
                      drwxr-xr-x   2 root  root   4.0K 2021-06-10 08:04 userdata
                      drwxr-xr-x  10 root  root   4.0K 1972-06-26 01:54 usr
                      drwxrwxr-x  11 audio camera 4.0K 2021-06-10 08:03 var
                      lrwxrwxrwx   1 root  root     15 1972-06-26 01:54 vendor -> /android/vendor
                      root@walleye:/ # ls -la /system_root/var/lib/lxc/android
                      total 322492
                      drwxrwxr-x 5 audio camera      4096 1972-06-26 01:54 .
                      drwxrwxr-x 3 audio camera      4096 2021-06-10 08:03 ..
                      -rw-rw-r-- 1 audio camera 330203136 2021-06-10 08:03 android-rootfs.img
                      -rw-r--r-- 1 root  root         989 2021-06-10 04:10 config
                      drwxr-xr-x 2 root  root        4096 2021-03-26 23:33 overrides
                      drwxr-xr-x 2 root  root        4096 1972-06-26 01:53 pre-start.d
                      -rwxr-xr-x 1 root  root        1251 2021-05-12 17:32 pre-start.sh
                      drwxr-xr-x 2 root  root        4096 2021-03-26 23:33 rootfs
                      
                      1 Reply Last reply Reply Quote 0
                      • flohackF Offline
                        flohack @agates
                        last edited by

                        @agates said in No luck installing on my Pixel 2 (walleye):

                        e behavior without having to do that, also.

                        Not quite sure what you mean: Did you run the installer at least one time through, with the "Bootstrap" option checked?

                        My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                        A 1 Reply Last reply Reply Quote 0
                        • A Offline
                          agates @flohack
                          last edited by

                          @flohack Yes. Sometimes rebooting into the ubports recovery during this troubleshooting results in a bootloader error, however. I've yet to reproduce it to get the error message to see if it's relevant.

                          I followed the installation instructions, I promise πŸ™‚

                          1 Reply Last reply Reply Quote 0
                          • flohackF Offline
                            flohack
                            last edited by

                            Okay caon you please mount /data and see whats the output? Thanks!

                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                            A 1 Reply Last reply Reply Quote 0
                            • A Offline
                              agates @flohack
                              last edited by

                              @flohack Just went to try and finally got the boot error I mentioned

                              Will reinstall and try again.

                              ERROR: Slot Unbootable: Load Error

                              signal-2021-06-12-145408.jpeg

                              flohackF 1 Reply Last reply Reply Quote 0
                              • flohackF Offline
                                flohack @agates
                                last edited by

                                @agates Well you might get slot unbootable every 3 unsuccessful boots. Please issue fastboot --set-active=(a or b depending on whats active when you installed)
                                Unless UT would boot correctly this will bite you from time to time

                                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                A 1 Reply Last reply Reply Quote 0
                                • A Offline
                                  agates @flohack
                                  last edited by

                                  @flohack Roger that.

                                  Here's what /data looks like.

                                  oot@walleye:/ # mount /data                                                                                                                                                                 
                                  root@walleye:/ # ls -lh /data
                                  total 2.0K
                                  drwx------ 4 root root 4.0K 1972-06-27 23:13 android-data
                                  
                                  root@walleye:/ # mount
                                  rootfs on / type rootfs (rw)
                                  tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=1850700k,nr_inodes=462675,mode=755)
                                  devpts on /dev/pts type devpts (rw,relatime,mode=600)
                                  proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
                                  sysfs on /sys type sysfs (rw,relatime)
                                  selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
                                  tmpfs on /mnt type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1850700k,nr_inodes=462675,mode=755,gid=1000)
                                  none on /acct type cgroup (rw,relatime,cpuacct)
                                  tmpfs on /tmp type tmpfs (rw,relatime,size=1850700k,nr_inodes=462675)
                                  tmpfs on /storage type tmpfs (rw,relatime,size=1850700k,nr_inodes=462675,mode=050,gid=1028)
                                  pstore on /sys/fs/pstore type pstore (rw,relatime)
                                  none on /config type configfs (rw,relatime)
                                  adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
                                  /dev/block/sda45 on /cache type ext4 (rw,relatime,errors=remount-ro,stripe=4096,data=ordered)
                                  /dev/block/sda45 on /data type ext4 (rw,relatime,errors=remount-ro,stripe=4096,data=ordered)
                                  
                                  flohackF 1 Reply Last reply Reply Quote 0
                                  • flohackF Offline
                                    flohack @agates
                                    last edited by

                                    @agates huh data is empty after installation? I would expect at least a cache.img there. Can you go to cache folder and look for a ubports-updater.log or similar name

                                    My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                    A 1 Reply Last reply Reply Quote 0
                                    • A Offline
                                      agates @flohack
                                      last edited by

                                      @flohack

                                      /cache/ubuntu_updater.log

                                      flohackF 1 Reply Last reply Reply Quote 0
                                      • flohackF Offline
                                        flohack @agates
                                        last edited by

                                        @agates Ok so that was with bootstrap option? I can see it does not flash vbmeta and dtbo ppartitions, maybe thats the problem? I will investigate.

                                        Can you please download this: https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fcommunity-ports%252Fjenkins-ci%252Fwalleye-taimen/job/main/lastSuccessfulBuild/artifact/halium_walleye.tar.xz and extract the files vbmeta.img and dtbo.img from the partitions folder?

                                        Then, go to fastboot and do a fastboot flash dtbo dtbo.img and a fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification

                                        Lets try this!

                                        BR Florian

                                        My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                        A 1 Reply Last reply Reply Quote 0
                                        • A Offline
                                          agates @flohack
                                          last edited by agates

                                          @flohack Yes, this is with bootstrap.

                                          To be safe, I re-ran the installer with bootstrap enabled. Waited for the bootstrap to finish and ran the commands you provided without issue, then continued with the installer after rebooting to recovery.

                                          I'm not seeing a change, however, except now it's update version 181 instead of 179.

                                          /cache/ubuntu_updater.log

                                          flohackF 1 Reply Last reply Reply Quote 0
                                          • flohackF Offline
                                            flohack @agates
                                            last edited by

                                            @agates Alright can you also send me the log of the installer? It will be on your host device in the .cache folder maybe

                                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                            A 1 Reply Last reply Reply Quote 0
                                            • A Offline
                                              agates @flohack
                                              last edited by

                                              @flohack Here you go

                                              ~/.cache/ubports/ubports-installer.log

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