View Full Version : Installed COS3 now locked
yzriders182
March 18th, 2013, 01:38 PM
I installed COS3 in my 03 Silverado everything loaded fine and did the key off cycle. I then went to upload my tune to COS3 and it says that then pcm had a unrecognizable file in it. Now I cant get it to do anything it just keeps saying that.
Any help? Thanks
yzriders182
March 18th, 2013, 02:15 PM
14738
14739
this is what it is saying
joecar
March 19th, 2013, 04:16 AM
Can you post the text from the console.
When you finished flashing the first time, did you turn off ignition/power for at least 15 seconds...?
Did this happen while doing a full flash or a cal-only flash...?
What version of V7 software...?
What version of V2 firmware...?
yzriders182
March 19th, 2013, 05:17 AM
I can post up the text from the console latter when I'm back on my computer.
Yes I did turn the key off for at least 15 seconds. I was doing a full flash of the COS3.
I cant remember the version of the software but I checked for updates and it says its up to date.
How do I tell what version of V2 im using?
Thanks for the help!!
GMPX
March 19th, 2013, 09:53 AM
The COS update is done in a few stages, when you flash the COS base file in, you then need to cal flash your original tune over that, then read it back out to get the full COS update file. Is that what you had done?
yzriders182
March 19th, 2013, 10:03 AM
The COS update is done in a few stages, when you flash the COS base file in, you then need to cal flash your original tune over that, then read it back out to get the full COS update file. Is that what you had done?
Yes that is what I am trying. I have both read and watched the tutorials.
I just tried a full reflash of COS3 and it worked! I then was able to upload my original tune and it worked fine as well. I then went to read the pcm and it now says the pcm is locked....
It says to try using the ALT Keys so I checked the ALT Key box and tried. No luck. I tried unpluging the scanner and restarting everything still no luck. I tried reinstalling the stock tune and no luck there so I tried reloading COS3 and still no luck.
This is what i got without the ALT Keys
16:48:28.576: Scanning for EFILive FlashScan V2 HAPI
16:48:28.591: Autodetect interface ...
16:48:28.763: Interface firmware version: 2.7.35
16:48:28.763: Connection to [FSV2] interface is OK
16:48:28.779: USB driver version: 4.0.0
16:48:28.779: USB library version: 3.1.18
16:48:28.794: Interface firmware model: FSV2
16:48:28.810: Interface firmware model: FSV2
16:48:28.810: Interface firmware version: 2.7.35
16:48:28.825: Interface firmware date: Jun 22, 2012
16:48:28.841: FlashScan serial number: 003931250449
16:48:28.857: FlashScan license number: 003931250449
16:48:28.872: Disconnecting ...
16:48:29.075: CAN-VPW Bridge Deactivated
16:48:29.075: Disconnected
16:48:29.715: Scanning for EFILive FlashScan V2 HAPI
16:48:29.730: Autodetect interface ...
16:48:29.964: Interface firmware version: 2.7.35
16:48:29.964: Connection to [FSV2] interface is OK
16:48:29.980: CAN-VPW Bridge Activated
16:48:30.058: Current protocol set to: "SAE J1850 VPW"
16:48:30.058: Autodetect PCM...
16:48:30.089: Connection to PCM is OK
16:48:30.105: Current protocol: "SAE J1850 VPW"
16:48:30.323: USB driver version: 4.0.0
16:48:30.323: USB library version: 3.1.18
16:48:30.339: Interface firmware model: FSV2
16:48:30.354: Interface firmware model: FSV2
16:48:30.370: Interface firmware version: 2.7.35
16:48:30.385: Interface firmware date: Jun 22, 2012
16:48:30.401: FlashScan serial number: 003931250449
16:48:30.417: FlashScan license number: 003931250449
16:48:30.697: Getting status...
16:48:30.744: Status: OK.
16:48:31.477: Bootloader version: LS1B_v1.7R (04DA-6638)
16:48:31.477: Preparing PCM for reading flash...
16:48:31.509: PCM seed is: $605A
16:48:31.509: Unlock attempt 1 of 1
16:48:31.867: Disconnecting ...
16:48:32.257: CAN-VPW Bridge Deactivated
16:48:32.257: Disconnected
16:48:38.143: Done!
16:49:07.814: Scanning for EFILive FlashScan V2 HAPI
16:49:07.829: Autodetect interface ...
16:49:08.063: Interface firmware version: 2.7.35
16:49:08.079: Connection to [FSV2] interface is OK
16:49:08.282: USB driver version: 4.0.0
16:49:08.297: USB library version: 3.1.18
16:49:08.313: Interface firmware model: FSV2
16:49:08.329: Interface firmware model: FSV2
16:49:08.344: Interface firmware version: 2.7.35
16:49:08.360: Interface firmware date: Jun 22, 2012
16:49:08.375: FlashScan serial number: 003931250449
16:49:08.375: FlashScan license number: 003931250449
16:49:08.407: Disconnecting ...
16:49:08.812: CAN-VPW Bridge Deactivated
16:49:08.812: Disconnected
16:49:09.467: Scanning for EFILive FlashScan V2 HAPI
16:49:09.483: Autodetect interface ...
16:49:09.717: Interface firmware version: 2.7.35
16:49:09.717: Connection to [FSV2] interface is OK
16:49:09.733: CAN-VPW Bridge Activated
16:49:09.795: Current protocol set to: "SAE J1850 VPW"
16:49:09.811: Autodetect PCM...
16:49:09.842: Connection to PCM is OK
16:49:09.857: Current protocol: "SAE J1850 VPW"
16:49:10.060: USB driver version: 4.0.0
16:49:10.076: USB library version: 3.1.18
16:49:10.091: Interface firmware model: FSV2
16:49:10.091: Interface firmware model: FSV2
16:49:10.107: Interface firmware version: 2.7.35
16:49:10.123: Interface firmware date: Jun 22, 2012
16:49:10.138: FlashScan serial number: 003931250449
16:49:10.154: FlashScan license number: 003931250449
16:49:10.450: Getting status...
16:49:10.482: Status: OK.
16:49:11.215: Bootloader version: LS1B_v1.7R (04DA-6638)
16:49:11.215: Preparing PCM for reading flash...
16:49:11.246: PCM seed is: $605A
16:49:11.246: Unlock attempt 1 of 1
16:49:11.605: Disconnecting ...
16:49:11.995: CAN-VPW Bridge Deactivated
16:49:11.995: Disconnected
16:49:15.291: Done!
With ALT Keys
16:46:06.108: Scanning for EFILive FlashScan V2 HAPI
16:46:06.124: Autodetect interface ...
16:46:06.358: Interface firmware version: 2.7.35
16:46:06.358: Connection to [FSV2] interface is OK
16:46:06.576: USB driver version: 4.0.0
16:46:06.576: USB library version: 3.1.18
16:46:06.592: Interface firmware model: FSV2
16:46:06.592: Interface firmware model: FSV2
16:46:06.608: Interface firmware version: 2.7.35
16:46:06.623: Interface firmware date: Jun 22, 2012
16:46:06.639: FlashScan serial number: 003931250449
16:46:06.654: FlashScan license number: 003931250449
16:46:06.670: Disconnecting ...
16:46:07.060: CAN-VPW Bridge Deactivated
16:46:07.076: Disconnected
16:46:07.715: Scanning for EFILive FlashScan V2 HAPI
16:46:07.731: Autodetect interface ...
16:46:07.965: Interface firmware version: 2.7.35
16:46:07.965: Connection to [FSV2] interface is OK
16:46:07.980: CAN-VPW Bridge Activated
16:46:08.058: Current protocol set to: "SAE J1850 VPW"
16:46:08.058: Autodetect PCM...
16:46:08.105: Connection to PCM is OK
16:46:08.121: Current protocol: "SAE J1850 VPW"
16:46:08.324: USB driver version: 4.0.0
16:46:08.339: USB library version: 3.1.18
16:46:08.355: Interface firmware model: FSV2
16:46:08.355: Interface firmware model: FSV2
16:46:08.370: Interface firmware version: 2.7.35
16:46:08.386: Interface firmware date: Jun 22, 2012
16:46:08.402: FlashScan serial number: 003931250449
16:46:08.417: FlashScan license number: 003931250449
16:46:08.714: Getting status...
16:46:08.745: Status: OK.
16:46:09.478: Bootloader version: LS1B_v1.7R (04DA-6638)
16:46:09.478: Preparing PCM for reading flash...
16:46:09.509: PCM seed is: $605A
16:46:09.509: Unlock attempt 1 of 4
16:46:09.899: Unlock attempt 2 of 4
16:46:10.274: Not ready, waiting 1 second for retry...
16:46:11.522: Not ready, waiting 1 second for retry...
16:46:12.770: Not ready, waiting 1 second for retry...
16:46:14.033: Not ready, waiting 1 second for retry...
16:46:15.281: Not ready, waiting 1 second for retry...
16:46:16.545: Not ready, waiting 1 second for retry...
16:46:17.808: Not ready, waiting 1 second for retry...
16:46:19.056: Not ready, waiting 1 second for retry...
16:46:20.320: Unlock attempt 3 of 4
16:46:20.694: Unlock attempt 4 of 4
16:46:21.084: Not ready, waiting 1 second for retry...
16:46:22.332: Not ready, waiting 1 second for retry...
16:46:23.580: Not ready, waiting 1 second for retry...
16:46:24.860: Not ready, waiting 1 second for retry...
16:46:26.108: Not ready, waiting 1 second for retry...
16:46:27.356: Not ready, waiting 1 second for retry...
16:46:28.604: Not ready, waiting 1 second for retry...
16:46:29.852: Not ready, waiting 1 second for retry...
16:46:31.115: Initializing PCM...
16:46:31.911: Initializing PCM, step 1 of 4
16:46:31.911: Initializing PCM, step 2 of 4
16:46:32.706: Initializing PCM, step 3 of 4
16:46:32.706: Initializing PCM, step 4 of 4
16:46:33.018: PCM lock has been re-armed, attempting to unlock PCM again...
16:46:33.034: PCM seed is: $605A
16:46:33.050: Unlock attempt 1 of 4
16:46:33.424: Unlock attempt 2 of 4
16:46:33.798: Not ready, waiting 1 second for retry...
16:46:35.046: Not ready, waiting 1 second for retry...
16:46:36.310: Not ready, waiting 1 second for retry...
16:46:37.558: Not ready, waiting 1 second for retry...
16:46:38.822: Not ready, waiting 1 second for retry...
16:46:40.085: Not ready, waiting 1 second for retry...
16:46:41.333: Not ready, waiting 1 second for retry...
16:46:42.597: Not ready, waiting 1 second for retry...
16:46:43.860: Unlock attempt 3 of 4
16:46:44.235: Unlock attempt 4 of 4
16:46:44.625: Not ready, waiting 1 second for retry...
16:46:45.873: Not ready, waiting 1 second for retry...
16:46:47.136: Not ready, waiting 1 second for retry...
16:46:48.384: Not ready, waiting 1 second for retry...
16:46:49.632: Not ready, waiting 1 second for retry...
16:46:50.880: Not ready, waiting 1 second for retry...
16:46:52.144: Not ready, waiting 1 second for retry...
16:46:53.392: Not ready, waiting 1 second for retry...
16:46:54.656: Initializing PCM...
16:46:55.467: Initializing PCM, step 1 of 4
16:46:55.467: Initializing PCM, step 2 of 4
16:46:56.262: Initializing PCM, step 3 of 4
16:46:56.262: Initializing PCM, step 4 of 4
16:46:56.559: PCM lock has been re-armed, attempting to unlock PCM again...
16:46:56.715: Initializing bootloader...
16:46:56.933: Error: Failed. Controller has returned to normal operation, please retry the operation.
16:46:57.167: Initializing bootloader, step 1 of 3
16:46:57.167: Error
16:46:57.167: Disconnecting ...
16:46:57.557: CAN-VPW Bridge Deactivated
16:46:57.573: Disconnected
16:47:03.922: Done!
yzriders182
March 19th, 2013, 10:06 AM
and this is what I got when trying to reflash the stock tune with COS3 installed
16:43:27.469: Scanning for EFILive FlashScan V2 HAPI
16:43:27.485: Autodetect interface ...
16:43:27.719: Interface firmware version: 2.7.35
16:43:27.719: Connection to [FSV2] interface is OK
16:43:27.734: CAN-VPW Bridge Activated
16:43:27.797: Current protocol set to: "SAE J1850 VPW"
16:43:27.797: Autodetect PCM...
16:43:27.828: Connection to PCM is OK
16:43:27.843: Current protocol: "SAE J1850 VPW"
16:43:28.062: USB driver version: 4.0.0
16:43:28.062: USB library version: 3.1.18
16:43:28.077: Interface firmware model: FSV2
16:43:28.077: Interface firmware model: FSV2
16:43:28.093: Interface firmware version: 2.7.35
16:43:28.109: Interface firmware date: Jun 22, 2012
16:43:28.124: FlashScan serial number: 003931250449
16:43:28.140: FlashScan license number: 003931250449
16:43:28.421: Getting status...
16:43:28.452: Status: OK.
16:43:35.035: Disconnecting ...
16:43:35.441: CAN-VPW Bridge Deactivated
16:43:35.441: Disconnected
16:43:36.096: Scanning for EFILive FlashScan V2 HAPI
16:43:36.111: Autodetect interface ...
16:43:36.345: Interface firmware version: 2.7.35
16:43:36.361: Connection to [FSV2] interface is OK
16:43:36.564: USB driver version: 4.0.0
16:43:36.579: USB library version: 3.1.18
16:43:36.595: Interface firmware model: FSV2
16:43:36.595: Interface firmware model: FSV2
16:43:36.611: Interface firmware version: 2.7.35
16:43:36.626: Interface firmware date: Jun 22, 2012
16:43:36.642: FlashScan serial number: 003931250449
16:43:36.657: FlashScan license number: 003931250449
16:43:36.673: Disconnecting ...
16:43:37.079: CAN-VPW Bridge Deactivated
16:43:37.079: Disconnected
16:43:37.734: Scanning for EFILive FlashScan V2 HAPI
16:43:37.749: Autodetect interface ...
16:43:37.983: Interface firmware version: 2.7.35
16:43:37.983: Connection to [FSV2] interface is OK
16:43:37.999: CAN-VPW Bridge Activated
16:43:38.061: Current protocol set to: "SAE J1850 VPW"
16:43:38.077: Autodetect PCM...
16:43:38.108: Connection to PCM is OK
16:43:38.124: Current protocol: "SAE J1850 VPW"
16:43:38.342: USB driver version: 4.0.0
16:43:38.342: USB library version: 3.1.18
16:43:38.358: Interface firmware model: FSV2
16:43:38.373: Interface firmware model: FSV2
16:43:38.389: Interface firmware version: 2.7.35
16:43:38.405: Interface firmware date: Jun 22, 2012
16:43:38.420: FlashScan serial number: 003931250449
16:43:38.436: FlashScan license number: 003931250449
16:43:38.717: Getting status...
16:43:38.748: Status: OK.
16:43:39.497: Bootloader version: LS1B_v1.7C (08DC-9623)
16:43:39.497: Preparing PCM for reflash...
16:43:39.528: PCM seed is: $605A
16:43:39.528: Unlock attempt 1 of 1
16:43:43.839: PCM is in an unknown state.
16:43:45.977: Clear emisison related DTCs...
16:43:45.992: Clear DTCs for all modules...
16:43:46.803: Disconnecting ...
16:43:47.193: CAN-VPW Bridge Deactivated
16:43:47.193: Disconnected
16:43:47.193: Data transfer was interrupted.
16:44:00.959: Done!
16:44:33.048: Scanning for EFILive FlashScan V2 HAPI
16:44:33.063: Autodetect interface ...
16:44:33.297: Interface firmware version: 2.7.35
16:44:33.313: Connection to [FSV2] interface is OK
16:44:33.516: USB driver version: 4.0.0
16:44:33.531: USB library version: 3.1.18
16:44:33.547: Interface firmware model: FSV2
16:44:33.547: Interface firmware model: FSV2
16:44:33.563: Interface firmware version: 2.7.35
16:44:33.578: Interface firmware date: Jun 22, 2012
16:44:33.594: FlashScan serial number: 003931250449
16:44:33.609: FlashScan license number: 003931250449
16:44:33.641: Disconnecting ...
16:44:34.031: CAN-VPW Bridge Deactivated
16:44:34.031: Disconnected
16:44:34.686: Scanning for EFILive FlashScan V2 HAPI
16:44:34.701: Autodetect interface ...
16:44:34.935: Interface firmware version: 2.7.35
16:44:34.935: Connection to [FSV2] interface is OK
16:44:34.951: CAN-VPW Bridge Activated
16:44:35.013: Current protocol set to: "SAE J1850 VPW"
16:44:35.029: Autodetect PCM...
16:44:35.060: Connection to PCM is OK
16:44:35.076: Current protocol: "SAE J1850 VPW"
16:44:35.294: USB driver version: 4.0.0
16:44:35.294: USB library version: 3.1.18
16:44:35.310: Interface firmware model: FSV2
16:44:35.325: Interface firmware model: FSV2
16:44:35.341: Interface firmware version: 2.7.35
16:44:35.357: Interface firmware date: Jun 22, 2012
16:44:35.372: FlashScan serial number: 003931250449
16:44:35.388: FlashScan license number: 003931250449
16:44:35.669: Getting status...
16:44:35.715: Status: OK.
16:44:36.464: Bootloader version: LS1B_v1.7C (08DC-9623)
16:44:36.464: Preparing PCM for reflash...
16:44:36.495: PCM seed is: $605A
16:44:36.495: Unlock attempt 1 of 1
16:44:40.745: PCM is in an unknown state.
16:44:42.882: Clear emisison related DTCs...
16:44:42.913: Clear DTCs for all modules...
16:44:43.724: Disconnecting ...
16:44:44.114: CAN-VPW Bridge Deactivated
16:44:44.114: Disconnected
16:44:44.114: Data transfer was interrupted.
16:44:47.937: Done!
yzriders182
March 19th, 2013, 10:16 AM
Firmware is 2.07.35
Bootlock is 2.07.04
Blacky
March 19th, 2013, 01:00 PM
Try installing RC1 from here: http://forum.efilive.com/showthread.php?21842-EFILive-RC-1-%28March-01-2013%29
Update your FlashScan firmware manually using the EFILive V8 Explorer program.
Then try reading the controller using the EFILive V8 Scan and Tune software.
Regards
Paul
yzriders182
March 20th, 2013, 12:23 PM
Ok I tried installing RC1 and updated my FlashScan firmware. I then tried reading the pcm with V8 and it says the PCM is locked and cant read.
I tried using V7.5 to read the pcm and it says the same thing...
Anything else I can try or that I might be doing wrong? Thanks for the help.
Blacky
March 20th, 2013, 12:28 PM
When using V8 (to read the controller) did you try checking the check-box: "Try Alt Keys" and "Assume Lock May Be Faulty"?
With those check boxes checked, V8 will try additional keys that may unlock the controller.
If you can read the controller using those settings, then once it has finished reading locate the (*.htx) trace file of the read process in the folder:
\My Documents\EFILive\V8\Trace and send the file to me. From that file I can probably figure out the key that you can use to unlock the controller.
If you still can't read the controller using those settings you will need to send the controller to someone who can unlock it.
EFILive can do that but it requires you to send your controller to our Melbourne Australia office.
Regards
Paul
joecar
March 20th, 2013, 12:31 PM
Ok I tried installing RC1 and updated my FlashScan firmware. I then tried reading the pcm with V8 and it says the PCM is locked and cant read.
I tried using V7.5 to read the pcm and it says the same thing...
Anything else I can try or that I might be doing wrong? Thanks for the help.Did you :
- flash the latest dated 2.07.35 firmware into your V2...?
- do BBx Program All...?
yzriders182
March 20th, 2013, 12:36 PM
flashed the latest dated 2.07.35 witch is dated 2/27/13
What do you mean by BBx Program All?
yzriders182
March 20th, 2013, 12:37 PM
I did not check the try alt keys box, but did check the assume lock may be faulty. Ill try checking both now.
Blacky
March 20th, 2013, 12:42 PM
flashed the latest dated 2.07.35 witch is dated 2/27/13
What do you mean by BBx Program All?
If/when you are attempting to flash using FlashScan in standalone mode (i.e. not via a laptop) then each time you update the software on your PC, you need to:
1. Update the firmware in your FlashScan device.
2. Update the configuration files on your FlashScan device using the [Program All] drop-down option on the [Program] button in the V8 software on the [F5: BBX] window.
If you are trying to reflash using V8 in pass-thru mode from your PC/laptop then you only need to update the firmware in your FlashScan.
Regards
Paul
yzriders182
March 20th, 2013, 12:52 PM
Ok I'm trying to read it using my laptop. Using v8 with alt keys and assumed lock boxes checked it says its locked with a custom code.
How would something like this happen?
Again thanks for the help guys!
Blacky
March 20th, 2013, 01:08 PM
When a full flash is performed on that controller, the memory area that contains the seed/key data is erased and overwritten. If something fails during the erase/write process then the seed/key data may not get restored correctly and/or it may get restored in a corrupt state.
Its almost impossible to know what seed/key values were written back to the controller - unless you have a trace file of that event.
If you have the *.blx trace files from the last successful full-flash that you did, then I can try and figure out the key for the data in the trace file.
The *.blx trace files are created by the V7 software and are stored in the folder: \My Documents\EFILive\V7.5\Bug Reports.
Send the file (or files) to me at
[email protected]
Regards
Paul
yzriders182
March 20th, 2013, 01:20 PM
I just sent it to you. Thanks for the help again
yzriders182
March 24th, 2013, 01:17 AM
Ok I got my PCM unlocked but now whenever I try to upload cos3 it fails. I can do a full flash of my stock tune just fine but not cos3. Any ideas?
Thanks
joecar
March 25th, 2013, 08:02 AM
Can you post the console text.
Blacky
March 25th, 2013, 09:36 AM
Ok I got my PCM unlocked but now whenever I try to upload cos3 it fails. I can do a full flash of my stock tune just fine but not cos3. Any ideas?
Thanks
Got the trace files, I'm still investigating...
Regards
Paul
yzriders182
March 30th, 2013, 10:45 AM
I got it to work thanks for the help Paul
joecar
March 31st, 2013, 08:20 AM
I got it to work thanks for the help PaulWhat did you do...?
Powered by vBulletin® Version 4.2.5 Copyright © 2026 vBulletin Solutions Inc. All rights reserved.