• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

CrazyHairGuy

New member
Jul 4, 2014
3
1
www.crazyhairguy.com
I'm not too well versed in this kinda stuff, but would it be possible to install the "regular" phone/tablet version of google play and install non-TV apps with this ROM? I tried editing the build.prop, but it still throws an error whenever I try to open the sideloaded phone app. Is it inherent to the OS itself?

--edit--
Is OTG disabled/is there a documented issue with OTG on this ROM? I have a squid-like cable that supplies power and also passes through three USB ports, and it worked with the stock firmware - but as soon as I flashed this image it seems to do absolutely nothing but pass power. Could it be exclusive to the onn. box?
 
Last edited:

HawaiiWarrior

New member
May 20, 2013
2
1
Tyler
Thanks for the feedback, @retyre. I tend to flash Android device ROMs only once every year or so, and when I do I usually end up failing with Windows and using Linux; I just really didn't feel like flashing a device or spinning up a virtual machine and getting USB devices functioning. I'll probably end up coming up with a more permanent Linux situation if I try a project like this again. However, I can confirm I was able to get the process working with the Windows driver.

Here's a screenshot showing the driver I was able to update in case anyone else was having a similar issue:
1634707339250.png


Just like @npjohnson recommended, all I had to do was select "Update Driver..." and point to this folder for the unknown device (it turns out I had already downloaded these too, I just didn't realize I could/should use these for the issue I was having):
1634707360859.png


Also, the commands that @criscodecookies posted on Aug. 5 were very useful as I didn't have an OTG host cable available. Without those commands, I would've been stuck not knowing when to flash recovery, the ROM itself, reboot, etc.

Thank you all for helping me get this working.
 

tramtrist

Senior Member
Jan 19, 2014
95
53
It appears youtubetv crashes when starting a video. Is this a DRM/widevine error or something? Pretty sad to go back to stock.
 

joebruin

New member
Oct 20, 2021
1
0
I got LineageOS loaded on my ONN device and I guess I was a little disappointed that it still required me to log into Google to get into the home page. Is there a way to load a default customer launcher (even Kodi) so that I can log out of Google?
 

kennkanniff

Senior Member
May 6, 2013
150
277

v12xke

Senior Member
Dec 5, 2010
2,082
666
The Woodlands, TX
Greetings, I've been flashing Nexus/Android phones for a long time but this (dopinder) gadget has got me a 'lil stumped. Unlocked, installed recovery, factory reset, wiped cache ALL OK, and then stuck on adb sideloading LOS. Initiating an update from ADB via recovery, cannot get past 50% before it aborts. File hash matches, I've tried 3 data cables, multiple USB ports on my rig that has no fastboot/adb issues with any other device. Binaries are up to date. Any suggestions would be welcomed.
 

UnionBlvd

Senior Member
Aug 12, 2012
89
22
Is OTG disabled/is there a documented issue with OTG on this ROM? I have a squid-like cable that supplies power and also passes through three USB ports, and it worked with the stock firmware - but as soon as I flashed this image it seems to do absolutely nothing but pass power. Could it be exclusive to the onn. box?
Surprised no one else replied, but I'm having the same problem on a Dynalink box. OTG cable went completely useless after installing Lineage.
 

v12xke

Senior Member
Dec 5, 2010
2,082
666
The Woodlands, TX
Will a wireless keyboard work with the dopinder box now or is this even possible for the future? I have an old logitech wireless one with a built in mouse pad. Or maybe something like THIS Rii mini that supports both wifi and bt.
 
Last edited:

HiJacK69

Member
Oct 8, 2011
43
2
I installed lineageos on my ONN box, but didn't like the results. I was having playback issues in 60 fps video formats. I flashed the factory image back and installed magisk. I have everything set up the way I like but. I spent so many hrs tinkering with it.

Is there a way to backup my ONN image? I'm used to using twrp. I checked the recovery options, but don't see an option to create a backup image. If this is possible, I plan to pick up a few more ONN boxes and just flashing my backup image onto the other boxes.

Thanks!
 

fathergweedo

Senior Member
Feb 8, 2014
140
48
Detroit
I installed lineageos on my ONN box, but didn't like the results. I was having playback issues in 60 fps video formats. I flashed the factory image back and installed magisk. I have everything set up the way I like but. I spent so many hrs tinkering with it.

Is there a way to backup my ONN image? I'm used to using twrp. I checked the recovery options, but don't see an option to create a backup image. If this is possible, I plan to pick up a few more ONN boxes and just flashing my backup image onto the other boxes.

Thanks!
May I ask what version of Magisk you used and any steps required for root on the stock OS? Meaning, can you patch the boot image from within, or patch a copy from elsewhere to flash via fastboot afterward? Sory to have no input of late in this thread, but RL comes first ;)

BTW, I still have a virgin (dopinder) device to play with if anyone has anything they want me to try.
 
Last edited:

