yashsingh1/xdaforums huggingface dataset:
[Google TV General] :
Caveat: I won't follow up on any questions. Do this at your own risk. You don't need an OTG cable.

If you can't boot into fastboot mode:

Get aml_flash_tool from here. I'm assuming that you're running linux and have libusb-dev.

Hold the small side button on dopinder, then plug in the microUSB cable. Keep holding the button for 10 seconds.

If you see `AMLogic` in `lsusb`, you're good to go. Otherwise, your device may be hard bricked, or you're doing something wrong.

run `./update scan` and `./update identify` as root

If it spits out a firmware version number, you're good to go. Mine gave me a few errors that I didn't care about.

run `./update partition boot <boot.img>` as root

run `./update bulkcmd "reset"` (including quotes) as root

You should now be in fastboot mode

If you can:

Boot into the bootloader mode. If you get an output in `fastboot devices`, you're good to go.

run `fastboot getvar all`. If you see "unlocked=true", you're good to go. Otherwise, follow the wiki instructions to unlock the bootloader. After `fastboot flashing unlock`, just run `fastboot reboot bootloader`.

fastboot flash dtb <dtb.img>

fastboot flash dtbo <dtbo.img>

fastboot flash boot <boot.img>

fastboot flash recovery <recovery.img>

fastboot boot <recovery.img>

This could get you past the soft brick, and into the LineageOS recovery, where you can install LineageOS as per the instructions in the wiki. You don't need to reboot between flashes; these can all be done consecutively. For some reason (probably due to earlier experimentation with the mainline kernel) I couldn't boot into recovery without flashing all the images first, so YMMV.
[Google TV General] :
The first step in the quote above flashes boot.img to the boot partition on the emmc.

The second step reboots the device.

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

Instead of:

update bulkcmd "reset"

Using this command:

update bulkcmd "fastboot"

would immediately load bootloader fastboot (without even rebooting).

And it isn't necessary to flash the boot partition first in order for this to happen.

Notice that there are no questions in this reply, so you won't have to violate your pledge not to follow up on any questions.
[Google TV General] :
I think you were so obsessed with the first line, you missed this part
[Google TV General] :
Booting into recovery is one thing, booting (or loading) bootloader fastboot is another.

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

update bulkcmd "reset"

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

update bulkcmd "fastboot"

immediately loads bootloader fastboot.

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

Im not clear how to run these commands:

"./update xxx"..do I type sh before or just ./update xxx within the terminal?

Also theres an 650mb update and it seems its obliged to update before doing anything further..should I update before the Lineage process or how it can be bypassed?
[Google TV General] :
Well, if what you described worked, I won't argue with that.

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

Anyway, if anyone wants to try using bulkcmd reset instead of bulkcmd fastboot, it will cause no harm to try.
[Google TV General] :
If it is bricked, how could the update install?
[Google TV General] js8call:
Yes..Im sorry for the miswording...

When I turned it on first time, bought it yesterday, it said it needed to be updated so I attached it to my wifi network and let it update the 650 mb..then I added my account and turned on developer mode..there was no oem unlock option..I read the web guide for Windows...I got to boot to the stock recovery..I tried to upload the dot files but it gave me an error..I skipped that step and proceeded to flash the Lineage recovery image..it took it but it shutdown..now I only get the ONN screen..

But in linux I ran lsusb and its listed as a Amlogic device...any help?
[Google TV General] BTK19:
What are dot files. Post in thread '[UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices' https://xdaforums.com/t/unofficial-...-g12-sm1-family-devices.4313743/post-87029813. that is the way to flash lineage
[Google TV General] :
It must have rebooted to install the update immediately after it downloaded.

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

So, if you ever got fully into the OS, the update was very likely installed before that.
[Google TV General] js8call:
I installed the Worldcup windows driver..I hold side button until Win7 registered and shows lisusb-win32 USB/Worldcup Drivers and its active . I go adb devices and no device is listed..I adb reboot bootloader and the Win 7 cmd says error : no devices found...the white tiny light on the box is off..what next?
[Google TV General] :
When the box has a wordcup connection to your windows pc, abd/fastboot can't communicate with the box.

