PDA

View Full Version : Won't flash



mijdirtyjeep
September 30th, 2010, 12:20 PM
I am having a problem since last Saturday trying to get a new DSP2 tune loaded on my truck.

It started out when I was working on it, and I had the batteries disconnected. I hooked them back up, and the truck would not start "just cranked". I found it had a Vats code, and after trying to flash it "unsuccessfully" it finally started.:confused: It runs and switches between the 2 tunes just fine, but when I try and reflash it just says "reflash unsuccessful, try again".

PS: also when I hook the Scan tool up to my truck, it comes up with some crazy vin number, and wants me to enter a vin. I enter my vin, and none of the Pids are valid:help2:

mijdirtyjeep
October 29th, 2010, 12:16 PM
Bump, still can not get EFI to flash a new tune "it has been 4 weeks", and the one on it just plain sucks!

PS: I copied the info it gave while trying to flash, hope it might help

20:58:30.171: Scanning for EFILive FlashScan V2 USB
20:58:30.187: Autodetect interface ...
20:58:32.015: Interface not detected
20:58:32.703: Scanning for EFILive FlashScan V2 HAPI
20:58:32.718: Autodetect interface ...
20:58:32.890: Interface firmware version: 2.6.6
20:58:32.906: Connection to [FSV2] interface is OK
20:58:32.921: CAN-VPW Bridge Activated
20:58:32.937: Current protocol set to: "SAE J1850 VPW"
20:58:32.937: Autodetect PCM...
20:58:33.000: Connection to PCM is OK
20:58:33.000: Autodetect TCM...
20:58:33.046: Connection to TCM is OK
20:58:33.062: Current protocol: "SAE J1850 VPW"
20:58:33.109: Interface firmware model: FSV2
20:58:33.125: Interface firmware version: 2.6.6
20:58:33.140: Interface firmware date: Dec 14, 2008
20:58:33.156: FlashScan serial number:
20:58:33.171: FlashScan license number:
20:58:33.296: Getting status...
20:58:33.343: Status: OK.
20:58:40.078: Disconnecting ...
20:58:40.453: CAN-VPW Bridge Deactivated
20:58:40.453: Disconnected
20:58:41.125: Scanning for EFILive FlashScan V2 USB
20:58:41.140: Autodetect interface ...
20:58:42.968: Interface not detected
20:58:43.656: Scanning for EFILive FlashScan V2 HAPI
20:58:43.671: Autodetect interface ...
20:58:43.859: Interface firmware version: 2.6.6
20:58:43.859: Connection to [FSV2] interface is OK
20:58:43.890: Interface firmware model: FSV2
20:58:43.906: Interface firmware version: 2.6.6
20:58:43.921: Interface firmware date: Dec 14, 2008
20:58:43.953: FlashScan serial number:
20:58:43.968: FlashScan license number:
20:58:44.000: Disconnecting ...
20:58:44.359: CAN-VPW Bridge Deactivated
20:58:44.375: Disconnected
20:58:45.031: Scanning for EFILive FlashScan V2 USB
20:58:45.046: Autodetect interface ...
20:58:46.875: Interface not detected
20:58:47.562: Scanning for EFILive FlashScan V2 HAPI
20:58:47.578: Autodetect interface ...
20:58:47.765: Interface firmware version: 2.6.6
20:58:47.765: Connection to [FSV2] interface is OK
20:58:47.781: CAN-VPW Bridge Activated
20:58:47.812: Current protocol set to: "SAE J1850 VPW"
20:58:47.812: Autodetect PCM...
20:58:47.859: Connection to PCM is OK
20:58:47.859: Autodetect TCM...
20:58:47.906: Connection to TCM is OK
20:58:47.921: Current protocol: "SAE J1850 VPW"
20:58:47.968: Interface firmware model: FSV2
20:58:47.984: Interface firmware version: 2.6.6
20:58:48.000: Interface firmware date: Dec 14, 2008
20:58:48.015: FlashScan serial number:
20:58:48.031: FlashScan license number:
20:58:48.140: Getting status...
20:58:48.187: Status: OK.
20:58:49.140: Bootloader version: DLB7_v1.4F (08A6-B0BB)
20:58:49.140: Preparing ECM for reflash...
20:58:49.171: ECM seed is: $7EDD
20:58:49.171: Unlock attempt 1 of 4
20:58:49.578: Unlock attempt 2 of 4
20:58:49.984: Not ready, waiting 1 second for retry...
20:58:51.250: Not ready, waiting 1 second for retry...
20:58:52.500: Not ready, waiting 1 second for retry...
20:58:53.750: Not ready, waiting 1 second for retry...
20:58:55.031: Not ready, waiting 1 second for retry...
20:58:56.296: Not ready, waiting 1 second for retry...
20:58:57.546: Not ready, waiting 1 second for retry...
20:58:58.781: Not ready, waiting 1 second for retry...
20:59:00.031: Not ready, waiting 1 second for retry...
20:59:01.281: Unlock attempt 3 of 4
20:59:01.671: Unlock attempt 4 of 4
20:59:02.093: Not ready, waiting 1 second for retry...
20:59:03.375: Not ready, waiting 1 second for retry...
20:59:04.640: Not ready, waiting 1 second for retry...
20:59:05.890: Not ready, waiting 1 second for retry...
20:59:07.140: Not ready, waiting 1 second for retry...
20:59:08.390: Not ready, waiting 1 second for retry...
20:59:09.656: Not ready, waiting 1 second for retry...
20:59:10.906: Not ready, waiting 1 second for retry...
20:59:12.156: Not ready, waiting 1 second for retry...
20:59:13.406: Initializing ECM...
20:59:14.250: Initializing ECM, step 1 of 4
20:59:14.250: Initializing ECM, step 2 of 4
20:59:15.093: Initializing ECM, step 3 of 4
20:59:15.093: Initializing ECM, step 4 of 4
20:59:15.390: ECM lock has been re-armed, attempting to unlock ECM again...

