Flipper/NFC/Fun_Files

BIG CHANGES COMING TO THIS SOON! Updated 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.

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.

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 (for discussions, testing, and any files.)