[WINDOWS][TOOL]Fire Toolbox V30.2

[Datastream33]

Thank you soo much for your quick reply!

I'll attach the pic of the keyboard (it's the official Amazon bluetooth keyboard for the Fire HD 10+)

If Automate could use those buttons as it is, it'll be just super.
If not, then might I request you to configure Shift + those dedicated buttons?

View attachment 5779193

Sweet, so it has a dedicated home button!

This could work with Automate. OK, I've modified the Launcher Invoker flo and attached it to this post (you'll need to extract it from the .zip file) and import it into Automate. (If you need help importing let us know)

Really hope this works! Please let us know how it goes and best of luck!

 

[redhub]

Hi and thanks for the great work on the toolbox!

I just used the toolbox on my new Fire HD10 Plus, firmware 7.3.2.4. The toolbox version 30.1 effectively blocks the firmware upgrade to 7.3.2.6. However, the same toolbox blocks the language download to the Librera app, which I use to read pdf files on my tablet. BTW, great app!

I'm concerned that disabling the OTA blocker in the toolbox will result in a firmware upgrade to version 7.3.2.6. Is there a safe way to download the language to the Librera app?
I would appreciate your support.

 

[blaacksheep]

Hi and thanks for the great work on the toolbox!

I just used the toolbox on my new Fire HD10 Plus, firmware 7.3.2.4. The toolbox version 30.1 effectively blocks the firmware upgrade to 7.3.2.6. However, the same toolbox blocks the language download to the Librera app, which I use to read pdf files on my tablet. BTW, great app!

I'm concerned that disabling the OTA blocker in the toolbox will result in a firmware upgrade to version 7.3.2.6. Is there a safe way to download the language to the Librera app?
I would appreciate your support.

Hi, and welcome to XDA!

You can use the RethinkDNS method of blocking the updates. A link to that method is located in my signature. It just blocks the apps responsible for updates from internet access so they can't update. In order to undo the method in Toolbox, I'm not certain if there's an option in Toolbox to undo it. If it works the way I think it does, you can go into WiFi settings and tap on the gear to the right of your network name, and look down a few lines until you see "Metered". Tap that and change it to either of the other options. Let me know how you do.

 

[redhub]

Hi, and welcome to XDA!

You can use the RethinkDNS method of blocking the updates. A link to that method is located in my signature. It just blocks the apps responsible for updates from internet access so they can't update. In order to undo the method in Toolbox, I'm not certain if there's an option in Toolbox to undo it. If it works the way I think it does, you can go into WiFi settings and tap on the gear to the right of your network name, and look down a few lines until you see "Metered". Tap that and change it to either of the other options. Let me know how you do.

Thank you for your quick response.
Temporarily disabling the "Metered" option for my wifi network took care of the issue and the language file downloaded correctly.

 

[blaacksheep]

Thank you for your quick response.
Temporarily disabling the "Metered" option for my wifi network took care of the issue and the language file downloaded correctly.

Just make sure you check the System Updates section of your Settings to see if there's an update waiting to install before you shut down/reboot. (Don't click "Check for updates", just look at the bottom where it says the current status.) If there is one waiting to be installed, report back here and we'll tell you how to get rid of it. Oh, and make sure you put it back to metered so an update doesn't slip through.

 

[Abyssul]

I have ben able to use this awesome tool to add in google services and strip out the amazon bloaware but unfortunately the custom launcher is not working for me. The device (fire 8 plus) is already on 8.3.1.3

When I install the nova launcher both Nova launcher and automate install and permissions are granted.

Then I see a message saying "the launcher invoker flow will now be imported into automate, please unlock your device (please do not interact with the touch screen during this process) and click OK to continue.

I click ok only to be greeted with an error about "Failed to read flow" on the tablet with the only option being cancel (import is greyed out). I have tried importing an older version of the launcher from this forum but that also did not work (the nova launcher opened once and then defaulted back to the fire home pages screen)

Could anyone who has seen this beofre please point me in the right direction as I think I am having a bit of a PEBKAC moment here.

I have a Amazon Fire HD 8 12th gen (2022) running 8.3.1.3 and running into this exact issue. I get the "failed to read flow" error on the tablet when settings up the custom launcher from the toolbox. I imported the flow directly from the toolbox manually. However, the launcher only opens once and then defaults back to the Fire launcher.

Home button press starts at 12-07 22:05:56.913. There are no other log entries on subsequent home button presses that open the Fire launcher.

12-07 22:05:45.400 I [email protected]: Flow beginning
12-07 22:05:45.412 I [email protected]: System setting get
12-07 22:05:45.424 I [email protected]: Fork
12-07 22:05:45.455 I [email protected]: Broadcast receive
12-07 22:05:45.461 I [email protected]: Fork
12-07 22:05:45.486 I [email protected]: Media button
12-07 22:05:45.517 I [email protected]: App in foreground?
12-07 22:05:56.913 I [email protected]: App start
12-07 22:05:57.012 I [email protected]: Fiber stop
12-07 22:05:57.046 I [email protected]: Fork
12-07 22:05:57.154 I [email protected]: Media button
12-07 22:05:57.202 I [email protected]: App in foreground?
12-07 22:05:57.249 I [email protected]: Stopped at end

 

[blaacksheep]

I have a Amazon Fire HD 8 12th gen (2022) running 8.3.1.3 and running into this exact issue. I get the "failed to read flow" error on the tablet when settings up the custom launcher from the toolbox. I imported the flow directly from the toolbox manually. However, the launcher only opens once and then defaults back to the Fire launcher.

Home button press starts at 12-07 22:05:56.913. There are no other log entries on subsequent home button presses that open the Fire launcher.

