yashsingh1/xdaforums huggingface dataset:
[Google TV General] retyre:
On the Onn device (and probably all the non-sabrina devices), there's no need to go through initial setup, forced update, and turn on dev options and USB debugging to update to LineageOS. Connecting to a Linux box while holding the side button down will put the device in burn mode. Once can then run ./update bulkcmd fastboot ("update" is the Amlogic update tool from the sabrina unlock thread: https://github.com/npjohnson/sabrina-unlock) to boot into fastboot. From there, fastboot flashing unlock will unlock the bootloader and then fastboot boot lineage_recovery.img and install LineageOS.

BTW, holding down the side button and connecting the device to power (non-PC) will boot the device into recovery mode. Useful if the device refuses to boot.
[Google TV General] KeepingItCuttingEdge:
I've had the nVidia Shield 2019 for almost 2 years now, but I'm new to this hardward and considering purchasing one. From reading the OP, I see that each unit's hardware varies slightly.

Do any of these all handle HDR10/HDR10+ and Dolby Vision/Atmos with LOS 18.1?

I'd have to buy the ADT-3 it seems to test Google Dev's Android 12 beta.

Android 13 for TV | Android Developers

developer.android.com

Or should I just get another Shield and be done with it and hope they update from Android 9 to 12 soon? Haha

THANKS in advance.
[Google TV General] npjohnson:
The CCwGTV will get official support at some point yes.

Yup.

11 is coming to shield very soon.

You should grab an onn or dynalink box tho! Adt-3 isn't Netflix certified and such.

None of them support HDR on lineage yet but it is on the Todo!
[Google TV General] seriousneo:
Hey so does this mean I don't need OTG cable for my Onn 4k box then? I can do all of this with just connection to my laptop + adb?
[Google TV General] npjohnson:
Yeah, I'll update the wiki soonish
[Google TV General] nefescalanadam:
is there any chance for Xiaomi mi box s 4k?
[Google TV General] fathergweedo:
Encountered the same issue here, read on...

He/she is correct, I wasn't able to actually toggle USB debugging until connecting to WiFi "and" logging into Google and accepting terms. Seems odd, but in several (>6 times) I had the same results. I have no idea how accepting the Google terms could affect this, but it is what it is. Biggest problem "could be" is upon connecting it to the internet, it automatically updates. Luckily the update to 09/02/2021 doesn't foil bootloader unlocking.

I received 2 of these yesterday and this happened to the 1st one. I searched for this issue everywhere and I only came upon this remark today. Thinking I may have a bad one, I tried the 2nd one today without ever connecting to WiFi. Went directly to settings/Device Preferences, and tapped the build number per normal. Went back to Developer Options and encountered the same "Developer options are not available for this user" message.

Not really a deal breaker as you can get to stock recovery by holding the side button while applying power and get to fastboot from there. Just need a hub and proper setup to unlock the bootloader via connected computer from there, I assume?

I don't want to plug my Linux box into a powered hub as I'm not sure of it. I'm awaiting a pair of OTG cables to actually complete this setup tomorrow, but from an earlier post here, I should be fine.

EDIT: Onn. "#2" is reset to OOB state and never connected to WiFi, so I still have a pure stock/reset one to play with if anyone wishes any testing from here. Other than protecting my Linux box, I'm game. It's not like bricking an expensive phone - LOL!
[Google TV General] fathergweedo:
Wow. I just looked at my history and I've been MIA here for over 18 months?? Time sure flies! May have to get up to speed a bit. The latest android version on my phones is Nougat/Oreo - o_O
[Google TV General] npjohnson:
Yeah, that's kind of expected almost every device nowadays requires you to log in and setup before unlocking bootloader's.

I thought the last guy was talking about on lineage lol
[Google TV General] fathergweedo:
I haven't even tried lineage as of yet, but this was my 1st encounter of having to loginin/setup to access debugging. Guess I'll find out tomorrow if it's really necessary when booting directly to the stock recovery > booloader. Fingers crossed ;)

