[WINDOWS/LINUX][TOOL]Fire Toolbox V34.0

[blaacksheep]

Will the Fire Toolbox be avaliable for the firestick or fire TV?

Welcome to XDA.

Right now it's not available for those devices, but we're still trying to talk Datastream33 into it. For the time being though, there are plenty of threads on XDA dealing with those devices. If the search function here in the forum doesn't give you the results you want, try using Google and add XDA into the search string.

 

[spocko]

Did you or anyone figure out how to fix this issue?

Unfortunately no. If a google account with active Family Link supervision is used on the Fire tablet, then that interferes with the ability to use Google apps on the tablet, even when the Family Link app is not installed on the tablet. The only "solutions" I'm aware of are to disable Family Link supervision on the google account, or use a different google account on the tablet.

 

[Datastream33]

How's it going, guys?

I sincerely hope everyone is having a great day/week so far!

I'm happy to announce that a new update has just been released! Now, let's take a closer look at what makes this update tick.

The New Reworked/Improved Pull and Push Tool​

You may notice that when the tool is executed from the Main Menu, it will now immediately throw you into the tool instead of presenting a window where you'd select what subtool you wanted (pull or push). This window has been removed and replaced with 3 tabs that line the top of the tool's window: Push, Pull, and Delete. By default, the Pull tab will be selected by default. The window layout is basically the same as the original, except the back and home buttons have been relocated to the left of the address bar instead.​

​

The Push tool when its tab is clicked will now condense the "Files in directory" and "Directories" lists to make way for the Push subtool that will take the original place of the "Files in directory" list. This change was made so when pushing a file or folder, the files in the current directory can still be viewed if needed.​

​

The ability to delete files/folders off the internal storage has also been added in this rework.​

​

Reading and processing of the internal storage has also been reworked, along with the Back and Home functions.​

Spoiler

​

​

Multi-User Support is Finally Here​

The Toolbox now supports applying changes to multiple users. This change wasn't easy and required a lot of changes under the hood, but it's finally here! Please let me know if you come across any issues with this new system.​

​

When you launch the Toolbox, you should see a new icon next to the Settings that looks like an outline of a person. Clicking this icon will bring up a new panel where you can select what user the Toolbox will apply changes to. By default, the foreground user (the currently logged-in user) will be selected, but this can be changed by clearing the "Apply changes to the foreground user." checkbox. You will now have the option to select what ever user you want from the list above the checkbox. However, keep in mind that any operations that require the user to be in the foreground may cease to function.​

Spoiler

​

​

The UI Frontend for ADB Shell​

This tool took some time to get working and frankly was one of the most annoying things to produce. Anyway, enough about ranting and let's take a look at what this tool adds. Firstly, one of the major features of this tool is the fact that you now can log the session. Any command typed and executed (if the user has enabled logging of the session) will be outputted to a log file that's saved to the user's Desktop.​

​

Command history is another thing that was added. Unlike the real thing, the Toolbox will save and remember commands you've executed and will even be available if the window is closed and a new session is started. This works by saving the executed commands to a text file in the ADB folder and parsing through it when the user presses the up or down arrow keys.​

​

My favorite part of this tool is the ability to toggle between using a debug shell or a standard shell when using a 7th gen device. Making commands such as "ls" and "cd" available in the /storage/emulated/0 directory.​

​

In addition, if you even want to go back to using ADB in CMD (like before) then all you need to do is open the Toolbox's Settings and check the box for "Start ADB Shell Tool in CMD". This will force the Toolbox to open the instance in CMD instead.​

Spoiler

Toolbox Updater and Micropatches​

In this update, the Toolbox Updater has been upgraded to include a better function for installing micropatches. Instead of making the required changes (like renaming the directory) in the Toolbox Updater itself, the Updater now generates a batch file in the Temp directory to take care of finishing the process. This is good because it ensures no processes are still using the folder (Toolbox Updater)... allowing it to actually be renamed properly. This should solve the issue of the shortcuts pointing to an invalid location causing Windows to not be able to locate the Toolbox's main executable.​

​

​

​

Wait, that's not everything! Take a look at the below changelog for the full scoop...

Fire Toolbox V21.0 - Changelog

• [Push and Pull] Merged push and pull subtools into one subtool.
• [Push and Pull] Reworked and improved the subtool.
• [Push and Pull] Added the Delete tab which has the ability to delete directories and files.
• [Manage Amazon Apps] Debloat lists can now be loaded even if the ListType varible isn't set.
• [Main Menu] Added "User Selector", a subtool that allows you to control which user the Toolbox applies changes to.
• [Custom Launcher] The Toolbox is now capable of setting the custom launchers as default on new gen tablets.
• [Sideload Apps] Fixed the misconfigured variable causing the Toolbox to crash when the Sideload Apps tool is executed.
• [YouTube Clients] Updated NewPipe to the latest version.
• [Toolbox Updater] Improved and fixed issues in the micropatch process.
• [Device Information] Instead of pulling the build.prop, getprop will be used instead to obtain build properties.
• [ADB Shell] Added GUI, the ability to log ADB sessions, and command history to the tool.
• [Settings] Added "Start ADB Shell Tool in CMD" setting to the Startup category in case you'd rather use CMD instead of the new GUI