Use the command line update.exe utility instead.
[Google TV General] js8call:
GitHub - khadas/utils: Utils/Tools for development

Utils/Tools for development. Contribute to khadas/utils development by creating an account on GitHub.

github.com

this site only has the git linux version..I cant find a standalone windows version,,,anyplace I can find it?...the openlinux2 amlogic site is down
[Google TV General] :
Khadas has a copy on github, here.

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

Or, attached is a copy previously linked in a prior forum post.
[Google TV General] js8call:
Thank you very much Goapy..I believe this box is bricked beyond repair..now Im NOT getting the ONN screen and if I press and hold the button the white led shows lit once very fast and then turns off..

On Ubuntu, dmesg says theres is a usb thing attached but USBview says a unknown thing is attached..I copied Kadas repo and ran aml-flash but says error : no devices..

Im going to assume that If I dont see the ONN screen anymore, its hardbricked..

Which is sad, 4k Youtube videos were really nice on this box..

Im going to try to exchange the box for another one..will you help me install.Lineage correctly?
[Google TV General] p0werpl:
I am sure goapy is the nicest human either side of the Mississippi, but please answer a couple of questions first:

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

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

What about stock do you not like that you want to install LOS?
[Google TV General] js8call:
Yes, Im sure he is a good person!

Thinking about what you proposed, I think your right..I only want the following apps installed..

Brave Browser

Flexie

Plex

Kodi

Viper4android

a noads YT app

Thats about what I like to have. I know Viper4andoid needs root SuperSu and busybox

I dont care about Netflix or Disney..I dont use them...

Any help?
[Google TV General] :
What happened to the worldcup connection that you were getting on your windows pc just a few hours prior?

It's very difficult to brick the onn device beyond repair. It takes something like bootloader corruption or physical hardware failure to do it. Anything less than that can usually be fixed using burn mode, including problems like a recovery bootloop.
[Google TV General] js8call:
the update.exe is giving a win core 12 dll error. I have updated my Win7 to SP2 and I still get the error..I can try on my win10 pc after work..but Im not getting the Onn screen anymore..I plug the box with the button pressed, I see a quick white blip and Win7 sees the worlcup device..but the Kadas update tool is not working becuase of the dll error..
[Google TV General] :
Did you also try the version of update.exe attached to forum post in amlogic.zip?
[Google TV General] js8call:
I forgot that one! Ill let you know at 6pm..
[Google TV General] :
Be sure all of the files from the zip archive are in the same directory as update.exe
[Google TV General] js8call:
I just bought a new box..I decided to keep the bricked box as the experiment box..so we can continue the unbricking process and document it here with all due credits..
[Google TV General] Slimshady997:
Is the stable version of lineageOS not out yet?
[Google TV General] fixsony:
this rom supports otg usb storage?
[Google TV General] p0werpl:
The stable version will be released conditional on BMI. How tall are you and how much do you weigh?
[Google TV General] npjohnson:
Nope. I am too busy at the moment.

Plus, it will only support wade and Deadpool at first. Sabrina and dopinder have issues we need to work out.

Yup!
[Google TV General] fixsony:
I don’t know what I’m doing wrong, but on the original firmware the set of otg cable plus usb hub plus ssd works fine, but on this firmware the ssd sees but does not open.
[Google TV General] js8call:
So far with the new box on stock I have been able to install Brave browser, but I dont get the onscreen keyboard..Kodi is kind of half working, if I add a private repo, some movies work but not all..Ethereum torrent client gives me a no permission error..I think the stock firmware after the update blocks or blacklists some UDP / TCP ports..
[Google TV General] Slimshady997:
Don't worry, I just want to be aware when the stable version comes out.
[Google TV General] VIPER4666:
Can build x96 max plus2-t s905x3 4+64？(╥╯﹏╰╥)ง( p′︵‵。) Thanks(◦˙▽˙◦)
[Google TV General] VIPER4666:
Here is its device tree :https://github.com/KostyaJRZ/device_amlogic_franklin

