problem sniff MF-Detect, OK with Official App, but not with Iceman Fork about chameleonmini-rebooted HOT 15 CLOSED

oppps, sorry I was wrong to post here, I confused with :
https://github.com/iceman1001/ChameleonMini-rebootedGUI
my bad :-(

from chameleonmini-rebooted.

yeah, different repo. Try the latest GUI code to see if it works better.
In iceman gui, there is no fast calc full calc only mfkey which looks on all existing collected data like full calc did.
Did you just try to swap between GUI applications or did you change anything with the application/chameleon..

from chameleonmini-rebooted.

it's the same with lastest gui code (I show you add Utils tab), no more key anyway, and I verified with official soft, it's always ok after a "full calc"

I just switch between app, I didn't make change on chameleon, here output for versionmy
--> VERSIONMY?
101:OK WITH TEXT
Chameleon-new-1.0

from chameleonmini-rebooted.

so using the old gui, it solves keys?
using the latest iceman gui, it doesn't solve anything..
Hard one to debug. We did update the mfkey implementation. Maybe a debug output to get which values was used for mfkey could be useful. It should also take some time to run it. Since it will run multiple mfkey sessions in order to find keys.

from chameleonmini-rebooted.

Sector 13, Block 52. It shoulds two different keys for same block which is a indication for failure. Which is possible for mfkey. Can you cut and paste all text from that "key detection result" box?

from chameleonmini-rebooted.

I just have 2 discovery key with official app, not more.
the good key is the second for my tag (Noralsy tag, if you want add to defaut_key file to PM3 no problem (because no include in default_keys) and second key (after hardnested) is 4243414F5250) :-)
13sec52blo A:
314B49474956
13sec52blo A:
4143414F5250

Maybe reader has 2 differents keys for different tag and try both together ?
From my memory, I already use chameleon with your app, but with a another reader card, and it worked, but I had only one key, so maybe it's a good indication for failure...

from chameleonmini-rebooted.

just for add a comment, I sniff another reader on slot 2, the results :

-- with iceman fork --

[Tag slot 1]
nothing...

[Tag slot 2]
[S0] KeyA [a0a1a2a3a4a5]
[S0] KeyA [a0a1a2a3a4a5]
[S60] KeyA [484558414354]
[S60] KeyA [484558414354]

-- with official app --

slot 1 :
13sec52blo A:
314B49474956
13sec52blo A:
4143414F5250

slot 2 :
15sec60blo A:
484558414354
0sec0blo A:
A0A1A2A3A4A5

It's not really a matter for me, just it's strange it doesn't success to calc key in the slot 1
if ok we can close this issue, if iceman fork doesn't give me a output just for 1 or 2 times, i just check with original soft, and no problem.

from chameleonmini-rebooted.

No that didn't make any sense. Slot 1 doesn't work but slot 2 does...
Would you mind testing the other slots aswell? To rule out that there is more slots not working.

I do spot another wrong, S60 should have been S15..

from chameleonmini-rebooted.

First a minor fix for GUI.
iceman1001/ChameleonMini-rebootedGUI@8ea3f5c

The output showed sector instead of block.

Then a fix for firmware..
cfd6a5d

the calculation when zero, was wrong. However it still is a problem with were the collected data is saved.

@shashadow would you mind testing things out?

from chameleonmini-rebooted.

hi Iceman,

hmmm… very bad news
I get last firmware, compiled with make,, put my files in flashtools directory and add boot_loader.
flash.bat was ok (make myfile.bin and myfilee.bin) , my chameleon has been successful upgraded with your last firmware, all was ok (note that we have a new ultralight option, cool :-) )
Is my procedure for upgrading correct ? it seems ok for me

already, "official client" doesn't work anymore … :-( so if your client make the job why not.

so, after configuring three first slot for MF_DETECTION, I go to my reader (the one who work only with official client), of course I use your last GUI compiled with visualstudio for do it.
but …in front of the reader … what a surprise…
When I approach Chameleon to the reader, I can see red light from chameleon, but light stay fix (normaly light blink when it works), and above all the reader has no reaction, Nothing, nada.
I tried with 3 différents slots but same problem, reader doesn't want to read anything :-(

I just hope you just make a little error in your firmware and it's fixable for next firmware, because I will be a bit bothered if I can't anymore snifff with my chameleon.

just for info : I tried with another reader, it's the same, so it's not the readers, it's really a issue chameleon.
and I tried too a mifare emulation 1k, it's ok for emulation

sniffff… need help :-(

from chameleonmini-rebooted.

just for add :
when I try to read with my phone the chameleon with MF_DETECT, it was the same than reader, no reaction.

I think either I did a bad thing when a upgrade firmware (but I Don't think because emulation works, and I can see the 3 ultralight option (EV), either your firmware is faulty.

So I used "upgrade" and "load défauts" with your app, this seems restore original firmware, and Indeed already official software works again. and when I use my phone with MF_DETECT, the phone react, so I think there a something wrong in new firmware.

from chameleonmini-rebooted.

Sorry to say, but there is no time left for me to work on it. Many interesting things could be adjusted and fixed for this Chameleon mini firmware, making it really usable in the field.

from chameleonmini-rebooted.

did you fix this one @bogiton ?

from chameleonmini-rebooted.

I hope so! I need someone to confirm. I just tried it with my pm3 with a test auth key and then I managed to recover successfully that key from within our GUI.

from chameleonmini-rebooted.

Ok it seem like the latest firmware and latest GUI sorts this out. @shashadow you can verify if you want but others already has done it.

from chameleonmini-rebooted.