[WINDOWS/LINUX][TOOL]Fire Toolbox V32.2

[chukkalasandeep]

Hi,

I am trying the tool for Fire HD Tablet 8, I am trying to install the custom launcher (Nova)but getting error as attached. I tried other options also but still same error. Can anyone help.

 

[Jumbo100]

For Google accounts, note change in behavior of Google Contacts with recent Google Play Services update:

This small Google Contacts change could have major consequences

Google is changing how Contacts stay synced on Android, as toggling sync off will now remove all contacts. Read on to know more!

www.androidauthority.com

New Google Contacts sync behavior is both a blessing and a curse

Google Contacts will wipe your saved contacts from a phone if you turn off sync

www.androidpolice.com

 

[Cpt.mactavish]

Firmware 7.3.2.7 9th gen firehd10
Firetoolbox 30.3
I use debloating script-keep amazon store(this way stock launcher Doesn't show tablet not registered msg)
Then block ota+updates from system modification settings
But after using for a few days without any issue..........somehow all amazon apps gets updated and comes back
Any way to prevent this?

 

[Cpt.mactavish]

@Datastream33 sir,plz help me

 

[chukkalasandeep]

Hi,

I am trying the tool for Fire HD Tablet 8, I am trying to install the custom launcher (Nova)but getting error as attached. I tried other options also but still same error. Can anyone help.View attachment 5921677

Hi @everyone, can one help on this?

 

[parataxis]

Hi @everyone, can one help on this?

Hi there, I would initially check your Kindle and make sure Developer Options are enabled and Debug Mode is turned on. Google if you need to.

Beyond that, perhaps check Java versioning (I don't think it's prepackaged) and uninstall/re-install the latest Java. If all else fails, you can always factory reset your Kindle (backup data first!), and start over to see if the problem is resolved. That "stack trace" tells me there is something corrupt on your Kindle since User Code is related to the tablet itself, and the debug trace unwinds towards the bottom to tell you the actualized error. I think if you press Volume Up and Power (it might be volume down) at same time during boot-up process it should bring up a fastboot shell and you can select factory defaults easily enough.

Good Luck!

 

[braveheartleo]

Hi @Datastream33

I've got another error report to make. After the update of FTB Linux to V1.1 I'm now getting this "failed to sideload the debugger due to an error" message upon program startup, and doesn't continue after that. The message window contains

From the error, it seems that the path got truncated somehow to V1.1/bin/AmazonDebugger/AmazonDebugger.apk instead of Fire Toolbox V1.1/bin/AmazonDebugger/AmazonDebugger.apk. That's the install directory and somehow the whitespaces in the file path got lost. I verified that the apk is present in the directory.

Can you take a look?

EDIT: This only happens when I connect 'douglas' to FTB Linux V1.1. There's no such error when 'onyx' is connected. My workaround for now is to transfer the apk and install it on the tablet.

 

[Datastream33]

Hi @Datastream33

I've got another error report to make. After the update of FTB Linux to V1.1 I'm now getting this "failed to sideload the debugger due to an error" message upon program startup, and doesn't continue after that. The message window contains
View attachment 5922423

From the error, it seems that the path got truncated somehow to V1.1/bin/AmazonDebugger/AmazonDebugger.apk instead of Fire Toolbox V1.1/bin/AmazonDebugger/AmazonDebugger.apk. That's the install directory and somehow the whitespaces in the file path got lost. I verified that the apk is present in the directory.

Can you take a look?

EDIT: This only happens when I connect 'douglas' to FTB Linux V1.1. There's no such error when 'onyx' is connected. My workaround for now is to transfer the apk and install it on the tablet.

Greetings!

Great catch my friend. The Toolbox originally wasn't going to support spaces in the root directory path (as you pointed out in the error message - the spaces weren't handled properly resulting in a broken path). However, @blaacksheep being the good guy that is, highly recommended that it should. Had to rewrite some tools but in the end the root directory now supports spaces. However, it seems I missed the path conversion for the debugger installation function. The issue has been fixed and an update has been released.

Yeah, douglas runs FireOS 5 which requires the debugger to be installed before the Toolbox can interact fully with the device. It allows us to hide packages, and perform some other interactions that wouldn't be possible without it. I'm starting to wonder if there's an equivalent for other FireOS versions that can be used to disable the protected packages on FireOS 7. Can't remember how we obtained the FireOS 5 one though.

I'd like to sincerely apologize for my late response. Glad to see you were able to find a workaround though!

Again, thank you so much for the report! By the way, how are things going with the port on your end? Is everything functional (besides the debugger failing to install)?

 

[Datastream33]

