• 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

fixsony

Member
Apr 27, 2008
29
2
Hi, I need help box stock in recovery boot loop
 

Attachments

  • Screen.jpg
    Screen.jpg
    146.3 KB · Views: 87
May 22, 2020
17
6
I mean, I probably won't be doing them, but I can tell you with confidence, it's like a 2 line change.
It's been a month and a half since we discussed the possibility of the tablet-flavored (non-TV) release. It seems that the number of complaints has decreased and the basic quality of builds has improved enough to bother you again in this regard: are there any positive changes in this direction, or it is not worth expecting to get a full-featured Android on dopinder? (I'm still following this thread carefully to make a buying decision.)
 

npjohnson

Recognized Developer
It's been a month and a half since we discussed the possibility of the tablet-flavored (non-TV) release. It seems that the number of complaints has decreased and the basic quality of builds has improved enough to bother you again in this regard: are there any positive changes in this direction, or it is not worth expecting to get a full-featured Android on dopinder? (I'm still following this thread carefully to make a buying decision.)
Eh, soon, sure.

I'll look into making a buildable target
 

shinji257

Senior Member
I've been watching this closely and at the moment I'm not going to be flashing it (the broken hardware omx is a bit of a breaker at the moment) but due to more recent experiments I've done is adoptable storage on LineageOS for these targets enabled and is it stable?

I forced it on Android TV 10 (stock) and it seemed to "work" but it made the whole OS unstable while accessing the drive. It would reboot randomly while transferring data or sometimes when just enumerating the installed applications. Occasionally it would fail to properly mount in the device and while it was listed it also said that the drive wasn't present. Eventually I gave up and removed it for the time being.
 

npjohnson

Recognized Developer
Hiya! I cant seem to find the download links for the rom or recovery for Wade. Was this project taken down?
New builds are going up tonight/tomorrow with October ASB
I've been watching this closely and at the moment I'm not going to be flashing it (the broken hardware omx is a bit of a breaker at the moment) but due to more recent experiments I've done is adoptable storage on LineageOS for these targets enabled and is it stable?

I forced it on Android TV 10 (stock) and it seemed to "work" but it made the whole OS unstable while accessing the drive. It would reboot randomly while transferring data or sometimes when just enumerating the installed applications. Occasionally it would fail to properly mount in the device and while it was listed it also said that the drive wasn't present. Eventually I gave up and removed it for the time being.
hardware OMX isn't that big a deal, all media still plays, and there's no "battery life" to worry about.

And yeah, adoptable storage is a bad idea, it isn't internal storage, and is at USB2 speeds - yeah, nah.
 

R3s1du3

Member
Apr 26, 2016
5
0
I have a quick problem (hopefully) picked the Onn 4k Tv box last week got force updated on start running stock OS 10 QT 20210902 firmware 1.01.32 I'm hitting a wall OEM unlock doesn't show up and I cant fastboot option doesn't detect device. I feel like I might be missing something or they changed something and started locking out mods. I followed the instruction cant figure out what's wrong
 

phony07

New member
Oct 8, 2021
3
0
First off, would like to start by thanking all the team for this project.
I just received my Onn device after two weeks of shipping :) and was ready to start the flashing.
But, first, October’s build are not yet ready I think (`An unknown error occurred`), and second, after reading the message of @R3s1du3, I’m hesitant to boot my device. The instructions clearly specify that:
> Warning: Before following these instructions please ensure that the device is on the latest Android 10 firmware.
but at the same time, it seems that connecting it to the internet would force an update that, a priori, disables OEM unlocking, at least option not visible in the Developer options.
What should I do?
 

npjohnson

Recognized Developer
I have a quick problem (hopefully) picked the Onn 4k Tv box last week got force updated on start running stock OS 10 QT 20210902 firmware 1.01.32 I'm hitting a wall OEM unlock doesn't show up and I cant fastboot option doesn't detect device. I feel like I might be missing something or they changed something and started locking out mods. I followed the instruction cant figure out what's wrong
I'm fairly certain the update doesn't block oem unlocking... worst case scenario bulkcmd commands are still available.

So, factory reset, set up (not on VPN or custom DNS), and go to dev settings, it's greyed out?
First off, would like to start by thanking all the team for this project.
I just received my Onn device after two weeks of shipping :) and was ready to start the flashing.
But, first, October’s build are not yet ready I think (`An unknown error occurred`), and second, after reading the message of @R3s1du3, I’m hesitant to boot my device. The instructions clearly specify that:
> Warning: Before following these instructions please ensure that the device is on the latest Android 10 firmware.
but at the same time, it seems that connecting it to the internet would force an update that, a priori, disables OEM unlocking, at least option not visible in the Developer options.
What should I do?
Hold off if you want but I struggle to believe they locked the bootloader forcibly.
 

