[Beta] Pixel 2 installer config
@flashylinux Well we took offline the installer config for walleye as it is not working currently. If you want to help testing thats fine, otherwise you will have to wait until we fix it at some point hopefully.
I removed the config now also from my first post. Sorry for the inconvenience!
@flohack I would love to help test! I have some experience with flashing and rooting. So I wouldn't be a complete noob haha.
How can I help?
Flohack last edited by Flohack
@flashylinux Currently the problem is: Pixel 2 and Pixel 2 XL share the same device tree and kernel. In fact, they are almost identical. Yet we were not able to boot into UI or even telnet mode with the Pixel 2. Something gets stuck with our boot image.
What you can do is:
- Wipe your device with TWRP (format userdata to remove encryption, wipe all other partitions as usual)
- Flash this boot image: https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%2Fcommunity-ports%2Fjenkins-ci%2Fwalleye-taimen/job/main/lastSuccessfulBuild/artifact/halium-boot_walleye.img into the active boot slot
- Flash dtbo and vbmeta from here: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc
- Note: vbmeta image needs to be flashed with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- Reboot the device
- Observe any activity on your USB on the host: Does any device appear after boot?
- If not, try to flash twrp into boot, and then make a one-time boot of the boot image, thereby hopefully getting in some way a /sys/fs/pstore/console-ramoops to see whats going wrong
I never had such troubles with booting our images as on the Pixel 2
@flohack Okay I will get to work on that.
Also I didnt mention in my first post. And I didnt see this in the thread but after the install it boots to a "installing updates" screen with the little robot. Afterwards it reboots and gets stuck at the google screen.
I am able to get to recovery mode. Would the logs from the recovery mode be helpful? I tried to download them but unfortunately, while linux sees the phone I cant access it's file system, so I would have to provide the logs as screenshots.
Flash dtbo and vbmeta from here: http://twoot.bin.org.in/nextcloud/index.php/apps/files/?dir=/porting/walleye%2C taimen/walleye&fileid=8312
When I click on this link it asks me to login to nextcloud.
@flashylinux Sorry this is the right link: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc
Not so good news.
Instead of the being frozen on the boot screen. Now it boot loops.
1. Wiped everything using TWRP
2. Flashed boot with “halium-boot_walleye.img”
3. Flashed dtbo with “dtbo.img”
4. Flashed vbmeta with “vbmeta.img” using fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Rebooted device
Result – Boot loops
1. Flashed boot with “twrp-3.3.0-0-walleye.img”
2. One time booted “halium-boot_walleye.img”
Result – This booted and then restarted and went into TWRP
I am able to see the device when I boot into TWRP though. Not sure if this is helpful or not.
@flashylinux Ok can you check after it bootloops if there is anything in /sys/fs/pstore?
That folder is empty
I cant edit posts I guess after so long so I am double posting but.
I have not been able to find any file in that directory.
- Wiped everything using TWRP
- Flashed boot with “halium-boot_walleye.img”
- Flashed dtbo with “dtbo.img”
- Flashed vbmeta with “vbmeta.img” using fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- Rebooted device
- Let Boot loop 3 times
- Booted into bootloader
- One time booted into TWRP
Result – Directory empty
- Flashed boot with “twrp-3.3.0-0-walleye.img”
- One time booted “halium-boot_walleye.img”
Result – Directory empty
I also noticed I was using boot slot "b" and changed it to "a" to see if that made a difference. DO NOT DO THIS. It would not allow me to boot or flash anything. It wouldn't even finish flashing a factory image. I changed it back to slot "b" and everything was back to normal.
@Flohack This page at postmarketOS wiki states some issues with pstore. Is it possible we're facing the same issues?
Also wondering if we need to set
clk_ignore_unused=true, though I'm not sure how or if you've already configured that
@agates Ill take a look. Well idk how to set clk_ignore_unused but I will try to find out.
@flohack Looks like clk_ignore_unused may be needed as a command line boot option, if I'm interpreting this correctly?
If there's an easy way I can test that I'd be happy to, though I realize the same chip is used in taimen and not having this issue.