yashsingh1/xdaforums huggingface dataset:
[Google TV General] npjohnson:
Run the flash all.

Super contains system and product etc.
[Google TV General] npjohnson:
They make heavy framework changes we can't make or small changes in dependencies that we can't account for.
[Google TV General] castone123:
edit: fixed the problem by flashing stock recovery then stock zip. Still cannot make my system writable even with magisk install.

I want to thank the people working on the project, keep it up guys.
[Google TV General] hydrocynus:
All, I cannot access the wiki for dopinder: https://wiki.oddsolutions.us/devices/dopinder/

Is there an issue with that built and this is why it is down? Thanks.
[Google TV General] fathergweedo:
Link seems to be offline at the moment. Unsure why. Any particulars you need?
[Google TV General] npjohnson:
Yeah, the power at my house is out, can't do much to help it.
[Google TV General] castone123:
How are you able to copy boot patch to pc? I cannot copy a file or app to sdcard using otg hub or make my pc see the device storage. I can use adb on the pc
[Google TV General] maamdroid:
Lol! Good luck getting power! Checked this and now I know why I can't either. :)

By the way, getting my 4th dopinger on Lineage now. Love it, thanks!
[Google TV General] hydrocynus:
I want to install lineage on my onn tv UHD. I need the up to date files required. Thanks.
[Google TV General] vandyman:
Are you saying that there is no information in the first post?

The links in question are working for me.
[Google TV General] fathergweedo:
I found what I *believe* to be the latest files for dopinder (lineage-18.1-20211118) on my laptop and placed them

here

. I'll leave it there until OP gets power and links are back up.
[Google TV General] npjohnson:
That is not my builds.

Not related to me at all and I know nothing of those.

I'll have my server up sometime tomorrow.

I'm out of town at the moment, even though the power is back on the server didn't auto power on.
[Google TV General] npjohnson:
I'll be turning the sever on tomorrow.

It was powered off due to power loss at my house.
[Google TV General] fathergweedo:
Hmmm... I'm sure that I got these 2 particular files from your link in the OP on December 4th and verified via my browser history. I haven't messed with Lineage on anything else so I cannot phantom where else they could have came from? I did install them that evening and all went well, but I have since restored it to stock for testing. All I did was add 2 checksum files and upped them to my AFH account for temporary access until you're back up. In any event, I restricted access moments ago to avoid any mishaps just in case.

I did see 10 downloads, so to those who got them you may wish to just wait until the OP links are working.

Apologies for any confusion, just trying to be of some help.
[Google TV General] npjohnson:
Oh, you uploaded them, sorry I thought you were downloading some random guys builds, yeah feel free to mirror them!
[Google TV General] fathergweedo:
Glad you replied! After my last post I opened up the zip and found this in the metadata:

post-build=Onn/sti6140d360/sti6140d360:10/QT/20210902:user/release-keys

post-build-incremental=eng.nolenj.20211118.155519

...and THEN I was thoroughly confused - lol.

I restored access for those who are still in need of the dopinder files and can't wait. May be a pita to install without the instructions on your wiki, but whatever ;)
[Google TV General] npjohnson:
site is back up.
[Google TV General] bravovn:
Nevermind, got stucked and fixed by aml update tool
[Google TV General] bravovn:
Anyway to remap App remote button by edit system file? Button mapper works well but at homelauncher it took me 4 seconds to open the app remapped not as fast as open Youtube tv or Netflix by default. Thanks.
[Google TV General] seriousneo:
This worked perfectly for me, it's a magisk module you gotta copy over. After then use the remap app to make the change.

