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

Search This thread

goapy

Senior Member
Dec 30, 2021
192
45
Caveat: I won't follow up on any questions. Do this at your own risk. You don't need an OTG cable.

If you can't boot into fastboot mode:
  • run `./update partition boot <boot.img>` as root
  • run `./update bulkcmd "reset"` (including quotes) as root
  • You should now be in fastboot mode

The first step in the quote above flashes boot.img to the boot partition on the emmc.
The second step reboots the device.

This probably won't result in rebooting to fastboot (the bootloader version of fastboot).

Instead of:
update bulkcmd "reset"

Using this command:
update bulkcmd "fastboot"

would immediately load bootloader fastboot (without even rebooting).
And it isn't necessary to flash the boot partition first in order for this to happen.

Notice that there are no questions in this reply, so you won't have to violate your pledge not to follow up on any questions.
 
D

Deleted member 12243335

Guest
The first step in the quote above flashes boot.img to the boot partition on the emmc.
The second step reboots the device.

This probably won't result in rebooting to fastboot (the bootloader version of fastboot).

Instead of:
update bulkcmd "reset"

Using this command:
update bulkcmd "fastboot"

would immediately load bootloader fastboot (without even rebooting).
And it isn't necessary to flash the boot partition first in order for this to happen.

Notice that there are no questions in this reply, so you won't have to violate your pledge not to follow up on any questions.

I think you were so obsessed with the first line, you missed this part

For some reason (probably due to earlier experimentation with the mainline kernel) I couldn't boot into recovery without flashing all the images first, so YMMV
 

goapy

Senior Member
Dec 30, 2021
192
45
I think you were so obsessed with the first line, you missed this part

For some reason (probably due to earlier experimentation with the mainline kernel) I couldn't boot into recovery without flashing all the images first, so YMMV

Booting into recovery is one thing, booting (or loading) bootloader fastboot is another.

Whatever is true about your earlier experimentation and the results it produced or the remediation that it required afterwards, it is still the case that the usb burn mode command:

update bulkcmd "reset"

only reboots the device. While the usb burn mode command:

update bulkcmd "fastboot"

immediately loads bootloader fastboot.

You listed a series of steps to get into "fastmode mode". I was merely pointing out, for others reading this thread, that these steps may be incorrect, in so far as using the update utility with the reset command in order to achieve that limited end.
 
D

Deleted member 12243335

Guest
Booting into recovery is one thing, booting (or loading) bootloader fastboot is another.

Whatever is true about your earlier experimentation and the results it produced or the remediation that it required afterwards, it is still the case that the usb burn mode command:

update bulkcmd "reset"

only reboots the device. While the usb burn mode command:

update bulkcmd "fastboot"

immediately loads bootloader fastboot.

You listed a series of steps to get into "fastmode mode". I was merely pointing out, for others reading this thread, that these steps may be incorrect, in so far as using the update utility with the reset command in order to achieve that limited end.
You're absolutely right. I should have probably explained how bulkcmd fastboot didn't initially work for me, how I spent an entire evening trying numerous other things to resolve the exact same problem the commenter I replied to was having, and how the only solution that ended up working was very hacky and dumb, that it warranted me making an xda-dev account to post a comment. I realize now the error of my ways.
 

js8call

Member
Aug 10, 2022
11
0
I have bricked my Onn TV box..it only shows the Onn screen..I tried to unbrick with the linux method but no luck..
Im not clear how to run these commands:
"./update xxx"..do I type sh before or just ./update xxx within the terminal?
Also theres an 650mb update and it seems its obliged to update before doing anything further..should I update before the Lineage process or how it can be bypassed?
 

goapy

Senior Member
Dec 30, 2021
192
45
You're absolutely right. I should have probably explained how bulkcmd fastboot didn't initially work for me, how I spent an entire evening trying numerous other things to resolve the exact same problem the commenter I replied to was having, and how the only solution that ended up working was very hacky and dumb, that it warranted me making an xda-dev account to post a comment. I realize now the error of my ways.

Well, if what you described worked, I won't argue with that.

It is difficult to understand how bulkcmd fastboot could fail to work though, as long as there is a burn mode connection. Because it executes directly in uboot instantaneously, without any reboot. This is easiest to see if a uart connection is also available while doing all of these operations. That is the best way to learn what is going on behind the scenes.

Anyway, if anyone wants to try using bulkcmd reset instead of bulkcmd fastboot, it will cause no harm to try.
 
