[WINDOWS][TOOL]Fire Toolbox V28.1

Search This thread

blaacksheep

Senior Member
Jun 20, 2020
960
532
Buffalo
Como hago para usar la caja de herramientas ?

I don't speak Spanish, but I do have Google translate.

You install Toolbox on your Windows computer, enable ADB debugging on your Fire tablet, then you connect your tablet to your computer to run the various tools on your tablet. I think it's pretty well explained in the first post of this thread.

(Translated with Google)
No hablo español, pero tengo traductor de Google. Instala Toolbox en su computadora con Windows, habilita la depuración de ADB en su tableta Fire, luego conecta su tableta a su computadora para ejecutar las diversas herramientas en su tableta. Creo que está bastante bien explicado en el primer mensaje de este hilo.
 
Last edited:

cf77

Member
Sep 10, 2021
21
6
Saw Amazon posting 7.3.2.3 firmware.
Has Amazon loosen up locking the navigating bar? in this new version?

I hope Amazon loosing hugh sales of their tablets.
 

westhamtim

New member
May 28, 2022
3
2
Hi

I'm trying to clean up my young daughter's FIre 7 using Toolbox. I've successfully run the Toolbox on my other Fire tablets but on this one the Toolbox tells me my device isn't authorized. According to the instructions I should see a pop up on the tablet that allows me to authorize it but no such pop up appears. I've toggled ADB debugging on & off, restarted everything but to no avail. I cant find the answer anywhere, can somebody please help>!

Thanks very much!!
 
  • Like
Reactions: Datastream33

Datastream33

Senior Member
Sep 17, 2017
2,179
1,793
Hi

I'm trying to clean up my young daughter's FIre 7 using Toolbox. I've successfully run the Toolbox on my other Fire tablets but on this one the Toolbox tells me my device isn't authorized. According to the instructions I should see a pop up on the tablet that allows me to authorize it but no such pop up appears. I've toggled ADB debugging on & off, restarted everything but to no avail. I cant find the answer anywhere, can somebody please help>!

Thanks very much!!
Greetings!

In the same place where USB Debugging (or ADB Debugging) is enabled, there should be another option titled "Revoke USB Debugging authorisations". Try tapping that, and then tap "OK" on the message that appears to seal the deal. Then disconnect your tablet from your computer, and re-plug it in. You should now be able to authorize it (if not repeat the procedure, but after revoking try restarting your computer and try again). If you need further help, please don't hesitate to ask. Best of luck! :D
 

westhamtim

New member
May 28, 2022
3
2
Greetings!

In the same place where USB Debugging (or ADB Debugging) is enabled, there should be another option titled "Revoke USB Debugging authorisations". Try tapping that, and then tap "OK" on the message that appears to seal the deal. Then disconnect your tablet from your computer, and re-plug it in. You should now be able to authorize it (if not repeat the procedure, but after revoking try restarting your computer and try again). If you need further help, please don't hesitate to ask. Best of luck! :D
Wow, thanks for the quick response! Unfortunately I've tried that and no luck. I did get the 'revoke access to USB debugging' dialogue message box come up and hit OK but still no dialogue box to authorize the device. When the device is plugged in it does show up as being attached in the ADB status box within the toolbox. Any other options or do I just need to write this off as one of those things?
 
  • Like
Reactions: blaacksheep

Datastream33

Senior Member
Sep 17, 2017
2,179
1,793
What's going on, guys?

I hope everyone is having a fantastic weekend so far!

I'm so excited to announce that Toolbox V28.0 has just been released! 🎉

In today's update, we have so many exciting things to go over, including a new method to bring back custom launchers on tablets running FireOS 7.3.2.2 and above!!! 🥳

So without further ado, let's jump into the meat and potatoes of the new update!

The Return of Custom Launchers and Other Improvements!​

So, as you guys may know, it's been pretty difficult to use third party launchers ever since FireOS 7.3.2.2 dropped. We had a workaround, but it was ideal and wouldn't survive a reboot. Fortunately, with the help of my favorite app ever... Automate, we now have a pretty decent method that even survives a reboot! Using Automate, we can await a keypress from the navigation bar and then launch any custom launcher of our choice!

