yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] DB126:
Amazon has little motivation to support hardware gps on Fire tabkets. They do not offer a mapping/navigation app nor support games that depend on precise location. Approximate location derived from various sources is good enough.
[Fire HD 8 and HD 10 General] Nemesis02:
That's not quite true. Amazon Fire tablets do come w/ a maps app, it's just not all that intuitive but it does have navigation.

[IMG="Maps"]https://xdaforums.com/attachment.php?attachmentid=4866513&stc=1&d=1572901500[/IMG]
[Fire HD 8 and HD 10 General] DB126:
Yep - I stand corrected. Neglected to consider Amazon Maps (and similar tools based on API V2) which is not competitive but there none the less. Problemo is no GPS based navigation on Amazon devices which renders it largely useless is most real-world scenarios. Stated another way, Amazon has little motivation to add hardware GPS to fire tablets given how they are positioned. One could argue what better marketing/shopping opportunity than a potential customer (presumably passenger) held hostage during a long road trip. Don't think it would sell. Apparently neither does Amazon. :)

To the best of my knowledge the only Amazon tablets with native GPS support were 3rd/4th gen HDX tablets with LTE capability.
[Fire HD 8 and HD 10 General] Rortiz2:
Nice info!

Maybe @Supersonic27543 knows something about those CVEs.
[Fire HD 8 and HD 10 General] LordSimal:
I just read, that the recent Google 03/2020 security patch fixed a root exploit applicable to Android devices with a MediaTek CPUs.

Can this help somehow?
[Fire HD 8 and HD 10 General] MontysEvilTwin:
Could that be [MENTION=8132642]diplomatic[/MENTION]'s mtk-su?
[Fire HD 8 and HD 10 General] Calthrop:
I've just recieved a replacement Fire HD 10 from Amazon, and out of the box its still on 7.3.1.0 - so will give the temp root a try.

Will rooting allow me to disable OTA, and permenantly remove amazon apps/launcher? I've been using the Toolbox on my now broken HD 10 and was happy with how it was set up, apart from the laucnher reverting everytime Amazon pushed out an update and Amazon apps reappearing.

***EDIT***

I've managed to root it, and install Magisk. I've debloated and disabled the OTA via the adb commands, and will install Play Services and Nova next. I still haven't connected it to wi-fi, am I safe to do so now?
[Fire HD 8 and HD 10 General] Rortiz2:
If you disabled OTAs with pm disable, you are safe to enable Wi-Fi now.
[Fire HD 8 and HD 10 General] newnewcomputer:
Congrats! Also u are lucky to get 7.3.1.0 as Amazon has started shipping newer rev in some regions / for some colors.

u are definitely safe to get on wifi if u have Magisk n disabled OTA via adb. i assume u have used "pm disable-user" command. U also mentioned using the Amazon Toolbox before. if so, please keep an eye n report back when/if the launcher revert or disabled app reappear.

i read that is common occurence in the Toolbox thread but rarely is that reported in this thread here w/ temp root n pm disable command. so im curious if pm root+pm disable-user is a more permanent sol'n. thanx!

PS: u can add the OTA disable command in the suroot file so that it will be executed during every boot up. i have been running that n not see any update from Amazon for more than a few months now.
[Fire HD 8 and HD 10 General] Calthrop:
Yep, I used the pm disable-user commands to disable OTA and all of the Amazon apps. I'll keep an eye on it, but hopefully the launcher doesn't revert.

How do I go about doing the suroot command? Its been a while since I rooted any of my devices, so not to familiar with everything I can do now.
[Fire HD 8 and HD 10 General] DB126:
Suggest renaming DeviceSoftwareOTA.apk (just that file; not everything that has OTA in the name) as absolute insurance against an unwanted OTA.
[Fire HD 8 and HD 10 General] Kctucka:
I didn't think you could do that without ability to modify system partition? Never tried though.
[Fire HD 8 and HD 10 General] DB126:
Correct - root and (implicitly) write access to the 'system' partition is required.
[Fire HD 8 and HD 10 General] newnewcomputer:
I assume you have followed @diplomatic 's steps to install Magisk. One of the steps is "put suboot.sh inside your /sdcard/init.d folder."

open suboot.sh w/ a text editor (i use Mixplorer from XDA here.) scroll down till u see the scripts for Magisk and add this line after those:

pm disable-user --user 0 com.amazon.device.software.ota

that will re-disable the OTA update app during every reboot n theoretically should stop amazon from slipping in an update. no update - no launcher reset :laugh:
[Fire HD 8 and HD 10 General] MontysEvilTwin:
To prevent OTA updates, if you are on OS 7.3.1.0, why not get a root shell with mtk-su and run the following:

pm uninstall -k --user 0 com.amazon.device.software.ota

This used to work without root until Amazon blocked it in OS 5.4.0.1. It does not delete the apk from the system folder.
[Fire HD 8 and HD 10 General] newnewcomputer:
good point - i remember when this mtk-su exploit was first reported, there were discussions on pm disable-user Vs pm disable Vs pm uninstall.

disable-user requires the least privilege while disable n uninstall requires more but all three are accessible thro' mtk-su. like u said, the apk in system folder will remain so none of them will not trip dm-verity.

for OS 5.3.x, pm disable was preferred cuz' pm uninstall usually requires a factory restore to be undone. now it seems like for newer OS which the Fire 10 2019 is on, the uninstall can be undone according to this thread.

real problem is no one seems to know how Amazon is re-activating updates. i know it has not happened to most in this thread w/ temp root+adb commands. but it seems to happen to others using the Toolbox. thats why its nice to hear from some1 who has used both methods to compare.

anyhow i dig out the code segment where i have edited the scripts in suroot.sh:

# Finish startup calls
magisk --post-fs-data
magisk --service
magisk --boot-complete
pm disable-user --user 0 com.amazon.device.software.ota
sysctl -w vm.swappiness=20

the last line will set swap file's swappiness to 20. default for Fire 10 2019 is 60 which itself is an improvement over previous OS which were set to 100.
[Fire HD 8 and HD 10 General] AmznUser444 Dev:
You can disable it completely to stop reverting the Amazon junk:

//Enter ADB shell
adb shell

//Disable it
pm disable-user --user 0 com.amazon.firelauncher (before you disable this, you can install an another launcher like Nova Launcher or Microsoft Launcher)
pm disable-user --user 0 com.amazon.device.software.ota
pm disable-user --user 0 com.amazon.device.software.ota.override
pm disable-user --user 0 com.amazon.settings.systemupdates
pm disable-user --user 0 com.amazon.kindle.otter.oobe.forced.ota
pm disable-user --user 0 com.amazon.dcp.contracts.library
[Fire HD 8 and HD 10 General] DB126:
Excellent (and accurate). Tweaking swappiness is a nice touch; the HD10 with 2GB ram generally won't benefit from a static swap file. FWIW - adjusting LMK values can also yield positive results depending on usage scenario.

---------- Post added at 11:20 AM ---------- Previous post was at 11:17 AM ----------

Just stop - posting shotgun guidance without an understanding of the ramifications (side effects) is a disservice to the xda community.
[Fire HD 8 and HD 10 General] Calthrop:
I'm off work this weekend, so will give all the above a try. Thanks everyone.
[Fire HD 8 and HD 10 General] pharpe:
I just got a new Fire HD 10 that was on 7.3.1.0. I did the temp root, removed all the Amazon stuff, installed google framework, and disabled auto updates. However, somehow overnight, it updated and everything is back. It's now on 7.3.1.2. Is there anyway to role back?
[Fire HD 8 and HD 10 General] Michajin:
No way to roll back...

How did you disable auto updates? I am on 7.3.1.0 and i have never had an issue. I have 2 more on 7.3.1.1 that are also still disabled.
[Fire HD 8 and HD 10 General] pharpe:
I figured there was no way to roll back so I just did a factory reset and sent it back. I used the tool kit to disable updates but it looks like that doesn't work. On the fence about buying another 10 or an 8 . It sounds like with the 8 I can unlock the bootloader which presents more options.
[Fire HD 8 and HD 10 General] Michajin:
Ok, I'm not sure how the tool kit tries to block the updates. I always have done-

pm disable-user --user 0 com.amazon.device.software.ota

pm disable-user --user 0 com.amazon.device.software.ota.override

And changed the launcher by installing a replacement then

pm disable-user --user 0 com.amazon.firelauncher

