ECM VIN change for Insignia/Buick Regal E39, E59 ECM 2-Byte Seed

Hello I purchased this and BCM vin change.  BCM vin change works really great right out of the box.  However, the ECU vin change is giving me problems.  When I try to program the vin the ecu already has, there is no error, programming successful.  However, when I try to program a different vin, there is an error and programing fails.  I see a few others purchased this before and I assume had no problem.  Am I doing something wrong.  I am attaching a video of it working and it not working.  Thank you friends.

Ok, yes I was using a 14 or 15 Malibu ECU.  It sounds like if I get a 2014 Buick Regal ECU then I'll be good.  I'll try that, thanks for the fast reply.

4 hours ago, med458 said:

Ok, yes I was using a 14 or 15 Malibu ECU.  It sounds like if I get a 2014 Buick Regal ECU then I'll be good.  I'll try that, thanks for the fast reply.

Throw the DPS log up as well anyways, it sometimes might be a different factor.  Just curious what it threw back to you myself :).

15 hours ago, codebuilder said:

Throw the DPS log up as well anyways, it sometimes might be a different factor.  Just curious what it threw back to you myself :).

My pleasure, attached find the log for the failure and the log for the success. 

Tomorrow I am scheduled to pick up an ECU from a 13 Regal.  My research reveals that the E39A were in Regals 13-16.  So my assumption is that the ability to write vin via DPS is an exploit in the early ECUs that was patched by GM in the later ECUs.  However, I thought about it more and perhaps the ability to write vin via DPS might be a new feature that was added, rather than being viewed as a vulnerability that needs to be patched, it may be viewed as a feature improvement that was not included in early ECUs.  So after I pick up my '13 Regal ECU, I might still have the same problem.  But if that happens, I will just then try to get a '16 Regal ECU and hopefully that one will finally have the ability to write vin. 

The overall goal is to use a genuine ECU as an ECU emulator.  You might recall the issues with the emulator seller being unreliable, the software itself being expensive and also leading to accounts using the emulator being banned from SPS.  Lyubomir posted a picture of his bench and creating that for myself is what my overall goal is.  I would be quite happy if I could get a bunch of modules like he has all connected up on the bench so it looks pretty close to a complete vehicle.  Then I could use Troy's vin change files to change the modules vins so they all match when I connect up to SPS.  My hope is that would allow me to fly under the radar when I try to program a module.

ProgramLogecmfailure.Txt ProgramLogecmsuccess.Txt

For someone who got this working with Buick Regal ECU please tell me the year of the Regal ECU or the 8-digit acdelco part number, if its not too much trouble.  Or otherwise if it was a Malibu or some other car it worked with, any specific information for any USA ECU that worked.  Thank you and happy new year!

On 12/29/2023 at 8:38 PM, med458 said:

For someone who got this working with Buick Regal ECU please tell me the year of the Regal ECU or the 8-digit acdelco part number, if its not too much trouble.  Or otherwise if it was a Malibu or some other car it worked with, any specific information for any USA ECU that worked.  Thank you and happy new year!

I haven't been around much (busy with Christmas).  Actually, this is interesting... It goes into security access, returns to normal then tries to set the VIN.  This might still work with a modified utility.  

11 hours ago, codebuilder said:

I haven't been around much (busy with Christmas).  Actually, this is interesting... It goes into security access, returns to normal then tries to set the VIN.  This might still work with a modified utility.  

Yes, I agree.  I am going to look into it further.  I see no reason why this should not behave more like Troy's BCM utility I also bought.  I have also been busy but in a few days will focus on this problem.

Let me ask others who have used this file:  You have not needed to mess with seed/key or PIN to do a successful write, is that correct?

I've run into this same issue with a 2016 ATS-V E92 ECM

You can change the vin in the ECU with the current utility file you have.  You just need to open the file in a hex editor and try to understand what the utility file is doing.  The GM Interpreters .pdf is what you need to reference and read.

SPS will let you download new calibrations for vins even if the ECM vin is different.

On 6/21/2024 at 1:57 AM, wasiil said:

Okay. VIN changed.  Solution for my case:

I have edited the EEPROM dump with hexeditor without checksum correction and loaded it with IO terminal. The DPS and GDS2 see the new VIN.

It is good you figured it out, however I'd prefer to do it with DPS because it is easy and fast.  I would be happy to do the hard work of finding a specific part number from a specific year/make/model if someone would point me in the right direction, if they figured it out and can provide a part number and make/model/year from a known working vehicle.