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

Search This thread

Datastream33

Senior Member
Sep 17, 2017
2,710
2,482
Thank you so much for this tool, @Datastream33 (y)(y)(y)(y)(y) Waiting on my next pay check to send you some love ;)

Question on restoring Fire Launcher. If you do so, will you be able to toggle between that and other launchers?

Hey, no problem at all my friend and THANK YOU in advance for your donation my good friend!!

Unfortuently, Amazon doesn't want you to use secondary launchers so swapping between launchers while Fire Launcher is enabled sadly isn't possible through normal means. However, on newer gens (8+) if you disable Fire Launcher and don't set a default you will be able to switch between launchers freely! Hope this helps! :D
 
  • Like
Reactions: maxq1

vivrosh

Senior Member
Sep 1, 2010
218
56
No matter what I do what driver I'm still my father is this not recognize by fire too or pc I don't know what to do I try so many different drivers in anyone help
 

NutterDog

New member
Jan 19, 2021
4
0
I'm stuck on the custom launcher downgrading Fire Launcher. It's just hanging and not getting the job done. Nova loaded and works, and I set up the Launcher Hijack when this step step was failing. This was how I original set my kindle up when I first got this kindle a couple years ago, though. I hate the newer 5 second delay and I wanted to use the Toolbox to get rid of the bloatware. I chose to reset the kindle to factory and start from scratch. I was really hoping to get the Fire Launcher downgrade to work and go back to the immediate home to nova launcher functionality! I'm messing with a Kindle 10 7th gen. Looks like maybe this is new to Toolbox 11? Is there an issue with it?
 

NutterDog

New member
Jan 19, 2021
4
0
Mega thanks Datastream33!

The issue I had with Fire Toolbox 10.2 and which I was able to resolve was that when I applied the Standard Debloat option the Kindle icon no longer showed on the tablet and then when I tried to read a .kfx ebook on the tablet I got the "The requested action is not permitted. Check parental controls settings and retry." message. What I did to fix the problem after trying multiple options was to re-enable Amazon Newsstand and that restored the Kindle icon and allowed me to read .kfx ebooks again. I think it would be good to leave Amazon Newsstand enabled by default in the Standard Debloat option.
Agreed - I didn't come across this until after I spent a bunch of time figuring out which package was causing the problem. Restoring Newstand fixed it. I couldn't load Kindle Reader from Google Play like someone with a new kindle reported they could, so I had to find a fix for this.
 

sr1sws

Member
Dec 3, 2020
27
6
Agreed - I didn't come across this until after I spent a bunch of time figuring out which package was causing the problem. Restoring Newstand fixed it. I couldn't load Kindle Reader from Google Play like someone with a new kindle reported they could, so I had to find a fix for this.
Hmmm... I just went to the Google Playstore, searched for Kindle and it came up with an 'enable' button. Pushing this restored use of the Kindle app. No Newstand required.
 

vivrosh

Senior Member
Sep 1, 2010
218
56
I just give up try one laptop two desktop all with Windows 10 and four different cable and try different driver still Fire hd 7th generation not detecting
 

NutterDog

New member
Jan 19, 2021
4
0
Hmmm... I just went to the Google Playstore, searched for Kindle and it came up with an 'enable' button. Pushing this restored use of the Kindle app. No Newstand required.
I'm not sure what makes it work on some and others - maybe different gens? I was able to find the app in Google Play and tap install, and it went through the process of downloading and installing, but when it was done the app would not show up and the Install button in Google Play would reappear instead of the usual Open. I tried installing numerous time and could not get it to work. For this reason, I had to go back to trying to make the built-in kindle functionality working again, in which having Newstand active is required to avoid the Parental Controls block.

A simple way to inform people would be to add a note about this when hovering over it in the manual hide/restore page for the next update.
 
Last edited:

NutterDog

New member
Jan 19, 2021
4
0
I just give up try one laptop two desktop all with Windows 10 and four different cable and try different driver still Fire hd 7th generation not detecting
I had the same struggle - several computers, several cords, several kindles. I knew that all the cords I used supported data transfer (some only support charing). I finally got one that worked, and it did have a much snugger fit into the kindle than the other cords I tried. All of my cords were generic extras. The take away is that they are built different! I was finally able to get my computer to detect our fire 8 and 10, both 7th gen, after much frustration.
 

specterflare

Member
Mar 14, 2020
17
19
Hey @Datastream33! Thanks again for this incredible tool. I was wondering if you were willing to accept a suggestion about the newly added FAQ section. In it, you state that it is not possible to replace the new (and annoying, imho) Device Manager button without rooting your device. However, you have underestimated your own tool's ability! All you have to do is use Toolbox to disable the navigation bar and then install one of the many navigation bar apps from the Play Store (I used Navigation Bar). No root required and took me like 5 minutes. Do you think this would be a good addition to the FAQ section, or am I overstepping my bounds? Either way, thanks again, and I look forward to further release.
 

Datastream33

