[WINDOWS][TOOL]Fire Toolbox V30.2

Search This thread

Datastream33

Senior Member
Sep 17, 2017
2,439
2,113
Thank you soo much for your quick reply!

I'll attach the pic of the keyboard (it's the official Amazon bluetooth keyboard for the Fire HD 10+)

If Automate could use those buttons as it is, it'll be just super.
If not, then might I request you to configure Shift + those dedicated buttons?

View attachment 5779193
Sweet, so it has a dedicated home button!

This could work with Automate. OK, I've modified the Launcher Invoker flo and attached it to this post (you'll need to extract it from the .zip file) and import it into Automate. (If you need help importing let us know)

Really hope this works! Please let us know how it goes and best of luck!
 

Attachments

  • Launcher Invoker [BT].zip
    420 bytes · Views: 33

redhub

New member
Nov 2, 2015
4
5
Hi and thanks for the great work on the toolbox!

I just used the toolbox on my new Fire HD10 Plus, firmware 7.3.2.4. The toolbox version 30.1 effectively blocks the firmware upgrade to 7.3.2.6. However, the same toolbox blocks the language download to the Librera app, which I use to read pdf files on my tablet. BTW, great app!

I'm concerned that disabling the OTA blocker in the toolbox will result in a firmware upgrade to version 7.3.2.6. Is there a safe way to download the language to the Librera app?
I would appreciate your support.
 
  • Like
Reactions: blaacksheep

blaacksheep

Senior Member
Jun 20, 2020
1,516
959
Buffalo
Hi and thanks for the great work on the toolbox!

I just used the toolbox on my new Fire HD10 Plus, firmware 7.3.2.4. The toolbox version 30.1 effectively blocks the firmware upgrade to 7.3.2.6. However, the same toolbox blocks the language download to the Librera app, which I use to read pdf files on my tablet. BTW, great app!

I'm concerned that disabling the OTA blocker in the toolbox will result in a firmware upgrade to version 7.3.2.6. Is there a safe way to download the language to the Librera app?
I would appreciate your support.
Hi, and welcome to XDA!

You can use the RethinkDNS method of blocking the updates. A link to that method is located in my signature. It just blocks the apps responsible for updates from internet access so they can't update. In order to undo the method in Toolbox, I'm not certain if there's an option in Toolbox to undo it. If it works the way I think it does, you can go into WiFi settings and tap on the gear to the right of your network name, and look down a few lines until you see "Metered". Tap that and change it to either of the other options. Let me know how you do. :)
 
  • Like
Reactions: redhub

redhub

New member
Nov 2, 2015
4
5
Hi, and welcome to XDA!

You can use the RethinkDNS method of blocking the updates. A link to that method is located in my signature. It just blocks the apps responsible for updates from internet access so they can't update. In order to undo the method in Toolbox, I'm not certain if there's an option in Toolbox to undo it. If it works the way I think it does, you can go into WiFi settings and tap on the gear to the right of your network name, and look down a few lines until you see "Metered". Tap that and change it to either of the other options. Let me know how you do. :)
Thank you for your quick response.
Temporarily disabling the "Metered" option for my wifi network took care of the issue and the language file downloaded correctly. :)
 

blaacksheep

Senior Member
Jun 20, 2020
1,516
959
Buffalo
Thank you for your quick response.
Temporarily disabling the "Metered" option for my wifi network took care of the issue and the language file downloaded correctly. :)
Just make sure you check the System Updates section of your Settings to see if there's an update waiting to install before you shut down/reboot. (Don't click "Check for updates", just look at the bottom where it says the current status.) If there is one waiting to be installed, report back here and we'll tell you how to get rid of it. (y) Oh, and make sure you put it back to metered so an update doesn't slip through.
 
Last edited:
  • Like
Reactions: redhub

Abyssul

Member
Oct 2, 2013
11
0
I have ben able to use this awesome tool to add in google services and strip out the amazon bloaware but unfortunately the custom launcher is not working for me. The device (fire 8 plus) is already on 8.3.1.3

When I install the nova launcher both Nova launcher and automate install and permissions are granted.

