[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] HyperDimensional:
My installation log, INCOMPLETE, will unspoil once finished.

This is my installation, I keep while doing these types of guides for my own and others' reference.

System information dump:

Pixel 3a 93UAY0GB8X MP1.0

Android version 12 Android security update May 5, 2022 Google Play system update January 1, 2022 Baseband version g670-00145-220106-B-8048689 Kernel version 4.9.292-gab4493f31457-ab8272301#0 Tue Mar 8 09:05:39 UTC 2022 Build number SP2A.2205050.008

Windows 10 Pro

Downloaded platform tools again.

unzipped `platform-tools_r34.0.5-windows.zip` to desktop

renamed old platform tools to old (I compared them with Free file sync and (turns out they were actually different)

added `C:\Users\Emma\Desktop\platform-tools` to system path environment varaible and restarted PC.

rechecked android version

unlocked developer options, by aggressively tapping on android build number (settings -> about phone)

still in settings, system -> developer options

enabled USB debugging

enabled OEM unlocking

Downloaded recovery image `https://github.com/ods-releases/sar...argo/lineage-21.0-20240122-recovery-sargo.img` and moved file into platform tools directory.

Downloaded lineage 21 main os zip `https://github.com/ods-releases/sar...go/lineage-21.0-20240122-UNOFFICIAL-sargo.zip` and moved file into platform tools directory.

Downloading everything was a error prone and laborious process, because I couldn't access github from my location temporarily. I wasn't sure if Github itself was down. I used a VPN to get around obstacle, but it was slow. This was especially an issue for the larger file. I eventually downloaded direct without the VPN. I don't know what the error was, but I got the file.

During this time I also downloaded both the webpage `https://developers.google.com/android/images` and the relevant file.

`https://developers.google.com/android/ota` and the relevant file

HIATUS. Drove around, partied, traumatized teenagers.

Finally got internet connection and stable table at the library, yay.

`adb -d reboot bootloader`

The phone showed the usb debugging dialog, I checked `always allow from this computer.` and Yes

`fastboot devices`

93UAY0GB8X fastboot

`fastboot flashing unlock`

got an OKAY back.

I then used the volume up and down keys to go from `DO NOT UNLOCK THE BOOTLOADER` to `UNLOCK THE BOOTLOADER` and selected via power key.

I used the volume keys to navigate the fastboot menu to the START and selected with the power button to start the phone

I ran through the mandatory phone set up and reenabled usb debugging

unlocked developer options, by aggressively tapping on android build number (settings -> about phone)

still in settings, system -> developer options

enabled USB debugging

I tried to reenable OEM unlock but it's already unlocked and greyed out, figures.

`adb -d reboot bootloader`

phone rebooted good

`fastboot devices`

same result as before.

I unplugged and replugged the device because I am a rebel.

Using the power and volume keys I restarted the bootloader.

`fastboot devices`

Same as before

I used tab button on the cmd for autocomplete

`fastboot flash boot ` <tab tab tab> to make

`fastboot flash boot lineage-21.0-20240122-recovery-sargo.img`

OKAY

OKAY

Used the volume keys to navigate and to Recovery and select with power button.

I DID NOT press the power button to pause.

Tapped "Factory Reset" and then "Format data/factory reset" then it warned me then I tapped "Format Data"

I stopped what I was doing and reread the instructions for the third time.

`adb -d sideload *.zip`

pressed tab to autocomplete to

`adb -d sideload lineage-21.0-20240122-UNOFFICIAL-sargo.zip`

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

God damn it.

Okay so I tapped on apply update, hoping to salvage this ****.

Apply from ADB

Okay we're back on.

Oh, it actually says so in the instructions, but it's under bullet point 5, oh well.

Process took about four minutes,

`adb -d sideload lineage-21.0-20240122-UNOFFICIAL-sargo.zip`

serving: 'lineage-21.0-20240122-UNOFFICIAL-sargo.zip' (~47%)

Instead of navigating the menu to advanced, reboot to recovery, I just clicked Yes

And then I rbooted to recovery again so I could read the link

g.co/ABH

This was one of the easier guides (and processes). There weren't any illegal flashers or downgrades to speak of. I like it. However, there were some points where the process or the knowledge is this implied thing. I wish I would've known to navigate via volume and power button. I wish it said how to do unlock developer options, just because I already know how to do these things doesn't make it a clear guide. I raise up this point because the open-source community depends on people and cutting those people off via overly terse guides is self-destructive.

Alright I'm gonna install magisk now, obviously I won't include that crap here.