Yep, I walked him through it.Well, unless you warned him not to turn it on and supply his wifi password, by the time you see it, it'll have 7.3.2.2 on it!![]()
I'm curious to see what OS comes on it.
</crossing my fingers>
Yep, I walked him through it.Well, unless you warned him not to turn it on and supply his wifi password, by the time you see it, it'll have 7.3.2.2 on it!![]()
Version 26.0 - Changelog
[Welcome Screen]
[Device Information]
- 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.
[Theme Selector]
- Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
[Custom Launcher]
- Moved the Theme Selector to the Welcome Screen.
[Modify System Settings]
- 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+.
[Lockscreen Management]
- 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.
[Hybrid Apps]
- Improved the warning regarding the Pattern security type.
[Manage Amazon Apps]
- Updated Disney+, and Netflix to the latest versions.
- When restoring from a debloat list, it now displays the proper header and message.
Greetings friend!Hey Datastream and thanks for your hard work
I just downloaded the v26 portable, extracted it and on doubleclick it starts the adb, shows shortly no updates and then closes itself again (v25.2 portable still working normal).
This is what I can see, before it's closing again:
View attachment 5489257
/edit
v25.2 is finding 2 Amazon Apps on my Fire HD 10 (2021) with OS 7.3.1.9 wich I can't disable:
App: Washington Post
Result: [FAILURE] Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown package: com.washingtonpost.rainbow
App: Mopria Print Service
Result: [FAILURE] Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown package: org.mopria.printplugin
I don't see any Washington Post Application on the Tablet, not sure about the Mopria Print Plugin though
I re-downloaded it and tried it again - same result.Greetings friend!
Can I have you re-download the portable build and try extracting again? Does it produce the same results?
Hmm, from the output it looks like Washington Post and the Print Plugin aren't installed.![]()
Thanks! I should have read the update-post more carefully - so much excitement...@cogno There will be no auto-update (it also say this in the update-post), because of changed folders.
Thanks a ton my friend! Looks like the crash is due to the Installation Management attempting to read the Datastream directory, but it doesn't exist so the Toolbox crashes. Working on a micropatch, and will release it ASAP! Thanks!I've got the same problem. Toolbox is closing immediately.
In the eventlog of my Windows PC (German language) I got the following error:
Anwendung: Fire Toolbox.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.IO.DirectoryNotFoundException
bei System.IO.__Error.WinIOError(Int32, System.String)
bei System.IO.FileSystemEnumerableIterator`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].CommonInit()
bei System.IO.FileSystemEnumerableIterator`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(System.String, System.String, System.String, System.IO.SearchOption, System.IO.SearchResultHandler`1<System.__Canon>, Boolean)
bei System.IO.Directory.GetDirectories(System.String)
bei AmazonFireToolbox.FirstStart.ToolboxInstallations(System.String)
bei AmazonFireToolbox.FirstStart._Lambda$__R124-1(System.Object)
bei System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
bei System.Threading.ThreadHelper.ThreadStart(System.Object)
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:Thanks for your detailed reply, I wiped the cache (twice), unfortunately the update is still showing as ready to install. I've restarted the tablet, through the Recovery menu, and it hasn't installed (yet), so there's hope at least...
ls -a
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.
Yeah, if it's not too late and it hasn't rebooted already. Reconnect it to Toolbox. On page 2, use Power Options. Choose Recovery mode. It will reboot your tablet into recovery mode. Use the Volume Up/Down buttons to select "wipe cache partition". press power briefly to confirm. Again, use the Up/Down buttons to select "yes". Again, press power to confirm. Your tablet will reboot and take a little longer than usual. It will rebuild the cache partition (which used to contain the downloaded update file). As long as you've disabled OTA Updates, you should be fine.Hi all, got a Fire HD 8 for the kids. It came with 7.3.2.1 but has already downloaded 7.3.2.2 which will be updated when there is low activity or the tablet is restarted, according to the message on screen.
I've disabled updates using Toobox now, but given the update was already downloaded, will this stop the update at this stage? or is there anything I can do to delete it before it installs?
Ask @Datastream33 where the update is hidden. He might still be around. He might know.Thanks for your detailed reply, I wiped the cache (twice), unfortunately the update is still showing as ready to install. I've restarted the tablet, through the Recovery menu, and it hasn't installed (yet), so there's hope at least...
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.I don't think a factory reset does an update first, but he could do it from recovery to be sure. ??
I like this navbar, it can hide itself or stay on and the buttons can be customised however you want, including the launching of an app like a custom launcher, works well for me with the default navbar hidden by the toolbox on my son's Kindle Fire HD 7. There's lots of other customisation options too and it's a free app: https://play.google.com/store/apps/details?id=ace.jun.simplecontrolYeah, the tablet arrived on schedule, and I allowed it to update to the latest firmware, although it was already on 7.3.2.2. I wanted to start with the worst case scenario that a new person would encounter. Boy, they put a lot more restrictions on it. I've got the update problem solved, and I've got the lockscreen ads solved - both with the same method. I've got 5 URL's blocked that solve both problems. You can do it with an open source VPN type ad blocker that lets you add your own lists to it's hosts file. It's now time to move on to the launcher problem and how to make a free replacement navbar behave like the original navbar and assign the home button to a new launcher. So far I've downloaded and run quite a few free ones, but they all want money to remap the home button. I'm still fooling around with several more before I give up and just use a gesture navbar replacement. I'm also starting to write up my experience to post for anyone that wants to explore this further.
It's taking longer than expected because I can only work on it for an hour or two a day before my head feels like it's going to explode!Give me a little more time. When I'm done, I think it will be worth the wait. Thanks for being patient.
![]()
Is there any toolbox update in the near future for the latest Amazon update?
And do I have a chance if I updated m fire hd 8 on the latest version to reset to an older? Like a old windows installation, or am I fu**ed?![]()
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.
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:
• Custom Launcher - Launchers can no longer be set as default, and the homekey re-route method must be reapplied after rebooting or shutting down the device.
• OTA Updates - OTAs can no longer be disabled.
• Lockscreen Ads Remover - Ads can no longer be removed from the lockscreen.
• 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.
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 |
Resource | Resource Link | Applicable Tools |
Custom Navigation Bar Icons | Navigation Bar Modifier | |
Toolbox Changelogs | N/A |
Version | Installer (.exe) | Portable (.zip) | Update Post | VirusTotal |
V26.1 | Post | Link | ||
V25.2 | Post | Link | ||
V24.0 | Download | Post | Link | |
*Halloween Edition | Download | *Bug Fix | Link | |
V23.0 | Download | Post | Link | |
V22.0 | Download | Post | Link | |
V21.0 | Download | Post | Link | |
V20.0 | Download | Post | Link | |
V19.0 | Download | Post | Link | |
V18.0 | Download | Post | Link | |
V17.0 | Download | Post | Link | |
V16.0 | Post | Link | ||
v15.0 | Post | Link | ||
V13.0 | Post | Link | ||
V12.0 | Post | Link | ||
V11.1 | Post | Link | ||
V11.0 | Post | Link | ||
V10.2 | Post | Link | ||
V10.1 | Post | Link | ||
V10.0 | Post | Link | ||
V9.2 | Post | Link | ||
V9.1 | Post | Link | ||
V9.0 | Post | Link | ||
V8.2 | Post | Link | ||
V8.1 | Post | Link | ||
V7.2.1 | Download | Post | Link | |
V7.1 | Post | Link | ||
V7.0 | Post | Link | ||
V6.56 | Post | Link | ||
V6.55 | Post | Link | ||
V6.54 | Download | Post | Link |
How can I run the Toolbox on Linux?The Toolbox is currently being developed for Linux systems in the Python programming language. If you'd like to see the progress of the port, you can do so at this link.Please be patient with me as the Linux port is being developed in my spare time and may take some time to complete. However, as the port progresses some builds will be released to those who'd like to help test alpha builds. More information on this later down the line. However, at the moment, the best way to run the Toolbox on Linux is to use VMWare and emulate Windows.
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".
Can the Toolbox be used to root my tablet?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.
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!
Google Family Link won't work on my tablet?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.
Version 26.0 - Changelog
[Welcome Screen]
[Device Information]
- 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.
[Theme Selector]
- Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
[Custom Launcher]
- Moved the Theme Selector to the Welcome Screen.
[Modify System Settings]
- 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+.
[Lockscreen Management]
- 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.
[Hybrid Apps]
- Improved the warning regarding the Pattern security type.
[Manage Amazon Apps]
- Updated Disney+, and Netflix to the latest versions.
- When restoring from a debloat list, it now displays the proper header and message.