There are, however, a few downsides, of course. For example, when opening an app that has a white background... it will appear as if the home button has vanished. This is a limitation of the method used, and we're looking into a workaround, but I'm afraid one might not be found... but we will see.

Anyway, along with the new activation method, there have also been some improvements to the tool itself. Firstly, as recommended by our good friend @blaacksheep, the "Enable widget Support" checkbox is now checked by default - because who doesn't widgets? Next, the decision to use the shell to re-route the home button for both Re-route and Downgrade methods has been reversed (it will now use cmd again). The reason for this is that it didn't really seem to be as effective as the cmd method. Finally, the method for reading FireOS version has been improved, and as a result the Toolbox is now capable of detecting what Launcher Activation Method is the best for your tablet and will select that method automatically.

Modify System Settings Has Been Modified!​

So, I promised a few folks I would add a subtool, that would make it easier to modify the tablet's overscan values. Well, in this update, I've decided to act on that promise! Firstly, I needed to figure out where this subtool would exist. I decided to create a new tab in the Modify System Settings tool just for the overscan... but then it occurred to me, that I could use this opportunity to create a display options tab and move a few of the existing "display" options to it. So, the tab was created, and the Display Timeout was moved to it firstly.

Now with this new tab, it was also decided that the Device Density tool would be also moved here instead of being its own tool. As a result, it's been removed from the Main Menu. Lastly, you'll find the Overscan option. From here, you can change both the portrait and landscape overscan values. Unfortunately, there isn't a way to retrieve the current overscan values by default. However, we can store a key in the settings database that will keep track of the overscan values changed by the Toolbox (it will not keep track of changed overscan values from outside the Toolbox) so that's good!

The last change in this tool is to the Device Dashboard Icon setting. Now, when you toggle it off, you'll be given the option to change the navigation bar's layout from 3 options: Default, Compact, and Android. This gives you greater control over how your navbar should look after the device dashboard icon is removed!

Device Detection is Now Dynamic!​

I've been noticing a few issues with Device Detection in the previous update. For whatever reason, it was detecting the device states wrong and was seeing a device when there really wasn't one. This has been addressed and should no longer occur. However, along with this change, the Toolbox's device detection has been improved in a certain manner that now allows it to detect device states dynamically. What I mean by this is, say you have a tablet plugged in, but the Toolbox is awaiting authorization... but then you unplug the device. In the past, the toolbox would still be awaiting authorization even though the tablet has been unplugged. Well, now when this occurs, the Toolbox is capable of seeing the device disconnect and will go back to the "no device" detected state. Pretty cool right? This works for authorization, no device, and too many devices detected.


Well, that's all the big highlights! But, that's not everything today's update has to offer! Feel free to check out the changelog below for more awesome changes!
Version 28.0

[ADB Shell]
• Improved some UI placements, and removed the select on hover for the output textbox.

[Main Menu]
• Improved detection of FireOS V7.3.2.2 and later.
• Reworked foreground user id obtainment.

[Custom Launcher]
• Added the "Custom Navbar Key" launcher activation method for tablets running FireOS 7.3.2.2 or greater.
• The best Launcher Activation Method for your tablet is now selected automatically.
• The Reroute and Downgrade activation methods now use the cmd sendkey method again. The shell method doesn't seem to be as effective.
• "Enable Widget Support" is now enabled by default.

[Google Services]
• Improved the messages that appear after a successful installation. Also added warnings about Google Accounts not being able to be removed, and Family Link/child profiles not working.

[Modify System Settings]
• A message is now shown when OTA Updates fail to disable on tablets running FireOS 7.3.2.2.
• When hiding the Device Dashboard Icon, you'll now be able to chose the layout of your navigation bar instead of the toolbox setting one for you.
• Added the "Display" tab, and moved "Display Timeout" to it.
• You can now change the overscan values in the Display tab.

[Device Detection]
• Fixed an issue with device detection logic that would read the "no devices attached" status incorrectly. This prevented the No Device window from appearing under the correct circumstances.
• Device Detection is now capable of detecting the device's state dynamically.

