Re: PCM Hammer - new ls1 flash tool
Posted: Tue May 28, 2019 12:37 am
I guess I'll try manually inputting the seed key my other PCM uses and see if I can read it then.
Electronic Fuel Injection - Developement & Tuning
https://pcmhacking.net/forums/
I asked them about this and they said unless you select to lock it, they do not change the seed key. I went in with my tech2 and had no troubles connecting with it.Yortt wrote:The later Flashscan software changes/cycles the seed which continues to be identified by Flashscan but is effectively locked to other software due to the seed key mismatch.THEFERMANATOR wrote:Don't think so. I just went back in and read it out using the stock key with no problem. I even went and flashed a different cal file in it making sure there was no locking protection enabled, and it went through without a problem. I have 2 identical PCM's setting on my kitchen table, a 35 amp power supply, bench harness, and tuning equipment. My V2 will read either PCM without problem(only 1 is licensed to my cable), I can connect my TECH 2 to either without issue, and I can even read the properties out of either PCM without issue, but I cannot read the file out of the PCM that is licensed to my V2. When I last flashed it, the seed key showed up as $FFFF if that helps. $2B76 is the seed key showing up for the PCM with a fresh TECH 2 flash in it.DavidBraley wrote:Is it possible EFI Live somehow locked the bin file the last time it was used to make changes to the PCM?
What is the PCM service number and what OS did you flash on it with EFI Live? When the seed shows up as FFFF on a 512K most of the time its due to flashing a 99/00 OS onto a 01/02 pcm or vise versa. The offset changes where data is written and a lot of times a check byte will not line back up correctly and will cause this issue.THEFERMANATOR wrote:Don't think so. I just went back in and read it out using the stock key with no problem. I even went and flashed a different cal file in it making sure there was no locking protection enabled, and it went through without a problem. I have 2 identical PCM's setting on my kitchen table, a 35 amp power supply, bench harness, and tuning equipment. My V2 will read either PCM without problem(only 1 is licensed to my cable), I can connect my TECH 2 to either without issue, and I can even read the properties out of either PCM without issue, but I cannot read the file out of the PCM that is licensed to my V2. When I last flashed it, the seed key showed up as $FFFF if that helps. $2B76 is the seed key showing up for the PCM with a fresh TECH 2 flash in it.DavidBraley wrote:Is it possible EFI Live somehow locked the bin file the last time it was used to make changes to the PCM?
Reading live data with a Tech 2 has nothing to do with the seed/key lock. The only way you would know if the tech 2 could unlock the PCM was to try and flash it with a tech 2. If it was able to unlock the pcm it would then flash what ever file you have loaded onto the PCM. If the tech 2 can't unlock it then it would report a flashing error.THEFERMANATOR wrote: I went in with my tech2 and had no troubles connecting with it.
It is a HP Tuners custom operating system , 1 bar, mafless.Wade wrote:anyone know anything about this bin its 1271001