@all Thanks for all your Help first of all
@Pilgrimsmaster Aww, now I see it too I only checked if OS and Bootrom are the same :'D Can happen
But, before we celebrate:
Unfortunately, it still does not work
I tried what @APartOfMe said, downloaded https://www.proxmarkbuilds.org/latest/rrg_other , had the Proxmark3 Easy on COM5, as said in the “Getting Started”.
First used the “pm3-flash-bootrom.bat”, then “pm3-flash-fullimage.bat” (both did their thing, and exited OK).
Bootup Info
[=] Using UART port COM5
[=] Communicating with PM3 over USB-CDC
██████╗ ███╗ ███╗█████╗
██╔══██╗████╗ ████║╚═══██╗
██████╔╝██╔████╔██║ ████╔╝
██╔═══╝ ██║╚██╔╝██║ ╚══██╗
██║ ██║ ╚═╝ ██║█████╔╝ Iceman
╚═╝ ╚═╝ ╚═╝╚════╝ bleeding edge
https://github.com/rfidresearchgroup/proxmark3/
[=] Creating initial preferences file
[=] Saving preferences…
[+] saved to json file C:\Users\simon\Desktop\prox_compiled\client/.proxmark3/preferences.json
[ Proxmark3 RFID instrument ]
[ CLIENT ]
client: RRG/Iceman/master/v4.13441-970-gf61f8e7f9 2021-09-09 11:31:49
compiled with MinGW-w64 10.3.0 OS:Windows (64b) ARCH:x86_64
[ PROXMARK3 ]
firmware… PM3 GENERIC
[ ARM ]
bootrom: RRG/Iceman/master/v4.13441-970-gf61f8e7f9 2021-09-09 11:31:36
os: RRG/Iceman/master/v4.13441-970-gf61f8e7f9 2021-09-09 11:31:43
compiled with GCC 10.1.0
[ FPGA ]
LF image built for 2s30vq100 on 2020-07-08 at 23:08:07
HF image built for 2s30vq100 on 2020-07-08 at 23:08:19
HF FeliCa image built for 2s30vq100 on 2020-07-08 at 23:08:30
[ Hardware ]
–= uC: AT91SAM7S512 Rev B
–= Embedded Processor: ARM7TDMI
–= Internal SRAM size: 64K bytes
–= Architecture identifier: AT91SAM7Sxx Series
–= Embedded flash memory 512K bytes ( 53% used )
After that, I opened “pm3.bat” and ran the Usual Commands trying to get a read (lf search, lf t55xx detect)
After many tries, it still is the Same as Before.
No change, lf search
still says:
[usb] pm3 → lf search
[=] NOTE: some demods output possible binary
[=] if it finds something that looks like a tag
[=] False Positives ARE possible
[=]
[=] Checking for known tags…
[=]
[-] No known 125/134 kHz tags found!
[=] Couldn’t identify a chipset
And lf t55xx detect
:
[usb] pm3 → lf t55xx detect
[!] Could not detect modulation automatically. Try setting it manually with ‘lf t55xx config’
@amal:
I can read the T5577 cards (programmed as em410x) included with the Proxmark, and my EM Chip Workplace keyfob, without Problem. Even before, with the mismatched Client/Firmware Situation.
Are there any things I can try before calling it quit with the LF side? I mean it is unusable anyway, so if it should get corrupted while trying “risky” commands to revive it, it wouldn’t be a problem. (before just giving up, we could at least try)
Are there options, worth trying?
In the situation, the Chip (LF Side only) has a Hardware Problem (would be a Bummer, but I understand that it can, unfortunately, happen sometimes) what would be the procedure?
I really don’t want to get through all that trouble removing/replacing the NExT.
(saw your post: amal.net/?p=3540)
I still have use for NExT, it’s basically an xNT now.
I am thinking of just buying an xEM, get it implanted in R0. Then my left Hand is HF (NExT with only the xNT Part working) and my right LF (xEM).
And the xEM should even have a little more read Range, right?
What are your guys thoughts ?