PCM Hammer Release 021
- antus
- Site Admin
- Posts: 8996
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Hammer Release 021
No. Write calibration is intended to be light touch. Changing the param block is essentially a clone, and will break people who are using commercial software because the identification of their pcm (vin / serial) will change for a calibration write. That should not happen for a calibration write.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: PCM Hammer Release 021
Tried with cardaq+3/snapon passthru pro 4. Shows voltage 0.03 and failed initializing. Works fine with sps2
got it work... think was bad connection.
new problem. here's data log.
[09:30:24:177] PCM Hammer 021
[09:30:24:185] Wednesday, September 25 2024 @09:30:24:18
[09:30:24:188] Initializing J2534 Device
[09:30:24:199] Loaded DLL
[09:30:24:208] Connected to the device.
[09:30:24:210] Battery Voltage is: 12.5
[09:30:24:220] Protocol Set
[09:30:24:221] Device initialization complete.
[09:30:24:322] Loaded help.html from network.
[09:30:24:323] Loaded start.txt from network.
[09:30:24:323] Loaded credits.html from network.
[09:30:24:336] Thanks for using PCM Hammer.
[09:30:44:962] Will save to C:\Users\Matt\Downloads\PcmHammer021\PcmHammer021\h3 test.bin
[09:30:55:052] Querying operating system of current PCM.
[09:30:55:066] TX: 6C 10 F0 3C 0A
[09:30:57:085] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:30:57:087] Sending 'test device present' notification.
[09:30:57:087] TX: 8C FE F0 3F
[09:30:59:099] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:30:59:099] Sending 'test device present' notification.
[09:30:59:100] TX: 8C FE F0 3F
[09:31:01:111] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:01:112] Sending 'test device present' notification.
[09:31:01:112] TX: 8C FE F0 3F
[09:31:03:129] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:03:130] Sending 'test device present' notification.
[09:31:03:130] TX: 8C FE F0 3F
[09:31:05:149] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:05:150] Receive timed out. Attempt #5, Timeout #5.
[09:31:05:150] TX: 6C 10 F0 3C 0A
[09:31:07:159] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:07:160] Sending 'test device present' notification.
[09:31:07:160] TX: 8C FE F0 3F
[09:31:09:165] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:09:168] Sending 'test device present' notification.
[09:31:09:172] TX: 8C FE F0 3F
[09:31:11:190] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:11:193] Sending 'test device present' notification.
[09:31:11:196] TX: 8C FE F0 3F
[09:31:13:216] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:13:218] Sending 'test device present' notification.
[09:31:13:221] TX: 8C FE F0 3F
[09:31:15:232] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:15:236] Receive timed out. Attempt #5, Timeout #5.
[09:31:15:240] Operating system query failed, will retry: Error
[09:31:15:245] TX: 6C 10 F0 20
[09:31:15:253] TX: 6C 10 F0 20
[09:31:15:261] TX: 6C 10 F0 3C 0A
[09:31:17:286] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:17:290] Sending 'test device present' notification.
[09:31:17:293] TX: 8C FE F0 3F
[09:31:19:307] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:19:310] Sending 'test device present' notification.
[09:31:19:313] TX: 8C FE F0 3F
[09:31:21:329] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:21:332] Sending 'test device present' notification.
[09:31:21:335] TX: 8C FE F0 3F
[09:31:23:360] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:23:363] Sending 'test device present' notification.
[09:31:23:366] TX: 8C FE F0 3F
[09:31:25:382] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:25:386] Receive timed out. Attempt #5, Timeout #5.
[09:31:25:390] TX: 6C 10 F0 3C 0A
[09:31:27:403] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:27:406] Sending 'test device present' notification.
[09:31:27:410] TX: 8C FE F0 3F
[09:31:29:431] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:29:434] Sending 'test device present' notification.
[09:31:29:437] TX: 8C FE F0 3F
[09:31:31:454] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:31:458] Sending 'test device present' notification.
[09:31:31:461] TX: 8C FE F0 3F
[09:31:33:479] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:33:482] Sending 'test device present' notification.
[09:31:33:485] TX: 8C FE F0 3F
[09:31:35:505] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:35:508] Receive timed out. Attempt #5, Timeout #5.
[09:31:35:511] Operating system query failed: Error
[09:31:35:514] Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[09:31:35:518] Sending 'test device present' notification.
[09:31:35:522] TX: 8C FE F0 3F
[09:32:28:599] Sending 'test device present' notification.
[09:32:28:604] TX: 8C FE F0 3F
[09:32:28:615] Using OsID: 12612557
[09:32:28:620] Suppressing VPW chatter.
[09:32:28:623] TX: 6C FE F0 28 00
[09:32:28:632] Sending 'test device present' notification.
[09:32:28:635] TX: 8C FE F0 3F
[09:32:30:650] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:32:30:763] Sending seed request.
[09:32:30:767] TX: 6C 10 F0 27 01
[09:32:32:782] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:32:32:785] No response to seed request.
[09:32:32:788] Unlock was not successful.
got it work... think was bad connection.
new problem. here's data log.
[09:30:24:177] PCM Hammer 021
[09:30:24:185] Wednesday, September 25 2024 @09:30:24:18
[09:30:24:188] Initializing J2534 Device
[09:30:24:199] Loaded DLL
[09:30:24:208] Connected to the device.
[09:30:24:210] Battery Voltage is: 12.5
[09:30:24:220] Protocol Set
[09:30:24:221] Device initialization complete.
[09:30:24:322] Loaded help.html from network.
[09:30:24:323] Loaded start.txt from network.
[09:30:24:323] Loaded credits.html from network.
[09:30:24:336] Thanks for using PCM Hammer.
[09:30:44:962] Will save to C:\Users\Matt\Downloads\PcmHammer021\PcmHammer021\h3 test.bin
[09:30:55:052] Querying operating system of current PCM.
[09:30:55:066] TX: 6C 10 F0 3C 0A
[09:30:57:085] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:30:57:087] Sending 'test device present' notification.
[09:30:57:087] TX: 8C FE F0 3F
[09:30:59:099] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:30:59:099] Sending 'test device present' notification.
[09:30:59:100] TX: 8C FE F0 3F
[09:31:01:111] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:01:112] Sending 'test device present' notification.
[09:31:01:112] TX: 8C FE F0 3F
[09:31:03:129] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:03:130] Sending 'test device present' notification.
[09:31:03:130] TX: 8C FE F0 3F
[09:31:05:149] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:05:150] Receive timed out. Attempt #5, Timeout #5.
[09:31:05:150] TX: 6C 10 F0 3C 0A
[09:31:07:159] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:07:160] Sending 'test device present' notification.
[09:31:07:160] TX: 8C FE F0 3F
[09:31:09:165] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:09:168] Sending 'test device present' notification.
[09:31:09:172] TX: 8C FE F0 3F
[09:31:11:190] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:11:193] Sending 'test device present' notification.
[09:31:11:196] TX: 8C FE F0 3F
[09:31:13:216] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:13:218] Sending 'test device present' notification.
[09:31:13:221] TX: 8C FE F0 3F
[09:31:15:232] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:15:236] Receive timed out. Attempt #5, Timeout #5.
[09:31:15:240] Operating system query failed, will retry: Error
[09:31:15:245] TX: 6C 10 F0 20
[09:31:15:253] TX: 6C 10 F0 20
[09:31:15:261] TX: 6C 10 F0 3C 0A
[09:31:17:286] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:17:290] Sending 'test device present' notification.
[09:31:17:293] TX: 8C FE F0 3F
[09:31:19:307] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:19:310] Sending 'test device present' notification.
[09:31:19:313] TX: 8C FE F0 3F
[09:31:21:329] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:21:332] Sending 'test device present' notification.
[09:31:21:335] TX: 8C FE F0 3F
[09:31:23:360] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:23:363] Sending 'test device present' notification.
[09:31:23:366] TX: 8C FE F0 3F
[09:31:25:382] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:25:386] Receive timed out. Attempt #5, Timeout #5.
[09:31:25:390] TX: 6C 10 F0 3C 0A
[09:31:27:403] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:27:406] Sending 'test device present' notification.
[09:31:27:410] TX: 8C FE F0 3F
[09:31:29:431] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:29:434] Sending 'test device present' notification.
[09:31:29:437] TX: 8C FE F0 3F
[09:31:31:454] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:31:458] Sending 'test device present' notification.
[09:31:31:461] TX: 8C FE F0 3F
[09:31:33:479] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:33:482] Sending 'test device present' notification.
[09:31:33:485] TX: 8C FE F0 3F
[09:31:35:505] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:31:35:508] Receive timed out. Attempt #5, Timeout #5.
[09:31:35:511] Operating system query failed: Error
[09:31:35:514] Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[09:31:35:518] Sending 'test device present' notification.
[09:31:35:522] TX: 8C FE F0 3F
[09:32:28:599] Sending 'test device present' notification.
[09:32:28:604] TX: 8C FE F0 3F
[09:32:28:615] Using OsID: 12612557
[09:32:28:620] Suppressing VPW chatter.
[09:32:28:623] TX: 6C FE F0 28 00
[09:32:28:632] Sending 'test device present' notification.
[09:32:28:635] TX: 8C FE F0 3F
[09:32:30:650] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:32:30:763] Sending seed request.
[09:32:30:767] TX: 6C 10 F0 27 01
[09:32:32:782] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:32:32:785] No response to seed request.
[09:32:32:788] Unlock was not successful.
- antus
- Site Admin
- Posts: 8996
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Hammer Release 021
Nothing at all coming back from the car. You've got battery power but check ignition and data wiring.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: PCM Hammer Release 021
Using bench harness. Thought so and plugged into hpt and was able to read. E40 ecu
Re: PCM Hammer Release 021
E40 isn't supported by PCM Hammer.
LS1 Boost OS Version 5 Available Here. For feature suggestions post in here Development Thread.
- Kdog
- Posts: 32
- Joined: Mon Mar 10, 2025 3:48 am
- cars: 1991 k2500 454 4speed
2002 40th anniversary Pontiac grand Prix gtp - Location: Cheyenne Wyoming
- Contact:
Re: PCM Hammer Release 021
well being my logs almost the exact same ill do this aswell. sure your familliar with my post. well maybe not, on 3800 pro junk forum evertyone seems numb (no offense) and another site
-"The only rock a man needs, is his Chevrolet"
Kenneth "-Kdog-" Pauli 2023-
Kenneth "-Kdog-" Pauli 2023-
-
- Posts: 2
- Joined: Thu Dec 21, 2023 2:42 am
- cars: 95 Cougar
04 Silverado
19 CT6
Re: PCM Hammer Release 021
Question on PCMHammer - can it repair the scrambled serial number and BCC number on a LS1 PCM? I have a 0411 LS1 PCM that has the infamous all zeros serial number and the BCC, and it looks like the seed/key is scrambled too as it's $FFFF. It would be nice if this could be fixed by means other than replacing the chip.
- antus
- Site Admin
- Posts: 8996
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: PCM Hammer Release 021
yes it can. do a clone write of a bin with complete information in it. The serial number is in the parameter block. You can write just this segment, but in practice you'll probably be wanted to change your OS to a well supported one and its good to make sure that block is in sync with the operating system hence a full write to begin with.
If you cant unlock because the seed and key are corrupted (also in that segment) you can do a full write in recovery mode by takeing the back of the pcm and momentarily grounding a pin, which crashes the computer to reset it, and causes a memory read to fail which triggers boot recovery mode. The moment the short is clear (as you just ground the pin for a brief moment) normal operation is restored so pcmhammer can complete the write cycle. The seed and key pair in the bin will be restored to the computer so that it will unlock normally next time.
See the thread here for recovery pin locations: viewtopic.php?t=8923
If you cant unlock because the seed and key are corrupted (also in that segment) you can do a full write in recovery mode by takeing the back of the pcm and momentarily grounding a pin, which crashes the computer to reset it, and causes a memory read to fail which triggers boot recovery mode. The moment the short is clear (as you just ground the pin for a brief moment) normal operation is restored so pcmhammer can complete the write cycle. The seed and key pair in the bin will be restored to the computer so that it will unlock normally next time.
See the thread here for recovery pin locations: viewtopic.php?t=8923
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
- Posts: 2
- Joined: Thu Dec 21, 2023 2:42 am
- cars: 95 Cougar
04 Silverado
19 CT6
Re: PCM Hammer Release 021
Thanks, I'll have to look around and see if I can find a proper intact BIN. I'm not so worried about getting a 'better OS', this is more or less a bench unit, but I'd like to get it back to normal status with the S/N being the proper one and the BCC matching that on the tag, etc. At least there's more than one way to do it.
Re: PCM Hammer Release 021
Hello everyone and congratulations for the forum. I searched for introductions/presentations section but I could not find it, so I apologize if I am making a mistake according to the forum rules.
My name is Davide and i'm writing from Italy, the work you have done to allow the reading/writing of the GM group control units is it fantastic! I found your forum because my friend bought a 2006 Hummer 3.5L with VATS problems and I would like to try to read the PCM to understand if it is possible to deactivate it in some way. To do this obviously I downloaded pcmhummer 21.2 and I tried to read the ecu but I received error related to the HW ID because the control unit was not recognized as P12 (log1 in attachment)
So I tried to modified the code (I hope I did it right, I'm a beginner) and added the ECU reference first in P12 1mb (log 2) and then in P12 2mb (log 3) but in both cases I can't read the ecu, can someone help me understand if and what I'm doing wrong? why can't I read the ecu?
In attachment logs and ecu pic.
Thanks a lot.
My name is Davide and i'm writing from Italy, the work you have done to allow the reading/writing of the GM group control units is it fantastic! I found your forum because my friend bought a 2006 Hummer 3.5L with VATS problems and I would like to try to read the PCM to understand if it is possible to deactivate it in some way. To do this obviously I downloaded pcmhummer 21.2 and I tried to read the ecu but I received error related to the HW ID because the control unit was not recognized as P12 (log1 in attachment)
So I tried to modified the code (I hope I did it right, I'm a beginner) and added the ECU reference first in P12 1mb (log 2) and then in P12 2mb (log 3) but in both cases I can't read the ecu, can someone help me understand if and what I'm doing wrong? why can't I read the ecu?
In attachment logs and ecu pic.
Thanks a lot.