yashsingh1/xdaforums huggingface dataset:
[Google TV General] JoshuaDoes:
We use software widevine for Exynos7420, so when you said hardware OMX was broken and software OMX was enabled in place I figured I'd need to revert that commit first :P
[Google TV General] JoshuaDoes:
If you want the exact size for tvstock it's 1072959488, though that'll change fast so make it higher
[Google TV General] fthomps:
The Tivo Stream 4K uses the S905Y2. Thought that was the same chip as the Onn ATV UHD. That's too bad about the bootloader though.
[Google TV General] npjohnson:
That's how much space you're reserving on system?

And the build system doesn't freak out about that for you?
[Google TV General] npjohnson:
Ah, missed the 4k part, yeah same soc but bootloader is locked
[Google TV General] JoshuaDoes:
Yeah I basically just poked the OpenGApps log for how much extra space it needed and added that to the total, and a couple builds later after messing with that total I got me a new setup wizard and no more insufficient space errors
[Google TV General] JoshuaDoes:
I ultimately settled on 1126400000, gives ~1.1GB to the system and accommodates the app adjustments I've been making for my builds without tripping OpenGApps' space check for TV stock
[Google TV General] npjohnson:
Thank you.
[Google TV General] npjohnson:
this ended up being _wayyyyy_ to much, as this is the full value of the partition vs just the space to reserve, both will work, but we want to split it amongst partitions. One of our guys recalculated it and got it working.

Should be good to build now from breakfast/extract-files (or syncing the muppets).

