- Jun 20, 2020
I just edited my previous post.Where is this folder?
I just edited my previous post.Where is this folder?
Thanks, trying it now. I tried to grab it after it downloaded it, but it must be something wrong on my end the file downloads as 0kb.I just edited my previous post.
There have been ongoing problems with getting Google Services running. They keep changing their servers and we keep chasing them.Thanks, trying it now. I tried to grab it after it downloaded it, but it must be something wrong on my end the file downloads as 0kb.
View attachment 5869485
Your download works as much as I can extract it and put the exe in my folder, but running it just runs the toolbox saying it's 30.3 but the google services downloads still say the links seem broken and don't work.
I'm not sure what's going on but I'm in no rush and I'm sure you have better things to do. I dont mind waiting till something official comes out.
I've tried turning off my pihole and other network protections, no difference.
You're having troubles with Fire Toolbox since Windows 7 requires a set of UBB/ADB drivers which are included in Windows 10/11, but not in Windows 7.
See OP#1 and expand "Getting Started" for specific instructions for downloading and installing drivers for Windows 7.
Looks like FTB installed correctly with the appropriate Windows 7 ADB/USB drivers, so the problem likely is in the way your Windows 7 setup is displaying FTB themes. There's a new "dark mode" in FTB v30.x but not much help if you can't access it.According to that, Toolbox will start once the drivers are installed. I have started toolbox and can get to the main menu but the program background is white as well as the lettering. I can see the buttons if I hover over them but that is about it that I can accomplish since I can't really see what is there.
According to that, Toolbox will start once the drivers are installed. I have started toolbox and can get to the main menu but the program background is white as well as the lettering. I can see the buttons if I hover over them but that is about it that I can accomplish since I can't really see what is there.
Looks like FTB installed correctly with the appropriate Windows 7 ADB/USB drivers, so the problem likely is in the way your Windows 7 setup is displaying FTB themes. There's a new "dark mode" in FTB v30.x but not much help if you can't access it.
It's been a long while since I've used Windows 7 and I can't recall the display settings routines needed. Sorry. May also be a related to outdated/incompatible Windows 7 display drivers.
I've been trying to figure out what would make Windows behave that way. What version of Windows are you running? If it's 7, open control panel, click System and Security, click System. On the left, click Advanced system settings, in the Performance pane click Settings, scroll to the bottom of the list-box and verify that "Use visual styles on windows and buttons" is marked. (Picture below.) If using another version of Windows, the same applies, but the setting may be in a different place. The important thing is to make sure it's checked.
View attachment 5869705
Thank you. at least I know what might be the problem now.
The box was checked when I went to look.
Sorry, thought I responded to this yesterday...There have been ongoing problems with getting Google Services running. They keep changing their servers and we keep chasing them.
Were you successful in your update? (Is the folder now named "Fire Toolbox V30.3" ?) If so, I could send you just the Google files to put in your .../bin/GoogleServices folder. Then it could update. You'd have to be running a compatible version to FireHD10 (2019) though. If you have an older version running FireOS 5 or a newer version running FireOS 8 , you'll need different files. PM me if you want to proceed down this rabbit hole and we'll give it a go.
Edit: Scratch that. I don't have the current Google Services files needed because I installed this so long ago and the app has been updated so many times. If you need Google Services sooner than Datastream can update, then you'll have to do it manually and use a site like apkpure.com to retrieve the needed Google files for your tablet.
Well, it was a thought.
The only other thought I have is to create a new account on your computer, and then install Toolbox in that new account without modifying ANY of the default settings in the new account. Something just says to me that you modified some default setting and that modification wasn't thought of when Toolbox was written. That's the easiest way to check out that theory.
Do you happen to have a reference to which version of YtK needs to be installed for that one to work? That's the main app I buy these tablets for lol.Ongoing incompatibility issues with YouTube TV and FireOS 8 on 12th Gen (2022) Fire tablets. No reported solution yet.
Only immediate workaround is accessing YouTube TV from a web browser
Possible solution would be for a clever dev to code a PWA (Progressive Web App) ie "hybrid app" for YtTV .
A similar situation for YouTube Kids was partially resolved by installing a specific older YtK version.
Try :Do you happen to have a reference to which version of YtK needs to be installed for that one to work? That's the main app I buy these tablets for lol.
Hate to even ask...but i installed the script and granted permissions, but automate won't run nova launcher. The flow from the community worked (easy launcher), but was super slow, so I was trying to get your flow working. In the logs I see: no activity found to handle intent...so it seems it doesn't know what launcher I'm using?Apologies man... been a really long and stressful day.
Yes, there is a stand-alone download. I've attached it here. All you need to do is extract and *import into Automate. Once imported, stop the old Launcher Invoker flow, and start the new one.
* If you get an error while importing, you may need to update Automate to the latest version. Here's the link to it on ApkMirror or just update via the Play Store.
Hate to even ask...but i installed the script and granted permissions, but automate won't run nova launcher. The flow from the community worked (easy launcher), but was super slow, so I was trying to get your flow working. In the logs I see: no activity found to handle intent...so it seems it doesn't know what launcher I'm using?
Oh, and I tried @blaacksheep 's thing of using media record instead of play button to no avail.
I got bold and tried editing the flow to just set the launcher variable to
"com.teslacoilsw.launcher" ... But that didn't seems to do it either
Thanks in advance
Thanks @blaacksheep , I probably didnt give the whole story. I installed the TB way back and I never got rid of the home key because I'm on 7.3.3.whaterver. ( Just found your post on using ReThinkDNS instead of DNS666, which has never worked for me - so thanks for that too!) For the home key, i was using the method that used the app "one button navigation" . However, I was tired of how it blocked the bottom of the screen and didn't rotate properly, so I came back to this thread to see if there was anything new and I stumbled over the Automate script posted by @Datastream33 and your comments about it. Seemed easy enough. ( I did NOT try to re-run FTB because I don't run windows day-to-day and so doing things on the tablet or via ADB is preferred) I got rid of "one button navigation" and installed Automate ( and got all the permissions right after a second try ) and then imported the "Launcher Invoker" script. In it's stock form, it did nothing and I got that error mentioned above, which seemed to indicate that it didn't know what my launcher was ( Nova7 ). From there i tried changing the media key, and then got even more brave and replaced the step that set the launcher variable with a new one that hard coded it as "com.teslacoilsw.launcher". that removed the error in the log, but the flow still failed to do anything. As proof Automate is setup correctly, I was able to enable the flow posted in the community "amazon fire tablet - Easy Home Launcher" and it works - but there is a solid 5 second delay before it swaps to Nova from Fire launcher which didn't work for me. It seemed @Datastream33 's script was better, but for some reason it isn't working.Getting Automate to launch another launcher (other than Fire's launcher) is a 2 part process. The first part is to replace the Home button with one of our making that isn't locked into Fire Launcher. The second part is setting up Automate to read that button press and direct it towards our preferred launcher. If you don't have both parts, it will fail.
The script in Custom Navbar Key does the first part. That's why if it fails to work as expected you have to run an ADB command to get your home key back. The second part is an interactive portion that must be followed exactly to give all required permissions to Automate.
For me, it worked the first time, but then I had been playing around with those aspects already when Datastream33 added that method. I assure you it can work, and work well enough that it doesn't detract from the user experience. You just have to start fresh and follow ALL the on-screen instructions.
|Name||Why It's Required||Required Version||Type|
|Python 3||Execute the Toolbox's scripts.||3.10+||package (obtained using package manager)|
|Pip 3||Download and install dependency modules.||23.0.0+||package|
|TKinter||Dependency GUI toolkit for PySimpleGUI.||Any||package|
|ImageTK (Pillow)||Modify/use Pillow image objects in PySimpleGUI.||Any||package|
|PySimpleGUI||GUI framework.||Any||pip module (obtained using pip3)|
|tqdm||Show download progress bars.||Any||pip module|
|requests||Download data from the internet.||Any||pip module|
|Pillow||Resize images given by the user for display in the GUI.||Any||pip module|
I've got another error report to make. After the update of FTB Linux to V1.1 I'm now getting this "failed to sideload the debugger due to an error" message upon program startup, and doesn't continue after that. The message window contains
View attachment 5922423
From the error, it seems that the path got truncated somehow to
Fire Toolbox V1.1/bin/AmazonDebugger/AmazonDebugger.apk. That's the install directory and somehow the whitespaces in the file path got lost. I verified that the apk is present in the directory.
Can you take a look?
EDIT: This only happens when I connect 'douglas' to FTB Linux V1.1. There's no such error when 'onyx' is connected. My workaround for now is to transfer the apk and install it on the tablet.
Thank you for your response!Hi, and welcome to XDA!
I can answer your first question. Yes, it's possible to hide or remove the navbar with Toolbox. Go to the Modify System Settings subtool > System UI tab > Navigation Bar tool. In the drop-down, select Disable or Hide. Hide just means you have to swipe up from the bottom for it to appear.
I'm sorry I don't know the answer to your second question. Someone else may be able to help you with that. I've only fooled around with split screen mode once or twice because it's not native to Android 9 (FireOS 7) and I don't use it on my phone because my eyes aren't that good anymore.
Non-rhetorically, FTB' s Backup & Restore management function may help to preserve much of the current state of your Fire tablet.Update: just executed Toolbox, everything went smooth! The only annoying thing is that again I have to reinstall and reconfigure everything C'mon guys it's a XXI century! (this is a rhetorical sentence of course)
The download link to the installer seems to be broken, and the portable version doesn't seem to be able to download google services either.
IMPORTANT INFORMATION REGARDING FIREOS 220.127.116.11+ AND THE TOOLBOX (PLEASE READ)
If your tablet is running FireOS 18.104.22.168 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.
We're looking into workarounds to the issues detailed above. Please keep an eye on the forum for further development.
|Amazon Fire 7 (2022)|
|Amazon Fire 10/10+ (2021)|
|Amazon Fire 8/8+ (2020)|
|Amazon Fire 10 (2019)|
|Amazon Fire 7 (2019)|
|Amazon Fire 8 (2018)|
|Amazon Fire 10 (2017)|
|Amazon Fire 8 (2017)|
|Amazon Fire 7 (2017)|
|Amazon Fire HD8 (2016)|
|Amazon Fire HD10 (2015)|
|Amazon Fire HD8 (2015)|
|Amazon Fire HD7 (2015)|
|Amazon Fire HD7 (2014)|
|Amazon Fire HD6 (2014)|
Custom Navigation Bar Icons
Navigation Bar Modifier
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.
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
- 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.
- Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
- 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 22.214.171.124+.
- 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.
- 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.