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.
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
Hi All, Hope someone may be able to assist.
I have just purchase a PM3 from china.
Followed the instructions for windows 7 from //www.proxmark.org/forum/viewtopic.php?id=1125
All seemed to be going great.
Was able to to do all, but when I got to "make clean" (all good), then when I did "make all", got some of the way, then I got
"proxguiqt.h:17:24: fatal error: QApplication: No such file or directory
compliation terminated.
make[1]: ***[pbj/proxgui.o] Error 1
maker[1]: Leaving directory 'pm3/client'
make: ***[client/all Error 2"
But still say unknown device when I plug the unit into my computer, nothing in the HID area.
cheers
Robert
Offline
sudo make
Offline
"sudo make"
Was told to start with//www.proxmark.org/forum/viewtopic.php?id=1125.
So I followed step by step till make all.
So you mean instead of testing by doing "make all", just do make
Offline
Looks like your qt directory is not known. Did you download the compile environment from the wiki?
Offline
Looks like your qt directory is not known. Did you download the compile environment from the wiki?
Done that one as well.
Then targeting to proxmark3.inf, in projects/proxmark3/pm3 for the driver.
I have also put computer in test mode, have disabled driver signing via gpedit.msc, but everthing I do the unit will sit in unkown device, and will not except the driver.
But happy to try again.
Cheers
Robert
Offline
I don't know why you want "make" the client
There're bulided file that you can download
If you want let it work in linux，maybe you should ask in http://www.proxmark.org/forum/viewforum.php?id=15
Offline
I was just following the instruction I was given, very new to this, so is there a better solution??.
Still my major issue is unable to load drivers, as my device is a unknown deivice, and windows will not see the driver in
MP3 as a driver for an unknown device.
Robert
Offline
So can Someone tell the name of the driver for Windows 7 64, that would be great.
Robert
Offline
Sounds to me like you got a bad device. If you hold the button down and connect the pm3 (keep the button pressed) does it detect?
Offline
Sounds to me like you got a bad device. If you hold the button down and connect the pm3 (keep the button pressed) does it detect?
I did what you asked, when plugged into top mini usb, while holding down the button, computer does see the unit, but still it still comes up as unknown device under other devices.
Cheers
Robert
Offline
As long as your device is not recognized with a correct driver, you cannot flash a new firmware. And without a new firmware you cannot use a new client software.
In device manager please right click on the "unknown device" then select properties, details, Hardware IDs. What do you get? Does it make difference with/without button pressed?
Offline
As long as your device is not recognized with a correct driver, you cannot flash a new firmware. And without a new firmware you cannot use a new client software.
In device manager please right click on the "unknown device" then select properties, details, Hardware IDs. What do you get? Does it make difference with/without button pressed?
Ok.
The hardware IDs I get is.
USB\VID_2D2D&PID_504D&REV_0001
USB\VID_2D2D&PID_504D
Makes no different if the button is presses or not.
I also purchased a new unit, still get the same results, unknown device in other devices, and when I upgrade driver, I get Window could not find driver software for your device.
Cheers
Robert
Last edited by Boof_rob (2018-05-03 01:10:22)
Offline
Try this driver file instead:
[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%ProviderName%
DriverVer=03/05/2018,1.1.1.0
[MANUFACTURER]
%ProviderName%=DeviceList, NTx86, NTamd64
[DeviceList.NTx86]
%DeviceName%=DriverInstall,USB\VID_9AC4&PID_4B8F
%DeviceName_old%=DriverInstall,USB\VID_2d2d&PID_504d
[DeviceList.NTamd64]
%DeviceName%=DriverInstall,USB\VID_9AC4&PID_4B8F
%DeviceName_old%=DriverInstall,USB\VID_2d2d&PID_504d
[DriverInstall]
include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=LowerFilterAddReg,SerialPropPageAddReg
[DriverInstall.Services]
include = mdmcpq.inf
AddService = usbser, 0x00000002, LowerFilter_Service_Inst
; This adds the serial port property tab to the device properties dialog
[SerialPropPageAddReg]
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
[Strings]
ProviderName = "proxmark.org"
DeviceName = "Proxmark3"
DeviceName_old = "Proxmark3 (old)"Offline
Try this driver file instead:
That worked, I now have aPromark3 (old) (Com32) in the Ports section of the Device manager. Is that correct??
Robert
Offline
Yes, that is OK. You may now continue with Flashing your Proxmark3 to the latest firmware.
Do NOT try to "Update Proxmark to the new new CDC Serial Interface".
Offline
Yes, that is OK. You may now continue with Flashing your Proxmark3 to the latest firmware.
Do NOT try to "Update Proxmark to the new new CDC Serial Interface".
So use the newest firmware from the official site?
Great
Robert
Offline
Any firmware you want. You just need to make sure that the client software and the firmware are the same version.
Last edited by piwi (2018-05-07 06:49:29)
Offline
Pages: 1