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

Search This thread

Unipac

Senior Member
Mar 20, 2009
57
5
Not sure why Amazon has not listed a specific f/w for 12th Gen HD8 Plus.

The bin file from the .de site is the same as on the .us one. However, I copied it into the root of "internal storage" and thought If I hit "check for updates" in the "About" section it would find it... but it didnt. So I took the risk, did a factory reset and searched for OTA Updates . the 8.3.1.3 was available (not the .4) so I installed that. Now everything works fine for now with the Google Play Store. Difference was that b/c I connected to wifi, I registered the Fire tablet right before doing anything else.

Thanks for the help!
 

Jumbo100

Senior Member
Jul 21, 2022
562
416
Thanks for keeping us updated ... glad everything worked out.

Confirms Google Play is stable on Fire HD 10 8Plus with f/w 8.3.1.3

Your risk assessment was correct; risk of installing OTA update in much less than the risk of installing incompatible software.

Still curious that Amazon hasn't posted f/w 8.3.1.3 update download for 12th Gen HD8 Plus tablets.

* Edit * correct HD10 ref to HD 8
 
Last edited:

Jumbo100

Senior Member
Jul 21, 2022
562
416
Where can I find the FireHD 10 FW 8.3.1.3?
Sorry ... weekend "brain fog" typo. 😖

Fire HD10/HD 10 Plus tablets still running FireOS 7. Waiting expectantly for 12th Gen HD10 rollout this Spring (?) ... most likely with the then-current version of FireOS 8. Hopefully it will still be as accommodating for Goggle Play and FTB mods as f/w 8.3.1.3
 
Last edited:

Jumbo100

Senior Member
Jul 21, 2022
562
416
ReVanced ... revisited

For those considering ReVanced (the successor to late, lamented YouTube Vanced), @Retrial has written a great thread with detailed installation guides and "unofficial" APKs for easy "no root" installations, for those of us who are "coding challenged".


Recently tried out the ReVanced and ReVanced Extended .apks on 11th Gen Fire HD10 (2021). On first inspection, both appear to be working well. Nice adjuncts to Fire Toolbox mods.
 
Last edited:

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
ReVanced ... revisited

For those considering ReVanced (the successor to late, lamented YouTube Vanced), @Retrial has written a great thread with detailed installation guides and "unofficial" APKs for easy "no root" installations, for those of us who are "coding challenged".


Recently tried out the ReVanced and ReVanced Extended .apks on 11th Gen Fire HD10 (2021). On first inspection, both appear to be working well. Nice adjuncts to to Fire Toolbox mods.
Ah, Revanced... so crazy to see how far it's come along. :D A very good guide you found there indeed. (y)
 
  • Like
Reactions: Jumbo100

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
FireOS 8.3.1.3 can still be manually downloaded at https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
but that can change at any moment. You've been warned.

Does anyone know of any tool that can extract apk files from an OpenGApps zip download?

I've been spelunking around XDA trying to find any such tool but with no luck.

I found one of questionable charactor (i.e. malware) for editing ROMs such as for LineageOS but but doesn't seem to work with an OpenGApps zip file.
You're talking about the zips you can download from this website right? If so, I can open the zip files in Ark pretty easily. Is there any specific app you're looking for? I could extract it and send it your way if you'd like?
 

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
I had the honor of being sent a test compilation of the port. For the most part, it's working fully. Some things need some attention, but all in all he's done a great job. I haven't heard back since I reported what I found. I don't know if I was too picky about things or if I didn't tell him anything he didn't already know. I hope he gets inspired enough to release an alpha version sometime soon.
@blaacksheep words cannot express just how helpful you've been during the testing phase! The reports were eye opening and really helped catch some issues I would of missed. Again, thank you so much for taking the time out of your day to help test the port! :D(y)

Progress has been going along quite rapidly. Fixed all the issues you kindly reported, and just recently got the Welcome Screen, Splash screen, Setup Tour, ADB Start screen, etc finished. All that's left is the Updater and then it should be ready to be tested one last time before public release. I'm excited! Can't wait to share with you all what we've been cooking! :D
 

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
Got a Fire HD with 7.3.2.4

Is there hope that the default Launcher can be disabled in the future or can I safely discard this into the trash?
I can't say for certain. There could be something we're missing, but as of now there is no way to disable Fire Launcher on FireOS 7.3.2.2+. Perhaps something can be found, and perhaps not. Only time will tell...
 
  • Like
Reactions: ItsZuri

ItsZuri

Member
Feb 5, 2023
12
6
HAHHAHA, fair enough. I suppose you wern't looking for a cryptic answer?
lol, it sounds crass but I literally have no use of it without a different Launcher. The Workaround doesn't really work that well right now since the Fire Launcher shows up a lot and there is also this weird delay. Fire Launcher is just a hot mess. So Yeah. It's glorified electrotrash right now for me.

