[Beta] Pixel 2 installer config

flohack · 9 Dec 2021, 18:11

As for the XL variant, here is the installer config for its small brother: (taken down since it does not work currently) - I hope that works equally well.

Note: Seems the cmdline argument is only understood with the installer run in Linux OS
Download this file
Download the UBports Installer from here: https://github.com/ubports/ubports-installer/releases/tag/0.8.8-beta (deb preferred, idk if the others accept cmdline arguments)
Start the installer from cmdline with the parameter -f <path-to-walleye.yml>

So you can install on the 2 already now, without having to wait for the release.

I´d love to receive feedback! Note this time the config works only for 2! Do not try to use the Pixel 2 XL, the installer will not check for sanity.

BR Florian

sakeineha · 24 Jul 2021, 16:23

@flohack hello sir , I am very happy to finally get support for pixel 2 family , but i am kind of facing an issue after getting successful installation msg on pixel 2 it reboots and gets stuck to google logo ...

BifPowers · 24 Jul 2021, 16:43

I have the same issue as sakeineha. Downgraded to Android 9, used the UB Ports installer. Everything went well, but it was stuck at the bootloader splash screen. After going into UB Port's recovery to check logs, I'm now getting an error on the bootloader screen: Slot Unbootable: Load Error. Please let me know if I can provide you with any logs, if they're still retrievable.

flohack · 25 Jul 2021, 18:55

We know there is a problem with Pixel 2, only Pixel 2 XL seems to work at this time. I will take down the config for walleye. And yes, I need debug assistances, it would involve using telnet adb and ssh, to see where we are in the boot process, also using boots with the volumen and power buttons multiple times, using fastboot boot to temporarily boot a kernel etc.
If some of you can help with this I can give some instructions maybe

BifPowers · 26 Jul 2021, 14:02

@flohack I have experience with ssh and adb. Telnet would be new to me. I don't have much experience beyond flashing Android ROMs, but I would like to help where I can.

flohack · 26 Jul 2021, 17:29

@bifpowers Ok in which timezone you are in?

BifPowers · 27 Jul 2021, 02:38

@flohack I'm in Eastern Time. I should have some time tomorrow evening to troubleshoot.

flohack · 27 Jul 2021, 11:00

@bifpowers Ok I will write up some explanations for you later

flohack · 4 Aug 2021, 14:21

Alright here are some generic steps to see where we are:

Check that kernel actually boots correctly:

On your host, enter dmesg -w and then power up the device
connect your USB cable. See if the host sees a new USB device
IF there are any messages about RNDIS coming up, try to ping 192.168.2.15 or 10.15.19.82 and eventually try either telnet on 192.168.2.15 or ssh (with user phablet) on 10.15.19.82

BifPowers · 4 Aug 2021, 22:46

@flohack Unfortunately I'm not getting anything from any of those steps. I'm on Windows 10 currently, and tried with both PowerShell and WSL Ubuntu.

Jay Ajit Mate · 8 May 2021, 17:22

I'm on arch linux and using the appimage installer. It gets stuck on "preparing system image/mounting partitions'
tried using an ubuntu vm -same problem

flohack · 18 Aug 2021, 21:48

HOLY CRAP!
I did not see that this devicetree uses 2 kernel configs for each device. I only patched the one for XL. I push now some changes to add also muskie.

Can someone in roughly 24hrs from now try again to install Pixel 2? I bet its working then

BR Florian

agates · 18 Aug 2021, 23:33

@flohack best email I've gotten all week! Will give it a shot.

flohack · 19 Aug 2021, 06:55

Here is the instruction how to flash:

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!

i2097i · 9 Mar 2021, 03:50

@flohack

I am unable to get past the recovery step. Everything seems to work, I reboot to recovery and I can interact with the UBports recovery mode interface but it never continues from that point. Any ideas?

Update: It seems to hang on the

Preparing system image
Mounting partitions...

section after the reboot to recovery (screenshot attached).

It could be that I am not giving it enough time so I am going to leave it throughout the night. Here is the verbose output of my UBPorts session:

...
info: Downloading 8 files
info: Downloaded file 1 of 8
info: Downloaded file 2 of 8
info: Downloaded file 3 of 8
info: Downloaded file 4 of 8
info: Downloaded file 5 of 8
info: Downloaded file 6 of 8
info: Downloaded file 7 of 8
info: Downloaded file 8 of 8
verbose: running core action write
verbose: running adb action wait
verbose: running adb action preparesystemimage

Thanks!

flohack · 3 Sept 2021, 06:59

Pixel 2 does not boot into UI anyways, I would ask you to wait a bit until we can get this sorted out finally. If you like, you can help debugging it maybe, if you are ok with using adb and fastboot directly.

flohack · 3 Sept 2021, 09:57

Ok guys lets try a different approach. Can you please enter fastboot, flash that image into boot: https://twoot.bin.org.in/nextcloud/index.php/s/mzfmYJscqPyM2Bc with fastboot flash boot boot.img - so far so old.
Now: DO NOT reboot, but select Boot to recovery. Does this bring up our UT recovery screen?

Thanks!

i2097i · 3 Sept 2021, 10:35

@flohack

Booted to fastboot
ran fastboot flash boot boot.img with this img

I am not sure what is meant by DO NOT reboot, but select Boot to recovery. After running the fastboot command should I just use volume up/down to make the recovery reboot option be visible? Not sure if it is supposed to do something at that point.

flohack · 3 Sept 2021, 10:44

@i2097i Yes exactly, select manually the recovery option.

i2097i · 9 Mar 2021, 11:00

@Flohack
yes, if I press the power button on recovery, it boots to UBPorts Recovery.

I also wanted to mention that I let this run all night and it was still on the verbose: running adb action preparesystemimage when I woke up this morning.