Top Liked Posts

  • 1
    i don't have a setup capable of a build environment unfortunately...but thank you for offering to help!! 😊
    No one's telling you to build, yo:

    tw.jpg


    Well, one can only offer.
    1
    No one's telling you to build, yo:

    View attachment 5473225

    Well, one can only offer.
    If you're looking to distribute, please start your own thread.

    Also, nice work!
  • 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!
    4
    In case this helps anyone, this is how I've been getting USB debugging on without a google account and without updates.

    Turn device on...
    -connect remote control
    -select language
    -skip phone setup
    -hit settings key on remote "cog-wheel"
    -go to "apps" > "see all apps"
    -select "update" and force stop
    -select "show system apps"
    -select "dynamic system updates" and force stop
    -select and disable (or force stop):
    *(it probably doesn't need to be all of these but I got sick and tired of narrowing it down)
    google
    google one time init
    google partner setup
    google play services
    google services framework
    market feedback agent
    second screen setup auth bridge
    settings suggestions
    setup wizard (force stop)
    setupcustomizer

    -back out, back out, back out, until...
    -setup remote again
    -select language again

    !!! - Pay attention directly after the next step. If you see anything other than "successfully connected to internet" then you missed something and it's going to download the update - hit settings button and wifi off

    -sign in to network (It should say "checking connection" "successfully connected to internet")
    -as soon as you see the screen with a black background and "updating apps" message
    -hit settings button on remote
    -turn off WiFi

    Now developer options can be enabled and USB debugging turned on.
    3
    Is this in reference to LineageOS or stock? I assume the former ("breaks AVB") refers to LineageOS, while the latter ("Magisk patched boot image") refers to stock?

    Unrelated: thank you for being so active in this thread, and for all the work you and others do to bring LineageOS to those who mostly just ask dumb questions or complain :p
    All of that was in reference to stock.

    Lineage can be safely updated after pretty much any modification as it flashes a full OTA, and disables AVB. Will persist magisk through OTAs
    2
    So, per device it's different:

    deadpool/dopinder/wade: you can't update while you're rooted or have any sort of modification to system, it breaks. Breaks AVB, now. If you just have a magisk patched boot image, that should be fine I think, Magisk has OTA handling.

    Sabrina: Don't update anything ever, this device will re-lock itself and probably brick itself if you do, once the exploit is run, you're unlocked and should leave it. As such, you can flash back to stock like the thread details, but beyond that, which will mean you can never unlock again, don't do anything like that.
    2
    I appreciate the heads up on all this, but earlier I did another repo sync for fun and my new builds have been booting (ofc without the ATV platform commits or apps, so they're bare builds), and since then I've been poking with space for OpenGApps TV stock via the systemimage reserved size before I start figuring my apps out. I'm willing to work through the progress until it does just work, but in the meantime I'm not intending to start making production releases any time soon so it's not an issue for my personal testing!
    Oh, do whatever you want! I wasn't trying to discourage you, just letting you know it's not yet ready.

    As for reserved sizes, I'm actually working on it right now. Very close to working.

    If you're interested in really helping out, help me figure out how to fix hardware backed OMX, as I have no clue. We just fell back to software backed OMX instead which is meh.
  • 11
    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 Unofficial Lineage OS 18.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:
    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:
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • Hardware backed OMX - Therefore, by proxy, L1 DRM is broken, we're currently trying to fix it, but it's proving tough to figure out. Software OMX fallback is in use for now, though, and works fine on almost all non-DRM videos.
    • SELinux is permissive, this is only due to a lack of time to put together a decent looking sepolicy for the devices,
    • (wade/dopinder only) Side-button doesn't work - On wade, you can use the IR remote to navigate recovery, on dopinder, you'll need an OTG adapter, and a keyboard or controller to attach.
    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. OTA is provided the same way officials would have them.
    • 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.
    FAQ:
    • Does L1 Widevine DRM break when I unlock my bootloader?

      Nope, it works fine, or at least, it will once we fix hardware backed OMX. L1 certificates, and the mechanism that reports is all still exist and work as expected.

    • Can I haz Netflix?

      Not the Android TV one, not until we fix hardware backed OMX, at least - after that it should work fine. For now, you can go sideload the tablet Netflix, it works fine!

    • 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?

      Nope, SELinux is permissive, among other things. You can probably use Magisk if you really need that, but the good news is, 99% of Android TV apps don't care about SafetyNet, unlike on mobile, where a lot of them do.

    • 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
    • stricted
    • webgeek1234
    • deadman96385
    • trautamaki
    • luca020400
    • aleasto
    9
    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!
    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!
    4
    sabrina support is live, enjoy.
    4
    In case this helps anyone, this is how I've been getting USB debugging on without a google account and without updates.

    Turn device on...
    -connect remote control
    -select language
    -skip phone setup
    -hit settings key on remote "cog-wheel"
    -go to "apps" > "see all apps"
    -select "update" and force stop
    -select "show system apps"
    -select "dynamic system updates" and force stop
    -select and disable (or force stop):
    *(it probably doesn't need to be all of these but I got sick and tired of narrowing it down)
    google
    google one time init
    google partner setup
    google play services
    google services framework
    market feedback agent
    second screen setup auth bridge
    settings suggestions
    setup wizard (force stop)
    setupcustomizer

    -back out, back out, back out, until...
    -setup remote again
    -select language again

    !!! - Pay attention directly after the next step. If you see anything other than "successfully connected to internet" then you missed something and it's going to download the update - hit settings button and wifi off

    -sign in to network (It should say "checking connection" "successfully connected to internet")
    -as soon as you see the screen with a black background and "updating apps" message
    -hit settings button on remote
    -turn off WiFi

    Now developer options can be enabled and USB debugging turned on.