yashsingh1/xdaforums huggingface dataset:
[Google TV General] BlacKn1ght:
Looks like my dopinder is in mask rom mode or something, I get:

ID 1b8e:c003 Amlogic, Inc.

from lsusb

usb 5-4: new high-speed USB device number 4 using xhci_hcd
usb 5-4: New USB device found, idVendor=1b8e, idProduct=c003, bcdDevice= 0.07
usb 5-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0

from dmesg

Is there some Amlogic utility I can use to get it back to a working state? Lineage 19.0 was not the move.. 😅
[Google TV General] retyre:
Download the update binary from here and run: sudo ./update bulkcmd fastboot. This should put you in fastboot mode, from where you can flash a factory image.
[Google TV General] BlacKn1ght:
Just double checking, I have dopinder (Walmart Onn 4k tv box), will it work the same regardless?
[Google TV General] Online Gravy:
Walmart has the UHD onn box on rollback for $20 so i got 3 more of them. Im now in the process of sourcing 64 GB emmc's to swap the 8 GB emmc's with. I have a hot air station and everything else i should need to make the swap. What im not sure of is how flashing the rom onto the new storage is gonna work. Will i need to preprogram the new emmc's?
[Google TV General] aaflan88:
Does it work on a nokia streambox 8000 with AMD Logic s905X3 ?
[Google TV General] npjohnson:
no
[Google TV General] kennkanniff:
@npjohnson Too bad your tweakers.net interview is behind a pay wall.
[Google TV General] npjohnson:
Was unaware.
[Google TV General] Online Gravy:
Cheapest samsung 64GB eMMC's i could source were $18.50USD per piece. I only got 4 cause of my financials. There was a YEESTOR brand eMMC for $7USD per piece but i decided on samsung since i couldn't verify if YEESTOR eMMC's would have similar endurance/quality. I plan on sharing the entire process once i have a workflow figured out. Might do this for other devices with horribly small storage, like the new chromecast, if others are interested
[Google TV General] :
You probably should start a separate thread for your project.

I can't imagine an empty emmc being easy to program in-circuit for devices like these, so it would probably be a good idea to preprogram. You'd need a programmer with a sdio controller that can put the emmc in the proper mode to create/write the boot partitions, and a linux build that recognizes them as well.

Doing this just for fun is all well and good, but it seems like a lot of work for a little benefit. If you do remove the emmc from sabrina, take some good photos of the board. I think that I have all of the lines to the emmc on sabrina mapped out correctly, but I'd like to be sure.
[Google TV General] Online Gravy:
I'll probably start a thread after im successful. I realize there wont be a huge benefit for these devices but i wanna do it anyway. Mostly because 8GB is almost unusable without frequent storage management, and using a USB hub to attach more storage just complicates things more for the average person who doesn't understand this stuff at all. My goal is to distribute these to all my friends/ family who don't have HTPC's as a solution that will never need the storage micro managed. The effort will make my life easier in the long run
[Google TV General] :
The tivo stream 4k also has only an 8gb emmc, but the board has a place for a tf socket that would probably work if installed. That might be easier than replacing the emmc. Of course, assumed internal storage from a micro sd card isn't as good as having it all on the emmc, but it still seems a whole lot easier.

If you want to blame anyone for the low emmc storage, blame netflix. Netflix certification requirements limit internal storage to 8gb, or 16gb for a/b devices.
[Google TV General] Online Gravy:
Never knew netflix was pulling that ****. A streaming service really shouldn't have such a strong influence on hardware. Too bad they cant stop me from doing what i want with my own hardware
[Google TV General] jamesklaas:
I just got lineage-18.1-20220211-UNOFFICIAL installed on my dopinder. I initially had trouble getting the instructions to work since after running fastboot flash recovery lineage-18.1-20220112-recovery-dopinder.img I couldn't get a response from the device.

I found a section on how to get around that with the following

adb reboot bootloader
fastboot flash recovery lineage-18.1-20210805-recovery-dopinder.img
fastboot boot lineage-18.1-20220112-recovery-dopinder.img

and you do the same for sideload.

I got it installed in any case. Aside from Netflix, I'm mostly happy with this.

