GM You done f*cked UP with programming
Posted: Thu Jan 21, 2021 5:04 pm
What an absolute stupid cluster fuck Iv had looking at some workshops doing Global A BCM and ECU replacements.
They kept failing at the last steps after flashing, I had them send through the SPS debug log and went through it steps.
Here is a crash course on what SHOULD happen when doing the immobiliser in second hand modules:
1) The modules ORIGINAL immo for the VIN it came from is sent to the module to "unlock" it.
2) a 10min timer is then initiated
3) The new vehicles immo is then programmed to it.
4) The environment identifier (Unique fingerprint) is programmed to all modules
Going through both logs for two different Global A vehicles, step 1 is fucked up. SPS is trying to 'unlock' using the NEW vehicles immo instead of the original vehicles immo.
This makes sense why so many places say they are not dealing with Global A as its a royal fuckup trying to get the security correct.
Anyways.. just a heads up to anyone messing with newer modules. GM is phasing our the "prepare for removal" option, as that literally does nothing when looking at logs, as they want it all done in the same programming session.
They kept failing at the last steps after flashing, I had them send through the SPS debug log and went through it steps.
Here is a crash course on what SHOULD happen when doing the immobiliser in second hand modules:
1) The modules ORIGINAL immo for the VIN it came from is sent to the module to "unlock" it.
2) a 10min timer is then initiated
3) The new vehicles immo is then programmed to it.
4) The environment identifier (Unique fingerprint) is programmed to all modules
Going through both logs for two different Global A vehicles, step 1 is fucked up. SPS is trying to 'unlock' using the NEW vehicles immo instead of the original vehicles immo.
This makes sense why so many places say they are not dealing with Global A as its a royal fuckup trying to get the security correct.
Anyways.. just a heads up to anyone messing with newer modules. GM is phasing our the "prepare for removal" option, as that literally does nothing when looking at logs, as they want it all done in the same programming session.