yashsingh1/xdaforums huggingface dataset:
[Fire TV General] EngineerMind:
The adb background restriction command was accepted without an error.

I then viewed the "update status" in "About" (But I did NOT click "check for updates") and it said something like "Last checked: none" (I also did my clear command). Then later in the day the update status now said something like "an update was downloaded and it will be installed when the firestick is idle for a long period of time".

So that suggests to me that the OTA was still able to run even after setting that background restriction.

But if just "looking" at the update status page (without clicking "search updates") causes the run-in-background restriction to be unblocked, then I guess I am starting to understand how quantum physics work.
[Fire TV General] EngineerMind:
So does the adb "clear" command delete the app "data" or "cache"?
[Fire TV General] Finnzz:
Thank you for the clarification. Logcat says:

Download provider: _data=/cache/partial_downloads/update-raven-diff-PS7242_2906_0021710461572-to-PS7242_user_3515_0021710617476-3.bin

This is where I see the '-3' added to the bin name. Since you are saying /cache/ is a separate partition this is moot. What is the cache partition size typically?
[Fire TV General] Sus_i:
The pm clear command clears all data from the app, it cleared also downloaded files from cache for me, at least in the past. But it seems that isn't the case for all devices, see postings from @Finnzz

Maybe amaz. changed something, for all or for newer devices, idk. I'm going to check this out for my fireTVs.

You're right, seems there are a few partial updates in your folder... I guess it's just a cube thing, idk.

I think there isn't a partial download folder for sheldon, mantis and all older fireTVs. Even the 4kmax doesn't print something like this in the log.

The size of cache differs, at least a (packed) full update.bin needs to fit.
[Fire TV General] Finnzz:
2 caveats. My Cube was never rebooted between the 4 updates. And I didn't keep recording until the update fully downloaded.

Also my update was very small (~63MB). So it's possible that the update files were accumulating because there was enough space that they didn't need to be deleted to make space to download the update again?
[Fire TV General] SweenWolf:
Mantis Patch (6.2.8.7)

Updated OTA Patches + Package Protection Removed.

Accessibility Patch is also included.

[NOTE:] TO BE USED WITH PATCHED BOOT IMAGE, EITHER FLASH ATTACHED BOOT.IMG OR USE MAGISK TO PATCH (FROM TWRP).
[Fire TV General] Sus_i:
63MB is small, will fit ten times or more.

I guess that folder will be clean, if you complete the download.

But then the cube will probably update ;)
[Fire TV General] Finnzz:
The full update file is only 63MB. I did let the update download complete each time, followed by the clear command. I have rebooted my device since this, and I'm still on the old OS version.

I figured at a minimum the clear command is deleting the OTA apk's information about the update file, so that even if it is there it's not trusted / installed?

Or maybe the update files are being deleted but there is a log of the update checks somewhere else that is incrementing the file name +'-1' each time even though there is no actual old files to create a filename conflict?

IDK, someone with a rooted FireOS7 stick could see what's going on more clearly.
[Fire TV General] Sus_i:
I guess there are more than one file in the partial folder, maybe the OS keeps them until the update is installed.

Edit: There is a partial download folder on my sheldon...

I'm going to look what the clear command does.
[Fire TV General] Sus_i:
FYI: The new unlock solution for sheldon / sheldonp and mantis was released a hour ago...

You can now unlock the bootloader and root the fireTV stick 3, the Lite stick and the 4k (non-max) stick, even if the efuse in the SOC is burned, i.e. works without shorting.

Amaz. will patch this with updates, so don't update to the latest.

If you don't own such a stick, hurry up and get one until it's to late :)

Links to the threads:

sheldon/sheldonp

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)

Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...

xdaforums.com

LineageOS:

https://xdaforums.com/t/rom-unoffic...-tv-stick-lite-sheldon.4410317/#post-86512399

mantis

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)

NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...

xdaforums.com

Edit: Just forgot to say, you can flash a Lite Stick into a normal fireTV3 Stick... and vice versa :)

Difference is the OS, not the hardware :D
[Fire TV General] EngineerMind:
Can you provide a link to it because I could not easily find it.
[Fire TV General] Sus_i:
Ok, had a look on sheldon, fireOS7 stick.

