yashsingh1/xdaforums huggingface dataset:
[Google TV General] npjohnson:
Deadpool and wade us hardware backed, all of them do now.

Nothing missing from stock, Wade and dopinder are near to identical stock ROM wise.
[Google TV General] :
Does the build for dopinder include (or support) the droidlogic videoplayer (Movie Player), com.droidlogic.videoplayer, like the original rom?

I haven't tested your builds since lineage-19.1-20220513, but I seem to remember having some trouble with the droidlogic videoplayer on dopinder. The apk for this app is build specific, or something like that (signatures or something).
[Google TV General] pepenador:
Has anyone experienced the following and perhaps have a solution...

I flashed dopinder back to stock using "udpate bulkcmd fastboot" and running the stock flash batch file. The flash appeared to succeed and all the messages confirmed a successful flash. However now when I plug the Onn unit into power it does not power-up at all.

I've tried re-flashing it a few times. Each time I get reports that the flash has been successful, but I can't get the unit to boot again.

Do I need to do anything else before or after the full stock flash to get the unit to boot again?

I had completed the same process previously while exploring the device and had no problem reverting to stock from LineageOS.

I flashed back to stock to try and identify any minor discrepancies between LineageOS and stock to try and identify what may be causing the Widevine DRM issue. However I've hit a block as I now can't boot at all.

Any ideas would be helpful.
[Google TV General] :
But you can still get a burn mode and/or fastboot connection?
[Google TV General] pepenador:
I can still get to burn mode and a fastboot connection via "update bulkcmd fastboot". I can also flash stock and it reports that it has been flashed successfully, however when I try and reboot it, it now just sits at the "Onn" screen. I did manage to reflash LineageOS and that surprisingly will boot.

So it appears that I can flash to a working LineageOS but no longer seem to be able to flash to stock.

I suspect that the equivalent of a disc's MBR may be corrupt, but nothing I've tried has worked.

commands such as "update reset dev0" and ' update bulkcmd "disc_initial 0" ' report that they have processed successfully, but I do not seem to be able to reflash back to a working version of stock.

Any ideas would be welcome
[Google TV General] npjohnson:
Make sure you flash dtb.img as _aml_dtb in burn mode
[Google TV General] pepenador:
Thank you. I will give this a try.
[Google TV General] pepenador:
I managed to lay hands on a second (stock) dopinder device. When comparing stock with LineageOS there are quite a few hardware decoders missing from Lineage. Could this be the root of the Widevine DRM issues. Have a look at the attached image:

If this is the case, would it be possible to copy over the required libraries from stock to LineageOS?

Also, I still wonder if the product name is effecting the Widevine crypto. Here are the product name differences:

Stock: sti6140d360

LineageOS: lineage_dopinder

Is there any online component to Widevine? Other crypto schemes include an online checking component and perhaps the name, build and build fingerprint details are causing the DRM crypto to fail.

Do either of these ideas (missing decoders or product name) make any sense?
[Google TV General] npjohnson:
Maybe I haven't covered this well enough, the issue and the reason that those codecs don't show is that l1 is broken on dopinder, it works on Wade, which is nearly identical, and Deadpool which is close. Really not sure why l1 is broken, if you fix it, those codecs will show.

As for fingerprint and description, those are both overridden to match stock, you're looking at different values, and not ones that anything important checks.

If you look at recent commit history, I made dopinder match how Wade (which works) does things everywhere that I could - not sure why it's broken.
[Google TV General] mtmoretz:
Thank you for the detailed explanation
[Google TV General] :
I haven't booted the current build for wade yet (to compare), but these are some of the errors the dopinder build has. Don't know if these are unusual or not:

[ 11.769237@0]s [TEE] MESSAGE: USER-TA:log_msg:68: KeymasterTA (err): app/ipc/keymaster_ipc.cpp, Line 386: Command 112 not allowed before configure command
[ 11.783059@0]s [TEE] MESSAGE: USER-TA:log_msg:68: KeymasterTA (err): app/ipc/keymaster_ipc.cpp, Line 601: Cannot dispatch unknown command 132
[ 11.795687@0]s [TEE] MESSAGE: USER-TA:log_msg:68: KeymasterTA (err): app/ipc/keymaster_ipc.cpp, Line 601: Cannot dispatch unknown command 116