Then I see a message saying "the launcher invoker flow will now be imported into automate, please unlock your device (please do not interact with the touch screen during this process) and click OK to continue.

I click ok only to be greeted with an error about "Failed to read flow" on the tablet with the only option being cancel (import is greyed out). I have tried importing an older version of the launcher from this forum but that also did not work (the nova launcher opened once and then defaulted back to the fire home pages screen)

Could anyone who has seen this beofre please point me in the right direction as I think I am having a bit of a PEBKAC moment here.
I have a Amazon Fire HD 8 12th gen (2022) running 8.3.1.3 and running into this exact issue. I get the "failed to read flow" error on the tablet when settings up the custom launcher from the toolbox. I imported the flow directly from the toolbox manually. However, the launcher only opens once and then defaults back to the Fire launcher.

Home button press starts at 12-07 22:05:56.913. There are no other log entries on subsequent home button presses that open the Fire launcher.
12-07 22:05:45.400 I [email protected]: Flow beginning
12-07 22:05:45.412 I [email protected]: System setting get
12-07 22:05:45.424 I [email protected]: Fork
12-07 22:05:45.455 I [email protected]: Broadcast receive
12-07 22:05:45.461 I [email protected]: Fork
12-07 22:05:45.486 I [email protected]: Media button
12-07 22:05:45.517 I [email protected]: App in foreground?
12-07 22:05:56.913 I [email protected]: App start
12-07 22:05:57.012 I [email protected]: Fiber stop
12-07 22:05:57.046 I [email protected]: Fork
12-07 22:05:57.154 I [email protected]: Media button
12-07 22:05:57.202 I [email protected]: App in foreground?
12-07 22:05:57.249 I [email protected]: Stopped at end
 

blaacksheep

Senior Member
Jun 20, 2020
1,516
959
Buffalo
I have a Amazon Fire HD 8 12th gen (2022) running 8.3.1.3 and running into this exact issue. I get the "failed to read flow" error on the tablet when settings up the custom launcher from the toolbox. I imported the flow directly from the toolbox manually. However, the launcher only opens once and then defaults back to the Fire launcher.

Home button press starts at 12-07 22:05:56.913. There are no other log entries on subsequent home button presses that open the Fire launcher.
Make sure that Automate is set to start on system startup, and that the flow "Launcher Invoker" is started. You said that all permissions were granted, so that should be enough.
 

mohnish92

Member
Dec 4, 2022
8
5
Sweet, so it has a dedicated home button!

This could work with Automate. OK, I've modified the Launcher Invoker flo and attached it to this post (you'll need to extract it from the .zip file) and import it into Automate. (If you need help importing let us know)

Really hope this works! Please let us know how it goes and best of luck!
Thank you for your reply!
I extracted the zip, placed it in my downloads folder, and then imported to Automate.
Then, I Stopped the original "Launcher Invoker" Flow and Started the "Launcher Invoker [1]" Flow.

