yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console Computers General] :
What sometimes works when the above happens is to re-initiate pairing mode on the device (the keyboard in your case) during each step. Start pairing mode once to get it detected, then re-start pairing mode from the beginning again when the screen transitions, then maybe even again while it is attempting communications. It might take some trial and error to get it paired successfully. If this sort of process will even work, of course.

All of those apps will run fine on the userdebug version. Apps that won't run are those that have a keymaster certificate, or verify attestation, or check for root, like netflix and peacock and some other major apps. The only free app that I know of that verifies attestation is tubi.

I will send you a private note with instructions. I don't want to be responsible for anyone bricking their device, even if they got it for five american dollars at the wall store.

My guess is that bluetooth functionality will be the same, but there is only one way to find out for sure.
[Android Stick & Console Computers General] Kate6:
That would be most appreciated!
[Android Stick & Console Computers General] jahrule:
Pushing the edited apk shouldn't be a problem or better yet we can include it into the system.img
[Android Stick & Console Computers General] ooftymcgoofty:
By flashing the debug rom and then yours from post 13 would I be able to get rid of the google ads on the home screen? Would you be able to tell me how to flash your rom without the bootloader? Thank you!
[Android Stick & Console Computers General] lamobius:
Can some one post instruction please how to update tivo 4 k firmware using 4515.zip file ?

Thanks
[Android Stick & Console Computers General] ooftymcgoofty:
Hi, I do not need to use otg with mine. Maybe try without and if that doesn't work try a different cable?

As for the flashing process, I am hoping to see a reply with guidance as well. Good luck!
[Android Stick & Console Computers General] ghettiguru:
I had a similar problem, the only way I was able to flash the device in USB burning mode was to make sure you have a better USBA to micro USB cord laying around. The one that comes with the tevo to power it doesn't support data transfer so it wouldn't show up. Once you know you have a good cable you must be a to micro USB for the power cord port, unplug it from the tivo but leave the USBA plugged into your computer not the wall, as you will be using the power port to flash. After a couple of hours and a few cords, The best way is to start holding the small reset button on the side of the Tivo box, then plugin the micro USB cord that's plugged into your laptop not the wall charger, then while holding the reset button plug in the micro USB and keep holding button till first it will show device is in fastboot mode, keep holding reset button and it will finally kick into USB burning mode. And if you had the USB burning tool w the debug firmware loaded already MAKING SURE TO UNCHECK BOTH erase buttons in the tool, loading password bin in the settings under input password or something, since you had the tool set to start it should start flashing as soon as it boots to USB burn mode with a good micro USB cable. Good luck and don't brick devices ppl lol
[Android Stick & Console Computers General] ghettiguru:
How do we keep debug firmware tho? I flashed to the 2225 debug build in his Google drive using USB burn tool but am force updated to firmware 5614 and required to activate on TiVo and immediately loose the debug build I need for root. And no OEM Unlock option. Is there a more recent debug firm I need root and can try building a Frankenstein img using android kitchen app but there seems to be a step I'm missing as I'm forced back to retail
[Android Stick & Console Computers General] ooftymcgoofty:
Wondering if anyone knows how to prevent the tivo from updating-through adb or otherwise. There are some workarounds on firestick blocking updates with adguard, but I can't identify which apps on the tivo are responsible for updates. I have a new one that wants to update to 5614, which is fine, but I just want to prevent it from going any further in the future. Thanks.
[Android Stick & Console Computers General] vettejock99:
I understand how to adb sideload things, do remote adb connect flash stuff, etc., but I don't understand which specific tool and process you're referencing for this device. Do you have a guide or links you could share? That would be awesome!

EDIT - Okay, I'm starting to connect some of the dots. The flash tool must be the Amlogic app from the Drive link.

EDIT 2 - Yeah, that tool wants an .img file to flash. The 4515 zip file has the various partition .img files not the entire group in a single flashable image. Looks like I need to search for a guide that has the full list of commands to flash the various files.

