yashsingh1/xdaforums huggingface dataset:
[Google TV General] Hig13:
I just used my phone and said to the assistant "set up a new device" or something, then I was able to connect it to wifi.
[Google TV General] dirtcat:
Hmmm ... now the boot screen won't come up at all!

I'm going to unplug this and leave it for a while.
[Google TV General] tokoam:
So is there a guide on how to install Magisk ?
[Google TV General] Hig13:
Spoiler content hidden.

Now, I have a question. Does anyone know how to remap the keys to the remote without using "Button Remapper"? I don't want to use an external app... but I guess I will if I have to lol...
[Google TV General] alan_harake:
Will this ROM ever get fixed? Honestly all it needs to be just about perfect is for video playback to work smoothly and the on screen keyboard to work. Not asking for an ETA, just wondering if these are issues planned to be resolved sometime.
[Google TV General] hp420:
i spoke too soon the other day saying this wasn't it. this was exactly it!!! the otg cable was blocking adb and fastboot commands. i removed it and this went perfectly, thanks!!!
[Google TV General] tokoam:
Can we safely do Magisk boot.ing

Does anybody know if its safe to flash magisk upgrades through the magisk app ? I know last time I tried to flash the the upgrade for magisk in the app on my 4k firestick it bricked the device . Also does anybody get greenscreens on booting ? It has issues booting 60% of the time .Also I have adb enabled but it keeps saying "No connection could be made because the target machine actively refused it" . Also after just one day of using this I get this on my display you can faintly see the image on top left corner . I cannot fix it it comes back on every reboot or power reset .I can hear my self clicking around so I know its in the OS but cant see anything . I have tried fastboot -w command to try and reset ? didnt work same image comes up . Also when I tried to rerun the the whole rom install it now says in ADB device offline . I need some help guys this is a wierd issue .

*EDIT ( I was able to get ADB working again I reflashed the rom and it fixed the strange video tearing image you see in the pic . However if the monitor or tv is not on the input and I switch to it after the fact it gives me a green screen )

May be some wierd memory bug ?
[Google TV General] hp420:
on screen kb works fine for me 🤷 so does video playback....perfectly smooth at 1080p. maybe it's on your end?
[Google TV General] alan_harake:
Lots of users on this thread do not have a working on screen keyboard nor working 4k playback. Can't even go through the setup without using adb on a computer since no keyboard.
[Google TV General] Hig13:
I also had the no keyboard issue after flashing this rom on the dopinder. But, I was able to get through the setup just fine without it. I just told my google assistant on my phone to add a new device and I gave it wifi access from there. Though not having the gboard and having to download some other keyboard kind of turned me off, along with a few other bugs I was seeing like the green screen any time I switch the device to a different display with a different resolution, and some glitchiness happening at the beginning of any playback. So I flashed back to stock and just rooted so I can debloat things.
[Google TV General] alan_harake:
I been wanting to flash back to stock. Is there any way to do it without a otg hub and a keyboard?
[Google TV General] dirtcat:
I just bricked mine completely trying to do this while following the official instructions. Careful!
[Google TV General] hp420:
what?? just use the android tv remote app on your phone 🤦🏽 it works perfectly!!

Android TV Remote Control - Apps on Google Play

Android TV Remote

play.google.com
[Google TV General] alan_harake:
lol considering this rom has less features than stock, this isn't a solution anybody should resort to.
[Google TV General] samsungs3neos3neos3neo:
Laptop. I figured it wouldn't matter because it's a USB 2 micro usb device that needs a USB 2 cord. But I just tried it with a docking station that has USB 3 and had the same issue.
[Google TV General] samsungs3neos3neos3neo:
I tried two different 3 ft cables, plus a 1 ft cable
[Google TV General] zimmie:
I have filed a bug report on lineageos site.
[Google TV General] treypop:
I've had similar problems before and for me it was a fastboot driver problem
[Google TV General] wyldwilly:
Thanks! I just did on OTA upgrade to 1110 build on dopinder: upgrade worked great (just like my phone) but DRM is still broke. Is this expected?
[Google TV General] npjohnson:
Yup! I've said it before and I'll say it once more - I have no clue what is wrong with dopinder and Sabrina.

