yashsingh1/xdaforums huggingface dataset:
[Fire TV General] Finnzz:
So the plan is to sink FireOS, then jump to another platform, and leave other FireOS users with a worse OS lol

There's so much more to ADB than using custom launchers. People use it to enable/disable apps, modifying permissions, setting screen savers and timers, setting keyboards, etc etc etc

Losing custom launchers was bad, losing ADB all together would be way worse.
[Fire TV General] xnappo:
I get it - but people are already using this method with a Pi or another computer. Honestly as I said I have updates blocked, so my question is more academic. The number of people who would understand how to do this is probably even smaller than the number of people who would do the second computer option.
[Fire TV General] yigitter:
so dont block ota updates and dont do anything dare Amazon to completely disable ADB for everyone.

For me Launcher is far more important then ADB itself.

i just need adb to run launchers properly. Everything else doesnt bother me in daily use.
[Fire TV General] MeowMeow5000:
any Shizuku tips n tricks to help forget Amazon launcher? :)
[Fire TV General] zanedlvz:
i tried everything, i keep getting “connection failed” “try re enabling ADB debugging” my usb debugging is on and if restarted my tv multiple times, even factory reset it and it still doesn’t work

any help?
[Fire TV General] safetyp1:
I have 2 fire stick 4k max 1st gen on OS 7.6.6.9 and both are getting “shell is busy” error in launcher manager 1.1.9 :/ that’s happening when I try to enable the overlay. This device still has lm 1.1.9 enabled.

But on one fire tv I disabled it and cannot re enable at all due to this error. I’ve had to put lm mini on that one.

Its also taking a long time to actually get to my custom launcher, used to be almost instant and now it’s 5sec even with lm 1.1.9.

Seems like my update blocking via DNS didn’t work or they snuck in somehow.
[Fire TV General] Finnzz:
Launcher Manager no longer works after the last update. Amazon disabled apps from using ADB, needed for LM:

Update blocks apps from using ADB -- NS6702/5093 -- PS7669/4007 -- RS8103/2083

The new PS7669/4007 update that began rolling out the last few days, blocks apps from being able to use ADB. This breaks many 3rd party apps, like Mouse Toggle and Launcher Manager. I'm assuming that Amazon is doing this to put a final death...

xdaforums.com

Wolf released a newer version called 'LM mini' which has a couple second delay between home press and custom launcher opening. It's a better than nothing solution.

[ROOT][MANTIS][FIRESTICK 4K] Custom Launcher Support and System Patches

CUSTOM LAUNCHER HANDLER (FIRESTICK 4K) - 6.7.0.2 This is a method to enable certain features disabled/blocked by Amazon, and this method does require TWRP to be installed on the device. This does not require any root access so you don't need to...

xdaforums.com

The work-arounds produce increasingly worse results as Amazon locks FireOS down more and more. LM mini was posted about by TUK on YouTube and AFTVNews, which will probably get it blacklisted first, before Amazon locks down setting app permissions next.

PS7671/4095 is already in early rollout, so we will see in following update how Amazon decides to crack down on this.
[Fire TV General] safetyp1:
Yeah I’m using lm mini on one now. That delay is painful. I think this might be the end of my firecsticks, time to look at Google CCwTV.
[Fire TV General] jimrin:
What did you have to do to get it to work for your 4K Max (2nd Gen) running FOS 8.1.0.3? I was able to use LM Mini to get a custom launcher working on my Fire TV Cubes and older Fire TV sticks, but for my 4K Max (2nd Gen), it brings up the custom launcher upon boot, but the Home button still takes me to the default Fire TV home screen.
[Fire TV General] safetyp1:
Ive solved it using the info in this thread: https://xdaforums.com/t/workaround-to-remap-home-key.4527599/page-2#post-89464514

I presume itll work for all devices. But you need some linux server on your netowkr to make it work.
[Fire TV General] soldiersinx:
I don't know if you solved this problem or not. But if you put the default Amazon launcher, you can get full access again to all your settings. Once you change what you need, you can set your launcher back to a custom one.