There is also a cache/partial_download folder. As soon as the download is complete, the package gets moved to cache and the partial folder is empty.

The pm clear command will not delete complete files, they are still there.

sheldon/sheldonp

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)

Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...

xdaforums.com

LineageOS:

https://xdaforums.com/t/rom-unoffic...-tv-stick-lite-sheldon.4410317/#post-86512399

mantis

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)

NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...

xdaforums.com
[Fire TV General] Finnzz:
Thanks for checking. Out of curiosity, if you cutoff internet access and disable the OTA package during the update download, does the file remain in cache/partial_download? And does the clear command delete it from partial_download?
[Fire TV General] Sus_i:
Can't check it now, because the stick downloads a bunch of component updates... a.k.a. amaz. bloat apps.

They are to small to cut it in between but I'm going to try it...
[Fire TV General] EngineerMind:
....and the mouse escapes from the cat's grip once again!
[Fire TV General] bloot:
Awesome! Will try it ASAP
[Fire TV General] Finnzz:
The problem has been reported a few times, but there is no known solution. Presumably the system is waiting on some process that is related to the disabled FireLauncher, and eventually gives up. Someone experiencing the problem needs to record the bootup log, and then someone will need to sift through that log to try to figure out where the hold up is.

When the boot delay was reported last year after the UI change update, it seemed to disappear on it's own. Someone had suggested a system components update eventually fixes it, IDK.
[Fire TV General] Alza3eeem:
Hey SweenWolf create tool to TDUK to remove updates. With tduk logo.

Is that available here without that logo....!!!!!
[Fire TV General] Finnzz:
Lol, no offense to TDUK but that app is an awful idea. If anyone is going to rely purely on manually clearing updates, they are pretty much gauranteed to get the update accidentally.

All a person has to do is forget to clear, or have their device crash and reboot with the update present, and they are getting updated.

@SweenWolf doesn't your update blocker on the OP both disable the OTA packages and clear them?

So even if pressing 'disable updates' can't disable the OTA apks, it still clears all the OTA apk's. And update blocker 1.3 has no ads ;). The update blocking in LM will do the same as well.
[Fire TV General] Broken267:
Hey devs, I have 3rd gen stick, with the latest updates. The launcher manager is working. I can get custom launcher. Home button takes to Wolf Launcher. The only problem I am facing is slow boot, like when with the stock launcher, it gets to the Launcher within 1 min. But when customer launcher is set, it takes 3-5 minutes to get to the custom launcher. Until then the firetv animation keep going on. I have extracted the logcat from the boot to the custom launcher. If anyone can look on it and find some way please let me know. Also please tell if any other information is required.
[Fire TV General] linuxlad:
So changing the launcher in 6287 is still not possible without root?
[Fire TV General] Pat1981:
Hi, thanks for your awesome work!

I have a little issue with wolf launcher 0.19 (and 0.18,..) and Launcher Manager 1.12 to 1.16.

Im using a Max Stick with 7.2.5.5 updates blocked via TechDoctorUK Blocker and Adguard in my wifi.

If I statt Wolf launcher it works perfect (can scroll and start apps)

If i enable via launcher Manager Wolf launcher to be default via home button, it starts wolf launcher but than it hangs.

I’ve tried to clear cache, reset wolf, uninstalled it and tried it with version 0.18.

Always same situation. Wolf Launcher hangs and can’t be used.

It works perfect I think with old launcher manager in techdoctoruk app, I think this was November 21?

Any ideas?

Thanks

Attached you find a screenshot when I start wolf via launcher manager (no icons) and later when I start wolf manual (with default aftv manager enabled)
[Fire TV General] Pat1981:
Delete
[Fire TV General] etami:
Just installed LM 1.1.6 and can't seem to get the update blocker to take. I select Block but it still shows Unblocked. Same with Debloat Tool, I select the options that are supposed to break Amazon updates then run the tool and they just revert to unchecked.

