yashsingh1/xdaforums huggingface dataset:
[Google TV General] criscodecookies:
Bootloader is supposed to only show the logo and fastboot commands should still work if it's connected to your PC.
[Google TV General] meber:
When I do fastboot devices it never appears. Maybe I'll try a different computer.
[Google TV General] meber:
So for an update to fix it I had to manually assign the driver. I selected the unrecognized device and clicked update driver, clicked browser local system, selected universal serial device and then selected ADB. From that point on it worked.
[Google TV General] fixsony:
I can't flash back to stock rom, get some error

>fastboot flash super super.img

target reported max download size of 134217728 bytes

Invalid sparse file format at header magi
[Google TV General] Bassmaster_lvn:
OK, the standard firmware has already been downloaded. Update.exe returns an error.
[Google TV General] :
How did your device fail? Was it after installing this lineage release?

What are you using for "standard firmware". Is it the files within wade-qt.20210326-factory.zip, or another source?

I did this not too long ago, but I didn't keep any notes. I vaguely remember using commands like the following (using the files from wade-qt.20210326-factory.zip):

update mwrite dtb.img mem dtb normal
update partition _aml_dtb dtb.img
update bulkcmd "disk_initial 0"
update partition dtbo dtbo.img
update partition recovery recovery.img
update partition super super.img
update partition vbmeta vbmeta.img