However, pressing the Home button on the keyboard still lands me to the Fire Launcher homescreen :(
Please let me know if I have to send any screenshot etc of the Automate page, or any log file to help with this process?
(I really appreciate your willingness to share such customization!)
 
Last edited:
Thank you for your reply!
I extracted the zip, placed it in my downloads folder, and then imported to Automate.
Then, I Stopped the original "Launcher Invoker" Flow and Started the "Launcher Invoker [1]" Flow.

However, pressing the Home button on the keyboard still lands me to the Fire Launcher homescreen :(
Please let me know if I have to send any screenshot etc of the Automate page, or any log file to help with this process?
(I really appreciate your willingness to share such customization!)
Screenshot your current navbar, this method required customized navbar with a custom layout, if you stll see original navbar layout with 3 button placed nearly each other, then it doesn't work.
 

mohnish92

Member
Dec 4, 2022
8
5
Screenshot your current navbar, this method required customized navbar with a custom layout, if you stll see original navbar layout with 3 button placed nearly each other, then it doesn't work.
The touch screen home button works fine, and it lands me to the Nova launcher home screen.

I'm facing an issue on the Fire HD Bluetooth Keyboard -- home screen physical button.
That lands me to the fire launcher home screen even with the modified invoker flow posted by datastream33 above.
 
  • Like
Reactions: ghoster76

KnightPhoenix

New member
Dec 6, 2022
3
2
Okay, just checking. I'm not sure about FireOS 8. A couple of users with 2022 tablets seem to have that problem. You can also let Google Play update Automate. Maybe it's a version thing. I'm just guessing here.😕
It is set to start on system startup and the flow is started. That is how I got my flow logs 😊
I have just found a plugin in the automate community called "Amazon Fire Tablet - Easy Home Launcher Changer". It seems to work but every now and again you see a flash of the old home pages when you click the home button (not every time and it disappears in half a second). Will try to go through and map it out later and see if I can work out why this works and the launcher is not.

Only other issue with the plugin is it asking you which launcher you want to use on load (but sure that could easily be hard coded).

Thanks for all the help and good advice.
 

Liara

Member
Dec 8, 2022
5
7
I have a Fire HD 10 from 2019. I want to use Toolbox on it for the first time. I wanted to ask if I'm right in thinking it would be best to reset the tablet beforehand.
 
  • Like
Reactions: Datastream33

Datastream33

Senior Member
Sep 17, 2017
2,439
2,113
I have just found a plugin in the automate community called "Amazon Fire Tablet - Easy Home Launcher Changer". It seems to work but every now and again you see a flash of the old home pages when you click the home button (not every time and it disappears in half a second). Will try to go through and map it out later and see if I can work out why this works and the launcher is not.

Only other issue with the plugin is it asking you which launcher you want to use on load (but sure that could easily be hard coded).

Thanks for all the help and good advice.
It looks like its using an atomic variable to hold the custom launcher variable. This means that once its set, it will remember the value even if the flow is stopped (e.g: set it and forget it). The flow however, is using the old method of waiting for the fire launcher to be in the foreground before launching the custom launcher.

This shouldn't work on newer tablets due to the 5 second delay issue. Apologizes if this information has been provided before, but which tablet and FireOS version do you have? Thanks!
 

Datastream33

Senior Member
Sep 17, 2017
2,439
2,113
The touch screen home button works fine, and it lands me to the Nova launcher home screen.

I'm facing an issue on the Fire HD Bluetooth Keyboard -- home screen physical button.
That lands me to the fire launcher home screen even with the modified invoker flow posted by datastream33 above.
Dang, ok...

We can try another combo such as Ctrl+z or something like that. Do you have a preference?
 

KnightPhoenix

New member
Dec 6, 2022
3
2
It looks like its using an atomic variable to hold the custom launcher variable. This means that once its set, it will remember the value even if the flow is stopped (e.g: set it and forget it). The flow however, is using the old method of waiting for the fire launcher to be in the foreground before launching the custom launcher.

This shouldn't work on newer tablets due to the 5 second delay issue. Apologizes if this information has been provided before, but which tablet and FireOS version do you have? Thanks!
In my case it is version 8.3.1.2. I forgot to unlink it from my account before shipping 😔
 

Top Liked Posts

  • 3
    @Datastream33 and @Jumbo100 thank you both for trying to help me. I have since stopped apps, cleared data, cleared cache, uninstalled google pay, removed most of the Amazon installed apps, but I'm still getting stuck at the pending.

    I thought I had a good chance that the Keep for Google and Google Drive apps installed through the amazon app store were causing the issue. Nope, removing those didn't change anything. I went through the settings on my working Fire 7 and compared them to the Fire 10, but nothing I see is different.

    I'm fine doing a wipe of the tablet. Are there some existing instructions on best practices on doing a wipe?
    2
    @Datastream33 and @Jumbo100 thank you both for trying to help me. I have since stopped apps, cleared data, cleared cache, uninstalled google pay, removed most of the Amazon installed apps, but I'm still getting stuck at the pending.

    I thought I had a good chance that the Keep for Google and Google Drive apps installed through the amazon app store were causing the issue. Nope, removing those didn't change anything. I went through the settings on my working Fire 7 and compared them to the Fire 10, but nothing I see is different.

    I'm fine doing a wipe of the tablet. Are there some existing instructions on best practices on doing a wipe?

    Just as a note to your misfortune with GPS, if you DO choose to wipe, After the wipe, first disable OTA updates. Then, before you start removing Amazon apps, install Google Play Services. That way you're not removing something that's expected to be there when GPS is installing. Finally, customize to your heart's content. (y)
    2
    @Datastream33 and @Jumbo100 thank you both for trying to help me. I have since stopped apps, cleared data, cleared cache, uninstalled google pay, removed most of the Amazon installed apps, but I'm still getting stuck at the pending.

    I thought I had a good chance that the Keep for Google and Google Drive apps installed through the amazon app store were causing the issue. Nope, removing those didn't change anything. I went through the settings on my working Fire 7 and compared them to the Fire 10, but nothing I see is different.

    I'm fine doing a wipe of the tablet. Are there some existing instructions on best practices on doing a wipe?
    Something really obscure from Google support ...

    If you're using a microSD card as extra storage, remove SD card from your device BEFORE installing/reinstalling Google Play infrastructure or doing a factory reset.

    I have no idea why this is needed or how it works , but Google Support sometimes mentions this in sidenotes. Should be SOP if if it causes problems.

    If you're doing a factory reset, probably wouldn't hurt if you waited to add microSdD card until everything else is setup.
    2
    Something really obscure from Google support ...

    If you're using a microSD card as external storage, remove SD card from your device BEFORE installing/reinstalling Google Play infrastructure.

    I have no idea why this is needed or how it works , but Google Support sometimes mentions this in sidenotes. Should be SOP if if it causes problems.
    I think there's a risk of the tablet wiping your card if you leave it in, but I never noticed that warning and I've wiped/installed Google Services many times on my tablets with SD cards formatted as external storage and as adopted storage. 🤷
    2
    I think there's a risk of the tablet wiping your card if you leave it in, but I never noticed that warning and I've wiped/installed Google Services many times on my tablets with SD cards formatted as external storage and as adopted storage. 🤷
    IDK ... Google Support ? ... lol
  • 8
    Hey, I know I'm a little tardy to the party... but I suppose it's better late than never... right?

    I'm happy to announce that today marks the 4TH YEAR ANNIVERSARY of the project! 🎉🎉

    2019, the year of the Toolbox's release... It seems like such a long time ago, doesn't it? (feels like 4 years to be exact ;)).

    Jokes aside, it's really cool to see how something that started out so simple, evolve into something much bigger than you could ever image. I mean, this project started out as a BATCH file for pete's sakes... its sole responsibility to remove lock screen ads!

    Release after release, the Toolbox grew, and so did its impact. Today we are on Version 30.3 and so many new features have seen the light of day. it's just so crazy to think that this small project has gotten this big. Sure, we've been through some hard times, with the whole download situation that happened in July, the release of FireOS 7.3.2.2, the play services issue on FireOS 8... just to name a few. But you guys stuck with me through it all, giving your support, and just being awesome people!

    Speaking of you guys, I just wanted to take some time to THANK YOU all from the bottom of my heart for being the BEST community on the entire internet. @Jumbo100 and I were discussing this and we both came to the conclusion that this community is one of the few communities where everyone has just been so kind, caring, positive, respectful and helpful towards each other without there being rude and toxic individuals running rampid. Words cannot express how grateful I am to be a part of it. You guys are my world, and seeing everyone come together like this is has just been a blessing. Thank YOU all so much from the bottom of my heart. :D

    I also want to give a huge shoutout to a few close friends on the forums that I couldn't have done all of this without: @blaacksheep, and @Jumbo100. I mean, where do i even start? You guys are really carrying this thread if I'm being honest. No question goes unanswered, and you guys are always on here offering advice, creating magnificent guides (especially your workaround guides @blaacksheep), and just generally being amazing people. We all owe you guys so much! The community growth is largely because of your guys efforts! Words just cannot express how lucky we are to have you two. THANK YOU!

    So What's Next for the Project?​

    The goal for this year is to complete and release the Python Port (more on that in a moment). But, I'd also like to jump into the VB version and fix up some issues that it has. Work needs to be done, and some improvements need to be made.

    As far as the port goes, I'm about to let out some information that may cause some anger for some folks. I've thought long and hard about this, and I've decided that the port will be closed-source, much like the Windows version. Yes, I know there are plenty of reason why open-sourcing it would be better than keeping it closed source, but I'm just not ready for that sort of thing yet. I'm not saying it will never happen, just not at the moment. I hope you guys can understand.

    Thank you all for taking the time to read this post, I really do appreciate it! Please have a good rest of your night, and I'll see you guys tomorrow!

    HERE'S TO A HAPPY 4-YEAR ANNIVERSARY OF THE TOOLBOX! 🥳
    3
    @Datastream33

    A Happy Fourth Anniversary to the Fire Toolbox Project !

    • 30 Version Updates spanning a host of Generations of Fire Tablets on 5 major FireOS platforms
    • 2M+ Thread Views, 11K+ Posts, a legion of followers
    Quite a Legacy!

    Thank you for your persistence and dedication to the Project - it’s been a Journey!!

    “ Alla salute – Cent’anni ! "
    3
    Manual updating is not working for me.

    I go from Settings --> Device Options but when I go to System Updates, I get kicked back to Settings

    FTB won't re-enable either OTA updates. I'm not sure about automatic updates. It looks like I can make a change on the tablet but FTB won't show any such change.

    There doesn't appear to be any method available for pointing the tablet towards the firmware update that's sitting in the internal storage folder.

    I've restored all Amazon apps. The only thing I can think to do next is a Reset to Factory Defaults.

    The one thing that I don't want to do is to go online to do anything automatically there.
    3
    I have Fire 8 (10th gen, 2020), and used (I think) v26 or so for the tool. I have system updates disabled so I can't see what version Fire OS I'm on but I haven't updated in more than a year at least.

    So is it worth updating to newer Fire OS for the tablet? Any significant updates? Does v30 of the tool do anything more/less that it would be worth running it and updating, or even starting again? I only use this Fire for basic use, media use.

    I still find the Fire tablets slow, this one was cheap it was worth it, is the 2022 version any faster in general use? Hate the pause and sluggish behaviour of it

    thanks
    If you've been away from the FTB community for a while you've missed a lot of excitement/angst/despair.

    From the FireOS 7.3.2.2 update (late November/21) there were some significant changes to how Fire tablets could be modded. Quoting from OP #1:

    " 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."


    This includes not being able to replace Amazon Launcher.

    Since then Amazon has added even more restrictions. @Datastream33 worked really hard to code various "workarounds" which are effective but are cumbersome and add to the "overhead" of the already limited system resources.

    So definitely DO NOT upgrade FireOS . Most of the FTB updates are related to the workarounds and probably wouldn't add any new functionality to your setup, although some of the FTB processes are improved.

    If your tablet is pre-f/w update 7.3.2.2, consider it to be part of the "Golden Age" of FTB mods ... it doesn't get any better!

    To improve the performance of your device consider reducing the number of apps installed to free as much memory as possible, especially for streaming media. Also consider cleaning the tablet caches periodically; services like YouTube can occupy as much as 250MB memory per hour.

    The newer Gen 12 tablets have moderately improved specs, but have their own problems running the Google Play ecosystem.
    3
    Godd tactical plan ... you need/want FireOS 8.3.1.3 but ONLY f/w 8.3.1.3.

    Keep a copy of the the f/w download for "safekeeping" , if you ever need to do a future device factory reset ... Amazon support only makes the current update available and doesn't archive previous versions.
    I can see that. Is there no 3rd-party website keeping any of the desired Fire OS versions available? Would Amazon shut that down?

    If they frown upon this, I guess you wouldn't be permitted on any host using Amazon Web Services. Terms of Service or some such legalese but this may be something that might fly under their radar.
  • 346


    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


    Toolbox:
    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V30.2​
    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
    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​
    Donate.png

    If you like my work and would like to support me feel free to Donate. Thank you!
    65
    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.

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