Potentially could be something related to the /factory partition having some differing component I haven't yet figured out.
[Google TV General] talksickisil:
So for Sabrina does that manufacturers date of the dongle itself as well as firmware need to be older than February 2021 like I saw on GitHub ? Or is it only the firmware I would need to downgrade. Please let me know. I have one on the way and love saving time on Sundays
[Google TV General] npjohnson:
No, safetynet is almost unused on ATV.
[Google TV General] S1ngl3-x:
I finally got my Wade working. I could not boot recovery before flashing rom. The key was to just partially plug in micro usb so that only power works but not the data transfer. After recovery showed up I have fully plugged in the cable and adb (data transfer) started working.

This tip saved me a ton of time. I have even bought a second dynalink and tried like 6 microusb cables.
[Google TV General] swim9988:
Hey everyone, I just bought wade on the rec of people in here (thanks for the insight, apologies for not replying in-thread).

I got stuck in the reboot to bootloader step that many others seem to have trouble with. I foolishly unplugged to restart, and now it doesn't go past Dynalink screen, and I can't get fastboot (or adb).

I'd really appreciate some help, I'm at a loss for anything I can do. Thanks!

(I did try that half-plug-in idea stated 1 post prior, but the device hangs on "Dynalink" whether plugged into wall, computer, or half-plugged into computer)
[Google TV General] S1ngl3-x:
Did you also hold the button for 10 seconds as is written in the manual?
[Google TV General] swim9988:
Yeah, nothing happened....
[Google TV General] js8call:
Succes with Dopinder and latest build, finally!

There is a quirk related to adb reboot recovery..didnt work after flashing lineagerecovery..but just I was about to restore to stock using the latest unbrick technique here on this thread, when it asks to unplug and press sidebutton until the worlcup drivers turns on, all of a sudden I got to recovery!

Sadly, its true..most free streaming apps are not fully operational..Most streams are DRM protected..FreeVee, Plex, some Tubi streams..

now, the challenge is Viper4Android..the magisk V4A module is useless, even installing the Audio Library module before..I tried to install by the old way, but busybox no longer works..

Help?
[Google TV General] npjohnson:
this is digital out over HDMI - and then processed by your endpoint - I am really not sure what if any benefit V4A could possibly have.
[Google TV General] js8call:
Thks..Bluetooth volume is insanely low..I tried with several BT headphones, too low..I just would like a bit louder..
[Google TV General] :
When dtb from lineage-19.1-20221110-UNOFFICIAL-dopinder is flashed, what is going on here:

_cmp_partition()-591: name: factory<-> factory
_cmp_partition()-592: size: 800000<->800000
_cmp_partition()-593: offset: 3fc00000<->3fc00000
_cmp_partition()-594: mask: 0000000b<->00000011
_cmp_iptbl()-630: partition 7 has changed
mmc_device_init()-1354: update rsv with dtb!
init_part() 297: PART_TYPE_AML
partition table success
[Google TV General] npjohnson:
I appreciate what you're trying to thought is going on this one, but not the layer which I meant, the layer where I suspect the issues are. Is the factory partition being mounted correctly and accessible in the user space level, at the moment we don't mount the factory partition, but stock does.

My confusion here is the Deadpool doesn't have this partition, Wade does, but apparently doesn't need it mounted, and Sabrina's is of a different name. I should have some time to look into this coming up soon.
[Google TV General] talksickisil:
Does anybody use Sabrina here? I would be able to just downgrade to an old stock image before feb 21 on a brand new ccwgtv and go from there? I noticed there’s no dtb or dtb0 to flash. Which is why I ordered it.
[Google TV General] :
I wasn't really trying to do anything, except understand. What's kind of unusual about dopinder is that the fat12 image is always fully populated in the factory partition, with the file names and data. Any dump of the factory partition, at any time, and the data will always be there.

Most other certified devices, factory will only occasionally have the fat12 image. More often the partition will be empty. It's just luck to dump out factory with the fat12 contents, more often it will just be empty, other than a header. I assumed that it was being emptied after the tee sucked it in somewhere else.

Anyway, I won't ask anymore irritating questions.
[Google TV General] npjohnson:
Oh, sure,

