yashsingh1/xdaforums huggingface dataset:
[Fire TV General] Finnzz:
It's hard to say. If you were already using Launcher Manager before the firmware upgrade it's worth trying. Use these steps:

https://xdaforums.com/t/app-firetv-...e-launcher-without-root.4176349/post-86717751
[Fire TV General] SONO1:
Hi !

I'm using a Amazon TV Cube 2 with Firmware 7.6.0.3 and have try to Blocked over Fritzbox 7590 .

Menu is Internet / Filter / List / Locked Internet sides :...

d1s31zyz7dcc2d.cloudfront.net

amzdigital-a.akamaihd.net

amzdigitaldownloads.edgesuite.net

softwareupdates.amazon.com

updates.amazon.com

Actually, I thought that updates are not possible anymore.

But updates are apparently not blocked !

Is there another change from Amazon ?

Greetz Alex
[Fire TV General] Greskac:
Is it possible to use a custom bootloader after the latest latest update for Amazon firestick? I heard that with the last update they enabled the use of custom launcher but nothing has been officially confirmed. I wouldn't want to update Firestick and then not be able to use a custom launcher.
[Fire TV General] Finnzz:
Does the Fritzbox block both http and https addresses, or only http? It would need to be able to block https addresses to work.

Custom bootloader is something very different than custom launcher. A custom bootloader would require bypassing secure boot which Amazon is not going to ever promote.

Where did you hear the latest update allows using custom launchers? That seems unlikely. The only people I have heard using a custom launcher on PS7603 are those that were grandfathered in by already having used a custom launcher prior to PS7273.
[Fire TV General] volkodav1975:
Google Chromecast with Google TV after updating Android 12, it is not possible to start another launcher. Can you help?
[Fire TV General] SONO1:
Hello Finnzz !

I have a Fritzbox 7590 ( latest Firmware ) there is no extra Option to block both http and https addresses,

Have you a Idear ?

Greetz Alex
[Fire TV General] Finnzz:
How are you determining if updates are blocked?

Try downloading this firmware bin from any device connected to the Fritzbox:

https://d1s31zyz7dcc2d.cloudfront.net/e27138e3d67ba0def02d589e77b14cc4/update-kindle-bueller-51.6.1.7_user_617513220.bin

This firmware is from one of the 5 addresses that you are blacklisting. If you can't access it, the Fritzbox block is working. If you can download that file, rather that entering just the 5 addresses, include https:// with each like this:

https://d1s31zyz7dcc2d.cloudfront.net

https://amzdigital-a.akamaihd.net

https://amzdigitaldownloads.edgesuite.net

https://softwareupdates.amazon.com

https://updates.amazon.com

Include the http:// version too for caution if you like:

http://d1s31zyz7dcc2d.cloudfront.net

http://amzdigital-a.akamaihd.net

http://amzdigitaldownloads.edgesuite.net

http://softwareupdates.amazon.com

http://updates.amazon.com

If you can still download the firmware bin above, then the Fritzbox isn't blocking https addresses. Since every router and company have their own router software it's hard to know what the router can do and how to do it without having the router itself.

If the Fritzbox can't block the firmware bin download, then try blocking updates via DNS block like so:

Block updates. DNS way. No root needed

Here is instructions of how to block Updates on a Fire TV. Important! Recently a Fire TV update released, it blocks any way to disable auto updates, except this one Some ISP are replacing client DNS requests by their own answers, in that case...

xdaforums.com

If that isn't working either then maybe something really has changed with updates in PS7603.
[Fire TV General] SONO1:
Hello Finnzz !

**** ...i can download this file ....my Fritzbox don't block this.....

hm , i have no idea.

Greetz Alex
[Fire TV General] Finnzz:
The Fritzbox probably doesn't support blocking https. It's not surprising, https is encrypted so that it's not possible for a lot (most?) of consumer grade routers to see https addresses.

Just use a DNS block method instead. There are a lot of tutorials on YouTube and Google on how to apply a DNS block. Or use Ighor's tutorial above.
[Fire TV General] brackenhill_mob:
Huh? Why can't you just block port 443?
[Fire TV General] Finnzz:
I meant blocking specific https addresses, not all https traffic. Blocking all https is going to lead to a lot of problems
[Fire TV General] brackenhill_mob:
LOL - I didn't read back far enough! My bad ;)
[Fire TV General] SONO1:
Hi Finnzz !

Your Tip to block all this Adresses works !

