Seed key brute force program.

selqs · Post by **selqs** » Mon Dec 09, 2024 3:52 pm

I tried the compilation program both from GitHub and here, and there’s no difference in either. My firewalls are off, and the antivirus program is disabled.

Post by **kur4o** » Mon Dec 09, 2024 5:35 pm

Your firmware might not be compatible with driver package you have installed, or it can be corrupted. You need to try firmware update or recovery of the mdi, There is some tutorials on google.

ironduke · Post by **ironduke** » Mon Dec 09, 2024 7:26 pm

Not sure what the other J2534 device is you have listed, don't know if that's screwing things up.

I just ran thru the github version and the version here without any issues with mdi and mdi2 here on my bench.
Updated it with a newer dll and a few other small changes, don't think it'll make a difference though.
Updated version is on the first page and below.

ECU.BruteForcer.0.0.9.7z

By the way.. I will edit the main page later but this is written to work with GM ecm's that communicate on pins 6 & 14 using high speed CAN AND use a 2 byte seed and key..
Will not work on older pin 2 VPW or newer 5 byte ecm's.

Post by **Tazzi** » Mon Dec 09, 2024 11:00 pm

Brute forcing a 5byte ECM.... Now, that may take a while

FFFFFFFFFF combinations... at 10seconds a pop... thats 348,652 years (Yes... years...)

selqs · Post by **selqs** » Tue Dec 10, 2024 2:47 pm

https://prnt.sc/aYoHmbh6b4tX
https://prnt.sc/yltYHjrYloyx

Hello, I tried your new version, and this time, without even trying to connect or performing a VIN check, I get an error as shown in the screenshot. Is there anything current that you need from me? I want to help. Could it be the program's DLL files or something similar? Or where can I find the older MDI DLL version to install and try its drivers?

ironduke · Post by **ironduke** » Tue Dec 10, 2024 3:03 pm

selqs wrote: Tue Dec 10, 2024 2:47 pm https://prnt.sc/aYoHmbh6b4tX
https://prnt.sc/yltYHjrYloyx

Hello, I tried your new version, and this time, without even trying to connect or performing a VIN check, I get an error as shown in the screenshot. Is there anything current that you need from me? I want to help. Could it be the program's DLL files or something similar? Or where can I find the older MDI DLL version to install and try its drivers?

That looks like it is not connected correctly. I get that message if the ecm is not powered up, wired up correctly, etc.. Very odd since you say the same tool with the same wiring communicates with other software..

Are you extracting the folder? or trying to run it from inside the zipped folder? Need to extract then open the folder and run the exe..

selqs · Post by **selqs** » Tue Dec 10, 2024 3:05 pm

ironduke wrote: Tue Dec 10, 2024 3:03 pm
selqs wrote: Tue Dec 10, 2024 2:47 pm https://prnt.sc/aYoHmbh6b4tX
https://prnt.sc/yltYHjrYloyx

Hello, I tried your new version, and this time, without even trying to connect or performing a VIN check, I get an error as shown in the screenshot. Is there anything current that you need from me? I want to help. Could it be the program's DLL files or something similar? Or where can I find the older MDI DLL version to install and try its drivers?
That looks like it is not connected correctly. I get that message if the ecm is not powered up, wired up correctly, etc.. Very odd since you say the same tool with the same wiring communicates with other software..

I can connect the same way via Tech2 on the bench, and everything is visible. What is the version of your MDI Manager?

ironduke · Post by **ironduke** » Tue Dec 10, 2024 3:07 pm

selqs wrote: Tue Dec 10, 2024 3:05 pm
ironduke wrote: Tue Dec 10, 2024 3:03 pm
selqs wrote: Tue Dec 10, 2024 2:47 pm https://prnt.sc/aYoHmbh6b4tX
https://prnt.sc/yltYHjrYloyx

Hello, I tried your new version, and this time, without even trying to connect or performing a VIN check, I get an error as shown in the screenshot. Is there anything current that you need from me? I want to help. Could it be the program's DLL files or something similar? Or where can I find the older MDI DLL version to install and try its drivers?
That looks like it is not connected correctly. I get that message if the ecm is not powered up, wired up correctly, etc.. Very odd since you say the same tool with the same wiring communicates with other software..
I can connect the same way via Tech2 on the bench, and everything is visible. What is the version of your MDI Manager?

Via tech2? or tech2win with the mdi???
As far as versions I am running the latest and greatest from gm/bosch

selqs · Post by **selqs** » Tue Dec 10, 2024 3:09 pm

ironduke wrote: Tue Dec 10, 2024 3:07 pm
selqs wrote: Tue Dec 10, 2024 3:05 pm
ironduke wrote: Tue Dec 10, 2024 3:03 pm

That looks like it is not connected correctly. I get that message if the ecm is not powered up, wired up correctly, etc.. Very odd since you say the same tool with the same wiring communicates with other software..
I can connect the same way via Tech2 on the bench, and everything is visible. What is the version of your MDI Manager?
Via tech2? or tech2win with the mdi???
As far as versions I am running the latest and greatest from gm/bosch

I can connect to the ECU using Tech2Win and the same cable setup with my HP Tuners device for software access.

ironduke · Post by **ironduke** » Tue Dec 10, 2024 3:40 pm

Real dumb question.. Do you have a genuine mdi 2 or a clone MDI 2?? If you open mdi manager is it showing up as a mdi1 or mdi 2?
Maybe try choosing mdi 1 in the menu and see what happens.. Really don't see why your having an issue.

Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.

Re: Seed key brute force program.