I think I got an rb error for boot.img and bootloader.img, but the existing partitions must have been okay, or else I was able to use fastboot by then to flash those partitions. Note that I hadn't used update before, so I was unfamiliar with its usage.
[Google TV General] Bassmaster_lvn:
Yes, I use wade-qt.20210326-factory.zip . Most likely I accidentally started flashing the firmware from adt-3 ((
[Google TV General] Eliminater74:
I have the TiVo Stream 4k as well. and I flashed that so called user debug build.. problem is this, when you

goto setting it up so you can turn debugging on, it updates it self then locks everything down again.

So I never had a chance to really test it.. but I will say, the TiVo is fast with that DDR4..

I think I have way to many Android TV Boxes.. I retired from Development on Phones and got bored, so moved into Android TV Boxes as well as Routers.. Plus Love using TiViMate for my TV Viewing Pressures.. :P
[Google TV General] :
Usb debugging and root are already on in the userdebug build. So, if you have usb connected, you can open settings via the adb shell before you setup a wifi connection during the initial setup wizard:

adb shell am start -a android.settings.SETTINGS

And then following a process similar to this one from earlier in this thread, the ota update can be bypassed. At least for a while anyway.

What I was wondering in my prior post though is whether or not the unlock obtained (by flashing the userdebug build) could be used for an alternative build like the lineage release that is the subject of this thread?
[Google TV General] xam1988:
Hi, I have the same problem whis onn ((

Only this:

G12A:BL:0253b8:61aa2d;FEAT:F2F939B2:32060;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:20000;USB:8;

If you can help, plese
[Google TV General] Eliminater74:
ill try again when I get time.. I know I have built bootloaders in the past for other amlogic devices.. and yes they worked.. compiling a bootloader is so confusing too.. but once you get the hng of it. its pretty easy. asuming I can get done what you said.. if I can find the bootloader board code for that device.. maybe change out the bootloader.. but as far as I know, even with that userdebug edition, the bootloader is still locked and cant overwrite it.. but ill look into it once again soon.. just done have the time right now.

Edit, the lock and unlock is handled by the bootloader, and even with that userdebug edition, you have to uncheck the erase bootloader and flash.. yes have password.bin file. but it wont allow overwriting bootloader.

I htink the only dif is, userdebug is not signed privet and might be sighed with public test keys. making it

east to test things. I guess. as I said.. when I boot it would download update.. ill bypass INET connection and see what I can do. with it.
[Google TV General] :
When you say "the bootloader is still locked and cant overwrite it", do you mean uboot (the bootloader board code in ddr_enc.usb)? Which is distinct from "unlocking the bootloader" with fastboot commands in order to allow flashing?

If erase bootloader and flash are not unchecked, USB mode changes to GX-CHIP (from worldcup) and then USB burn mode access is lost, at least with the included password.bin. What causes this to happen? Something must be overwritten, what is it?

If the change from worldcup to GX-CHIP is because "the bootloader board" code is overwritten (when those two tool options are not unchecked), then the secure image must contain new bootloader board code, correct?

Do you remember offhand in which version of the firmware they disabled oem unlock (unlocking the bootloader to allow flashing)? Do you have a copy of the firmware for the last version that allowed this?
[Google TV General] Big Dumb Object:
Today I discovered a new tool for root-less AFR activation and some other useful tasks, perhaps it will interest you. It's called tvQuickActions.
[Google TV General] :
You paid the $1.99 for it?
[Google TV General] Big Dumb Object:
No, since my Onn's are in unwrapped boxes waiting for this ROM to be finished (not a very risky investment, because cheap).

If you want to try the app without buying, you can get it from Mobilism for free. Hope I'm not violating the rules by this mentioning.
[Google TV General] Big Dumb Object:
And I would like to annoy you again with another noobish question (sorry): are any of these boxes equipped with HDMI surge protection? I have heard that the HDMI ports of cheap set-top boxes sometimes die because of the economy on extra diodes, and that the third-party solutions do not quite protect against this.
[Google TV General] npjohnson:
I don't think so?
[Google TV General] Eliminater74:
I will have to look into this later on, DOnt know off hand. I been busy working on a TWRP for this ONN Device.

which I have working for the most part.. Just cant get system and vendor to mount.

but everything else mounts. I know system is dm-2 as well as dm-4 and vendor is dm-3 as well as dm-5

but will not mount no matter what I do. so i been racking my brain trying to figure that out.

and Just so we dont hijack this mans thread, just send me PM aka DM, on here or telegram, same username on telegram.. because I truly think we are just a bit off main subject here. Other then if we can get TiVo Stream 4k unlocked, then I am pretty sure we could get lineage on that too.. there isnt to much of a dif between s905x2 and s905y2 the y2 mainly used for small set boxes. But truth, that TiVo DDR4 RAM is fricken fast... for a cheap Box, that thing is super fast.. but the current software that is comes with isnt well designed. alot of funtions have been crippled..
[Google TV General] :
I will end my extraneous blather right here.
[Google TV General] Big Dumb Object:
So, it's probably not the best idea to hot-plug HDMI cable when the box is powered...
[Google TV General] npjohnson:
Meh, it's a low chance.
[Google TV General] mr.acarlton:
i get the same
[Google TV General] Erv349:
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!
[Google TV General] Erv349:
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.
[Google TV General] Eliminater74:
when you boot, you will see the lineage boot gfx, not the ONN gfx. that is how you will know your in Lineage..
[Google TV General] Eliminater74:
python issues. looks to me.. but I could be wrong on this matte.r
[Google TV General] mr.acarlton:
Hardware backed OMX fixed yet?
[Google TV General] Big Dumb Object:
I don't think anything might have changed radically in just two weeks.
[Google TV General] mr.acarlton:
I thought this thread was a year old?
[Google TV General] Big Dumb Object:
Of course, I was referring to the author's last response on this subject. As for the OMX challenge itself, it is much more than one year old. Keep my fingers crossed for npjohnson and all who are involved in its overcoming.
[Google TV General] mr.acarlton:
agree these are great little boxes

There's on rollback right now too YMMV
[Google TV General] Eliminater74:
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.
[Google TV General] vandyman:
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... 👍
[Google TV General] Eliminater74:
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..
[Google TV General] ROM_gamer987:
@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?
[Google TV General] ROM_gamer987:
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
[Google TV General] mr.acarlton:
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?
[Google TV General] Eliminater74:
reset it and start over.. something messed up.....
[Google TV General] alphaprime07:
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 !
[Google TV General] Eliminater74:
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 .
[Google TV General] romBuild:
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$
[Google TV General] symbiiote:
{Deleted}
[Google TV General] Eliminater74:
I have had many people sending me messages asking for this scrip, I never heard back from @npjohnson as to the okey to posting this, so I will just post this, if he has an issue, I will delete it.. for now here is the zip..

I am not one to write instructions and so on. I only wrote a quick one. Please be smart and view the bat file before you run it. Never just take anyones word for it.. View the files before you run them.

This is not a quick fix everything for you peepz, its only to allow going back in forth a bit easier on you.

if you have no clue what worldcup or should I say USB Burn mode is, then this is prob not for you.

matter of fact I would say the whole project would prob be a bit to advanced for you.

I am sorta moving on from this, bought a Khadas Vim 3 Pro board. Which Google fully supports, and I am going to tinker with that, the Raspberry PI 4 just bored me. But I am willing to help here if I can.

Hope all continues to go well for the OP.. Its people like him that you all have options like this.

Take care..
[Google TV General] Jerky_san:
Script fixed my boot loop problems! Thanks ^_^
[Google TV General] :
Thanks! It's too bad that usb burning mode is increasingly being disabled in new model devices. The askey ASK-STI6220 (S905X4) doesn't have it. The uboot menu is missing "update - Enter v2 usbburning mode". They've replaced it with a distinct version of fastboot (different than bootloader fastboot and fastbootd). Even masking the rom brings up only this mini version of fastboot. And it is no where near as capable as usb burning mode.
[Google TV General] Eliminater74:
get your self a Khadas VIM3 Basic/Pro if you wanna play around with all that.. Google's source code officially supports it. I have already built 4 roms with only uses googles source.. but tell you the truth, I think that same device tree can be modified to work for other amlogic g12 boards..

BTW: dif beterrn the Basic and Pro are 2/16 and 4/32 both DDR4 Ram..

Not trying to Hijack thread.. because I just think with the release of all that as well with this could make something work better.
[Google TV General] ojai0217:
Hi guys, I'm trying to build for the dopinder myself. After couple tweaks (e.g. fixing some paths of proprietary blobs), I got the final zip built without any failures. However, the installation of the new zip via recovery is failing with the following error:

assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))

What I noticed that the size of the zip I built is almost half size of the original working version. (390MB vs 690M). Comparing side by side on the contents of zips, I see that my build is missing 'bootloader.img' and the huge difference on the size of 'product.new.data.br' (60MB vs 337MB).

I believe that I've followed all the steps according to this. Any hints or advices?

Another question: How do I get a write access on /sys/devices/virtual/? I'm trying to create some files especially under android_usb to enable accessory mode for dopinder. Even magisk's su wont' give me enough permission. It seems to be something with dm-verity which I might need to disable by building the rom myself?
[Google TV General] npjohnson:
prop files should need no updates - you need to extract them from the deadpool r build, or an existing lineageos build, preferably existing lineageos build.

It's half the size because I build GApps in ;p you won't have that.

Bootloader.img just needs to be the same one from in the lineage package I give out, so as long as you flash that once, you're fine.

as for files on /sys - uh, that's not normally something one does? They should be made by init or the kernel.
[Google TV General] ojai0217:
Thanks. So, my build is OK, and I need to figure out why it doesn't get installed somehow...

For prop files, I used the onn device running the latest lineage to extract those. However, the following files were unable to be extracted.

!! odm/etc/firmware/firmware.le: file not found in source
!! odm/usr/idc/Vendor_000d_Product_3838.idc: file not found in source
!! odm/usr/idc/Vendor_000d_Product_3839.idc: file not found in source
!! odm/usr/keylayout/Vendor_000d_Product_3838.kl: file not found in source
!! odm/usr/keylayout/Vendor_000d_Product_3839.kl: file not found in source
!! odm/usr/keylayout/Vendor_7545_Product_0021.kl: file not found in source

!! system/etc/audio_effects.conf: file not found in source
!! system/etc/permissions/privapp-permissions-atv-lineage.xml: file not found in source
!! system/etc/permissions/privapp-permissions-google-lineage.xml: file not found in source
!! system/lib/hw/screen_source.amlogic.so: file not found in source
!! system/lib/libmediahal_resman.system.so: file not found in source
!! system/lib/libmediahal_tsplayer.system.so: file not found in source
!! system/lib/libmediahal_videodec.system.so: file not found in source

The problem is that the extract util is appending /system prefix to those paths, and found out that there is no symbolic link for odm under /system in the device. Obviously, it also tries to look for /system/system/... which is invalid path.

BTW, for /sys to access usb driver, as per your comment, I sort of expected to be tweaking init and kernel anyway once I got the good-to-go builds.
[Google TV General] npjohnson:
Yeah you can't extract from a running build, I need to fix that guide, you need to extract it from a pre-built zip
[Google TV General] glenb77:
Thanks for developing this. On an onn. I managed to get the rom installed, but had many problems, the adb kept dropping out after different steps in the wiki. The bootloader did unlock though and the box had updated prior. Running the rom i had several issues and reverted to stock. I had no issue just going step by step from the flash-all.sh. i am in linux and needed those commands one by one and the commands prefaced by 'sudo'. I don't use the name apps, netflix etc. my main use is for mythtv as 'frontend'. most of the content is mpeg2 interlaced (over the air broadcasts), and the deinterlacing was really bad. on the stock it's perfect. so i thought i'd let you know. also at points the rom was sluggish in responding to input. Thank you for you efforts, I hope to be able to try again soon!
[Google TV General] BlacKn1ght:
In the process of trying to update to a new system and recovery build, I think my dopinder is stuck at the bootloader screen (androidtv logo)? Is there any way that I can put it back in a flashable state? fastboot and adb both don't see any device, and I don't know which amlogic tool to use, if any. I'm on linux, but I also have windows.
[Google TV General] Big Dumb Object:
It seems that after another month, the last hope for fixing OMX is Android 12, isn't it? Haven't you experimented with it already? (Asking just because unofficial LOS19 builds are starting to appear all around.)
[Google TV General] npjohnson:
Yeah I already have 12 booting, OMX is still dead :(
[Google TV General] Big Dumb Object:
What a pain... Are there any positive perspectives left?
[Google TV General] npjohnson:
At the moment not really
[Google TV General] Big Dumb Object:
Maybe there is some not-so-elegant way, that although will shut the door to official status, but in return will make things work as they should? I think, a multimedia device without hardware codecs is like a car without seats - it rides of course, but who cares...
[Google TV General] npjohnson:
There's not even a non-elegant way, we have no clue why it doesn't work
[Google TV General] BlacKn1ght:
Anyone have any suggestions for this? I know it's not bricked at the very least 😅
[Google TV General] Big Dumb Object:
And even in the "heavy framework changes [...] or small changes in dependencies" we cannot look for any vague hope? That time you said it with the goal of the future official release in mind, but today's situation seems different.
[Google TV General] npjohnson:
From my side, no, I have nothing left to try sadly.

Will still release 12 builds very soon
[Google TV General] BlacKn1ght:
Is there some specific driver that I need? Windows isn't detecting it at all anymore, and there's no boot logo from HDMI either.
[Google TV General] tenfox:
Thank you very much for this project.

I have 18.1-20220112 successfully running on dopinder. FYI I was unable to get 19.0-20220114 recovery to boot (black screen, no adb, fastboot reports device:"?????????") and didn't risk flashing 19.0-20220114 main rom.

Please post a GApps-free or tablet build if you have the time. I would love to use these boxes for fun things without logging into a Google account.

Thanks again!
[Google TV General] npjohnson:
19.0 is not ready. Testing.

Also Gapps free, meh. Maybe at some point.