[WINDOWS/LINUX][TOOL]Fire Toolbox V32.2

Search This thread

Datastream33

Senior Member
Sep 17, 2017
2,613
2,347
the option to disable the home screen and replace it with a custom launcher doesn't seem to work. I've tried Lawnchaire launcher and Nova Launcher and the toolbox says it installed it fine and disabled the amazon launcher. but I'm still stuck with the amazon launcher

is this a known issue?
Hmm, could you please remind me which tablet you have? I'm wondering if the option is being displayed when it shouldn't. If your tablet is running FireOS 7.3.2.2 disabling won't work due to Fire Launcher now being a protected app.
 

Datastream33

Senior Member
Sep 17, 2017
2,613
2,347
Hi! I just got an Amazon Fire 10, 11th generation. Found this bc I am incensed by the ads on the screensaver and the limited controls. I'm new to a lot of the language on this page - if I 'install' the Toolbox installer on my roommate's mac book, will I be able to delete without damage to their device?

Also since it's June 2023 - would love a check in if this installer still works w the new tech.

Thank you so much!
This is a tough one. I'm afraid the port was never tested on a Mac before so I'm not sure if it would even work. I unfortunately don't have a Mac or know anyone that does, so it makes it a little complicated...

I'm not sure how to package it, or even run it. Anyone have any suggestions? Thanks!
 
  • Like
Reactions: fishbellbone

stevejohnson42

Senior Member
Dec 7, 2013
411
189
Aiken, South Carolina
First attempt - Linux Mint xfce v21.1 -- was missing modules ; installed those fine - stuck on error "ADB cannot identify your device due to a missing udev rule ... " - a helpful button with "How to add Udev Rule" -- however - when I click on it ; launches Firefox (my default) , loads my default page and error box pops up again -- ideas ?
 
  • Like
Reactions: Datastream33

stevejohnson42

Senior Member
Dec 7, 2013
411
189
Aiken, South Carolina
Hi,

I'm now test-driving the newly-minted Linux FTB :D Many thanks for this @Datastream33

Unfortunately, I hit a snag, and it is requesting that I add a missing udev rule. Clicking on the button on How to Add doesn't do anything but closes and reopens the window prompting to add the rule. I'm running FTB Linux as a regular user which I think is the intended design. My distro is

Code:
Distributor ID: Neon
Description:    KDE neon 5.27
Release:        22.04
Codename:       jammy

View attachment 5913261
similar issue on Linux Mint 21.1 xfce 64-b9t
 
  • Like
Reactions: Datastream33
First attempt - Linux Mint xfce v21.1 -- was missing modules ; installed those fine - stuck on error "ADB cannot identify your device due to a missing udev rule ... " - a helpful button with "How to add Udev Rule" -- however - when I click on it ; launches Firefox (my default) , loads my default page and error box pops up again -- ideas ?

similar issue on Linux Mint 21.1 xfce 64-b9t

Solution (perhaps) mentioned here....

 
  • Like
Reactions: Octopus2

stevejohnson42

Senior Member
Dec 7, 2013
411
189
Aiken, South Carolina
Solution (perhaps) mentioned here....

thanks - tried ; will need to review a bit more - getting stuck after issuing
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0338", GROUP="plugdev"
-- then getting :
ATTR{idVendor}==1949,: command not found

attr shows up in /bin - went there and opened as root and used terminal there - same thing
 
@Datastream33
Sir,i may have found why i kept getting those updates even though i blocked ota through fallback method (by toolbox 30.3)

When I'm in metered network(which is set to connected wifi by toolbox during procedure) i face no updates....but when i connect to new wifi(while moving between campus/library) it doesn’t stay metered.... It sets to detect automatically.... That's when i get update.....

Is there any way to make it automatically set all new wifi's to metered? Maybe any adb commands?? Or by automate??
 

Datastream33