[Density Modifier]
• Has been moved to a subtool in the Modify System Settings Display tab, and removed from the Main Menu.
Ready to download V28.0? Well, be sure to drop by the Downloads' section of the OP and get you either the installer or the archived version! However, if you have a previous version of the toolbox installed, you could also update using the Toolbox's built-in updater!

As always guys, I want to thank you all from the bottom of my heart for being such amazing people! I feel blessed to be a part of a community as great as this one! Thank YOU all for the support, donations, and kindness you guys continue to show! The respectful nature, and the helpfulness of everyone is just so overwhelming! THANK YOU guys! :D

I'd also like to THANK our good friend @blaacksheep for being such a great friend and helping out the community as much as he does! I mean, the post where he shared his workarounds for the FireOS 7.3.2.2 issues is really amazing, and I can't thank him enough for it! You rock, my friend! :D

Before this post ends (I know it's a little long as is, but please bear with me) I'd like to give an update on the Python port. Been working on it a lot as of late and have made some pretty decent progress. I would like to state now that this will be the last update to the VB version of the Toolbox for a while, so I can focus all my attention on the port. Remember, I'm updating the port progress page as I go, so keep an eye on it if you'd like to keep updated with the progress. I may have a public test build coming up soon.. well have to see. But just thought I should let you guys know what's going on.

Well, that's all I've got for now! I sincerely hope you guys enjoy the update, and until next time guys... Peace! ✌️
 

blaacksheep

Senior Member
Jun 20, 2020
960
532
Buffalo
Wow, thanks for the quick response! Unfortunately I've tried that and no luck. I did get the 'revoke access to USB debugging' dialogue message box come up and hit OK but still no dialogue box to authorize the device. When the device is plugged in it does show up as being attached in the ADB status box within the toolbox. Any other options or do I just need to write this off as one of those things?

I noticed that on my HD8 (2020) that the tablet has to be connected as a camera for ADB and Toolbox to function. On my HD10 (2019) it didn't matter and I left it connected as a media device.

Try connecting your device, swiping down once and look for "System . Connected as *" . Tap it, and change it to Camera. That might get you going.

Oh, and welcome to XDA!:)
 

TrentFTW

New member
May 29, 2022
1
2
Hello! I have been using this tool for a couple years, amazing work. On V 28.0 when I use the Custom Launcher option and try to install Nova, I get an error that says, "Hmm, it seems Automate failed to install! The reason for failure is: Performing Streamed Install." Now it looks like my home button does not work and the program won't let me use the "Restore Fire Launcher" option. Any help would be appreciated.

Thanks!

Edit: Installed automate manually. It works now. Thanks!
 
Last edited:

manyxda

Member
Dec 29, 2021
43
29

The Return of Custom Launchers and Other Improvements!​

So, as you guys may know, it's been pretty difficult to use third party launchers ever since FireOS 7.3.2.2 dropped. We had a workaround, but it was ideal and wouldn't survive a reboot. Fortunately, with the help of my favorite app ever... Automate, we now have a pretty decent method that even survives a reboot! Using Automate, we can await a keypress from the navigation bar and then launch any custom launcher of our choice!
This made my weekend! Thanks very much!

Observations on the install process (for anybody similarly situated as I am)

- When installing v28 (as well as v27 before) I had to disable my antivirust (Avast) and firewall (Comodo). Otherwise, way too many questions from the firewall.

- Version 28 recommended "Install for all users" (unlike v27, which I believe recommends "Install only for me"). On "Install for all users," however, v28 would not start. I had to uninstall and choose "Install only for me." (I was logged into Windows as a standard user if that makes a difference.)

- When, after an install, you choose to go a "tour," you only get to see the "tour" window and not the "main" and no obvious way to say, "Okay I am done." You just have to dismiss the "tour" (click the top-right "x"), and the "main" pops up. (I got stumped here with v27 and again this time. Maybe there is nobody else clueless as I am.)


I deleted my plea for help on "Custom Launcher" because TrentFTW (above) already reported the same thing. I was just being stupid not to read what others had to say.
 
Last edited:

Datastream33