Hi @everyone, can one help on this?

Greetings!

May I ask which tablet was in use when the error occurred? Thank you in advanced!

 

[braveheartleo]

However, @blaacksheep being the good guy that is, highly recommended that it should. Had to rewrite some tools but in the end the root directory now supports spaces. However, it seems I missed the path conversion for the debugger installation function. The issue has been fixed and an update has been released.

That was quick! Thank you. What @blaacksheep has done is good programming practice and I'm glad for it. It's okay, we miss some things here and there but nothing that can't be quickfixed.

Yeah, douglas runs FireOS 5 which requires the debugger to be installed before the Toolbox can interact fully with the device. It allows us to hide packages, and perform some other interactions that wouldn't be possible without it. I'm starting to wonder if there's an equivalent for other FireOS versions that can be used to disable the protected packages on FireOS 7. Can't remember how we obtained the FireOS 5 one though.

Yeah, I was quite surprised that this AmazonDebugger upon close inspection is com.amazon.unifiedsharefacebook. There are some good things coming for FireOS V7, so let's just wait for it.

I'd like to sincerely apologize for my late response. Glad to see you were able to find a workaround though!

Again, thank you so much for the report! By the way, how are things going with the port on your end? Is everything functional (besides the debugger failing to install)?

It's okay no need for apologies. This is just standard error reporting for the improvement of the program and for the benefit of many.

So far I have not encountered any other issues in my use case, but maybe that's because I only make use of some of the toolbox functions. I'll report again should I encounter some.

Thank you once again for the great support.

 

[Datastream33]

@Datastream33 sir,plz help me