Search goes on....
[Android Stick & Console Computers General] ghettiguru:
You are correct you use the USB burn tool you just have to load the image and the burn tool from the zip in his drive, this device is different than phones and stuff I have been unable to find a boot.img ECT even after flashing. My problem now is STAYING on debug firmware as it updates me off to 5624 as I have to wipe data to flash and am forced to update and reactiva
[Android Stick & Console Computers General] vettejock99:
@jahrule Looks like I'm stuck as are others. I have several Stream 4Ks so it wouldn't be the end of the world if I bricked one but just trying to understand the steps. All are de-Tivo'd but none are running the debug firmwre - they're running the latest public v9.0-5.4.1 with PI.5614 release-keys. I can't tell if I can/should flash the debug firmware, and how in any case I'd then be able to use the zip file you provided previously, or the 4515 zip file to upgrade.

Any chance you could hammer out a short X-step how-to?
[Android Stick & Console Computers General] vettejock99:
Well I'm stuck on 5614 so 5624 would be progress, I suppose. I can see how the data wipe and reactivation would be a PITA.

Does the debug firmware have a more full-fledged recovery that allows for sideloading of updates? The stock one doesn't seem to allow that for me.
[Android Stick & Console Computers General] ghettiguru:
Typo lol 5614 I meant. I'm about to try to go from a fresh wipe install of the debug build, boot to bootloader and see if it will allow me to disable verity ECT maybe will bypass force update (which probably won't work because I have to toggle OEM unlock and can't bc I'm never actually booted to debug before force update) before going to a Frankenstein build with debug bootloader and 5614 system or something crazy
[Android Stick & Console Computers General] vettejock99:
Went ahead and took one of my devices through the debug firmware flash process and yeah, I totally see what you're talking about with the forced update being a PITA. I was going to block some of the firmware check queries at the firewall and while I've blocked a lot of the Tivo activation and other stuff temprorarily if it gets even a whiff of an update it won't let you stop it and with a recovery wipe it is still there.
[Android Stick & Console Computers General] ghettiguru:
I'm thinking about downloading that guys 5614 build and editing the build prop to trick the device into thinking I'm on version 5614 but doubt that will work. I'll post
[Android Stick & Console Computers General] lamobius:
How do I update to the android 10 using zip file or there is img file attached , I see only 4515 zip , after I installed the debug build from his Google drive ?

thanks
[Android Stick & Console Computers General] lamobius:
Any chance you could provide out a short X-step how-to flash 4515 zip file ?
[Android Stick & Console Computers General] reticularimus:
hello vettejock99 would you please explain to me how to turn off the built in root. i know how to install magisk but how to disable the existing root in android 10 debug build. also please explain how to install LSPosed. please explain all of these steps like you giving the instructions to a three year old because i'm not an egghead nerd this is my first post.
[Android Stick & Console Computers General] lamobius:
hello reticularimus , how did you update to android 10 firmware ?​

I am getting following errors when trying to adb sideload

C:\adbLink>adb sideload 4515.zip

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

Thnaks
[Android Stick & Console Computers General] reticularimus:
never mind vettejock99 someone else helped me i got it now thanks anyway.
[Android Stick & Console Computers General] vettejock99:
@goapy @jahrule Hey fellas, look like the steps are coming together, but the key part as to how you flash the debug zip since it isn't an img file is still missing. Can you help us understand how to do that?
[Android Stick & Console Computers General] :
A single image of the type used by the gui burn tool could be made but it is not that much more difficult to just flash the partitions individually. Others in this thread have managed to pull it off.
[Android Stick & Console Computers General] vettejock99:
Understood, but is there a complete list of those commands specific to this device somewhere? Or do I just I just ignore the non-img files and flash images to partions, e.g.:

fastboot flash recovery recovery.img

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

..etc