[ 13.935209@0]s [TEE] the package has 105 fws totally.
[ 13.935210@0]s [TEE] the fw pack ver v0.2 is too lower.
[ 13.935211@0]s [TEE] it may work abnormally so need to be update in time.
[ 13.935213@0]s [TEE] the fw with 488 KB will be loaded.

[ 747.022919@0]s [TEE] tvp_mode 2
[ 747.022926@0]s [TEE] [Secmem_V2_CheckTVPBind:46] error return 1
[ 747.022928@0]s [TEE] [Secmem_V2_MemToPhyRPC:769] error return 1
[ 747.022929@0]s [TEE] cmd id 256 return error 1
[ 747.022930@0]s [TEE] AllocBuffer Failed 1
[ 747.022931@0]s [TEE] Map paddr failed e2e00000 100000 816
[ 747.022932@0]s [TEE] [WVCENC_CopyBuffer:1112] error return 1c

[ 891.288690@0]s [TEE] [Secmem_V2_CheckTVPBind:46] error return 1
[ 891.294533@0]s [TEE] [Secmem_V2_MemToPhyRPC:769] error return 1
[ 891.300490@0]s [TEE] cmd id 256 return error 1
[ 891.304839@0]s [TEE] AllocBuffer Failed 1
[ 891.308824@0]s [TEE] Map paddr failed e2e00000 100000 1394
[ 891.314287@0]s [TEE] [OEMCrypto_DecryptCENC(): destination status: 28]
[ 891.320858@0]s [TEE] [WVCENC_DecryptCENC:433] error return 1c

The keybox reads fine, so it must be some tee (interaction) stuff.
[Google TV General] npjohnson:
This is exactly the issue.

And yes, it is definitely the interaction it or something funky with .TA files.
[Google TV General] pepenador:
@npjohnson is there any chance that with dopinder a partition containing the .TA files is being corrupted during the flashing process itself?

After a number of successful flashes, I am unable to flash dopinder back to stock (but I can flash back to LineageOS). This seems to be due to partition corruption or a partition size mismatch which no longer matches the ROM's expectations. In the past I have seen similar issues with devices that have had their partitions corrupted, however these devices were all phones (not set-top boxes) and none of them were AMLogic SOCs.

What would happen if you were to install LineageOS on dopinder and then seperatelly flash a copy of a known good stock partition containing working .TA files. Is this even feasible?

One final question about the dopinder ROM. Is it running SE Linux permissive? If it is not, would it be possible to make it SE Linux permissive to check to see if the SE Linux permissions may be causing a problem? If this works, then at least we know that we would just need to tweak the SE Linux manifest to correct the .TA file access. Again, I could be 100 miles off on this, but it's just another thought.
[Google TV General] squamo:
I have a really weird problem. I've flashed the dtb, dtbo, and recovery, but I can only access the recovery menu when it's plugged into the wall plug it came with. When I do the same with a PC to flash the ROM, it just wont boot into recovery even while the button is being held down. Im guessing it might be a power thing since the device takes 5 volts which i dont think the ports on my PC can supply. Anyone else have any guesses?
[Google TV General] :
A button press triggers a series of sequential checks. One of the earlier checks tests for a usb connection,

If it finds a usb connection, it uses that.

Only if it doesn't find a usb connection does it boot to recovery.

upgrade_key=if gpio input GPIOAO_3; then echo detect upgrade key; run update;fi;

update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;
[Google TV General] squamo:
Is there either a way to hide the usb connection or boot it into adb mode?
[Google TV General] fixsony:
Have you tried doing a factory reset?
[Google TV General] npjohnson:
No.

/vendor contains them and it is reflashed on every lineage install.

You need to flash _aml_dtb in burn mode from stock to boot stock, there is your booting stock issue - no corruption, if GPT was corrupted, you wouldn't be able to boot anything.

You can't flash Android 10 (stock) vendor on Android 12 (LineageOS). Just won't work.

And yes, it is permissive, and even if it's not, I assure you this isn't the issue as my dopinder is permissive.
[Google TV General] pepenador:
@npjohnson Thank you for your patience in explaining and your ongoing attempts to crack the dopinder DRM issues.
[Google TV General] anphabvn:
Fire stick 3rd also have Lineage Os 18 but only 1Gb Ram. Which device should i buy Onn box or FireStick?
[Google TV General] RDS5:
id suggest avoiding both.

onn box is better and will likely last you longer (because its more powerful and has a stronger community around it), and ive had pretty good experience with mine (dynalink 4k, nearly identical hardware).