Could it be anything to do with the fact I'm currently using the AdGuard workaround to block updates by barring the ota.update processes access to cellular and wifi data? I'd like to stop using that method if i can get LM to handle it. I'm on 3rd Gen stick running 7.2.4.2.
[Fire TV General] Finnzz:
Are you on 7.2.4.2 / 3515? If so, Amazon protected the OTA packages on that build forward so that they can no longer be disabled using ADB. If ADB is no longer an option, then you have to block via DNS or router.
[Fire TV General] Sus_i:
Another way is to unlock/root and use the pm disable commands without a hitch ;)

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)

Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...

xdaforums.com
[Fire TV General] etami:
Thanks @Finnzz and @Sus_i Yes I am on 7.2.4.2/3515 unfortunately. I'm only a newbie to Firestick (3 weeks) and started reading here and elsewhere just in time to block the updates that disable custom launchers but not before I got the 3515 update. The DNS or router option won't work for me as I'm constantly on the move and using other peoples gear. And I don't think I'm competent enough to go the Root path, even with the step-by-step guides, but maybe a bit more reading will help. Is factory reset an option? Would that take me back to original firmware so that I can start again from there? Otherwise, I've at least got the Adguard method that is working for now. Appreciate your help.
[Fire TV General] EngineerMind:
No - factory reset will not go back a version.
[Fire TV General] Finnzz:
Rooting exploits don't come along often, so they should be considered seriously when they do. There are still a number of fireTV models that have never been rooted.

There was a change in management heads of Amazon devices in late 2021, and the new management seems to have made a priority of going after any user customization and exploits.

Don't take for granted the options you have now, because Amazon new execs are taking a real Fu*k you approach
[Fire TV General] etami:
I see what you're saying, the time is now. Looks like I've got some studying to do. I've flashed custom roms on phones before but never used a linux machine. Maybe it's time to check out WSL on Windows 11 and go from there. You're a champ.
[Fire TV General] RaynMerc:
I had the exact same problem. Set Wolf Launcher as Default launcher. Then hold the home button on the brocken Wolf Launcher. Go to Settings -> Apps and delete Wolf Launcher Data. This worked for me. Hope it helps you.
[Fire TV General] Sus_i:
The best is if you grab the fireISO from the unlock-OPs github... burned with rufus to usb pendrive.

Unlocking was never easier, it's only running two scripts in a terminal and connecting the sticks USB to the PC. Then flash magisk to root, done :)
[Fire TV General] etami:
I've been following the steps in the UNLOCK/ROOT/TWRP page you linked, so thanks for that . . . I'm learning as I go along. Being a newbie, your reply raises a few questions, if you don't mind me asking, and they would no doubt be so basic . . . but with the likelihood of embarrassing myself here goes:

"flash magisk to root" - I read that I need to do this once the process reboots into TWRP. Is there any page where this process is explained, as that's where the ROOT instructions stop. And where would I find magisk?

"grab the fireISO from the unlock-OPs github" - how would I find that? And is that the rom I should be flashing? Once on pendrive, do I just plug it into a second pc usb port?
[Fire TV General] Sus_i:
You can download Magisk here:

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Download and rename the .apk into .zip

If you get a message 'boot into twrp', something like this should work:

adb push Magisk-v24.2.zip /sdcard
adb shell
twrp install /sdcard/Magisk-v24.2.zip

The fireISO is just a linux Live-ISO that already contains all prerequisites required for running the unlock exploit scripts, i.e. kamakiri. You need to burn this ISO with rufus to an usb-storage-stick. This stick gets bootable, you may look on how to boot such a live system on your PC system at power-on.

Releases · amonet-kamakiri/fireiso

ISO with patched kernel for kamakiri and amonet. Contribute to amonet-kamakiri/fireiso development by creating an account on GitHub.

github.com

If you get questions, ask in the unlock thread, since it's a bit off-topic here.
[Fire TV General] dikodahan:
Hey @SweenWolf,

Thank you for supplying the files. I do have a couple of questions on the supplied files if you don't mind:

1. Do they also work on a 4k stick with 6.2.8.1 firmware version?

2. Can you please share (for the less savvy people here) how to use them, post rooting and already in the TWRP boot menu?