If you are ready to download the new update, head on over to the Downloads' section of the OP. Please keep in mind, because the Toolbox Updater is receiving an upgrade, the update must be downloaded and installed manually.

As always, BIG SHOUTOUT goes to all you lovely people who've shown their support, whether that be through interacting with one another, sharing resolutions to issues/problems, and being all around amazing people! I'd also like to take the time to THANK the folks who've supported through the means of donations... I REALLY do appreciate it and would like to thank you for being so kind.

Well, that's everything I've got for now... please have a wonderful rest of your night/day, and I'll see you guys later. Peace!

 

[ya14]

Awesome update. Thank you for your continued hard work!

Just got the tablet and was wondering if there is anyway to control the charging of the battery without root access? Unfortunately got the 11th gen, which cannot be rooted as of this writing. Trying to use the tablet as a home automation kiosk and want to adhere to the 80/20 rule for charging. Would love to not kill the battery or be forced to take it out

 

[ya14]

Gotcha. Thanks!

Yeah, I saw it being possible if you get a smart charger and it'll just kill the power to it once it detects it at X battery level. But that's unfortunate to hear that the stock firmware can't even have this function. Here's hoping Amazon adds it down the road.

 

[Raldor]

Does it work for the Fire TV Stick/Cube?

 

[ump]

Thanks sir, I'll give that a shot, appreciate the help.

So, I did a Factory reset and still same issue will not let me register the device, keeps saying my information is incorrect, I have verified that it is correct. I even called support they had me do a wipe throught the recovery menu and still same issue. Now, they are asking me to return the device so a tech can look at it, any other thought befor I go that route?

Thanks

 

[ump]

It sounds like something is wrong with the device if a issue like this persists after a factory reset, i dont think there is anything more you can do besides letting Amazon deal with it.

That was my thought as well, but hey, never hurts to ask.

 

[blaacksheep]

So, I did a Factory reset and still same issue will not let me register the device, keeps saying my information is incorrect, I have verified that it is correct. I even called support they had me do a wipe throught the recovery menu and still same issue. Now, they are asking me to return the device so a tech can look at it, any other thought befor I go that route?

Thanks

Before you return the device, it may be due to it being new and not fully explored by this tool and users discovering new problems that were just introduced.

If you want to explore a little further, download ADB App Control from CyberCat on XDA from here. Install and run it and let it install it's associated app on your tablet.

Under the Applications tab (1), select Disabled (2). In the search box (3), enter "kindle". Enable any of the apps in (4). Click "Apply" (5). Then close ADB App Control.

This image was from my Fire 10 (2019) so it could be different for the new tablet. Reboot your tablet and try using the Kindle app again.

Edit: Also check that under All or System, that "Content Management System" (com.amazon.kindle.cms) is enabled.

 

[ump]

Before you return the device, it may be due to it being new and not fully explored by this tool and users discovering new problems that were just introduced.

If you want to explore a little further, download ADB App Control from CyberCat on XDA from here. Install and run it and let it install it's associated app on your tablet.

View attachment 5378925

Under the Applications tab (1), select Disabled (2). In the search box (3), enter "kindle". Enable any of the apps in (4). Click "Apply" (5). Then close ADB App Control.

This image was from my Fire 10 (2019) so it could be different for the new tablet. Reboot your tablet and try using the Kindle app again.

Edit: Also check that under All or System, that "Content Management System" (com.amazon.kindle.cms) is enabled.

The saga continues, Under disabled apps and searching kindle nothing shows up

 

[blaacksheep]

The saga continues, Under disabled apps and searching kindle nothing shows up

That means that none of those apps are disabled. I'm about out of ideas. Well, at least you got another useful app out of the ordeal. If you do return it, just do a factory reset beforehand to remove any mods and your personal data.

 

[ump]

That means that none of those apps are disabled. I'm about out of ideas. Well, at least you got another useful app out of the ordeal. If you do return it, just do a factory reset beforehand to remove any mods and your personal data

 

[ump]

Me as well. I did learn a new app so yea! We'll see what the tech at Amazon say, If all else fails and they don't do anything I will de-Amazon it like before and use it as I was, just will not be able to use Kindle App, no huge loss, I can read my books on my Phione

 

[blaacksheep]

Me as well. I did learn a new app so yea! We'll see what the tech at Amazon say, If all else fails and they don't do anything I will de-Amazon it like before and use it as I was, just will not be able to use Kindle App, no huge loss, I can read my books on my Phione

