yashsingh1/xdaforums huggingface dataset:
[Fire TV General] RiCkLaR:
Running the latest firmware build (FS7273/2625) on Cube 2nd Gen. and notice a few more "junk" system apps have been added.

Here is my current DISABLED app list:

raven:/ $ pm list packages -d
package:com.android.internal.display.cutout.emulation.corner
package:com.android.internal.display.cutout.emulation.double
package:com.amazon.recess
package:com.amazon.whisperplay.contracts
package:com.amazon.dcp.contracts.library
package:com.amazon.metricstest
package:com.amazon.bueller.photos
package:com.ivona.orchestrator
package:com.amazon.device.logmanager
package:com.amazon.shoptv.firetv.client
package:com.amazon.ftv.screensaver
package:com.amazon.tv.ooberesource
package:com.android.internal.display.cutout.emulation.tall
package:com.amazon.client.metrics.api
package:com.amazon.aca
package:com.amazon.dcp
package:com.android.nfc
package:com.amazon.logan
package:com.amazon.tahoe
package:com.imdb.livingroom.firetv
package:com.amazon.wirelessmetrics.service
package:com.amazon.tv.fw.metrics
package:com.android.dreams.basic
package:com.amazon.firehomestarter
package:com.amazon.ftv.profilepicker
package:com.amazon.device.sale.service
package:com.amazon.dummy.contacts
package:com.svox.pico
package:com.amazon.tv.forcedotaupdater.v2
package:com.amazon.client.metrics
package:com.amazon.dummy.calendar
package:com.amazon.dummy.gallery
package:com.amazon.ags.app
package:com.amazon.dummy.alarmclock
package:com.amazon.kso.blackbird
package:com.amazon.whisperjoin.middleware.np
package:com.amazon.whisperplay.service.install
package:com.ivona.tts.oem
package:com.amazon.shoptv.client
package:com.amazon.alexashopping
package:com.amazon.franktvinput
package:com.amazon.cloud9
package:com.amazon.dummy.music

Please, will any of the FireOS wizards here review the list and let me know if anything should actually be ENABLED. Note: I am a Prime member so not fully debloated all the Amazon apps.
[Fire TV General] EngineerMind:
I did not know that - wow, that sucks.
[Fire TV General] Friendlyx33:
All they do now for me is prevent the buttons from accidentally going to their app, which is better than nothing. Basically nothing happens when one of the remapped buttons are pressed.

version 7.2.7.3
[Fire TV General] Finnzz:
AFTVnews updated the instructions for remapping the app buttons about a month ago. Did the updated instructions already stop working?
[Fire TV General] Friendlyx33:
I deleted all 3 after the newest destructive fire tv update and reinstalled them one by one using the newer instructions... Doesn't work anymore. Opening the individual apks that you "create" with that process DOES open what app you set them to open but for some reason the buttons just aren't connecting to the apks, if that makes sense. Clearly someone at amazon didn't appreciate all these "hacks".

Version 7.2.7.3
[Fire TV General] HillsmanUp:
Should've googled a little more before spend what amount to 300 bucks on a Firestick here in Brazil... It would've been better getting a generic android stick instead....
[Fire TV General] simonho1989:
So, the rumored new method using tatal commander to uninstall updated version of launcher to stock version

After that , the home replacable? or it still rely on Launcher Manager to disable it?
[Fire TV General] HillsmanUp:
For me, neither of them worked.
[Fire TV General] gotovanko1:
For me method work on Firestick 4k mantis...ON cube doesn't so far. I hope this hack with removing ftv launcher will help wolf to create newer and better launcher for FOS7 also
[Fire TV General] Finnzz:
There have been ~3 updates since Amazon disabled custom launchers. It would be helpful if people mentioned the device / firmware and build that either worked or didn't.

Otherwise it's just confusing having a mix of 'it works', 'doesn't work'.

