pcmhacking.net

Antus, I do not currently have another compatible device, only the J2534 device I mentioned.

Hi Bill. Did you try again using PCM Hammer r20 after the failures you are having with r21? It would confirm what you are saying in regard to r21.

darkman5001, Antus confirmed it is a known issue in his initial response to my post.

Bill

[08:37:45:913] Unlock succeeded.

No point in forcing recovery mode, recovery mode will be of no help!

As Antus stated, it is NOT a PcmHammer issue!

No disrespect @BillNobody, it is in fact the current OS on the PCM or the PCM itself that is the issue ...
The following,

[08:37:51:493] RX: 6C F0 10 7F 34 00 10 00 FF 80 33

comes from the OS on the PCM!

FULL Write a valid file of a stock virgin Os for the hardware and it'll either work or fail, if it fails, toss the PCM and get another, the flash chip is most likely failing ...

Seems to me it's more likely his drewtech somehow causing the issue if he can't read any pcms now. I haven't tried v21 yet with my nano but I'm sure others have. Anyone else have a drewtech?

Just to be clear here, I am not bashing the 'Hammer. Maybe it is a glitch in the OS, although HPT reads just fine using what I am sure closely resembles GM's flash routines so, in essence it IS an issue that PCM Hammer does not mitigate. It's nothing personal, just the facts.

Gampy, Yes, I can just update the entire binary to a newer version, but that disrupts the current "tuned" binary residing in the PCM at the moment. I would like to preserve it for "transfer" to a newer OS but it looks like I will have to do it the laborious way using cut and paste with HPT and TunerPro.

Cincinnatus, I own a Dearborn Group Technologies device, NOT Drew Technologies/OPUS. I owned a Drew device, bought from an authorized dealer. The unit failed 6 months in and Drew would not warranty it because the dealer had bought it roughly a year and a half before I purchased it according to the serial number, which left the 12 month warranty expired. So, in short F&%#! Drew Technologies.

Bill

Sorry Bill, I misunderstood when I saw dgtech. Are you saying drewtech wouldn't warranty something their distributor (dealer) sold you even though you had only owned it for 6 months? What a sh!tty way to treat a customer. I have hptuned pcms I can try to read with v21 and report back.

Cincinnatus, I bought a device, sealed in the original Drew Tech cardboard box, and since it sat on their distributors shelf for a year and a half, they basically gave me the middle finger. So I returned the favor and patronized their competition.

BillNobody wrote:Cincinnatus, I bought a device, sealed in the original Drew Tech cardboard box, and since it sat on their distributors shelf for a year and a half, they basically gave me the middle finger. So I returned the favor and patronized their competition.

Just for the sake of debugging. You can get this program

viewtopic.php?f=42&t=7753

And run the test script to test pcm functionality.

Save result to a txt file and post. For instructions how to run scripts check the thread.

I think a test with pcmhammer v20 will be interesting. I'd expect the same result. I think recovery mode will be different, from memory the OS does not have a chance to reject the kernel or at least doesnt follow the same logic as the main OS. When this happened to NSFW's corvette PCM in the very early days of pcmhammer he was able to do a recovery boot and flash of his initial bin to fix it. In fact doing so was the very first full flash with pcmhammer ever done. But if the pcm is rejecting the request for a good reason, some other problem on the bus, there might still be lots of retries if you work around it this way.