hello, i got a pm3 today and i basically wiped off everything by accident but i luckily copied the stuff anyways and its on another tag. Is there a way to rewrite my hid chip to restore it. thanks.
1 Like
Maybe? There’s so much information missing here to know for sure.
Is your original fob a T5577 chip?
Did you do a T5577 dump?
How did you record the information?
1 Like
It’s a chip, I did Lf search then took a screen shot of it I have the raw thing and all of that
1 Like
Can you post the screenshot? Yes your fob info will be in it but as long as you don’t give your name and what is for then it’s basically useless to the Internet
1 Like
Have you tried using the lf hid clone command?
What does it say?
1 Like
I’ve tried and it says done but then after I do lf search it says no known 125/134 khz tags found in red. Is there anything I can do to rewrite it.
1 Like
That could just be a coupling/positioning issue
Try lf hid reader -@, this will make it scan continuously so you can move the card all over/under/around the PM3 and see if you can get it to read
1 Like
Doesn’t work, comes up with the same thing in red when I do lf search. Basically I also thought I should let you know that I cleared of all the previous data before it by accident and that’s why I ran into this issue. What else should I try to try and rewrite into it
1 Like
The next steps would be trying to communicate directly with the T5577, try lf t5 detect until you can find a position with a good connection
1 Like
Still doesnt work. i believe its bricked is there any way i can try to unbrick it when i do the config it says Chip type… T55x7
[=] Modulation… ASK
[=] Bit rate… 0 - RF/8
[=] Inverted… No
[=] Offset… 0
[=] Seq. terminator… No
[=] Block0… 00008000 (user set)
[=] Downlink mode… default/fixed bit length
[=] Password set… Yes
[=] Password… 00000000
If you can’t get reliable results from the lf t5 detect then you can’t communicate with the chip to do anything. Either because the chip itself is misbehaving or due to improper coupling
1 Like
Interesting. This is probably why nothing is working.
1 Like
nothing works, i guess the fobs broken after all of that it still says this when i do the lf t55xx config command
[=] Chip type… T55x7
[=] Modulation… ASK
[=] Bit rate… 0 - RF/8
[=] Inverted… No
[=] Offset… 0
[=] Seq. terminator… No
[=] Block0… 00000000 (n/a)
[=] Downlink mode… default/fixed bit length
[=] Password set… No
This is different. I’m betting it might be revivable but not without a lot of fidgeting
1 Like
Hi, The lf t5 config command shows what the proxmark settings currently are, not the chip.
they will probably eather be the defaults, or the result of the last successful t5 detect.
You could try:
script run lf_t55xx_fix
There is also test mode which will work only if it’s a genuine t5577, not if it’s a t5200 which many are.
Some commands to toss at it might be:
lf t55 write -b 0 -d 000880E0 --r0
lf t55 write -b 0 -d 000880E0 --r1
lf t55 write -b 0 -d 000880E0 --r1 -t
lf t55 write -b 0 -d 000880E0 --r2
lf t55 write -b 0 -d 000880E0 --r2 -t
lf t55 write -b 0 -d 000880E0 --r3
lf t55 write -b 0 -d 000880E0 --r3 -t
There are some good posts on here about all that already, so no point repeating them!
Do a
lf t5 det after that lot, and perhaps you might get a response!
Then you’ll have to do the hid clone to put it back to what it should be!
Of course, all this assumes it’s a t55xx, if it’s not, then it’s eather read only, or busted in some way we don’t have enough info to know about!