yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Android Development] Datastream33:
OK, so I've been thinking about switching the Windows version over to the single-file format much like the FTB Linux AppImage. But, I'd also like to get your guy's feedback on it just to make sure it's something we'd all like to do. Every voice matters!

So, instead of shipping the Toolbox in a folder with the adb and bin directories, those said directories will be embedded into the Toolbox and extracted into a single place on your hard drive (%LOCALAPPDATA%\Datastream\FireToolbox) if missing, making the Toolbox itself, "one-file" (The Updater will also be integrated into the Toolbox itself instead of being a separate program). This will also remove the need for the Installer.

This means, if you take a screenshot, record a video, make a system backup, change the Toolbox's settings, etc it can all be accessible by any future versions of the Toolbox without having to copy the data and paste it into the new build location.

So how do you guys feel about this format change? Or would you prefer we stick to the current format of the Installer and Portable builds?
[Fire HD 8 and HD 10 Android Development] :
I'm still a little baffled tbh (not with the functionality, that works perfectly)

There's a separate option for OTA so I don't understand why the first option (auto updates) refers to OTA at all. I thought the first was only for the automatic updates (i.e. Amazon Apps) Or am I confusing things?

I saw the wording had changed for v6. Has the logic?
[Fire HD 8 and HD 10 Android Development] Jumbo100:
"If You Don't Understand the Problem, You Won't Recognize the Solution"

- old biz adage

As a Linux noob (aka 新手) , I have a vague understanding of the Appimage concept , but tbh I can't imagine how that construct would work in a Windows environment.

Can you explain further?
[Fire HD 8 and HD 10 Android Development] :
Tbh, my inclination is to think it was the other way around. That is, the adb directory in my user environment (site-packages) was found before the AppImage environment was even checked. So the import understandably tried to load adb from there.

We know that the adb module was successfully extracted to appimage environment (we can see it) so there's no reason for it not to load if found. In fact, we know it loads since once my site-package adb was removed, the local adb was found and loaded just fine.So I see the issue as being where FTB/python is looking and in what order, i.e. paths.

I don't understand AppImages tbh, so I am really just guessing here, but I thought they were completely standalone. If so, there is no need for it reach out to a wider environment than its own. The extract process knows where it has extracted to, so it ought know equally where to look. Does an AppImage need the full python sys.path? Can it not be restricted to only its local managed environment, i.e. where it extracted its files to?

Well, I got it to work by potentially nobbling something else! That's not really an ideal fix! ;)

I've no idea what python package was using the adb directory in my local site-packages directory. A pip install of something I'd guess! I've not yet had anything fail (touch wood) so maybe something that has been since removed and not cleaned up after itself. Dunno in truth. Thing is, something did install that adb directory and so removing it would obviously cause it to fail. I think we do have to look at somehow restricting the AppImage to look only in its own managed environment. Or a 'hack' might be to change the name of its own adb directory!

Edit: I see that I'm over simplifying. From playing with Python again (dangerous that) and the 'TryADBImport' script you provided, I see that a module_path variable IS being set to the local environment only and then set as the first path in sys.path. So the import statement is indeed looking more broadly by default.

