No luck installing on my Pixel 2 (walleye)
-
@wilson Ok no idea. will think how wwe can solve that
-
Same issue here, can test whenever as it's not my primary device.
-
Alright sorry took some time. As 2 XL kinda works now, I want to turn my attention to Pixel 2 again. As I do not own the device I need someone with a bit of curiosity to debug the reboot issue for me, if its still persisting. Please head over to https://forums.ubports.com/topic/6251/beta-pixel-2-installer-config and report me back any new findings.
I hope the reboot does not appear anymore
-
@flohack I dusted off my old pixel 2 and gave it a try. After reverting to android 9, I tried the installer from the command line with the new config file. That seemed to work well, going through all of the prompts. Once finished, I got the UB ports avatar and a message stating it was updating. Once finished, it rebooted and got stuck on the Google logo. I let it hang for about 10 minutes and tried two more times with fresh wipes. No luck.
-
@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!
-
@flohack I tried both commands. Both hang without resolution.
-
Alright, I will think about a debug possibility...
What Android was installed before?
-
@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.
-
@ljrichards1066 It should not matter actually. Are you familiar with fastboot and adb? I have some manual debug steps
-
@flohack I've got a working knowledge of it from messing around with rooting and Android roms. I'd certainly be willing to try.
-
@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.
-
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
-
@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.logIn 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.
-
@agates Wait a second how did you flash recovery? The device should not even have a recovery partition...
-
@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
-
@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.
-
@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!
