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

[dirtcat]

Both YES.
To watch YouTube freely, check out NewPipe first. To block ads on rooted device I can advise AdAway, but there are plenty of other root-less alternatives that work by running a local VPN.


Start by checking out the official documentation HERE.

I'm concerned about not being able to navigate through YouTube with the remote control. I will try NewPipe but I'm hoping that the rooted AdAway actually blocks YouTube ads - I'm really not sure that it will.

As for Magisk documentation, XDA recently published this article on the process. It would be nice to know if somebody has already done the work on this specific Onn Android TV device. If not, it looks like I'm just going to have to give it a go.

 

[dirtcat]

Does anybody have a link to the factory OS/image/whatever for this device?

I want to "start fresh" and see if I can get Magisk working on the stock image.

 

[CambriaTester]

Anyone else not seeing oem unlock after latest update?

 

[Online Gravy]

Anyone else not seeing oem unlock after latest update?

You don't need to toggle OEM unlock to unlock the bootloader, just boot to bootloader and issue the unlock command

 

[Online Gravy]

Folks - it looks like to truly root this Onn device I need to install Magisk. I need some help installing this! Can anybody guide me?

Also, two questions:

- I guess if I've gotten as far as installing this Lineage OS, then the bootloader is unlocked, right?
- If the bootloader is unlocked ... then can I use the stock OS that came with this device and root it with Magisk ... and use Netflix like normal and install an ad blocker? My goal is to be able to watch YouTube without ads!

The YouTube apps ad delivery system is extremely complex, you can't bock in app ads without using a a modded client like YouTube vanced. Vanced doesn't work for Android tv, however, there are alternatives like Smart YouTube TV and its successor Smart YouTube Next

 

[Big Dumb Object]

Is this Android TV

Let me ask a question that may be a little off-topic here, but has its addressees right here for sure.
In the same repo with builds for Amlogic boxes, there are also LOS17 builds for Nvidia Shield TV (foster) (the most up-to-date around). Since I really prefer the full (non-TV) android and hoping for it for the dopinder someday, for now I could give a try with Shield TV, and would like to understand if your builds for foster are also TV-flavored or not. (Thanks)

 

[npjohnson]

Let me ask a question that may be a little off-topic here, but has its addressees right here for sure.
In the same repo with builds for Amlogic boxes, there are also LOS17 builds for Nvidia Shield TV (foster) (the most up-to-date around). Since I really prefer the full (non-TV) android and hoping for it for the dopinder someday, for now I could give a try with Shield TV, and would like to understand if your builds for foster are also TV-flavored or not. (Thanks)

they're beta, not at all for release - but I do both foster and foster_tab builds.

 

[Big Dumb Object]

they're beta, not at all for release - but I do both foster and foster_tab builds.

That would be just wonderful, looking forward to it! And maybe it makes sense to order dopinder right now counting on the same approach? (I'm following this thread to make a purchase if the tablet version comes out.)

 

[npjohnson]

That would be just wonderful, looking forward to it! And maybe it makes sense to order dopinder right now counting on the same approach? (I'm following this thread to make a purchase if the tablet version comes out.)

I mean, I probably won't be doing them, but I can tell you with confidence, it's like a 2 line change.

 

[Big Dumb Object]

I mean, I probably won't be doing them, but I can tell you with confidence, it's like a 2 line change.

In some cases, users are offered to make a build themselves with a choice of their preferred flavor. For me It would be very convenient to be able to download a prebuilt ROM, but even if you totally reject such a dualism, please consider the option of adding TV/Tablet selection to the building guide if possible.

 

[npjohnson]

Does anybody have a link to the factory OS/image/whatever for this device?

I want to "start fresh" and see if I can get Magisk working on the stock image.

In the OP, under FAQ

Anyone else not seeing oem unlock after latest update?

Weird, I see it.

The YouTube apps ad delivery system is extremely complex, you can't bock in app ads without using a a modded client like YouTube vanced. Vanced doesn't work for Android tv, however, there are alternatives like Smart YouTube TV and its successor Smart YouTube Next

Yeah it can be weird.

 

[criscodecookies]

Does anybody have a link to the factory OS/image/whatever for this device?

I want to "start fresh" and see if I can get Magisk working on the stock image.

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.

 

[albinoman887]

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.

This is is exactly what I've been waating to do just didn't want to go through the tedious parrt of figuring out the keymap remapping scheme . Could you share your changes or point me in the right direction? Also can I get some clarification on DRM is it working or not working ? The OP is a little confusing. If I understand correctly it is not working but only because od broken HW omx not bootloader unlock so it's just a bug not a limitation. Or is that incorrect? (I'll help with development btw, synced tree last night . Gonna dive in tonight)

 

[npjohnson]

This is is exactly what I've been waating to do just didn't want to go through the tedious parrt of figuring out the keymap remapping scheme . Could you share your changes or point me in the right direction? Also can I get some clarification on DRM is it working or not working ? The OP is a little confusing. If I understand correctly it is not working but only because od broken HW omx not bootloader unlock so it's just a bug not a limitation. Or is that incorrect? (I'll help with development btw, synced tree last night . Gonna dive in tonight)

