Ask @Datastream33 where the update is hidden. He might still be around. He might know.
[WINDOWS][TOOL]Fire Toolbox V28.1
- Thread starter Datastream33
- Start date
Hmm, the ota file could be in numerous places. However, they usually put the update on the root of the internal storage, but hide it from view. Try executing an ADB Shell from the Toolbox's main menu and let us know the output of the following command:
Code:
ls -aSo, I did some research, and it looks like the updates are stored in: /data/ota-package/. Might not be able to delete the update due to not having the proper permissions. Perhaps, a factory reset is the best way to go in this situation...
EDIT: Hmm, maybe we don't want to factory reset either... if the update hasn't installed already, it's waiting for the user to manually start the update due to automatic updates being disabled. A factory reset may enable automatic updates and starting installing the update... hmmm...
Maybe try clearing the Storage for System Updates (both entries in Settings), DeviceSoftwareOTA, and also for Download Manager.
Last edited:
So, I did some research, and it looks like the updates are stored in: /data/ota-package/. Might not be able to delete the update due to not having the proper permissions. Perhaps, a factory reset is the best way to go in this situation...
EDIT: Hmm, maybe we don't want to factory reset either... if the update hasn't installed already, it's waiting for the user to manually start the update due to automatic updates being disabled. A factory reset may enable automatic updates and starting installing the update... hmmm...
I don't think a factory reset does an update first, but he could do it from recovery to be sure. ??
My bad, what I'm saying is... if the device is factory resetted, but the update file isn't removed in the reset process it could start auto installing the OTA. I believe the update isn't auto installing right now is because Automatic Updates has been disabled. So by resetting it, it would return that flag to default and could auto-install the OTA before Automatic Updates can be toggled off again.
Just a thought. I hadn't considered the mechanism of the update process. You're probably right.
I am sorry to be quoting my own earlier comment, but I am supplementing it with a picture. In it you will see that my new HD 8's screen is positively gray next to the blackness of my HD 10. The eBay vendor claims that this grayness is normal to HD 8. What is the truth? If anybody has both HD 8 and HD 10, please tell me whether they show the kind of difference as shown in the picture. If you have an HD 8, does it show such a strong contrast between (gray) actual display vs. (black) border?
ADDED LATER:
I did some looking and was able to confirm that the grayness is normal to (or at least prevalent in) HD 8. See the video clips below. My HD 8 behaves much as do those in the clips.
Note: when the screen is gray it will give to all colors a faded look unless you are using the device in darkness.
Therefore if you care about accuracy of color reproduction in all lighting conditions, here seems to be a reason you should choose an HD 10 over HD 8.
I am sorry the links blew up into what you see and take up much room.
The link below is of HD 8 9th gen (2019) or earlier and so is not directly on point, but shows the grayness best.
Last edited:
I've cleared the storage as instructed, and can happily report the update is goneSo, I did some research, and it looks like the updates are stored in: /data/ota-package/. Might not be able to delete the update due to not having the proper permissions. Perhaps, a factory reset is the best way to go in this situation...
EDIT: Hmm, maybe we don't want to factory reset either... if the update hasn't installed already, it's waiting for the user to manually start the update due to automatic updates being disabled. A factory reset may enable automatic updates and starting installing the update... hmmm...
Maybe try clearing the Storage for System Updates (both entries in Settings), DeviceSoftwareOTA, and also for Download Manager.
Thanks again for your help!
I f*cked up my old fire 8 so had to buy a new one. Was busy doing it all by hand.
I must say: who...you are a hero. Man, if I wasnt already married, i would ask you...
I must say: who...you are a hero. Man, if I wasnt already married, i would ask you...
That's awesome! So glad to hear!I've cleared the storage as instructed, and can happily report the update is gone
Thanks again for your help!
Nicely done!
Not sure if you're talking to me or not but if so glad to see the Toolbox has helped you my friend!I f*cked up my old fire 8 so had to buy a new one. Was busy doing it all by hand.
I must say: who...you are a hero. Man, if I wasnt already married, i would ask you...
Have a good one my friend!
Last edited:
I'm getting an error message when I try to download the Google Services saying the APK is corrupted and failed to download properly.
Help.
Help.
Hi. and welcome to XDA!
That could happen if the Toolbox downloaded a corrupted file. (Go figure!) The easiest way to fix it is to right-click on your Toolbox desktop icon and select Open File Location. (The wording might be slightly different in Windows 10/11.) In that folder, double-click the "bin" folder. Now double-click the "Google Services" folder. Delete everything in there. Toolbox will download it again on the next try. Close your file browser and try installing Google Services again. Hopefully it will work this time.
That could happen if the Toolbox downloaded a corrupted file. (Go figure!) The easiest way to fix it is to right-click on your Toolbox desktop icon and select Open File Location. (The wording might be slightly different in Windows 10/11.) In that folder, double-click the "bin" folder. Now double-click the "Google Services" folder. Delete everything in there. Toolbox will download it again on the next try. Close your file browser and try installing Google Services again. Hopefully it will work this time.
What is the effect of manually turning off DNS66 if it is set to "Always on VPN" in Activity Launcher?
Will Activity Laucher go, "Some fool turned that off. I'll turn it back on," do it?
I ask the question because I have the same Amazon servers blacklisted in my router. While at home, therefore, I may not want a double blocking by DNS66, which may be a hit on battery or speed.
If Activity Launcher will countermand a manual action (as above), then on coming home I am looking at two things to turn off: DNS66 and Activity Launcher. Of course this would mean turning two things on when going out.
In the unlikely event that Activity Launcher can distinguish DNS66 (somehow) quitting on its own vs. a person turning it off, then Activity Launcher can stay on all the time and I get to turn only one thing on and off (DNS66).
Or maybe the hit on battery and speed is negligible in your experience? In this case, I may just keep DNS66 all the time. (This "on and off" thing may just be the way to get my tablet to update again because one day I may forget.)
Activity Launcher is just a means of calling already installed activities or apps. It's used because there is no provided means of accessing those activities without ADB or another program.
I hadn't actually checked what would happen if you turn off DNS66 when it was set as Always On VPN until I read your post.
It turns out that if you do turn off DNS66 with that setting on, it just gives you a notification on the Notification Bar. 
It doesn't actually stop any traffic from going through. Only the other switch below Always On VPN does that, but that doesn't play well with Amazon or DNS66 and stops all traffic. 
I guess you can leave Always On VPN turned off.DNS66 is a low resource program and probably saves more battery than it uses by blocking extra traffic and stopping the rendering of ads. All it does is intercepts any DNS lookups and if they are on it's lists it returns 127.0.0.1 (localhost) as the numeric address for the DNS lookup where they go unanswered. The app or browser gets no response from that address so it cant connect with the intended ad server or update server. The process fails. Having an extra block on your router or a PiHole won't matter because they'll never get the request as it's been locally redirected to a dead end.
I don't recommend turning off DNS66. It might be your only defense against further updates if you are on someone else's WiFi. It most certainly isn't a bottleneck as far as speed goes. It runs on all my android devices except my phone while I'm using a real VPN. As a matter of fact, it's one of the first apps I install on any device I use just for the ad blocking.
Edit: Thanks, @manyxda for bringing this up and making me revisit the usefulness of Activity Launcher in this case. It turns out not to be needed and I've edited my tutorial post to reflect that.
Last edited:
Looks like it's available for purchase on June 29. The best thing about the new tablet in my opinion is it's the first Amazon tablet with Android 11 (we'll have to see how locked down they are on release). So, that's pretty cool. Although, comparing it the Fire HD 8 (2020) I believe the new tablet is weaker.
I’m sorry my autocorrect made it say “is” instead of os. I meant the operating system update.
Sorry, I read your post wrong I thought you meant the tablets like the fire hd 8.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
12What's going on, guys?
I hope everyone is having a fantastic weekend so far!
I'm so excited to announce that Toolbox V28.0 has just been released!
In today's update, we have so many exciting things to go over, including a new method to bring back custom launchers on tablets running FireOS 7.3.2.2 and above!!!
So without further ado, let's jump into the meat and potatoes of the new update!
The Return of Custom Launchers and Other Improvements!
So, as you guys may know, it's been pretty difficult to use third party launchers ever since FireOS 7.3.2.2 dropped. We had a workaround, but it was ideal and wouldn't survive a reboot. Fortunately, with the help of my favorite app ever... Automate, we now have a pretty decent method that even survives a reboot! Using Automate, we can await a keypress from the navigation bar and then launch any custom launcher of our choice!
There are, however, a few downsides, of course. For example, when opening an app that has a white background... it will appear as if the home button has vanished. This is a limitation of the method used, and we're looking into a workaround, but I'm afraid one might not be found... but we will see.
Anyway, along with the new activation method, there have also been some improvements to the tool itself. Firstly, as recommended by our good friend @blaacksheep, the "Enable widget Support" checkbox is now checked by default - because who doesn't widgets? Next, the decision to use the shell to re-route the home button for both Re-route and Downgrade methods has been reversed (it will now use cmd again). The reason for this is that it didn't really seem to be as effective as the cmd method. Finally, the method for reading FireOS version has been improved, and as a result the Toolbox is now capable of detecting what Launcher Activation Method is the best for your tablet and will select that method automatically.
Modify System Settings Has Been Modified!
So, I promised a few folks I would add a subtool, that would make it easier to modify the tablet's overscan values. Well, in this update, I've decided to act on that promise! Firstly, I needed to figure out where this subtool would exist. I decided to create a new tab in the Modify System Settings tool just for the overscan... but then it occurred to me, that I could use this opportunity to create a display options tab and move a few of the existing "display" options to it. So, the tab was created, and the Display Timeout was moved to it firstly.
Now with this new tab, it was also decided that the Device Density tool would be also moved here instead of being its own tool. As a result, it's been removed from the Main Menu. Lastly, you'll find the Overscan option. From here, you can change both the portrait and landscape overscan values. Unfortunately, there isn't a way to retrieve the current overscan values by default. However, we can store a key in the settings database that will keep track of the overscan values changed by the Toolbox (it will not keep track of changed overscan values from outside the Toolbox) so that's good!
The last change in this tool is to the Device Dashboard Icon setting. Now, when you toggle it off, you'll be given the option to change the navigation bar's layout from 3 options: Default, Compact, and Android. This gives you greater control over how your navbar should look after the device dashboard icon is removed!
Device Detection is Now Dynamic!
I've been noticing a few issues with Device Detection in the previous update. For whatever reason, it was detecting the device states wrong and was seeing a device when there really wasn't one. This has been addressed and should no longer occur. However, along with this change, the Toolbox's device detection has been improved in a certain manner that now allows it to detect device states dynamically. What I mean by this is, say you have a tablet plugged in, but the Toolbox is awaiting authorization... but then you unplug the device. In the past, the toolbox would still be awaiting authorization even though the tablet has been unplugged. Well, now when this occurs, the Toolbox is capable of seeing the device disconnect and will go back to the "no device" detected state. Pretty cool right? This works for authorization, no device, and too many devices detected.
Well, that's all the big highlights! But, that's not everything today's update has to offer! Feel free to check out the changelog below for more awesome changes!
Ready to download V28.0? Well, be sure to drop by the Downloads' section of the OP and get you either the installer or the archived version! However, if you have a previous version of the toolbox installed, you could also update using the Toolbox's built-in updater!
As always guys, I want to thank you all from the bottom of my heart for being such amazing people! I feel blessed to be a part of a community as great as this one! Thank YOU all for the support, donations, and kindness you guys continue to show! The respectful nature, and the helpfulness of everyone is just so overwhelming! THANK YOU guys!
I'd also like to THANK our good friend @blaacksheep for being such a great friend and helping out the community as much as he does! I mean, the post where he shared his workarounds for the FireOS 7.3.2.2 issues is really amazing, and I can't thank him enough for it! You rock, my friend!
Before this post ends (I know it's a little long as is, but please bear with me) I'd like to give an update on the Python port. Been working on it a lot as of late and have made some pretty decent progress. I would like to state now that this will be the last update to the VB version of the Toolbox for a while, so I can focus all my attention on the port. Remember, I'm updating the port progress page as I go, so keep an eye on it if you'd like to keep updated with the progress. I may have a public test build coming up soon.. well have to see. But just thought I should let you guys know what's going on.
Well, that's all I've got for now! I sincerely hope you guys enjoy the update, and until next time guys... Peace!
3I'd like to sincerely apologize to everyone. I know i said i'd release a micropatch later that day. However, when i posted that i didn't know i'd lose power due to the winds all day yesterday. Apparently a tree branch hit the line and knocked it out.
Staying with my patents until its fixed. Again, i'd like to apologize for not keeping my word.
On a lighter note, hope everyone has a GREAT father's day!2I am confused. I am new to the Fire 10 2021 model and new to this forum. I do not understand the problem some people are having with Amazon apps being reinstalled after removal using the Toolbox. After doing a complete debloat I went into settings and selected apps. Then clicked on system to get to the ones I want. First one to select is DeviceSoftwareOTA. You can't disable it but you can select Data Usage and disable background data. Also unselect Notifications and Modify System Settings. Do the same for ForcedOTA and both System Update apps. You can't disable them but you can stop them talking to the internet. Using this method none of the Amazon apps have reappeared on my Fire10. Am I missing something? This works for me. Regards. John Smith
PS. My Fire 10 is not registered. Does this make a difference?2Hello! I have been using this tool for a couple years, amazing work. On V 28.0 when I use the Custom Launcher option and try to install Nova, I get an error that says, "Hmm, it seems Automate failed to install! The reason for failure is: Performing Streamed Install." Now it looks like my home button does not work and the program won't let me use the "Restore Fire Launcher" option. Any help would be appreciated.
Thanks!
Edit: Installed automate manually. It works now. Thanks!2
Don't have HD 10 from 2019, but have HD 8 from 2020 and HD 10 from 2021. Every app I ever installed on these two from Google Play or F-Droid worked just fine. For PDF, ReadEra and Xodo worked fine. Haven't tried Office. -
306
═══════════════════════════════════
Fire Toolbox V28.1
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 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 - 2021) 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 PostVirusTotalV27.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!61
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!
31I'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!!
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!20Well, I guess it's finally time to explain myself. You see, ever since Christmas I've been mostly radio silent. Well, this is attributed to Covid running rampant in my parent's household after Christmas. My whole family besides a few were infected (myself included) with the Omicron variant. We are just barely coming out of it, and life is slowly going back to normal. Just wanted to let you guys know where I've been, as I've seen comments (not on this forum) stating that the project is dead, and I've given up on it... that is simply not true. We will press on, and development should start moving forward once more! Again, thank you to @Falcon342, and @blaacksheep for carrying the torch as always! I do appreciate it! - 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)
