yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Android Development] lucian74:
did reset it as suggested - looked a video about automate now - but didnt try it yet.
[Fire HD 8 and HD 10 Android Development] Trebrick:
Thanks for the reply. Yah nothing working. O well no biggie. Thanks anyway
[Fire HD 8 and HD 10 Android Development] Jumbo100:
Actually it COULD be a "big deal" . If some of your Android apps have suddenly stopped working and can't be "repaired" using standard Android troubleshooting techniques, it makes me suspicious that Google may be making changes to GPS with some recent updates.

This Spring/Summer Google upgraded it's "Certified Play" standards using the new "Android Play Integrity" API. This requires all Android apps be recorded to meet the the new higher standard by 2024. Effectively, whan an app is installed from Play Store, a "signature" is set on the app to indentify it as "genuine" Play Certified. When an app is hacked/prirated/modded it will be treated as malware and will crash ... which is great ... It protects the Play Store. BUT the standard is also applied to uncertified devices such as FIRE DEVICES!

So, if apps installed from Play Store need to run trough the Android Play Integrity API infrastructure they will crash on Fire tablets ! ... THAT'S a "big deal" ... and that's scary!

My "Google paranoia" is showing.
[Fire HD 8 and HD 10 Android Development] cacondilac:
Hi all. I'm new to the forum.

I'm just about to purchase a refurbed Fire 10 with a view to using Fire toolbox to get Google play services up and have this error, custom launcher is still ok.

I don't know what should i do :((
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Hi, and welcome to XDA!

That message indicates that ADB tried to install an app that didn't have the right extention (.apk or .apex) To me, that means the Google Services apps got corrupted during download to your PC. The easiest way to fix that is to go into the installation folder (something like "C:\Users\YourUsername\AppData\local\Datastream\Fire Toolbox V29.x\bin\Google Services"), and delete the contents of the Google Services folder. Then restart the app and try installing again. That should make Toolbox re-download the Google Services apps and correct the problem. :)
[Fire HD 8 and HD 10 Android Development] Davy49:
Hi Everyone,

I'm sitting here typing this post with frustration all over my face, as I do in fact now realize that my gung ho experiment I did with my fire 7 (2019 edition) backfired on me. Upon performing a factory reset on my tablet I failed to disable the wifi setup function and of course by not doing so I received the latest fire o.s. firmware update (7.3.2.4) . I've been reading here in this forum just how much amazon seemingly keeps trying to cripple the use of the fire toolbox software, and now I've experienced that fact first hand. So basically I guess what I'm now looking for is some kind of reference guide as to how to get my fire 7 (2019 edition) setup in a 'similar' fashion to the way I had it setup when I was running a lower version # of the fire o.s. firmware. It surely would be great if users of fire tablets could somehow downgrade the firmware to a lower version # so the fire toolbox would function properly once again.