However, I found that if I turn the box off with the remote, it can no longer be turned on with the remote after a little while (I haven't figured out how long exactly). Right now it's just attached to a dumb display for messing with and will probably be attached to a TV in the future which will power it.

Has anyone else found this issue with the remote not turning it on?
[Google TV General] ketu:
Hello,

Is this compatibile with Minix Neo X8H?

Can we install it in the box?
[Google TV General] theprogramcam:
I have the Walmart Onn 4k tv box dopinder and was successful at getting the lineage installed. Once installed I am unable to access root at all. Is there a way around this? Reason I wanted the lineage was to have my own boot image and boot animation but am unable to access without root
[Google TV General] drmarble:
You can install magisk to get root. You can also use adb root to edit files. Lineage has no native root support.
[Google TV General] theprogramcam:
I was unable to use magisk with this device. I suppose I may have the wrong files. I will search the forum to ensure it is not already posted and I just over looked
[Google TV General] iamrance.asa:
I'm having issues with video apps on Lineage 18.1 on Dopinder. Netflix also just crashes instead of opens. Any advice on how to rectify this on my end?

Also, is there a special guide for the Lineage 19 build on the GitHub? Recovery is just a blank screen on it
[Google TV General] npjohnson:
Hardware OMX is broken.

And no, 19.0 is WIP.
[Google TV General] ShinyDiamond234:
Hi everyone, I'm having a few small problems on my dopinder box after installing LineageOS 18.1 on it. First problem is that the setup gave me no chance to program the remote to my TV's power and volume controls, and second is that I can't figure out how to add it to my Google Home setup where I have it in a specific room. My TV is an LG dumb TV from ~2016 and the settings doesn't show a clear option for HDMI-CEC but the power and volume controls worked on my old Onn tv box I had before this one, but I'm using the old one's remote still.

Any help would be appreciated. Thanks in advance!
[Google TV General] mitmille:
I ran into pretty much the same issues. The only option under LineageOS is to use HDMI-CEC. I had issues with that as well. It just didn't seem to work. An addition, the Onn unit supports a combination of IR and HDMI-CEC. Very useful for older devices that do not support CEC. LineageOS did not give me the option of supporting both. At had problems with both turning on and off power and volume control. -- I ended up reflashing the original firmware back on to the Onn unit. After that, everything was back to normal.
[Google TV General] htc_softbank:
I can't get the LineageOS revovery to respond on the Dopinger (Onn 4k Streaming Box , factory 2). I can flash boot the lineage revocery, but once in recovery, the front button doesn't allow navigation when I short press and when I connect a USB keboard it doesn't respond either.

I noticed if I long press the front button on the box, the highlight color turns to green, but short press does not allow navigation.

I tried many different versions on the 18.1 recoveries on the Git, but all have the same problem. Are the recoveries not working, or am I doing something wrong?

Releases · ods-releases/dopinder

Contribute to ods-releases/dopinder development by creating an account on GitHub.

github.com
[Google TV General] htc_softbank:
Ahh, so there is a problem! The install process must be pretty complicated if they got it working. Nothing responds once you get the box into the custom recovery. It would be great if someone can fix that or update the instructions on how the 3 devs got it to work.
[Google TV General] htc_softbank:
Was there ever a fix for this? Your post is from Aug 2021 and the issue still remains in April 2022.. I bought this box because it still shows supported. Maybe update the page to explain how you guys performed the workaround or update the page to explain this box actually doesn't work?

Install LineageOS on dopinder | Odd Solutions Wiki

wiki.oddsolutions.us
[Google TV General] npjohnson:
adb reboot sideload works.

It's not that complicated
[Google TV General] htc_softbank:
Unfortunately it is that complicated. Is there a command to get from fastboot to reboot into adb sideload after I flash the lineage recovery?

As a reminder, you need to install the custom recovery to be able to sideload the lineageos image. (otherwise it fails signature verification)

As far as I can see, there is no way to get from fastboot to adb sideload without the onn 4k booting into the os and over writting the lineage recovery I flashed.

Also, if I boot into the lineage recovery, I can't adb sideload since I cannot navigate using the button to turn on adb under the advanced option. (I get ERROR:CLOSED when I try to sideload)

So I think it's a circular catch 22 situation. lol

But ff there is some kind of trick / more detailed instructions I need to use so I can get into ADB sideload with the custom recovery (since the button or USB keyboard don't function) , that would be greatly appreciated!
[Google TV General] htc_softbank:
This is really confusing to read people got this installed on dopinger, then they don't provide the details on the workaround on getting ADB sideload turned on when the recovery is unresponsive to inputs to turn it on. :s
[Google TV General] htc_softbank:
ONCE YOU ARE IN THE LINEAGE RECOVERY:

Restarts the android device into bootloader mode.

$ adb reboot sideload
[Google TV General] npjohnson:
Dude. I said this. Like 3 times. lol.

I intend to document this better on my wiki but I'm more focused on making this builds official instead.

Boot to recovery, `adb reboot sideload`, all should be good - I enable adb by default on recovery images (unless something went sideways in recent builds).
[Google TV General] htc_softbank:
Seems like all the replies I read didn't mention that. I thought running ADB commands in fastboot wouldn't work until you turn it on. So learned something new. :)

This is a very unusual situation. I've never come across a device that has un-responsive recovery where this workaround is needed.

Anyhow, thanks! I have lineage installed now!
[Google TV General] npjohnson:
uh, you aren't running adb reboot sideload in fastboot - you're doing it from the "broken" (it works fine but the DTB is wrong) recovery.
[Google TV General] drmarble:
You can use the method described in this post:

It work. Good luck, have fun.
[Google TV General] Windows_Washer:
Hi - Have been watching this tread and thought I saw that you are moving on to begin A 12. Does that mean developer on 11 will stop? I haven’t seen a post that all issues have been resolved like Netflix and needing to side load. TY 😀
[Google TV General] Tantrim:
Is it possible to clone one of my dopinder onn 4k's and flash that image onto the other onn 4k's i have?
[Google TV General] npjohnson:
nope
[Google TV General] Tantrim:
Is it possible to modify the LineageOS build with apps/settings that I desire? I'm a junior software dev but for web stuff not android development so I'm new to all of this. That being said, I'm not sure the amount of effort required or other options I might have.

Also thanks for the work you're putting in here.
[Google TV General] npjohnson:
Yeah totally, the wiki even has build guides on how to build for this device.

The modifications you make will be up to you though, making a setting default is fairly easy in TV settings, and you can include an app pretty easily.
[Google TV General] Tantrim:
Build for dopinder | Odd Solutions Wiki

wiki.oddsolutions.us

^ is this the proper place to start? I want to make sure I'm going down the correct rabbit hole lol.

Also I'm curious, and I'm sure this is a noob question. You said I can include an app. Does this mean it's just the raw installed apk? Or is it possible to have an apk preloaded with my settings as well? You mentioned TV settings, I'm assuming you mean the android device settings.
[Google TV General] npjohnson:
yes.

and yes.

You can't flag settings on a prebuilt apk but you can on a source built one.
[Google TV General] Tantrim:
The app I would most like preconfigured is Flauncher.. which is open source luckily. I'll get to that road when I get there lol. Many more hurdles to jump before that happens!

Thanks again!
[Google TV General] npjohnson:
. build/envsetup.sh && repopick 327744

We have devs that use flauncher, so that command picks flauncher in.

Reference: https://review.lineageos.org/c/LineageOS/android_device_lineage_atv/+/327744
[Google TV General] Tantrim:
I've spent all day from installing vmware with linux and all of the involved android stuff.

I was having errors extracting the proprietary blobs from the zip file so I went ahead and installed LineageOS 18.1 on the dopinder. I tried extracting the blobs with ./extract-files.sh directly from the phone and received the following errors

​

After receiving these errors I was able to successfully run breakfast without errors.

source build/envsetup.sh
breakfast dopinder

Also I'm getting "brunch command not found". From what I understand that is supposed to come with the repo that I pulled down? That being said I'm currently running repo sync again.
[Google TV General] drmarble:
You can get the proprietary files from theMuppets: https://github.com/TheMuppets/proprietary_vendor_askey

Just include this repository in your local manifests. For more info: muppets: https://gist.github.com/fourkbomb/261ced58cd029c5f7742350aafdd9825

Good Luck, Have Fun.
[Google TV General] npjohnson:
yeah, use this - you'll need askey and amlogic.
[Google TV General] Tantrim:
Thanks! This worked, or so I think. The build is taking ages. Maybe I didn't setup the caching correctly.

a few things I have questions about:

1. Is signing the build necessary?

2. How do I preload apk's into my local build? I would like these apps to be installed by default similar to how other preloaded apps are just "there".
[Google TV General] lqtdc:
any way yo remap the physical buttons on the remote?

I have installed LineageOS but I want to launch SME
[Google TV General] npjohnson:
Download button remapper from play store.
[Google TV General] npjohnson:
build can take hours on old hardware.

1. No, you can leave test-keys.

2. See the muppets repo, it includes several prebuilt apps in makefile form. Copy that.
[Google TV General] fleisch80:
does anyone know how to unbrick this device . after a new update the box would not take

the flash of the rom. like a stupid idiot i went and tried to lock it back down because i was having problems even with just reverting back to stock.

any suggestions . i hardbricked it . no movement after bootloader , no lights,

just the android tv boot.
[Google TV General] fleisch80:
she bit me good lol
[Google TV General] npjohnson:
hold button, plug it in and pay you see burn mode in device manager/lsusb.
[Google TV General] fleisch80:
thank you friend for the guidance . its my fault . i should of known better than to hit relock

before i reverted everything back .

seems like french toast . would not take .

tried the above . there must be some pinout combination , i hear that flashburn software can recover am logic

boxes , but its hardware specific and needs pinouts to be shorted . i guess its easier to buy another 20.00 box than have big headaches late at night.

the box got me good friend . thank you for your guidance .

im glad though its not too much for another one.

chris.
[Google TV General] npjohnson:
no need to short pins order an hdmi recovery Amlogic jig to get into burn mode.
[Google TV General] :
Is "hdmi recovery Amlogic jig" the official product name?

Are the "jigs" at the following links examples of such?

https://www.tindie.com/products/superna9999/meson-hdmi-recovery-boot-plug/
https://www.aliexpress.com/item/4000494867545.html

Edit: for others reading along, there is additional information on github.

But if this mode can function to boot from usb or sdc, what is the bridge from either of those to usb burning mode?
[Google TV General] npjohnson:
Yes the tindie one.

Other ones probs work.

And if you don't have USB or sec plugged in, it falls back to burn mode :)
[Google TV General] :
Interesting. I'll give this doowhacky a try, although I imagine that getting to burn mode is probably dependent on environment variables like sdc_burning, usb_burning, update, upgrade_key, etc. being set to default or common values. One device that I've recently been playing around with has none of these set or even present, and if I set them, somehow defenv overwrites it all eventually. The uart log shows errors like this:

## Error: "upgrade_key" not defined
## Error: "sdc_burning" not defined
## Error: "usb_burning" not defined
[Google TV General] npjohnson:
No, as long as you can get into burn you can recover. Those are harmless
[Google TV General] fleisch80:
I just wanted everyone to be aware ,

The last 2 Android box onn updates had evasive countermeasures .

Ill elaborate.

Since the onn box has sound that's not the loudest ( on my setup anyway )

I had a sound booster app that would increase the sound on it .

All of a sudden the last Google update removed the app .

There were other things removed by itself too , but I'm more concerned that

the Google ecosystem has plans to lock down and control its devices just like

the big " A" did .

I tried to flash lineage on the other onn box that I had ,

Its not a coincidence that after the reboot , the box got hit with an update then

it softbricked .

ok , ill admit I didn't help it none . I finished it off by getting mad and

fully hard bricking it lol.

Has anyone else noticed evasive things occurring on their onn box since the

last few updates . any changes in how it runs , or what it can or can't do.
[Google TV General] :
Is there any reason that the recovery image used for the installation of these LOS builds does not start the uart console? The stock recovery used by all of the askey devices supported by these LOS builds do start the console.

The recovery used for installation does provide very rich loglevel output over the uart, which is useful. But it also would be useful to have the console enabled.
[Google TV General] npjohnson:
just an oversight? Push a change to enable it to Gerrit.
[Google TV General] Tantrim:
My goal is to be able to remap my YouTube, Netflix, Disney+, and HBOMAX buttons on my dopinder stock remote.

I must add I want to remain on stock.

I have a feeling the answer is to install Magisk with stock recovery found here as the boot image. If that is the case, is the below method in the spoiler still the correct way of handling this?

EDIT: I found post #115. Can I do this alone and the buttons will work? Or must this be done in addition to the root and at what step if so.

Thanks for any help. I'm still new to this.

Spoiler content hidden.
[Google TV General] Tantrim:
I know you've moved onto other devices and I don't want to re-hijack this thread. I'll keep this quick as I just have 1 question if you don't mind answering.

Can I flash a stock backup to another, different dopinder that is completely stock out of a box?

I ask because I'm scared of possibly bricking if I try. I know you said with burn mode that it's nearly impossible to brick but I want to make sure.
[Google TV General] Eliminater74:
yes you should be able to do that. as long as you do it right. as I said, its nearlly impossible to brick.. I even tried to brick mine just for kicks. and no matter what I did I was still able to get out of it. But at the same time I have many years of experience in this field.. I still have mine, I have 4 of them..........

and yes I kinda movied on, working with a Khadas Vim3 but im always willing to help if I can.
[Google TV General] famewolf:
I'll start out by saying I use linux as my main os and work with various phones via adb and fastboot. My onn has updated to the latest update which shows January 5th security date. I have gone into it's setting and enabled usb debugging mode. I do not see an option to enable oem unlock. It's connected via usb to my computer using the same cable I've used with a couple of other devices without issue but nothing is showing under adb devices which is kinda a show stopper. I've got the onn showing on tv and no "allow access to usb debugging" popup is coming up like it does on recent phones so I'm at a loss why it's not showing up. Anyone have any ideas?

*disregard* Tried another cable and it worked as expected..no idea why the difference.
[Google TV General] :
I'm assuming that there was a reboot in between the cable swap. On some devices, it can take a reboot after usb debugging is activated before the usb port will be properly set to slave mode. There is a bootparam otg_device= which can be set to 0 or 1.

0 is host, 1 is slave. Sometimes the bootparam is toggled via an environment variable that requires a reboot. Other devices switch it on the fly. Whether it works (as slave mode) or not can be further complicated if the otg pin in the micro usb plug is being physically jumped to ground, which forces slave mode.

For some steps in LOS installation on some of the supported devices, otg mode is useful for some parts of the installation (like if a mouse or keyboard needs to be connected), but other steps in the installation benefit from a non-otg mode connection. It can be trickier than one would think at first glance.
[Google TV General] famewolf:
I'm up and running on dopinger following this post..no need for otg cable: https://xdaforums.com/t/unofficial-...-g12-sm1-family-devices.4313743/post-85434073

This should be in the wiki for dopinder!

So lineage is up and running but this is the situation....something in my wifi setup prevents updates from working....I disabled adguard home and it would at least download the update but then says "verification failed" and tries to download it again. On stock which recognized both of my otg ethernet adapters I plugged one of them in and plugged it straight to the t-mobile gateway I use for internet and it downloaded the update. On lineageos neither of my otg ethernet devices are recognized so as it stands I'll have to install them manually. Additionally I've already had one hard freeze while in google play installing apps which never occured on stock. Hows the situation for others because I'm seriously considering going back to stock.

2nd hard freeze when signing into google after saying "yes it's me" on phone. These issues might be fixed if I could get the updates installed. I could tether to my cell phone but that's around 700mb of downloads.

Under discovery in settings I tried to do setup..entered my gmail password, said "yes it's me" on phone and it said an error had occured on the onn4k...and after trying to re-enter on onn4k 2 times gave me same error has occured.

I'm gonna guess that no hard ethernet drives were compiled into the kernel or as modules because I tried a third usb to ethernet and although the usb ports worked fine telling me the otg cable is working the ethernet again didn't even light up. It's a shame and it may be something particular to my setup but stock appears to be more stable FOR ME..can't speak for anyone else. I'll roll back tomorrow.