The older 2017 10HD and the 2018 8HD are both rootable, the 2019 10HD is 50/50 on what OS comes on it now. The 8HD is decent device. You might be able the catch a cheap one from an auction. I just got a like new 8hd from goodwill for $40. I did the shorting method this time because it was faster, the shorting point is easily accessible.
[Fire HD 8 and HD 10 General] DB126:
[MENTION=4914529]Michajin[/MENTION] will be familiar with this tired refrain: "pm disable ..." commands are easily reversible. Now there's no telling if this is what happened on your device, just a possibility. The best way to insure OTA updates remain blocked is to rename DeciceSoftwareOTA.apk to an identifier of your choosing.
[Fire HD 8 and HD 10 General] Michajin:
I did some looking at the toolbox. The tool itself does not disable OTA updates. It disables amazon appstore updates. The OP does explain how to uninstall the OTA software though here ...

Post #2234

https://xdaforums.com/hd8-hd10/deve...olbox-v1-0-t3889604/post81921289#post81921289
[Fire HD 8 and HD 10 General] DB126:
Interesting choice of targets. I wonder why this (or other durable approaches) are not baked into the toolbox for devices that have root access. Not for us to answer.
[Fire HD 8 and HD 10 General] Michajin:
I seen in the thread people are requesting it. But it looks like a decent tool for newbs and he is managing it to work on a bunch of devices. He is very active in the thread so kudos to him. I think the "automatic updates" should be labeled differently imo. If this is truly why he believed his OTA's were disabled. Either the rooted uninstall or renaming method or an option for non-root to disable via ADB (possible temporary) should be fairly easy scripts to write into the program. He is also using automate to block ad's on the lockscreen (which is a total workaround). Another option would be to make a init-d script to disable on boot. But the tool works well for those who are new or lack any effort in learning... But this is totally off topic in this thread, so i apolgize. I just hope more don't get confused on the whole blocking updates from just using the tool, unless i am missing something.
[Fire HD 8 and HD 10 General] newnewcomputer:
i remember that OP's Automate sol'n for HD8 2017 after Amazon disabled the privilege elevation method in one of the updates. Seems like he has broadened its scope since...agree that it is an interesting mix n some, like OTA block n wallpaper changer, will not work as implemented.

OP is definitely active n responsive in that thread. it has quite a following but some ppl would have done well to expand their reads on XDA. below are 2 recent posts in that thread...they are circa 2018 :eek:
[Fire HD 8 and HD 10 General] bobjackson.other:
Is this project dead or are people solving for this in the background? Just curious. Would like to help, if possible.
[Fire HD 8 and HD 10 General] LordSimal:
Since https://xdaforums.com/hd8-hd10/general/donate-to-k4y0z-unbrick-twrp-unlock-t3995201 has been closed and this thread is going on for like 6 months I guess unlocked bootloader/TWRP/Custom-ROM for the Fire HD10 2019 will never happen.

Therefore the only way to at least unbloat the tablet is to use the Amazon Fire Toolbox.
[Fire HD 8 and HD 10 General] dsubscribe:
[MENTION=5488402]DB126[/MENTION],

on a 2019 Fire HD10 v.73.1.0

I have "UID: 0 cap: 3fffffffff selinux: permissive"

But getting "mv: bad 'DeviceSoftwareOTA.apk': Read-only file system" when trying to rename

/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk
[Fire HD 8 and HD 10 General] DB126:
No root permissions in target folder.
[Fire HD 8 and HD 10 General] Michajin:
You have root access,you need to make the directory editable i think (im not a linux guy). You can also make a back up and uninstall it. I seen someone made use of the rapid root magisk init.d and installed in the script to disable OTA's. I find it easier to disable OTA's but there is some debate about if it is permanant. The 2019 hd10 i have had disabled for 6 months. Pick your poison....
[Fire HD 8 and HD 10 General] dsubscribe:
respective folders have write permissions:

UID: 0 cap: 3fffffffff selinux: permissive

drwxr-xr-x 17 root root 4096 2009-01-01 00:00 system

drwxr-xr-x 172 root root 8192 2009-01-01 00:00 priv-app

drwxr-xr-x 3 root root 4096 2009-01-01 00:00 DeviceSoftwareOTA

-rw-r--r-- 1 root root 915650 2009-01-01 00:00 DeviceSoftwareOTA.apk

chmod: chmod 'DeviceSoftwareOTA.apk' to 100777: Read-only file system

I am using only diplomatic's mtk-su script, no Magisk

