yashsingh1/xdaforums huggingface dataset:
[Google TV General] zimmie:
Thanks to developers that made this possible.

the instructions on the wiki is not clear as i have bootlooped a "wade".

Device was bought of labeled Dynalink Andriod TV Box.

Device came with an update already applied.

*Security patch from Feb. 2021*

OEM Unlock wasn't available on the Developers option page.

Booted into bootloader and unlocked the bootloader.

Rebooted the device back to the bootlaoder and flashed both dtb/dtbo images.

WIki instructions says to reboot after this.

after rebooting the device has gone into a bootloop.

it will not boot into recovery nor Burner mode.

holding the switch during power give the "Dynalink" Splash-screen for 2 seconds and it reboots again.

not holding it just keeps rebooting after 3 secs without any led flash nor flash screen.

i can tell from the flicker from the HDMI input.

So the question is what did i do wrong? was i suppose to reboot after flashing those 2 imgs DTB/DTBO without flashing a recovery? or are those DTB/DTBO files bad? i used the files located in the zip files of the signed lineage zip file.

I have ordered another one and i do not want to boot loop it again.

Thanks
[Google TV General] npjohnson:
where does it say to reboot after that? https://wiki.lineageos.org/devices/wade/install
[Google TV General] npjohnson:
you can't run adb reboot bootloader from fastboot, so that should have triggered, but I'll update the wiki to clarify
[Google TV General] zimmie:
Thanks. Is there anyway to recover this unit?
[Google TV General] npjohnson:
wiki updated, deploying it tonight.
[Google TV General] npjohnson:
Easily, just plug a USB cable from your laptop into the device while holding the button, then use update.exe to flash lineage recovery.

Done.
[Google TV General] zimmie:
Keeps looping and it won't stay on long enough to be detected by the computer.
[Google TV General] npjohnson:
try diff cable and port - that's not how that should work.
[Google TV General] zimmie:
Did that, didn't work. Also try using a 3amp power supply unit inline with the data USB lines. Still nothing.. keeps looping..

Thanks to papa Bezos I'll have another one in a few days.
[Google TV General] npjohnson:
This is 100% recoverable, it's just some specific instance issue here. what do you see in device manager when you connect?
[Google TV General] zimmie:
Nothing.

With a Usb port analyzer, i see something and it quickly disapears (loops)before windows is able to enumerate it.
[Google TV General] npjohnson:
got linux around you can try?
[Google TV General] zimmie:
I can install a distro.

What can we do in Linux If the hardware is not stablely booting?
[Google TV General] npjohnson:
might be a USB registration thing - this might initialize quick enough.
[Google TV General] zimmie:
If that was the case then it should stop looping with a just a power supply.

I think only way to recover is a JTAG.

Thank you very much for your support if this was device not under warranty i would have put in the extra effort. They are soo cheap that it's not worth the time.

I'll keep you updated on the new device when i receive it.

Lastly can i just boot the new device straight into the bootloader and unlock it ? Rather than doing the initial android tv setup/enabling developers mode? It seems not bring anything since there is no OEM unlocking tab.
[Google TV General] npjohnson:
Your assumption is false.

Data being connected at the right time dictates whether you boot to burn mode or recovery mode.

There isn't even JTAG on this board lol - idk what you're talking about. There is UART, which can defy fix this, but overkill - you can devs get to burn mode, I've been in the exact same situation when I brought up lineage ;p

No, update to latest OTA first.
[Google TV General] :
Is this while connected to a windows computer?

If so, if you don't have the worldcup drivers installed on your computer, then while you're holding the button, the worldcup usb connection won't be made, and then the device will move ahead to the next step in recovery process, which is booting the recovery partition. But if you don't have dtb/dtbo installed that will allow the current recovery partition to boot, the device will either get stuck or just start all of the above attempts over again.

Do you have the worldcup drivers installed?
[Google TV General] talksickisil:
Is there a mirror site for dopinder guide and links? The linked site is down . Thanks.
[Google TV General] S1ngl3-x:
I have the same issue with boot after flashing dtbo and rebooting. Only "Dynalink" is displayed. I can't do anything with it and bought another one.

Is there another way to save the device? When I connect it I can't see it in adb or fastboot.

Someone asked if I have linux laying around which I do. So what should I try?
[Google TV General] zimmie:
I was able to recover the device. Using the USB burning tool and AML update CMD tool.

