pcmhacking.net

I have a 2008 pontiac g8 reading the cluster's st95160 chip EEPROM trying to edit, my initial read was corrupt. I tried blanking my chip and rewriting my stock .bin but it is a corrupted read the hex is skewed and the ascii doesnt list my VIN. Does anyone have a 08 G8 .bin file they would share with me, so I can get my cluster working please, thank you

jake9713 wrote:I have a 2008 pontiac g8 reading the cluster's st95160 chip EEPROM trying to edit, my initial read was corrupt. I tried blanking my chip and rewriting my stock .bin but it is a corrupted read the hex is skewed and the ascii doesnt list my VIN. Does anyone have a 08 G8 .bin file they would share with me, so I can get my cluster working please, thank you

Unfortunately not of the eeprom since I use the obd port for all its programming. What were you trying to do to it??

Tazzi wrote:

jake9713 wrote:I have a 2008 pontiac g8 reading the cluster's st95160 chip EEPROM trying to edit, my initial read was corrupt. I tried blanking my chip and rewriting my stock .bin but it is a corrupted read the hex is skewed and the ascii doesnt list my VIN. Does anyone have a 08 G8 .bin file they would share with me, so I can get my cluster working please, thank you

Unfortunately not of the eeprom since I use the obd port for all its programming. What were you trying to do to it??

I am trying to correct my odo, the car was originally flood salvaged, original cluster was no good, I bought another used cluster, but the vin and odo are wrong, trying to correct it with my hex editor.

jake9713 wrote: I am trying to correct my odo, the car was originally flood salvaged, original cluster was no good, I bought another used cluster, but the vin and odo are wrong, trying to correct it with my hex editor.

Ok, read the original one and dump into the replacement.?

Using eeprom programmers does run the risk of corrupted data as there are no checkin checks on eeproms to validate what you have is correct. A “verify” which most softwares have will just re-read but if it’s reading incorrectly, it’s just going to validate incorrect data.

Anyways, clone the original or even just move the eeprom from the original to the replacement cluster.

I would do that, however I dont have the original. The original cluster was corroded so badly that it all crumbled apart and I had to toss it. How are you doing it through OBDII, doesnt gm sps not allow you to flash IPC? Or are you using a 3rd party?

Oh right, thats no good!
I use my own software since I provide programming service for Holdens and most General Motor makes including the G8's.

Tazzi wrote:Oh right, thats no good!
I use my own software since I provide programming service for Holdens and most General Motor makes including the G8's.

Thanks for replying Tazzi, any chance if I blank this EEPROM completely and try to do a SPS2 flash with my MDI if it will work? I know generally dealers cant set mileage just want to get it working again with a base file. Writing that corrupt file was a big rookie mistake... I didnt notice it was corrupted until I found the vin missing and botched code at the end... I read on the G8 forums that if I plug this in as is with mixmatched miles and VIN it will trip some sort of tamper codes and lock down some other modules? Any truth to that? its an 08 model 6.0L 6speed auto car, USA spec. Black cluster 92220531 MB reads 8200-28481-04

jake9713 wrote:

Tazzi wrote:Oh right, thats no good!
I use my own software since I provide programming service for Holdens and most General Motor makes including the G8's.

Thanks for replying Tazzi, any chance if I blank this EEPROM completely and try to do a SPS2 flash with my MDI if it will work? I know generally dealers cant set mileage just want to get it working again with a base file. Writing that corrupt file was a big rookie mistake... I didnt notice it was corrupted until I found the vin missing and botched code at the end... I read on the G8 forums that if I plug this in as is with mixmatched miles and VIN it will trip some sort of tamper codes and lock down some other modules? Any truth to that? its an 08 model 6.0L 6speed auto car, USA spec. Black cluster 92220531 MB reads 8200-28481-04

There is only 1 person in the world I have seen talk about "tamper codes" and he clearly has no idea what he's talking about (Also why they dont provide a programming service for the clusters).

Wiping the eeprom is kinda like wiping your computer hdd. If theres nothing there... SPS will not understand what to do.

More then welcome to ship it to my colleague in Canada and we can look into trying to recover it, done plenty of the G8s over the years.

ah makes sense, I may have to resort to that, im going to try to source a bin file if at possible first, thanks for all the help