yashsingh1/xdaforums huggingface dataset:
[Google TV General] cannondale0815:
Just checking in once more on this -- I assume answer is still the same as before that it's not yet supported, correct? If so, @npjohnson could you update the reference to the remote in the original post? Right now it says that the stock remote is fully working/supported, but maybe add a little info about the above. Thanks!
[Google TV General] npjohnson:
It works fine, we just have no app to configure it.

Working on it
[Google TV General] ali387:
Hello there. I need some help. I followed the instructions to install LOS 20 for wade on my Dynalink (wade) device.

I completed step 5 (Flash recovery onto your device) and step 6 (Now reboot into recovery to verify the installation)

But my device is staying stuck at 'DynaLink' logo

here is the screenshot of the terminal session:
[Google TV General] ali387:
I am able to access my device using AMLogic USB Burning tool. And have attempted steps outlined by forum member zimmie

Still no luck in finding a path to move forward to 'Installing LineageOS from recovery' step.

I get error at: update.exe 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]Err:bulkInReply=[]

ERR: AmlUsbBulkCmd failed!

​
[Google TV General] ali387:
I missed one key warning in the instructions. I used my device right out of the box without updating it. I only powered it up to set the USB debugging on and went my merry way to install LOS 20.

The instructions say that i need to update my device up to android 12.

I have found the original factory image here on another thread. I have reverted back to original image and now running through update process.

I will retry installing LOS 20 after updates are done.
[Google TV General] Functioner:
That response is the expected response to "update bulkcmd fastboot". After running the command, check if the usb connection has actually successfully changed to a fastboot connection.

fastboot devices

If the fastboot device is not shown, try immediately executing "update bulkcmd fastboot" again. Sometimes it takes another try. If the fastboot device is shown, proceed on to whatever fastboot commands.
[Google TV General] ali387:
I retried the LOS 20 install steps after upgrading to latest patches on the device. Same result .
[Google TV General] ali387:
Thanks. Will give it a try.
[Google TV General] ali387:
tried running multiple times immediately but still same result.

Is the firmware version shown by update.exe identify right?
[Google TV General] npjohnson:
try this on a USB2.0 HUB or a diff cable/port.
[Google TV General] ali387:
Good point. I will try that out. Thanks.
[Google TV General] mmortal03:
Just FYI, the previous Onn device just got a new maintenance release on stock. (February 5, 2023 security patch)
[Google TV General] S1ngl3-x:
Is this still broken only on our wade devices or is the issue relevant for everybody?
[Google TV General] npjohnson:
mkay, on it
[Google TV General] npjohnson:
everyone - won't give this advice out often, but for stock updates for these devices, pls @ me, I want to get these merged as quick as possible.

Want to avoid the "wade got 12 and I didn't know for 3 months" issue haha

dopinder update is integrated for the next build. Thx for the heads up.
[Google TV General] km230580:
HI Thanks to make lineage os for Android Tv, this ROM will support AlfaWise H96 PRO+ 3/32! android box?
[Google TV General] npjohnson:
No, you would need to port it.
[Google TV General] ali387:
I tried different cables and another PC with USB 2.0 port but no success.

What helped me move along was your suggestion on reddit to another person with similar issue: on wade.

update bulkcmd "reboot bootloader"

After that I ran:

fastboot flash recovery recovery.img

fastboot boot recovery.img

Now I can reboot to recovery but it has uncovered couple of issues with my device:

1. tapping on side button does not move to next menu item on recovery screen, I have to use remote to move the selection to factory reset.

2. once 'factory reset' is selected then I long press the side button. It turns the 'factory reset' to green/teal but no prompt comes up to format data. or any response from the recovery screen.

Has anyone run into this problem? Any suggestions to try?

PS: I have previously followed these instructions successfully to install LineageOS on to Onn device. (of course different image files)

PS2:

Here is getvarall output for my device (i case if this device is different from previous ones):

[root@fireiso ~/Downloads]# fastboot getvar all

(bootloader) hw-revision:0

(bootloader) battery-voltage:4

(bootloader) is-userspace:no

(bootloader) is-logical:data:no

(bootloader) is-logical:metadata:no

(bootloader) is-logical:misc:no

