Windows 10 - COM Port not being recognized

jayc · 2017-05-07 06:33:38

Folks!

Following the Windows instructions in this link https://github.com/Proxmark/proxmark3/wiki/Windows

I have made progress and now at the point of establishing a COM Port for the Proxmark3.

I did the FLASH NEW Bootrom from pm3-bin-756.

The flash was successful but the COM port is not showing up in the Device Manager.

I still see the libusb-win32 devices - ProxMark-3 RFID instrument in the Device Manager.

I need the COM port to execute the ./client/proxmark3.exe comX.

Thanks!

Last edited by jayc (2017-05-07 06:34:26)

ntk · 2017-05-07 10:38:05

After changing HID to CDC device by flashing bootrom, you need to inenabling, then de-install or upgrading the libusb-win32 to new CDC proxmark3 driver for window to see the re-flashed device. When you plugin off and re-plug in, you'll see window will search new driver, and try to setup PORT COM.

from window7 there is a problem with signed/unsigned USB proxmark driver.
(google for test mode, and unsigned driver window10 to see tool/howto get window accept proxmark3 driver)

run window in "test mode" to install the proxmark drivers. without a proxmark pluggin.

restart window then pluggin proxmark

marshmellow · 2017-05-07 15:25:53

If you flash the bootrom you will need to flash the arm as well.

And 765 is really really old.

ntk · 2017-05-07 17:17:40

@Marshmellow, I think that version should still be OK for now, because JayC just needs something simple to upgrade the proxmark3 ready to be a USB communications device class. After that he can tackle the step of install unsigned USB driver in window 10 "test mode".

When window complete installing the driver, then JayC can setup the build environment proxspace and compile more up-to-dated SW for his proxmark3 he will start studying and testing

@JayC just doing slowly each step, sail close to the instruction then you should be fine.

Last edited by ntk (2017-05-07 17:19:32)

marshmellow · 2017-05-07 17:21:52

If you have mismatched versions of bootrom and arm the device won't even be detected by any os... (Unless you hold the button to get ready to flash...)

ntk · 2017-05-07 17:39:18

@Marshmellow OK you are right better safe than sorry.

@JayC follow the instruction line for line, as MM said, do:

FLASH - Bootrom.bat

FLASH - FPGA fullimage.bat

FLASH - OS.bat

FLASH - NEW Bootrom (uses old flasher exe with -b option).bat

marshmellow · 2017-05-07 18:32:26

Don't use old flasher EVER, unless you know exactly what you are doing.

trevor_s · 2017-05-07 18:34:56

ntk wrote:

@Marshmellow OK you are right better safe than sorry.
@JayC follow the instruction line for line, as MM said, do:
FLASH - Bootrom.bat
FLASH - FPGA fullimage.bat
FLASH - OS.bat
FLASH - NEW Bootrom (uses old flasher exe with -b option).bat

I'm pretty much at this step on in device manager mine says just HID Compliant vender-defined device. Is there any way I can get this to the USB class. My bootrom is a different version than my OS is. I just need to know if there are any options. Thanks!

ntk · 2017-05-07 20:15:40

uuuhhhhmmm U thought that was the option....

it is long time ago before the dementia I recall I used a prebuilt windows, check the batch files and dependencies, then run those batch files to. Roughly it was so.

The other brutal way is do it straight over JTAG.

trevor_s · 2017-05-07 20:45:46

ntk wrote:

uuuhhhhmmm U thought that was the option....
it is long time ago before the dementia I recall I used a prebuilt windows, check the batch files and dependencies, then run those batch files to. Roughly it was so.
The other brutal way is do it straight over JTAG.

I'm not exactly sure what you're talking about here. Currently I can't flash using the regular flasher in Ubuntu. IT says 'Unknown Proxmark Mode". Are you saying I need to get that old release as described above and run all of those bat files? I just want to make sure. Thanks!

trevor_s · 2017-05-07 21:01:08

ntk wrote:

@Marshmellow OK you are right better safe than sorry.
@JayC follow the instruction line for line, as MM said, do:
FLASH - Bootrom.bat
FLASH - FPGA fullimage.bat
FLASH - OS.bat
FLASH - NEW Bootrom (uses old flasher exe with -b option).bat

Doesn't this contradict what MM said about never using an old Flasher?

jayc · 2017-05-07 21:16:09

Thanks!

What's the difference between the pm3-bin-756 versus the pm3-bin-756- lua branch?

iceman · 2017-05-07 21:35:43

I must hav missed something, why would you even consider flashing r756 ?

trevor_s · 2017-05-07 21:44:04

iceman wrote:

I must hav missed something, why would you even consider flashing r756 ?

does your HID brute work? its not registering any scans for me

Last edited by trevor_s (2017-05-07 22:50:26)

iceman · 2017-05-07 23:09:23

not at all, its unfinished with the generation of wiegand codes.

trevor_s · 2017-05-07 23:26:54

iceman wrote:

not at all, its unfinished with the generation of wiegand codes.

damn! best way to downgrade without breaking everything? this broke it for me https://github.com/exploitagency/github-proxmark3-standalone-lf-emulator

jayc · 2017-05-08 03:32:28

iceman wrote:

I must hav missed something, why would you even consider flashing r756 ?

It was in the instructions provided in https://github.com/Proxmark/proxmark3/wiki/Windows

What do you recommend?

Thanks.

iceman · 2017-05-08 07:59:36

[NOTE: if your proxmark has a firmware greater than r654 (old google code naming) you will need the new CDC serial drivers contained in pm3-bin-756 (cdc+lua).rar that is also available in the above link - more info in this paragraph]

Since r655 (included) proxmark uses the new CDC/Serial interface; it is very fast if compared to old libusb one. Usually proxmark boards bought online have r486 or r650 firmware so you will probably need to update your firmware if you want to use the latest code revisions !

So you had a firmware before r655 ?!? You must had bought it four years ago or earlier.

Proxmark3 community

Announcement

#1 2017-05-07 06:33:38

Windows 10 - COM Port not being recognized

#2 2017-05-07 10:38:05

Re: Windows 10 - COM Port not being recognized

#3 2017-05-07 15:25:53

Re: Windows 10 - COM Port not being recognized

#4 2017-05-07 17:17:40

Re: Windows 10 - COM Port not being recognized

#5 2017-05-07 17:21:52

Re: Windows 10 - COM Port not being recognized

#6 2017-05-07 17:39:18

Re: Windows 10 - COM Port not being recognized

#7 2017-05-07 18:32:26

Re: Windows 10 - COM Port not being recognized

#8 2017-05-07 18:34:56

Re: Windows 10 - COM Port not being recognized

#9 2017-05-07 20:15:40

Re: Windows 10 - COM Port not being recognized

#10 2017-05-07 20:45:46

Re: Windows 10 - COM Port not being recognized

#11 2017-05-07 21:01:08

Re: Windows 10 - COM Port not being recognized

#12 2017-05-07 21:16:09

Re: Windows 10 - COM Port not being recognized

#13 2017-05-07 21:35:43

Re: Windows 10 - COM Port not being recognized

#14 2017-05-07 21:44:04

Re: Windows 10 - COM Port not being recognized

#15 2017-05-07 23:09:23

Re: Windows 10 - COM Port not being recognized

#16 2017-05-07 23:26:54

Re: Windows 10 - COM Port not being recognized

#17 2017-05-08 03:32:28

Re: Windows 10 - COM Port not being recognized

#18 2017-05-08 07:59:36

Re: Windows 10 - COM Port not being recognized

Board footer