Proxmark Help! t55xx detect not working

Unfortunately, this might be something to discuss with Iceman - it seems like a bad processing for t55xx?

I’ve only ever used the ‘normal’ fork.

1 Like

I might give the normal fork a shot - very well could be a bug

1 Like

I’m struggling with the normal fork, seems the Mac instructions I found are a bit incomplete as I’m getting commands failing. Maybe a fresh start tomorrow is on the cards, but I’ll also try reaching out to Iceman and others on the Proxmark forums and see if they have any advice.

I’m not sure if you have been on the Proxmark forum before, and probably telling you to suck eggs, but Just make sure your do you due diligence and thoroughly research your question before you ask it.
You only need to read some of their comments and you will see they are not particularly forgiving of people who ask questions that are covered elsewhere in the forum.
Just a friendly “heads up”

Iceman IS the man though.
Iceman is to Proxmark What Amal is to…Well, ALL OF THIS!!!

2 Likes

Hi iam at work right now but as soon as I get home I’ll try and work with you on re writing the blocks manually to setup basic EM410x (as they came from DT) . Also I’ll try to make sure with you as to how you created the iceman1001 rrg firmware (did you change to PM3OTHER?)… WE WILL GET YOU BACK WORK IF POSS.

3 Likes

That’d be awesome! I did set to PM3OTHER, no issues with any of the other functionality, so I’m sure it’s something simple I’ve missed.

Or perhaps a shitty antenna, I wouldn’t be surprised to find out all of this is due to poor coupling with my knockoff Proxmark.

1 Like

All I’ve done over there so far is post an introduction, in my googling efforts I couldn’t find anyone else with these issues, but I’ll make sure to search their forums and if I can’t find anything I’ll make sure my post is nice and detailed.

2 Likes

Did you get it to work? i have the same problem

Welcome @teeny
Do you have some more info for us?
What Proxmark do you have
What software and firmware are you running?
What implant do you have?

Have you checked out

Hi
At the moment i only trying to clone a tag to a blank card t55x7 and i get stuck at lf t55 detect.
I’m using a proxmark3 rdv4

Proxmark Output

[ Proxmark3 RFID instrument ]

[ CLIENT ]
client: RRG/Iceman
compiled with GCC 9.3.0 OS:Linux ARCH:x86_64

[ PROXMARK3 RDV4 ]
external flash: present
smartcard reader: present

[ PROXMARK3 RDV4 Extras ]
FPC USART for BT add-on support: absent

[ ARM ]
bootrom: RRG/Iceman/master/cb8d589f 2020-05-19 09:31:06
os: RRG/Iceman/master/cb8d589f 2020-05-19 09:31:14
compiled with GCC 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]

[ FPGA ]
LF image built for 2s30vq100 on 2020-02-22 at 12:51:14
HF image built for 2s30vq100 on 2020-01-12 at 15:31:16

[ Hardware ]
–= uC: AT91SAM7S512 Rev A
–= Embedded Processor: ARM7TDMI
–= Nonvolatile Program Memory Size: 512K bytes, Used: 288754 bytes (55%) Free: 235534 bytes (45%)
–= Second Nonvolatile Program Memory Size: None
–= Internal SRAM Size: 64K bytes
–= Architecture Identifier: AT91SAM7Sxx Series
–= Nonvolatile Program Memory Type: Embedded Flash Memory

[usb] pm3 --> hw tune
[=] Measuring antenna characteristics, please wait…
:clock1: 8
[+] LF antenna: 75,49 V - 125,00 kHz
[+] LF antenna: 35,20 V - 134,83 kHz
[+] LF optimal: 75,49 V - 125,00 kHz
[+] LF antenna is OK

[+] HF antenna: 47,16 V - 13.56 MHz
[+] HF antenna is OK

[+] Displaying LF tuning graph. Divisor 88 is 134,83 kHz, 95 is 125,00 kHz.

[usb] pm3 --> lf sea
[=] NOTE: some demods output possible binary
[=] if it finds something that looks like a tag
[=] False Positives ARE possible
[=]
[=] Checking for known tags…
[=]
[+] EM410x pattern found

EM TAG ID : 00000874FC

Possible de-scramble patterns

Unique TAG ID : 0000102E3F
HoneyWell IdentKey {
DEZ 8 : 00554236
DEZ 10 : 0000554236
DEZ 5.5 : 00008.29948
DEZ 3.5A : 000.29948
DEZ 3.5B : 000.29948
DEZ 3.5C : 008.29948
DEZ 14/IK2 : 00000000554236
DEZ 15/IK3 : 000000001060415
DEZ 20/ZK : 00000000010002140315
}
Other : 29948_008_00554236
Pattern Paxton : 1880828 [0x1CB2FC]
Pattern 1 : 318749 [0x4DD1D]
Pattern Sebury : 29948 8 554236 [0x74FC 0x8 0x874FC]

[+] Valid EM410x ID found!

[usb] pm3 --> lf t55xx detect
[!] :warning: Could not detect modulation automatically. Try setting it manually with ‘lf t55xx config’
[usb] pm3 --> lf t55xx info
[usb] pm3 -->

@teeny So I don’t think this will be super useful to you but I tried to see if I got the same result.

I have a PM3 easy with the Iceman fork on Mac and I was able to use lf t55xx detect without any problem.

Like I said, I don’t think this helps you other than saying it’s probably not the firmware. There was a previous bug using that command that @TomHarkness posted to GitHub and they fixed it in 2018. Your version isn’t that old right?

Link: https://github.com/RfidResearchGroup/proxmark3/issues/3

1 Like

