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 question <Strange thing between Raspi and Win 10> said I can not get some KeyA and all the KeyB.
Today I get a master write in 2015-3-19,and make in kali .
It get all the KEY.Running well.
so I think the problem still on the software.
solved
solved
solvedsolved
solved
solved
Last edited by repreentative (2017-03-28 03:38:34)
Offline
There was no need to open another thread. You still cannot flash the firmware, right?
What is your firmware version? Type hw ver and post the output here.
Offline
YES,It is always can not send bytes to paoxmark3 .
proxmark3> hw ver
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: /-suspect 2015-04-02 15:12:04
#db# os: /-suspect 2015-04-02 15:12:11
#db# HF FPGA image built on 2015/03/09 at 08:41:42
There was no need to open another thread. You still cannot flash the firmware, right?
What is your firmware version? Type hw ver and post the output here.
Last edited by repreentative (2017-03-27 08:44:22)
Offline
Your bootrom and firmware are from April 2015.
Your bootrom is OK - no need for hid-flasher.
Your firmware (os) is outdated. And it explains why the client software from 2015-3-19 works for you. It matches the firmware version.
So it is neither a firmware nor a client software issue. You have to flash the firmware which matches the client software.
Offline
yes yes yes you are right.
I thought a good idea ...I copy the bootroom.elf and the fullimage.elf to win10...
and use the .bat to write the two files in proxmark3...
I am successd....hahhahahahahh
tahnk you very very very much.
Your bootrom and firmware are from April 2015.
Your bootrom is OK - no need for hid-flasher.
Your firmware (os) is outdated. And it explains why the client software from 2015-3-19 works for you. It matches the firmware version.
So it is neither a firmware nor a client software issue. You have to flash the firmware which matches the client software.
Offline
but what the mean of
.eml not found or locked
when i hf mf eload 42A07BBB
yes yes yes you are right.
I thought a good idea ...I copy the bootroom.elf and the fullimage.elf to win10...
and use the .bat to write the two files in proxmark3...
I am successd....hahhahahahahh
tahnk you very very very much.piwi wrote:Your bootrom and firmware are from April 2015.
Your bootrom is OK - no need for hid-flasher.
Your firmware (os) is outdated. And it explains why the client software from 2015-3-19 works for you. It matches the firmware version.
So it is neither a firmware nor a client software issue. You have to flash the firmware which matches the client software.
Offline
Please, keep the threads neat and clean. If your original question is solved, edit first post and add "[solved]" to it. Same goes with your old thread.
Start a new thread for new questions. Do take time to read the helptexts. Usually implemented with "h" parameter, like hf mf eload h
Offline