No luck installing on my Pixel 2 (walleye)

flohack

@ljrichards1066 Alright can you please let it get stuck on the Google screen, and then try either telnet 192.168.2.15 or ssh phablet@10.15.19.82 ? THanks!

ljrichards1066

@flohack I tried both commands. Both hang without resolution.

flohack

Alright, I will think about a debug possibility...

What Android was installed before?

ljrichards1066

@flohack I had a lineage build based on Android 9 on it. When I get off work today, I can try it from stock android 9 and see if the results are better.

flohack

@ljrichards1066 It should not matter actually. Are you familiar with fastboot and adb? I have some manual debug steps

ljrichards1066

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

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.

flohack

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

agates

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

flohack

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

flohack

@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

agates

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

agates

@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

flohack

@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?

agates

@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

flohack

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

agates

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

Will reinstall and try again.

ERROR: Slot Unbootable: Load Error

flohack

@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

agates

@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)

flohack

@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