phony07

New member
Oct 8, 2021
3
0
Well, it works! Sure, "OEM unlock" does not appear in Developer settings, but I was able to unlock just fine. I also followed the instruction given by @criscodecookies in https://forum.xda-developers.com/t/...-g12-sm1-family-devices.4313743/post-85434073.

1. Settings > Privacy > Ads > Opt out of Ads Personalization ;
2. Disable automatic updates from Play Store ;
3. Enable "Developer options" and "USB debugging" ;
4. I recommend people to downgrade Android TV Home to version 2 :
Code:
adb install -d './com.google.android.tvlauncher_2.3.1-340788485-f-1010901809_minAPI26(nodpi)_apkmirror.com.apk'
5. Download and sideload F-Droid ;
6. Install Aurora Store from F-Droid app and spoof "Realme 5 Pro" within the app ;
7. Because Netflix TV is not yet supported by this ROM due to OMX, search and install Netflix from within Aurora Store ;
8. Generate and sideload an Android TV shortcut for the sideloaded Netflix using this generator :
Code:
Name: Netlfix Launcher
Package: com.netflix.mediaclient
Logo: https://play-lh.googleusercontent.com/TBRwjS_qfJCSj1m7zZB93FnpJM5fSpMA_wUlFDLxWAb45T9RmwBvQd5cWR5viJJOhkI=s180
Banner: https://play-lh.googleusercontent.com/ybf8V_yUFpSgW-rs1r7oigzSAWIQcSHCwHd2EYkxRD0KGz8CNBp0DN8T1Rz17KvJJSYl
9. Sideload MATVT and follow these instructions after installation to get a working virtual mouse (by default, long press on "mute button" will toggle between scroll and mouse mode) ;

That being said, I’ve not been able to login into Netflix using the remote :/
 
Last edited:

npjohnson

Recognized Developer

R3s1du3

Member
Apr 26, 2016
5
0
I finally got it working not sure what the issue is had the sideload rom 3 times before it stopped erroring out aside from the Netflix and HBOmax issues I noticed everything displays fairly well on a 4K monitor but if i switch over to a 1080p display things are fuzzy (text apps) and I cant adjust display settings in OS
 

iPack

New member
Apr 13, 2013
3
0
@npjohnson I am unable to ADB into the Walmart Onn UHD Box (dopinder). When I enable Developer Options, it says " Developer options are not available for this user". I would like to get LineageOS on this box. Any help is appreciated. Thanks.
 
Last edited:

tokoam

Senior Member
Jun 24, 2007
920
167
Plantation
cannot connect to 10.0.0.18:5555: No connection could be made because the target machine actively refused it. (10061) . This is the error I get when trying to connect to ADB wirelessly . I never get a prompt any reason why ?it never seems to want to connect . USB debugging is enabled I have tried to turn it off and on but no go .
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Th
    Surprised no one else replied, but I'm having the same problem on a Dynalink box. OTG cable went completely useless after installing Lineage.
    This is fixed. Next build will do it.
    2
    It's been a month and a half since we discussed the possibility of the tablet-flavored (non-TV) release. It seems that the number of complaints has decreased and the basic quality of builds has improved enough to bother you again in this regard: are there any positive changes in this direction, or it is not worth expecting to get a full-featured Android on dopinder? (I'm still following this thread carefully to make a buying decision.)
    Eh, soon, sure.

    I'll look into making a buildable target
    2
    The device is in fastboot mode; your PC is not configured to detect it. You haven't installed fastboot drivers in Windows (https://developer.android.com/studio/run/win-usb), so it's no wonder the device is not being recognized.

    Given how easy it is to boot Linux from a flash drive, it's pretty much an expectation on here that you try this in Linux and not in Windows.
    Windows works fine. Just install the drivers like the wiki details.
    1
    Hey so does this mean I don't need OTG cable for my Onn 4k box then? I can do all of this with just connection to my laptop + adb?
    Yeah, I'll update the wiki soonish
    1
    I haven't even tried lineage as of yet, but this was my 1st encounter of having to loginin/setup to access debugging. Guess I'll find out tomorrow if it's really necessary when booting directly to the stock recovery > booloader. Fingers crossed ;)
    It's not necessary at all, you can boot into bootloader mode and just issue the command
  • 10
    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
    6
    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!
    4
    sabrina support is live, enjoy.
    3
    could you all please take this to private message? there's 3 pages of messages from you talking about fixing one user's device. we all keep getting notifications for every message you post 🤷

    thank you 😊
    This is all relevant information that anyone who gets in this situation would benefit from.

    You can turn off the notifications, or set up daily summaries?
    3
    Th
    Surprised no one else replied, but I'm having the same problem on a Dynalink box. OTG cable went completely useless after installing Lineage.
    This is fixed. Next build will do it.