[GUIDE][NO ROOT] Remove Amazon apps on Fire 10 HD 2019

[BobPony]

Requires ADB to be installed on system, here's the list of commands that will get rid most of the amazon apps including OTA.

Legal Notices
adb shell pm disable-user --user 0 com.amazon.legalsettings

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

Weather
adb shell pm disable-user --user 0 com.amazon.weather

adb shell pm disable-user --user 0 com.amazon.platform

System updates
adb shell pm disable-user --user 0 com.amazon.settings.systemupdates

Kindle books
adb shell pm disable-user --user 0 com.amazon.kindle

Prime video
adb shell pm disable-user --user 0 com.amazon.avod

Special offers
adb shell pm disable-user --user 0 com.amazon.kindle.kso

Content Management service
adb shell pm disable-user --user 0 com.amazon.kindle.cms

Kindle store
adb shell pm disable-user --user 0 com.amazon.webapp

adb shell pm disable-user --user 0 com.amazon.tahoe

adb shell pm disable-user --user 0 com.amazon.iris

adb shell pm disable-user --user 0 com.audible.application.kindle

adb shell pm disable-user --user 0 com.amazon.cloud9.kids

adb shell pm disable-user --user 0 com.amazon.cloud9.contentservice

Silk browser
adb shell pm disable-user --user 0 com.amazon.cloud9

Amazon app store
adb shell pm disable-user --user 0 com.amazon.venezia

Amazon goodreads share
adb shell pm disable-user --user 0 com.amazon.unifiedsharegoodreads

Goodreads
adb shell pm disable-user --user 0 com.goodreads.kindle

Amazon gamecircle
adb shell pm disable-user --user 0 com.amazon.ags.app

Amazon Maps
adb shell pm disable-user --user 0 com.amazon.geo.mapsv2.services

adb shell pm disable-user --user 0 com.amazon.geo.mapsv2

adb shell pm disable-user --user 0 com.amazon.geo.client.maps

Shop Amazon
adb shell pm disable-user --user 0 com.amazon.windowshop

adb shell pm disable-user --user 0 com.amazon.csapp

adb shell pm disable-user --user 0 amazon.alexa.tablet

adb shell pm disable-user --user 0 com.amazon.dee.app

adb shell pm disable-user --user 0 com.amazon.mp3

adb shell pm disable-user --user 0 com.amazon.photos

Calendar/Contacts/Email
adb shell pm disable-user --user 0 com.android.calendar
adb shell pm disable-user --user 0 com.android.contacts
adb shell pm disable-user --user 0 com.android.email

OTA Photo Importer
adb shell pm disable-user --user 0 com.amazon.photos.importer

Device Setup
adb shell pm disable-user --user 0 com.amazon.kindle.otter.oobe

 

[fourteen00]

Hey, I tried a few of these and they worked, I think its just disabling them but either way I dont have to see their faces, I mostly did the updates OTA, Maps and good reads so I cant speak for the others. Thanks for the tip.

 

[DB126]

Hey, I tried a few of these and they worked, I think its just disabling them but either way I dont have to see their faces, I mostly did the updates OTA, Maps and good reads so I cant speak for the others. Thanks for the tip.

Many will come back over time as disabling system apps using this method is not durable. Rinse and repeat as needed.

 

[Xinto]

Many will come back over time as disabling system apps using this method is not durable. Rinse and repeat as needed.

This ^. I'm pretty sure Amazon will re-enable apps via OTA updates, unless you disable them via some script or via exploit which will be found in around 2 weeks

Sent from my Fire using Tapatalk

 

[BXM500]

Many will come back over time as disabling system apps using this method is not durable. Rinse and repeat as needed.

Why would they come back? I also disabled Amazon Appstore and OTA updater.

 

[Xinto]

Why would they come back? I also disabled Amazon Appstore and OTA updater.

Because they want you to use their services and Google banned them for using their services, at least that's what I know so we have to use their super idiotic services

Sent from my Fire using Tapatalk

 

[BXM500]

Because they want you to use their services and Google banned them for using their services, at least that's what I know so we have to use their super idiotic services

Sent from my Fire using Tapatalk

I understand that but I have literally blocked them from everything. Amazon has no control over my tablet anymore. I won't do any OTA updates.

 

[Xinto]

I understand that but I have literally blocked them from everything. Amazon has no control over my tablet anymore. I won't do any OTA updates.

