Under Tools
PoR & OTA guides
One page per OTA failure code. What causes it, what to do, and when retrying makes it worse.
0x01
PoR 01 — RC/CC/DS failed
Why SIM OTA returns status 01: wrong KID, stale MSISDN–IMSI inventory, or checksum computed over the wrong byte range for SMS-PP.
Read →0x02
SCP80 CNTR low — counter recovery
PoR 02 means your server counter is behind the card. Parallel senders, DB restore, and accepted-but-recorded-failed commands are the usual origins.
Read →0x06
PoR 06 — unidentified security (clear-text diagnostic)
Status 06 is sent unciphered with no RC/CC/DS — the best diagnostic PoR. Check KIc/KID key version equality, PoR rules, then CHL.
Read →0x08
PoR 08 — more time needed (do not retry)
Status 08 is not a failure. Retrying produces a spurious CNTR low because the original command was already accepted and counted.
Read →0x00
PoR 00 is not APDU success
Status 00 means the secured packet was accepted. The RFM or RAM APDU inside can still have failed. Check additional response data before marking the card done.
Read →0x09
PoR 09 — TAR unknown during migration
Status 09 means no application is registered for that TAR. On a mixed-vendor campaign that is often a segmentation result: those cards still need the install campaign.
Read →On-prem
On-site OTA when you cannot put keys in a cloud
Small MVNO and IoT connectivity operators that already own SMSC traffic: on-site RFM/RAM over SMS, no platform fee on that traffic, OPC/Ki stay on site. Not an eSIM RSP.
Read →Stuck on a campaign?
Failing OTA needs a plan, not a bigger blast
Decoders explain a code. Thousands of the same code need inventory, SPI and segmentation work.