David :-(

Update: I'm thinking that I'll go ahead and order this tablet @ amazon: https://www.amazon.com/Display-Quad...cc4-932c-1ecc3b275cc3&pd_rd_i=B0B51S8M4S&th=1
[Fire HD 8 and HD 10 Android Development] blaacksheep:
I didn't think you'd be happy with that "upgrade". I kind of warned you in my reply to your post about "living on the bleeding edge" and getting the latest f/w. I bought a second tablet to experiment with the new f/w because it was close to prime day. It took some messing around with it but I've got it about as good as I can expect. It will never be as smooth in operation as my other tablet, but it works. The best thing to do is just fool around with it until you get it to where it behaves. Play around with Custom Navbar Key and Dark Mode to get the best navbar experience you can. Resetting now won't cause further damage.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
@Davy49

Love your sense of experimentation and curiosity. That's what "true" learning is all about ... experiencing "failure" and moving forward; not from repeating status quo successes.

I think a far more "challenging" experiment would be how to expand your Fire tablet function WIHOUT the Google Play Service infrastructure. Much of the attraction of FTB is how easy it is installing Google Play Store and gaining access to all the apps not on Amazon Appstore ... and that's almost always successful.

But what if you can't use Google Play Store ... how can you expand Fire tablet functionality without it? That's the challenge facing FTB users with the new 12th Gen Fire 7/8 tablets with FireOS 8 are facing now.

@Datastream33 @blaacksheep et al, have suggested something like Aurora Store as an alternative, but the process and its outcomes have not been fully documented on Fire tablets. I don't it's easy.

That's a challenging project and would be of real value to all generations of FTB and Fire tablet users.
[Fire HD 8 and HD 10 Android Development] Davy49:
I'm really thinking more & more about obtaining a new completely different brand of android tablet that comes ready for use when I first turn it on. Even when my fire 7 (2019 edition) was brand new it was pretty slow due to the very low hardware specifications. My android lg velvet 5g phone that has android o.s. version 12 on it runs circles around my fire tablet. I went ahead & ordered this tablet on amazon yesterday, and of course no offense to datastream or anyone else here in this forum, but as most owners of fire tablets already know the firmware developers @ amazon continue to further cripple the fire toolbox software from doing what it was originally designed to do (modify a fire tablet so it more closely resembled an actual android tablet) yesterday I purchased this tablet on amazon: https://www.amazon.com/gp/product/B0B51S8M4S/ref=ppx_yo_dt_b_asin_title_o00_s00

David
[Fire HD 8 and HD 10 Android Development] dpraved:
Well, I just soft bricked my device after disabling every system app haha .. (had to enter recovery mode to wipe/reset)

Must be list within this 500 page thread which services are okay to disable under 'advanced'?
[Fire HD 8 and HD 10 Android Development] blaacksheep:
That's a really subjective topic - which apps to disable. It all depends on what you want. Myself, I usually use "Simple" and click "Disable All". Then I turn the 3 or 4 apps I want back on and apply. It's always worked for me but YMMV.
[Fire HD 8 and HD 10 Android Development] drizzt09:
See this post from the dev awhile back. https://xdaforums.com/showthread.php?p=79427460
[Fire HD 8 and HD 10 Android Development] pieceofphil:
Hmm thank you, but I don't want it as internal memory, just usual external memory with writing rights to be able to swap files from the tablet to the SD card with file managers on the tablet...

I can access the SD card with my computer and swap the files there, but that's a bit impractical:cyclops:
[Fire HD 8 and HD 10 Android Development] Datastream33:
Have you checked to make sure that the SDCard isn't formatted as NTFS and it is FAT32 formatted? Another thing that could be conflicting is the removal of the Docs app. Can you please check if the app still remains on your tablet? If this app isn't present its know to cause issues with moving docs and opening files with other apps. If this is the issue please download and install Toolbox V5.0 and use the Manual Restore tool to restore the docs app. If the problem lies somewhere else I'm not sure what/where it could be coming from unfortunately.
[Fire HD 8 and HD 10 Android Development] Datastream33:
If the system can be mounted as read/write then I suppose there wouldn't be any harm in doing the awesome idea you have proposed. I would be more then glad to do it this way if it can be done using temp root. You can confirm 100% that this could work? I do not own a working 7th gen device so I can't test right now.
[Fire HD 8 and HD 10 Android Development] drizzt09:
I Have 7" 7th gen. If you give me manual steps to test I can try it out for you
[Fire HD 8 and HD 10 Android Development] Datastream33:
Ok, sweet! Thank you! :D

Please follow these steps, and let's see:

Please open Toolbox v5.0.

Click the "ADB Shells" tool and execute the "Temporary Root" shell.

When the root shell finally appears type the following command:

mount -o remount -rw /system

Wait for command to finish and then type this command to check if the system is read/write:

mount | grep system

Like for example, when executing the first command on my device nothing happens, and then when I execute the last command on my HD8 (2018) I get:

/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime,data=ordered)

Unfortently the "ro" means it is read only. If I was able to mount the system as RW you would get this instead:

/dev/block/dm-0 on /system type ext4 (rw,seclabel,relatime,data=ordered)

