using the user defined key of 0x944d worked for reading. When i tried to write, there were a bunch of timeouts, and PCMHammer froze. This bricked the ECU further. Guess it is getting opened up.
EDIT:
I think what happened is that at least one of the sectors got erased. After restarting PCMHammer and power cycling the ECU, the "Read properties" option failed with unexpected response. After that, i attempted a "write full flash" with a known good bin. PCMHammer successfully entered recovery mode and was able to write the full flash to the ECU.
After that the ECU appears to be fully functional and responds to all of the usual PCMHammer shenanigans. So, thank you kindly for the help!!
I would recommend caution with the particular bin in question as it does not seem to play nice with PCMHammer for whatever reason. Additionally, PCMBinBuilder does not like it. For example, if you try to change the eeprom data such as the VIN, you get:
* Eeprom_data *
Seed FFFF
Bin Key 944D [OK]
Hardware 9386530
Serial 1EB1VZ5E1227
Id 3154131286
Id2 4294967295
Broadcast ????
VIN 1GBFG15R121000000
Filling empty area
[OK]
Validating segments
[OK]
Setting VIN to: 1GCHK29UX2E696969
[OK]
Applying patches
[OK]
Calculating checksums
OS checksum: 0761 [OK]
EngineCal checksum: 5B78 [OK]
EngineDiag checksum: 4F5F [OK]
TransCal checksum: D377 [OK]
TransDiag checksum: B45D [OK]
Fuel checksum: B568 [OK]
System checksum: 79E3 [OK]
Speedo checksum: 609E [OK]
Calculating Eeprom key
Seed: FFFF
Bin Key: 944D [OK]
Validating data
Error:
Error: Eeprom_data Broadcast code missing!
so, something tells me that there is an issue with that particular bin, although i couldn't say exactly what it is.
Thanks for all the help and use caution!!
Bookmarks