Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
The card I Cracked on Win 10, I got the keyA and keyB like that
|---|----------------|---|----------------|---|
|sec|key A |res|key B |res|
|---|----------------|---|----------------|---|
|000| ffffffffffff | 1 | ffffffffffff | 1 |
|001| 4c4452464a48 | 1 | d97014793eca | 1 |
|002| 4c4452464a48 | 1 | 7dfb28bbfde3 | 1 |
|003| 544c35373031 | 1 | ffffffffffff | 1 |
|004| 4c4452464a48 | 1 | d187c04f06e7 | 1 |
|005| 221cbfc82141 | 1 | bf98cdea6623 | 1 |
|006| 439638fa3390 | 1 | ffffffffffff | 1 |
|007| ffffffffffff | 1 | ffffffffffff | 1 |
|008| a463e6591766 | 1 | 608087091837 | 1 |
|009| 4c444f50454e | 1 | 24a77b4ba9a2 | 1 |
|010| 59d5085af988 | 1 | ffffffffffff | 1 |
|011| ffffffffffff | 1 | ffffffffffff | 1 |
|012| ffffffffffff | 1 | ffffffffffff | 1 |
|013| ffffffffffff | 1 | ffffffffffff | 1 |
|014| 281683716a1f | 1 | 281683716a1f | 1 |
|015| ffffffffffff | 1 | ffffffffffff | 1 |
The keyB is easy to get
but on Raspi3 kali, I can not get the keyB...:D
|---|----------------|---|----------------|---|
|sec|key A |res|key B |res|
|---|----------------|---|----------------|---|
|000| ffffffffffff | 1 | ffffffffffff | 1 |
|001| 4c4452464a48 | 1 | 000000000000 | 0 |
|002| 4c4452464a48 | 1 | 000000000000 | 0 |
|003| ffffffffffff | 1 | ffffffffffff | 1 |
|004| 4c4452464a48 | 1 | 000000000000 | 0 |
|005| 221cbfc82141 | 1 | 000000000000 | 0 |
|006| ffffffffffff | 1 | ffffffffffff | 1 |
|007| ffffffffffff | 1 | ffffffffffff | 1 |
|008| a463e6591766 | 1 | 000000000000 | 0 |
|009| 4c444f50454e | 1 | 000000000000 | 0 |
|010| ffffffffffff | 1 | ffffffffffff | 1 |
|011| ffffffffffff | 1 | ffffffffffff | 1 |
|012| ffffffffffff | 1 | ffffffffffff | 1 |
|013| ffffffffffff | 1 | ffffffffffff | 1 |
|014| 281683716a1f | 1 | 281683716a1f | 1 |
|015| ffffffffffff | 1 | ffffffffffff | 1 |
and I can not Upgrading Proxmark3 to CDC Bootloader and Upgrading Proxmark3 Firmware at kali.
one said WAITING FOR Proxmark to appear on USB .(I ALWAYS PRESS THE BUTTON)
the other is Sending bytes to proxmark faild.
@piwi @iceman
Last edited by repreentative (2017-03-24 07:11:18)
Offline
what kind of pm3 do you have? If you bought it recently, the device already have the cdc-bootrom installed. If you bought it before 2014 it didnt.
When you flash, do you use "client/flasher" command? if you do, then you are using the CDC version.
You will need to be more specific about what your problems, which commands did you use, tracelogs, which version of firmware are you using etc if you want us to help you.
Offline
The pm3 I bought it recently,seem like 125KHZ ...
I can copy card at win10 use the client.I wanna to know why I can not get the KeyB at kali.
The same card ,at win 10.I use the Proxmark3_EASY_GUI.exe.. It works well.keyB is obviously.
But at Rsapi the order is 'proxmark3> hf mf nested 1 0 A ffffffffffff d', I got the keyB is zero .
OH。。。some keyA IS also lose cant read.sorry,my description maybe is not accurate.
but it is the same one card. at kali I can not get the block.
SO I dont think the problem on hardware.
what kind of pm3 do you have? If you bought it recently, the device already have the cdc-bootrom installed. If you bought it before 2014 it didnt.
When you flash, do you use "client/flasher" command? if you do, then you are using the CDC version.
You will need to be more specific about what your problems, which commands did you use, tracelogs, which version of firmware are you using etc if you want us to help you.
Last edited by repreentative (2017-03-24 08:57:18)
Offline
If you read the forum about "nested" command, you would have found out that it doesn't always find all keys. You may need to run it several times. And even then, there is no guarantee. I suggest you take some time to understand the commands involved and what their limits and function is.
Offline
Proxmark3_Easy_GUI.exe on Win10 and your self compiled proxmark3 on RasPi/KaLi are probably a different version and would require to flash the corresponding firmware version. I understand that you have problems with flashing the firmware, therefore the version on RasPi probably doesn't fit.
What are the results with Kali Linux on your PC?
Offline
I try seven or eight tinmes? both on Raspi and kali linux vmware
they are both can not calculation all the key.
Missing part about 3 keyA and 6 keyB.
Proxmark3_Easy_GUI.exe on Win10 and your self compiled proxmark3 on RasPi/KaLi are probably a different version and would require to flash the corresponding firmware version. I understand that you have problems with flashing the firmware, therefore the version on RasPi probably doesn't fit.
What are the results with Kali Linux on your PC?
Last edited by repreentative (2017-03-24 11:54:25)
Offline
This confirms my assumption: your PM3 firmware and your self compiled client software don't match. You need to reflash your firmware or stick with Proxmark3_Easy_GUI.exe.
Offline
I also think the problem at the firmware.
but when I PRESS the button and at the /proxmark3/client
and run the order ./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
The yellow and red light are bright. but something like
eat
help This help. Use '<command> help' for details of a particular command.
data { Plot window / data buffer manipulation... }
hf { High Frequency commands... }
hw { Hardware commands... }
lf { Low Frequency commands... }
reveng Crc calculations from the software reveng1-30
script { Scripting commands }
quit Exit program
exit Exit program
exit
(process:1264): GLib-CRITICAL **: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
(very long this is the end)
seems like can not upgrad Proxmark3 Firmware.
it is a bug? VERY SMALL... fell life are so hard
This confirms my assumption: your PM3 firmware and your self compiled client software don't match. You need to reflash your firmware or stick with Proxmark3_Easy_GUI.exe.
Last edited by repreentative (2017-03-24 16:10:19)
Offline
Are you trying to run the flash command from inside the proxmark client? (or inside proxmark easy gui?) You can't do that.
you need to execute it from a command prompt.
Offline
haha,I am the green hand.a beginner.
but I know the different between root@kali:~/promark3/client#
and proxmark3>
my order is root@kali:~/promark3/client# ./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
and I can not upgrad Proxmark3 Firmware on windows use cmd.exe...
Are you trying to run the flash command from inside the proxmark client? (or inside proxmark easy gui?) You can't do that.
you need to execute it from a command prompt.
Offline
Would you please run
./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
without pressing any button and paste the output here?
Offline
sorry,Because of the time difference,I went to sleep about 01:00
AT the kali2.0 linux slightly normal point
root@kali:~/proxmark3/client# ./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elfLoading ELF file '../armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002b610->0x0002b610) [R X] @0x94
1: V 0x00200000 P 0x0012d610 (0x0000196c->0x0000196c) [RW ] @0x2b6a4
Note: Extending previous segment from 0x2b610 to 0x2cf7c bytes
Waiting for Proxmark to appear on /dev/ttyACM0. Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on /dev/ttyACM0........ Found.
Sending bytes to proxmark failed
but at Raspi kali rolling ,It is strange, a very long paragraph about help command
help This help. Use '<command> help' for details of a particular command.
data { Plot window / data buffer manipulation... }
hf { High Frequency commands... }
hw { Hardware commands... }
lf { Low Frequency commands... }
reveng Crc calculations from the software reveng1-30
script { Scripting commands }
quit Exit program
exit Exit program
exit
(process:1264): GLib-CRITICAL **: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
(very long this is the end)
like the #8
Would you please run
./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
without pressing any button and paste the output here?
Offline
That looks like a real bug I suggest starting an new issue on Github for the trackrecord.
The flasher executable doesn't not dump help-text like that. When you create the issue, try using pastebin.com for your traceoutputs.
It makes yr issues easier to read, and easier to follow the traces aswell.
Offline
To be honest,I do not know what the pastebin.com is... and some thing I should paste on it.
now is 23:00 I try last time today...
first , I upgrade the firmware on win10 use the .bat to make the firmware reset,seems like it is successful.
and then ,I use the order dmesg|grep -i usb ,and I could see the ACM is 1. maybe my description is not good
so I try to update firmware use the order ./flasher / dev / ttyACM1 ../armsrc/obj/fullimage.elf
Not surprisingly,It coule be FOUND ,but Sendind bytes to proxmark faild.
I gie up today.fight tomorrow
thank you iceman and piwi.
goog night for myself....
That looks like a real bug I suggest starting an new issue on Github for the trackrecord.
The flasher executable doesn't not dump help-text like that. When you create the issue, try using pastebin.com for your traceoutputs.
It makes yr issues easier to read, and easier to follow the traces aswell.
Offline