https://xdaforums.com/t/unofficial-...1-family-devices.4313743/page-6#post-85523519
[Google TV General] Big Dumb Object:
Not that fixing the hardware OMX isn't enough of a problem, but do you also consider the Auto Frame Rate and Auto HDR functionality? (Here is a popular variant of the implementation of the first one.)
[Google TV General] npjohnson:
Auto-Frame Rate is an S specific feature, and HDR will probably come along with OMX.
[Google TV General] Big Dumb Object:
Forgive me, but could you define this term, please.
[Google TV General] npjohnson:
Android S specific. Next big version.
[Google TV General] t0ib0i:
I just flashed my Onn TV box to ineage-18.1-20211214-UNOFFICIAL-dopinder.zip but voice search is not working on YouTube. Is there a noob tutorial on how to get root on the stock rom instead? TIA
[Google TV General] npjohnson:
Just use Magisk like you would anywhere else - can probably flash via Lineage Recovery too.
[Google TV General] Levi0630:
This guy is awesome 👍 this worked
[Google TV General] itsfitts:
I have been reading through this thread little by little for about a week now, im sure theres info im about to mention thats already been acknowledged and resolved, so sorry in advance!!

I use tvQuickActions on my ATV's for apps that require a mouse cursor to navigate(Youtube Vanced, Brave Browser, etc..). This app worked on stock Onn UHD box. After switching to lineage the cursor appears and moves around but doesn't actually 'click' anything. Anyone have a clue to this? This app also fails to call Recent Apps activity and Previous App, are these not implemented into the rom or is it just this app failing? I've enabled it in accessibility several times but keeps disabling again somehow? I'm going to try Button Mapper and see if i can narrow it down.

Another issue I noticed since switching, when using Send Files To TV app for sending apks to sideload on the box, sometimes the box appears twice as a destination(same IP though), refuses connection from my phone when I send, or usally just doesn't appear at all. Interestingly, when using the android virtual remote sometimes the box appears twice as well, and neither can be connected to.

Prime video or any major streamer doesn't work so far as I've seen, at least for me, and streaming from other sources video occasionally becomes very choppy as if the system is under heavy load, then evens out for a bit.

I've had an instance of an app installing straight to system app, unable to be opened, idk whats up with that

I regularly use X-plore File Manager which now complains about "no activity to manage some permission to access all files", which i have allowed myself through settings.

Havent figured out programming IR remote to TV yet.

I'm sure there re more bugs to be found, these are all new issues that I've never had/have on stock.

Thanks for the rom though, i appreciate all the effort you put into this before and in the future!!
[Google TV General] Twerkhole:
Got this installed. 👍 everything working great. Except kodi 19 and tivimate playback. Both act the same way. Very choppy playback then video just freezes. Any suggestions to fixing this?
[Google TV General] Eliminater74:
@npjohnson ,

Is this said to still work? I have this very box, along with many others, But commands given to unlock

bootloader will not work. Says unlock ability is 0 meaning, Cant unlock.

can unlock critical but not sure if its truly unlocking it.. all the fastboot oem commands

work regardless of what you put.. but no info comes out just OK..

example you cpould type, fastboot oem killemall and it would say OK..

so all OEM's are triggered but nothing more then that. kinda strange.

there is also no OEM unlock in developer settings.. Now my device is upgraded to latest release.

Guess I should say what device I have, its your "Dynalink 4k" (Wade) above..

I have a few dif devices, Like the TiVo Stream 4k, Jetstream 4k,

all the Amazon Cubes and firesticks 4k, even have the Raspberry pi 4 8gb edition.

I have had other Android boxes, but got rid of them. or broke em. even bricked a few.. beyond repair.

I know all about the ROM Mask Mode. done it many times to a few of my boxes, even had a switch that allowed me to put it into rom mask mode anytime I needed it too.

So I am just wondering if this is said to still work, or did Dynalink cover up the ability to unlock the bootloader anymore. I know its all locked up, because the fastboot getvar all shows it locked.
[Google TV General] :
As of this date, dynalink factory firmware newer than 20210326 may have trouble booting the lineage recovery used to install this lineage release.

Restoring the dynalink device to the 20210326 firmware before attempting to boot the lineage recovery should allow the lineage recovery to boot.

As of this date, no it's not. See here.
[Google TV General] Eliminater74:
I couldnt tell you the firmware version at this time now, I got rid of that device and just picked up the Onn Android TV Box, that by all means seems better anyhow.. even controls TV Vol and power unlike the Dynalink. anyhow.

I didnt get an option to update it just did it on its own.. I did however flashed the firmware factory image that is posted up on this thread.. and it did reset it and it worked, but it auto updated to latest again.

