Jump to content

Apps deliberately refusing to work on modded devices

From Consumer Rights Wiki
Revision as of 18:09, 10 June 2025 by JP (talk | contribs) (Format examples section for different operating systems and add a "Main article" link (WIP))

Article Status Notice: This Article is a stub

Notice: This Article Requires Additional Expansion

This article is underdeveloped, and needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Issues may include:

  • This article needs to be expanded to provide meaningful information
  • This article requires additional verifiable evidence to demonstrate systemic impact
  • More documentation is needed to establish how this reflects broader consumer protection concerns
  • The connection between individual incidents and company-wide practices needs to be better established
  • The article is simply too short, and lacks sufficient content

How you can help:

  • Add documented examples with verifiable sources
  • Provide evidence of similar incidents affecting other consumers
  • Include relevant company policies or communications that demonstrate systemic practices
  • Link to credible reporting that covers these issues
  • Flesh out the article with relevant information

This notice will be removed once the article is sufficiently developed. Once you believe the article is ready to have its notice removed, visit the Discord (join here) and post to the #appeals channel, or mention its status on the article's talk page.

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.[1][2]

How it works

Phones and PCs include a Trusted Platform Module [3]: 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

Android[1]

Main article: 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[4][5]

References

  1. 1.0 1.1 "Apps & Games need PI". XDA Forums.
  2. "Configure API responses". Google.
  3. "Trusted Platform Module". Archived from the original on 2016-08-03.
  4. "PlayIntegrity Verification failed - ChatGPT / Bugs". OpenAI Developer Community.
  5. "Question - ChatGPT error: Preauth Playintegrity verification failed". XDA Forums.