[Google TV General] w00cash:
Well, the first problem that I have encountered was unlocking the bootloader. The official manual at any point states that it would be necessary to use aml-flash-tool. Just a few quick commands, and you're done. Bootloader unlocked.

Workaround this was not an easy feat because I needed to dig through this and LOS 19.1 threads to gather pieces of information here and there.

When I was finally done and had unlocked the bootloader, everything was supposed to be straightforward.

It is not either.

This is the command line that I have used to get it done:

PS C:\Windows\system32> adb devices
List of devices attached
DDEU2123002535 device
PS C:\Windows\system32> adb reboot bootloader
PS C:\Windows\system32> fastboot devices
DDEU2123002535 fastboot
PS C:\Windows\system32> fastboot flash dtb C:\************\wade\dtb.img
Warning: skip copying dtb image avb footer (dtb partition size: 0, dtb image size: 82666).
Sending 'dtb' (80 KB) OKAY [ 0.031s]
Writing 'dtb' OKAY [ 0.232s]
Finished. Total time: 0.633s
PS C:\Windows\system32> fastboot flash dtbo C:\************\wade\dtbo.img
Sending 'dtbo' (2048 KB) OKAY [ 0.116s]
Writing 'dtbo' OKAY [ 0.147s]
Finished. Total time: 0.548s
PS C:\Windows\system32> fastboot devices
DDEU2123002535 fastboot
PS C:\Windows\system32> fastboot flash recovery C:\************\wade\recovery.img
Sending 'recovery' (24576 KB) OKAY [ 1.135s]
Writing 'recovery' OKAY [ 1.089s]
Finished. Total time: 2.540s
PS C:\Windows\system32> fastboot boot C:\************\wade\recovery.img
Sending 'boot.img' (24576 KB) OKAY [ 1.121s]
Booting OKAY [ 0.022s]
Finished. Total time: 1.158s

And nothing happend. No LOS logo, just Dynalink. So as manual states I tried to flash and boot recovery once more

PS C:\Windows\system32> fastboot devices
???????????? fastboot

What? No serial number in fastboot? Thats new. That never happened

PS C:\Windows\system32> fastboot flash recovery C:\************\wade\recovery.img
PS C:\Windows\system32> fastboot devices
???????????? fastboot
PS C:\Windows\system32> fastboot boot C:\************\wade\recovery.img
Sending 'boot.img' (24576 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS C:\Windows\system32> fastboot devices
???????????? fastboot

At this point I knew that it is not going to work, but I tried once more anyway.

PS C:\Windows\system32> fastboot flash recovery C:\************\wade\recovery.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 25165824).
Sending 'recovery' (24576 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
PS C:\Windows\system32> ^C
PS C:\Windows\system32> fastboot devices
???????????? fastboot
PS C:\Windows\system32> fastboot reboot
Rebooting FAILED (Write to device failed (no link))
fastboot: error: Command failed

Being unable to boot into recovery after flashing quite common, from my understanding.

here or here or here is the evidence

Just to clarify. I am a noob/layman in terms of coding and software development in general. I am aware of my limitations, and I wouldn't even try if installation instructions were beyond my level of understanding. I have been using LOS for years on two phones (first samsung, now POCO), where the installation manual was a bit more complicated than on wade. This seemed relatively easy, so I went with it. I couldn't be farther from the truth.

I am aware that somewhere in this thread there might be a solution to my problem and I somehow missed it, but I would expect to find it in an official installation manual instead of gluing pieces of information together. I had to bring it back to stock 3 times already because nothing worked. For now, I am just glad that I put it back on its feet and got it working on stock. I'll stay with that until I find the motivation to try again.