20:59:15.421: ECM seed is: $7EDD
20:59:15.437: Unlock attempt 1 of 4
20:59:15.875: Unlock attempt 2 of 4
20:59:16.265: Not ready, waiting 1 second for retry...
20:59:17.578: Not ready, waiting 1 second for retry...
20:59:18.843: Not ready, waiting 1 second for retry...
20:59:20.093: Not ready, waiting 1 second for retry...
20:59:21.343: Not ready, waiting 1 second for retry...
20:59:22.593: Not ready, waiting 1 second for retry...
20:59:23.843: Not ready, waiting 1 second for retry...
20:59:25.093: Not ready, waiting 1 second for retry...
20:59:26.359: Not ready, waiting 1 second for retry...
20:59:27.625: Unlock attempt 3 of 4
20:59:28.046: Unlock attempt 4 of 4
20:59:28.468: Not ready, waiting 1 second for retry...
20:59:29.734: Not ready, waiting 1 second for retry...
20:59:31.000: Not ready, waiting 1 second for retry...
20:59:32.234: Not ready, waiting 1 second for retry...
20:59:33.500: Not ready, waiting 1 second for retry...
20:59:34.750: Not ready, waiting 1 second for retry...
20:59:36.000: Not ready, waiting 1 second for retry...
20:59:37.250: Not ready, waiting 1 second for retry...
20:59:38.531: Not ready, waiting 1 second for retry...
20:59:39.812: Initializing ECM...
20:59:40.687: Initializing ECM, step 1 of 4
20:59:40.687: Initializing ECM, step 2 of 4
20:59:41.546: Initializing ECM, step 3 of 4
20:59:41.546: Initializing ECM, step 4 of 4
20:59:41.828: ECM lock has been re-armed, attempting to unlock ECM again...

