Flipper/NFC/Fun_Files
2022-06-26 23:00:24 -07:00
..
Call_911.nfc Will call 911 if scanned and launched 2022-06-26 23:00:24 -07:00
Empty_NTAG213.nfc Fun NFC files to play with 2022-05-20 23:31:32 -07:00
Empty_NTAG216.nfc Fun NFC files to play with 2022-05-20 23:31:32 -07:00
Flipper_wifi_connect.nfc Fun NFC files to play with 2022-05-20 23:31:32 -07:00
Go2_Flipper.nfc Open FlipperOne (added) 2022-05-20 18:34:35 -07:00
Google.nfc Fun files. Triple the verified NFC keys and scan all 32! 2022-05-14 12:23:57 -07:00
GuidoZ.nfc Fun files. Triple the verified NFC keys and scan all 32! 2022-05-14 12:23:57 -07:00
How_to_compile_DFU.nfc Better captures and fun files 2022-05-20 23:54:05 -07:00
Open_Android_flipper.nfc Fun NFC files to play with 2022-05-20 23:29:34 -07:00
ReadMe.md Update ReadMe.md 2022-06-14 14:47:25 -07:00
Rickroll_no_ads.nfc Rename Rickroll_noad.nfc to Rickroll_no_ads.nfc 2022-06-14 14:38:42 -07:00
RickRoll.nfc Fun files. Triple the verified NFC keys and scan all 32! 2022-05-14 12:23:57 -07:00

BIG CHANGES COMING TO THIS! Need to update info as the below is no longer (entirely) true.

Some files that are fun to use. Starting to get a better idea on the structure (Flipper format) of NFC files and payloads.


Flipper Zero can read the following:

  • T5777 Card Freq 125K
  • 125 kHz RFID (MiFare Classic Card)
  • NFC MiFare Classic Clear Tag
  • NFC HID Card Freq 125KHZ
  • 125 kHz RFID FourPoints.Com Card NFC
  • NFC Mifare Ultral/NTAG Gen1A 1k S50 HF RFID Card
  • NFC UID Freq 13.56MHZ Card | NFC Hotel KeyCards
  • NFC ValuProx 125kHz ISO

Example using the RickRoll.nfc file. Leave the data in pages 1 through 6 alone (though not always true, but it is for YouTube links.)

Page 7: 79 6F 75 74
Page 8: 75 2E 62 65
Page 9: 2F 64 51 77
Page 10: 34 77 39 57
Page 11: 67 58 63 51

This is simply the YouTube "share" link encoded into HEX and split into 4 byte chunks. See for yourself...

HEX from above: 79 6F 75 74 75 2E 62 65 2F 64 51 77 34 77 39 57 67 58 63 51
Converted: youtu.be/dQw4w9WgXcQ

The last byte in page 6 (0x04) defines what type of encoding (data sheet and URI identifier codes). To convert your link to HEX, use anything such as an online tool. Read up on generic cloner passwords as they may exist and may be needed to access information.

One limitation is the URL will be truncated if it goes beyond page 11! If your URL is less than exact, pad it with 00, making sure page 12 stays as "FE 00 00 00". Note that TinyURL links appear to fit well and conversion/use is free. If your link doesn't launch automatically when scanned, try using a different URI identifier.

Acknowledgements: RogueMaster | cyanic | Null Silvry | Equip | DDVL (for discussions, testing, and any files.)

NTAG Differences | NTAG Datasheet | ASCII to HEX | HEX to Decimal (Other converters at both links.)

NFC_Mem_Opt

Value    Protocol     (SOURCE)
------    ----------
0x00     No prepending is done ... the entire URI is contained in the URI Field
0x01     http://www.
0x02     https://www.
0x03     http://
0x04     https://
0x05     tel:
0x06     mailto:
0x07     ftp://anonymous:anonymous@
0x08     ftp://ftp.
0x09     ftps://
0x0A     sftp://
0x0B     smb://
0x0C     nfs://
0x0D     ftp://
0x0E     dav://
0x0F     news:
0x10     telnet://
0x11     imap:
0x12     rtsp://
0x13     urn:
0x14     pop:
0x15     sip:
0x16     sips:
0x17     tftp:
0x18     btspp://
0x19     btl2cap://
0x1A     btgoep://
0x1B     tcpobex://
0x1C     irdaobex://
0x1D     file://
0x1E     urn:epc:id:
0x1F     urn:epc:tag:
0x20     urn:epc:pat:
0x21     urn:epc:raw:
0x22     urn:epc:
0x23     urn:nfc: