flexUG4 (Ultimate Magic gen4) is now available!

Looking for an NFC implant that can have more than just 4-byte MIFARE Classic 1ks cloned to it? Here are some of the things the flexUG4 can emulate:

  • MIFARE Mini S20 4/7/10 byte UID
  • MIFARE 1k S50 4/7/10 byte UID
  • MIFARE 4k S70 4/7/10 byte UID
  • MIFARE Ultralight EV1
  • NTAG 210/212/213/215/216

Ha, I feel there should be



for the FlexUG4.

I wonder if its because it was pre-released to DT Club members over 2 months ago. (One of the DT Club perks.)

The ULTIMATE MAGIC CARD GEN4 is an Amazing chip, along with its many emulation options, it is almost “unbrickable”
I would still reccomend getting a gen4 magic card for test reading and writing to.
I carry one with me in my backpack, with my test card pack cards.

During my travels in Asia, I have found Mifare Classic 1k is highly prevalent and ~80% of hotels would use it, When its not, Mifare Ultralight EV1 has been my nemesis.

In NZ, Ultralight EV1 is far more prevalent, and has been a pain in the arse.

For those that have been on the same boat, We now have a Solution, and its fucken great.

Obviously, there are the many other emulation options for it, and I regret not becoming more proficient in its use prior to getting the FlexUG4, and I still have some stuff to learn, but it is well documented.
A PM3 will be your best friend, but a Flipper Zero is also a good associate.

I plan to write a proper review of the FlexUG4
Spoiler alert, it gets 5 stars
:star: :star: :star: :star: :star:

and seperately, even though there is a lot of documentation.

I am going to try and simplify it, to make it even easier to use.


:100: If you’ve got need for a NFC magic implant and have the funds for a flex, this is far and away the best option.


Wish I had a need for it, but I barely use my xMagic as it is.
Although I suppose it is fairly future-proof, being able to clone that many different cards.

Currently have an Apex Flex in P2 left hand, how much interference would there be with this in say P1 left? Or would it be better to keep them a hand apart?
Don’t have much in the right hand yet, but was kind of saving space for something special.

1 Like

So this is like the FlexM1 upgrade?

1 Like

That’s one way to put it. But these two are in totally different weight classes. The flexM1 is a one trick pony–the flexUG4 does nearly all the things :grinning:


That would be close enough to cause complications, I suspect. p1 and p4 should be good, if you’ve got space.


Yeah, already have the Apex in P2 left, so I’ll just have to shove this one into P1 right.

That’s the problem with “Oh no, Mrs Installer, I’m not planning on having any more implants put in, just go ahead and stick that one wherever you feel like” :joy:


I Absolutely love my FlexM1, and use it frequently, But If I could choose only one, It would be the FlexUG4 ( don’t tell my FlexM1 )

I would put the FlexUG4 on par with the ApexFlex for capability, BUT, their capabilities are complementary to each other rather than comparative.

If you had an ApexFlex and FlexUG4, you would have a VERY powerful combination and would be covered for ALMOST any HF requirement.

Of course there are outliers and so much technology in one space, so you would never get a single implant to cover everything, but between these two, you get pretty damn close.

I would call the FlexUG4 “special”

Good decision, this keeps your P3 or P4 free for the other “Special” implant

Haha, well if it makes you feel better, I try to plan ahead with my installs, and I have still ended up moving and removing a few because I got another implant I hadn’t planned for…


Is the FlexUG4 programmable using Mifare Classic Tool on an Android smartphone, or only using a dedicated device like a Proxmark 3 or Flipper Zero?

Thanks in advance.

1 Like

If it’s setup as a MIFARE Classic 1k with 4-byte UID, you can use MCT. Checkout the video on the product page. I do exactly that : )


Thanks. My source tag will be a 7-byte UID, so using MCT won’t work for my situation then?

Unfortunately not–it’s a limitation of MCT.

OK sure, no problem. Getting a bundled PM3 isn’t a huge expense compared to the cost of the FlexUG4 anyway I suppose.


That’s a great mindset. Not to mention having a Proxmark opens so many doors!


Pun intended? :face_with_hand_over_mouth:


hi there everyone
Q: whats the memory size of the ug4 8k 16k 32k
thank you

I’m not sure what the actual memory is but from what I’ve seen the amount available is based on the chip it’s emulating. It can do MFC with up to 4k. Or an NTAG216 which has 888 bytes or an NTAGi2c which, while it can have 2k of memory, only 1k is usable (see the xSIID page for more).


ok so. if im understanding this correctly it can only behave like the chip its emulating and that determines the usable memory size
the ntagi2c 2k usable memory problem seems like a This is how we want to read it so you change it not us kind of problem.
to be clear reading the explanation of sXIID old vs new
and why is something i can only halfway understand

will this chip only ever be able to emulate what it can do now?
no possible DESFire EV2/3 32kB update or something?

thank you so much mr. tac0s for taking the time to help


The NTAG I2C chip used in the SiiD module we used to construct the xSIID implant has 2kB of memory, split into two large memory sectors. The problem is that the NTAG I2C chip is not commonly used by consumers, and at the moment there are no apps available that properly identify and read the entire user memory beyond 1kB. Please read this forum post carefully as it explains the issue and possible remedies; https://forum.dangerousthings.com/t/so-what-happened-with-the-2k-memory-on-the-xsiid

It’s not like the Apex which can be updated so the flexUG4’s functionality will not be expanded beyond the capability of the chip. The lua script that configures it supports most of the chip’s functionality but not some of the ultralight options–so there will be more easily accessible functionality at some point in the future beyond our control. Regarding DESFire, no. I wouldn’t expect that to be a thing, unfortunately.