What is Reddit's opinion of NFC TagInfo by NXP?

From 3.5 billion Reddit comments

First of all, you should be more specific about what you actually have in terms of readers and cards.

If you want to play with FeliCa, you should get yourself an RC-S380 and use it with something like nfcpy: read the documentation at http://nfcpy.readthedocs.org/en/latest/topics/get-started.html#read-and-write-tags to get started.

You will also find NXP's TagInfo (https://play.google.com/store/apps/details?id=com.nxp.taginfolite&hl=en) helpful for dumping the contents of cards you want to examine.

For FeliCa cards, FeliCa Lite-S (RC-S966) can be bought in small quantities, and documentation is easily available without NDA.

If you want to do the "real stuff" (FeliCa Standard: mutual authentication, defining your own card formats, etc), go and buy the FeliCa Enterprise SDK.

If you want to clone a card, you should indicate what kind of card you want to clone, but in general the system is designed to resist this.

if nintendo wont replace it, then you're outta luck. if your phone has a NFC reader you can download a nfc app such as NFC Tag Info to see if it can read it. it should at least register something if the chip is functional, even if the data is not present. if it still doesn't register theres really nothing you can do at that point.

I think the type of card issued by Wise depends on the country where it's issued, even though it always behaves as a debit card.

If you're curious about the card type, this Android app shows some information of NFC tags, including contactless cards: https://play.google.com/store/apps/details?id=com.nxp.taginfolite

My wise card says "Visa Credit Card" / "Label: Visa Prepaid".

I don't immediately see correlation between the printed card number and the UID.

Can you post the full card data?

