Proxmark3 community
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.
Announcement
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.
Pages: 1
#1 2012-09-19 18:14:54
- reks13
- Contributor
- Registered: 2010-12-10
- Posts: 16
Error in new update in command Hitag
I tested new update and see error.
When i tried write data 00 00 00 22 to page 6 of transponder and used "snoop" command i see log:
ETU :rssi: who bytes
---------+----+----+-----------
+ 0: : c0
+ 1456: : 9a 92 96 a4
+ 1456: : 64 80
+ 756: : 00 00 00 44
So password was 4D 49 4B 52, in log it looks like password *2 and data is *2
Offline
#2 2012-09-19 18:16:28
- reks13
- Contributor
- Registered: 2010-12-10
- Posts: 16
Re: Error in new update in command Hitag
Also what is ETU, rssi ?
Offline
#3 2012-09-19 18:35:32
- reks13
- Contributor
- Registered: 2010-12-10
- Posts: 16
Re: Error in new update in command Hitag
More about it, in log no data from TAG, i can see data from reader only.
But reader show readed data from TAG, proxmark doesnt has any info from TAG.
Offline
#4 2012-09-19 19:35:25
- rule
- Member
- Registered: 2008-05-21
- Posts: 417
Re: Error in new update in command Hitag
Use a different angle, distance or antenna. This will solve your problem.
Furthermore, you see that it seems to miss the first bit, which makes the Manchester decoding fail (1 bit shifted). This is indeed the same as if you value is multiplied by 2, but it actually just shifted, because the first bit is missing 
A better trace should solve the bit-shift problem as well!
Offline
Pages: 1