Thanks guys.
[Google TV General] S1ngl3-x:
What did you do exactly?
[Google TV General] skippyd:
The link in my signature should fix your device...

If it doesn't then I can fix it in other ways.... Currently there is no way to brick these devices. I have had mine bricked multiple different ways and I've always brought it back to factory.
[Google TV General] samsungs3neos3neos3neo:
What's causing the issue people are having with wade? Is there something wrong in the wiki?

The dtb olink is empty and the dtb link should be the same as what's in the lineage zip? So do you just extract the two files from the official lineage zip and follow the wiki?

What should I watch out for as I try this?
[Google TV General] dungeon_mesher:
I don't feel confident in the bootloader steps, so I'm waiting for some advice. None of the fastboot commands seem to work i.e. they're not having any effect on the device

Trying 'fastboot reboot-recovery' isn't doing anything, so I'm afraid that flashing the dtb files will require the recovery tools to unbrick.

I'm on the latest platform tools platform-tools_r33.0.3-windows. wade is on the latest April '22 security patch. Any suggestions would be helpful
[Google TV General] dungeon_mesher:
It feels like my device isn't OEM unlocked, but I followed the steps and my device reset to factory after running 'fastboot flashing unlock'
[Google TV General] skippyd:
the command to go to recovery is..... "fastboot boot path-to-recovery.img-file"

example if you put the current recovery / dtb /dtbo in the same folder as your adb tools

fastboot flash dtb dtb.img
fastboot flash dtbo dtbo.img
fastboot flash recovery lineage-19.1-20221023-recovery-wade.img
fastboot boot lineage-19.1-20221023-recovery-wade.img
[Google TV General] skippyd:
this post works the best to install linage on these
[Google TV General] samsungs3neos3neos3neo:
Do you get anything from 'fastboot devices'?
[Google TV General] StiM_AddiCt:
Hello all.

I just received my "wade" today and finally was able to get LOS19 running. However I ended up using the dtb.img from the current update nightly build. My wifi is not working. Looks like the one I should have used (that fixes wifi?) was hosted separately.

How can I go about updating the dtb to fix my wifi? I can boot into LOS and get into the recovery, but haven't figured out how to get my PC talking to "wade" again. They can't see each other. Once that is fixed, do I just flash the dtb.img file and all is good? Or?
[Google TV General] zimmie:
What did you do exactly?

Here is a quick guide for anyone that brinks their unit.

Here is the set of tools i used.

File on MEGA

mega.nz

Install Amlogic_USB_Burning_Tool_v2.2.0 and all the drivers that comes with it.

Open the application, hold the side the button and plug in the device.

The application will make the device hold state without looping.

Close the applicaiton

Open CMD and navigate to "aml-flash-tool-master\tools\windows"

run the following commands,

update.exe partition dtbo C:\directory to\dtbo.img
update.exe partition _aml_dtb C:\directory to\dtb.img
update.exe partition recovery C:\directory to\recovery.img

onces that done. reboot the device whiles holding the button.

Open the burning tool get a hold of it and close it.

run cmd and navigate back to "aml-flash-tool-master\tools\windows"

run this command.

update.exe bulkcmd fastboot

you cannot boot in to recovery as the wiki states. i have no idea why.

so command "fastboot reboot-recovery" doesn't work.

what worked for me was "fastboot boot path-to-recovery.img-file"

from there on, install the lineage.zip file with adb command and whatever else you want to install.

done.
[Google TV General] samsungs3neos3neos3neo:
So should I be using DTBO from inside the official lineage zip, but use DTB from https://download.ods.ninja/Android/firmware/wade/dtb/ ?

And does the wiki still need updating? I am hesitant to start the process yet since people are reporting issues
[Google TV General] npjohnson:
The wiki is now updated.
[Google TV General] samsungs3neos3neos3neo:
What changed? And is there a difference between the dtb file on your site linked from the wiki and the dtb inside the official lineage zip? Which should I use?

The Princeton site still has nothing.
[Google TV General] npjohnson:
Use the one linked on the official wiki. 0 difference between zip one and my site, I just needed an openly downloadable one and lineage infra was really slow to get the dtb files posted, so I used my site for now.
[Google TV General] samsungs3neos3neos3neo:
Ok, thanks! So I booted and did the OTA update. It kept turning off during initial setup and a few times after. It seemed to stabilize, then I got 'adb devices' to work, but 'adb reboot bootloader' reboots it then gets stuck on the Dynalink logo screen. Am I doing something wrong? Are there other drivers required not mentioned in the wiki?

