MDI Clones and Techline

[kur4o]

If no reasonable explanation is provided, you definitely needs to raise the case to some agencies.

If it wasn`t mdi serial why they block you at the first place and requested pictures. They will never admit some errors, so some begging on the phone, might get you back your access.

There was 1 official government site that provide info for all subscription sites per manufacturer, but can`t remember it or find it now.

[Hacktacular]

If no reasonable explanation is provided, you definitely needs to raise the case to some agencies.

If it wasn`t mdi serial why they block you at the first place and requested pictures. They will never admit some errors, so some begging on the phone, might get you back your access.

There was 1 official government site that provide info for all subscription sites per manufacturer, but can`t remember it or find it now.

I appreciate the feedback. I am really disappointed in the way this was handled so far. It would be different if they said you did x, with an explanation. I wonder if they have banned my vin/device or if a new account would avoid the wait for answers?

[Gatecrasher]

Have you guys noticed this change to the individual VIN accounts?

There are two limitations on the per-vehicle programming. The subscription expires based on whichever of the following occurs first:
1. 24 Months.
2. The number of programming equals the number of programmable modules in the vehicle.

[beeradoc]

If no reasonable explanation is provided, you definitely needs to raise the case to some agencies.

If it wasn`t mdi serial why they block you at the first place and requested pictures. They will never admit some errors, so some begging on the phone, might get you back your access.

There was 1 official government site that provide info for all subscription sites per manufacturer, but can`t remember it or find it now.

I appreciate the feedback. I am really disappointed in the way this was handled so far. It would be different if they said you did x, with an explanation. I wonder if they have banned my vin/device or if a new account would avoid the wait for answers?

They have some really odd rules if you read closely, like no bench flashing modules

[Hacktacular]

If no reasonable explanation is provided, you definitely needs to raise the case to some agencies.

If it wasn`t mdi serial why they block you at the first place and requested pictures. They will never admit some errors, so some begging on the phone, might get you back your access.

There was 1 official government site that provide info for all subscription sites per manufacturer, but can`t remember it or find it now.

I appreciate the feedback. I am really disappointed in the way this was handled so far. It would be different if they said you did x, with an explanation. I wonder if they have banned my vin/device or if a new account would avoid the wait for answers?

They have some really odd rules if you read closely, like no bench flashing modules

Yes, I read that and thought that was odd as well.

[morfi]

Myself I got banned (I have the infamous SN 22129579) but unbanned conditionally to get a genuine MDI. I'll go with SN change soon but first on a smurf account and license. I'll then sniff the traffic to see what is sent to acdelco. Has anyone tried that already? I hope the traffic doesn't have any encryption (besides TLS) or some data mangling

[morfi]

Just a short update. I've captured some of the traffic but right now I'm stuck at VIN authorisation (awaiting reply from delco). I though the 1 day - 18 euro package does not have any VIN restrictions. So far the VIN auth endpoint was the first one where TLC is sending J2534 device ID. I'll share traces once I'll be able to do a successful programming... as a hobbyist it's infuriating how obsessed they are on gatekeeping. I wonder if "real" service shops have same issues with GM official software.

Can someone with gen MDI1/2 share what's the device ID that shows up in TLC/DPS. It'll look something like this: Bosch;MDI;04.04;J2534-2:SN='_________' CXN='USB';
I'm curious about this "04.04" and "-2" part if it's the same across all MDI[1/2] devices

[antus]

04.04 is the dll interface version, and its in the j2534-2 spec

https://www.sae.org/standards/content/j2534/2/

"The SAE J2534-2 document meets these needs by detailing extensions to API version 04.04 of the SAE J2534-1 specification. It is not required for an interface to be fully compliant with API version 04.04 of the SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the vehicle OEMs and scan tool manufacturers."

I cant say if all devices follow the same version of the spec. But I know 04.04 is typical and where Ive inspected device drivers i am yet see a different version on any tool that I have had on my desk.

[morfi]

Good so Ill proceed with this SN. Is it harmful (in general) to just update (program through SPS2) each and every module there is or its usually "dont touch it if it works or youll regret that". If its the former then I wonder why updating vehicle modules isnt standard maintenance procude when in shops (time consuming with no benefit?). I dont expect any more updates to my 10yo vehicle so I thought that if I go with every module update&programming while archiving the calibration files, theyll be usable for life

[ironduke]

Gm tells you not to update a module unless there's a bulletin/pi, or a recall or some other reason for doing it. yet they come out with updates and sometimes in the text it'll explain exactly why.. Sometimes there is no explanation.. So for this reason I always check module updates pertaining to a customer concern.
If your having a problem and contact gm technical assistance the first thing they ask is if you checked for module updates for the area of concern. So given this they also want you to do the same thing even if in print it does not state that.

Newer vehicles seem to be a lot more robust in the programming area. older vehicles especially pre CAN that use pin 2 vpw seem to be a lot more prone to crashing and bricking modules.. I think the newer ones are designed with a bootloader that can handle programming incidents a lot better than the old ones. Make sure battery voltage is good, battery is good, cables are good and there are no pets or trainee's, or kids, or anything touching the cables while it's programming.. They want a battery maintainer on the battery while programming to prevent a problem if the battery is too weak, imo a battery charger on low with a voltage display is ok as long as it's connected to the battery.. Yes it is pulsed dc but as long as the battery is decent that will be absorbed and programming will go just fine.

My own opinion is I have no problems checking and programming every module in a car if requested, but if it's pin 2 vpw I give them a heck of a warning and would rather not program a module even if there is an update unless they have a concern they are trying to address. Especially if it's 10+ years and the programming has been fine for that amount of time and usually well over 100k miles..