Senior Member
Sep 17, 2017
2,710
2,482
Hey @Datastream33! Thanks again for this incredible tool. I was wondering if you were willing to accept a suggestion about the newly added FAQ section. In it, you state that it is not possible to replace the new (and annoying, imho) Device Manager button without rooting your device. However, you have underestimated your own tool's ability! All you have to do is use Toolbox to disable the navigation bar and then install one of the many navigation bar apps from the Play Store (I used Navigation Bar). No root required and took me like 5 minutes. Do you think this would be a good addition to the FAQ section, or am I overstepping my bounds? Either way, thanks again, and I look forward to further release.
Hey friend,

Glad to hear you find the Toolbox useful and incredible! Really does mean a ton! :D

As for your suggestion, I think that's a good idea and can defintly be added to the FAQ as a resolve to the whole Device Dashboard button issue! ;)
 

lenny64

Member
Dec 30, 2017
29
7
I deactivated anything from amazon, could this block system updates?

The update check fails. If someone knows the urls that are used from the fireOS, then I can check whether they can be reached correctly from my network.

thx
 

lewmur

Senior Member
Apr 30, 2011
3,055
616
I deactivated anything from amazon, could this block system updates?

The update check fails. If someone knows the urls that are used from the fireOS, then I can check whether they can be reached correctly from my network.

thx
Not only can it, but most people wan t it to block them. Amazon updates can restore all the things you took the trouble to disable.
 
  • Like
Reactions: Datastream33

AntwonJenkins

Senior Member
Sep 26, 2010
106
37
SC
Hey @Datastream33! Thanks again for this incredible tool. I was wondering if you were willing to accept a suggestion about the newly added FAQ section. In it, you state that it is not possible to replace the new (and annoying, imho) Device Manager button without rooting your device. However, you have underestimated your own tool's ability! All you have to do is use Toolbox to disable the navigation bar and then install one of the many navigation bar apps from the Play Store (I used Navigation Bar). No root required and took me like 5 minutes. Do you think this would be a good addition to the FAQ section, or am I overstepping my bounds? Either way, thanks again, and I look forward to further release.

Thank you for suggesting this! However the nav bar replacement app you suggested didn't seem to want to work in landscape mode on my Fire 8. I found another similar app called Custom Navigation Bar that is working well, although it did require an ADB command to allow app permissions.

Now if we can figure out how to get the Device Dashboard icon off the lock screen, we'll be all set!
 

lenny64

Member
Dec 30, 2017
29
7
Not only can it, but most people wan t it to block them. Amazon updates can restore all the things you took the trouble to disable.
ok, automatic update is problematic. But if I want to use the latest security patches I need to install updates from time to time. Even if i need to use this nice fire toolbox again.

But a complete reset before the update and restore ... would be too much work.
 

Datastream33

Senior Member
Sep 17, 2017
2,710
2,482
ok, automatic update is problematic. But if I want to use the latest security patches I need to install updates from time to time. Even if i need to use this nice fire toolbox again.

But a complete reset before the update and restore ... would be too much work.

If you'd like to install OTA Updates you can execute the Modify System Settings tool and toggle on OTA Updates, perform the needed updates, then toggle off OTAs once again. Just know an OTA might restore system apps you've disable/hidden.
 

blaacksheep

Senior Member
Jun 20, 2020
2,125
1,380
Buffalo
ok, automatic update is problematic. But if I want to use the latest security patches I need to install updates from time to time. Even if i need to use this nice fire toolbox again.

But a complete reset before the update and restore ... would be too much work.

You don't need to completely reset and restore before/after a system update. You'll just need to re-apply patches for whatever apps get restored with the system update. The updates can be disabled/re-enabled in Toolbox under Modify System Settings > OTA Updates.

Just be aware that any future update from Amazon has the potential to COMPLETELY break the Toolbox and revert your tablet into an Amazon consumption device or add new unwanted apps. An example being the Device Dashboard button that's been added to the problems for Datastream33 to contend with. I locked out updates right out of the box and don't have that issue.

edit: Datastream33 beat me.
 
  • Like
Reactions: lenny64

lenny64

Member
Dec 30, 2017
29
7
I don't need to rush an update, if there are currently problems.

It would be just for security patches, but after a while I'll have to update.
 

jaflame

Member
Oct 2, 2020
6
0
I'm trying to install the original google calculator but the play store says device incompatible. I tried downloading the apk ones but there are parse errors when opening the downloaded file. The other calculator i tried is the xioami one but that one crashes and doesn't work. The rest of the calculator apps are crap to me. Any solutions?
 