id recommend getting the dynalink 4k since it doesnt have any current issues with this rom, but the developer's hard at work getting the onn box working, so if you dont mind waiting a little bit, the onn box is just as good as the dynalink 4k.
[Google TV General] tenfox:
Thank you again for this project. I have 19.1-20220810 with 19.1-20220809-recovery running successfully on dopinder. Smooth and no issues with anything I've run on it.

I would like to do the following: Have dopinder boxes running a basic android desktop to launch a video presentation I can hand out to people. I don't need any internet connectvity, gapps or anything other than apps and files I can sideload.

So, is it possible to get dopinder to run with a basic android system without going through androidtv setup? (logging in to wifi, a google account, etc)

I'm willing to put in the time to set up a build environment, but I wanted to check if what I will end up building will look like a blank android tablet, or will I be back to having androidtv wanting to set up a google account for each box?

Thank you very much for your time!
[Google TV General] Big Dumb Object:
This subject has been covered many times here (you can do a search for the keyword "tablet"). In short, the tablet version without GApps will be available on the official release, just as happened with Nvidia Shield TV (according to npjohnson).
[Google TV General] GroundControl2MT:
I happen to find a new in box ccwgtv mfg: 10/2020 on ebay today. is sabrina working on the latest builds yet 'lineage-19.1-20220810'? If not what is the last working build for sabrina? thank you
[Google TV General] npjohnson:
It "works" - bout in the same boat as dopinder. Some DRM works but not all.
[Google TV General] nosillock:
I've been using 18.1 lineageOS (dopinder) for a pretty specific use-case and it has worked well. I recently got a new Onn 4k device to try the 19.1 build. My use requires that my application be the device owner, i.e. dpm set-device-owner command, etc. This all worked fine for 18.1, but I am having issues setting the device owner on 19.1. Anyone have any thoughts?
[Google TV General] Slimshady997:
where can I download that version of lineageOS?
[Google TV General] EtSimulViator444:
I'd like to know where I can find the 18.1 version of LOS for dopinder as well
[Google TV General] npjohnson:
wade and deadpool are official now!
[Google TV General] :
Congratulations! It's been a long and winding road. Nice work!

I like wade better than dopinder anyway. Dopinder seems more prone to spontaneously combust. Just looking at the boards side-by-side, wade has a more robust component selection in several key circuits.
[Google TV General] forart.eu:
Congrats !

There is a way to have "generic" builds - like LibreELEC, to be clear - for all Amlogic-based boxes ?
[Google TV General] npjohnson:
Not using my trees.
[Google TV General] 1eleas:
Hi all,

quick question regarding the "Walmart Dynalink 4K Box". Can I use the same procedure/ image for the non Walmart Dynalink 4k box --> https://dynalink.life/products/dynalink-android-tv?
[Google TV General] Big Dumb Object:
Seems like one of those things that people usually comment like "wish I'd known about this sooner". There are so many voices around claiming that Onn 4K is the same thing as Dynalink 4K, just cheaper, so don't be a fool to overpay.

Might it be worth it to be mentioned in the title post to guide those who haven't yet made a purchase? 10 bucks in exchange for reliability is worth some consideration.
[Google TV General] npjohnson:
No. Completely different.
[Google TV General] npjohnson:
I have had 2 dopinders just randomly die, now given, these devices were meant for flashing multiple times a month, and I do for development, but still - I am convinced dopinder's are the meeseeks of Android TV's lol.

wade on the other hand is the same one I've always had.

wade + Deadpool are _identical_ down to kernel-side stuff, just wade has IR turned on in DTBO, as it has IR soldered where Deadpool doesn't - in theory you could desolder the one on wade and swap it over. They're that similar.

dopinder on the other hand is a diff CPU, diff board layout, and RTK (cheaper, worse) Wi-Fi/BT chip.
[Google TV General] R!ffRaff:
good work,

what is the chance of an adaptation for the nich wallmart boxes? i would like to use one from amazon - wallmart no longer exists here.

i hope for a possibility
[Google TV General] npjohnson:
what do you mean?
[Google TV General] R!ffRaff:
i would like to install LOS on the dynlink 4k from Amazon (walmart does not exist here), same question at #1231.

you write in #1233 that it is not possible - where are the differences there? from phones I know no problems in different regions and that only in the mobile area!
[Google TV General] npjohnson:
Interesting.

Yes. You totally can.

