PCMHammer P04
Re: PCMHammer P04
Do you know if they are original or have they been cloned ??
Use PCMHammer Release 21.x to verify the Chip ID vs. pulling the hood.
However, Antus is correct, so ...
-Enjoy
Use PCMHammer Release 21.x to verify the Chip ID vs. pulling the hood.
However, Antus is correct, so ...
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
-
- Posts: 252
- Joined: Sat Dec 18, 2021 8:15 am
- cars: 2005 Yukon, 2004 Suburban, 2001 Tahoe, 2002 Envoy, 2006 Envoy, 2003 Lincoln LS
- Location: New Jersey, USA
Re: PCMHammer P04
My apologies. I was wrong about the flash chip being misrepresented. I have so many PCMs it's crazy, and not GM controllers. Wouldn't be the first time I confused Intel and AMD.antus wrote:Thanks for the results. I'll look in more detail shortly. A quick answer:
"The P59 Intel was misrepresented as an AMD."
This isn't possible. The chip id comes from the chip itself, there is no lookup against OSID or anything we could have gotten wrong. If the system was broken it'd be an invalid ID and say unknown and abort. You might want to pop the lid and check you havn't got your PCMs mixed up.
I am not sure what to expect from the test write. Are you able to read a bin, change the vin, key off, power off (to persist the vin change to flash), then do a write paramater block to write the original paramater block only back from your first bin? The change of vin will mean a change in that block is found and it will erase and write it. But being a param block its a bit safter than writing more than that. I suspect it'll work fine. If it erases but doesnt write security key will be FFFF and you can use a custom key with a normal copy of pcmhammer to write the original param block back.

-
- Posts: 252
- Joined: Sat Dec 18, 2021 8:15 am
- cars: 2005 Yukon, 2004 Suburban, 2001 Tahoe, 2002 Envoy, 2006 Envoy, 2003 Lincoln LS
- Location: New Jersey, USA
Re: PCMHammer P04
I know for a fact they are original and not cloned. I was wrong though. All were AMDs that identified as AMD.Gampy wrote:Do you know if they are original or have they been cloned ??
Use PCMHammer Release 21.x to verify the Chip ID vs. pulling the hood.
However, Antus is correct, so ...
-Enjoy
- antus
- Site Admin
- Posts: 9008
- 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: PCMHammer P04
well this is the p04 thread but since we are testing here, reporting P01, P59, P12 are all working with the test build for me.
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: PCMHammer P04
Awesome ...
Get any retries or ??
-Enjoy
Get any retries or ??
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
- antus
- Site Admin
- Posts: 9008
- 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: PCMHammer P04
no retries. tested on avt and mdi (j2534)
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: PCMHammer P04
Awesome, thank you.
-Enjoy
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
- antus
- Site Admin
- Posts: 9008
- 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: PCMHammer P04
I got my first successful erase and write out of the P08. Now to bring our work together, and see what is outstanding. Probably OSIDs at a minimum.
[10:18:10:249] WARNING: This version uses the new Assembly Kernels, USE AT YOUR OWN RISK!
[10:18:16:882] C:\Users\a\Documents\p08-20230702-antuswazhere.bin
[10:18:16:897] Validating 512k file.
[10:18:16:911] Start End Stored Needed Verdict Segment Name
[10:18:16:924] 00000 7FFFB CD48 CD48 Good Whole File
[10:18:16:936] Requesting operating system ID...
[10:18:17:033] PCM and file are both for the same Hardware P08
[10:18:17:045] PCM and file are both operating system 12206029
[10:18:17:054] WARNING: P08 Support is still in development.
[10:18:18:168] Unlock succeeded.
[10:18:18:245] Attempting switch to VPW 4x
[10:18:18:280] Module 0x10 (engine controller) has agreed to enter high-speed mode.
[10:18:21:646] Kernel upload 21% complete.
[10:18:21:836] Kernel upload 47% complete.
[10:18:22:019] Kernel upload 73% complete.
[10:18:22:210] Kernel upload 100% complete.
[10:18:23:341] Kernel Version: 82400208
[10:18:23:361] Kernel uploaded to PCM succesfully.
[10:18:23:448] PCM and image file are both operating system 12206029
[10:18:23:525] Flash chip: Intel 28F400B, 512kb
[10:18:23:535] Calculating CRCs from file.
[10:18:23:564] Requesting CRCs from PCM.
[10:18:23:573] Range File CRC PCM CRC Verdict Purpose
[10:18:23:583] 060000-07FFFF not needed not needed n/a OperatingSystem
[10:18:23:592] 040000-05FFFF not needed not needed n/a OperatingSystem
[10:18:23:602] 020000-03FFFF not needed not needed n/a OperatingSystem
[10:18:23:611] 008000-01FFFF not needed not needed n/a Calibration
[10:18:23:930] 006000-007FFF 1BA3E32E 1BA3E32E Same Parameter
[10:18:24:257] 004000-005FFF D70D1B8C 85B5BB36 Different Parameter
[10:18:24:280] 000000-003FFF not needed not needed n/a Boot
[10:18:24:292] Processing range 004000-005FFF
[10:18:24:301] Erasing.
[10:18:25:375] Writing...
[10:18:33:087] Calculating CRCs from file.
[10:18:33:100] Requesting CRCs from PCM.
[10:18:33:108] Range File CRC PCM CRC Verdict Purpose
[10:18:33:118] 060000-07FFFF not needed not needed n/a OperatingSystem
[10:18:33:128] 040000-05FFFF not needed not needed n/a OperatingSystem
[10:18:33:139] 020000-03FFFF not needed not needed n/a OperatingSystem
[10:18:33:149] 008000-01FFFF not needed not needed n/a Calibration
[10:18:33:473] 006000-007FFF 1BA3E32E 1BA3E32E Same Parameter
[10:18:33:805] 004000-005FFF D70D1B8C D70D1B8C Same Parameter
[10:18:33:828] 000000-003FFF not needed not needed n/a Boot
[10:18:33:900] All relevant ranges are identical.
[10:18:33:918] All write-request messages succeeded on the first try. You have an excellent connection to the PCM.
[10:18:33:929] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[10:18:33:941] Flash successful!
[10:18:34:017] Clearing trouble codes.
[10:18:35:156] Elapsed time 00:00:16.9782604
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: PCMHammer P04
It's about time ... 
Good job!
-Enjoy

Good job!
-Enjoy
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
- antus
- Site Admin
- Posts: 9008
- 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: PCMHammer P04
Ive merged your branch, and tidied up and reapplied mine to that. There is a new pull request at: https://github.com/LegacyNsfw/PcmHacks/pull/327
We need to re-test P01, P59, P10, P12, P12b on that branch. If everything is still healthy we'll also need to add a P08 OSID database.
Gampy, if you can rebase any further P04 work to this branch that'd be awesome.
We need to re-test P01, P59, P10, P12, P12b on that branch. If everything is still healthy we'll also need to add a P08 OSID database.
Gampy, if you can rebase any further P04 work to this branch that'd be awesome.
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