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

[npjohnson]

Amlogic G12*/SM1 Family Devices

- 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:

• deadpool - Google ADT-3
• wade - Walmart Dynalink 4K Box

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:

• deadpool - Google ADT-3
• dopinder - Walmart Onn UHD Box
• sabrina - Chromecast with Google TV
• wade - Walmart Dynalink 4K Box

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:

• m5 - Banana Pi M5
• odroidc4 - Odroid C4
• radxa0 - Rock Pi Radxa Zero

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

 

[Stricted]

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

 

[lmore377]

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.

 

[Big Dumb Object]

Do these builds support Signature Spoofing to replace GApps with MicroG?

 

[npjohnson]

Do these builds support Signature Spoofing to replace GApps with MicroG?

No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.

 

[npjohnson]

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.

 

[Big Dumb Object]

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]

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).

 

[lmore377]

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]

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]

okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions

Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.

 

[npjohnson]

Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.

64-bit kernel, 32-bit userspace - aiming to do 64 bit userspace someday.

 

[lmore377]

Do you have an ETA for when the next builds will be done?

 

[npjohnson]

Do you have an ETA for when the next builds will be done?

they're uploaded now - sorry, got caught up putting out fires at work all day today lol

 

[lmore377]

they're uploaded now - sorry, got caught up putting out fires at work all day today lol

I'll try it and flashing dtb for the button in recovery in a bit

 

[npjohnson]

I'll try it and flashing dtb for the button in recovery in a bit

DTBO/DTB - they need to be in sync.

 

[lmore377]

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]

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]

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]

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...