pcmhacking.net

is it possible to quickly change the algorithm for the seed/key that the program uses? I need to change the odometer in a Colorado and the key that is calculated is incorrect. I dug around the code a bit and it looks like maybe there is already support for other algos.

also, anyone know the algo for these clusters?

Algo might be the same, but if it's an unknown Operating system it uses a different algo by default.. I'd try changing the default algo to the known algo that is used for known OS's and see if that unlocks it..
Post up if you have trouble changing that and building it, someone can probably do it for you pretty quick..
What are you using for hardware? Do you need a J2534 enabled version as well??

I did send you a pm with j25434 enabled and the default unknown OS algo changed to the same, but.. I just noticed you said colorado.. Isn't the colorado's odometer in the BCM?

thanks, i will check it out. as far I have figured out... the colorado ipc pulls the odometer from the bcm, but only if the bcm mileage is more than the current odometer mileage. so when this used cluster was plugged in, the higher mileage from the donor truck is what is showing. Apparently when this happens the odometer no longer counts as well.

i may be wrong about this though

so this cluster uses algo class2 0

but I didn't have any luck learning the mileage. response to the sent message: 6C60F03B9945000085E3 was: 6CF0607F3B994500008531

oh well, it was worth a shot.

gmtech825 wrote:so this cluster uses algo class2 0

but I didn't have any luck learning the mileage. response to the sent message: 6C60F03B9945000085E3 was: 6CF0607F3B994500008531

oh well, it was worth a shot.

Good try in any case.. Something I was going to try but haven't had the time yet.. Send a bunch of 1A commands to see what it spits out.. Maybe mileage isn't stored in DID 99 for your cluster but is put somewhere else??

ironduke wrote:

gmtech825 wrote:so this cluster uses algo class2 0

but I didn't have any luck learning the mileage. response to the sent message: 6C60F03B9945000085E3 was: 6CF0607F3B994500008531

oh well, it was worth a shot.

Good try in any case.. Something I was going to try but haven't had the time yet.. Send a bunch of 1A commands to see what it spits out.. Maybe mileage isn't stored in DID 99 for your cluster but is put somewhere else??

Colorado 04-12 and h3 06-10 store the Millage in the bcm (master) and ipc slave. If the millage is higher in the bcm it will over write the cluster. If the Millage is lower in the bcm cluster won’t count until the bcm reaches a amount higher then the cluster.

I can desolder the bcm chip and wipe it for what ever Millage you want I can only get the first major digits correct though. The last part is random.

I can wipe the eprom on the cluster and it will read zero, next key on off cycle it will read what’s in the bcm.

I have sent class 2 Millage to the cluster without a bcm present and it wrote Millage to the cluster! I have a cluster now that reads 999,999 seems to be the max it will go to.. lol

What I was trying to do was to get it to go to 1000,000 and then hopefully roll over to zero! But I can’t get it to read anything more then 999,999!

So I think the only way is via the eprom direct.

You probably need to send a higher mileage. The clusters can usually store higher mileage than 1,000,000. I’m not sure how the mileage is sent to the cluster but send all 0xFF for the mileage should set the mileage to the max it can store.

MIKE here is a new icon for IPC HAMMER