Remind you that, even know I flashed it, it boot looped a few times before going into stock recovery where I had to factory reset it, then it booted just fine.

Also I used USB Burning mode to flash the images with Amlogic Updater tool..

just couldnt get dtb to flash only dtb0............ But still it reset it and flashed..

but yes new firmware stops everything from working......... They always have to ruin a good thing.

So you pretty much need an older edition of Dynalink or at least DC INET before it starts to update..

Which I didnt test that part.. but im assuming if you DC INET before the check and update, you should still be able to log fully into box where you might be able to make the required changes.. But I do know for a fact, that you can flash stock factory image that is listed on this site, and it will reset it.. you will have to get into recovery to reset data and so on.. meaning Factory Reset.

I been working with Android Boxes a long time.. so I pretty much know my way around Amlogic Devices pretty well.. and just a little on Rockchip devices.. and never messed with allwinner and a few others.. Even messing

with a Raspberry Pi-4 8GB Edition.........

Retired from Android Development long ago.. But I love to mess around from time 2 time......

I even work with OpenWRT, creating custom Firmware for the Linksys Router Devices.

But if anyone gets a Dynalink just stop it before it updates and go for the changes their. if its already updated, then just use USB burning mode (hold button plugging in micro USB cable that allows for Data, Do not use cable that it comes with) and run the update.exe command... to flash the factory image that is listed here..

But thanks for the heads up and verification to my claim..
[Google TV General] :
If you were able to restore the factory firmware using usb mode, then the bootloader shouldn't be locked.

I found a version of the Amlogic USB update tool (update.exe) and was able to recover my device to the 20210326 factory firmware. The bootloader is still unlocked, so all is good with this device. I don't know why I had trouble the first time.
[Google TV General] Eliminater74:
I am pretty sure I might be able to create a fully working USB Burn Image from the stock factory firmware that is listed here. Using this here: linux-amlogic-toolkit, Which is

not originally my work, But original developer stopped working on it after android 7 or 8.

I modded it to pick up where they left off. I didnt change the README yet.. so alot that it says it cant do in README is false.. because I made it so it can do that. I also created it to go along side "Superr's Kitchen (Linux Edition)"

also created it to allow signing images and so on depending on command you can extract every single

image from it or just the basic group and ofcorse it can repack the image as well..

I know the layout of USB Burn Tool Images pretty well. bootloader is a u212 board. extracting another u212 image getting the layout and copying all the images, changing them to parsing images which script I created will do.

changing the burn confi files to match. changing the name of a few images..

repacking it, then flashing it with USB burn tool, you pretty much would have stock back on with little to no issues at all. Most know how to use USB Burn tool. few understand the fastboot way..

If anyone is interested, I will put together a working image for that matter.. but only when I have the time.
[Google TV General] npjohnson:
newer firmwares work, but need additional magic. I'll update the wiki soon.
[Google TV General] Eliminater74:
you should create a discord channel or something. your really on to something here, your going to get alot of attention soon. More then your getting now.. maybe creating discord can help with development, many devs and people here that can help make the process better and faster for you..

Not to mention Help people need.. alot dont seem to understand instructions. Having a discord channel can allow others to help the people that need it..

Just a suggestion..
[Google TV General] blaze2051:
does the google tv have GSI support?
[Google TV General] npjohnson:
I appreciate it, but I'll be pushing these official soon enough.

Like I said elsewhere, yes so long as the GSI is small enough.
[Google TV General] Eliminater74:
@npjohnson ,

I gave this a try, bought another ONN Box just to test this.

I use TiViMate Have 2 iptv subscriptions, very choppy video, but I know its not the hardware or video codec.. its

the wifi, for some reason wifi 5ghrz isnt very strong. had a very hard time even signing in and so on.

downloads would take forever. you might wanna take a look into that. alot of the issues I see people complaining about video being choppy, most likely related to wifi signal strenth very low.

Wifi drivers are prob not up to cue..

going to restore stock back on it and make sure that is what I am seeing.. hmm. Looking at my routers clients, the stength isnt so bad.. but whatever is the issue, its related to wifi.

