Consumer Rights Wiki - User contributions [en]

Apps deliberately refusing to work on modded devices

2026-01-09T20:42:47Z

Magnusmaster: Added new Vietnam banking regulation

Apps running on [[Android]] and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{Cite web |title=Apps & Games need PI |url=https://xdaforums.com/t/4677050/ |url-status=live |archive-url=https://archive.ph/xgtcn |archive-date=8 Jan 2026 |website=XDA Forums}}</ref><ref>{{Cite web |title=Configure API responses |url=https://developer.android.com/google/play/integrity/setup#configure-api |website=Google}}</ref>

Effective March 1st 2026, all banking apps in Vietnam must detect whether the app is running on a device that has an unlocked bootloader, is rooted or has ADB enabled and cease to function if that is the case <ref>{{Cite web |title=[Discussion] The root-and-mod-hiding / fingerprint-spoofing / keybox-stealing cat-and-mouse game |url=https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/page-118#post-90441375}}</ref>

==How it works==
Some phones and PCs include a [[Trusted computing|Trusted Platform Module]] <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=3 Aug 2016}}</ref>: a chip independent from the device's CPU which can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered with, and if so will block functionality or refuse to work altogether. If done properly, remote attestation is impossible to spoof, even by the owner of the device.

==Why it is a problem==
The owner of the phone is unable to do the following (while continuing to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services (see [[Forced app download]]), and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, as they then couldn't interact with those businesses which require or heavily encourage their app.

==Examples==

===Android<ref name=":0" />===
{{Main|Google Play Integrity API}}
*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator
*ChatGPT<ref>{{Cite web |title=PlayIntegrity Verification failed - ChatGPT / Bugs |url=https://community.openai.com/t/1267945 |website=OpenAI Developer Community}}</ref><ref>{{Cite web |title=Question - ChatGPT error: Preauth Playintegrity verification failed |url=https://xdaforums.com/t/4737618/ |website=XDA Forums}}</ref>
==References==
{{reflist}}

[[Category:Common terms]]

List of phones that do not allow bootloader unlock

2025-07-27T17:57:03Z

Magnusmaster: /* Examples[3] */

A bootloader is a program that runs when the phone turns on and loads the operating system. <ref>{{Cite web |title=GNU Grub website |url=https://www.gnu.org/software/grub/index.html}}</ref> Most phones lock the bootloader by default, which means that a new bootloader or operating system can't be installed on the phone. <ref>{{Cite web |title=Lock and unlock the bootloader |url=https://source.android.com/docs/core/architecture/bootloader/locking_unlocking |website=Android Open Source project}}</ref>

==How it works==
Some manufacturers do not allow unlocking the bootloader even if the phone is not under a contract. Some manufacturers allow to unlock the bootloader on some regions, or require a payment or an online connection to unlock the phone. Some manufacturers may void the warranty or block certain features permanently if the bootloader is unlocked

==Why it is a problem==
If the bootloader cannot be unlocked the operating system can't be modified in any way which is not allowed by the manufacturer.

==Examples<ref>{{Cite web |last= |first= |title=Bootloader wall of shame |url=https://github.com/melontini/bootloader-unlock-wall-of-shame |website=GitHub}}</ref>==

*Huawei
*HMD Global/Nokia
*Vivo/IQOO
*ZTE
*Meizu
*Asus
*Alcatel
*Apple
*Energizer
*Cat
*Sharp
*Doogee
*TCL
*Coolpad
*Realme (on some regions)
*OPPO (outside China)
*Xiaomi (China only)
*Samsung
*HTC
*Motorola (on some devices)
*Google Pixel (Verizon)

==References==
{{reflist}}

[[Category:Common terms]]

List of phones that do not allow bootloader unlock

2025-06-14T01:03:21Z

Magnusmaster: Created page with "A bootloader is a program that runs when the phone turns on and loads the operating system. <ref>{{Cite web |title=GNU Grub website |url=https://www.gnu.org/software/grub/index.html}}</ref> Most phones lock the bootloader by default, which means that a new bootloader or operating system can't be installed on the phone. <ref>{{Cite web |title=Lock and unlock the bootloader |url=https://source.android.com/docs/core/architecture/bootloader/locking_unlocking |website=Android..."

A bootloader is a program that runs when the phone turns on and loads the operating system. <ref>{{Cite web |title=GNU Grub website |url=https://www.gnu.org/software/grub/index.html}}</ref> Most phones lock the bootloader by default, which means that a new bootloader or operating system can't be installed on the phone. <ref>{{Cite web |title=Lock and unlock the bootloader |url=https://source.android.com/docs/core/architecture/bootloader/locking_unlocking |website=Android Open Source project}}</ref>

==How it works==
Some manufacturers do not allow unlocking the bootloader even if the phone is not under a contract. Some manufacturers allow to unlock the bootloader on some regions, or require a payment or an online connection to unlock the phone. Some manufacturers may void the warranty or block certain features permanently if the bootloader is unlocked

==Why it is a problem==
If the bootloader cannot be unlocked the operating system can't be modified in any way which is not allowed by the manufacturer.

==Examples<ref>{{Cite web |last= |first= |title=Bootloader wall of shame |url=https://github.com/melontini/bootloader-unlock-wall-of-shame |website=GitHub}}</ref> ==

* Huawei
* HMD Global/Nokia
* Vivo/IQOO
* ZTE
* Meizu
* Asus
* Alcatel
* Apple
* Energizer
* Cat
* Sharp
* Doogee
* TCL
* Coolpad
* Realme (on some regions)
* OPPO (outside China)
* Xiaomi (China only)
* Samsung (USA only)
* HTC
* Motorola (on some devices)

==References==
{{reflist}}

[[Category:Common terms]]

Talk:Applications deliberately refusing to work on modded devices

2025-06-12T01:26:08Z

Magnusmaster: Magnusmaster moved page Talk:Applications deliberately refusing to work on modded devices to Talk:Apps deliberately refusing to work on modded devices: Change page title

#REDIRECT [[Talk:Apps deliberately refusing to work on modded devices]]

Talk:Apps deliberately refusing to work on modded devices

2025-06-12T01:26:08Z

Magnusmaster: Magnusmaster moved page Talk:Applications deliberately refusing to work on modded devices to Talk:Apps deliberately refusing to work on modded devices: Change page title

== Needs expansion ==

This article is a little short and needs more explanation. Once more is added, we can get the stub notice taken off. [[User:Atsumari|Atsumari]] ([[User talk:Atsumari|talk]]) 14:27, 10 June 2025 (UTC)

== Needs a better title ==

Self-explanatory, the title is rather lengthy for what seems like a theme article... [[User:JamesTDG|JamesTDG]] ([[User talk:JamesTDG|talk]]) 01:27, 11 June 2025 (UTC)

Applications deliberately refusing to work on modded devices

2025-06-12T01:26:08Z

Magnusmaster: Magnusmaster moved page Applications deliberately refusing to work on modded devices to Apps deliberately refusing to work on modded devices: Change page title

#REDIRECT [[Apps deliberately refusing to work on modded devices]]

Apps deliberately refusing to work on modded devices

2025-06-12T01:26:08Z

Magnusmaster: Magnusmaster moved page Applications deliberately refusing to work on modded devices to Apps deliberately refusing to work on modded devices: Change page title

Apps running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{Cite web |title=Apps & Games need PI |url=https://xdaforums.com/t/4677050/ |website=XDA Forums}}</ref><ref>{{Cite web |title=Configure API responses |url=https://developer.android.com/google/play/integrity/setup#configure-api |website=Google}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip independent from the device's CPU which can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered with, and if so will block functionality or refuse to work altogether. If done properly, remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continuing to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services (see [[Forced app download]]), and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, as they then couldn't interact with those businesses which require or heavily encourage their app.

==Examples==

===Android<ref name=":0" />===
{{Main|Google Play Integrity API}}
*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator
*ChatGPT<ref>{{Cite web |title=PlayIntegrity Verification failed - ChatGPT / Bugs |url=https://community.openai.com/t/1267945 |website=OpenAI Developer Community}}</ref><ref>{{Cite web |title=Question - ChatGPT error: Preauth Playintegrity verification failed |url=https://xdaforums.com/t/4737618/ |website=XDA Forums}}</ref>
==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T03:12:32Z

Magnusmaster: fix references

Apps running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{Cite web |title=Apps & Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forums}}</ref><ref>{{Cite web |title=Configure API responses |url=https://developer.android.com/google/play/integrity/setup#configure-api |website=Google}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip independent from the device's CPU and can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services (see [[Forced app download]]), and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples<ref name=":0" />==

*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator 

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T03:10:27Z

Magnusmaster:

Apps running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{title=Apps&Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forum}}</ref><ref>{{title=Configure API responses (optional) |url=https://developer.android.com/google/play/integrity/setup#default}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip independent from the device's CPU and can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services (see [[Forced app download]]), and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples<ref name=":0" />==

*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator 

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T03:09:16Z

Magnusmaster: /* Why it is a problem */

Apps running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{title=Apps&Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forum}}</ref><ref>{{title=Configure API responses (optional) |url=https://developer.android.com/google/play/integrity/setup#default}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services (see [[Forced app download]]), and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples<ref name=":0" />==

*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator 

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T03:07:54Z

Magnusmaster:

Apps running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{title=Apps&Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forum}}</ref><ref>{{title=Configure API responses (optional) |url=https://developer.android.com/google/play/integrity/setup#default}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples<ref name=":0" />==

*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator 

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T02:52:52Z

Magnusmaster:

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{Cite web |last= |first=Vision |title=Apps&Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forum}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples<ref name=":0" />==

*Google Wallet
*VPN by Google for Pixel
*Netflix
*McDonald's App
*Google Messages (RCS does not work when device is modded)
*Uber Driver
*Twitter/X
*Twilio Authy Authenticator 

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T02:46:46Z

Magnusmaster: Add more links

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.<ref name=":0">{{Cite web |first=Vision |title=Apps&Games need PI |url=https://xdaforums.com/t/apps-games-need-pi-list.4677050/ |website=XDA Forum}}</ref>

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform Module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-date=2016-08-03}}</ref>: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

== Examples<ref name=":0" /> ==

* Google Wallet
* VPN by Google for Pixel
* Netflix
* McDonald's App
* Google Messages (RCS does not work when device is modded)
* Uber Driver
* Twitter/X
* Twilio Authy Authenticator 

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T02:40:05Z

Magnusmaster:

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module <ref>{{Cite web |title=Trusted Platform module |url=http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1 |archive-url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1}}</ref>: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-10T02:37:23Z

Magnusmaster: Add link

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module [http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1]: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called remote attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly remote attestation is impossible to spoof, even by the owner of the device.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that block modded devices)

*update the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are left unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-09T23:59:47Z

Magnusmaster:

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called hardware attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly hardware attestation is impossible to spoof, even by the device's owner.
==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that refuse to support modded devices)

*upgrade the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-09T23:58:45Z

Magnusmaster:

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module
<references>
<ref>{{Cite web |first=IBM |title=TPM - Trusted Platform Module |url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1}}</ref>
</references>
<nowiki>:</nowiki> a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called hardware attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly hardware attestation is impossible to spoof, even by the device's owner.

==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that refuse to support modded devices)

*upgrade the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-09T23:57:43Z

Magnusmaster:

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module
<references>
<ref>{{Cite web |title=TPM - Trusted Platform Module (IBM) |url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1}}</ref>
</references>
<nowiki>:</nowiki> a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called hardware attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly hardware attestation is impossible to spoof, even by the device's owner.

==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that refuse to support modded devices)

*upgrade the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-09T23:56:05Z

Magnusmaster:

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module
<references><ref>{{Cite web |title= |url=https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1}}</ref>https://web.archive.org/web/20160803203400/http://www-01.ibm.com/support/docview.wss?uid=pos1R1003970&aid=1</references>
<nowiki>:</nowiki> a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called hardware attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly hardware attestation is impossible to spoof, even by the device's owner.

==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that refuse to support modded devices)

*upgrade the device operating system once it is no longer supported by the device manufacturer
*use alternative operating systems such as Linux or other Android-based operating systems that add new features
*remove all bloatware
*access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]

Apps deliberately refusing to work on modded devices

2025-06-09T23:51:06Z

Magnusmaster: First draft

Applications running on Android and potentially other operating systems can detect if the device has been modded and refuse to function if that is the case. This can happen if the device allows the user to run applications as root or administrator, has an unlocked bootloader or runs a different operating system than the one provided by the manufacturer.

==How it works==
Phones and PCs include a Trusted Platform Module: a chip that controls the device's main processor can only run software signed by the device manufacturer. This chip allows applications to use a technique called hardware attestation to detect if the operating system has been tampered in any way and in such a case block functionality or refuse to work altogether. If done properly hardware attestation is impossible to spoof, even by the device's owner.

==Why it is a problem==
The owner of the phone is unable to do the following (while continue to use applications that refuse to support modded devices)

* upgrade the device operating system once it is no longer supported by the device manufacturer
* use alternative operating systems such as Linux or other Android-based operating systems that add new features
* remove all bloatware
* access all data stored on the device

Since many businesses and governments require their customers to download their proprietary application to their phones in order to use their services, and many of those applications refuse to work on a modded device, people are unable to modify their phone as they wish, or else they wouldn't be able to interact with those businesses that require or heavily encourage their app.

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

[[Category:Common terms]]