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

Search This thread

Erv349

New member
May 21, 2014
2
0
I am having a hell of a time getting this Walmart onn 4K Box/dopinder to flash recovery. I am able to get to the bootloader, but I am not able to see it as a "fastboot" device. I was forced to update to the "October 2021" update. Any help would be greatly appreciated!
 

Erv349

New member
May 21, 2014
2
0
Ok so I figured it out, when in the bootloader, I realized that my computer wasn't recongnizing the devices, so I just made it use the ADB driver. So I have now formatted and flashed LineageOS, but its not showing me the LineageOS version in the About Section. Soooo how else can I verify that it is indeed Lineage? It shows my "build" version as onn-user 10 qt 2021111111 release-keys.
 

Eliminater74

Recognized Developer
Ok so I figured it out, when in the bootloader, I realized that my computer wasn't recongnizing the devices, so I just made it use the ADB driver. So I have now formatted and flashed LineageOS, but its not showing me the LineageOS version in the About Section. Soooo how else can I verify that it is indeed Lineage? It shows my "build" version as onn-user 10 qt 2021111111 release-keys.
when you boot, you will see the lineage boot gfx, not the ONN gfx. that is how you will know your in Lineage..
 
  • Like
Reactions: kozmo2k4

mcdonagh

New member
Jan 17, 2022
1
0
I'm trying to build lineageos for dopinder, and was following the guide provided here: https://wiki.oddsolutions.us/devices/dopinder/build

I'm running Windows 10 with Debian Unstable WSL 2. After building for about 4 hours, it just fails. Part of the error log says ext2fs, but I'm running ext4 in wsl.

Looking for dependencies in device/askey/dopinder Looking for dependencies in device/amlogic/g12-common Looking for dependencies in kernel/amlogic/linux-4.9 kernel/amlogic/linux-4.9 has no additional dependencies. Looking for dependencies in hardware/amlogic/kernel-modules/mali-driver hardware/amlogic/kernel-modules/mali-driver has no additional dependencies. product/dopinder/obj/PACKAGING/odm_intermediates/odm_image_info.txt out/target/product/dopinder/odm.img out/target/product/dopinder/system ) && (true )" 2022-01-17 17:52:29 - build_image.py - ERROR : Failed to build out/target/product/dopinder/odm.img from out/target/product/dopinder/odm Traceback (most recent call last): File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 174, in _run_module_as_main File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 72, in _run_code File "~/lineageos/out/host/linux-x86/bin/build_image/__main__.py", line 12, in <module> File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 174, in _run_module_as_main File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 72, in _run_code File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 816, in <module> File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 808, in main File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 438, in BuildImage File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 101, in GetFilesystemCharacteristics File "~/lineageos/out/host/linux-x86/bin/build_image/common.py", line 281, in RunAndCheckOutput common.ExternalError: Failed to run command '['tune2fs', '-l', 'out/target/product/dopinder/unsparse_odm.img']' (exit code 1): ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether out/target/product/dopinder/unsparse_odm.img is mounted. tune2fs 1.45.4 (23-Sep-2019) [ 0% 19/3121] Building Kernel Config make: Entering directory '~/lineageos/kernel/amlogic/linux-4.9' make[1]: Entering directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' GEN ./Makefile KCONFIG_SELINUX((null)) KCONFIG_LOG_SELINUX((null)) KCONFIG_VARIANT(arch/arm64/configs/g12a_variant_defconfig) KCONFIG_DEBUG((null)) # # configuration written to .config # make[1]: Leaving directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' make: Leaving directory '~/lineageos/kernel/amlogic/linux-4.9' make: Entering directory '~/lineageos/kernel/amlogic/linux-4.9' make[1]: Entering directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' GEN ./Makefile scripts/kconfig/conf --savedefconfig=defconfig Kconfig make[1]: Leaving directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' make: Leaving directory '~/lineageos/kernel/amlogic/linux-4.9' 17:52:32 ninja failed with: exit status 1 #### failed to build some targets (13 seconds) ####

