[WINDOWS][TOOL]Fire Toolbox V30.2

Search This thread
By:
Advanced…
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
Eiion said:
The play store version was never installed. As mentioned before, I was always using the version you can install with toolbox. It's just that that version was outdated (see Datastreams comment about that above).
Click to expand...
Click to collapse
Understand.

So regardless of source, you have updated Netflix so that it is now recognized as an updated Amazon app. That's great.

Still, as a precaution, check Netflix in Play Store to ensure that if there is a listing for Netflix app it is set so auto-update is disabled; sometimes Play Store "polls" your system and finds an app downloaded/updated from AppStore and recognizes it as a Play Store app and tries to update, causing "update clash" . Precautionary chek , not a big deal.
 
Last edited:
S

smartass1379

Member
Jan 31, 2009
16
6
I was running 7.3.2.6 but they just released 7.3.2.7. Re-routing the home key still works and so does the play store but disabling Fire Launcher is still not possible. Let me know if there is anything else you want me to test out.
 
  • Like
Reactions: Jumbo100
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
Last edited:
B

BE4N

Member
Jan 23, 2023
6
7
Google Play is stuck at pending when installing any apps.

Fresh install with toolbox v30.3 on Amazon Fire 10 (2017). I tried clearing cache, rebooting but still the same issue. I waited at least 30 mins before signing into google play for the first time. I tried adding apps through the play.google.com website and still the same issue. I tried it with multiple apps including chrome The same google account on my Fire HD 8 7th Gen works fine.

Thank you in advance!
 
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
twinotter said:
Any suggestions on getting Find My Device or similar working on a Kindle Fire 8 (2020)?

Thanks!
Click to expand...
Click to collapse
Strangely, "Find My Device" service on Fire tablets is not enabled in all geographic regions. In my region, Find My Device is not available , but per Amazon Customer Service " we're working hard to make this feature available in the future " ... Thanks, Amazon ... Great marketing 🙄

Check with your local Amazon Customer Support for availability status.
 
Last edited:
Datastream33

Datastream33

Senior Member
Sep 17, 2017
2,458
2,154
BE4N said:
Google Play is stuck at pending when installing any apps.

Fresh install with toolbox v30.3 on Amazon Fire 10 (2017). I tried clearing cache, rebooting but still the same issue. I waited at least 30 mins before signing into google play for the first time. I tried adding apps through the play.google.com website and still the same issue. I tried it with multiple apps including chrome The same google account on my Fire HD 8 7th Gen works fine.

Thank you in advance!
Click to expand...
Click to collapse
Try force stopping and clearing the cache for the following apps:
  • Google Play Services
  • Google Play Framework
  • Google Play Store
  • Downloads
  • Download Manager
After clearing the cache and force stopping the above apps, the Play Store should start downloading the pending apps. Best of luck and let us know how it goes! :D
 
  • Like
Reactions: Jumbo100
B

BE4N

Member
Jan 23, 2023
6
7
Datastream33 said:
Try force stopping and clearing the cache for the following apps:
  • Google Play Services
  • Google Play Framework
  • Google Play Store
  • Downloads
  • Download Manager
After clearing the cache and force stopping the above apps, the Play Store should start downloading the pending apps. Best of luck and let us know how it goes! :D
Click to expand...
Click to collapse
Wow! Thank you so much for the quick reply.

Am I supposed to do this under Settings/Aoos & Games/Manage all Applications? If so when I do go Google Play Services I cannot Force Stop and Clear Cache doesn't seem to do anything.

I have Google Services Framework and not Google Play Framework. I cleared the cache there.

I don't see Downloads or Download Manager.

I tired stopping, clearing data and clearing caches for what I could and no change in my status. Please forgive me if I'm not understanding the instructions.

Now when I go to Google Play manage apps & device I get a sad satellite saying something went wrong.
 
  • Like
Reactions: Datastream33
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
BE4N said:
I don't see Downloads or Download Manager.
Click to expand...
Click to collapse
Download and Download Manager are FireOS "system" apps and are normally hidden. Try:

Setting>Apps & Notifications ... tap to expand "See all xxx apps" > App info ... turn on "Show System" button.

