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

Search This thread

Datastream33

Senior Member
Sep 17, 2017
2,797
2,645
╓─────────────────────────────────────────────────╖

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

╙──────────────────────────────────────────────────╜

FireToolbox.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/USB Debugging 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
Standalone (.exe)
Update Post
Checksums​
V38.0​
Post

SHA256 Hashes​

FilenameSHA256 Hash
FTB_V38.0_Standalone.zipee24062c6009b1264a17e22c5f99672f7aecae251f19f964afe1162fb448dd3e

WARNING: Due to Rentry adding Cloudflare to their website, previous versions (under V37.1) of the Toolbox are unable to download files or reach out to the server to check for notifications, updates, or even retrieve download links for Google Services/hybrid apps. It's recommended to use the latest version of the Toolbox for the best experience.

Standalone (One-File)​

Version
Standalone (.exe)
Update Post
Checksum
V37.1​
Post​
V37.0​
Post
V36.1​
Post​
V35.0​
Post

Standard (Independent)​

Version
Installer (.exe)
Portable (.zip)
Update Post
VirusTotal
Checksums
V34.0​
Post
Link​
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
AppImage
Update Post
Checksums (SHA256)
V9.0​
Post

SHA256 Hash

FilenameSHA256 Hash
FTB_V9.0_AppImage.7z14b456617790a3c3ec434b41b6e54b2c2304b0804f63e2470ec8198d1ea73110


WARNING: Due to Rentry adding Cloudflare to their website, previous versions of the Toolbox are unable to download files or reach out to the server to check for notifications, updates, or even retrieve download links for Google Services/hybrid apps. It's recommended to use the latest version of the Toolbox for the best experience.

AppImages​

Version
AppImage
Update Post
Checksums (SHA256)
V8.1 (Beta)​
Post​
V8.0 (Beta)​
Post
V7.1 (Beta)​
Post​
V7.0 (Beta)​
Post​
V6.3 (Beta)​
Post​
V6.0 (Beta)​
Post


Standard​

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​
Python Version​
Installer​
Update Post​
Checksum​
V5.0 (Beta)​
3.10.x​
Post
V5.0 (Beta)​
3.11.x​
Post

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!
 

Attachments

  • DeviceCompat.png
    DeviceCompat.png
    42.2 KB · Views: 14,131
Last edited:

Datastream33

Senior Member
Sep 17, 2017
2,797
2,645
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 also execute the "reset_navbar" (without quotes) command in the ADB Shell tool.

Google Family Link won't work on my tablet?
Unfortunately, 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 dependencies, and the tablets not being certified through Google's Play Protect platform. We're still actively 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?
Primarily, 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 positive.
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
 
Last edited:

Jumbo100

Senior Member
Jul 21, 2022
1,155
989
## 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 !
 

Datastream33

Senior Member
Sep 17, 2017
2,797
2,645
2018 HD 8, did the remove lockscreen ads. went through its process. said sucess. nothing changed, and nothing in the downloads folder

This tool is designed to install Automate, push Amazon Lockscreen Ads Remover V4.5 to tablet, and install all permissions required to run the script. Now, to get it all set up and working you need to enter Automate and open the settings. From here you are looking for an option that's titled "Run on system startup" make sure you enable this option. Now, for installing the adblocker you can import it into Automate (Flow is found on your internal storage or sdcard) Or you can download the script from the automate community. Refer to this forum if you need assistance (skip steps 1-5 because they have already been done automatically by the toolbox). Sorry I can't write up a detailed post, I'm at a family gathering at the moment. Just let me know if you need further assistance.
 

newfires

New member
Jan 14, 2019
1
1
Great tool! However, after "removing everything Amazon", it seems to have also removed parental controls which screws up some things. I get "the requested action is not permitted. Check parental controls settings and retry" when I try to download offline translation functionality in Google Translate. When I go to the the tablets settings>parental controls, it won't open. Also seems to not allow install of Amazon related apps like kindle and prime video.
 
  • Like
Reactions: flores1970sergio

Datastream33

Senior Member
Sep 17, 2017
2,797
2,645
Great tool! However, after "removing everything Amazon", it seems to have also removed parental controls which screws up some things. I get "the requested action is not permitted. Check parental controls settings and retry" when I try to download offline translation functionality in Google Translate. When I go to the the tablets settings>parental controls, it won't open. Also seems to not allow install of Amazon related apps like kindle and prime video.