I appreciate the help :)
 
  • Like
Reactions: Datastream33

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
lol, it sounds crass but I literally have no use of it without a different Launcher. The Workaround doesn't really work that well right now since the Fire Launcher shows up a lot and there is also this weird delay. Fire Launcher is just a hot mess. So Yeah. It's glorified electrotrash right now for me.

I appreciate the help :)
Yeah, the workarounds are a pain to deal with. Just out of curiosity, which workaround were you using?

By the way, I see you just registered today. Welcome to XDA my friend! :D
 
  • Like
Reactions: ItsZuri

ItsZuri

Member
Feb 5, 2023
12
6
Yeah, the workarounds are a pain to deal with. Just out of curiosity, which workaround were you using?
I'm just using the Toolbox one? It Installs Nova/Lawnchair fine and Automate as well but Automate seems really slow and it's annoying that it often switches to the Fire Launcher for me. I can't set either of them as a default so they show up as an opened App and Automate is too slow to catch up for me.
 

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
I'm just using the Toolbox one? It Installs Nova/Lawnchair fine and Automate as well but Automate seems really slow and it's annoying that it often switches to the Fire Launcher for me. I can't set either of them as a default so they show up as an opened App and Automate is too slow to catch up for me.
Just curious as to what activation method was used. I'm going to guess it was the Shortcut Launcher?