Last edited:

js8call

Member
Aug 10, 2022
11
0
Yes..Im sorry for the miswording...
When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..then I added my account and turned on developer mode..there was no oem unlock option..I read the web guide for Windows...I got to boot to the stock recovery..I tried to upload the dot files but it gave me an error..I skipped that step and proceeded to flash the Lineage recovery image..it took it but it shutdown..now I only get the ONN screen..
But in linux I ran lsusb and its listed as a Amlogic device...any help?

If it is bricked, how could the update install
 

BTK19

Senior Member
Jan 25, 2021
85
23
EARTH
Amazon Fire TV
Nexus 6
Yes..Im sorry for the miswording...
When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..then I added my account and turned on developer mode..there was no oem unlock option..I read the web guide for Windows...I got to boot to the stock recovery..I tried to upload the dot files but it gave me an error..I skipped that step and proceeded to flash the Lineage recovery image..it took it but it shutdown..now I only get the ONN screen..
But in linux I ran lsusb and its listed as a Amlogic device...any help?
What are dot files. Post in thread '[UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices' https://forum.xda-developers.com/t/...-g12-sm1-family-devices.4313743/post-87029813. that is the way to flash lineage
 
Last edited:

goapy

Senior Member
Dec 30, 2021
192
45
When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..

It must have rebooted to install the update immediately after it downloaded.

When an automatic check for updates is made as part of the oobe/setup wizard process during the first boot of the device, it won't continue without first rebooting to install the just downloaded update.

So, if you ever got fully into the OS, the update was very likely installed before that.
 

js8call

Member
Aug 10, 2022
11
0
I installed the Worldcup windows driver..I hold side button until Win7 registered and shows lisusb-win32 USB/Worldcup Drivers and its active . I go adb devices and no device is listed..I adb reboot bootloader and the Win 7 cmd says error : no devices found...the white tiny light on the box is off..what next?
 

goapy

Senior Member
Dec 30, 2021
192
45
When the box has a wordcup connection to your windows pc, abd/fastboot can't communicate with the box.

Use the command line update.exe utility instead.
 

js8call

Member
Aug 10, 2022
11
0
When the box has a wordcup connection to your windows pc, abd/fastboot can't communicate with the box.

Use the command line update.exe utility instead.
this site only has the git linux version..I cant find a standalone windows version,,,anyplace I can find it?...the openlinux2 amlogic site is down
 

goapy

Senior Member
Dec 30, 2021
192
45
Khadas has a copy on github, here.

All of the dlls in the folder are required in addition to the update.exe binary.

Or, attached is a copy previously linked in a prior forum post.
 

Attachments

  • amlogic.zip
    52.9 KB · Views: 25

js8call

Member
Aug 10, 2022
11
0
Khadas has a copy on github, here.

All of the dlls in the folder are required in addition to the update.exe binary.

Or, attached is a copy previously linked in a prior forum post.
Thank you very much Goapy..I believe this box is bricked beyond repair..now Im NOT getting the ONN screen and if I press and hold the button the white led shows lit once very fast and then turns off..
On Ubuntu, dmesg says theres is a usb thing attached but USBview says a unknown thing is attached..I copied Kadas repo and ran aml-flash but says error : no devices..
Im going to assume that If I dont see the ONN screen anymore, its hardbricked..
Which is sad, 4k Youtube videos were really nice on this box..
Im going to try to exchange the box for another one..will you help me install.Lineage correctly?
 

p0werpl

Senior Member
Aug 30, 2021
68
8
Im going to try to exchange the box for another one..will you help me install.Lineage correctly?
I am sure goapy is the nicest human either side of the Mississippi, but please answer a couple of questions first:

You have already chalked out plans to return Onn #1 because you were unable to unbrick it. What makes you think Onn #2 will not suffer the same fate? Asked differently, what skills have you gained in the intervening time to bring about a different outcome?

Have you read the last few pages (including clear statements by the OP) about how LOS on the Onn box (dopinder) has DRM issues? Based on your request above, I think the answer is clear, but please answer anyway.

What about stock do you not like that you want to install LOS?
 
Last edited:
  • Like
Reactions: BTK19

js8call

Member
Aug 10, 2022
11
0
I am sure goapy is the nicest human either side of the Mississippi, but please answer a couple of questions first:

You have already chalked out plans to return Onn #1 because you were unable to unbrick it. What makes you think Onn #2 will not suffer the same fate? Asked differently, what skills have you gained in the intervening time to bring about a different outcome?

Have you read the last few pages (including clear statements by the OP) about how LOS on the Onn box (dopinder) has DRM issues? Based on your request above, I think the answer is clear, but please answer anyway.

What about stock do you not like that you want to install LOS?
Yes, Im sure he is a good person!
Thinking about what you proposed, I think your right..I only want the following apps installed..
Brave Browser
Flexie
Plex
Kodi
Viper4android
a noads YT app

Thats about what I like to have. I know Viper4andoid needs root SuperSu and busybox
I dont care about Netflix or Disney..I dont use them...
Any help?
 

goapy

Senior Member
Dec 30, 2021
192
45
I believe this box is bricked beyond repair..now Im NOT getting the ONN screen and if I press and hold the button the white led shows lit once very fast and then turns off..
What happened to the worldcup connection that you were getting on your windows pc just a few hours prior?

It's very difficult to brick the onn device beyond repair. It takes something like bootloader corruption or physical hardware failure to do it. Anything less than that can usually be fixed using burn mode, including problems like a recovery bootloop.
 

js8call

Member
Aug 10, 2022
11
0
What happened to the worldcup connection that you were getting on your windows pc just a few hours prior?

It's very difficult to brick the onn device beyond repair. It takes something like bootloader corruption or physical hardware failure to do it. Anything less than that can usually be fixed using burn mode, including problems like a recovery bootloop.
the update.exe is giving a win core 12 dll error. I have updated my Win7 to SP2 and I still get the error..I can try on my win10 pc after work..but Im not getting the Onn screen anymore..I plug the box with the button pressed, I see a quick white blip and Win7 sees the worlcup device..but the Kadas update tool is not working becuase of the dll error..
 