My initial guess is that this may only work on FireOS6. My second guess is that Amazon is already aware of this loophole and a patch is rolling out that some have already gotten.
[Fire TV General] gotovanko1:
You are right my device is Amazon fire cube fos 7237/2625
[Fire TV General] RiCkLaR:
The hack/loophole works with all current firmware and devices, it works because of the default logic of Android to allow System Apps to have data reset.

But you are correct, a new firmware is in the works, probably in testing phase as new version and build numbers already posted here:

Fire TV Device and Accessory Software Updates

Partial Copy/Paste from link:

Amazon Fire TV Devices

Amazon Fire TV Cube (2nd Generation): FireOS 7.2.7.9 (23253929604 (PS7279/2766))

Amazon Fire TV Cube (1st Generation): FireOS 6.2.8.9 (7013876100 (6289/3905))

Fire TV Recast: FireOS 6.2.8.9 (7013876100 (6289/3905))

Amazon Fire TV Stick 4K: FireOS 6.2.8.9 (7013876100 (6289/3905))

Fire TV Stick 4K Max: FireOS 7.2.7.9 (23253929604 (PS7279/2766))

Fire TV Stick (3rd Generation): FireOS 7.2.7.9 (23253929604 (PS7279/2766))

Fire TV Stick Lite: FireOS 7.2.7.9 (23253929604 (PS7279/2766))

Amazon Fire TV (3rd Generation): FireOS 6.2.8.9 (7013876100 (6289/3905))

Amazon Fire TV (2nd Generation): FireOS 5.2.8.8 (676742620 (5288/7426))

Amazon Fire TV (1st Generation): FireOS 5.2.7.4 (656639420)

Fire TV Stick with Alexa Voice Remote: FireOS 5.2.8.8 (676742620 (5288/7426))

Fire TV Stick with Voice Remote: FireOS 5.2.8.8 (676742620 (5288/7426))

Fire TV Stick (1st Generation): FireOS 5.2.8.8 (676742620 (5288/7426))

Fire TV Stick Basic Edition: FireOS 5.2.8.0 (668694820)

In-Car Entertainment with Fire TV built-in: FireOS 7.2.7.7 (23119693188)
[Fire TV General] Brian2022:
Hey I followed all your steps and even double checked my spelling but as I soon as I disable update blocker in debloat tool and go to update screen it starts trying to update from Amazon. I have attached a photo of blokada, is there something I'm missing ? I assumed its just inbl ad blocking blocked hosts ? Is there any other settings to adjust ?
[Fire TV General] RiCkLaR:
What firmware version & build number are you on?
[Fire TV General] Brian2022:
sorry for delayed response 6.2.8.1 (NS6281/4061)

the reason i was actually trying to test this was to use it on firesticks running on my parents house they got updated by accident, currently i am doing the adguard to block updates but i dont feel that is complete safe if the unit gets restarted and not turned back on.. their firesticks are on the 6.2.8.7 (not sure of build) and wont allow the custom launcher to work..... previously i had blokada running for just ad blocking purposes for tv/movie apps so it would be nice to get this to work on their units to stop and future updates.... then i will try some of the previous solutions with no root to get customer launcher working again
[Fire TV General] RiCkLaR:
Haven't used Blokada 4 in a long while, but your picture above looks like you are making a HOST file and not a Domain Block rule. I don't block full firmware OTA updates on my FireTV devices, but I do use RethinkDNS app to firewall the OTA update apps in the FireHD tablets.

All the sticks are the 4K sticks, correct?

On the sticks with 6.2.8.7 uninstall & clear data for the KFTV-Launcher with ADB

adb shell
pm clear com.amazon.tv.launcher
pm uninstall com.amazon.tv.launcher

Then immediately Press HOME-button on the Remote and Dialog Pop-up should let you select your Custom Launcher of choice.

If you have the UpdateBlocker app or the recent LauncherManager app activate the Disable System Updates option.

If you just are using Debloat Toolbox disable the OTA packages. Sadly the recent firmware like 6.2.8.7 then only 1-of-3 of the OTA packages can be disabled, this ( com.amazon.tv.forcedotaupdater.v2 ) package. This is what updates the individual system apps.