Can anyone help me understand why this is failing here, and how I can fix and/or circumvent this?

I really don't want gapps on my devices
 

Eliminater74

Recognized Developer
I'm trying to build lineageos for dopinder, and was following the guide provided here: https://wiki.oddsolutions.us/devices/dopinder/build

I'm running Windows 10 with Debian Unstable WSL 2. After building for about 4 hours, it just fails. Part of the error log says ext2fs, but I'm running ext4 in wsl.

Looking for dependencies in device/askey/dopinder Looking for dependencies in device/amlogic/g12-common Looking for dependencies in kernel/amlogic/linux-4.9 kernel/amlogic/linux-4.9 has no additional dependencies. Looking for dependencies in hardware/amlogic/kernel-modules/mali-driver hardware/amlogic/kernel-modules/mali-driver has no additional dependencies. product/dopinder/obj/PACKAGING/odm_intermediates/odm_image_info.txt out/target/product/dopinder/odm.img out/target/product/dopinder/system ) && (true )" 2022-01-17 17:52:29 - build_image.py - ERROR : Failed to build out/target/product/dopinder/odm.img from out/target/product/dopinder/odm Traceback (most recent call last): File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 174, in _run_module_as_main File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 72, in _run_code File "~/lineageos/out/host/linux-x86/bin/build_image/__main__.py", line 12, in <module> File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 174, in _run_module_as_main File "~/lineageos/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 72, in _run_code File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 816, in <module> File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 808, in main File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 438, in BuildImage File "~/lineageos/out/host/linux-x86/bin/build_image/build_image.py", line 101, in GetFilesystemCharacteristics File "~/lineageos/out/host/linux-x86/bin/build_image/common.py", line 281, in RunAndCheckOutput common.ExternalError: Failed to run command '['tune2fs', '-l', 'out/target/product/dopinder/unsparse_odm.img']' (exit code 1): ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether out/target/product/dopinder/unsparse_odm.img is mounted. tune2fs 1.45.4 (23-Sep-2019) [ 0% 19/3121] Building Kernel Config make: Entering directory '~/lineageos/kernel/amlogic/linux-4.9' make[1]: Entering directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' GEN ./Makefile KCONFIG_SELINUX((null)) KCONFIG_LOG_SELINUX((null)) KCONFIG_VARIANT(arch/arm64/configs/g12a_variant_defconfig) KCONFIG_DEBUG((null)) # # configuration written to .config # make[1]: Leaving directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' make: Leaving directory '~/lineageos/kernel/amlogic/linux-4.9' make: Entering directory '~/lineageos/kernel/amlogic/linux-4.9' make[1]: Entering directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' GEN ./Makefile scripts/kconfig/conf --savedefconfig=defconfig Kconfig make[1]: Leaving directory '~/lineageos/out/target/product/dopinder/obj/KERNEL_OBJ' make: Leaving directory '~/lineageos/kernel/amlogic/linux-4.9' 17:52:32 ninja failed with: exit status 1 #### failed to build some targets (13 seconds) ####

Can anyone help me understand why this is failing here, and how I can fix and/or circumvent this?

I really don't want gapps on my devices
python issues. looks to me.. but I could be wrong on this matte.r
 

Eliminater74

Recognized Developer
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.
 

vandyman

Senior Member
Jul 30, 2012
824
433
S.Jersey
Google Pixel 5
Google Pixel 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.
I would like to try the script/mod for my own curiosity. I am an intermediate adb-fastboot user. But it will be a great learning experience.

Are you going to create a thread to maintain this mod or post it on Github?

Thanks... 👍
 
  • Like
Reactions: mr.acarlton

Eliminater74

Recognized Developer
I would like to try the script/mod for my own curiosity. I am an intermediate adb-fastboot user. But it will be a great learning experience.

Are you going to create a thread to maintain this mod or post it on Github?