I have used the chances Sunday ...and have since every day testet Update check ........and last possible Check was Sunday !

Great Thx Alex
[Fire TV General] ermacwins:
Just dug out my firestick with Alexa and I can't install launcher manager, get a parsing error. It's currently on OS 5.2.7.3

However I have disabled updates with adb.
[Fire TV General] sibok:
Do you know what can I try to understand what's goig on? In my case, to be able to switch to another launcher i had to uninstall the amazon launcher.
[Fire TV General] Finnzz:
The first thing I'd do is check to see what other packages/apps you have disabled in case any are related to casting.

You can either run the ADB command

ADB shell pm list packages -d

Or you can use Wolf's debloat tool in the second post of this thread to see what apps are disabled (check mark). Make sure you include system apps by uncrossing the eye icon in the top right corner.

I'm a little skeptical that casting would have changed in the last 6months to start requiring Amazon Launcher to be active, but I really couldn't say for sure.

I don't think there is any functional distinction between a disabled launcher and an uninstalled one in the use of Miracast. In your case you still have Amazon launcher on the system partition anyway, it's just apparently not functioning, effectively disabled.
[Fire TV General] mmortal03:
You should mention this on the SmartTube Telegram group if you haven't already. I don't know what the expected behavior is on that, or any technical limitations involved, but people there should know.
[Fire TV General] Finnzz:
I don't think it's an issue specific to STN, or necessarily even a bug. If I'm casting Amazon Music to the FireTV, Miracast to the FireTV doesn't work either. But I can Miracast from a second phone that isn't casting to the FireTV already.

So on a second look, I think this may be a limitation of the source device doing the casting, not being able to Miracast while other apps on the phone are already casting.

This might even just be a limitation of my phone manufacturer (OnePlus) and OS?
[Fire TV General] volkodav1975:
Above I wrote that on Google Chromecast with Google removed the possibility of replacing the launcher. This launcher can be installed on Android 12 and assigned in its settings for autoplay. I enclose two versions, Russian and English.

View attachment 5747929
[Fire TV General] MrTooPhone:
Finally got around to installing today. No issue. Thanks again!
[Fire TV General] techker:
is the source code available?or is this a closed project?
[Fire TV General] Greskac:
Sorry, I was wrong. I meant installing a custom launcher after Amazon Update.
[Fire TV General] pras_pp:
Which app/files are blocking access to change original launcher?
[Fire TV General] Finnzz:
Probably /data/system/packages.xml

Installing / uninstalling / disabling packages (APKs) is handled by the PackageManagerService. The Package Manager stores app permissions in packages.xml

My guess is that the OTA and Amazon launcher apps are being given a permission in packages.xml that doesn't allow the app to be disabled at the user level. Launcher Manager relies on being able to disable the Amazon Launcher.

Someone with PS7273 firmware or newer, and root access, would have to confirm that.

Package Manager | Application Security Cheat Sheet

0xn3va.gitbook.io
[Fire TV General] Galoup:
hi,

it possible to remove the amazon launcher?

How ?

Thanks
[Fire TV General] BigBrosMo:
I just got a new 4k max. Unopened. Is there anything I can do to avoid having it locked to the Amazon launcher? I want launch manager.
[Fire TV General] Finnzz:
https://xdaforums.com/t/app-firetv-...e-launcher-without-root.4176349/post-87236889
[Fire TV General] BigBrosMo:
Ok thanks. I got the blocked updates working and added hosts to Blokada BUT now I can't download any apps. It just says "you own it" then I click download and it times out on reconnecting. I disabled blokada and it still won't download any apps. How do I get my downloads working?
[Fire TV General] Finnzz:
If you skipped the registration update, your current firmware is probably > PS7273. If so, you don't need to use a DNS blocker like Blokada.

Launcher Manager / other settings / Amazon os updates / disable system updates

This disables the OTA app.

I'm not sure what network changes Blokada makes. You may need to uninstall it and forget your WiFi connection, then reconnect to clear out any network settings changes.
[Fire TV General] BigBrosMo:
Thanks. Firmware is PS7608. But when I go to LM and choose block updates it won't change. Says Unblocked. If I click disable system updates it just flashes and still says Unblocked.
[Fire TV General] Finnzz:
PS7608 is the latest firmware for the 4K Max. It must have downloaded an update during the setup process (or it shipped with PS7608?). Launcher Manager / Custom Launcher use isn't going to work after PS7273. Both the OTA and Amazon Launcher apps are protected on PS7608.

You can return the Stick, and get a new one. Then follow the guide on how to skip the registration update. In a nutshell, when you first start up the stick and connect to your WiFi it will say checking for updates. Disconnect your router, hold back+menu buttons for 5sec until the accessibility menu appears, press back again, and that skips the initial update. Then register the device. Download Launcher Manager, block updates.
[Fire TV General] BigBrosMo:
But I am using it... Launcher Manager and Wolf Launcher. No issues.... no delay when I press home, and firestick reboots/restarts into Wolf Launcher. It says Update Error when I check updates... but I assume that's because I have Blokada on. Its DEFINITELY saying PS7608 is current firmware.
[Fire TV General] Finnzz:
In that case, I'm guessing you did avoid the registration update, installed LM + WL, but didn't successfully block updates. Then the device updated to PS7608.

LM+WL will keep working as is for now, as long as you don't disable WL / enable Amazon Launcher. If you do, Amazon Launcher can't be disabled again.

You have a few options, 1) get a new stick, block updates right away and keep the ability to disable/enable Amazon Launcher and OTA apps. 2) keep what you have and use a DNS blocker like Blokada to avoid any further updates 3) keep receiving updates and hope for the best, LM+WL will keep working as long as they don't push an update that force-enables Amazon Launcher.

A lot of people didn't block updates after PS7273 and are holding on to their LM+WL like your are now, and just hoping for the best, continuing to update their firmware.
[Fire TV General] Palindrombn:
I now have a fire stick max, if I have the Wolf L installed, can I still use the Netflix and Disney buttons on the remote or will they no longer work?
[Fire TV General] Finnzz:
Yes channel buttons still function normally. Launcher Manager only indirectly remaps the home button, by setting a custom launcher (Wolf Launcher in your case).
[Fire TV General] eXtremeDevil:
Any news on this? Is this project still alive?
[Fire TV General] questionesse:
Just checking back every once in a while - by skimming through it looks like there's still no way to get the launcher working again?
[Fire TV General] pitsensas:
Hello,

I'm new in the FireTV world and I have bought a Fire TV Stick 4K with FireOS 6.2.9.3 (NS6293/4731).

I want to change the default launcher by another (Wolf or Leanback), so I have followed the instructions to save and after deleted the KFTV launcher app.

But now, when I go to Launcher Manager, I can see that the current launcher is com.amazon.firehomestarter.FireHomeStarterApplication

I found this topic.; https://xdaforums.com/t/app-firetv-...er-without-root.4176349/page-51#post-86770371

Can I follow it without any risk ?

Because I'm not able to save com.amazon.firehomestarter and com.amazon.tv.launcher before to uninstall them and I do know if I can find the "right" launcher on this cloud : https://gist.github.com/JulyIghor/d3d3dd460527a1d2b5b67954160d4abf

Thanks in advance
[Fire TV General] pitsensas:
Hello,

So, I have tried by disabling instead of uninstall but withtout success for com.amazon.tv.launcher and com.amazon.firehomestarter !

C:\androidSDK\platform-tools>adb shell
mantis:/ $ pm clear com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.tv.forcedotaupdater.v2
Success
mantis:/ $ pm disable-user com.amazon.tv.forcedotaupdater.v2
pm disable-user com.amazon.tv.forcedotaupdater.v2
Package com.amazon.tv.forcedotaupdater.v2 new state: disabled-user
mantis:/ $ pm clear com.amazon.firehomestarter
pm clear com.amazon.firehomestarter
Success
mantis:/ $ pm disable-user com.amazon.firehomestarter
pm disable-user com.amazon.firehomestarter
Error: java.lang.SecurityException: Cannot disable a protected package: com.amazon.firehomestarter
1|mantis:/ $ pm clear com.amazon.tv.launcher
pm clear com.amazon.tv.launcher
Success
mantis:/ $ pm disable-user com.amazon.tv.launcher
pm disable-user com.amazon.tv.launcher
Error: java.lang.SecurityException: Cannot disable a protected package: com.amazon.tv.launcher
1|mantis:/ $
[Fire TV General] Finnzz:
Amazon patched FireOS 6.2.8.7, Launcher Manager doesn't work after that version unless you were already using it before the patch.
[Fire TV General] pitsensas:
Thanks for this precision !

As I can not select a custom Launcher anymore, Do you recommend me to update with FireOs 7x ?
[Fire TV General] Finnzz:
FireOS6 FireTV devices can't be updated to FireOS7.