Only thing left is hardware OMX. Hopefully we can figure it out!
[Google TV General] lmore377:
I didn't know that was a command but it worked. I'll let you know how it goes once it finishes sideloading.
[Google TV General] lmore377:
Still stuck on the lineage os boot animation. I'm thinking maybe there's just something wrong with my box (I've been messing with it before all of this) so I might pick up another tomorrow and try it with that.

Edit: I just realized I've been talking to you thru reddit lol. I'm lmore3 on there.
[Google TV General] npjohnson:
Lol, reddit chat will be easier to debug, I'll hit you up there tomorrow.
[Google TV General] androidlover420:
Can someone provide the GMS less launcher from this
[Google TV General] npjohnson:
GitHub.com/LineageOS/android_device_lineage_atv
[Google TV General] androidlover420:
Thank You !
[Google TV General] BlacKn1ght:
Hello, I've unlocked the bootloader for flashing, however when I try to flash the DTB image I get an error:

$ fastboot flash dtb lineage-18.1-20210802-dtb-dopinder.img
Sending 'dtb' (81 KB) OKAY [ 0.003s]
Writing 'dtb' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Is there anything that I'm doing wrong? The DTBO image flashes fine though.
[Google TV General] MDMAchine:
Same issue as above when flashing dtb.

fastboot flash dtb /Users/mdmachine/Desktop/Onn\ 4k\ TV/DTB/lineage-18.1-20210802-dtb-dopinder.img
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
target reported max download size of 536870912 bytes
sending 'dtb' (81 KB)...
OKAY [ 0.005s]
writing 'dtb'...
FAILED (remote: No such file or directory)
finished. total time: 0.007s

If I move along into lineage recovery, obviously I cant do anything.

And after a reset it's back to stock recovery.
[Google TV General] eagledipesh:
Are you planning to support other amlogic boards like s912 tx92??
[Google TV General] TR3275:
Which features from Google TV was included in the LineageOS build? The one feature I wish the Android TV that Google TV has is the multiple profile support. I want to set up my Onn. 4K box with a kids profile. So far my options have been limited.
[Google TV General] lmore377:
@MDMAchine

Make sure you do 'adb reboot bootloader' and not 'adb reboot fastboot'. The box should be stuck on the boot logo and shouldn't show anything else. The dtb partition isn't accessible from the fastboot that runs in recovery mode.
[Google TV General] criscodecookies:
Be careful guys, just bricked one of mine by doing adb reboot bootloader, then flashing dtb and dtbo.

Should note the instructions say to use fastboot but dtb won't flash unless in bootloader.

Now my Onn 4K only boots to the Amlogic flash mode which only the USB Burning Tool can use,

I'd need a full system dump ".img" of the device to unbrick it.

If any of you can make one if you have root working I'd greatly appreciate it!
[Google TV General] lmore377:
Do you have soldering experience and a serial adapter or arduino? If you do, you can stop the box from going to burn mode and get fastboot again so you can flash the factory image. I'll walk you through it.
[Google TV General] MDMAchine:
Too late lol....
[Google TV General] fixsony:
Only this current firmware update in case it's ever useful in the future

10 QT 202110519

https://android.googleapis.com/packages/ota-api/package/2d05bfef7d34e4ac55141761e58b2f4a36184674.zip
[Google TV General] lmore377:
If your box still shows the bootlogo it can be unbricked. There is no image available that can be flashed through burn mode but if you can open up the box and solder some wires to a serial adapter you can interrupt uboot before it goes into burn mode and make it go into fastboot mode instead and you can flash the factory images in the main post. I'll make a tutorial in a bit.
[Google TV General] npjohnson:
No. Different generation of chip.

I've crossed out the links in the OP - further investigation is needed.

but there is a full factory image with DTB linked in the FAQ.

Install this driver: https://drive.google.com/file/d/1q3Hwrmx-YCrw9U5JGtI2Ocn06zPkjrEG/view?usp=sharing

Download the amlogic `update` tool http://openlinux2.amlogic.com/download/A113/Tool/flash-tool-v4.7/flash-tool/tools/windows/ and run `update.exe bulkcmd fastboot` - then you can flash the factory image as usual.

Sorry about this, AML DTB's are... weird compared to other devices.
[Google TV General] lmore377:
1. Open up the case and take out the PCB. You can do this however you want but it seems like the easiest way to do it is with two plastic cards. Be careful along the edge where the button is because you can snap off the plastic bit and it'll be a lot harder to push the button.

2. Solder a USB to Serial adapter with the following pinout (except for VCC)

3. Plug the adapter into your computer and open up a terminal program

4. Hold down control + C on your keyboard while plugging the box into your computer with micro USB. A lot of text should fly by then you should be met with 'g12a_u212_v1#'

5. Type fastboot and hit enter. Download the factory image if you haven't already. Before anything, do 'fastboot flash dtb dtb.img' then finally you can run flash_all.sh or just flash them all manually.

Edit: or just do what the post above says lol. That one didn't show up until I posted this.
[Google TV General] criscodecookies:
I was aware of the risks of flashing an unofficial ROM and knew there was no way to enter recovery using the remote like with the Mi Box.

It's great to see there's multiple solutions/options especially so quickly, thank you both!

I can confirm the amlogic update command worked and flashing the factory image has it running again.

At least now the chances for a true brick are minimal given these options.
[Google TV General] JMBN.:
Thsnks for the effort.

How come you guys decided to include Google launcher with ads rather than one of the alternatives with no ads?
[Google TV General] ROM_gamer987:
So on stock software my onn box decided to not connect to the remote anymore, i reset it 6 times already, i have adb disabled so i can't reboot to bootloader that way, how can i get to my bootloader to flash the rom and hopefully fix the issue? (the controller is fine it connects to my phone fine)
[Google TV General] v12xke:
@ROM_gamer987

Not sure how you would access adb with adb debugging disabled. You can still get to stock recovery using the button, where I *think* reboot to bootloader is an option and then fastboot flash the stock rom. Flashing the stock rom which *should* get you squared away. Stock rom is linked in the wiki and you can just unpack the zip and run the script.
[Google TV General] brick00444:
I want to say Thank you for your work. I have 1 issue. I use the app Channels DVR and it opens fine and sees all my channels but when I choose a channels it just shows a black screen. Sorry if I posted this in the wrong area. but just wondering if others are having similar issues. Could it be something to do with DRM? Also should have said I'm using an ONN box
[Google TV General] Broman400:
Can I root my Onn box without installing Lineage on it?
[Google TV General] fathergweedo:
Yes. There are several posts here in the thread about this, but it boils down to pushing your stock boot.img to the device and using Magisk to patch it, then pulling it and eventually flashing it via fastboot.
[Google TV General] npjohnson:
search for amlogic's "Update" tool - then run update.exe bulkcmd fastboot, at which point you can fastboot oem unlock, and fastboot boot a recovery image.
[Google TV General] npjohnson:
Yeah it's probs related to h264/h265 largely being only hardware backed codecs :/
[Google TV General] brick00444:
Thanks for the response
[Google TV General] Broman400:
Do I have to have a custom recovery installed for this? Only reason I want to do this is to install a script to be able to remap the remote buttons
[Google TV General] alphahere:
No you don't need a custom recovery to root the ONN. Can you kindly share this script to remap the keys?

Thanks
[Google TV General] grape12:
I have the same issue. Here is a logcat. Any suggestions?
[Google TV General] fathergweedo:
You just barely beat me to this answer - lol! I was busy restoring one of these to pure stock in order to verify my operations, but I 2nd the motion to share the remap script. I'm hoping to use the YouTube button to launch SmartTubeNext. Fingers crossed ;)
[Google TV General] npjohnson:
Hardware backed OMX sadly. Trying to fix it.
[Google TV General] fathergweedo:
Stock recovery will do. I just reset one of these to pure stock to verify. I used Magisk 23.0 (follow the "Patching Images" section of THIS), and the 10 QT 20210902 boot image to patch (assuming you are at this build). I uploaded those stock boot and recovery images Here. Unless you've already flashed the custom recovery from this thread, you only need the boot.img.

You may want to install a file manager (I used FX File Explorer) before hand to navigate the boot.img to be patched via Magisk.
[Google TV General] TheEnekaign:
Do we know if Wade has anti-rollback by any chance? and/or if someone has an old update for it I could try to sideload through ADB. My wade/dynalink device updated unexpectedly the other night to build PI.PG2-DL-ATV36-Dynalink_V2.02.09 user release-keys, and now OEM Unlock doesn't exist in the dev options and fastboot flashing unlock fails with remote: unlock_ability is 0, can not unlock.

I saw a few OTA zips for the Onn box, but I haven't seen anything about Wade/Dynalink.
[Google TV General] hp420:
buy a new remote and use button remapper. you won't regret it!!! there's about 4-5 buttons i just can't remap...but i think this is where that script mentioned may come in.

i bought this one for $13, and my stock remote just lives in a drawer now.

https://www.amazon.com/dp/B01CL3ZXGO/ref=cm_sw_r_apan_glt_fabc_H6W7G1VGV6ESHGZN14D6?_encoding=UTF8&psc=1

button remapper plays well, within reason, and it uses an air mouse, as well. this has saved my ass in SEVERAL apps that aren't really ATV compatible. if the cursor won't scroll you can click the air mouse button, then just click the button you want just like it's a touch screen device!! the only real drawback is having to use an otg cable for the dongle.

i have a button for settings, one for sTube, one for live tv, one for sling, one to my cloud storage.... it's been AMAZING switching between apps without having to go home!!
[Google TV General] alphahere:
Looks like a great remote. Heck, the onn only costs 7 dollars more than the that remote. I use an old bluetooth android keyboard and bluetooth mouse. This combination works well for setup.
[Google TV General] Big Dumb Object:
Check it out on the Aliexpress: MX3 is a fairly common model, which is not hard to find cheaper and in various configurations.

Taking a moment I would like to express some respect for the tablet release for Shield. With this, it's owners already have the official Google-less Android 10 builds with MicroG. Although I'm still counting on the same thing with Onn, it made me pleased anyway. Thanks for work!
[Google TV General] Big Dumb Object:
It is noteworthy that there is a LineageOS for MicroG release for non-tablet edition too. Does this mean that MicroG was somehow adapted for Android TV? This is strange, but unfortunately I can not check myself, because I don't have Shield.
[Google TV General] npjohnson:
Nope it doesn't work. They just blindly pushed it out.
[Google TV General] hp420:
you save $2 and wait until christmas for delivery. i'll use amazon thanks. but yes, it is fairly common 😊
[Google TV General] techdeisel:
Hold the side button while plugging the device into your computer or power that will put it into the bootloader
[Google TV General] grave35:
After two minutes of operation, the remote control stops working. Updating to the latest build and resetting does not solve the problem. In settings, it says that the remote control is connected. how can I fix the problem?
[Google TV General] npjohnson:
Chromecast? If so, not sure, I've hit that bug once and can't figure it out.
[Google TV General] grave35:
Yes. This error is present on two devices. On the first device, the firmware of the remote control is out of the box. On the second device, the firmware on the remote 27.4 has been updated to the latest version. Can we try to collect logs and find this error?
[Google TV General] npjohnson:
You can, I have it locally and can recreate, I just can't figure it out at the moment
[Google TV General] ROM_gamer987:
i can't find the update tool, i only found an usb burning tool and a flash tool, both of them don't have update.exe
[Google TV General] npjohnson:
https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/khadas/utils&ved=2ahUKEwj546622Kf0AhWyVTABHTpRAGIQFnoECAQQAQ&usg=AOvVaw1MLXFgPTBCrWN7jZxZhtRv
[Google TV General] ROM_gamer987:
I get error, Libusb0.dll was not found
[Google TV General] npjohnson:
Install libusb-dev
[Google TV General] ROM_gamer987:
Tried on linux (arch) and it said No [WorldCup Device], Device is on the setup screen (Idk how to get it in fastboot/bootloader)
[Google TV General] npjohnson:
Hold the button on the side and plug it into your PC.

The sudo ./update bulkcmd fastboot
[Google TV General] ROM_gamer987:
Hey i managed to flash the rom, im still having the issue that my remote won't connect

I took a logcat and it saw a bunch of Bluetooth errors, could you look at it?
[Google TV General] ROM_gamer987:
cat

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com
[Google TV General] npjohnson:
I get the same errors in my Sabrina. I just don't know how to fix it.

Contributions welcome if you figure it out.

Edit: wait you have remote issues on an onn box? That's weird, mine works fine...
[Google TV General] ROM_gamer987:
I'm guessing that the new update included some kind of Bluetooth update that broke stuff, Maybe flashing older stock will work?
[Google TV General] npjohnson:
Nope, I'm on the newest firmware.

I'll look at the log later tonight.
[Google TV General] ROM_gamer987:
How can i skip setup? i can't edit build.prop when booted to setup because adb root needs to be toggled and on recovery idk how to mount system to edit build.prop, how do i skip it?
[Google TV General] npjohnson:
You don't.

Use the button to navigate recovery to advanced, then mount system, then all partitions are mapped and you can Mount them manually.
[Google TV General] ROM_gamer987:
So i mounted system and then used mount -o remount,rw /mnt/system, i tried adb push to add the line but it said the device was out of storage, i then tried echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop, It didn;t give any errors but it alsso didn't write anything to the file, now my build.prop is wiped because adb push wiped it, wat do i do?
[Google TV General] npjohnson:
Reflash the ROM, on dynamic devices you'll need to make space first, go delete some useless app or component to make space.
[Google TV General] ROM_gamer987:
I have been searching for something to delete, can't find something
[Google TV General] npjohnson:
oh, that setupwizard prop doesn't work on ATV anyway. You can just delete SUW.
[Google TV General] ROM_gamer987:
I deleted some fonts and added the prop, it resulted in a boot loop, i also tried to disable setup wiz with adb but it was still there, Where do i find the setup wiz to delete it in adb shell?
[Google TV General] npjohnson:
Just rm it off the product partition.
[Google TV General] ROM_gamer987:
Where is product partition? /product is empty
[Google TV General] npjohnson:
Like I said, you need to mount system in recovery, then the partitions are mapped and you can Mount them and do whatever you want.

But honestly it's much easier to just go through SUW.
[Google TV General] ROM_gamer987:
i mounted system and checked /product /mnt/product and /mnt/system/product, all of them are empty, also hom am i supposed to go through setup when the controller won't connect?
[Google TV General] npjohnson:
Just wait for me to look at it at this point.

You need to mount the product partition by hand, it'll just be easier to wait until I can debug it.
[Google TV General] ROM_gamer987:
k
[Google TV General] retyre:
Which build of LOS are you on? Are you just looking to edit /system/build.prop?
[Google TV General] ROM_gamer987:
I'm on latest build that was released, np said that the prop won't work on atv so i need to mount product on lineage recovery and delete the setup wiz or wait until he looks at it
[Google TV General] retyre:
Can you link to that build? I'm assuming you're grappling with a sabrina? If you let me know, I will PM you a link to an edited super.img with SUW gone from /product/app/ and some free space in the dynamic partitions (to do with them as you please).

We are assuming deleting SUW will let you in without completing setup, but I'm not sure.

Alternatively, why can't you download product.img (from the same location as the build), mount it, delete SUW, and flash it in fastbootd?
[Google TV General] ROM_gamer987:
This is the build https://updater.oddsolutions.us/#/devices/dopinder/builds Im using a dopinder, The product partition is on a .new.dat.br file and idk how to extract it and flash it, if you can give me a build without the suw i would really appreciate it, im assuming that after i skip setup i will be able to use a usb keyboard to navigate to Bluetooth settings and connect another remote or use a usb remote with an otg adapter
[Google TV General] retyre:
Look here: https://download.ods.ninja/Android/lineage/dopinder/. If you can't mount the .img and delete SUW, post here and I will PM you the new product.img.
[Google TV General] ROM_gamer987:
Mounted the img, only found SetupWraithPrebuilt, is that the correct setupwiz?
[Google TV General] retyre:
Yes
[Google TV General] ROM_gamer987:
welp idk how to repack the img after mounting it, the binary is only for ubuntu im on arch
[Google TV General] retyre:
Why go there? Unmount the image, boot to fastbootd, fastboot flash product product.img, and fastboot reboot.
[Google TV General] ROM_gamer987:
Does the changes I do to the mounted folder affect the file? Do I need to use img2simg?
[Google TV General] retyre:
Yes and no.
[Google TV General] ROM_gamer987:
❯ sudo fastboot flash product /home/davi/Downloads/prod.raw

Invalid sparse file format at header magic

Resizing 'product' FAILED (remote: 'unknown command')

fastboot: error: Command faile
[Google TV General] npjohnson:
you're not in fastbootd. you're in bootloader
[Google TV General] seriousneo:
I'm currently stuck in the adb sideload screen, what commands do I do to get out of this? I'm trying to flash magisk but tried to reboot a few times when I couldn't figure it out. It keeps booting into ADB sideload version 18.1 even after unplugging.

Dopinder directly plugged into mac

Edit: I can do "sudo ./adb sideload /Users/dennis/Downloads/dopinder-qt.20210519-factory.zip", but I'm stuck in signature verification screen and got no OTG or keyboard for this.

This is what I see when "sudo ./adb devices"

List of devices attached

OUSA2115016557 sideload

Edit2: just going to flash latest lineageOS build on dopinder, that is processing right now with no sig verification. Now trying to figure out how to get back to stock with magisk. LineageOS booted just fine though!
[Google TV General] ROM_gamer987:
Extract stock zip file and run the flash script
[Google TV General] ROM_gamer987:
Update: I managed to skip setup, Bluetooth is still broken tho, Could you check the logcat i sent a few messages above? It's kinda weird that it can find the devices but not connect to them
[Google TV General] seriousneo:
Thanks! I wasn't able to get the script to run but I was able to do each command one by one and now I'm back to stock but have to setup now and do the update.

I saw this guide on what I should be doing, #128, is it okay to use the boot.img from the stock zip? And where do I install Magisk to, I have the magisk zip file. What's the easiest way to do stock root? My only objective is to be able to remap those 4 app buttons below on dopinder remote
[Google TV General] ROM_gamer987:
Tbh even with root i doubt you will be able to remap them, if you still want root try to fastboot boot the lineage recovery and sideload the magisk zip
[Google TV General] seriousneo:
I am now having trouble getting beyond the first steps of the wiki.

platform-tools % adb reboot bootloader
platform-tools % fastboot devices
OUSA2115016557 fastboot
platform-tools % fastboot flashing unlock
OKAY [ 0.048s]
Finished. Total time: 0.051s

My devices does not reboot nor does it wipe at all. I had successfully done this step last night but when I flashed stock everything back I have trouble. Does this mean that my bootloader is actually unlocked still? I have to pull power to reboot fine into stock, but when I try to flash recovery, that shows as finished but when I try to reboot into recovery via "fastboot reboot recovery" it shows as finished but actually doesn't reboot anything. "fastboot reboot" works to go to normal, but not "fastboot reboot recovery" after flashing

platform-tools % fastboot flash recovery /Users/dennis/Downloads/lineage-18.1-20211118-recovery-dopinder.img
Sending 'recovery' (24576 KB) OKAY [ 1.165s]
Writing 'recovery' OKAY [ 0.858s]
Finished. Total time: 2.182s

fastboot reboot recovery
Rebooting into recovery OKAY [ 0.006s]
Finished. Total time: 0.006s

And when I do "adb reboot recovery" after booting up normally it takes me to the stock recovery, so lineageos recovery flashing didnt work

Install LineageOS on dopinder | Odd Solutions Wiki

wiki.oddsolutions.us

Edit: all good now. I followed this guide step by step after I figured out recovery issue #164
[Google TV General] seriousneo:
Hey I get no director found when I try to do "su adb push onntvremapfolder /data/adb/modules" How can I see this folder?
[Google TV General] npjohnson:
You're running adb as root for no reason.

you need to enable adb root in dev settings, then run adb root and adb remount before you push things.