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

Search This thread

npjohnson

Recognized Developer
lineage-os-logo.png

Amlogic G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.

Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:

Official Builds:
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.

Unofficial Builds:
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:
  • Recent apps/Multitasking menu doesn't launch.
  • (sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
  • (dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
  • GApps are baked in - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
  • Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
  • On the unofficial OTA is provided the same way officials would have them.
  • Find any more on an official build? Report them according to this guide.
FAQ:
  • Does L1 Widevine DRM break when I unlock my bootloader?

    Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.

  • Can I haz Netflix?

    Yup! Play Store has it for you.

  • Is this Android TV or Google TV?

    Android TV, with some of the better components of Google TV.

  • Can I go back to stock and relock the bootloader?

    Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.

  • Are these the stock codenames for these devices?

    Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.

  • Does it pass SafetyNet?

    Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.

  • Does the stock remote work?

    Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!

  • Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?

    Nope.

  • I have a very similar device! Can I install these builds and use them?

    No. Please don't do that. You will brick your device, as we include firmware and bootloader images.

    If you're a developer looking to help port to a new device, contact me.

Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9

Contributors:
  • npjohnson
  • bgcngm
  • stricted
  • webgeek1234
  • deadman96385
  • trautamaki
  • luca020400
  • aleasto
 

Attachments

  • settings-about.png
    settings-about.png
    66.8 KB · Views: 3,533
  • settings-devices.png
    settings-devices.png
    99.3 KB · Views: 3,316
  • home-screen.png
    home-screen.png
    2 MB · Views: 3,411
  • TV.jpg
    TV.jpg
    3.9 MB · Views: 3,572
Last edited:

lmore377

Member
Jul 2, 2016
35
6
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS

It pretty much just stops there except for the occasional healthd battery message.
 

npjohnson

Recognized Developer
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS

It pretty much just stops there except for the occasional healthd battery message.
yeah, aware of the issue, it's video firmware not loading, building new builds now.

But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
 
  • Like
Reactions: seriousneo

Big Dumb Object

Senior Member
May 22, 2020
81
31
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.

Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
 

npjohnson

Recognized Developer
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.

Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Eh, maybe once we're in a more functional state (eg. Hardware OMX gets fixed).
 
  • Like
Reactions: Big Dumb Object

lmore377

Member
Jul 2, 2016
35
6
yeah, aware of the issue, it's video firmware not loading, building new builds now.

But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
 

npjohnson

Recognized Developer
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
 

lmore377

Member
Jul 2, 2016
35
6
DTBO/DTB - they need to be in sync.
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
 

npjohnson

Recognized Developer
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
 

lmore377

Member
Jul 2, 2016
35
6
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
 

npjohnson

Recognized Developer
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
Adb reboot sideload works, maybe just reboot sideload?

I'll go grab an Onn box at Walmart tmrw afternoon.

I know it works as 3 of our developers have and use it.

Just a matter of install process it seems...
 

Top Liked Posts

  • 1
    I'm currently using the latest official wade build (2nd October) without google services. Sadly, the WiFi does not work. With Ethernet Plugged-In everything seems fine.
    Is this a known Bug?
    yes, DTB got mangled, we are trying to fix it.
  • 3
    There is a known issue with official DTB images - we are working on it.
    3
    Also, I solved the signing issue with Luca's help.

    Builds should hopefully roll for wade/Deadpool with no GMS tomorrow.

    I'll then look into tablet builds feasibility.
    2
    However I run into a boot loop. I see the LinageOS Logo and sometimes the remote control but after that the box restarts. I installed several times with the same result.
    Do you have an idea what I could do?
    You could list, with precision, the steps that you repeatedly did and maybe someone will notice where you went wrong. Most problems lately seem to involve failure to flash the appropriate dtb/dtbo at the appropriate time(s).

    With the v18 builds, it was fortunate that dtb/dtbo were also compatible with stock and vice versa. For whatever reason (I don't know) there is not this same sort of dtb/dtbo compatibility between stock and v19 builds.
    2
    Would you expand upon this using maximum detail?

    Sure, but it requires root and some familiarity with shell. Also, you are likely aware, but this is a rare problem only for networks which filter by mac. If you are unable to see wifi networks at all, you have a different problem.

    First, attempt to connect to or create a connection through the android UI to the SSID of your network. If this problem relates to you, you should be able to see your SSID but the connection will fail. That's fine, leave the failed connection there and enter shell. Then, edit:
    Code:
    /data/misc/apexdata/com.android.wifi/WifiConfigStore.xml
    Find the code block for your SSID (it should be the only one). You are interested in the keys:
    Code:
    RandomizedMacAddress
    MacRandomizationSetting
    RandomizedMacAddress contains the randomized mac android wants to use for your SSID. You would supply this mac to your router. MacRandomizationSetting should be set to 0 (zero) to avoid re-randomization every time the interface goes up, like so:
    Code:
    <int name="MacRandomizationSetting" value="0" />
    Reboot and you should have a persistent mac.

    But wait! There is an easier way, which does not require root or shell. It turns out the UI settings are available AFTER a connection has been successfully negotiated. Provided you have access to your router settings, I would recomend you temporarily disable mac filtering on your router, connect normally, then access the wade UI Settings submenu under the active connection to disable mac randomization. You can then re-enable mac filtering on your router and supply the (now persistent or hardware stock) mac.

    I have also encountered another issue which may be problematic for android TV on wade:
    5) HDR. Wade really, really wants to use HDR. Even when it shouldn't and on SDR sources. Even with HDR manually disabled in Settings (I suspect this option is broken or not checked at boot), we still boot to HDR modes which then persist in apps. In fact, wade will preferentially boot to a lower resolution with display HDR support, rather than a higher resolution without display HDR support. It is possible to force SDR by manually switching to a higher resolution without HDR support, then back to lower resolutions, so the SDR modes are available, just not properly selected. I am not sure if this problem is specific to wade, or something general to lineage.
    2
    For this you need to join the number of those people here who are waiting for the tablet builds arrival on the official release day. Take your ticket and have a seat beside me.
    Or just don't use google apps, you can build without them easily.

    ATV works fine enough without gapps.

    Tablet builds will follow.

    The official builds are queued but they fail to sign for some reason - working that out rn.
  • 26
    lineage-os-logo.png

    Amlogic G12*/SM1 Family Devices
    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:

    Official Builds:
    Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.

    Unofficial Builds:
    We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
    EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.

    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • Recent apps/Multitasking menu doesn't launch.
    • (sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
    • (dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
    Notes:
    • GApps are baked in - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
    • Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
    • On the unofficial OTA is provided the same way officials would have them.
    • Find any more on an official build? Report them according to this guide.
    FAQ:
    • Does L1 Widevine DRM break when I unlock my bootloader?

      Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.

    • Can I haz Netflix?

      Yup! Play Store has it for you.

    • Is this Android TV or Google TV?

      Android TV, with some of the better components of Google TV.

    • Can I go back to stock and relock the bootloader?

      Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.

    • Are these the stock codenames for these devices?

      Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.

    • Does it pass SafetyNet?

      Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.

    • Does the stock remote work?

      Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!

    • Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?

      Nope.

    • I have a very similar device! Can I install these builds and use them?

      No. Please don't do that. You will brick your device, as we include firmware and bootloader images.

      If you're a developer looking to help port to a new device, contact me.

    Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9

    Contributors:
    • npjohnson
    • bgcngm
    • stricted
    • webgeek1234
    • deadman96385
    • trautamaki
    • luca020400
    • aleasto
    14
    Yeah, you used the stock recovery. You need to fastboot flash, then fastboot boot recovery, I'll update the docs.

    For dopinder, it's needed right now.

    Found a procedure for dopinder without the need for keyboard/OTG.

    The docs under "Installing a custom recovery using fastboot" state to use "adb reboot fastboot" which doesn't work for booting recovery, needed to do "adb reboot bootloader" instead.

    Full command log (after unlocking bootloader and re-enabling USB debugging) of the install process with just a regular Micro USB to USB A cable:
    Code:
    adb reboot bootloader
    fastboot flash recovery lineage-18.1-20210805-recovery-dopinder.img
    fastboot boot lineage-18.1-20210805-recovery-dopinder.img
    adb reboot sideload
    adb sideload lineage-18.1-20210805-UNOFFICIAL-dopinder.zip
    # if successful then load bootloader and factory reset
    adb reboot bootloader
    fastboot -w
    fastboot reboot

    Successfully booted to LineageOS after this!
    6
    wade and deadpool are official now!
    6
    Note:

    Since the Lineage Android TV Builds for this little box (aka Boxes), are stable for the most part, but seems
    people are bouncing back in forth from Stock to Lineage and back to stock.

    I created a batch file that will auto flash the stock images and wipe data and so on.. pretty much it will
    make your box as it was when you first booted it after taking it home to try it.

    2nd, I also created a batch file that will backup current images.. No need for a fancy recovery or anything like the
    such. it will use the worldcup or what I like to say, USB Burn mode, and backup each and every partition.
    as well as some not so much needed ones like, misc and metadata. (Just for giggles)..

    backups will be copied to backup dir, I also created a separate batch file to restore your backup.


    I am one that hates doing things the long way over and over, so I always create ways to make things simple
    in the future for people.

    This way, you all can test your hearts out all the new lineages and still have your full Stock backup (including data).
    and restore back in forth as you wish.

    I will upload the backup_restore zip package as soon as I can and with @npjohnson permission I will link
    in thread. Otherwise you will have to just DM/PM me and ill link you the location.

    I am just trying to help the many that I seen complain and dont understand how to go back in forth.
    so with this script, it should take care of most on that. No Fancy Recovery needed...

    you will need worldcup driver for Amlogic........ you can find that on your own.

    Also, to get into USB Burn mode, press side button while plugging in USB cable.
    Keep pressing till you see the LOGO or hear the sound from your computer.

    then just run the batch file and wait..

    if its easier for you:

    Run the batch file, it will keep saying waiting for device..
    Just press the side button while plugging in USB, when you see it start, then release button...........
    and wait till finished..

    Only TESTED On Dopinder Boxes, but im sure they are all the same as for the partition layouts.
    5
    I ultimately settled on 1126400000, gives ~1.1GB to the system and accommodates the app adjustments I've been making for my builds without tripping OpenGApps' space check for TV stock
    this ended up being _wayyyyy_ to much, as this is the full value of the partition vs just the space to reserve, both will work, but we want to split it amongst partitions. One of our guys recalculated it and got it working.

    Should be good to build now from breakfast/extract-files (or syncing the muppets).

    Only thing left is hardware OMX. Hopefully we can figure it out!