Edit: you may wanna enable wireless debugging so people can connect to their box wireless using abdlink or something else. its a simple build.prop edit to enable it. if I remember right.. 90% of all Android boxes have this

turned on automatically when debugging is turned on. Just a pain in the butt to have to connect PC to it everytime.

For those that want wireless debugging now, but not enabled, just install Wireless ADB from playstore..

must have root.. but im sure if I remember right its a build.prop edit that will allow for it.

I know the guy that does the lineage drops for Raspberry PI 4 has it enabled. maybe check with him.

I love his builds.. I just kinda broke my Raspberry and they are all out of stock everywhere for the 8gb edition.

and not paying 200.00 for one when I can get it for 75.00..

But in all this build is nice. Just gota wait till more bugs are out.. I dont mind testing new builds as they come out.

but without wireless debugging enabled it just makes it hard for me.. extra steps that I dont wanna have to go through each and everytime.. So please enable that for us..
[Google TV General] Big Dumb Object:
Could it be that you found a clue for OMX problem?
[Google TV General] npjohnson:
I have a few ideas to try once home from holidays.

I'm hoping 12 just fixes it, but I bricked my Deadpool hard. So. Limited atm. Lol
[Google TV General] hova1888:
please tell me if there is support afr for onn. box?
[Google TV General] npjohnson:
afr?

Adaptive framerate? No. It doesn't have android 12, nor support it yet.
[Google TV General] abel408:
Is anyone else having problems with Plex not being able to resume/fast forward/rewind media? I just get an infinite loading circle. So odd... This is the only device I have that has this problem.

I'm also having issues with the remote not turning the device on when powered off. I can use the remote to turn the device off, but can't get it to turn back on. The button on the device doesn't seem to turn it back on either. I have to unplug it, then plug it back in. This is for the onn device.
[Google TV General] pieboots:
Not sure if off-topic but these Amlogic SOC's are 64 bit. But the Android rom is running in 32 bit mode meaning only armeabi-v7a apps are supported. Is there a way to enable 64 bit apps for arm64-v8a in the kernel? These would be perfect for a project I am currently developing since I need 50+ arm64-v8a capable devices. Thanks for any help here.
[Google TV General] npjohnson:
Nope. Our GPU blobs don't like 64-bit mode, sadly. Recovery boots tho.
[Google TV General] Eliminater74:
your best bet is, either buy a true 64bit Rom Android TV Box or get a Raspberry PI-4 and install Lineage Android TV on that.. they have all the way up to android 11 for android tv and 12 for tablet mode tv.. all running on 64bit..
[Google TV General] pieboots:
Thanks for the tip, I am currently running a few pi 4's with lineage but they all keep freezing after a while, so it's not too reliable. Also hard to get more pi's right now anyway. Frustrating.
[Google TV General] Bassmaster_lvn:
Hello. My Dynalink only boots to the Amlogic flash mode which only the USB Burning Tool can use. Can it be restored? The device is defined as a WorldCup Device. USB_Burning_Tool also defines. Please help to restore.
[Google TV General] Eliminater74:
where there is a will, there is a way.. download the firmware said in topic.. for your device.

flash it from update mode.. if you dont have the command update.exe mode, I will upload a copy and all you have to do is add the images you downloaded into the images directory and click the restare.bat file and wait..

I personally custom a script that will auto flash everything back as if it was first bought.. that might help you..

just let me know.

EDIT: OOPSIE: I mean the stock firmware.. Download that for your device.. Not the Lineage ones..

you can do the lineage ones after you restore your device..
[Google TV General] npjohnson:
We just include GApps at the moment to simplify things.

When this goes official, you'll have the option of either.
[Google TV General] npjohnson:
After a brief intermission, all builds are posted again, and boot. Enjoy.
[Google TV General] criscodecookies:
I see flashing dtb/dtbo was removed from install guide.

Skipping that part I still can't get it to flash correctly, this is my command log:

adb reboot fastboot
fastboot flash recovery lineage-18.1-20210805-recovery-dopinder.img
target reported max download size of 536870912 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 0.540s]
finished. total time: 1.658s
fastboot reboot
adb reboot sideload
adb sideload lineage-18.1-20210805-UNOFFICIAL-dopinder.zip
serving: 'lineage-18.1-20210805-UNOFFICIAL-dopinder.zip' (~47%) * failed to read command: No error