Download/Download Manager should now be listed (... long list !)

Proceed as previously directed by @Datastream33 .
 
Last edited:
  • Like
Reactions: Datastream33
blizzardblaise

blizzardblaise

Member
Mar 14, 2022
32
8
New York
My Fire HD 10 just updated to OS 7.3.2.7

What changes were made with this? The only thing I notice so far is that some books which I purchased that previously didn't show covers in the carousel now show up.

Edit: Now the books are showing up as blank blue covers again. UGH!
 
Last edited:
B

BE4N

Member
Jan 23, 2023
6
7
Jumbo100 said:
Download and Download Manager are FireOS "system" apps and are normally hidden. Try:

Setting>Apps & Notifications ... tap to expand "See all xxx apps" > App info ... turn on "Show System" button.

Download/Download Manager should now be listed (... long list !)

Proceed as previously directed by @Datastream33 .
Click to expand...
Click to collapse
Thank you. I'm still getting stuck at pending.

The steps are a little bit different on my Fire OS 5.7.0.0. I did Settings>Apps & Games>Manage All Applications and scrolled over to the All tab.

Downloads wasn't running but I cleared the cache
Download manager was running and I stopped. Clearing cache didn't change the cache size of 36KB
Google Play Services was not running but I was able to clear the cache to 12KB
I don't have Google Play Framework but I had Google Services Framework. Am I missing something or is Google Services Framework the correct one? It wasn't running but I cleared the cache.
Google Play Store was stopped and the 1.5MB cache cleared down to 12KB
 
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
BE4N said:
Thank you. I'm still getting stuck at pending.

The steps are a little bit different on my Fire OS 5.7.0.0. I did Settings>Apps & Games>Manage All Applications and scrolled over to the All tab.

Downloads wasn't running but I cleared the cache
Download manager was running and I stopped. Clearing cache didn't change the cache size of 36KB
Google Play Services was not running but I was able to clear the cache to 12KB
I don't have Google Play Framework but I had Google Services Framework. Am I missing something or is Google Services Framework the correct one? It wasn't running but I cleared the cache.
Google Play Store was stopped and the 1.5MB cache cleared down to 12KB
Click to expand...
Click to collapse
Sorry, forgot that older HD10s are running FireOS 5 (before my time) , but same process, just different UI.

Google Services Framework is the new name of current Google Play Framework; indicates that Google Play infrastructure has auto-updated to current versions. So far so good.

@Datastream33's process for clearing cache data is standard SOP, but if that didn't work , try the next troubleshooting steps.

Try signing-out of your Google account and signing-in again BUT you must sign-out it fom another Android device or from a web browser on your computer.

From Google, open your account avatar (upper right corner), then

open "Manage your Goggle Account" > open Security tab > scroll down to "Your Devices" and tap open "Manage all devices" > select your Fire tablet and expand > select Sign Out.

May have to repeat if there are multiple entries for you our Fire tablet.

Now sign-in on your Fire tablet and restart app downloads.

Hope this works ... more troubleshooting steps available if necessary.
 
Last edited:
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
blizzardblaise said:
My Fire HD 10 just updated to OS 7.3.2.7

What changes were made with this? The only thing I notice so far is that some books which I purchased that previously didn't show covers in the carousel now show up.

Edit: Now the books are showing up as blank blue covers again. UGH!
Click to expand...
Click to collapse
If you haven't disabled OTA Updates, Amazon will continuosly "push" updates on FireOS and all Amazon apps .. for better or worse. Kindle most recently updated ca. 20 January.

Problems with bookcover art are Kindle related and have been ongoing for years, and have become worse with last year's changes to Kindle Store infrastructure. Lots of Kindle related forums on the web discussing workarounds, most of them pretty kludgey. Kindle app updates never seem to address the problems.

Personally, I've given up worrying about it. 🙃

+ Edit +
If you're using the Google version of Kindle app, switching to "native" Amazon app may be of some help.
 
Last edited:
blizzardblaise

blizzardblaise

Member
Mar 14, 2022
32
8
New York
Things haven't been working good for my Kindle Fire 10 so I factory reset everything. OTA has been on but I welcome the new update. It's showing the covers now that I've factory reset and is working more smoothly. I was also able to use Fire Toolbox without a problem.
 
  • Like