20:59:41.984: Initializing bootloader...
20:59:42.187: Error: Failed. Controller has returned to normal operation, please retry the operation.
20:59:42.437: Initializing bootloader, step 1 of 5
20:59:42.437: Error
20:59:48.015: ECM is in an unknown state.
20:59:50.140: Clear emisison related DTCs...
20:59:50.187: Clear DTCs for all modules...
20:59:50.500: Disconnecting ...
20:59:50.875: CAN-VPW Bridge Deactivated
20:59:50.875: Disconnected
20:59:50.875: Data transfer was interrupted.
20:59:52.718: Done!

joecar
October 29th, 2010, 01:36 PM
Hi Jim,

I'm sorry I somehow missed your post above 4 weeks ago.

I pm'd Tech Support.


In the meantime...

Which build version of V7/V8 software do you have installed...?

I see your V2 has firmware 2.06.06... you're going to have to update your V7 and V8 software and update the V2 bootblock/firmware.

See builds 133 and 115 here: Download Software (http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133)

After updating V7 and V8 you will have to update your V2 bootblock and firmware.

mijdirtyjeep
October 29th, 2010, 01:55 PM
It was build 7.5.6 "build 117". I just up dated to build V7 "113", and V8and am in the process of heading back out to try again!
I also just updated the bootblock and filmware!

mijdirtyjeep
October 29th, 2010, 02:37 PM
OK this is the info I get now that I am all up to date!

22:38:01.046: Scanning for EFILive FlashScan V2 USB
22:38:01.046: Autodetect interface ...
22:38:02.843: Interface not detected
22:38:03.484: Scanning for EFILive FlashScan V2 HAPI
22:38:03.500: Autodetect interface ...
22:38:03.562: Interface firmware version: 2.6.41
22:38:03.562: Connection to [FSV2] interface is OK
22:38:03.593: Interface firmware model: FSV2
22:38:03.625: Interface firmware version: 2.6.41
22:38:03.640: Interface firmware date: Sep 12, 2010
22:38:03.656: FlashScan serial number: 003736168831
22:38:03.671: FlashScan license number: 003736168831
22:38:03.703: Disconnecting ...
22:38:04.125: CAN-VPW Bridge Deactivated
22:38:04.125: Disconnected
22:38:04.734: Scanning for EFILive FlashScan V2 USB
22:38:04.750: Autodetect interface ...
22:38:06.546: Interface not detected
22:38:07.187: Scanning for EFILive FlashScan V2 HAPI
22:38:07.203: Autodetect interface ...
22:38:07.265: Interface firmware version: 2.6.41
22:38:07.265: Connection to [FSV2] interface is OK
22:38:07.281: CAN-VPW Bridge Activated
22:38:07.359: Current protocol set to: "SAE J1850 VPW"
22:38:07.359: Autodetect PCM...
22:38:07.406: Connection to PCM is OK
22:38:07.406: Autodetect TCM...
22:38:07.453: Connection to TCM is OK
22:38:07.468: Current protocol: "SAE J1850 VPW"
22:38:07.500: Interface firmware model: FSV2
22:38:07.531: Interface firmware version: 2.6.41
22:38:07.546: Interface firmware date: Sep 12, 2010
22:38:07.562: FlashScan serial number: 003736168831
22:38:07.578: FlashScan license number: 003736168831
22:38:07.687: Getting status...
22:38:07.734: Status: OK.
22:38:08.671: Bootloader version: DLB7_v1.4F (08A6-B0BB)
22:38:08.671: Preparing ECM for reflash...
22:38:08.718: ECM seed is: $7EDD
22:38:08.718: Unlock attempt 1 of 4
22:38:09.125: Unlock attempt 2 of 4
22:38:09.531: Not ready, waiting 1 second for retry...
22:38:10.812: Not ready, waiting 1 second for retry...
22:38:12.078: Not ready, waiting 1 second for retry...
22:38:13.343: Not ready, waiting 1 second for retry...
22:38:14.609: Not ready, waiting 1 second for retry...
22:38:15.875: Not ready, waiting 1 second for retry...
22:38:17.140: Not ready, waiting 1 second for retry...
22:38:18.406: Not ready, waiting 1 second for retry...
22:38:19.687: Not ready, waiting 1 second for retry...
22:38:20.953: Unlock attempt 3 of 4
22:38:21.359: Unlock attempt 4 of 4
22:38:21.765: Not ready, waiting 1 second for retry...
22:38:23.031: Not ready, waiting 1 second for retry...
22:38:24.296: Not ready, waiting 1 second for retry...
22:38:25.562: Not ready, waiting 1 second for retry...
22:38:26.828: Not ready, waiting 1 second for retry...
22:38:28.093: Not ready, waiting 1 second for retry...
22:38:29.359: Not ready, waiting 1 second for retry...
22:38:30.625: Not ready, waiting 1 second for retry...
22:38:31.890: Not ready, waiting 1 second for retry...
22:38:33.171: Initializing ECM...
22:38:34.015: Initializing ECM, step 1 of 4
22:38:34.015: Initializing ECM, step 2 of 4
22:38:34.875: Initializing ECM, step 3 of 4
22:38:34.875: Initializing ECM, step 4 of 4
22:38:35.171: ECM lock has been re-armed, attempting to unlock ECM again...