It's kind of annoying right? So, whats happening is Its coded to remove Parental Controls but I've just discovered it isn't able to because Parental Controls is a Device Administrator which you can't uninstall even with ADB without deactivating it first. As a result, I will update the tool so it doesn't remove anything related to parental controls until we can find a way to disable it. However, chances are kind of slim. I don't think its possible without root but we will see. I'm also thinking about a restore option for the "Remove Everything Amazon" tool that returns the amazon system apps so you don't have to do a factory reset. :)
 

jjta

Senior Member
May 23, 2008
84
14
It's kind of annoying right? So, whats happening is Its coded to remove Parental Controls but I've just discovered it isn't able to because Parental Controls is a Device Administrator which you can't uninstall even with ADB without deactivating it first. As a result, I will update the tool so it doesn't remove anything related to parental controls until we can find a way to disable it. However, chances are kind of slim. I don't think its possible without root but we will see. I'm also thinking about a restore option for the "Remove Everything Amazon" tool that returns the amazon system apps so you don't have to do a factory reset. :)

Pls let us know when it's updated I would love to remove amazon bloat and free up some space
 
  • Like
Reactions: flores1970sergio

Datastream33

Senior Member
Sep 17, 2017
2,797
2,645
question, if i remove everything amazon-related, can i still install kindle app from play store,? i tried this with a previous tool and had no succes, it would fail to install kindle from play store, i had to factory reset back.

Hmmm, I'm not sure about this. I can test it at home and let you know how it goes if you would like. However, it would be a few hours from now if your interested.
 

shonkin

Senior Member
Oct 15, 2012
1,460
586
Will this work on a Kindle Fire 10" Gen 5 version? I've already hacked my wife's 2017 using another more complex path to doing so, but a friend just asked me to hack his Gen 5 10" and I'd love to do it as easily as this. However, a bit nervous if this doesn't allow it.
 
  • Like
Reactions: flores1970sergio

shonkin

Senior Member
Oct 15, 2012
1,460
586
I think I answered my own question. Using a windows 10 computer, I connected the 10" Fire Gen 5... ran the program... and it continually crashed after initially finding the kindle. I never got the menu with the options. And where does this program unpack itself to once the EXE zip is run?
 

Datastream33

Senior Member
Sep 17, 2017
2,797
2,645
I think I answered my own question. Using a windows 10 computer, I connected the 10" Fire Gen 5... ran the program... and it continually crashed after initially finding the kindle. I never got the menu with the options. And where does this program unpack itself to once the EXE zip is run?