Either way, good idea to delete the DATA for all the OTA packages

adb shell
pm clear com.amazon.device.software.ota
pm clear com.amazon.device.software.ota.override
pm clear com.amazon.tv.forcedotaupdater.v2

Now if you want to expirement for your old build (NS6281/4061) stick, if you want to enable com.amazon.tv.forcedotaupdater.v2 you can then Check For Updates in FireTV settings and install all the recent individual system app updates. Then use Debloat Toolbox or ADB to disable all the unneeded system apps again like the FTV-Launcher. My 4K-Max stick had one of the buggered firmwares that wouldn't update, so enabled that single OTA package, updated system apps, then disable launcher and the ota package again, the enabled the other two OTA apps to update to most recent firmware and still have the launcher disabled.

Note make sure com.amazon.tv.forcedotaupdater.v2 is disabled before uninstall and clear of KFTV-Launcher (com.amazon.tv.launcher).

Good luck.
[Fire TV General] Brian2022:
Interesting so if I am understanding you correctly you max 4k still stick is up-to-date for firmware and apps but you are still able to use customer launcher and you are able to block or install updates as you want ?

Yes correct I have some regualar 4k sticks and some 4k max sticks....most system apps I don't care about I just like customer launcher layout and the ability to use prime video
[Fire TV General] RiCkLaR:
Yes, latest firmware build (7.2.7.3/2625) on 4K-Max, launcher disabled, and launcher and all other system apps updated to latest versions. But be warned for future full firmware version updates I am no longer able to block the OTA packages internally with UpdateBlocker apps without some sort of DNS filter. Currently the package:com.amazon.tv.forcedotaupdater.v2 can still be blocked so any future individual KFTV-Launcher update doesn't get pushed to the device automatically. Just make sure to "clear" the Data for all the OTA apps first before starting the downloads if you plan to try to upgrade apps then firmware.
[Fire TV General] N3o21:
Hi,

I bought another one Fire Cube 2nd gen to my household (third...), since it is nice android box for kodi and netflix for 60 EUR. Unfortunately this last one updated during initial process to FireOS 7.2.7.3 (PS7273/2625) :( (now I have blocked updates on my network by faking DNS responses, but too late now).

Now I am stuck with stock launcher and unable to use Launcher Manager to have pretty interface (instead that messy KFTV).

So far I found this:

When I do pm uninstall com.amazon.tv.launcher, launcher is immediately set to com.amazon.firehomestarter.FireHomeStarterApplication. Which then set's it to com.amazon.tv.launcher as soon as I press home button on remote.

I am not able to set LauncherManager as "launcher".

Somewhere I found you can set Android launcher manually.

So I did checked what launcher is on other FireTV Cubes I have home with cmd shortcut get-default-launcher.

I did set cmd package set-home-activity "com.wolf.lm/com.wolf.lm.launcher.LMUHandler". Which aparrently kinda worked, because output (even after multiple reboots) is now:

cmd shortcut get-default-launcher
Launcher: ComponentInfo{com.wolf.lm/com.wolf.lm.launcher.LMUHandler}

But unfortunately, launcher still remains the stock KFTV.

Anyone have some ideas what to try next? Would be nice to have LauncherManager working on all TV Cubes.
[Fire TV General] Brian2022:
Thought I would just update from my experience that I had yesterday. I am using the adguard method for blocking updates currently 3 X 4k sticks on 6.2.8.7 with (3768) and on all 3 of the sticks when i reboot them adguard restarted immediately and would not allow any updates to come through, just shows error i tried once before rebooting and then again right after rebooting and same error so that is just my experience maybe others is different.

(My preference would be with blokada 4 but I have had no success yet using it to block those 5 hosts once I can figure this out I will switch back to just blokada 4))

