Hi everyone, I have a 2014 Chevy Cruze Diesel, I have seen a lot newer VCIMs from newer Generations being reprogrammed or directions to on this forum. However, I have a Gen A VCIM that I swapped out to get onstar back up from the old CDMA (2G) to the LTE/4G. I got this from a donor vehicle (2014 Silverado 1500) following matching the part numbers as specified under the Canadian CDMA transition bulletin. Surprisingly it works, I had OnStar activate but the vehicle shows as the Chevy 1500 in our myChevrolet app. I can navigate, remote lock/unlock, sound horn, light flash and locate the vehicle...but I am missing remote start and of course the vehicle (VIN) and model are incorrect. I would like to correct this.

From the rabbit hole I went down, everything I have found is conflicting - some folks said to order a newer VCIM module (F type) and program, or that I could not change the myChevrolet side - since they are one shot units and nothing can be done, and some folks said I can use SPS to change the VIN, but there were issues in the software trying to be reloaded for instance...

Has anyone had any luck on reprogramming and/or getting my Chevy to update? I assume if we can successfully reprogram, that Onstar could just re-register it.

So my questions:

1) Can you reconfigure or reset an already-initialized 23230538 for my Cruze’s actual VIN and vehicle equipment?

2) My goal is for OnStar and myChevrolet to recognize the Cruze and provide its supported features, not simply to change the VIN displayed by a diagnostic tool. How can I do this?

Info:

Cruze VIN: 1G1P75SZ7E7131548
Installed module: GM 23230538 / LG TC10AN3FUN5
Module STID: 117851388
Original module: 95328112

I had a good look at: GM Telematics control module reprogramming - GM Discussion Forum - www.CameraLoops.ru

Seems @Troy mentions he can use the calibration files to create the VIN and PIN change files needed to recycle these modules. Has anyone successfully done this with a Gen A part and linked it with Onstar and MyChevy? What else is normally involved?

I'm having the same issues with a slightly newer telematics module. I've got it on the bench and communicating with DPS, GDS, and SPS2.

The module does not show a VIN, but the used replacement module when registered with Onstar shows the incorrect vehicle in the app.

5 hours ago, BLKATSG said:

I'm having the same issues with a slightly newer telematics module. I've got it on the bench and communicating with DPS, GDS, and SPS2.

The module does not show a VIN, but the used replacement module when registered with Onstar shows the incorrect vehicle in the app.

Have you actually performed the VIN/PIN change and completed the appropriate SPS programming and activation, or have you only established bench communication so far?

It appears from what @Troy did or others is get the config and then modify this or procure the VIN/PIN combo. But I saw the part was not gen A of course..so wait!