I was also able to get into recovery by holding the button before plugging in. I navigated to the menu option to reboot into bootloader and that didn't work either.
[Google TV General] npjohnson:
Dynalink logo is bootloader. Jusy use fastboot after that.
[Google TV General] samsungs3neos3neos3neo:
haha wow.. thanks! unlock command failed..?

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

OKAY [ 0.032s]

Finished. Total time: 0.032s

Rebooting into bootloader OKAY [ 0.016s]

Finished. Total time: 0.016s

FAILED (Write to device failed (Unknown error))

fastboot: error: Command failed
[Google TV General] StiM_AddiCt:
Any idea what to do if my wifi isn’t working? The wifi setting is off. When I enable it, it just turns itself back off. Never displays nearby wifi. Followed the guide yesterday. Used the dtb and dtbo from inside the official lineage zip. This is for a dynalink wade.
[Google TV General] samsungs3neos3neos3neo:
Disregard my previous reply. I didn't realize those were supposed to be three separate commands. I'm wondering if I should hold off on dtb and dtbo given StiM_AddiCt's post...
[Google TV General] zimmie:
Lineage working beautifully after Several days of running. I'm new to android TV. This little thing packs a punch.

How do I buy developers a beer?

Already donated to lineage organization.
[Google TV General] :
Was this wiki instruction intentionally crafted to set the lock variable to a locked value? I'm sure that it works, because it was described the same way earlier in this thread, and was reported to fix whatever issue was caused by the the oem lock implementation issue (or whatever it is called) from last year. And that is also how google did it for deadpool for dev builds. Would an unlocked value not work to fix the issue?

When one of my dopinder devices had this issue last year, a reboot wasn't required after the above command. I did something like;

fastboot oem 'setenv lock 10101000;save'

fastboot flashing unlock

fastboot flash recovery name-of lineage-recovery.img

fastboot oem 'reboot recovery'

That's from my notes from back then. Now, of course, dtb/dtbo would need to be flashed as part of the above steps.
[Google TV General] talksickisil:
Hello. Dopinder here. Dtb and dtb0 links in the instructions point to an empty folder. does this mean the files are no longer necessary? I can't get this damn recovery to flash. Please help. If theres anything specific for walmart onn 4k box/dopinder please tell me. Thank you for your work.
[Google TV General] :
They are there. The folder is not empty, there is another folder within (bearing a date). dtbo is within that folder. dtb is in the other link referenced in the instructions.
[Google TV General] samsungs3neos3neos3neo:
So wifi is working for you? Are you talking about official wade or one of the other?
[Google TV General] samsungs3neos3neos3neo:
And these latest files work for you including wifi is ok? A user just posted slightly before you regarding wifi issues. They used the files in the official zip but they are the same as the externally linked ones (per npjohnson, and I also checked with windiff)

Edit: I see you're talking about dopinder, not wade
[Google TV General] npjohnson:
you didn't follow the guide then.

PayPal.me/nolenjohnson, or my GitHub sponsors in signature
[Google TV General] samsungs3neos3neos3neo:
What did he do wrong that would have affected WiFi? Use the dtb and dtbo from the official zip or something else?
[Google TV General] StiM_AddiCt:
How should I go about reflashing the DTB and DTBO? Will it require the recovery and lineage to be reflashed also?
[Google TV General] RDS5:
you can actually overclock the dynalink 4k practically the same way as any other generic arm SBC (modifying the dtb).

its likely true for the rest of these devices (since they all use the same kernel).

where can i post the modified dtbs for dynalink 4k?
[Google TV General] Slimshady997:
Is dopinder already stable in streaming applications? Where can I see a list of fixed issues?
[Google TV General] skippyd:
Its stable but Netflix won't work without mods.... also if you enjoy controlling your tv with your remote then stay with retail. I run both and I think retail is faster.
[Google TV General] samsungs3neos3neos3neo:
The Amlogic_Driver dpinst64.exe installation says libwdi install failed...

any tips?

@npjohnson I have no wifi on wade. Enabling usb debugging in developer settings does nothing. I can get to lineage recovery by holding the dynalink and plugging in usb, then navigate with the reboot to fastboot. but fastboot devices says "?????????????"