Senior Member
Sep 17, 2017
2,179
1,793
Hello! I have been using this tool for a couple years, amazing work. On V 28.0 when I use the Custom Launcher option and try to install Nova, I get an error that says, "Hmm, it seems Automate failed to install! The reason for failure is: Performing Streamed Install." Now it looks like my home button does not work and the program won't let me use the "Restore Fire Launcher" option. Any help would be appreciated.

Thanks!
I apparently screwed up in the pathing location for the Automate apk. Working to release a fix asap! Thank you for bringing this to my attention!
 
  • Like
Reactions: manyxda

manyxda

Member
Dec 29, 2021
43
29
I apparently screwed up in the pathing location for the Automate apk. Working to release a fix asap! Thank you for bringing this to my attention!

Thank you very much. I believe the "Restore Fire Launcher" option would also be independently valuable.

On Automate's navbar buttons not showing against a white background, I notice that Amazon's stock navbar buttons also have poor visibility against the same (e.g. RD Client, aka Microsoft Remote Desktop), almost invisible. I wonder Automate could be worse. Anxious to find out when the fix comes out.
 
Last edited:
  • Like
Reactions: Datastream33

westhamtim

New member
May 28, 2022
3
2
I noticed that on my HD8 (2020) that the tablet has to be connected as a camera for ADB and Toolbox to function. On my HD10 (2019) it didn't matter and I left it connected as a media device.

Try connecting your device, swiping down once and look for "System . Connected as *" . Tap it, and change it to Camera. That might get you going.

Oh, and welcome to XDA!:)
Thanks also for the response. I've played around with this but still no luck.

Interestingly I've now installed v28 and the error message I get is slightly different, it now says "unauthorized transport_id:1". Don't know if that's helpful...??

And just noticed that when I close down the toolbox I get a dialogue box telling me "Failed to obtain the tablet's generation info"
 
Last edited:

seraph973

Member
Aug 13, 2011
5
1
my fire auto updated to 7.2.2.3 the other day. i tried the DNS66, followed all instructions and i still see ads on my lockscreen.
 

Datastream33

Senior Member
Sep 17, 2017
2,179
1,793
Ok, so I've updated the links in the OP to point to the new fixed version... V28.1. This update includes fixes to Automate failing to install due to an incorrect pathing to the Automate apk and a few other improvements:
Version 28.1

[Custom Launcher]
• Fixed incorrect pathing for the Automate apk which was causing installation to fail.
• Fixed the error message not displaying properly when Automate fails to install.
• Added the ability to "Restore Navigation Bar" to the Tool Options.

If you had troubles with Automate failing to install with Toolbox V28.0, please update to V28.1, open the Custom Launcher tool, click the ":" icon at the upper right, and from the Tool Options click "Restore Navigation Bar".

After this, it should now work as expected. So sorry for the screw-up! My sincerest apologizes!
 
  • Like
Reactions: manyxda

manyxda

Member
Dec 29, 2021
43
29
Ok, so I've updated the links in the OP to point to the new fixed version... V28.1.

Thanks so much!

OP still says "V28.0," but when you click "Download" you get V28.1.

"Restore Fire Launcher" works!

But "Custom Navbar Key" still does not on m HD10.

I get this popup on the desktop.

Picture 1
1.jpg


Followed by a popup on HD 10 with "CANCE" and "IMPORT." (One time I ignored as I was not to interact with the touch screen; the next time I clicked "IMPORT.")

Then the following on the desktop.

Picture 2
2.jpg


But nothing shows up on either desktop or tablet that asks me to "Accept" anything.

As for the poor visibility against white, this is what I've found out. Amazon's stock buttons are not white but a light gray. Therefore when the background is actually white, the buttons become dark gray (dark by contrast with white). This happens on Google Play Store app. But when the background is the same or near shade of gray as the buttons, they become (totally or near) invisible. This happens on RD Client (aka Microsoft Remote Desktop). If this is true, the new buttons (those I am supposed to get from "Custom Navbar Key") should *not* compare unfavorably with stock on visibility (they just do poorly in different regions of shades). By the way on many apps, the stock buttons seem to retain a thin strip of black background of their own. (The two apps mentioned above are exceptions, in which the strip vanishes.) Sorry that was a ramble. Hope it made sense.
 
