[WINDOWS/LINUX][TOOL]Fire Toolbox V34.0

Search This thread

c-f-g

Member
Jan 20, 2013
39
1
Some things to check/try:

  • As suggested earlier, check your cable or try another cable.
  • Verify that USB debugging is enabled on your tablet.
  • Set your USB connection to File Transfer in Settings > Connected Devices > USB.
  • Check your computer under Device Manager to make sure there isn't a driver issue. The device should show up under Fire Devices > Android USB Interface with no exclamation points.
If that all checks out -
  • disconnect your tablet
  • go to Developer Options
  • toggle off/on USB debugging
  • Tap Revoke USB debugging authorizations
  • Make sure your tablet's screen is on
  • Plug the tablet back in to your computer and launch Toolbox.
  • Your tablet should now show the option to Allow the connection
  • Make sure the box to always accept is checked and accept the connection.

I've had issues in the past with ADB connections. I hope this helps. It really sounds like your cable or connector, though.
Thanks for your input.

The cable is working, at least another non-amazon-device is getting detected by windows.
USB debugging is enabled.
If I switch to this page, all radio buttons are greyed out.

androidDialog.jpg

I don't have a Fire Devices in my Device Manager.
deviceManager.jpg

I use Windows 10, so normally it should handle the driver issue for me (and it did so a year ago when I first used fire toolbox; so normally the driver should still be there?)

Please advice me how to fix this.

€dit: I installed the drivers manually, but that doesn't change anything.
 
Last edited:

Kryga-i9506

Member
Jun 13, 2020
32
19
Any chance of having a linux version or a mono compatible one?
FAQ says

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.
 

Darkzoner

New member
Jan 9, 2022
1
0
First of all, thank you Datastream33! It was really easy to do! A mini tutorial, a wizard with explanations so you know what you are about to do, most things worked great at first try. Great work :)!

Like some people above I had problems installing the Google services too.
I had error messages with "Bad user number" (can provide details) and all installations of google services failed. Then i tried installing without calender and contact sync and it worked. Funny thing, afterwards i was able to install all services (again) with contact sync and after that all services (again) with calender sync.
May be worth a try, if you haven't tested that. I have a Fire HD 10 (2021) with firmware version 7.3.2.1 and used Fire Toolbox 26.1, so your experience may differ.

After i went through the Fire Toolbox Setup wizard and had done most of the suggested things, i wanted to control if firmware updates are disabled on the device, but i wasn't able to (Toolbox says disabled).

Question:
Clicking on "System Updates" (Settings > Device Options > System Updates) drops me back to the "Settings" page. Is this normal/known? Is there a way to resolve that?
 

kieferschild

New member
Jan 20, 2010
3
1
How does one keep their Fire tablet up to date with OS updates?

Also, does anyone know if it's possible to get a native VPN client on this tablet or know of a reliable one for L2TP?
 

blaacksheep

Senior Member
Jun 20, 2020
2,129
1,386
Buffalo
Thanks for your input.

The cable is working, at least another non-amazon-device is getting detected by windows.
USB debugging is enabled.
If I switch to this page, all radio buttons are greyed out.

View attachment 5504019

I don't have a Fire Devices in my Device Manager.
View attachment 5504017

I use Windows 10, so normally it should handle the driver issue for me (and it did so a year ago when I first used fire toolbox; so normally the driver should still be there?)

Please advice me how to fix this.

€dit: I installed the drivers manually, but that doesn't change anything.

Okay, I don't speak German so I don't recognize all the items in your device manager screengrab, but it doesn't look like your tablet is there. It is possible that it is there, listed as another device with a different driver loaded, but probably not.

That leaves us with a connection problem. Since you say that your cable works with another non-amazon device, have you tried reversing the plug on the tablet? It's possible that one side of the plug works while the other does not.

Maybe another port on your computer would work.