I'm more used to phones and some of these partitions I've not run into before.
[Android Stick & Console Computers General] :
The number of devices automatically getting the ota has increased this week, so you could just wait for that. It shouldn't be that much longer. If you don't want to wait, see the list of commands sent.
[Android Stick & Console Computers General] vettejock99:
I probably will. I hate to sound dense, but where is the list of commands sent? Here in the thread somewhere I didn't see? Decoding the updater-script?
[Android Stick & Console Computers General] :
I sent it to you in a conversation post about an hour ago. It looks like it is still there to me, but maybe you can't see it?
[Android Stick & Console Computers General] vettejock99:
Got it - thanks!
[Android Stick & Console Computers General] jahrule:
Sharing things via DM does not encourage open development. The 10 beta build i have not tried because there was no open instructions.
[Android Stick & Console Computers General] jahrule:
I didn't provide that zip and the person that did share didn't provide any instructions. Again, sharing things via DM does not foster development. Please ask the original poster how to use the zip s/he uploaded.
[Android Stick & Console Computers General] vettejock99:
Fair point. And I didn't share it because I imagine he/she had reasons for doing it via DM vs. posting it here or it would've been done already. I didn't even actually end up using it as the push came through the next morning, but the instructions could be helpful for a future build.

With a build that has all the appropriate files, one could possibly follow these steps to flash them in a single fastboot session before rebooting, but they could brick their device and I cannot vouch for any files or steps (as I didn't end up doing them) so caveat emptor:

fastboot flashing unlock

fastboot flash bootloader bootloader.img

fastboot flash boot boot.img

fastboot flash dtb dt.img

fastboot flash dtbo dtbo.img

fastboot flash logo logo.img

fastboot flash recovery recovery.img

fastboot flash vbmeta vbmeta.img

fastboot reboot bootloader

fastboot flash oem oem.img

fastboot flash super super.img

fastboot erase data

fastboot erase cache

fastboot reboot
[Android Stick & Console Computers General] :
The over the air update is available to all now. There is little, if any, reason to manually update now.
[Android Stick & Console Computers General] :
Public discussion also leads to quicker patching of useful functionality.

The bootloader is the master of the control of this functionality. The OS has the general ability to be configured to "ask" the bootloader to do things.

In order for an OS side setting to work, it would need to be respected by the bootloader.

In this case it is not. At least specifically when it comes to oem unlock functionality, as precisely defined. This does not mean that there aren't plenty of other holes.

The way that Fire TV development got around this sort of limitation (of an uncooperative bootloader) was to patch the bootloader on the fly every time in memory.
[Android Stick & Console Computers General] jahrule:
If public sharing of information and development is something you are worried about, then maybe this is not the right hobby for you.

Note: upgrading with OTA will block usb burning tool and one wont be able to reflash the debug version from the google drive. Also, the OTA one is not a user debug build
[Android Stick & Console Computers General] jahrule:
Thanks for sharing. You are missing a step there to flash system.img for future people.
[Android Stick & Console Computers General] jahrule:
https://www.tivocommunity.com/threads/fully-extracted-tivo-stream-4k-rom.584788/post-12536783 this is a good post for others curious about how to enable/disable flashing mode. TLDR bootloader checks if userdebug then flashing else nope.
[Android Stick & Console Computers General] :
You might be right. I should look into other hobbies. Any suggestions? I've considered skydiving but I'm afraid of heights and also afraid of flying.

When to publically release an exploit is a real consideration that can be in the ultimate best interest of the enthusiast community. It is all about the timing.

I haven't noticed this but I will check again.

Unlike android 9, android 10 employs dynamically mapped partitions.

system.img, along with vendor, product and odm are all stored within super.img.

Flashing the super image directly allows using the bootloader version of fastboot for the entire process, rather than switching to the user space fastbootd in order to flash the dynamically mapped partitions individually.
[Android Stick & Console Computers General] jahrule:
I understand your concern, but nothing we are talking about are exploits. It is merely using the usb burn tool which is not a secret.

That would be great thanks.

Thanks for clarifying! TIL
[Android Stick & Console Computers General] vettejock99:
@goapy My apologies if sharing those commands let out TMI. I was not aware of what might be derived.

@jahrule Not sure where anyone suggested this was their hobby, rather than something simpler and more straightforward, FWIW.
[Android Stick & Console Computers General] __3xcalibur:
Bypassing the initial activation can be done with: (as of 5222)

pm uninstall --user 0 com.google.android.tungsten.setupwraith

Which uninstalls the setup app. Please be aware of what this does

Edit:

Uninstalling may not be required and may mess up critical steps.

Force stopping multiple times seems to skip some parts.
[Android Stick & Console Computers General] jahrule:
Has anyone been able to use USB burn tool after android 10 upgrade to go back? I haven't had any luck. Might want to hold off on upgrade for anyone who is still on 9.
[Android Stick & Console Computers General] ghettiguru:
They locked the burn tool? Fail. I'm on debug 10, thanks to @goapy and there's now a Magisk module to hide debug builds by the...husky dude that makes the magisk bootloop module that allows for wildvine l1. See his point though? Ppl started modding and it caused them to lock the burn tool. I have a twrp port I've made I'll release as soon as I get back home...may help w future issues may not as TWRP gets erased with OTAs. I should have tried orange fox, but I had at least a source to port twrp from with a similar AMLogic device so I went with that. He isn't being stingy quickly shared all info with anyone asking in the forums, he just tried to keep it on the down low so people didn't end up having to shove aluminum foil and crap in ports to flash (i.e fire stick). While we're on that there are two test points on the board that will allow usb flashing, you can either touch it w metal pin, or do what the Russians did w the same SEI400 board but different brand name, and solder a wire to it w a push button toggle so you can put it back together just press the button when needed for flashing. I considered soldering a MicroSD port, but after reading the Russian stuff it seems their version didn't have USB c like ours, but reverse..they had sd and no USB c. After reading they figured out there was a usb-c spot and then soldered USB c but from when I gathered with Google translate anyhow, and looking at the board I see what they mean, the MicroSD and USBC slots share the same data bus so I think you can only use one at a time. They engineered some stuff with the toggle switch so you can use one or the other as needed but I would just use my USBC hub and I have a solid state drive that can handle a lot more than that SD card ever could so no need. I'll have to go and look for a picture of the test point if you need it, I would link the site but it's against forum policy especially given the source. If you Google Okko Smart box anything about modding you'll find it, but it's against forum rules not only bc it's another phone site, but also known for sneaky kgb Russian spyware, so go w antivirus or not at all lol.
[Android Stick & Console Computers General] jahrule:
TWRP port would be good for people. The burn tool isn't locked. It is just the new 10 system partition is not supported with burn tool.
[Android Stick & Console Computers General] jahrule:
For anyone on v10 release. One can use the `update.exe` amlogic tool to issue a

update bulkcmd "reboot fastboot"

this will get the device in fastbootd mode which one can flash imgs to. It is a limited fastboot mode though.
[Android Stick & Console Computers General] jahrule:
Fyi:

Erasing the bootloader gets one to the bootrom which shows up as gx-chip. One can interact with it via update/USB burn tool however it is password protected and the password.bin on this thread does not unlock it. Essentially one has a brick. If we can get past this I can do a lot more digging in.

Vbmeta can be disabled and one can boot with any signed boot IMG, but any other partitions this is because of secure boot. I have tested and was able to boot up and run aidens ROM for instance using everything from that ROM except the bootloader and boot IMG.

Hope that helps folks.
[Android Stick & Console Computers General] :
When you say "one has a brick", do you mean that the device won't boot to the OS at all?

If such is the case, probably the only way to restore the original bootloader is to install (solder) in an sd card slot and boot from that. The bootrom tries to boot from emmc first, and if it can't, it tries to boot from the sd card. Once the OS is booted from the sd card, the bootloader partition on the emmc can be restored with the original bootloader image using dd.

That is the case for android 9. The system partition can be changed if vbmeta is disabled and the bootloader is unlocked, but none of the bootable partitions (like boot and recovery) can be changed.

But this is not the case for android 10. All of the partitions can be modified, including boot and recovery, if vbmeta is disabled and the bootloader is unlocked.
[Android Stick & Console Computers General] rczrider:
Is there a consensus on avoiding the upgrade to 10?

I have a Stream 4K I haven't plugged in for some time and it's still on 9. Any reason to hold off on going to 10 and if so, how might I block/disable it?
[Android Stick & Console Computers General] ooftymcgoofty:
I block it to avoid the home screen ads. I have one that upgraded to ten, runs fine as long as I use a 2amp charger (was seeing reboots with supplied 1amp) . But the ads are there to stay.

To keep it from updating from 9 you have to disable play services as the update is pushed by Google, not tivo. Once a week or so I have to enable it briefly to shut up Netflix.

As you see on this thread, there is no going back once it updates to 10. I can't think of another reason to avoid ten other than the banner ads, though. Others on this thread may have much keener insight, though.
[Android Stick & Console Computers General] fixsony:
Someone could tell how you can install the 10 android debug version. Thanks.
[Android Stick & Console Computers General] xoxo_xdagirl91:
Hi friend, can you post instructions on how you installed the debug 10 build? I flashed the debug 9 build and tried flashing debug 10 through fastboot but there is no system.img or super.img that was linked in the 4515.zip. I tried converting the system.dat.br to system.img and I was able to but it failed when trying to flash. Currently stuck in fastboot mode as there is no system installed. Any help is greatly appreciated
[Android Stick & Console Computers General] xoxo_xdagirl91:
can you post instructions on how to flash the Stream 4k 4515.zip that was linked pls
[Android Stick & Console Computers General] manolodf:
Hey guys, so I have a couple of Tivo Stream 4k's and I overall like it because of the remote, and I de-cluttered it a bit and mapped some buttons, but one thing I really want to be able to do is have like a restricted mode, like google tv has the restricted profile, or some android tcl tvs have those profiles that are locked (These are going in vacation rentals so ease of use is important, but also the ability to have protection to not have stuff moved around)

Any suggesions on how to add this type of protection so I can lock the settings, enter a locked profile that they cannot get out of without a pin?
[Android Stick & Console Computers General] ghettiguru:
I never get on XDA because drama, most of my group left here due to the new staff. I just noticed something I don't think anyone else is pointing out I am still on that debug 10 debug firmware and I don't have to worry about losing my Google speech or anything. Here's a little tip, the debug firmware Boot and everything allows for the OEM unlock of course. But it sticks in system once it's done so you can keep the system from the debug build and the super and whatnot, once you're all set up flash the stock Android 10 boot image if you can get it from what would be the OTA update I think someone has already posted it. So that means you're going to be on complete debug except the boot and that's enough because it's not going to have the test key stuff .you will lose that unlock toggle but it doesn't matter you stay unlocked that's done in system. And it will stop you from getting updated off of root and debug and having to disable Google stuff last I care to check but I have TWRP. I've been meaning to build an orange Fox but I've got three builds for my phone we had to do our self with my group, and we're having to build our own ROMs and I've been satisfied with my current setup ATV ROM ported from OKKO box is aosp, and that TWRP isn't hard to Port from the same box because you don't have to worry about touch screen drivers or anything it's literally a text file there in the boot for your remote control configuration I'll dump mine if I get the chance. Hell I'll just upload the boot and recovery to the TWRP generator bot that will generate a whole tree on Telegram that's how we built TWRP orange Fox and Skyhawk for the phone I'm on now along with action recovery builder by one Mr Captain throwback on GitHub. It's about time to crank out an orange Fox For it anyway
[Android Stick & Console Computers General] EnkryptedSpirit:
I totally understand what you mean by drama. I don't use XDA that much either, due to not being exceptionally gifted in the programming dept. and getting frowned upon for things not *clicking* in my head when it comes to doing things. Anyway, I have the Tivo Stream 4K myself and was wondering about the rooting and custom rom process. Is there any way you could help me with it? I'm still learning and step-by-steps help me alot in learning to do things. Thanks!