yashsingh1/xdaforums huggingface dataset:
[Google TV General] zweiund40:
Hi, since some time is passing by and i've read here that it doesn't need to go back to android 10 to install this (changes in the wiki) i've trying again to install Lineage 20 on my wade.

Unfortunaly i have the same issues than before to unlock the bootloader.

I've got always the info that my device is locked.

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

FAILED (remote: 'locked device')

fastboot: error: Command failed

What i'am doing wrong?

Tryed it under Linux and Windows 11. Developer Options activated, OEM Unlock is greyed out, wade recognize the connected Devices (adb connection establisehed), in fastboot mode wade is present. Wade is on Android 12.

thx
[Google TV General] J_Woo:
Issue them as 3 separate commands by removing &&

You may just need to go back into fastboot and issue: fastboot flashing unlock
[Google TV General] J_Woo:
Want to commend the developers. This ROM is really good and WADE performs quite well. Memory management, use of storage and performance are a ton better than stock devices. Well done!!!!
[Google TV General] npjohnson:
try just running fastboot oem 'setenv lock 10101000;save' and let me know what it says.
[Google TV General] zweiund40:
hi, thanks for your answer. Tryed this out before and now again with the same result - locked device

$ fastboot oem 'setenv lock 10101000;save'

FAILED (remote: 'locked device')

fastboot: error: Command failed
[Google TV General] zweiund40:
hi, tryed it out some time before, doesn't work :-(

fastboot flashing unlock

FAILED (remote: 'unlock_ability is 0, can not unlock')

fastboot: error: Command failed

thx for your help
[Google TV General] Functioner:
Try "burn mode". Obtain worldcup drivers and command line "update" program for your OS.

Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;

update bulkcmd "setenv lock 10100000"

update bulkcmd "saveenv"

Then reboot and see if fastboot works for flashing. Don't repeat the oem commands in the quote above. If you have trouble getting a fastboot connection, use "burn mode" again to start a fastboot connection:

update bulkcmd "fastboot"

Note that changing the lock variable value often requires doing a factory reset. The recovery "rescueparty" menu will prompt you if this is necessary.
[Google TV General] npjohnson:
Boot to burn mod using the button on the side and plugging in, then use amlogic update tool to run "update bulkcmd 'setenv lock 10101000;save'"
[Google TV General] npjohnson:
This, his instructions are better lol
[Google TV General] linux2023:
I also updated to android 12 stock but that was intentional as the official LineageOS instructions for wade said to update to stock 12.0 first. So the instructions should be changed.

EDIT: I FIXED IT BY REINSTALLING THE STOCK ROM VIA BURN MODE AND INSTALLING LINEAGEOS AGAIN

I ran the latest 20230416 official build and that finally boots up unlike the older official versions (latest unofficial did work fine) although my wi-fi isn't working at all (latest unofficial works fine). No networks are detected and when I toggle wifi to on and go out of settings and go back again it still says it's turned off.

Anyone can help?
[Google TV General] zweiund40:
Thx a lot! That worked for me to unlock the bootloader.
[Google TV General] npjohnson:
I'll update instructions soon.
[Google TV General] J_Woo:
Any way to fix sleep mode so the remote can awaken WADE just like the official builds?
[Google TV General] npjohnson:
Uh, it does here - you need to pair it via Bluetooth, maybe you're only using IR?
[Google TV General] Skyty1991:
Hmmm... Do you have any recommendations for cables then? Cause I'm running out of ideas.

I've tried 3 different cables on 3 different laptops. One laptop has 4 ports, the other 3 and the other 2. I tried all 3 cables on each port on the laptops.

The closest I ever got was the noise that your PC makes when you plug the device in, that was then immediately follows by the disconnecting noise. Most of the time it just made the disconnecting noise when I plug it in. Not to mention up until the point I flashed the dtb and dtbo files my cable and port recognized the Onn.

Did anyone else experience this issue with the Onn and find a way to resolve it?
[Google TV General] Slimshady997:
Do you know if lineageOS for dopinder is already stable or if there is a version, I have seen that they talk a lot about version 18.1, do you think that this is stable? If so, where can I find it, thank you very much.
[Google TV General] Boundless7927:
Apologies for a maybe silly question, but can I use dopinder without having to login to a google account for set up? I'll just be using Jellyfin on this and no play store.
[Google TV General] cannondale0815:
Yes, I had to try four different cables before I found one that works. Very finicky.
[Google TV General] Skyty1991:
Part of the challenge is even finding a micro USB cable... I could only find one at Walmart and it was a hybrid that had a dongle for USB C and iPhones.