Also I was able to get the customer launcher working again by using the Total Commander method, other apps installed LM version 1.1.6 and unified debloat tool box, only thing i noticed was it had wiped out my background picture in the customer launcher and just has black background screen but thats not a big deal

Hopefully that helps
[Fire TV General] badabing2003:
I keep on seeing references to Disabling System updates in Launcher Manager.

Where exactly is this option? I'm using the latest 1.1.7

Thanks
[Fire TV General] aliinbox:
LM settings-> Other settings -> Amazon OS Updates
[Fire TV General] badabing2003:
Thank you, would have never guessed, seeing keyboard, screensaver ... and thinking it's FireTV settings.

Thanks
[Fire TV General] badabing2003:
It worked on FireTV Max, but didn't on two FireTV 4K devices

It would spin and come back with Unblocked

View attachment 5591407

What would cause this?

They are both on 6.8.1 and LM 1.1.7
[Fire TV General] RiCkLaR:
Make an ADB connection and check if the OTA packages are disabled, and double check the firmware build number, maybe your 4k sticks got one of the latest firmwares.

OTA packages that should be disabled:

com.amazon.device.software.ota
com.amazon.device.software.ota.override
com.amazon.tv.forcedotaupdater.v2

CMD to show disabled packages:

adb shell
pm list packages -d
[Fire TV General] RiCkLaR:
Hmm, in my devices package:com.amazon.firehomestarter was disabled long before the recent painful updates and stayed disabled after the firmware (PS7273/2625) update got pushed. This may well be why my devices are working normally with Wolf Launcher set as default after the simple Clear Data & Uninstall of FTV-Launcher.

Maybe try:

adb shell
pm clear com.amazon.tv.forcedotaupdater.v2
pm disable-user com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.firehomestarter
pm uninstall com.amazon.firehomestarter
pm clear com.amazon.tv.launcher
pm uninstall com.amazon.tv.launcher

Then IMMEDIATELY press HOME-button on remote and see if Launcher Selection Dialog box appears.

Alternatively, you can have LauncherManager open & running in the foreground, which should show the switch from the Current Launcher activity of FTV-Launcher back to Android default if the Uninstall of Firehomestarter works.
[Fire TV General] badabing2003:
Here's what I get on two FireTV 4K sticks

mantis:/ $ pm list packages -d
package:com.amazon.firehomestarter
package:com.amazon.tv.forcedotaupdater.v2
package:com.amazon.tv.launcher

On 4K Max, I get

kara:/ $ pm list packages -d
package:com.android.nfc
package:com.amazon.firehomestarter
package:com.amazon.tv.forcedotaupdater.v2
package:com.amazon.device.software.ota
package:com.amazon.tv.launcher
package:com.amazon.device.software.ota.override

I tried disabling and got this error

mantis:/ $ pm disable-user com.amazon.device.software.ota
Error: java.lang.SecurityException: Cannot disable a protected package: com.amazon.device.software.ota
1|mantis:/ $ pm disable-user com.amazon.device.software.ota.override
Error: java.lang.SecurityException: Cannot disable a protected package: com.amazon.device.software.ota.override

But I am on 6281

See more details