Reactions: Datastream33 and Jumbo100
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
blizzardblaise said:
Things haven't been working good for my Kindle Fire 10 so I factory reset everything. OTA has been on but I welcome the new update. It's showing the covers now that I've factory reset and is working more smoothly. I was also able to use Fire Toolbox without a problem.
Click to expand...
Click to collapse
Glad Kindle's working again. Factory resets can do wonders ... early Spring Cleaning !
 
Last edited:
  • Like
Reactions: Datastream33
B

BE4N

Member
Jan 23, 2023
6
7
Jumbo100 said:
Sorry, forgot that older HD10s are running FireOS 5 (before my time) , but same process, just different UI.

Google Services Framework is the new name of current Google Play Framework; indicates that Google Play infrastructure has auto-updated to current versions. So far so good.

@Datastream33's process for clearing cache data is standard SOP, but if that didn't work , try the next troubleshooting steps.

Try signing-out of your Google account and signing-in again BUT you must sign-out it fom another Android device or from a web browser on your computer.

From Google, open your account avatar (upper right corner), then

open "Manage your Goggle Account" > open Security tab > scroll down to "Your Devices" and tap open "Manage all devices" > select your Fire tablet and expand > select Sign Out.

May have to repeat if there are multiple entries for you our Fire tablet.

Now sign-in on your Fire tablet and restart app downloads.

Hope this works ... more troubleshooting steps available if necessary.
Click to expand...
Click to collapse

Thank you again for taking the time to help me troubleshoot my issues.

I followed the steps more than once and no luck. I even cleared the cache before logging in again one of those times. It actually kept me logged into the play store until I cleared the cache. I also signed out of all android sessions that I didn't recognize just in case.
 
  • Like
Reactions: Datastream33
C

cfw_xda

New member
Jul 15, 2013
1
1
Hi Friends.

I have a UK Fire HD 10 Plus 11th Gen Build 0021274104964 which I think might be quite an old firmware 7.3.2.2 (?) and Fire Toolbox install quite a time ago.

With other Fire devices I used to periodically wipe, OTA update and then install Fire Toolbox, so that the tablet had any amazon bug fixes or new features etc

Is this not a good idea anymore? Should I just do a Fire Toolbox update?

Thanks
John
 
  • Like
Reactions: blaacksheep
blaacksheep

blaacksheep

Senior Member
Jun 20, 2020
1,638
1,031
Buffalo
cfw_xda said:
Hi Friends.

I have a UK Fire HD 10 Plus 11th Gen Build 0021274104964 which I think might be quite an old firmware 7.3.2.2 (?) and Fire Toolbox install quite a time ago.

With other Fire devices I used to periodically wipe, OTA update and then install Fire Toolbox, so that the tablet had any amazon bug fixes or new features etc

Is this not a good idea anymore? Should I just do a Fire Toolbox update?

Thanks
John
Click to expand...
Click to collapse

Hi, and welcome to XDA (or welcome back, as the case may be)!

I think that the 2021 HD 10+ tablets came with v7.3.2.2 or later. I don't think they came with any earlier versions. That said, I don't think there have been any major improvements since then, but there was something I don't use that was added since.

Unless you are looking for a specific feature that was added, it's generally not a good idea to allow any firmware updates to your tablet since any update has the potential to remove any Toolbox modifications and to lock you out from restoring them using Toolbox again. Case in point, v7.3.2.2 caused much unhappiness when it took away the ability to remove the stock Amazon launcher and forced some major workarounds just to use another launcher.

It's also generally best not to do a factory reset unless there is something seriously messed up with your OS because of the danger of getting an unwanted firmware update. It's like they say: "If it ain't broke, don't fix it"!

Periodically, Toolbox gets some major upgrades that add new features to it, so using the most up-to-date version of Toolbox is usually best, but there's no need to update your tablet's Toolbox modifications if they still work fine. Many of the Toolbox updates only change the sources or versions of the software that gets installed. Once installed, software like Automate can be updated through Google's Playstore, and Playstore itself will auto-update. You just don't want Google to auto-update native Amazon apps because installing Playstore versions of native apps can cause version clash and cause the Amazon apps to fail. Many native apps can be updated through Amazon's appstore or through the links in my signature.
 
  • Like
