Duramax With Edge Insight

[WisconsinHick1]

Alright I have two ecm's that are acting as if they are locked. 01 Truck with 03 OS and 03 VIN. Both flashed fine before hooking up Edge Insight then go to reflash and this is what I'm getting. I have tried all the different "Use Alt Keys" and "Lock Maybe Faulty" with no luck. Any help would be great!

Executing: C:\Program Files (x86)\EFILive\V8\Config\E54_F.obj
Virtual Machine Started
Script Loaded
Script Verified
Checking Data File...
Unlocking: Trying MFG Key...
Unlocking: Trying EFILocker...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying AUTO Key 1...
Unlocking: Trying AUTO Key 2...
Unlocking: Trying FS Key 1...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying FS Key 2...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying MFG Key...
Unlocking: Trying ALT Key 1...
Unlocking: Trying ALT Key 2...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying ALT Key 3...
Executing: Boot Loader...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying MFG Key...
Unlocking: Trying EFILocker...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying AUTO Key 1...
Unlocking: Trying AUTO Key 2...
Unlocking: Trying FS Key 1...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying FS Key 2...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying MFG Key...
Unlocking: Trying ALT Key 1...
Unlocking: Trying ALT Key 2...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Wait...
Unlocking: Trying ALT Key 3...
Please: Wait...
Script exited with code $0534: Invalid Serial Number.

[GMPX]

Did you try unplugging the Edge to see if the problem goes away?

[WisconsinHick1]

That was both in the truck with the Edge unhooked and on my stand alone flash unit. Does the Edge place any info in the ECM? Do I have to some how release the Edge from the ECM?

[Mitco39]

Try using V7.5, if I get weird errors like that I always try V7.5 as a last resort and it usually seems to do the trick.

[WisconsinHick1]

Alright Mitch I'll give that a shot tonight when I get home and report back.

[Mitco39]

Also if that doesnt work and you havent already tried it, just disconnect the batteries for a bit. Usually the V8 software will let an invalid serial go through as its common that they get all messed up from time to time. Either way it should go eventually.

[WisconsinHick1]

The one thing I have found interesting is now that I have updated my Insight it asks me to verify my VIN.

[Mitco39]

It did that on the wifes truck to. When I checked it with EFILive the vin was some jumbled up crap. Its common for the VIN and serial to get all messed up during a flash. The truck seems to run and flash just fine otherwise tho, I did have to turn off the VATS but since then its been good.

[WisconsinHick1]

Ok good I'm not the only one. To turn off the VATS do I just 0 everything out? I have thought about doing that but I was worried it might mess something else up.

[Mitco39]

Just change the enable to disable and your good to go.

[WisconsinHick1]

Well I got one ecm to take with 7.5.

But I think the second one is shot.

17:34:12.843: Scanning for EFILive FlashScan V2 HAPI
17:34:12.859: Autodetect interface ...
17:34:13.074: Interface firmware version: 2.7.64
17:34:13.074: Connection to [FSV2] interface is OK
17:34:13.089: CAN-VPW Bridge Activated
17:34:13.138: Current protocol set to: "SAE J1850 VPW"
17:34:13.138: Autodetect PCM...
17:34:13.185: Connection to PCM is OK
17:34:13.201: Current protocol: "SAE J1850 VPW"
17:34:13.404: USB driver version: 2.8.40
17:34:13.404: USB library version: 3.2.7
17:34:13.419: Interface firmware model: FSV2
17:34:13.419: Interface firmware version: 2.7.64
17:34:13.436: Interface firmware date: Jul 19, 2014
17:34:13.444: FlashScan serial number: 003603096380
17:34:13.444: FlashScan license number: 003487846557
17:34:13.706: Getting status...
17:34:13.753: Status: OK.
17:34:22.538: Disconnecting ...
17:34:22.915: CAN-VPW Bridge Deactivated
17:34:22.931: Disconnected
17:34:23.612: Scanning for EFILive FlashScan V2 HAPI
17:34:23.628: Autodetect interface ...
17:34:23.833: Interface firmware version: 2.7.64
17:34:23.848: Connection to [FSV2] interface is OK
17:34:24.056: USB driver version: 2.8.40
17:34:24.056: USB library version: 3.2.7
17:34:24.056: Interface firmware model: FSV2
17:34:24.071: Interface firmware version: 2.7.64
17:34:24.071: Interface firmware date: Jul 19, 2014
17:34:24.087: FlashScan serial number: 003603096380
17:34:24.102: FlashScan license number: 003487846557
17:34:24.118: Disconnecting ...
17:34:24.489: CAN-VPW Bridge Deactivated
17:34:24.505: Disconnected
17:34:25.181: Scanning for EFILive FlashScan V2 HAPI
17:34:25.197: Autodetect interface ...
17:34:25.410: Interface firmware version: 2.7.64
17:34:25.410: Connection to [FSV2] interface is OK
17:34:25.426: CAN-VPW Bridge Activated
17:34:25.473: Current protocol set to: "SAE J1850 VPW"
17:34:25.473: Autodetect PCM...
17:34:25.520: Connection to PCM is OK
17:34:25.535: Current protocol: "SAE J1850 VPW"
17:34:25.742: USB driver version: 2.8.40
17:34:25.742: USB library version: 3.2.7
17:34:25.742: Interface firmware model: FSV2
17:34:25.758: Interface firmware version: 2.7.64
17:34:25.758: Interface firmware date: Jul 19, 2014
17:34:25.773: FlashScan serial number: 003603096380
17:34:25.773: FlashScan license number: 003487846557
17:34:26.058: Getting status...
17:34:26.090: Status: OK.
17:34:26.943: Bootloader version: DLB7_v1.5F (08AA-B073)
17:34:26.943: Preparing ECM for reflash...
17:34:26.974: ECM seed is: $DE57
17:34:26.974: Unlock attempt 1 of 4
17:34:27.370: Unlock attempt 2 of 4
17:34:27.749: Not ready, waiting 1 second for retry...
17:34:29.009: Not ready, waiting 1 second for retry...
17:34:30.267: Not ready, waiting 1 second for retry...
17:34:31.526: Not ready, waiting 1 second for retry...
17:34:32.778: Not ready, waiting 1 second for retry...
17:34:34.035: Not ready, waiting 1 second for retry...
17:34:35.293: Not ready, waiting 1 second for retry...
17:34:36.562: Not ready, waiting 1 second for retry...
17:34:37.813: Not ready, waiting 1 second for retry...
17:34:39.068: Unlock attempt 3 of 4
17:34:39.451: Unlock attempt 4 of 4
17:34:39.829: Not ready, waiting 1 second for retry...
17:34:41.093: Not ready, waiting 1 second for retry...
17:34:42.355: Not ready, waiting 1 second for retry...
17:34:43.625: Not ready, waiting 1 second for retry...
17:34:44.884: Not ready, waiting 1 second for retry...
17:34:46.131: Not ready, waiting 1 second for retry...
17:34:47.387: Not ready, waiting 1 second for retry...
17:34:48.637: Not ready, waiting 1 second for retry...
17:34:49.886: Not ready, waiting 1 second for retry...
17:34:51.140: Initializing ECM...
17:34:51.904: Initializing ECM, step 1 of 4
17:34:51.904: Initializing ECM, step 2 of 4
17:34:52.673: Initializing ECM, step 3 of 4
17:34:54.146: Initializing ECM, step 4 of 4
17:34:54.429: ECM lock has been re-armed, attempting to unlock ECM again...