Senior Member
Sep 17, 2017
2,613
2,347
First attempt - Linux Mint xfce v21.1 -- was missing modules ; installed those fine - stuck on error "ADB cannot identify your device due to a missing udev rule ... " - a helpful button with "How to add Udev Rule" -- however - when I click on it ; launches Firefox (my default) , loads my default page and error box pops up again -- ideas ?
Greetings!

May I ask which version of the port you have? In V1.1, the Toolbox should create a udev rule for you.
 

Zelda2013

Senior Member
1686434502199.png

was trying to set One UI for my launcher but it just gets stuck on this. Help?
 

LeftHand0fGod

New member
Jun 11, 2023
2
0
attempted install on kde plasma and got this in konsole

Traceback (most recent call last):
File ".pyarmor/pack/dist/Installer.py", line 2, in <module>
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "PyInstaller/loader/pyimod02_importers.py", line 352, in exec_module
File "<frozen pyarmor_runtime_004083>", line 2, in <module>
RuntimeError: missing license key to run the script (1:10555)
[91103] Failed to execute script 'Installer' due to unhandled exception!
 

Datastream33

Senior Member
Sep 17, 2017
2,613
2,347
attempted install on kde plasma and got this in konsole

Traceback (most recent call last):
File ".pyarmor/pack/dist/Installer.py", line 2, in <module>
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "PyInstaller/loader/pyimod02_importers.py", line 352, in exec_module
File "<frozen pyarmor_runtime_004083>", line 2, in <module>
RuntimeError: missing license key to run the script (1:10555)
[91103] Failed to execute script 'Installer' due to unhandled exception!
Hmm, I would try downloading a fresh copy of the installer.
 
attempted install on kde plasma and got this in konsole

Traceback (most recent call last):
File ".pyarmor/pack/dist/Installer.py", line 2, in <module>
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "PyInstaller/loader/pyimod02_importers.py", line 352, in exec_module
File "<frozen pyarmor_runtime_004083>", line 2, in <module>
RuntimeError: missing license key to run the script (1:10555)
[91103] Failed to execute script 'Installer' due to unhandled exception!
This may not be a helpful post but...

I think I had this error yesterday when I installed on Mint 21. From memory, the advice I recall I found was to make sure the Fire was unlocked, connected and awake when installing the toolbox.

I will double check that later (hopefully still in my browser history) and report back, but for now it might get you going. Suffice it to say that I was able to install and get the toolbox working.

Edit: yes indeed, I'd found my answer earlier in this thread....

 
Last edited:
I installed the toolbox yesterday under linux (Mint 21) and proceeded to debloat and tweak etc in the hope of deAmazoning my Fire (a 2nd hand 10th gen 8, on 7.3.2.7)

I've got the known issue of replacing the Fire launcher (I've used Nova for years and like it) that I'm currently trying to resolve. Launcher Hijack sort of works, it's hit and miss. The 'home' key usually activates/displays the Fire launcher and then after a few seconds, Nova takes over... or sometimes not. It's annoying but not a show stopper. Simply tapping on the Hijack app gets Nova back. If I find a solution, I'll post it.

I seem to have stopped OTA updates (more by luck than design) but have now set 'restricted' via the toolbox anyway. Initially, I got updates so tried the RethinkDNS solution but I wasn't happy with it; it seemed to mess with internal network connections. I use my tablets as device controllers too; Kodi, Sonos, LMS, etc and these apps sometimes didn't work. Tbf there's probably a solution somewhere in the settings but I didn't play around with them. Short of it is that I removed it but have had no OTA updates since (touch wood)

As the more mature version of toolbox seemed to be on the Windows platform, I tried that first. I only have a Win7 setup (a 'just in case' box) but had problems getting the Google ADB drivers recognised. The linux version installed perfectly and is a very slick, intuitive and complete piece of software - I'm most impressed (y)
 

stevejohnson42

Senior Member
Dec 7, 2013
411
189
Aiken, South Carolina
Greetings!