Sorry, I thought this was asking about the dynalink stick - that box is the same.
[Google TV General] R!ffRaff:
that's nice, after I saw that you led the box to the release, I immediately ordered one for myself. this is already shipped on Amazon EU. 🚚

I will be happy to test and report it. :cool:

In your instructions: download dtb and dtb is empty - no files available
[Google TV General] jamesklaas:
So... I'm pretty sure I've totally bricked my dopinder.

OTA upgrade for the LineageOS wouldn't upgrade 19.1, so I assumed I would have to go through the installation again, but I knew the bootloader was unlocked already.

So I skipped to the step of "Flashing the dtb and dtbo partitions".

When I tried to

adb reboot bootloader

it stopped responding, so I unplugged it. Now it isn't recognized by Linux any more unless I hold the button down and plug it in.

Before, when I plugged it in dmesg said:

new high-speed USB device number 9 using xhci_hcd
New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 4.40
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: sti6140d360
Manufacturer: askey
SerialNumber: OUSA2115001711
USB disconnect, device number 9
new high-speed USB device number 10 using xhci_hcd
New USB device found, idVendor=18d1, idProduct=0d02, bcdDevice=99.99
New USB device strings: Mfr=1, Product=2, SerialNumber=3
Product: USB download gadget
Manufacturer: amlogic
SerialNumber: OUSA2115001711

Now, after holding down the button and plugging it in, dmesg says:

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

How unfortunate am I?
[Google TV General] npjohnson:
`So I skipped to the step of "Flashing the dtb and dtbo partitions".` - yeah, you need those. They're there for a reason.

You can use amlogics `update` binary and run `sudo update bulkcmd fastboot` to get to bootloader and start again.
[Google TV General] jamesklaas:
Well, I didn't skip "Flashing the dtb and dtbo partitions", I went directly to it. But it still didn't work as expected.

I'll have to find that and investigate. Thanks.
[Google TV General] R!ffRaff:
where can I find the two dtb and dtbo images? the linked directory (wiki) is empty!
[Google TV General] npjohnson:
yeah, needed space on the server. I'll get new builds up once the ASB is merged. Give it like, 5 days.
[Google TV General] HartmutH:
At first thank you for developing!

I tried to install the last unofficial (lineage-19.1-20220908-UNOFFICIAL-wade.zip) version on my "Dynalink DL-ATV36".

The installation done without errors. However I run into a boot loop. I see the LinageOS Logo and sometimes the remote control but after that the box restarts. I installed several times with the same result.

Do you have an idea what I could do?
[Google TV General] :
You could list, with precision, the steps that you repeatedly did and maybe someone will notice where you went wrong. Most problems lately seem to involve failure to flash the appropriate dtb/dtbo at the appropriate time(s).