Anyway, sorry to hear Automate under performed. Our biggest problem has always been a lack of RAM on the tablets. :(
 
  • Like
Reactions: ItsZuri

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
No need to be sorry. 4GB isn't enough? Also I picked the default option. Is there something better?
Ah, you have the 4GB model? I was thinking of 10th gen and below which had 2 to 3GB.

The quickest activation method would be the Custom Navbar. It modifies the navbar to start the launcher on home key press. Doesn't rely on Fire Launcher to be in the foreground like the Shortcut Launcher does. Of course, it has it's drawbacks... the button can be harder to see in light apps, and media apps can consume the keypress. But overall, it would probably suite you better if Fire Launcher is something you loathe.

Sorry I would provide a screenshot, but I just had to recently re-install my OS and don't have the windows VMs setup yet.
 

ItsZuri

Member
Feb 5, 2023
12
6
Ah, you have the 4GB model? I was thinking of 10th gen and below which had 2 to 3GB.

The quickest activation method would be the Custom Navbar. It modifies the navbar to start the launcher on home key press. Doesn't rely on Fire Launcher to be in the foreground like the Shortcut Launcher does. Of course, it has it's drawbacks... the button can be harder to see in light apps, and media apps can consume the keypress. But overall, it would probably suite you better if Fire Launcher is something you loathe.
Pretty sure thats the default pick and yeah it didnt work well for me. The button doesnt work at all in apps and I have to hit the square button first and then the circle works.

Also it often swaps to the Fire Launcher when closing everything.
 

Datastream33

Senior Member
Sep 17, 2017
2,503
2,205
Pretty sure thats the default pick and yeah it didnt work well for me. The button doesnt work at all in apps and I have to hit the square button first and then the circle works.

Also it often swaps to the Fire Launcher when closing everything.
Is the Launcher Invoker flo running in Automate? The homekey wont work without it.
 
  • Like
Reactions: ItsZuri

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    New Platform, Who 'Dis?​



    How's it going guys?

    I sincerely hope everyone had a fantastic weekend, and all the mothers out there had a fantastic Mother's Day!

    I've got something so exciting to share with you, and I can't wait to share all the details! So, let's not dilly dally and jump right into the announcement!


    🎉🎉🎉The Linux Python port is finally ready to be released!! 🎉🎉🎉

    pyftb_V1.0_beta.png
    I'm so excited to finally share the port with you all! So, in true fashion, let's get started with the port background!

    The Extremely Interesting Port Background​

    For the longest time, the Toolbox has been a Windows only application. As you all know, it started out as a simple batch file and then was shifted to Visual Basic back in 2020. In the Visual Basic announcement post, I stated that I'd code the Toolbox in a way that would allow it to run under Wine for those of you who were running Linux. Well at the time I knew nothing about Linux, and was naive to think that I could just change code around and it would magically run on Linux easy peasy. Surprise, surprise it wasn't that easy! So, the Linux port was thrown on the back burner.

    A year or so later I started learning Linux, and fell it love with it. I decided to take my new experience and run with it. So, I started looking into ways I could port the Toolbox to Linux. I tried so many different methods, but none of them stuck with me. I had the problem of building up a prototype but then dumping it in exchange for trying something new. This is partially why it took so long for the port to be released, could never settle on just one platform.

    Some time in 2022, I came across PySimpleGUI while learning the Python programming language and instantly fell in love with it. So, development started, and the rest is history. Pretty exciting stuff right? My main point to this section is to come clean on why it took so long for the port to be released. So, I'd like to take a second and just apologize for taking so long. You guys have been patiently waiting, and I can't thank you enough for your godly patience. Better late then never, right? right?

    Linux Base Compatibilities?​

    When testing, we mainly targeted Debian based distros, primarily KDE Neon and Mint. We're not exactly sure how well the Toolbox will play with other derivatives, so if you're on an RPM, Fedora, RHEL, openSUSE, etc base then please let us know how the Toolbox works with your distro! We're very curious! Also, a HUGE shout out goes to my good friend @blaacksheep for taking time out of his day just to test the alpha builds! Your reports have massively helped during development and I can't thank you enough! You're the man as always! :D


    What Will I Need to Run the Toolbox?​

    The Toolbox does have a few dependencies that must be resolved before the Toolbox will function:

    NameWhy It's RequiredRequired VersionType
    Python 3Execute the Toolbox's scripts.3.10+package (obtained using package manager)
    Pip 3Download and install dependency modules.23.0.0+package
    TKinterDependency GUI toolkit for PySimpleGUI.Anypackage
    ImageTK (Pillow)Modify/use Pillow image objects in PySimpleGUI.Anypackage
    PySimpleGUIGUI framework.Anypip module (obtained using pip3)
    tqdmShow download progress bars.Anypip module
    requestsDownload data from the internet.Anypip module
    PillowResize images given by the user for display in the GUI.Anypip module

    Let's Talk About The Installer!​

    In order to make the installation process as seamless as possible, we've cooked up an installer that should ease the installation process! The Installer is designed to check for, and even install (pip modules only) dependencies, inform of the Toolbox's Privacy Policy/Terms of Use, extract and install the latest TB build, and create menu/desktop shortcuts! Very cool, yes?

    However, much like the Toolbox, the installer is still in beta. You may come across some bugs/issues that could impact the overall experience. If you do happen to come across any while using the Installer please let us know so that we can squash that bug asap, and create a better experience!

    Download

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

    VersionInstaller (.exe)
    V1.0 (Beta)Download

    Bugs/Issues​

    The Toolbox (and it's installer) is currently in the beta stages. It's not 100% caught up to the Windows version, so there may be some missing features. You may also encounter some bugs/issues that may impact the overall experience. If you do come across any, please, please let us know about them so they may be fixed. When reporting a bug please provide the following info:
    • What Linux distro are you on?
    • What tablet do you have? (please provide the tablet's name, it's generation, FireOS version)
    • What tool did the error occur in, and what process caused the error to occur?
    • Is there any error output when running the Toolbox in a Terminal?
    • What Python3/Pip3 version are you running?
    • Do you have a screenshot of the error?
    Any further information would be extremely helpful. By helping squash bugs, you're making sure the experience that much better for not only you, but also for your fellow peers. :D

    Notes​

    • If the Toolbox gets stuck on the "The Toolbox is starting the Android Debug Bridge (ADB)" screen for more then 30 seconds you may need to grant execute permissions to the adb binary file in the "Fire Toolbox V1.0\adb\unix\" directory. Once granted, close out of the Toolbox and re-launch it.

    • While the Toolbox is written in Python, it is not open-source (yet). Perhaps it will be some time in the future, but as of now it will be closed-source. Thank you so much for your understanding.

    • The port may not run on Windows. My primary focus was on Linux, but it's a possibility that one day it will.

    On an entirely different note, a new update is being developed for the Windows version. I understand that the Automate methods are somewhat of a headache right now, so that's being looked into. Are there any other issues/bugs you guys feel need to be addressed with the Windows version? Please do let me know!

    Well, that's all for now folks! Hopefully you're all having a terrific Wednesday so far! Love you all, and I'll catch you on the flipside! Peace.✌️
    3
    Hi @Datastream33

    I've got another error report to make. After the update of FTB Linux to V1.1 I'm now getting this "failed to sideload the debugger due to an error" message upon program startup, and doesn't continue after that. The message window contains
    View attachment 5922423

    From the error, it seems that the path got truncated somehow to V1.1/bin/AmazonDebugger/AmazonDebugger.apk instead of Fire Toolbox V1.1/bin/AmazonDebugger/AmazonDebugger.apk. That's the install directory and somehow the whitespaces in the file path got lost. I verified that the apk is present in the directory.

    Can you take a look?

    EDIT: This only happens when I connect 'douglas' to FTB Linux V1.1. There's no such error when 'onyx' is connected. My workaround for now is to transfer the apk and install it on the tablet.
    Greetings!

    Great catch my friend. The Toolbox originally wasn't going to support spaces in the root directory path (as you pointed out in the error message - the spaces weren't handled properly resulting in a broken path). However, @blaacksheep being the good guy that is, highly recommended that it should. Had to rewrite some tools but in the end the root directory now supports spaces. However, it seems I missed the path conversion for the debugger installation function. The issue has been fixed and an update has been released. :D

    Yeah, douglas runs FireOS 5 which requires the debugger to be installed before the Toolbox can interact fully with the device. It allows us to hide packages, and perform some other interactions that wouldn't be possible without it. I'm starting to wonder if there's an equivalent for other FireOS versions that can be used to disable the protected packages on FireOS 7. Can't remember how we obtained the FireOS 5 one though.

    I'd like to sincerely apologize for my late response. Glad to see you were able to find a workaround though!

    Again, thank you so much for the report! By the way, how are things going with the port on your end? Is everything functional (besides the debugger failing to install)?
    2
    Update: just executed Toolbox, everything went smooth! The only annoying thing is that again I have to reinstall and reconfigure everything :cautious: C'mon guys it's a XXI century! (this is a rhetorical sentence of course)
    Non-rhetorically, FTB' s Backup & Restore management function may help to preserve much of the current state of your Fire tablet.

    @Datastream33 says:

    " The backup solution the Toolbox uses would allow you to restore the settings database (so things like your navigation bar layout, quick settings toggles, etc), user installed apps (apps you've installed, but doesn't include the app's data), files and directories on the internal storage (downloaded files, pictures, simple app data, etc), and package states (disables/enables system apps depending upon their states when the backup was created. If any app was disabled, and is now enabled, it will be disabled again). "

    Not an everyday tool but nice to have for disaster recovery or cloning multiple devices.
    2
    Hello guys, I have a question 'cause manual isn't clear enough.

    I just received Fire HD 10 (2021) as a replacement of similar Fire HD 10 died yesterday. Amazon support guy told me, I need to keep new device registered on my Amazon account to receive a full refund for the new one.

    So my question is, if I turn off all my Wi-Fi routers (I have 2 broadband internet connections at home), turn on the new HD and follow the manual from OP (skip the Wi-Fi setup, select a nearby network and provide a dummy password, turn on development mode etc.), turn off OTA, remove Amazon's "bloatware", etc. by using FireToolbox (I have been using it for years), I assume everything will be fine, "accidental" OS updates (if any of course) will not happens in future?
    2
    Hello guys, I have a question 'cause manual isn't clear enough.

    I just received Fire HD 10 (2021) as a replacement of similar Fire HD 10 died yesterday. Amazon support guy told me, I need to keep new device registered on my Amazon account to receive a full refund for the new one.

    So my question is, if I turn off all my Wi-Fi routers (I have 2 broadband internet connections at home), turn on the new HD and follow the manual from OP (skip the Wi-Fi setup, select a nearby network and provide a dummy password, turn on development mode etc.), turn off OTA, remove Amazon's "bloatware", etc. by using FireToolbox (I have been using it for years), I assume everything will be fine, "accidental" OS updates (if any of course) will not happens in future?

    It's even simpler than that. You just need to go to the screen that you would select a wifi network to connect to, and then tap the back button. Then a skip option will appear for you to skip the step. You might not be so lucky though. I'm thinking it will already have your wifi password because of being pre-linked to your Amazon account. You would then have to set it up with your wifi turned off as you said, and run Toolbox to hopefully disable OTA updates if your tablet is somehow pre-7.3.1.2. Then just proceed normally. The device registration will not matter any longer and will be required if you wish to use Shop Amazon and/or Prime Video.

    P.S. Don't run the "standard debloat" script right away. Just use the Manual (Simple) Amazon app management tool to disable the apps you don't want and pay attention to the colors of the apps. Green is safe, yellow apps have cautions because they may be needed for other things, and red are probably not safe to disable. The descriptions in the lower-right will advise you on them. After you get things working to your satisfaction, you can run the "standard debloat" if you still wish. (I've never run it on mine.) If you're planning on using Prime Video, leave the Shop Amazon app enabled too so you can sign in if required by Prime.(y)
  • 365


    Fire Toolbox V30.2
    All-In-One Toolbox for Fire Tablets!





    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.
    • 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 7 (2022)
    12​
    Amazon Fire 10/10+ (2021)
    11​
    Amazon Fire 8/8+ (2020)
    10​
    Amazon Fire 10 (2019)
    9​
    Amazon Fire 7 (2019)
    9​
    Amazon Fire 8 (2018)
    8​
    Amazon Fire 10 (2017)
    7​
    Amazon Fire 8 (2017)
    7​
    Amazon Fire 7 (2017)
    7​
    Amazon Fire HD8 (2016)
    6​
    Amazon Fire HD10 (2015)
    5​
    Amazon Fire HD8 (2015)
    5​
    Amazon Fire HD7 (2015)
    5​
    Amazon Fire HD7 (2014)
    4​
    Amazon Fire HD6 (2014)
    4​

    In this forum, you may hear the word "generation" being used when talking about Fire Tablets. Just know that "generation" effectively means the same as "what year was the tablet manufactured?". This may seem confusing and as a result a reference table has been provided for you below.

    screenshot-2020-12-15-174539-jpg.5158661


    GettingStarted.png


    Getting the Toolbox up and running with your tablet is surprisingly a very easy procedure. The only thing required is for you to enable Developer Options and ADB on your tablet. So, without further ado, let's get started.

    At this point, please read the section below, and make sure to follow the correct guide that is made for your tablet on how to set up the device so it works with the Toolbox.

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

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

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

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

    ToolsSubtools.png


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

    Downloads.png


    Windows:
    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V30.2​
    Post​
    Link​
    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V30.1​
    Post​
    Link​
    V30.0​
    Post
    Link
    V29.0​
    Post
    Link
    V28.9​
    Download​
    Post
    Link
    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​

    *Linux:
    Version
    Installer
    Portable (.zip)
    Update Post
    VirusTotal
    V1.0 (Beta)​
    N/A​
    Post
    Link​

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

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

    Donate.png

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


    My Home Button isn't working after using the Custom Launcher Tool?
    Due to the way the process works, it alters your navigation bar's home key to send a key event that can be picked up by Automate. Once Automate reads this event, it launches your custom launcher automatically.
    However, if the flow in Automate isn't running, the navbar key will not work, and nothing will happen when it's tapped. To fix this, either open Automate and start the "Launcher Invoker" flow again, or execute the Custom Launcher tool in the Toolbox, click the ":" icon (upper-right) to show the Tool Options panel, and click the "Restore Navigation Bar" button to restore the stock layout.

    Google Family Link won't work on my tablet?
    Unfortuently, no matter how hard we try, we still haven't been able to get Family Link to work correctly on the tablets. The Family Link app fails to install, and the Child account refuses to login. No matter what we tried, we couldn't get a Child account to work on the tablets.
    We believe this has to do with missing dependecies, and the tablets not being certified through Google's Play Protect platform. We're still activly looking into getting the issue resolved. Until then, it's recommended that you use an alternative such as Amazon's FreeTime, Eyezy, or another third-party family managing software.

    How can I remove a Google Account from my tablet?
    Because of the missing accounts section in the Settings app it will be a little more difficult to remove Google Accounts directly from the tablet. The easiest way that I've found is to visit this page: https://myaccount.google.com/security, sign-in to your Google Account, scroll down to "Your Devices" and click the "Manage devices" button. From the list of devices find your tablet and in the upper right-corner click the 3-dot icon and from the list select "Sign out".

    Can the Toolbox be used to root my tablet?
    Primarly, rooting a Fire Tablet requires the user to open the back of the device and short out a certain point on the motherboard. The Toolbox has been designed for folks who'd rather not bark down this alley. It uses the power of ADB to make changes, and is meant to be an alternative to rooting. In summery, the Toolbox isn't designed to root.

    The Toolbox is being marked as a virus?
    This is likely because the Toolbox (and it's installer) aren't signed with a software license. This freaks Windows out because it sees that there is no publisher, and as a result it displays a warning (smartscreen). In addition, some anti-viruses might also flag the Toolbox as a virus simply because the build is relatively new and there is no record of it in the anti-viruses database, resulting in a false positve.
    As always, I take your security and privacy VERY seriously! If you do not feel safe with installing the Toolbox due to virus concerns, I respect and support your decision. It is always up to the user and their judgment! :D
    32
    I'd also like to take the time to acknowledge today as a very special day for this project! Today marks the 3RD YEAR anniversary of the project!!! 😄 🎉🎉

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

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

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

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

    HERE'S TO THE TOOLBOX'S 3RD YEAR ANNIVERSARY!! 👏:D
    28
    Last edited 9-30-2022

    A lot has changed since I first posted this. Toolbox has been updated to v29.0 and now has a new method of replacing the Fire Launcher, DNS66 is only a delaying tactic and doesn't stop updates in all cases, and the Lockscreen Ad removal process in the old FTB v9.2 still works to remove the ads. I leave the post up, but understand that it's just for reference as a starting point for you to explore these things.


    What to do about F/W v. 7.3.2.2

    So your Fire tablet has the latest firmware update on it (v7.3.2.2) and Fire Toolbox won't do what it's supposed to. All is not lost. I've collected some workarounds that will keep Amazon at bay. The three main problems are:

    1) You can't stop Automatic updates.

    2) You can't get rid of the lockscreen ads.

    3) You hate the Amazon Launcher, but Amazon won't let you change it permanently.


    Once those three problems are addressed, you pretty much have your tablet back. The Toolbox will still work for all the other things you want modify. First, get your tablet set up with Toolbox, install Google Services, and install the launcher you want. (Make sure to select "Enable Widget Support".) We'll take care of the Amazon Launcher later. So let's get started with the 3 main problems.

    1) Automatic updates.

    This method is far from perfect and has sometimes allowed updates to somehow slip by. The only other way to do this that I know is to use an app blocking firewall and block the update apps. I chose this method because it doesn't require a 'training period' to train the app on what to block and what to let through. Also, if you've already got lockscreen ads in your tablet's cache, this will not remove them. This method must be in place before you first connect to WiFi for the lockscreen ad blocking to work.

    We need to stop the tablet from contacting Amazon to update it's firmware. We can no longer disable the service that does this, BUT, we can interfere with it's ability to contact the server from which it gets its updates. On a computer, we would modify the hosts file and block the addresses of the update servers. On an Android device, we need root access to do that, but there is an alternate way of adding things to the hosts file - with a VPN. We'll use a free and open source ad blocking VPN app to do this. The app is called DNS66 and it's available through F-Droid. You need to make sure this is always running to be protected from updates. Luckily, android has a feature to assist us in this. It's called "Always On VPN" and we need another app to access the hidden setting for this. We'll use "Activity Launcher" to get to this setting. Activity Launcher is available from Google's Play Store.

    It turns out that using Activity Launcher to change this hidden setting does nothing more than give you an extra notification that your VPN is off. It doesn't stop traffic, so it's useless. Besides, my tablet has taken to turning the "Always On VPN" setting back off every time I boot. (Thanks Amazon!) Activity Launcher is still useful for finding settings that Amazon doesn't see fit to include. It also makes desktop shortcuts to those settings if you wish.

    Download DNS66 to your computer from f-droid.org or from the attached file, copy it to your tablet and install it. Also go to the Play Store and install Activity Launcher. Finally, get the Amzn_Blcklist.txt that's attached to this post and copy that to your tablet. The blocklist file must remain on your tablet, so put it somewhere where it won't get deleted. I suggest in the root of your internal storage. (/storage/emulated/0)

    Open DNS66. There are a couple settings that must be changed. On the Start tab, turn on "Watch Connection". (All 3 switches should now be on.)
    DNS66-start.jpg

    Now go to the Hosts tab. Tap the "+" in the lower-right. Under Title, type "Amazon Blocklist". Tap the paper clip on the next line. Navigate to the Amzn_Blocklist.txt file you downloaded earlier and select it. Now tap "Done" in the upper-right. You should now have the first and last entry on the displayed list selected.
    dns66-hosts.jpg

    Now go to the Apps tab. Turn on "Show System Apps". Tap the gear under the Show System Apps switch and select "No Apps". All the switches below that should now be off.
    dns66-apps.jpg

    You can optionally set your own DNS servers on the next screen if you'd like. I like to turn on Custom DNS Servers, deselect the German ones that are pre-selected, and then turn on the last two servers (CloudFlare).
    dns66-dns.jpg

    This can also be done with Toolbox making this step unnecessary. Now go back to the Start tab. Tap "Start". It will notify you that it wants to connect to a VPN. Tap Yes or OK and allow it.

    Quick note: Do not use the Toolbox DNS changer in Modify System Settings AND the DNS66 Custom DNS setting together. This will cause connectivity to fail. I use DNS66 and not Toolbox's DNS changer. Having the Custom DNS Servers set ins DNS66, and using the Toolbox DNS changer simultaneously caused me hours of grief trying to figure out why Google couldn't connect!

    Now Launch Activity Launcher. Tap the magnifying glass in the upper-right. Enter "VPN". One setting should appear called "VPN". Tap it. Tap the gear on the end of the DNS66 line. Turn on Always-on VPN. Turning on the other switch makes Google Services think you are disconnected, so leave that one off. Step one accomplished.

    actlaunch-vpn.jpg


    Notes:

    DNS66 takes several seconds before it gets started when you first boot, so it is possible that the tablet will make a DNS query for the update server or the lockscreen ad server before it loads. Best practice is to turn off WiFi before you power down or reboot.

    ----------



    2) Lockscreen Ads.


    Toolbox v29.0 now takes care of lockscreen ads!


    It turns out, that blocking those update servers also blocks your tablet from getting any lockscreen
    ads! No further action is needed. I stopped investigating this because I chose to disable the lockscreen completely. If you want to do that, you can do it in Toolbox, or in Activity Launcher that you just installed. Launch Activity Launcher. Tap the magnifying glass. Type in "screenlock". Now tap the last item (.password.ScreenLockSuggestionActivity). Select None and you're done.



    Notes:

    It has come to my attention that when disabling your PIN, it may still ask you for a PIN by Parental Controls for some settings or activities. I would suggest if you're going to disable your PIN, to first set it to something simple like 0000, reboot it, and then disable the PIN. That way you'll know what PIN you set if it suddenly asks you next month for your PIN.

    Another way to disable lockscreen ads is detailed Here.

    ----------



    3) Amazon Launcher.


    New: Toolbox v29 has remediated most of the difficulties in replacing the launcher. Always check that you have the latest version of Toolbox. I'll leave the rest of the post up to inspire ideas.


    The latest version of Toolbox (v 28.1) has a new tool called 'Custom Navbar Key'. This method uses Automate to automatically replace the Home button every time you reboot. It works rather nicely. I leave this section posted for completeness and to facilitate experimentation on other choices.

    The way we're going to get rid of the Amazon Launcher is by not calling it! We're going to replace the Home button with another button that we can map to any launcher we'd like. This isn't a perfect solution, but it is FREE. If you're willing to spend a couple bucks, you can purchase a more configurable gesture navigation app with more features, but this is FREE, so maybe you can accept it's shortcomings. I'll keep this post updated with other navbar replacements that people suggest.

    Go to the Play Store. Get and install "One Button Navigation". Launch it. It will want you to turn on Accessability Service for it. Follow the on-screen instructions and turn on "One Button Navigation Bar". You'll see your new nav button at the bottom of the screen. I like to adjust the width down to a dot, like the button it's replacing, but that's up to you. I also like to make the background black and the botton bright yellow so that I'm reminded it's running. Set up the background and button colors as you like them. Yeah, I know the ads in this are obtrusive, but you'll never see them once it's set up. Also DNS66 will block the ads if you install that first.
    obn-set.jpg

    Next tap the Action tab. Tap "Single Click". Scroll down and select "Launch Application...". Select the launcher that you installed with Toolbox here. In my case, it was Nova 7. (Google updated the Nova version that Toolbox installed.) Now you can set any other actions you'd like for the new button.
    obn-act.jpg

    I didn't want anything additional, so I made the gestures similar to the original buttons. This is all up to you. You can reverse them or set additional functionality to the button. I ended up with a new navbar that covers the original navbar (the one with the home button that brings up the Amazon Launcher). I now have a button that when pressed, takes me to my launcher. When I swipe it left, it goes back a screen. When I swipe it right, it shows the recents. I spent a lot of time with other navbar replacements and this is the minimalist replacement that works best for me. YMMV. Before someone complains that it doesn't work in landscape mode, I'm not the developer. You should rate it and leave a comment for him! This is the best I could find that does what I want for FREE.

    ----------



    I'll edit this post with your suggestions for better solutions to these problems and keep a list of navbar replacements that people suggest at the end so you can find what works best for you.


    ----------------------------------------------------------
    Some Suggested Navigation Bar replacements:
    ----------------------------------------------------------

    One Button Navigation Bar by Nu-Kob (PlayStore)

    Pie Control by coolAce (PlayStore)

    Simple Control by coolAce (PlayStore)



    DNS66 is available from F-Droid.org (dated March 26, 2021)
    Activity Launcher is available from APKMirror.com (dated March 21,2022)
    21
    What's going on, guys?

    I sincerely hope everyone is doing good, and having a wonderful December so far!

    Today marks the release of V26.0 of the Toolbox! So, without further ado... let's take a look at what this release has to offer!

    Welcome, Welcome, Welcome... Screen!​

    You know, every time I run a build for the first time I go through the Theme Selector, then the Tour, and then the Welcome Screen. I just think to myself "this is just a mess" - so in this update I thought I'd focus on improving it and making it better. I started by re-designing the Welcome Screen and doing my best to link all three tools into something that looked visually appealing. Now, in a tabbed interface you'll find the Setup Tour in the very first tab, Theme Selection (with a new UI) in the second, Installation Management in the third, and finally in the fourth the Changelog.

    Now let's talk specifically about the Installation Management tool. This bad boy now has the ability to read installations from directories other than the default (localappdata\Datastream). So, if you've got your installations in a custom location, and you'd like to manage them, it's now possible to point the path to that location. This should help make managing installations a lot easier!

    Custom Launchers on FireOS 7.3.2.2​

    As some of you may know, I bit the bullet and updated my tablet to the latest version of FireOS... to the dreaded 7.3.2.2. This update, from what I heard, caused the Custom Launcher and disabling OTAs tools to no longer function and after updating, I soon discovered that it was indeed the case. I then tried everything I could think and well really didn't turn up any valuable workarounds... until I tried the method we'd been using on older gen devices... and it worked! Of course, just like on the older gens, it has the drawback of being removed every time the device is rebooted. However, it's the only method I could find, so it's better than nothing, right?

    Anyway, while coding it in I decided to take the liberty of also clean up the code, and the UI a bit. What's cool is the tool will now read what generation your tablet is, and display what methods are available to use. You'll also find that the initial method selection UI is a lot more usable compared to its previous iteration.

    Change the Timeout for the Display?​

    Ah, the latest addition to the General group in the Modify System Settings tool. This subtool not only allows you to alter the timeout to traditional values, but also allows you to set a custom timeout. Want your screen to sleep after 24 hours of inactivity? This one's for you folks who want to extend the timeout as much as you can. Just be careful, it may cause a burn-in if your tablet's screen remains on the same screen for too long!

    Let's Talk Linux Port Stuff​

    I guess the point of this section is to ask you guys if you're ok with updates to the VB version being slowed down, so I can focus more on the port? I'd also like to address a common question I get asked about it being open-source. Right now, I'm planning on it being closed-source for now. However, I am planning on making it open-source when I feel like the time is right. Please be patient! So, let's get back to the original question... are you guy's ok if I shift primary focus to the port?


    Wait, that's not everything! If you're interested in everything that's changed... please take a look at the changelog below:
    Version 26.0 - Changelog

    [Welcome Screen]
    • Updated the user interface.
    • Added better installation detection to the Installation Management subtool.
    • You can now specify what directory the Installation Management subtool will scan to detect installations.
    • Improved the look of the Theme Selector.
    • Fixed a bug causing the Startup Tour to not load tools correctly.
    [Device Information]
    • Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
    [Theme Selector]
    • Moved the Theme Selector to the Welcome Screen.
    [Custom Launcher]
    • Improved the UI.
    • Made significant improvements to the code, and fixed various bugs/issues.
    • Added Re-route Homekey option for tablets running FireOS 7.3.2.2+.
    [Modify System Settings]
    • Added the ability to change the "Display Timeout" to the General tab.
    • You can now set a custom Display Timeout of up to 24 hours.
    [Lockscreen Management]
    • Improved the warning regarding the Pattern security type.
    [Hybrid Apps]
    • Updated Disney+, and Netflix to the latest versions.
    [Manage Amazon Apps]
    • When restoring from a debloat list, it now displays the proper header and message.

    Ready to download V26.0? Head on over to the Download's section of the OP. By the way, because of some directory changes to the bin folder... the update will not show up in the Updater. It must be installed via the Installer or extracted from the Portable release.

    Ok, my favorite part about of these release posts... sharing appreciation for you awesome folks! I just wanted to say I'm so blessed to be a part of the wonderful community over here on XDA. You guys are incredible people and in fact... this is perhaps the one place I've been on that I don't see negativity or people bullying one another. You guys are just AMAZING and I wanted to let you know that I appreciate everyone's support! Furthermore, you guys are what keep this project going, and it wouldn't be where it is today without you guys! So please pat yourself on the back - you deserve it!

    Also, I'd like to place the limelight on my good friends @blaacksheep, and of course @Falcon342. I just can't express how much I appreciate all you've done for this thread! I haven't had the time to get on here because of work and when I come on the forum I see you guys helping out and answering questions. I really do appreciate the time and effort you two have put into being so freaking helpful! However, I've got to be honest, I'm extremely sad because I feel like I'm not doing enough. I'm sure you guys would like a little help (I'm gonna try harder to be more active on here when I can to hopefully help you guys out). Anyway, thank you guys again!! I really do appreciate it!!!!

    Also, don't think I forgot about you donators! I just want to say I'm so honored that you'd donate your hard-earned cash. Sometimes I feel like I don't deserve it. Guys and gals, THANK YOU so much for donating! I really do appreciate every penny! :D

    This year has flown by and Christmas is right around the corner, so I just wanted to say MERRY CHRISTMAS and I hope you all had a remarkable 2021! Let's hope 2022 is an even better year! 🙏

    Well, that's all I've got for now! Have a good one, guys, and until next time... Peace! ✌️