I was trying to figure out how to change display from always HDR to adaptive and the settings wasn't there. Someone on Reddit told me about the Amazon launcher and I was able to access everything again.
[Fire TV General] jimrin:
Thanks for the info. It's awesome to be able to make the custom launcher start up by an external adb command, but as you said, need a Linux server running on my network which I do not currently have...
[Fire TV General] xnappo:
Just get a Pi-zero. $10.
[Fire TV General] pitsensas:
Hello @Finnzz ,

On my side, I was using this method since May 2023 : https://xdaforums.com/t/4k-max-with-tasker-to-launch-wolf-on-home-button.4541521/#post-87997103

But from February 2024, due to the OS update and ADB blocking, I have changed the config of Tasker by calling directly the Wolf application (instead of ADB command). The delay to see the Wolf launcher screen is 2-3s, so for me, this is acceptable !
[Fire TV General] Finnzz:
Tasker will give you the same results and delay as LM mini. LM mini is more compact (uses less resources) and it covers up the Amazon homescreen during that 2-3sec delay. It's also free and easier to setup than Tasker. But Tasker is less likely to get blacklisted.
[Fire TV General] jimrin:
I think I have basically the same situation as you. I had some 4K Max (Gen 2) Fire TV sticks which I bought around Christmas time, but didn't know the process to block updates when setting up the Fire TV stick, so they all got upgraded to 8.1.0.3. :( But then when I found out how to (try to) block updates upon Fire TV stick, I just ordered a new one since they are "on sale". I was able to block the update to 8.1.0.3 so it is still on 8.1.0.1. However, I cannot run the old method as it tells me it is protected. So possibly, they now come protected or the update to protect was able to get through (since I was actually not technically not blocking updates, but stopping my Internet connection in time before it can complete the download of 8.1.0.3). I was able to use local ADB to clear out the partially downloaded update. Sigh, next time I should just block the update sites.

Anyway, even with 8.1.0.1, the new method doesn't seem to work either...

And LM Mini also doesn't seem to work either... The behavior of my 8.1.0.1 Fire TV stick is the same as my 8.1.0.3 Fire TV stick which is upon boot up, eventually it will get to the custom launcher, but pressing the Home key doesn't seem to do anything. It is allowing me to do remote ADB updates on both, but still, doesn't seem to have any impact.
[Fire TV General] pitsensas:
Hello. I can suggest you to try with LM (FOS) 1.1.6 : https://xdaforums.com/attachments/lm-fos-1-1-6-apk.5550709/

The higher versions are here to add the "Home hook" when LM was not installed before the initial update during installation.