Can you please execute the commands above and after executing the last command can you please share with me the output? Thank YOU SO MUCH for helping me with this drizz! You are AWESOME friend! :D
[Fire HD 8 and HD 10 Android Development] drizzt09:
Just an fyi. I have gone to bed. But will try in the morning. (So you aren't up waiting)
[Fire HD 8 and HD 10 Android Development] Datastream33:
Ok, that is fine. Have a good sleep! See ya tomorrow :D
[Fire HD 8 and HD 10 Android Development] Rortiz2:
mtk-su doesn't work on Fire 7 7th gen. MT8127 = arm..
[Fire HD 8 and HD 10 Android Development] Kctucka:
Unfortunately, temp root won't work on the 7" 7th gen.

I don't have my computer currently to mess around with doing it with temp root, but it does work with root.

It should work though, as I had to mount system rw in order to fully root in a temp root shell. I will test more though when I'm back at my computer tomorrow night.
[Fire HD 8 and HD 10 Android Development] DB126:
Think carefully before treading into the liabilities of mounting system r/w on random user devices. In a perfect world where you control all the knobs/dials (and the encapsulating code never fails) the risk is manageable. Unfortunately, the methodology used by the toolbox does not provide such assurances as evidenced by the comments posted to this thread.
[Fire HD 8 and HD 10 Android Development] klausb65:
The name of the file could also be: com.teslacoilsw.launcher-2

(it is in my system so)
[Fire HD 8 and HD 10 Android Development] drizzt09:
As mentioned by 2 others. temp root doesnt work. says not supported.

ro.build.version.fireos=5.3.6.8

ro.build.version.fireos.sdk=4

ro.build.version.sdk=22

ro.product.brand=Amazon

ro.product.name=austin

ro.product.device=austin

ro.product.package_name=com.amazon.austin.android.os

ro.product.board=austin

ro.product.cpu.abi=armeabi-v7a
[Fire HD 8 and HD 10 Android Development] Datastream33:
Ah, i see. Well that actually makes sense now that I think about it. I thought I remembered diplomatic telling me 7th gen wern't supported but I wasn't 100% sure. Oh well.
[Fire HD 8 and HD 10 Android Development] Kctucka:
7th Gen HD 8 and HD 10 are supported. Fire 7 7th Gen isn't.

I'll run some tests tomorrow to confirm I can get it working on my HD 10 just with temp root.
[Fire HD 8 and HD 10 Android Development] fbueller:
I have a FireHD 10, 2017 version. I used version 3.2 of the Toolbox with Launcher Hijack and installed Nova. Of course, there are delays in bringing up the launcher when the home button is pushed using LH. Can I update the Toolbox to 5.0 and rerun it to remove Fire Launcher? Will that cause problems? Should I uninstall LH first? I'd prefer a native solution using Nova than Launcher Hijack since it's probably much faster. Are there drawbacks/benefits to using one method vs. the other? Thanks!
[Fire HD 8 and HD 10 Android Development] KevMetal:
I used the tool on my fire tablet 8 hd 2018 . I started without root ...

-installing Play & Framework worked well

-wallpaper changer installs but fails to allow wallpaper change

-removing "everything Amazon" works but only in the sense that the apps are disabled by adb but on reboot they are re- enabled by system

-launcher hijack uninstalled on reboot and launcher reverts to Fire launcher

-lockscreen ads removal fails to install apk on sd card

-temp root fails to execute

*i had to use the twrp + magisk exploit for fire tablet 8 and to delete amazon apks through recovery to make my custom launcher stick.

using V5
[Fire HD 8 and HD 10 Android Development] Kctucka:
[MENTION=8560782]Datastream33[/MENTION] I uninstalled Magisk from my HD 10, cleared cache/dalvik, and started testing. None of my root apps were working at the time.

I was able to move nova launcher to system/priv-app and get widgets working using just temporary root shell from the toolbox.

As another user pointed out, the package could be called "com.teslacoilsw.launcher-2 " so it might make sense to have it start at 1 and iterate up to 5 if it returns "no such file or directory"

Either way, up to you if you want to include it.

I'll just leave it here again for anyone with a 7th gen fire 8 HD or fire 10 HD who's having issues with Nova:

Open a temporary root shell from the toolbox. Copy the following code:

mount -o remount -rw /system
cp -pr /data/app/com.teslacoilsw.launcher-1 /system/priv-app/com.teslacoilsw.launcher
pm disable com.amazon.firelauncher

Restart your device, and Nova will be your default launcher, with widgets enabled.

If OTAs are not blocked, it won't be permanent, as each update wipes system.
[Fire HD 8 and HD 10 Android Development] blackFirefly:
This is a great tool, thank you!

Unfortunately, I'm having touble to use the WallChanger App /:

I've instaled it, chose a photo but then it closes itself and changes the background to an image with the text "Wallpater is not set correctly Relaunch the WallChanger app". I've tried to relaunch the app several times and also restarted the Fire HD 10 (2017). But it's not working. And I'm even unable to redo the change. Now I have a really strange background xD

Why is it not asking me to crop the image? Do I have to install an other app to make it work?

Please help! Im stuck here!
[Fire HD 8 and HD 10 Android Development] Datastream33:
Yeah, WallChanger isn't perfect and I believe the app was never finished or simply isn't updated to the latest version (it is impossible to find). I'm looking for a non-root method at the moment and hoping to improve some features of the Toolbox that aren't working to satisfactory. In order to revert the process you might need to uninstall WallChanger and set a new wallpaper. I will let you know if I come across anything. I'm sorry for any inconvenience WallChanger may have caused.
[Fire HD 8 and HD 10 Android Development] Phatboyj420:
@blaacksheep​

Looking for some simple guidance / clarification

I have several 8th gen tabs that I bought last year with the hopes of eventually modding them, similar to what's being done in this thread. Now I've finally gotten around to doing some research, and am trying to determine my best course of action.

First I'm trying to definitively determine the latest F-OS firmware that will allow for completely replacing the Launcher.

I thought I had this answered for myself as to be 7.3.2.1 using the FTBv25, but then I saw your signature with the link about 7.3.2.1 although when following said link it is actually 7.3.2.2 that is being discussed.

Can you point me on the right path?

Thanks in Advance,

Phatboyj

...

..

.
[Fire HD 8 and HD 10 Android Development] ghoster76:
Well the DNS66 seem doesn't help blocking updates. I got it killed while my Fire sleeping in a while. As I unlocked the lockscreen then saw several apps disabled then be enabled right after then. That means DNS66 was always killed by something. Not sure how to prevent system update.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
To be overly simplistic:

"The Great Divide" (TGD) : introduction of FireOS 7.3.2.2 (Nov/21)

BEFORE TGD : Full FTB mod function

AFTER TGD : Restricted FTB mod function

Your Fire tablets are from the "Before" times and have the best opportunity for the "full" FTB mod experience. FireOS 7.3.2.1 was the last f/w update from the "Golden Age" of fulsome FTB mods ... you/re so lucky!

FTB V.29.x has new functions which may be of interest to you, but as always, can't fix the underlying restrictions of f/w 7.3.2.2 ... the "Great Divide".

## Edit ##

To your specific question:

You can't fully replace Amazon Launcher with f/w 7.3.2.1 ... hasn't been possible for quite a while. However the new "CustomNavBar" in FTB V.29.x is an elegant workaround and although not totally seamless, works very effectively.
[Fire HD 8 and HD 10 Android Development] amppcguru:
I have often wondered how to figure out what the codename is for a specific device and where to find it?

I'm just about to return my New Fire HD8+ 2022 if I can't get Google Play store. It makes owning one pointless & have to go back and find an Android tablet other than Amazon that doesn't discriminate what you install on it.

Only had a few days & really disappointed I didn't keep the previous version I had gotten right before they announced the New Version. FTB worked flawlessly on it and I had access to all my Google Play store apps & was so grateful for it. Will that patch work for me before I ship this back?
[Fire HD 8 and HD 10 Android Development] Phatboyj420:
Thank You, @Jumbo100

So then I was right, in my original thinking ? I should be able to install directly to the 7.3.2.1 and then fully deblaot via FTB 25? Once done what new functions might I check out in FTB 29?

Is it possible to downgrade from an OS7 build back to OS6 ?

Or,

is that only possible if you followed the xyz root method from early on?
[Fire HD 8 and HD 10 Android Development] Jumbo100:
@Datastream33 has just released V29.2 "micro patch" which should work on 12th Gen Fire HD8 tablets.

However, FTB can't fix the fundamental incompatibility of FireOS 8 and Google Play Services infrastructure ... they just won't work together.

Amazon has always stated (in fine print) that Fire devices do not support Google Play ... with FireOS8 they really mean it.

So, sadly you're right ... if you want/need a fulsome Google Play experience, avoid the 12th Gen Fire 7/8 tablets. Luckily, Amazon has a generous return policy.
[Fire HD 8 and HD 10 Android Development] amppcguru:
Thanks for letting me know! Just waiting for UPS to come get it & wanted to know if I should keep it or not. Bummer 😞 I have an Nexus 7.2 & really wanted something like it after the usb port failed and I could no longer keep it updated after flashing a partition expander that wiped it clean and I couldn't get the newer Roms transferred back to it.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
You're right "on track" ... if you can keep f/w 7.3.2.1 on your Fire tablets, you're "golden". Just closely stick to the prescribed FTB install protocols. Easy ... even the "newbie soccer moms" can do it. (No offence to the tech skills of "newbie soccer moms").

You can upgrade to FTB V.29.x now; same functionality as V25.0 but much easier to use. See recent @Datastream33 roll-out post which details all the new features he added ... nice.

Be careful about being overly agressive with "debloating"; possible to "soft brick" if overdone. Use selectively.

You can't roll back FireOS to earlier versions ... Amazon's seen to that. Apparently, they've engineered a hardware/software "e-fuse" which "trips" and "hard bricks" the device for anyone bold enough to try "hack" on current Fire devices using older "rooting" techniques to roll back FireOS versions.

Not aware of any custom ROMs for current Fire devices on XDA site; not even a bootloader "hack" to even attempt a root. Earlier root hacks on some previous Fire 8 tabs involved "shorting" motherboard components and fancy Linux scripts ... before my time and ouside my skill set. Not sure if applicable now. I'm sure the XDA "braintrust" would have found something if it were possible by now.
[Fire HD 8 and HD 10 Android Development] Jumbo100:
See recent posts re: Rethinkdns by @blaacksheep et al.

Promising allternative to DNS66 ... has a "Firewall" function as well as standard IP/DNS blocking.

May be a more robust solution to blocking Amazon OTA updates and Amazon "push" ads.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
So far in my testing of RethinkDNS, everything has gone well. I'm not turning off WiFi before shutdowns/reboots and it has always started up right away before the tablet can connect to an Amazon update server. It wasn't right away that DNS66 let an update slip through, so I'm continuing to test this and check the updates status to see if it has downloaded a pending update that I need to erase before rebooting. Still it looks very promising and if it continues to serve the purpose, I'll write up a post on how I've configured it.
[Fire HD 8 and HD 10 Android Development] Phatboyj420:
F Hd 8 8th on 7.3.2.1 Is there a way to use Nova as my launcher and maintain the functionality of the "Show Mode Dock", when docked ?
[Fire HD 8 and HD 10 Android Development] drovan:
Experiencing an issue here wonder if anyone else with a new fire has the same problem.

On Fire OS 8 models (2022 7 and 2022 HD8) toggling the hide device dashboard icon switch doesn't actually change anything on the tablet, same for the navigation bar settings modifier. You can manipulate the settings within fire toolbox, but no changes ever register on the tablet itself. The nav bar just stays the same default appearance no matter what.
[Fire HD 8 and HD 10 Android Development] blaacksheep:
It's possible that it's a FireOS 8 issue because that's only been a problem with the new 2022 models. They may have "protected" those setting somehow, or moved the settings somewhere else and left those settings there as a distraction while actually using settings from somewhere else.

If you're feeling adventurous, you may want to grab SetEdit from Aurora or Apkmirror and have a look around at those settings. Be very cautious with that app though. It allows access to things that should not be changed and can soft-brick your tablet. In other words, if you don't know what it does, google the setting before you change it with SetEdit.
[Fire HD 8 and HD 10 Android Development] Tacos RT:
When running Fire Toolbox's Custom Launcher tool, the attempt to push the Launcher Invoker flow results in Automate prompting with Failed to read Flo. Any ideas?

Fire HD 10 Plus 11th gen - Fire OS 7.3.2.4

Fire Toolbox V29.2

Automate 1.30.0
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Hi, and welcome to XDA!

It seems that people are having trouble with getting Automate set up lately on their tablets. I was assuming that they didn't follow the instructions carefully and missed a step along the line, but maybe not. I'll suggest that you try again, carefully following the instructions on the screen(s) and to give Automate the permissions that it requires. If you've already tried that, maybe the .flo file got corrupted during download. Try replacing the Launcher Invoker.flo file in C:\Users\YourUserName\Appdata\Local\Datastream\Fire Toolbox V29.2\bin\Automate\Flows folder with the attached file and running Toolbox again. (You need to extract the file first.)
[Fire HD 8 and HD 10 Android Development] blaacksheep:
Yeah, always use the latest version of Toolbox! (y) You can always get the latest version in the original post.
[Fire HD 8 and HD 10 Android Development] Tacos RT:
I was definitely on the latest update (V29.2) when the problem happened. I've been using the Toolbox updater since V26.0... So, I guess I want to still point out that a re-install did the trick and the Toolbox updater shouldn't be heavily relied on...

Thanks!