Thank you for the comprehensive answer, exactly what I was looking for!
So based on this, it sounds like the Fire HD 8 (2020) should work well with Fire Toolbox.
[WINDOWS][TOOL]Fire Toolbox V30.2
- Thread starter Datastream33
- Start date
So based on this, it sounds like the Fire HD 8 (2020) should work well with Fire Toolbox.
I have a Fire HD 8 (2020). It came with firmware v7.3.2.2. It already suffers from the problems associated with the new(er) firmware. I bought it knowing that, to help out mitigating the problems. If you want one with earlier firmware, you'll have to get one from 2019 or earlier. Large retail box stores like Target are a good place to look besides checking out refurbs on Amazon Warehouse. You'll have the best chance getting older stock with pre-7.3.2.2 firmware.
(BTW, it works quite well despite the newer firmware.
)11th Gen Fire HD10 (2021) : FireOS 7
12th Gen Fire HD 7/8 (2022) : Fire OS 8
Suspect next Fire HD10 (Spring 2023 ?) will be 12th Gen with FireOS 8.
Edit: My Fire HD10 (2021) came "factory fresh" with f/w 7.3.1.? and was replaced under warranty (in July 2022) with a refurb unit with f/w 7.3.2.2
Last edited:
Thanks for clarifying. I wasn't sure about the 2021's. I was thinking that more than just the 2022 HD 7/8's were FireOS 8 but wasn't sure when I posted that.
So @tk423 : if you want Google Play Services and thus Google Play Store, don't buy the 2022's.
Just bought a Fire 10 (2021) yesterday since I wanted to use it for some sort of custom display. This was also a refurb unit and it arrived ~7AM today. It has OS 7.3.2.3, if that helps.Thanks for clarifying. I wasn't sure about the 2021's. I was thinking that more than just the 2022 HD 7/8's were FireOS 8 but wasn't sure when I posted that.
So @tk423 : if you want Google Play Services and thus Google Play Store, don't buy the 2022's.
Haven't connected it to wifi or disabled OTA yet, but will try DNS66 for blocking OTA updates and see what sticks.
Awesome job on the tool guys, thank you!
Hi, and welcome to XDA!
I've purchased several items from Amazon Warehouse (the refurbished items) and they've all been in "like new" condition. Most are only a dollar or 2 cheaper than new, but for tablets you have a better chance of getting an earlier firmware.
It's too bad yours didn't come with v7.3.2.1 or earlier. You can still work with 7.3.2.3 though. Just remember to select any WiFi network and then go back a page when it asks for your password for the "skip" option to appear at the bottom of the WiFi setup page.
RethinkDNS is a better option than DNS66 and I'm writing up a guide on setting it up right now. It's not that hard, but there are so many things that can be set in RethinkDNS and the options aren't as clearly labeled as I'd like, so I figured I'd make a guide so I'd only have to type it all out once.
Jumbo100 says that v7.3.2.6 is out now. Who knows what new options they'll block with each new "upgrade". You probably don't want any "upgrades".
Have fun with your new tablet. Just don't expect it to be a speed demon because of the limited hardware. If you keep it simple and don't overload it with software it'll treat you well.
I have done so and won't turn on wifi until I figure out the DNS blockerHi, and welcome to XDA!
I've purchased several items from Amazon Warehouse (the refurbished items) and they've all been in "like new" condition. Most are only a dollar or 2 cheaper than new, but for tablets you have a better chance of getting an earlier firmware.
It's too bad yours didn't come with v7.3.2.1 or earlier. You can still work with 7.3.2.3 though. Just remember to select any WiFi network and then go back a page when it asks for your password for the "skip" option to appear at the bottom of the WiFi setup page.
RethinkDNS is a better option than DNS66 and I'm writing up a guide on setting it up right now. It's not that hard, but there are so many things that can be set in RethinkDNS and the options aren't as clearly labeled as I'd like, so I figured I'd make a guide so I'd only have to type it all out once.
Jumbo100 says that v7.3.2.6 is out now. Who knows what new options they'll block with each new "upgrade". You probably don't want any "upgrades".
Have fun with your new tablet. Just don't expect it to be a speed demon because of the limited hardware. If you keep it simple and don't overload it with software it'll treat you well.
Will wait for that guide. Meanwhile I won't really need to use the tablet for much - so I'll keep it lobotomized and can try out RethinkDNS from a fresh-ish tablet here.
Speaking of, is there a way to get notified by that guide when it comes out? I'm not too sure how XDA notifications work so far.
Performance shouldn't be a problem - I just want it to run one custom app all the time, and debloating it + removing ads should be good for all my purposes.
Thanks!
I'll link it in my signature so that anyone who wants to read it will only have to go to my last post to find it. I'll try to get it done before the weekend.I have done so and won't turn on wifi until I figure out the DNS blocker
Will wait for that guide. Meanwhile I won't really need to use the tablet for much - so I'll keep it lobotomized and can try out RethinkDNS from a fresh-ish tablet here.
Speaking of, is there a way to get notified by that guide when it comes out? I'm not too sure how XDA notifications work so far.
Performance shouldn't be a problem - I just want it to run one custom app all the time, and debloating it + removing ads should be good for all my purposes.
Thanks!
Arrrgh!!! I uninstalled RethinkDNS so that I could write up a guide to setting things up and documenting the whole procedure. Everything was going great, I downloaded a fresh copy on my computer which was a newer version than the one I had been using. I installed and configured it as I was writing my guide. I rebooted the tablet and, lo and behold, I got a message saying that RethinkDNS had been disabled. I tapped it to start it up again, rebooted, and same thing.
I'd forgotten that I originally used a second app, Activity Launcher, to get to the hidden setting "VpnSettingsActivity", where you can enable "Always On VPN". Then it was working again.
So I just have to add a few steps to my guide so it's not hard to follow. I'm almost done and it will be posted in a day or so. Bear with me and I think you'll be happy if you want to set this up. Almost there!
I'd forgotten that I originally used a second app, Activity Launcher, to get to the hidden setting "VpnSettingsActivity", where you can enable "Always On VPN". Then it was working again.
So I just have to add a few steps to my guide so it's not hard to follow. I'm almost done and it will be posted in a day or so. Bear with me and I think you'll be happy if you want to set this up. Almost there!
Hello everyone, does anyone here feel that the FireHD tablet's PIN is dying too quickly. I bought my FireHD10 2019 in May 2021, now it's November 2022 (about 1.5 years). My available PIN capacity is only about 70%. I do my test with Accubattery and observe by eye. The battery capacity is fully charged to 100% and quickly drains to 70% in about 5-10 minutes (watching Youtube and reading stories). From about 70% or less, it works properly. 1.5 years of battery capacity remaining 70%, is that normal? I only use it for the purpose of watching youtube and reading stories, my charging cycle is about 4-7 days for a single charge.
Lithium ion batteries lifetimes depend on their usage. In your usage case, you may be better served to only charge them to 80%, and don't discharge them below 40%. I know that doesn't even use half of their capacity, but if the tablet is always home near a charger, it shouldn't be a problem. I try to keep my batteries within those bounds unless I'm planning on an extended use situation. I use Battery Charge Monitor on my devices that aren't rooted to alert me when I reach those boundaries. My last phone is still going strong on it's original battery and it's a Moto G6 purchased in 2019. (It's old, I know.)
The reason to stop at 80% is because of the stress a full charge puts on a battery. Charging above 80% eventually leads to swollen batteries and I'm sure you've seen that before. The reason to not discharge below 40% is that not using the full capacity of the battery doesn't require as much of a battery's life in recharging. They only have a limited number of full charge cycles before they lose capacity like an SD card only has a limited number of write cycles. Li-ion batteries also don't suffer "memory effect" like earlier Ni-Cd batteries do and the limited charge range will not affect the ability to fully discharge them if the need arises. Also a large number of partial charges is easier on the battery than a smaller number of full charge/discharge cycles.
Last edited:
sticky wicket.
I saw a post that said to 'uninstall g-play services' and i did (but from tablet settings menu instead of from FTB39.02 (Ugh!!)...
Now I can't seem to find the package to reinstall.
UPDATE/Solution (doy!)
on the main menu of the Fire Tool box, click the gear icon in upper right side
run the startup commands again, and all worked fine.
I saw a post that said to 'uninstall g-play services' and i did (but from tablet settings menu instead of from FTB39.02 (Ugh!!)...
Now I can't seem to find the package to reinstall.
UPDATE/Solution (doy!)
on the main menu of the Fire Tool box, click the gear icon in upper right side
run the startup commands again, and all worked fine.
Just a quick note..
Just updated to 29.2
I reset my tablet (I've done silly things to it and finally decided to start over).
All went well until I tried to install a new launcher. The tool couldn't find the apks. After I managed to read the various error dialog boxes, I navagated to:
C:\Users\Simeon\AppData\Local\Datastream\Fire Toolbox V29.0
Whilst poking around (this is on window 10 home) I found that the "Custom Launchers" sub-directory in the bin directory had not been created so the tool had no place to download the apk to. I created the directory in the proper place and I was able to install LawnChair sucessfully.
Also while trying to get Contact Syncing installed, I got another error.
in ../bin/Google Services/Android (x(32) the tool was looking for ConSync9.apk It wasn't there, but ConSync7.apk was! I renamed the file to 9 and reran the tool and all was well.
I just thought I'd drop by in case this hadn't been figured out yet. While using the tool a dialog popped up saying there were issues with installing launchers in v29.
I hope this information helps.
Just updated to 29.2
I reset my tablet (I've done silly things to it and finally decided to start over).
All went well until I tried to install a new launcher. The tool couldn't find the apks. After I managed to read the various error dialog boxes, I navagated to:
C:\Users\Simeon\AppData\Local\Datastream\Fire Toolbox V29.0
Whilst poking around (this is on window 10 home) I found that the "Custom Launchers" sub-directory in the bin directory had not been created so the tool had no place to download the apk to. I created the directory in the proper place and I was able to install LawnChair sucessfully.
Also while trying to get Contact Syncing installed, I got another error.
in ../bin/Google Services/Android (x(32) the tool was looking for ConSync9.apk It wasn't there, but ConSync7.apk was! I renamed the file to 9 and reran the tool and all was well.
I just thought I'd drop by in case this hadn't been figured out yet. While using the tool a dialog popped up saying there were issues with installing launchers in v29.
I hope this information helps.
I just had a look at FTB 30.0. It seems that there's a new, still in testing method of restricting OTA Updates! I'd like to give this a try, but @Datastream33 says I should back up all my installed stuff and reset the tablet first. I'm going to hold off on this for the time being and see what the other users have to say about how effective this is. I'd really like to hear more about the method. I suppose I could dig around the OP and find the release notes, but I'm sure he'll post something soon about this. Anyways, great work, Datastream! Keep us posted on the new restriction method.
I just checked my HD 8 Plus and the OS went from 7.3.2.4 to 7.3.2.6 even though I run DNS66 and wait for the shield before enabling Wi-Fi. However, I can't discern any real operational difference between 7.3.2.4 to 7.3.2.6. But I'd like to buy another one running 7.3.2.1 or earlier if I was certain of the OS. Any ideas?
Thanks for the new version V30.0
Unfortunately, still unable to modify anything to do with the navbar on Fire OS8 models. My 2022 Fire 7 and 8 cant disable device dashboard icon or rearrange any of the softkeys using the modifier. You're able to change the settings within toolbox, but none of the changes reflect on the tablet. Not sure if this was talked about recently or if its unfixable.
Unfortunately, still unable to modify anything to do with the navbar on Fire OS8 models. My 2022 Fire 7 and 8 cant disable device dashboard icon or rearrange any of the softkeys using the modifier. You're able to change the settings within toolbox, but none of the changes reflect on the tablet. Not sure if this was talked about recently or if its unfixable.
I think it was mentioned about a week ago. What has probably happened is that they changed the way that the navbar functions in FireOS 8. Datastream probably won't be able to do much about it without access to a new 2022 tablet to see what changes have been made or if he reads about the changes in FireOS 8 somewhere in the Android forums. Amazon isn't about to provide a roadmap for him to follow in order to defeat their OS programming.
(You could always donate a new tablet to him so he can attack the problem! LOL)
Similar threads
Top Liked Posts
-
2FireOS 8.3.1.3 can still be manually downloaded at https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE
but that can change at any moment. You've been warned.
Does anyone know of any tool that can extract apk files from an OpenGApps zip download?
I've been spelunking around XDA trying to find any such tool but with no luck.
I found one of questionable charactor (i.e. malware) for editing ROMs such as for LineageOS but but doesn't seem to work with an OpenGApps zip file.1
Thanks for your insight on AWS servers ... something I really never thought much about before.
I think I may have to do a major "rethink" on my approach to the Amazon/FireOS infrastructure.
Get back to you soon, after I think this through.1
I think it's an issue for every new Gen 12 Fire tablet user !
Short story: Google Play infrastructure and FTB mods seem to more stable with f/w 8.3.1.3 , so you may need a f/w update to get things sorted out.
Check out some recent posts on the thread to get a scope of the problem and the various solutions offered.
A complicating factor is the recent roll out of f/w 8.3.1.4 OTA ... unknown effects .. for better or worse.
Suggest doing the additional research and pinging us again to see how you would like to proceed.
Goggle Account Authentication is a common problem but may be related to the above. FWIW try the following:
- clearing the data/user caches from the 4 Google Play apps
- signing-out of your google account from your computer or a browser
- rebooting your device
- signing-in again from your Fire tablet.
The Fire Toolbox problem with Google Play installation is unclear. Did you "side load" the 4 Google Play apps before using Fire Toolbox?1Hey , a shout-out to Gen 12 Fire tablet users in the Community !
Amazon is now "pushing" FireOS 8.3.1.4 updates via OTA.
If you have recently updated to f/w 8.3.1.4 ( intentionally or unintentionally ! ) , we could really use some feedback on how it's affecting the Google Play infrastructure and any FTB mods ... for better or worse.
Currently, f/w 8.3.1.3 seems to be working reasonable well, but f/w 8.3.1.4 is an unknown quantity ... hoping that f/w 8.3.1.4 is okay.
Your help is keenly anticipated and appreciated. Thanks.1
Thank you. So first i will update to 8.3.1.3.
I went to the Amazon page but I only find the Update for the Fire HD 8 12th Gen and Fire HD 8 Plus 10th Gen - but not for the Fire HD 8 Plus 12th Gen I have. Can I just use the one for the non-Plus 12th gen?
EDIT: And does it make any difference as I am not from the US and bought the Fire HD 8 in Germany or can I just use the bin files? -
9Hey, I know I'm a little tardy to the party... but I suppose it's better late than never... right?
I'm happy to announce that today marks the 4TH YEAR ANNIVERSARY of the project!
2019, the year of the Toolbox's release... It seems like such a long time ago, doesn't it? (feels like 4 years to be exact).
Jokes aside, it's really cool to see how something that started out so simple, evolve into something much bigger than you could ever image. I mean, this project started out as a BATCH file for pete's sakes... its sole responsibility to remove lock screen ads!
Release after release, the Toolbox grew, and so did its impact. Today we are on Version 30.3 and so many new features have seen the light of day. it's just so crazy to think that this small project has gotten this big. Sure, we've been through some hard times, with the whole download situation that happened in July, the release of FireOS 7.3.2.2, the play services issue on FireOS 8... just to name a few. But you guys stuck with me through it all, giving your support, and just being awesome people!
Speaking of you guys, I just wanted to take some time to THANK YOU all from the bottom of my heart for being the BEST community on the entire internet. @Jumbo100 and I were discussing this and we both came to the conclusion that this community is one of the few communities where everyone has just been so kind, caring, positive, respectful and helpful towards each other without there being rude and toxic individuals running rampid. Words cannot express how grateful I am to be a part of it. You guys are my world, and seeing everyone come together like this is has just been a blessing. Thank YOU all so much from the bottom of my heart.
I also want to give a huge shoutout to a few close friends on the forums that I couldn't have done all of this without: @blaacksheep, and @Jumbo100. I mean, where do i even start? You guys are really carrying this thread if I'm being honest. No question goes unanswered, and you guys are always on here offering advice, creating magnificent guides (especially your workaround guides @blaacksheep), and just generally being amazing people. We all owe you guys so much! The community growth is largely because of your guys efforts! Words just cannot express how lucky we are to have you two. THANK YOU!
So What's Next for the Project?
The goal for this year is to complete and release the Python Port (more on that in a moment). But, I'd also like to jump into the VB version and fix up some issues that it has. Work needs to be done, and some improvements need to be made.
As far as the port goes, I'm about to let out some information that may cause some anger for some folks. I've thought long and hard about this, and I've decided that the port will be closed-source, much like the Windows version. Yes, I know there are plenty of reason why open-sourcing it would be better than keeping it closed source, but I'm just not ready for that sort of thing yet. I'm not saying it will never happen, just not at the moment. I hope you guys can understand.
Thank you all for taking the time to read this post, I really do appreciate it! Please have a good rest of your night, and I'll see you guys tomorrow!
HERE'S TO A HAPPY 4-YEAR ANNIVERSARY OF THE TOOLBOX!
3@Datastream33
A Happy Fourth Anniversary to the Fire Toolbox Project !
- 30 Version Updates spanning a host of Generations of Fire Tablets on 5 major FireOS platforms
- 2M+ Thread Views, 11K+ Posts, a legion of followers
Thank you for your persistence and dedication to the Project - it’s been a Journey!!
“ Alla salute – Cent’anni ! "3Manual updating is not working for me.
I go from Settings --> Device Options but when I go to System Updates, I get kicked back to Settings
FTB won't re-enable either OTA updates. I'm not sure about automatic updates. It looks like I can make a change on the tablet but FTB won't show any such change.
There doesn't appear to be any method available for pointing the tablet towards the firmware update that's sitting in the internal storage folder.
I've restored all Amazon apps. The only thing I can think to do next is a Reset to Factory Defaults.
The one thing that I don't want to do is to go online to do anything automatically there.3
If you've been away from the FTB community for a while you've missed a lot of excitement/angst/despair.
From the FireOS 7.3.2.2 update (late November/21) there were some significant changes to how Fire tablets could be modded. Quoting from OP #1:
" IMPORTANT INFORMATION REGARDING FIREOS 7.3.2.2+ AND THE TOOLBOX (PLEASE READ)
If your tablet is running FireOS 7.3.2.2 or above please note that some functions of the Toolbox may not work due to new restrictions in the new firmware. The following tools either do not work or have limited functionality:
• OTA Updates - OTAs can no longer be disabled.
• Manage Amazon Apps - Some system apps can no longer be disabled."
This includes not being able to replace Amazon Launcher.
Since then Amazon has added even more restrictions. @Datastream33 worked really hard to code various "workarounds" which are effective but are cumbersome and add to the "overhead" of the already limited system resources.
So definitely DO NOT upgrade FireOS . Most of the FTB updates are related to the workarounds and probably wouldn't add any new functionality to your setup, although some of the FTB processes are improved.
If your tablet is pre-f/w update 7.3.2.2, consider it to be part of the "Golden Age" of FTB mods ... it doesn't get any better!
To improve the performance of your device consider reducing the number of apps installed to free as much memory as possible, especially for streaming media. Also consider cleaning the tablet caches periodically; services like YouTube can occupy as much as 250MB memory per hour.
The newer Gen 12 tablets have moderately improved specs, but have their own problems running the Google Play ecosystem.3
I can see that. Is there no 3rd-party website keeping any of the desired Fire OS versions available? Would Amazon shut that down?
If they frown upon this, I guess you wouldn't be permitted on any host using Amazon Web Services. Terms of Service or some such legalese but this may be something that might fly under their radar. -
348
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.
Toolbox:
Other Downloads:
ResourceResource LinkApplicable ToolsCustom Navigation Bar IconsNavigation Bar ModifierToolbox ChangelogsN/A
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
If you like my work and would like to support me feel free to Donate. Thank you!66
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)
