I have a KSECT5577 Emulator card but the lf t55xx detect command doesn’t work.
Please see my efforts below.
When trying to write and read I’m not seeing the results expected in the guide.
Please can somebody point me in the right direction direction?
[usb] pm3 → lf t55xx detect
[!] command execution time out
[!] command execution time out
[!] command execution time out
[!] command execution time out
[!] Could not detect modulation automatically. Try setting it manually with ‘lf t55xx config’
Yeah, looks like you have a firmware mismatch. I haven’t seen it say “suspect” before…that’s a little…dare I say suspect? O.o
I’m a little more than exhausted, so grain of salt, but I’d recommend pulling the latest from github and reflashing.
Go into the ProxSpace environment, then run cd proxmark to change directory to where the proxmark files should be located, then git pull to pull the latest release, then make clean && make all to compile, ./pm3-flash-bootrom to flash the bootrom, and finally ./pm3-flash-fullimage to flash the full image.
Pulling this from:
The only difference is you already have the files from the Proxmark GitHub, so you want to do git pull instead of git clone to update the files.
And I changed make clean && make -j8 all because iirc that was messing with some people. The -j8 tells it to run multiple threads during compiling which should make it faster but taking that out doesn’t hurt the process.
I only seem to have .proxmark3 directory and no proxspace.
All I’m seeing is this:
ashscott@espresense-lounge .proxmark3 % ls
history.txt logs preferences.json
ashscott@espresense-lounge .proxmark3 % git pull
fatal: not a git repository (or any of the parent directories): .git
Yes, you’ll not remember - barely do. I found you on a blog or forum and you sent me 2 RFID tags. No implanters at the time though or you couldn’t send them outside the US or somesuch. I never forgot your name though!
Anyway, I’m only now getting started with this. Guess it’s all just about priorities. I now have the time and a need.
Sorry, I made an ass out of myself and ass-umed you were on windows. No proxspace then, but you should have a proxmark3 directory as well as a .proxmark3 directory. We want the non hidden proxmark3 directory.
It does not. To update you need to pull the latest release and flash it, which is what we’re trying to do to fix the firmware mismatch.
My next step would be deleting the proxmark3 directories and starting again following this guide. proxmark3 should be a git directory if properly installed.
You’re thinking re-install from scratch, I hate to say it, but I’m thinking (given the 15 year comment) it may be that the PM isn’t in bootloader mode. Do the lights on the PM indicate that it’s in bootloader mode.
It can’t hurt to try the flashing/initial setup.
Being that the PM3RDV4.01 setup/use was the easiest part of my implant research journey, I’d also look at interference. (PM3 in a SLNT bag and/or making sure you’re in an area without interference.)
@ashs Can you disclose what OS/hardware you’re using? Mac/Ubuntu/Linux/other? (not needed, but I’m curious given your screenshots.)
If I were you, in the situation/state your PM3 appears to be in, I’d start fresh, in a completely different directory. With the fresh install instructions from…This link. @Pilgrimsmaster had the right idea, but linked to the Linux instructions, and with Macos, it’s a bit different.
This is what I currently think is the issue (not being able to run pm3-flash-all right now.) But doing the above should get you all set.
step 3 isn’t optional for you this time around. (Sorry for being unclear before.)
Ok, this depends on what hardware you actually have.
If you have a Proxmark3 Easy, then you want the PM3GENERIC line without the pound sign.
If you have a Proxmark3 RDV4 (not the Easy) then you want the PM3RDV4 line without the pound sign.
If you want to be really confused (don’t do this) then type make platform= and you’ll see a WHOLE LOT of options that you don’t need right now. (I mean you can do it, just don’t choose one. )
You’re making great progress! Don’t hesitate to ask more questions if you have them.
command execution time out
)