Amazon updates FireOS6 and FireOS7 in parallel. Custom Launcher use was patched in 6.2.8.7 and 7.2.7.3, which were both pushed out to FireTV devices last March.

If your Fire Stick is still within it's return period, my recommendation would be to return it, and buy a new one. The new stick will ship with old firmware (pre 6.2.8.7). Skip the setup firmware update, block updates, and then you can still use custom launchers with LM.
[Fire TV General] pitsensas:
Thanks. Custom Launcher is not a priority. I have putted the Wolf shortcut on the Homescreen, so a click on this one and Wolf menu appears !

So, I will keep this box !
[Fire TV General] ersan191:
Unrelated to OS6, but I ordered two 4K Max sticks on Black Friday - one Refurbished and one New and they both came with 7.2.7.9 installed already. If anyone was trying to get a pre-block 4K Max you'll have to look elsewhere.
[Fire TV General] SevenFXD:
where's the Wolf Launcher apk?
[Fire TV General] arkvays:
https://apkpure.com/de/wolf-launcher/com.latestlaunchers.wolflauncher#menu
[Fire TV General] Finnzz:
Last version before development stopped.
[Fire TV General] leodawson:
Darn... Tried it with the Fire stick 4k max, using Fire OS, version: 7.6.1.4. Doesn't work. I really appreciate this app though, thanks for creating it... I despise the stock amazon launcher, I hope there's an update in the future that'll make this work on newer Fire OS versions.
[Fire TV General] linolino:
happy now.

Downloaded (wolf)Launcher App.

Used the Procedure to remap my (unused) Disney+ button on the remote for RemapperApp and when pressing the "Disney+" button on remote now the (Wolf)Launcher) opens up
[Fire TV General] xnappo:
After a few hours, I managed to get instant home-key launching of Kodi (my preferred launcher) using Tasker and Termux. I think it is somewhat similar to @daavm 's method.

Quick demo:

I will edit this post as people find problems, sorry I did this over two days and I am sure I will miss something.

The key is to use Termux to launch the new launcher, and to run it twice.

Below you will need to install stuff inside Termux such as vi and adb.

Install Termux and Tasker

Install Android tools inside Termux:

pkg install android-tools

Set up Termux permissions for Tasker:

adb shell pm grant net.dinglisch.android.taskerm com.termux.permission.RUN_COMMAND

In Termux edit ~/.termux/termux.properties and uncomment the line:

allow-external-apps = true

mkdir ~/.termux/tasker

cd ~/.termux/tasker

vi ~/.termux/tasker/runKodi

