yashsingh1/xdaforums huggingface dataset:
[Google TV General] edwrapxda:
Edit: I went back to Lineage after discovering stock refused to stay connected to a wifi network if there wasn't an outgoing internet connection. In the process, I discovered most of the issues I had prior were no longer occurring. The only thing I had changed in the interim was updating to the latest stock firmware, which I didn't think would have an effect on anything in Lineage.

The only problem I'm still having is the slight video stutter when using both framerate matching and hardware acceleration. Either seems to work fine by itself.

As for the actual procedure to revert to stock, I could never directly fastboot flash the various partitions, as that would error out. Using the aml-flash-tool to partition worked for most of the partitions, and then rebooting into fastboot would allow all of the fastboot flash commands to work. you need to advanced reboot into the bootloader, then the flash-all script commands will work. I was previously going into fastboot mode from recovery, which doesn’t work correctly.
[Google TV General] npjohnson:
which device?
[Google TV General] enfermo:
Hi

Need to ask for a micro usb OTG hub

I like to have

Ethernet Adapter​

3 or MORE USB Ports​

USB OTG Hub​

Micro USB OTG Cable HUB​

Powered Network Adapter​

I find This OTG HUB Adapter does not support “Fast Charger”(Voltage>5V or Current>2A),otherwise the OTG HUB Adapter will heat up and burn out.