Then there's the possibility that the connector on your tablet is bad or malfunctioning. I can't help with that other than to suggest trying to swap hardware with another Amazon tablet. You could get a 'parts' tablet from ebay to try this. Can you transfer files to the tablet with File Manager on your computer? Does your tablet show up as a portable device in File Manager? (You'll need to have the tablet connection set to File Transfer on the tablet.) If so, it should work and it's a driver problem and I'm at a loss for more ideas at the moment.
 
Last edited:

brianblank

New member
Nov 23, 2011
3
1
I'm new to Fire Toolbox, I searched for solutions but didn't find anything.

I ran the toolbox on my HD 8 Plus a few months ago with no issues. I ran it on my partner's HD 10 this week, it went smoothly except for one thing. I can't register the device in order to use the Amazon apps, specifically Goodreads. When I launch Goodreads or the Amazon App Store I get a "Device Not Registered" error, when I tap register either the app closes or it just spins and spins and nothing happens.

Details of her HD 10:
Device: Amazon Fire HD 10 (2021)
Codename: trona
FireOS Version: 7.3.1.9
Android Version: 9.0
Security Patch: 2018-10-05

Any suggestions would be greatly appreciated
 

Attachments

  • PXL_20220110_194445062.jpg
    PXL_20220110_194445062.jpg
    402.1 KB · Views: 67

itimi

New member
Dec 26, 2021
2
0
Hey Guys, awesome tool and great community over here 👌

I have a new Fire HD 10 (11th Gen) with luckily OS 7.3.2.1, so the Toolbox worked like a charm (so I think).
I have my "main" user configured and all good, but whenever I create a second user via the toolbox, this user disappears after reboot, happened multiple times now 🙈
And when I create a Kids user, this one stays, but apps won´t work after reboot (Audible for example, runs fine the first time, but after reboot it´s just loading into a black screen and soon after back to homescreen).

Is there anyone with similar trouble or any idea what I´m doing wrong?
Cheers Tim
 

mckay1988

Member
Jan 14, 2013
45
9
hi
im waiting today my fire 10 hd tablet but at the order, i forgot to disable account linking. Is there a way to disable this before i turn off the device? i dont want to update the OTA update. And if i can, can i disable the updates then? please answer fast :)
 

itimi

New member
Dec 26, 2021
2
0
If your not signed into the device with your Amazon account then all users execpt the main user disappear when you reboot,
Unless you find a workaround (like you did) to keep the user, but a Kids user is much more restricted so apps not working after reboot isnt very surprising.
Ah ok, so I have to have a second Amazon Account for the second user for it to be persistent?
 

frosty68

Senior Member
Jul 23, 2011
242
32
I can install apps from the Google store but the ones I've paid for (specifically driving theory test) don't open, any solution?
 

mckay1988

Member
Jan 14, 2013
45
9
is anyone have problems with night mode?
i turned it on in developer settings but the quick settings menu stays white. any solutions?
 

ktklein72

Senior Member
Jul 8, 2011
214
21
So. Jersey / Philly
Im sorry if this has been asked but I just can't find the answer. Is there a way to permanently set Nova Launcher as the default launcher with the 11th Gen Fire HD 10? I ran the toolbox, installed Google services and got rid of adds on the lock screen but just cannot get Nova to fully work. Thanks in advance.
 

ktklein72

Senior Member
Jul 8, 2011
214
21
So. Jersey / Philly
Try running this command in the "ADB Shell" tool:

Code:
pm disable-user --user 0 com.amazon.firelauncher

If you get a error that its a protected package then your on FireOS 7.3.2.2 and need to use the "Re-route Homekey" method provided by the "Custom Launcher" tool.
yes, definitely on 7.3.2.2

