Skip to Content
Platform.Ontology

Root and jailbreak detection

Apps infer root or jailbreak from files, props and attestation; neither OS gives a direct flag.

Gets silentlyDevice detailsIntegrityAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can guess if your phone is rooted or jailbroken, but cannot be sure

Apps infer root or jailbreak from files, props and attestation; neither OS gives a direct flag.

Rooted or jailbroken phones weaken the sandbox. Banking and game apps lock them out; privacy tool users get caught as false positives.

What it can and can't do

What the user does: Nothing. The app checks when it opens, or when you sign in or pay

It can

  • Look for files and tools that rooted or jailbroken phones often have
  • Check Android build tags and Play Integrity results
  • Block or limit the app if it decides your phone is modified

It cannot

  • Get a direct yes or no; neither system gives a flag
  • Catch phones that hide the change, such as Magisk on Android
  • Catch every modified phone; the checks can be evaded
  • See what else you changed on the phone

How it differs between platforms: Android adds Play Integrity verdicts from Google. iPhone apps use guesses only.

On Android and iPhone

AndroidiPhone
StatusPartialPartial
First versionAndroid 1.0 (API 1)iOS 2.0
Permission or entitlementNot listednone
Protection levelnonenone
How access is grantednonenone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyNone listedNone listed
APIFile checks for su, Build.TAGS test-keys, Play Integrity verdictsHeuristic and evadable
NotesChecks are heuristic and evadable (Magisk hides)None

Data you get

What comes back: Rooted flag
Shape: boolean
How often: On check

FieldTypeUnitRangePrecision
rootedbooleanNonetrue, false1 bit

Technical limits

  • Heuristic only

The story

What it is

Apps look for signs that a phone has been unlocked at a deep level.

For you

You never see the check. If your phone is rooted or jailbroken, banking and game apps may refuse to open. The reason is safety, but privacy tool users can get blocked by mistake.

For makers

A modified phone can fake taps, hide malware and steal logins. Makers use it to protect money and fair play. Neither phone gives a direct flag, so apps guess from files and cloud attestation.

Where you see it

TypeExampleApps
bankingA bank app locks you out on a rooted phone to stop malware from reading the screen.None named
gamesA shooter game bans players on jailbroken phones using speed and aim cheats.None named
paymentsA tap to pay wallet refuses to work on a rooted phone.Google Wallet
mediaA streaming app lowers video quality to standard on a rooted phone to protect licences.Netflix
enterpriseA work app blocks company mail on a jailbroken phone.None named
securityA fraud tool raises the risk score of any login from a modified device.None named

Risks

  • Blocks privacy tool users
  • Can be fooled

Android and iPhone in short

  • Android: Apps use Play Integrity verdicts, and rooted phones often fail them.
  • iPhone: App Attest and file checks, but Apple gives no direct jailbreak flag.

What the platform says

  • Google: Play Integrity API. Developer pitch: check that your app runs on a genuine, unmodified Android device from Google Play.
  • Apple: App Attest. Developer pitch: confirm requests come from a real, unmodified copy of your app on an Apple device.

Good uses and abuse

Legitimate uses

  • Fraud prevention

Known abuse

  • Lock out power users

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits2Rough identifying entropy, when known
  • Play Integrity verdicts. Can ask Google whether the phone and app look genuine and unmodified
  • App Attest. Can prove its requests come from the real app on a real iPhone

Same idea on the web

Sources

How well checked: Inferred from related behavior.

On this page