I believe this may be a bug in the tablet detect section of the code. I know it can read Hd10 (2017), hd8 (2017), and hd (2018) without error. I'm not sure what's going on but I will look into it. Oh and also, a new version of the tool is coming soon!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Seasons Greetings,

    Just wanted to hop on here real quick to wish you all a very Merry Christmas! 🎅🎄

    I hope everyone is able to spend it with the ones they love. If you don't celebrate Christmas then I sincerly hope you have a wonderful day. :D
    5
    What's going on guys?

    I hope everyone had a great Christmas, and an even better 2024.

    Today marks the release of both Fire Toolbox V38.0 (Windows), and V9.0 (Linux). So let's not dilly dally, and just jump into it. Here's the major highlights of today's releases:

    Externalizing the External Files​

    Perhaps the biggest change, I'm excited to announce that it's now possible to change the location where the external files are extracted to!

    So, if you're running the Toolbox for the very first time, the first thing you'll be asked is where you'd like to extract the external files to. If you've ran previous versions of the Toolbox (standalone only) then the Toolbox will just launch like normal.

    It's important to know that the following locations will ALWAYS to presence over custom paths (for legacy support):
    • Linux - /home/$USER/.local/share/Datastream/FireToolbox
    • Windows - %LOCALAPPDATA%\Datastream\FireToolbox
    Now when it comes to custom paths, the Toolbox will place a pointer file in the following location:
    • Linux - /home/$USER/.config/FireToolbox/external_path.txt
    • Windows - C:\Users\%USERNAME%\Documents\FireToolbox\External_Path.txt
    This pointer file contains the custom path for the external files, and will be read by the Toolbox when it's looking for the external files (remember, custom paths are checked AFTER the legacy paths).

    However, if you've ran previous versions and would like to move your external files to a different location, all you need to do is launch the Toolbox's Settings subtool, navigate to the new External Files tab, and select the Migrate External Files option in the Manage External Files section. You'll then be asked where you'd like to migrate the files to. Once you've selected the desired option, the Toolbox will start copying over your external files to the new location, before killing ADB, executing a helper batch script (Only on Windows), and then closing the Toolbox. Once the old root is deleted by the helper batch script, it will re-launch the Toolbox with the new external files location being set (this can be verified by checking the path under the External Files Location section in the External files tab in the Settings subtool).

    Also, if you've got a broken external files setup, in the same section as the Migrate feature there's also a featured titled Update External Files that will as the name suggests, place new files into the external files directory. Note that this process does NOT replace your alias file, settings/notification files. It simply re-adds any missing files.

    1736133642336.png


    1736133827175.png

    Managing Those Tasks​

    A new addition to the Manage Amazon Apps is the Task Manager subtool. Like all task managers, this subtool is designed to show you what apps are running, their process IDs (PID), and how much RAM each app is using. In the top left of the tool, you'll find the Total RAM, and Free RAM usage (realtime) info.

    Now under the header, this is where the apps are listed out in panels. Now unlike the Free RAM, the RAM usage for each app is not realtime and updates every 2 seconds. The reason for this is simply because the adb command we need to run take some time, and calculations need to made before the new info can be displayed. Currently, the Task Manager can only force stop apps, but I'm planning on adding in new features in future updates.

    So, to force stop an app, all you need to do is click on the name of the process you want to force stop. Once clicked, the text's background will change to blue indicating that it has been selected. Now click the Force Stop button on the upper-right hand corner and then click Yes on the messagebox asking if you'd like to force stop it. That's it. The app will disappear from the list. Also, if you open another app, it's process will show up at the bottom of the list, but It may take a few seconds to appear.

    Windows
    1736132764272.png


    Linux
    1736132865130.png

    Highlighting the ADB Shell Changes​

    The latest update introduces several enhancements to improve user experience and functionality. Error output is now displayed, making it easier to identify issues. Additionally, if the alias file is missing, it will be created automatically upon the tool's initial launch, rather than waiting for the first command execution.

    Two new default aliases, "enable_app" and "disable_app," have been added as shorthand for the "disable-user" and "enable" PM commands. A fix has been implemented to ensure that the logcat command on no longer continues running after the tool's window is closed (Windows only).

    To enhance clarity, executed commands are now highlighted in green (yellow on Linux) within the output section, allowing users to easily distinguish between previous commands and their outputs. Furthermore, context menus have been added to both the Output and input sections, providing options to "Copy All," "Copy Selected," "Paste," "Copy," and "Select All." Lastly, if a default alias is introduced in a new release, the Toolbox will automatically append these new aliases to the user's alias file automatically.

    1736133500093.png


    1736133387352.png

    Talking to the Server​

    Also joining the Settings is another brand new tab, the "Server" tab. In this tab, you'll be able to see if the Toolbox is successfully able to ping the Pastefy website. Pastefy is where our download pointer links are stored, so if the Toolbox is able to reach it downloads will fail, notifications won't be recieved, and updates can't be checked. If an error does occur a red X will be shown, and below it the reason for failure will be displayed. If it's successful, then a green checkmark will be shown.There's also a refresh button (↺) that can be clicked to force the Toolbox to try and ping again. Usually, a failure to ping Pastefy is a result of no internet connection, or a block via your computer or router's firewall. This tab was added to help troubleshoot and narrow down the issue for an easier fix. ;)

    1736133129045.png


    1736133060626.png

    Adding a Welcome to the Window​

    Now this one's for my penguin lovers. Starting in V9.0, it's now possible to enable window resizing directly from the Welcome Screen. Just navigate to the Window tab, and from there you can toggle the always on top setting, enable window resizing, and change the window scaling. This makes it so much easier to toggle on the necessary settings if the Toolbox doesn't play well with your window manager.

    1736132986697.png

    Changelogs​

    Interested in everything that's changed, here's the changelog for both releases:

    Windows​

    Fire Toolbox V38.0

    [ADB Shell]
    • Error output is now shown.
    • The alias file (if missing) is now created on the tool's initial launch instead of before executing the first command.
    • Added 2 new default aliases: enable_app and disable_app (shorthand for the "disable-user" and "enable" pm commands).
    • Fixed an issue where the logcat command would continue to run after the tool's window was closed.
    • Executed commands are now highlighted in green in the output section to help differentiate previous commands from command output.
    • Added a context menu to the Output section with options to "Copy All" or "Copy Selected" output.
    • Added a context menu to the input section with the option to "Paste", "Copy", and "Select All".
    • If a default alias is added to a new release, the Toolbox will now append the new aliases to the user's alias file automatically.

    [External Files]
    • Added the option to choose where you'd like the external files to be extracted to.

    [Device Detection]
    • The Toolbox now properly detects when the tablet is offline, and will auto-restart the adb server.

    [Sideload Apps]
    • Added checks to ensure that an APK can be installed based on its minimum SDK version.
    • When loading an app for sideload, hovering the mouse over the app label will now show a tooltip with information such as the app label, the package name, app version, and the main activity.

    [Foss App Center]
    • Updated all apps to the latest versions.
    • Added Material Files to the apps list.

    [Settings]
    • Added the Server tab.
    • Added the Server Status section to the Server tab.
    • Added the External Files tab.
    • Added the option to Migrate the external files, and Update external files options to the External Files tab.

    [Manage Amazon Apps]
    • Added the Task Manager subtool to the Advanced section.

    [Custom Launcher]
    • Added an option to mute the Notification stream after setting up the Custom Navbar Key launcher activation method (removes the popping sound that occurs when playing media).

    [Play Services]
    • When installing using local files (downloaded play service files from a previous session), the downloaded archive is now checked via 7z to ensure the 7z archive is valid.
    • Added further checks to ensure download links, and download info is properly obtained from the server before downloading.

    Linux​

    Fire Toolbox V9.0

    [Foss App Center]
    • Updated all apps to the latest versions.
    • Added Material Files to the apps list.

    [External Files]
    • Added the option to choose where you'd like the external files to be extracted to.

    [ADB Shell]
    • History now behaves as it should.
    • Added 2 new default aliases: enable_app and disable_app (shorthand for the "disable-user" and "enable" pm commands).
    • Executed commands are now highlighted in yellow in the output section to help differentiate previous commands from command output.
    • Added a context menu to the input section with the option to "Paste", and "Select All".
    • If a default alias is added to a new release, the Toolbox will now append the new aliases to the user's alias file automatically.

    [Manage Amazon Apps]
    • Added the Task Manager subtool to the Advanced section.

    [Welcome Screen]
    • Added the Window tab, with the options to change the window scaling, enable resizing, and toggling always on top.

    [Settings]
    • Added the Server tab.
    • Added the Server Status section to the Server tab.
    • Added the External Files tab.
    • Added the option to Migrate the external files, and Update external files options to the External Files tab.

    [Custom Launcher]
    • Fixed an issue where the Install button wouldn't appear when selecting a custom launcher in the "Install Launcher" tab.
    • Added an option to mute the Notification stream after setting up the Custom Navbar Key launcher activation method (removes the popping sound that occurs when playing media).

    [Device Detection]
    • The Toolbox now properly detects when the tablet is offline, and will auto-restart the adb server.

    [Sideload Apps]
    • When loading an app for sideload, hovering the mouse over the app label will now show a tooltip with information such as the app label, the package name, the version name, and the main activity.
    • Improved XAPK support.
    • Fixed the Auto-load APK feature so it now properly detects new downloads.
    • Added checks to ensure that an APK can be installed based on its minimum SDK version.

    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. So starting tonight, I will be sharing the SHA256 checksums for both the Installer, and Portable builds (should of done this a long time ago, but better late then never right?). 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​

    NamePlatformDownload
    Fire Toolbox V38.0WindowsStandalone (.exe)
    Fire Toolbox V9.0LinuxAppImage

    SHA256 Checksums​

    FilenameSHA256 Hash
    FTB_V38.0_Standalone.zipee24062c6009b1264a17e22c5f99672f7aecae251f19f964afe1162fb448dd3e
    FTB_V9.0_AppImage.7z14b456617790a3c3ec434b41b6e54b2c2304b0804f63e2470ec8198d1ea73110

    Wrapping Things Up​

    Once again, a huge shoutout to all you wonderful people for your incredible support! Whether you’ve engaged with one another, sharing resolutions to problems, or simply been amazing, your contributions mean the world. I also want to extend my heartfelt thanks to those who have supported us through donations. Your kindness is truly appreciated!

    Also, a ENORMOUS shoutout goes to @blaacksheep, @Jumbo100, and @DB126 for being all around amazing people! You're continued support, advice, solutions, and commitment to this amazing community is invaluable and highly appreciated. Thank you 3 so much for everything you've done, couldn't imagine what it would be without you guys!

    Hey, so 2024 is officially over, so happy late New Years to everyone, and thank you all so much for giving the Toolbox a chance. 2024 was great, and I can't wait to see where 2025 is going to take us. Wishing everyone the best that 2025 has to offer! :D

    Well, that's everything I've got for now... please have a wonderful rest of your night/day, and I'll see you guys later. Peace!✌️
    3
    What if i already linked my device and updated the amazon update....
    (did not know bout this till after purchased)

    Any assistance greatly appreciated

    I did the same, but the Toolbox still worked fine. I did it on a Fire 7 12th Gen.

    This was primarily a precaution for earlier versions of FireOS, where you would not pre-register your device and then it wouldn't already have your wifi password. This was to prevent it from updating to F/W v7.3.2.2 and lock you out of changing your launcher.

    If you bought a new tablet, it likely came with FireOS 8 and you probably want the updates anyway for Google compatibility. In any case, workarounds have been developed to get around their lockdowns.

    You'll want to register your device anyway if you wish to use any Amazon Services. You'll have to log in to Amazon to use them and that will register your tablet.

    In other words, it's okay and not a problem anymore. :)
    3
    Developer Options ... an overview ... more than just USB Debugging:

    2
    No problem. :)

    To summarize, if you have a 2017 or earlier tablet (FireOS 5) and are familiar with using a kernel exploit to root, search the thread or ask here for a link to a thread telling you how to root your tablet. If you have an early 2019 tablet that hasn't been updated to beyond F/W v7..3 .1.2, there's a few threads on getting temp root on those. Anything beyond Dec. 2019 is blocked and not rootable yet that I know of, but you may want to block updates because the v7.3.2.2 update made many apps "system protected" and prevents you from modifying many things, thus the workarounds in Toolbox were added. If your tablet is on v8.x.x.x of FireOS, you probably don't want to block updates because at least the first few updates are needed to make Google Services work properly with FireOS, and the updates don't further lock down the tablet.

    (I don't seem to summarize well now do I? lol)

    Merry Christmas!
    Thanks, Heres the strange thing. I bought both at the same time. Both are gen 11 Fire 10. One of them I can fully de-bloat but the other I cannot. They are 2 different builds but both bought at the same time. I believe one may have been patched and the other was not. Anyways not a big deal, thanks for the help
  • 394
    ╓─────────────────────────────────────────────────╖

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

    ╙──────────────────────────────────────────────────╜

    FireToolbox.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/USB Debugging 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
    Standalone (.exe)
    Update Post
    Checksums​
    V38.0​
    Post

    SHA256 Hashes​

    FilenameSHA256 Hash
    FTB_V38.0_Standalone.zipee24062c6009b1264a17e22c5f99672f7aecae251f19f964afe1162fb448dd3e

    WARNING: Due to Rentry adding Cloudflare to their website, previous versions (under V37.1) of the Toolbox are unable to download files or reach out to the server to check for notifications, updates, or even retrieve download links for Google Services/hybrid apps. It's recommended to use the latest version of the Toolbox for the best experience.

    Standalone (One-File)​

    Version
    Standalone (.exe)
    Update Post
    Checksum
    V37.1​
    Post​
    V37.0​
    Post
    V36.1​
    Post​
    V35.0​
    Post

    Standard (Independent)​

    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    Checksums
    V34.0​
    Post
    Link​
    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
    AppImage
    Update Post
    Checksums (SHA256)
    V9.0​
    Post

    SHA256 Hash

    FilenameSHA256 Hash
    FTB_V9.0_AppImage.7z14b456617790a3c3ec434b41b6e54b2c2304b0804f63e2470ec8198d1ea73110


    WARNING: Due to Rentry adding Cloudflare to their website, previous versions of the Toolbox are unable to download files or reach out to the server to check for notifications, updates, or even retrieve download links for Google Services/hybrid apps. It's recommended to use the latest version of the Toolbox for the best experience.

    AppImages​

    Version
    AppImage
    Update Post
    Checksums (SHA256)
    V8.1 (Beta)​
    Post​
    V8.0 (Beta)​
    Post
    V7.1 (Beta)​
    Post​
    V7.0 (Beta)​
    Post​
    V6.3 (Beta)​
    Post​
    V6.0 (Beta)​
    Post


    Standard​

    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​
    Python Version​
    Installer​
    Update Post​
    Checksum​
    V5.0 (Beta)​
    3.10.x​
    Post
    V5.0 (Beta)​
    3.11.x​
    Post

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

    Google Family Link won't work on my tablet?
    Unfortunately, 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 dependencies, and the tablets not being certified through Google's Play Protect platform. We're still actively 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?
    Primarily, 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 positive.
    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! ✌️