The Android status bar says Emergency Calls Only despite an active subscription. The following process separates a transient symptom from a repeatable configuration or compatibility issue without relying on a full reinstall.
What the user actually sees
Primary symptom. The Android status bar says Emergency Calls Only despite an active subscription. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
Separate configuration from service faults
The first hypothesis is a mismatch in the failing path. Check a regional carrier outage and verify SIM/eSIM line state and plan validity. The second is a lower-level state that the interface may not show: inspect registration status, network mode and roaming restrictions with the carrier. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this Android issue, capture Android version, carrier policy and device-management state and compare the same phone on a trusted alternative network or with a controlled setting. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
Read the evidence
| What you observe | What it suggests | Focused response |
|---|---|---|
| The Android status bar says Emergency Calls Only despite an active subscription | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Check a regional carrier outage and verify SIM/eSIM line state and plan validity. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Reseat a removable SIM only with power off or re-enable the intended eSIM line and restart network registration. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Inspect registration status, network mode and roaming restrictions with the carrier. |
Before changing anything: Preserve local saves, accounts and recovery options; prefer reversible settings and documented vendor procedures over factory reset. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks check a regional carrier outage and verify SIM/eSIM line state and plan validity. The Advanced path investigates inspect registration status, network mode and roaming restrictions with the carrier. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Capture the reproducible symptom
The Android status bar says Emergency Calls Only despite an active subscription. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the Emergency Calls Only on Android: Check SIM and Carrier Registration guide.
Check a regional carrier outage and verify SIM/eSIM line state
Check a regional carrier outage and verify SIM/eSIM line state and plan validity. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust reseat a removable SIM only with power off or re-enable
Reseat a removable SIM only with power off or re-enable the intended eSIM line and restart network registration. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify normal calls and cellular data function outside
Normal calls and cellular data function outside emergency-only mode. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Inspect supporting logs
Collect the error text or state relevant to Emergency Calls Only on Android: Check SIM and Carrier Registration. Record Android version, carrier policy and device-management state; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect registration status, network mode and roaming restrictions
Inspect registration status, network mode and roaming restrictions with the carrier. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
Rule out related configuration drift
Where practical, compare the same phone on a trusted alternative network or with a controlled setting. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Verify and record results
Normal calls and cellular data function outside emergency-only mode. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
What not to assume
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, inspect registration status, network mode and roaming restrictions with the carrier. Compare the same phone on a trusted alternative network or with a controlled setting rather than adding random fixes on top of one another.
For escalation, retain Android version, carrier policy and device-management state, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish the same phone on a trusted alternative network or with a controlled setting from a general outage without repeating risky actions.
Verification procedure
Pass condition: Normal calls and cellular data function outside emergency-only mode. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
Prevention and next steps
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Preserve local saves, accounts and recovery options; prefer reversible settings and documented vendor procedures over factory reset.
Prevent recurrence: Document the working correction: Reseat a removable SIM only with power off or re-enable the intended eSIM line and restart network registration. Retain the accepted result (normal calls and cellular data function outside emergency-only mode) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
Normal calls and cellular data function outside emergency-only mode. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Check a regional carrier outage and verify SIM/eSIM line state and plan validity. Then choose the smallest supported intervention: reseat a removable SIM only with power off or re-enable the intended eSIM line and restart network registration. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Inspect registration status, network mode and roaming restrictions with the carrier. Do not include credentials or private customer data.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.