Thanks... 👍
its not really a mod. its just a helper script for the devices listed in thread..
In other words, you download the stock rom that the OP displays link too.
and unzip it, and add the contents to stock_image directory

then run restore_stock_askey_adt3.bat and wait.. it will do everything needed to get your box back to stock, as if you just bought it and took it home.


Another good thing about this, using USB Burn Mode, you pretty much cant brick your device and if you do, you can still restore it. As long as you dont completely flash some messed up bootloader from another device or something.. you can restore it with no problem.. pretty much zero chance of bricking..
 
Last edited:
  • Like
Reactions: vandyman

ROM_gamer987

Senior Member
Aug 8, 2020
88
28
@npjohnson I can't skip setup anymore, i removed setupwraith from product.new.dat and flashed it, still won't work, is there any chance you can add a flag or something in future builds to skip setup?
 

ROM_gamer987

Senior Member
Aug 8, 2020
88
28
@npjohnson I can't skip setup anymore, i removed setupwraith from product.new.dat and flashed it, still won't work, is there any chance you can add a flag or something in future builds to skip setup?
Update: i skipped setup again but now i have 3 new issues, 1: if i try to enable developer mode it says "Developer mode can't be acceded from this user" 2: I Can't install/update anything from the play store it gets stuck on pending (i waited 20 mins) 3: Gboard does not work at all and leanback won't register keypress
 

mr.acarlton

Member
Mar 30, 2011
14
1
OnePlus 8
To anybody that can help .... just got couple of theses ONN Android TV boxes to play around with and see if I can make them work for my needs etc. I'm having issues with the remote if the remote get unpaired or I unpair it (removed a bluetooth and it unpaired both lol). I have to either reset the unit in adb mode or otg keyboard to it and get into settings. The issue is with the second option I dont get the normal remote setup I have to use bluetooth connection settings. Any ideas?
 
  • Like
Reactions: kozmo2k4

Eliminater74

Recognized Developer
To anybody that can help .... just got couple of theses ONN Android TV boxes to play around with and see if I can make them work for my needs etc. I'm having issues with the remote if the remote get unpaired or I unpair it (removed a bluetooth and it unpaired both lol). I have to either reset the unit in adb mode or otg keyboard to it and get into settings. The issue is with the second option I dont get the normal remote setup I have to use bluetooth connection settings. Any ideas?
reset it and start over.. something messed up.....
 

alphaprime07

New member
Jan 22, 2022
1
0
EDIT: Nevermind, i tried yet another USB cable and it worked !

Hello !

