A closer look into card.dmp reveals, that there was no payload in the 1024 bytes this particular MIFARE Classic stored. Since, the card doesn't have any payload, the application has to work based on childish assumption, that the UID of a RFID-tag cannot be changed.
UID: C5 17 EA 2EATQA: 00 04SAK: 08 2TYPE: NXP MIFARE CLASSIC 1k Plus 2k SL1 1k Ev1proprietary non iso14443-4 card found, RATS not supportedAnswers to magic commands (GEN 1a): YESPrng detection: WEAKValid ISO14443-A Tag FoundThe New edited clone still doesn't work:(I decide to go through each sector on the clone and compare it to each sector on the original and find that 4 sectors have differences in them. So i manually change each sector so that all sectors are all the same.
I try the fob again and now the cloned fob that i have heavily edited wont even open the front door.Do now i'm completely lost and don't know what to try next. Is anyone able to help point me in the right direction. No, I dont have a Gen 2 card. Need to look around a purchase some new cardsIf you can wait a few weeks, you can get small quantities of Gen2 cards for $1 or less from China. Search Aliexpress for 'CUID' (the Chinese to English translation for Gen2).I've tried many different Gen1a cards from China through Aliexpress. With Gen1a cards I found some (not all) reply with a different SAK from the written SAK but it never made any difference to the TDi readers on my apartment block.
My TDi readers seem to ignore SAK.It's possible your reader employs countermeasures against Gen1 and/or Gen1a. I found a mixture of TDi reader firmwares on my apartment complex; most work with Gen1a cards but some send a Magic wipe command (which the 'a' of Gen1a is immune too because it ignores the wipe command), some readers send the first part of a magic command and halt if a response is received (Gen1a is not immune to this, it fails).