With the v18 builds, it was fortunate that dtb/dtbo were also compatible with stock and vice versa. For whatever reason (I don't know) there is not this same sort of dtb/dtbo compatibility between stock and v19 builds.
[Google TV General] HartmutH:
I used this tutorial step by step (https://wiki.lineageos.org/devices/wade/install) and got no error on my Ubuntu terminal. However, I may have restarted the box too quickly after fastboot flash dtb & dtbo because I didn't get any feedback on the TV screen at that point.

Is there a way to flash dtb & dtbo again? I have the problem that when the TV box is in recovery mode I have an ADB connection to my Ubuntu laptop, but when I restart the TV box in the bootloader the ADB connection is not available.
[Google TV General] BTK19:
In bootloader its fastboot not ADB
[Google TV General] HartmutH:
Oh yeah! You're right. Thank you! I tested it and got a fastboot connection. Thats good but then I got a error message as I tried to flash dtb ...

I format data but it did not help.

hartmut@ubuntu:~/Dokumente/220908_Walmat_TV$ sudo fastboot flash dtb lineage-19.1-20220908-dtb-wade.img

Sending 'dtb' (81 KB) OKAY [ 0.010s]

Writing 'dtb' FAILED (remote: 'No such file or directory')

fastboot: error: Command failed
[Google TV General] BTK19:
Did you cd into the directory were the dtb image is before trying to flash it. Like if its in downloads. cd /home/username/Downloads
[Google TV General] retyre:
That's likely not the issue. Senor(a) looks to be in fastboot, not bootloader (i.e., should be doing reboot bootloader, not reboot fastboot).
[Google TV General] HartmutH:
Now I was able to install dtb again. The problem was, that I used the recovery UI from the TV Box to go into the bootloader (advanced --> reboot to bootloader). That didn't work for me. Then I used "adb reboot bootloader" from my Laptops (terminal) and it was possible to do all steps from the tutorial again. Without any error!

However the result is the same. Boot Loop :(

Are the old images available somewhere? Perhaps I should try an 18.1 image?
[Google TV General] xJumper:
Hey guys, decades long lurker here that almost never posts and just reads (usually I can do everything just from that).

So I read through all pages of this thread, managed to brick my device (Dynalink 4K Box), unbrick it using the ./update burntool and fully successfully flash lineage recovery and the new lineage-19.1-20220908-UNOFFICIAL-wade.zip

Just wanna say huge thanks to all of you working on helping people here in this thread and working on this project.

I do have one problem though.

So after successfully installing lineage recovery and lineage OS, the OS boots and gets past the usual Lineage OS logo and goes to the remote control pairing screen. Somehow I cannot get the remote to pair yet the remote actually is paired.

I can control the volume with the volume button, pressing the power button turns the TV box off and on except somehow the OS is not recognizing the pairing. The OS is stuck and just keeps showing the pairing animation telling you to press the back button and home button for three seconds. I'll admit I don't know much about the gestures/button combos on Android TV's but I have been holding down the back button while holding the home button, trying every combination thereof and cannot get it to go past this screen.

Like I said the remote is paired as I can control the volume and turn the box off and on yet I cannot bypass the pairing screen. Is there some key/button combination to bypass the pairing screen since it obviously is paired already or am I just not pressing the right button combinations?
[Google TV General] BTK19:
Have you tried just pushing the back button after its paired and seeing if it continued on with setup
[Google TV General] xJumper:
Yes I did try that, usually on most Android TV boxes that skips the pairing animation and goes to whatever menu is supposed to come after; that does not work in this case and just simply resets the pairing animation.

Could this just possible be a bug from one of the newer releases? I hope not, want to get this thing running soon.
[Google TV General] npjohnson:
it isn't paired, it is using IR to control it.

You need to do the wade pairing combo, it isn't the same as the default one iirc.
[Google TV General] xJumper:
And how do I do this? What is the "wade pairing combo" Is this a special combo? I am following what it says on the screen, pressing and holding back & home buttons and nothing is happening.

Do I need a different remote? What do I need to do here.
[Google TV General] npjohnson:
Select + Volume Down
[Google TV General] xJumper:
Well what do you know it works, mega thanks!!!!

I know this sounds dumb but I bet anything I won't be the only one to get this issues, so for all the other lurkers I got to look stupid for you.

Many thanks to all the guys here and the project, it's awsome having bloat free Arm64 devices whether it's Lineage OS on mobiles or TV boxes.

One more thing though, is there an option to bypass the Google Account sign in and just use the box as a local user?
[Google TV General] HartmutH:
I found the problem! It was my TV! SIMPLINK was activated and was the reason for the boot Loop.

LineageOS runs perfect!

Thank you for help! :)
[Google TV General] npjohnson:
What is SIMPLINK?
[Google TV General] :
It's probably some branded variant of CEC but maybe not exactly?

Consumer & Home Electronics from LG | LG UK

Explore the latest range of consumer electronics & home appliances from LG UK.

www.lg.com
[Google TV General] :
What was it doing? You'd get as far as the remote pairing screen, and then SIMPLINK would turn off the TV?
[Google TV General] Big Dumb Object:
For this you need to join the number of those people here who are waiting for the tablet builds arrival on the official release day. Take your ticket and have a seat beside me.
[Google TV General] npjohnson:
Or just don't use google apps, you can build without them easily.

ATV works fine enough without gapps.

Tablet builds will follow.

The official builds are queued but they fail to sign for some reason - working that out rn.
[Google TV General] HartmutH:
No, it seem that SIMPLINK turn off the TV Box for a short moment. I dont no what exactly happend but it looks like a normal boot loop.

I have to say, it is a really old TV, perhaps SIMPLINK is on modern TVs no longer a problem.
[Google TV General] HartmutH:
@goapy is right, I use a LG TV and SIMPLINK is a way to connect perefery (e.g Bluray Player) with the TV that they work better together. Switch off together and so on. Not really necessary for me.
[Google TV General] nosillock:
Where are the official builds for wade? The link https://download.lineageos.org/wade here is blank. Is the listed unofficial build the same as the official build at this point? https://updater.oddsolutions.us/#/devices/wade/builds
[Google TV General] BTK19:
Two post above yours explains what's happening