Is PoR 09 a failure in a migration?

Usually it is information. Route 09 cards to the install campaign instead of retrying the migrate command.

Could the TAR simply be wrong?

Yes. Check the three-byte TAR in the command header against the card vendor. The packet decoder shows TAR without uploading the hex.

Guide · TS 102 225 · 0x09

PoR 09 — TAR unknown during migration

TAR Unknown.

ETSI TS 102 225 (Release 19) + 3GPP TS 31.115
Full reference
All parsers

TAR unknown is how a live migration discovers who does not yet carry the applet. Retrying the same RAM command on those cards fails identically. Split the estate: cards that answer 09 go to install; cards that accept the TAR go to the migrate command. Confirm the TAR against TS 101 220 annex D and the vendor manual — vendor TARs vary and the manual wins. Decode the command packet to see which TAR you actually sent.

Usual cause

The card has no application registered against the Toolkit Application Reference you addressed. Either the TAR is wrong, or the application is genuinely not on that card, or it is present but not registered for the toolkit event you are using.

What to do

Verify the TAR against TS 101 220 annex D and the card vendor manual — vendor TARs vary and the manual wins. On a migration this code is usually informative rather than an error: it is how you discover which cards do not yet carry your applet, so treat it as a segmentation result and route those cards to the install campaign instead of retrying.

TS 101 220 annex D

Parsers — nothing uploaded

Read the packet. Then talk.

Hex stays in the browser. Do not paste production keys. If the estate is still stuck after the decode, that is the programme.

TS 102 225 / TS 31.115

Packet decoder

SPI, key versions, TAR, counter, CHL — command or PoR.

Tools page

Auto Command Response

Packet, in hex

Paste a packet, or load one of the examples above.

TS 102 225 table 5

PoR status lookup

Cause, action, whether retrying can help.

Full table

Look up a code

Hex, with or without 0x

Questions

Is PoR 09 a failure in a migration?: Usually it is information. Route 09 cards to the install campaign instead of retrying the migrate command.
Could the TAR simply be wrong?: Yes. Check the three-byte TAR in the command header against the card vendor. The packet decoder shows TAR without uploading the hex.

Mid-campaign?

A live estate

Rescue, retry policy and mixed-estate forensics — or a CSV in MoreOTA if you already run the server.

Discuss rescue MoreOTA server