• 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

fathergweedo

Senior Member
Feb 8, 2014
139
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!
Assuming you have root, you should be able to pull each partition in an adb shell. Sorry I don't recall the commands. I would likely have to dig up some VERY old notes (that maybe gone), or do some serious searching here on other threads.
 

npjohnson

Recognized Developer
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.
Yeah, from in Android. Worked fine before.
Looks like the wiki is down...
It's back, brief reboot.
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.
Flash it via recovery, or just patch the boot image like their wiki details.
 

emveepee

New member
Sep 28, 2010
2
1
Installed fine on ONN but ExoPlayer reports it doesn't support mpeg2video so something is different from stock. Is this expected, I've done multiple installs with the same results.
 

npjohnson

Recognized Developer
Can someone please help me to flash stock OS on Onn box, I tried a few times but it keeps giving a error, signature verification failed error 21 and failed to find update binary META-INF/com/google/android/update-binary, not sure what am I doing wrong.

I downloaded the stock image form here, https://download.ods.ninja/Android/firmware/dopinder/.
That doesn't get flashed in recovery... its a factory image. Flash it using the flash-all.sh script.
 
  • Like
Reactions: dealercohagen

HiJacK69

Member
Oct 8, 2011
43
2
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.
I used version 23.0, which I grabbed from the developer's website. In regards to the steps, I just did a search in the forum for "magisk", and I believe it was the 2 or 3 result from the top. Someone had posted step-by-step instructions. Just remember to unlock the bootloader first.
 
Last edited:
  • Like
Reactions: fathergweedo

HiJacK69

Member
Oct 8, 2011
43
2
Assuming you have root, you should be able to pull each partition in an adb shell. Sorry I don't recall the commands. I would likely have to dig up some VERY old notes (that maybe gone), or do some serious searching here on other threads.
I managed to find a version of TWRP from another forum. I haven't tried it yet, but it's for the S905Y2 chipset. I'm hoping it works, so I can make a backup. I also found some old posts for backing up nandroid for phones, but haven't tried it yet.
 

hp420

Senior Member
Jul 31, 2011
2,566
1,430
Gainesville, Fl
Google Nexus 4
T-Mobile LG G2
  • Like
Reactions: v12xke

fixsony

Member
Apr 27, 2008
41
2
I don't want to look annoying, but I still haven't been able to revive my TV box. I changed the usb cable, changed computers and the result is the same. With a successful flashing, my TV box either gets into a cyclic restart or gets stuck in a constant load (colored figures spin and move). What am I doing wrong, have any ideas? Thanks.
 

v12xke

Senior Member
Dec 5, 2010
2,082
666
The Woodlands, TX
You don't mention whether this is your first LOS install or you have had it working before?

My stumbling block was not fastboot booting recovery after flashing it. I thought the adb install was successful but it wasn't .

If you already had LOS up and running fine before until SHTF then just reflash back to stock and start fresh using THIS from an earlier post
 

fixsony

Member
Apr 27, 2008
41
2
You don't mention whether this is your first LOS install or you have had it working before?

My stumbling block was not fastboot booting recovery after flashing it. I thought the adb install was successful but it wasn't .

If you already had LOS up and running fine before until SHTF then just reflash back to stock and start fresh using THIS from an earlier post
Try this way and now non stop booting LineageOS logo going
 

Attachments

  • 2021-10-29 19-18-31.mp4
    123.3 KB · Views: 0

Top Liked Posts

  • 3
    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.
  • 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!
    3
    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 I'm successfully running the LineageOS 18.1 dopinder builds, and I decided I wanted to try my hand at supporting ATV devices with my custom ROM project. Got a clean repo sync of lineage-18.1 and ran a successful dopinder build, but it doesn't boot and hangs at splash, and after a few boot attempts HDMI dies until I restore to stock. What's the quickest way to get adb debugging in early init so I can get a logcat and dmesg to study?
    your issue is that these devices aren't fully official for good reason ;p we just merged enforcing selinux yesterday, and GApps reservation space isn't done yet.

    You also need all the ATV platform commits for your ROM, and the apps and such.

    Honestly, give it a month or so and it should /just work/.
    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.
  • 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.
    3
    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.