2019 Fire HD10 , firmware 7.3.1.0 new out of box. Has not connected to wifi
[Fire HD 8 and HD 10 General] DB126:
Whelp, haven't experienced an issue renaming this file on numerous devices. Specific to the HD 8, initially secured temp root via mtk-su (months ago) and successfully renamed DeviceSoftwareOTA.apk. At a later point executed bootloader unlock, rooted (Magisk) and confirmed prior actions. I don't recall the procedural details or any unusual 'hurdles'; only relevant at the time of need and then quickly forgotten. Then again, being older than dirt I often forget me own name. Good luck, mate.
[Fire HD 8 and HD 10 General] Michajin:
I thought i saw something that the temp root itself would not allow system changes. I could be wrong. I would install magisk temp root and back up DeviceSoftwareOTA.apk then uninstall it.. Personally, i just used magisk with the mtk-su. Just easier to manage....
[Fire HD 8 and HD 10 General] DB126:
Yep, stimulating some dusty synapses. Believe I went with temp Magisk prior to unlocking. Note permissions query doesn't always reveal the real deal w/temp root.
[Fire HD 8 and HD 10 General] dsubscribe:
Spending way too much time troubleshooting. So, I successfully installed magisk & enabled su . But getting error trying to uninsall

adb shell pm uninstall --user 0 com.amazon.device.software.ota

Failure [DELETE_FAILED_INTERNAL_ERROR]
[Fire HD 8 and HD 10 General] Michajin:
I would suggest using disable then. I haven't had an issue with using disable, but others have. I have been using this on my 10hd (2019) for 6 months without issues. But that being said, I have also put it into the init-d file for magisk so on every reboot, it tries to disable it. From what i understand there is a amazon way of enabling these apps, but I have not had it happen to me (I know if you take a update it will enable them). All i can think of is the temp root doesnt allow system changes to uninstall or modify.

adb shell pm disable-user --user 0 com.amazon.device.software.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota.override
[Fire HD 8 and HD 10 General] dsubscribe:
I am new to Magisk & novice with adb. I have Magisk running the script upon boot

Is the command "adb shell pm uninstall" using root/su automatically?
[Fire HD 8 and HD 10 General] Michajin:
you have to run a shell and then do su, you should see a #

root - karnak:/ #

not root - karnak:/ $

adb shell

su (accept on screen if requested)

pm uninstall com.amazon.device.software.ota

You should see maverick (I had my HD8 plugged in)

You need to run su to uninstall, but the disable works also... no root needed...
[Fire HD 8 and HD 10 General] dsubscribe:
Tried this way as well...same result. I'll have to stick with disabled. Thanks for the responses.
[Fire HD 8 and HD 10 General] gdroid666:
is there any hope of a noob friendly guide for getting updates blocked on my tablet coming anytime soon?

i had this thing sitting here never booted since like black Friday i think it probably has 7.3.1.0 or below and i would like to preserve it but i would also like to use the tabet

should i wait it out a little longer ? or do you think there is not anyhting worth waiting for?

i didn't wait with my 2018 HD 8 and now i am stuck on higher FW with no root
[Fire HD 8 and HD 10 General] Michajin:
since you posted the same question in (2) forums, here is the same answer...

Yes you should be fine. Once you get to the wifi select, hit back. and then skip. You should be able to get into the OS without connecting to the Wifi, Do not connect to the network until you have installed the MTK-su root (with magisk) and have disabled updates. Once you get into the OS check the version. They were all shipping with 7.3.1.0 in October... If good go to this thread to get root and magisk, then search for disable (do not just click in development setting, it will still update)

https://xdaforums.com/hd8...hd-10-t3904595

Then do this for always root...

https://xdaforums.com/sho...&postcount=135

Message me for questions, i can walk you through it... Either renaming the update or disabling the OTA app seems to disable updating.. . Just do not connect to the internet until you have them blocked...
[Fire HD 8 and HD 10 General] infernix:
For those using bootless root with magisk and an init.d, just create /sdcard/init.d/no-ota.sh and fill with:

#!/system/bin/sh
sleep 5s
su -c 'rm -f /data/ota/* /data/ota_package/*'
su -c 'chown root:root /data/ota /data/ota_package'
su -c 'chmod 000 /data/ota /data/ota_package'

