Seed key brute force program.

[antus]

P12 is completely standard VPW communication. Nothing special (other than the algo) was needed from what we already had in the unlock in pcmhammer for P12.

[julespatch]

hey mate, just tried running in my Win7 32 bit VM after updating Fusion, now I get this message?
Anything I can do?

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: ECU_brute_force.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: d3f77273
Problem Signature 04: System.Core
Problem Signature 05: 4.7.3081.0
Problem Signature 06: 5b1888da
Problem Signature 07: b77
Problem Signature 08: 4d
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[ironduke]

I believe you need to have .net installed but I don't remember the version.. 4.8 probably.. I don't think I posted t he debug exe as that needs a different version I believe that comes with visual studio

[julespatch]

I believe you need to have .net installed but I don't remember the version.. 4.8 probably.. I don't think I posted t he debug exe as that needs a different version I believe that comes with visual studio

ok np. it was weird as it was working inside this VM before. all good, ran it on another machine

[selqs]

Hello,

When I try to connect to the E38 ECU with HP Tuners, I get error code X36. It seems the previous owner has locked it. I'm trying to use the program you mentioned, but I can't scan with it. I couldn't get it to work. I can connect with my MDI and MDI2 devices using their original software, but your program doesn't recognize the device as shown in the image. It detected the device once recently, but it didn't read the VIN code and couldn't perform the scan. Does it not work with MDI? Is there an updated version of the program? How can I find the password? I can also extract the .bin file from the ECU. However, at the moment, the device doesn't appear to be connected on the screen, even though it is physically connected. It's installed on my bench setup.





https://i.imgur.com/rI2wYzD.jpeg

[VX L67 Getrag]

you will need to get the MDI connected properly without the X through it & then it will start communicating!

[ironduke]

I'm wondering if you had the mdi connected to something else at that time and it was in use with another program?

The more I think about it the dll in use is probably an old one and might not be compatible with the newer mdi manager and firmware's for the mdi and mdi2..
I'll see if I can find a newer build and post it up..

[antus]

If that image is popping up with the red X its the drivers saying they cant talk to the MDI, not a problem with the application. If it pops up when the application tries to connect rather it says the app is talking to the drivers OK, the problem is after that. Like others said, perhaps in use/not connected/not powered. In use is likely, its easy to leave some other tool connected and minimized and forget about it. I have certainly done this before when messing around. Loggers like universal patcher are easy to set and literally forget when debugging an issue and monitoring the bus.

[selqs]

Thank you for your assistance and responses. During my tests, the device is not connected to any program. When I select the MDI from the CMD window and proceed, I hear the USB connection sound on the computer, and the reading process starts with my device as the lights activate, but it still shows as “X.”

I am using the latest GM Tech2, etc., and it seems, as you mentioned, the DLL package might not be compatible. Where can I find an older version of the driver DLL package? If I install it, maybe it will work. What do you think?

Also, I may have the chance to try another device. Which devices would be the most reliable and compatible? Would something like ELM work?

Thank you!

edit : " Senddata Exception #1 Error source: J2534-Sharp " I tried another mdi device. This one gave an error.

[ironduke]

Where did you get the program your trying? from github or a download here?
Might try turning off your firewall temporarily to see if that makes a difference..