No luck installing on my Pixel 2 (walleye)
-
@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 -
@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?
-
@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
-
Okay caon you please mount /data and see whats the output? Thanks!
-
@flohack Just went to try and finally got the boot error I mentioned
Will reinstall and try again.
ERROR: Slot Unbootable: Load Error
-
@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 -
@flohack Roger that.
Here's what
/datalooks 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-dataroot@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) -
@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
-
-
@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.imgand afastboot flash vbmeta vbmeta.img --disable-verity --disable-verificationLets try this!
BR Florian
-
@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.
-
@agates Alright can you also send me the log of the installer? It will be on your host device in the .cache folder maybe
-
@flohack Here you go
-
Guys,
unfortunately I had to remove Pixel2 (not XL) from the installer as its not clear how to fix it, and I want to prevent bad experience.
I still need someone with a bit of a hacker gene to help me debugging and maybe find out whats wrong.
BR Florian
-
I made some progress
The build did not have the kernel config updated for the Pixel 2, I fixed that now and lets see todays build. As it is removed from the installer you would need to flash the kernel manually:
- Download https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fcommunity-ports%252Fjenkins-ci%252Fwalleye-taimen/job/main/lastSuccessfulBuild/artifact/halium-boot_walleye.img and flash this with fastboot flash boot halium-boot_walleye.img
Good Luck!
-
@flohack Unfortunately, I'm getting the same behavior (stuck at white google boot logo).
Will try to get logs again to see if there's something new.
-
@agates Can you try to connect with either telnet 192.168.2.15 or ssh phablet@10.15.19.82 when its stuck?
-
@flohack Both fail with network unreachable
-
@agates damnit its getting personal. So lets try this:
- Can you flash TWRP recovery to boot
- Then, run
fastboot boot halium-boot_walleye.imgand let it get stuck for lets say 5mins - Then, Long-press power to reboot into recovery
- finally, when TWRP has booted can you enter
adb shelland then try to see if that file exists:/sys/fs/pstore/console_ramoops?
Thanks!
-
@flohack Okay so to be clear, I:
- Flashed TWRP to the boot partition:
fastboot flash boot twrp-3.3.0-0-walleye.img - Booted into the halium boot image directly:
fastboot boot halium-boot_walleye.img - Waited 10 minutes
- Force-rebooted the device, it booted into TWRP
- Opened
adb shellchecking for/sys/fs/pstore/console_ramoops.
Unfortunately that file isn't there... the
pstoredirectory is empty.Here are the images used with sha256sum:
twrp-3.3.0-0-walleye.img:e7edcfb553b5c9b7ed717b3439c465075ee17b0eb938bafdce511bbea1cc3cd6
halium-boot_walleye.img:ed82425569e229863e58c17e636a2e341374d796520a478598580cbf9878127c - Flashed TWRP to the boot partition:
