[WINDOWS][TOOL]Fire Toolbox V30.0

Search This thread

Datastream33

Senior Member
Sep 17, 2017
2,334
2,039
I believe the problem is not that Automate stops working during media playback, but the button mapping itself. I had a similar problem with audio playback and the home button not functioning. I had a chat with @Datastream33 and he made a couple changes that corrected the problem. I believe he mapped the button differently because the button mapping was taken from Automate by the media app while using it. I don't know the exact issue, but it's close to that. I tagged Datastream here because you'll need to talk with him about the issue you're having. He's been in here frequently the past few days so he'll probably see this soon. (y)
I'm wondering if the tablet is running Android 11. Perhaps it handles media buttons differently and the apps are consuming the key presses? My OnePlus is running a custom Android 12 rom... going to try it on that.

EDIT: It looks like the keyevents are being consumed by media apps. Hmm...
 
Last edited:
  • Like
Reactions: blaacksheep

ooonimrodooo

Senior Member
Jan 28, 2011
261
109
Corfu, Ny
Hmm, I'm sorry to hear that, my friend. Doesn't sound fun! Let's see if we can figure out a solution. Firstly, I just have a few questions regarding the tablet's current setup.

Which specific tablet do you have? Automate was installed and the flo was imported by Toolbox V29.0, right? Does the home button function as normal when not viewing media? *What's the current navigation bar layout? Lastly, could you please specify some of the apps where the issue occurs?

*The navigation bar layout can be obtained by executing the following command in an ADB Shell:
Code:
settings --user current get secure sysui_nav_bar

I know I'm asking a lot of questions... just hoping we can get enough information to figure this out. Thank you so much in advance for any answers to the questions provided.
Thanks for your reply!

I have the Fire HD 8 Kids Pro. Bought it during Prime Day this year. Unfortunately the it was already updated to Fire OS 7.3.2.2 when I received it. I think I used Fire Toolbox v 28.4? maybe 28.6? Whichever was out right around prime day. So the flow was imported on one of those versions. So I went through the custom launcher option in 29.0 yesterday, but it did not seem to make a difference. The home button has also done this since I first imported it. Just thought it was a limitation that I had to deal with. But I decided to look into it again. He only has YouTube, YouTube Kids and Disney+ on the tablet as far as media goes. They all seem to have this issue when watching a video.

He is currently using the tablet, but I can grab the nav bar layout tomorrow and update you.

 
  • Like
Reactions: Datastream33

Datastream33

Senior Member
Sep 17, 2017
2,334
2,039
Thanks for your reply!

I have the Fire HD 8 Kids Pro. Bought it during Prime Day this year. Unfortunately the it was already updated to Fire OS 7.3.2.2 when I received it. I think I used Fire Toolbox v 28.4? maybe 28.6? Whichever was out right around prime day. So the flow was imported on one of those versions. So I went through the custom launcher option in 29.0 yesterday, but it did not seem to make a difference. The home button has also done this since I first imported it. Just thought it was a limitation that I had to deal with. But I decided to look into it again. He only has YouTube, YouTube Kids and Disney+ on the tablet as far as media goes. They all seem to have this issue when watching a video.

He is currently using the tablet, but I can grab the nav bar layout tomorrow and update you.

Thank you so much for the response. I really do appreciate it!

Doing a little digging, it's been discovered that in a large majority of the media apps, It appears that they are consuming (reading the event and responding to it by not performing any action) the keyevents sent by the home key. Because the events are being consumed, Automate isn't picking up the event. Looking into a workaround.
 

Jumbo100

Senior Member
Jul 21, 2022
305
241
Hello, It's been a while since I've interacted with this community. But I just wanted to stay up to date with everything happening.

1. I noticed an ongoing problem with the google play store (from previous threads). For me, I've had my Fire HD 8 plus for a few months now and everything seems fine. Should I be worried?

2. I don't know if this is a normal feature with the fire tablet, but every time I watch or play a video full screen, the brightness goes down.

3. What are the new features of the fire toolbox?

4. I installed the Nova Launcher on my tablet and noticed that there are some glitches. Sometimes it takes a while for it to load (the screen goes black and then refreshes) after pressing the "home button". As far as I know, the "re-routing" function on the toolbox did not work and I found a small workaround for it. There is an app called "Simple Control" that basically gives you a second home button; you could create a shortcut to open the nova launcher and make it act like the new home button. Maybe this is the reason for it acting this way?

A while back, I posted a problem with my fire toolbox. I was not able to open it and a warning popped up. I don't know if this has been fixed but I will check. Hope this helps with anyone.
Some general "catch-up" comments:
- if your Fire Toolbox set up stable and working for you, you're in a good position and you haven't missed much. A lot of the angst you see is from users of the new 12th Gen Fire tablets with FireOS8. Major incompatibility/instability with Google Play Services and related apps. HeartBreak city.
- try turning off "Adaptive brightness" and manually setting screen brightness. Adaptive brightness seems to have a mind of its own sometimes.
- check out @Datastream33 roll out announcement earlier this week (post #10,056) for new Fire Toolbox v29.0. Details some exciting new functions. v29.0 should cleanup some of the nagging interconnect bugs.
- Nothing new on alternative launchers. Custom Launcher "workaround" with Nova unchanged and stilt a little "klugy". New Dark mode in v29.0 may help "disappearing" Home button.

@Datastream33 has always been making frequent "micro" updates, so it's probably good idea to check for FTB updates if you encounter any problems.
 
Last edited:
  • Like
Reactions: blaacksheep

ooonimrodooo

Senior Member
Jan 28, 2011
261
109
Corfu, Ny
Thank you so much for the response. I really do appreciate it!

Doing a little digging, it's been discovered that in a large majority of the media apps, It appears that they are consuming (reading the event and responding to it by not performing any action) the keyevents sent by the home key. Because the events are being consumed, Automate isn't picking up the event. Looking into a workaround.
Wow I can't believe no one has reported this issue. I feel like I am helping this awesome app get even better! If there is anything else I can do to help. let me know!
 
  • Like
Reactions: blaacksheep
Hey guys, today i've got my HD 8+ (2020). Sadly, it has the Fire OS version 7.3.2.3.
So now my questions are:
- Is it no longer possible to disable OTA with this Fire OS version?
- Can i disable ads on lockscreen with this Fire OS version?
- Can i install Google Play Services and Store on this Fire OS version? And does it run without problems on this Fire OS version?
 
  • Like
Reactions: Datastream33

Jumbo100

Senior Member
Jul 21, 2022
305
241
Hey guys, today i've got my HD 8+ (2020). Sadly, it has the Fire OS version 7.3.2.3.
So now my questions are:
- Is it no longer possible to disable OTA with this Fire OS version?
- Can i disable ads on lockscreen with this Fire OS version?
- Can i install Google Play Services and Store on this Fire OS version? And does it run without problems on this Fire OS version?
The Fire HD 8/HD 8+ (2020) are arguably the "sweet spot" of the Fire tablet portfolio, and are prime candidates for Fire Toolbox modifications. The firmware pre-7.3.2.2 has the most flexibility to make changes but the newer f/w will still give you a great experrience.

Specific to your questions:
1. No, you cannot diable OTA updates with Fire OS 7.3.2.3
2. Yes, you will be able to disable Lockscreen Ads; especially easy with new FTB V29.0
3. Yes, you can install the full Google Play Services suite and have full access to the Google Play Store. Problems with GPS currently apply only the new 12th Gen Fire tablets (Fire 7 2022) with Fire OS 8.

Be sure to check out the new features on FTB V 29.0 ... you may be surprised at what you can do.

As always, the caveat to carefully follow the FTB installation protocols will give you a trouble-free experience.
 
Last edited:
  • Like
Reactions: Datastream33
The Fire HD 8/HD 8+ (2020) are arguably the "sweet spot" of the Fire tablet portfolio, and are prime candidates for Fire Toolbox modifications. The firmware pre-7.3.2.2 has the most flexibility to make changes but the newer f/w will still give you a great experrience.

Specific to your questions:
1. No, you cannot diable OTA updates with Fire OS 7.3.2.3
2. Yes, you will be a disable Lockscreen Ads; especially easy with new FTB V29.0
3. Yes, you can install the full Google Play Services suite and have full access to the Google Play Store. Problems with GPS currently apply only the new 12th Gen Fire tablets (Fire 7 2022) with Fire OS 8.

Be sure to check out the new features on FTB V 29.0 ... you may be surprised at what you can do.

As always, the caveat to carefully follow the FTB installation protocols will give you a trouble-free experience.

Thank you very much for your answer.
Do you know or anybody else which domains are used for OTA on the fire tabs?
The same like on fire tv:

d1s31zyz7dcc2d.cloudfront.net
amzdigital-a.akamaihd.net
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com

I would then block the updates in this way.
 
  • Like
Reactions: Datastream33

Jumbo100

Senior Member
Jul 21, 2022
305
241
Thank you very much for your answer.
Do you know or anybody else which domains are used for OTA on the fire tabs?
The same like on fire tv:

d1s31zyz7dcc2d.cloudfront.net
amzdigital-a.akamaihd.net
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com

I would then block the updates in this way.
Current DNS block list per Fire Toolbox protocol provided by @blaacksheep

# Amazon Update Servers

127.0.0.1 localhost
::1 localhost

127.0.0.1 d1s31zyz7dcc2d.cloudfront.net
127.0.0.1 amzdigital-a.akamaihd.net
127.0.0.1 amzdigitaldownloads.edgesuite.net
127.0.0.1 softwareupdates.amazon.com
127.0.0.1 updates.amazon.com
127.0.0.1 arcus-uswest.amazon.com
127.0.0.1 arcus-useast.amazon.com
 
Last edited:

RiCkLaR

Senior Member
Dec 4, 2018
59
37
Current DNS block list per Fire Toolbox protocol provided by @blaacksheep

# Amazon Update Servers

127.0.0.1 localhost
::1 localhost

127.0.0.1 d1s31zyz7dcc2d.cloudfront.net
127.0.0.1 amzdigital-a.akamaihd.net
127.0.0.1 amzdigitaldownloads.edgesuite.net
127.0.0.1 softwareupdates.amazon.com
127.0.0.1 updates.amazon.com
127.0.0.1 arcus-uswest.amazon.com
127.0.0.1 arcus-useast.amazon.com
That "arcus" IP is how Amazon sneaked one update by my blocks, using RethinkDNS app now on my tablets, cause RethinkDNS app has an incredibly nice FIREWALL feature, and I just firewall all the update system apps now.
 
That "arcus" IP is how Amazon sneaked one update by my blocks, using RethinkDNS app now on my tablets, cause RethinkDNS app has an incredibly nice FIREWALL feature, and I just firewall all the update system apps now.
Which "update system apps" do I have to block?

And yes, RethinkDNS is a great app (y)
 
  • Like
Reactions: Datastream33

blaacksheep

Senior Member
Jun 20, 2020
1,435
889
Buffalo
The newer ones didn't work for me for some reason. This was the only one I could find that worked.

Ummm, which newer "ones"? Which file did you use? Do you need a copy as well?

Edit: I see. I looked back in the thread and it seems that you used the file you linked to from uptodown.com. I have working files for any built-in Amazon apps that no longer work, I pulled them from a 7.3.2.3 tablet, if you need them.
 
Last edited:
  • Like
Reactions: Datastream33

blaacksheep

Senior Member
Jun 20, 2020
1,435
889
Buffalo
A little confusion here.

Does the "Amazon for Tablets" APK you downloaded from uptodown.com link work or not work ?

I think he was responding to my response to someone else with the same problem. It just wasn't clear what he was trying to say until I went back and reread the thread. I think he was just saying that the file he found on uptodown worked, where the other ones from apkmirror and the like, did not. I just don't trust uptodown because I don't know how curated the files there are. But then, I realize that when I say that my files were pulled from a 7.3.2.3 tablet, for all anybody knows they could be malicious.

I would encourage anyone who gets update files for the non-working Amazon apps to scan them first. They could probably be verified by their signatures, too.
 

darbNator

Member
Jul 20, 2022
33
22
I think he was responding to my response to someone else with the same problem. It just wasn't clear what he was trying to say until I went back and reread the thread. I think he was just saying that the file he found on uptodown worked, where the other ones from apkmirror and the like, did not. I just don't trust uptodown because I don't know how curated the files there are. But then, I realize that when I say that my files were pulled from a 7.3.2.3 tablet, for all anybody knows they could be malicious.

I would encourage anyone who gets update files for the non-working Amazon apps to scan them first. They could probably be verified by their signatures, too.
Yes I was apprehensive about it as well but saw several people vouching it and that it had a large download base. It is also from an Italian website but the app is in English. Very odd..... but it works.
 

Top Liked Posts

  • 1
    Hi folks, I just got my Fire HD 10 (2021) and luckily it shipped with 7.3.2.1. I noticed it tried to connect to my wifi at the start, even though I unchecked the "Link device" box upon ordering. Sneaky buggers...

    Now I'm just hoping FTB's "OTA updates: disabled" really means that it'll safely stay on 7.3.2.1.

    Anyway major thanks to @Datastream33 for the "new user tour" in FTB. I was afraid I'd have to discover all the options and which ones to use, but the tour runs all the useful changes.

    And also a big thank you to all the helpful people in this thread - @Jumbo100 , @blaacksheep and way too many others! Your posts have helped me make this setup easy as pie. And now I'm going to install some Play Store apps. :D
    1
    Hi guys!
    Just bought the new Fire HD 8 2022, running Fire OS 8.3.1.3. Loving the improved experience over the 2020 version, the quality of the display is miles ahead in terms of color accuracy, despite not being laminated.

    I installed the Google Play services manually using the How to Geek guide, and everything is working really well.

    Only problem is that I cannot make any of the two the custom launcher methods work. This is using Fire Toolbox 30.0. It seems like the button presses are registered because the screen does react at the end of the ADB commands, but my custom launcher (Microsoft Launcher) doesn't open.

    When using the second method, Fire Tool box does install Automate on my tablet, yet there is no flo that can be seen in the application.

    Am I doing anything wrong or does the Fire Toolbox cannot yet implement a custom launcher on Fire OS 8?

    I own both the latest 10 and 8 tablets, and I really love the devices after customizing them. I'd love the launcher to work on the 8 to make my experience near perfect.

    Thanks in advance guys! Thanks to Datastream for the great work!
    1
    You need to uninstall that Google Play version of Shop Amazon and/or Amazon for Tablets. It won't work and will break the app. After uninstalling the Google version, click on the last link in my signature and grab the apk files of any Amazon apps you are using. I pulled the updates from another tablet I have with the newer firmware.

    I tried the Amazon ROM version first - it told me it was no longer supported and opened a browser page.

    I then tried the Google Play version, expecting it not to work (and it doesn't!)

    Thanks, I will try the apk...
  • 11
    Yo, what's going on, guys?

    I hope everyone is having a wonderful Thursday night so far, and everyone is safe and healthy!

    Toolbox V30.0 just dropped, and I gotta say... this one's a good one! So without further ado, let's just jump right into it!

    Restrict Them OTAs!​

    In V30.0 we have a brand-new method to help tackle OTAs. This method works by revoking all "dangerous" permissions such as the Storage permission (as an example), restricting background data usage (meaning they can only use data (to download) when the app is in the foreground), and clears the cache of all OTA Packages. If the method is run, you may notice that it recommends that you factory reset the tablet before running it (this isn't required through). This is recommended because by factory resetting it effectively removes all apps installed by DeviceSoftwareOTA such as the Amazon Freevee app (as an example).

    As reported by @Jumbo100, FireOS 7.3.2.6 was released a few days ago and so far my tablet has remained on FireOS 7.3.2.4. I have no blocking at the router level present, nor a DNS app installed. The tablet was factory resetted and this method was run against it (a few days ago). So far it seems to be holding up, and no apps have been installed by DeviceSoftwareOTA as of this post. It remains to be seen if this experience is the same with this method for everyone else... but I suppose only time will tell!

    Some Fine changes to the Google Services Tool...​

    Firstly, I'd like to discuss the issues with Play Services on FireOS 8. Looking back through the thread, I came across this post by @sfair74 and upon reading the error message the Toolbox provided on a failed install it all makes sense. It looks like a conflicting provider name is causing the installation to fail. Specifically, the install provider for Android Auto. It seems to be crashing with a provider in android.managedprovisioning. I'm guessing it's a policy that's been set to deny the install provider from running. Of course, I could be 100% wrong in this area, but that's what it looks like to me. Planning on picking up a 12th gen for Christmas to look further into it.

    Anyway, with all of that being said, I'd like to use that to segway into the next change brought about in V30.0. Because play services don't install on FireOS 8, it's now possible to have the Toolbox download and install Aurora Store instead. All you have to do is launch the Play Services tool, and execute it. It will then detect your FireOS version and ask you if you want to install Aurora instead of play services. I'm planning on updating this later to include this option for all FireOS versions as well.

    Finally, for this block, let's discuss the last few changes to the Google Services tool. It's been noted that Play Services updates itself automatically in the background, so I've decided to remove the Update Play Services subtool in the Manage tool simply because it's not needed. Lastly, after installation of Play Services is successful, the Toolbox will now present the ability to manage them after install... as intended.


    The Toolbox Updater Has Been Updated?​

    I know right? Could only stand it being broken for so long. Ok, maybe using the term "broken" isn't entirely accurate... anyway, let's jump into the fixes/improvements that were made to the updater. The motivation for this update, finally, fixed the incorrect folder name update pathing issue when a successful update occurs. As you know, when going from one version to the next... the Updater is supposed to automatically rename the Toolbox's root directory to the new version. Well, let's just say that it wasn't working at all and was causing confusion. Due to the generated script's pathing variable being incorrectly defined, it leads to this situation. Anyway, it's now been fixed and should update the folder name as intended.

    Next, I've taken the liberty of completely rewriting the Updater in a way that allows us to now determine what the base version is... making it possible to only show micropatches that apply to that specific base version. Meaning, if a micropatch is put out for V31.0, but the installed version is V30.0 (just as an example) then that micropatch will not show up in the Updater until you've updated to V31.0. This prevents the issue some users were having where files were missing that were supposed to be received in the base update before the micropatch. And overall, the code was refactored and improved as well.


    Notifications, Notifications, Notifications... Oh, You Heard Me the First Time?​

    Awesomely, the Notification Center has been overhauled as well to resolve some of the major issues we had with it. Firstly, notifications are parsed a lot more effectively and takes less processing power doing so. Plus, notifications are now marked as read by actually reading them (instead of closing the Notification Center, and they all get marked as read). This means, notifications are less likely to be missed. Selective broadcasting is also now a thing... notifications can now be sent to selective versions of the Toolbox. So for example, a notification was sent out to versions below 30.0 informing that V30.0 was released, while on V30.0 that message didn't show up. Pretty cool, huh?


    Wait, What Does That Command Do? Introducing Aliases!​

    This is perhaps my favorite out of all the changes in tonight's update. As a long time Linux user (I use Arch btw) I've had my fair share of command line usage... and the biggest thing that's been a treat to do is create and use aliases. If you aren't sure what aliases do, they are effectively short handles for commands... for example, say I'm constantly running the same long command every day: "cd ~/Download;ls;rm -r *;ls" well by using an alias I can instead type (after defining it): "cleardl" and it will run the same command. A lot quicker and more efficient if you ask me.

    Anyway, with that explanation out of the way... I'm excited to announce that ADB Shell now supports aliases! All you need to do is type: "alias -a NAMEOFALIAS=COMMAND" and press ENTER. This will attempt to create that new alias. To view aliases, just use the "alias -v" command, and delete an alias use the "alias -r ALIASNAME" command.

    For example:
    1. alias -a cleardl=cd ~/Download;ls;rm -r *;ls
    2. alias -v
    3. alias -r cleardl

    You can also just execute: "alias", and it will remind you of what switches are supported. Furthermore, unlike Linux's aliases implementation you do not need to close out of your session to use the new alias... it will be available immediately after it's added! In addition, I've taken the liberty of adding a default alias... named "reset navbar" and as expected it resets your navbar layout back to default. I hope you find this new addition useful, and please feel free to play around it with!


    Easier Access to VPN Settings?​

    Hey, @blaacksheep this one's for you my friend! In the Modify System Settings > Networking tab you'll find a new subtool to help launch VPN Settings without having to use Activity Launcher! ;)


    Wait, that's not everything that his update has to offer! Please take a look at the changelog below for more info on what's changed in V30.0:
    V30.0 - Changelog

    [Google Services]
    • Added the option to download and install Aurora Store instead of Play Services on 12th gen tablets.
    • Fixed a crash that would occur when a download fails due to disabled/dead play service links.
    • Fixed Play Services not being manageable after install.
    • Removed "Update Play Services" manage option. Play Services auto-updates itself so this feature isn't needed.

    [keyboard and Input]
    • Fixed a crash that would occur when closing the ADB Input window.

    [ADB Shell]
    • Added the ability to create, view, and delete command aliases.

    [Modify System Settings]
    • It's now possible to re-enable OTA Updates if desired on tablets running FireOS 7.3.2.2 and above.
    • Added the ability to restrict OTA Updates on tablets running FireOS 7.3.2.2 and above.
    • Added the VPN Settings subtool to the Networking tab.

    [Custom Launcher]
    • Added the new Launcher Invoker flo.

    [Toolbox Updater]
    • Fixed incorrect pathing when updating the folder name after an upgrade.
    • Overhauled/cleaned up the download and install logic to be more reliable.
    • Micropatches will now only show up if you're on the patches target base.

    [Notifications]
    • Fixed a crash occuring when checking for notifications fails due to unresolved hosts.
    • Overhauled/improved notification obtainment and display logic.
    Ready to download and install V30.0? Head on over to the Downloads section of the OP and get you a copy of the installer or the portable build! As a side note, the update will NOT appear in the Toolbox Updater, as the Updater itself has received an update. Please manually download and install it via the links in the OP.

    I just wanted to, again, take the time to show my appreciation and gratitude towards this community. I generally don't see all positive interactions on the internet, except in this community! You guys are all lovely people, and the way you all interact pleasantly with one another is something I just find awesome. Thank you all for the massive support you've shown not only to each other... but to me as well. Again, shoutout to the people who've donated recently... I really do appreciate it!

    And again, thank you, @blaacksheep and @Jumbo100 for everything you guys have done for this community. Don't know where we'd be without you guys! Thanks a ton!

    Well, that's all I've got for now. I hope you guys enjoy the update... and until next time guys, peace!
    4
    I was about to release a guide on disabling OTA updates by blocking the servers with RethinkDNS when @Datastream33 released v30 of Toolbox with a new data-restricting method of blocking them. I waited a little bit to see the reaction to it and it seems that it blocks some other things too.

    Without further ado, here's a preliminary guide to setting up RethinkDNS and Activity Launcher to block any DNS lookups for Amazon's update servers.

    -----------------------------------------------------------------------------

    Alright, I've been testing this app for over a month and I haven't gotten any surprise "updates" just waiting for a reboot to install themselves! I haven't been turning off WiFi before rebooting, or taken any precautions to prevent updates other than just this app with the settings given here. I've only checked if there was an update waiting to install before turning my tablet off so I could delete it if I found one. My tablet has stayed on v7.3.2.3, while the most current release is 7.3.2.6. Using DNS66, I got surprised by the update from 7.3.2.2. I started watching for updates and had to delete them several times before I started using RethinkDNS. Using RethinkDNS has worked flawlessly in disabling OTA updates . The only caveate is that you can't run a "real" VPN along with RethinkDNS because it uses the VPN interface of your tablet in order to work. If you must run a VPN, you'll have to put my blocklist into your router's firewall rules so that the VPN interface of your tablet is free to run a VPN.

    Step 1
    Turn off your tablet's WiFi and disable DNS66 or any other VPN you are running.

    Step 2
    Get RethinkDNS from the source and sideload it to your tablet. The current version is v053k. Get Activity Launcher from UpToDown.com and sideload that to your tablet.

    Step 3
    Install RethinkDNS. Install Activity Launcher. (You can combine steps and just stream install them from your computer if you'd like.)

    Step 4
    Launch RethinkDNS. Tap "Apps" in the upper-left. A box will pop up saying "Start DNS and Firewall (default)". Tap "START". Another box will pop up saying "Attention!.....". Tap "Proceed". Another box will pop up saying "Connection request". Tap "OK". The app will start. Now you just need to configure it.

    Step 5
    Tap "Apps" in the upper-left once again. Now a list of installed apps will populate the screen. There are 4 apps you want to block to prevent OTA Updates. Scroll down the list and find each of these apps and tap the blue WiFi and the blue Mobile Data icon next to each of them so they toggle to red.

    They are:
    • DeviceSoftwareOTA - when you block this a box will pop up saying it will also block 3 other apps. Tap "Proceed". It will repeat that warning when you block both the WiFi and Mobile Network options. When you are done, both should change from blue to red and it should say "blocked" under DeviceSoftwareOTA.

    • Forced OTA - Block both WiFi and Mobile Data on this. No popup boxes this time, the inicators just change from blue to red.

    • System Updates (1) - This should already be blocked from the first app. If not, repeat the proceedure and block both WiFi and Mobile Data

    • System Updates (2) - Again, this should be blocked from the first app and if not repeat the blocking proceedure.

    Now to check if you are configured properly, look at the top and tap the "Blocked" heading. Your dispay should now list just those 4 apps and the indicators on the right should all be red. Tap to toggle any that are still blue.


    Step 6
    Now we need to use Activity Launcher to get to the hidden VPN settings of your tablet. Launch Activity Launcher. Let it load (it takes several seconds) and use the search glass in the upper-right. Type in "VPN" (without the quotes). At the bottom of the list under settings you'll see VPN. Tap it. Now find RethinkDNS on the list of installed VPN's and tap the gear at the right. Tap "Always-on VPN" to toggle it on. Tap "Block connections without VPN" to toggle that on. You'll get a warning screen, but acknowledge that and turn it on.

    Edit: This can now also be done in Toolbox by going into Modify System Settings > Networking tab > VPN Settings if you don't want to install Activity Launcher, but Activity Launcher allows you access to other settings that Amazon hides.

    Step 7
    Turn on your WiFi now.

    Congratulations! You're all done. You should be safe from further updates.

    Optional:

    There are other DNS changes that RethinkDNS can make. If you require them relaunch RethinkDNS and tap the DNS tab in upper-right to change DNS settings.

    Your DNS lookups by default will use DoH (DNS over HTTPS). This makes it almost impossible for your DNS lookups to be redirected to a different site than what you typed into your browser. It also makes your DNS lookups unreadable by your ISP so they can't track what you do by your unencrypted DNS lookups (which happen even though your traffic may be encrypted). RethinkDNS also offers Dnscrypt, which is another method of doing the same thing. I believe DoH (the default) is most compatable and left that alone.

    You can also use "filtered" DNS lookups to block offensive sites, block piracy sites, block adult sites, etc.

    You can also use Cloudflare DNS, Google DNS, CleanBrowsing DNS, Quad9 DNS, or a custom DNS. If you know what you want, you can change your DNS settings here.

    If you want to use additional blocklists in your DNS lookups, tap "On-device blocklists". Tap "Disabled" to enable this feature. Let it download the available blocklists. Tap "Configure". Under the "SIMPLE" tab, tap the filters you wish to use. Tap "APPLY".


    You can change any other defaults if you wish. This includes all the settings in the settings menu. I left all these setting alone. I would recommend testing your internet after each change you make. If your internet stops working, go back to the defaults until you've determined that you really want to change that setting. Otherwise all the defaults will work fine for the purpose of blocking updates.

    If needed, I'll post screenshots of the setup procedure.

    NOTE: A reboot may be required after this procedure before you once again get internet access. (Thanks @smirnoff9969 )
    3
    Arrrgh!!! I uninstalled RethinkDNS so that I could write up a guide to setting things up and documenting the whole procedure. Everything was going great, I downloaded a fresh copy on my computer which was a newer version than the one I had been using. I installed and configured it as I was writing my guide. I rebooted the tablet and, lo and behold, I got a message saying that RethinkDNS had been disabled. I tapped it to start it up again, rebooted, and same thing.

    I'd forgotten that I originally used a second app, Activity Launcher, to get to the hidden setting "VpnSettingsActivity", where you can enable "Always On VPN". Then it was working again.

    So I just have to add a few steps to my guide so it's not hard to follow. I'm almost done and it will be posted in a day or so. Bear with me and I think you'll be happy if you want to set this up. Almost there!😌
    3
    Hi, and welcome to XDA!

    Take a look at the links in my signature. I've got updated apps for the Amazon App Store, Prime Video, Kindle, and others. They were pulled from my other tablet with newer firmware (7.3.2.3). Just uninstall any updates you tried to use from the play store or somewhere else, and install what you need over the top of the pre-installed apps.
    Ahh, Thank You So Much! That worked like a charm, this is for my father who is disabled due to a bad stroke. He has a older Fire 10" but the amazon shopping app has no longer been supported and it redirects to a browser. The browser is a cluttered mess and he has very bad eyesight due to the stroke so this was the fix, and I worried I messed it up and would have to return it.
    I also picked up a older Fire 8" off woot to trade in for a 10", been thinking about a 10" tab for myself but dont care for the fire OS. Im pretty impressed with this toolbox, and this will probably tip me over the edge to get one for my self.

    Thanks Again
    3
    By the way, I read somewhere in the instructions that you should deactivate updates for the kindle app in the play store. Why is that?
    In general, it's good practice to disable ALl auto-updates on Google Play Store and only update manually as required ... this avoids any potential "update clash" between AppStore and Play Store app version updates, particularly with the native Amazon apps, like Kindle. Update clash is "fatal" and inconvenient at best.

    Apps installed from AppStore should only be updated by AppStore to avoid trouble.
  • 340


    Fire Toolbox V30.0
    All-In-One Toolbox for Fire Tablets!




    FTBV26.1.PNG

    Introduction.png


    The Fire Toolbox is a collection of useful ADB (Android Debug Bridge) tweaks that can be applied to Amazon's Fire Tablets. The Toolbox project aims to help users fully customize and unlock the full potential of their tablets by putting all the power into their hands.
    The Toolbox doesn't touch the system partition meaning all changes made can be reversed either through the tools/subtools themselves or through a factory reset. This means the Toolbox does NOT void your warranty.

    Compatibility.png


    IMPORTANT INFORMATION REGARDING FIREOS 7.3.2.2+ AND THE TOOLBOX (PLEASE READ)

    If your tablet is running FireOS 7.3.2.2 or above please note that some functions of the Toolbox may not work due to new restrictions in the new firmware. The following tools either do not work or have limited functionality:

    • OTA Updates - OTAs can no longer be disabled.
    • Manage Amazon Apps - Some system apps can no longer be disabled.

    We're looking into workarounds to the issues detailed above. Please keep an eye on the forum for further development.

    Device Name:
    Generation:
    Amazon Fire 7 (2022)
    12​
    Amazon Fire 10/10+ (2021)
    11​
    Amazon Fire 8/8+ (2020)
    10​
    Amazon Fire 10 (2019)
    9​
    Amazon Fire 7 (2019)
    9​
    Amazon Fire 8 (2018)
    8​
    Amazon Fire 10 (2017)
    7​
    Amazon Fire 8 (2017)
    7​
    Amazon Fire 7 (2017)
    7​
    Amazon Fire HD8 (2016)
    6​
    Amazon Fire HD10 (2015)
    5​
    Amazon Fire HD8 (2015)
    5​
    Amazon Fire HD7 (2015)
    5​
    Amazon Fire HD7 (2014)
    4​
    Amazon Fire HD6 (2014)
    4​

    In this forum, you may hear the word "generation" being used when talking about Fire Tablets. Just know that "generation" effectively means the same as "what year was the tablet manufactured?". This may seem confusing and as a result a reference table has been provided for you below.

    screenshot-2020-12-15-174539-jpg.5158661


    GettingStarted.png


    Getting the Toolbox up and running with your tablet is surprisingly a very easy procedure. The only thing required is for you to enable Developer Options and ADB on your tablet. So, without further ado, let's get started.

    At this point, please read the section below, and make sure to follow the correct guide that is made for your tablet on how to set up the device so it works with the Toolbox.

    FIRE HD 7, 8, 10 (2018 - 2022) Guide:
    Before purchasing the tablet:
    • Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)

      if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
    Booting the tablet for the first time:
    • Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
    • When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
    • Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
    • Select ANY network from the list (even if you don't know the password).
    • Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
    • At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
    • It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
    • You should immeditely be thrown into Fire Launcher. You're now ready to enable USB/ADB Debugging.
    Enabling USB Debugging:
    • Turn on your tablet and go to Settings > Device Options > About Fire Tablet and tap on the Serial Number until you unlock Developer Options.
    • Press the back button and find the new Developer Options and toggle it on.
    • Scroll down till you find USB Debugging and enable it.
    Setting up the drivers:
    If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time.
    • Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
    • Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
    • Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
    • Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
    • At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
    • On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
    That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!

    FIRE HD 6, 7, 8, 10 (2014 - 2017) Guide:
    Before purchasing the tablet:
    • Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)

      if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
    Booting the tablet for the first time:
    • Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
    • When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
    • Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
    • Select ANY network from the list (even if you don't know the password).
    • Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
    • At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
    • It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
    • You should immeditely be thrown into Fire Launcher. You're now ready to enable ADB Debugging.
    Enabling ADB Debugging:
    • Turn on your tablet and go to Settings > Device Options and tap on the Serial Number until you unlock Developer Options.
    • Find the new Developer Options and toggle it on.
    • Scroll down till you find ADB Debugging and enable it.
    Setting up the drivers:
    If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time.
    • Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
    • Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
    • Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
    • Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
    • At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
    • On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
    That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!

    ToolsSubtools.png


    • ADB Shell - Spawn a Unix shell that can be used to communicate with the device and execute commands.
    • Custom Launcher - Replace Fire Launcher with a custom launcher.
    • Enable Widget Support - Enable widgets on supported launchers.
    • Custom Sounds - Set custom sounds for notifications, lock/unlock events, low battery, and more!
    • Density Modifier - Change the value of pixels per inch to either decrease or increase resolution.
    • Restore Default Density - Restore the factory default density.
    • Google Assistant - Replace Amazon Alexa with Google Assistant.
    • Google Services - Install Google Services and the Play Store.
    • Google Services (Manage)
    • Add/Remove Google Accounts
    • Clear Data/Cache for Play Services
    • Uninstall Play Services
    • Hybrid Apps - Sideload Amazon Appstore apps without having the Appstore enabled.
    • Keyboard and Input - Manage other input methods and install custom keyboards.
    • Lockscreen Wallpaper - Replace the lockscreen's wallpaper with a custom one.
    • Manage Amazon Apps - Manage the Amazon apps installed on your tablet.
    • Hide/disable Amazon Apps - Hide and Disable Amazon apps through presets or manually select apps.
    • Restore Amazon Apps - Completely restore every Amazon app or manually select apps to restore.
    • Modify System Settings -
    • Power Options - Reboot, shutdown, reboot into recovery, or reboot the tablet into bootloader mode.
    • Parental Controls Hide - Installs a service that auto-dismisses messages from Parental Controls.
    • Privacy Controls - Disable telemetry collection of app usage data, interest based ads, etc.
    • Push and Pull
    • Push - Transfer files from your computer to your tablet.
    • Pull - Retrieve files from your tablet and transfer them to your computer.
    • Remove Lockscreen Ads - Remove ads from the lockscreen.
    • Screen Capturing - Record the device's screen, or capture a screenshot.
    • Sideload Apps - Install APKs from sources outside of the Amazon Appstore.
    • System Backup
    • Backup - Create a backup of the current system configuration.
    • Restore - Restore system configuration from a previously created backup.
    • User Management (8th gen and above)
    • Create a User - Create a new user.
    • Delete a User - Delete a toolbox created user.
    • Switch Users - Switch the current user to a different Toolbox created user.
    • YouTube Clients - Install third-party Youtube clients.

    Downloads.png


    Toolbox:
    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V30.0​
    Post
    Link


    Other Downloads:
    Resource
    Resource Link
    Applicable Tools
    Custom Navigation Bar Icons​
    Navigation Bar Modifier​
    Toolbox Changelogs​
    N/A​

    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V29.0​
    Post
    Link
    V28.9​
    Download​
    Post
    Link
    V27.0​
    Post
    Link
    V26.1​
    Post
    Link
    V25.2​
    Post
    Link​
    V24.0​
    Download​
    Post
    Link
    *Halloween Edition​
    Download​
    Link​
    V23.0​
    Download​
    Post
    Link
    V22.0​
    Download​
    Post
    Link
    V21.0​
    Download​
    Post
    Link
    V20.0​
    Download​
    Post
    Link
    V19.0​
    Download​
    Post
    Link
    V18.0​
    Download​
    Post
    Link
    V17.0​
    Download​
    Post
    Link
    V16.0​
    Post​
    Link
    v15.0​
    Post​
    Link
    V13.0​
    Post​
    Link​
    V12.0​
    Post​
    Link​
    V11.1​
    Post​
    Link​
    V11.0​
    Post​
    Link​
    V10.2​
    Post​
    Link​
    V10.1​
    Post​
    Link​
    V10.0​
    Post​
    Link​
    V9.2​
    Post​
    Link​
    V9.1​
    Post​
    Link
    V9.0​
    Post​
    Link​
    V8.2​
    Post​
    Link
    V8.1​
    Post​
    Link​
    V7.2.1​
    Download​
    Post​
    Link
    V7.1​
    Post​
    Link
    V7.0​
    Post​
    Link
    V6.56​
    Post​
    Link
    V6.55​
    Post​
    Link
    V6.54​
    Download​
    Post​
    Link​
    Donate.png

    If you like my work and would like to support me feel free to Donate. Thank you!
    65
    FAQ.png

    How can I run the Toolbox on Linux?
    The Toolbox is currently being developed for Linux systems in the Python programming language. If you'd like to see the progress of the port, you can do so at this link.
    Please be patient with me as the Linux port is being developed in my spare time and may take some time to complete. However, as the port progresses some builds will be released to those who'd like to help test alpha builds. More information on this later down the line.
    However, at the moment, the best way to run the Toolbox on Linux is to use VMWare and emulate Windows.

    My Home Button isn't working after using the Custom Launcher Tool?
    Due to the way the process works, it alters your navigation bar's home key to send a key event that can be picked up by Automate. Once Automate reads this event, it launches your custom launcher automatically.
    However, if the flow in Automate isn't running, the navbar key will not work, and nothing will happen when it's tapped. To fix this, either open Automate and start the "Launcher Invoker" flow again, or execute the Custom Launcher tool in the Toolbox, click the ":" icon (upper-right) to show the Tool Options panel, and click the "Restore Navigation Bar" button to restore the stock layout.

    Google Family Link won't work on my tablet?
    Unfortuently, no matter how hard we try, we still haven't been able to get Family Link to work correctly on the tablets. The Family Link app fails to install, and the Child account refuses to login. No matter what we tried, we couldn't get a Child account to work on the tablets.
    We believe this has to do with missing dependecies, and the tablets not being certified through Google's Play Protect platform. We're still activly looking into getting the issue resolved. Until then, it's recommended that you use an alternative such as Amazon's FreeTime, Eyezy, or another third-party family managing software.

    How can I remove a Google Account from my tablet?
    Because of the missing accounts section in the Settings app it will be a little more difficult to remove Google Accounts directly from the tablet. The easiest way that I've found is to visit this page: https://myaccount.google.com/security, sign-in to your Google Account, scroll down to "Your Devices" and click the "Manage devices" button. From the list of devices find your tablet and in the upper right-corner click the 3-dot icon and from the list select "Sign out".

    Can the Toolbox be used to root my tablet?
    Primarly, rooting a Fire Tablet requires the user to open the back of the device and short out a certain point on the motherboard. The Toolbox has been designed for folks who'd rather not bark down this alley. It uses the power of ADB to make changes, and is meant to be an alternative to rooting. In summery, the Toolbox isn't designed to root.

    The Toolbox is being marked as a virus?
    This is likely because the Toolbox (and it's installer) aren't signed with a software license. This freaks Windows out because it sees that there is no publisher, and as a result it displays a warning (smartscreen). In addition, some anti-viruses might also flag the Toolbox as a virus simply because the build is relatively new and there is no record of it in the anti-viruses database, resulting in a false positve.
    As always, I take your security and privacy VERY seriously! If you do not feel safe with installing the Toolbox due to virus concerns, I respect and support your decision. It is always up to the user and their judgment! :D
    31
    I'd also like to take the time to acknowledge today as a very special day for this project! Today marks the 3RD YEAR anniversary of the project!!! 😄 🎉🎉

    It seems like only yesterday, that the first version of the Toolbox was released! It's just crazy to think that it all started in 2019, as a very simple batch file program designed solemnly to remove lock screen ads, and has grown into what it is today! If you're interested in what started it all, I'd highly recommend checking out this post. It dives a little more into the Toolbox's background and it's beginnings!

    I just wanted to THANK YOU all from the bottom of my heart for making the last 3 years so memorable! If it wasn't for the amazing support and this wonderful community, the project would've died a long time ago! You guys are the fuel that feeds the Toolbox's development!

    Through this project, I've gotten to meet some wonderful people that I'd consider to be good friends:
    @Davy49, @Tailborn, @Falcon342, @blaacksheep, and of course you (the one reading this)!

    So, where does the Toolbox go from here? Well, I suppose the next step would be to bring the Toolbox to more platforms! Currently, the Toolbox is being ported to other platforms using the Python programming language, and PySimpleGUI. I've also been asked if the Toolbox Python port will ever become open-source, and I think the answer is most likely yes. Big things are planned for the Toolbox this year, and I hope you'll join me on this journey!

    HERE'S TO THE TOOLBOX'S 3RD YEAR ANNIVERSARY!! 👏:D
    28
    Last edited 9-30-2022

    A lot has changed since I first posted this. Toolbox has been updated to v29.0 and now has a new method of replacing the Fire Launcher, DNS66 is only a delaying tactic and doesn't stop updates in all cases, and the Lockscreen Ad removal process in the old FTB v9.2 still works to remove the ads. I leave the post up, but understand that it's just for reference as a starting point for you to explore these things.


    What to do about F/W v. 7.3.2.2

    So your Fire tablet has the latest firmware update on it (v7.3.2.2) and Fire Toolbox won't do what it's supposed to. All is not lost. I've collected some workarounds that will keep Amazon at bay. The three main problems are:

    1) You can't stop Automatic updates.

    2) You can't get rid of the lockscreen ads.

    3) You hate the Amazon Launcher, but Amazon won't let you change it permanently.


    Once those three problems are addressed, you pretty much have your tablet back. The Toolbox will still work for all the other things you want modify. First, get your tablet set up with Toolbox, install Google Services, and install the launcher you want. (Make sure to select "Enable Widget Support".) We'll take care of the Amazon Launcher later. So let's get started with the 3 main problems.

    1) Automatic updates.

    This method is far from perfect and has sometimes allowed updates to somehow slip by. The only other way to do this that I know is to use an app blocking firewall and block the update apps. I chose this method because it doesn't require a 'training period' to train the app on what to block and what to let through. Also, if you've already got lockscreen ads in your tablet's cache, this will not remove them. This method must be in place before you first connect to WiFi for the lockscreen ad blocking to work.

    We need to stop the tablet from contacting Amazon to update it's firmware. We can no longer disable the service that does this, BUT, we can interfere with it's ability to contact the server from which it gets its updates. On a computer, we would modify the hosts file and block the addresses of the update servers. On an Android device, we need root access to do that, but there is an alternate way of adding things to the hosts file - with a VPN. We'll use a free and open source ad blocking VPN app to do this. The app is called DNS66 and it's available through F-Droid. You need to make sure this is always running to be protected from updates. Luckily, android has a feature to assist us in this. It's called "Always On VPN" and we need another app to access the hidden setting for this. We'll use "Activity Launcher" to get to this setting. Activity Launcher is available from Google's Play Store.

    It turns out that using Activity Launcher to change this hidden setting does nothing more than give you an extra notification that your VPN is off. It doesn't stop traffic, so it's useless. Besides, my tablet has taken to turning the "Always On VPN" setting back off every time I boot. (Thanks Amazon!) Activity Launcher is still useful for finding settings that Amazon doesn't see fit to include. It also makes desktop shortcuts to those settings if you wish.

    Download DNS66 to your computer from f-droid.org or from the attached file, copy it to your tablet and install it. Also go to the Play Store and install Activity Launcher. Finally, get the Amzn_Blcklist.txt that's attached to this post and copy that to your tablet. The blocklist file must remain on your tablet, so put it somewhere where it won't get deleted. I suggest in the root of your internal storage. (/storage/emulated/0)

    Open DNS66. There are a couple settings that must be changed. On the Start tab, turn on "Watch Connection". (All 3 switches should now be on.)
    DNS66-start.jpg

    Now go to the Hosts tab. Tap the "+" in the lower-right. Under Title, type "Amazon Blocklist". Tap the paper clip on the next line. Navigate to the Amzn_Blocklist.txt file you downloaded earlier and select it. Now tap "Done" in the upper-right. You should now have the first and last entry on the displayed list selected.
    dns66-hosts.jpg

    Now go to the Apps tab. Turn on "Show System Apps". Tap the gear under the Show System Apps switch and select "No Apps". All the switches below that should now be off.
    dns66-apps.jpg

    You can optionally set your own DNS servers on the next screen if you'd like. I like to turn on Custom DNS Servers, deselect the German ones that are pre-selected, and then turn on the last two servers (CloudFlare).
    dns66-dns.jpg

    This can also be done with Toolbox making this step unnecessary. Now go back to the Start tab. Tap "Start". It will notify you that it wants to connect to a VPN. Tap Yes or OK and allow it.

    Quick note: Do not use the Toolbox DNS changer in Modify System Settings AND the DNS66 Custom DNS setting together. This will cause connectivity to fail. I use DNS66 and not Toolbox's DNS changer. Having the Custom DNS Servers set ins DNS66, and using the Toolbox DNS changer simultaneously caused me hours of grief trying to figure out why Google couldn't connect!

    Now Launch Activity Launcher. Tap the magnifying glass in the upper-right. Enter "VPN". One setting should appear called "VPN". Tap it. Tap the gear on the end of the DNS66 line. Turn on Always-on VPN. Turning on the other switch makes Google Services think you are disconnected, so leave that one off. Step one accomplished.

    actlaunch-vpn.jpg


    Notes:

    DNS66 takes several seconds before it gets started when you first boot, so it is possible that the tablet will make a DNS query for the update server or the lockscreen ad server before it loads. Best practice is to turn off WiFi before you power down or reboot.

    ----------



    2) Lockscreen Ads.


    Toolbox v29.0 now takes care of lockscreen ads!


    It turns out, that blocking those update servers also blocks your tablet from getting any lockscreen
    ads! No further action is needed. I stopped investigating this because I chose to disable the lockscreen completely. If you want to do that, you can do it in Toolbox, or in Activity Launcher that you just installed. Launch Activity Launcher. Tap the magnifying glass. Type in "screenlock". Now tap the last item (.password.ScreenLockSuggestionActivity). Select None and you're done.



    Notes:

    It has come to my attention that when disabling your PIN, it may still ask you for a PIN by Parental Controls for some settings or activities. I would suggest if you're going to disable your PIN, to first set it to something simple like 0000, reboot it, and then disable the PIN. That way you'll know what PIN you set if it suddenly asks you next month for your PIN.

    Another way to disable lockscreen ads is detailed Here.

    ----------



    3) Amazon Launcher.


    New: Toolbox v29 has remediated most of the difficulties in replacing the launcher. Always check that you have the latest version of Toolbox. I'll leave the rest of the post up to inspire ideas.


    The latest version of Toolbox (v 28.1) has a new tool called 'Custom Navbar Key'. This method uses Automate to automatically replace the Home button every time you reboot. It works rather nicely. I leave this section posted for completeness and to facilitate experimentation on other choices.

    The way we're going to get rid of the Amazon Launcher is by not calling it! We're going to replace the Home button with another button that we can map to any launcher we'd like. This isn't a perfect solution, but it is FREE. If you're willing to spend a couple bucks, you can purchase a more configurable gesture navigation app with more features, but this is FREE, so maybe you can accept it's shortcomings. I'll keep this post updated with other navbar replacements that people suggest.

    Go to the Play Store. Get and install "One Button Navigation". Launch it. It will want you to turn on Accessability Service for it. Follow the on-screen instructions and turn on "One Button Navigation Bar". You'll see your new nav button at the bottom of the screen. I like to adjust the width down to a dot, like the button it's replacing, but that's up to you. I also like to make the background black and the botton bright yellow so that I'm reminded it's running. Set up the background and button colors as you like them. Yeah, I know the ads in this are obtrusive, but you'll never see them once it's set up. Also DNS66 will block the ads if you install that first.
    obn-set.jpg

    Next tap the Action tab. Tap "Single Click". Scroll down and select "Launch Application...". Select the launcher that you installed with Toolbox here. In my case, it was Nova 7. (Google updated the Nova version that Toolbox installed.) Now you can set any other actions you'd like for the new button.
    obn-act.jpg

    I didn't want anything additional, so I made the gestures similar to the original buttons. This is all up to you. You can reverse them or set additional functionality to the button. I ended up with a new navbar that covers the original navbar (the one with the home button that brings up the Amazon Launcher). I now have a button that when pressed, takes me to my launcher. When I swipe it left, it goes back a screen. When I swipe it right, it shows the recents. I spent a lot of time with other navbar replacements and this is the minimalist replacement that works best for me. YMMV. Before someone complains that it doesn't work in landscape mode, I'm not the developer. You should rate it and leave a comment for him! This is the best I could find that does what I want for FREE.

    ----------



    I'll edit this post with your suggestions for better solutions to these problems and keep a list of navbar replacements that people suggest at the end so you can find what works best for you.


    ----------------------------------------------------------
    Some Suggested Navigation Bar replacements:
    ----------------------------------------------------------

    One Button Navigation Bar by Nu-Kob (PlayStore)

    Pie Control by coolAce (PlayStore)

    Simple Control by coolAce (PlayStore)



    DNS66 is available from F-Droid.org (dated March 26, 2021)
    Activity Launcher is available from APKMirror.com (dated March 21,2022)
    21
    What's going on, guys?

    I sincerely hope everyone is doing good, and having a wonderful December so far!

    Today marks the release of V26.0 of the Toolbox! So, without further ado... let's take a look at what this release has to offer!

    Welcome, Welcome, Welcome... Screen!​

    You know, every time I run a build for the first time I go through the Theme Selector, then the Tour, and then the Welcome Screen. I just think to myself "this is just a mess" - so in this update I thought I'd focus on improving it and making it better. I started by re-designing the Welcome Screen and doing my best to link all three tools into something that looked visually appealing. Now, in a tabbed interface you'll find the Setup Tour in the very first tab, Theme Selection (with a new UI) in the second, Installation Management in the third, and finally in the fourth the Changelog.

    Now let's talk specifically about the Installation Management tool. This bad boy now has the ability to read installations from directories other than the default (localappdata\Datastream). So, if you've got your installations in a custom location, and you'd like to manage them, it's now possible to point the path to that location. This should help make managing installations a lot easier!

    Custom Launchers on FireOS 7.3.2.2​

    As some of you may know, I bit the bullet and updated my tablet to the latest version of FireOS... to the dreaded 7.3.2.2. This update, from what I heard, caused the Custom Launcher and disabling OTAs tools to no longer function and after updating, I soon discovered that it was indeed the case. I then tried everything I could think and well really didn't turn up any valuable workarounds... until I tried the method we'd been using on older gen devices... and it worked! Of course, just like on the older gens, it has the drawback of being removed every time the device is rebooted. However, it's the only method I could find, so it's better than nothing, right?

    Anyway, while coding it in I decided to take the liberty of also clean up the code, and the UI a bit. What's cool is the tool will now read what generation your tablet is, and display what methods are available to use. You'll also find that the initial method selection UI is a lot more usable compared to its previous iteration.

    Change the Timeout for the Display?​

    Ah, the latest addition to the General group in the Modify System Settings tool. This subtool not only allows you to alter the timeout to traditional values, but also allows you to set a custom timeout. Want your screen to sleep after 24 hours of inactivity? This one's for you folks who want to extend the timeout as much as you can. Just be careful, it may cause a burn-in if your tablet's screen remains on the same screen for too long!

    Let's Talk Linux Port Stuff​

    I guess the point of this section is to ask you guys if you're ok with updates to the VB version being slowed down, so I can focus more on the port? I'd also like to address a common question I get asked about it being open-source. Right now, I'm planning on it being closed-source for now. However, I am planning on making it open-source when I feel like the time is right. Please be patient! So, let's get back to the original question... are you guy's ok if I shift primary focus to the port?


    Wait, that's not everything! If you're interested in everything that's changed... please take a look at the changelog below:
    Version 26.0 - Changelog

    [Welcome Screen]
    • Updated the user interface.
    • Added better installation detection to the Installation Management subtool.
    • You can now specify what directory the Installation Management subtool will scan to detect installations.
    • Improved the look of the Theme Selector.
    • Fixed a bug causing the Startup Tour to not load tools correctly.
    [Device Information]
    • Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
    [Theme Selector]
    • Moved the Theme Selector to the Welcome Screen.
    [Custom Launcher]
    • Improved the UI.
    • Made significant improvements to the code, and fixed various bugs/issues.
    • Added Re-route Homekey option for tablets running FireOS 7.3.2.2+.
    [Modify System Settings]
    • Added the ability to change the "Display Timeout" to the General tab.
    • You can now set a custom Display Timeout of up to 24 hours.
    [Lockscreen Management]
    • Improved the warning regarding the Pattern security type.
    [Hybrid Apps]
    • Updated Disney+, and Netflix to the latest versions.
    [Manage Amazon Apps]
    • When restoring from a debloat list, it now displays the proper header and message.

    Ready to download V26.0? Head on over to the Download's section of the OP. By the way, because of some directory changes to the bin folder... the update will not show up in the Updater. It must be installed via the Installer or extracted from the Portable release.

    Ok, my favorite part about of these release posts... sharing appreciation for you awesome folks! I just wanted to say I'm so blessed to be a part of the wonderful community over here on XDA. You guys are incredible people and in fact... this is perhaps the one place I've been on that I don't see negativity or people bullying one another. You guys are just AMAZING and I wanted to let you know that I appreciate everyone's support! Furthermore, you guys are what keep this project going, and it wouldn't be where it is today without you guys! So please pat yourself on the back - you deserve it!

    Also, I'd like to place the limelight on my good friends @blaacksheep, and of course @Falcon342. I just can't express how much I appreciate all you've done for this thread! I haven't had the time to get on here because of work and when I come on the forum I see you guys helping out and answering questions. I really do appreciate the time and effort you two have put into being so freaking helpful! However, I've got to be honest, I'm extremely sad because I feel like I'm not doing enough. I'm sure you guys would like a little help (I'm gonna try harder to be more active on here when I can to hopefully help you guys out). Anyway, thank you guys again!! I really do appreciate it!!!!

    Also, don't think I forgot about you donators! I just want to say I'm so honored that you'd donate your hard-earned cash. Sometimes I feel like I don't deserve it. Guys and gals, THANK YOU so much for donating! I really do appreciate every penny! :D

    This year has flown by and Christmas is right around the corner, so I just wanted to say MERRY CHRISTMAS and I hope you all had a remarkable 2021! Let's hope 2022 is an even better year! 🙏

    Well, that's all I've got for now! Have a good one, guys, and until next time... Peace! ✌️