pcmhacking.net

tech2win is not a j2534 application and is accessed quiet different. X-mark can means only that device is not accessible or available for connection.

Try some other j-program[universal patcher for example, or pcmhammer] and if you still get X, reinstall drivers and update firmware.
drivers and firmware must match for sure.

With MDI/MDI2, some antivirus programs will block the network connection that the MDI uses for its communication.

https://prnt.sc/S_pmOPkzR3Oq

"Hello, I have an MDI1 device with an MDI2 logo clone, and I can establish a connection as shown in the screenshot. I am already selecting the first option, MDI1, in the options. When I select the second option, it asks for MDI2, so I can't connect to it at all. The drive and device appear to be up to date."



Edit : https://ibb.co/chDdBdn

I think I finally did it. He's trying it right now. If I'm not mistaken

selqs wrote: ↑Sat Dec 14, 2024 10:32 pm https://prnt.sc/S_pmOPkzR3Oq

"Hello, I have an MDI1 device with an MDI2 logo clone, and I can establish a connection as shown in the screenshot. I am already selecting the first option, MDI1, in the options. When I select the second option, it asks for MDI2, so I can't connect to it at all. The drive and device appear to be up to date."



Edit : https://ibb.co/chDdBdn

I think I finally did it. He's trying it right now. If I'm not mistaken

Looks like it's working.. What did you find that got it working?

ironduke wrote: ↑Mon Dec 16, 2024 10:44 am

selqs wrote: ↑Sat Dec 14, 2024 10:32 pm https://prnt.sc/S_pmOPkzR3Oq

"Hello, I have an MDI1 device with an MDI2 logo clone, and I can establish a connection as shown in the screenshot. I am already selecting the first option, MDI1, in the options. When I select the second option, it asks for MDI2, so I can't connect to it at all. The drive and device appear to be up to date."



Edit : https://ibb.co/chDdBdn

I think I finally did it. He's trying it right now. If I'm not mistaken

Looks like it's working.. What did you find that got it working?

I updated all the drivers again and found that the electricity going to the ecu was weak. When the ecu electricity was sufficient, it started working.

It keeps scanning. I don't know if it can connect directly when I find the code. Can you recommend a program to connect directly and remove the password?

Interesting. MDI Powers off of the OBD2 port shared with the PCM so probably that means it was too low to power the MDI so the drivers would be correct in saying they cant find the MDI. Not sure why it'd work with other software.. might have been a driver version problem as well on top of that, or maybe just borderline power and one day was luckier than the others.

antus wrote: ↑Thu Dec 19, 2024 6:55 pm Interesting. MDI Powers off of the OBD2 port shared with the PCM so probably that means it was too low to power the MDI so the drivers would be correct in saying they cant find the MDI. Not sure why it'd work with other software.. might have been a driver version problem as well on top of that, or maybe just borderline power and one day was luckier than the others.

Yes, but if you do not provide sufficient electricity to the ECU via the battery and the power device, the ECU will not turn itself on.

I have another question in my mind. When I connected with another custom program, it gave me the seed and key outline directly. I tried to calculate it in 1-2 different places and enter with the key, but it did not enter. Could the seed key it gave be wrong? Or did I calculate it wrong? Could there be a different operation we did here with the given seed key? I could not make sense of it. If the key given with brute force is the same, I will be disappointed

what pcm? what seed and key?

antus wrote: ↑Thu Dec 19, 2024 7:28 pm what pcm? what seed and key?

e38 ecu - https://i.ibb.co/PNgGzw9/qwr.jpg