yashsingh1/xdaforums huggingface dataset:
[Google TV General] the.real.p3y0t3:
Ok so a little unneeded panic there. BL unlocked fine AND serial console works fine. AML has some serious mods going on in their implementation of u-boot. ANYHOW, I recently ordered a set of two cheapo usb2serial adapters (prolific clones), which arrived a couple of days ago.... With SIX friends! Eight for the price of two? So yea, if anybody has a need for one, pm me your info and you'll get a early xmas present. And hey, dont just msg me because you want a freebie! You'll need a soldering iron and skills + a real need and interest in using one. This box is a good starting point or learning aid for the TX RX GRD pads are easily accessible. I personally put a usb female on it, and male on the adapter so I didnt have toi have wires connected all the time.... Ghetto fabulous!
[Google TV General] Functioner:
How do you provide access through the plastic case?

I installed a standard header and notched a hole in the case.
[Google TV General] ali387:
Wow serious stuff.

To both you and Functioner:

I would love to see a guide (or a link to a discussion) on how to open up the Onn box and attach a header. I have USB to serial cable and a soldering iron. Thanks.

UPDATE:

Found couple of pictures posted by Functioner. Got it opened without breaking any clips. I have header pins from college days (RPi labs). WOuld be great to see images of your pins/header installation to ONN 4k board.
[Google TV General] chadillac.q.roberts:
were you ever able to recover from the softbrick? I'm in the same boat. I downloaded Amlogic USB Burning Tool v3.2.0 but when I plug in the device it doesn't show in the tool. Online guides say I need to get to recovery mode but I'm not sure how to do that when adb and fastboot don't recognize it. I'm stuck on the onn. screen after attempting to flash a dopinder boot.img patched by magisk (before I found this thread).

update: I was able to get into fastboot mode by just not having the HDMI cable plugged in and plugging in the box while holding the reset button. still not fastboot flash commands work.

`FAILED (remote: 'unknown command') fastboot: error: Command failed`

