Unfortunately no. If a google account with active Family Link supervision is used on the Fire tablet, then that interferes with the ability to use Google apps on the tablet, even when the Family Link app is not installed on the tablet. The only "solutions" I'm aware of are to disable Family Link supervision on the google account, or use a different google account on the tablet.
[WINDOWS/LINUX][TOOL]Fire Toolbox V30.2
- Thread starter Datastream33
- Start date
How's it going, guys?
I sincerely hope everyone is having a great day/week so far!
I'm happy to announce that a new update has just been released! Now, let's take a closer look at what makes this update tick.
As always, BIG SHOUTOUT goes to all you lovely people who've shown their support, whether that be through interacting with one another, sharing resolutions to issues/problems, and being all around amazing people! I'd also like to take the time to THANK the folks who've supported through the means of donations... I REALLY do appreciate it and would like to thank you for being so kind.
Well, that's everything I've got for now... please have a wonderful rest of your night/day, and I'll see you guys later. Peace!
I sincerely hope everyone is having a great day/week so far!
I'm happy to announce that a new update has just been released! Now, let's take a closer look at what makes this update tick.
The New Reworked/Improved Pull and Push Tool
You may notice that when the tool is executed from the Main Menu, it will now immediately throw you into the tool instead of presenting a window where you'd select what subtool you wanted (pull or push). This window has been removed and replaced with 3 tabs that line the top of the tool's window: Push, Pull, and Delete. By default, the Pull tab will be selected by default. The window layout is basically the same as the original, except the back and home buttons have been relocated to the left of the address bar instead.
The Push tool when its tab is clicked will now condense the "Files in directory" and "Directories" lists to make way for the Push subtool that will take the original place of the "Files in directory" list. This change was made so when pushing a file or folder, the files in the current directory can still be viewed if needed.
The ability to delete files/folders off the internal storage has also been added in this rework.
Reading and processing of the internal storage has also been reworked, along with the Back and Home functions.
Multi-User Support is Finally Here
The Toolbox now supports applying changes to multiple users. This change wasn't easy and required a lot of changes under the hood, but it's finally here! Please let me know if you come across any issues with this new system.
When you launch the Toolbox, you should see a new icon next to the Settings that looks like an outline of a person. Clicking this icon will bring up a new panel where you can select what user the Toolbox will apply changes to. By default, the foreground user (the currently logged-in user) will be selected, but this can be changed by clearing the "Apply changes to the foreground user." checkbox. You will now have the option to select what ever user you want from the list above the checkbox. However, keep in mind that any operations that require the user to be in the foreground may cease to function.
The UI Frontend for ADB Shell
This tool took some time to get working and frankly was one of the most annoying things to produce. Anyway, enough about ranting and let's take a look at what this tool adds. Firstly, one of the major features of this tool is the fact that you now can log the session. Any command typed and executed (if the user has enabled logging of the session) will be outputted to a log file that's saved to the user's Desktop.
Command history is another thing that was added. Unlike the real thing, the Toolbox will save and remember commands you've executed and will even be available if the window is closed and a new session is started. This works by saving the executed commands to a text file in the ADB folder and parsing through it when the user presses the up or down arrow keys.
My favorite part of this tool is the ability to toggle between using a debug shell or a standard shell when using a 7th gen device. Making commands such as "ls" and "cd" available in the /storage/emulated/0 directory.
In addition, if you even want to go back to using ADB in CMD (like before) then all you need to do is open the Toolbox's Settings and check the box for "Start ADB Shell Tool in CMD". This will force the Toolbox to open the instance in CMD instead.
Toolbox Updater and Micropatches
In this update, the Toolbox Updater has been upgraded to include a better function for installing micropatches. Instead of making the required changes (like renaming the directory) in the Toolbox Updater itself, the Updater now generates a batch file in the Temp directory to take care of finishing the process. This is good because it ensures no processes are still using the folder (Toolbox Updater)... allowing it to actually be renamed properly. This should solve the issue of the shortcuts pointing to an invalid location causing Windows to not be able to locate the Toolbox's main executable.
Wait, that's not everything! Take a look at the below changelog for the full scoop...If you are ready to download the new update, head on over to the Downloads' section of the OP. Please keep in mind, because the Toolbox Updater is receiving an upgrade, the update must be downloaded and installed manually.
As always, BIG SHOUTOUT goes to all you lovely people who've shown their support, whether that be through interacting with one another, sharing resolutions to issues/problems, and being all around amazing people! I'd also like to take the time to THANK the folks who've supported through the means of donations... I REALLY do appreciate it and would like to thank you for being so kind.
Well, that's everything I've got for now... please have a wonderful rest of your night/day, and I'll see you guys later. Peace!
Last edited:
Awesome update. Thank you for your continued hard work!
Just got the tablet and was wondering if there is anyway to control the charging of the battery without root access? Unfortunately got the 11th gen, which cannot be rooted as of this writing. Trying to use the tablet as a home automation kiosk and want to adhere to the 80/20 rule for charging. Would love to not kill the battery or be forced to take it out
Just got the tablet and was wondering if there is anyway to control the charging of the battery without root access? Unfortunately got the 11th gen, which cannot be rooted as of this writing. Trying to use the tablet as a home automation kiosk and want to adhere to the 80/20 rule for charging. Would love to not kill the battery or be forced to take it out
Gotcha. Thanks!
Yeah, I saw it being possible if you get a smart charger and it'll just kill the power to it once it detects it at X battery level. But that's unfortunate to hear that the stock firmware can't even have this function. Here's hoping Amazon adds it down the road.
Yeah, I saw it being possible if you get a smart charger and it'll just kill the power to it once it detects it at X battery level. But that's unfortunate to hear that the stock firmware can't even have this function. Here's hoping Amazon adds it down the road.
So, I did a Factory reset and still same issue will not let me register the device, keeps saying my information is incorrect, I have verified that it is correct. I even called support they had me do a wipe throught the recovery menu and still same issue. Now, they are asking me to return the device so a tech can look at it, any other thought befor I go that route?
Thanks
Before you return the device, it may be due to it being new and not fully explored by this tool and users discovering new problems that were just introduced.
If you want to explore a little further, download ADB App Control from CyberCat on XDA from here. Install and run it and let it install it's associated app on your tablet.
Under the Applications tab (1), select Disabled (2). In the search box (3), enter "kindle". Enable any of the apps in (4). Click "Apply" (5). Then close ADB App Control.
This image was from my Fire 10 (2019) so it could be different for the new tablet. Reboot your tablet and try using the Kindle app again.
Edit: Also check that under All or System, that "Content Management System" (com.amazon.kindle.cms) is enabled.
Last edited:
The saga continues, Under disabled apps and searching kindle nothing shows up
Me as well. I did learn a new app so yea! We'll see what the tech at Amazon say, If all else fails and they don't do anything I will de-Amazon it like before and use it as I was, just will not be able to use Kindle App, no huge loss, I can read my books on my Phione
I'm just outside the return window but well witin Warrenty, they are going to check it out and either resolve or return it to me, if they can't fine a problem. My hope is they just replace it and call it a day.
I'll update once I get it back They say within 5 days
Hey, @Datastream33, thanks for the great app - it's like a Swiss army knife for Fire HDs, all in one! I'm using your app all the time and just donated $10 to you (this should be done much earlier, sorry!)
I have one feature request to you (if it's possible of course!): currently I'm making a "backup copy" of my primary Galaxy Tab A5 on my newly received Fire HD 10 (2021) - just in case of battery discharge or accidently broken screen (by my kids) or.. whatever
Everything are copied fine, and my new Fire HD 10 looks & works exactly as my Galaxy Tab, except Chrome web shortcuts on home screen. BTW, Chrome, installed on Fire HD, is missing option to add shortcut on home screen, however Nova launcher restored all apps & web shortcuts perfectly (web shortcuts with correct icons). But... when I tap on web shortcut, nothing happened but just an error message "permission denied" shown. Do you know how to fix the issue? That will be nice!
Thanks a lot, man! Please keep working on this perfect software!
I have one feature request to you (if it's possible of course!): currently I'm making a "backup copy" of my primary Galaxy Tab A5 on my newly received Fire HD 10 (2021) - just in case of battery discharge or accidently broken screen (by my kids) or.. whatever
Everything are copied fine, and my new Fire HD 10 looks & works exactly as my Galaxy Tab, except Chrome web shortcuts on home screen. BTW, Chrome, installed on Fire HD, is missing option to add shortcut on home screen, however Nova launcher restored all apps & web shortcuts perfectly (web shortcuts with correct icons). But... when I tap on web shortcut, nothing happened but just an error message "permission denied" shown. Do you know how to fix the issue? That will be nice!
Thanks a lot, man! Please keep working on this perfect software!
Hey, @Datastream33, thanks for the great app - it's like a Swiss army knife for Fire HDs, all in one! I'm using your app all the time and just donated $10 to you (this should be done much earlier, sorry!)
I have one feature request to you (if it's possible of course!): currently I'm making a "backup copy" of my primary Galaxy Tab A5 on my newly received Fire HD 10 (2021) - just in case of battery discharge or accidently broken screen (by my kids) or.. whatever
Everything are copied fine, and my new Fire HD 10 looks & works exactly as my Galaxy Tab, except Chrome web shortcuts on home screen. BTW, Chrome, installed on Fire HD, is missing option to add shortcut on home screen, however Nova launcher restored all apps & web shortcuts perfectly (web shortcuts with correct icons). But... when I tap on web shortcut, nothing happened but just an error message "permission denied" shown. Do you know how to fix the issue? That will be nice!
Thanks a lot, man! Please keep working on this perfect software!
I think the problem of shortcuts not being available in Chrome and web shortcuts not working is due to Nova Launcher not having all it's defaults. I think you need to issue the following ADB command to fix that:
Code:
adb shell pm set-home-activity com.teslacoilsw.launcher/activityThanks for suggestion but this doesn't work for me, I'm getting an error:
Code:
java.lang.IllegalArgumentException: Component ComponentInfo{com.teslacoilsw.launcher/activity} cannot be home on user 0I was just trying to put together something that Datstteam33 said a couple of pages ago with the app name of the Nova Launcher. If you go back to page 292 or 294, I think you'll find a conversation about the same problem you're having. I think he solved it by installing yet another launcher just so he would be offered the option to set the default. Then Datastream33 commented about the launcher not having all it's defaults and saying it was a simple ADB command to fix it which he revealed several posts later. I didn't try it out but just replaced <appname> with the lancher name and posted it. Maybe I've given you enough info to solve your problem. If not, I'll look into it further tomorrow.
I think you're mistaken or got me wrong: there is no conversation about my issue on these pages - guys are talking about setting default launcher by using adb command. But Nova launcher is already set as my default launcher, and widgets support is already enabled - I have no issues at all.
I suspect that creating web shortcuts in modern Android (not sure about FireOS) uses a different API than the widgets API. Or it will require some additional permission(s). So, in my case, set-home-activity command doesn't make any sense.
So, I believe, there are few possible options to solve the problem:
- find a way to grant specific permissions for Nova Launcher
- ask Nova Launcher devs to add "web shortcut" feature (but, I afraid so, simple impossible - a lot of Nova customers are already asked for that feature for a years without any luck)
- find a simple standard Android widget with launch a specific web page functionality. This is a very possible option, I believe so (especially if look for the old widgets for former Android OSes). Unfortunately, I can't find any old/outdated widget with required functionality
- write this widget by myself
Last edited:
Hi,
First of all, thanks for your work and effort in supporting this for so many generations. I have two questions regarding some functionality for the Fire 10 (2019)
1. Is it possible to remove the camera and device dashboard shortcuts from the lock screen?
2. I enabled the cast option through the navigation bar. Whenever I try to cast my tablet to my roku tv, it does not appear. This happens in my Google pixel as well, which I solve by going into settings and enabling wireless display. Is there a way to enable this?
Thanks for the help
First of all, thanks for your work and effort in supporting this for so many generations. I have two questions regarding some functionality for the Fire 10 (2019)
1. Is it possible to remove the camera and device dashboard shortcuts from the lock screen?
2. I enabled the cast option through the navigation bar. Whenever I try to cast my tablet to my roku tv, it does not appear. This happens in my Google pixel as well, which I solve by going into settings and enabling wireless display. Is there a way to enable this?
Thanks for the help
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6New Platform, Who 'Dis?
How's it going guys?
I sincerely hope everyone had a fantastic weekend, and all the mothers out there had a fantastic Mother's Day!
I've got something so exciting to share with you, and I can't wait to share all the details! So, let's not dilly dally and jump right into the announcement!
I'm so excited to finally share the port with you all! So, in true fashion, let's get started with the port background!
The Linux Python port is finally ready to be released!!
The Extremely Interesting Port Background
For the longest time, the Toolbox has been a Windows only application. As you all know, it started out as a simple batch file and then was shifted to Visual Basic back in 2020. In the Visual Basic announcement post, I stated that I'd code the Toolbox in a way that would allow it to run under Wine for those of you who were running Linux. Well at the time I knew nothing about Linux, and was naive to think that I could just change code around and it would magically run on Linux easy peasy. Surprise, surprise it wasn't that easy! So, the Linux port was thrown on the back burner.
A year or so later I started learning Linux, and fell it love with it. I decided to take my new experience and run with it. So, I started looking into ways I could port the Toolbox to Linux. I tried so many different methods, but none of them stuck with me. I had the problem of building up a prototype but then dumping it in exchange for trying something new. This is partially why it took so long for the port to be released, could never settle on just one platform.
Some time in 2022, I came across PySimpleGUI while learning the Python programming language and instantly fell in love with it. So, development started, and the rest is history. Pretty exciting stuff right? My main point to this section is to come clean on why it took so long for the port to be released. So, I'd like to take a second and just apologize for taking so long. You guys have been patiently waiting, and I can't thank you enough for your godly patience. Better late then never, right? right?
Linux Base Compatibilities?
When testing, we mainly targeted Debian based distros, primarily KDE Neon and Mint. We're not exactly sure how well the Toolbox will play with other derivatives, so if you're on an RPM, Fedora, RHEL, openSUSE, etc base then please let us know how the Toolbox works with your distro! We're very curious! Also, a HUGE shout out goes to my good friend @blaacksheep for taking time out of his day just to test the alpha builds! Your reports have massively helped during development and I can't thank you enough! You're the man as always!
What Will I Need to Run the Toolbox?
The Toolbox does have a few dependencies that must be resolved before the Toolbox will function:
Name Why It's Required Required Version Type Python 3 Execute the Toolbox's scripts. 3.10+ package (obtained using package manager) Pip 3 Download and install dependency modules. 23.0.0+ package TKinter Dependency GUI toolkit for PySimpleGUI. Any package ImageTK (Pillow) Modify/use Pillow image objects in PySimpleGUI. Any package PySimpleGUI GUI framework. Any pip module (obtained using pip3) tqdm Show download progress bars. Any pip module requests Download data from the internet. Any pip module Pillow Resize images given by the user for display in the GUI. Any pip module
Let's Talk About The Installer!
In order to make the installation process as seamless as possible, we've cooked up an installer that should ease the installation process! The Installer is designed to check for, and even install (pip modules only) dependencies, inform of the Toolbox's Privacy Policy/Terms of Use, extract and install the latest TB build, and create menu/desktop shortcuts! Very cool, yes?
However, much like the Toolbox, the installer is still in beta. You may come across some bugs/issues that could impact the overall experience. If you do happen to come across any while using the Installer please let us know so that we can squash that bug asap, and create a better experience!
Download
While in Beta, I'd like to heavy push the installer so that we can get it to stable along with the Toolbox. So, for now, the only download option will be the installer. Once the Toolbox and the Installer are both stable a portable option will be available. However, if you really need a portable version please PM and I'll send you the link.
Version Installer (.exe) V1.0 (Beta) Download
Bugs/Issues
The Toolbox (and it's installer) is currently in the beta stages. It's not 100% caught up to the Windows version, so there may be some missing features. You may also encounter some bugs/issues that may impact the overall experience. If you do come across any, please, please let us know about them so they may be fixed. When reporting a bug please provide the following info:
- What Linux distro are you on?
- What tablet do you have? (please provide the tablet's name, it's generation, FireOS version)
- What tool did the error occur in, and what process caused the error to occur?
- Is there any error output when running the Toolbox in a Terminal?
- What Python3/Pip3 version are you running?
- Do you have a screenshot of the error?
Notes
- If the Toolbox gets stuck on the "The Toolbox is starting the Android Debug Bridge (ADB)" screen for more then 30 seconds you may need to grant execute permissions to the adb binary file in the "Fire Toolbox V1.0\adb\unix\" directory. Once granted, close out of the Toolbox and re-launch it.
- While the Toolbox is written in Python, it is not open-source (yet). Perhaps it will be some time in the future, but as of now it will be closed-source. Thank you so much for your understanding.
- The port may not run on Windows. My primary focus was on Linux, but it's a possibility that one day it will.
On an entirely different note, a new update is being developed for the Windows version. I understand that the Automate methods are somewhat of a headache right now, so that's being looked into. Are there any other issues/bugs you guys feel need to be addressed with the Windows version? Please do let me know!
Well, that's all for now folks! Hopefully you're all having a terrific Wednesday so far! Love you all, and I'll catch you on the flipside! Peace.3
Greetings!
Great catch my friend. The Toolbox originally wasn't going to support spaces in the root directory path (as you pointed out in the error message - the spaces weren't handled properly resulting in a broken path). However, @blaacksheep being the good guy that is, highly recommended that it should. Had to rewrite some tools but in the end the root directory now supports spaces. However, it seems I missed the path conversion for the debugger installation function. The issue has been fixed and an update has been released.
Yeah, douglas runs FireOS 5 which requires the debugger to be installed before the Toolbox can interact fully with the device. It allows us to hide packages, and perform some other interactions that wouldn't be possible without it. I'm starting to wonder if there's an equivalent for other FireOS versions that can be used to disable the protected packages on FireOS 7. Can't remember how we obtained the FireOS 5 one though.
I'd like to sincerely apologize for my late response. Glad to see you were able to find a workaround though!
Again, thank you so much for the report! By the way, how are things going with the port on your end? Is everything functional (besides the debugger failing to install)?2
thank you--that worked!! the issue, then, seems to have been something with calibre...!!!!22Hello i got a a Fire HD 10 Plus (11. Genration) for my kids.
I downloaded the Fire toolbox and installed the Nova Launcher.
All is finde. By rebooting the System the Nova launcher doesn´t launc automatically.
Can i change this or is it normal?
Or ist there another way to get the Nova Launcher start automatically?
Hijack Launcher (Any Launcher?)
-
365
Fire Toolbox V30.2
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:Amazon Fire 7 (2022) 12Amazon Fire 10/10+ (2021) 11Amazon Fire 8/8+ (2020) 10Amazon Fire 10 (2019) 9Amazon Fire 7 (2019) 9Amazon Fire 8 (2018) 8Amazon Fire 10 (2017) 7Amazon Fire 8 (2017) 7Amazon Fire 7 (2017) 7Amazon Fire HD8 (2016) 6Amazon Fire HD10 (2015) 5Amazon Fire HD8 (2015) 5Amazon Fire HD7 (2015) 5Amazon Fire HD7 (2014) 4Amazon 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.
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!
• 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.
Windows:
VersionInstaller (.exe)Portable (.zip)Update PostVirusTotalV30.1PostLinkV30.0PostLinkV29.0PostLinkV28.9DownloadPostLinkV27.0PostLinkV26.1PostLinkV25.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:
* 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!70
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)
