yashsingh1/xdaforums huggingface dataset:
[Google TV General] talksickisil:
I mean, you could search emotn ui launcher.. it’s actually designed for android tv, and has both live wallpapers and clock and weather widgets you can display. I just went to search it on play store before replying, and it’s seems it’s recently been removed. So, at your own risk and maybe search why is it not in play store or check out screen shots of how it looks on google images before downloading it. I can’t imagine a phone launcher like nova or apex to play nicely with android tv
[Google TV General] talksickisil:
Fantastic news. Whenever it comes. Do not rush it by any means
[Google TV General] xperanto:
The "Ok button" is wrongly assigned to the power button on the remote, but only in recovery mode .At least on my EU-Version. So press the power button on your remote to select.

Also, keep in mind, that wade uses IR for the remote and not bt in recovery mode.

It's somehow unclear for me if wade uses only BT completely as i think, instead of IR in LOS (e.g. if i cover the the ir-diode on the remote or use it while in another room it still works for e.g. navigating, but not in recovery).

Could be that IR is just meant as a fallback for recovery.
[Google TV General] matrix200200:
Thanks I will try.

Do you know if it supports shortcuts?

I have a program called "Http shortcuts" to run my smart home stuff (Domotociz shortcuts).

Except for that I just need VLC and access to something similar to app drawer (don't want to put all my apps on the main screen).
[Google TV General] talksickisil:
Well I know the path. It’s the files in system > usr> key layout. The onn has a slightly different setup as somebody who had dopinder and then wade, both with magisk… that onn remote remap is not 100% compatible with wade a lot works but it doesn’t completely work. We need to ask the developer of that script to make it for wade. It works good. But just like you mentioned you need to know which file to change. There’s about 100 .kl files in the location I mentioned.
[Google TV General] talksickisil:
Good evening gentleman. So I ordered one of those Playstation Classics online I got a great deal on it. BUT, in order to mod it I needed a low power usb drive. The only one I know for sure is low power was the one assigned as internal storage on dynalink. So I cloned the drive on etcher, but I decided to start with a fresh install of Lineage since the cloned drive was larger and dynalink would not see the drives actual size. What was my point again? Oh yeah, I am no longer having issues with network upon reboot. Previously I needed to toggle wifi off then back on with every reboot. I could be wrong but I suspect the issue I was having is related to the apps having the issue were being installed onto my flash drive acting as internal storage rather than being installed to ACTUAL internal storage. Long story short, I have even less to complain about now. Has anybody else had this issue only to see it resolve recently? I am on the 12/4 build. If anybody is having this issue with wifi on reboot and is using an older build, try the 12/4 nightly and let me know if the issue remains! Thanks. I wish I would have waited one more day as the nightly builds always drop on Sunday but that's okay. Hope you guys have a great weekend.
[Google TV General] activadroid:
Meanwhile, Wade UNofficial link seems down / gone. Is it being updated or cancelled ?
[Google TV General] npjohnson:
Server maintenance
[Google TV General] iodemos:
My DynaLink TV Box Model DL-ATV36 is broken. After power on the logo DYNALINK is stuck, nothing works - neither ADB nor FASTBOOT mode are possible.

The 16-bit 'aml-flash-tool' from 2018 does not run on a Windows 10 64-bit system because of its incompatibility, on a Windows 8.1 32-bit system after entering the command 'update.exe bulkcmd fastboot' it aborts with the note: "Too big to fit in memory".

Is there another way to get into fastboot mode to at least flash the stock recovery.img?
[Google TV General] talksickisil:
Can you get to recovery by holding the button on the device while plugging it in ?
[Google TV General] AiM2LeaRn:
to use the remote to navigate recovery

-power button on remote is <enter><Select> on the recovery screen

-back button on the remote is to go back on the recovery screen

-up/down on the remote is to move up/down on the recovery screen
[Google TV General] AiM2LeaRn:
Does anyone know if can you SKIP the initial setup ( Connect to Wifi and Google Account Creation Setup ) with the UNOFFICIAL lineage build?
[Google TV General] activadroid:
just checked after installing today (2022Dec12) latest UNofficial wade (ver 20221212 downloaded an hour ago) Settings > Privacy > Trust > shows Android security patches as "A few months out of date'.

I would expect minutes, hours, or days out of date & not months.

Can anyone enlighten ?
[Google TV General] iodemos:
No, no reaction.

After entering

fastboot flashing unlock

fastboot flash dtb lineage-19.1-20221024-dtb-wade

fastboot flash dtbo dtbo.img

fastboot flash recovery lineage-19.1-20221211-recovery-wade.img

still shows only the DynaLink logo.
[Google TV General] xperanto:
You can skip/bypass the Google setup wizard in Unofficial LOS with

adb shell settings put global setup_wizard_has_run 1

adb shell settings put secure user_setup_complete 1

adb shell settings put global device_provisioned 1
[Google TV General] AiM2LeaRn:
wow, your are a life saver, thanks IT WORKED!!!!

i QUICKLY (cause if i dont push to allow adb connection the popup disappears after a few seconds) so i quickly enabled the adb connection at FIRST BOOT when the popup appeared. then i typed your commands in adb

adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1

and then i unplugged the power from the device and plugged it back in and i was able to bypass the setup. bro thanks again.
[Google TV General] iodemos:
Thanks for the hint dtb.

Just can't reflash as the TV box is not recognized in device manager nor does it

responds to any adb or fastboot commands. Only the DynaLink logo is displayed.
[Google TV General] iodemos:
Well, I am already looking, but so far without success.

- - -

update bulkcmd fastboot

[update]:No [WorldCup Device] device after scan

[update]ERR(L1094):can not find device
[Google TV General] iodemos:
The good news first: I was able to revive my TV box.

However,, the tips here and the extensive searching here on XDA were of no help to me. I finally found on the WWW the "Amlogic G12* SM1 Family Devices Tools v1.00" which reinstalled stock Android 10.

Spoiler content hidden.

The bad news: The installation after the LineageOS Wiki Install LineageOS on wade bricks again my DynaLink TV Box Model DL-ATV36.

Unlocking the bootloader

adb reboot bootloader

fastboot devices

fastboot oem 'setenv lock 10101000;save'

fastboot reboot bootloader

fastboot flashing unlock

(6.) The TV box did not reboot automatically, so I rebooted it manually.

(7.) Since the device was completely reset, USB debugging had to be re-enabled to continue.

Flashing the partitions dtb and dtbo

Flashing the dtb and dtbo partitions

- - -

adb reboot bootloader

fastboot flash dtb dtb.img

fastboot flash dtbo dtbo.img

Installing a custom recovery with fastboot

- - -

adb reboot bootloader

fastboot devices

fastboot flash recovery lineage-19.1-20221211-recovery-wade.img

fastboot reboot-recovery

The command »fastboot reboot-recovery« was not executed, that means the TV-Box did not boot into the recovery to verify the installation.

Trying to boot the TV box manually into recovery mode failed and ended again at the DynaLink logo - and again could not be controlled with adb or fastboot commands. So I was again at the point #1.737 "My DynaLink TV Box Model DL-ATV36 is broken".

I will not use the official LOS installation guide again, so: which How-To brings me to the successful 'LineageOS on wade' installation?
[Google TV General] AiM2LeaRn:
i had "format system" in recovery and the same thing happened to me, i got stuck on the logo and wasnt getting detected in fastboot, recovery or bootloader and the serial number was missing. I had to use the burn tool to restore factory image and then it worked again and the serial number was restored.

there are a bunch of ways to restore factory firmware, plenty are listed in this thread but its going to take time to READ and CAREFULLY FOLLOW.

have to install world cup driver and adb drivers. Helps if you have the windows sound on to help you know when it detects the device. you have to do the plug in while holding power button trick and as soon as you hear the detection noise in windows just wait like 1-3 seconds and you can let go of the power button, its all about timing it right, but eventually it detects and starts flashing from the logo screen.

I HOLD NO RESPONSIBILITY IF YOU TRY THIS BELOW, HOWEVER IT WORKED FOR ME...

this is automated and fairly simple and might work, i would try this first becuase it automates the driver installation and all the files you need to restore.

Amlogic G12 SM1 Family Unbricking Tools - Google Drive

drive.google.com

if that doesnt work you should have all the drivers and stuff installed from the files above and then you can maybe give this a try the RESTORE function from "backup and restore " script from Eliminater74 from here:

https://xdaforums.com/t/official-unofficial-lineageos-19-1-for-amlogic-g12-sm1-family-devices.4313743/post-86327923

if those 2 dont work theres Amlogic burn tool... i personally got it to with the restore script from Eliminator. dont hold me responsible for using any of those methods or files, use at your own risk, however they worked for me.
[Google TV General] AiM2LeaRn:
Unlocking Process​

#enable usb debugging

adb reboot bootloader

#check to see if your device is detected

fastboot devices

#send unlock code to device

fastboot oem 'setenv lock 10101000;save'

#reboot to bootloader for system to acknowledge and apply previous code

fastboot reboot bootloader

#unlock the bootloader

fastboot flashing unlock

#reboot to system

fastboot reboot

FLASHING PROCESS​

#enable USB Debugging

adb reboot bootloader

#fastboot flash dtb dtb.img

fastboot flash dtb lineage-19.1-20221024-dtb-wade.img

#fastboot flash dtbo dtbo.img

fastboot flash dtbo dtbo.img

##flash recovery image

fastboot flash recovery lineage-19.1-20221211-recovery-wade.img

##attempt to boot into recovery

fastboot boot lineage-19.1-20221211-recovery-wade.img

#it will either boot into recovery or it will hang/freeze

##DO NOT LET IT BOOT INTO SYSTEM

##DO NOT LET IT BOOT INTO SYSTEM

##DO NOT LET IT BOOT INTO SYSTEM

##you must either go directly to recovery by

##manual method or by commands

#personally it hung on me every time i tried the command and i had to manually reboot into

#recovery by disconnecting the usb cable and then

#hold power button on actual device (not the remote) while plugging in the usb cable into the computer

#once in the linage recovery

#Now tap Factory Reset, then Format data / factory reset and continue with the formatting process.

#DO NOT Format System

#now you can sideload lineage by choosing

#“Apply Update”, then “Apply from ADB” to begin sideload.

adb sideload lineage-19.1-20221211-nightly-wade-signed.zip

#optional if you want Gapps

adb sideload MindTheGapps-12.1.0-arm-AndroidTV-20220912_160805.zip

#reboot to system using recovery and enjoy

EXTRA NOTES:

# if it hangs and gets in a bootloop/soft brick,

# just disconnect usb power cable and then hold the power button down on the actual device

# and then power on the device by plugging back in the usb cable

#having windows volume on to hear the USB Hardware detection sound helps alot to know when its in recovery/bootloader mode

#use the remote to navigate recovery on WADE/DYNALINK

#Dynalink remote is BOTH a IR and Bluetooth remote

#note that other manufactures may just be Bluetooth remote

#if your remote doesnt have IR function you must use a microUSB to USB hub and connect a keyboard/mouse

-power button on remote is <enter><Select> on the recovery screen

-back button on the remote is to go back on the recovery screen

-up/down on the remote is to move up/down on the recovery screen
[Google TV General] iodemos:
Hi @AiM2LeaRn, thank you for your detailed answer. I'll try it and give feedback.
[Google TV General] iodemos:
Booting into the lineage recovery is not executed, neither by fastboot commands nor by manual method. The DynaLink logo is frozen, the contact to the host machine is broken. Nothing works anymore except - reinstalling stock Android 10.
[Google TV General] activadroid:
Did you try the UNofficial wade version yet ?

I installed that version from 20221212 and it seems OK.
[Google TV General] AiM2LeaRn:
it should work... all i can think of is that you are possibly flashing the wrong files or typing something wrong in the wrong place.

can you post the Three DIRECT links to the DTB DTBO and RECOVERY files you are using?

can you also post a screenshot of the ADB screen to see what you are typing?
[Google TV General] matrix200200:
Ok, so I got around th play with emotn ui launcher and I am sorry to say its an utter garbage.

No support for shortcuts, weather shortcut that I couldn't remove and where is clock again?

This launcher is basically, the same old tired junk I had on cheap chinese tv boxes in 2015.

I am sorry, but this one is hardly a reason to give up on Nova launcher.
[Google TV General] S1ngl3-x:
Does anyone know if it is possible to get chromecast working?

I've got official wade and lineageos on phone as well with microg (avicii).

Both devices have screencasting in menu but loading up YouTube does not work.

Is there anything I am doing wrong?
[Google TV General] Slimshady997:
what are the devices? Is there already a stable version for dopinder?
[Google TV General] Mayrbek86:
how to flash this prefix to the factory firmware image?
[Google TV General] matrix200200:
Some wifi issues.

I am experiencing the device not automatically reconnecting to wifi after having been put to sleep.

Also, I tried setting up static ip and noticed the static ip screen in settings appears to be non functional.

I cannot type and cannot save a static ip.

Also except the static ip text box, there are no other settings present (subnet/gateway/dns etc).
[Google TV General] zweiund40:
Seems like the Same Problem i had.

Solution for me was to switch from linux to Win11, installing Amlogic_USB_Burning_Tool_v2.0.2 as suggested in this thread including the Drivers to went back to Stock.

Started the Tool, pressed the Button on the Box when plugged the USB cable in the Port of My Laptop. I was very suprised that the recovery Started directly, without adb or fastboot - so i could finish the Installation of the Rom and till Now everything seems to work 😁
[Google TV General] npjohnson:
LineageOS 20 thread is up: https://xdaforums.com/t/official-un...logic-gxm-gxl-g12-sm1-family-devices.4534935/

Quick update:

- wade/dopidner install instructions are fixed to avoid DTB/DTBO reboot boot loop issue

- We figured out the devkits not booting, they will boot very soon!

- dopinder/Sabrina might have L1 fixed, will need y'all to test

- 20 also fixed a lot of small QOL things in the platform
[Google TV General] zweiund40:
Hi2all

I'd would like to thank the maintainer of this rom a lot. Great work!

With this it was possible for me to get an ungoogled Android Streaming Device (wade).

In case of an app that asked every time for googleservices (RTL+) I've installed Microg, which was a little bit tricky (adb sideload Magisk -> installing fdroid (adb) -> installing Material File Manager (from fdroid) -> installing LSPosed (within Magisk) -> installing Fakestore -> installing minMicrog-nogoolag(within Magisk).

The needed Apps for streaming I'm getting through Auroradroid/Aurorastore which is a little bit tricky too in case of the UI what is normally for Touch Devices. In cause of this is only a one-time process it seems no Problem for me.

Till now everything seems to work fine and I'm very happy with this.

Due to a more cleaner and easier installation a version with microg (or signature spoofing) within would be great, but I don’t know how hard it is to build it and how many Users would like to have this feature.

So again, thx a lot and best regards

Christoph
[Google TV General] talksickisil:
This was something I wanted to look into. I fell out of the root /custom rom scene since I switched my phone in 2018. It’s these tv boxes that has me back. How do you install F droid through adb? Is it possible to just install all of my apks thru adb? When I tried going without g apps I got stuck due to having no file manager installed. I’m not sure how many of my apps NEED google services. Honestly if I could install my fx file manager apk thru adb id probably just start there
[Google TV General] zweiund40:
Hi,

Yes, you can install fdroid via adb install. As Filemanager i prefere Material Filemanager from fdroid because it can browse the network. If you got all your needed apps for this architecture you can install them by adb too, but there will be no updates for them. Thats the reason I am using Aurorastore to install apps. Its an Appmanager to get apps from the playstore without the need of an Google account.

I think it's a good idea to start like you suggested. If there are problems in case of apps which needs Google services you can install microG and the rest later.

Hope I could helped you a little bit.

If you have more questions you can ask.

Good luck!
[Google TV General] Slimshady997:
The streaming services still do not work and in the case of Netflix it is not compatible with Android 13
[Google TV General] rapboys16:
Ditto, unfortunately again none of the streaming services work. :(
[Google TV General] MrPlayboy22:
Dear friends, you already helped me once (thanks again!) - so hopefully you can help me again.

Device: wade

Android version: 12.1 / LinageOS 19.1

I was on an unofficial version as of October 2022. Today I updated via the official updater (Settings -> System -> Updater) to the latest, unofficial version (2013-01-01). It updated sucessully and everything works, beside Wifi. This one seems to be broken for whatever reason (it was working before!). Obviously now "re-updating" does not work any longer, as there is no Wifi available.

How could I get my Wifi working again? Turning it off/on via the settings seems to not do the deal.

Furthermore, there seems to be an option via Ethernet. Would someone have a cable/ adapter solution (on Amazon?) that I could order as a backup for potential future Wifi issues?

Thanks a lot in advance for your kind support and help. Highly appreciated.
[Google TV General] sjustinas:
I have had my WiFi broken by updates many times, and what worked for me every time was to flash previous known-good DTB and DTBO. Use aml-flash-tool as described here. You don't need to follow all the steps, for me it was enough to:

1. Turn on wade while holding the side button (to enter AMLogic burn mode)

2. ./update bulkcmd fastboot

3. fastboot flash dtb dtb.img

4. fastboot flash dtbo dtbo.img

5. fastboot reboot

The DTB/DTBO files I use are from lineage-19.1-20221023-nightly-wade-signed.zip
[Google TV General] MrPlayboy22:
Thanks @sjustinas - much appreciated and sorry for getting back so late to you (I was on a business trip).

I tried now to get the DTB(O) files according to your description (which seems to be for Linux, including the tool). Very sadly, I only have Windows (10) available. Would you mind guiding me to a tool (and respective commands) for Windows? Thanks a lot in advance for your kind support again to get my box working again - very much appreciated!
[Google TV General] sjustinas:
Yeah, it seems like aml-flash-tool is only available for Linux. I am not sure what the equivalent for Windows is. If you are at all comfortable with Linux, you could boot a live USB of Ubuntu and use that.
[Google TV General] MrPlayboy22:
Thanks @sjustinas - will try to get a USB stick up and running. A pitty, it is not available for Windows.

@npjohnson - would you potentially have a Windows (10) working solution to the issue, as this might happen to other users as well? Thanks ahead :)
[Google TV General] npjohnson:
There is a flash-tool but I know nothing about it. AML Burning Tool
[Google TV General] itchydroid:
After soft-bricking my ONN devices I was able to recover on windows 10 using the method above but I used the windows flash tool from https://github.com/osmc/aml-flash-tool. There is a download for the Windows tool under https://github.com/osmc/aml-flash-tool/tree/master/tools/windows. You will need to ensure you have the right drivers installed first which you can get from https://drive.google.com/file/d/1q3Hwrmx-YCrw9U5JGtI2Ocn06zPkjrEG/view

Make sure that you connect the hdmi to tv and the other to pc/laptop so that if it boots into the bootloader gui, you can navigate it.

On some occasions I got a blank screen or just the ONN logo but no fastboot. In this case i issued the 'update bulkcmd fastboot' command and was able to enter into fastboot mode.

EDIT: Also you might need to run fastboot as administrator on the windows console. Im not 100% sure as I am a linux guy :) . I just use a windows laptop to do device/firmware flash and recoveries because a lot of the these tools are usually windows.
[Google TV General] endera:
So anyone have this working on a radxa zero ?
[Google TV General] MrPlayboy22:
Dear @itchydroid - thanks for your detailed help and sorry for coming back again to you.... I still struggle slightly ;-)