Top Liked Posts

  • 2
    Would you expand upon this using maximum detail?

    Sure, but it requires root and some familiarity with shell. Also, you are likely aware, but this is a rare problem only for networks which filter by mac. If you are unable to see wifi networks at all, you have a different problem.

    First, attempt to connect to or create a connection through the android UI to the SSID of your network. If this problem relates to you, you should be able to see your SSID but the connection will fail. That's fine, leave the failed connection there and enter shell. Then, edit:
    Code:
    /data/misc/apexdata/com.android.wifi/WifiConfigStore.xml
    Find the code block for your SSID (it should be the only one). You are interested in the keys:
    Code:
    RandomizedMacAddress
    MacRandomizationSetting
    RandomizedMacAddress contains the randomized mac android wants to use for your SSID. You would supply this mac to your router. MacRandomizationSetting should be set to 0 (zero) to avoid re-randomization every time the interface goes up, like so:
    Code:
    <int name="MacRandomizationSetting" value="0" />
    Reboot and you should have a persistent mac.

    But wait! There is an easier way, which does not require root or shell. It turns out the UI settings are available AFTER a connection has been successfully negotiated. Provided you have access to your router settings, I would recomend you temporarily disable mac filtering on your router, connect normally, then access the wade UI Settings submenu under the active connection to disable mac randomization. You can then re-enable mac filtering on your router and supply the (now persistent or hardware stock) mac.

    I have also encountered another issue which may be problematic for android TV on wade:
    5) HDR. Wade really, really wants to use HDR. Even when it shouldn't and on SDR sources. Even with HDR manually disabled in Settings (I suspect this option is broken or not checked at boot), we still boot to HDR modes which then persist in apps. In fact, wade will preferentially boot to a lower resolution with display HDR support, rather than a higher resolution without display HDR support. It is possible to force SDR by manually switching to a higher resolution without HDR support, then back to lower resolutions, so the SDR modes are available, just not properly selected. I am not sure if this problem is specific to wade, or something general to lineage.
    1
    Thx for debugging this. GMS successfully randomized Mac, the aosp component appears to fail. I will disable Mac randomization and fix it.

    You're very welcome. I'm delighted to have made a contribution.

    What do you mean the "blob" I'm the official is wrong? What blob?

    dtb.img

    The partition image in 19.1-20220918-nightly appears to have failed to build. It still boots, but with significantly reduced functionality. I see you have just pushed 19.1-20220925-nightly. I have not flashed this yet, but I think it has the same problem. Compare the partition from 19.1-20220908-UNOFFICIAL.
    1
    Stock sets it though? Why wouldn't we.
    Cause it causes problems, it would be beneficial to not have the device upscale everything to HDR when viewing SDR content; especially for people who have old HDR compatible 8-bit TV-panel's that don't actually output 10-bit color correctly, cause they will have an extremely over-saturated color palette.

    The Amlogic source-code I have is for Android 9, and their supplemental vendor app DROID_SETTINGS had these activities:

    com.droidlogic.tv.settings.display.sdr.SdrSettingActivity
    com.droidlogic.tv.settings.display.hdr.HdrSettingActivity

    And the only Amlogic device I've seen be updated to give User access to these settings activities was the the Onn.4K, but Askey only made the HdrSettingActivity available, it's where you switched it to On, Off, or Auto; it was labeled as the "HDR" setting, and made available under the Display settings options.

    If somebody had the time to code all the extra settings that Amlogic makes available for the DROIDLOGIC app to access, that would be awesome, but for now I just ask that we eliminate that sdr2hdr prop.
  • 6
    wade and deadpool are official now!
    3
    Hi all,
    quick question regarding the "Walmart Dynalink 4K Box". Can I use the same procedure/ image for the non Walmart Dynalink 4k box --> https://dynalink.life/products/dynalink-android-tv?

    i would like to install LOS on the dynlink 4k from Amazon (walmart does not exist here), same question at #1231.

    you write in #1233 that it is not possible - where are the differences there? from phones I know no problems in different regions and that only in the mobile area!
    Interesting.

    Yes. You totally can.

    Sorry, I thought this was asking about the dynalink stick - that box is the same.
    3
    Also, I solved the signing issue with Luca's help.

    Builds should hopefully roll for wade/Deadpool with no GMS tomorrow.

    I'll then look into tablet builds feasibility.
    2
    However I run into a boot loop. I see the LinageOS Logo and sometimes the remote control but after that the box restarts. I installed several times with the same result.
    Do you have an idea what I could do?
    You could list, with precision, the steps that you repeatedly did and maybe someone will notice where you went wrong. Most problems lately seem to involve failure to flash the appropriate dtb/dtbo at the appropriate time(s).

    With the v18 builds, it was fortunate that dtb/dtbo were also compatible with stock and vice versa. For whatever reason (I don't know) there is not this same sort of dtb/dtbo compatibility between stock and v19 builds.
    2
    For this you need to join the number of those people here who are waiting for the tablet builds arrival on the official release day. Take your ticket and have a seat beside me.
    Or just don't use google apps, you can build without them easily.

    ATV works fine enough without gapps.

    Tablet builds will follow.

    The official builds are queued but they fail to sign for some reason - working that out rn.
  • 26
    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 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:
    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:
    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:
    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
    14
    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!
    6
    wade and deadpool are official now!
    6
    Note:

    Since the Lineage Android TV Builds for this little box (aka Boxes), are stable for the most part, but seems
    people are bouncing back in forth from Stock to Lineage and back to stock.

    I created a batch file that will auto flash the stock images and wipe data and so on.. pretty much it will
    make your box as it was when you first booted it after taking it home to try it.

    2nd, I also created a batch file that will backup current images.. No need for a fancy recovery or anything like the
    such. it will use the worldcup or what I like to say, USB Burn mode, and backup each and every partition.
    as well as some not so much needed ones like, misc and metadata. (Just for giggles)..

    backups will be copied to backup dir, I also created a separate batch file to restore your backup.


    I am one that hates doing things the long way over and over, so I always create ways to make things simple
    in the future for people.

    This way, you all can test your hearts out all the new lineages and still have your full Stock backup (including data).
    and restore back in forth as you wish.

    I will upload the backup_restore zip package as soon as I can and with @npjohnson permission I will link
    in thread. Otherwise you will have to just DM/PM me and ill link you the location.

    I am just trying to help the many that I seen complain and dont understand how to go back in forth.
    so with this script, it should take care of most on that. No Fancy Recovery needed...

    you will need worldcup driver for Amlogic........ you can find that on your own.

    Also, to get into USB Burn mode, press side button while plugging in USB cable.
    Keep pressing till you see the LOGO or hear the sound from your computer.

    then just run the batch file and wait..

    if its easier for you:

    Run the batch file, it will keep saying waiting for device..
    Just press the side button while plugging in USB, when you see it start, then release button...........
    and wait till finished..

    Only TESTED On Dopinder Boxes, but im sure they are all the same as for the partition layouts.
    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!