Last edited:
  • Like
Reactions: blaacksheep

Blinker7

Member
Oct 11, 2012
11
1
Hi guys,
I am thinking about getting Fire HD 10, the one from 2019. Now, I know it's not really powerful machine and I don't expect it to run some productivity apps and AAA games, just basic. I am student so I will mainly use it for Office apps (Word, Outlook etc), view pdfs and that stuff + some easy games just to pass the time.
Now, my question is, how good is combability when you install Play Store, like did it happed that you can't install something from the store? Did you have any problems, from your experiences?
 
  • Like
Reactions: blaacksheep

blaacksheep

Senior Member
Jun 20, 2020
960
532
Buffalo
Thanks so much!

OP still says "V28.0," but when you click "Download" you get V28.1.

"Restore Fire Launcher" works!

But "Custom Navbar Key" still does not on m HD10.

I get this popup on the desktop.

Picture 1
View attachment 5625521

Followed by a popup on HD 10 with "CANCE" and "IMPORT." (One time I ignored as I was not to interact with the touch screen; the next time I clicked "IMPORT.")

Then the following on the desktop.

Picture 2
View attachment 5625523

But nothing shows up on either desktop or tablet that asks me to "Accept" anything.

As for the poor visibility against white, this is what I've found out. Amazon's stock buttons are not white but a light gray. Therefore when the background is actually white, the buttons become dark gray (dark by contrast with white). This happens on Google Play Store app. But when the background is the same or near shade of gray as the buttons, they become (totally or near) invisible. This happens on RD Client (aka Microsoft Remote Desktop). If this is true, the new buttons (those I am supposed to get from "Custom Navbar Key") should *not* compare unfavorably with stock on visibility (they just do poorly in different regions of shades). By the way on many apps, the stock buttons seem to retain a thin strip of black background of their own. (The two apps mentioned above are exceptions, in which the strip vanishes.) Sorry that was a ramble. Hope it made sense.

It may have completed successfully. Open up your app drawer and tap Automate. Now follow the instructions from your last screenshot.
 
  • Like
Reactions: manyxda

