yashsingh1/xdaforums huggingface dataset:
[Fire TV General] Finnzz:
I didn't mean to go after Ighor. Using your own DNS server or a known public one would be my preference. Ighor's write-up is a good stepping stone for anyone that wants to block updates immediately, while they figure out a long-term self-reliant method.

@TakeTheActive your devices are unique in that they are running much older software versions, so you have more options than regular devices out there. The update skipping trick before registration no longer works on newer software builds, unless like Wolf mentioned you have root access.

For your FireHD tablets, you should root them and put LineageOS on them. I know that the 2016 and 2017 models are rootable and a few others from that time. I get nearly 60days standby time on my 2017 model with lineageos, and it's noticably faster

https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/

@Sus_i glad the Max is still in the clear. I'm also curious, what build of FireOS7.2.5.5 are you on? 2465?
[Fire TV General] Sus_i:
No, sry, just had a look and it's probably not the latest out there.

kara:/ $ getprop ro.build.version.number
0021911669892
kara:/ $ getprop ro.build.display.id
PS7255
kara:/ $ getprop ro.build.version.release
9
kara:/ $ getprop ro.build.date
Tue Oct 19 17:37:58 UTC 2021
kara:/ $ getprop ro.build.fingerprint
Amazon/kara/kara:7.0/PS7255/2444N:user/amz-p,release-keys
kara:/ $

So my stick runs an older OS, PS7255/2444 from Oct 2021.

I wonder why my stick shows still as up-to-date. I guess I need to enable updates to check this again.
[Fire TV General] Finnzz:
Maybe it's Amazon's rolling updates, and 2465 is still in the process of rolling out to all devices.

Does 2444 have the 2min boot time with Amazon launcher disabled, or does that happen only with 2465?
[Fire TV General] Sus_i:
Maybe yes, I'm going to take a look for 2465.

Just enabled the OTA package, but got an error... because of Ighors DNS :) It's working awesome.

Idk. Haven't played with the Max, sits in a drawer most of the time ;)

What launcher is affected?
[Fire TV General] TakeTheActive:
I don't see either of us as 'going after Ighor' - I DO see us educating the 'Non-Technical' folks of the 'possible' dangers of using an 'unknown' third-party site (long time) as their 'firewall' ;).

As I stated in my previous post, I haven't tried my 'procedure' (from my recent virgin 'Tank' FOS5 experiment) on my virgin Firestick 4K 'Mantis' w/FOS6 yet (maybe tonight), but, with my Pi-Hole DHCP Server BLOCKING the Six DNS Addresses, I'm curious to see how a virgin Firestick 4K 'Mantis' reacts - does it FAIL to UPDATE but still go to Registration; or does it do 'something else'? :coffee: 🍿

One thing that always discouraged me from rooting them was, IIRC - it's been a LONG time since I researched this - opening the case, partially disassembling the tablet and shorting some pins.

​

THIS ^^^ is good news! Thanks!!! (y)

I'm sure glad that I met you 'through Reddit'! :) 🍻

(y)

SO MANY (Non-Technical?) folks don't realize the amount of time and effort required to dis-assemble / reverse-design SOMEONE ELSE'S code in order to UNDERSTAND their THOUGHT PROCESS and then be able to SUCCESSFULLY Enhance / Add Features / Improve upon it... :rolleyes: :(

Rather than appreciate what they've already received for FREE, I still see NEW users IMMEDIATELY asking for MORE features to be added... :eek: :p :( :rolleyes:
[Fire TV General] Sus_i:
I don't think the DNS will harm anything.

The fireTV uses Certs all the time, everything is encrypted...

Give it a few weeks, then it's Method #6 in the AFTVNews block guide ;)
[Fire TV General] Bashar20:
it seems there is an issue with Wolf Launcher 1.1.9 backup and restore. I took a backup using 1.1.9. Uninstalled it then reinstalled it and restored from backup but my sections, order of icons and wallpaper were not retained. Wolf_Backup folder is present and the Files folder contain my wallpaper and sections. Any thoughts?
[Fire TV General] TakeTheActive:
OFF-TOPIC:

Americans have a LOT of colloquialisms / sayings. IMHO, this is because a LOT of unexpected CRAP occurs during our lives and our parents, and their parents, and their parent's parents, started saying things that just sort of 'caught on', like "The best-laid plans of mice and men (often go awry)".

Spoiler content hidden.

Back to Firestick land:

I installed Launcher Manager 1.0.7 for FOS5 on my virgin 'Tank' and I couldn't get the Wolf Launcher to launch with the HOME button so I attempted to install FireTV Settings 3.0, which wouldn't install. So, I tried FireTV Settings from the TechdoctorUK Tutorials and that did install, but didn't do anything either. So, I tried a few ADB commands:

adb shell pm grant com.wolf.fos5.settings android.permission.SYSTEM_ALERT_WINDOW

error: protocol fault (couldn't read status): No error

adb shell pm grant com.wolf.fos5.settings android.permission.READ_LOGS

error: device '(null)' not found

adb shell pm grant com.wolf.firetvsettings android.permission.WRITE_SECURE_SETTINGS

error: device '(null)' not found

So I tried the FireTV Toolbox (FOS5 1.6) on my Android Tablet:

Setup Launcher Manager [GO] 'appeared' to work fine.

I went to my Firestick 'Tank' and Launcher Manager now showed "Permissions Granted" but it still wouldn't launch the Wolf Launcher when pressing the HOME key on the remote.

So, I now went back to my Android Tablet, using FireTV Toolbox, and Uninstalled Launcher Manager App

Now, my Firestick 'Tank' is BRICKED - Oops...

It's only $20 lost but if there's an ADB command, or two, that I can send, I'll give it a shot.

I guess that I put the Launcher Manager App 'in charge' and then when I uninstalled it, the Amazon Launcher DID NOT resume control. I can now certainly see how easy it is to "Screw Up"... :(
[Fire TV General] Sus_i:
Hmm, can't see the reason for a brick, but (if adb isn't aviable) you may try the unbrick solution here:

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)

Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...

xdaforums.com

There are sticks out with a patched bootrom, so you may try the unbrick in order to know if it will work for your device...

In case the stick is permanently bricked, you can also trade it in at amazon... This way I've got my 4k-Max for about 20 bucks, shipped in a broken first-gen fireTV without remote and powersupply ;)
[Fire TV General] SweenWolf:
FireTVSettings uses Accessibility Services and no longer works on Stock OS. I use it daily because I have a patched stick. (So its only for those whose Device allow binding of Accessibility Services on 3rd-party Applications)

Because its mimimum required Android version is Nougat

There is something wrong with your ADB (download latest platform tools from Google)

and WRITE_SECURE_SETTINGS permission is no longer required for Launcher Manager for FireOS 5.

About error: device '(null)' not found make sure your are connected via adb

if you have multiple devices connected then you can use

adb devices

to get list of attached devices

and then you can use

adb -s deviceID shell

to connect to adb shell, here deviceID can be anything, if its an emulator then its gonna be "emulator-5554"

if its a device connected by usb then it will show devices serial number

if its connected by TCP/IP protocol then its goona be devices ip along with its port "192.168.43.20:5555"

if you use any app that emulates adb shell connection then you can omit adb shell and can start with pm grant

(This info is for anyone who encounter a problem like this, considering if they read the posts)

if you the watchdog is running and you have given SYSTEM_ALERT_WINDOW and READ_LOGS permissions then just select the launcher from the list and check the "Launcher Detection" checkbox and click save.

Sometimes its killed so just open the Launcher Manager once again and press home.

FireOS 5 has crappy adb deamon so we cannot run adb commands on the device natively.

and the LM (FOS5) - 1.0.7 does not perform any change on the system. It just checks if you have pressed the home button, if you have then it launches the Custom launcher.

What do you mean by bricked? i need more info on that

This version of LM can not kill a stick (DO NOT WORRY, just do not perform a factory reset.)

if you do then you will lose ADB authorization, you can always connect your pc directly with your stick with USB to revive it.

Launcher Manager is never in charge, if it was then there wouldn't be any 5 second delay to launch any app.
[Fire TV General] TakeTheActive:
My apologies for my delayed response here on XDA - I've been attempting to put out my 'TiVo Fire' 🔥 all day, between hours on the telephone with both their Level 1 and Level 2 Tech Support and composing a narrative on the TiVo Community Forum detailing my 'problem' (and TiVo's lack of support; It's tiring...).

TL;DR:

Right after running UNINSTALL Launch Manager via the FireTV Toolbox, I lost 'Navigation Control' (i.e. I couldn't move my cursor / select ANYTHING). I re-booted my Firestick several times. Maybe once, I saw the Wolf Launcher come up (but couldn't do anything with it), then after the next power-cycle, I saw 'Background Apps & Processes' come up - sadly, it's all a 'blur' now since it happened so fast and I wasn't expecting any problems. So, I bailed out for the night.

This morning, after a night's sleep, I didn't want to be "That Idiot" with dead batteries in his remote, so I pulled the batteries and re-tested them in my 'Chinese Battery Tester with a Small Resistor Load' (better than an unloaded DVM, IMO). They were EXCELLENT a week ago when I broke the seal on the box and installed the Firestick (even though I bought the Firestick several years ago) and they were STILL excellent today. * BUT * when I re-installed the batteries, the remote began working again. Son-of-a-Gun?!? Somehow the Bluetooth / WiFi / RFE from the remote to the Firestick got 'borked' and everything is now working fine :confused: .

Some 'Yada, Yada, Yada' on why I did what I did:

Considering the age of my virgin 'Tank', running FOS5 (5.2.4.2), I felt that it might be worth a shot to try some older software from that era.

Text like:

...gets me confused (i.e. I see the word 'ANY', even though I don't know what '71 or lower' means). ;)

I'm running Android Debug Bridge version 1.0.32 on my old Windows Vista PC, where I run a lot of 'Old Crap' like '"Who's on my WiFi?", etc... that I don't want to clutter my main Windows 7 PC up with. I'll look into upgrading...

But, but, but... it's in Post #1?!? ;)...

So, today, besides the 'strange phenomenon' of coaxial cable center conductor oxidation causing 'select' frequency attenuation, I now have to worry about Firestick remote radios getting accidentally 'borked' when unistalling software :) .

Thanks for your timely, detailed response to my questions and I hope that both your response, and my detailed reply today, help someone reading this thread in the future :cool:.
[Fire TV General] Sus_i:
Nope, imo thats the wrong approach.

Quit using old third party stuff.

You may go ahead and just 'unlock' the whole potential of your stick.

[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)

Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...

xdaforums.com
[Fire TV General] Finnzz:
I didn't even think about rooting, that's definitely the best way to go if it's possible on that Tank!
[Fire TV General] Sus_i:
TakeTheActive talked about an old stick that shipped with an old OS, so the stick is 100% vulnerable to amonet. :)

