yashsingh1/xdaforums huggingface dataset:
[Google TV General] :
This should probably be discussed in a different thread. But to answer briefly, the post to which you responded was merely about modern amlogic SoCs (such as the X4, Y4 and others) replacing "v2 usbburning mode" with "Amlogic DNL protocol". Askey's sti6220d315 (verizon stream tv v2) is one device to which this applies. I describe this slightly more thoroughly in this thread.

Whatever "factory" mode may be used to recover a device is separate and apart from other amlogic features.

The sti6220d315's bootloader is readily unlocked, and the device does not use secure boot or an encrypted bootloader. The button on the top of the device will force an adnl (Amlogic DNL protocol) connection if the usb c port is connected to a host computer, or will reboot to recovery if the usb c port is not connected to a host computer. Note that the usb a port can only be used for peripherals, not for a slave connection.

Overall, running an alternate os on the sti6220d315 should be possible and straightforward, but I haven't done it yet.
[Google TV General] npjohnson:
People who brick their Sabrina - here's a gift: https://github.com/npjohnson/sabrina-unlock/blob/main/repair.sh

This will repair pretty much any Sabrina that is broken.
[Google TV General] npjohnson:
Additionally, dopinder, wade, and Deadpool all boot now.
[Google TV General] curryrice71:
Thank you! I see this build from 2022-05-15 lineage-19.1-20220515-UNOFFICIAL-dopinder.zip

should I wait until the next build comes out to try it on dopinder?
[Google TV General] TabascoJoe:
Latest 19.1 image and recovery are working...

It was a lot of trial and error (dont ask)

but after an hour the dopinder is working

ty
[Google TV General] RDS5:
how?

im on wade and ive been waiting for a way to get 19.1 working with its recovery, since i dont wanna fiddle with the 18.1 recovery.

how did you manage to do it? unless its device specific...
[Google TV General] TabascoJoe:
I think it is...

The instructions talked about flashing dtb and the dtbo partition, so I did that...

Other than that, dont ask... a lot of reboots and reflashes to get to the recovery, but finally it worked

Proof attached
[Google TV General] :
Were the contents of the 20220515 url links for these builds changed to contain the fixes, or should we wait for url links with a later date?
[Google TV General] npjohnson:
The existing builds were 100% functional.

People weren't flashing dtb/dtbo. Absolutely necessary.

I put it in the wiki.

The only _truly_ broken one is Sabrina.
[Google TV General] curryrice71:
I'm trying this on my Walmart ONN 4K box/dopinder. I got to this point in the steps:

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

I'm not sure it works though, I get this:

[update]No [WorldCup Device] device after scan

[update]ERR(L1095):can not find device

I ran the steps exactly up to that point. It's not bricked and I can reboot back into Android TV. It's running 1.01.35 firmware. Is the firmware too new?

Since the output from the update bulkcmd fastboot command didn't look right I just stopped at that point.

Right before that step it says to go into burn mode. Does 'adb reboot bootloader' put it in burn mode or do i need to hold down the button or something when i power it on?

Thanks in advance for any advice.
[Google TV General] endera:
LineageOS for Radxa Zero

Thanks! I will try this later.

forum.radxa.com

I tried this image, but it automatic boot into bootloader when power pluged in. I tried ‘fastboot reboot recovery’ and ‘fastboot continue’, and it reboot and boot into bootloader again. Then I ‘fastboot boot lineage-19.1-20220515-recovery-radxa0.img’, it successful boot into Lineage OS 19.1 recovery. But when I ADB sideload lineage-19.1-20220515-UNOFFICIAL-radxa0.zip, recovery had error again, said 'update_dynamic_partitions(package_extract_file(“dynamic_partitions_op_list”))'How to solve this?Thanks.

https://forum.radxa.com/uploads/default/optimized/2X/e/e25007459c3373d4c718710ac88a58bd7ce7e0cd_2_690x388.jpeg
[Google TV General] espchl:
Thanks a lot for all your help! Had no luck getting fastboot to work. But good to know abou the power of burn mode.
[Google TV General] espchl:
Thanks for your gift!

It's somehow not working for my Sabrina. Does not enter fastbootd and keeps bootlooping. But it got a new led blinking pattern after using the repair script and the led is turning white for the first time.

Do you have any idea?

Thanks
[Google TV General] npjohnson:
So weird.