If you're within the warranty window, then swap it for a new one or "downgrade" to a 2019 version that no one has reported these problems with. I somehow doubt that their "tech" can walk you through to a full solution. Thanks for reporting back to us on your results.

 

[ump]

If you're within the warranty window, then swap it for a new one or "downgrade" to a 2019 version that no one has reported these problems with. I somehow doubt that their "tech" can walk you through to a full solution. Thanks for reporting back to us on your results.

I'm just outside the return window but well witin Warrenty, they are going to check it out and either resolve or return it to me, if they can't fine a problem. My hope is they just replace it and call it a day. I'll update once I get it back They say within 5 days

 

[sensboston]

Hey, @Datastream33, thanks for the great app - it's like a Swiss army knife for Fire HDs, all in one! I'm using your app all the time and just donated $10 to you (this should be done much earlier, sorry!)

I have one feature request to you (if it's possible of course!): currently I'm making a "backup copy" of my primary Galaxy Tab A5 on my newly received Fire HD 10 (2021) - just in case of battery discharge or accidently broken screen (by my kids) or.. whatever

Everything are copied fine, and my new Fire HD 10 looks & works exactly as my Galaxy Tab, except Chrome web shortcuts on home screen. BTW, Chrome, installed on Fire HD, is missing option to add shortcut on home screen, however Nova launcher restored all apps & web shortcuts perfectly (web shortcuts with correct icons). But... when I tap on web shortcut, nothing happened but just an error message "permission denied" shown. Do you know how to fix the issue? That will be nice!

Thanks a lot, man! Please keep working on this perfect software!

 

[blaacksheep]

Hey, @Datastream33, thanks for the great app - it's like a Swiss army knife for Fire HDs, all in one! I'm using your app all the time and just donated $10 to you (this should be done much earlier, sorry!)

I have one feature request to you (if it's possible of course!): currently I'm making a "backup copy" of my primary Galaxy Tab A5 on my newly received Fire HD 10 (2021) - just in case of battery discharge or accidently broken screen (by my kids) or.. whatever

Everything are copied fine, and my new Fire HD 10 looks & works exactly as my Galaxy Tab, except Chrome web shortcuts on home screen. BTW, Chrome, installed on Fire HD, is missing option to add shortcut on home screen, however Nova launcher restored all apps & web shortcuts perfectly (web shortcuts with correct icons). But... when I tap on web shortcut, nothing happened but just an error message "permission denied" shown. Do you know how to fix the issue? That will be nice!

Thanks a lot, man! Please keep working on this perfect software!

I think the problem of shortcuts not being available in Chrome and web shortcuts not working is due to Nova Launcher not having all it's defaults. I think you need to issue the following ADB command to fix that:

adb shell pm set-home-activity com.teslacoilsw.launcher/activity

(Someone with more experience feel free to correct me if I'm wrong.)

 

[sensboston]

adb shell pm set-home-activity com.teslacoilsw.launcher/activity

Thanks for suggestion but this doesn't work for me, I'm getting an error:

java.lang.IllegalArgumentException: Component ComponentInfo{com.teslacoilsw.launcher/activity} cannot be home on user 0

 

[blaacksheep]

Thanks for suggestion but this doesn't work for me, I'm getting an error:

java.lang.IllegalArgumentException: Component ComponentInfo{com.teslacoilsw.launcher/activity} cannot be home on user 0

I was just trying to put together something that Datstteam33 said a couple of pages ago with the app name of the Nova Launcher. If you go back to page 292 or 294, I think you'll find a conversation about the same problem you're having. I think he solved it by installing yet another launcher just so he would be offered the option to set the default. Then Datastream33 commented about the launcher not having all it's defaults and saying it was a simple ADB command to fix it which he revealed several posts later. I didn't try it out but just replaced <appname> with the lancher name and posted it. Maybe I've given you enough info to solve your problem. If not, I'll look into it further tomorrow.

 

[sensboston]

If you go back to page 292 or 294, I think you'll find a conversation about the same problem you're having.

I think you're mistaken or got me wrong: there is no conversation about my issue on these pages - guys are talking about setting default launcher by using adb command. But Nova launcher is already set as my default launcher, and widgets support is already enabled - I have no issues at all.

I suspect that creating web shortcuts in modern Android (not sure about FireOS) uses a different API than the widgets API. Or it will require some additional permission(s). So, in my case, set-home-activity command doesn't make any sense.

So, I believe, there are few possible options to solve the problem:

• find a way to grant specific permissions for Nova Launcher
• ask Nova Launcher devs to add "web shortcut" feature (but, I afraid so, simple impossible - a lot of Nova customers are already asked for that feature for a years without any luck)
• find a simple standard Android widget with launch a specific web page functionality. This is a very possible option, I believe so (especially if look for the old widgets for former Android OSes). Unfortunately, I can't find any old/outdated widget with required functionality
• write this widget by myself