So the DTB partition isn't a typically enumerated partition, any attempt to flash it is first verified for validity as the DTB is used by u-boot, and the device likes to make sure it isn't bricking itself. It then does the equivalent of dd'ing to the hidden partition _aml_dtb, which is only exposed to the user space as /dev/dtb, not as a block device.

unrelated to the factory partition.

And yeah, factory image being empty is normal, except on amlogic where the contents are semi random per device lol.

And no, it isn't emptied by TEE post provisioning, it depends what TEE you use and how it is handled, QCOM for ex reads these once at time of provisioning into NVRAM.

Amlogic devices either hardcode them or slap them in /factory - there isn't a standard way to do so, as I don't really think AML initially intended their boards to be L1 DRM compliant? In BSP's that compatibility is even added later than other features.

You aren't irritating me at all! Sorry if it came off that way, more than happy to have people tossing out ideas!

Also, check my DM when you get a moment.
[Google TV General] npjohnson:
No. Antirollback prevents you from going back, it will brick.
[Google TV General] talksickisil:
Oh… okay 💔💔thanks for letting me know!! I used Walmart + delivery (it never came even though it was promised for today) I did order delivery from the store though. I’m hoping I get one that’s been in the same place for a long time. I messed up my onn flashing dtb and dtb0 now it just doesn’t boot. The tool you linked in the faq that link for that version is dead. I tried using aml burn tool and aml flash tool nothing I did resulted in any success. So I gave up. But now knowing this, I’d love to fix this problem with the onn/dopinder. I can’t find it with adb devices no matter what I do. The burning tool that has you load stock images to flash to the device every time I would fail the check. It’s like not even the burning tool can make a connection. I can’t boot into recovery either.
[Google TV General] talksickisil:
Again thanks for the update! Because of your update I went ahead and canceled the ccwgtv and ordered a dynalink/wade. Can I use the onn remote with it? Also… if anybody has a recent solution to fix dopinder not connecting to adb or booting recovery none whatsoever do I get anything but the “onn” screen please let me know the most updated solution. And for wade is it better to get an official nightly build or unofficial build?
[Google TV General] npjohnson:
yup!

Wade is way better
[Google TV General] talksickisil:
Nice!!!! Thanks bro. What’s different between the weekly official builds and your non official builds? Where should I start?
[Google TV General] swim9988:
I apologize, I'm sure bumping one's own question is frowned upon, but just to follow up, does anyone know if there's any way to salvage Wade hanging on Dynalink screen? TIA
[Google TV General] :
Have you tried using a burn mode connection to write back the factory dtb, dtbo & recovery? Something like described here and here?
[Google TV General] edwrapxda:
A few notes on the wiki for wade that I think have been mentioned already, but I’d forgotten when I installed today:

1) the device reboots after unlocking, but back into fastboot mode. A “fastboot reboot” reboots again into the normal system

2) “fastboot reboot-recovery” doesn’t work and should instead be “fastboot boot <recovery_filename>.img”. (edit: this only seems to work after using aml-flash-tool) This is probably the step most likely to inadvertently lead someone to think they soft-bricked their device

3) power button on remote is the OK button in the lineage recovery

4) as someone that hadn’t installed lineage before, there maybe should be a warning not to erase the system partition in the factory reset section. edit: actually, I re-did the whole thing from stock without erasing /system and still didn't have wifi again

5) that aml-flash-tool and the commands to flash the various partitions should probably be stickied somewhere, as that saved my bacon

Everything seems to be working now, but there were some confusing moments along the way (mostly due to my own stupidity). Thanks to the developers and people in this thread!
[Google TV General] nixikec:
Would something like https://auroraoss.com/ or similar app store, run on the official builds? Like it does on a firestick?
[Google TV General] S1ngl3-x:
I use aurora store all only and it works reasonably well. However it's far from it's proper functionality. Still very useful nonetheless.

Far better than fdroid on android tv. I had to sideload via adb both of them.

If anyone has android tv store recommendations I would love to hear them.
[Google TV General] stmdisco32:
I have a deadpool device that was previously running ATV9. I flashed dtb, dtbo, recovery as described in the wiki. When sideloading lineage-19.1-20221110-UNOFFICIAL-deadpool.zip, I get:

E:[liblp]Logical partition metadata has invalid geometry magic signature
Target: ADT-3/adt3/adt3: 12/STT1.211025.001.Z4/7928020:user/release-keys
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))

I also tried flashing super_empty.img, but it didn't help. Is this a matter of doing some manual repartitioning?

Thanks!
[Google TV General] npjohnson:
Did... Did you say Android 9? That was never officially available for Deadpool lol - you sure?

And try flashing stock super image, then going back to lineage.
[Google TV General] stmdisco32:
I flashed super.img from deadpool-rtt1.200909.003.A2-factory and that fixed it up! Thanks
[Google TV General] npjohnson:
so weird - Deadpool even, before the adt3 rebrand - that is not normal. Where did you get this device?
[Google TV General] stmdisco32:
Long story, but it's clearly an engineering sample of some kind. There's no markings on it at all.

Thanks again for your help.
[Google TV General] npjohnson:
if you live in the US and are interested in potentially selling that - DM me.
[Google TV General] swim9988:
Thank you, no I hadn't seen that and haven't tried yet.

It looks like the WorldCup driver listed is for windows, but the flash tool is for all OS's. Do you know if linux drivers exists, or should I look at wine/VM (or borrow windows machine)?
[Google TV General] genesan:
Oh yeah, one more thing I wanted to mention, as I thought this was odd...

I already closed the term window unfortunately BUT I noticed when running the "fastboot getvar all" command that the device was identified not as dopinder but as "franklin"...anyone else notice this? Just thought that was weird but not important or anything-just curious I guess :)

Thanks Again, everyone!
[Google TV General] :
The stick version onn device is not a supported device for this lineage build. It runs the 805y amlogic SoC and android 9. You can really mess up this device if you flash the bootloader/dtb/dtbo from these builds to this device.

Rooting it will also be difficult because even though the device is readily unlockable, the bootable partitions are signature verified. You should be able to disable whatever apps you are concerned about using adb though without root.
[Google TV General] genesan:
Sorry, I was a little unclear. Yes, you are correct...the FIRST device I purchased was the stick unit that was a couple of months ago, though. I don't recall what it's codename was but it couldv'e been "franklin". However, the device I am referring to as being codenamed "franklin" according to the "fastboot getvar all" output is ACTUALLY the newest Onn BOX I've purchased, NOT the stick. So I'm using the box that correctly matches the image on the LineageOS page, the small square box that requires an HDMI cable as opposed to the stick unit that plugs directly into an HDMI port, like a Fire Stick would. And yes, attempting to use a firmware or firmware contents for one device on a different model is probably always a bad idea-so I'd leave your comment just in case someone might try to make that "newb" mistake that even I made (which I knew better but eh, it was on sale for like $14 so no big loss). Thanks for the feedback, though...I still appreciate the effort, friend :)

Sincerely-

G
[Google TV General] :
You're correct. I've updated my last post. The stick version is stephen, not franklin.

If you've only been working with the box version, you should be fine.

Apologies for the error.
[Google TV General] edwrapxda:
I thought the HDR was fixed recently? (edit: or maybe not, see page 68) I’m still seeing HDR always on or always off depending on the TV setting, and not changing depending on the video file. This is with wade on the latest nightly with two different TVs and a bunch of different video players

The post before yours has a quote with some links to commands to run with the aml-flash-tool, which you’ll probably want to use to get out of your predicament. There’s both a windows and linux version available. I used it on linux yesterday without issue to recover a wade device