I've tracked down the python package I had installed. It's simply a python-adb package (https://github.com/google/python-adb) used as "a complete replacement and rearchitecture of the Android project" (why? No idea!) and I've equally no idea why I installed it. I can certainly live without it.
[Fire HD 8 and HD 10 Android Development] DB126:
I'm a fan. Adds some complexity for you but presents a cleaner experience for 95% of the target audience
[Fire HD 8 and HD 10 Android Development] DB126:
FWIW - Issue self-rectified after 24-36 hrs as has been the case in the past w/other devices on FireOS 8. Clearly related to incremental (silent) Google Play Services and related binary updates. Rebooting, waiting 10-15 min, clearing app/device cache all ineffective. Simply leaving alone for a day (radios on) yields a usable device. It's like the thing knows I'm close to curbing it and redeems itself for another round [lol]
[Fire HD 8 and HD 10 Android Development] rbudrick:
Hello. I've spent about 4 hours trying to get Fire Toolbox to even open, but I hit roadblocks every time. If I open v 34.2, I get a whitish window that just closes after a few seconds:

If I try 33.1 I at least get an error message:

I am running Windows 11 on a Surface 2 and trying to run against a Fire 7, 4th gen. ADB shows this as the attached unit:

Glad for any help that can be offered!

-rbudrick
[Fire HD 8 and HD 10 Android Development] eepymeowers:
Hey, I had to get a new Fire 7 9th Gen due to a failed digitizer replacement on my previous one, and the new one I got is running 7.3.2.9, while my previous one was running 7.3.1.5. Is there any way to swap motherboards without damaging them or potentially downgrade the new one to 7.3.1.5? They both still turn on and on the failed digitizer replacement one, I can use scrcpy to control it (for now) since the digitizer partially works. Any help regarding this would be GREATLY appreciated since I do not like the inability to disable OTA updates and the annoying home workaround on my new one.

Edit: to be clear, the main thing preventing me from just swapping motherboards is the fact that I do not currently have a soldering tip that is small enough to desolder and then solder the speaker. I might be able to get one sometime, but if there's any way to swap them easier, I would love to know.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I believe most if not all the components except for the speaker and maybe the battery are plugged in, so it shouldn't be too difficult to swap them out. You can go to ifixit.com or do a google search for disassembly and find youtube videos about most every common Fire tablet.

As far as soldering the speaker wires, you might be able to cut and strip/splice the wires if you can't get a soldering iron, but you can even buy one of those on Amazon for <$25. Personally, I'd buy the soldering iron and some 60/40 solder. Make sure to get the lead solder as the lead-free solder doesn't work nearly as well and takes more heat to melt. Kester is a good brand for solder. It has been around since I was a kid and it still works. :)

Edit: If they are both the same year and model tablet, you can probably just swap the display board and be done. (y)
[Fire HD 8 and HD 10 Android Development] eepymeowers:
They are both Fire 7 2019 models, unfortunately the KF7 2019 model has a little piece blocking the speaker from just coming out of the tablet so I'll figure it out, thank you!
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I found a couple videos that may help a little. The first is a little rough on the battery, but shows the steps involved in tearing one down. The second one is just a battery replacement video, but shows a more delicate procedure for that. Hope it's useful in some way. :)
[Fire HD 8 and HD 10 Android Development] eepymeowers:
I would like to ask though, is it possible to downgrade it from 7.3.2.9 to 7.3.2.2 (iirc the version that put the changes i dislike in place)?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Unfortunately, no. Amazon has locked out downgrades in it's firmware so there is no way to do that without root access, and if we had that we wouldn't need Toolkit. :(
[Fire HD 8 and HD 10 Android Development] pol1345:
I am having problems installing play store on amazon fire table 7 os 8.3.2.3 any tutorial.??
[Fire HD 8 and HD 10 Android Development] Datastream33:
Certainly!

The Toolbox installations currently look like this:

With the "one-file" approach, the installations will instead look like this:

The Toolbox Updater will be integrated into the Toolbox itself, the .dll files will no longer be needed as NAudio will be removed (as it's not really needed), and the Changelog.txt file will also be integrated. Now you may be wondering about the "bin" and "adb" folders? Well, those folders will also be embedded into the Toolbox's exe and will be extracted where needed (hence Fire Toolbox.exe going up from 61 MB to 95 MB). Now these folders are still required and must be present on the user's hard drive for the Toolbox to function. So, the Toolbox on first start will check for the presence of the adb and bin folders in the following location: %LOCALAPPDATA%\Datastream\FireToolbox. If the folders aren't present, then they will be extracted from the Toolbox's .exe to said location.

So the "%LOCALAPPDATA%\Datastream\FireToolbox" directory will look like this:

This format allows us to have a persistent environment for all future versions of the Toolbox. So, if you create a system backup on V35 and then run V36 to restore it, then the backup will show up and be available as if it was created on that build. This also includes Notifications and Settings, so you no longer need to mark all notifications as read or reconfigure your settings each time a new build drops.

So, what do you think?
[Fire HD 8 and HD 10 Android Development] Datastream33:
Well, technically this setting was added before OTA Updates so it was kind of left there. I left it in just as a safety net in case OTAs hadn't been blocked, but an OTA was being downloaded and pending install. It was theorized that using this setting would prevent it from automatically installing, giving you the chance to clear the OTA package from the system. The tool just never mentioned it as it's toggled with a single ADB command, while the Amazon AppStore actually needs to be interacted with so the tool is a lot more vocal about it.

So, in V6 I added in a check to ensure the AppStore is actually enabled and if so, a message to ask the user if they'd like to continue with toggling the automatic app installs feature in the AppStore.
[Fire HD 8 and HD 10 Android Development] eepymeowers:
Figured. Will either suffer with the latest or swap motherboards when I can (or both!)
[Fire HD 8 and HD 10 Android Development] Datastream33:
Greetings!

If you're just looking for a straight up tutorial then Android Police has a great one on the subject. Here's the link. :D
[Fire HD 8 and HD 10 Android Development] Datastream33:
Greetings!

Hmm, 4th gen... would you happen to know which version of FireOS the tablet is running? If its FireOS 4, you'll need to update it to FireOS 5 before the debugger will install. You can check the FireOS version by running this command in an ADB shell:

adb shell getprop | findstr ro.build.mktg.fireos
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Outstanding! Elegantly simple. Really gives consistency to end-user FTB update process and improves the usability of the backup subtool.

As an aside, any initial thoughts on how well FTB would run on the new Windows/ARM infrasttucure? Sounds messy at first glance!
[Fire HD 8 and HD 10 Android Development] DB126:
Solid 2nd on @Jumbo100 sentiments! Long favored standalone (single file) apps and installers that play nice across builds. Nice FTB evolution if you opt to move forward on this.
[Fire HD 8 and HD 10 Android Development] gwanbear:
Hello everyone, I'm a long time occasional user of FTB on Linux. It's a great tool and whilst I use it only rarely, I wouldn't be without it, so muchos gracias to all who develop and support it. When I ran the version 5 linux port this morning, I got asked to register for pysimplegui. That's the first time I've seen this, is it normal? I reinstalled and checked the dependencies but get the same. Is there something else I can do?
[Fire HD 8 and HD 10 Android Development] froopfrucht:
Hello dear staff or knowing people,

i have two issues with my Fire Tablet HD 10 (gen. 2021) after running the firetool box 34.2:

1) As it is said, changing the home button to return to Nova Launcher only works until a reboot. Is there a work around available or is this still up to date?

2) Each time I want to access Google Playstore I have to sign in. If I press on the Sign-In button, the next windows (blue-ish) says sign-in is not possible without any options. I could not find this issue here in the forum, hopefully you know an answer for this.

I used the tablet already >0.5year with standard Fire OS and Amazon and everything and I wanted to give this (firetool box) a shot. Unfortunately the restricted OS-Version seems to leave some compromises, so I am not yet sure if it is worth for my kind of use.

Thanks in advance for your help, appreciate it very much.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Hi, and welcome to XDA!

While I've never seen this problem before, you should be using v6.3 of Toolbox because it's in a new Appimage format that is a single file. It doesn't really need "installing". You just extract it, put the folder somewhere you like, and run it. It'll create a desktop shortcut the first time it's run and doesn't require any dependencies as they're all self-contained. :)

The download is always contained in the first post in this thread and is kept updated as new versions come out. I've linked it above for you also. (y)
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Hi, and welcome to XDA!

The first issue is because of the Launcher Activation Method you've chosen. If you chose Reroute Homekey, it behaves as you've described. If you want a persistent solution, you need to reboot to disable the rerouted key, and now run Custom Launcher in Toolbox again. This time, choose your launcher and select Custom Navbar Key. Follow the directions exactly and don't press buttons before you're asked to do so. This will install Automate and import a flow after making a new replacement Home button that launches your launcher. It's easy to mess up the script here, so proceed slowly. If you follow carefully, it should work fine when you're done.

The second issue could be a number of things, but I suspect it's because you ran either the full debloat or the standard debloat before you installed Google Services and removed a service that is needed by Google for it to operate correctly. I you did run one of the debloat scripts, you can restore the disabled services by running Manage Amazon Apps > Automated tab and use the pull-down menu to Restore Everything. You'll probably need to reboot afterwards for it to restore everything. Then, you may need to uninstall and then re-install Google Services for things to work. Remember to wait 10 minutes or so for Google to update itself before trying to run it after reinstalling it.

I'm just taking educated guesses here so if neither solution applies to your tablet, we'll need some more information on what you've done so far to get a better idea. I hope this is helpful. :)
[Fire HD 8 and HD 10 Android Development] aMikeF:
can you tell me this comands? please :)
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I believe Datastream needs the build.prop file from your tablet as is mentioned in this post to someone else asking for adding support. The post includes a tool for pulling the file automatically as well as the commands to pull it manually. Just pull the build.prop file and include it as an attachment in a post or a PM to Datastream. (y)
[Fire HD 8 and HD 10 Android Development] rbudrick:
Hello. I'm afraid this command gives no error, but also no results. It just returns back to the prompt. In the device settings itself, though, it seems to list the version as 4.5.3, but it does not let me update it. It was factory reset to get it back to a useable state (Mother in law forgot PIN to the device). it does not seem to want to download and run updates, and when trying to do so manually via putting the .bin on the root directory and clicking the "Check Now" button under system updates, it never seems to kick off. Not sure why. It immediately gives a "Last Update Failed" error. Any advice is much appreciated.