Do you happen to know the brand that you used?

Were you experiencing the same issue that I was above?
[Google TV General] cannondale0815:
It was just one of my plethora of random cables at home, unbranded. In my case the device wasn't recognized by the Windows laptop at all (didn't show up in device manager) until the fourth cable I tried.

I would look on Amazon and buy a few name brand cables, for example from Anker.
[Google TV General] Skyty1991:
That's the weird thing for me though. The cable is was using was working up until I flashed the dtb and dtbo files. Then it just stopped being recognized. Doesn't seemt o be a rhyme or reason to it.
[Google TV General] npjohnson:
Sadly I don't maybe a powered one? That splits data and power.

No, it was never stable - 18.1 used software rendering - couldn't even do 1080p right.

If you flash gapps you need to login, if you don't you don't.
[Google TV General] talksickisil:
It’s been a bit since I’ve downloaded a build or even used “wade” one thing that has came in my absence maybe: but how do I reboot after holding down the power key? I get the 3 circles now. (Power off, restart, and screenshot) I can’t figure out how to make a selection. I’m sure I’m missing something obvious here? Is it an issue using the onn remote with the dynalink box now? I prefer the full Bluetooth of the white onn remote and haven’t had this issue previously. I have a wireless keyboard and mouse plugged into the OTG but it would be nice to use the remote for power cycling. Thanks in advance for setting me straight
[Google TV General] Skyty1991:
Well, if my math is right I tried 108 different combos. I have a powered USB port with 4 ports. I tried 3 cables on all 4 ports between 9 USB ports between 3 different laptops and still nothing.

It just made the connecting noise followed by the disconnecting noise.

I wish I had the link but I recall someone saying that you could force it into burn mode or something through Linux? Something about a way that you could force the computer to ping a USB port?

