[Feature] Testing for Pixel 3a XL

[ncorder]

I recently purchased a Pixel 3a XL and am trying to migrate from Ubuntu Touch to Lineage OS.

As long as it isn't damaging to the device, I would love to be a tester for providing support for the machine if possible.
It is reasonable for me to test the installer with the 3a image? What should I keep in mind beforehand.

[ncorder]

Looking through this: https://github.com/openandroidinstaller-dev/openandroidinstaller#how-to-contribute-your-own-installation-configurations

I believe the only thing I must change from the 3a and 3a XL is that the 3a XL's codename is bonito

https://github.com/openandroidinstaller-dev/openandroidinstaller/blob/main/openandroidinstaller/assets/configs/sargo.yaml

---

Would this be the only change to the file I would make: https://paste.debian.net/1260944/

[ncorder]

Does the installer require that I flash Android 12.0.1 first?
https://flash.android.com/build/8561491?target=bonito-user&signed

12.0.1 has a few versions, I can try and test with SP2A.220505.006

---

Link to android images and flasher: https://developers.google.com/android/images#bonito
Google has a fairly easy to use web-based system for installing different versions of Android.

---

Tools Used ( for documentation purposes ):
Browser: Brave Browser ( any chromium-based browser should work)
Trisquel OS

[ncorder]

Pastebin of log: https://paste.debian.net/1260952/

Screenshot at 2022-11-16 17-30-24

[ncorder]

It appeared to be idling after that step, but to clarify is there anything I must do on the device after booting into TWRP, or should my laptop continue with the installation after that step?

Edit:
I reinstalled Android 12.0.1 with SP2A.220505.006 but, I will continue working to migrate over to Lineage OS.
If you have any recommendations for how to get the installer working with this device let me know!

[tsterbak]

Hey, thank you for your interest in the project! :)
I'm looking into the issue and trying to figure out what went wrong here.

This issue might be related to protected/encrypted partitions on the phone that TWRP cannot wipe and so a factory reset is not possible. I will try to reproduce it with a Pixel 3a which should be fairly similar.
Did you enable a device pin/fingerprint or similar on the install of the previous ROM? If yes, you could try to disable all of that and retry installing with the OpenAndroidInstaller.

Thanks a lot for your time and effort!
If you like to contribute your config file, feel free to open a pull request :)

[tsterbak]

You are right, currently Android 12.0.1 is required. I'm working on automated checks for making sure this is the case before letting people progress.
Version SP2A.220505.006 should be fine.

[tsterbak]

Hey @ncorder, I could partially reproduce the issue with my Pixel 3a and adding a PIN. So removing the PIN and/or Fingerprintlock should fix that issue. Does it work for you?

I will add that to the requirements.

[ncorder]

You might edit the screen for selecting "restart bootloader" to include directions for the user to use the

• volume keys to switch between options
• power button to select

Especially if this projects goal is to make it easy for any non-technical person to install a different Android ROM.

[ncorder]

Re-flashed SP2A.220505.006 from this link.

Did the initialization steps, offline and no pin. Enabled developer mode + USB Debugging.

Log file: https://paste.debian.net/1261563/

[ncorder]

I've been selecting "Bootloader is already unlocked" because I have installed LineageOS and Ubuntu Touch on this device before.

Should I start leaving that button unselected? The bootloader should be unlocked.

[tsterbak]

Thanks for testing again!

I can see, what the issue is. This will be fixed in the next release, coming next week. Or you build/run from the current dev-branch.
It would be great if you could open a PR for your config and add it to the assets/config directory as well to the README in the supported devices table.

[tsterbak]

You might edit the screen for selecting "restart bootloader" to include directions for the user to use the

* volume keys to switch between options

* power button to select

Especially if this projects goal is to make it easy for any non-technical person to install a different Android ROM.

You are right! The texts need some more work. Right now, I'm mostly working on making the experience better and easier from a technical perspective. But soon I will spend more time on texts.
Note, that these text about the bootloader is part of the config. So, if you want, you can propose a better version of the text for your device. This might be generalized at a later point in time.

[tsterbak]

With the latest release, official support for Google Pixel 3a XL is there! Give it a try if you like! :) All feedback is appreciated!