Thanks very much!

-R
[Fire HD 8 and HD 10 Android Development] blaacksheep:
You can download the update directly from Amazon from this page. There are instructions there to help you too. :) It appears that the latest update for a Fire HD 7 (2014) is FireOS v5.3.6.2. That should work with Toolbox.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Deleted
[Fire HD 8 and HD 10 Android Development] sparker781:
Good Morning All

I am trying to install either Google Services and Playstore or Aurora on m son in law's Amazon HD8 (2015). I am using Toolbox V34.0 and while the app itself runs and I am able to perform the standard things like remove the ads from the lockscreen. When attempting to run the Play Store option, it spins to start up and then the app just closes. No error message. I am running it on W11 not sure if that's the culprit.

Thanks for the assistance or suggestions
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I'd forgotten about the tablet being an internal, non-public release. You're probably right about it not being able to be updated in the usual manner.
[Fire HD 8 and HD 10 Android Development] Rortiz2:
I know this is off-topic but, If you're interested, I have the same device as you (ariel) and I managed to boot LineageOS 12.1 (Android 5.1.1) on it. I'll release the ROM as soon as I fix a few bugs.

Regarding FireOS 4.5.3, you can update to FireOS 5, but you must follow very specific instructions, which can be found here. Be glad the OTA updater wasn't able to download FireOS 5, because if it did, you'd have hard bricked your device. Keep OTAs turned off if you're going to use FireOS 4.5.3.