the re-route home key does work however after each reboot it is gone and has to be re-done again. kinda annoying. at least I mostly got rid of the lock screen ads (using the Automate app (i say mostly because after each reboot I need to re-run the services to get the ads to stop again (but no cable to pc connection is required at least).

hopefully a new "fix" can be devised so Nova can be made the permanent launcher

keeping my fingers crossed 🤞
 

Tylz

New member
Jan 13, 2022
1
0
Good afternoon,

I was attempting to setup multiple accounts but it seems i can't have the nova launcher on both profiles? Or maybe i'm just doing it all wrong to begin with.
 

Top Liked Posts

  • 2
    @blaacksheep, I'm using Nova Launcher Prime 7.0.58 but my FireOS v7.3.2.9 (there is nothing I can do - replacement device came with that version).

    Thanks for the advice: after "playing" with WeaWow I've finally added widget to my home (making everything very same on both my Fire HD 10)

    But here is another issue: Google Chrome browser option to add page to the home screen is missing :( I do have a few home-brew smart home gadgets with built-in web pages for control & configuration (on screenshot "X10" & "Smart blind remote") but can't add 'em :( Do you know how to fix?
    2
    @blaacksheep, I'm using Nova Launcher Prime 7.0.58 but my FireOS v7.3.2.9 (there is nothing I can do - replacement device came with that version).

    Thanks for the advice: after "playing" with WeaWow I've finally added widget to my home (making everything very same on both my Fire HD 10)

    But here is another issue: Google Chrome browser option to add page to the home screen is missing :( I do have a few home-brew smart home gadgets with built-in web pages for control & configuration (on screenshot "X10" & "Smart blind remote") but can't add 'em :( Do you know how to fix?
    FireOS with Fire Launcher do not natively support shortcuts or widgets.

    But some third -party launchers (like Nova Launcher) can support widgets , but still not shortcuts.

    You're successfully using widgets now with Nova Launcher.

    To workaround shortcut deficiency, try using a shortcut/widget maker app to generate a "pseudo-widget" from a webpage address ... basically a shortcut "re-skinned" as a widget.
    2
    FireOS with Fire Launcher do not natively support shortcuts or widgets.
    But some third -party launchers (like Nova Launcher) can support widgets , but still not shortcuts.
    A year ago everything worked perfectly, as on "native" Android, and I'm still able to create webpage shortcuts on home screen from Google Chrome on my another Fire HD 10 (11th gen but about 3 yo, of course hacked by FTB).
    BTW, thanks for advice! Will use this workaround if I can't find a proper solution for the damn Chrome.
    2
    A year ago everything worked perfectly, as on "native" Android, and I'm still able to create webpage shortcuts on home screen from Google Chrome on my another Fire HD 10 (11th gen but about 3 yo, of course hacked by FTB).
    BTW, thanks for advice! Will use this workaround if I can't find a proper solution for the damn Chrome.
    Yeah, widget support is just lacking in FireOS. It may have worked on older firmware versions, but Amazon continues to block things that don't support your tablet as an Amazon shopping device!

    Your only option is to do what Jumbo100 said and try a shortcut/widget maker app to create what you need. Hopefully, you are successful. (y)
    2
    A year ago everything worked perfectly, as on "native" Android, and I'm still able to create webpage shortcuts on home screen from Google Chrome on my another Fire HD 10 (11th gen but about 3 yo, of course hacked by FTB).
    BTW, thanks for advice! Will use this workaround if I can't find a proper solution for the damn Chrome.
    One of of the FireOS shortcomings subsequent to f/w 7.3.2.2. None of the usual web browsers used on Nova Launcher can create shortcuts to Fire tablet homepages with recent f/w. Not really a specific Chrome browser problem per se.

    Shortcut Maker for Android (by dev Rushikesh Kamewar) has been vetted by the Community as a workable solution, but there may be other viable apps.
  • 3
    What's going on, guys?

    Long time no see!

    I know this is out of the blue, but I'm extremely excited to announce that Fire Toolbox V34.0 has just been released. There's some good changes in here, so let's not delay any further and get into the nitty gritty of today's update.

    Let's Rethink the Blocking of OTA Updates​

    OK, I’ll be the first to admit that the current restriction workaround of setting the Wi-Fi networks as metered isn’t ideal for a large majority of cases. It not only prevents HD streaming in some apps, but can slow down downloads and uploads. So, it would be ideal if we had a different approach, one that just works for our case? Well luckily for us, @blaacksheep has us covered as usual. In today’s update, I’m excited to announce that the Toolbox is now capable of installing and configuring Rethink Dns for tablets running on a restricted firmware! Huge shoutout to @blaacksheep’s guide, It was a very valuable resource in getting this thing setup!

    Unlike the metered method, Rethink allows us to block connections to Amazon’s servers, without sacrificing networks speeds. But because Rethink is always running in the background it will consume some RAM which can impact performance on tablets with a lower RAM capacity. Despite this, it’s still worth a try if you’re experiencing issues with the metered method.

    The method works by installing Rethink, setting it as an "always on VPN", and then restoring a settings backup that contains the neccessary rules for blacklisting connections to Amazon's OTA updates servers, and preventing network access for the OTA Update system packages.

    If you’re interested in trying this method, all you need to do is launch the Modify System Settings tool, and click the toggle next to OTA Updates (you will have to revert the Metered method before the Rethink method can be used), and select Rethink from the new method selection window!

    ModifySystem_BlockOTAMethods.PNG



    Switching It Up With Languages​

    For tablets running FireOS 7.3.2.0+ now have the option to change the device's language, even using languages not listed in Amazon's language selection in the Device Setup app! However, there's always a downside, and in this case the downside is that because Amazon didn't get around to fully translating the OS for different languages only some parts of the OS have been translated. From what I could gather, the Settings app is where it's mostly noticeable. Some headers and descriptions may appear in the selected langauge, while some may still appear in English.

    And while we're on the subject of languages, as far as I could tell, there's no way of adding additional languages to the tablets without root access. So I'm afraid there isn't much we can do about the partial support, or adding additional languages that aren't already supported.

    ModifySystem_LangLocale.png



    Restoring What Matters the Most From System Backups​

    So this next feature is something I think has been needed for some time now. When restoring a backup, it's now possible to select what elements from your backup you actually want to restore. So, if you have backup with the Internal Storage, package states, and user apps, but you just want to restore the package states, you can now tell the Toolbox that's what you want and instead of it restoring the entire backup all at once you can now restore just the package states. Pretty freaking cool aye? The list view has also been updated so the backups will now appear from top to bottom instead of from left to right.

    SystemBackup_RestoreSelected.PNG



    A new Google Assistant​

    When it comes to downloading, this tool and the Google Services tool were the hardest ones to account for. The Google app itself (depending upon which version of Android your tablet runs) is a fairly large APK (120MB+), and after APKMirror shut down access to direct download links we had a fairly hard time hosting the APKs ourselves so we figured since we already had Play Services installed, we'd just rely on the Play Store to download/install the Play Store for us. Of course I didn't think of the possibility of the Play Store blocking access to the Google app due to an unsupported device. Luckily, we just discovered that another popular APK website (trusted) allows direct downloads, so the Google app is now downloaded from there, solving the whole issues with the Play Store.

    Also, the process of fully activating Google Assistant has changed with time, so I took the liberty of adding an instructional video/text tutorial that goes over the onboarding process. And for some reason the Gassist APK has been missing from previous Toolbox builds, so that has also been restored.


    Hiding Those Pesky Unsupported Settings​

    As Android continues to evolve, new features are constantly added and some features are sometimes removed. In past versions of the Toolbox, some features could be found that would have no impact on different versions of Android and would often cause confusion due to their inclusion. For me this was something I've been meaning to tackle for some time now. Not everything has been accounted for just yet, but I think it's a good start. So, here's just a few of the subtools that have been hidden for specific Android versions:

    [Custom Launcher]
    • To avoid confusion, the Launcher Activation methods that aren’t compatible with the tablet’s firmware are now hidden.

    [SystemUI Modifier]
    • Due to Google removing the ability to modify the navigation bar through the settings database, the Navigation Bar Modifier will now be hidden for tablets running FireOS 8+.

    [Modify System Settings]
    • The Do Not Disturb (Voluem Panel), and Power Notifications options should only be shown on tablets running FireOS 6.
    • The Night Mode (Dark Theme), and Gesture Navigation options should only be shown on tablets running FireOS 8+.
    • The Language Locale option should only be shown on tablets running FireOS 7+.
    • Gesture Navigation will only be shown on tablets running FireOS 8+.

    A New Way of Navigation on FireOS 8​

    Thanks to @dbdude58 for discovering an easy way to activate Gesture Navigation, it's now possible to toggle on/off gesture navigation in the Modify System Settings tool (SystemUI tab)! While it does survive a reboot, there can be some cases of the navbar glitching out, and sometimes weird behavior can occur (at least in my testing). But, it's a breath of fresh air to use on FireOS nonethless.

    What's Changed Exactly?​

    Interested in everything that's been changed in today's update? Here's the changelog:
    Version 34.0 - Changelog

    [Google Services (Manual)]
    • Calendar and Contact android providers are now enabled during install.
    • Fixed crash occurring when closing the window.

    [Google Services]
    • Calendar and Contact android providers are now enabled during install.

    [Custom Launcher]
    • Launcher Activation Methods that aren't compatible with the tablet's firmware are now hidden.

    [Networking]
    • Added warning message when Rentry.co can't be reached.

    [ADB Input]
    • Fixed crash occuring on window close.

    [Google Assistant]
    • The Google app is now downloaded from a separate source instead of installing via the Play Store.
    • Instructions on how to properly setup Google Assistant has been added.
    • Restored the missing GAssist APk.

    [Lockscreen Management]
    • Fixed crash occuring on window close.

    [Manage Amazon Apps (Automatic)]
    • Removed "Device Setup" from Standard Debloat/Restore presets.

    [Manage Amazon Apps (Manual - Simple)]
    • Updated the description, and changed app color to red for the "Device Setup" app.

    [Manage Amazon Apps (Manual - Advanced)]
    • Fixed crash occurring when clicking the App Info button for User Apps.
    • Fixed crash occurring when an app's icon is in .xml format (the tool will not read/display icons in .xml).

    [Modify System Settings]
    • Added the option to block OTAs using RethinkDNS on restricted firmwares.
    • Settings not supported by the tablet's firmware are now hidden.
    • Added the option to change the language locale to the SystemUI tab.
    • Added the option to toggle on/off Gesture Navigation for tablets running FireOS 8+.

    [Device Information]
    • Added a search function for the buildprop.

    [Hybrid Apps]
    • If a hybrid app fails to download, the install process is skipped and the corrupted file is deleted.
    • Fixed the update function not working as expected.

    [Settings Database Modifier]
    • Fixed an issue preventing keys from being deleted.

    [System Backup]
    • When restoring a backup, you can now select which elements you'd like to restore.
    • Backups are now displayed from top to bottom, instead of left to right.

    [SystemUI Modifier]
    • Added "Alexa Hands-Free", "Smart Home", "Work", and "Data Saver" toggle options to the Quick Settings Modifier.
    • The Navigation Bar Modifier is now hiden for devices running FireOS 8+ as a result of the ability to modify the navigation bar being removed from Android.

    Scam Sites and Ensuring Your Download is Legit​

    It has come to my attention that there are some scam sites out there claiming to be the "official" website for Fire Toolbox. Please do NOT download anything from these sites! They could distributing malware, or bundling it with the Toolbox. I do NOT run any other websites (besides the two wordpress websites - Datastream33, aftb), and I do NOT post Toolbox updates or builds anywhere else except right here on XDA. Once you've downloaded either the Installer or Portable build, I'd strongly suggest checking the SHA256 checksum and ensuring the file's checksum matches the checksum posted here before installing.

    If you're comfortable with the command line you can use CertUtil (certutil -hashfile filepath SHA256) or Powershell (Get-FileHash filepath), or if you prefer a GUI you can try my new Sha256Checker tool.


    Downloads​

    NameInstaller (.exe)Portable (.zip)
    Fire Toolbox V34.0Download


    SHA256 Hashes​

    FilenameSHA256 Hash
    FTB_V34.0_Installer.exedf19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc
    FTB_V34.0_Portable.zipf47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f

    Thank You, Thank You, Thank you!​

    Hey guys, I know I haven't shown my face in here for some time... but I just wanted to let you all know that I have been keeping tabs on the thread. I just wanted to once again thank you all from the bottom of my heart for being so caring, and kind towards each other. I've been in and out of some communities and let's just say, there are some VERY vicious people out there. So thank you all for being so kind and respectful.

    As always, I need to give a GIANT shoutout to my good friends, @blaacksheep and @Jumbo100! I want to thank you guys so much for your dedication, support, and wonderful guides! I have no idea what we would do without you! It's been a long ride, and I'm glad we get to share it with you fine gentlemen. Thank you for everything you've done! :D

    Another huge shoutout goes to the fine folks who've sent some of their hard earned money towards the coffee fund. THANK YOU all so much! I really do appreciate it!

    Oh, before I forget... my Linux enjoyers... we've got something cooking that I think you'll enjoy. Stay tuned! ;)

    Well, that’s all I got for now, stay safe everyone, and hope you all have a fantastic rest of your day/night! Until next time, peace!
    3
    I used the Toolbox for the first time yesterday and installed the Aurora Store and remove screenlock. IIRC, I had to choose between signing in with my Google account or as Anonymous. I chose Anonymous. Now I find that my File Manager app (which I use to send books to the Fire using FTP) will only start FTP File Sharing if 'Anonymous' is ticked. If I untick it then there is no option to 'Start' the FTP.
    As far as I can tell the Fire does not have a User called Anonymous. What do I need to do to keep the Aurora Store and get my FTP sharing back to being password-free? Thanks.

    Your File Management app set up as an Anonymous FPT client as default.

    If you don't want Anonymous mode by default, reconfigure app as a regular Google/Android FTP client.
    3
    Welp, an unexpected gift for those running a FireOS 8.3.2.2 on a Max 11 or HD10; not certain about other devices rocking FireOS 8. Google Voice typing is working again! I'm dictating this post on a Max 11.

    Not sure when that got enabled; thought I had checked after fire OS 8.3.2.2 came out but perhaps not.

    Happy yapping!
    3
    Any help guys?Please.
    Greetings

    Failed to mention this in the method description - if the custom launcher can't be seen on the first few rows (the rows of apps present when Fire Launcher is started) and is further down the list then Automate won't start the launcher (tap on it) as it's waiting for the element to "appear" on screen. Try testing this theory out by swiping down on Fire Launcher and see if Automate starts the custom launcher once it appears on screen.
    3
    Hello I have used V33.1 and I have a few problems, I have a fire kindle 8 2020 and I can’t disable fire launcher, (I am using Microsoft launcher BTW) also I am trying to restore a backup (made on fire toolbox) to my kindle 7 2019 but I can’t seem to find the backup I made on my kindle 8 to restore it on my kindle 7 plz can you help me.

    (If my problems are fixed in the latest version,I can use it as I’m on holiday and I don’t have any Wi-Fi)
    FTB is not designed as a full system backup utility; it basically just backs up the device "configuration state" . A full system backup requires system root access , which isn't available on newer Fire tablets.
    Backups can be restored to a different device IF it's the same model and firmware version. (I.E. you have 2 Fire HD 8's that are both the same.) If you try to restore to a different model or year, you'll have to keep your fingers crossed. It might work, but don't rely on it.
    I don't necessarily see a problem with restoring the 2020 backup onto a 2019 model (they both run Android 9). However, I would HIGHLY advise against restoring the 2020's settings database onto the 2019 as there are some keys in some of the tables that could result in a soft brick if changed. But, if you're just trying to copy the apps from the 2020 to the 2019 then I say go for it. Just make sure to create a backup on your 2020 with ONLY the user apps option selected (make sure to name it something simple like "UserApps_Backup" for easy identification later), then restore that newly created backup onto the 2019 tablet. Here's how:

    Launch the Toolbox, click the gear icon at the upper-right to open the settings, click the "About" tab in the Settings window, then click "Open Installation Directory".

    This will open the Toolbox's root directory in File Explorer. Now click the "bin" folder, then "System Backups". In the "System Backups" folder, create a new folder, and name it "Amazon Fire HD 7 (2019)" (without the quotes). Now double click the "Amazon Fire HD 8 (2020)" folder, and copy the backup file you want to restore onto your 2019 tablet (the UserApps_Backup.7z file from earlier). Paste that backup file into the "Amazon Fire HD 7 (2019)" folder. Now the backup should show up in the Toolbox for restore.

    Please note that I don't recommend restoring backups on different Android versions. But because both your tablets run Android 9 you should ok as long as you're just restoring user apps and package states.
  • 383


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




    FTBV32.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.

    DeviceCompat.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, but can be restricted.
    • 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:
    FireOS Version
    Base Android Version
    **Restricted
    Amazon Fire HD 10 (2023)
    13​
    8​
    11​
    Yes (8.3.1.9+)​
    Amazon Fire Max 11 (2023)
    13​
    8​
    11​
    Yes (8.3.1.9+)​
    Amazon Fire 8 (2022)
    12​
    8​
    11​
    Yes (8.3.1.9+)​
    Amazon Fire 7 (2022)
    12​
    8​
    11​
    Yes (8.3.1.9+)​
    Amazon Fire 10/10+ (2021)
    11​
    7​
    9​
    Yes (7.3.2.2+)​
    Amazon Fire 8/8+ (2020)
    10​
    7​
    9​
    Yes (7.3.2.2+)​
    Amazon Fire 10 (2019)
    9​
    7​
    9​
    Yes (7.3.2.2+)​
    Amazon Fire 7 (2019)
    9​
    7​
    9​
    Yes (7.3.2.2+)​
    Amazon Fire 8 (2018)
    8​
    7​
    9​
    Yes (7.3.2.2+)​
    Amazon Fire 10 (2017)
    7​
    5​
    5.1​
    No
    Amazon Fire 8 (2017)
    7​
    5​
    5.1​
    No
    Amazon Fire 7 (2017)
    7​
    5​
    5.1​
    No
    Amazon Fire HD8 (2016)
    6​
    5​
    5.1​
    No
    Amazon Fire HD10 (2015)
    5​
    5​
    5.1​
    No
    Amazon Fire HD8 (2015)
    5​
    5​
    5.1​
    No
    Amazon Fire HD7 (2015)
    5​
    5​
    5.1​
    No
    Amazon Fire HD7 (2014)
    4​
    5​
    5.1​
    No
    Amazon Fire HD6 (2014)
    4​
    5​
    5.1​
    No

    * Generation equates to the year the tablet was released. For example, if the generation is 13 it means the tablet was released in 2023. 10 means the tablet was released in 2020... so on and so forth.

    ** Restricted equates to wether or not Amazon has locked down the firmware. When a firmware is restricted it means we cannot fully block OTAs, use custom launchers without Fire Launcher, lockscreen ads can no longer be permanantly removed, and some system apps can't be disabled. Even though a tablet is marked as Restricted in the table above, sometimes it may only apply to certain versions of FireOS. If your tablet is on a firmware before the listed firmware then your tablet is NOT restricted. See the "FireOS Restrictions and Fire Toolbox" section of the FAQ section (post #2) for further information on restricted firmwares.

    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 - 2023) 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!

    Downloads.png


    Windows:​

    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V34.0​
    Post
    Link​

    SHA256 Hashes​

    FilenameSHA256 Hash
    FTB_V34.0_Installer.exedf19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc
    FTB_V34.0_Portable.zipf47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f

    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    Checksums
    V33.1​
    Post​
    Link​
    V33.0​
    Download​
    Post
    Link​
    V32.4​
    Post​
    Link​
    V32.3​
    Download​
    Post
    Link​
    V32.2​
    Post​
    Link​
    V32.0​
    Download​
    Post​
    Link​
    V31.0​
    Download​
    Post​
    Link​
    V30.2​
    Download​
    Post​
    Link​
    V30.1​
    Download​
    Post​
    Link​
    V30.0​
    Download​
    Post
    Link
    V29.0​
    Download​
    Post
    Link
    V28.9​
    Download​
    Download​
    Post
    Link
    V27.0​
    Download​
    Post
    Link
    V26.1​
    Download​
    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​

    *Linux:​

    Version
    Python Version
    Installer
    Update Post
    V5.0 (Beta)​
    3.10.x​
    Post
    V5.0 (Beta)​
    3.11.x​
    Post

    NOTICE: You must obtain the correct version for your installed Python version. Run "python3 -V" in the Terminal to get the installed python version for your distro.

    SHA256 Hashes

    FilenameSHA256 Hash
    FTB_V5.0_Installer_Python3.10.7z985f1fc24d21c7506b9245f8ba37194380535fb5a8ef9af762d7d6d3853498ec
    FTB_V5.0_Installer_Python3.11.7z110bebfe5e28c75bd6235434f3b0ea640d6f24f77ef859a704db2a673972e01b

    * While in Beta, I'd like to heavy push the installer so that we can get it to stable along with the Toolbox. So, for now, the only download option will be the installer. Once the Toolbox and the Installer are both stable a portable option will be available. However, if you really need a portable version please PM me and I'll send you the link.

    Version
    Python Version
    Installer
    Update Post
    VirusTotal
    V4.0 (Beta)​
    3.10.x​
    Post
    Link​
    V4.0 (Beta)​
    3.11.x​
    Post
    Link​

    Version
    Python Version
    Installer
    Update Post
    VirusTotal
    V3.0 (Beta)​
    Python 3.10.x​
    Post
    Link​
    V3.0 (Beta)​
    Python 3.11.x​
    Post
    Link​

    Version
    Installer
    Portable (.zip)
    Update Post
    VirusTotal
    V2.0 (Beta)​
    n/A​
    Post​
    Link​
    V1.0 (Beta)​
    N/A​
    Post
    Link​

    Other Downloads:​

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

    Donate.png

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


    The Toolbox won't display correctly. The window is pure white and the text is faded. How can I fix this?
    2021-01-07_052532-jpg.5179871

    This can happen if window style and effects are turned off.

    Windows 7
    Control Panel > Performance Information and Tools > Adjust Visual Effects > Use Visual Styles on Windows and Buttons.


    Image credit: @gsm2001

    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. You can execute the "reset_navbar" (without quotes) command in the ADB Shell tool.

    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
    32
    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! ✌️