[UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

[goapy]

thats good, but doesnt the current build you have installed overwrite the recovery you have? so if i ever wanted to update to a newer version of 19.1, i would have to reboot to bootloader, boot into 18.1 recovery.img and then flash it?

Well, if you use the 18.1 recovery to sideload 19.1, that sideloaded installation ends with the 19.1 recovery on the device.

I don't see any reason why you couldn't immediately flash the 18.1 recovery again after that if you want to test these builds, if you're worried about the 19.1 recovery.

 

[RDS5]

Well, if you use the 18.1 recovery to sideload 19.1, that sideloaded installation ends with the 19.1 recovery on the device.

I don't see any reason why you couldn't immediately flash the 18.1 recovery again after that if you want to test these builds, if you're worried about the 19.1 recovery.

doesnt the actual os overwrite the recovery partition with its own recovery? so if i were to flash 18.1 recovery again it would overwrite it with 19.1? or am i getting this the wrong way, and only the stock os does that.
ill flash it right now anyways and check it out.

 

[RDS5]

nevermind its stuck on the androidtv logo. ill do a factory reset (if i even can, since it didnt want to fastboot-boot into the 18.1 recovery after flashing 19.1) and if that still doesnt work ill go back to stock, go to 18.1 and just wait for official release.
the xda releases arent worth the trouble currently, and they wont be up until the recovery boots.

 

[goapy]

doesnt the actual os overwrite the recovery partition with its own recovery?

I don't think that the running system ever updates the recovery partition unless it's applying an ota.

nevermind its stuck on the androidtv logo. ill do a factory reset (if i even can, since it didnt want to fastboot-boot into the 18.1 recovery after flashing 19.1) and if that still doesnt work ill go back to stock, go to 18.1 and just wait for official release.

If you've just finished sideloading 19.1, you can run;

adb reboot bootloader

To flash the 18.1 recovery, or even the stock recovery.

While you're in that same bootloader fastboot session, it wouldn't hurt to also run;

fastboot erase data
fastboot erase cache

Which is the equivalent of a factory reset. You needn't ever reboot to the recovery again.

The bootloader's support for burn mode stays constant regardless of which build is present on the device (18.1/19.1/factory)

So whenever you're stuck, you can do the steps like at the end of this post to resolve the issue.

 

[jwchen119]

no sadly, i tried to use mouse toggle and it wouldnt work.
i wish there was some kind of mouse toggle alternative, it would be a gigantic save.
does anyone know of alternative apps? ive only tried the free one but the paid one only supports a handful of devices.

Have you tried tvQuickActions on Play store yet?
I can triggered the mouse toggle to work with it's feature on stock ROM.

 

[kennkanniff]

i probably will write up install instructions for the `BananaPi-M5` and `Odroid C4` Soon™
its a bit more complicated than just booting into recovery and flashing it unfortunately

Just received an Banana Pi-M5 and I would definitely appreciated a guide for that device.

 

[npjohnson]

Just received an Banana Pi-M5 and I would definitely appreciated a guide for that device.

I am working on wiki instructions for them now. End of the month they should be up.

 

[endera]

Yup it's a devboard

How are the installation steps on Radxa Zero?

 

[npjohnson]

How are the installation steps on Radxa Zero?

Coming soon

 

[#2!]

I wasn't able to revert back to stock from Lineage using the factory zip files, for whatever reason it would bootloop the Onn logo. However holding the box side button allowed opening the stock recovery and from there was able to enter bootloader, boot Lineage recovery and flash the stock OTA zip modifying it to remove the first line (newer build check) in updater-script. This required an OTG Y adapter and powered USB hub for keyboard and USB stick.

I can also confirm Magisk v23 works well on Lineage and Stock after simply flashing the zip (rename .apk to .zip) using Lineage recovery. Was able to create a simple module to replace /vendor/usr/keylayout/Vendor_0957_Product_0005.kl with TV, Channel Up/Down, Netflix etc to numpad keys which can then be remapped using an app like Button Mapper.

Thanks!! I had the same issue bootloop with the factory zip file. The stock OTA zip you posted worked for me without any modification. Just opened stock recovery with the button, selected ADB sideload and sideloaded that zip file. No adapter or hub needed.

 

[espchl]

Hey,
I flashed my Sabrina with 19.1 today, following the instructions.
Something went wrong, the device did not boot to os and got stuck at the android tv logo.
I was able to enter fastboot and was able to enter the recovery,. But no boot to os.
I manually flashed the 18.1 recovery via fastboot (stupid enough) and are now stuck at the android tv animation. The device can't enter recovery now. It's also not possible to use fastboot.

Is there anything I can do to unbrick my device? I appreciate any help!
I tried to use "update bulkcmd fastboot" but without a working fastboot, its not possible to flash the recovery again

Thanks in advance!

 

[kennkanniff]

Hey,
I flashed my Sabrina with 19.1 today, following the instructions.
Something went wrong, the device did not boot to os and got stuck at the android tv logo.
I was able to enter fastboot and was able to enter the recovery,. But no boot to os.
I manually flashed the 18.1 recovery via fastboot (stupid enough) and are now stuck at the android tv animation. The device can't enter recovery now. It's also not possible to use fastboot.

Is there anything I can do to unbrick my device? I appreciate any help!
I tried to use "update bulkcmd fastboot" but without a working fastboot, its not possible to flash the recovery again

Thanks in advance!

Try this:

update partition recovery path/to/lineageos-18.1-recovery.img

 

[espchl]

Try this:

update partition recovery path/to/lineageos-18.1-recovery.img

Thank you. Seemed to work without error.
Sadly I'm still not able to enter fastbootd.

Is it somehow possible to flash to stock and start from scratch?
Thanks

 

[kennkanniff]

Thank you. Seemed to work without error.
Sadly I'm still not able to enter fastbootd.

Is it somehow possible to flash to stock and start from scratch?
Thanks

You should be able to use the exploit now. If that does not work you should try the custom exploit in post #782. No expert just sharing my experience.

 

[retyre]

You should be able to use the exploit now. If that does not work you should try the custom exploit in post #782. No expert just sharing my experience.

Not sure that will work since he/she cannot boot into the OS.

@espchl: What you should do is put back the 19.1 (not 18.1) recovery:

sudo ./update partition recovery lineage-19.1-20220515-recovery-sabrina.img

and see whether that lets you boot into fastbootd.

 

[sjustinas]

Just flashed the latest build to my wade. Had to flash it using the 18.1 recovery, because the latest recovery would not work (neither via "fastboot flash", nor "fastboot boot" - I would remain at the OEM's bootloader screen).

Auto frame rate works great with Jellyfin and SmartTubeNext! (when enabled in both Android's and respective
apps' settings).

However, I've hit a couple of minor issues so far:

• My TV is constantly in HDR mode, even when in the launcher or watching SDR content. This was also the case with Dynalink's stock software, however I was be able to remedy this by choosing the "Auto" (rather than "On") HDR mode in Droid Settings. Lineage, of course, has no Droid Settings. Any way to resolve this?
• The launcher seems to crash when I tap the Apps icon (see video). In reality, the screen also goes completely black for a second before the launcher re-opens. One can access the apps through the favorites bar, or via Settings -> Apps, but it is slightly annoying. Version of "com.google.android.tvlauncher" is 3.5.3-434707177-f (the latest via Play Store).
  Uninstalling updates to the launcher (effectively reverting to 3.1.2-3668464-f) fixes this.
• Can't seem to find the option to enable adb over network in the developer settings.

Thanks for your efforts on this!

 

[iyah123]

Coming soon

Can you share if it's emmc or uSD boot ?

 

[npjohnson]

Can you share if it's emmc or uSD boot ?

Emmc only

 

[espchl]

You should be able to use the exploit now. If that does not work you should try the custom exploit in post #782. No expert just sharing my experience.

Thank you for your help. It's still not working. After using the custom exploit the device is stuck in a bootloop (orange led turning on an off).

@espchl: What you should do is put back the 19.1 (not 18.1) recovery:

sudo ./update partition recovery lineage-19.1-20220515-recovery-sabrina.img

and see whether that lets you boot into fastbootd.

Thanks. But somehow it's also not working. Seems I'm not able to write to recovery anymore.

It looks like there is some error...

file size is 0x1800000
AmlUsbTplCmd = download store recovery normal 0x1800000 rettemp = 1 buffer = download store recovery normal 0x1800000
AmlUsbReadStatus retusb = 1
[update]ERR(L306):cmdret=[]

 

[iyah123]

Emmc only

Thx.
A few more questions ...
Does chromecasting work ?
Has anyone tested using a usb-c to 3.5mm adapter to capture audio output ?

As you may have figured, am looking for a cheaper chromecast, but audio only, to turn passive/active speakers into smart speakers.
Thx