Note that if you flash the wrong bootloaders or make a (simple) mistake, you'll end up with a nice paperweight since this device does not have bootrom mode enabled. The only way to unbrick it is through Preloader mode, which was patched starting with FireOS 5.3.1.0.​
[Fire HD 8 and HD 10 Android Development] bally12345:
Hi all got a fire 11 tab and thought I blocked systems updates, don't really use tablet much. But the other day I charged it and it automatically updated to Fire OS 8.3.2.3!

How can I confirm I blocked updates and doesnt even matter now that latest version?
[Fire HD 8 and HD 10 Android Development] rbudrick:
Hello. Your link specifies to download 5.4.0.0, but that appears to no longer be an option offered for download .

For other folks that mentioned I should try the instructions given by Amazon, those are indeed the steps I mentioned that did not work,

Thank you,

R

Edit: I'm also glad to get Lineage if all else fails. A straight Android install at the latest version the device can handle is fine by me, if that's what Lineage is.
[Fire HD 8 and HD 10 Android Development] Rortiz2:
You should be able to complete the process successfully using the latest update bin. Once again, following the instructions provided by Amazon will led to a permanent brick. That's how I killed one of my Fire HD6s.

LineageOS 12.1, which is still based on Android 5.1.1 and derived from AOSP, runs significantly smoother than FireOS, but it doesn't have a newer Android version for now.​