Top Liked Posts

  • 3
    I have a Firemax 11 with 8.3.1.5
    Used Rethinkdns to protect and firebox to install Google, change launcher to Nova.
    Everything works fine for a while then for no reason that I can detect (no pattern of apps used) it reverts to the built in launcher and a 5s delay before Nova is back. To get out of that I have to toggle the home switch in Accessibility settings off then on again.
    Using the latest Toolbox version.
    Is there some setting I can use to avoid the slightly tedious reset?
    I believe the accessibility service stops when the app is killed by battery optimization. Try running this command in an ADB Shell to turn off the battery optimization for Launcher Hijack:
    Code:
    dumpsys deviceidle whitelist +com.baronkiko.launcherhijacl
    3
    Hi @Datastream33 and @blaacksheep

    Thanks again for this awesome toolbox!

    Here to report a problem I'm having today.

    I have a Fire Max 11 running version: 8.3.1.5, which I previously, successfully modded with FTB V32.2.

    I decided to factory reset and try the new FTB V34.1, but I'm getting new problems with the Setup Tour that I didn't previously - and still don't - experience with V32.2.

    I go through Step 1 of the Setup Tour, click the "Run Tool" button for "Modify System Settings" and I get 2 problems in there:

    1) "Automatic Updates" incorrectly reports "Enabled" in FTB, when it is set to "Disabled" on the device (and vice versa after toggling this in FTB).

    2) When I click on the button to disable "OTA updates", I get the following error:

    Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue.
    If you click Quit, the application will close immediately.

    Unable to case object type 'System.Object[]' to type 'System.Windows.Forms.Label'.

    DETAILS:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.InvalidCastException: Unable to cast object of type 'System.Object[]' to type 'System.Windows.Forms.Label'.
    at AmazonFireToolbox.ModifySys.imgToggle_SelectedValueChanged(Object sender, EventArgs e)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9232.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    ----------------------------------------
    Fire Toolbox
    Assembly Version: 34.1.0.0
    Win32 Version: 34.1.0.0
    CodeBase: file:///D:/PortablePrograms/Fire%20Toolbox%20V34.1/Fire%20Toolbox.exe
    ----------------------------------------
    Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9236.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9236.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9214.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    ----------------------------------------
    Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Clicking "Continue" doesn't display a change for "OTA Updates", so it seems to be ineffective as a result.

    If I revert to FTB V32.2 these two options still work correctly, so it seems to be an issue introduced in one of the versions since then.

    Any help would be appreciated to get it working with the latest version, if possible.
    Greetings! Thank you so much for the report my friend, and sorry for the crashes/issues.

    In V34 I changed the way the options were created. For some reason, I forgot to update the click handlers for the OTA Updates setting for "unrestricted" firmwares so it was pointing to a default handler that wasn't setup for handling the click event properly... resulting in the crash. I also noticed the toggle settings were inverted (as you mentioned). I've fixed the issues and just release a micropatch. :D

    In addition, I've also adjusted the automatic Updates setting so that if the Amazon Appstore is enabled, then the Toolbox will now ask you if you'd like to toggle the Appstore's Automatic Updates, and will only update the setting if it's in sync with the OTA Automatic Updates. And lastly, a new window will appear when toggling the Amazon Appstore's automatic setting that shows what the Toolbox is doing. Thanks again for the report! :D
    2
    Hey @Datastream33

    Advisory to FTB installs of alternative YouTube apps.


    Google's announcement :
    Ah great, they're going down the same route that Reddit went. Killing off all 3rd party apps that don't adhere to their ads modal. Cool.
    2
    Please halp me guys I really want to use costume launcher with shortcut launcher method but it doesn't work.
    Are you using Nova 7 by chance?

    If so, run this command in an ADB Shell and then stop and start the Shortcut Launcher flow in Automate:
    Code:
    settings put secure tb_custom_launcher_name Nova7
    2
    I've fixed the issues and just release a micropatch.

    Just downloaded the micropatch and can confirm it's all working now. Excellent support, thank you!

    In addition, I've also adjusted the automatic Updates setting so that if the Amazon Appstore is enabled, then the Toolbox will now ask you if you'd like to toggle the Appstore's Automatic Updates

    Can confirm this also popped up and worked as you described.

    Thanks so much for your quick response.

    I can confirm that from a standing start, following a Factory Reset, my Fire Max 11 (running 8.3.1.5) was able to succefully complete every step of FTB's Setup Tour. Prefection! :D
  • 4
    I just got a Fire HD 10 (2023) that I ordered yesterday.
    When I ordered it, I did not uncheck the "Link the device to your Amazon account".

    So far, I have not turned it on. Would it be a problem if it updates to latest FireOS?
    Wouldn't I be able to still use the Toolbox??

    If updating is a big deal, I guess I would just have to turn off my Wifi at home, turn the tablet on and factory reset it. This way it should forget my home wifi, shouldn't it?
    It's fine if your tablet registers w/Amazon. As for updates, it really depends where your interests/passions lie. Blocking updates will give you more control over the device but an inferior experience with some apps, especially those linked to the Google ecosystem. Allowing updates will resolve most app issues but limit device customization. It's important to understand there is no going back once your device updates.

    More recent Amazon devices (2022 and beyond) running FireOS 8 fare poorly with Google apps if not brought to at least FireOS 8.3.2.x. Once at that level there's little benefit to continued blocking.

    If you value control and enjoy endlessly fiddling with your device then follow advise posted earlier in this thread to keep the Amazon boogeyman at bay. If you bought your device with the intention of using a variety of contemporary Google apps then allowing your device to behave naturally will yield the fewest hassles.
    3
    After following the instruction, when I try to install Google Sheets (or Docs, etc.) in Google Play Store, the process of 'Pending, verified by Play Protect' keeps going indefinitely. Please help because I want to install Google sheets on this Fire HD 2017. Thank you.
    You're experiencing "intergenerational software" clash/incompatibility.

    Google has been recently upgrading their "Google Suite" software to run only on newer versions of Android OS.

    For example, current Google Sheets app now requires Android 8 (or later). Same for Google Docs.

    Gen 7 (2017) Fire 7/HD8/HD10 tablets run FireOS 5.x (based on Android 5.1, API level 22). Latest FireOS version is f/wv 5.3.7.3.

    You'll need to sideload an older version of the software from a reliable APK repository, compatible with FireOS 5.x , although some earlier app versions may be backward compatible. YMMV.

    Make sure to diable auto-updating of software in Play Store to maintain older software versions, both universally and app specific.

    Alternatively, you can access Sheets from the web app @ sheets.google.com (in desktop mode), or from Google Drive.
    3
    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.
    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.
    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:

    Launch the Toolbox, click the gear icon at the upper-right to open the settings, click the "About" tab in the Settings window, then click "Open Installation Directory".

    This will open the Toolbox's root directory in File Explorer. Now click the "bin" folder, then "System Backups". In the "System Backups" folder, create a new folder, and name it "Amazon Fire HD 7 (2019)" (without the quotes). Now double click the "Amazon Fire HD 8 (2020)" folder, and copy the backup file you want to restore onto your 2019 tablet (the UserApps_Backup.7z file from earlier). Paste that backup file into the "Amazon Fire HD 7 (2019)" folder. Now the backup should show up in the Toolbox for restore.

    Please note that I don't recommend restoring backups on different Android versions. But because both your tablets run Android 9 you should ok as long as you're just restoring user apps and package states.
    3
    Welp, an unexpected gift for those running a FireOS 8.3.2.2 on a Max 11 or HD10; not certain about other devices rocking FireOS 8. Google Voice typing is working again! I'm dictating this post on a Max 11.

    Not sure when that got enabled; thought I had checked after fire OS 8.3.2.2 came out but perhaps not.

    Happy yapping!
    3
    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.

    Your File Management app set up as an Anonymous FPT client as default.

    If you don't want Anonymous mode by default, reconfigure app as a regular Google/Android FTP client.
  • 381


    Fire Toolbox V34.0
    All-In-One Toolbox for Fire Tablets!




    FTBV32.png



    Introduction.png


    The Fire Toolbox is a collection of useful ADB (Android Debug Bridge) tweaks that can be applied to Amazon's Fire Tablets. The Toolbox project aims to help users fully customize and unlock the full potential of their tablets by putting all the power into their hands.
    The Toolbox doesn't touch the system partition meaning all changes made can be reversed either through the tools/subtools themselves or through a factory reset. This means the Toolbox does NOT void your warranty.

    DeviceCompat.png


    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

    * Generation equates to the year the tablet was released. For example, if the generation is 13 it means the tablet was released in 2023. 10 means the tablet was released in 2020... so on and so forth.

    ** Restricted equates to wether or not Amazon has locked down the firmware. When a firmware is restricted it means we cannot fully block OTAs, use custom launchers without Fire Launcher, lockscreen ads can no longer be permanantly removed, and some system apps can't be disabled. Even though a tablet is marked as Restricted in the table above, sometimes it may only apply to certain versions of FireOS. If your tablet is on a firmware before the listed firmware then your tablet is NOT restricted. See the "FireOS Restrictions and Fire Toolbox" section of the FAQ section (post #2) for further information on restricted firmwares.

    GettingStarted.png


    Getting the Toolbox up and running with your tablet is surprisingly a very easy procedure. The only thing required is for you to enable Developer Options and ADB on your tablet. So, without further ado, let's get started.

    At this point, please read the section below, and make sure to follow the correct guide that is made for your tablet on how to set up the device so it works with the Toolbox.

    FIRE HD 7, 8, 10 (2018 - 2023) Guide:
    Before purchasing the tablet:
    • Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)

      if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
    Booting the tablet for the first time:
    • Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
    • When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
    • Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
    • Select ANY network from the list (even if you don't know the password).
    • Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
    • At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
    • It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
    • You should immeditely be thrown into Fire Launcher. You're now ready to enable USB/ADB Debugging.
    Enabling USB Debugging:
    • Turn on your tablet and go to Settings > Device Options > About Fire Tablet and tap on the Serial Number until you unlock Developer Options.
    • Press the back button and find the new Developer Options and toggle it on.
    • Scroll down till you find USB Debugging and enable it.
    Setting up the drivers:
    If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time.
    • Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
    • Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
    • Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
    • Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
    • At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
    • On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
    That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!

    FIRE HD 6, 7, 8, 10 (2014 - 2017) Guide:
    Before purchasing the tablet:
    • Make sure you uncheck the "Link device to your Amazon account to simplify setup" box before Adding to Cart. (See this screenshot, credits go to @ancientrael)

      if the box remains checked, your tablet will automatically update to the latest version of FireOS the second it auto-connects to your wifi.
    Booting the tablet for the first time:
    • Wait for your tablet to fully boot up for the first time (may take a few seconds to minutes).
    • When it boots, it will ask you for the language you'd like the OS to use. Select your prefered language.
    • Tapping the blue arrow at the bottom of the screen, you'll be asked to connect to a WIFI network.
    • Select ANY network from the list (even if you don't know the password).
    • Once it asks for the password, tap the "Cancel" button and it will take you to the previous screen with the Wifi networks.
    • At the bottom of the screen, you should now see a "Skip Setup" button, go ahead and tap that.
    • It will now ask if you're sure you want to skip fire setup. Just tap "Skip" once more.
    • You should immeditely be thrown into Fire Launcher. You're now ready to enable ADB Debugging.
    Enabling ADB Debugging:
    • Turn on your tablet and go to Settings > Device Options and tap on the Serial Number until you unlock Developer Options.
    • Find the new Developer Options and toggle it on.
    • Scroll down till you find ADB Debugging and enable it.
    Setting up the drivers:
    If you are on Windows 10 or Windows 11 you do NOT need to following this guide because Windows will setup the needed drivers by default automatically. All you need to do is plug your tablet in and Windows will take care of the rest. Please wait until these drivers are fully installed before laucnhing the Toolbox for the first time.
    • Download the latest version of the Toolbox from the Downloads section of this page and install it onto your PC.
    • Plug your tablet into the computer, and Windows will start installing the MTP drivers. It will also attempt to install the ADB driver but will fail. (This is normal and to be expected)
    • Launch the Toolbox, and it should detect your Windows version and inform you that further driver setup is required. It will then ask you if you'd like the Toolbox to download and install the drivers.
    • Click the "Yes" button, wait for the download to finish and follow the driver setup. If this for some reason doesn't work, please follow this guide to manually install the drivers.
    • At this point, If drivers are setup properly... the Toolbox will inform you that the "device isn't authorized. Please authorize your device now."
    • On your tablet, you should see a new prompt asking if you want to Allow USB Debugging and should show the computer's RSA key fingerprint. Tick the box that says "Always allow from the computer" and hit ok.
    That's it, the Toolbox should recognize your tablet and will take you to the main menu. Enjoy!

    Downloads.png


    Windows:​

    Version
    Installer (.exe)
    Portable (.zip)
    Update Post
    VirusTotal
    V34.0​
    Post
    Link​

    SHA256 Hashes​

    FilenameSHA256 Hash
    FTB_V34.0_Installer.exedf19c7f691674c1dc4d3a91c32f3fa351a27c344f3bf265c6d8301f0056a98dc
    FTB_V34.0_Portable.zipf47618c589e61dc94c7672b37d38a3ae31bb8edf2e5bae8f0ded8d2a1321dd5f

    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​
    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​

    *Linux:​

    Version
    Python Version
    Installer
    Update Post
    V5.0 (Beta)​
    3.10.x​
    Post
    V5.0 (Beta)​
    3.11.x​
    Post

    NOTICE: You must obtain the correct version for your installed Python version. Run "python3 -V" in the Terminal to get the installed python version for your distro.

    SHA256 Hashes

    FilenameSHA256 Hash
    FTB_V5.0_Installer_Python3.10.7z985f1fc24d21c7506b9245f8ba37194380535fb5a8ef9af762d7d6d3853498ec
    FTB_V5.0_Installer_Python3.11.7z110bebfe5e28c75bd6235434f3b0ea640d6f24f77ef859a704db2a673972e01b

    * While in Beta, I'd like to heavy push the installer so that we can get it to stable along with the Toolbox. So, for now, the only download option will be the installer. Once the Toolbox and the Installer are both stable a portable option will be available. However, if you really need a portable version please PM me and I'll send you the link.

    Version
    Python Version
    Installer
    Update Post
    VirusTotal
    V4.0 (Beta)​
    3.10.x​
    Post
    Link​
    V4.0 (Beta)​
    3.11.x​
    Post
    Link​

    Version
    Python Version
    Installer
    Update Post
    VirusTotal
    V3.0 (Beta)​
    Python 3.10.x​
    Post
    Link​
    V3.0 (Beta)​
    Python 3.11.x​
    Post
    Link​

    Version
    Installer
    Portable (.zip)
    Update Post
    VirusTotal
    V2.0 (Beta)​
    n/A​
    Post​
    Link​
    V1.0 (Beta)​
    N/A​
    Post
    Link​

    Other Downloads:​

    Resource
    Resource Link
    Applicable Tools
    Custom Navigation Bar Icons​
    Navigation Bar Modifier​
    Toolbox Changelogs​
    N/A​

    Donate.png

    If you like my work and would like to support me feel free to Donate. Thank you!
    76
    FAQ.png


    The Toolbox won't display correctly. The window is pure white and the text is faded. How can I fix this?
    2021-01-07_052532-jpg.5179871

    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! :D
    32
    I'd also like to take the time to acknowledge today as a very special day for this project! Today marks the 3RD YEAR anniversary of the project!!! 😄 🎉🎉

    It seems like only yesterday, that the first version of the Toolbox was released! It's just crazy to think that it all started in 2019, as a very simple batch file program designed solemnly to remove lock screen ads, and has grown into what it is today! If you're interested in what started it all, I'd highly recommend checking out this post. It dives a little more into the Toolbox's background and it's beginnings!

    I just wanted to THANK YOU all from the bottom of my heart for making the last 3 years so memorable! If it wasn't for the amazing support and this wonderful community, the project would've died a long time ago! You guys are the fuel that feeds the Toolbox's development!

    Through this project, I've gotten to meet some wonderful people that I'd consider to be good friends:
    @Davy49, @Tailborn, @Falcon342, @blaacksheep, and of course you (the one reading this)!

    So, where does the Toolbox go from here? Well, I suppose the next step would be to bring the Toolbox to more platforms! Currently, the Toolbox is being ported to other platforms using the Python programming language, and PySimpleGUI. I've also been asked if the Toolbox Python port will ever become open-source, and I think the answer is most likely yes. Big things are planned for the Toolbox this year, and I hope you'll join me on this journey!

    HERE'S TO THE TOOLBOX'S 3RD YEAR ANNIVERSARY!! 👏:D
    28
    Last edited 9-30-2022

    A lot has changed since I first posted this. Toolbox has been updated to v29.0 and now has a new method of replacing the Fire Launcher, DNS66 is only a delaying tactic and doesn't stop updates in all cases, and the Lockscreen Ad removal process in the old FTB v9.2 still works to remove the ads. I leave the post up, but understand that it's just for reference as a starting point for you to explore these things.


    What to do about F/W v. 7.3.2.2

    So your Fire tablet has the latest firmware update on it (v7.3.2.2) and Fire Toolbox won't do what it's supposed to. All is not lost. I've collected some workarounds that will keep Amazon at bay. The three main problems are:

    1) You can't stop Automatic updates.

    2) You can't get rid of the lockscreen ads.

    3) You hate the Amazon Launcher, but Amazon won't let you change it permanently.


    Once those three problems are addressed, you pretty much have your tablet back. The Toolbox will still work for all the other things you want modify. First, get your tablet set up with Toolbox, install Google Services, and install the launcher you want. (Make sure to select "Enable Widget Support".) We'll take care of the Amazon Launcher later. So let's get started with the 3 main problems.

    1) Automatic updates.

    This method is far from perfect and has sometimes allowed updates to somehow slip by. The only other way to do this that I know is to use an app blocking firewall and block the update apps. I chose this method because it doesn't require a 'training period' to train the app on what to block and what to let through. Also, if you've already got lockscreen ads in your tablet's cache, this will not remove them. This method must be in place before you first connect to WiFi for the lockscreen ad blocking to work.

    We need to stop the tablet from contacting Amazon to update it's firmware. We can no longer disable the service that does this, BUT, we can interfere with it's ability to contact the server from which it gets its updates. On a computer, we would modify the hosts file and block the addresses of the update servers. On an Android device, we need root access to do that, but there is an alternate way of adding things to the hosts file - with a VPN. We'll use a free and open source ad blocking VPN app to do this. The app is called DNS66 and it's available through F-Droid. You need to make sure this is always running to be protected from updates. Luckily, android has a feature to assist us in this. It's called "Always On VPN" and we need another app to access the hidden setting for this. We'll use "Activity Launcher" to get to this setting. Activity Launcher is available from Google's Play Store.

    It turns out that using Activity Launcher to change this hidden setting does nothing more than give you an extra notification that your VPN is off. It doesn't stop traffic, so it's useless. Besides, my tablet has taken to turning the "Always On VPN" setting back off every time I boot. (Thanks Amazon!) Activity Launcher is still useful for finding settings that Amazon doesn't see fit to include. It also makes desktop shortcuts to those settings if you wish.

    Download DNS66 to your computer from f-droid.org or from the attached file, copy it to your tablet and install it. Also go to the Play Store and install Activity Launcher. Finally, get the Amzn_Blcklist.txt that's attached to this post and copy that to your tablet. The blocklist file must remain on your tablet, so put it somewhere where it won't get deleted. I suggest in the root of your internal storage. (/storage/emulated/0)

    Open DNS66. There are a couple settings that must be changed. On the Start tab, turn on "Watch Connection". (All 3 switches should now be on.)
    DNS66-start.jpg

    Now go to the Hosts tab. Tap the "+" in the lower-right. Under Title, type "Amazon Blocklist". Tap the paper clip on the next line. Navigate to the Amzn_Blocklist.txt file you downloaded earlier and select it. Now tap "Done" in the upper-right. You should now have the first and last entry on the displayed list selected.
    dns66-hosts.jpg

    Now go to the Apps tab. Turn on "Show System Apps". Tap the gear under the Show System Apps switch and select "No Apps". All the switches below that should now be off.
    dns66-apps.jpg

    You can optionally set your own DNS servers on the next screen if you'd like. I like to turn on Custom DNS Servers, deselect the German ones that are pre-selected, and then turn on the last two servers (CloudFlare).
    dns66-dns.jpg

    This can also be done with Toolbox making this step unnecessary. Now go back to the Start tab. Tap "Start". It will notify you that it wants to connect to a VPN. Tap Yes or OK and allow it.

    Quick note: Do not use the Toolbox DNS changer in Modify System Settings AND the DNS66 Custom DNS setting together. This will cause connectivity to fail. I use DNS66 and not Toolbox's DNS changer. Having the Custom DNS Servers set ins DNS66, and using the Toolbox DNS changer simultaneously caused me hours of grief trying to figure out why Google couldn't connect!

    Now Launch Activity Launcher. Tap the magnifying glass in the upper-right. Enter "VPN". One setting should appear called "VPN". Tap it. Tap the gear on the end of the DNS66 line. Turn on Always-on VPN. Turning on the other switch makes Google Services think you are disconnected, so leave that one off. Step one accomplished.

    actlaunch-vpn.jpg


    Notes:

    DNS66 takes several seconds before it gets started when you first boot, so it is possible that the tablet will make a DNS query for the update server or the lockscreen ad server before it loads. Best practice is to turn off WiFi before you power down or reboot.

    ----------



    2) Lockscreen Ads.


    Toolbox v29.0 now takes care of lockscreen ads!


    It turns out, that blocking those update servers also blocks your tablet from getting any lockscreen
    ads! No further action is needed. I stopped investigating this because I chose to disable the lockscreen completely. If you want to do that, you can do it in Toolbox, or in Activity Launcher that you just installed. Launch Activity Launcher. Tap the magnifying glass. Type in "screenlock". Now tap the last item (.password.ScreenLockSuggestionActivity). Select None and you're done.



    Notes:

    It has come to my attention that when disabling your PIN, it may still ask you for a PIN by Parental Controls for some settings or activities. I would suggest if you're going to disable your PIN, to first set it to something simple like 0000, reboot it, and then disable the PIN. That way you'll know what PIN you set if it suddenly asks you next month for your PIN.

    Another way to disable lockscreen ads is detailed Here.

    ----------



    3) Amazon Launcher.


    New: Toolbox v29 has remediated most of the difficulties in replacing the launcher. Always check that you have the latest version of Toolbox. I'll leave the rest of the post up to inspire ideas.


    The latest version of Toolbox (v 28.1) has a new tool called 'Custom Navbar Key'. This method uses Automate to automatically replace the Home button every time you reboot. It works rather nicely. I leave this section posted for completeness and to facilitate experimentation on other choices.

    The way we're going to get rid of the Amazon Launcher is by not calling it! We're going to replace the Home button with another button that we can map to any launcher we'd like. This isn't a perfect solution, but it is FREE. If you're willing to spend a couple bucks, you can purchase a more configurable gesture navigation app with more features, but this is FREE, so maybe you can accept it's shortcomings. I'll keep this post updated with other navbar replacements that people suggest.

    Go to the Play Store. Get and install "One Button Navigation". Launch it. It will want you to turn on Accessability Service for it. Follow the on-screen instructions and turn on "One Button Navigation Bar". You'll see your new nav button at the bottom of the screen. I like to adjust the width down to a dot, like the button it's replacing, but that's up to you. I also like to make the background black and the botton bright yellow so that I'm reminded it's running. Set up the background and button colors as you like them. Yeah, I know the ads in this are obtrusive, but you'll never see them once it's set up. Also DNS66 will block the ads if you install that first.
    obn-set.jpg

    Next tap the Action tab. Tap "Single Click". Scroll down and select "Launch Application...". Select the launcher that you installed with Toolbox here. In my case, it was Nova 7. (Google updated the Nova version that Toolbox installed.) Now you can set any other actions you'd like for the new button.
    obn-act.jpg

    I didn't want anything additional, so I made the gestures similar to the original buttons. This is all up to you. You can reverse them or set additional functionality to the button. I ended up with a new navbar that covers the original navbar (the one with the home button that brings up the Amazon Launcher). I now have a button that when pressed, takes me to my launcher. When I swipe it left, it goes back a screen. When I swipe it right, it shows the recents. I spent a lot of time with other navbar replacements and this is the minimalist replacement that works best for me. YMMV. Before someone complains that it doesn't work in landscape mode, I'm not the developer. You should rate it and leave a comment for him! This is the best I could find that does what I want for FREE.

    ----------



    I'll edit this post with your suggestions for better solutions to these problems and keep a list of navbar replacements that people suggest at the end so you can find what works best for you.


    ----------------------------------------------------------
    Some Suggested Navigation Bar replacements:
    ----------------------------------------------------------

    One Button Navigation Bar by Nu-Kob (PlayStore)

    Pie Control by coolAce (PlayStore)

    Simple Control by coolAce (PlayStore)



    DNS66 is available from F-Droid.org (dated March 26, 2021)
    Activity Launcher is available from APKMirror.com (dated March 21,2022)
    21
    What's going on, guys?

    I sincerely hope everyone is doing good, and having a wonderful December so far!

    Today marks the release of V26.0 of the Toolbox! So, without further ado... let's take a look at what this release has to offer!

    Welcome, Welcome, Welcome... Screen!​

    You know, every time I run a build for the first time I go through the Theme Selector, then the Tour, and then the Welcome Screen. I just think to myself "this is just a mess" - so in this update I thought I'd focus on improving it and making it better. I started by re-designing the Welcome Screen and doing my best to link all three tools into something that looked visually appealing. Now, in a tabbed interface you'll find the Setup Tour in the very first tab, Theme Selection (with a new UI) in the second, Installation Management in the third, and finally in the fourth the Changelog.

    Now let's talk specifically about the Installation Management tool. This bad boy now has the ability to read installations from directories other than the default (localappdata\Datastream). So, if you've got your installations in a custom location, and you'd like to manage them, it's now possible to point the path to that location. This should help make managing installations a lot easier!

    Custom Launchers on FireOS 7.3.2.2​

    As some of you may know, I bit the bullet and updated my tablet to the latest version of FireOS... to the dreaded 7.3.2.2. This update, from what I heard, caused the Custom Launcher and disabling OTAs tools to no longer function and after updating, I soon discovered that it was indeed the case. I then tried everything I could think and well really didn't turn up any valuable workarounds... until I tried the method we'd been using on older gen devices... and it worked! Of course, just like on the older gens, it has the drawback of being removed every time the device is rebooted. However, it's the only method I could find, so it's better than nothing, right?

    Anyway, while coding it in I decided to take the liberty of also clean up the code, and the UI a bit. What's cool is the tool will now read what generation your tablet is, and display what methods are available to use. You'll also find that the initial method selection UI is a lot more usable compared to its previous iteration.

    Change the Timeout for the Display?​

    Ah, the latest addition to the General group in the Modify System Settings tool. This subtool not only allows you to alter the timeout to traditional values, but also allows you to set a custom timeout. Want your screen to sleep after 24 hours of inactivity? This one's for you folks who want to extend the timeout as much as you can. Just be careful, it may cause a burn-in if your tablet's screen remains on the same screen for too long!

    Let's Talk Linux Port Stuff​

    I guess the point of this section is to ask you guys if you're ok with updates to the VB version being slowed down, so I can focus more on the port? I'd also like to address a common question I get asked about it being open-source. Right now, I'm planning on it being closed-source for now. However, I am planning on making it open-source when I feel like the time is right. Please be patient! So, let's get back to the original question... are you guy's ok if I shift primary focus to the port?


    Wait, that's not everything! If you're interested in everything that's changed... please take a look at the changelog below:
    Version 26.0 - Changelog

    [Welcome Screen]
    • 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.
    [Device Information]
    • Fixed chipset information not displaying for some tablets due to a renamed string in getprop.
    [Theme Selector]
    • Moved the Theme Selector to the Welcome Screen.
    [Custom Launcher]
    • 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+.
    [Modify System Settings]
    • 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.
    [Lockscreen Management]
    • Improved the warning regarding the Pattern security type.
    [Hybrid Apps]
    • Updated Disney+, and Netflix to the latest versions.
    [Manage Amazon Apps]
    • When restoring from a debloat list, it now displays the proper header and message.

    Ready to download V26.0? Head on over to the Download's section of the OP. By the way, because of some directory changes to the bin folder... the update will not show up in the Updater. It must be installed via the Installer or extracted from the Portable release.

    Ok, my favorite part about of these release posts... sharing appreciation for you awesome folks! I just wanted to say I'm so blessed to be a part of the wonderful community over here on XDA. You guys are incredible people and in fact... this is perhaps the one place I've been on that I don't see negativity or people bullying one another. You guys are just AMAZING and I wanted to let you know that I appreciate everyone's support! Furthermore, you guys are what keep this project going, and it wouldn't be where it is today without you guys! So please pat yourself on the back - you deserve it!

    Also, I'd like to place the limelight on my good friends @blaacksheep, and of course @Falcon342. I just can't express how much I appreciate all you've done for this thread! I haven't had the time to get on here because of work and when I come on the forum I see you guys helping out and answering questions. I really do appreciate the time and effort you two have put into being so freaking helpful! However, I've got to be honest, I'm extremely sad because I feel like I'm not doing enough. I'm sure you guys would like a little help (I'm gonna try harder to be more active on here when I can to hopefully help you guys out). Anyway, thank you guys again!! I really do appreciate it!!!!

    Also, don't think I forgot about you donators! I just want to say I'm so honored that you'd donate your hard-earned cash. Sometimes I feel like I don't deserve it. Guys and gals, THANK YOU so much for donating! I really do appreciate every penny! :D

    This year has flown by and Christmas is right around the corner, so I just wanted to say MERRY CHRISTMAS and I hope you all had a remarkable 2021! Let's hope 2022 is an even better year! 🙏

    Well, that's all I've got for now! Have a good one, guys, and until next time... Peace! ✌️