Much appreciated!
[Fire TV General] etami:
Yeah, sorry mate, I led you off-topic. Many thanks for the links and explaining the process. Was heading down the WSL path but was told (on the proper thread) that won't work. No matter, as you say the fireISO bootable will do the trick.
[Fire TV General] SweenWolf:
I specifically included the version number after the patches because they are incompatible with other versions, so if you don't want a bootloop then don't flash them on other version (but its revertable using TWRP)

https://xdaforums.com/t/fire-tv-sti...y-no-ota-pre-rooted-rom.4298357/post-85345513 is the link for 6.2.8.1 (go to the link and the instructions are already there as well as link for newer patch (v2) for 6.2.8.1 as well as a flashable zip to update TZ on the device)

https://xdaforums.com/t/fire-tv-sti...y-no-ota-pre-rooted-rom.4298357/post-85824345 is the link for my patched Magisk (Only the apk is patched and it will not support any image patching functions, it will just act as a SU Manager, if you don't want to brick your stick do not flash any images on official Magisk Manager)

For these patches you don't have to root the device, if you want to have root only then flash Magisk otherwise flash the boot.img attached in the post along with the thead for that specific version.

Flashing Procedure.

As you might know you need a otg and a mouse attached for it. (Pen drive isn't needed you can just push the files to /sdcard), you can also use commandline (Sus_i has already posted a How to). Choice is entirely up to you.

1. Boot into TWRP

2. select Install on the TWRP menu and choose the "Patch - xxxx.zip" (e.g Patch - 6.2.8.1 (NO FOTA).zip)

and then swipe to flash.

after its done go back to twrp menu > wipe > advanced then choose Cache and Dalvik Cache.

For Root​

3(a).1 If you want Root then download Magisk.zip from https://github.com/topjohnwu/Magisk/releases

or use the one linked above.

3(a).2 From TWRP Menu select Install and choose the downloaded zip and swipe to flash.

after flashing is done select Wipe Davlik / Cache and then Reboot.

Your device will be rooted.

For NO Root​

3(b).1 Download the boot.img provided along with the patch.

3(b).2 Open TWRP and select Install then click on Install Image (from right side), then choose the Boot.img and flash as "Boot" and swipe to flash.

after flashing is done select Wipe Davlik / Cache and then Reboot.

You will not have root access on your devices but these patched will work nevertheless.

NOTE: These patches do not requires a root access to work, they just need TWRP. its up to you if you want root access or not.
[Fire TV General] DJDamaux:
Any idea why Widgets won't work on my Android TV? They don't show up after trying to add it, like the weather app. I'm using Wolf Launcher with the Launcher Manger (ATV) and everything is granted yes. Help! Thanks!
[Fire TV General] EngineerMind:
Are you running FireOS 7+? (widgets don't work with FireOS 6)
[Fire TV General] DJDamaux:
I said Android TV, not FireOS. Also it's Android 9.0 if that's maybe why it doesn't work
[Fire TV General] fire_cuber:
[APP][FIRETV][NOROOT] Launcher Manager (Change Launcher without Root)​

Well, guess why only FIRETV and not Android TV is in the title of this topic. :rolleyes:
[Fire TV General] roligov:
Cheers for your continued hard work mate!
[Fire TV General] Selocan20:
Hey there, sorry if double but:

Is there any Option for 4k Version 6.2.8.7 to set wolf Launcher as standard again without Root?

If not, is it possible to downgrade / delete Updates? I‘m ready to also set back to factory again
[Fire TV General] EngineerMind:
No.

No.
[Fire TV General] EngineerMind:
The best thing to do (in my opinion) is:

1) Buy a "new" firestick on ebay - this way you know for sure it does not yet have the wolf-killing update on it (because that particular firestick was originally bought by the seller before the wolf-killing update was released). If you buy a "used" firestick, then depending on the last time it was connected to the internet, the wolf-killing update might already be on it.

2) Then using the *special* setup method described in an earlier post, set it up while preventing it from successfully doing the "download latest version" step (so it will not install the wolf-killing update).

3) Then disable the three OTA files using ADB, so it will never download the wolf-killing update again.
[Fire TV General] johnsmith0123:
I am running Launcher Manager 1.1.6 (FOS 6 & 7) on My fire TV cube Fire OS 7.2.4.2.