(bootloader) is-logical:super:no

(bootloader) is-logical:boot:no

(bootloader) is-logical:system:yes

(bootloader) is-logical:vendor:yes

(bootloader) is-logical product:yes

(bootloader) is-logical: odm:yes

(bootloader) slot-count:0

(bootloader) max-download-size:0x08000000

(bootloader) serialno:WUSA23******

(bootloader) product:franklin

(bootloader) unlocked:yes

(bootloader) has-slot:data:no

(bootloader) has-slot:metadata:no

(bootloader) has-slot:misc:no

(bootloader) has-slot:super:no

(bootloader) has-slot:boot:no

(bootloader) has-slot:system:no

(bootloader) has-slot:vendor:no

(bootloader) has-slot product:no

(bootloader) has-slot odm:no

(bootloader) secure:no

(bootloader) super-partition-name:super

(bootloader) version-baseband:N/A

(bootloader) version-bootloader:01.01.221216.094717

(bootloader) partition-size:boot:0000000001000000

(bootloader) partition-size:metadata:0000000001000000

(bootloader) partition-size:misc:0000000000200000

(bootloader) partition-size:super:0000000064000000

(bootloader) partition-size:data:0000000123dfc000

all: version:0.4

Finished. Total time: 2.259s
[Google TV General] npjohnson:
Use the remote, use the d-pad to navigate and then the power button on the remote to select
[Google TV General] sjustinas:
Any way to persist this across reboots?
[Google TV General] ali387:
Awesome. Thanks for all your efforts in building this nice OS. And supporting and guiding us in installing and use of the software.

I have successfully installed 5/14 build. It booted up fine and now it is downloading 5/21 update.
[Google TV General] fepij52921:
@npjohnson ?

Would you add support for this installer: https://openandroidinstaller.org/ ?

It only supports phones now, but other devices should be possible: https://github.com/openandroidinsta...ntribute-your-own-installation-configurations
[Google TV General] npjohnson:
To the unofficials? Probably not to be honest.

I don't feel like tailoring amlogic burn mode into that.
[Google TV General] fepij52921:
I was thinking of the official builds actually, are those supported by other developers?
[Google TV General] npjohnson:
Oh there's 0 chance of that.

It took the lineage infrastructure team two years to deploy the new download portal, very doubtful that something like that would be adapted, it would also require extensive wiki changes, and a much more systematic approach to changing it out.

Don't see it happening officially ever tbh.
[Google TV General] bumerc:
1. # BoardConfig.mk

BOARD_KERNEL_CMDLINE += hdr_policy=1

2. # recompile kernel

m bootimage
[Google TV General] npjohnson:
Is this something that makes sense to put in official builds?
[Google TV General] apropper:
Hi, I'm having a hard time trying to flash. I keep getting the device locked message in cmd when trying the "fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock" step in the instructions. I saw the quote above and...