Top Liked Posts

  • 1
    I recently upgraded from my Fire HDX the 2022 version of the Fire 7 tablet, which is running Fire OS 8.3.1.1, and was looking for a way to remove built-in apps (I know you cannot completely remove the apps Amazon pre-installs on Fire tablets but I want to hide Goodreads, Audible, and Freevee, if possible).

    I was trying to use Fire Toolbox and got the message in the attached print screen, which I'm assuming has something to do with Fire Toolbox not being updated for new Fire tablet versions but I am not 100% sure.

    I am wondering if Fire Toolbox will work for Fire OS 8 at some point in the future or there is some workaround I can use now to get it to work?

    Fire Error.png
    1
    I'm assuming has something to do with Fire Toolbox not being updated for new Fire tablet versions but I am not 100% sure.
    More than likely yes. You can check the devices supported on page 1 of this thread. I don't see anything from 2022 listed. Datastream33 is the developer of the toolbox. He would have to get his hands on any new devices (I assume) before they are supported.
  • 3
    I'd like to sincerely apologize to everyone. I know i said i'd release a micropatch later that day. However, when i posted that i didn't know i'd lose power due to the winds all day yesterday. Apparently a tree branch hit the line and knocked it out.

    Staying with my patents until its fixed. Again, i'd like to apologize for not keeping my word. 😞

    On a lighter note, hope everyone has a GREAT father's day! :D
    2
    Wow! That laptop is just a young kid compared to my daily-use machine. (I'm on a 2013 HP workstation with a Core2 Duo.)

    To me, it looks like Toolbox attempts to start up ADB and fails without a proper notification. That suggests download file corruption. I would try downloading the portable (.zip) version and setting it up in a temp folder. If the portable version runs, then you just need to replace your installed version.

    Let us know what you find. 👀

    Edit: See what @manyxda said above. I'd forgotten about that!
    I agree with you that it's likely due to issues with adb.
    With the portable version you mean a portable version of the adb driver? I'm confused. If you're talking about the tollboox, I indeed downloaded the exe, not the archive.

    (I've already had replied to manyxda's post above before seeing yours - as said there, the laptop has access to the web.)
    2
    I'm currently trying to get the Toolbox installed on my Lenovo X270 laptop. To me it looks like it's having difficulties at installing adb and I'm stuck here:
    View attachment 5628729
    I've tried it several times, the last try with Windows' Firwall and Virus Scanner disabled but still without any success.

    Sure, the Laptop is from 2017 and only sporting an Intel i5 7300U so it's not the fastest but that shouldn't be a reason for it not to work at all.
    Any suggestions?

    Wow! That laptop is just a young kid compared to my daily-use machine. (I'm on a 2013 HP workstation with a Core2 Duo.)

    To me, it looks like Toolbox attempts to start up ADB and fails without a proper notification. That suggests download file corruption. I would try downloading the portable (.zip) version and setting it up in a temp folder. If the portable version runs, then you just need to replace your installed version.

    Let us know what you find. 👀

    Edit: See what @manyxda said above. I'd forgotten about that!
    2
    I'm currently trying to get the Toolbox installed on my Lenovo X270 laptop. To me it looks like it's having difficulties at installing adb and I'm stuck here:
    Fire Toolbox.jpg

    I've tried it several times, the last try with Windows' Firwall and Virus Scanner disabled but still without any success.

    Sure, the Laptop is from 2017 and only sporting an Intel i5 7300U so it's not the fastest but that shouldn't be a reason for it not to work at all.
    Any suggestions?
    2
    I'm currently trying to get the Toolbox installed on my Lenovo X270 laptop. To me it looks like it's having difficulties at installing adb and I'm stuck here:
    View attachment 5628729
    I've tried it several times, the last try with Windows' Firwall and Virus Scanner disabled but still without any success.

    Sure, the Laptop is from 2017 and only sporting an Intel i5 7300U so it's not the fastest but that shouldn't be a reason for it not to work at all.
    Any suggestions?

    I had that same problem when I tried to use the Toolbox without Internet. My notes go like this:

    QUOTE. Give computer Internet access. Otherwise, on starting Toolbox (for the first time after install), you will see a popup with, "The Toolbox is starting the Android Debug Bridge (ADB) and setting up the environment. Once this process is completed the Toolbox will start." > The popup stays up indefinitely (no sign of Toolbox main window). > Manually closing popup gives a Toolbox main window with no content (all white). UNQUOTE
  • 308

    ═══════════════════════════════════
    Fire Toolbox V28.1

    All-In-One Toolbox for Fire Tablets!
    ═══════════════════════════════════


    FTBV26.1.PNG

    Introduction.png


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

    Compatibility.png


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

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

    • OTA Updates - OTAs can no longer be disabled.
    • Lockscreen Ads Remover - Ads can no longer be removed from the lockscreen.
    • 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 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 - 2021) Guide:
    Before purchasing the tablet:
    • Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)

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

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

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

    ToolsSubtools.png


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

    Downloads.png


    Toolbox:
    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V28.1​
    Post
    Link​

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

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

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

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

    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

    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.
    31
    I'd also like to take the time to acknowledge today as a very special day for this project! Today marks the 3RD YEAR anniversary of the project!!! 😄 🎉🎉

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

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

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

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

    HERE'S TO THE TOOLBOX'S 3RD YEAR ANNIVERSARY!! 👏:D
    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! ✌️
    20
    Well, I guess it's finally time to explain myself. You see, ever since Christmas I've been mostly radio silent. Well, this is attributed to Covid running rampant in my parent's household after Christmas. My whole family besides a few were infected (myself included) with the Omicron variant. We are just barely coming out of it, and life is slowly going back to normal. Just wanted to let you guys know where I've been, as I've seen comments (not on this forum) stating that the project is dead, and I've given up on it... that is simply not true. We will press on, and development should start moving forward once more! Again, thank you to @Falcon342, and @blaacksheep for carrying the torch as always! I do appreciate it! :D