Of course as soon as I ask a question (I've been working on this silently for 3 days now) I find a solution. For anyone else who has this problem:

Instructions to restore fastboot commands

From there I was able to just flash boot.img extracted from payload.bin from the ota.zip posted on this thread.
[Google TV General] bigfloppa234:
I think I screwed up my streaming box beyond recovery.. I was trying to flash stock factory images (turns out they were the wrong images) onto mine and now it won't boot and is detected as this in fastboot. It doesn't show anything on a display either

View attachment 5987255

Fastboot and adnl can't flash anything

View attachment 5987257

View attachment 5987259

Didn't even last 24 hours.. lol. Any help?
[Google TV General] Functioner:
Seems like you flashed the wrong bootloader at some point prior to the above.

There are two adnl modes;

bootrom adnl mode

bootloader (bl33) adnl mode

The adnl commands that you're using above will only work when your device has a bootloader (bl33) adnl connection.

But if you previously overwrote the bootloader with the wrong bootloader image, you won't be able to get a bootloader (bl33) adnl connection.

If the SoC can't boot the bootloader that is on the device, it automatically starts a bootrom adnl connection.

A bootrom adnl connection has very limited commands, and most of the useful ones are protected by a 16 byte password.

If what you have is a bootrom adnl connection, you probably won't be able to fix your device. It would be possible if the 2nd Gen walmart onn device had a sd card slot, but since it doesn't, probably the only way to fix it would be to write the bootloader directly to the emmc.

Maybe you can still exchange it for another one?
[Google TV General] bigfloppa234:
I'll exchange it if I can't flash a new bootloader - thanks for the information!
[Google TV General] disposablereviewer:
I did this exact same thing not realizing I had a different/newer model ONN box and was reading the wrong lineage thread entirely. All I see is the single pixel colored line when it boots as you described and I'd like to revert if I can.

Do you have the stock dtb.img or know how I can obtain it? I'm still able to get into fastboot without issue and flashing still works without errors. But I'm pretty sure flashing the incorrect dtb.img, dtbo.img, and/or recovery.img is my main issue.

Seems like flashing the original dtb files should fix it. I was able to extract the dtbo.img from the provided image in the second posting of this thread, but it doesn't contain the dtb.img. it didn't fix my problem to only reflash the correct dtbo.img unfortunately. I guess i need to also reflash the dtb.img and/or recovery.img but not sure where to find them.

I can potentially run through all your steps you did to fix your issue, but I suspect that might be overkill since fastboot flashing is still working for me and I'd rather not risk it if I don't need to. maybe that's the only option to resolve this though if the stock dtb.img can't be found.

Or has anyone else run into this problem and fixed it somehow and know the steps?

EDIT: for anyone else in this same situation, the solution to recover the device is outlined in this thread
[Google TV General] bigfloppa234:
Exchanged my bricked Onn streaming box for a new one. Is there any way to make a backup of every partition on the device?
[Google TV General] treypop:
If you unlock the bootloader I think you should be able to with TWRP using commands
[Google TV General] bigfloppa234:
Where do I find a build of TWRP for this device?
[Google TV General] Functioner:
It's not exactly for this device, but others have reported that it works. I haven't tried it:

#43

No video output, just adb shell.

I used uart shell in stock recovery to dump the partitions before ever setting up the device.
[Google TV General] kalehrl:
How does adb actually work in twrp?

You just boot it with that command and a USB cable plugged in your computer, issue 'adb devices' and you see your device listed? After that you can issue adb commands and they stick after reboot?
[Google TV General] bigfloppa234:
Worked for me. How exactly do I dump the partitions though?
[Google TV General] groovey 2 shoes:
Question how do you delete keyboard history? 🤔
[Google TV General] treypop:
You should be all clear it's storage and that should clear the history
[Google TV General] genesan:
I've went through multiple posts here on XDA relevant to the ONN 4K Walmart Android TV box, but it seems there has yet to be a plain-jabe guide of any sorts related to Rooting/Unlocking this device. My overall goal would be to make the device as close to AndroidTV, that is, with the ATV Launcher and whatnot, as possible. The play store that comes on the device is very limited and I purchased this device hoping there'd be a root/jailbreaking guide but knowing I could very well brick the device attempting to follow such a guide. So, if I missed anything in plain site, I apologize, but my questions are...

Is there currently any known root and..

Is there currently any custom recovery images for this device, (such as TWRP, Red Wolf, etc).

Thanks in advance to anyone monitoring this or able to provide feedback/advice!

CG
[Google TV General] BTK19:
Thread '[OFFICIAL/UNOFFICIAL] LineageOS 20 for Amlogic GXL/GXM/G12*/SM1/NE Family Devices' https://xdaforums.com/t/official-un...ic-gxl-gxm-g12-sm1-ne-family-devices.4534935/ there is that
[Google TV General] BTK19:
Or this one. Thread 'Walmart ONN Android TV' https://xdaforums.com/t/walmart-onn-android-tv.4313411/
[Google TV General] BTK19:
Unless your talking about the 2023 Onn with google TV in that case this is the thread for it
[Google TV General] genesan:
Yeah this is the device I'm referring to...

I just bought it a couple of days ago from Walmart so I'm pretty sure this is the right thread.

I'm seeing a lot of posts regarding soldering and UART/Console/command-line options and I've never got into learning all of that. I get ADB and Fastboot, and I've dealt with flashing and custom recoveries and ROMs for years but my limited knowledge stops at console commands and actually modifying the physical components internally...so I'm guessing that's where development currently is...if so, I'll just keep checking back and trying to learn more about UART and the like.
[Google TV General] BTK19:
There is this Thread. '[Guides] 2023 Walmart ONN Google TV' https://xdaforums.com/t/guides-2023-walmart-onn-google-tv.4610749/
[Google TV General] groovey 2 shoes:
It didn't clear the keyboards memory of typed words
[Google TV General] gmjh:
I'm kind of surprised that no one has mentioned anything about using Kodi with this. Here's the issue. The onn box will not output anything but Stereo pcm on Kodi. Yes I've got audio Passthrough on Kodi and the TV. I've tried every single audio combination on the onn box, on Kodi and on the Tv. It doesn't matter what your try the onn box will always output nothing but stereo pcm with Kodi. It won't even do Dolby 2.0. It will of course do Dolby 5.1 on any streaming app. I'm not really looking for a solution here, I don't think there is one, just pointing out this issue which probably isn't even the fault of the onn box. It's probably some limitation of the latest Google TV build.
[Google TV General] treypop:
Magisk has updated recently. Is it safe to update it through the app?
[Google TV General] treypop:
I just tried it and it will try to patch the boot partition. I forgot Magisk can't automatically patch the RAM disk
[Google TV General] gmjh:
In case anyone finds this post on a Google search then the solution is to change the default sound setting of 'Passthrough audio device' from 'IEC Kodi Packer' to 'RAW Android Packer'. I've never had to change that setting before but it looks like it has to be used by Android 12 on Google TV boxes.
[Google TV General] darkvoid:
This is correct, the settings for my Onkyo receiver are:

Allow Passthrough: On

Passthrough output device: AudioTrack (RAW), Android IEC packer

Dolby Digital (AC3) capable receiver: On

Dolby Digital Plus (E-AC3) capable receiver: On

DTS Capable receiver: On

With this threw all the DD5.1, Atmos, DD+, DTS, DTS HA & DTS MA samples I have at it and they all played fine.
[Google TV General] gmjh:
That's right. And if it's on IEC Packer (Kodi), which is the default setting, then the Onn box will not output anything other than stereo PCM from Kodi. Which is a shame because most people using the Onn box will assume Kodi can't passthrough 5.1 etc and just delete Kodi.
[Google TV General] deskjet390:
What did you do to the vendor_boot.img to get magisk to work?

I have been trying to find guides or details on modifications you have to make to the vendor_boot.img and havent been able to find anything that says what we need to insert.
[Google TV General] Functioner:
Adb connection issues are more likely to be caused by PC hardware or PC operating system issues.

Try ruling out these issues by using different PC hardware/operatiing system, or, if this is not possible, by using a different usb port/cable, or connecting to adb over wi-fi instead of usb.
[Google TV General] ali387:
Thanks for your astute suggestion. Appreciate it.

Used Win10 PC with the same USB cable. Working fine now.

I had switched to the Linux machine due to non-functioning fastboot on Win10 PC.
[Google TV General] dmarshn:
Could somebody please explain if there is a way to access and edit the "android/data" folder on this device?

I have gone through the process to root my 2023 onn box but still, when i try to "adb push .kodi /sdcard/android/data/org.xbmc.kodi/files/" it tells me "remote secure mkdirs failed: Operation not permitted"

Literally the only thing I am trying to do is move my kodi build onto my storage. Ever since android 11+ it seems to be impossible. I have tried multiple devices, and just about every possible file explorer and even installing the missing "files" app. I have tried pushing through adb to different locations too and unzipping in the kodi folder, and even though Mixplorer has root, it will not allow me to extract in that folder. The gui pops up for a split second and then disappears.
[Google TV General] kalehrl:
You can make a backup of your Kodi using 'adb backup' command:

adb backup -apk org.xbmc.kodi -f "location\on\your\pc\kodi.adb"

Then restore it using 'adb restore' command:

adb restore "location\on\your\pc\kodi.adb"

It works this way for sure no matter the android version.
[Google TV General] dmarshn:
I appreciate your response, but I am not sure it will work in my case.

The "backup" that I have is on my PC. its just my kodi data folder. I do not have it on an android device yet, that is my problem.

I tried making a backup of the standard kodi install using the method you described, and I was going to put my files in the backup and then restore them to the device, but the backup that gets created is just 1 single file that is not editable or accessible on windows as far as I can tell.

I have already rooted my device, how is there no way for me to access that android/data folder?
[Google TV General] kalehrl:
Did you try running Kodi once so that /sdcard/android/data/org.xbmc.kodi/files folder is created?

Then run:

adb push .kodi /sdcard/Android/data/org.xbmc.kodi/files/

'Android' must be capitalised.
[Google TV General] dmarshn:
Yes I installed kodi and let it run so that the folders were created. This is the message i get when trying to adb push to that folder...

adb push .kodi /sdcard/Android/data/org.xbmc.kodi/files/
adb: error: failed to copy '.kodi\addons\context.seren\addon.xml' to '/sdcard/Android/data/org.xbmc.kodi/files/.kodi/addons/context.seren/addon.xml': remote secure_mkdirs failed: Permission denied
adb: error: failed to read copy response

Is there something I need to do to ensure that ADB is connecting to my device with root?
[Google TV General] kalehrl:
Try running:

adb shell chmod -R 777 /sdcard/Android/data/org.xbmc.kodi/files
[Google TV General] dmarshn:
No luck, just outputs a bunch of "Operation not permitted" spam. Does that imply that root is not working? I was able to grant root perms to Mixplorer when magisk prompted me so I would assume that means its rooted.
[Google TV General] kalehrl:
What happens if you run 'adb root'
[Google TV General] dmarshn:
Comes back with "adbd cannot run as root in production builds"

Then I tried adb shell > su and I was prompted by magisk to allow root access to shell, but still no luck in editing the android/data folder :/
[Google TV General] Dionicio3:
anyone else having issues connecting USB devices? I tried a keyboard and mouse as well as a thumb drive, and the box doesn't recognize any of it
[Google TV General] deskjet390:
You have to turn USB debugging off and then reboot
[Google TV General] ali387:
Thanks for pointing this out. Solved my issue of why USB Ethernet was not recognized or working.
[Google TV General] eagledipesh:
I have gen 1 Walmart onn box, after updating to latest July update, the Google voice on remote control stopped working, earlier there use to be flashing green lights on remote now the green light just stays on, anyone facing similar issues with latest build?
[Google TV General] Dismal.:
Have you tried removing the batteries and putting them back in
[Google TV General] eagledipesh:
Yes done all that, even did a reset, is it working fine for you, I was thinking of going back to previous release but don't know how to do it without unlocking the bootloader.
[Google TV General] Dismal.:
I dont have this device but I do have the Chromecast with Google TV and wanted to make sure that you at least tried this
[Google TV General] brickerGod:
hello guys, i need some help with this device, i tried to install lineage dopinder and now its bricked without chance of booting into full fastboot, so i cant use fastboot flash command, it shows

[yo@arc ~]$ fastboot devices
0099d5110280070f00000000 Amlogic DNL

i dont have an uart programmer so idk if i can fix via usb and aml_flash_tool (in linux) since it can be detected...

i followed these steps but after fastboot reboot bootloader it doesnt show the device anymore in fastboot devices

[yo@arc ~]$ fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.050s
[yo@arc ~]$ fastboot devices
[yo@arc ~]$
[Google TV General] bigfloppa234:
I had the same problem and ended up exchanging my bricked unit for a working unit.
[Google TV General] ragarcia87:
You can do

fastboot reboot bootloader

This will get you back to full fastboot
[Google TV General] brickerGod:
in my message i said what happened with that command already... i cant see my device in `fastboot devices` after `fastboot reboot bootloader`
[Google TV General] Functioner:
There are two types of adnl connections. One type is established at the bootrom level, the other type is established at the bootloader (or tpl/u-boot) level.

The latter requires a working bootloader, and is the only type of adnl connection that will work with the "fastboot reboot bootloader" command.

So, it seems possible that the bootloader on your device is corrupted, and the adnl connection you're getting is a bootrom adnl connection. This type of connection won't be of much use in fixing the device, since it is password protected.

You can verify the type of adnl connection by using one of the adnl host side tools for amlogic adnl mode. There are linux and windows versions. Another way to tell is if the adnl connection is instantaneous upon connection of the device to a usb port on your PC, then it is probably a bootrom adnl connection. If the adnl connection takes a little while, or requires that you hold the reset button to obtain it, it is probably a bootloader adnl connection.

https://dl.khadas.com/products/vim4/tool/
[Google TV General] brickerGod:
this is the case, i need to press the reset button to enter into

[yo@arc ~]$ fastboot devices
0099d5110280070f00000000 Amlogic DNL
[Google TV General] Functioner:
If you have a monitor connected to the hdmi output while doing the above, is the onn boot logo shown on the screen? If it isn't, then it isn't a bootloader connection. What does the device do if you don't press the reset button?

Instead of typing "fastboot devices" at the stage shown in your quote above, type "fastboot oem help" and reply with the output returned.

As shown in this post, a bootloader adnl connection should always display "fastboot", not "Amlogic DNL", in response to the "fastboot devices" command:

C:\---path--to--fastboot-adb--->fastboot devices
XXXXXXXXXXXXXXXXXXXXXXXX fastboot
^^24 digits^^

C:\---path--to--fastboot-adb--->fastboot devices
GUSAXXXXXXXXXX fastboot
^^14 digits^^

The response returned for the "fastboot devices" command that:

has 14 digits (beginning with GUSA) is a bootloader fastboot connection.

has 24 digits is an adnl connection

So, the fact that you're seeing "Amlogic DNL" in response to the fastboot devices command probably means that your connection is a bootrom connection.
[Google TV General] brickerGod:
1.if i connect it without pressing anything, i get into the "onn" boot logo, `fastboot devices` doesn't show anything and `fastboot oem help` keeps in `< waiting for any device >`

2. if i connect pressing the reset button, it doesnt show me any display, its without any signal and it shows me

[yo@arc ~]$ fastboot devices
0099d5110280070f00000000 Amlogic DNL

then,

[yo@arc ~]$ fastboot oem help
OKAY [ 0.082s]
Finished. Total time: 0.082s
[yo@arc ~]$

and `fastboot reboot bootloader` sends me to the same as point 1
[Google TV General] Functioner:
That's a good sign. That means the bootloader is working. You should be able to fix your device, and the "fastboot reboot bootloader" command should work. I don't know why it isn't working. Perhaps it is some issue with the version of fastboot that you're running, your PC, or your OS.

There is a connection type change after "fastboot reboot bootloader" is executed. Perhaps there is some problem with the connection type change with your setup.

The other possibility is that the device is some kind of recovery bootloop, such that a reboot to the bootloader is not possible.

You'd probably need to connect the uart to know for sure. And that might just be the beginning of a complex process that would take a lot of your time. Best just to exchange the device if you can.

You can use the previously mentioned adnl host side tools (at the khadas link) to use the adnl connection to write partitions directly (without first rebooting to fastboot), but I'm not optimistic that doing this would fix your device.

You could also try some other version of fastboot, including a windows version, if you haven't tried already.
[Google TV General] brickerGod:
when this happened, i didnt got the fastboot device one time so i reinstalled android-tools hoping it will save the same device keys but after the reinstall i lost the adb permission... i though my fastboot was broken so i tried to reinstall to see if it shows the device again via usb
[Google TV General] Functioner:
Device keys aren't applicable at the bootloader stage for a fastboot connection.

An adb connection that requires device keys exists only in userspace. Your device isn't booting that far.

I don't think I'll be able to help you.
[Google TV General] Groovygrover:
I have the 2023 onn 4k tv box, and after receiving some updates today it seems that the box reset itself. Google TV was re-installed and several apps were added, but my original apps remained and are even functional. Apps like Tivimate and Stremio still work fine. However, no matter how I try, I can no longer access settings. Also, the home button no longer works. I tried re-pairing the remote but that didn't work. Voice access did not work either. The only button on the box that I found is next to the HDMI connection and it is associated with pairing the remote, not for resetting the unit. I can use the partially bricked onn box it as is for a while, but it is a major pain not having access to the home button. Also it is only a matter of time before I will absolutely require access to the settings menu. At this point I don't even know how I can do a factory reset without access to settings or a reset button. I have resigned myself to buying another unit and setting it all up again, but I am open to any ideas or suggestions anyone on this forum might have. Thank you for any advice!
[Google TV General] Rolaand Jyayz:
Hold the button next to the HDMI when you plug in the power and it should reboot to recovery where you can enter fastboot or do a system restore. The same thing happened to me. First I couldn't get into developer options. Then I couldn't got to the system tab in settings. Then i lost all settings. After restoring, no more issues and I have full access to all settings. I think the issue is cause when you open magisk and choose to update and flash directly. This is because it flashes the boot.img and not the vendor_boot.img. I have stayed away from that option and all of my settings are still accessible. You will not lose root when you restore the system. If you already bought a new one, be aware not to flash from magisk and now you should have what you need to restore your previous 2023 box and keep the root.
[Google TV General] matrix200200:
Change default launcher on dopinder?

I have lost dolby sound after the latest December update and tried to rollback.

As a result I got into a bootloop and had to reformat.

Now I am no longer able to set default launcher to Nova like it used to be before the whole ordeal.

How do I disable Google TV Home launcher?
[Google TV General] silenzi:
is there an easy way to keep the walmart onn 4k box from updating android, i have tried moving the option to off but it doesnt seem to stop updates, apologies for derpy question bit new to all this thanks
[Samsung Galaxy S22 Ultra] pattiking:
As shown in the title
[Samsung Galaxy S22 Ultra] V0latyle:
Did you search before posting? It's Rule #1.

Guide

It is well known that US market Samsung devices with Qualcomm SoC's are typically not bootloader unlockable.