Only late tank sticks, manufactured in december 2019 or later, are probably not vulnerable... which is a really bad thing, because the unlock solution is a superb unbrick solution too.

Rooting the OS (flashing magisk) is an optional step...

If you unlock the bootloader, you can do almost all with TWRP recovery and it's shell too.
[Fire TV General] Alza3eeem:
New video about Wolf launcher 1.9 and LM 1.5

I am happy for @SweenWolf finally get recognized on youtube... many thanks Wolf for your hard work.. keep up the great job..
[Fire TV General] CloudItaly:
If you can give me some instruction, i can try to create an debug file for you.
[Fire TV General] TOMillr:
@SweenWolf

A quick feature suggestion: Is it possible to add advanced configuration options for HDMI-CEC commands?

I'd love to have the ability to assign unused CEC button presses from the TV remote to custom Android TV remote control inputs.

For example, you could use the "red"-button from the tv remote to act like the menu button or launch a specific app. Or double pressing the "back"-button on the tv remote to be registered as the "home"-button. That way you could get around the Android TV interface by just using the TV remote and the CEC protocol.

There's a tool for the nVidia shield that allows HDMI CEC remote button presses to work as customizable shortcuts:

https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/297663/auto-refresh-rate-tool-google-play/
[Fire TV General] Alekos:
imagine if Wolf teamed up with the dev from FLauncher? endless possibilities....
[Fire TV General] Powerfader:
Is this the latest version for a 2019 Nvidia Shield Pro?

Short Link for Downloader

Launcher Manager 1.0.4 (ATV)

https://bit.ly/SWLMA104
[Fire TV General] Alekos:
Yup
[Fire TV General] Finnzz:
If you can connect your FireTV to a computer via USB, then you can make an ADB connection with the device early in the bootup process. You can then use logcat to record the boot process. This will generate A LOT of messages that will be hard to sort through, but it's a starting point at least.