for Android9(っ╥╯﹏╰╥c)( p′︵‵。)
[Google TV General] npjohnson:
This doesn't use our common tree at all so no.

If you want to build a tree that uses our common tree, do so and send an email to devrel@limeageos.org - we can get it forked.
[Google TV General] VIPER4666:
device tree(╥╯﹏╰╥)ง
[Google TV General] npjohnson:
This is how that works, like I said, make a tree with proper history that inherits our commentary, then send an email to that email for review of the tree
[Google TV General] Jhoopes517:
@npjohnson finally got around to picking up 2 of the onn boxes. Excited to see where things go.

I saw you mentioned that there were some issues to be worked out with dopinder. Let me know if you need a tester (Though, I am sure you have plenty!)
[Google TV General] RDS5:
my flash drive worked but worked excruciatingly slowly as internal storage.

i do not recommend it because it is limited at usb 2.0 (because the usb connector on the box is usb micro, which is 2.0 only!). if your using it as external i dont see the point in using an ssd, and the speed might be causing compatibility issues.

also dont get mad at it because i did and now the flash drive turns into a usb-assisted heater...
[Google TV General] fixsony:
The problem is not speed, but the fact that everything works on the original rom, but not on this rom.
[Google TV General] dirtcat:
I'm concerned about not being able to navigate through YouTube with the remote control. I will try NewPipe but I'm hoping that the rooted AdAway actually blocks YouTube ads - I'm really not sure that it will.

As for Magisk documentation, XDA recently published this article on the process. It would be nice to know if somebody has already done the work on this specific Onn Android TV device. If not, it looks like I'm just going to have to give it a go.
[Google TV General] dirtcat:
Does anybody have a link to the factory OS/image/whatever for this device?

I want to "start fresh" and see if I can get Magisk working on the stock image.
[Google TV General] CambriaTester:
Anyone else not seeing oem unlock after latest update?
[Google TV General] Online Gravy:
You don't need to toggle OEM unlock to unlock the bootloader, just boot to bootloader and issue the unlock command
[Google TV General] Online Gravy:
The YouTube apps ad delivery system is extremely complex, you can't bock in app ads without using a a modded client like YouTube vanced. Vanced doesn't work for Android tv, however, there are alternatives like Smart YouTube TV and its successor Smart YouTube Next
[Google TV General] Big Dumb Object:
Let me ask a question that may be a little off-topic here, but has its addressees right here for sure.

