First of all, why do you need NTAG216F (type 13) vs NTAG216 (type 7)? The magic chip does not actually have a field detect pin in hardware. Are you attempting to clone / copy an existing NTAG216F and want to make it as legit as possible?
Regardless, I would try NTAG216 first just to ensure it can be set up correctly. So, I would;
script run hf_mfu_magicwrite -w
script run hf_mfu_magicwrite -t7
script run hf_mfu_magicwrite -u 01020304050607
script run hf_mfu_magicwrite -o E1106D00
script run hf_mfu_magicwrite -v 0004040201001303
Basically the first thing you do is wipe the chip, then set the type which should set up the memory pages correctly for an NTAG216. After that setting the UID, OTP bytes, and version info… that should be enough that when you scan with taginfo on android it should scan properly and return memory contents.
If you are trying to clone a chip and want to set the signature then you will have to read the signature from your source chip and write it with the -s command so it will match/verify properly.
You can verify after by running the read command;
script run hf_mfu_magicwrite -c
Post the results to ensure the tag has been set up properly as NTAG216, then once you are sure you can go about writing to memory pages. The first page of user writable memory is page 04 and each page is 4 bytes long, written 4 bytes or one page at a time.