No Service on a Leased Device: SIM, Baseband, or Carrier — a Three-Link Triage

Published 2026-11-15 · LuckyMDM Blog

Bottom line: when a subscriber reports "no service", the device itself is only one of three candidate causes. The chain runs SIM, baseband, carrier side — and the triage starts with two actions that take 3 minutes per unit: dial *#06#, then read the Modem Firmware line in Settings, General, About. An IMEI that pops up and a firmware line that is populated point the investigation away from hardware; an empty firmware line points straight at it.

The three links in the chain

The SIM link is an identity document, not a component: its typical failures are state changes on the carrier's account — suspension, deactivation, an expired eSIM profile — and the card itself stays healthy. The baseband link is the cellular processor, where the IMEI is burned in; its failures are physical, mostly solder joints stressed by drops or liquid exposure, and a device with a failing baseband often still runs Wi-Fi — that asymmetry is a diagnostic in itself. The carrier link is the database side: the registration request is compared against the account state, the IMEI blocklist, and the lock list, and every failure on this link happens off the device. Replacing the handset solves nothing there.

Two self-checks and one reference SIM

Dial *#06#: the IMEI popping up means the baseband is responding. Then Settings, General, About: the Modem Firmware line carries a version string precisely because it is not static text — the system queries the baseband, and the baseband answers at every boot. The two self-checks take 2 minutes per unit combined. An empty line is the classic criterion for a non-answering baseband, which is why it beats repair folklore like "dropped phones with no service are usually reflow jobs": it is an existence check on the reporting chain itself, not a statistical guess. The reference SIM closes the triage in three steps, 10 minutes per unit: a known-good SIM swapped in, service returns — suspicion moves to the original card or account; no change — the reference SIM goes into a second known-good device; healthy there but dead here — the chain is pinned to the device side.

What the ledger fields do during triage

LuckyMDM (Sichuan Starlight Network LLC) sets the last-heartbeat timestamp and the current ICCID as the first pair of fields a no-service ticket reads: a device whose heartbeat keeps updating while cellular is down goes to SIM-side triage, not to the tamper-investigation queue. The two queues differ by an order of magnitude in cost, and entering the wrong one burns the hours first.

Offline for management is not offline for cellular

A device with cellular down is not necessarily unreachable. Management commands ride whatever network channel is available; when Wi-Fi is up, the device stays online and the heartbeat keeps flowing. A ticket pattern of "customer reports no bars, heartbeat normal" is a link problem, not a control problem — and the reverse, a stopped heartbeat, belongs to the offline-investigation chain with its own evidence fields. Two investigation lines, separated by two fields.

Observation table

ObservationFirst suspicionDecided by
*#06# shows no IMEIBaseband linkEmpty Modem Firmware line; hardware direction
Firmware populated, no serviceSIM or carrier sideThree-step reference-SIM swap
Service returns with reference SIMOriginal card or accountAccount status and suspension check
Reference SIM dead here, alive elsewhereDevice sideSend for repair with the triage record attached
Intermittent serviceCoverage or hardwareSame-spot retest against a second device

The fourth row is where the triage ends: the repair ticket leaves with the three steps documented, and the repair bench starts from the pinned link instead of reproducing from zero.

The arithmetic of triage-first

A 500-unit fleet logging 3 to 5 no-service tickets a month — roughly 1 percent of the fleet — spends under 1 hour a month on triage at 10 minutes per unit. The two wrong directions cost differently: treating an account problem as hardware runs a repair cycle of 3 to 5 days at 400 dollars or more, plus the subscriber swap; treating a hardware problem as an account problem sends the subscriber to the carrier shop twice, and the ticket cycles at least two rounds. On a lease that runs 24 months, a misdiagnosed unit can cycle through the wrong queue for most of a term before anyone reads the right field. Both branches are unbounded; the triage that prevents them is capped at 10 minutes per unit. The structural reason: the check is embedded in the intake of the ticket, while the cost of skipping it is discovered after the work is already spent.

Three misconceptions

Misconception one: no service means baseband first. The order is backwards: the SIM and carrier checks cost minutes, the hardware check costs days. Triage runs from the cheap link to the expensive one — reference SIM first, repair bench last.

Misconception two: service restored closes the ticket. A suspended account recovers when payment lands, but the cause of the suspension stays unexamined — the same unit re-enters the ticket queue the next month. Closing requires reading the account state, not the signal icon.

Misconception three: offline in the console means tampering. Offline means the device is not online right now; a dead cellular line, no Wi-Fi, and a powered-off device all render identically in the console. The last-heartbeat and ICCID fields separate the branches before anyone picks a queue.

Boundaries and where this does not apply

eSIM-only units have no slot, so the reference-SIM swap becomes deleting and re-downloading the eSIM profile — same logic, different gesture. Long-term roaming SIMs carry account states that only the home carrier can read; a local carrier shop will not see the full picture. And units with a board-level repair history can show an intermittent Modem Firmware line while calls work — for those, the verdict needs the repair-history field from the ledger stacked on top, not the settings line alone.

FAQ

Does *#06# work on every unit? Mainstream iOS and Android units respond to it. Where a custom build ignores the code, the About page's IMEI and Modem Firmware lines answer the same question.

Is an empty Modem Firmware line a death sentence? It is a direction, not a verdict: it says the baseband is not reporting, and the repair bench still owns the distinction between a reflow job and something worse. Triage pins the link; it does not write the repair order.

Does a blocklisted unit get signal with its own SIM? Typically no — the blocklist bars the IMEI from registration regardless of whose SIM is inserted. That differs from a lock, which rejects other carriers' SIMs; two different rejections, keyed to the same number.

Which fields belong on the repair ticket? The last-heartbeat timestamp, the current ICCID, and the three triage steps' outcomes. With those, the bench skips baseline reproduction and starts at the pinned link.

Does Wi-Fi-yes-cellular-no affect management? Command delivery is unaffected while any network channel is up. The honest handling is flagging the unit as cellular-abnormal in the ledger until the link recovers, rather than merging it into the device-fault pile.

The checklist

All Articles