[WINDOWS/LINUX][TOOL]Fire Toolbox V34.0
- Thread starter Datastream33
- Start date
That looks like you have your font size set to 125% in Windows. The Toolbox doesn't deal with that well as you see. If you don't want to set your font size to the default 100%, the easiest thing to do is create another user account on your computer and use that when you need Toolbox.
You Sir are top banana!! Thanks a lot, took some time to find the 125%!
All good now, thanks a lot
Anyone else get crash notices poping up all the time about Devs something or other? How to stop it?
No, the Fire 10 after the Toolbox has done it's thing.
It would be advantageous if you could be more specific about the error messages. Try to read them before they disappear. I know it's tough when they vanish before you get the chance to read them, but maybe you can find something that causes the error and repeat it a few times to read the message.
I was also unable to get voice typing to work in GBoard. It does work in Swiftkey though, so I just switched to that.
I made 2 profiles but I can only install google play only on one of them.
Can`t I install google play on both profiles?
Can`t I install google play on both profiles?
I did that , but the thing is that when I change user and try to install google play services it gives me errors all the time....
For some reason it only goes through installing play services but only on one user (doesn`t matter which one btw)
It worked.... Thank you very much
Just got a new HD 8, downloaded V23 and went to town on it. Everything went smoothly until I tried installing google services which gave me the same corrupt file error others have mentioned. Is there a current work around? I tried the side loading fix from back in the April discussions, but that didn't work.
Hey, I have an Fire 10 HD, I've tried to download google services but has loading and it isn't actually downloading what do I do? I have also tried deleting the apk out of the folder
Last edited:
Google suddenly failed to refresh Google Play Services on my Fire8. It is needed by among us, for example ...
About a week ago I deleted and reinstalled Google with the current toolbox, it worked, but now I have the same google services error.
Which version and source should we use for sideload the services apk?
About a week ago I deleted and reinstalled Google with the current toolbox, it worked, but now I have the same google services error.
Which version and source should we use for sideload the services apk?
Is there any new development on this front? I would also like to remove a Google account from my Fire. I am currently logged in with two accounts in the Play Store, one of which I no longer use. Thank you.Greetings friend!
On some tablets, the Accounts activity is present and from here we can effectively remove accounts. However, it's been observed that a large majority of tablets are missing this activity. This unfortunately means we'd need to find an alternative method of removing accounts, and so far we've come up short. Hopefully something can be found soon.
By the way, welcome to XDA!
What's going on, guys? I hope everyone is having a great Friday so far!
Tonight, we have the release of V24.0 and let's just say that it packs a punch! So, without further ado... let's take a more detailed look at what the update has to offer!
For example, in the last few previous releases we've had changes to the Toolbox Updater which prevented updates from being released through that medium. As a result, I've had some folks inform that they didn't know any updates were released. Well, using the Notification Center, a message can now be sent out to relay information about a new release.
In the Notification Center you'll see the subject of the message, the message, a timestamp of when the message was sent out and when you received it. You can also cycle through the notifications by clicking the < > buttons at the bottom left of the window, and next to that you'll see how many notifications are unread. In addition, The messages can also contain actions that can execute a command, or open a webpage (the Toolbox will show what website it wants to open, or what command is going to be executed, and will ask for your permission before doing so).
Overall, a nifty little tool that I hope will be extremely useful down the line!
So far, you can change the DNS to any of the following providers:
P.S: I'd use the Adguard provider because it can help block ads as well...
All you have to do is open the Toolbox, Execute the Google Services (Manage) subtool, and at the bottom you should an option to Update Play Services. The Toolbox will then check the currently installed version for Play Services and compare it to the version on the server. If the one on the server is newer than the currently installed one, then the Toolbox will present an update button that once clicked will download and install the newest version of Play Services automatically! Pretty cool, huh?
Wait, that's not everything V24.0 has to offer! Take a look at the change log below for the full scoop!
Ready to download V24.0? Head on over to the Downloads' section of the OP, or you can upgrade from a previous version to V24.0 using the Toolbox Updater!
With everything else out of the way, I'd like to say that this community is such a blessing, as I've been able to meet some really cool and awesome people through it. I just want to take a little time and let you guys know that I truly appreciate the support and interactions I've with each one of you... It really means a lot to me! In addition, HUGE THANKS GOES OUT TO THE LOVELY DONATORS!! I really do APPRECIATE it and I feel so blessed! THANKS AGAIN!!
Well, that's all I've got for now. I sincerely hope you enjoy V24.0, and please continue to have a wonderful day/night!
Tonight, we have the release of V24.0 and let's just say that it packs a punch! So, without further ado... let's take a more detailed look at what the update has to offer!
The Notification Center
Ah, the Notification Center... a returning tool from the Batch version of the Toolbox. However, unlike the version in the batch edition... this one doesn't crash the entire program and actually works! Anyway, let's talk about why this tool was added in the first place. The primary reason for this tools' addition is relaying of information in the easiest and most efficient way possible.For example, in the last few previous releases we've had changes to the Toolbox Updater which prevented updates from being released through that medium. As a result, I've had some folks inform that they didn't know any updates were released. Well, using the Notification Center, a message can now be sent out to relay information about a new release.
In the Notification Center you'll see the subject of the message, the message, a timestamp of when the message was sent out and when you received it. You can also cycle through the notifications by clicking the < > buttons at the bottom left of the window, and next to that you'll see how many notifications are unread. In addition, The messages can also contain actions that can execute a command, or open a webpage (the Toolbox will show what website it wants to open, or what command is going to be executed, and will ask for your permission before doing so).
Overall, a nifty little tool that I hope will be extremely useful down the line!
Private DNS Anyone?
As requested by a few of you lovely folks here on the forum, the Toolbox now supports changing the DNS servers your tablet uses (Unfortunately, only supported on new gen devices)! The best part is... when you change the DNS Resolver, the change is made globally! Meaning any WIFI network you connect to, or any profile you log in to, will use the specified DNS you've set. Pretty nifty if you ask me.So far, you can change the DNS to any of the following providers:
- Adguard
- Cloudflare (1.1.1.1)
- Google Public (8.8.8.8)
- Default (ISP)
P.S: I'd use the Adguard provider because it can help block ads as well...
Taking Sideload Apps to a New Level with XAPK Support
The wonderful and crafty .xapk format is used by third-party apk distribution websites such as ApkPure and Apkmirror to distribute apks and resources more effectively. However, because this format isn't officially recognized by Google they can be a little more tricky to install than traditional APKs, and require a lot more work to get going. Despite this, after a long time of figuring out how to accomplish installing these files... I'm proud to announce that the Toolbox now supports installing .xapks! Gone are the days of seeking out an apk version of an app.Dealing With the "Update play services" Error
As I'm sure some of you are aware, for whatever reason, Google Play Services keeps throwing an error asking users to update Play Services. However, when the notification is clicked it brings up the Play Store page for Play Services, and unfortunately it seems that the Update button is missing. It was soon discovered that manually sideloading the latest version of Play Services seems to fix the issue. Well, to combat this issue, the Toolbox is now capable of updating the Play Services app for you!All you have to do is open the Toolbox, Execute the Google Services (Manage) subtool, and at the bottom you should an option to Update Play Services. The Toolbox will then check the currently installed version for Play Services and compare it to the version on the server. If the one on the server is newer than the currently installed one, then the Toolbox will present an update button that once clicked will download and install the newest version of Play Services automatically! Pretty cool, huh?
Manage Amazon Apps (Manually - Simple) Improvements
Another requested feature? Heck... yes! Much like its Advanced counterpart... the manual simple subtool now takes into account what apps in the list have been disabled and will relocate them to the Restore list. This should help relay which apps are still enabled, and what apps can be restored. Making management a heck of a lot easier! Another cool change is that the console now retains all results instead of clearing the output after each operation, and the IMBd package name has been updated to the correct one.Wait, that's not everything V24.0 has to offer! Take a look at the change log below for the full scoop!
Ready to download V24.0? Head on over to the Downloads' section of the OP, or you can upgrade from a previous version to V24.0 using the Toolbox Updater!
With everything else out of the way, I'd like to say that this community is such a blessing, as I've been able to meet some really cool and awesome people through it. I just want to take a little time and let you guys know that I truly appreciate the support and interactions I've with each one of you... It really means a lot to me! In addition, HUGE THANKS GOES OUT TO THE LOVELY DONATORS!! I really do APPRECIATE it and I feel so blessed! THANKS AGAIN!!
Well, that's all I've got for now. I sincerely hope you enjoy V24.0, and please continue to have a wonderful day/night!
@Datastream33
Thanks. Tested version V24, but there are no updates found for google play services?
Installed: Google Play Services 21.36.14
Error: Google Play services won't run unless you update Google Play services
Thanks. Tested version V24, but there are no updates found for google play services?
Installed: Google Play Services 21.36.14
Error: Google Play services won't run unless you update Google Play services
I just updated to v. 24. Thanks for continuing to maintain this software.
My Amazon Fire tablet hasn't been updated in months. The version on my tablet is FireOS 7.3.1.8; build date of Jan 2021 (the latest updated OS I can download from amazon, is 7.3.2.1). I have seen a page here that explains how to manually update (just using the System Updates gets me the "check for updates failed" message): https://www.lifewire.com/update-kindle-fire-tablet-2740669 But even manually moving the update file gets me the same error message.
Can the toolbox be used to get the tablet to update itself (I'm not talking about the toolbox itself being updated)?
My Amazon Fire tablet hasn't been updated in months. The version on my tablet is FireOS 7.3.1.8; build date of Jan 2021 (the latest updated OS I can download from amazon, is 7.3.2.1). I have seen a page here that explains how to manually update (just using the System Updates gets me the "check for updates failed" message): https://www.lifewire.com/update-kindle-fire-tablet-2740669 But even manually moving the update file gets me the same error message.
Can the toolbox be used to get the tablet to update itself (I'm not talking about the toolbox itself being updated)?
Similar threads
Top Liked Posts
-
2@blaacksheep, I'm using Nova Launcher Prime 7.0.58 but my FireOS v7.3.2.9 (there is nothing I can do - replacement device came with that version).
Thanks for the advice: after "playing" with WeaWow I've finally added widget to my home (making everything very same on both my Fire HD 10)
But here is another issue: Google Chrome browser option to add page to the home screen is missing I do have a few home-brew smart home gadgets with built-in web pages for control & configuration (on screenshot "X10" & "Smart blind remote") but can't add 'em Do you know how to fix?2
FireOS with Fire Launcher do not natively support shortcuts or widgets.@blaacksheep, I'm using Nova Launcher Prime 7.0.58 but my FireOS v7.3.2.9 (there is nothing I can do - replacement device came with that version).
Thanks for the advice: after "playing" with WeaWow I've finally added widget to my home (making everything very same on both my Fire HD 10)
But here is another issue: Google Chrome browser option to add page to the home screen is missing I do have a few home-brew smart home gadgets with built-in web pages for control & configuration (on screenshot "X10" & "Smart blind remote") but can't add 'em Do you know how to fix?
But some third -party launchers (like Nova Launcher) can support widgets , but still not shortcuts.
You're successfully using widgets now with Nova Launcher.
To workaround shortcut deficiency, try using a shortcut/widget maker app to generate a "pseudo-widget" from a webpage address ... basically a shortcut "re-skinned" as a widget.2
A year ago everything worked perfectly, as on "native" Android, and I'm still able to create webpage shortcuts on home screen from Google Chrome on my another Fire HD 10 (11th gen but about 3 yo, of course hacked by FTB).
BTW, thanks for advice! Will use this workaround if I can't find a proper solution for the damn Chrome.2
Yeah, widget support is just lacking in FireOS. It may have worked on older firmware versions, but Amazon continues to block things that don't support your tablet as an Amazon shopping device!
Your only option is to do what Jumbo100 said and try a shortcut/widget maker app to create what you need. Hopefully, you are successful.2
One of of the FireOS shortcomings subsequent to f/w 7.3.2.2. None of the usual web browsers used on Nova Launcher can create shortcuts to Fire tablet homepages with recent f/w. Not really a specific Chrome browser problem per se.
Shortcut Maker for Android (by dev Rushikesh Kamewar) has been vetted by the Community as a workable solution, but there may be other viable apps. -
3What's going on, guys?
Long time no see!
I know this is out of the blue, but I'm extremely excited to announce that Fire Toolbox V34.0 has just been released. There's some good changes in here, so let's not delay any further and get into the nitty gritty of today's update.
Let's Rethink the Blocking of OTA Updates
OK, I’ll be the first to admit that the current restriction workaround of setting the Wi-Fi networks as metered isn’t ideal for a large majority of cases. It not only prevents HD streaming in some apps, but can slow down downloads and uploads. So, it would be ideal if we had a different approach, one that just works for our case? Well luckily for us, @blaacksheep has us covered as usual. In today’s update, I’m excited to announce that the Toolbox is now capable of installing and configuring Rethink Dns for tablets running on a restricted firmware! Huge shoutout to @blaacksheep’s guide, It was a very valuable resource in getting this thing setup!
Unlike the metered method, Rethink allows us to block connections to Amazon’s servers, without sacrificing networks speeds. But because Rethink is always running in the background it will consume some RAM which can impact performance on tablets with a lower RAM capacity. Despite this, it’s still worth a try if you’re experiencing issues with the metered method.
The method works by installing Rethink, setting it as an "always on VPN", and then restoring a settings backup that contains the neccessary rules for blacklisting connections to Amazon's OTA updates servers, and preventing network access for the OTA Update system packages.
If you’re interested in trying this method, all you need to do is launch the Modify System Settings tool, and click the toggle next to OTA Updates (you will have to revert the Metered method before the Rethink method can be used), and select Rethink from the new method selection window!
Switching It Up With Languages
For tablets running FireOS 7.3.2.0+ now have the option to change the device's language, even using languages not listed in Amazon's language selection in the Device Setup app! However, there's always a downside, and in this case the downside is that because Amazon didn't get around to fully translating the OS for different languages only some parts of the OS have been translated. From what I could gather, the Settings app is where it's mostly noticeable. Some headers and descriptions may appear in the selected langauge, while some may still appear in English.
And while we're on the subject of languages, as far as I could tell, there's no way of adding additional languages to the tablets without root access. So I'm afraid there isn't much we can do about the partial support, or adding additional languages that aren't already supported.
Restoring What Matters the Most From System Backups
So this next feature is something I think has been needed for some time now. When restoring a backup, it's now possible to select what elements from your backup you actually want to restore. So, if you have backup with the Internal Storage, package states, and user apps, but you just want to restore the package states, you can now tell the Toolbox that's what you want and instead of it restoring the entire backup all at once you can now restore just the package states. Pretty freaking cool aye? The list view has also been updated so the backups will now appear from top to bottom instead of from left to right.
A new Google Assistant
When it comes to downloading, this tool and the Google Services tool were the hardest ones to account for. The Google app itself (depending upon which version of Android your tablet runs) is a fairly large APK (120MB+), and after APKMirror shut down access to direct download links we had a fairly hard time hosting the APKs ourselves so we figured since we already had Play Services installed, we'd just rely on the Play Store to download/install the Play Store for us. Of course I didn't think of the possibility of the Play Store blocking access to the Google app due to an unsupported device. Luckily, we just discovered that another popular APK website (trusted) allows direct downloads, so the Google app is now downloaded from there, solving the whole issues with the Play Store.
Also, the process of fully activating Google Assistant has changed with time, so I took the liberty of adding an instructional video/text tutorial that goes over the onboarding process. And for some reason the Gassist APK has been missing from previous Toolbox builds, so that has also been restored.
Hiding Those Pesky Unsupported Settings
As Android continues to evolve, new features are constantly added and some features are sometimes removed. In past versions of the Toolbox, some features could be found that would have no impact on different versions of Android and would often cause confusion due to their inclusion. For me this was something I've been meaning to tackle for some time now. Not everything has been accounted for just yet, but I think it's a good start. So, here's just a few of the subtools that have been hidden for specific Android versions:
[Custom Launcher]
- To avoid confusion, the Launcher Activation methods that aren’t compatible with the tablet’s firmware are now hidden.
[SystemUI Modifier]
- Due to Google removing the ability to modify the navigation bar through the settings database, the Navigation Bar Modifier will now be hidden for tablets running FireOS 8+.
[Modify System Settings]
- The Do Not Disturb (Voluem Panel), and Power Notifications options should only be shown on tablets running FireOS 6.
- The Night Mode (Dark Theme), and Gesture Navigation options should only be shown on tablets running FireOS 8+.
- The Language Locale option should only be shown on tablets running FireOS 7+.
- Gesture Navigation will only be shown on tablets running FireOS 8+.
A New Way of Navigation on FireOS 8
Thanks to @dbdude58 for discovering an easy way to activate Gesture Navigation, it's now possible to toggle on/off gesture navigation in the Modify System Settings tool (SystemUI tab)! While it does survive a reboot, there can be some cases of the navbar glitching out, and sometimes weird behavior can occur (at least in my testing). But, it's a breath of fresh air to use on FireOS nonethless.
What's Changed Exactly?
Interested in everything that's been changed in today's update? Here's the changelog:
Scam Sites and Ensuring Your Download is Legit
It has come to my attention that there are some scam sites out there claiming to be the "official" website for Fire Toolbox. Please do NOT download anything from these sites! They could distributing malware, or bundling it with the Toolbox. I do NOT run any other websites (besides the two wordpress websites - Datastream33, aftb), and I do NOT post Toolbox updates or builds anywhere else except right here on XDA. Once you've downloaded either the Installer or Portable build, I'd strongly suggest checking the SHA256 checksum and ensuring the file's checksum matches the checksum posted here before installing.
If you're comfortable with the command line you can use CertUtil (certutil -hashfile filepath SHA256) or Powershell (Get-FileHash filepath), or if you prefer a GUI you can try my new Sha256Checker tool.
Downloads
SHA256 Hashes
Filename SHA256 Hash FTB_V34.0_Installer.exe df19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc FTB_V34.0_Portable.zip f47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f
Thank You, Thank You, Thank you!
Hey guys, I know I haven't shown my face in here for some time... but I just wanted to let you all know that I have been keeping tabs on the thread. I just wanted to once again thank you all from the bottom of my heart for being so caring, and kind towards each other. I've been in and out of some communities and let's just say, there are some VERY vicious people out there. So thank you all for being so kind and respectful.
As always, I need to give a GIANT shoutout to my good friends, @blaacksheep and @Jumbo100! I want to thank you guys so much for your dedication, support, and wonderful guides! I have no idea what we would do without you! It's been a long ride, and I'm glad we get to share it with you fine gentlemen. Thank you for everything you've done!
Another huge shoutout goes to the fine folks who've sent some of their hard earned money towards the coffee fund. THANK YOU all so much! I really do appreciate it!
Oh, before I forget... my Linux enjoyers... we've got something cooking that I think you'll enjoy. Stay tuned!
Well, that’s all I got for now, stay safe everyone, and hope you all have a fantastic rest of your day/night! Until next time, peace!3
I don't necessarily see a problem with restoring the 2020 backup onto a 2019 model (they both run Android 9). However, I would HIGHLY advise against restoring the 2020's settings database onto the 2019 as there are some keys in some of the tables that could result in a soft brick if changed. But, if you're just trying to copy the apps from the 2020 to the 2019 then I say go for it. Just make sure to create a backup on your 2020 with ONLY the user apps option selected (make sure to name it something simple like "UserApps_Backup" for easy identification later), then restore that newly created backup onto the 2019 tablet. Here's how:
Launch the Toolbox, click the gear icon at the upper-right to open the settings, click the "About" tab in the Settings window, then click "Open Installation Directory".
This will open the Toolbox's root directory in File Explorer. Now click the "bin" folder, then "System Backups". In the "System Backups" folder, create a new folder, and name it "Amazon Fire HD 7 (2019)" (without the quotes). Now double click the "Amazon Fire HD 8 (2020)" folder, and copy the backup file you want to restore onto your 2019 tablet (the UserApps_Backup.7z file from earlier). Paste that backup file into the "Amazon Fire HD 7 (2019)" folder. Now the backup should show up in the Toolbox for restore.
Please note that I don't recommend restoring backups on different Android versions. But because both your tablets run Android 9 you should ok as long as you're just restoring user apps and package states.3Welp, an unexpected gift for those running a FireOS 8.3.2.2 on a Max 11 or HD10; not certain about other devices rocking FireOS 8. Google Voice typing is working again! I'm dictating this post on a Max 11.
Not sure when that got enabled; thought I had checked after fire OS 8.3.2.2 came out but perhaps not.
Happy yapping!3
Greetings
Failed to mention this in the method description - if the custom launcher can't be seen on the first few rows (the rows of apps present when Fire Launcher is started) and is further down the list then Automate won't start the launcher (tap on it) as it's waiting for the element to "appear" on screen. Try testing this theory out by swiping down on Fire Launcher and see if Automate starts the custom launcher once it appears on screen.3
Your File Management app set up as an Anonymous FPT client as default.
If you don't want Anonymous mode by default, reconfigure app as a regular Google/Android FTP client. -
383
Fire Toolbox V34.0
All-In-One Toolbox for Fire Tablets!
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.
Device Name: *Generation:FireOS VersionBase Android Version**RestrictedAmazon Fire HD 10 (2023) 13811Yes (8.3.1.9+)Amazon Fire Max 11 (2023) 13811Yes (8.3.1.9+)Amazon Fire 8 (2022) 12811Yes (8.3.1.9+)Amazon Fire 7 (2022) 12811Yes (8.3.1.9+)Amazon Fire 10/10+ (2021) 1179Yes (7.3.2.2+)Amazon Fire 8/8+ (2020) 1079Yes (7.3.2.2+)Amazon Fire 10 (2019) 979Yes (7.3.2.2+)Amazon Fire 7 (2019) 979Yes (7.3.2.2+)Amazon Fire 8 (2018) 879Yes (7.3.2.2+)Amazon Fire 10 (2017) 755.1NoAmazon Fire 8 (2017) 755.1NoAmazon Fire 7 (2017) 755.1NoAmazon Fire HD8 (2016) 655.1NoAmazon Fire HD10 (2015) 555.1NoAmazon Fire HD8 (2015) 555.1NoAmazon Fire HD7 (2015) 555.1NoAmazon Fire HD7 (2014) 455.1NoAmazon Fire HD6 (2014) 455.1No
* Generation equates to the year the tablet was released. For example, if the generation is 13 it means the tablet was released in 2023. 10 means the tablet was released in 2020... so on and so forth.
** Restricted equates to wether or not Amazon has locked down the firmware. When a firmware is restricted it means we cannot fully block OTAs, use custom launchers without Fire Launcher, lockscreen ads can no longer be permanantly removed, and some system apps can't be disabled. Even though a tablet is marked as Restricted in the table above, sometimes it may only apply to certain versions of FireOS. If your tablet is on a firmware before the listed firmware then your tablet is NOT restricted. See the "FireOS Restrictions and Fire Toolbox" section of the FAQ section (post #2) for further information on restricted firmwares.
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 - 2023) Guide:Before purchasing the tablet:- Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)
if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
Booting the tablet for the first time:- Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
- When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
- Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
- Select ANY network from the list (even if you don't know the password).
- Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
- At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
- It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
- You should immeditely be thrown into Fire Launcher. You're now ready to enable USB/ADB Debugging.
Enabling USB Debugging:- Turn on your tablet and go to Settings > Device Options > About Fire Tablet and tap on the Serial Number until you unlock Developer Options.
- Press the back button and find the new Developer Options and toggle it on.
- Scroll down till you find USB Debugging and enable it.
Setting up the drivers:If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time. - Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
- Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
- Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
- Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
- At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
- On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!
FIRE HD 6, 7, 8, 10 (2014 - 2017) Guide:Before purchasing the tablet:- Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)
if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
Booting the tablet for the first time:- Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
- When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
- Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
- Select ANY network from the list (even if you don't know the password).
- Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
- At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
- It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
- You should immeditely be thrown into Fire Launcher. You're now ready to enable ADB Debugging.
Enabling ADB Debugging:- Turn on your tablet and go to Settings > Device Options and tap on the Serial Number until you unlock Developer Options.
- Find the new Developer Options and toggle it on.
- Scroll down till you find ADB Debugging and enable it.
Setting up the drivers:If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time. - Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
- Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
- Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
- Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
- At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
- On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!
Windows:
SHA256 Hashes
Filename SHA256 Hash FTB_V34.0_Installer.exe df19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc FTB_V34.0_Portable.zip f47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f
VersionInstaller (.exe)Portable (.zip)Update PostVirusTotalChecksumsV33.1PostLinkV33.0DownloadPostLinkV32.4PostLinkV32.3DownloadPostLinkV32.2PostLinkV32.0DownloadPostLinkV31.0DownloadPostLinkV30.2DownloadPostLinkV30.1DownloadPostLinkV30.0DownloadPostLinkV29.0DownloadPostLinkV28.9DownloadDownloadPostLinkV27.0DownloadPostLinkV26.1DownloadPostLinkV25.2PostLinkV24.0DownloadPostLink*Halloween EditionDownload*Bug FixLinkV23.0DownloadPostLinkV22.0DownloadPostLinkV21.0DownloadPostLinkV20.0DownloadPostLinkV19.0DownloadPostLinkV18.0DownloadPostLinkV17.0DownloadPostLinkV16.0PostLinkv15.0PostLinkV13.0PostLinkV12.0PostLinkV11.1PostLinkV11.0PostLinkV10.2PostLinkV10.1PostLinkV10.0PostLinkV9.2PostLinkV9.1PostLinkV9.0PostLinkV8.2PostLinkV8.1PostLinkV7.2.1DownloadPostLinkV7.1PostLinkV7.0PostLinkV6.56PostLinkV6.55PostLinkV6.54DownloadPostLink
*Linux:
NOTICE: You must obtain the correct version for your installed Python version. Run "python3 -V" in the Terminal to get the installed python version for your distro.
SHA256 Hashes
Filename SHA256 Hash FTB_V5.0_Installer_Python3.10.7z 985f1fc24d21c7506b9245f8ba37194380535fb5a8ef9af762d7d6d3853498ec FTB_V5.0_Installer_Python3.11.7z 110bebfe5e28c75bd6235434f3b0ea640d6f24f77ef859a704db2a673972e01b
* 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:
ResourceResource LinkApplicable ToolsCustom Navigation Bar IconsNavigation Bar ModifierToolbox ChangelogsN/A
If you like my work and would like to support me feel free to Donate. Thank you!76
The Toolbox won't display correctly. The window is pure white and the text is faded. How can I fix this?
This can happen if window style and effects are turned off.
Windows 7
Control Panel > Performance Information and Tools > Adjust Visual Effects > Use Visual Styles on Windows and Buttons.
Image credit: @gsm2001
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!32I'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!!
28Last 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.)
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.
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.
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).
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.
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 detailedHere.
----------
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.
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.
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)21What'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:
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!
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!
- 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)