so I'm stuck. could you help please?

EDIT: I can no longer get into recovery. Holding the dynalink button while plugging in no longer works. And I enabled to in-system options to reboot into recovery or bootloader. All of the above just go to perpetual "androidtv" logo screen, and 'fastboot devices' returns nothing
[Google TV General] samsungs3neos3neos3neo:
Thanks! I'll try it. The burning tool was showing a device even through the driver install failed. Maybe because the other world cup driver worked ok. the update.exe command for dtbo didn't work though

EDIT: @XDA-DB I downloaded the tool here and got back to stock. https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-87532333

@npjohnson how should I proceed with wade? do you know why wifi is broken? I followed the guide exactly, except I used the dtb and dtbo files from the official zip because they are the same as from the external links in the wiki, right?
[Google TV General] samsungs3neos3neos3neo:
@npjohnson I used the 20221030 dtbo on the Princeton site, the 20221024 dtb on your site, and the official 20221030 lineage install and recovery. It worked, but I couldn't get to recovery by using fastboot reboot-recovery. Holding the button and plugging in did not work after several tries. I was about to go back to stock again with this tool https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-87532333 and was holding the button and plugging in again, then it randomly decided to work, so I got lineage installed (no gapps).

WiFI did work fine. I sideloaded f-droid and firefox (fenix from github). It worked for a while. Then in the middle of installing VLC via f-droid, the device powered off. Now it boots to the "androidtv" logo, hangs, reboots, and cycles.
[Google TV General] :
I don't know of any version of fastboot that accepts "reboot-recovery" as a command line parameter.

All of these askey devices turn the "oem" parameter into a full u-boot shell. Most other certified android tv devices don't allow the "oem" parameter to work this way. Rather, they white list only some shell commands. Given that these askey devices can run any u-boot shell command via fastboot oem;

fastboot oem "reboot recovery"

would probably be a better instruction for the wiki than the current "fastboot reboot-recovery" instruction.
[Google TV General] samsungs3neos3neos3neo:
I used the stock-installing tool again (which worked a few times previously). All the steps were reported successful, and the device now shows the dynalink logo again, but it won't boot. It shows the logo for a bit, shuts off, reboots, repeats.

Maybe my device is just defective from the start.
[Google TV General] :
Are you running your own build, or the build from this thread?

If your device rebooted in the middle of installing and/or running vlc, that is a little unusual.

Would it be difficult for you to hook up the uart connection?
[Google TV General] StiM_AddiCt:
So I am struck and too dumb to figure this out. I can boot into LOS19. I can enable usb debugging and rooted debugging. Windows cannot see my device via adb devices or fastboot devices. The unit does show up in the device manager.

I can hold the button on the device and boot into the recovery. If I go into advanced options and enable ADB, windows still cannot see it. If I reboot to bootloader windows cannot see it (it reboots to an android tv logo). It still shows up in device manager but adb devices doesn't list the device.

Am I missing something simple here? I am trying to update my dtb and dtbo with what is hopefully the correct version to fix my wifi issues. Since the links in the guide had no files listed for the dtb I used the one inside the nightly zip and that didnt work. So I am trying to see if reflashing the dtb will work.

EDIT: If I enter fastbootd mode, Windows reports this:

C:\Windows\system32>fastboot devices

???????????? fastboot

So at least it can see it there?
[Google TV General] npjohnson:
It's a newer thing, but this is a common thing, being fastboot reboot-recovery - it does seem, however, deadpool on 12 has this, but wade/dopinder don't.

I'll update the guides. Thx.
[Google TV General] samsungs3neos3neos3neo:
I used the official lineage release. I think it turned off while it was downloading VLC, before the installation started. uart connection, like open up the device? I'm not sure I can afford to sink any more time into this piece of **** device. $40 was too good to be true. It rebooted like four times during the initial setup when I first powered it on before even plugging it in my computer.
[Google TV General] samsungs3neos3neos3neo:
This tool worked for me a few times. https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-87532333

I had the same issue with no wifi. I used the tool to get back to stock and then started over. By that time there was dtbo in the princeton site and wifi worked with that and the October 30 official lineage release of wade. But then it shut off in the middle of using it after being operational for at least half an hour. After that I tried the tool again to go back to stock and it reported successful and showed the old dynalink logo, but now it's in a bootloop and is basically bricked.
[Google TV General] skippyd:
It's not bricked and I can help you fix it...