In the same repo with builds for Amlogic boxes, there are also LOS17 builds for Nvidia Shield TV (foster) (the most up-to-date around). Since I really prefer the full (non-TV) android and hoping for it for the dopinder someday, for now I could give a try with Shield TV, and would like to understand if your builds for foster are also TV-flavored or not. (Thanks)
[Google TV General] npjohnson:
they're beta, not at all for release - but I do both foster and foster_tab builds.
[Google TV General] Big Dumb Object:
That would be just wonderful, looking forward to it! And maybe it makes sense to order dopinder right now counting on the same approach? (I'm following this thread to make a purchase if the tablet version comes out.)
[Google TV General] npjohnson:
I mean, I probably won't be doing them, but I can tell you with confidence, it's like a 2 line change.
[Google TV General] Big Dumb Object:
In some cases, users are offered to make a build themselves with a choice of their preferred flavor. For me It would be very convenient to be able to download a prebuilt ROM, but even if you totally reject such a dualism, please consider the option of adding TV/Tablet selection to the building guide if possible.
[Google TV General] npjohnson:
In the OP, under FAQ

Weird, I see it.

Yeah it can be weird.
[Google TV General] criscodecookies:
I wasn't able to revert back to stock from Lineage using the factory zip files, for whatever reason it would bootloop the Onn logo. However holding the box side button allowed opening the stock recovery and from there was able to enter bootloader, boot Lineage recovery and flash the stock OTA zip modifying it to remove the first line (newer build check) in updater-script. This required an OTG Y adapter and powered USB hub for keyboard and USB stick.

I can also confirm Magisk v23 works well on Lineage and Stock after simply flashing the zip (rename .apk to .zip) using Lineage recovery. Was able to create a simple module to replace /vendor/usr/keylayout/Vendor_0957_Product_0005.kl with TV, Channel Up/Down, Netflix etc to numpad keys which can then be remapped using an app like Button Mapper.
[Google TV General] albinoman887:
This is is exactly what I've been waating to do just didn't want to go through the tedious parrt of figuring out the keymap remapping scheme . Could you share your changes or point me in the right direction? Also can I get some clarification on DRM is it working or not working ? The OP is a little confusing. If I understand correctly it is not working but only because od broken HW omx not bootloader unlock so it's just a bug not a limitation. Or is that incorrect? (I'll help with development btw, synced tree last night . Gonna dive in tonight)
[Google TV General] npjohnson:
yeah, bug, not limitation.
[Google TV General] criscodecookies:
Netflix and Amazon Prime 4k work with Magisk on stock, safetynet ctsProfile does fail but looks like it doesn't matter like OP said.

For remap I placed the attached folder in /data/adb/modules
[Google TV General] albinoman887:
facepalm. I totally overlooked the fact that you are using the onn tv box , i have the dynalink (wade) so the remote is a little different. i was too lazy to drive to walmart and dynalink is on amazon. how did you determine what scancode each key was? thats all i need to figure out. and finally... anyone know where i can buy a remote that is the same layout and button count as the one with the onn box that is actually blutooth not some stupid usb dongle on 2.4ghtz? just curious. i'm almost thinking of just gettting the onn box and returning it without the remote and see if they take it lol
[Google TV General] criscodecookies:
adb shell getevent, then press buttons and note the line which has 'c' in the 3rd parameter ex. /dev/input/event4: 0004 0004 000c0042

then cat /proc/bus/input/devices (which may need root) to get vendor and product of the input device:

I: Bus=0005 Vendor=0957 Product=0005 Version=0011
N: Name="Onn-Remote"
P: Phys=
S: Sysfs=/devices/virtual/misc/uhid/0005:0957:0005.0001/input/input4
[Google TV General] Hig13:
I have the dopinder and have successfully booted up into lineage, seems like it's working but I'm stuck on the connect the remote screen. I hold the back and home button and the remote starts flashing with a green light, but it never connects to the device. Am I missing something? I've tried my best to search this post for other people having a similar issue but have come up empty. Anyone able to help me solve this? Should I just try reflashing or doing another factory reset?

Some how I got it to work, so never mind about that. I just held the two buttons and once it started flashing I set the remote down next to dopinder and ran to another room for something and when I got back it was connected.
[Google TV General] albinoman887:
Thanks man! got it done . now the fun part, coming up with my own actions for the buttons in button mapper. thanks again
[Google TV General] epiphone324:
On a Dopinder, would I be able to unlock the bootloader and then sideload magisk to root on stock without first installing lineageOS and reverting to stock?
[Google TV General] Kalentia:
Is there any possibility that you could release new builds of the dtb/dtbo images for dopinder? I understand that DRM is broken at the moment, but I don't personally care about that since I use this device mostly for YouTube and streaming from my local media server. Without DRM this device is still fully functional for my use case, but I can't continue with the installation instructions since the files needed to get recovery working have apparently been MIA for a couple weeks. Thank you!
[Google TV General] BTK19:
If you look in the rom zip the dtb/dtbo images are in there
[Google TV General] npjohnson:
correct.
[Google TV General] RDS5:
does it see regular flash drives? the older version of android may have had a driver that this newer version of android simply dropped for your specific drive enclosure.