Well, if you disabled OTA via some script them ok, but if you didn't they will install automatically even if you don't press install button, I assume you disabled it via script

Sent from my Fire using Tapatalk

 

[BXM500]

Well, if you disabled OTA via some script them ok, but if you didn't they will install automatically even if you don't press install button, I assume you disabled it via script

Sent from my Fire using Tapatalk

Hmm.. That's interesting. I didn't use any script. But how are they going to install when all related packages are disabled?

I guess we'll see

 

[Xinto]

Hmm.. That's interesting. I didn't use any script. But how are they going to install when all related packages are disabled?



I guess we'll see

I believe they hid something on root level, so I don't think using only adb is going to solve any problem, I would suggest waiting 2 weeks to 1 month and unlock tablet

Sent from my Fire using Tapatalk

 

[DB126]

Why would they come back? I also disabled Amazon Appstore and OTA updater.

If you nutered (renamed) DeviceSoftwareOTA.apk then most apps disabled via "pm disable-user ..." will remain in that state. Otherwise, they are easily reenabled via other processes or OTA activity. Disabling the previously mentioned app (none of the others really matter) and/or the Amazon app store via 'pm disable-user ...' is not durable as has been demonstrated on numerous occasions. FireOS will periodically re-enable apps/services it deems essential.

Caveat: I do not currently own a 2019 HD 10 (one is on the way) so it's possible behavior may be different on the FIreOS variant loaded on this devices. That said, FireOS has been behaving this way since early v3.x builds released in 2012. I see no reason why Amazon would reverse positions now as Fire devices are intended to be captive portals into the Amazon ecosystem, not general purpose Android gizmos.

---------- Post added at 12:57 PM ---------- Previous post was at 12:46 PM ----------

Because they want you to use their services and Google banned them for using their services, at least that's what I know so we have to use their super idiotic services

Not entirely accurate. While Amazon does want you to use their app store as it serves as a source of revenue to subsidize the low cost of hardware (not to mention the rest of the Amazon ecosystem) they do not explicitly block the installation of Google Play Service/Store. Google did not 'ban' Amazon devices. While FireOS is a heavily skinned Android variant it does not meet the criteria to have Google Play Service pre-installed given the presence of a competitive app store. All of the major players operate this way. It would be nice to see Amazon offer Fire devices in two flavors (one with a generic Android build including the Play Store at a higher price point) but there is no economic incentive to do so. If you want that buy an Onn or Samsung device.

 

[Xinto]

If you nutered (renamed) DeviceSoftwareOTA.apk then most apps disabled via "pm disable-user ..." will remain in that state. Otherwise, they are easily reenabled via other processes or OTA activity. Disabling the previously mentioned app (none of the others really matter) and/or the Amazon app store via 'pm disable-user ...' is not durable as has been demonstrated on numerous occasions. FireOS will periodically re-enable apps/services it deems essential.



Caveat: I do not currently own a 2019 HD 10 (one is on the way) so it's possible behavior may be different on the FIreOS variant loaded on this devices. That said, FireOS has been behaving this way since early v3.x builds released in 2012. I see no reason why Amazon would reverse positions now as Fire devices are intended to be captive portals into the Amazon ecosystem, not general purpose Android gizmos.

---------- Post added at 12:57 PM ---------- Previous post was at 12:46 PM ----------



Not entirely accurate. While Amazon does want you to use their app store as it serves as a source of revenue to subsidize the low cost of hardware (not to mention the rest of the Amazon ecosystem) they do not explicitly block the installation of Google Play Service/Store. Google did not 'ban' Amazon devices. While FireOS is a heavily skinned Android variant it does not meet the criteria to have Google Play Service pre-installed given the presence of a competitive app store. All of the major players operate this way. It would be nice to see Amazon offer Fire devices in two flavors (one with a generic Android build including the Play Store at a higher price point) but there is no economic incentive to do so. If you want that buy an Onn or Samsung device.