Also... I am in the process of creating a new tool with this being automated and other options like rooting factory etc...

Plug in device to computer while holding button down on side

update.exe bulkcmd fastboot

confirm you are connected to fastboot

fastboot devices

Now time to get to recovery... you will need the dtb, dtbo, and recovery from whatever build you want... factory or Lin 19

fastboot flash dtb dtb.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot boot recovery.img

Once in recovery use the button on the side and short press to sideload option then long press on that option. then sideload whatever build you decided to use.

adb sideload name of zip file you want to use.zip
[Google TV General] js8call:
I cant see your signature..can you post the link? thks..
[Google TV General] skippyd:
Amlogic G12 SM1 Family Unbricking Tools - Google Drive

drive.google.com
[Google TV General] js8call:
thank you..I bricked a Dopinder using the dbt files inside the 19.1 Dopinder big file..
[Google TV General] samsungs3neos3neos3neo:
Thanks a ton for the help! It worked up until sideloading lineage. I've tried a bunch of times and it keeps timing out or something at various percentage levels of completion (4%, 18%, 32%, etc.). It seems like the device doesn't have enough power or something and keeps turning off. I've tried various cables and ports, including a port on a powered usb dock.

serving: 'lineage-19.1-20221030-nightly-wade-signed.zip' (~32%) adb: failed to read command: No error
[Google TV General] skippyd:
You have to use the recovery file from the same place you got 'lineage-19.1-20221030-nightly-wade-signed.zip'...

then code would be....

fastboot flash dtb dtb.img
fastboot flash dtbo dtbo.img
fastboot flash recovery lineage-19.1-20221030-recovery-wade.img
fastboot boot lineage-19.1-20221030-recovery-wade.img

follow all other steps

or copy paste to make a *.bat to put in the dir of your adb and update...

@echo off
cls
title [ I made my own window ]
update.exe bulkcmd fastboot
pause
echo.
echo ***wait 5 seconds***
echo.
pause
fastboot devices
echo.
echo ***if no device close window***
echo.
pause
fastboot flash dtb dtb.img
fastboot flash dtbo dtbo.img
fastboot flash recovery lineage-19.1-20221030-recovery-wade.img
pause
echo.
echo ***booting recovery. In recovery goto sideload***
echo.
fastboot boot lineage-19.1-20221030-recovery-wade.img
pause
echo.
echo ***wait for device to say ready to sideload***
echo.
pause
adb sideload lineage-19.1-20221030-nightly-wade-signed.zip

attach is above code for wade
[Google TV General] samsungs3neos3neos3neo:
yep, that's exactly what I did. I just downloaded new copies of the official lineage zip and the recovery image, both from the official wiki. I tried using the dtb/dtbo extracted from the official oct 30 lineage zip, as well as the files linked from the wiki on the two external sites.

I tried your stock tool again and it something new happened. now it shows the green android lying down with the chest plate opened up and a red triangle with message "no command"

Even if I get it working, I expect it will just randomly turn off again. I don't understand how I had lineage working with wifi just fine for a while and then it randomly starting bootlooping.
[Google TV General] talksickisil:
I’m sorry I don’t have money to donate to further dopinders development but I do want to say thanks from the bottom of my heart. I’m having a hell of a time trying to sign into Google though. I tried the okay google set up my device feature and it found “tv with Chromecast built in” I tried to connect to it and the 4 digit code on the phone never shows up on the dopinder. I just wanted to note to other onn box users it’s probably better to sign in manually and then AFTER flashing the rom wipe cache (and only cache) this helped me finally get to sign in. Also I wasn’t able to unlock the bootloader yet I have the 0908 recovery and rom both installed. The option in developer options for unlock bootloader is untickable. Is it really advantageous to have it unlocked?
[Google TV General] js8call:
cou

could you upload the dbt and dbt0 files somewhere? they are not available anymore..
[Google TV General] skippyd:
in the zip now
[Google TV General] StiM_AddiCt:
Wow thanks for the tip! I got back to stock. Time to try this again with the correct dtb and dtbo now that they are actually linked in the guide.
[Google TV General] StiM_AddiCt:
Thank you for this. It was super helpful.