Make sure that Automate is set to start on system startup, and that the flow "Launcher Invoker" is started. You said that all permissions were granted, so that should be enough.

 

[Abyssul]

Make sure that Automate is set to start on system startup, and that the flow "Launcher Invoker" is started. You said that all permissions were granted, so that should be enough.

It is set to start on system startup and the flow is started. That is how I got my flow logs

 

[blaacksheep]

It is set to start on system startup and the flow is started. That is how I got my flow logs

Okay, just checking. I'm not sure about FireOS 8. A couple of users with 2022 tablets seem to have that problem. You can also let Google Play update Automate. Maybe it's a version thing. I'm just guessing here.

 

[mohnish92]

Sweet, so it has a dedicated home button!

This could work with Automate. OK, I've modified the Launcher Invoker flo and attached it to this post (you'll need to extract it from the .zip file) and import it into Automate. (If you need help importing let us know)

Really hope this works! Please let us know how it goes and best of luck!

Thank you for your reply!
I extracted the zip, placed it in my downloads folder, and then imported to Automate.
Then, I Stopped the original "Launcher Invoker" Flow and Started the "Launcher Invoker [1]" Flow.

However, pressing the Home button on the keyboard still lands me to the Fire Launcher homescreen
Please let me know if I have to send any screenshot etc of the Automate page, or any log file to help with this process?
(I really appreciate your willingness to share such customization!)

 

[ghoster76]

Thank you for your reply!
I extracted the zip, placed it in my downloads folder, and then imported to Automate.
Then, I Stopped the original "Launcher Invoker" Flow and Started the "Launcher Invoker [1]" Flow.

However, pressing the Home button on the keyboard still lands me to the Fire Launcher homescreen
Please let me know if I have to send any screenshot etc of the Automate page, or any log file to help with this process?
(I really appreciate your willingness to share such customization!)

Screenshot your current navbar, this method required customized navbar with a custom layout, if you stll see original navbar layout with 3 button placed nearly each other, then it doesn't work.

 

[mohnish92]

Screenshot your current navbar, this method required customized navbar with a custom layout, if you stll see original navbar layout with 3 button placed nearly each other, then it doesn't work.

The touch screen home button works fine, and it lands me to the Nova launcher home screen.

I'm facing an issue on the Fire HD Bluetooth Keyboard -- home screen physical button.
That lands me to the fire launcher home screen even with the modified invoker flow posted by datastream33 above.

 

[SurroundSound]

I undone rethinkdns method of blocking OTA and Alexa is working again. I know I'm vulnerable to updates now but I find Alexa very useful.

 

[KnightPhoenix]

Okay, just checking. I'm not sure about FireOS 8. A couple of users with 2022 tablets seem to have that problem. You can also let Google Play update Automate. Maybe it's a version thing. I'm just guessing here.

It is set to start on system startup and the flow is started. That is how I got my flow logs

I have just found a plugin in the automate community called "Amazon Fire Tablet - Easy Home Launcher Changer". It seems to work but every now and again you see a flash of the old home pages when you click the home button (not every time and it disappears in half a second). Will try to go through and map it out later and see if I can work out why this works and the launcher is not.

Only other issue with the plugin is it asking you which launcher you want to use on load (but sure that could easily be hard coded).

Thanks for all the help and good advice.

 

[Liara]

I have a Fire HD 10 from 2019. I want to use Toolbox on it for the first time. I wanted to ask if I'm right in thinking it would be best to reset the tablet beforehand.

 

[Datastream33]

I have a Fire HD 10 from 2019. I want to use Toolbox on it for the first time. I wanted to ask if I'm right in thinking it would be best to reset the tablet beforehand.

You're without a doubt correct. Start with a clean slate.

 

[Datastream33]

I have just found a plugin in the automate community called "Amazon Fire Tablet - Easy Home Launcher Changer". It seems to work but every now and again you see a flash of the old home pages when you click the home button (not every time and it disappears in half a second). Will try to go through and map it out later and see if I can work out why this works and the launcher is not.

Only other issue with the plugin is it asking you which launcher you want to use on load (but sure that could easily be hard coded).

Thanks for all the help and good advice.

It looks like its using an atomic variable to hold the custom launcher variable. This means that once its set, it will remember the value even if the flow is stopped (e.g: set it and forget it). The flow however, is using the old method of waiting for the fire launcher to be in the foreground before launching the custom launcher.

This shouldn't work on newer tablets due to the 5 second delay issue. Apologizes if this information has been provided before, but which tablet and FireOS version do you have? Thanks!

 

[Datastream33]

I undone rethinkdns method of blocking OTA and Alexa is working again. I know I'm vulnerable to updates now but I find Alexa very useful.

Do what you gotta do my friend.

Have you tried the Restrict OTA method? It may allow you to keep Alexa while also blocking OTAs. But, may also prevent background downloads.

 

[Datastream33]

The touch screen home button works fine, and it lands me to the Nova launcher home screen.

I'm facing an issue on the Fire HD Bluetooth Keyboard -- home screen physical button.
That lands me to the fire launcher home screen even with the modified invoker flow posted by datastream33 above.

Dang, ok...

We can try another combo such as Ctrl+z or something like that. Do you have a preference?

 

[KnightPhoenix]

It looks like its using an atomic variable to hold the custom launcher variable. This means that once its set, it will remember the value even if the flow is stopped (e.g: set it and forget it). The flow however, is using the old method of waiting for the fire launcher to be in the foreground before launching the custom launcher.

This shouldn't work on newer tablets due to the 5 second delay issue. Apologizes if this information has been provided before, but which tablet and FireOS version do you have? Thanks!

In my case it is version 8.3.1.2. I forgot to unlink it from my account before shipping