Device shows this after sideload:

Verifying update package..
E:failed to verify whole-file signature
Update package verification took 303.7 s (result 1).
E:Signature verification failed
E:error: 21

Install from ADB complete (status: 2).

Is it possible that rebooting to system after flashing recovery restores the stock recovery?

Also unable to Enter recovery directly from fastboot with any combination of OTG+hub/keyboard, as if it's not a direct micro USB to USB A cable my PC won't detect the device for sideload, not sure how others are able to.
[Google TV General] Juppy99:
got this same issue, sadly i dont have an OTG cable to hook up a keyboard.
[Google TV General] npjohnson:
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.
[Google TV General] criscodecookies:
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:

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!
[Google TV General] npjohnson:
aight, will update instructions.
[Google TV General] kenicenoel:
I think I bricked mine. It's stuck on the Android TV logo after flashing the dtb and dtbo file yesterday
[Google TV General] criscodecookies:
The virtual keyboard doesn't work/open at all for me, so during setup I ran the following commands to enter WiFi pass/email etc.

adb shell input text "TEXT"
# press enter/continue
adb shell input keyevent 66

Attached a logcat of when an input field is focused.

Casting doesn't seem to work, redacted client ID's with 'XXXXXXXXX': https://pastebin.com/PMyWZTvH (couldn't get it to attach)

Also couldn't get sound to work.
[Google TV General] criscodecookies:
Follow this procedure https://xdaforums.com/t/unofficial-...-g12-sm1-family-devices.4313743/post-85425773
[Google TV General] npjohnson:
you know what's funny, I hit that to, try not connecting ADB/computer? See if it makes keyboard pop up.

Casting is known to be broken on dopinder atm. Need to work through this further. I'm just so limited on time.
[Google TV General] criscodecookies:
Wasn't sure if these were known issues already, and this isn't my daily driver so take your time!

Tried plugging into the stock power cable didn't fix the keyboard issue.

The sound issue I think is something to do with the internal volume.

The only way I got the sound to work is by accident while installing Android TV Infrared Service (com.google.android.tv.axel) and running the setup via adb shell am start -n com.google.android.tv.axel/.ui.wizard.OobeActivity then sound works after.

The IR/app also works, do you know if it will be included (in settings) in future releases?
[Google TV General] npjohnson:
yes it will.

and, did you try turning the volume up on the remote?

Makes me think it was stuck in IR or CEC mode... which is weird.
[Google TV General] criscodecookies:
Yup tried Vol up/down, Mute buttons on the remote, even tried sending the input keycodes via adb (24 and 91), nothing.

It's not muted because I can see in logs that it's toggling mute correctly but it's throwing a warning with it that the current volume level is 0, and min=1. Nothing in the logs when Vol up/down is pressed except TelcomManager is missing.

Edit: You were right about CEC, disabling CEC entirely (Connected devices -> HDMI-CEC) fixes the sound/volume button issue, however this means it's not respecting the option under Device preferences -> Inputs -> CEC Volume Control as it was disabled and is by default.

Also got the virtual keyboard working somehow, the only things I did were uninstall Gboard updates, clear data, and disable/enable Android TV Remote Services then reboot.
[Google TV General] alan_harake:
Few things I've noticed after installation and using the rom. There is no option to setup the remote to the tv for IR. So I have no volume control or input and power is controlled by cec instead of IR. On screen keyboard doesn't work on any apps. Settings button on the onn remote doesn't work. YouTube playback is broken. Only plays for half a second then freezes. And holding the home button is binded to opening assistant instead of going to the apps menu like it should. Would also be nice to see the Google tv ui be ported.
[Google TV General] meber:
I'm not sure what I am doing wrong. Whenever I try to do an adb reboot bootloader it restarts but then just sits at the ONN logo and never progresses.

Even if I connect the original power supply and hold down the side button while booting to bring up the Android menu and select Reboot Bootloader it gets stuck at the ONN logo.

Any help?