(if you don't know vi, use nano)

runKodi contents:

adb shell am start -n "net.kodinerds.maven.kodi/.Splash"

(I *think* the command for Wolf Launcher is "com.wolf.firelauncher/.screens.launcher.LauncherActivity")

Save file

Test running 'runKodi' launches Kodi

In tasker, set up a TaskerFunction->TermuxCommand:

TermuxCommand(/data/data/com.termux/files/home/.termux/tasker/runKodi,,,false)

Copy/paste so this runs twice

Test task works

Give Tasker permissions:

adb shell pm grant net.dinglisch.android.taskerm android.permission.READ_LOGS
adb shell pm grant net.dinglisch.android.taskerm android.permission.SYSTEM_ALERT_WINDOW
adb shell am force-stop net.dinglisch.android.taskerm

Assign profile to launch it, I am using the logcat looking for:

amazon.intent.action.HOME_PRESSED

Good luck!!
[Fire TV General] mai55:
Привет, ребята!

Я работаю над темой.
[Fire TV General] rety20:
The android TV version seems to have broken my installation of the latest version of lineageOS on raspberry pi 4B.

Enabling custom launcher immediately disabled my controls (back, home, directional navigation, select etc). And current launcher changed to something along the lines of "select default home launcher dialogue box". Mouse controls still worked, and selection of "enable, disable, options" was possible, but clicking on them did nothing. After restarting the device, it won't boot past a completely blank gray screen with mouse cursor. Some system components are working (or not) as "unable to connect to WiFi" notification appeared briefly.

Looks like I'm gonna have to reinstall Android TV to fix this. Would suggest that those running lineageOS on raspberry pi refrain from using this app until this major issue is resolved.
[Fire TV General] mai55:
Finished working on the theme "Wolf&Glass". 150 transparent banners. Wallpaper included. It is better to use dark wallpaper, plain. Banner sizes are adjusted in the launcher.

P.S. You can order the missing custom banners
[Fire TV General] meeeeeeeeeeeeeeeeeeow:
Man, you are the best! Maybe you could alter the tutorial for first time Termux users:

They have to run the

pkg install android-tools

command to be able to use adb shell and also after the first time running an adb shell command you get a prompt where you have to accept (and tik the message box once), then run the same command again.

And also the steps 10 - 11 have to be repeated after creating a profile.

Which event would you choose to start the task after the boot/wake up from standby? Currently I'm using the Launch At Boot app which allows to start an app after the boot / wake up. It would be more convenient to use just different profiles instead of different apps for every use case.
[Fire TV General] xnappo:
Thanks for the input! It was hard to think about Termux stuff since I already had it installed for a while. I am a bit confused about what you mean by repeating 10-11 after creating the profile? I just pointed the profile to that task?

Glad it worked for you. For the boot case I am using a profile:

Event->System->Device Boot

Also - instead of running twice, I now use something to check if the first time worked, and only then do it again. I can provide these details if the running twice isn't reliable for others. I think most are using Wolf instead of Kodi, so not sure how well this works.

@Falcon_X FYI
[Fire TV General] meeeeeeeeeeeeeeeeeeow:
I was not able to link the task to the new profile, instead I had to create a new one. It would be nice if you provided the alternative way. I'm using it with Wolf Launcher.

I'm no tasker pro but is there a way to disable the notification for the task? Also is there a way to minimize the delay (I know it has to be written into/read out the log first, but maybe there is a delay inside tasker)?
[Fire TV General] xnappo:
That is weird, for me when I create the profile, then back out, it asks my to link it to a task, and the task I created was on that list...
[Fire TV General] meeeeeeeeeeeeeeeeeeow:
Ok the wake up event is: Event -> Display -> Display On.
[Fire TV General] xnappo:
Yep - sorry I was thinking boot - Display On is also super useful - I actually use this to do some other various stuff too (sometimes my projector doesn't turn on, so I send a network command to turn it on).
[Fire TV General] eXtremeDevil:
Quick question, right now I have the package com.amazon.firehomestarter disabled (it was disabled before the system update that prevent disabling packages) and com.amazon.tv.launcher enabled, so right now I can use any launcher and I'm in fact using Wolf Launcher. But what I can NOT do is launch stock launcher. Do you guys know of any command like "launch com.amazon.tv.launcher/ActivityX" to bring up the stock launcher?

Thanks!
[Fire TV General] meeeeeeeeeeeeeeeeeeow:
Don't you have a backup of the original launcher apk? I think if you go this way you are not able to use the original launcher. You have to install the old file or reset your Fire device
[Fire TV General] eXtremeDevil:
I do have the original launcher installed and enabled, only the firehomestarter package is disabled (but also installed).
[Fire TV General] Finnzz:
am start -n com.amazon.tv.launcher/.ui.HomeActivity_vNext

But I'm pretty sure it won't work for people who uninstalled the Amazon Launcher to set Wolf back to the main Launcher. It doesn't seem to matter that the system partition copy of the launcher is present and enabled.

It's probably why it hasn't set itself back as the main Launcher.

What do you need to access from the Amazon Launcher?
[Fire TV General] eXtremeDevil:
I just wanted to have the possibility, although is not strictly necessary. What do you guys mean by "uninstalled"? I never uninstalled the launcher or any other system app, it is only disabled (homestarter, not the launcher).

EDIT

I tried the command and it's giving me this:

Unknown command: start

EDIT 2

Seems like the correct command is "am", now I get this:

Error type 3
Error: Activity class {com.amazon.tv.launcher/com.amazon.tv.launcher.ui.HomeActivity_vNext} does not exist.
[Fire TV General] Finnzz:
Sorry, corrected, yes am not pm

It's not going to be possible to access the homescreen for those that are hanging on to WL because FireHomeStarter is still disabled. Download Activity Launcher and check KFTV (Amazon Launcher), it will show you all the activities, and you can click on them to try them, but none of the accessible ones will take you to the homescreen.

If you really need the Amazon homescreen, you can look into the home button remapping method that people have been mentioning here and on other threads. It keeps KFTV accessible but it has downsides and I think you are better off with what you have now.

If you re-enable FireHomeStarter, then you will never be able to go back to that method. It's a one way street.
[Fire TV General] eXtremeDevil:
I know that, I don't want to enable HomeStarter by now, I will keep it this way. Thanks for the info!
[Fire TV General] bluedisc:
wrong thread