Firmware 7.3.2.7 9th gen firehd10
Firetoolbox 30.3
I use debloating script-keep amazon store(this way stock launcher Doesn't show tablet not registered msg)
Then block ota+updates from system modification settings
But after using for a few days without any issue..........somehow all amazon apps gets updated and comes back
Any way to prevent this?

Greetings!

I'd firstly like to apologize for the late reply.

Generally, in this situation, I'd recommend factory resetting the tablet and immediately blocking OTAs before DeviceSoftwareOTA even has a chance to download and install Amazon app updates. However, if you don't want to lose all your apps and data (can't blame you one bit) you could try unrestricting OTAs (I'd recommend unplugging your router beforehand), and restricting them again. That should clear any apps DeviceSoftwareOTA has downloaded and prevent them from coming back (I'd also recommend toggling off Automatic Updates as well if it isn't already toggled off). Debloat again and you should be good to go.

Please let us know how it goes, and best of luck!

 

[Datastream33]

That was quick! Thank you. What @blaacksheep has done is good programming practice and I'm glad for it. It's okay, we miss some things here and there but nothing that can't be quickfixed.

Yeah, I was quite surprised that this AmazonDebugger upon close inspection is com.amazon.unifiedsharefacebook. There are some good things coming for FireOS V7, so let's just wait for it.

It's okay no need for apologies. This is just standard error reporting for the improvement of the program and for the benefit of many.

So far I have not encountered any other issues in my use case, but maybe that's because I only make use of some of the toolbox functions. I'll report again should I encounter some.

Thank you once again for the great support.

No problem, like you said... any easy fix! But yeah, @blaacksheep is often my voice of reason. He's constantly helped me with oversights and prevented some pretty stupid ideas I've had in the past when it comes to the Toolbox.

As for the debugger, it does have a pretty interesting package name right?

Glad to see your looking out for our fellow peers! I really appreciate it, and I'm sure those fine folks do too!

Awesome! Glad to hear everything is running smoothly (for the most part)! Again, thanks a ton for the reports (and for any further ones you may provide in the future)!

It's been a pleasure friend! Hope you're having a great day/night so far!

 

[Jumbo100]

Heads-up for list/note makers using Google Assistant:

Google Assistant is killing support for notes and lists integration with third-party apps

Assistant will soon stop working with non-Google notes and lists apps

www.androidpolice.com

Google Assistant third-party Notes & Lists integration is coming to an end

Google Assistant will no longer be able to create notes/lists on third-party apps. Previous notes/lists could disappear as well.

www.androidauthority.com

Google Assistant’s 3rd-party Notes & Lists integration is shutting down

One casualty of the June 20 deprecation is the shutdown of third-party Google Assistant Notes & Lists integration...

9to5google.com

 

[chupajr]

Hi @Datastream33 , I am seeing this issue running in Ubunto 20.04. I tried in both Python 3.10 and 3.7 environments.

I'm a Python dev so feel free to DM me if you want to get into technical nitty-gritty

❯ ./FTB_Beta_V1.0_Installer                                                                                                                                                                             
[664837] Error loading Python lib '/tmp/_MEIG3EQmT/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIG3EQmT/libpython3.10.so.1.0)

 

[jonny.pl]

@blaacksheep @Datastream33

is it normal, that the Amazon Fire Launcher appears, when i am pushing the back key from the launcher (Nova launcher)?
When i am pushing the "Tab / Change App" Button, the Nova launcher Appears?

On the App Automate i got 2 Flow that are called both Launcher Invoker... I am confused. Also the Launcher Log tells me

"Stopped by block"
Fork
Medie Button
App in foreground?
Fiber stop
stopped by block
Media Button
App in foreground?

Help!

Otherwise can i downgrade the Amazon Fire Version to an older one? I dont want that the Amazon Launcher appears!

 

[blaacksheep]

@blaacksheep @Datastream33

is it normal, that the Amazon Fire Launcher appears, when i am pushing the back key from the launcher (Nova launcher)?
When i am pushing the "Tab / Change App" Button, the Nova launcher Appears?

On the App Automate i got 2 Flow that are called both Launcher Invoker... I am confused. Also the Launcher Log tells me

"Stopped by block"
Fork
Medie Button
App in foreground?
Fiber stop
stopped by block
Media Button
App in foreground?

Help!

Otherwise can i downgrade the Amazon Fire Version to an older one? I dont want that the Amazon Launcher appears!

It sounds like what happens if you have FireOS v7.3.2.2 or higher and you're using the Custom Navbar Button method of launcher replacement.

If so, YES, it's completely normal. This is due to the Amazon Launcher being a "protected app" and Toolbox not being able to disable it. The only method that has been successful at replacing the launcher is to just not call it. The Home button replacement calls your custom launcher instead of the Amazon Launcher. The Back button, when pressed from the custom launcher screen, will in fact call the previous running app. Unfortunately, the Amazon Launcher app is at the top of that list and will get called when you press Back.

It sounds like you have two instances of the Launcher Invoker flow in Automate. You could try stopping one and see how it behaves. If it doesn't work, restart the flow you stopped and then stop the other one. What I believe you'll find is they both do the same thing and only one of them is needed. If so, it's probably safe to remove one or leave it stopped.

There's no way to downgrade your FireOS version to an earlier version of firmware. Amazon has seen to it that it's not possible (at least not without root privileges). If you have an earlier version of FireOS like V5.x.x.x in an older tablet like a pre-2017 Fire, then you may be able to get root and replace the firmware with generic Android firmware. Just search the site for instructions.

 

[jonny.pl]

Yes i was using the CustomNavBar Button Methode.

Earlier i tried the Homebutton method, nur there i had the same problems that the Amazon Launcher appears in some ways.

We got a Fire Hd 10 Pro 2021. Before i updated the Fire Hd 10 there Was installed an eaelier version. I dont know which one...

 

[blaacksheep]

Yes i was using the CustomNavBar Button Methode.

Earlier i tried the Homebutton method, nur there i had the same problems that the Amazon Launcher appears in some ways.

We got a Fire Hd 10 Pro 2021. Before i updated the Fire Hd 10 there Was installed an eaelier version. I dont know which one...

A 2021 tablet most likely came with FireOS v8.x.x.x. Your best bet would be to get used to the idiosyncrasies of the workarounds that have been used to bypass Amazon's forced apps and just wait and watch for any news of discovered new vulnerabilities to get root permissions. Even a temp root will allow us to further remove restrictions from the tablets. Otherwise, Toolbox is your one-stop convenient place to get the most up to date workarounds and advice on your fire tablet.

 

[Jumbo100]

While you're modding your Fire tablet, customize your keyboard too:

How to customize your Gboard toolbar and shortcuts

Gboard has plenty of neat functions, with some being easier to find than others. Now, you can change that by...

9to5google.com

... and the text-by-voice mic icon still doesn't work with FireOS

 

[Stef71]

Hello,
I also got my Fire HD 10 (2021) today and it has the firmware 7.3.1.9. The tablet should serve as a wall tablet to display my visualization of my home automation. Tasker, Fully Kiosk Browser should later run on it. Now I would have questions about what I have to do to get the best out of the tablet. The "Disable Lockscreen" option is clear so far. Use Toolbox 30.3 with Windows 10
From what I've read, I shouldn't update the tablet with a newer firmware, correct? I haven't set up WiFi yet.

I have to say that I tried it today and it worked right away and the tablet was reset to factory settings and now when I run the "Disable Lockscreen" function it always asks me for a screen lock and select "None" and then it doesn't go any further.

Best regards
Stefan