you may want to try putting the ssd in a different drive enclosure and see if anything changes (i will likely test on mine too and check if my external hard drives work on my android tv).

if flash drives work and other enclosures work too its likely that this enclosure's drivers are non-standard and for some reason were included with the older android version. if nothing works then its got to do with your adapter/device.
[Google TV General] ls4860:
I can't find dtb and dtbo files on this website anymore, do I still have to flash dtb and dtboI files to my Onn. UHD streaming device or I can skip this step?

I also found those two files on OTA file (lineage-19.1-20220810-UNOFFICIAL-dopinder.zip), should I unzip the two files to flash to complete this step?
[Google TV General] npjohnson:
Yes, unzip.
[Google TV General] crazyjim_68:
Where do you report bugs? It looks like you can only report for official lines of lineageos.

The issue I am having is that wifi direct is not working. I can use wifi direct apps on the official firmware. Examples, securetether, pdanet do not work.
[Google TV General] npjohnson:
Which device? Need to know if I'm looking in Broadcom chip land or Realtek land.
[Google TV General] crazyjim_68:
Walmart Onn Device--dopinder
[Google TV General] pepenador:
Just a thought for dopinder and the failure to currently play streaming media. A few experiments showed that it is not all streaming media apps that don't work, just some. For example, Disney+ and Netflix do not currently work on dopinder, however ABCiView (ABC Australia Catch-Up Service like BBC iPlayer) does work. So I wonder, instead of DRM being the root problem, is it possible that one of the codecs has been corrupted on dopinder? I am guessing that Netflix and Disney+ currently use the same streaming codec, but that the Australian ABC iView uses an older (and different) codec. I have not dug into the logs yet, but I was just wondering aboout codecs as I investigate this device. That said it's the cheapest 4K device I can find here in Houston. Walmart may suck eggs, but they do have cheap stuff!

Edit. The ABCiView app as it is geo-locked to Australia. VPNs are your friend.
[Google TV General] npjohnson:
Nope, it's DRM that stuff isn't L1, Disney+ and Netflix are.

We know exactly the issue - L1 TEE applets won't connect to TEE - but we don't know why.
[Google TV General] pepenador:
I'm really reaching, but is there any chance that the device name "dopinder-default" is causing issues with TEE? I have found some applications are not happy with the device identifying itself as "dopinder-default" but start working if I spoof another device e.g. "BRAVIA_ATV2_EU". However none of these apps are DRM video related...

Thank you @npjohnson and all other dopinder-detectives for your ongoing investigations... 😃
[Google TV General] npjohnson:
What do you mean? The device identifies as dopinder – default?

That wouldn't cause this issue but would be an entirely separate issue, mine doesn't do that, are you guys doing anything special that could be causing it to do that?
[Google TV General] pepenador:
I'm not changing anything in the base OS, but if you use an app such as Aurora Store (open source google playstore alternative) it reports the device as "dopinder-default". Using these settings, the playstore does not return any available apps as the playstore does not have a device profile for "dopinder-default". However Aurora Store allow you to spoof a device ID, so if you choose something else, such as the "BRAVIA_ATV2_EU" then the playstore "recognizes" the device and makes downloads available. In a similar way that WiFi WPA encryption uses the SSID as part of the decryption key, I was wondering if Widevine uses the device name as part of the decryption key for TEE. I must admit that I know very little about the inner workings of TEE and Widevine at a technical level.

Do you know which version of LineageOS was the last to allow successful Widevine decryption? If I can get my hands on that, I may be able to do a little digging.
[Google TV General] npjohnson:
There was no version.

It used software backed decoding which was in large part useless for anything DRM'd.

There is no base besides stock to compare to.
[Google TV General] pepenador:
Ahh, I see. But it is working for deadpool and wade? Are they also using software backed decoding?

Anyway, I'll poke around with stock and see if there are perhaps some missing binaries that we can import.