pcmhacking.net

Just a quick post to save some people a headache.

GM have updated techline connect again and found a way to lockout clone mdi and mdi2 devices.

I tested what would happen if a clone device was used and it is a bit of a nightmare, It will let you login and do one programming session, once you quit techline it locks your account so you can no longer launch techline at all.

The resolution required multiple emails and phone calls to the ebusiness helpcenter to get my account unlocked and was advised if I use the clone device again it will be locked again and i will nnot be able to unlock it.

Use a clone on techline at your own peril now

I've seen other posts on this, holy crap!!!!

I do not know about the fake mdi2/mdi stuffed inside an mdi2 case but the old school mdi 1's can have the serial number changed. I am assuming this is how they're identifying them?

Which version of mdi did you try this with? can you post up your serial number? it's been so long since I've done it I don't even know what the clone serial number is, curious if the fake mdi 2's have the same serial as the original fake mdi 1's...

I did a ton of programming yesterday but honestly think it was all with my genuine mdi 2.. Just because all the programming was newer vehicles that required mdi 2 usage. very curious if I can use my clone mdi 1's with changed serials..

Some debug log with command requests per initial connection will reveal how they identify the clones.

Clearly Bosch cracked the shits about how many clones were being used and got GM to detect them, Id expect the next firmware update for the MDI1's will brick every tool with a clone serial.

I did read a post on here about changing the serial, but not knowing anything about linux at all it is probably above my skill level.

I will check my serial when I get home, but it is 100 percent an mdi 1 clone, not the mdi 2 version

I was looking for something else in some of my way back files.. The clone mdi 1's serial should be 22129579
I have not personally witnessed this banning or shutdown of accounts but it is something to make me a bit paranoid.. I don't have any mdi's with the clone serial number so I should be all set.
I don't know much about linux either but I managed it, lol.. Been a few years though, I really should see if I have anything saved as far as instructions.. there should be some here or on the web somewhere..

Hi Ironduke,

I can confirm that is the serial number mine has.

I did find some instructions on here at mhh from what appeara to be the same guy, but i couldnt make heads or tails of them haha

beeradoc wrote: ↑Fri Sep 20, 2024 8:31 pm Hi Ironduke,

I can confirm that is the serial number mine has.

I did find some instructions on here at mhh from what appeara to be the same guy, but i couldnt make heads or tails of them haha

Yeah, I may have been involved in that topic that many years ago, lol.. Someone actually just pm'd me about it. My memory is shot and my files are long gone. I did it with a couple about 2 years ago in the home garage, I'm gonna check that pc and see if I can find some notes.. I can type a few things here but I'm not gonna get it right.. Think I telneted in and pushed mtd10 to the sd card, modded it, then pushed from the sd card back to flash.. I defintely don't remember much past that..

I tried programming today with a genuine mdi2. It would detect vin and get right up to detecting the module after saying it will use a licence, then crash saying there's no comms.
Anyone else had that issue?

Gonna hook a module on the bench and try later, might have been a glitch...but it was on 2 different cars

julespatch wrote: ↑Tue Sep 24, 2024 7:18 pm I tried programming today with a genuine mdi2. It would detect vin and get right up to detecting the module after saying it will use a licence, then crash saying there's no comms.
Anyone else had that issue?

Gonna hook a module on the bench and try later, might have been a glitch...but it was on 2 different cars

No problem programming on the bench or in car with a genuine MDI