Does blocking the OTA with rethink and activity launched block Alexa ? Seems Alexa not working for me.
Sweet, so it has a dedicated home button!Thank you soo much for your quick reply!
I'll attach the pic of the keyboard (it's the official Amazon bluetooth keyboard for the Fire HD 10+)
If Automate could use those buttons as it is, it'll be just super.
If not, then might I request you to configure Shift + those dedicated buttons?
View attachment 5779193
Hi, and welcome to XDA!Hi and thanks for the great work on the toolbox!
I just used the toolbox on my new Fire HD10 Plus, firmware 7.3.2.4. The toolbox version 30.1 effectively blocks the firmware upgrade to 7.3.2.6. However, the same toolbox blocks the language download to the Librera app, which I use to read pdf files on my tablet. BTW, great app!
I'm concerned that disabling the OTA blocker in the toolbox will result in a firmware upgrade to version 7.3.2.6. Is there a safe way to download the language to the Librera app?
I would appreciate your support.
Thank you for your quick response.Hi, and welcome to XDA!
You can use the RethinkDNS method of blocking the updates. A link to that method is located in my signature. It just blocks the apps responsible for updates from internet access so they can't update. In order to undo the method in Toolbox, I'm not certain if there's an option in Toolbox to undo it. If it works the way I think it does, you can go into WiFi settings and tap on the gear to the right of your network name, and look down a few lines until you see "Metered". Tap that and change it to either of the other options. Let me know how you do.
Just make sure you check the System Updates section of your Settings to see if there's an update waiting to install before you shut down/reboot. (Don't click "Check for updates", just look at the bottom where it says the current status.) If there is one waiting to be installed, report back here and we'll tell you how to get rid of it. Oh, and make sure you put it back to metered so an update doesn't slip through.Thank you for your quick response.
Temporarily disabling the "Metered" option for my wifi network took care of the issue and the language file downloaded correctly.
I have a Amazon Fire HD 8 12th gen (2022) running 8.3.1.3 and running into this exact issue. I get the "failed to read flow" error on the tablet when settings up the custom launcher from the toolbox. I imported the flow directly from the toolbox manually. However, the launcher only opens once and then defaults back to the Fire launcher.I have ben able to use this awesome tool to add in google services and strip out the amazon bloaware but unfortunately the custom launcher is not working for me. The device (fire 8 plus) is already on 8.3.1.3
When I install the nova launcher both Nova launcher and automate install and permissions are granted.
Then I see a message saying "the launcher invoker flow will now be imported into automate, please unlock your device (please do not interact with the touch screen during this process) and click OK to continue.
I click ok only to be greeted with an error about "Failed to read flow" on the tablet with the only option being cancel (import is greyed out). I have tried importing an older version of the launcher from this forum but that also did not work (the nova launcher opened once and then defaulted back to the fire home pages screen)
Could anyone who has seen this beofre please point me in the right direction as I think I am having a bit of a PEBKAC moment here.
12-07 22:05:45.400 I 34@1: Flow beginning
12-07 22:05:45.412 I 34@34: System setting get
12-07 22:05:45.424 I 34@29: Fork
12-07 22:05:45.455 I 34@31: Broadcast receive
12-07 22:05:45.461 I 35@24: Fork
12-07 22:05:45.486 I 35@4: Media button
12-07 22:05:45.517 I 36@25: App in foreground?
12-07 22:05:56.913 I 36@5: App start
12-07 22:05:57.012 I 36@28: Fiber stop
12-07 22:05:57.046 I 36@24: Fork
12-07 22:05:57.154 I 36@4: Media button
12-07 22:05:57.202 I 37@25: App in foreground?
12-07 22:05:57.249 I 37@0: Stopped at end
Make sure that Automate is set to start on system startup, and that the flow "Launcher Invoker" is started. You said that all permissions were granted, so that should be enough.I have a Amazon Fire HD 8 12th gen (2022) running 8.3.1.3 and running into this exact issue. I get the "failed to read flow" error on the tablet when settings up the custom launcher from the toolbox. I imported the flow directly from the toolbox manually. However, the launcher only opens once and then defaults back to the Fire launcher.
Home button press starts at 12-07 22:05:56.913. There are no other log entries on subsequent home button presses that open the Fire launcher.
It is set to start on system startup and the flow is started. That is how I got my flow logsMake sure that Automate is set to start on system startup, and that the flow "Launcher Invoker" is started. You said that all permissions were granted, so that should be enough.
Okay, just checking. I'm not sure about FireOS 8. A couple of users with 2022 tablets seem to have that problem. You can also let Google Play update Automate. Maybe it's a version thing. I'm just guessing here.It is set to start on system startup and the flow is started. That is how I got my flow logs
Thank you for your reply!Sweet, so it has a dedicated home button!
This could work with Automate. OK, I've modified the Launcher Invoker flo and attached it to this post (you'll need to extract it from the .zip file) and import it into Automate. (If you need help importing let us know)
Really hope this works! Please let us know how it goes and best of luck!
Screenshot your current navbar, this method required customized navbar with a custom layout, if you stll see original navbar layout with 3 button placed nearly each other, then it doesn't work.Thank you for your reply!
I extracted the zip, placed it in my downloads folder, and then imported to Automate.
Then, I Stopped the original "Launcher Invoker" Flow and Started the "Launcher Invoker [1]" Flow.
However, pressing the Home button on the keyboard still lands me to the Fire Launcher homescreen
Please let me know if I have to send any screenshot etc of the Automate page, or any log file to help with this process?
(I really appreciate your willingness to share such customization!)
The touch screen home button works fine, and it lands me to the Nova launcher home screen.Screenshot your current navbar, this method required customized navbar with a custom layout, if you stll see original navbar layout with 3 button placed nearly each other, then it doesn't work.
Okay, just checking. I'm not sure about FireOS 8. A couple of users with 2022 tablets seem to have that problem. You can also let Google Play update Automate. Maybe it's a version thing. I'm just guessing here.
I have just found a plugin in the automate community called "Amazon Fire Tablet - Easy Home Launcher Changer". It seems to work but every now and again you see a flash of the old home pages when you click the home button (not every time and it disappears in half a second). Will try to go through and map it out later and see if I can work out why this works and the launcher is not.It is set to start on system startup and the flow is started. That is how I got my flow logs
You're without a doubt correct. Start with a clean slate.I have a Fire HD 10 from 2019. I want to use Toolbox on it for the first time. I wanted to ask if I'm right in thinking it would be best to reset the tablet beforehand.
It looks like its using an atomic variable to hold the custom launcher variable. This means that once its set, it will remember the value even if the flow is stopped (e.g: set it and forget it). The flow however, is using the old method of waiting for the fire launcher to be in the foreground before launching the custom launcher.I have just found a plugin in the automate community called "Amazon Fire Tablet - Easy Home Launcher Changer". It seems to work but every now and again you see a flash of the old home pages when you click the home button (not every time and it disappears in half a second). Will try to go through and map it out later and see if I can work out why this works and the launcher is not.
Only other issue with the plugin is it asking you which launcher you want to use on load (but sure that could easily be hard coded).
Thanks for all the help and good advice.
Do what you gotta do my friend.I undone rethinkdns method of blocking OTA and Alexa is working again. I know I'm vulnerable to updates now but I find Alexa very useful.
Dang, ok...The touch screen home button works fine, and it lands me to the Nova launcher home screen.
I'm facing an issue on the Fire HD Bluetooth Keyboard -- home screen physical button.
That lands me to the fire launcher home screen even with the modified invoker flow posted by datastream33 above.
First two posts have everything you need.Hello all, there are so many pages in this thread, that it is difficult to find the latest toolkit to change Fire HD 10 (11th Gen) to Android. please help to find the toolkit for windows 11. Thanks
Version 34.0 - Changelog
[Google Services (Manual)]
• Calendar and Contact android providers are now enabled during install.
• Fixed crash occurring when closing the window.
[Google Services]
• Calendar and Contact android providers are now enabled during install.
[Custom Launcher]
• Launcher Activation Methods that aren't compatible with the tablet's firmware are now hidden.
[Networking]
• Added warning message when Rentry.co can't be reached.
[ADB Input]
• Fixed crash occuring on window close.
[Google Assistant]
• The Google app is now downloaded from a separate source instead of installing via the Play Store.
• Instructions on how to properly setup Google Assistant has been added.
• Restored the missing GAssist APk.
[Lockscreen Management]
• Fixed crash occuring on window close.
[Manage Amazon Apps (Automatic)]
• Removed "Device Setup" from Standard Debloat/Restore presets.
[Manage Amazon Apps (Manual - Simple)]
• Updated the description, and changed app color to red for the "Device Setup" app.
[Manage Amazon Apps (Manual - Advanced)]
• Fixed crash occurring when clicking the App Info button for User Apps.
• Fixed crash occurring when an app's icon is in .xml format (the tool will not read/display icons in .xml).
[Modify System Settings]
• Added the option to block OTAs using RethinkDNS on restricted firmwares.
• Settings not supported by the tablet's firmware are now hidden.
• Added the option to change the language locale to the SystemUI tab.
• Added the option to toggle on/off Gesture Navigation for tablets running FireOS 8+.
[Device Information]
• Added a search function for the buildprop.
[Hybrid Apps]
• If a hybrid app fails to download, the install process is skipped and the corrupted file is deleted.
• Fixed the update function not working as expected.
[Settings Database Modifier]
• Fixed an issue preventing keys from being deleted.
[System Backup]
• When restoring a backup, you can now select which elements you'd like to restore.
• Backups are now displayed from top to bottom, instead of left to right.
[SystemUI Modifier]
• Added "Alexa Hands-Free", "Smart Home", "Work", and "Data Saver" toggle options to the Quick Settings Modifier.
• The Navigation Bar Modifier is now hiden for devices running FireOS 8+ as a result of the ability to modify the navigation bar being removed from Android.
Filename | SHA256 Hash |
FTB_V34.0_Installer.exe | df19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc |
FTB_V34.0_Portable.zip | f47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f |
I used the Toolbox for the first time yesterday and installed the Aurora Store and remove screenlock. IIRC, I had to choose between signing in with my Google account or as Anonymous. I chose Anonymous. Now I find that my File Manager app (which I use to send books to the Fire using FTP) will only start FTP File Sharing if 'Anonymous' is ticked. If I untick it then there is no option to 'Start' the FTP.
As far as I can tell the Fire does not have a User called Anonymous. What do I need to do to keep the Aurora Store and get my FTP sharing back to being password-free? Thanks.
Greetings
Hello I have used V33.1 and I have a few problems, I have a fire kindle 8 2020 and I can’t disable fire launcher, (I am using Microsoft launcher BTW) also I am trying to restore a backup (made on fire toolbox) to my kindle 7 2019 but I can’t seem to find the backup I made on my kindle 8 to restore it on my kindle 7 plz can you help me.
(If my problems are fixed in the latest version,I can use it as I’m on holiday and I don’t have any Wi-Fi)
FTB is not designed as a full system backup utility; it basically just backs up the device "configuration state" . A full system backup requires system root access , which isn't available on newer Fire tablets.
I don't necessarily see a problem with restoring the 2020 backup onto a 2019 model (they both run Android 9). However, I would HIGHLY advise against restoring the 2020's settings database onto the 2019 as there are some keys in some of the tables that could result in a soft brick if changed. But, if you're just trying to copy the apps from the 2020 to the 2019 then I say go for it. Just make sure to create a backup on your 2020 with ONLY the user apps option selected (make sure to name it something simple like "UserApps_Backup" for easy identification later), then restore that newly created backup onto the 2019 tablet. Here's how:Backups can be restored to a different device IF it's the same model and firmware version. (I.E. you have 2 Fire HD 8's that are both the same.) If you try to restore to a different model or year, you'll have to keep your fingers crossed. It might work, but don't rely on it.
IMPORTANT INFORMATION REGARDING FIREOS 7.3.2.2+ AND THE TOOLBOX (PLEASE READ)
If your tablet is running FireOS 7.3.2.2 or above please note that some functions of the Toolbox may not work due to new restrictions in the new firmware. The following tools either do not work or have limited functionality:
• OTA Updates - OTAs can no longer be disabled, but can be restricted.
• Manage Amazon Apps - Some system apps can no longer be disabled.
We're looking into workarounds to the issues detailed above. Please keep an eye on the forum for further development.
Device Name: | *Generation: | FireOS Version | Base Android Version | **Restricted |
Amazon Fire HD 10 (2023) | 13 | 8 | 11 | Yes (8.3.1.9+) |
Amazon Fire Max 11 (2023) | 13 | 8 | 11 | Yes (8.3.1.9+) |
Amazon Fire 8 (2022) | 12 | 8 | 11 | Yes (8.3.1.9+) |
Amazon Fire 7 (2022) | 12 | 8 | 11 | Yes (8.3.1.9+) |
Amazon Fire 10/10+ (2021) | 11 | 7 | 9 | Yes (7.3.2.2+) |
Amazon Fire 8/8+ (2020) | 10 | 7 | 9 | Yes (7.3.2.2+) |
Amazon Fire 10 (2019) | 9 | 7 | 9 | Yes (7.3.2.2+) |
Amazon Fire 7 (2019) | 9 | 7 | 9 | Yes (7.3.2.2+) |
Amazon Fire 8 (2018) | 8 | 7 | 9 | Yes (7.3.2.2+) |
Amazon Fire 10 (2017) | 7 | 5 | 5.1 | No |
Amazon Fire 8 (2017) | 7 | 5 | 5.1 | No |
Amazon Fire 7 (2017) | 7 | 5 | 5.1 | No |
Amazon Fire HD8 (2016) | 6 | 5 | 5.1 | No |
Amazon Fire HD10 (2015) | 5 | 5 | 5.1 | No |
Amazon Fire HD8 (2015) | 5 | 5 | 5.1 | No |
Amazon Fire HD7 (2015) | 5 | 5 | 5.1 | No |
Amazon Fire HD7 (2014) | 4 | 5 | 5.1 | No |
Amazon Fire HD6 (2014) | 4 | 5 | 5.1 | No |
Filename | SHA256 Hash |
FTB_V34.0_Installer.exe | df19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc |
FTB_V34.0_Portable.zip | f47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f |
Version | Installer (.exe) | Portable (.zip) | Update Post | VirusTotal | Checksums |
V33.1 | Post | Link | |||
V33.0 | Download | Post | Link | ||
V32.4 | Post | Link | |||
V32.3 | Download | Post | Link | ||
V32.2 | Post | Link | |||
V32.0 | Download | Post | Link | ||
V31.0 | Download | Post | Link | ||
V30.2 | Download | Post | Link | ||
V30.1 | Download | Post | Link | ||
V30.0 | Download | Post | Link | ||
V29.0 | Download | Post | Link | ||
V28.9 | Download | Download | Post | Link | |
V27.0 | Download | Post | Link | ||
V26.1 | Download | 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 |
Filename | SHA256 Hash |
FTB_V5.0_Installer_Python3.10.7z | 985f1fc24d21c7506b9245f8ba37194380535fb5a8ef9af762d7d6d3853498ec |
FTB_V5.0_Installer_Python3.11.7z | 110bebfe5e28c75bd6235434f3b0ea640d6f24f77ef859a704db2a673972e01b |
Resource | Resource Link | Applicable Tools |
Custom Navigation Bar Icons | Navigation Bar Modifier | |
Toolbox Changelogs | N/A |
The Toolbox won't display correctly. The window is pure white and the text is faded. How can I fix this?
This can happen if window style and effects are turned off.
Windows 7
Control Panel > Performance Information and Tools > Adjust Visual Effects > Use Visual Styles on Windows and Buttons.
Image credit: @gsm2001
My Home Button isn't working after using the Custom Launcher Tool?Due to the way the process works, it alters your navigation bar's home key to send a key event that can be picked up by Automate. Once Automate reads this event, it launches your custom launcher automatically. However, if the flow in Automate isn't running, the navbar key will not work, and nothing will happen when it's tapped. To fix this, either open Automate and start the "Launcher Invoker" flow again, or execute the Custom Launcher tool in the Toolbox, click the ":" icon (upper-right) to show the Tool Options panel, and click the "Restore Navigation Bar" button to restore the stock layout. You can execute the "reset_navbar" (without quotes) command in the ADB Shell tool.
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.
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!
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.