From my experience, most modules are safe to program as their internal boot code will prevent a permanent brick until a completed OS/Cals is performed.
ALTHOUGH, some modules cause much better headaches then others. Perfect example is the 2013-ish to 2019 GMC/Chev instrument clusters, some variants that require an operating system update, will then have the screen will go completely black and no longer operate. This is due to requiring a USB update, which, I am sure some techs have found out the hard way, does not always get detected after the OS update.
As for MDI SN, I am pretty sure they are scanning the logs that get uploaded to their server after the app loads in. These logs do not appear to disappear afterwards, so I believe they scan them every single time.
I had a local workshop have their account flagged due to using a clone MDI, so they created a fresh account and bought a genuine MDI2 straight from Bosch, but their account flagged still after their first session.
The email they got from support suggested to clean install Techline and wipe away old traces before using it again.
Im guessing the above.. is what causes some people to get caught out?
MDI Clones and Techline
Re: MDI Clones and Techline
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726

Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
