i have a galaxy s3, and today i got an infineon myd nfc (SLE 66R32P), but i can't store anything on it. i tried to use the programs nfc retag, nfc task launcher and the nxp tag writer, but none work. i've attached some screenshots.
(the text on the first says: "tag not supported. it's no NDEF-tag or NDEF-formatable tag.)
i know that it is not write-protected. the documentation of the tag says:
documentation
NFC Tag Operation
• Support of NFC Forum™ - Type 2 Tag Operation Specification
• Up to 2048 bytes NFC memory available
– organized in static or dynamic memory structure
– pre-defined memory size for NFC Forum™ Type 2 Tag Operation (up to two 1 kByte sectors)
• Pre-configured NFC memory with empty NDEF message (INITIALIZED state)
Click to expand...
Click to collapse
wergor said:
i have a galaxy s3, and today i got an infineon myd nfc (SLE 66R32P), but i can't store anything on it. i tried to use the programs nfc retag, nfc task launcher and the nxp tag writer, but none work. i've attached some screenshots.
(the text on the first says: "tag not supported. it's no NDEF-tag or NDEF-formatable tag.)
i know that it is not write-protected. the documentation of the tag says:
Click to expand...
Click to collapse
Ok, can only speak for NFC ReTag
the tag specification says : "Pre-configured NFC memory with empty NDEF message (INITIALIZED state)" ---> so it should be already NDEF pre-formated and the NFC ReTag error message "already NDEF-formated" should be correct .... Have you tried to write a special NFC ReTag tag ?
btw. you can pm me in german for further support , if you want ....
ascsa said:
Ok, can only speak for NFC ReTag
the tag specification says : "Pre-configured NFC memory with empty NDEF message (INITIALIZED state)" ---> so it should be already pre-formated and the NFC ReTag error message "already NDEF-formated" should be correct .... Have you tried to write a special NFC ReTag tag ?
btw. you can pm me in german for further support , if you want ....
Click to expand...
Click to collapse
i tried that too, it says "Tag is write protected, blocked or not formated! nothing done! you can try to format the tag if the error persists!"
wergor said:
i tried that too, it says "Tag is write protected, blocked or not formated! nothing done! you can try to format the tag if the error persists!"
Click to expand...
Click to collapse
Hmmm Ok,
unfortunately this is the NFC ReTag message, if the app could not write your tag .... Normally it occurs when the tag is not NDEF formated or you write-protected the tag ... I assume this is a new tag, and you never write-protected it .... ?
Strange, according to the tag specs this tag should work ... unless i missed something obviously ....
EDIT: had a look at the tag documentation, found this on page 7:
Infineon's my-d™ NFC family convinces with fast communication speed and high robustness. Furthermore, the
SLE 66RxxP family can be operated as NFC Forum™ Type 2 Tag.
and this on page 11:
The my-d™ NFC are delivered with pre-configured NFC memory; the Capability Container bytes are programmed
and the data area holds an empty NDEF message; this represents the NFC Forum™ Type 2 Tag INITIALIZED
state within the tag life cycle. With this pre-configuration the my-d™ NFC can be immediately used in NFC
infrastructures.
For further details regarding the NFC initialization of my-d™ NFC please refer to the Data Book and the Application
Note “How to operate my-d™ devices in NFC Forum™ Type 2 Tag infrastructures” available at Chip Card &
Security " Attention: This pre-configuration can be over-written to any value. Initial shipments of the my-d™ NFC
devices have been delivered without this configuration."
So, perhaps you got one of these initial shipment tags .....
ascsa said:
Hmmm Ok,
unfortunately this is the NFC ReTag message, if the app could not write your tag .... Normally it occurs when the tag is not NDEF formated or you write-protected the tag ... I assume this is a new tag, and you never write-protected it .... ?
Strange, according to the tag specs this tag should work ... unless i missed something obviously ....
EDIT: had a look at the tag documentation, found this on page 7:
Infineon's my-d™ NFC family convinces with fast communication speed and high robustness. Furthermore, the
SLE 66RxxP family can be operated as NFC Forum™ Type 2 Tag.
and this on page 11:
The my-d™ NFC are delivered with pre-configured NFC memory; the Capability Container bytes are programmed
and the data area holds an empty NDEF message; this represents the NFC Forum™ Type 2 Tag INITIALIZED
state within the tag life cycle. With this pre-configuration the my-d™ NFC can be immediately used in NFC
infrastructures.
For further details regarding the NFC initialization of my-d™ NFC please refer to the Data Book and the Application
Note “How to operate my-d™ devices in NFC Forum™ Type 2 Tag infrastructures” available at Chip Card &
Security " Attention: This pre-configuration can be over-written to any value. Initial shipments of the my-d™ NFC
devices have been delivered without this configuration."
So, perhaps you got one of these initial shipment tags .....
Click to expand...
Click to collapse
Yes, i think it is one of those... guess i need a nfc reader for pc to initialize the tag...
wergor said:
Yes, i think it is one of those... guess i need a nfc reader for pc to initialize the tag...
Click to expand...
Click to collapse
yep, but I´m not sure if anybody other than the manufacturer can initialize these tags ...
Anyway ,you should be able to use this tag (without initializing) with NFC ReTag ... writing a special NFC ReTag tag is not possible, but you only need that for better dispatching process and everything else should work without writing something to the tag
ascsa said:
yep, but I´m not sure if anybody other than the manufacturer can initialize these tags ...
Anyway ,you should be able to use this tag (without initializing) with NFC ReTag ... writing a special NFC ReTag tag is not possible, but you only need that for better dispatching process and everything else should work without writing something to the tag
Click to expand...
Click to collapse
well, the tag IS initialized, but only with zeros (see screenshots) and not with a NDEF message.
documentation said:
The my-d™ NFC are delivered with pre-configured NFC memory; the Capability Container bytes are programmed
and the data area holds an empty NDEF message; this represents the NFC Forum™ Type 2 Tag INITIALIZED
state within the tag life cycle
Click to expand...
Click to collapse
as i understand it, "initializing" (what i want to do) just means writing any ndef message to the tag (and set those "capability container bytes").
if i had an nfc reader i could test this, i already found a program (for pc) can write NDEF messages to tags. but i somehow doubt that works. it's never that easy maybe android just doesn't support that particular tag...
Related
Is there some way to copy one RFID NFC tag to another blank NFC tag with the SGS3?. I have 2 active NFC tags that I would like to mess around with and see if I can actually copy them and get the same access as my authentic ones offers.
So down to the question. Is it possible to copy the entire contents of an NFC chip and write it to another one with an app, and in that case which one?
bump* I'd like to know as well
copy a tag
"NFC Smart Q supports reading or copying a tag"
I just read this, didn't use this app.
There must be more nfc apps in Google's android shop, doing this trick.
I cannot post links, i'm sure you will find it.
MeX_DK said:
Is there some way to copy one RFID NFC tag to another blank NFC tag with the SGS3?. I have 2 active NFC tags that I would like to mess around with and see if I can actually copy them and get the same access as my authentic ones offers.
So down to the question. Is it possible to copy the entire contents of an NFC chip and write it to another one with an app, and in that case which one?
Click to expand...
Click to collapse
Depends. If it's a tag without any protection, yes.
If it's a tag with crypto, such as most RFID door entry systems, contactless credit cards, subway cards - no, they're intentionally designed to prevent such things. (Specific systems may have been hacked, but in general, these are not copyable.)
"Not protected" means I can edit them as I want right??
So if I can solve the encryption manually than I can change my info on my NFC card with the help of my cellphone.
Is that right??
https://play.google.com/store/apps/details?id=com.skjolberg.nfc.clone2. Try this..... Works for me
Sent from my Nexus 4
carhustler said:
https://play.google.com/store/apps/details?id=com.skjolberg.nfc.clone2. Try this..... Works for me
Sent from my Nexus 4
Click to expand...
Click to collapse
Agreed - may not work for everything, but definitely one of the better tag cloning apps.
Hello,
I am new at nfc so please do not judge me
I have one question:
It is possible to write dokumrent path in nfc tags for example:URL.
but on the path will be security level as:
login
pasword
And after you type your login and password it is automatically opened your dokument.
I was tried to write this way, but after I type login and password the link is not active longer and I have to search manually the document in my data base.
Waiiting fot you answers
For any information I would be thankfull.
P.S. It is possible to do this with my samsung galaxy s3?
Hi,
due to my app NFC ReTag, I experiment a lot with write-protected NFC tags (like lift tickets/ski pass, library cards, company badges etc.) and I have a large collection of these tags. One of the latest tags I got, is a ski pass with android.nfc.tech.NfcV tag tech (no other tech on it!). This tag works as expected on all of my testing devices exept the Nexus 10 (couldn´t test on a nexus 4 so far, but I assume it will be the same).
On the nexus 10 the tag not only isn´t recognized, but also breaks the NFC function ....After taping this tag to the device, NFC is not longer working on the device -> any other tag will not be recognized ! ...
It´s not a big deal, because disabling NFC, and enabling it again will fix it (using the lock screen will also do the trick!) but this is annoying ...
Checked my nfc tag collection and found another NfcV tag with the same behavior. The nexus 7 with JB 4.2.1 has NO problems, so I think this related to the Broadcom NFC controller ....
...and unlike the Mifare classic tags issues, this is not a lack of support (which is OK, because of the proprietary NXP protocol) but an annoying bug from my point of view.
ascsa said:
Hi,
due to my app NFC ReTag, I experiment a lot with write-protected NFC tags (like lift tickets/ski pass, library cards, company badges etc.) and I have a large collection of these tags. One of the latest tags I got, is a ski pass with android.nfc.tech.NfcV tag tech (no other tech on it!). This tag works as expected on all of my testing devices exept the Nexus 10 (couldn´t test on a nexus 4 so far, but I assume it will be the same).
On the nexus 10 the tag not only isn´t recognized, but also breaks the NFC function ....After taping this tag to the device, NFC is not longer working on the device -> any other tag will not be recognized ! ...
It´s not a big deal, because disabling NFC, and enabling it again will fix it (using the lock screen will also do the trick!) but this is annoying ...
Checked my nfc tag collection and found another NfcV tag with the same behavior. The nexus 7 with JB 4.2.1 has NO problems, so I think this related to the Broadcom NFC controller ....
...and unlike the Mifare classic tags issues, this is not a lack of support (which is OK, because of the proprietary NXP protocol) but an annoying bug from my point of view.
Click to expand...
Click to collapse
Is an exception being thrown in the log (either Android internal class or jni)? Can you capture that if it is?
krohnjw said:
Is an exception being thrown in the log (either Android internal class or jni)? Can you capture that if it is?
Click to expand...
Click to collapse
Nope, logcat shows nothing ....no NativeNfcTag tag, no dispatching message etc. ...
ascsa said:
Nope, logcat shows nothing ....no NativeNfcTag tag, no dispatching message etc. ...
Click to expand...
Click to collapse
Anything from BrcmNfcJni?
krohnjw said:
Anything from BrcmNfcJni?
Click to expand...
Click to collapse
nope .... nothing ....if I clear the log, and scan the tag, I don´t get a single entry ...
If anyone's curious we have confirmation it's a known issue. Some NfcV tags don't implement an optional part of the protocol that the Broadcom stack is looking for and it's hanging as a result. It's a known issue, there's a fix for it and it will be pushed in an update eventually.
Android 4.2.2 update ...still the same issue...so perhaps with the next update
Official Bug link?
krohnjw said:
If anyone's curious we have confirmation it's a known issue. Some NfcV tags don't implement an optional part of the protocol that the Broadcom stack is looking for and it's hanging as a result. It's a known issue, there's a fix for it and it will be pushed in an update eventually.
Click to expand...
Click to collapse
Is there an 'official' bug raised for that issue?
h ttps://code.google.com/p/android/issues/list
8y5 said:
Is there an 'official' bug raised for that issue?
h ttps://code.google.com/p/android/issues/list
Click to expand...
Click to collapse
afaik, no. I made some logs and krohnjw discussed this issue directly with the responsible person ...
solved in JB 4.3
OK, just for the sake of completeness: Seems that the android JB 4.3 Update fixed the problem. So, apparently the broadcom NFC stack got the update.
and to the broadcom/android guys: I know how you "fixed" it ... not ideal, but it works
I've been seeing posts on Google+ of people having trouble to use Android Beam and some tags. The antenna is under the X of Nexus on this device, which is different from the previous Nexus 7 (which was more towards the top). Still, I'm curious if more people have trouble with Beam/NFC tags.
haven't had any trouble yet. only sent a few pictures back and forth from my galaxy nexus, but everything has transferred just fine. haven't tried web pages, videos, or apps though.
Yeah, I've seen mentions of beam issues, too. No problems here, though.
Sent from my Galaxy Nexus
Worked normal using super beam( I recommend that over android beam anyways)
Sent from my Nexus 7 using Tapatalk 4 Beta
Fine for beam
Yeah, same here. No problems. I don't use NFC much, but tested it a little with my new N7 HD (or whatever we're calling it) and my SGS III and it they both made a sound (phone buzzed too) no problem. I'd just as soon use the QR part of super beam anyway since my good batteries (zero lemon!) don't have NFC.
It does not work with me I tried under X and every where but still wont work
I tested with Nexus 4, Galaxy s4, and Nexus 4 Wireless Charger
I tried it with my old Nexus 7, and I had to hold them together and wiggle them around for several seconds before it beeped. This is probably because I had no idea the antenna was down in the middle. I'll have to try the middle of the new one against the top of the old one and see if it is more immediate.
I returned my Nexus 7 due to the qi not working on it, prior to doing that though I had checked out the nfc with both a Razr Maxx HD and a DNA... worked fine. After exchanging the Nexus7 with a new one, my qi charge now works but the NFC doesn't. I table and/or phone makes a beep and the "Touch to send" screen pops up but no files or images send. Not too worried since I don't think it's an option I would use much and I don't want to exchange the tablet again for a different one (again).
I've had no problems sending or receiving. In addition wireless charging works great, too. It's the only way I charge the N7 since I got it.
This is what I have been able to determin.
Works:
- Device to device (Nexus 7 v2 & GAlaxy Note II)
- Generic NFC tags from ebay (They also work with my NOTE II and TecTiles app)
- NFC Task Launcher app
- UPDATE: Samsung TecTiles just worked after being written with NFC Task Launcher.
Does not work:
- UPDATE: Samsung TecTiles just worked after being written with NFC Task Launcher.
- Samsung TecTiles app
Don't have and have not tried with the new TecTiles 2
This may shed some light into the TecTiles issue:
http://www.anandtech.com/show/6919/...le-with-original-tectiles-tectile-2-announced
RojasTKD said:
This is what I have been able to determin.
Works:
- Device to device (Nexus 7 v2 & GAlaxy Note II)
- Generic NFC tags from ebay (They also work with my NOTE II and TecTiles app)
- NFC Task Launcher app
- UPDATE: Samsung TecTiles just worked after being written with NFC Task Launcher.
Does not work:
- UPDATE: Samsung TecTiles just worked after being written with NFC Task Launcher.
- Samsung TecTiles app
Don't have and have not tried with the new TecTiles 2
This may shed some light into the TecTiles issue:
http://www.anandtech.com/show/6919/...le-with-original-tectiles-tectile-2-announced
Click to expand...
Click to collapse
I can also confirm that Kamor NFC Tags are not working with the Nexus 7 (2013) Wifi or LTE models. Here is information from the NXP TagInfo app regarding the non-supported tags from a Nexus 7 (2012) where the tag tiles work.
* TagInfo scan (version 2.00) 2013-10-08 09:15:09 **
-- INFO ------------------------------
# IC manufacturer:
NXP Semiconductors
# IC type:
MIFARE Classic (MF1S50)
-- NDEF ------------------------------
# NFC data set storage not present:
Maximum NDEF storage size after format: 716 bytes
-- EXTRA ------------------------------
# Memory size:
1 kB
* 16 sectors, with 4 blocks per sector
* 64 blocks, with 16 bytes per block
-- TECH ------------------------------
# Technologies supported:
MIFARE Classic compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible
# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable]
android.nfc.tech.NdefFormatable
android.nfc.tech.MifareClassic
android.nfc.tech.NfcA
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms
After some Googling, I have found that Android supports a few NFC tag technologies (and that some of them are RFID standards also).
Android supports the following NFC tag technologies:
TagTechnology - The interface that all tag technology classes must implement.
NfcA - Provides access to NFC-A (ISO 14443-3A) properties and I/O operations.
NfcB - Provides access to NFC-B (ISO 14443-3B) properties and I/O operations.
NfcF - Provides access to NFC-F (JIS 6319-4) properties and I/O operations.
NfcV - Provides access to NFC-V (ISO 15693) properties and I/O operations.
IsoDep - Provides access to ISO-DEP (ISO 14443-4) properties and I/O operations.
Ndef - Provides access to NDEF data and operations on NFC tags that have been formatted as NDEF.
NdefFormatable - Provides a format operations for tags that may be NDEF formattable.
Can anyone else who is having problems with specific NFC tags or tiles verify with TagInfo the type of tag used? I suspect there may be a problem with NfcA compatibility on the NFC stack used with the 2013 models.
buckofive said:
I can also confirm that Kamor NFC Tags are not working with the Nexus 7 (2013) Wifi or LTE models. Here is information from the NXP TagInfo app regarding the non-supported tags from a Nexus 7 (2012) where the tag tiles work.
* TagInfo scan (version 2.00) 2013-10-08 09:15:09 **
-- INFO ------------------------------
# IC manufacturer:
NXP Semiconductors
# IC type:
MIFARE Classic (MF1S50)
-- NDEF ------------------------------
# NFC data set storage not present:
Maximum NDEF storage size after format: 716 bytes
-- EXTRA ------------------------------
# Memory size:
1 kB
* 16 sectors, with 4 blocks per sector
* 64 blocks, with 16 bytes per block
-- TECH ------------------------------
# Technologies supported:
MIFARE Classic compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible
# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.MifareClassic, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable]
android.nfc.tech.NdefFormatable
android.nfc.tech.MifareClassic
android.nfc.tech.NfcA
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms
After some Googling, I have found that Android supports a few NFC tag technologies (and that some of them are RFID standards also).
Android supports the following NFC tag technologies:
TagTechnology - The interface that all tag technology classes must implement.
NfcA - Provides access to NFC-A (ISO 14443-3A) properties and I/O operations.
NfcB - Provides access to NFC-B (ISO 14443-3B) properties and I/O operations.
NfcF - Provides access to NFC-F (JIS 6319-4) properties and I/O operations.
NfcV - Provides access to NFC-V (ISO 15693) properties and I/O operations.
IsoDep - Provides access to ISO-DEP (ISO 14443-4) properties and I/O operations.
Ndef - Provides access to NDEF data and operations on NFC tags that have been formatted as NDEF.
NdefFormatable - Provides a format operations for tags that may be NDEF formattable.
Can anyone else who is having problems with specific NFC tags or tiles verify with TagInfo the type of tag used? I suspect there may be a problem with NfcA compatibility on the NFC stack used with the 2013 models.
Click to expand...
Click to collapse
The article I posted clearly states the issue. Here is an excerpt of the pertinent part:
" When I saw the presence of BCM2079x, I remembered that this reader doesn’t read MIFARE tags, which the NXP solution does, since it is an NXP tag format. Instead Broadcom only reads tags which adhere to the standard NFC Forum tag types. Ordinarily this isn’t much of a problem, as long as users are aware of the limitation and to stay away from MIFARE classic tags on an incompatible reader."
Sent from my Nexus 7 using Tapatalk 4
I can't my NFC to work at all. I have the ntag203 tags so I know their compliant. I get nothing at all. Guess I'm going to take this tablet back and exchange. I've used several apps. If any one knows a fix or how to check and see if the hardware is at fault please pm me If I knew how to check I would.
asdf1nit said:
I can't my NFC to work at all. I have the ntag203 tags so I know their compliant. I get nothing at all. Guess I'm going to take this tablet back and exchange. I've used several apps. If any one knows a fix or how to check and see if the hardware is at fault please pm me If I knew how to check I would.
Click to expand...
Click to collapse
neither do I, it can't find a nexus 4/nexus 5 nor compatible tags
If someone find a fix, post your solution please
it worked only ONCE with a tag, then I tried to read it again and since then nothing...I tried changing roms, full wipe
I found this:
http://www.andytags.com/nfc-tags-compatibility-issues.html
...not sure if it's helpful, but there you go.
Well, here's what I want to do.
I read the NFC tag (it's not write protected or anything like that), check the block data in hex, modify it, write the tag with the new data.
Is this possible? What app is capable of doing this?
The tag is Mifare Ultralight.
Please take a moment to read through this before posting, not only is a brief description of NFC and some of its uses included but also you will find a few of the more commonly asked questions. Over time these will be added to accommodate new or recurring queries that are being seen in this thread. If you have come to the thread to ask about emulating, copying or bypassing your Mifare card head down to the FAQs below .
What Is NFC
Near Field Communication (NFC) is a technology that was built upon Radio Frequency Identification (RFID). It allows for the storage of data without the need for a direct power supply. When a reader such as a NFC enabled phone comes within range (usually an inch or less) data can be read/written from/to the tag.
Objects containing NFC can be found in two varieties, active or passive. Passive devices are ones that contains data but do not read and generally will not have their own power supply. These are found in NFC tags such as those in Credit/Debit cards, Student or ID cards, Library books and passports among many. For a much larger of scannable objects see here. Their are also active devices, these can read information stored on other NFC devices and for the majority of us here these will be our phones. These active devices can also usually alter the data found on tags or transmit/exchange data with other active devices.
Uses for NFC
NFC has many uses both commercial and on a development/hobby level, here are just a few:
Contactless payment
Transfer of data from phone to phone
Share and log on to WI-FI
Sharing contact information
Automating tasks
Storing bitcoin wallets
Disabling alarms
Send Wake-On-Lan commands
FAQs
How can I emulate, copy, edit or bypass my Mifare card (student ID, work ID, Bus pass etc)?
The short answer: you can't
The long answer: There are numerous reasons why you may have had issues finding this information on XDA. Primarily because it is not possible from the vast majority of phones and for good reason. Mifare as mentioned above is a security layer for NFC cards and therefore the process isn't as simple as just downloading an app, scanning a security card and then forgetting about it. Secondly depending on the type of tag you are trying to use this is either A) illegal or B) against your companies, service provider, school's security policy and as such you will not find this information on XDA.
Your options from here are: look elsewhere for this information, just use your card as instructed or speak to your IT department about adding another form of NFC tag to the system, I for instance have an NFC tag implanted in my hand which my IT department was more than happy to add to my user profile at university. More information on this can be found here.
Click to expand...
Click to collapse
How can I hack my Bus pass, Oyster card etc to add more credit or extend its expiration date?
See the answer above ^
Click to expand...
Click to collapse
How can I unlock my Android phone using NFC
See "NFC LockscreenOffEnabler" for Xposed
Click to expand...
Click to collapse
How can I make Android trigger an event when I scan an NFC tag?
For simple commands you can use apps such as NFC Tools or Trigger.
For more complicated tasks a combination of Tasker and Locale can be used to launch just about any chain of events upon finding a specific tag. Of course alternatives do exist, so be sure to check out a few of the other projects around the site
Click to expand...
Click to collapse