Reactions: cfw_xda and Jumbo100
J

Jumbo100

Senior Member
Jul 21, 2022
470
361
BE4N said:
Thank you again for taking the time to help me troubleshoot my issues.

I followed the steps more than once and no luck. I even cleared the cache before logging in again one of those times. It actually kept me logged into the play store until I cleared the cache. I also signed out of all android sessions that I didn't recognize just in case.
Click to expand...
Click to collapse
Sorry you're having so many problems getting Google Play apps installed ... it can be most frustrating and time consuming.

The "pending downloads" problem has plauged Android users for years ... it's just not Fire tablets, but even "flagship" Android devices. The Google/Android support web pages have thousands of posts complaining. It's a common situation that Google can't seem to easily address after all these years.

So far, you've applied "fixes" for the most common issues of corrupt data caches and account authentications. In most cases that solves the problem. Any further troubleshooting is more obscure and has rapidly diminishing returns.

In end, Google usually gives up and just recommends a factory reset. Some fix ☹️

If you want to continue troubleshooting, ping us and we can carry on.
 
Last edited:
  • Like
Reactions: Datastream33
You must log in or register to reply here.

Similar threads

sd_shadow
[Root] Amazon Fire HD 8 & 10 (5th Gen 2015)
Replies
209
Views
123K
R
ryny24
nyln
Amazon Fire HD 8" & 10" - remove firelauncher (no root)
Replies
8
Views
58K
P
Provided
DragonFire1024
[ROOT] Install a full Linux distribution on Amazon HD 10?
Replies
17
Views
73K
S
Samperk1.0
D
Amazon Fire HD 10 9th gen (2019) -- Fire OS 7.3.1.6 root possible?
Replies
29
Views
43K
MrZaku086
MrZaku086
M
[Tool][Mac] Google Installer and Amazon Killer
Replies
17
Views
42K
pastorbennett
pastorbennett

Top Liked Posts