I've got the worldcup drivers and I have my dynalink box recognized by amlogic usb burning tool. But I don't know what you mean by using "update program for worldcup. Please help.
[Google TV General] apropper:
Also what do you mean by amlogic update tool? I found Amlogic USB Burning Tool from websearch, not sure if it's the same thing.
[Google TV General] npjohnson:
same thing
[Google TV General] apropper:
Ok, how would I run a command from that program?
[Google TV General] npjohnson:
there's a tool called update in that burn tools package, run `update bulkcmd 'setenv lock 10101000;save`
[Google TV General] apropper:
Damn, I don't see that option anywhere. Is this the right program? I'm sorry if I'm being ignorant but all I need to do is unlock the bootloader and I'm at a wall right now.
[Google TV General] npjohnson:
no, use this https://github.com/khadas/utils/tree/master/aml-flash-tool/tools/windows
[Google TV General] apropper:
How do I use this? I dl'd all those files into one folder. Nothing happens when I click "aml packer" or "update.exe". Please explain further. I've installed lineage on my phone before and that was a piece of cake. This, not so much. I feel so dumb trying to figure this out.
[Google TV General] npjohnson:
it's a command line tool. Why are you doing this again?

You can run this from the boot loader instead - just use cmd not powershell
[Google TV General] apropper:
I was following the regular instructions from the wiki and couldn't get past the oem unlocking step to unlock the bootloader. Kept throwing "FAILED (remote: locked device)" at me.

This is what happened when I was in burn mode

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd 'setenv lock 10101000;save'

AmlUsbBulkCmd[10101000;save']

[AmlUsbRom]Inf:bulkInReply failed:

ERR: AmlUsbBulkCmd failed!

This happened when I restarted the device and did the reboot bootloader command

C:\Users\user\Downloads\aml-flash-tool>adb devices

List of devices attached

WUSA2301003863 device

C:\Users\user\Downloads\aml-flash-tool>adb reboot bootloader

C:\Users\user\Downloads\aml-flash-tool>fastboot devices

WUSA2301003863 fastboot

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd 'setenv lock 10101000;save'

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

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

I have world cup drivers installed, btw.
[Google TV General] apropper:
Okay, I followed Functioner's instructions and was able to run both "setenv lock 10100000" and update bulkcmd "saveenv" successfully. But now I rebooted and see a recovery error screen saying can't load android system. So I factory reset. Tried unlock bootloader command in fastboot and got this,

C:\Users\user\Downloads\aml-flash-tool>fastboot oem 'setenv lock 10101000;save' && fastboot reboot bootloader && fastboot flashing unlock

...

OKAY [ 0.038s]

finished. total time: 0.039s

rebooting into bootloader...

OKAY [ 0.007s]

finished. total time: 0.007s

...

FAILED (command write failed (Unknown error))

finished. total time: 0.002s

Rebooted, same recovery error screen telling me to factory reset. I don't mean to use you as my personal tech support, but what am I doing wrong here?
[Google TV General] apropper:
I'm pulling my hair out over this. Factory reset a couple of times, tried Functioner's instructions again. Here's what happens:

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd "setenv lock 10100000"

AmlUsbBulkCmd[setenv lock 10100000]

[AmlUsbRom]Inf:bulkInReply success

C:\Users\user\Downloads\aml-flash-tool>update bulkcmd "saveenv"

AmlUsbBulkCmd[saveenv]

[AmlUsbRom]Inf:bulkInReply success

C:\Users\user\Downloads\aml-flash-tool>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!

I get this error every time and have to factory reset. And I still can't unlock the bootloader through the wiki instructions either. I'm new here, so please don't accuse me of spamming, but I'm genuinely stuck and don't know what to do. It seems easy enough for everyone else to get this running. Ugh! Why can't I figure this out?!
[Google TV General] Functioner:
Your mistake was doing this:

after you had already unlocked the bootloader doing this:

You're relocking the bootloader by doing "fastboot oem 'setenv lock 10101000;save'" after you unlocked the bootloader using burn mode.

It's okay to do the factory reset after you unlock the bootloader using burn mode, as you did here:

The factory reset is required, as I explained in the post because unlocking the bootloader using burn mode is a non-standard way to do it, and it does not erase the data partition as part of the unlocking process (like fastboot does when it works to unlock properly), so a manual clearing of the data partition is required.

Repeat the burn mode unlock process, and the factory reset process, but then don't do any of this:
[Google TV General] Functioner:
Did you check for a fastboot connection after doing:

update bulkcmd "fastboot"

by running the command:

fastboot devices

Some of the error messages you see from the burn mode client reflect the change in connection type over usb from world cup connection (burn mode) to fastboot connection (using android drivers).

Check for a fastboot connection after running

update bulkcmd "fastboot"

using the command

fastboot devices

Just don't run any "fastboot oem" commands after that.
[Google TV General] apropper:
@Functioner thanks for the reply. So I installed the dbt and dbto files, then flashed recovery. I can't boot into recovery, and I'm stuck at the dynalink screen no matter if the cable is plugged into my computer or into the wall. I don't get any result at all when I type fastboot devices into cmd. Do I need to flash the stock firmware and if so, how to I do that?
[Google TV General] apropper:
So I did some looking around and found this from @npjohnson

https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-85425773

and put the device in burn mode and tried running the command `update.exe bulkcmd fastboot` and got this:

C:\Users\user\Downloads\aml-flash-tool>update.exe 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!

I do have worldcup drivers installed, it shows through device manager but after I run this command, I get a yellow triangle over the worldcup device in device manager. Please help, I'm trying to unbrick this thing.
[Google TV General] Functioner:
You're not able to get a burn mode connection anymore? I'm not sure that I know what state your device is in.

If you can't get a fastboot connection, forget about fastboot for the time being. If you are still able to get a burn mode connection, maybe try restoring the original dtb/dtbo/recovery using burn mode, like described at the top of this post.

Of course, you'd use the image files for your device, not the image files mentioned in the post.
[Google TV General] npjohnson:
different USB port or USB2 hub
[Google TV General] tannergt2:
Hi all,

I am trying to flash wade and i got into the same situation as @apropper, the official instructions work only until flashing the recovery image. Rebooting into recovery does not work, so I followed what was suggested here of using burn mode. `update bulkcmd fastboot` fails (aparently, at least), so it nevers enters into fastboot. In comments from previous releases of Lineage, some users say you can ignore that failing message and try to list the devices, but it does not seem to be the case anymore.

Any hints how to get into fastboot, or how to go back and try again the process?

Update:

I solved the issue by following the same steps but from Ubuntu and it works fine. So after `update bulkcmd fastboot`, still the same "error" shows up, just ignore it, and run `fastboot devices`, you will see the device will be listed. The same steps from windows do not work, in case someone else faces the same issue.
[Google TV General] Billionairez:
can teach me how to setup?
[Google TV General] dany0808:
Hello

I think this could be lil offtopic..

Does anybody knows if there is any chance to have a decent speed external storage on my dopinder?

Like some hack to speedup the micro usb otg or maybe a physical mod to main board for reading microSD/usb C otg
[Google TV General] Functioner:
Nice find! I had considered the possibility that usb might be behaving differently on windows as compared to linux, so I opened a windows session in a vm. It appeared to work the same, but the version of windows that I have installed is v8.1. I don't have windows 10/11 installed because they are such horrific advertising engines.

I remember changes in the way usb was handled just between windows 8 and 8.1, so I guess windows 10 and/or 11 might have more usb changes. When you open a command prompt or powershell window in windows 10/11, do you do it as an administrator?
[Google TV General] apropper:
Ok, so after getting a new box, following the instructions I've learned after the last couple of days, I was able to get it running. After unlocking the bootloader and doing a factory reset, I was able to flash the necessary files (though I did have to wrestle with reinstalling adb drivers to get it recognized in fastboot).

GOOD STUFF

- I'm genuinely surprised how well this runs. I was able to sideload apps no problem and so far everything works. The UI itself is really clean, no ads, no other bs. Remote works, bluetooth works, all that. Great job putting this together and I look forward to future updates.

NOT SO GOOD

- The instructions on the wiki are in DIRE need of updating. I don't mean to come off so critical, but there is no reason for someone to have to conduct hours of research when the outlined steps fail them.

- Also, you should all keep in mind that not everyone has the experience you do in using cmd and drivers and all that stuff. The main reason I had to make an account was because I'd see posts talking about terms without posting links, like it's given knowledge what worldcup drivers are and whatever else I was asking about before.

Again, not trying to insult anyone, I'm grateful for the help, I just want people to keep in mind how challenging this can be without properly safed instructions, and for those outside of the xda realm. I also want to reiterate how happy I am with my Lineage-infused box. Thanks again for all the hard work you've all done with this project, and good luck with your future endeavors. Peace and love.
[Google TV General] fepij52921:
Real bummer, it would be nice to have an easier way to install some version of this since it is far from smooth if it ever works.
[Google TV General] mmortal03:
Very doubtful. I'm imagining that if some sort of transparent compression formatting of external storage was supported in LOS 20, you might be able to achieve somewhat faster effective transfers of content using the USB 2.0 OTG connection. But what is the use case? You're probably going to have better luck serving the files over 5GHz wireless.
[Google TV General] hellerhd:
Hi @apropper,

Thank you very much for providing a general impression of the current ROM status. This looks very promissing!

Wiht your experience, couldn't you write up a short summarized Instruction 'how to install' for the 'non developers' to ease the process for them (and me :) ).

That would be great!

Thanks in advance.
[Google TV General] forart.eu:
For those interested in porting to Chinese boxes, someone is trying to adapt "LOS4AML" (GXM, Q200 - based on hertz build - in this case):

https://forum.freaktab.com/node/832145

Hope that inspires.
[Google TV General] sjustinas:
I would say probably yeah. I am not an expert on those matters though - not sure if there are any drawbacks. IIRC stock ROM's "Droid Settings" app eventually gained this option (Auto-HDR depending on the source), the default "HDR always on" behavior was perhaps a bit of a mistake.
[Google TV General] npjohnson:
done. Next build will have it.
[Google TV General] npjohnson:
Also great news, devkits are shipping now! We fixed the issue holding them back - so now it's just dopinder/Sabrina lagging - and I think strongly that dopinders 12 release upcoming will solve it's issue.
[Google TV General] niuxxd:
I have successfully installed LineageOS 20 (lineage-20.0-20230604-nightly-wade-signed.zip)on my Dynalink Android TV box, and most features are working flawlessly.

However, I am experiencing an issue with the volume control on my remote.

Strangely, the volume control does not work unless I connect the TV box with scrcpy at the same time. I have attempted to use KeyMapper to remap the launch app keys, but unfortunately, KeyMapper does not recognize the volume control key either.
[Google TV General] kennkanniff:
Thanks. I created an aml_upgrade.img for the M5 but it bootloops.
[Google TV General] npjohnson:
Uh. Did you sync the most recent changes?
[Google TV General] kennkanniff:
After re syncing and a make clean the build fails:

"acp: file 'out/target/product/m5/logo.img' does not exist"

Should I use the method in the wiki or #183?
[Google TV General] npjohnson:
183
[Google TV General] kennkanniff:
Build successful but still not booting into OS. It shows the text 'erasing' and then reboots.
[Google TV General] npjohnson:
"Erasing"? Are you sure you aren' t in recovery?
[Google TV General] kennkanniff:
I don't think so. It shows the Android TV logo and reboots then it shows a Lineageos logo with the 'erasing' underneath it and it reboots and repeats itself.

EDIT: It mounts as an MTP device when the lineageos logo is shown.
[Google TV General] npjohnson:
that's recovery.
[Google TV General] kennkanniff:
Okay, so it's in a recovery bootloop. Any idea why it does not stay in recovery?
[Google TV General] npjohnson:
use uart to interrupt u-boot and then fastboot reboot to clear the boot reason
[Google TV General] kennkanniff:
I connected the M5 to my computer with an USB to TTL converter. When I try to monitor the device is see nothing.
[Google TV General] npjohnson:
You should 100% get UART.

Maybe rx->tx backwards or busted ttl adapter?
[Google TV General] kennkanniff:
The adapter works fine on a RPI. I can get a shell. I use the same pins on M5 and have also tried the dedicated UART pins.
[Google TV General] kennkanniff:
How exactly does this work. Will I see any output in my console? Do I need to press some key-stroke to interrupt u-boot?
[Google TV General] npjohnson:
You will see a string that

You will see a string that is the boot ROM, you will then see BL2 logs, u boot, and then the kernel start.

When uboot happens just hit enter a ton of times

112500 baud
[Google TV General] kennkanniff:
I am positive my UART port is borked. I am able to boot into lineage recovery by holding SW1 button while booting but I can not select anything.
[Google TV General] npjohnson:
that's really abnormal.
[Google TV General] kennkanniff:
Maybe an DTB issue?
[Google TV General] npjohnson:
We flash our own DTB which has all that enabled. Let me ping the maintainer who owns m5.

But even if we messed up DTB, the first string should print, that's bootROM.
[Google TV General] Sant1936:
Anyway to enable miracast and adative storage on this thing? I noticed its disabled for some reason and Im not sure which magisk module is safe. Android version:12
[Google TV General] npjohnson:
miracast no, you'd need a reciever app downloaded - and adaptive storage, bad idea, USB2 is dog slow.
[Google TV General] Sant1936:
Got my technologies moxed up. When I said miracast, I meant chromecast. And when I said adtive storage, I meant a fix for scoped storage which I think was introduced in android 11?