EDIT: I'm quite rusty and behind the times of late. All I've managed so far is to unlock/verify unlocked the bootloaader on the Onn/dopinder #1 and boot (not yet flash) the (lineage-18.1-20211007-recovery-dopinder.img) recovery. Still have to tweak in my setup before I have the "warm fuzzy" necessary to play around.
[Google TV General] npjohnson:
It's not necessary at all, you can boot into bootloader mode and just issue the command
[Google TV General] fathergweedo:
Pretty much figured that's enough, but the USB port on the Linux box doesn't have enough output to power the dopinger + USB keyboard that I wish to navigate with. The (quite old) " HooToo 40W/7.8A USB Travel Charger" that I have connected has a pair of OTG ports, but I'm not sure exactly how it works (who keeps manuals/instructions?). For current setup I just have OTG-1 of the "hub" to the dopinger and OTG-2 for the keyboard. It powers those up fine, but I still need a means to connect it to the computer. Awaiting a cable to safely complete the circuit (unless I'm just being a puss???) -LOL
[Google TV General] HawaiiWarrior:
I bought the ONN box from Walmart this past weekend to try and get Lineage OS running. There were a handful of updates that installed on my first login.

Now, when I run the "adb reboot bootloader" command in ADB after enabling USB Debugging, the command appears to work but then the ONN bootscreen appears frozen on the connected tv. At the same time, I don't see the device when I run the "fastboot devices" command, and if I try to "fastboot reboot" command it hangs on the "waiting for any device >" message.

I also see a "USB download gadget" under the Windows 10 Device Manager screen after running the ADB command while I am unsuccessfully trying to run the Fastboot command.

I'm wondering if I might have missed a step to install ONN drivers, or whether the OTA updates may have broken the "adb reboot bootloader" method.

If anybody has a troubleshooting idea, I'd be happy to give it a try and confirm what does/doesn't work.

---

Update to add screenshots:

Windows 10 Device Manager "USB download gadget":

ADB command errors (adb successful, fastboot unsuccessful):

ONN device version after updating on 10/16/2021:

Bootscreen stuck after "adb reboot bootloader" command:
[Google TV General] retyre:
The device is in fastboot mode; your PC is not configured to detect it. You haven't installed fastboot drivers in Windows (https://developer.android.com/studio/run/win-usb), so it's no wonder the device is not being recognized.

Given how easy it is to boot Linux from a flash drive, it's pretty much an expectation on here that you try this in Linux and not in Windows.
[Google TV General] npjohnson:
Windows works fine. Just install the drivers like the wiki details.
[Google TV General] CrazyHairGuy:
I'm not too well versed in this kinda stuff, but would it be possible to install the "regular" phone/tablet version of google play and install non-TV apps with this ROM? I tried editing the build.prop, but it still throws an error whenever I try to open the sideloaded phone app. Is it inherent to the OS itself?

--edit--

Is OTG disabled/is there a documented issue with OTG on this ROM? I have a squid-like cable that supplies power and also passes through three USB ports, and it worked with the stock firmware - but as soon as I flashed this image it seems to do absolutely nothing but pass power. Could it be exclusive to the onn. box?
[Google TV General] HawaiiWarrior:
Thanks for the feedback, @retyre. I tend to flash Android device ROMs only once every year or so, and when I do I usually end up failing with Windows and using Linux; I just really didn't feel like flashing a device or spinning up a virtual machine and getting USB devices functioning. I'll probably end up coming up with a more permanent Linux situation if I try a project like this again. However, I can confirm I was able to get the process working with the Windows driver.

Here's a screenshot showing the driver I was able to update in case anyone else was having a similar issue:

Just like @npjohnson recommended, all I had to do was select "Update Driver..." and point to this folder for the unknown device (it turns out I had already downloaded these too, I just didn't realize I could/should use these for the issue I was having):

Also, the commands that @criscodecookies posted on Aug. 5 were very useful as I didn't have an OTG host cable available. Without those commands, I would've been stuck not knowing when to flash recovery, the ROM itself, reboot, etc.

Thank you all for helping me get this working.
[Google TV General] tramtrist:
It appears youtubetv crashes when starting a video. Is this a DRM/widevine error or something? Pretty sad to go back to stock.
[Google TV General] joebruin:
I got LineageOS loaded on my ONN device and I guess I was a little disappointed that it still required me to log into Google to get into the home page. Is there a way to load a default customer launcher (even Kodi) so that I can log out of Google?
[Google TV General] kennkanniff:
Are these commits still needed?
[Google TV General] npjohnson:
Yes
[Google TV General] v12xke:
Greetings, I've been flashing Nexus/Android phones for a long time but this (dopinder) gadget has got me a 'lil stumped. Unlocked, installed recovery, factory reset, wiped cache ALL OK, and then stuck on adb sideloading LOS. Initiating an update from ADB via recovery, cannot get past 50% before it aborts. File hash matches, I've tried 3 data cables, multiple USB ports on my rig that has no fastboot/adb issues with any other device. Binaries are up to date. Any suggestions would be welcomed.
[Google TV General] techdeisel:
works fine for me just doesnt add live tile or autosign me in like my CCWGTV, only found netflix an disneyplus dont work for me
[Google TV General] meber:
Mine does the same. It opens and then like 3 seconds later it crashes.
[Google TV General] UnionBlvd:
Surprised no one else replied, but I'm having the same problem on a Dynalink box. OTG cable went completely useless after installing Lineage.
[Google TV General] kennkanniff:
If I build with MicroG baked in I get a black screen after setup. I can't check logs because I can't enable ADB. Any thoughts?
[Google TV General] npjohnson:
Yeah, microg doesn't have any handling set up for ATV GMS which is totally different.
[Google TV General] npjohnson:
Th

This is fixed. Next build will do it.
[Google TV General] v12xke:
Is the wiki down temp for maintenance or down hard?
[Google TV General] npjohnson:
maintenance.
[Google TV General] npjohnson:
Wiki is back up.
[Google TV General] v12xke:
Will a wireless keyboard work with the dopinder box now or is this even possible for the future? I have an old logitech wireless one with a built in mouse pad. Or maybe something like THIS Rii mini that supports both wifi and bt.
[Google TV General] HiJacK69:
I installed lineageos on my ONN box, but didn't like the results. I was having playback issues in 60 fps video formats. I flashed the factory image back and installed magisk. I have everything set up the way I like but. I spent so many hrs tinkering with it.

Is there a way to backup my ONN image? I'm used to using twrp. I checked the recovery options, but don't see an option to create a backup image. If this is possible, I plan to pick up a few more ONN boxes and just flashing my backup image onto the other boxes.

Thanks!
[Google TV General] Nasty64:
Looks like the wiki is down...
[Google TV General] fathergweedo:
May I ask what version of Magisk you used and any steps required for root on the stock OS? Meaning, can you patch the boot image from within, or patch a copy from elsewhere to flash via fastboot afterward? Sory to have no input of late in this thread, but RL comes first ;)

BTW, I still have a virgin (dopinder) device to play with if anyone has anything they want me to try.
[Google TV General] fathergweedo:
Assuming you have root, you should be able to pull each partition in an adb shell. Sorry I don't recall the commands. I would likely have to dig up some VERY old notes (that maybe gone), or do some serious searching here on other threads.
[Google TV General] npjohnson:
Yeah, from in Android. Worked fine before.

It's back, brief reboot.

Flash it via recovery, or just patch the boot image like their wiki details.
[Google TV General] dealercohagen:
Can someone please help me to flash stock OS on Onn box, I tried a few times but it keeps giving a error, signature verification failed error 21 and failed to find update binary META-INF/com/google/android/update-binary, not sure what am I doing wrong.

I downloaded the stock image form here, https://download.ods.ninja/Android/firmware/dopinder/.
[Google TV General] emveepee:
Installed fine on ONN but ExoPlayer reports it doesn't support mpeg2video so something is different from stock. Is this expected, I've done multiple installs with the same results.
[Google TV General] npjohnson:
"hardware backed OMX is broken" - the OP
[Google TV General] npjohnson:
That doesn't get flashed in recovery... its a factory image. Flash it using the flash-all.sh script.
[Google TV General] dealercohagen:
Oh I don't know, I flashed it using the flash-all sh script and worked, thank you.
[Google TV General] HiJacK69:
I used version 23.0, which I grabbed from the developer's website. In regards to the steps, I just did a search in the forum for "magisk", and I believe it was the 2 or 3 result from the top. Someone had posted step-by-step instructions. Just remember to unlock the bootloader first.
[Google TV General] HiJacK69:
I managed to find a version of TWRP from another forum. I haven't tried it yet, but it's for the S905Y2 chipset. I'm hoping it works, so I can make a backup. I also found some old posts for backing up nandroid for phones, but haven't tried it yet.
[Google TV General] emveepee:
Thanks I was reading that only DRM was broken. My mistake.
[Google TV General] hp420:
that rii remote is a complete piece of trash. i owned one. this one works great with dopinder, but it won't work in recovery.

