yashsingh1/xdaforums huggingface dataset:
[Google TV General] mcain5546:
npjohnson,

1st off, thank you a ton for your work on these devices and for staying the course as things seem to change often forcing you to adapt your build in order for all of us here to benefit from it. It doesn't go unnoticed.... at least not by some.

I'm chiming in on this remark because, just as pedr0.m and a few others on this thread, I'm not understanding the instructions per the wiki when it gets to the part of installing the "update" file and so I'm literally stuck there b/c I'm not gonna smoke my device - regardless of the cost - when so many others have successfully pulled this off.

Here's my issue and I believe the others' as well: The wiki states:

"

Download this tool and either put it in the same directory you downloaded your images to.

Run sudo ./update bulkcmd fastboot and enter your sudo password. "

1st - "

EITHER

put it in the same directory you downloaded your images to"

OR

..... what ? exactly??? and more importantly

2 - windows doesn't use sudo, but I understand that to be as admin, but then neither does windows respond to

./update bulkcmd fastboot

with anything but an error message.

" '.' is not recognized as an internal or external command,

operable program or batch file. "

to be exact.

Then you state that "update.exe" is a thing, and so I ran

update.exe bulkcmd fastboot

to which i got

" 'update.exe' is not recognized as an internal or external command, operable program or batch file. "

So then I added .exe at the end of the "update" file so that it became update.exe, but when I ran the above command again I got this error

"

---------------------------

Unsupported 16-Bit Application

---------------------------

The program or feature "\??\C:\Users\kn0eb\abd-fastboot\platform-tools\update.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.

And so with that, could you please break it down for a mere mortal as myself? I know you're busy and have a life and all cause don't we all? But for the life of me, I've read this entire 50+ page thread and there's nothing here to point in whatever direction i need to go. Thanks ahead for and if you can help.

-kn0wb0ttie-
[Google TV General] p0werpl:
You think just adding a .exe to a Linux binary makes it a Windows executable? And you're finding (trivial) faults with the wiki?

There is a Windows directory in there (a little search would have helped). You should be using this instead: link.
[Google TV General] rapboys16:
I tried 3 different versions, including older versions, but PrimeVideo and Disney+ didn't work.
[Google TV General] rapboys16:
Apps open but videos do not open.
[Google TV General] Slimshady997:
friend, you still need help already can fix and can install lineageOS system. I had also stayed on the onn screen.
[Google TV General] Slimshady997:
Now that I can install lineageOS, no video app works.
[Google TV General] Slimshady997:
what are the steps to reinstall the original rom?
[Google TV General] p0werpl:
From the OP: "Can I go back to stock and relock the bootloader?"

Also from the OP: "If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here."
[Google TV General] rapboys16:
We have nothing to do with root. This is an androidTV firmware, we expect completely stable (at least working) Stream applications. I tried 4 different versions of linageOS, unfortunately the situation is the same, I'm talking about the Onn device.
[Google TV General] Slimshady997:
sorry, that's the OP. I didn't understand very well.
[Google TV General] kennkanniff:
This thread hurts my brain.
[Google TV General] lqtdc:
anyway to unbrick my device?

it cannot be seeing as adb or fastboot device.

Stuck on lineageos arrow scream.
[Google TV General] EtSimulViator444:
If someone can help this guy and I that'd be great, and thank you in advance, otherwise I have a useless onn tv box 4k (dopinder).
[Google TV General] p0werpl:
Being able to put the device in burn mode is an absolute requirement. That's easier to do in Linux (doing so in Windows requires the correct drivers, something the folks here may be even less willing to guide you through). Nearly every Linux distro has a live ISO that can be burned into USB and booted from. Please read up on this and don't expect help here on this topic.

How do you put the device in burn mode? Press the side button and plug it into your PC (with the correct drivers installed for Windows). This mode is extremely difficult for end users to accidentally disable, especially for these devices (newer Amlogic devices might use dnl), so posting here that you are not able to enter burn mode is usually a sign of user error.