What I have done (on Windows 10):

- Installed the drivers as per your link

- Installed the windows files of the AML-flash-tool as per your link

- Connected via HDMI to the TV and via USB (with a proper USB cable) to the laptop

- Running the console with local Admin rights (see below)

Where is the issue

- When running the console, I get the following error message:

Microsoft Windows [Version 10.0.19045.2486]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9

C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9>update bulkcmd fastboot
AmlUsbBulkCmd[fastboot]
usbReadFile len=512,ret=-5 error_msg=libusb0-dll:err [submit_async] submitting request failed, win error: A device attached to the system is not functioning.

[AmlUsbRom]Err:return len=-1 < strLenBusy 11
[AmlUsbRom]Inf:bulkInReply
ERR: AmlUsbBulkCmd failed!

C:\Users\User\Desktop\Dynalink TV Box\AML Flash Tool 4.9>

I feel like I am not too far away - yet still too far away to get my Wifi issues sorted :-(

By the way: With the AMLogic USB Burning Tool, I see the device connected. So the burning mode seems to be "correct".

Could you please guide me/ help me? Thanks a lot!!!

Screenshots of the setting:

- Driver

- Console:
[Google TV General] itchydroid:
I think you can ignore the failure. I get the same thing. After the failure, if I run "fastboot devices" the box should show up.

EDIT: After the failure, you should hear the windows usb "disconnect" sound and a short while later, the reconnect sound. This is the device switching to allow fastboot to work.
[Google TV General] MrPlayboy22:
THIS DID IT! THANK YOU VERY MUCH :)

You are my hero!!!