I had to wipe the tablet and so Im trying to install all this over again. I choose install google services and it froze on step 2 downloading. I left it for over an hour. I closed it and restarted the google services install again. It went through everything this time but when it installed play services it gives me an error. it says i need to delete the apk and try again.
where do i delete the apk
Edit: Found the spot to delete the files.
Tried installing through the toolbox again and it still failed, so I just downloaded them myself and sideloaded the apks
Ok, I think I've managed to find a workaround to the Play Store issue for now. Below, I've attached a zip file containing the latest version of Play Services apk (21.33.13). Let's give it a try:
Please download and extract the archive to somewhere you'll remember.
Open the Toolbox, and navigate to Main Menu 2.
Execute the Sideload Apps tool.
Check the box next to "Reinstall" in the Installation Flags section.
In the App #1 category click the Browse button.
Navigate to the location where you extracted the .zip in the first step.
Double-click the PlayServices_21_33_13.apk file, and click the Sideload button.
Wait for the Toolbox to reinstall the app.
Once you see Success, please reboot the tablet.
That should do the trick, please let me know if you encounter any issues and I'd be more then happy to assist further. Best of luck guys!
I still cant get the playstore to work correctly
I have tried this one and it checks for update and then fails, 'something went wrong'
I tried searching and downloading the beta version (com.google.android.gms_21.36.14_(100400-395708125)-213614028_minAPI28(arm64-v8a,armeabi-v7a)(nodpi)) That gave the same error.
I found this post on Reddit asking whats going on with Google Play and people in the comments say joining the beta program for Google Play Services seems to fix the issue.
Hmm, I kind of wondered about that. Signing up for the beta allows you to install the beta version which would be an updated version compared to the one released via the standard channel. In fact, I'm guessing the apk from post #6,226 is the beta .apk just uploaded to APKMirror without mention of it being a beta version?
View attachment 5409573View attachment 5409575
first image is what i get then 2nd pops up i downloaded drivers then first message pops up again and nothing changes just keep getting same old first message.
Yeah, @Falcon342 is 100% correct. All you need is the redistributable and you should be good to go! Let us know if you run into any other issues and we'd be more then happy to assist further! Best of luck!
• Install the Apk provided below to your tablet (Android 7.0+ required)
• if you have a custom launcher installed go to that one (not the new one you just installed)
• in your launcher hold down on a blank spot, click widgets, now add the shade launcher widget, once you add the shade launcher widget a list will appear scroll through until you find "Screen saver" tap it, now it will be on your homescreen,
(If you added the widget to a different custom launcher you can remove now Shade launcher, the widget wont be deleted)
Now open the new widget and change the options and plug in your tablet to test.
(Note: a clock app is needed to use the screensaver to display time, the stock one should work)
Toolbox didn't seem to want to swap out the launcher on my 6th gens as well, tried both methods. I feel like the command that got spun up in the terminal failed, but didn't catch an exception...
It turns out i overcomplicated the process, if you add a normal settings widget there is a screen saver widget in there, although i dont know if this widget will be available on earlier versions of FireOS,
Hi - So I changed my PIN to a Pattern and am unable to enter the PIN any longer. Guess in my excitement must have missed a warning that there is no going back. Logging to my Amazon account I see no place to reset the PIN. There is no option on the tablet screen to enter my Amazon password either. I've attempted this from the 'change PIN' screen presented by Fire Toolbox and also on the main lockscreen where it DOES offer the option to reset the pin but when pressed does nothing. Any help would be appreciated. Thanks
I'm sad to inform you... there is unfortunately no way to disable the Pattern because I think Amazon never intended for it to be used in the first place. Unfortunately, the only way to remove it is to factory reset the tablet.
I've tried to find a workaround and haven't found anything yet. So sorry my friend...
I had to wipe the tablet and so Im trying to install all this over again. I choose install google services and it froze on step 2 downloading. I left it for over an hour. I closed it and restarted the google services install again. It went through everything this time but when it installed play services it gives me an error. it says i need to delete the apk and try again.
where do i delete the apk
Edit: Found the spot to delete the files.
Tried installing through the toolbox again and it still failed, so I just downloaded them myself and sideloaded the apks
Yeah, sorry about that! The message is vague and needs improving... perhaps actually telling the user where the apks are located so they can be deleted more easily? Anyway, even if it was through different means I'm glad you were able to find a solution! Great work my friend and sorry for the inconvenience!
I'm sad to inform you... there is unfortunately no way to disable the Pattern because I think Amazon never intended for it to be used in the first place. Unfortunately, the only way to remove it is to factory reset the tablet.
I've tried to find a workaround and haven't found anything yet. So sorry my friend...
Hi Datastream33. You might want to include a notice about the irreversability of Pattern Lock on the subtool so users are aware of this before they select that option (in the next update).
I'm sad to inform you... there is unfortunately no way to disable the Pattern because I think Amazon never intended for it to be used in the first place. Unfortunately, the only way to remove it is to factory reset the tablet.
I've tried to find a workaround and haven't found anything yet. So sorry my friend...
Haha oh well not an issue yet I guess, I only discovered it because of trying to install a CA certificate in Adguard to allow HTTPS filtering which asked for my PIN. Guess that's not getting installed! Hopefully you'll have an AHA!!! moment and get a reversal method in an upcoming release. Thanks for your hard work.
Yeah, @Falcon342 is 100% correct. All you need is the redistributable and you should be good to go! Let us know if you run into any other issues and we'd be more then happy to assist further! Best of luck!
also to note the C++ did work, i had it installed but it was damaged to i repaired it and now it runs, but now i have the messages that close the program out as shown above
The easiest way is to install a VPN type adblocker. I've successfully used DNS66 (available @ F-Droid.com) and another that I can't think of. DNS66 works very reliably, is free, uses little CPU and memory, and also blocks a lot of ads.
Thanks, I was looking for a way to use Pihole for the DNS but it doesn't look like this will be possible. Hopefully someone will succeed in unlocking the bootloader soon!
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 Compatibility:
Device Name:
Generation:
Amazon Fire 10/10+ (2021)
11
Amazon Fire 8/8+ (2020)
10
Amazon Fire 10 (2019)
9
Amazon Fire 7 (2019)
9
Amazon Fire 8 (2018)
8
Amazon Fire 10 (2017)
7
Amazon Fire 8 (2017)
7
Amazon Fire 7 (2017)
7
Amazon Fire HD8 (2016)
6
Amazon Fire HD10 (2015)
5
Amazon Fire HD8 (2015)
5
Amazon Fire HD7 (2015)
5
Amazon Fire HD7 (2014)
4
Amazon Fire HD6 (2014)
4
In this forum, you may hear the word "generation" being used when talking about Fire Tablets. Just know that "generation" effectively means the same as "what year was the tablet manufactured?". This may seem confusing and as a result a reference table has been provided for you below.
Getting Started:
Getting the Toolbox up and running with your tablet is surprisingly a very easy procedure. The only thing required is for you to enable Developer Options and ADB on your tablet. So, without further ado, let's get started.
At this point, please read the section below, and make sure to follow the correct guide that is made for your tablet on how to set up the device so it works with the Toolbox.
FIRE HD 7, 8, 10 (2018 - 2021) Guide:
1. Turn on your tablet and go to Settings > Device Options > About Fire Tablet and tap on the Serial Number until you unlock Developer Options.
2. Press the back button and find the new Developer Options and toggle it on.
3. Scroll down till you find USB Debugging and enable it.
4. Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
5. *Plug your tablet into your computer and allow Windows to install the necessary drivers (if you haven't done so already).
6. Open the Toolbox and wait for it to setup the environment and start ADB (It may appear that the Toolbox is frozen, just please give it a second).
7. If you are on Windows 8.1 or below the Toolbox will inform you that additional driver setup is required and will ask for your permission to download and install the required 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.
8. At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
9. 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:
1. Turn on your tablet and go to Settings > Device Options and tap on the Serial Number until you unlock Developer Options.
2. Find the new Developer Options and tap on it.
3. Scroll down till you find Enable ADB and enable it.
4. Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
5. *Plug your tablet into your computer and allow Windows to install the necessary drivers (if you haven't done so already).
6. Open the Toolbox and wait for it to setup the environment and start ADB (It may appear that the Toolbox is frozen, just please give it a second).
7. If you are on Windows 8.1 or below the Toolbox will inform you that additional driver setup is required and will ask for your permission to download and install the required 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.
8. At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
9. 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!
Tools and Subtools:
• 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.
1. I don't see my tablet listed in the supported devices, how can I request support to be added?
* For the requested tablet to be supported, we need a little more information from you in order to add support. Please download this .zip file, extract the folder within the zip to the desktop, and run the Identify.bat (make sure your tablet is plugged into the PC) file to get the code name of the device. Once the code name is found by the tool, press any key to copy it to the clipboard. Now reply to the forum with the code name, and the tablet's complete name. See the example below for reference:
Code:
Tablet: Amazon Fire HD8 (2018)[/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT][/INDENT]
[INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT][INDENT]Device Codename: karnak
* Please note that any devices produced before 5th generation unfortunately cannot receive support. I'd recommend visiting the forum for your device and rooting if possible. Sorry for the inconvenience.
2. What does the error "one of more ADB enabled devices are connected. please remove all devices except a supported amazon fire device." mean?
This error occurs when more then one ADB enabled devices are connected to your computer. Because multiple devices are connected, the Toolbox isn't sure which device to send the commands to so it simply closes and asks that you remove all ADB devices except the Fire Tablet. You may see the following terms being used in the PLUGGED IN list the Toolbox provides:
Code:
G0W0xxxxxxxxxxxxx
This is likely your Amazon Fire Tablet. Furthermore, any connected device connected via a usb cable to your computer will likely be a single string (such as the one shown above) and will not contain any special characters.
Code:
emulator-xxxx
This likely means an Android emulator is running on your system. Ensure programs like Bluestcks, Nox, Android Studio, Genymotion, LDPlayer, Virtualbox (emulating android), etc aren't running in the background while attempting to use the Toolbox.
Code:
192.168.0.xx
This means a device is connected to your computer via TCP/IP (wireless debugging) and has ADB debugging (USB Debugging) enabled. Ensure all devices that run Android in your household are either disconnected from the network temporary, or ADB Debugging (USB Debugging) is disabled. Examples of Android devices that may have ADB enabled: Fire TV, Android TV, phones, tablets, etc.
3. How can I remove a Google Account from my tablet?
Because of the missing accounts section in the Settings app it will be a little more difficult to remove Google Accounts directly from the tablet. The easiest way that I've found is to visit this page: https://myaccount.google.com/security, sign-in to your Google Account, scroll down to "Your Devices" and click the "Manage devices" button. From the list of devices find your tablet and in the upper right-corner click the 3-dot icon and from the list select "Sign out".
Unfortunately, the Toolbox is not yet capable of rooting any of the supported devices. There are plans to include root methods for a few select tablets but will take some time before they are ready.
6. Why is the Toolbox being marked as a virus?
The Toolbox (and it's installer) isn't signed with a software license and therefore your computer isn't sure who the publisher is which may worry some anti-viruses, effectively producing a false positive that flags the Toolbox as a virus. The same issue goes for Windows smart screen as well. 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!
7. Where did the Changelog go?
Due to the changelog's length it has been given its own post entirely. You can find it here.
8. I found a bug/issue in the Toolbox, how do I report it?
You may leave a post on this forum. Please include the error/issue and possible ways to replicate it, then copy down the error information (if the Toolbox presents any) and paste it as a post here on the forum. If you could also share a screenshot or video that would also help greatly. In addition, please make sure to also include what tablet you have and what tool the error is coming from and I will do my best to fix it ASAP. Thanks!
Buy me a Coffee:
If you like my work and would like to support me feel free to Donate. Thank you!
I just got a Fire HD 10 (2023) that I ordered yesterday.
When I ordered it, I did not uncheck the "Link the device to your Amazon account".
So far, I have not turned it on. Would it be a problem if it updates to latest FireOS?
Wouldn't I be able to still use the Toolbox??
If updating is a big deal, I guess I would just have to turn off my Wifi at home, turn the tablet on and factory reset it. This way it should forget my home wifi, shouldn't it?
It's fine if your tablet registers w/Amazon. As for updates, it really depends where your interests/passions lie. Blocking updates will give you more control over the device but an inferior experience with some apps, especially those linked to the Google ecosystem. Allowing updates will resolve most app issues but limit device customization. It's important to understand there is no going back once your device updates.
More recent Amazon devices (2022 and beyond) running FireOS 8 fare poorly with Google apps if not brought to at least FireOS 8.3.2.x. Once at that level there's little benefit to continued blocking.
If you value control and enjoy endlessly fiddling with your device then follow advise posted earlier in this thread to keep the Amazon boogeyman at bay. If you bought your device with the intention of using a variety of contemporary Google apps then allowing your device to behave naturally will yield the fewest hassles.
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.
Welp, 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.
Hello I have used V33.1 and I have a few problems, I have a fire kindle 8 2020 and I can’t disable fire launcher, (I am using Microsoft launcher BTW) also I am trying to restore a backup (made on fire toolbox) to my kindle 7 2019 but I can’t seem to find the backup I made on my kindle 8 to restore it on my kindle 7 plz can you help me.
(If my problems are fixed in the latest version,I can use it as I’m on holiday and I don’t have any Wi-Fi)
FTB is not designed as a full system backup utility; it basically just backs up the device "configuration state" . A full system backup requires system root access , which isn't available on newer Fire tablets.
Backups can be restored to a different device IF it's the same model and firmware version. (I.E. you have 2 Fire HD 8's that are both the same.) If you try to restore to a different model or year, you'll have to keep your fingers crossed. It might work, but don't rely on it.
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.
I used the Toolbox for the first time yesterday and installed the Aurora Store and remove screenlock. IIRC, I had to choose between signing in with my Google account or as Anonymous. I chose Anonymous. Now I find that my File Manager app (which I use to send books to the Fire using FTP) will only start FTP File Sharing if 'Anonymous' is ticked. If I untick it then there is no option to 'Start' the FTP.
As far as I can tell the Fire does not have a User called Anonymous. What do I need to do to keep the Aurora Store and get my FTP sharing back to being password-free? Thanks.
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.
IMPORTANT INFORMATION REGARDING FIREOS 7.3.2.2+ AND THE TOOLBOX (PLEASE READ)
If your tablet is running FireOS 7.3.2.2 or above please note that some functions of the Toolbox may not work due to new restrictions in the new firmware. The following tools either do not work or have limited functionality:
• OTA Updates - OTAs can no longer be disabled, but can be restricted.
• Manage Amazon Apps - Some system apps can no longer be disabled.
We're looking into workarounds to the issues detailed above. Please keep an eye on the forum for further development.
* 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!
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.
* 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.
My Home Button isn't working after using the Custom Launcher Tool?
Due to the way the process works, it alters your navigation bar's home key to send a key event that can be picked up by Automate. Once Automate reads this event, it launches your custom launcher automatically.
However, if the flow in Automate isn't running, the navbar key will not work, and nothing will happen when it's tapped. To fix this, either open Automate and start the "Launcher Invoker" flow again, or execute the Custom Launcher tool in the Toolbox, click the ":" icon (upper-right) to show the Tool Options panel, and click the "Restore Navigation Bar" button to restore the stock layout. You can execute the "reset_navbar" (without quotes) command in the ADB Shell tool.
Unfortuently, no matter how hard we try, we still haven't been able to get Family Link to work correctly on the tablets. The Family Link app fails to install, and the Child account refuses to login. No matter what we tried, we couldn't get a Child account to work on the tablets.
We believe this has to do with missing dependecies, and the tablets not being certified through Google's Play Protect platform. We're still activly looking into getting the issue resolved. Until then, it's recommended that you use an alternative such as Amazon's FreeTime, Eyezy, or another third-party family managing software.
How can I remove a Google Account from my tablet?
Because of the missing accounts section in the Settings app it will be a little more difficult to remove Google Accounts directly from the tablet. The easiest way that I've found is to visit this page: https://myaccount.google.com/security, sign-in to your Google Account, scroll down to "Your Devices" and click the "Manage devices" button. From the list of devices find your tablet and in the upper right-corner click the 3-dot icon and from the list select "Sign out".
Primarly, rooting a Fire Tablet requires the user to open the back of the device and short out a certain point on the motherboard. The Toolbox has been designed for folks who'd rather not bark down this alley. It uses the power of ADB to make changes, and is meant to be an alternative to rooting. In summery, the Toolbox isn't designed to root.
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!
I'd also like to take the time to acknowledge today as a very special day for this project! Today marks the 3RD YEAR anniversary of the project!!!
It seems like only yesterday, that the first version of the Toolbox was released! It's just crazy to think that it all started in 2019, as a very simple batch file program designed solemnly to remove lock screen ads, and has grown into what it is today! If you're interested in what started it all, I'd highly recommend checking out this post. It dives a little more into the Toolbox's background and it's beginnings!
I just wanted to THANK YOU all from the bottom of my heart for making the last 3 years so memorable! If it wasn't for the amazing support and this wonderful community, the project would've died a long time ago! You guys are the fuel that feeds the Toolbox's development!
Through this project, I've gotten to meet some wonderful people that I'd consider to be good friends: @Davy49, @Tailborn, @Falcon342, @blaacksheep, and of course you (the one reading this)!
So, where does the Toolbox go from here? Well, I suppose the next step would be to bring the Toolbox to more platforms! Currently, the Toolbox is being ported to other platforms using the Python programming language, and PySimpleGUI. I've also been asked if the Toolbox Python port will ever become open-source, and I think the answer is most likely yes. Big things are planned for the Toolbox this year, and I hope you'll join me on this journey!
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 detailed Here.
----------
3)Amazon Launcher.
New: Toolbox v29 has remediated most of the difficulties in replacing the launcher. Always check that you have the latest version of Toolbox. I'll leave the rest of the post up to inspire ideas.
The latest version of Toolbox (v 28.1) has a new tool called 'Custom Navbar Key'. This method uses Automate to automatically replace the Home button every time you reboot. It works rather nicely. I leave this section posted for completeness and to facilitate experimentation on other choices.
The way we're going to get rid of the Amazon Launcher is by not calling it! We're going to replace the Home button with another button that we can map to any launcher we'd like. This isn't a perfect solution, but it is FREE. If you're willing to spend a couple bucks, you can purchase a more configurable gesture navigation app with more features, but this is FREE, so maybe you can accept it's shortcomings. I'll keep this post updated with other navbar replacements that people suggest.
Go to the Play Store. Get and install "One Button Navigation". Launch it. It will want you to turn on Accessability Service for it. Follow the on-screen instructions and turn on "One Button Navigation Bar". You'll see your new nav button at the bottom of the screen. I like to adjust the width down to a dot, like the button it's replacing, but that's up to you. I also like to make the background black and the botton bright yellow so that I'm reminded it's running. Set up the background and button colors as you like them. Yeah, I know the ads in this are obtrusive, but you'll never see them once it's set up. Also DNS66 will block the ads if you install that first.
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:
----------------------------------------------------------
I sincerely hope everyone is doing good, and having a wonderful December so far!
Today marks the release of V26.0 of the Toolbox! So, without further ado... let's take a look at what this release has to offer!
Welcome, Welcome, Welcome... Screen!
You know, every time I run a build for the first time I go through the Theme Selector, then the Tour, and then the Welcome Screen. I just think to myself "this is just a mess" - so in this update I thought I'd focus on improving it and making it better. I started by re-designing the Welcome Screen and doing my best to link all three tools into something that looked visually appealing. Now, in a tabbed interface you'll find the Setup Tour in the very first tab, Theme Selection (with a new UI) in the second, Installation Management in the third, and finally in the fourth the Changelog.
Now let's talk specifically about the Installation Management tool. This bad boy now has the ability to read installations from directories other than the default (localappdata\Datastream). So, if you've got your installations in a custom location, and you'd like to manage them, it's now possible to point the path to that location. This should help make managing installations a lot easier!
Custom Launchers on FireOS 7.3.2.2
As some of you may know, I bit the bullet and updated my tablet to the latest version of FireOS... to the dreaded 7.3.2.2. This update, from what I heard, caused the Custom Launcher and disabling OTAs tools to no longer function and after updating, I soon discovered that it was indeed the case. I then tried everything I could think and well really didn't turn up any valuable workarounds... until I tried the method we'd been using on older gen devices... and it worked! Of course, just like on the older gens, it has the drawback of being removed every time the device is rebooted. However, it's the only method I could find, so it's better than nothing, right?
Anyway, while coding it in I decided to take the liberty of also clean up the code, and the UI a bit. What's cool is the tool will now read what generation your tablet is, and display what methods are available to use. You'll also find that the initial method selection UI is a lot more usable compared to its previous iteration.
Change the Timeout for the Display?
Ah, the latest addition to the General group in the Modify System Settings tool. This subtool not only allows you to alter the timeout to traditional values, but also allows you to set a custom timeout. Want your screen to sleep after 24 hours of inactivity? This one's for you folks who want to extend the timeout as much as you can. Just be careful, it may cause a burn-in if your tablet's screen remains on the same screen for too long!
Let's Talk Linux Port Stuff
I guess the point of this section is to ask you guys if you're ok with updates to the VB version being slowed down, so I can focus more on the port? I'd also like to address a common question I get asked about it being open-source. Right now, I'm planning on it being closed-source for now. However, I am planning on making it open-source when I feel like the time is right. Please be patient! So, let's get back to the original question... are you guy's ok if I shift primary focus to the port?
Wait, that's not everything! If you're interested in everything that's changed... please take a look at the changelog below:
Version 26.0 - Changelog
[Welcome Screen]
Updated the user interface.
Added better installation detection to the Installation Management subtool.
You can now specify what directory the Installation Management subtool will scan to detect installations.
Improved the look of the Theme Selector.
Fixed a bug causing the Startup Tour to not load tools correctly.
[Device Information]
Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
[Theme Selector]
Moved the Theme Selector to the Welcome Screen.
[Custom Launcher]
Improved the UI.
Made significant improvements to the code, and fixed various bugs/issues.
Added Re-route Homekey option for tablets running FireOS 7.3.2.2+.
[Modify System Settings]
Added the ability to change the "Display Timeout" to the General tab.
You can now set a custom Display Timeout of up to 24 hours.
[Lockscreen Management]
Improved the warning regarding the Pattern security type.
[Hybrid Apps]
Updated Disney+, and Netflix to the latest versions.
[Manage Amazon Apps]
When restoring from a debloat list, it now displays the proper header and message.
Ready to download V26.0? Head on over to the Download's section of the OP. By the way, because of some directory changes to the bin folder... the update will not show up in the Updater. It must be installed via the Installer or extracted from the Portable release.
Ok, my favorite part about of these release posts... sharing appreciation for you awesome folks! I just wanted to say I'm so blessed to be a part of the wonderful community over here on XDA. You guys are incredible people and in fact... this is perhaps the one place I've been on that I don't see negativity or people bullying one another. You guys are just AMAZING and I wanted to let you know that I appreciate everyone's support! Furthermore, you guys are what keep this project going, and it wouldn't be where it is today without you guys! So please pat yourself on the back - you deserve it!
Also, I'd like to place the limelight on my good friends @blaacksheep, and of course @Falcon342. I just can't express how much I appreciate all you've done for this thread! I haven't had the time to get on here because of work and when I come on the forum I see you guys helping out and answering questions. I really do appreciate the time and effort you two have put into being so freaking helpful! However, I've got to be honest, I'm extremely sad because I feel like I'm not doing enough. I'm sure you guys would like a little help (I'm gonna try harder to be more active on here when I can to hopefully help you guys out). Anyway, thank you guys again!! I really do appreciate it!!!!
Also, don't think I forgot about you donators! I just want to say I'm so honored that you'd donate your hard-earned cash. Sometimes I feel like I don't deserve it. Guys and gals, THANK YOU so much for donating! I really do appreciate every penny!
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!