(sorry for the off-topic, OP)
[Fire HD 8 and HD 10 Android Development] DB126:
No point in blocking updates once past FireOS 8.3.1.8. Given current base I'd argue accepting routine updates will do no harm an may actually be beneficial. Of course, if you opt for heavy mods via FTB or use an alternate launcher then accepting an update could yield a temporary annoyance as some preferences may revert to device defaults. So far nothing more agregious as Amazon has effectively locked down (blocked) the most interesting tweaks on FireOS for quite some time. Keep in mind the Android 11 base and Amazon's ongoing war with Google with be the biggest disruptors if you're looking for a more generic Android experience.

FWIW - I have the same device on the same firmware level.
[Fire HD 8 and HD 10 Android Development] Massyboy:
Is there a list of what no longer works in the most recent firmware for the Fire 11? I'm experiencing a lot of wi-fi connection issues on mine and am considering just updating it from 8.3.1.5 but obviously I'm hesitant about knowing what functionality I'd lose if I did so.

I remove lockscreen ads and disable the lockscreen too but nothing like custom launchers. Any pointers would be useful and apologies if there's somewhere where this stuff is documented
[Fire HD 8 and HD 10 Android Development] Massyboy:
I've just seen that you added ControlD support-I have a ControlD account but I can't seem to work out how to add my account info in when selecting ControlD on the DNS resolver options. Am I missing something?

Many thanks
[Fire HD 8 and HD 10 Android Development] gguerra:
Hello Guys

Having an issue with Automate. I am using the Shortcut Launcher method and I am having it start Evie custom launcher . I did enable "Auto Start" in settings. It seems it is not starting the custom launcher on it's own.

Did I miss a something?

I know Automate is not affiliated with FTB, I just thought someone would know.

Is there anything else I can check? TIA

Edit: I will be trying the Custom Nav Bar method instead although I still need to tap on the home button so not automatic, does it work better on restarts?
[Fire HD 8 and HD 10 Android Development] varyamereon:
Hey @rem3r, did you ever find a solution for this? I'm looking to achieve the same thing.
[Fire HD 8 and HD 10 Android Development] DB126:
Not aware of a decisive list. I opted to pay up to remove lockscreen ads (Fire 11 only) as biometric login is smooth/reliable/seamless. Far better than under glass readers on many new phones.

Fire 11 is a cranky bloke on FireOS builds <8.3.2.x. I was close to abandoning mine until 8.3.1.9 came out. Things have only gotten better with subsequent updates.

Using a credible VPN based ad blocker (eg: Adguard) goes a long way toward improving both user experience and device stability.

Have to choose your battles. I'm long past dinking around with devices for hours to achieve some modest cosmetic goal. Become a grumpy old goat. Yeah - get off my lawn too. :)
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Haha. Reminds me of this shirt from Amazon. ;)
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Woke Agism !
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Custom NavBar is often preferred since since it is persistent after device reboots.

Recheck that all Automate permissions are enabled, especially "Run on system startup" . Use FTB to reinstall Invoker Flow if necessary.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Wi-Fi connectivity is pretty reliable on stock Fire tablets/FireOS OOTB. Updating f/w may not resolve your issues and may complicate your FTB mods.

Check the network configuration setting on any DNS resolver/adblocking hardware/software you may be using for any conflicts.

Connection issues may also arise if you are using "network metering" to block OTA updates.
[Fire HD 8 and HD 10 Android Development] DB126:
Conversely, a firmware update will likely help If the issue is primarily with Google based apps (including Chrome) -and- Google Play Services is installed. I experienced numerous connectivity related issues on FireOS 8.3.1.x with GPS installed. Problem dissipated when GPS was removed. Seemed related to GPS attempts to establish if an Internet connection was present. Erratic and annoying; Fire 11 almost became a high speed frisbee on several occasions. No such issue on 2023 HD10s acquired later and already on fire OS 8.3.2.x.