FlexM1 Magic 1k or an xM1 Magic 1k

Support
21

I understand you can do it accidentally, although using something like MCT should avoid that.

I personally went the gen 1 for implanting, as it can be “reset” through the backdoor if you brick it. I also have the ring which is in gen 2 format which I use for hotel keys. That way if I do brick it, then it is just a ring and I don’t need to be cut open to remove it.

I am yet to encounter one of the readers which have been mentioned in here which checks if the chip you are using accepts the magic backdoor commands. From the little I have read about that, they seem to be more prominent in China than elsewhere though I am sure someone on here will correct me if I am wrong.

I hope this helps.

22

Do you know if there is any video o post that shows exactly what should not be done? I mean, I mean, like the videos that show what you should do for this or that, etc. One that shows what you should not do with these …M1. I think much much people are avoiding buying the 2g just because of the bad publicity, and lack of knowledge in general (me included) @amal ??

23

I believe if you write a BCC that doesn’t match the UID in the manufacturer’s block (sector 0) it’ll brick the chip.

24

gen2 can usually undo this if its the only discrepancy

but yes its important to calculate the correct BCC for the uid

Calculate your own mifare classic UID bcc so you dont brick your tag (for gen2 block 0 self writers)

BCC calc in simplicity is just xoring the uid byte by byte starting from 0, and using the outputted xor from the first byte for the second byte 

xor-ing is lining up the binary and if the number above and below are the same, value is 0 and if theyre different its 1

0000 0000
0000 0001 = 01
0000 0001 XOR = 0000 0001 = 01

0000 0001
0000 0010 = 02
0000 0011 XOR = 0000 0011 = 02

0000 0011
0000 0011 = 03
0000 0000 XOR = 0000 0000 = 00

0000 0000
0000 0100 = 04
0000 0100 XOR = 0000 0000 =4

bcc = 04 for UID of 01020304