I was wondering if all the NFC tags are compatible with all phones.. P.EX. i was about to get
http://www.ebay.com/itm/10pcs-NFC-S...130?pt=LH_DefaultDomain_0&hash=item231dcadbaa
10pcs for around 10$ but are they going to be compatible with xperia S which i own? Is this the same as the original tags included in the box?
Sorry if this is a NOOB question!!!!
cdrov said:
I was wondering if all the NFC tags are compatible with all phones.. P.EX. i was about to get
http://www.ebay.com/itm/10pcs-NFC-S...130?pt=LH_DefaultDomain_0&hash=item231dcadbaa
10pcs for around 10$ but are they going to be compatible with xperia S which i own? Is this the same as the original tags included in the box?
Sorry if this is a NOOB question!!!!
Click to expand...
Click to collapse
Those will work. They aren't the same.
The tags included with the phone are Mifare Ultralight based. These are NFC Forum Type 2 tags with 64 bytes of memory (48 writable).
The ones you have linked are Mifare Classic 1K. These contain 1K or memory (~716 writable). These are *not* NFC Forum type tags. All this means is that they aren't guaranteed to work with all future iterations of devices. Blackberries, for example, don't do so well with 1K tags. Android devices though don't seem to have any problem with them.
Thank you, i am going to get them, and i ll get back here to post the results
wich devices support NFC?
Hey guys do Samsung Galaxy S2 GT-i9100 support NFC? if yes why my device dont support the NFC?
I am on Resurrection Remix ics V2.2
do it disabled or what's the problem?
Won't work on the 9100
From what I have read only special made 9100s will work with NFC. The one that I know will work is the 9100P. So if you have that one you are in luck. The other ones I don't think will. Also the Note will work, but that is a whole other phone.
I have a bunch of blank NFC tags from Texas Instruments (about 40 in total) in varying sizes (both physical and storage-wise), shapes, and casings. While I'm able to read them on my Galaxy S3, none of the apps I've tried are able to write to them.
After some poking around, I determined that these are all NFC-V tags (ISO/IEC 15693 compliant), which are apparently not NDEF-compatible. While the Android OS supports them, it provides no functionality to interface with them other than transcieve (raw read/write). Lacking the knowledge to write my own interface app, I'm reduced to research, questions, and experimentation.
Does anybody have any experience using Android to write to NFC-V tags? If so, what were you able to store and how did you do it?
https://play.google.com/store/apps/...1bGwsMSwxLDEsImNvbS5ueHAubmZjLnRhZ3dyaXRlciJd
try this app, it might work for you.
Thanks for the reply. That's actually the first app I tried, and no matter what type of data I try to write, I get the following: ow.ly/c5ubE
I've been putting a lot of my effort into getting this (ow.ly/c5uaz) app to work since it specifies NFC-V and ISO/IEC 15693 compatibility, but I still can't get it to write any data (NDEF or raw). From reading up on NFC-V, I get the impression this may be an issue with one-bit vs two-bit addressing and the app assuming which it is wrongly, but I have no way to confirm that. That said, the source for that app is available for download from its developer here (ow.ly/c5uaR) if anybody is interested in picking it apart.
Aren't they locked?
I can't give you more clues as I've just started reading about NFC.
daniel_loft said:
Aren't they locked?
I can't give you more clues as I've just started reading about NFC.
Click to expand...
Click to collapse
Not that I'm aware. I can read them, and the access conditions allow writes. TI also advertises that they're shipped unlocked and unprotected.
Having done a fair amount of research since, it seems the issue is that NFC-V tags are not part of the NFC Forum standard, and there's no standard way to store NDEF data on them. Short of writing my own app with a proprietary method of doing so, I think the only option for those tags is to wait until NXP, TI, the NFC Forum, etc decide on a standard, then all the NFC Android apps update appropriately.
Fortunately, I've since gained access to the NXP Semiconductors samples ordering system, and their MiFARE tags are differently complicated but NDEF-formatable, so I'm making some headway.
rowanator0 said:
Not that I'm aware. I can read them, and the access conditions allow writes. TI also advertises that they're shipped unlocked and unprotected.
Having done a fair amount of research since, it seems the issue is that NFC-V tags are not part of the NFC Forum standard, and there's no standard way to store NDEF data on them. Short of writing my own app with a proprietary method of doing so, I think the only option for those tags is to wait until NXP, TI, the NFC Forum, etc decide on a standard, then all the NFC Android apps update appropriately.
Fortunately, I've since gained access to the NXP Semiconductors samples ordering system, and their MiFARE tags are differently complicated but NDEF-formatable, so I'm making some headway.
Click to expand...
Click to collapse
Hm, I belive that NFCIP-2 specifies something according to vicinity cards, but I don't remember what exactly. The main problem is though that the NFC chip of the SG3, which should be PN544 (not 100% sure, but I tihnk its the same as in the predecessor, and NXP didn't release PN547 yet) does not have the capability to write vicinity cards. I think there were datasheets on this though.
Damastus said:
Hm, I belive that NFCIP-2 specifies something according to vicinity cards, but I don't remember what exactly. The main problem is though that the NFC chip of the SG3, which should be PN544 (not 100% sure, but I tihnk its the same as in the predecessor, and NXP didn't release PN547 yet) does not have the capability to write vicinity cards. I think there were datasheets on this though.
Click to expand...
Click to collapse
Can you define "vicinity" in this context? If you're referring specifically to NFC-V, you may be on to something. If you just mean proximity cards in general, though, I am able to write to MiFARE tags. Furthermore, as I understand it, with the right software behind an NFC reader/writer, you can theoretically read/write just about anything that uses 13.56MHz, simply as a result of the way the active field works.
Additionally, you seem to be correct about the NFC chip in the S3 (see ow.ly/foV15), but according to the NXP spec sheet for that chip (ow.ly/foUYj), it should be able to read/write tags that meet the same ISO standards as my TI tags. Apologies for the shortened URLs; I don't have enough posts yet to post links and that seems to be the only way to get around it.
rowanator0 said:
Can you define "vicinity" in this context? If you're referring specifically to NFC-V, you may be on to something. If you just mean proximity cards in general, though, I am able to write to MiFARE tags. Furthermore, as I understand it, with the right software behind an NFC reader/writer, you can theoretically read/write just about anything that uses 13.56MHz, simply as a result of the way the active field works.
Additionally, you seem to be correct about the NFC chip in the S3 (see ow.ly/foV15), but according to the NXP spec sheet for that chip (ow.ly/foUYj), it should be able to read/write tags that meet the same ISO standards as my TI tags. Apologies for the shortened URLs; I don't have enough posts yet to post links and that seems to be the only way to get around it.
Click to expand...
Click to collapse
ISO15693 is the vicinity card standard (basicly the same as the other ISO14443 standard, but those ISO15693 cards have a bigger range up to several meters). Cards that can be read via NFC-V are vicinity cards / tags. Though I checked again, you are right, coming from the data sheet, it should be able to read and write them.
Btw, your idea to be able to read and write anything that uses 13.56MHz is to idealistic. There are many kinds of cards and standards with many different protocols (many of them are even proprietary, like Mifare Classic, Legic, iClass etc.) involved in this. These protocols are most of the time implemented on the hardware level. One of the reasons for that is the fact that there are also very strict timings cards, tags and reader have to comply to. Going up layers of software can be to slow in that case.
You can read most of the ISO 14443 A and B compliant cards for example, but Mifare Classic can only be read with phones that feature chips that implement the ISO 14443-3 A protocol. The PN544 can read Mifare Classic, because hes manufactured by NXP, the same company that holds the patents and rights of the Mifare Classic standard.
Damastus said:
ISO15693 is the vicinity card standard (basicly the same as the other ISO14443 standard, but those ISO15693 cards have a bigger range up to several meters). Cards that can be read via NFC-V are vicinity cards / tags. Though I checked again, you are right, coming from the data sheet, it should be able to read and write them.
Btw, your idea to be able to read and write anything that uses 13.56MHz is to idealistic. There are many kinds of cards and standards with many different protocols (many of them are even proprietary, like Mifare Classic, Legic, iClass etc.) involved in this. These protocols are most of the time implemented on the hardware level. One of the reasons for that is the fact that there are also very strict timings cards, tags and reader have to comply to. Going up layers of software can be to slow in that case.
You can read most of the ISO 14443 A and B compliant cards for example, but Mifare Classic can only be read with phones that feature chips that implement the ISO 14443-3 A protocol. The PN544 can read Mifare Classic, because hes manufactured by NXP, the same company that holds the patents and rights of the Mifare Classic standard.
Click to expand...
Click to collapse
Which leaves us pretty much back where we started.
As for my "WORKS WITH EVERYTHING" comment, you're absolutely right. I should have specified ISO14443/15693 (and even then my original statement would be wrong). Basically, I was referring to the fact that if you have the command set for something that operates on the 13.56MHz frequency, you can in theory write software to interface with it, as you can send and receive pretty much any raw data you want. However, you're right--there are plenty of 13.56MHz devices, both passive and active, that some active modules simply cannot communicate with.
Hello there, people,
I'm opening this thread in order to facilitate the other peoples' attempts to get free NFC tags. And for this I invite everybody to contribute with name of the firm/site address, what did you get, how long did it take to get them and if you payed anything (for ex. shipping), how did you get them.
I promise to keep the first post updated with the info that pops up in the future posts.
Thanks for helping!
Source: NFC NetStore
What I got: 10 Circus Mifare Ultralight, 10 BullsEye Mifare Ultralight, 10 BullsEye NTAG203, 1 on-metal sticker, 1 locked business card, 5 locked BullsEye Mifare Ultralight (on a poster)
Time to get: 3 days (1 envelope from Finland to Romania)
Price: 0
How: wrote them an e-mail, they asked me to order this and to tell them a few details about how am I going to use the tags.
Step by step on how to obtain these free samples?
We are offering free samples to promote our product. Just PM me or go to our website - Contact Us page and let us know how many tags you are looking for and what you intend to do with them.
NFC-SMARTAGS said:
if you want free sample you can have it simply to contact my shop
i can send you sticker just for 10 peoples
send a letter with stamps and your adress to : NFC-SMARTAGS.COM 18 rue Montpensier 64000 Pau FRANCE
Click to expand...
Click to collapse
Hi.can you send to Israel too?
Thanks.
Sent from my GT-I9300 using xda premium
Just thought I'd add to this and say what a gent the guy over at Shop4NFC is. There are very few places left where you get something for free!!
It took about a week to come and now that they have i can start experimenting
Thanks again Shop4NFC !!!!
Regards
Umar
Need NFC TAGS for evaluation
Hello friends,
I am from India, i want to know is there any company or anyone who can provide some NFC TAGS for evaluation purpose(for some small read/write functions)... in India....
Thank you
Robogar, is the offer still valid? Do you happen to have rectangular tags?
nfc expert, do you happen to have rectangular tags?
Hello, I'm wondering if you're still producing NFC tag samples? I was planning to test out this storage system that uses RSA keys stored on NFC tags to decrypt drives.
i know precious little about the nitty-gritty of RFID or NFC stuff, but i'm wondering if there's such a thing as an RFID or NFC spoofer (emulator) that works at the standard nfc frequency of 13.56mhz, and uses the iso 14443 standard.
i'm wondering if it's possible to spoof those sky-landers figures, which use nfc. it's currently impossible to write one figure onto another because of access restrictions on the first little block in the rfid tag. and I'm not aware of any commercially available generic RFID tags that have *quite* the same hardware as the figures.
I believe the sky-landers use MiFare Classic tags, and have a locked block 0 (or UID), in that block 0 is the code which says which character they are.
is it in principle, possible to "project" a fake MiFare tag from an nfc equipped phone, also with a fake UID?
for that matter, are there any breakout boards that can do this, like an arduino shield?
*BUMP*
I'd also like to pull this off with my G-Nex...
The breakout board I use is from Adafruit.com which at the moment is hooked up to a raspberry pi. You could theoretically spoof a tag if you will. But I don't follow the logic to do so. I think what you want to do is more like cloning and siphoning. Check over on the Kali Linux forums, new version of backtrack they are working on something that does just that. I read a little into it about how they were basically bumping into people at a conference or getting in range of someone with there phone out texting or not paying attention and we're able to do just that.
Sent from my SAMSUNG-SGH-I747 using xda premium
Osbor said:
i know precious little about the nitty-gritty of RFID or NFC stuff, but i'm wondering if there's such a thing as an RFID or NFC spoofer (emulator) that works at the standard nfc frequency of 13.56mhz, and uses the iso 14443 standard.
i'm wondering if it's possible to spoof those sky-landers figures, which use nfc. it's currently impossible to write one figure onto another because of access restrictions on the first little block in the rfid tag. and I'm not aware of any commercially available generic RFID tags that have *quite* the same hardware as the figures.
I believe the sky-landers use MiFare Classic tags, and have a locked block 0 (or UID), in that block 0 is the code which says which character they are.
is it in principle, possible to "project" a fake MiFare tag from an nfc equipped phone, also with a fake UID?
for that matter, are there any breakout boards that can do this, like an arduino shield?
Click to expand...
Click to collapse
In theory one is able to emulate a NXP MiFare Classic card using an Android device. However, the firmware of the NFC chip is programmed to produce a different UID with each transmission, therefore the new firmware for the chip would have to modified to produce a static UID. If you want to learn more of the capabilities of the NXP NFC chips used in most Android devices, navigate to NXP's website and there is plenty of info.
From The Q, Of Course
live the life you love, love the life you live
Hey everyone,
While looking online for pinouts, I was able to come across some noteworthy docs about the NXP chipsets including the PN532 and PN554
Within the document for the PN532, commands (Which I assume are either Java/ dalvik and/or op-code instruction set/ library) are mentioned. Considering the the PN554, the NFC chipset that is used in the Samsung Galaxy line of phones, and perhaps even more non-Samsung devices, I'm assuming that the commands should work on the PN554 chips.
For those circuit benders, I've complied an excel spreadsheet of the Pinouts and the block diagram/BGA for the PN544 in an attempt to create a reference document for this forum.
Also attached is a 7zip file of the PN532 manual and the entire PN544 reference document
Hope this helps out the forum
Joe