will appreciate the time and suggestions
[Google TV General] edwrapxda:
Sorry, forgot to mention - wade
[Google TV General] talksickisil:
none of them are going to charge your devices. OTG will not support charging. Power and data transfer only with an OTG.
[Google TV General] talksickisil:
just sent you a meager paypal donation sir. I didn't want to mention it here but I couldn't figure out how to leave a note. Thanks for your work on this project.
[Google TV General] npjohnson:
thanks!
[Google TV General] activadroid:
Connector signal levels = TTL. I used a USB to TTL converter based on FTDI Chip (bought on eBay). A company called JST makes tiny connectors, I am not sure if the connector on Wade is one of theirs. On Onn/dopinder you have to solder (and it is easier with a REALLY small tip on iron, and stereo headset magnifier with loupe (Harbor Freight $6 or better similar). For the Dynalink/Wade, I found the exact matching connector plug from an old Ego 56V dead battery internal wiring harness (for cordless yard tool) I took apart years ago, and soldered the wires to the FTDI board. (the newer Ego batteries all use larger connectors, unfortunately, so I don't have spare connectors to loan or sell)
[Google TV General] talksickisil:
No worries there. Due to having the OTG hub and a flash drive on hand , I was able to flash the official lineage and gapps on wade. Anybody with an OTG and a flash drive or sd to usb etc, can flash the lineage rom directly from the lineage recovery. I sort of figured this out randomly. The onn doesn’t turn onn anymore. Literally dead. Side note to anybody reading: dynalink/wade is 29.99 now. Like a week after I bought it they dropped the price.
[Google TV General] talksickisil:
I forgot to mention that my onn dying I believe was caused by me accidentally leaving it powered on when it was stuck on the boot screen for hours I switched tv input to my Apple TV then kinda forgot about it, went to bed with it on etc. I’d love to bring it back to life as some type of side project hobby. But I don’t think there’s much hope. Unless you or anybody else has some good ideas. Thanks for explaining that connector. I am nowhere near a hardware expert. I spent quite a bit of time trying to figure out what it was called and if I could do what was mentioned on the early pages of this thread without soldering.😂 no luck even finding out what it was called , let alone what can I do with it. Until I got my mid tier galaxy tab a7 a little over a year ago, I hadn’t even rooted or unlocked any android device since like 2015. It’s kinda cool to see what had changed and what hasn’t since then.
[Google TV General] talksickisil:
Hopefully I’m not taking the thread captive. Few days in, the only bug I’ve noticed is right after I reboot, it connects to my wifi like usually, but all of my apps tell me I don’t have internet until I toggle wifi off and then right back on again. Not really a huge issue. It only appears after booting. I know this isn’t the right place to officially report a big, I just wanted to mention it and see if anybody else has this going on. One other weird thing is if I hold the home button down longer than a half second, Google assistant pops up. However, I’m using dopinder remote, paired with wade. I can’t stand wades remote.
[Google TV General] papashango92:
Anyone have any idea on how to install magisk on stock dopinder? Anything 25 or above causes a bootloop and anything under grants no root access. Applying to boot.img via app then fastboot flashing.
[Google TV General] edwrapxda:
On wade, I went back to stock (edit: and updated to latest, like the one time this worked) to test something, and then back to Lineage and auto HDR isn’t working again (HDR is on all the time if enabled on TV). Why would this vary from install to install? Is this working for other people?
[Google TV General] npjohnson:
likely some magic persistent settings - I'll have to look into it.
[Google TV General] papashango92:
Thanks, I was following a different tutorial that didn't have the checksum step, it was either that or me using my phone app to patch and not the box itself. I found a patched boot.img posted in the thread and that worked.
[Google TV General] bryantdl7:
FYI - Anyone with a dynalink 4K that gets bricked, this is the full steps I took to unbrick it. Special thanks to npjohnson for letting be bug him with various technical questions out of the blue!

=====================

How to unbrick dynalink 4k if stuck at dynalink logo:

=====================

Assumptions made:

- You're on ubuntu

- All scripts run as root (sudo -iu root)

- You can see your amlogic device listed running lsusb (also as root!)

1. power off unit by unplugging

2. plug unit back in to a computer while holding side button

3. download and install https://github.com/khadas/utils/tree/master/aml-flash-tool/tools/linux-x86 on ubuntu

4. go to the path of /home/your-user-name-here/Downloads/utils-master/aml-flash-tool/tools/linux-x86/ in a terminal window,

5. run these cmds. you can get these files from the official lineageos page if you dont have them already.

Note: you need to go to your own username, and of course in the future a different date will be on the recovery file, make sure to copy the file name from your specific dtb file.

./update partition dtbo /home/bryantdl7/Downloads/dtbo.img
./update partition _aml_dtb /home/bryantdl7/Downloads/lineage-19.1-20221024-dtb-wade.img
./update partition recovery /home/bryantdl7/Downloads/lineage-19.1-20221120-recovery-wade.img
./update bulkcmd fastboot

6. verify you are in fastboot by doing:

fastboot devices

, it should display a device in fastboot.

7. run

fastboot reboot bootloader

as a sanity check, sometimes it half loaded for me.

8. download the factory images via OP's post

9. run the flash all script inside the factory image.

10. You are unbricked!
[Google TV General] papashango92:
What's the best way to navigate adaway in stock dopinder because the remote isn't cutting it.
[Google TV General] bryantdl7:
Get a mouse which supports bluetooth and connect it to the android tv. You could also use a USB mouse if you have a USB OTG cable laying around.
[Google TV General] fepij52921:
I am trying the Wade instructions: https://wiki.lineageos.org/devices/wade/install

There two things that fail for me right the way.

When trying fastboot devices on the first step, I don't get an answer, and the devices has the triangle on the device manager, where should I look for other drivers for this?

The device doesn't have a OEM unlock in Developer Options (Just the USB debugging)

I am testing this on a Windows Machine if that changes anything.

Another semi relate question, does it matter here that the date for firmware is older than the build: https://download.ods.ninja/Android/firmware/wade/dtb/
[Google TV General] fepij52921:
That's the exact driver I have, I already tried as admin and tried rebooting the windows machine.
[Google TV General] fepij52921:
Are you using it with a mouse? I sideload them it on stock, F-droid doesn't seem to install correctly at all and in case of of Aurora I can't install apps since input from the remove doesn't allow me to select the apps.

As for alternatives, I have not test it, but there is this other F-droid frontend: https://github.com/NeoApplications/Neo-Store/
[Google TV General] joaocandre:
Is a rooting guide available anywhere for wade? Would like to try to somewhat debloat the stock ROM before flashing LOS.
[Google TV General] S1ngl3-x:
I am using Aurora store with the provided remote. It's however really UX unfriendly because I need to guess the inputs. Navigation is not highlighted in any way so I basically click OK to get my cursor location, go back and the continue searching. I've had best luck with search and then install functionality. The gener dashboard, categories and so on just didn't really work.
[Google TV General] matrix200200:
After having tried several times to follow the guide for dopinder, now my device is stuck at boot screen.

Fastboot doesnt see the device.

What are my options?
[Google TV General] matrix200200:
No.

Neither adb, nor fastboot.

Using Windows 10 (but can try Linux).

And no, device manager is not seeing the usb device.

The last option is to open up the device and use a usb to serial to reflash it, I guess?
[Google TV General] matrix200200:
Wow thanks.

I got into recovery!

Now I need to search, what to do next.

I actually searched the thread for "stuck at boot logo" and didn't find anything useful

Wonder what I should have searched for.
[Google TV General] matrix200200:
Yeah I got it done.

LineageOS installed.
[Google TV General] papashango92:
Tubi is giving me DRM issues with some movies and not others on dopinder. Very odd.
[Google TV General] npjohnson:
Driver signing? What driver are you using?

The Google (signed) USB driver works fine for adb and fast boot.

Are you talking about the am logic driver? There are signed versions. But anyway, I'm just going to add a "Linux only" tag to the install guide for wade and dopinder.
[Google TV General] jim16127:
Searching 84 pages is daunting! Although I only needed to read page 1 and page 84.

There are a few steps in the wiki linked on page 1 for Dopinger - Walmart Onn UHD Box that WOULD NOT WORK.

On this page https://wiki.oddsolutions.us/devices/dopinder/install under Unlocking the Bootloader < Step 5. It states to enter this command

fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

The only way I could get it to work was typing each command separately

fastboot oem 'setenv lock 10101000;save'

fastboot reboot bootloader

fastboot flashing unlock

Then under Flashing the dtb and dtbo partitions it has 2 links for the required files...and one link is DEAD! The real place to find those 2 files is INSIDE the LineageOS zip that you download (the OS Install file. It's over 700MB) kudos @XDA-DB

Finally on Step 6 of Installing a Custom Recovery using fastboot. It states to type "fastboot reboot-recovery" but it never boots Recovery.

Power cycling the device then puts it in a state with NO fastboot or adb connection!

Unplug device. Hold button on device and slightly plug into PC until it powers on. When you see the Onn splash screen. Let go of button and fully plug in. You're now in Lineage Recovery that you installed. Again kudos @XDA-DB
[Google TV General] jim16127:
I have one final inquiry. What's the best method to enable root on these unofficial LienageOS builds. I do not see a toggle in developer options. Currently a few mouse clicks away from trying Magisks official github install. Just seems like extra since I just went through all that. Lol
[Google TV General] npjohnson:
So, running them separately doesn't make much sense. `&&` says "run this after that if it succeeds" - this is on linux?

DTB - ugh, I need to fix my upload scripts - will do

reboot-recovery - fixing it.

fastboot - does not need root/sudo at all - it needs proper u-dev which is detailed on the wiki. You don't need to set MTP - ADB works just fine? I'm using it now.

The half-plug thing is an interesting finding I will note the wiki - thanks.

Wade is way better - can't agree more. IMO IR remote of wade is better even.

Appreciate it.
[Google TV General] wright6432:
Thanks to all of the helpful comments here in the forum. I thought I bricked two devices, but I was able to unbrick them through the usb trick given by XDA-DB given here in the forums. Very appreciative. I successfully got lineage os to boot, but there are no apps. Only "Settings." I saw the lineage directions to load the GAPPS on first boot, but I was not planning to use GAPPS, so I did not think it applied to my situation. I was planning to sideload F-Droid. I have attempted several times to sideload the F-Droid apk now and I'm being given an error "E: Failed to find binary META-INF/com/google/android/update-binary." I'm assuming I should have sideloaded F-Droid before first boot. Is it going to be possible to sideload the F-Droid apk or do I need to start over from scratch?

The compleate readout is:

Verifying update package...

E: footer is wrong

Update package verification took 0.1 s (result 1).

E: Signature verification failed (I click "yes proceed with the installation" here)

E: error: 21

Installing update...

E: Failed to find update binary META-INF/com/google/android/update-binary

Install from ADB complete (status 2).

After this, I "Apply updates" and "Reboot System now," but there is no F-Droid app and nothing in the downloads folder. Any help would be appreciated. Thank you.
[Google TV General] jim16127:
@npjohnson

Thank you for reading and taking note. THAT'S AWESOME! The separating of commands only even popped in my head because of the error I kept receiving. "Status write failed (too many links)"

I didn't know how to slow the execution of commands aside from manually entering them. All of this was done on Windows 7 Pro. I failed to mention that. I tried in Linux first but couldn't connect to adb over USB. Not until I was attempting in a windows environment did I think to try without the otg cable connected. And voila! Again thanks for all the effort into this project!
[Google TV General] edwrapxda:
If you’re successfully in Lineage, just like with regular Android after turning on USB debugging, you can use adb to install any apk - “adb install <f-droid.apk>“

You can also toggle on adb over wifi in the developer options, after which you’ll need to “adb connect <IP address>”
[Google TV General] wright6432:
Wow, that was easy and yes it worked. For some reason I thought I had to sideload it. Thank you very much.
[Google TV General] viggi5k:
I just installed the newest nightly on a freshly bought wade.

Some notes:

- thanks for the hint with the button and usb cable to access recovery after the fastboot reboot-recovery not worked.

- don't use the included usb cable as it seems to not have data pins (at least eu version sold at amazon.de).

Sadly I cant activate Wifi. This seems to have been a bug in an older release. Any help on this?

thanks
[Google TV General] viggi5k:
Adding to this:

I wanted to downgrade LOS to the 1106 nightly but it denies because of SPL downgrade
[Google TV General] viggi5k:
lineage-19.1-20221113-nightly-wade-signed.zip fixed it
[Google TV General] jim16127:
Is it possible to enable exfat filesystem support? Whether natively or via root? Mainly I want Kodi or MrMC to read a 5TB external drive formatted to exfat and load local media? Any input is appreciated.

I specifically purchased this device to accomplish having a fully offline portable media library. If exfat cannot be accomplished. NTFS is my only other option (not prefered). I know the stock firmware would mount NTFS but I didn't test any further since I knew I wanted to ditch the stock rom.

Also, is there a method to remap the bottom 4 buttons on the remote?
[Google TV General] ChriMo:
I know/use Lineage OS 18.1 TV (A11) and it misses a function from smartphone Android ROMs

App Info > Permissions > Mobile data & Wi-Fi > Multiple Options to Allow/Reject

App Info > Permissions > Network > Allow/Reject

(or similar path/words)

It would interest me if this Lineage OS 19.1 TV (A12) has that feature to forbid WLAN/LAN(/MobileData) access for an App?

BTW: I saw A13 TV is released for ADT-3 devs, so maybe that iteration will have that option? Did not find it in the Release Notes.
[Google TV General] Slimshady997:
Is there an official version of dopinder or a stable one in which the streaming applications work?
[Google TV General] jim16127:
No there is not. From what I gather. If that’s desired then my understanding is get a WADE.
[Google TV General] talksickisil:
Now that a few more people have LOS installed I need to ask again: is anybody else facing wifi issues after rebooting? even though settings shows device as connected to internet , my device can’t utilize wifi unless I toggle off wifi and then back on again. this only needs to be toggled off then back on immediately after reboot. (Thanks button mapper for saving me the grief of getting to network settings every reboot at least is silver lining) I’m using the 11/20 official nightly build and g apps.
[Google TV General] zimmie:
Yes I have networking issues as well both wifi and Ethernet. I'm sure I'm not the only one.

I filed a bug but doesn't seems it was even looked at.

I'm pretty sure everyone has this problem.
[Google TV General] wright6432:
I successfully got wade running on my dynalink box. I set it up withoug any GAPPS and was going to attempt to do everything de-googled. I can not get kodi to work. Has anybody else had similar problems? I cannot even download any version of kodi other than the newest beta version, which is not suggested yet. I'm not sure if I need some sort of GAPPS to allow the framework for kodi. Any suggestions?
[Google TV General] talksickisil:
Personally, with the official build for wade I HAD to get gapps because without it I had zero apps installed. If you do the unofficial build instead I believe OP includes play store just so you can get up and running. What happens with kodi? You installed it and it just force closes when you open it or what?
[Google TV General] wright6432:
When I attempt to install any version of Kodi, other than Kodi 20.0, I get an error stating "This app is incompatible with your device." I've tried sideloading the APK, Aurora Store and F-droid.
[Google TV General] wright6432:
I have tried installing the app through the command line, also from F-droid and Aurora Store, but I am being given an error stating that "This app is not compatible with your device" error on all versions of Kodi other than Kodi 20, which is not the suggested version.
[Google TV General] jim16127:
Thanks for the filesystem response. Yes NTFS is the only logical solution. (FAT32 has 4GB file size limit)

I’ve been to that GitHub page more than once. Essentially all I need to do is step 8. Although when I open the script...it doesn’t make sense to me. Where is it grabbing the onntvremap directory? Or is it merely creating the directory then moving it? If it’s the latter and it’s only creating an empty folder and moving it with permissions. What sorcery is occurring in the script that changes the behavior of the button mapper app?

#!/bin/bash

# Remap remote for Onn. 4k streaming box
# Author: Amit Raut

# Push the onntvremap directory to /sdcard/Download/
echo "[+] Pushing onntvremap directory to downloads"
adb push onntvremap/ /sdcard/Download/

# move the onntvremap directory to /data/adb/modules/ as root user
echo "[+] Moving onntvremap directory to /data/adb/modules"
adb shell "su -c mv /sdcard/Download/onntvremap /data/adb/modules/"

echo "[+] Use button mapper and grant superuser access to remap the remote keys as per your liking"

echo "[+] Rebooting..."
adb reboot
[Google TV General] Big Dumb Object:
So you abandoned the idea of the tablet builds eventually?

I try not to push hard on this subject, but now, after seeing somebody here experimenting with de-googling of ATV, I'm starting to think again how nice it would be to have a tablet build suitable for MicroG edition.
[Google TV General] matrix200200:
My struggle with the Android TV continues.

Now I got Nova launcher installed, but still unable to use any widgets.

Tried adding my usual Analog clock widget and the moment I place it on the screen, it just disappears.

What are my options of placing a clock on the home screen somehow?

At this point I am willing to settle even for digital one (though analog would be preferable).
[Google TV General] npjohnson:
LineageOS 20.0 is coming for these devices, this thread will close once the builds are ready.

Just as a heads up.
[Google TV General] npjohnson:
we don't have the app widget permission installed, that is why it doesn't work.
[Google TV General] matrix200200:
Can it be fixed somehow?
[Google TV General] matrix200200:
What about live wallpaper with a clock?

Would it work?

EDIT:

Apparently Live wallpapers are impossible either.

I get "App not installed" message when I try to choose any live wallpaper.
[Google TV General] OT4KUBoi:
I have a Dynalink box too, how have you managed to do wade? When I try to unlock the bootloader I always receive

I am using Windows 10 right now:

C:\Windows\system32>fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

OKAY [ 0.023s]

Finished. Total time: 0.024s

Rebooting into bootloader OKAY [ 0.006s]

Finished. Total time: 0.008s

FAILED (Write to device failed (Unknown error))

fastboot: error: Command failed

When I tried it on Linux(Fedora):

fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

resulted in <waiting for device> (On an Andriod Smartphone I now would have to plug the charger I know, but on the dynalink has no battery, so it turns off)

Can you (guys) help me?
[Google TV General] npjohnson:
Or I could just update the OP - or even better the wiki that this all lives on.

lol

Never understood "reserved posts".
[Google TV General] OT4KUBoi:
Thank you I just wasn't sure what to look for exactly, unfortunately I have a bootloop on my Dynalink wade after installing dtb and dtbo:(

Mega Link is down, where can I download this aml-flash-tool-master for this purpose? Which recovery file will I need?

Edit: Found the aml flash tool master and recovery file but still do not know what to do exactly in order to fix the bootloop via Windows 10 or Linux (Fedora)
[Google TV General] fixsony:
Good news, when should we expect?
[Google TV General] npjohnson:
whenever it's ready - don't have an ETA.
[Google TV General] OT4KUBoi:
I had succes with unbricking my Dynalink wade on windows 10 using this unbricking tool:

Amlogic G12 SM1 Family Unbricking Tools - Google Drive

drive.google.com

Thanks alot to @skippyd, it saved me alot of headache :)

- Advise from me: Next time, try to put in all the unzipping parts in one folder

I followed the instructions by @npjohnson from a previous page:

"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 "

-> And I managed to get to the Lineage OS Recovery Screen as you can see on the picture, but unfortunately I was not able to press the "OK"/"Enter" Button on any of the options, does anyone know what causes this?

- I had no other option than pulling the plug, which led to a bootloop and now I am back on stock again.

- I noticed trying to change from charging to MTP (Media Transfer Protocol) always leads to crashing, but I need it on Linux(Fedora) in order to get permission in adb. (I do not receive an USB Debugging request on Linux somehow)