pcmhacking.net

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.

Sounds like the "right to repair" is being slowly trickled through.

Hopefully it's something you can make a tool for? What model is this for? Or is this in general.

The1 wrote:Sounds like the "right to repair" is being slowly trickled through.

Hopefully it's something you can make a tool for? What model is this for? Or is this in general.

One was for a 2018 HSV Colorado, One was for a GMC Sierra and also got another shop in the states asking about fixing a Chev Camaro with same problem.

So it appears to be a problem in general. I tend to use my own tools for all of this anyways which is why I don't come across the problem. The resetting/writing is very similar to that of the E55's immo. Just a matter of knowing the code or bruteforcing it (10sec per attempt = 27hours).

Once immo is correct, change VIN to new cars and then SPS update. SPS wont try do the immo as the vin matches.

Have you checked 1A table requests to see if they contain anything? Some of the bosch ecu's ive done are tricky to, you request a table and it returns nothing, but if you seed key unlock then request the same table you get data back with the pin.

GM screws something up, nah... I don't believe it.. lmao..

Have you tried the new techline connect that is supposed to be replacing tis2web,gds2,sps,si,VIR, and run and renew tech2win?? That is a joke..

and yes, sps has been getting worse with weird errors on the new brake module recalls we've been doing, try it in the morning and it crashes, try it in the afternoon and they might have it it fixed..

Starting to wonder how intentional this. Could be to force people to not use second hand modules?

clearly intentional with VZ

Techline can suck my hairy balls.
So shit.
Regular SPS and security access is now gone. Cunts

julespatch wrote:Techline can suck my hairy balls.
So shit.
Regular SPS and security access is now gone. Cunts

Yeeeeeeeeeeeeeeeeeeeeeeeepp.. they keep making things more and more complicated.

I get at least 2 calls a day now in regards to being unable to program second hand parts.

julespatch wrote:Techline can suck my hairy balls.
So shit.
Regular SPS and security access is now gone. Cunts

Oh, FFS, since when???