Here is a brief intro to logcat:

https://xdaforums.com/t/tutorial-how-to-logcat.1726238/#post-28187592

EDIT: if you make an ADB connect, you can type reboot to restart the device, and then type the following to automatically reconnect and start logging:

adb wait-for-device && adb logcat > logcat.txt
[Fire TV General] Powerfader:
It doesn't install
[Fire TV General] Finnzz:
Is your Shield on AndroidTV 9 or 11? If you are in AndroidTV 11, then you may be in uncharted territory. I doubt Launcher Manager was ever tested on 11.

EDIT: Launcher Manager appears to still work on the Shield after the 11 update, according to this thread:

ShieldAndroidTV/comments/s2ao8r
[Fire TV General] Alekos:
I have the 2017 shield 16GB with version 9.0 (A11) and it works fine. What error are you getting when installing it? How are you getting it on your Shield? Direct through the bitly link or copying it from your phone? Restart your shield and try again and update us with more information.
[Fire TV General] Powerfader:
I finally found a way to get it downloaded and installed, but I had to uninstall it and go back to the v.1.0.3, because the v.1.0.4 would not allow me to disable the Wolf Launcher to enable me to switch back to the nVidia stock launcher.

I had no issues rolling back and my Wolf Launcher was still intact and functioning properly.

But thanks for the reply.

Btw, I am using a 2019 nVidia Pro with the nVidia 9.0.1 Android 11 update with all 4 hotfixes. The latest hotfix was dropped about 2-3 hours ago. I installed from this site using this code. https://bit.ly/SWLMA104
[Fire TV General] Powerfader:
Yeah, It worked fine, except for allowing to return to the stock launcher.
[Fire TV General] Alekos:
ok, weird, I just installed 9.01 Shield Experience, removed 1.04 and removed wolf launcher, reinstalled Wolf 1.1.9 and it worked. Also worked with FLauncher.

Can you try one last time with 1.04 and latest Wolf? download 104 (and make sure it installs, I usually install it on my phone first - without running and it and removing it right after, just to make sure the apk isn't corrupt, then transfer it to the shield using x-plore (don't use ES File explorer, unsafe). Streamhub's library from Unlink has latest wolf launcher and x-plore if you need it...
[Fire TV General] Powerfader:
I tried the Streamhub but I kept getting a parsing error. Besides, I already have Wolf Launch 0.1.9 installed. So, I went online to several 3rd party sites and there is no v.1.1.9 I am figuring you did a typo. I believe the most current version of the Wolf Launcher is v.0.1.9

Ok, got it figured out and it probably always did work properly. After I disabled the Wolf Launcher, I would click on the back button on the v.1.0.3. With the new updated v.1.0.4 if you click the back button you stay on the Wolf Launcher, but when you click on the home button then it takes you back to the nvidia stock launcher home page. What is weird though, if I disable the Wolf Launcher and click the back button it takes me to the Wolf Launcher page. Now I can do everything on that page as normal i.e., clicking on apps, exiting those apps search, play, etc... and everything functions fine, but as soon as I click the home button it will take back to the nvidia home page.

It doesn't bother me, but I was wondering if that is harmful in any way? If not, then why not just enable the Wolf Launcher. Then immediately disable it and click the back button instead of the home button and surf around on the Wolf Launcher page and when you want to go back to the nvidia home page just click on the home button without going to the Launch Mager app since you have already disabled the Wolf Launcher. Does that make sense? Try it. After you have disabled the Wolf Launcher click the back button and it will stay on the Wolf page. Now while you are there click your home button and it will switch you to the nvidia home page without going back to the Launcher Manager to disable the Wolf page, because it has already been disabled.

Btw, I was just used to clicking the back button to go to either navidia's or Wolf screens with the v.1.0.3. The v1.0.4 requires you to click the home button instead. When I enable Wolf, I can click the return button and it takes me to the Wolf page, but when I disable the Wolf page, I have to click the home button to go back to the nvidia page. Clicking the return button does not take you back to nvidia page.