But, if you are still in the original OS version, your target is to disable firehomestarter and remove KFTVLauncher and the old version of LM are able to do it for FireOs 6 & 7 (but I don't know for FireOs 8) !

To check if firehomestarter is disabled :

adb shell pm list packages -d

And check if the package com.amazon.firehomestarter is present

Good luck !
[Fire TV General] pitsensas:
Hello,

Normally yes, a long press on Home Button will open the menu : https://i0.wp.com/www.alphr.com/wp-content/uploads/2022/02/2-1.png

And you have the FireTV settings on the right !
[Fire TV General] crazyazz:
What is the best launcher to use with LM mini?
[Fire TV General] SweenWolf:
So LM Mini not working on 4K Max (Gen 2) devices?

Can anyone send me a logcat of pressing home button (do not use LM mini) at that time.

I may not be able release a fix for it before 28th anyway but I will be anle to know whats causing the issue
[Fire TV General] sibok:
Which command do you need me to run? adb logcat what else?

BTW, LM mini takes 10 seconds to launch ATV launcher after booting.
[Fire TV General] SweenWolf:
Just adb logcat.

I need logs for at least 5 seconds.

Any app can take up to 20 seconds to launch on Boot, thats how fireOS works
[Fire TV General] sibok:
There are a lot of messages. Don't know why but it's constantly printing.

Key press is at the end.

dpaste/RPy40 (Bash)

Another one, just in case.

dpaste/xv34y (Bash)
[Fire TV General] SweenWolf:
Try with trigger "ActivityTaskManager" and send me logcat, try other triggers and do tell me the results.

Setting up this apk does not require a reboot, after giving permission click on "Recheck" the app will reboot itself.
[Fire TV General] sibok:
Yes, I noticed. That's why I asked for a concrete command just to capture key pressing.

When running logcat it constantly printed messages.

BTW, I've just installed the provided APK but no trigger took me to ATV. The home button always took me to Stock Launcher.

I'll try to get the logcat.
[Fire TV General] ChrisNelson93:
Hi I also wanted to note that I have been unable to get LM mini to work with my fire srick 4k Max Gen 2.
[Fire TV General] :
https://paste.quest/?3b58ef19d9615da7#8wEwoxxZmUJjkB9aM14nmfdwjaLaPkeqXaC6j8wZG6Ar

None of them worked on a 4K (non Max) Gen 2.
[Fire TV General] Dimitrij4k:
Hey, thx for your great work :-) I tested all triggers with an AFTV MAX 2nd Gen and none of them work.

I press all my thumbs for a solution...
[Fire TV General] Dimitrij4k:
Is it possible to flash a ADB Server on a ESP32 (cheap/low power) and link LM to this ESP.

The ESP could WiFi ADB to the FireTV and send commands back to the FireTV....

Some People have a Home Assistant, they could ue it.. at the end of the day we just need a seperate ADB Server and ADB Wifi Bridge to the Firetv... could LM communicate like this? Grab Events should work from an external ADB ?!

Im not a Pro... but i think the idea could work.... and should be instant...
[Fire TV General] shaunoleary:
I made the huge mistake of resetting my modem without first disconnecting power to my two Fire TV's. I'd forgotten that one (My Fire TV Lite) is connected via LAN (not WiFi), so as soon as the modem reset and the network came up, the sneaky thing updated its firmware before I could re-enable URL blocking on my modem.

By the time I realised, it was too late. Both my sticks had updated to 7.6.7.1, so party's over as far as LM 1.1.9 is concerned.

So I went for broke and blocked the update URLs as quickly as I could, and went to survey the damage. Both devices had updated themselves to 7.6.7.1, and LM was not working ("ADB Shell is busy" error). So I reset the FTV lite, and factory reset the FTV Lite. Firmware update failed, so I held BACK and MENU until the VoiceView menu came up. Pressed BACK, and continued with the default setup.

I activated Debugging, installed Downloader, and used it to install LM Mini. Ran these commands via adb:

I had a launcher installed (in my case I'm using LeanBackOnFire), and used LM Mini to activate it as the defautl launcher. No reason you couldn't use Wolf or some other launcher if you chose.

I also installed Launch on Boot from Downloader, and used it to set LeanBackOnFire to start on device boot.

The result of all this ...

On boot-up, the FTV will show the default FTV launcher for about 30-45 seconds (give or take), then shows FireTV logo with a spinning arror, and switches to LeanBackOnFire. Subsequent use of the HOME button will generally return you to LeanBackOnFire. Kodi etc can be installed and used as normal.

Everything seems to be okay as long as you don't perform any functions that cause the stick to slow down or lock up. One thiing I found was risky was attempting to use some alternate TV browsers (such as Joyen and TVBro) - they tend to cause slow-downs when trying to play video. If this happens, pressing the HOME button will likely return you to the default FTV Home, rather than your custom launcher. In this case, either restart the Fire TV, or quit the app that was bogging down the Fre TV, wait for half a minute or so and then pressing HOME should revert to your custom launcher.

I'm getting same results on Fire TV Lite (sheldon), and Fire TV 4K Max (kara), both runing 6.7.6.1 firmware.

I've found that Amazon's default Silk browser for Fire TV is a much safer bet, and runs better than any of the third party ones I've tried, so it's now become my default.

I hope this helps someone out!
[Fire TV General] xnappo:
Yes, this can totally work. Would just do it with Tasker if I had to, but I have managed to stop updates for now.
[Fire TV General] mimeau:
I thought I'd post it in this thread too in case some people would be interested. Based on daavm script in this thread , I made and published a light docker image that allows the instantaneous start of a launcher.

Here's the link to the Docker Hub image page.

There is two environment variables to set :

FIRETV_HOST to indicate the IP address of the FireTV

FIRETV_LAUNCHER to indicate which app (and Activity) to start. By default, it opens up Wold Launcher, so if you use it no need to set the env var.

So now, on any machine running docker, you can use:

docker run -it --net=host -e FIRETV_HOST=192.168.1.17 -e FIRETV_LAUNCHER=com.wolf.firelauncher/.screens.launcher.LauncherActivity mimeau/firetv-hook

or simply (if you use Wolf Launcher, and change the IP of course)

docker run -it --net=host -e FIRETV_HOST=192.168.1.17 mimeau/firetv-hook

Use -d option if you want to start the container in the background.

If you're using docker-compose, just add the following:

version: "2.1"
services:
firetv-hook:
image: mimeau/firetv-hook
container_name: firetv-hook
environment:
- FIRETV_HOST=<YOUR_FIRE_TV_IP_ADDRESS>
- FIRETV_LAUNCHER=com.wolf.firelauncher/.screens.launcher.LauncherActivity
network_mode: "host"

Just accept the new fingerprint on the FireTV and that's it. Instant launcher is back again :D

I've found that having Launcher Manager installed is still a necessity to access FireTV settings, so I advise against uninstalling it.

I'm running the script on my NAS, works fine for now. The script looks like it survived a FireTV reboot, but I have not testing extensively so YMMV.
[Fire TV General] Dimitrij4k:
i can add a Home Assistant Automation.... (for always on FireTV)

Set your Wolf Launcher on TV on and TV off to be the active App.... it dont fix the Home Button Problem, but it will make he TV experience better...

1. Add "Android Debug Bridge" into your HA via Devices

2. Config it with your FireTV IP

3. Make a Automation under Settings of HA

"IF" -> When the TV go on/off

"Then" -> Choose the Service Android Debug Bridge, then choose the Device "Fire TV" and set this command: adb shell am start com.wolf.firelauncher

The command is for the Wolf Launcher.

Maybe it will help somebody.....
[Fire TV General] soldiersinx:
I mentioned before that my gen 2 max updated but I was still able to use wolf launcher and the home button still took me back to it.

I tried to disable wolf launcher/launcher manager just to see if I can access the full settings. I wanted to run this firestick on a different TV, but unable to get to cec settings to set the soundbar/tv. I am unable to disable either wolf or lm to get to the stock launcher.

I put the Firestick back to the TV it was originally setup on so everything is working the way it is supposed to.

Is this the normal behavior once the fire stick is updated? I was originally on 8.1.0.0 I think. I don't mind if this is the case and wolf launcher/lm is now locked down as the default because adb is now locked.
[Fire TV General] signde:
I'm probably missing something here - with the latest fireOS 7 using Launch Manager Mini, how can I get to any fireOS settings? Non Mini provides most of these, Mini does not. Non Mini won't let me into them with Mini running, something to effect of ADB is already in use.
[Fire TV General] SweenWolf:
Use "LM Settings" from the following post

[ROOT][MANTIS][FIRESTICK 4K] Custom Launcher Support and System Patches

CUSTOM LAUNCHER HANDLER (FIRESTICK 4K) - 6.7.0.2 This is a method to enable certain features disabled/blocked by Amazon, and this method does require TWRP to be installed on the device. This does not require any root access so you don't need to...

xdaforums.com
[Fire TV General] simonchunk:
Can confirm LM Mini not working on 4K Max Gen 2 (Karat) 8.1.0.1. It will boot to Wolf after 25secs, but home button returns to stock launcher. Have tried the new LM Mini provided and all triggers, but none are working as others have found. Happy to do testing if needed
[Fire TV General] FireTV006:
Hello,

Same issue here.

I have bought a new FireStick 4K Max Gen2. I have avoided the 1st update during setup installation by following this : https://www.aftvnews.com/how-to-ski...reset-on-a-fire-tv-firestick-or-fire-tv-cube/.

So, the FireStick 4K max stays is OS version 8.1.0.1 and I have blocked the future update with Blokada apk.

arcus-uswest.amazon.com

softwareupdates.amazon.com

prod.ota-cloudfront.net

d1s31zyz7dcc2d.cloudfront.net

d1s31zyz7dcc2d.cloudfront.prod.ota-cloudfront.net

arcus-uswest.amazon.com

I have installed LM FOS 1.1.6 (because some success 1 year ago with FireStick 4K) but unfortunately, I was not able to deactivate KFTV launcher and replaced it by Wolf Launcher. I suppose that the OLD method is no more possible with OS 8.1.0.1

So, I have installed LM FOS 1.1.9 (https://xdaforums.com/t/app-firetv-...er-without-root.4176349/page-92#post-89132658) to use the NEW method but unfortunately, the hook of the HOME button doesn't work (tried witll all trigger keys) and on rebbot, Wolf screen appears 15s after startup.

I know that the NEW method through LM FOS 1.1.9 works with OS 8.1.0.1 because I have already do it 4 months ago on another box (but unfortunately updated to OS 8.1.0.2 and now ADB shell is blocked !)

To conclude, I have 2 questions :

1. OLD method is not possible with OS 8.1.0.1 ?

2. What are the recovery solutions when the Home button hook doesn't work as expected ?

Thanks for your support. It will be appreciated here ! ;)

EDIT:

For the question 2, I have used the workaround with Tasker and Termux : https://xdaforums.com/t/4k-max-with-tasker-to-launch-wolf-on-home-button.4541521/#post-87997103
[Fire TV General] jkbee26:
Hi,

Does it still work on any Fire TV, Android TV, Google TV?
[Fire TV General] MrTooPhone:
I still use the Wolf Launcher on my firestick and .ONN. No issues.
[Fire TV General] vuoshinotizy:
How? When i press home button the device return to stock home :/
[Fire TV General] MrTooPhone:
Maybe I got lucky long ago with the Firestick when I deleted the stock launcher. So now I am occasionally prompted how I want to proceed. I am offered Wolf Launcher or Launcher Manager. I choose Wolf Launcher. On .ONN, I don't use Launch Manager, I manually launch Wolf Launcher when I boot the device and all goes well. Hitting the Home button on .ONN does take me back to stock launcher, but Wolf Launcher is right their to click on again.
[Fire TV General] xnappo:
Yes, sounds like you disabled the package a really long time ago before the war even really started. Indeed you are lucky. For that case they never forced it back, but for newer versions it can't be done.
[Fire TV General] mea_pulpa:
Same here . Wolf launcher working and home button also still works perfectly .

I am using LM 1.1.6 . The firmware on my mantis firestick is 6.7.0.4 . @MrTooPhone What are your versions ?

I have disabled a bunch of packages through TDUK unified debloat toolbox app a long time ago , yet that app does not seem to work anymore since local ADB is "occupied" it sais . I can still check which apps exactly I disabled though .

TDUK update wiper does not work anymore either because of the ADB "occupied" .

If I can provide some info that could prove useful to get newer sticks working properly again , just ask and I will provide the info from my stick .
[Fire TV General] MrTooPhone:
Same, LM 1.1.6, Firestick 6.7.0.4

Never used any TDUK apps. Only "Background Apps and Process List" which still works.
[Fire TV General] Finnzz:
It's funny calling those TDUK apps on Wolf's own thread. Wolf created both, the Debloat tool is in the second post o_O

The answer to your question has been covered before. The FireHomeStarter app was disabled by LM on your Stick before it became a protected app. So now FireHomeStarter is locked in the disabled state, which is enough to keep using a custom launcher.

You'll lose custom launcher use after a factory reset or with an OTA FireHomeStarter update. Amazingly Amazon has never bothered to push one out to disable custom launchers on all the scraggler sticks holding on to custom launchers by a string :LOL:
[Fire TV General] MrTooPhone:
So long ago a suggested fix was to freeze or delete the stock launcher. So I made a copy of the stock launcher and deleted it. Just trying to understand my luck, if I had froze vice deleted the stock launcher, would I be back on stock now?
[Fire TV General] Finnzz:
This only worked for Sticks that still had FireHomeStarter disabled before Amazon protected the APK.

When you delete the default launcher (data partition copy) and press home, Android/FireOS asks what launcher to use.

Delete the Amazon launcher, when FireHomeStarter is still enabled and FireHomeStarter automatically makes the system partition copy of Amazon Launcher the default launcher.

The system partition copy is read-only, can't be deleted.
[Fire TV General] JoWazzoo:
Thanks - I guess that I missed his post. HAND
[Fire TV General] SweenWolf:
There is an apk in the OP for FOS5, will be updating that in a few minutes, check that out.

will have some issues but it is what it is.
[Fire TV General] JoWazzoo:
Thank you. Enjoying using your stuff, but still have problems with wallpaper & widgets in Wolf Launcher.
[Fire TV General] SweenWolf:
Sorry change of plans, removing the apk for now, will upload tomorrow.

About the wallpaper, goto Launcher Settings > Wallpaper > Turn on Application Wallpaper then select any wallpaper of your choice.

About widget, i will add an apk which will set the widget for the launcher.
[Fire TV General] JoWazzoo:
Cool. I have tried Wolf Launcher on a Firestick os 5.* and an Android 10 generic box (Transpeed) and in both cases when I go to Select wallpaper it is just a black screen. I have moved files up 1 directory and no joy. Thanks again for all your efforts.
[Fire TV General] SweenWolf:
On Android 10+ devices you will have to use CCGTV version otherwise you wont be able to select any launcher,

On FireOS 5, you'll have to enable "Application Wallpaper" in Launcher Settings or you will see a black screen because Amazon does not support Wallpapers.

And apps are added in the OP.
[Fire TV General] JoWazzoo:
Thank you. Will give it a try.
[Fire TV General] JoWazzoo:
"On FireOS 5, you'll have to enable "Application Wallpaper" in Launcher Settings or you will see a black screen because Amazon does not support Wallpapers."

Did that in both and no Joy. Clicked off & on a couple times.
[Fire TV General] SweenWolf:
After enabling wallpaper did you select any wallpaper or you just enabled or disabled.
[Fire TV General] AlexRuEkb:
Hi!

Now my AFTV4K OS 6280 has version 0.1.6 installed. How can you upgrade to Wolf Launcher 0.1.7 (FIRETV) without deleting the previous one so that you don't have to configure everything again?
[Fire TV General] AlexRuEkb:
Now my AFTV4K OS 6280 has version 0.1.6 installed. How can you upgrade to Wolf Launcher 0.1.7 (FIRETV) without deleting the previous one so that you don't have to configure everything again?
[Fire TV General] SweenWolf:
http://bit.ly/SWWL17

enter this link in downloader

open and install it. the launcher will be updated.
[Fire TV General] Toothless_NEO:
That's good to hear, I think the issue with SuperSU is theme related because in

That's good to hear, I have a Pre-Rooted Stock rom that I can probably use. As for SuperSU's crash issue I think it is theme related because a post in my thread here said it could be caused by the device theme, which aligned with the test I did by changing the SuperSU package name.

I'll report back if changing the theme worked.