This way, even if the OTA apps somehow magically re-enable themselves, they won't be able to write to those directories, effectively blocking the ability to download the OTA binary there.
[Fire HD 8 and HD 10 General] _phk_:
[MENTION=4914529]Michajin[/MENTION]: your links are not working
[Fire HD 8 and HD 10 General] Michajin:
They are the links from the OP (post#1). I messed up on them. Use mtk-su ,-21+ for root. Then use the magisk (on the op, post #1) for root on boot for a permanent option.

---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------

Using adb user disable had prevented anything from updating in all of mine. 1 rooted, 2 on stock. 6 months. No issues.
[Fire HD 8 and HD 10 General] gdroid666:
"Yes you should be fine. Once you get to the wifi select, hit back. and then skip. You should be able to get into the OS without connecting to the Wifi,"

Yeah i remember doing this with my 2015 fire 7's ,those were the last Amazon devices i rooted

so now i just went to try it out and it seem like there is no way to do it , it goes to the language select screen then i select English

and it goes to the wifi screen, but there is no skip option , going back just brings me right back to the language screen
[Fire HD 8 and HD 10 General] Michajin:
Press select network, but don't pick one, his cancel. then skip.. try that...
[Fire HD 8 and HD 10 General] gdroid666:
ok thanks yes that worked , just checked , yes it is still 7.3.1.0

but i am not sure what to do now, i haven't rooted one of these things in a long time

my PC that had ADB environment setup is broke so i assume 1st thing i need to do is set up drivers and ADB right?
[Fire HD 8 and HD 10 General] Michajin:
option b select a network. just disable the update before it installed after you get to dev options to turn on adb...

Forced OTA

adb shell pm disable-user --user 0 com.amazon.kindle.otter.oobe.forced.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota.override

Just don't let it sit idle, or let it reboot (force power off), there is risk here though...

---------- Post added at 06:34 PM ---------- Previous post was at 06:30 PM ----------

Great, once you get into it. do this to stop OTA's once you get ADB debugging on...

Forced OTA

adb shell pm disable-user --user 0 com.amazon.device.software.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota.override

Then proceed with MTK rooting, it is recommended to add this to the init-d script when you get that far..

---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------

adb link is what i use... comes with working drivers, What PC environment are you on? Win/Mac/Linux?
[Fire HD 8 and HD 10 General] gdroid666:
win 10
[Fire HD 8 and HD 10 General] Michajin:
I use adblink for tools on win10. Your call though...

https://xdaforums.com/fire-tv/themes-apps/adblink-v2-04-t3389826

It was designed for fire tv, but works great for fast tools on amazon devices...
[Fire HD 8 and HD 10 General] gdroid666:
how do you use it ,i installed it but i can't get it to do anything , it doesn't detect my tablet

what am i supposed to select for USB option the tablet, file transfer?

i plugged it in and granted USB permissions for file transfer , nothing shows up it looks like this tool is only designed to connecting wirelessly via IP

m PC installed the fire drivers and it shows in explorer as a drive but in this adblink program i see nothing under connected devices window or in the select device pulldown

EDIT: NM i finally got it i had to hit ADB refresh

so now how do i block the updates , you are saying i can't block updates without rooting 1st right

the links were broken so what should i do next?
[Fire HD 8 and HD 10 General] Michajin:
from a shell just start off at "pm disable-user...", from a console just use the following.

adb shell pm disable-user --user 0 com.amazon.device.software.ota

adb shell pm disable-user --user 0 com.amazon.device.software.ota.override

The first post of this thread has links ...

Temp root:

https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595

Bootless root (sets root manager and starts root on start up)

https://xdaforums.com/showpost.php?p=79626434&postcount=135
[Fire HD 8 and HD 10 General] gdroid666:
ok so i ran the

pm disable-user --user 0 com.amazon.device.software.ota

pm disable-user --user 0 com.amazon.device.software.ota.override

commands from maverick shell $

and i have achieved UID 0 selinux permissive

when i click your link for the majisk installation at the top of the post it says obsolete

so do you want me to follow the guide from the OP from the link you sent or should i go to the newer one and follow that?

also how long does this temproot presist? what will break it , rebooting the tablet only , or if i disconnect from the PC /ADB will it go away?

i assume when you said in the mtk thread to make sure the tablet screen stays on that that was just for running the script right ,after the script runs successfully it's ok to let the screen go off and i wont lose the temp root i assume