Btw, what is the point of the new option "Custom Launcher Options"? Why would I want to launch by default to any app other than the Wolf Launcher? I can map a button on my remote to do that. Right now, I have 48 apps hidden on my Wolf page and with 1 click on my mouse they are revealed for me to use. Then with another click they will all disappear again. I have my Tivimate app embedded on my background pic and with a click on my Go/Select button on my remote it will launch my Tivimate app. So, I don't understand why I would use the Custom Launcher Option? Am I missing something, or not understanding the function?
[Fire TV General] Finnzz:
Just different use case scenarios, greater flexibility.

I saw one user wanting to setup a FireStick for Kodi use only. The device was for his father and by making Kodi the Launcher, the device boots straight to Kodi and keeps him in Kodi if he presses home.

Generally the custom launcher option helps set an app/launcher that is not detected by the OS as a launcher.
[Fire TV General] dikodahan:
hey @SweenWolf

Please find the attached translation file for Hebrew (Israel).

Bear in mind that this is a right to left language, so, if you can add to the next beta version I'll be able to test and see how it works in the LM.

Thank you!
[Fire TV General] Powerfader:
but you can just as easily do that by mapping a button on your remote or set that app as a widget on your home screen. I set Tivimate on a full screen widget and made that widget invisible. So, all I have to do is click the go/enter button on my remote to launch Tivimate. prior to my getting Tivimate I remapped the Netfliux button to launch my iptv service.

But I get your point about the older generation and tech. I am 70 yrs old and can't stand trying to teach those old farts anything about tech. lol
[Fire TV General] dikodahan:
Thank you for pointing it out.

Can you please share the latest version of the strings file so I can make the necessary updates and additions?
[Fire TV General] dikodahan:
I believe I found it, though this one is from SweenWolf's post for beta2 and there might be a few additions still needed (I don't recall seeing any of the pin password sections in it).

Please find the attached updated version.

As far as the name of the language to be listed (I think it would be good to add that to the XML file in the future as well, could not see it in there now). The parentheses seems off but that is because it is a right to left language. Should be fine with a copy/paste.

עברית (ישראל)

he-IL, Hebrew (Israel)
[Fire TV General] Nathaniel9:
Based on the current version 1.6.0(beta3) I have added the missing strings to your strings.xml file.

See your conversations.

For all other translators I extracted the original strings.xml file of version 1.6.0(beta3). See file attachment.
[Fire TV General] dikodahan:
here you go
[Fire TV General] psymsi:
If anyone is still looking for a (safer than external DNS) way to prevent updates, see my post below. I've been able to block manual update checks using the latest AdAway and the AFTV update URLs. No reason to believe this won't stop the automatic updates as well.

OTA update block with AdAway (no root)

Edit: WARNING A few reports of AdAway temporarily stopping the service. You could possibly double up with Adguard or a similar connection blocker. But it's not going to be 100%. Router blocking or a Pi-Hole setup is going to be more secure, so...

xdaforums.com
[Fire TV General] tjuma:
Should have blocked updates :(

The newest one (FOS 7.2.7.3 PS7273/2622) seems to have broken the ability to set a new launcher with launcher manager on my FireTV Cube.

After activating custom launcher it stays on: "KFTV-Launcher (Stock Launcher)" and hitting the home button just takes me back to stock launcher without showing the usual popup. Tried reinstalling newest versions of LM and different launchers plus clearing data/cache but nothing seems to help.
[Fire TV General] Finnzz:
That came quick after the update protection
[Fire TV General] froli13:
Same for me on Firestick 4K on FOS 6.2.8.7 (NS6287/3768). It's the first time it happens to me at least? Is it something that occurs often? Will an update of launcher manager fix that at some point or do I have to find a way to downgrade FOS?
[Fire TV General] Alza3eeem:
Hello, if you found a way to downgrade please share
[Fire TV General] trapperjohn:
Hi,

With firestick 4k just came out with os 6.2.8.7

launcher has stopped working it will open but settings will not stick.

Up to today I was using launcher (1.1.5) and wolf ( 0.1.9)

So now when hitting home button it takes me to default fire is screen have not seen this for many months !!!

Is there a newer version of launcher than 1.1.5 that will!

Thank you for your help,

Bryan
[Fire TV General] brackenhill_mob:
I too have latest nVIDIA Shield ROM with Hotfixes applied and 104 works perfectly for me with FLauncher - finally a decent, non-intrusive home screen again ;)

@Powerfader @SweenWolf