https://www.amazon.com/dp/B01CL3ZXGO/ref=cm_sw_r_apan_glt_fabc_H6QVNXNEV8XHNJATZQ0V
[Google TV General] fixsony:
I don't want to look annoying, but I still haven't been able to revive my TV box. I changed the usb cable, changed computers and the result is the same. With a successful flashing, my TV box either gets into a cyclic restart or gets stuck in a constant load (colored figures spin and move). What am I doing wrong, have any ideas? Thanks.
[Google TV General] v12xke:
You don't mention whether this is your first LOS install or you have had it working before?

My stumbling block was not fastboot booting recovery after flashing it. I thought the adb install was successful but it wasn't .

If you already had LOS up and running fine before until SHTF then just reflash back to stock and start fresh using THIS from an earlier post
[Google TV General] fixsony:
Try this way and now non stop booting LineageOS logo going
[Google TV General] npjohnson:
Gonna bet you didn't format data like the wiki says to?
[Google TV General] fixsony:
So far I now two way, one is fastboot -w and second from recovery. This is right way?
[Google TV General] npjohnson:
Recovery - but you didn't follow the wiki, so, you should do that next time to save head-ache.

But yeah for now just boot to recovery and wipe userdata "factory reset".
[Google TV General] fixsony:
I did so many times, no luck.
[Google TV General] npjohnson:
Weird, I'll look at the newest build.
[Google TV General] tokoam:
There is a new build the wiki shows last update was on the 7th of this month btw Happy Halloween .
[Google TV General] npjohnson:
the 7th is the newest.
[Google TV General] fixsony:
No any ideas to get fix device?
[Google TV General] v12xke:
1. Read the advice given to you before to flash the stock OS and try again. Did you read that?

2. Link to the zipfile with everything you need to flash back to stock is given in the Wiki.

3. Follow the code in THIS thread.

This is exactly what was suggested to you last week.
[Google TV General] fixsony:
I did all this more than once and everything went well without any errors. Based on all your prompts and instructions, everything went well except my box does not start successfully. Thanks again for your help, but it looks like the TV box can be thrown away.
[Google TV General] v12xke:
Ah, so you reflashed your box to stock? It sounds like you never made it there and THAT is your current issue. Did you use the included script, flash-all? Describe how you attempted to flash to stock.
[Google TV General] fixsony:
I did flash-all and moreover on two different computers and different wires. I also used the instructions you gave and tried to flash LineageOS.
[Google TV General] v12xke:
@fixsony

There are no instructions to reflash to stock. It helps if you have been flashing Google phones for a while. You cannot flash the zip file via adb. You have to extract the zip contents into your adb folder. The script is a linux shell script that can't be executed in Windows/DOS command prompt. You have to open the script file in a text editor, remove the first line and then re-save it to flash-all. BAT. Once you create this new batch file, reboot the box, make sure you have a good adb connection = "adb devices" returns your serial number. "adb reboot fastboot" to get a working fastboot prompt. = "fastboot devices" returns your serial. THEN run the batch file "flash-all.bat". This will return your box to stock. It will boot up and you then have to enable adb debugging before you can attempt to install LOS, or you may want to leave it stock for now and wait for the next update.
[Google TV General] fixsony:
Thanks again for the help, I do not want to praise myself, but this device is not my first device, so I am surprised that I cannot beat it. I can make a video of the whole process and show you.
[Google TV General] v12xke:
@fixsony

Copy-pasting the resulting screen text from your command window after running flash-all.bat would be a hell of a lot more useful than a video.
[Google TV General] fathergweedo:
For one thing you are missing the last command: fastboot reboot

Curious why you're using PowersHELL vs command prompt?

Seems you're .bat file may be lacking? Not trying to be critical, just trying to understand...

EDIT: and I just noticed your earlier posting to "reboot fastboot." Should be "reboot bootloader" no?
[Google TV General] fixsony:
I did last command: fastboot reboot after coping the text, and i tried both.
[Google TV General] retyre:
20210519 is not the latest stock firmware for the device. It's 20210902. Do you know whether your box updated to it when you powered it on?