edit: this is the specific post that I followed initially that got me into lineage recovery successfully
[Google TV General] genesan:
No worries :)
[Google TV General] genesan:
I actually went ahead with the flash...despite some bugginess that I suspect was all on my end and/or user error, ha. MUCH to my surprise, it worked but I'm not getting WiFi connectivity...would doing a factory reset be safe as long as it's from the same LOS Recovery it should just factory reset like a phone would, do you agree? Because I know some ROMs, when flashing them on devices to test/build, require you to do a final fastboot -w after rebooting from a successful flash BEFORE booting into your new rom's first boot...if I have to go back to recovery firmware I'm probably not going ot have much success. I'm using MX Linux ATM, wondering if one of the handful of Linux distros I have would be much more efficient in doing this...or even dual-booting WIN10...I don't know how to I could've lost the drivers or hardware compat for WiFi but I'm also assuming that stuff is all in the system/super images and not modified when flashing a custom LOS rom?
[Google TV General] talksickisil:
So my dopinder doesn’t even power on whatsoever anymore. But I’m actually here for help with wade. I have the lineage recovery and dtb and dtbo flashed. When I enable adb sideload my computer doesn’t connect. Not even with adb over wifi either. I’m thinking what went wrong was following the instructions on the installation guide. It tells me to wipe the data and cache BEFORE installing LOS. But doesn’t doing that wipe the boxes saved fingerprint of my computer??? Please help me fix this somebody!!! If I have to do the soldering to serial port I’m a total noob and don’t even have an iron. Photo of my two hopefully temporary paper weights. If I can get the wade up and running I’m golden. I’ve tried booting in recovery’s fast boot mode the bootloader mode and nothing. Adb nor fastboot work. I wish it was possible to flash from “sd card” aka my usb flash drive And OTG on this Recovery. I am so damn close but yet so far!!! With little hope
[Google TV General] js8call:
Went back to stock..finally managed to get Viper4Android working..I had to Magisk Selinux change first..although the Bass and Clarity are not enabled, the rest are more or less working and it helped a lot with the low BT volume..
[Google TV General] npjohnson:
The fingerprint has nothing to do with anything.

You don't need so solder. You're in recovery.

Check device manager and see if something shows up, you probably have a driver issue. Or change your USB cable/port - you're fine.

dopinder's like to randomly die! I've had two die.

I think they use ****ty emmcs.
[Google TV General] talksickisil:
I used Linux mint to get to that point. I don’t think drivers will change much. That flash tool you link on page 3.. version 4.7 of the FLASH tool and not the burn tool I can’t find anywhere! Every version of the flash tool I tried pretends to connect to the box thru adb. I proved it by leaving the box not plugged into anything and it would still say “connected” but I can boot into windows again if the correct tools are out there. Thanks.
[Google TV General] npjohnson:
if you can get to recovery then why in the world are you using burn mode?
[Google TV General] talksickisil:
Yeah I can’t get to the settings I have the lineage recovery installed but factory resetting it after flashing recovery I’m pretty sure is the problem here. When I had the dopinder working, I did a dirty flash accidentally and then factory reset afterwards and I was good.

Now to explain my picture here. On the left is dopinder on the right is wade. What is the name of the connector soldered to the right of the micro usb port ONLY on the wade??? Is that rs485? Can I buy an rs485 to usb adapter for the control+c thing mentioned on page 3? Because I can’t solder. I’m hoping this is my out.
[Google TV General] npjohnson:
factory resetting is fine just fine. Does nothing that would hard your ability to boot into recovery.

I have no clue what that tiny header is called. It is not rs485 lolol
[Google TV General] talksickisil:
Because when I enable the adb sideload in recovery, it says adb enabled ready for sideload etc and I still can’t connect to adb or fastboot 😭 . If there’s a way to get it working again without burn mode I’d love to know of it. Hell I even went thru most of this thread I tried adb reboot sideload but obviously with no adb connection it does nothing
[Google TV General] npjohnson:
So you select sideload in recovery and it shows you a device in adb devices?
[Google TV General] talksickisil:
Nothing shows up on adb devices nor fastboot devices even when I use recovery to manually reboot its fastboot or bootloader
[Google TV General] npjohnson:
Does anything show up in dmesg upon connection?
[Google TV General] talksickisil:
Bro thank you so much for answering my questions. Update: so if you have a micro usb OTG hub, you can plug in a keyboard and a flash drive with the lineage OS .zip on it, the lineage recovery will pick it up. But it won’t show the option to install from storage until the flash driver is connected to the OTG. I needed the keyboard to navigate recovery. Photos showing me flashing from storage in case this is news to anybody. If this is old news then sorry, I’m late to the party!!! Anyways it’s time for me to set this baby up!!!