No luck installing on my Pixel 2 (walleye)

[flohack]

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

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

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

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]

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

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

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

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

[cliffcoggin]

@flohack Which version of the installer please?

[flohack]

@cliffcoggin 0.8.8

[BifPowers]

@flohack I've successfully installed the OS on the Pixel 2. I'm getting a lot of touchscreen problems though, like double or ghost touches. Shutdown seems to really power off the device though.