Skip to main content

SIM Card Tools — Filesystem, APDU & eSIM

Beyond discovering and presenting SIMs, OmniWeb gives you a set of low-level card tools that reach through any reader on any agent to talk to the card directly: browse and edit its file system, send raw APDUs by hand, watch the live APDU trace of a remote-SIM session, and manage eSIM profiles on an eUICC. This page is the operations guide for those tools.

← Operations Guide

These tools sit alongside — and reuse — the existing SIM features. Start here for the bigger picture:

  • SIM Bank — the inventory: which SIMs are in which readers across every agent. Every tool on this page targets a reader from that inventory, and the SIM Bank's per-slot actions deep-link straight into them.
  • SIM Images (SAIP Profile Packages) — saving a read-out file system as a portable image, and browsing/diffing saved images.
  • Remote SIM & Virtual SIM — presenting a SIM (real or virtual) to a modem over the network via card emulators.
  • OTA SIM Management — the same file-level editing, but reaching a card over the air with secured (03.48 / SCP80) packets instead of a local reader.

All four tools below live in the sidebar under the SIMs group.

One reader, one consumer at a time​

A physical PC/SC reader can only be driven by one thing at a time. Whenever a tool on this page needs a reader, and something else already holds it — another operator reading it, or a live remote-SIM banking session presenting it to a modem — the tool shows who holds it and why, and offers an explicit Take over. There is no silent kick: taking over cancels the other session (and, for a banking session, disconnects that SIM↔cardem link). Editing/sending is a control action gated behind the SIM-bank control permission — without it you can view readers but not drive cards.

SIM Filesystem Explorer​

Pick a reader and read the whole file tree of its card: the MF, DF.GSM / DF.TELECOM, ADF.USIM and ADF.ISIM and all their EFs, with every readable file decoded into named fields. A progress bar shows the walk ("read X of Y files — EF.…") since a full read touches many files.

  • Search the tree by file code (FID), short name, or description — a search for "Emergency Call Codes" finds EF.ECC, not just 6FB7.
  • PIN-protected files are flagged, never read — the explorer will not burn PIN retries.
  • Edit an EF (with the control permission): the detail pane offers a schema-driven form (decoded fields, typed) where available, falling back to raw hex. Writing is destructive and asks for confirmation. Where an EF needs authentication, use Verify CHV/ADM first — it tests a PIN/ADM key against the card (reporting remaining tries, never burning the last retry) and, once proven, reuses it for the write. Saved keys for a card's ICCID are offered automatically from the SIM key store.
  • Save image snapshots the decoded tree as a named SIM Image; Compare with image diffs the live card against a saved one; Saved images opens the image library. You can also open a saved image as a tree (?image=<id>) to browse a card you no longer have in a reader.

The reader must be free (not held by a remote-SIM session) — or you can Take over as above.

APDU Terminal​

The APDU Terminal is a hand console for the card: type a raw APDU in hex, send it to the card in a chosen reader, and see the response decoded — the command's INS name, the status word and its meaning, and an expanded interpretation of any response data (an FCP TLV tree, decoded EF fields, or an AUTHENTICATE result). Canned buttons (SELECT MF, STATUS, READ BINARY, GET RESPONSE, …) fill common commands. Input is whitespace/colon-tolerant and validated (whole bytes, at least CLA/INS/P1/P2).

Two modes:

ModeBehaviourUse for
Single-shotEach APDU is self-contained; the card resets to the MF between sends.One-off probes.
SessionOpens a persistent, exclusive card session so state (selection, authentication) persists across APDUs — a SELECT then a READ BINARY works; a VERIFY shares its auth with a later UPDATE. The reader stays held until you close the session.Stateful sequences.

The SIM Bank's per-slot APDU action deep-links here with that exact reader preselected. Same one-consumer/Take-over rules apply.

APDU Log​

Where the terminal is you driving one card, the APDU Log is a passive live trace of the command/response APDUs exchanged between a modem and a (remote) SIM through the remote-SIM / cardem chain. Turn on capture and it tails the exchange: each row pairs a modem→card command with its decoded status word, plus the same response decoding as the terminal (FCP tree, EF fields, ATR/reset events). You can pause the view (capture keeps running), filter by command/hex/SW, and auto-scroll.

Use it to see what a modem is actually asking the SIM during an attach or an IR.38 test run — which files it selects, where a VERIFY fails, whether an AUTHENTICATE succeeds — without instrumenting the modem. It pairs naturally with Remote SIM, which sets up the modem↔SIM link the log then traces.

eSIM (LPA)​

The eSIM tool manages an eUICC — a physical eSIM chip in one of your readers — through the agent's Local Profile Assistant (LPA). An eUICC holds several profiles but only one is active at a time.

  • eUICC card — shows the chip's EID.
  • Installed profiles — every profile on the card: its state (active/disabled), nickname, provider, name, and ICCID. Per profile you can enable (make it the active eSIM), disable, rename (nickname), or delete (removes it from the eUICC — irreversible, so it confirms first).
  • Download a profile — pull a new profile from an operator's SM-DP+ and install it onto the card, either from a whole activation code (LPA:1$smdp.example.com$MATCHING-ID) or from a split SM-DP+ address + Matching ID, with an optional confirmation code.

This is for eSIM (eUICC) cards specifically — for classic SIM/UICC file editing use the Filesystem Explorer above, and for editing a card remotely use OTA.

Last updated on