[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 on Unofficial builds - 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. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.

  • 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: 4,054
  • settings-devices.png
    settings-devices.png
    99.3 KB · Views: 3,832
  • home-screen.png
    home-screen.png
    2 MB · Views: 3,931
  • TV.jpg
    TV.jpg
    3.9 MB · Views: 4,128
Last edited:

lmore377

Member
Jul 2, 2016
35
9
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.
 
  • Like
Reactions: shelanur

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
96
35
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
9
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
9
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
9
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

  • There are no posts matching your filters.
  • 2
    Thanks. I was just about to try it but the files aren't there anymore. The link loads but it says an error occurred.

    I'm not sure if an older unofficial version would work when the newer official version doesn't. It might be a problem with my device and not the lineage zip. I might have messed it up somehow with the huge amount of reflashing and resetting that I've done.
    new builds coming.
    2
    No.
    Neither adb, nor fastboot.
    Using Windows 10 (but can try Linux).
    And no, device manager is not seeing the usb device.
    The last option is to open up the device and use a usb to serial to reflash it, I guess?
    This thread has 84 pages and at least a handful of people have had the exact same issue as you, with others posting the solutions. It also doesnt help most lineageOS install guides are incorrect and assume everyone knows about driver signing on windows 10+ or needing to run fastboot with elevated privs. Then there's the "i dont want to read 84 pages to find the answers already posted" and i don't blame people, who has time for that.

    Hold the button on the side of the device down, and plug the usb A male connector slowly into your PC until just the power pins make contact, then release the button. This will change how the device boots. After you do so, plug the usb A male connector fully into the port to allow a data connection. Your windows pc should make a "do doop" noise. Now see if you can get somewhere.

    For future reference for Anyone flashing their android devices (outside of samsung devices). Linux is much easier to do it from and most linux distros can boot to a live CD without needing to install. All functionality of downloading files from firefox and installing the adb fastboot tools are available without installing linux. Both Ubuntu & Mint (debian based) and EndeavourOS (arch based) work great for this.

    Google "Ventoy" for making a usb boot drive that you can use for multiple ISOs at the same time. You can partition space to allow a "permanent" storage area for said ISOs to write downloaded files to when booted into the live environments.
    2
    FYI - Anyone with a dynalink 4K that gets bricked, this is the full steps I took to unbrick it. Special thanks to npjohnson for letting be bug him with various technical questions out of the blue!



    =====================
    How to unbrick dynalink 4k if stuck at dynalink logo:
    =====================

    Assumptions made:
    - You're on ubuntu
    - All scripts run as root (sudo -iu root)
    - You can see your amlogic device listed running lsusb (also as root!)

    1. power off unit by unplugging
    2. plug unit back in to a computer while holding side button
    3. download and install https://github.com/khadas/utils/tree/master/aml-flash-tool/tools/linux-x86 on ubuntu
    4. go to the path of /home/your-user-name-here/Downloads/utils-master/aml-flash-tool/tools/linux-x86/ in a terminal window,
    5. run these cmds. you can get these files from the official lineageos page if you dont have them already.

    Note: you need to go to your own username, and of course in the future a different date will be on the recovery file, make sure to copy the file name from your specific dtb file.

    Bash:
    ./update partition dtbo /home/bryantdl7/Downloads/dtbo.img
    ./update partition _aml_dtb /home/bryantdl7/Downloads/lineage-19.1-20221024-dtb-wade.img
    ./update partition recovery /home/bryantdl7/Downloads/lineage-19.1-20221120-recovery-wade.img
    ./update bulkcmd fastboot

    6. verify you are in fastboot by doing:
    Bash:
    fastboot devices
    , it should display a device in fastboot.
    7. run
    Bash:
    fastboot reboot bootloader
    as a sanity check, sometimes it half loaded for me.
    8. download the factory images via OP's post
    9. run the flash all script inside the factory image.
    10. You are unbricked!
    1
    I extracted dtb & dtbo from the zip in the link for Wade UNofficial on first page of this forum
    1
    Searching 84 pages is daunting! Although I only needed to read page 1 and page 84.
    There are a few steps in the wiki linked on page 1 for Dopinger - Walmart Onn UHD Box that WOULD NOT WORK.
    On this page https://wiki.oddsolutions.us/devices/dopinder/install under Unlocking the Bootloader < Step 5. It states to enter this command

    fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

    The only way I could get it to work was typing each command separately

    fastboot oem 'setenv lock 10101000;save'
    fastboot reboot bootloader
    fastboot flashing unlock


    Then under Flashing the dtb and dtbo partitions it has 2 links for the required files...and one link is DEAD! The real place to find those 2 files is INSIDE the LineageOS zip that you download (the OS Install file. It's over 700MB) kudos @XDA-DB

    Finally on Step 6 of Installing a Custom Recovery using fastboot. It states to type "fastboot reboot-recovery" but it never boots Recovery.
    Power cycling the device then puts it in a state with NO fastboot or adb connection!
    Unplug device. Hold button on device and slightly plug into PC until it powers on. When you see the Onn splash screen. Let go of button and fully plug in. You're now in Lineage Recovery that you installed. Again kudos @XDA-DB
    So, running them separately doesn't make much sense. `&&` says "run this after that if it succeeds" - this is on linux?

    DTB - ugh, I need to fix my upload scripts - will do

    reboot-recovery - fixing it.
    some special notes that could be added to the dopinder wiki as well.

    Fastboot needs to be run as root (or sudo / doas) on linux

    In order for dopinder to show up in adb, under developer options, set MPT on but turn off usb debug first or the stock OS crashes (does not occur under LOS). once MPT is enabled, re-enable usb debugging.

    Onn's booting into another mode when detecting data causes trouble for quite a few.

    And some advice for anyone looking to buy one of the devices: just buy a wade. dopinder has so many little issues (emmc burning out, overheating and freezing, the mtp slider crashing the OS, not booting recovery when connected to a pc). The only redeeming quality of dopinder is the remote (and the price).

    You don't need to give me credit for anything, jim. I don't help others for e-clout.
    Not everyone will read, not everyones native language is english, not everyone has the foundational knowledge. All we can do is try to make it as easy as possible. If those "who know" can offload the burden of the devs, they can focus on doing what they like to do best (unless you like herding cats then who am I to judge).
    fastboot - does not need root/sudo at all - it needs proper u-dev which is detailed on the wiki. You don't need to set MTP - ADB works just fine? I'm using it now.

    The half-plug thing is an interesting finding I will note the wiki - thanks.

    Wade is way better - can't agree more. IMO IR remote of wade is better even.

    Appreciate it.
  • 27
    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 on Unofficial builds - 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. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.

    • 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!
    7
    deadpool an wade are official again, hopefully we got it all right this time around.

    onto dopinder and Sabrina. Hoping to get those shipped soon.
    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.
    6
    wade and deadpool are official now!