[ro.boot.lk_buildtime]: [20211004163543]
[ro.boot.pl_buildtime]: [20191106]
[ro.boot.prod]: [1]
[ro.boot.rpmb_state]: [1]
[ro.boot.secure_cpu]: [1]
[ro.boot.selinux]: [disable]
[ro.boot.unlocked_kernel]: [false]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.veritymode]: [eio]
[ro.bootimage.build.date]: [Sat Dec 11 04:04:54 UTC 2021]
[ro.bootimage.build.date.utc]: [1639195494]
[ro.bootimage.build.fingerprint]: [Amazon/mantis/mantis:6.0/NS6281/4812N:user/amz-p,release-keys]
[ro.build.date]: [Sat Dec 11 04:04:54 UTC 2021]
[ro.build.date.utc]: [1639195494]
[ro.build.description]: [mantis-user 6.0 NS6281 4812 amz-p,release-keys]
[ro.build.display.id]: [NS6281]
[ro.build.fingerprint]: [Amazon/mantis/mantis:6.0/NS6281/4812N:user/amz-p,release-keys]
[ro.build.flavor]: [mantis-user]
[ro.build.id]: [NS6281]
[ro.build.lab126.build]: [4812]
[ro.build.lab126.buildtype]: [Nightly]
[ro.build.lab126.project]: [mantis_fireos_ship_6281]
[ro.build.mktg.fireos]: [Fire OS 6.2.8.1]
[ro.build.product]: [mantis]
[ro.build.tags]: [amz-p,release-keys]
[ro.build.thumbprint]: [6.0/NS6281/4812N:user/amz-p,release-keys]
[ro.build.type]: [user]
[ro.build.user]: [build]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: [NHG47K]
[ro.build.version.codename]: [REL]
[ro.build.version.fireos]: [6.0]
[ro.build.version.incremental]: [0005940366468]
[ro.build.version.name]: [Fire OS 6.2.8.1 (NS6281/4812)]
[ro.build.version.number]: [0005940366468]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [7.1.2]
[ro.build.version.sdk]: [25]
[ro.build.version.security_patch]: [2019-09-01]
[ro.build.version.serial]: [4812]

What gives?
[Fire TV General] RiCkLaR:
The build date, build id, and build version.serial are the key info there.

Your Fire0S6 4K sticks got that first firmware which prevented blocking full OTA updates, that was made in Decemeber 2021; that is why those 2 OTA packages are now "protected packages."
[Fire TV General] badabing2003:
Thanks

ok, that makes sense, but shouldn't the build id be different than 6281 ?

Maybe I'm mixing up the build IDs
[Fire TV General] RiCkLaR:
6.2.8.1 is the Build ID, but the "version" of the build is that 2nd 4 digit number in the fingerprint, I only tracked 3 different versions for the 6.2.8.1 firmware, there could have been a lot more before Amazon pushed the 6.2.8.7 variants.
[Fire TV General] badabing2003:
It shows how organized and structured they are (Not), build id does not change but the version changes?

At worst it should be the other way around, even then it would be a bad practice.

Would this still be rootable? Maybe it's time for me to root them.
[Fire TV General] AmwJuJo:
Hi,

I installed this on a FireTv Lite(7.3.7.3), but I don't see the option to choose Wolf Launcher from the settings. Am I doing something wrong? Do i need to install the launcher separate or is it blocked by Amazon with the new update?

Thank you.
[Fire TV General] RiCkLaR:
You are on a newer firmware build that blocks ability to permanently change the launcher. Anyways, Wolf Launcher is its own APK, seperate from LauncherManager, the file is posted somewhere in this thread, will have to search page by page till you find the shared link.
[Fire TV General] AmwJuJo:
Thank you for your quick reply.

I shouldn't updated it when it asked for it the other day.

My understanding is that no launcher will work or is ant other 3rd party that will still work?
[Fire TV General] N3o21:
Unfortunately it does not work because com.amazon.firehomestarter cannot be uninstalled (or disabled or user-disabled).

I had one more idea... But does not work either.

I extracted APK packages for firehomestarter and tv.launcher from FireTV Cube which I have on older firmware (where LauncherManager works OK) and tried to install them into this updated Cube. But installation failed with "INSTALL_FAILED_VERSION_DOWNGRADE" - so this is another way which does not lead to success.
[Fire TV General] geogaddi47:
For those that have updated to the latest version and can't get the Total Commander uninstall method to work I have found a workaround with Tasker.

Basically, it involves setting up a profile that detects when the Fire Launcher is active and then immediately launches Wolf Launcher. There is a few seconds delay for Tasker to detect the Fire launcher but Wolf is launched about 5 seconds after the home button is pressed.

I've also set up a profile that launches Wolf Launcher on device boot.

These methods aren't as efficient as the previous Launcher Manager one but will continue to work regardless of any further updates as it just requires Tasker.