In the script, if you run everything up until the first "update" command after the bootloader is loaded, you will be in burn mode and can flash whatever you want.
[Google TV General] Wagmans:
Thanks. I was unable to to PM you, that's why I posted this here.

I'll start another topic on it- these boxes are pretty much everywhere for cheap, as Verizon is giving them out for free, so I'd like to be able to try and get Coreelec up and running on it.

Be interesting to see if I could get get Lineage running on it as well.
[Google TV General] :
I will try installing coreelec after I finish with the firetv gen2 cube. I was able to snap up more than a dozen of them for next to nothing, which is a good price for X4 devices.

As I said before, the device is trivially unlockable, rootable, and will run modified system images with avb/verity/verification (patched vbmeta) all disabled. So, you should be able to just dive right in and have at it. If the factory device trees are compatible, it should be as easy as falling onto a log.
[Google TV General] Wagmans:
I was fooling around with it earlier. I was able to get it into fast boot no problem but I got stuck there, I couldn’t figure out how to unlock it. I’m sort of a novice when it comes to this stuff but I’m learning. I’m sure you’ll have more success than me.
[Google TV General] curryrice71:
I got this to work on dopinder, but chromecast wouldn't work with any app except maybe youtube so I already went back to stock. It was a fun exercise, look forward to future developments with this.
[Google TV General] npjohnson:
Fun fact - GXL/GXM support is incoming. VIM1/VIM2/ADT-2 to start, but people should be able to use these to bring up dev boards and china boxes with nominal effort.
[Google TV General] forart.eu:
Thanks for your work, @npjohnson !

Maybe you're not interested in, but - expecially for upcoming "privacy-risky" china boxes support - would be extremely interesting to have a "Google-free" (formely LOS+Microg) builds too.

We posted the idea @ \e\ community forums too:

\e\ for Android (TV) boxes too?

Nowdays many peoples has smart TVs/boxes at home, many of them produced in China and with “unclear” Android firmwares. It would be interesting to have a “free as in freedom” firmware(s) to clear them up from bloatwares, Google services and (maybe) stock mal/spyware. There’s already some...

community.e.foundation

Thanks again and hope that inspires !
[Google TV General] eauyong:
Go for those Askey (Asustek subsidiary) Taiwan boxes such as Onn and Dynalink TV boxes also Verizon.
[Google TV General] npjohnson:
Sorry, but their whole core system doesn't support Android TV GMS at the moment
[Google TV General] ubergeek77:
Is there any more info on this? Looking to install LineageOS on my sabrina, but I'm not sure exactly which builds are broken, or if any of them are safe to install. Does anyone know which of the builds listed on the build page are safe to install, if any?
[Google TV General] npjohnson:
No, nothing 19.1 is for Sabrina at the moment - I need to debug it.
[Google TV General] ubergeek77:
Thanks! I assume that means the 18.1 builds should be safe until then.
[Google TV General] npjohnson:
I mean I haven't built or cared about 18.1 for g12 since 19.1 went live. So, maybe. idk.
[Google TV General] ThrowAway420:
If you don't mind me asking what did you do to get LineageOS to work, as I'm pretty much stuck at where your previous post was at. Running sudo ./update bulkcmd fastboot gets me to the same error.

[update]No [WorldCup Device] device after scan

[update]ERR(L1095):can not find device

Edit: also I found something interesting with my device (ONN 4k box). It wont boot into Burn Mode unless it only has power, no transferring data. I tested this by powering off my PC then plugging in a cable that can do both power and data transfer, then powering on my PC while holding onto the button on the side of the TV Box, I successfully got me into "Burn Mode". But if I had just plugged the cable into my device while my PC was still on and while holding onto the side button, I would just see the ONN logo and nothing else would happen.

Thank you guys in advance
[Google TV General] curryrice71:
so from here:

[update]No [WorldCup Device] device after scan

[update]ERR(L1095):can not find device

if you say fastboot devices and it's still shows a device, this is what I did:

fastboot flash dtb <dtb>.img

fastboot flash dtbo <dtbo>.img

fastboot flash recovery lineage-19.1-20220515-recovery-dopinder.img