yeah, bug, not limitation.

 

[criscodecookies]

This is is exactly what I've been waating to do just didn't want to go through the tedious parrt of figuring out the keymap remapping scheme . Could you share your changes or point me in the right direction? Also can I get some clarification on DRM is it working or not working ? The OP is a little confusing. If I understand correctly it is not working but only because od broken HW omx not bootloader unlock so it's just a bug not a limitation. Or is that incorrect? (I'll help with development btw, synced tree last night . Gonna dive in tonight)

Netflix and Amazon Prime 4k work with Magisk on stock, safetynet ctsProfile does fail but looks like it doesn't matter like OP said.

For remap I placed the attached folder in /data/adb/modules

 

[albinoman887]

Netflix and Amazon Prime 4k work with Magisk on stock, safetynet ctsProfile does fail but looks like it doesn't matter like OP said.

For remap I placed the attached folder in /data/adb/modules

facepalm. I totally overlooked the fact that you are using the onn tv box , i have the dynalink (wade) so the remote is a little different. i was too lazy to drive to walmart and dynalink is on amazon. how did you determine what scancode each key was? thats all i need to figure out. and finally... anyone know where i can buy a remote that is the same layout and button count as the one with the onn box that is actually blutooth not some stupid usb dongle on 2.4ghtz? just curious. i'm almost thinking of just gettting the onn box and returning it without the remote and see if they take it lol

 

[criscodecookies]

facepalm. I totally overlooked the fact that you are using the onn tv box , i have the dynalink (wade) so the remote is a little different. i was too lazy to drive to walmart and dynalink is on amazon. how did you determine what scancode each key was? thats all i need to figure out. and finally... anyone know where i can buy a remote that is the same layout and button count as the one with the onn box that is actually blutooth not some stupid usb dongle on 2.4ghtz? just curious. i'm almost thinking of just gettting the onn box and returning it without the remote and see if they take it lol

adb shell getevent, then press buttons and note the line which has 'c' in the 3rd parameter ex. /dev/input/event4: 0004 0004 000c0042
then cat /proc/bus/input/devices (which may need root) to get vendor and product of the input device:

I: Bus=0005 Vendor=0957 Product=0005 Version=0011
N: Name="Onn-Remote"
P: Phys=
S: Sysfs=/devices/virtual/misc/uhid/0005:0957:0005.0001/input/input4

 

[Hig13]

I have the dopinder and have successfully booted up into lineage, seems like it's working but I'm stuck on the connect the remote screen. I hold the back and home button and the remote starts flashing with a green light, but it never connects to the device. Am I missing something? I've tried my best to search this post for other people having a similar issue but have come up empty. Anyone able to help me solve this? Should I just try reflashing or doing another factory reset?

Some how I got it to work, so never mind about that. I just held the two buttons and once it started flashing I set the remote down next to dopinder and ran to another room for something and when I got back it was connected.

 

[albinoman887]

adb shell getevent, then press buttons and note the line which has 'c' in the 3rd parameter ex. /dev/input/event4: 0004 0004 000c0042
then cat /proc/bus/input/devices (which may need root) to get vendor and product of the input device:

I: Bus=0005 Vendor=0957 Product=0005 Version=0011
N: Name="Onn-Remote"
P: Phys=
S: Sysfs=/devices/virtual/misc/uhid/0005:0957:0005.0001/input/input4

Thanks man! got it done . now the fun part, coming up with my own actions for the buttons in button mapper. thanks again

 

[epiphone324]

On a Dopinder, would I be able to unlock the bootloader and then sideload magisk to root on stock without first installing lineageOS and reverting to stock?