May I ask which version of the port you have? In V1.1, the Toolbox should create a udev rule for you.
I had pulled V1.0 - thanks ; will review updated one - my mistake ; I thought I had snagged the latest. In very short term - I got a functioning tool - downloaded the portable version and used my wife's laptop to create on USB drive to use there :)
 

Top Liked Posts

  • 3
    That’s encouraging, is yours a Fire Max 11 too?

    I gave up after three tries as every time after about 7-10 days I would get crashing apps, but funnily no problems with Play store or Google apps. It was usually browsers, Outlook and some others, but always the same ones.

    I am currently running mine stock, but all apps not available from Amazon I am getting from Uptodown and it’s been working flawlessly. The only thing I don’t have is the Google apps which I am not missing really, but I may give FTB another go if it is more stable on 8.3.2.0
    Yep - Max 11

    FireOS 8.3.2 is unrelated to FTB other than the restrictions imposed by the OS. The former addresses most (if not all) recently introduced FireOS incompatibilities with Google Play Services which underlying reason why many Google and various 3rd party apps that depend on GPS were misbehaving. The latter facilitates tweaks to FireOS that are not supported by the native UI. FTB is an excellent tool for those unfamiliar with ADB and general programming.

    In short, if you want your device to reliably work with apps that utilize GPS upgrade to FireOS 8.3.2.x. If your world is defined by the launcher UX then stick with whatever version you're on today.
    2
    I've got a fire max 11, but it's on 8.3.1.5 The Google apps seem to behave themselves until I install the YouTube kids app for my children and the YouTube music app doesn't work either. Won't let me sign in. it says that the Google play services isn't installed when I try to open the YouTube kids app even though the play store works and YouTube works etc. Now some of the apps randomly close when I open them, sometimes they will work sometimes not. last time I tried I had to factory reset and install everything again. I wonder if 8.3.2.0 update will fix the problem with the youtube kids and youtube music apps. I was reluctant to try because it will lock down more amazon apps and not allow me to remove the fire launcher.
    FWIW - YouTube music works fine on 8.3.2.0; didn't try kids but expect a similar outcome.
    1
    Greetings!

    Hmm, let's see if we can get down to the bottom of this!

    Let's see if logcat can help us here... please open an ADB Shell and try the following commands one by one:
    Code:
    cmd
    Code:
    exit
    Code:
    adb logcat -b crash > C:\users\%USERNAME%\Desktop\log.txt
    After executing the command above, please open the Gmail app, and perform the steps that causes it to crash. Repeat the crash a few times, then click on the command prompt window, and finally press CTRL+C to stop logcat's execution.

    On your desktop you'll find a new txt file named log.txt... could you please upload that file and share the link with us so we can take a look further and see if it can be determined as to what is causing the crash?
    You bet but I'm watching the Cassidy Hutchinson interview. I'll probably upload it tomorrow.
    1
    No issues after a 10+ day run on 8.3.2.0. Have yet to encounter a Google or 3rd party app that won't launch and remain running assuming prerequisites are satisfied. How well that app functions remains a crap shoot given FireOS weirdness...which has always been the case for Amazon gizmos.
    I've got a fire max 11, but it's on 8.3.1.5 The Google apps seem to behave themselves until I install the YouTube kids app for my children and the YouTube music app doesn't work either. Won't let me sign in. it says that the Google play services isn't installed when I try to open the YouTube kids app even though the play store works and YouTube works etc. Now some of the apps randomly close when I open them, sometimes they will work sometimes not. last time I tried I had to factory reset and install everything again. I wonder if 8.3.2.0 update will fix the problem with the youtube kids and youtube music apps. I was reluctant to try because it will lock down more amazon apps and not allow me to remove the fire launcher.
    1
    I've got a fire max 11, but it's on 8.3.1.5 The Google apps seem to behave themselves until I install the YouTube kids app for my children and the YouTube music app doesn't work either. Won't let me sign in. it says that the Google play services isn't installed when I try to open the YouTube kids app even though the play store works and YouTube works etc. Now some of the apps randomly close when I open them, sometimes they will work sometimes not. last time I tried I had to factory reset and install everything again. I wonder if 8.3.2.0 update will fix the problem with the youtube kids and youtube music apps. I was reluctant to try because it will lock down more amazon apps and not allow me to remove the fire launcher.
    yeah the solution datastream suggested to me worked on my max 11 with 8.3.1.5
    but now it is doing it again, everyhting was workinf flawlessly but then today I noticed that when I try and launch the Google app from nova launcher nav bar widget it is immediatley force closing agin or it force closes shen I try and type something, the I notice that Gmail is also force closing not always but most of the time I tried not soft and har reboots and it didnt help, the Google app also neeed an update and after updating it it is still force closing from the nova aluncher widget but it worked before an afte the update if I launch it from the app drawer icon.
    oter google apps seem to work but I was trying to do a log in with googl eor link to Goole with one of my other app accounts and I was getting the your devie has no google play services message, aftet that is when it started acing up again
    so I think that it might have something to do with trying to connect another service to use google log in, like when it contacts google servers to use sign in with google it seems to break something
    I will try and run the commands datastrea told me againa nd see if it will fix it again and if it does I am not going to be using log in with google for any of my other stuff again
    I am not sure that is wha caused it but it is funny that it was all working perfectly untill I tried to renew my magic jack subscription I think
    it said connect you account to Google for Google log in and when i tried to do that it said I needed play services and then not long after i tried using the Google search wiidget and noticed it was force closing again where it has been working perfectly ever since I tried those commands from datastream.
    I think they are to do with a whitelist and mabybe connecting the particular Googl server that ahndles the login in with google stuff is flaggin me for the blacklist again?just a theory what do you guys think?
    Also I beleives datastream said he added the commands to FTB but I am not sure if it is a stand alone tool or what it's called or if it just does it during the intial wizard setup
  • 4
    Ok, welp... it seems pastebin had enough of us and turned off the bins that contained pointers for the download links. I've updated the Toolbox to include new pointer links using rentry.co instead of pastebin.com. As a result, *downloads in V32.2 are now working once more!

    * Downloads will ONLY work in V32.2 and above. Make sure you obtain the new build from the OP!

    I've also updated the device detection code so it will no longer set FireOS 8.3.1.5 as restricted.

    Downloads​

    Version​
    Installer (.exe)​
    Portable (.zip)​
    V32.2​
    3
    ## SPAM/WAREZ ALERT ##

    This is NOT an official Fire Toolbox website:


    Only download Fire Toolbox software from links in OP#1 to avoid possible spam/warez !
    3
    Hey @Datastream33

    Heads-up for FTB device ident

    New Fire HD10 13th Gen 2023 just released
    Model : KFTUWI
    Code name TBD
    3
    Google authenticator is working perfect for me on 8.3.2.0 as are most apps :)
    That is good to hear. Would you kindly please install Google Authenticator and advise if it's working on the latest firmware? Greatly appreciated.
    3
    Changelogs of firetoolbox 32.2?
    Greetings!

    Not much has changed in V32.2.

    Just updated the pointer for the download links to obtain them from Rentry instead of Pastebin. The device detection code was also updated to ensure FireOS 8.3.1.5 isn't marked as "restricted" when it shouldn't be. Not too many changes this time around... been mainly focused on the Linux port. :D
  • 375



    Fire Toolbox V32.2
    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.

    View attachment 5469557

    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 Max 11 (2023)
    13​
    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 - 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!

    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


    Windows:​

    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V32.2​
    Post​
    Link​
    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    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
    VirusTotal
    V3.0 (Beta)​
    3.10.x​
    Post
    Link​
    V3.0 (Beta)​
    3.11.x​
    Post
    Link​

    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.

    * 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
    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!
    74
    FAQ.png


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