I just received my Dynalink (Wade) device and I have troubles accessing ADB/Fast via USB. I tried both from Linux and Windows (different computers) and in both cases, I can only connect to the device with ADB via WIFI (I can reboot in fastboot/recovery mode and then, I'm unable to perform any fastboot command as the device is not detected).
The device doesn't show up with lsusb command (my kernel is up to date). I tried multiple USB ports and usb cables.
Did anyone encounter this issue ?

Here are the devices information from the recovery menu:
Dynalink/sti6130d350/sti6130d3501
10/QT/20210326

And here are the information from the Android "about" menu:
Security update:
5 february 2021

Kernel version:
4.9.180
#1 Fri Mar 26 13:50:33 CST 2021

Build:
PI.PG2-DL-ATV36-WalMart_V2.01.06 user release-keys

If someone has an idea, that would be awesome !
Thanks in advance !
 

Eliminater74

Recognized Developer
EDIT: Nevermind, i tried yet another USB cable and it worked !

Hello !

I just received my Dynalink (Wade) device and I have troubles accessing ADB/Fast via USB. I tried both from Linux and Windows (different computers) and in both cases, I can only connect to the device with ADB via WIFI (I can reboot in fastboot/recovery mode and then, I'm unable to perform any fastboot command as the device is not detected).
The device doesn't show up with lsusb command (my kernel is up to date). I tried multiple USB ports and usb cables.
Did anyone encounter this issue ?

Here are the devices information from the recovery menu:
Dynalink/sti6130d350/sti6130d3501
10/QT/20210326

And here are the information from the Android "about" menu:
Security update:
5 february 2021

Kernel version:
4.9.180
#1 Fri Mar 26 13:50:33 CST 2021

Build:
PI.PG2-DL-ATV36-WalMart_V2.01.06 user release-keys

If someone has an idea, that would be awesome !
Thanks in advance !

yeah make sure you use a USB cable that has full function, pretty much data cable..
the USB cables that come with these devices are only charging cables, they are missing the wires for the data. So make sure you have a USB cable handy .
 

romBuild

New member
Jan 27, 2022
1
0
I have the Dynalink/Wade device and I'm not able to unlock the device. I'm getting an error message unlock_ability is 0, can not unlock I do not see an OEM option under developer options. Is there another way to unlock the device?


xxx:platform localhost$ fastboot devices WUSA2041013029 fastboot xxx:platform localhost$ fastboot flashing unlock FAILED (remote: 'unlock_ability is 0, can not unlock') fastboot: error: Command failed xxx:platform localhost$ fastboot oem unlock OKAY [ 0.009s] Finished. Total time: 0.009s xxx:platform localhost$ fastboot flash recovery recovery.img Sending 'recovery' (24576 KB) OKAY [ 1.308s] Writing 'recovery' FAILED (remote: 'locked device') fastboot: error: Command failed xxx:platform localhost$
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I was somewhat puzzled when occasionally checked this thread I almost gave up and didn't find the familiar mention of a broken OMX in the description, then found this post of yours and... Wow... Looks like a tiny revolution for Android development on Amlogic. How did you manage to do that?
    I missed one line in the kernel cmdline when I first brought these devices up to 12! Lol.

    On 11 it was legitimately broken, but on 12, all I needed was:

    use_uvm=1.

    That was it.
    3
    19.1 on dopinder is broken - rest of devices are fine.

    We know why. We know how to fix it.

    I will fix it as soon as I'm able. Noted in OP it's broken.
    2
    I missed one line in the kernel cmdline when I first brought these devices up to 12! Lol.
    That is so much... like myself 🙃

    Glad I failed to sell my four Onns purchased solely for the sake of LineageOS. Thank you for not dropping this project!
    2
    Yes! It boots to OS (I also observed that slight flicker you talked about). What steps should I follow to get back to factory unlocked? Can I just boot to fastboot from OS now?
    Just follow the usual procedure with the original exploit. Before you do any of that, however, overwrite the incompatible recovery with something that works. If you have root access, you can dd the correct recovery.img before trying anything else.

    You should be able to reboot to bootloader (not fastboot), after which you should be able to fastboot flash recovery with the correct recovery.img (assuming you weren't able to dd as above).
    2
    If you're stuck in a recovery bootloop, it's usually the result of writing an incompatible recovery image to the recovery partition. You will not be able to reboot into fastboot because that's conditional on having a working recovery. If this is your issue, you might be able to escape the bootloop by remapping recovery (temporarily) to boot normally.

    Does the led ever turn white? If it's blinking green, can you print out (via uart) what's going on?

    Try the attached file (overwrite sabrina.bootloader.bin in the original exploit package) and post your results here.
  • 19
    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 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:
    • deadpool - Google ADT-3
    • dopinder - Walmart Onn UHD Box - Broken at the moment - fixing it.
    • sabrina - Chromecast with Google TV
    • wade - Walmart Dynalink 4K Box
    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:
    • SELinux is permissive, this is only due to a lack of time to put together a decent looking sepolicy for these devices.
    • (sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
    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. L1 certificates, and the mechanism that reports is all still exist and work as expected.

    • Can I haz Netflix?

      Yup, but only if your devices stock build supports it.

    • 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. It will likely pass after we finish enforcing SELinux, though.

    • 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
    • bgcngm
    12
    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
    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!
    4
    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