Assuming the device shows up in burn mode (lsusb in Linux should show an Amlogic device (1b8e:c003 Amlogic, Inc.), you can use the Linux update binary poster earlier in this thread (for Windows, use update.exe from a link I posted earlier). The update utility can be used to unbrick the device (especially the dopinder, which is even more difficult to brick than, say, sabrina).

If you cannot enter burn mode, repeatedly posting in this thread that you're bricked and want to unbrick will get you nowhere. These posts over the last few pages have made this thread almost unreadable.
[Google TV General] mtmoretz:
I was finally able to get mine working last night, but my issues happened when it was stuck on the "Onn." splash screen. Not sure if that is what you're referring to, but I found the solution after a bit of digging in the forum. Shutdown your PC, hold down the button on the left side of the box as you power on your PC, and that will force the ONN box to boot into recovery. From there, you can Format and sideload Lineage if that is where your issues are. I am running Ubuntu 22.04 on my PC, but i would assume this should work for Windows as well. If this isn't your problem, I hope I didn't waste too much of your time.
[Google TV General] npjohnson:
Fixed. Was an selinux denial.

New builds are up.
[Google TV General] mtmoretz:
Just updated via the updater and still can't watch videos on Prime or Disney+. Error code 42 on Disney+. I made sure the update was the newest for today. Is there another way I should update to the new build?
[Google TV General] Chicharito Nguyễn:
Help me rom stock

For onn stick fullhd

And onn 4k

Someone help me

Please !

I need help
[Google TV General] Slimshady997:
I also have the same problem when installing lineageOS 19.1, no video application works for me, apart from the moment the image goes away for 1 or 2 seconds and then comes back.
[Google TV General] Slimshady997:
I had stayed on the onn screen, but if I entered the recovery by pressing the device button after connecting it, but no PC detected it anymore. I had to buy an otg cable with power to put the system on a flash drive and install it from the recovery and it worked. after that I have had problems with streaming applications that do not work, the control is not fully compatible and between moments the image goes away for 1 or 2 seconds.

this is the cable i used.

View attachment D_NQ_NP_889286-MEC43450330016_092020-O.webp
[Google TV General] rapboys16:
The situation is unfortunately the same again, Stream video service applications are opened, but when I open the content I am trying to watch, I get the same error. The version I have installed is "lineage-19.1-20220717-UNOFFICIAL-dopinder.zip".
[Google TV General] lqtdc:
Hello p0werpl,

i can use linux if needed. is there a windows driver for the burn mode?
[Google TV General] instylz:
(dopinder) can't get Netflix to work. For me it's been that way for the past 6-7 builds. I was never able to get it to work. It says we're having trouble playing this title right now for all movies I select. I checked the guide and didn't see further pre requisites. Am I missing something?
[Google TV General] Slimshady997:
I went back to the factory ROM, I had high expectations about lineageOS for dopinder, but the only thing I found was problems with the system.

If someone is stuck on the home screen, does not want to return and does not know, write to me, I have no problem helping.
[Google TV General] mtmoretz:
Is there any sort of log files I can pull and send, and if so, how would I go about doing so? I would love to use this for my daily media consumption device. Though I'm not a programmer or developer, I would like to contribute in some way if possible. BTW, I'm using the Onn/dopinder device
[Google TV General] npjohnson:
yea I just checked dopinder - something is funky - this worked like a month ago, trying to debug what broke it at the moment. wade and Deadpool are 100% fine.
[Google TV General] lqtdc:
hello, I was able to setup a linux machine.

Now my onn device does not show any video but I can see in burn mode in Linux.

I am able to use the update tool to flash dtbo, boot and recovery but still no shwoing video.

can someone point me to a guide on how to recover from burn mode using the update tool?
[Google TV General] npjohnson:
flash those via burn mode, then run ./update bulkcmd fastboot, then flash the factory image in the OP from fastboot.
[Google TV General] lqtdc:
I flashed dtbo, boot and recovery.

I run ./update bulkcmd fastboot and got this

AmlUsbBulkCmd[fastboot]

[AmlUsbRom]Err:retunr len=0 < strLenBusy 11

[AmlUsbRom]Inf:bulkInReply

ERR: AmlUsbBulkCmd failed!

not sure if i am missing something
[Google TV General] Slimshady997:
Do you mean the problems we mentioned? no streaming app works among others.
[Google TV General] npjohnson:
All but dopinder work now - we are working on dopinder.
[Google TV General] hoon.young.kim:
lineage-19.1-20220720-UNOFFICIAL-dopinder.zip

lasteat build still doesn't work streaming apps.

also what is 'lineage-19.1-20220720-boot-dopinder.img' for?

i can not find about boot.img on install guide
[Google TV General] lqtdc:
any help with this?
[Google TV General] npjohnson:
It's not going to be fixed until we figure it out.

We're actively trying to figure it out.

I will loudly announce on this thread when it is fixed.
[Google TV General] hoon.young.kim:
is there any way to download old version a month ago? i can not find older than 0612 build. 0612 also does not work to play video
[Google TV General] npjohnson:
No. And again, I'll fix this, just give me a bit.
[Google TV General] p0werpl:
How did you flash dtbo, boot and recovery? Using update or fastboot? Which version of the images did you flash? Stock or LOS? What was the underlying OS and what were you doing (flashing what?) when the device got bricked?

After flashing the images, have you unplugged and powered on the device (without holding the side button)? Do you see a difference in what appears on your screen? What shows up in lsusb?

What happens when you put the device in burn mode and run ./update bulkcmd fastboot (without flashing anything else)? Keep trying that update command. It should work.
[Google TV General] lqtdc:
Hello @p0werpl,

thanks for your response. I connected my dopinder in burn mode, holding the side button while connecting the USB, to a Ubuntu machine. I set up the update application following the guide here:

utils/aml-flash-tool/tools/_install_ at master · khadas/utils

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

github.com

I flashed all partions using these command:

./update partition dtbo <dtbo img>

./update partition boot <boot img>

./update partition recovery <recovery img>

all were succesfully flashed. Only one failing is dtb. Using this command

./update partition dtb <dtb img>

I used all latest releases from this page.

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

download.ods.ninja

in all the process, I dont get any HDMI output. this command:

./update bulkcmd fastboot

get me this output:

AmlUsbBulkCmd[fastboot]

[AmlUsbRom]Err:return len=0 < strLenBusy 11

[AmlUsbRom]Inf:bulkInReply

ERR: AmlUsbBulkCmd failed!

I saw on the guide that they send several commands using this format:

./update bulkcmd "fastboot" <<<using quotes.

I tried this and now when i connect the devicet shows under: adb devices

<code> sideload

But when tried to adb sideload any version, got failing after 47%
[Google TV General] p0werpl:
Why are you using the LOS files? The goal here is to unbrick by going back to stock (LOS has issues on dopinder in any case). You should be using this: link

If you were able to get to adb sideload, the recovery screen should show up on your TV.
[Google TV General] lqtdc:
ok, in which state should i flash this?
[Google TV General] p0werpl:
FL preferably, but no further than GA.

Flash using fastboot. If you cannot access fastboot, use update to flash bootloader, boot, recovery, dtb, dtbo, and then try fastboot.
[Google TV General] sebas4200:
Work on standby mode too , for tvs with no cec dopinder doesnt go to sleep have to unplug to g set it back on . Went back to stock rom since Disney + dont work . Thanks again for your work , no standby really kills this rom for daily use

Holding side button on dopinder after flashing recovery , and rebooting (pulling plug while holding button on dopinder ) should be part of instructions, or else well think were bricked stuck on onn screen with no usb debugging detection
[Google TV General] lqtdc:
I did put teh device in adb sideload.

C:\platform-tools>adb devices

List of devices attached

OUSA2112007618 sideload

then i tried to sideload the stock zip file.

Stuck at 0% for a couple of hours

C:\platform-tools>adb sideload dopinder-qt.20210519-factory.zip

serving: 'dopinder-qt.20210519-factory.zip' (~0%)
[Google TV General] p0werpl:
That zip cannot be sideloaded. You have to extract its contents and flash using fastboot or update.
[Google TV General] jjnova:
Welp.

Tried to flash back to stock, and am now stuck in a boot loop. Fantastic.

Anyone that flashed back to stock, did you bump into issues? The device is able to boot into bootloader and android recovery. I utilized the qt-dopinger file from the first post, went through each command with no issues, but each time it boot loops to the ONN logo and restarts.
[Google TV General] lqtdc:
@p0werpl Thanks, I was able to restore my dopinder.
[Google TV General] p0werpl:
Great! Now please pay it forward. It appears jjnova has picked a number and is first in line. He's all yours.
[Google TV General] stumlad:
Not sure if I bricked my Onn 4k or if somehow the device won't power on. I flashed the dtb and dtbo partitions and then did flash recovery step for the 20220717 recovery dopinder img. This indicated it worked, so I ran fastboot reboot-recovery.

At this point I thought I should be at a state where i'm in recovery mode and able to peform the step to install LineageOS from recovery but it was completely stuck on the Onn screen with no options to choose from. I tried to unplug and start it up again, but it didn't boot up to anything. There's no light on the side of the box. I tried holding down the power button for 5,10, 15+ seconds and nothing. When something is bricked I would expect to at least see some signs of power getting to the device..... any ideas?
[Google TV General] mtmoretz:
If it's soft-bricked, it will be stuck on the Onn screen, if it's hard-bricked, that's about what you'd expect. Try changing USB/power cables to ensure there isn't anything wring with the USB cable or port on your computer, but if it doesn't power on after that, it's probably done for.
[Google TV General] stumlad:
So I fiddled with it a bit. I have no idea if this helped or if it was just luck, but i held down the button while plugging it into my PC.. the light eventually came on and windows recognized it. I had hdmi output to one of my monitors and nothing showed up, but I was able to start the process.... Eventually the Onn screen came on and I was able to flash dtb/dtbo, then went to recovery img step

After executing

I then perform:

So this is where it gets stuck on the Onn screen. This is what happened before it hit the state i was previously in. So right now I guess i'm soft-bricked?

EDIT: I can't believe I didn't see the messages above this. Someone else point out that after recovery it gets stuck on the Onn screen and you have to unplug/replug and hold the button. This put me in recovery mode. The only thing is, my remote for the Onn isn't paired anymore so I'm unable to actually do anything on this screen.
[Google TV General] mtmoretz:
If it's soft-bricked, it will be stuck on the Onn screen, if it's hard-bricked

If it's soft-bricked, it will be stuck on the Onn screen, if it's hard-bricked, that's about what you'd expect. Try changing USB/power cables to ensure there isn't anything wring with the USB cable or port on your computer, but if it doesn't power on after that, it's probably done for.

Use the side-button on the box. Short press to move and long press to select or maybe it was the other way around
[Google TV General] stumlad:
This did the trick! Thanks!
[Google TV General] jjnova:
I have fixed the boot loop issue. It was as simple as updating adb and fastboot.

Backstory for reference: Linux machine wouldn't recognize the device when plugged into USB. There are solutions to fix this online, but they all require SystemD which my main machine does not have. So I went and dusted off a windows machine, and each step in the process went (visually) flawless. Each step completed and gave an 'Okay".

After flashing the stock ROM multiple times, erasing userdata, wiping, etc and getting no further than a boot loop, I thought to myself, "When was the last time I used Windows?". The answer it seems, was the last time I needed it to do something with a device, because I was running adb 1.x and the current version is adb 33.x.

I installed the latest versions of adb and fastboot, went through the process again, and now the device has booted and I am looking at the screen to pair the remote for the first time.

Hopefully the above has a keyword or two that will help someone in the future. I look forward to the time when LineageOS is running on this device in a state that will appease both myself and the wife. Me being a tinkerer, and her being someone that wants to watch HBO Max, Netflix, etc.

Thank you.
[Google TV General] mtmoretz:
I too am a tinkerer who has to take into account the "wife approval factor". I'll be glad when this device is up to her standards and "just works".

Incidentally, what distro do you use?
[Google TV General] jjnova:
I have been using MX Linux for a few years now. Mostly 100% happy with it. I use fairly new AMD hardware, and they have a repository dedicated to what they call "Advanced Hardware Support".

Though, unfortunately, when it came to this device, I couldn't even setup udev rules since lsusb wouldn't recognize the device as plugged in. Dug through all my cables to make sure I was using one that supported data transfer, and still no luck. Windows 10 recognized it immediately.

The wife factor is pretty major. Stock seems to me the way to go for the time being, maybe with a better remote that can be programmed. We have only had it two days but really want a play/pause button. Also the pre-programmed shortcuts on the remote don't mean much to us. I need to look into that, but I am sure a decent remote costs more than this device did!
[Google TV General] mtmoretz:
I too am a tinkerer who has to take into account the "wife approval factor". I'll be glad when this device is up to her standards and "just works".

Coincidentally, what distro do you use?

I've never tried MX Linux, but I've tried a few others and find myself returning to Xubuntu every time.

We're running a firestick at the moment but will be switching when this device is operational on lineage.
[Google TV General] treypop:
I'm wanting to flash the lineage recovery on my device and stay on stock firmware but the recovery image isn't working when I flash it. Do I have to flash the dtb.img & dtbo.img files for the recovery to flash correctly? Sorry if this has been asked before this is a very long thread at this point.
[Google TV General] mtmoretz:
Seeing that the installation guide here says to flash the dtb and dtbo before flashing recovery, I would assume they would need to be flashed first. Make sure to read the entire guide to make sure what you are wanting to do is possible. Hope this helps
[Google TV General] treypop:
Thank you. now my question is do I just pull there dtb and dtbo files from a lineage build? the file linked in the guide doesn't contain the files
[Google TV General] mtmoretz:
That is strange. I installed mine 2 weeks ago, but I remember downloading them from that guide's link. I wonder why they removed the files or maybe changed the link ¯\_(ツ)_/¯

Edit: I found out that this has the dtb.img and dtbo.img, you just have to extract it
[Google TV General] npjohnson:
the issue here is I clear them off monthly - I'll store them somewhere more permanent.
[Google TV General] treypop:
after getting the recovery flashed I rebooted but it never booted to the stock os and I cant seem to get it to flash. When I attempt to flash the stock os that's provided in the thread it gives me an error 21 signature verification failed. How do I flash the stock OS?
[Google TV General] wizardknight:
I just picked up the Walmart Onn UHD Box, and was considering loading dopinder. Can anyone tell me if it supports CEC? I like to use my tv remote for everything if possible.
[Google TV General] mtmoretz:
My advice would be to poke around the settings on stock and find out. Dopinder still isn't playing most app videos yet, but they are working on it
[Google TV General] mtmoretz:
Wanted to check and see if any progress had been made on dopinder or if there is anything I can do to help. Thanks
[Google TV General] Big Dumb Object:
Today is a somewhat special date: the first anniversary of this thread! 🥳🎂

Looks like it unexpectedly turned out to be a real development marathon, so certain persons here should be recognized for their perseverance, I think. But since the journey to the official release isn't over, it would be nice to get some kind of progress state report. Is the project still has some roadmap with particular milestones, or to date it's all about catching occasional bugs?
[Google TV General] npjohnson:
Without dopinder, we intend to ship wade and Deadpool officially very soon.

Need to fix DRM on dopinder, then it can follow.

devkits and Sabrina will lag behind.
[Google TV General] ustix:
So is there anybody who has successfully installed this on Radxa Zero? Because I have tried many aml images, many of the zips from the attached sites, but non of them are working. Can't they just make an aml image with the full OS, leaving that recovery installation method for someone else?
[Google TV General] npjohnson:
It is broken at the moment. Only 18.1 boots on radxa.
[Google TV General] ustix:
Thank you, I have tried everything but nothing worked, also the aml just vanished from the ods.ninja site. I would really appreciate a working one but maybe i will build one myself.
[Google TV General] npjohnson:
yes... it vanished because it was horridly broken.

No 19.1 builds boot on radxa atm.
[Google TV General] rapboys16:
The new version of Dopinder has arrived! So is DRM working properly in this version?
[Google TV General] mtmoretz:
Just tested and it appears there are still DRM issues, so my guess is that the update is a security update, which is also much appreciated! Just excited for the time when I can use this as my daily driver.
[Google TV General] rapboys16:
I have the same excitement🔥😊
[Google TV General] npjohnson:
No
[Google TV General] npjohnson:
On an upside, Sabrina now boots
[Google TV General] treypop:
Is there a way to configure ir remote controls on LineageOS?