Does this ring any bells? I'm at a bit of a standstill so I'd be willing to try some stuff.
[Google TV General] link1375:
Sorry, I am new to this topic. You stated that the ROM should not be installed on a similar device. Does this mean, that even if the same SoC is used, the ROM should not be installed? For instance, the Dynalink TV Box (wade) has the Amlogic S905x2 installed, like the Strong Leaps-S1 (https://www.strong.tv/de/products/ip-tv-receivers-de/leap-s1/). Can I use the ROM for the Leap-S1?

Also what are those "Amlogic GXL/GXM/G12*/SM1" family devices? E.g. I cannot find any results on google regarding Amlogic GXL.

​
[Google TV General] npjohnson:
GXBB = s905

GXL = s905x

GXM = s91w

G12A = s905x2/y2

SM1 = s905d3/d3g

Basically what I was trying to say in the title, and as I say later in that post is that these trees will support all of those SOCs, but that developers will largely need to port the device themselves.

Really you will need to fork the device most similar to yours (if it's s905x2 use wade), replace the variables in lineage_$target.mk to match your device, add the DTS files for your specific devices to the kernel directory, and build the correct module for your wifi/BT chip.

It's pretty straight forward. Only additional porting piece may be sepolicy changes for your hardware.
[Google TV General] link1375:
Thank you for the info. Do you have general sources I can check on how to build my own custom ROM (regardless if it is android or android tv/google tv) for a device of my choice? Including ways to avoid bricking the device while debugging the ROM?
[Google TV General] npjohnson:
The wiki linked in OP has a build guide!

Additionally almost impossible to brick these as long as you have access to burn mode.
[Google TV General] bumerc:
Hi, i have a question about porting QCOM wifi, chip qca9377, to gxm platform, soc s912. As I noticed, the default here is the old legacy HAL, which apparently does not work properly. The qca9377 driver works and loads fw, wifi can be activated in the settings, but after entering the key, the connection to the wifi network does not occur. The connection attempt fails after a while and the available networks disappear from the settings. Android logs are not available, since adb is activated only with working wifi. Can you advise me anything about this?

Perhaps the use of wcn6740 HAL will bring positive results, have not tested yet..

Thanks for your work!
[Google TV General] npjohnson:
qca9337 I think has some newer releases under Deadpool's source code on Google source - not sure though.

Deadpool packed all wifi drivers in pretty much haha.

I'd look and try that but I'd need logs to helpful further.
[Google TV General] bumerc:
Thank you for your reply. I am attaching some log files here :)

If you need filtered logs, or any other type of logs.. let me know

Here is the download link to the logs

edit: corrected link
[Google TV General] PhoneThe4th:
I have attempted to install the official LineageOS 20 builds on 2 new, separate Dynalink (wade) devices (both updated to the latest Android 12 official builds [security patch Oct. 2022]) and both have bricked after the step "fastboot boot recovery.img" is entered in adb.

It goes to a black screen after boot attempt and just hangs there indefinitely (waited about 10-20 minutes). I attempted to see if fastboot was still able yo recognize the still plugged in device on my adb (on PC) and it does recognize a device, but now the fastboot ID only shows '????????' and is unresponsive after trying any fastboot commands.

I was forced to unplug the usb. Both devices now are bricked as after re-plugging the usb cable back after, adb and fastboot doesn't recognize either device.

As a precursor, I am very experienced in degoogling devices and installing ROMS, but for this, I followed the official instructions to the letter as this is not a phone, which I am most familiar with.

Is the instructions faulty and needs updating? Is the latest official wade OS update preventing something in its security patch? Any help would be useful as I probably will try a 3rd attempt and quit if I get the same bricking issue.
[Google TV General] roswellraygun:
From what I can tell, the ones labeled "Google TV" rather than "Android TV" are the new ones and I've heard they use the S905Y4. I picked up a couple and confirmed they are using Cortex-A35 (rather than the A53 of my dopinder). I'm assuming a new tree is a pretty big lift? I've never done Android build work, but is there anything I could do to help?
[Google TV General] npjohnson:
Not really. And to be honest we likely won't be making said new tree until ADT-4 comes out.
[Google TV General] linux2023:
This happened because you updated to android 12 stock. Have you already installed dtb and dtbo images? If you did, you first needed to reboot to bootloader again and afterwards should've booted to the recovery.img. If you're soft-bricked you need to enter amlogic burn mode and unbrick via aml-flash-tool (linux only).

stock roms: https://download.ods.ninja/Android/firmware/

aml-flash-tool: https://github.com/khadas/utils (download zip)

Unbrick:

Enter amlogic burnmode by powering on the device whilst holding the button.

cd /home/[username]/build/utils-master/aml-flash-tool/tools/linux-x86
./update partition dtbo /home/[username]/Documents/wade/los20_20230416/dtbo.img
./update partition _aml_dtb /home/[username]/Documents/wade/los20_20230416/lineage-20.0-20230201-dtb-wade.img
./update partition recovery /home/[username]/Documents/wade/los20_20230416/recovery.img
./update bulkcmd fastboot

You can now decide to install stock rom or try lineageOS again. You can find the stock rom via OP post.

Here's what I did to install lineageOS:

adb reboot bootloader
sudo fastboot flash dtb lineage-20.0-20230201-dtb-wade.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot reboot bootloader
sudo fastboot flash recovery recovery.img
sudo fastboot boot recovery.img

Here's what I did to install stock:

adb reboot bootloader
cd /home/[username]/Documents/wade/wade-qt.20210326-factory/
./flash-all.sh (you may need to give permissions, do sudo chmod +x flash-all.sh)
[Google TV General] PhoneThe4th:
Thank you for the great info, that unfortunately is missing on the LineageOS official wiki instructions, especially on recommendation to upgrade to the latest Android 12 update. I'll try your advice on my next 'wade' device tomorrow, and have some kind of linux device to try burn mode to fix bricking issues. I'll relay my results.
[Google TV General] S1ngl3-x:
I also cannot even restart after updating. The restart menu is different (contains circles) and I cannot select a single thing.

Also KODI accounts are reset with app restart. The issue appeared after updating the system not the Kodi.
[Google TV General] talksickisil:
You can restart from the settings menu but yeah, same.
[Google TV General] Sant1936:
How do I get magisk working on stock? I tried flashing the recovery first, but it only booted into the custom recovery when I did that. The second time I tried without the dtb and o, but wouldn't boot at all. (I accidently flash 2021 stock recovery first, so that might have something to do with it) Now I patched the stock boot from op's post with magisk, but that caused a boot failure as well. Did I flash the recovery wrong?
[Google TV General] Sant1936:
Fixed. Here's how I rooted my dynalink without recovery.

-Make sure you're on the latest firmware and bootloader is unlocked.

-Download the backup tool from https://xdaforums.com/t/official-un...-g12-sm1-family-devices.4313743/post-86327923

-Boot your device in amlogic flash mode by holding the button on the side when turning on and run the backup bat

-Wait until finished. You should have a folder with the boot.img

-To make things easier, use webadb to install magisk to your box and transfer the boot.img

-Patch the img with magisk

>Use webadb again to download the patched boot.img

>Exit webadb and start regular adb on your pc.

-Reboot into bootloader

-Fastboot flash boot (Name of patched boot.img)

-it should succeed. Fastboot reboot.
[Google TV General] npjohnson:
Good news for all - the new ONN box and the newer generation of devices can be supported by the current tree.

Will just need some work.

We will 100% need the ADT-4 to be released though.
[Google TV General] TTcell:
Fingers crossed that there won't be any problems with L1 (widevine) and the 2nd generation ONN Google TV box.
[Google TV General] talksickisil:
I never successfuly used the flash tool on my dopinder/onn that being said, you can also just use the boot.img from the lineage download page, patch in magisk, then install with fastboot. Never heard of webadb I assume its wireless adb? I'm going to look into this tool thanks for mentioning it
[Google TV General] Sant1936:
Never knew that boot.img was stock. At least you have a full backup this way. I found it easier to run the backup tool first, and then booting into flash mode.

Webadb is just adb in your browser. I figured since you're doing the root process while connected to pc, you might as well use webadb to install apps and get the patched boot.img faster
[Google TV General] espionage724:
I have a Onn 4K streaming box (the rounded square UHD one for $20), and ended up stuck at the Onn boot screen with no adb/fastboot detection after trying to follow the instructions on the LOS device page. I recovered it with this on Ubuntu 23.04.

I ended up flashing 20230326 first following the directions about dtb and dtbo and using the images found inside that LOS archive, flashed the same date recovery downloaded from the build site, booted it, sideloaded 20230326, and it booted fine! I then sideloaded 20230417 and it worked fine too.

Overall, it's significantly faster! Now that it's done, what can I do with it? :p The one thing I think could be interesting is replacing the HOSTS file but I have to figure out how to do that; I'm thinking mount a partition from recovery and pull, edit the file, and push it back to the device?

Also, is it possible to change the display resolution, or disable HDR?
[Google TV General] tenfox:
Continues to be a great rom, thank you @npjohnson!

I recently upgraded to 20.0-20230423-nightly (rooted) on my wade, and noticed an odd issue:

I have been experiencing intermittent CEC issues where my wade's remote will stop controlling the volume of my theatre receiver over HDMI and fails back to just showing me the android volume popup. I am not sure of the source yet (it may be the receiver, cables, or something completely outside the wade). I'm pretty sure it has to do with some sleep mode on the wade or an app being power managed, though I haven't tracked it down yet. But anyway, during one of these issues, the wade's system->reboot menu choice changed to 'Reboot to Safe Mode' rather than just 'Reboot'. Odd and I'm not sure what exactly triggered that, but the problem is what happened next.

After rebooting to safe mode and back again to normal, it disabled both Wifi and Bluetooth. Wifi was no problem to toggle back, but (unless I'm blind) I couldn't find a system menu setting for bluetooth. I eventually had to reenable bluetooth through shell. IR continued to work fine for the remote.

I'd welcome any thoughts on the CEC issue, and I can't yet reproduce it reliably. But mainly I wanted to post to suggest making sure bluetooth settings are in the system menu or otherwise toggleable so someone else doesn't get randomly stuck without their (BT mode) remote.

Thanks again!
[Google TV General] talksickisil:
Maybe it isn't stock. I remember reading use stock in the instructions but I just went ahead and did it. Had no problems.
[Google TV General] ji:
Anyone been experiencing troubles with casting on builds? Been unable to do that or use the virtual remote using MindTheGapps - errors in logcat seem to point to some kind of certificate that never got generated

might steal some blobs from @npjohnson's build if his is working :unsure:
[Google TV General] npjohnson:
On the official?
[Google TV General] ji:
oops shouldve specified, self build signed w/ my own keys - synched mindthegapps inline build - i am thinking its the actual GMS apps but im not too certain - grabbing ADB now
[Google TV General] npjohnson:
strange - should work fine - is this wade?
[Google TV General] ji:
correct - heres best ADB stuff I could find, its something related to certs when I try straight casting instead of the remote that errors out with some kind of cert issue also

05-05 13:07:45.638 7352 7401 D AtvRemote.ConnectedClients: Client 192.168.1.51:60674 connecting
05-05 13:07:45.654 7352 30135 I AtvRemote.PacketReaderThread: Communication starting with 192.168.1.51:60674
05-05 13:07:45.681 3284 3284 D AmlogicKeymaster: id: 1, ctx: 0xf17c0890, cmd: 4
05-05 13:07:45.695 3284 3284 D AmlogicKeymaster: Received 24 byte response
05-05 13:07:45.699 3284 3284 D AmlogicKeymaster: id: 1, ctx: 0xf17c0890, cmd: 8
05-05 13:07:45.699 3284 3284 D AmlogicKeymaster: Received 24 byte response
05-05 13:07:45.700 3284 3284 D AmlogicKeymaster: id: 1, ctx: 0xf17c0890, cmd: 12
05-05 13:07:45.742 3284 3284 D AmlogicKeymaster: Received 276 byte response
05-05 13:07:45.791 7352 30135 V NativeCrypto: SSL handshake aborted: ssl=0xe8c63b98: Failure in SSL library, usually a protocol error
05-05 13:07:45.791 7352 30135 V NativeCrypto: error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN (third_party/openssl/boringssl/src/ssl/tls_record.cc:592 0xe911a460:0x00000003)
05-05 13:07:45.794 7352 30135 W AtvRemote.TcpClient: Incoming connection from unknown device 192.168.1.51:60674
05-05 13:07:45.795 7352 30134 W AtvRemote.ConnectedClients: Client 192.168.1.51:60674 connecting failure
05-05 13:07:45.797 7352 30135 W AtvRemote.PacketReaderThread: Failed to prepare input stream for 192.168.1.51:60674

for casting:

05-05 13:17:35.358 3347 5046 W resolv : SSL_connect write error 0, mark 0xf0064: Try again
05-05 13:17:35.360 3347 5046 W resolv : TLS Handshake failed
05-05 13:17:35.362 3347 5046 W resolv : query failed
05-05 13:17:35.363 3347 5046 W resolv : validateDnsTlsServer returned 0 for 2001:48f8:300b:11a0:5a9c:fcff:fe10:63e
05-05 13:17:35.367 3347 5046 W resolv : Validation failed
05-05 13:17:36.156 3347 5101 W resolv : SSL_connect write error 0, mark 0xf0064: Try again
05-05 13:17:36.158 3347 5101 W resolv : TLS Handshake failed
05-05 13:17:36.160 3347 5101 W resolv : query failed
05-05 13:17:36.161 3347 5101 W resolv : validateDnsTlsServer returned 0 for 192.168.1.1
05-05 13:17:36.164 3347 5101 W resolv : Validation failed

full logcat: https://pst.moe/paste/djoxfy
[Google TV General] ji:
annnd just realized whats wrong - for some reason mediashell isnt making it into my system even when its included in the target files, time for me to do some digging!
[Google TV General] npjohnson:
oh that would do it lol
[Google TV General] ji:
no idea why, im just synching mindthegapps and nothing else

When it tried registering packagemanger would error out with "No APK Signature Scheme v2", so I just flashed gapps seperately and that got around whatever the issue is

However, TV remote service is still broken with the same error as previously pasted above (TLS handshake fail)
[Google TV General] ji:
and just double checked and the remote issue persists on the unoffical oddsolutions builds
[Google TV General] mmortal03:
Someone (@dysoct ) asked the same question a few months ago, but I don't think anyone had an answer for him: https://xdaforums.com/t/official-un...1-family-devices.4534935/page-4#post-88122433
[Google TV General] tenfox:
Set /sys/module/am_vecm/parameters/hdr_policy to 1, SDR will play as SDR, HDR will play as HDR.
[Google TV General] dorkshoei:
I was finally able to get my Radxa0 working using 18.1. Many thanks to npjohnston for his extensive help via PM. There were quite a few issues that needed to be corrected to get it working.

I managed to adjust device/radxa/radxa0/lineage_radxa0.mk so it now builds standard Android, not Android TV (the default).

Couple issues:

1. The initial boot splash before initial Lineage animation still says Android TV. How do I fix this?

2. The display I'm using is 1920x1080 but it rotatable and I'd like the default orientation to be portrait. How do I reconfigure the build so the default orientation is portrait. Also, the initial lock screen seems mis-sized (too large so it's outside the screen size). Is this what is controlled by TARGET_SCREEN_{WIDTH,HEIGHT}? If so, I'm unsure how forcing portrait mode impacts how you specify height and width.

Thanks!
[Google TV General] dysoct:
Yeah 😅 But glad I'm able to figure it out myself. Same answer as @tenfox gave. Also just in case you updated to official wade's A12 and wanted to try out LOS 20, just need to flash dtb from LOS 19 in order for it to boot up (also by trying it out myself).