What mode does the box boot into when powered off and powered back on? How are you putting it in bootloader mode to flash the firmware?
[Google TV General] fathergweedo:
Unrelated but I have a virgin dopinder unit (#2) that has never been connected to WiFi/setup/etc., yet I'm able to boot the custom recovery from fastboot?

curley@Z97N-WIFI ~/Downloads/AndroidTV $ fastboot devices
OUSA2111025813 fastboot
curley@Z97N-WIFI ~/Downloads/AndroidTV $ fastboot getvar unlocked
unlocked: no
finished. total time: 0.052s
curley@Z97N-WIFI ~/Downloads/AndroidTV $ fastboot boot lineage-18.1-20211007-recovery-dopinder.img
downloading 'boot.img'...
OKAY [ 1.205s]
booting...
OKAY [ 0.000s]
finished. total time: 1.205s
curley@Z97N-WIFI ~/Downloads/AndroidTV $

Weird that I can do this with the bootloader still locked?
[Google TV General] fathergweedo:
I don't know of a full flash for 20210902, but I have the earlier version (dopinder-qt.20210519-factory). The newer one that I have, is an update to 20210902 and I'm not sure how useful this can be from fastboot. I only used the boot.img to root the updated (online) stock ROM.
[Google TV General] fixsony:
after flashing, the device enters non-stop booting, to enter in bootloader I am holding button and connect to pc and enter command update.exe bulkcmd fastboot. from wiki newest available for download 20210519
[Google TV General] retyre:
Are you able to boot lineage recovery from bootloader (fastboot boot /path/to/lineage_recovery.img)?
[Google TV General] fixsony:
Yes
[Google TV General] npjohnson:
Yeah, security flaw, I reported it already.

Then you're not bricked - install lineageos, wipe data, and enjoy.

I don't know what you're doing wrong here - I just tried the build and it boots.
[Google TV General] JoshuaDoes:
So I'm successfully running the LineageOS 18.1 dopinder builds, and I decided I wanted to try my hand at supporting ATV devices with my custom ROM project. Got a clean repo sync of lineage-18.1 and ran a successful dopinder build, but it doesn't boot and hangs at splash, and after a few boot attempts HDMI dies until I restore to stock. What's the quickest way to get adb debugging in early init so I can get a logcat and dmesg to study?
[Google TV General] ROM_gamer987:
Hey can u provide me with the device tree,vendor and etc..., everything needed for building, i wanna try to build a rom for the device
[Google TV General] drmarble:
Build for dopinder | Odd Solutions Wiki

wiki.oddsolutions.us
[Google TV General] ROM_gamer987:
That's telling me to just run breakfest and rely on roomservice to download it, it's not an official lineage device tho (and im building another rom) so it won't download, i need the actual git repos or a local manifest
[Google TV General] JoshuaDoes:
It actually is an official device in progress, just unofficially listed on their own site until it's ready to be fully LineageOS official. When you breakfast dopinder, it pulls straight from LineageOS's GitHub for all except proprietary vendor files, which you can pull from the ROM with the extract files script provided by the device tree.
[Google TV General] fthomps:
Any chance this will work on the Tivo Stream 4k?
[Google TV General] npjohnson:
your issue is that these devices aren't fully official for good reason ;p we just merged enforcing selinux yesterday, and GApps reservation space isn't done yet.

You also need all the ATV platform commits for your ROM, and the apps and such.

Honestly, give it a month or so and it should /just work/.
[Google TV General] npjohnson:
Yeah, and the instructions are right. That will (as of today) get you a booting build if you have vendor in place from themuppets like literally every other device. Just trace the lineage.dependencies files if you really don't want to use Lineage source. Warning - there are a TON of platform commits and repos you'll need to track in a different ROM to properly support ATV - hell - the SUW doesn't even fully support controller right now - we're working on it.

Correct.

Nope. Not even same SoC, plus that device's bootloader is locked.
[Google TV General] JoshuaDoes:
I appreciate the heads up on all this, but earlier I did another repo sync for fun and my new builds have been booting (ofc without the ATV platform commits or apps, so they're bare builds), and since then I've been poking with space for OpenGApps TV stock via the systemimage reserved size before I start figuring my apps out. I'm willing to work through the progress until it does just work, but in the meantime I'm not intending to start making production releases any time soon so it's not an issue for my personal testing!
[Google TV General] npjohnson:
Oh, do whatever you want! I wasn't trying to discourage you, just letting you know it's not yet ready.

As for reserved sizes, I'm actually working on it right now. Very close to working.

If you're interested in really helping out, help me figure out how to fix hardware backed OMX, as I have no clue. We just fell back to software backed OMX instead which is meh.
[Google TV General] JoshuaDoes:
I may actually try helping out with that, I'll have more time tomorrow but once I get home tonight I'll comb the errors and see what stands out to me
[Google TV General] npjohnson:
You need to revert the software OMX commit in device tree to test. Thx