22:38:35.218: ECM seed is: $7EDD
22:38:35.218: Unlock attempt 1 of 4
22:38:35.609: Unlock attempt 2 of 4
22:38:36.031: Not ready, waiting 1 second for retry...
22:38:37.296: Not ready, waiting 1 second for retry...
22:38:38.562: Not ready, waiting 1 second for retry...
22:38:39.828: Not ready, waiting 1 second for retry...
22:38:41.093: Not ready, waiting 1 second for retry...
22:38:42.359: Not ready, waiting 1 second for retry...
22:38:43.640: Not ready, waiting 1 second for retry...
22:38:44.921: Not ready, waiting 1 second for retry...
22:38:46.187: Not ready, waiting 1 second for retry...
22:38:47.453: Unlock attempt 3 of 4
22:38:47.859: Unlock attempt 4 of 4
22:38:48.265: Not ready, waiting 1 second for retry...
22:38:49.546: Not ready, waiting 1 second for retry...
22:38:50.812: Not ready, waiting 1 second for retry...
22:38:52.078: Not ready, waiting 1 second for retry...
22:38:53.343: Not ready, waiting 1 second for retry...
22:38:54.625: Not ready, waiting 1 second for retry...
22:38:55.890: Not ready, waiting 1 second for retry...
22:38:57.156: Not ready, waiting 1 second for retry...
22:38:58.421: Not ready, waiting 1 second for retry...
22:38:59.687: Initializing ECM...
22:39:00.531: Initializing ECM, step 1 of 4
22:39:00.531: Initializing ECM, step 2 of 4
22:39:01.390: Initializing ECM, step 3 of 4
22:39:01.390: Initializing ECM, step 4 of 4
22:39:01.687: ECM lock has been re-armed, attempting to unlock ECM again...

22:39:01.843: Initializing bootloader...
22:39:02.031: Error: Failed. Controller has returned to normal operation, please retry the operation.
22:39:02.265: Initializing bootloader, step 1 of 5
22:39:02.265: Error
22:39:05.953: ECM is in an unknown state.
22:39:08.078: Clear emisison related DTCs...
22:39:08.125: Clear DTCs for all modules...
22:39:08.468: Disconnecting ...
22:39:09.250: CAN-VPW Bridge Deactivated
22:39:09.250: Disconnected
22:39:09.250: Data transfer was interrupted.
22:39:10.046: Done!

