[WINDOWS][TOOL]Fire Toolbox V28.1

Search This thread

mspa

New member
May 20, 2022
4
5
Thanks for your detailed reply, I wiped the cache (twice), unfortunately the update is still showing as ready to install. I've restarted the tablet, through the Recovery menu, and it hasn't installed (yet), so there's hope at least...
I wonder would doing a factory reset get rid of it?
 

Datastream33

Senior Member
Sep 17, 2017
2,179
1,794
Thanks for your detailed reply, I wiped the cache (twice), unfortunately the update is still showing as ready to install. I've restarted the tablet, through the Recovery menu, and it hasn't installed (yet), so there's hope at least...
Hmm, the ota file could be in numerous places. However, they usually put the update on the root of the internal storage, but hide it from view. Try executing an ADB Shell from the Toolbox's main menu and let us know the output of the following command:
Code:
ls -a
 

Datastream33

Senior Member
Sep 17, 2017
2,179
1,794
Hmm, the ota file could be in numerous places. However, they usually put the update on the root of the internal storage, but hide it from view. Try executing an ADB Shell from the Toolbox's main menu and let us know the output of the following command:
Code:
ls -a
So, I did some research, and it looks like the updates are stored in: /data/ota-package/. Might not be able to delete the update due to not having the proper permissions. Perhaps, a factory reset is the best way to go in this situation... :(

EDIT: Hmm, maybe we don't want to factory reset either... if the update hasn't installed already, it's waiting for the user to manually start the update due to automatic updates being disabled. A factory reset may enable automatic updates and starting installing the update... hmmm...

Maybe try clearing the Storage for System Updates (both entries in Settings), DeviceSoftwareOTA, and also for Download Manager.
 
Last edited:

blaacksheep

Senior Member
Jun 20, 2020
967
535
Buffalo
So, I did some research, and it looks like the updates are stored in: /data/ota-package/. Might not be able to delete the update due to not having the proper permissions. Perhaps, a factory reset is the best way to go in this situation... :(

EDIT: Hmm, maybe we don't want to factory reset either... if the update hasn't installed already, it's waiting for the user to manually start the update due to automatic updates being disabled. A factory reset may enable automatic updates and starting installing the update... hmmm...

I don't think a factory reset does an update first, but he could do it from recovery to be sure. ??
 

Datastream33

Senior Member
Sep 17, 2017
2,179
1,794
I don't think a factory reset does an update first, but he could do it from recovery to be sure. ??
My bad, what I'm saying is... if the device is factory resetted, but the update file isn't removed in the reset process it could start auto installing the OTA. I believe the update isn't auto installing right now is because Automatic Updates has been disabled. So by resetting it, it would return that flag to default and could auto-install the OTA before Automatic Updates can be toggled off again.
 
  • Like
Reactions: blaacksheep

blaacksheep

Senior Member
Jun 20, 2020
967
535
Buffalo
My bad, what I'm saying is... if the device is factory resetted, but the update file isn't removed in the reset process it could start auto installing the OTA. I believe the update isn't auto installing right now is because Automatic Updates has been disabled. So by resetting it, it would return that flag to default and could auto-install the OTA before Automatic Updates can be toggled off again.
Just a thought. I hadn't considered the mechanism of the update process. You're probably right.
 

manyxda

Member
Dec 29, 2021
43
29
I just got a Fire HD 8 (inch) Generation 10 (2020) (hereinafter "hd8-g10") i.e. the latest HD 8, and notice that its screen is different from that of HD 10 Gen 11 (2021) ("hd10-g11"):

- On hd10-g11, the actual display area and the border around it are the same black color.
- On hd8-g10, actual display is a gray framed by a black border.
- As a result, hd8-g10's display area is lighter (less black) than that of hd10-g11.

Is this something I should expect of an hd8-g10, or did I receive a defective instance of hd8-g10?

If this is as should have been expected, I would urge anyone reading this to avoid getting an hd8-g10.

(At least the HD 8 was firmware 7.3.1.7. I got it on eBay.)
I am sorry to be quoting my own earlier comment, but I am supplementing it with a picture. In it you will see that my new HD 8's screen is positively gray next to the blackness of my HD 10. The eBay vendor claims that this grayness is normal to HD 8. What is the truth? If anybody has both HD 8 and HD 10, please tell me whether they show the kind of difference as shown in the picture. If you have an HD 8, does it show such a strong contrast between (gray) actual display vs. (black) border?

20220520_151753.jpg


ADDED LATER:

I did some looking and was able to confirm that the grayness is normal to (or at least prevalent in) HD 8. See the video clips below. My HD 8 behaves much as do those in the clips.

Note: when the screen is gray it will give to all colors a faded look unless you are using the device in darkness.

Therefore if you care about accuracy of color reproduction in all lighting conditions, here seems to be a reason you should choose an HD 10 over HD 8.

I am sorry the links blew up into what you see and take up much room.




The link below is of HD 8 9th gen (2019) or earlier and so is not directly on point, but shows the grayness best.

 
Last edited:

mspa

New member
May 20, 2022
4
5
So, I did some research, and it looks like the updates are stored in: /data/ota-package/. Might not be able to delete the update due to not having the proper permissions. Perhaps, a factory reset is the best way to go in this situation... :(

EDIT: Hmm, maybe we don't want to factory reset either... if the update hasn't installed already, it's waiting for the user to manually start the update due to automatic updates being disabled. A factory reset may enable automatic updates and starting installing the update... hmmm...

Maybe try clearing the Storage for System Updates (both entries in Settings), DeviceSoftwareOTA, and also for Download Manager.
I've cleared the storage as instructed, and can happily report the update is gone :D
Thanks again for your help!
 

blaacksheep

Senior Member
Jun 20, 2020
967
535
Buffalo
Hi. and welcome to XDA!

That could happen if the Toolbox downloaded a corrupted file. (Go figure!) The easiest way to fix it is to right-click on your Toolbox desktop icon and select Open File Location. (The wording might be slightly different in Windows 10/11.) In that folder, double-click the "bin" folder. Now double-click the "Google Services" folder. Delete everything in there. Toolbox will download it again on the next try. Close your file browser and try installing Google Services again. Hopefully it will work this time. :)
 

manyxda

Member
Dec 29, 2021
43
29
Now Launch Activity Launcher. Tap the magnifying glass in the upper-right. Enter "VPN". One setting should appear called "VPN".

What is the effect of manually turning off DNS66 if it is set to "Always on VPN" in Activity Launcher?

Will Activity Laucher go, "Some fool turned that off. I'll turn it back on," do it?

I ask the question because I have the same Amazon servers blacklisted in my router. While at home, therefore, I may not want a double blocking by DNS66, which may be a hit on battery or speed.

If Activity Launcher will countermand a manual action (as above), then on coming home I am looking at two things to turn off: DNS66 and Activity Launcher. Of course this would mean turning two things on when going out.

In the unlikely event that Activity Launcher can distinguish DNS66 (somehow) quitting on its own vs. a person turning it off, then Activity Launcher can stay on all the time and I get to turn only one thing on and off (DNS66).

Or maybe the hit on battery and speed is negligible in your experience? In this case, I may just keep DNS66 all the time. (This "on and off" thing may just be the way to get my tablet to update again because one day I may forget.)
 
  • Like
Reactions: blaacksheep

blaacksheep

Senior Member
Jun 20, 2020
967
535
Buffalo
What is the effect of manually turning off DNS66 if it is set to "Always on VPN" in Activity Launcher?

Will Activity Laucher go, "Some fool turned that off. I'll turn it back on," do it?

I ask the question because I have the same Amazon servers blacklisted in my router. While at home, therefore, I may not want a double blocking by DNS66, which may be a hit on battery or speed.

If Activity Launcher will countermand a manual action (as above), then on coming home I am looking at two things to turn off: DNS66 and Activity Launcher. Of course this would mean turning two things on when going out.

In the unlikely event that Activity Launcher can distinguish DNS66 (somehow) quitting on its own vs. a person turning it off, then Activity Launcher can stay on all the time and I get to turn only one thing on and off (DNS66).

Or maybe the hit on battery and speed is negligible in your experience? In this case, I may just keep DNS66 all the time. (This "on and off" thing may just be the way to get my tablet to update again because one day I may forget.)

Activity Launcher is just a means of calling already installed activities or apps. It's used because there is no provided means of accessing those activities without ADB or another program.

I hadn't actually checked what would happen if you turn off DNS66 when it was set as Always On VPN until I read your post. :unsure: It turns out that if you do turn off DNS66 with that setting on, it just gives you a notification on the Notification Bar. 🤨 It doesn't actually stop any traffic from going through. Only the other switch below Always On VPN does that, but that doesn't play well with Amazon or DNS66 and stops all traffic. ☹️ I guess you can leave Always On VPN turned off.

DNS66 is a low resource program and probably saves more battery than it uses by blocking extra traffic and stopping the rendering of ads. All it does is intercepts any DNS lookups and if they are on it's lists it returns 127.0.0.1 (localhost) as the numeric address for the DNS lookup where they go unanswered. The app or browser gets no response from that address so it cant connect with the intended ad server or update server. The process fails. Having an extra block on your router or a PiHole won't matter because they'll never get the request as it's been locally redirected to a dead end.

I don't recommend turning off DNS66. It might be your only defense against further updates if you are on someone else's WiFi. It most certainly isn't a bottleneck as far as speed goes. It runs on all my android devices except my phone while I'm using a real VPN. As a matter of fact, it's one of the first apps I install on any device I use just for the ad blocking. :)

Edit: Thanks, @manyxda for bringing this up and making me revisit the usefulness of Activity Launcher in this case. It turns out not to be needed and I've edited my tutorial post to reflect that.☺️
 
Last edited:
  • Like
Reactions: manyxda

mdb301

Member
Mar 11, 2022
7
3
Does anyone know when fire is 8 will come out and if there will be any big features? I was just curious.
 

Datastream33

Senior Member
Sep 17, 2017
2,179
1,794
Does anyone know when fire is 8 will come out and if there will be any big features? I was just curious.
Looks like it's available for purchase on June 29. The best thing about the new tablet in my opinion is it's the first Amazon tablet with Android 11 (we'll have to see how locked down they are on release). So, that's pretty cool. Although, comparing it the Fire HD 8 (2020) I believe the new tablet is weaker.
 

mdb301

Member
Mar 11, 2022
7
3
Looks like it's available for purchase on June 29. The best thing about the new tablet in my opinion is it's the first Amazon tablet with Android 11 (we'll have to see how locked down they are on release). So, that's pretty cool. Although, comparing it the Fire HD 8 (2020) I believe the new tablet is weaker.
I’m sorry my autocorrect made it say “is” instead of os. I meant the operating system update.
 

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?

    View attachment 5649635

    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.
    Greetings!

    I don't believe the 2022 models are supported by the current release. However, if you could be kind enough to help out by sharing the device's build.prop file, we can ensure support is quickly added.

    The build.prop file can be obtained manually through the use of the "adb shell getprop>buildprop.txt" command or through the use of the GetProp tool (attached as a .zip to this post). The tool is a simple .bat file (you can even view the source code) and will automatically pull the buildprop for you.

    If you could be so kind as to send me the build.prop via a PM that would help out immensely!
    1
    I want to update from 7.3.1.9 to 7.3.2.1

    My HD10 is crashing a lot when showing videos, so I thought I would try to update the f/w to try to understand if it is a hardware issue or not.

    I have a copy of the 7.3.2.1 installer.

    I am running V25.2 version of the Fire Toolbox since 12/2021

    My question is should I uninstall any of the toolbox modifications before I run the updater.

    I know I will need to be careful right after the update to make sure I don't get updates pulled before I get the toolbox connected up again.

    Also what is the best version of the toolbox for 7.3.2.1? I read that V28 has some launcher options removed.

    Thanks a lot in advance - I did try to find what to do in this thread, but it is very long - Mark
    1
    Mannnn... I didn't know we have a problem with 7.3.2.2. I just bought my HD10 and it automatically updated. I didn't know... Should have stopped it when I had a chance... ugh! Can I downgrade it?

    Apparently, 7.3.2.2 was released in November 2021. I guess I'll have to wait for the rest of the year and MAYBE the Toolbox will have some ways to bypass the issues by that time...
    1
    Mannnn... I didn't know we have a problem with 7.3.2.2. I just bought my HD10 and it automatically updated. I didn't know... Should have stopped it when I had a chance... ugh! Can I downgrade it?

    Apparently, 7.3.2.2 was released in November 2021. I guess I'll have to wait for the rest of the year and MAYBE the Toolbox will have some ways to bypass the issues by that time...

    Hi and welcome to XDA!

    The biggest problem of the launcher replacement being blocked has been addressed in the latest Toolbox version. For the other problems, see the post in my signature for a starting point. :)
    1
    Hi and welcome to XDA!

    The biggest problem of the launcher replacement being blocked has been addressed in the latest Toolbox version. For the other problems, see the post in my signature for a starting point. :)

    Thanks for your reply. You meant the Custom Navbar Key in Toolbox version 21 right? For the custom Launcher, I am using that to launch Nova Launcer.

    Although sometimes when I tap "Back" or "Recent App". It pops back to the Amazon launcher :) So a little problematic but I guess that's the best we have at the moment.
  • 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
    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
    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 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
    Interesting. The behavior you're describing in quotes matches exactly what happens on my screen with one major difference: My laptop does have access to the internet via wifi. In fact I wrote my last comment on it.

    I've fixed the new tablet on the PC by now but only because I didn't have the time to mess around another hour to get tollboox installed on the laptop.
    I've even followed the description here to manually install drivers but still without any success in getting tollboox installed.

    So still, if anyone has any idea how to get tollboox running on my old trusty Win 10 Pro Laptop then any help is appreciated.
  • 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