fastboot boot lineage-19.1-20220515-recovery-dopinder.img (yes, I couldn't get it to boot itself into recovery from here so i booted from the file)

then if you get it into the lineage os recovery then you can do the:

adb reboot recovery

then hopefully it will boot into recovery from the device itself, then if it does you can

then from there I sideloaded the full lineage os build
[Google TV General] ubergeek77:
This question is a few months old, but since I just figured this out, might as well answer it for everyone.

You can easily skip the Google sign in during setup, but you will need Magisk and the Magisk app installed. Get the latest Magisk .apk, flash that .apk in Lineage recovery (the .apk is a flashable zip), then reboot.

You should see the Setup Wizard once you reboot. Use `adb install` to install that same Magisk .apk, then `adb shell` into your device. Enter the `su` command, and you will see a superuser prompt on your device. Grant it so that the shell has root privileges.

Enter the command `setprop ro.setupwizard.mode DISABLED`

Finally enter this command: `am force-stop com.google.android.tungsten.setupwraith`

If successful (and if I didn't forget anything, I did all this testing last night), you should immediately be dropped into the launcher. Even if you reboot, you will never see the setup wizard again unless you factory reset. No account needed!

This only works so easily on Lineage because it has adb enabled unconditionally, meaning you don't need access to the Settings app first. You *can* skip setup in a similar way on the stock builds, but it's a lot harder - there's no way to get an adb shell on stock during setup, even with Magisk. So you have to unpack the system.img from stock, remove the write protection from it, enlarge it, mount it, add that build property, and finally flash it... it's a bit involved. But it does work! And you can flash the clean system.img back if you wanted to once you've skipped the setup.

I know this is the Lineage thread, but I should also note that the launcher on the stock, non-Lineage image, will aggressively force you to sign in even after you skip the setup. It literally won't let you use it without an account, it will just keep spamming that sign in prompt every time you close it. But, you can get to system settings from here to enable adb, so from there you can just disable the stock launcher and use pretty much whatever launcher you want.
[Google TV General] Big Dumb Object:
It would be great to have a full-functional Chromecast on all these ROMs, but as a workaround, you can try to use Chromecast receivers in form of a third-party app, like CastReceiver.

I'm still looking forward to eventually getting a choice between both ATV and Tablet flavors of this ROM, which automatically leads to the release of LOS for MicroG.
[Google TV General] pddc:
Dopinder with 19.1 doesn't seem to support ADB over Ethernet. Any way to enable it? I can ping unit fine over Ethernet.
[Google TV General] npjohnson:
Enable ADB over network in dev settings?
[Google TV General] kennkanniff:
I have the same problem. I compilled an aml_upgrade_package.img from lineageos source but it is nearly 400 megabytes smaller so I am afraid to flash it.
[Google TV General] ozkaya:
guys, would it be able to program the G10 remote (the one that comes with Onn 4k box and many other Chinese Units) to send out IR commands to control TV etc? I read online that if you have Chromecast remote, anything you program into it, transfers into G10 remote. I don't have a Chromecast remote but maybe we can trigger the activity which programs the remote.
[Google TV General] pddc:
Not sure If I'm being blind, but cannot see it there for the life in me!!!
[Google TV General] RDS5:
ok my dynalink 4k (wade) is working fine but theres one small problem.

remember how you say "only a small amount of apps on android tv actually care about safety net"?

funny thing is, bell apps do. they give me either a "device is rooted" message or a fake "hdcp error" (even tho hdcp is working since netflix and other apps do work).

now how can i stop it from detecting me? i have already installed universal safetynet fix and magisk hide props, and both didnt fix it.

maybe im not using them correctly either, im not sure, but i really need help getting this thing to bypass safety net.
[Google TV General] pddc:
got it. setprop persist.adb.tcp.port 5555 from the adb shell did the trick
[Google TV General] npjohnson:
you didn't include gapps, I did.
[Google TV General] kennkanniff:
Thanks. Can you share u-boot.bin for M5? I used a random one I found on the internet but the image does not flash.
[Google TV General] npjohnson:
Ah yeah, crap, those are prebuilt aren't they.

I'll publisize the repo later.
[Google TV General] DJFLAME210:
anyone have any 19.1 lineage builds for Dopinder... seems like they were taken off of the lineagewiki odd solutions website... or it could be down at the moment on my end but anywho TIA
[Google TV General] npjohnson:
It had grown _way_ to large. Had to purge. with that said, I plan on building for all devices tonight.
[Google TV General] DJFLAME210:
hell yeah!! much love my guy.... ill be up waiting for sure then lol
[Google TV General] endera:
Odd Solutions Downloads

updater.oddsolutions.us
[Google TV General] RoyaldArmer1331:
Hello, I'm trying to install LineageOS on dopinder and can't find the dtb and dtbo files from this link from the wiki: https://download.ods.ninja/Android/lineage/dopinder/

Are the dtb and dtbo files not required anymore or are they currently being built right now?
[Google TV General] npjohnson:
Builds are in progress
[Google TV General] Garrett Cornwell:
Builds still in progress by chance? Just checked and the folder still looks empty here: https://download.ods.ninja/Android/lineage/dopinder/

I cannot thank you enough for supporting all of these devices! Greatly appreciated!
[Google TV General] npjohnson:
Yup, give it 2 days. TVs last
[Google TV General] Stricted:
to get a working u-boot.bin for the m5 do the following:

git clone https://github.com/Stricted/deadpool_u-boot_build ~/deadpool_u-boot_build
cd ~/deadpool_u-boot_build
./build_m5.sh
cp uboot-bins/u-boot.bin <path to android source>/device/bananapi/m5/factory
[Google TV General] kennkanniff:
Thank you. I can flash the image now. It still boots straight to fastboot though. Any idea why?
[Google TV General] Incognit420:
I can't get to recovery with onn tv box. It stays at the onn logo after fastboot reboot recovery and fastboot boot recovery.img.
[Google TV General] npjohnson:
Don't do that.

reboot to bootloader

fastboot flash dtb and dtbo

Then fast boot boot recovery.img.

It will work fine.
[Google TV General] rub1k:
Just got a dopinder from Walmart and read through all 48+ pages of this thread -- thanks everyone for all your contributions.

Before flashing the latest 19.1 LineageOS build, is there anything I should (or shouldn't) do with the device? Should I plug it in and let it update to the latest update (if one is available, depending what build it shipped with)? Or does it really not matter one way or another if I'm going to flash LineageOS?

Just want to make sure they didn't do something screwy like lock the bootloader and/or disable unlocking, etc.

Thanks in advance.
[Google TV General] npjohnson:
Update to newest build on stock.

Enable ADB.

adb reboot bootloader

fastboot oem 'setenv lock 10101000;save'

fastboot reboot bootloader

fastboot flashing unlock

fastboot flash dtb lineage-dtb.img

fastboot flash dtbo lineage-dtbo.img

fastboot flash recovery lineage-recovery.img

fastboot reboot-bootloader

fastboot boot lineage-recovery.img

Use button to select "Factory Reset", "Wipe Data", once complete, "Apply Update", "From ADB"

Then adb side load /path/to/lineage.zip, click reboot, profit.
[Google TV General] Incognit420:
Thank you! I was missing the dtb and dtbo. I'm at another problem, los19 turns off and remote won't turn it back on, have to unplug as well power button doesn't work on tv. So I flashed the stock firmware, but now I get stuck at onn logo. I can still get into bootloader and stock recovery but I don't want los until it's stable. Thank you.
[Google TV General] npjohnson:
Remote works fine here - not sure what's going on.
[Google TV General] Incognit420:
Yeah my remote won't control tv input, vol and power. I can power off the onn but can't turn it on. I messed with the CEC settings and get vol to work but it controls vol only on the onn, not the tv. Well I try flashing again and see if it works.

Edit: I get mount udisk failed in stock recovery.
[Google TV General] npjohnson:
Boot lineage and turn off CEC in settings. Bet it just works then
[Google TV General] Incognit420:
I'm trying to reinstall lineage but when trying to flash dtb, dtbo I get "error: cannot determine image filename for lineage-19.1-dtb.img".

Edit: I figured it out, duh I had the wrong command when I needed to use fastboot flash dtb dtb.img lol I was forgetting to put the first dtb in the command. I did get back to stock but the batch file in the zip did not work I flashed all stock files one by one and left out raw boot and only used flash boot boot.img
[Google TV General] RDS5:
how would i compile and flash an overclocked kernel to wade?

im not sure how id overclock this device since its not qualcomm or anything so there arent any tutorials on making a custom overclocked kernel for them.
[Google TV General] npjohnson:
because you aren't specifying to flash to dtb.

fastboot flash dtb filename.img
[Google TV General] npjohnson:
I really wouldn't - we have both a tight power budget and thermal budget already pushes limits. Bad idea.
[Google TV General] RDS5:
oof. in terms of thermal budget im ok because i added another heatsink to the inside and strapped on a fan onto the box, but if i use a stronger power adapter, would that fix it? or are the internal circuits just underrated for such a thing, so they wouldnt bother pulling more amps from my stronger power adapter?
[Google TV General] npjohnson:
You can't hook up anything more than what we have powerwise
[Google TV General] npjohnson:
Alright, I did moved u-boot somewhere accessible.

You can now sync https://github.com/TheMuppets/proprietary_vendor_amlogic to vendor/amlogic and boot, it will auto include and all work.
[Google TV General] kennkanniff:
Still stuck at fastboot.
[Google TV General] Stricted:
i will run a build shortly and check whats going on
[Google TV General] Spusuf:
Just installed on wade, heres whats bugging me:

- Casting does not work, it does not show in list of devices nor Google home through automatic or manual discovery

- No option to "stay awake" (stay connected to wifi when tv off to enable casting to turn on tv like chromecast)

- No option to map IR remote (need for IR power on using stock remote), are there any android tv compatible apps to map IR signals to button presses and would that even work for device power on. (again not an issue if device was staying awake and just sent out a CEC command to power on TV)

Besides that I love it, extremely snappy considering the hardware. Android 12 looks exactly the same as android 10, would love some tweaks to get rid of the spam ads on services I dont use, but I understand thats out of the scope of this project.
[Google TV General] forart.eu:
...out of curiosity: when will be possible to test a "generic" build for S9xx-based devices ?

Thanks for your work !
[Google TV General] Meliorem:
So I've registered an account because I've apparently (soft / hard ?) bricked my second dopinder device. After reading all 49 pages I thought 19.1 recovery was fixed for dopinder but maybe not, in my case at least. Although, that may be my fault. I tried going by the instructions on the wiki (again) but I get stuck at a certain point. I also have the problem another user posted about where after trying to run the update script, it supposedly fails with:

[update]No [WorldCup Device] device after scan
[update]ERR(L1095):can not find device

I tried opening the script in various text editors (nano, Kate, Libreoffice Writer) and it's mostly gibberish, can't make much out, so how others have run those commands one by one, IDK. (I'm on openSUSE Tumbleweed Linux BTW -- no access to a Windows machine.) Based on some stuff I read in here, I thought moving on to flashing dtb & dtbo might have worked and I flashed those successfully. I flashed LOS 19.1 recovery successfully, but trying to reboot by itself into recovery OR booting the recovery img file directly don't work. It just sits on the onn screen in perpetuity (I waited 10 minutes both times). So I'm guessing, in my case at least, either the 19.1 recovery doesn't work (couldn't find the 18.1 recovery anywhere), or because the update script didn't work it prevented me from progressing to recovery.

My current state is stuck on the onn screen (trying to boot to burn mode just results in this same current state -- stuck on the onn screen). Adb and fastboot no longer see the device at all, so I can't interact with it anymore.

I also tried the instructions in comment 938 . However, as I said, it doesn't work. It wouldn't boot to 19.1's recovery by itself or by booting the img file directly, so no luck there.

Suggestions?

Maybe if I can do something to be able to flash 18.1 recovery and install 19.1 that will be enough to get me up and running.
[Google TV General] ROM_gamer987:
Download lean back keyboard and press on spacebar, then select show software keyboard when USB keyboard connected, then switch back to gboard
[Google TV General] Online Gravy:
successfully installed the 8/12 build and managed to sideload magisk with a powered usb hub and a keyboard
[Google TV General] Online Gravy:
It seems like in app downloads are extremely slow, vanced manager times out while downloading all the splits it needs and magisk can't even check safety net
[Google TV General] meber:
Can you link the powered usb hub - I was unable to sideload magisk with my OTG cable.
[Google TV General] Online Gravy:
its some generic hub i found awhile ago. only reason i was able to sideload magisk was because the box rebooted to sideload mode after i unplugged it to connect it to the host side of the hub. just put magisk on a flash drive and flashed it from there
[Google TV General] meber:
Thanks I'll have to figure how to install the zip off of the flash drive.
[Google TV General] Big Dumb Object:
Perhaps I'm not fully grasping your need, but wouldn't this cheap little thing work for you? I saw it in action at one of the YouTube reviewers, and seems it served him well.
[Google TV General] Online Gravy:
What i did was connect the device to my laptop through my powered USB hub. From there i used ADB to reboot into sideload. Then i unplugged the hub from my laptop and plugged the host cable into the device with an OTG adapter. When it powered on it booted back into sideload, not sure why or how, so i took the opportunity to plug in a keyboard and flashdrive formatted as fat32 with a magisk zip on it. Then i selected the apply update option and choose the usb option, from there i was able to select the zip file and the option to ignore the signature check