Tordne
October 29th, 2010, 03:41 PM
Have you got any aftermarket items (iPod chargers, stereo, remote start etc. that might be interfering on the bus)? Have you disconnected the Info and Radio fuses? Have you tried in low speed mode?

mijdirtyjeep
October 29th, 2010, 11:34 PM
No aftermarket items on the truck!

I have never been able to flash in High Speed mode, I always had to uncheck that and check Try Alt Keys?

I have never pulled any fuses before to flash, but will give that a try and report back on the results!

The funny thing is that when I try and run the ScanToolB] it asked me for the VIN everytime I open it "never did that before". I put in my VIN number, then it validates PIDS "I check the ones I want". Then when I hit the Green button to connect, it changes the VIN at the bottom of the page to this [B]ÌýKŸw&]õ_¢&xxxxxx "the X's are boxes and symbols that I am unsure of how to make on my computer". After it changes the VIN from the one I put in to messed up VIN all the PIDS on the selection page are not supported?

mijdirtyjeep
October 30th, 2010, 03:32 AM
Alright, here is what I have tried this morning.

Unhooked both batteries "for and hour"
Unhooked TCM "for an hour"
Unhooked ECM "for an hour"
I then undid the bail connectors "main harness and found 2 of the pins "on the lower one" were pushed back, I got them secured back in and rehooked everything back up.
I then pulled the Info/Radio/Factory amp fuses, and tried to flash "same as before".
I then tried the Scan tool, and got the same crazy VIN as before.
Next I used the FlashScan to check the VIN/OP system and found the TCM will show the correct VIN, but the ECM shows the crazy Vin that the scan tool show's!

My question now is there a way to reflash the correct Vin onto the ECM with EFI? Also how would the ECM loose the vin, but still work just fine?

joecar
October 30th, 2010, 07:23 AM
No aftermarket items on the truck!

I have never been able to flash in High Speed mode, I always had to uncheck that and check Try Alt Keys?

I have never pulled any fuses before to flash, but will give that a try and report back on the results!

The funny thing is that when I try and run the ScanToolB] it asked me for the VIN everytime I open it "never did that before". I put in my VIN number, then it validates PIDS "I check the ones I want". Then when I hit the Green button to connect, it changes the VIN at the bottom of the page to this [B]ÌýKŸw&]õ_¢&xxxxxx "the X's are boxes and symbols that I am unsure of how to make on my computer". After it changes the VIN from the one I put in to messed up VIN all the PIDS on the selection page are not supported?You need to update the V2 firmware (may require updating V2 bootblock first), you need to update the V7/V8 software first.

Install V7 and V8; then start EFILive Explorer and goto the Firmware tab.

Do not proceed until you've updated V7/V8 and bootblock/firmware.

joecar
October 30th, 2010, 07:27 AM
After you update, use the scantool Bidirectional->Change VIN to enter your correct VIN (writes VIN to ECM).

Then before logging, also do File->Enter VIN (for pid selection filtering).

mijdirtyjeep
October 30th, 2010, 08:04 AM
OK, sorry forgot to mention I did update everything including bootblock.

Also I can not change the VIN in the Bidirectional as the VIN that comes up when I connect is "ÌýKŸw&]õx¢&IHG@" "copied if finally" and not alphanumeric!

I am at a loss, and have been told I need a new ECM, which just plain sucks seeing I think I need a CP3 pump as well "I think, can not log it to be sure".

Tordne
October 30th, 2010, 03:50 PM
The LB7 ECM has been known to go bad, for seemly no reason. I wonder if that may just have happened to yours.

Forgot to ask also, do you have good battery voltage when you're flashing? Perhaps have a charger connected at the time so you can sustain a 12V supply?

Incidentally, are you able to read the ECM out?

mijdirtyjeep
October 31st, 2010, 12:48 PM
I am starting to think it is junk!

It has over 12v and I did try to flash with my charger on just to eliminate that variable.

Oh and it will not read the ECM either. I have talked with IdahoRob about just replacing this one with a good one.