When it boots up it takes very long time to finish loading up. Have TiviMate installed. I can hear the sound from the apps for a long time. while booting up. Is that normal?

is there a reason why booting up takes lot more time.

is there a way to stop getting any updates?

Many thanks
[Fire TV General] Sterny:
Hi guys, apologies if this has already been solved somewhere.

I have 2 fire sticks(4K) both running Wolf Launcher and I love it. The only issue is that on one of them when I press the home button it returns to the Amazon stock launcher. I’m trying to figure out they this is.

FIRE OS is 6.2.8.7

Any help much appreciated
[Fire TV General] bloot:
That's a problem that appeared on 7.2.4.2/3515 for me, it did not happen on previous builds (2907 and earlier).
[Fire TV General] EngineerMind:
The 6.2.8.7 update prevents using a custom launcher.
[Fire TV General] Sterny:
Dammit!

Is there anyway to roll back or to prevent my other stick from updating?
[Fire TV General] EngineerMind:
No

A few posts back I offer a work-around.
[Fire TV General] Sterny:
Well, that sucks. The stock launcher is awful!
[Fire TV General] Finnzz:
@bloot @johnsmith0123 @QuiDC96

Regarding the slow boot up, @Broken267 recorded the bootup log with Wolf launcher (slow boot) and the default Amazon launcher.

Amazon added a 'real home signal' check to the January update. So now the boot animation will keep looping until the either there is a message from 'real home' (I assume this is the default homescreen launcher, which is disabled) or the timer times out after a couple minutes.

It appears that the system continues to load behind the boot animation, and you just can't see it.

One thought is that you might be able to use Launcher Manager's ADB function to create a command that runs on boot to open the Wolf Launcher, bringing it to the foreground, sending the looping logo to the background.

Go to Launcher Manager 1.1.6 / Other Settings / ADB Commands / add new command (corner plus sign)

Label it what you want (eg Wolf on Boot)

Enter the command:

am start com.wolf.firelauncher

Check execute on Boot, and save

Reboot to see if Wolf Launcher appears sooner.

It's possible that this ADB command will get called too early and may need a delay added. To add a 10sec delay use this ADB command:

sleep 10 && am start com.wolf.firelauncher
[Fire TV General] bloot:
Many thanks for the detailed explanation, however as I own a sheldon and there's a exploit to unlock it now, I was able to roll back to stock 7.2.4.2/2907 via TWRP, and there's no more long boot with custom launcher enabled :)

Of course I can now disable Amazon updates too using the LM built-in update blocker (it was impossible on 3515).
[Fire TV General] EngineerMind:
I tried this even with a 12 second delay, but it didn't work :(

I even have one of the 4k max buttons mapped to another app and pressing that button during the long animated firetv logo did not bring that app to the foreground either (but when the animation finally stopped and disappeared, the button app I selected was in the foreground and not wolf)
[Fire TV General] Finnzz:
Thank you for trying it, that makes sense. If you could bring apps to the foreground then any of the app buttons would bring the apps up.

Maybe there is a way to force close the boot animation then. Will have to search and see if that's possible.

EDIT: WindowManagerService is what eventually times out and stops the boot animation

"service.bootanim.exit", "1".

Unsure if or how that could be called early. There's also differences between Android and FireOS. This is what appears when the default Amazon Launcher is present

SettingsProvider: Notifying for 0: content://settings/secure/bootanim.real_home_ready
[Fire TV General] Datastream33:
Ah, they hit the Fire TVs with the old protected package as well, huh? :(
[Fire TV General] Tech0308:
If you have root you can forgo the boot animation with debug.sf.nobootanimation=1 prop which works well for me since it's just a black screen for a few seconds
[Fire TV General] Finnzz:
True, if you root there are serveral options. And I'd personally take that route.

The reason why Launcher Manager has been the most popular FireTV mod of the last year is because it's a nonroot customization that is easy and fast to implement by the most novice user, and has little to no chance of bricking the device.

I'm glad to see new rooting methods, but there are still a number of devices without this option, and many users that don't want to take that road for any number of reasons.
[Fire TV General] Tejas tedi:
No problems in downgrading?, from which version you downgraded?

And can you link the firmware file of 7.2.4.2 of fs lite?