I don't like the fact that they're trying to tell us that fireos is not an Android when it clearly is, heck it even removed split screen feature, which is easy to change if you have root access but still, their policy is super strange, I would like fireos if it had option to change launcher and remove lockscreen completely (I don't really like lock screens because I want to jump straight to content where I left it) otherwise fireos is well optimised for this tab, I currently have HD8 with Lineage 14 and it is a super stable ROM, will test 16 when graphics problem is solved

Sent from my Fire using Tapatalk

 

[BXM500]

I believe they hid something on root level, so I don't think using only adb is going to solve any problem, I would suggest waiting 2 weeks to 1 month and unlock tablet

Sent from my Fire using Tapatalk

Thank you for the clarification. Yes, I'll be waiting for the bootloader unlock, twrp, root and lineage os port like most of us.

 

[Xinto]

Thank you for the clarification. Yes, I'll be waiting for the bootloader unlock, twrp, root and lineage os port like most of us.

I believe engineers missed something with HD10 2019 too so we can put bootrom to download mode as we did so with HD8

Sent from my Fire using Tapatalk

 

[DB126]

I don't like the fact that they're trying to tell us that fireos is not an Android when it clearly is...

Semantics. Just because FireOS is based on Android does not mean it has to behave like AOSP or contain the same feature set. Most consumer (and many commercial) products share a common base that is customized to the sellers liking. I appreciate you and many others have a different opinion on the matter but it falls into the 'want' category. Amazon, Samsung and a handful of other manufactures that heavily skin Android are (mostly) playing by the rules established by Google. If there was sufficient consumer demand for an alternative Amazon or some other manufacture would sell it.

---------- Post added at 01:26 PM ---------- Previous post was at 01:16 PM ----------

I believe engineers missed something with HD10 2019 too so we can put bootrom to download mode as we did so with HD8

Engineers? All recent Amazon devices are re-purposed commodity grade hardware already on the market. Amazon isn't going to heavily invest in writing custom bootloaders/kernels, radio firmware, etc beyond flipping switches to disable functionality (eg: nutter fastboot command set). FireOS is simply a skinned Android variant that angles users toward Amazon's ecosystem. Stated another way, it makes little economic sense to lock down hardware to deter the 1% enthusiast club that make up XDA and similar boards.

 

[Xinto]

Semantics. Just because FireOS is based on Android does not mean it has to behave like AOSP or contain the same feature set. Most consumer (and many commercial) products share a common base that is customized to the sellers liking. I appreciate you and many others have a different opinion on the matter but it falls into the 'want' category. Amazon, Samsung and a handful of other manufactures that heavily skin Android are (mostly) playing by the rules established by Google. If there was sufficient consumer demand for an alternative Amazon or some other manufacture would sell it.

Well, I didn't say that they need to integrate AOSP to their tabs, I say that they should make Android more Android-y or something like that, I don't mind skinning Android as I myself love OneUI, btw your idea that they should make something with Google play available is a good idea, probably something like "Amazon Fire HD 10 Google Play edition" it would be a lot better
Sent from my Fire using Tapatalk

 

[DB126]

Well, I didn't say that they need to integrate AOSP to their tabs, I say that they should make Android more Android-y or something like that, I don't mind skinning Android as I myself love OneUI, btw your idea that they should make something with Google play available is a good idea, probably something like "Amazon Fire HD 10 Google Play edition" it would be a lot better

I personally believe Amazon is quite happy with their Android skin (aka FireOS) just the way it is with only minor evolutionary tweaks. Been more-or-less the same for the past 4 major revisions. Keep in mind the economic drivers; becoming more "Android-y" doesn't necessarily drive sales in the Amazon ecosystem. Tech enthusiasts see it differently but that's not the demographic they're after.

Contributed to a sustained OT rush (guilty as charged); let's bring this thread back to what the thread title suggests.

 

[Michajin]

If anyone is interested, install alternate launcher and disable amazons, i used trebuchet cm 13.... INSTALL LAUNCHER FIRST....

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

 

[gosch2912]

Hi. Does there exits a list where I can assing what command Is for what app? I can not assing every command to a known app ( e.g. com.amazon.tahoe or com.amazon.iris)

 

[Kctucka]

Why would they come back? I also disabled Amazon Appstore and OTA updater.

Using this method only disables the packages for user 0. They are still active at a system level, and are capable of restoring themselves. Amazon has always done this.

You could potentially run a startup script with init.d script support, or run it however often the packages restore.

Hi. Does there exits a list where I can assing what command Is for what app? I can not assing every command to a known app ( e.g. com.amazon.tahoe or com.amazon.iris)

adb shell
pm list packages

Edit NVM, completely misunderstood. This list from the last fire 10 should be mostly the same:

https://docs.google.com/spreadsheets/d/19KAt3uzWB-13F9utW56ITkZaPBNIYF_jYl2tvQV0hrc/htmlview