No luck installing on my Pixel 2 (walleye)

agates · 12 Jun 2021, 20:13

flohack · 13 Jun 2021, 07:36

@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

agates · 13 Jun 2021, 19:21

@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

flohack · 13 Jun 2021, 19:55

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

agates · 13 Jun 2021, 20:07

@flohack Here you go

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

flohack · 26 Jul 2021, 07:01

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

flohack · 19 Aug 2021, 06:55

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!

agates · 20 Aug 2021, 00:57

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

flohack · 20 Aug 2021, 11:24

@agates Can you try to connect with either telnet 192.168.2.15 or ssh phablet@10.15.19.82 when its stuck?

agates · 21 Aug 2021, 19:39

@flohack Both fail with network unreachable

flohack · 21 Aug 2021, 19:51

@agates damnit its getting personal. So lets try this:

Can you flash TWRP recovery to boot
Then, run fastboot boot halium-boot_walleye.img and 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 shell and then try to see if that file exists: /sys/fs/pstore/console_ramoops ?

Thanks!

agates · 21 Aug 2021, 21:19

@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 shell checking for /sys/fs/pstore/console_ramoops.

Unfortunately that file isn't there... the pstore directory is empty.

Here are the images used with sha256sum:
twrp-3.3.0-0-walleye.img: e7edcfb553b5c9b7ed717b3439c465075ee17b0eb938bafdce511bbea1cc3cd6
halium-boot_walleye.img: ed82425569e229863e58c17e636a2e341374d796520a478598580cbf9878127c

flohack · 21 Aug 2021, 21:44

@agates Alright can you try the same with wiping data partition first? I have a suspicion... Wipe data, and then try telnet 192.168.2.15 again one time, and if this does not come up, try to boot into that recovery again and see for a pstore...

agates · 22 Aug 2021, 04:53

@flohack OK, I flashed TWRP to the boot partition, booted into TWRP, wiped the data partition, then booted into halium-boot_walleye.img directly from fastboot.

Same result, can't telnet, no console_ramoops file.

Wondering if I should start from android again for a clean slate?

flohack · 22 Aug 2021, 20:02

@agates No I dont think Android is the issue. The symptom seems that the kernel does not boot at all. Thats weird somehow. I will continue digging... ^^

Contonice · 27 Aug 2021, 09:52

I repeated @agates's path and got the same result:
I flashed the latest android 9 using the google site.
Installed ubports installer on ubuntu computer.
Downloaded the config walleye.yml for my google pixel 2 and ran the installer with it. Installation was successful. Then flashed halium-boot_walleye.img via fastboot.
The phone won't boot and hangs on the google logo.
The /sys/fs/pstore folder is empty.

flohack · 29 Aug 2021, 21:41

@contonice oh there is one thing I want to try, please take this boot.img instead of halium-boot: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc

agates · 29 Aug 2021, 22:43

@flohack Still no luck here, no console_ramoops found, and same behavior with stuck at google logo.

Here's the last_kmsg if it helps.

EDIT: I attempted with both the TWRP+boot method and the ubports installer (modifying the config with that new url for boot.img).

flohack · 30 Aug 2021, 09:16

@agates Huh the device has last_kmsg but thats from recovery only. Sad, I will try to flash the walleye kernel on taimen lets see ^^

flohack · 8 Nov 2021, 08:33

Guys Pixel 2 is back in the installer, please give it a try