In order to get Tasker to detect the Fire Launcher app as active I had to grant Tasker App Usage Stats permission using ADB with 'adb shell pm grant net.dinglisch.android.taskerm android.permission.PACKAGE_USAGE_STATS'.
[Fire TV General] gotovanko1:
Can you make tutorial how to step by step with your settings and pictures if its possible. Still no luck with update fire tv cube :(
[Fire TV General] eXtremeDevil:
Somehow LM broke my stock launcher,

com.amazon.tv.launcher

and

com.amazon.firehomestarter

are disabled and can't get them to be enabled again.

Any solutions? Maybe Fire OS updated while those packages were disabled and now they can't be reenabled? Any "easy" solution without factory resetting my device?

Thanks.
[Fire TV General] SweenWolf:
https://xdaforums.com/t/app-firetv-...e-launcher-without-root.4176349/post-86665997
[Fire TV General] aruisi21:
Can't it be used on Fire OS 7.2.7.3(PS7273/2625)？
[Fire TV General] eXtremeDevil:
My god, you saved my life, thanks!! Can I do the same with

com.amazon.firehomestarter

? Should that package remain disabled?

Right now I'm on LM 1.1.6, do you recomend me testing with 1.1.7?

Also, now that I notice it, nfc package seems disabled as well, any idea why?
[Fire TV General] RiCkLaR:
AMAZON broke the ability of to Toogle the FTV-Launcher Off/On in their quest to stop users from disabling the FTV-Launcher homescreen, it was not the fault of LM.

If you never want to use a third-party launcher again, then go right ahead and enable the package:com.amazon.firehomestarter.

Do you know what NFC is? It is not needed on a streaming device. But if you are bothered that it is disabled, go right ahead and enable it.
[Fire TV General] RiCkLaR:
Not all of LauncherManager's features can be used on the latest firmware. The main feature being changing the default-launcher is now blocked on the latest firmware releases.
[Fire TV General] eXtremeDevil:
While it is not directly fault of LM, if LM in the first place disabled the package and now an update broke the ability to toggle (enable/disable) the package, somehow LM was involved in this situation.

How should I? You said it, now packages can't be toggled. Or are you saying that packages can be normally disabled/enabled, and toggling is another matter? Wolf's instructions worked well, although I don't know if they involved uninstalling updates of the official launcher.

I do know what it is, it even shouldn't be there if you ask me. I don't want to enable it, I was just asking out of curiosity. If it is disabled by default, why putting it in the first place? Or was it disabled by some app/process/setting?

Thanks for the answers anyway, let's wait for Wolf's answer and see what he has to say :)
[Fire TV General] SweenWolf:
My given commands uninstalls the updates first, then reinstalls the stock launcher.

Advanced users can do this without having to uninstall the updates, but they don't have to read my posts to do that, they already know what to do.

These command may or may not throw some error depending on package state (stock, stock updated or not installed)

So just type the commands no matter the result and you'll have your stock launcher back again.

You can do the same for firehomestarter.

Actually if you enable firehomestarter then it will enable and launch Amazon Launcher (its the only purpose of this app)

I don't know what package uses NFC so I will not comment on that, but on stick there is no need of NFC but I think Cube has NFC (again I don't have a cube so i may be wrong)
[Fire TV General] eXtremeDevil:
It's weird that the NFC package is there and disabled. It doesn't bother me at all, I just found it weird and went to ask here in case anyone has more info. Your commands worked well, I can now access search and settings screens again, and all that without losing custom launcher functionality. I guess for now I will keep firehomestarter disabled. One question though, I didn't quite get this part, so is my stock launcher package now with or without its updates? In case it is without, can it be updated again?

BTW, how can I enable or reinstall the package without uninstalling it first? I'm familiar with adb and shell, but I have little experience in managing packages through adb, even less on non rooted environments...

Right now I'm on LM 1.1.6, would you recommend me testing with 1.1.7?

Thanks!