24 Hours 30 Days All time
  • 2
    S
    slcdroidpunk
    blaacksheep said:
    Getting Automate to launch another launcher (other than Fire's launcher) is a 2 part process. The first part is to replace the Home button with one of our making that isn't locked into Fire Launcher. The second part is setting up Automate to read that button press and direct it towards our preferred launcher. If you don't have both parts, it will fail.

    The script in Custom Navbar Key does the first part. That's why if it fails to work as expected you have to run an ADB command to get your home key back. The second part is an interactive portion that must be followed exactly to give all required permissions to Automate.

    For me, it worked the first time, but then I had been playing around with those aspects already when Datastream33 added that method. I assure you it can work, and work well enough that it doesn't detract from the user experience. You just have to start fresh and follow ALL the on-screen instructions. :)
    Click to expand...
    Click to collapse
    Thanks @blaacksheep , I probably didnt give the whole story. I installed the TB way back and I never got rid of the home key because I'm on 7.3.3.whaterver. ( Just found your post on using ReThinkDNS instead of DNS666, which has never worked for me - so thanks for that too!) For the home key, i was using the method that used the app "one button navigation" . However, I was tired of how it blocked the bottom of the screen and didn't rotate properly, so I came back to this thread to see if there was anything new and I stumbled over the Automate script posted by @Datastream33 and your comments about it. Seemed easy enough. ( I did NOT try to re-run FTB because I don't run windows day-to-day and so doing things on the tablet or via ADB is preferred) I got rid of "one button navigation" and installed Automate ( and got all the permissions right after a second try ) and then imported the "Launcher Invoker[3]" script. In it's stock form, it did nothing and I got that error mentioned above, which seemed to indicate that it didn't know what my launcher was ( Nova7 ). From there i tried changing the media key, and then got even more brave and replaced the step that set the launcher variable with a new one that hard coded it as "com.teslacoilsw.launcher". that removed the error in the log, but the flow still failed to do anything. As proof Automate is setup correctly, I was able to enable the flow posted in the community "amazon fire tablet - Easy Home Launcher" and it works - but there is a solid 5 second delay before it swaps to Nova from Fire launcher which didn't work for me. It seemed @Datastream33 's script was better, but for some reason it isn't working.

    i wasn't sure if you were implying something else had to happen for the Automate script to work - but restoring the home key couldn't be it, because i never got rid of it in the first place.

    I guess I just need to suck it up and install the newest TB and try using that.
    View
    2
    blaacksheep
    blaacksheep
    Yes, you need to run the Custom Launcher tool in TB to replace the home button on the tablet with a newly created button thats mapped to the Automate script. After that. it should work properly if you've given Automate the required permissions.

    BTW, if you don't run Windows regularly, perhaps you're running Linux? If so, a beta of FTB written for Linux is on the way! :D I don't know how soon, but it seems to be very close to happening. There's a link in the second post of this thread to the webpage that shows the progress of the project. But, for the time being, there's always VM's and dual-boot to run Toolbox in. (y)
    View
    1
    blaacksheep
    blaacksheep
    slcdroidpunk said:
    Hate to even ask...but i installed the script and granted permissions, but automate won't run nova launcher. The flow from the community worked (easy launcher), but was super slow, so I was trying to get your flow working. In the logs I see: no activity found to handle intent...so it seems it doesn't know what launcher I'm using?

    Oh, and I tried @blaacksheep 's thing of using media record instead of play button to no avail.

    I got bold and tried editing the flow to just set the launcher variable to
    "com.teslacoilsw.launcher" ... But that didn't seems to do it either :(

    Thanks in advance
    Click to expand...
    Click to collapse

    Getting Automate to launch another launcher (other than Fire's launcher) is a 2 part process. The first part is to replace the Home button with one of our making that isn't locked into Fire Launcher. The second part is setting up Automate to read that button press and direct it towards our preferred launcher. If you don't have both parts, it will fail.

    The script in Custom Navbar Key does the first part. That's why if it fails to work as expected you have to run an ADB command to get your home key back. The second part is an interactive portion that must be followed exactly to give all required permissions to Automate.

    For me, it worked the first time, but then I had been playing around with those aspects already when Datastream33 added that method. I assure you it can work, and work well enough that it doesn't detract from the user experience. You just have to start fresh and follow ALL the on-screen instructions. :)
    View
    1
    S
    slcdroidpunk
    blaacksheep said:
    Yes, you need to run the Custom Launcher tool in TB to replace the home button on the tablet with a newly created button thats mapped to the Automate script. After that. it should work properly if you've given Automate the required permissions.

    BTW, if you don't run Windows regularly, perhaps you're running Linux? If so, a beta of FTB written for Linux is on the way! :D I don't know how soon, but it seems to be very close to happening. There's a link in the second post of this thread to the webpage that shows the progress of the project. But, for the time being, there's always VM's and dual-boot to run Toolbox in. (y)
    Click to expand...
    Click to collapse

    Re-ran TB. It isn't that hard, I'm just stubborn. I DO run linux - i gave up watching the linux thread a while ago, but maybe i'll check it out again.

    thanks for your help - it wasn't super smooth but after about 10 tries of installing/rebooting the tablet I got the custom navbar working. And it works great. ( I think I struggled because i already had Automate and the script had issues, kept getting stuck in a loop where it would open Nova and show the options ). Anyway, all's well that ends well - can't thank you and @Datastream33 enough!!!
    View
  • 3
    G
    gomus
    If this has been addressed, I apologize, but I did a cursory search with no results. I've noticed that two of my devices - Fire HD 8 Plus 12th gen (8.3.1.3) and a Fire 7 12th gen (8.3.1.4) - both wil not run Youtube TV. Youtube is fine but the Youtube TV fails with the dreaded "Youtube TV won't run without Google Play services, which are missing from your device."

    Google Play and all of the other apps work just fine. So far, I've only noticed Youtube TV suffering from this. My 10th gen tablets are all running different versions of 7.3.X.X and Youtube TV works fine on those. It appears that Amazon OS8 is the culprit. I'll try running that in a browser but figured I'd toss this out in hopes there was a fix for it.

    Thanks all for all that you do.
    View
    2
    CFKod
    CFKod
    Warning to those who have SD card formatted as internal storage (instead of portable storage)
    Move playstore and its dependencies back to internal storage, else you lose it should your SD card become corrupt. Also worthwhile making sure your default launcher is also on Internal


    You can see which apps are on the SD card by going to
    Settings > Storage > SD Card and selecting “Apps.”
    Select the following apps one by one
    1. play store
    2. play services
    3. Google account manager
    4. Google services framework
    Select “Change,” and select “Internal Storage.”


    WARNING : The above is confirmed correct for FireOS 8.3.1.3
    However, older versions may not be able to differentiate your SD card from internal storage, once you go down the adoptable route.
    View
    2
    CFKod
    CFKod
    blaacksheep said:
    I just went through this the other day because my 512GB SD card set as adoptable storage was suddenly corrupted. I pulled it and ran a couple utilities on my Linux computer but was not able to repair it. I ended up formatting and testing it again. It passed, so I threw it back in and adopted it again. It took me most of a day to refill the data and reload the software.
    Click to expand...
    Click to collapse
    The exact headache I had. One day everything disappeared, my initial worry that it some how updated was proven false obviously, tried the SD In Linux and not recognised.. Tried on my phone.. Nothing.. Only option given on the amazon tablet was to format again.

    So I chose internal storage again.. This time making sure my important apps are on internal hehe

    (perhaps if would have shown on gparted, however android was the safest route, but I did lose all the apps that we had spent ages setting up. Doh!)
    View
    2
    J
    Jumbo100
    gomus said:
    If this has been addressed, I apologize, but I did a cursory search with no results. I've noticed that two of my devices - Fire HD 8 Plus 12th gen (8.3.1.3) and a Fire 7 12th gen (8.3.1.4) - both wil not run Youtube TV. Youtube is fine but the Youtube TV fails with the dreaded "Youtube TV won't run without Google Play services, which are missing from your device."
    Click to expand...
    Click to collapse
    Ongoing incompatibility issues with YouTube TV and FireOS 8 on 12th Gen (2022) Fire tablets. No reported solution yet.

    Only immediate workaround is accessing YouTube TV from a web browser
    @ https://tv.youtube.com/welcome/.

    Possible solution would be for a clever dev to code a PWA (Progressive Web App) ie "hybrid app" for YtTV .

    A similar situation for YouTube Kids was partially resolved by installing a specific older YtK version.
    View
    2
    J
    Jumbo100
    A 10.1" inch Linux tablet @ Fire HD10 price points !?

    Linux Tablet PineTab2 Estimated To Launch In April From $159

    Linux Tablet PineTab2 Estimated To Launch In...
    tabletmonkeys.com tabletmonkeys.com

    View
  • 354
    Datastream33
    Datastream33


    Fire Toolbox V30.2
    All-In-One Toolbox for Fire Tablets!
    ​



    ​

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

    Compatibility.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.
    • 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.
    Click to expand...
    Click to collapse

    Device Name:
    Generation:​
    Amazon Fire 7 (2022)
    12​
    Amazon Fire 10/10+ (2021)
    11​
    Amazon Fire 8/8+ (2020)
    10​
    Amazon Fire 10 (2019)
    9​
    Amazon Fire 7 (2019)
    9​
    Amazon Fire 8 (2018)
    8​
    Amazon Fire 10 (2017)
    7​
    Amazon Fire 8 (2017)
    7​
    Amazon Fire 7 (2017)
    7​
    Amazon Fire HD8 (2016)
    6​
    Amazon Fire HD10 (2015)
    5​
    Amazon Fire HD8 (2015)
    5​
    Amazon Fire HD7 (2015)
    5​
    Amazon Fire HD7 (2014)
    4​
    Amazon Fire HD6 (2014)
    4​

    In this forum, you may hear the word "generation" being used when talking about Fire Tablets. Just know that "generation" effectively means the same as "what year was the tablet manufactured?". This may seem confusing and as a result a reference table has been provided for you below.​

    screenshot-2020-12-15-174539-jpg.5158661
    ​


    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 - 2022) 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!​
    ​

    ToolsSubtools.png


    • ADB Shell - Spawn a Unix shell that can be used to communicate with the device and execute commands.​
    • Custom Launcher - Replace Fire Launcher with a custom launcher.​
    • Enable Widget Support - Enable widgets on supported launchers.​
    • Custom Sounds - Set custom sounds for notifications, lock/unlock events, low battery, and more!​
    • Density Modifier - Change the value of pixels per inch to either decrease or increase resolution.​
    ​
    • Restore Default Density - Restore the factory default density.​
    • Google Assistant - Replace Amazon Alexa with Google Assistant.​
    • Google Services - Install Google Services and the Play Store.​
    • Google Services (Manage)​
    • Add/Remove Google Accounts​
    • Clear Data/Cache for Play Services​
    • Uninstall Play Services​
    • Hybrid Apps - Sideload Amazon Appstore apps without having the Appstore enabled.​
    • Keyboard and Input - Manage other input methods and install custom keyboards.​
    • Lockscreen Wallpaper - Replace the lockscreen's wallpaper with a custom one. ​
    • Manage Amazon Apps - Manage the Amazon apps installed on your tablet.​
    • Hide/disable Amazon Apps - Hide and Disable Amazon apps through presets or manually select apps.​
    • Restore Amazon Apps - Completely restore every Amazon app or manually select apps to restore.​
    • Modify System Settings - ​
    • Power Options - Reboot, shutdown, reboot into recovery, or reboot the tablet into bootloader mode.​
    • Parental Controls Hide - Installs a service that auto-dismisses messages from Parental Controls.​
    • Privacy Controls - Disable telemetry collection of app usage data, interest based ads, etc. ​
    • Push and Pull​
    • Push - Transfer files from your computer to your tablet.​
    • Pull - Retrieve files from your tablet and transfer them to your computer.​
    • Remove Lockscreen Ads - Remove ads from the lockscreen.​
    • Screen Capturing - Record the device's screen, or capture a screenshot.​
    • Sideload Apps - Install APKs from sources outside of the Amazon Appstore.​
    • System Backup ​
    • Backup - Create a backup of the current system configuration.​
    • Restore - Restore system configuration from a previously created backup.​
    • User Management (8th gen and above)​
    • Create a User - Create a new user.​
    • Delete a User - Delete a toolbox created user.​
    • Switch Users - Switch the current user to a different Toolbox created user.​
    • YouTube Clients - Install third-party Youtube clients. ​
    ​

    Downloads.png


    Toolbox:
    Version​
    Installer (.exe)​
    Portable (.zip)​
    Update Post​
    VirusTotal​
    V30.2​
    Post​
    Link​


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

    Version​
    Installer (.exe)​
    Portable (.zip)​
    Update Post​
    VirusTotal​
    V30.1​
    Post​
    Link​
    V30.0​
    Post​
    Link​
    V29.0​
    Post​
    Link​
    V28.9​
    Download​
    Post​
    Link​
    V27.0​
    Post​
    Link​
    V26.1​
    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​
    ​
    Donate.png

    ​
    If you like my work and would like to support me feel free to Donate. Thank you!
    View
    69
    Datastream33
    Datastream33
    FAQ.png

    How can I run the Toolbox on Linux?​
    ​
    The Toolbox is currently being developed for Linux systems in the Python programming language. If you'd like to see the progress of the port, you can do so at this link.​
    ​
    Please be patient with me as the Linux port is being developed in my spare time and may take some time to complete. However, as the port progresses some builds will be released to those who'd like to help test alpha builds. More information on this later down the line. ​
    ​
    However, at the moment, the best way to run the Toolbox on Linux is to use VMWare and emulate Windows.​
    Click to expand...
    Click to collapse

    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. ​
    Click to expand...
    Click to collapse

    ​
    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.​
    Click to expand...
    Click to collapse

    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". ​
    Click to expand...
    Click to collapse

    ​
    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.​
    Click to expand...
    Click to collapse

    ​
    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​
    Click to expand...
    Click to collapse
    View
    32
    Datastream33
    Datastream33
    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
    View
    28
    blaacksheep
    blaacksheep
    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)
    View
    21
    Datastream33
    Datastream33
    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.
    Click to expand...
    Click to collapse

    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! ✌️
    View

New posts