If you have an NFC enabled android phone, you could one of many apps (NFC Taginfo, or MIFARE++ Ultralight would likely work fine) to dump the full contents of the card (if it's not password protected).

Different tags will have different methods of cloning, and some can't be cloned at all. The NXP Taginfo app will be able to tell you what kind this is

Do you know what types of cards they are? Can you read them with https://github.com/ikarus23/MifareClassicTool/ ? What does https://play.google.com/store/apps/details?id=com.nxp.taginfolite&hl=en&gl=US say about them?

Some tags are encrypted, but sometimes they use a default key you can find out.

Emulating cards is hard, it's generally easier to copy the tag and you can put a sticker on your phone case (away from the nfc antenna).

On Android, get the app NFC TagInfo by NXP. Open the app, make sure your NFC is enabled, and then scan the tag. On the IC Info tab you should see "IC type: NTAG215" if the tag is Amiibo compatible.

Curious if the NXP TagInfo app picks up anything from the key.

https://play.google.com/store/apps/details?id=com.nxp.taginfolite

It pulls a lot of info from my Neo.

I'm not familiar with that program, so I cannot say if it's accurate or not. If you have an Android phone with NFC, I would suggest downloading NXP TagInfo and scanning the card with it so you can see what it says under 'IC Type' in the info tab.

Depends what you wanna do. If its just see detailed info about a tag and what's on it, check out TagInfo.

NB: The Note 3 has its NFC chip built into the battery - if you've got an aftermarket battery you may not have an NFC circuit.

I'm trying to create an app very similar to NFC TagInfo by NXP, where a ViewPager contains multiple Fragment's. Furthermore, when a new NFC tag is discovered, the content inside the Fragment's changes accordingly.

How do I go about changing fragment content?

I have so far implemented matching tabs in my application by following the guide: Google Play Style Tabs using TabLayout

An Android app by NXP called NFC TagInfo.

A really useful tool!

You can download an app for your phone called "NFC TagInfo by NXP" and it'll read some of the contents of your wristband that gets sent to the scanners if you hold it to the back of your phone. You can also read (some of the unencrypted) data on hotel keys and things like credit cards with that app too.

Anyways using that you can see it's using this chip: https://www.nxp.com/products/rfid-nfc/mifare-hf/mifare-ultralight/mifare-ultralight-ev1:MF0ULX1. Note that there are multiple levels of security inside the chip to prevent you from just straight up cloning it to get into ACL for free.
And yes, it works essentially like you described where each wristband has a specific ID associated with it that is read by the scanners, and then that ID is tied on the backend servers to your credit card and PIN and emergency contacts. So none of that information is ever stored on the actual wristband.
I doubt the service is hosted by Amex though since that's not their main business but I'm not really sure.

It will really depend on what RFID chip the ID card uses. What cloner did you get? If it is a 125 kHZ cloner like this (often known as "Chinese blue cloners"), try reading the ID card. If it reads, then it is 125 kHZ and you can write to a T5577 chip.

If you have an Android phone, install NEX TagInfo or NFC Tools.

If it is MIFARE Classic, then also great, you can clone it to a "magic" MIFARE Classic 1K tag. Gen 1 magic tags will require a Proxmark3, however, gen 2 magic tags can be written with MIFARE Classic Tool. For further reading, https://forum.dangerousthings.com/t/magic-mifare-chips/6696

If it is MIFARE Ultralight, it's likely UID based and there are magic tags that you can clone to, however, I'm not very familiar with those.

If it is MIFARE DESFIRE, FeliCa, etc., they are encrypted and can't be cloned (at least no one is known to have figured how to hack it).

Those are the most common tags that I'm familiar with. There's other tags like Icode, Iclass, etc. that I'm not familiar with, so I'm not sure if they can be cloned or not. If you can't read it with your phone or a 125 kHz cloner, it's likely an older protocol that will be more difficult figuring it out.

I was using this app to try to read basic info about the tags. Some RFID tags were just never detected when I tried.

> Except it's not, and you need a NFC-F device to use it. https://support.google.com/androidpay/answer/6224811

No. You need an Osaifu-Keitai device, exactly as Google states. You already have an NFC-F device, it's called a Nexus 6P. We'll prove that later, hold on.

I've figured out your misunderstanding. You've confused NFC-A and NFC-F, and are of the impression that you can read a FeliCa card on an NFC-A device in some kind of limited mode.

Let's set the story straight. All NFC controllers support both NFC-A and NFC-F. It's a certification requirement.

NFC-A uses the ISO-14443-A physical layer: 106 to 848 kbps, 100% ASK modulation with modified Miller encoding from card to reader and Manchester encoding in the other, little-endian.

NFC-F uses the FeliCa physical layer: 212 or 424 kbps, 8-30% ASK modulation (Sony says 10% because that's the average) with Manchester encoding in both directions, big-endian, FeliCa framing format.

Since the physical layers and framing formats are different, if you can read a FeliCa card - even its ID - you are using NFC-F.

Still have doubts? The NFC controller in the Nexus 6P is an NXP PN548. The datasheet for this isn't public, but a whole load of Android devices used a PN544 - the earlier version - and the datasheet for that is here: https://www.nxp.com/documents/leaflet/75016890.pdf

Note the clear reference to FeliCa support in the PN544 datasheet. Not just the ISO or JIS standard - but the FeliCa(R) trademark. I think NXP knows what they mean when they say their chip supports FeliCa.

Let's go further. Grab NXP's TagInfo application (https://play.google.com/store/apps/details?id=com.nxp.taginfolite&hl=en), run it on your Nexus 6P, and touch a FeliCa card. You'll clearly see the technology type described as 'android.nfc.tech.NfcF'. Now, use TagInfo's settings to disable NFC-F polling and try to scan the card again. It won't work.

Back to Sony's diagram that you point out: you'll see that ISO 18092 spans ISO-14443-A and FeliCa physical layers. That's because it's an application layer protocol. What you will also see on that diagram is that all of the FeliCa stuff uses the FeliCa interface, ie: NFC-F. There is no interoperability with NFC-A at all, as you'll quickly realize with a TagInfo session. What you've got is an NFC controller that can do both. The PN548 can do a few others as well; NFC-B, and a couple more obscure proprietary contactless implementations like iCODE and Topaz.

So, to sum up:

• Your Nexus 6P supports FeliCa. The Nexus 5 supports FeliCa. So do millions of other Android devices - because every NFC device supports NFC-F.

• FeliCa without encryption is still FeliCa. But even if you insist that encryption is a requirement, those NXP ICs can also handle encrypted services if the card issuer wants it that way; for example, I could sign up with Sony to issue my own FeliCa Standard cards, with my own system code (0xD00D, naturally: the Common Area used by Edy is 0xFE00, the Cybernetics area used by most transport cards is 0x0003, etc) and using those keys successfully mutually authenticate with my own cards and read/write encrypted data. The reason it's not done is because of trust issues, not technical issues. The PN544 supports 'FeliCa RF' emulation, which means that the host has to handle all of the framing, but it's possible to emulate a FeliCa card if you can get at the keys.

• NFC-F is not Osaifu-Keitai. You need an Osaifu-Keitai device for Edy. Most Osaifu-Keitai devices are NFC-F compliant. Some early Android smartphones are not; they have only Osaifu-Keitai support, no NFC. The Osaifu-Keitai API is also different (applications read and write from PON, CEN, RFS, RFW, etc) - the Edy application, and Android Pay itself as a front-end for Edy - uses those interfaces, not the Android 'NfcF' API.

• Your idea of 'FeliCa' appears to be just Osaifu-Keitai. That is a specific implementation where FeliCa Networks manages access to a Mobile FeliCa IC. The keys required are not available unless you use a FeliCa Networks approved SE. There are two. One is the Mobile FeliCa IC, the other is the Apple implementation using a NXP controller with embedded secure element. The whole thing that stops Edy working on non-Japanese phones is access to the keys and not anything about the hardware or the protocol. Access to the keys is controlled by the business model of Osaifu-Keitai, because FeliCa Networks manages the Common Area service. FeliCa Networks doesn't manage every service: Suica is actually a separate 'virtual card' (in FeliCa terminology, an 'Area') and the keys are managed by JR directly.

• You can get NFC controllers from other manufacturers besides NXP and Sony, such as the Broadcom BCM20797 in the Nexus 5. Broadcom will tell you the BCM20797 handles FeliCa too. Of course it does, because NFC requires NFC-A and NFC-F.

• Google caused a lot of confusion by rebranding an Edy front-end as Android Pay.

Now, please go and play with NFC-F on your Nexus 6P, and quit it with the 'but Apple!', and 'but Sony!' stuff. The only special thing about Osaifu-Keitai is access to a set of keys required for the trust hierarchy of Edy to work. It's not about special chips: they are just where the business rules say the keys for the system have to be held. It would be more than possible for an HCE-F implementation to be done with access to the keys brokered by a cloud-based service, just as it is for HCE-A Android Pay. That's why HCE-F has been introduced; it's coming. Wait and see.