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.
Hi
I wanted to check if anybody else is having an issue or if someone can help me whats going on?
I was flashing between builds already often and never had issues.
about two days ago I built from scratch the master branch and the iceman build
I flashed first to iceman and checked the new commands and went then to the main / master build.
Did some testing with lf sim and wanted to check if its now working in iceman too..
since then, no matter what I try first to flash it gives me back
Error: Unexpected reply 0x00fe NACK (expected ACK)
The funny thing as I said: I built it from scratch
Moved back to my recent versions folder and tried to flash this iceman built - works like a charm
tried a make clean and make all in the recent built didnt change anything about it
any idea whats going on? why was I successful flashing it once then? *hmm*
*edit*
seems to be some issue with the bootloader
as soon as I flash the "old" iceman build bootloader and then flash the "new" iceman build bootloader its working fine again
Proxmark3 Easy ElecHouse
When I use
bootrom: master/v2.2.0-348-g02069db-suspect
os: master/v2.2.0-348-g02069db-suspect
I can not flash to
bootrom iceman/master/v1.1.0-2001-g966c111
os: iceman/master/v1.1.0-2001-g966c111
because of a bootrom issue?
seems it goes to simulation mode (from what the lights look like)
when I instead flash following bootrom first its fine to go to 2001 rom:
bootrom iceman/master/v1.1.0-1887-g27c2477
Last edited by HighPressure (2017-03-20 21:22:52)
Offline
To make the bootrom working, try this solution: http://www.proxmark.org/forum/viewtopic … 344#p26344
Offline
Thanks, i'll try later if taking out the lines fixes the issue for me too.
My current workaround for the older version bootloader did the job for now too
Offline
#confirmed
commenting as described in the other thread did fix it for me to
Offline
great, I suggest you edit your first post and add [solved] to the beginning of the subject
Offline
To prevent same/similar issues in the future: why not making 256K the default?
Offline
Quite simple, because that doesn't solve the actual problem. The offending lines in bootrom.c and flash.c shouldn't trigger this error.
The 512 mode doesn't work basically, which I would rather solve. I work with my rdv2.0 (512kb) device and I want to use the most of it. My fork has problems with the old green pcb (see "hf mf mifare" for example) and rdv3.0 easy device is not my target either.
My fork works quite well with rdv2.0, which is why I decided to target this device. If iceman fork doesn't work for someone on another device, they have always the option with PM3 Master.
Offline