Sorry, forgot to update this one!

It was a bad release of the Iceman firmware that didn’t have it working reliably. Delete your old client, download the latest Iceman release, then reflash your hardware and try again.

made a new pull and flash my proxmark with the latest and the problem is still there.

Proxmark

[=] Session log /home/teeny/.proxmark3/logs/log_20200723.txt
[+] loaded from JSON file /home/teeny/.proxmark3/preferences.json
[=] Using UART port /dev/ttyACM0
[=] Communicating with PM3 over USB-CDC

██████╗ ███╗ ███╗█████╗
██╔══██╗████╗ ████║╚═══██╗
██████╔╝██╔████╔██║ ████╔╝
██╔═══╝ ██║╚██╔╝██║ ╚══██╗
██║ ██║ ╚═╝ ██║█████╔╝ :snowflake: iceman@icesql.net
╚═╝ ╚═╝ ╚═╝╚════╝ bleeding edge :coffee:

https://github.com/rfidresearchgroup/proxmark3/

[ Proxmark3 RFID instrument ]

[ CLIENT ]
client: RRG/Iceman/master/v4.9237-618-g84a49bf0 2020-07-23 11:19:17
compiled with GCC 9.3.0 OS:Linux ARCH:x86_64

[ PROXMARK3 RDV4 ]
external flash: present
smartcard reader: present

[ PROXMARK3 RDV4 Extras ]
FPC USART for BT add-on support: absent

[ ARM ]
bootrom: RRG/Iceman/master/v4.9237-618-g84a49bf0 2020-07-23 11:19:39
os: RRG/Iceman/master/v4.9237-618-g84a49bf0 2020-07-23 11:19:50
compiled with GCC 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]

[ FPGA ]
LF image built for 2s30vq100 on 2020-02-22 at 12:51:14
HF image built for 2s30vq100 on 2020-01-12 at 15:31:16

[ Hardware ]
–= uC: AT91SAM7S512 Rev A
–= Embedded Processor: ARM7TDMI
–= Nonvolatile Program Memory Size: 512K bytes, Used: 259976 bytes (50%) Free: 264312 bytes (50%)
–= Second Nonvolatile Program Memory Size: None
–= Internal SRAM Size: 64K bytes
–= Architecture Identifier: AT91SAM7Sxx Series
–= Nonvolatile Program Memory Type: Embedded Flash Memory

[usb] pm3 --> lf sea
[=] NOTE: some demods output possible binary
[=] if it finds something that looks like a tag
[=] False Positives ARE possible
[=]
[=] Checking for known tags…
[=]
[+] EM410x pattern found

EM TAG ID : 00000874FC

Possible de-scramble patterns

Unique TAG ID : 0000102E3F
HoneyWell IdentKey {
DEZ 8 : 00554236
DEZ 10 : 0000554236
DEZ 5.5 : 00008.29948
DEZ 3.5A : 000.29948
DEZ 3.5B : 000.29948
DEZ 3.5C : 008.29948
DEZ 14/IK2 : 00000000554236
DEZ 15/IK3 : 000000001060415
DEZ 20/ZK : 00000000010002140315
}
Other : 29948_008_00554236
Pattern Paxton : 1880828 [0x1CB2FC]
Pattern 1 : 318749 [0x4DD1D]
Pattern Sebury : 29948 8 554236 [0x74FC 0x8 0x874FC]

[+] Valid EM410x ID found!

[usb] pm3 --> lf t55 detect
[!] :warning: Could not detect modulation automatically. Try setting it manually with ‘lf t55xx config’
[usb] pm3 -->

its still the same version
[ FPGA ]
LF image built for 2s30vq100 on 2020-02-22 at 12:51:14
@Compgeek can you check your FPGA version?
@Locutus it was a 2020 version. But i found some lua scripts for testing t55x7 that i will try out

That’s the right FPGA version, all seems to check out.

I did notice though in the screenshot that you didn’t run (or cut out from the log) hw tune

It should be run every time you open the software, especially if you are using the T55xx commands since coupling is critical.

I did it with and without hw tune and got the same result. Tested all the lua scripts for t55x7 and got Could not detect modulation automatically. Try setting it manually with ‘lf t55xx config’ on all the scripts

Damn, I think this is one for the gurus at the proxmark forum - just make sure you tell them what you’ve tried in your post!

Same thing, did you ever get it to work?

Still working on it and learning.

I am no expert, and this is just my 2 cents.
I noticed in your hw tune that your optimal voltage is around 70v, this suggests that your rdv4 lf antenna is set to long range mode. In this mode, it reads the implants better, but to read a card in this mode you really need to have the card at least 2.5-10cm (1-4") away from the antenna to read properly in my experience (I think the over voltage resets the chip mid read, and I read that somewhere here on the forum). You could also switch it to regular mode and do another hw tune to get the voltages down. Another trick I’ve been using when messing with my implant, it so have 2 sacrificial t5577 cards on hand, one in a completely wiped state (and just because I can, I will usually also write line by line block 1 and 2 of page 1 of the “wiped” card with the trackability data from my implant as a backup) and the second card, I do the entire procedure of wiping, detecting, writing, detecting, dumping to verify with both the card and the implant. At each step I do the card first then implant, then move to next step. This really seems to help when the detect command has trouble catching what state the implant is in, as well as slowing me down enough to not make silly mistakes.

3 Likes

Well, your 2 cents made me solve my problem, Thank you.
I check my setting on my proxmark and you are right. It was set to range. So I changed it and did a test and it did not work. So I used lf t55 write b 0 d 00088048 t and got it in test mode and then it was smooth sailing

5 Likes