17:34:54.448: ECM seed is: $DE57
17:34:54.448: Unlock attempt 1 of 4
17:34:54.827: Unlock attempt 2 of 4
17:34:55.198: Not ready, waiting 1 second for retry...
17:34:56.451: Not ready, waiting 1 second for retry...
17:34:57.701: Not ready, waiting 1 second for retry...
17:34:58.943: Not ready, waiting 1 second for retry...
17:35:00.206: Not ready, waiting 1 second for retry...
17:35:01.456: Not ready, waiting 1 second for retry...
17:35:02.700: Not ready, waiting 1 second for retry...
17:35:03.949: Not ready, waiting 1 second for retry...
17:35:05.202: Not ready, waiting 1 second for retry...
17:35:06.464: Unlock attempt 3 of 4
17:35:06.823: Unlock attempt 4 of 4
17:35:07.193: Not ready, waiting 1 second for retry...
17:35:08.438: Not ready, waiting 1 second for retry...
17:35:09.690: Not ready, waiting 1 second for retry...
17:35:10.927: Not ready, waiting 1 second for retry...
17:35:12.165: Not ready, waiting 1 second for retry...
17:35:13.423: Not ready, waiting 1 second for retry...
17:35:14.670: Not ready, waiting 1 second for retry...
17:35:15.918: Not ready, waiting 1 second for retry...
17:35:17.175: Not ready, waiting 1 second for retry...
17:35:18.425: Initializing ECM...
17:35:19.165: Initializing ECM, step 1 of 4
17:35:19.165: Initializing ECM, step 2 of 4
17:35:19.912: Initializing ECM, step 3 of 4
17:35:21.392: Initializing ECM, step 4 of 4
17:35:21.677: ECM lock has been re-armed, attempting to unlock ECM again...

17:35:21.834: Initializing bootloader...
17:35:21.902: Error: Failed. Controller has returned to normal operation, please retry the operation.
17:35:22.139: Initializing bootloader, step 1 of 5
17:35:22.139: Error
17:36:16.337: ECM is in an unknown state.
17:36:18.491: Clear emisison related DTCs...
17:36:18.507: Clear DTCs for all modules...
17:36:19.343: Disconnecting ...
17:36:19.720: CAN-VPW Bridge Deactivated
17:36:19.720: Disconnected
17:36:19.736: Data transfer was interrupted.
17:36:26.637: Done!

[Mitco39]

Its not shot, if your communicating with it there is still life there. Do you have a remote start or security system at all in the truck? When installers install it they tap into the purple wire at the back of the OBD plug. On the 01-05 trucks this has to be either cut or removed during the flash process as 9 times out of 10 it will kick EFI Live out.

[WisconsinHick1]

That was the message when I was flashing on my bench top stand alone harness. I will try it on the truck tonight and no it is a bare bones work truck with no remote start or security system. But I will check the OBD wires on the truck to make sure no one tapped into it.

[Mitco39]

Have you tried the repair flash that comes up after it thinks the computer is in a unknown state? Its been awhile but I believe its a Red Cross button that shows up?

[WisconsinHick1]

That I have not. I will give that a go.

[WisconsinHick1]

Still no luck. But I still have communication with the ECM. :wallbash: