V2 will not stay connected to my computer

[Burnt_Bizcut00]

I have been trying to tune an 05 LLY Duramax but keep running into problems with my flashscan disconnecting. It took forever to pull the stock tune out so I could modify it, when I go to put the new tune in i only get to the "license ecm" phase now before the flashscan will lose communication with my computer. I have narrowed it down to the computer-V2 communication after I had only the v2 connected to my laptop . Sometimes the tune tool software will freeze when I go to open it with the v2 connected. I have done some searching and have tried all the recommendations with no luck still. Here's what I have tried-
1)Tried using a different laptop (mine is a new HP running windows 7) which was running windows 7 as well.
2) Updated to the latest version of EFILive
3) Tried using a different USB cable for the laptop to V2 Connection
4) Tried installing the old version of the USB drivers using the USB manager in V8
5) Cursed at it for 10 min straight :hihi:

I am not sure what else to try. I noticed when I connect my V2 to the computer every time, I get a notice in the bottom right corner of the screen saying that its " installing USB driver." I'm guessing that maybe my computer is installing the latest usb driver automatically when I connect the V2 instead of using the old usb driver like I told it to use. I just used my EFILive to tune an 04 Duramax a month ago and had no problems.

[Tordne]

You could try THIS (http://support.efilive.com/kb_article.php?ref=2864-USDC-6616) process to downgrade to the 2.02.04 drivers. Also, does the USB port connection feel tight, like it's not lose and could be the cause of the disconnections?

[Burnt_Bizcut00]

Thats what I did in step number 4. And the connecion feels tight. I have tried every usb port in my computer. Im stumped.

[Tordne]

For the USB connection I was sort of meaning:
1) Does it feel secure with the connection between the cable and the socket? From your feedback I expect that it does.
2) Does the port feel secure in the device (i.e it isn't lose indicating a poor connection or broken solder joint)?

Do you notice the device disconnecting when you not actually doing anything (not reading/flashing/logging)? I expect you may notice the device just randomly rebooting?

The freezing you describe is absolutely a known issue with the newer version drivers.

[Burnt_Bizcut00]

The cable feels normal at both connections. I notice that the device freezes or disconnects whenever I go to open my tune tool or the efilive explorer. It will also disconnect right before tuning and ecm. I have tried to downgrade the usb drivers multipul times with no luck. It acts the same with the old and new drivers. I am thinking that my computer may be updating the drivers automatically when I connect the device even though I have insalled the old ones.

[Tordne]

Ensuring you have the 2.02.04 drivers installed is essential. Unless that is the case then you may get irregular results. I gather you have followed the USB Manager guide I included in a previous post with FlashScan disconnected?

[Burnt_Bizcut00]

Yep. I followed the instructions exactly to install the USB drivers. I really need to get this solved. I have a VIN license tied up with this, and my friend bought an Edge CTS just so we could tune a DSP5 into it. I really cant just walk away with $500+ already invested.

[joecar]

Which Windows OS do you have installed...?


Is there another laptop/PC you can try...?

[Burnt_Bizcut00]

Which Windows OS do you have installed...?


Is there another laptop/PC you can try...?
Already tried a different PC. I have windows 7 installed. I have tried everything I can think of. I am getting the same symptoms of the new usb driver bug, but when i install the old one it still acts the same.
If I uninstall all of my efilive programs, then reinstall them, will I lose all my saved tunes? I'm thinking that's what I'm going to try next.

[joecar]

Copy the folder My Documents\EFILive (which has subfodlers V7.5 and V8) to same safe place.

[Burnt_Bizcut00]

Ok I uninstalled all the programs from my computer, then reinstalled them and got the same problem. Will someone PLEASE help me get this figured out? Are there any tests I can run to pinpoint the problem? Everytime I try to open the the explorer, I get a little icon in the lower right corner saying the flashscan is not responding.

[joecar]

The problem happens even after this...? :


Ensuring you have the 2.02.04 drivers installed is essential. Unless that is the case then you may get irregular results. I gather you have followed the USB Manager guide I included in a previous post with FlashScan disconnected?

[Tordne]

Ok I uninstalled all the programs from my computer, then reinstalled them and got the same problem. Will someone PLEASE help me get this figured out? Are there any tests I can run to pinpoint the problem? Everytime I try to open the the explorer, I get a little icon in the lower right corner saying the flashscan is not responding.

It's going to be one of few things:
1) You're not running the 2.02.04 drivers (there is a link above relating to USB Manager).

2) You're running very old 2.04.x firmware. The V8 software not responding will do this as bootblock/firmware prior to 2.5 is not supported by V8. Please see these knowledgebase articles for general information about on-going software and firmware updates:
- Software updates (http://support.efilive.com/kb_article.php?ref=5404-IJZV-0820)
- Firmware updates (http://support.efilive.com/kb_article.php?ref=7243-SFGL-2949)

Install the software updates first as the V8 software incorporates the new bootblock and firmware updates for your device.

If you have very old 2.04.x firmware please see the bottom section of the firmware updates article. If you are on this very old release it is imperative that you first upgrade to 2.07.72 prior to upgrading to the later bootblock and firmware versions. This is outlined in the document.

3) Cable or device fault. You indicate you've tried a different cable so that can be ruled out. You could get the device sent in for inspection/repair but that will cost you shipping and possible an inspection fee and repair costs so last resort.

4) You have some very odd system issue that is just going to be too difficult to diagnose.

My money is on 1) or 2) personally.

Cheers,

[Burnt_Bizcut00]

It's going to be one of few things:
1) You're not running the 2.02.04 drivers (there is a link above relating to USB Manager).

2) You're running very old 2.04.x firmware. The V8 software not responding will do this as bootblock/firmware prior to 2.5 is not supported by V8. Please see these knowledgebase articles for general information about on-going software and firmware updates:
- Software updates (http://support.efilive.com/kb_article.php?ref=5404-IJZV-0820)
- Firmware updates (http://support.efilive.com/kb_article.php?ref=7243-SFGL-2949)

Install the software updates first as the V8 software incorporates the new bootblock and firmware updates for your device.

If you have very old 2.04.x firmware please see the bottom section of the firmware updates article. If you are on this very old release it is imperative that you first upgrade to 2.07.72 prior to upgrading to the later bootblock and firmware versions. This is outlined in the document.

3) Cable or device fault. You indicate you've tried a different cable so that can be ruled out. You could get the device sent in for inspection/repair but that will cost you shipping and possible an inspection fee and repair costs so last resort.

4) You have some very odd system issue that is just going to be too difficult to diagnose.

My money is on 1) or 2) personally.

Cheers,

It was number 2 I had- Firmware: 2.04.70 Date- 10 Dec 2007,Boot Block Ver. 2.04.10 Date 10Nov 2006 loaded on my V2. I'm really surprised it took someone this long to suggest that I update my actual V2.
If anyone else is having this problem, and they have already tried the USB driver downgrade, connect your flashscan to your computer hit F4, F3, F1 and see what firmware and boot block you are using. If it is something old like 2.04.xx, follow the pdf help file found @ Start->All Programs->EFIlive->V8->Documents-> Upgrading Flashscan. MAKE SURE you read the whole pdf file first because there's some very specific instructions if you have an older FW and BB.

Now when I open up the Explorer icon it asks me to upgrade my boot block from 2.05.08 to 2.07.04. Should I go ahead and do this? I don't want to mess anything up now that I have it working now.

[Tordne]

The first tip you gave (the message about not responding) was the first indication that this was a possible cause.

If the device has been successfully upgrade to both the 2.05 bootblock and firmware then please do go ahead and upgrade to the 2.07 series. While V8 will now recognize the device the software will not support it at that version.

Glad its sorted :)

Cheers,

[joecar]

It was number 2 I had- Firmware: 2.04.70 Date- 10 Dec 2007,Boot Block Ver. 2.04.10 Date 10Nov 2006 loaded on my V2. I'm really surprised it took someone this long to suggest that I update my actual V2.
It was all in how you worded post #1, it steered us into USB drivers :)




If anyone else is having this problem, and they have already tried the USB driver downgrade, connect your flashscan to your computer hit F4, F3, F1 and see what firmware and boot block you are using. If it is something old like 2.04.xx, follow the pdf help file found @ Start->All Programs->EFIlive->V8->Documents-> Upgrading Flashscan. MAKE SURE you read the whole pdf file first because there's some very specific instructions if you have an older FW and BB.
Very good advice :cheers:



Now when I open up the Explorer icon it asks me to upgrade my boot block from 2.05.08 to 2.07.04. Should I go ahead and do this? I don't want to mess anything up now that I have it working now.No, not quite... follow what the Upgrading Flashscan pdf says

( do not update using V8 S&T or V8 EE until after you've arrived at bootblock 2.07.04 and firmware 2.07.35 )

[joecar]

Related threads:
Upgrading-from-older-bootblock-firmware (http://forum.efilive.com/showthread.php?20952-Upgrading-from-older-bootblock-firmware)
2011-gmc-2500-hd-bootloader-rejected (http://forum.efilive.com/showthread.php?21005-2011-gmc-2500-hd-bootloader-rejected)
Updating-V2-firmware-bootblock (http://forum.efilive.com/showthread.php?20954-Updating-V2-firmware-bootblock)

[Burnt_Bizcut00]

Well I went to tune my buddy's duramax that I had been trying to get done the past few months and ended up ruining the ECM. The Flashscan won't communicate with the ECM and the truck won't start.
I had my tune all loaded up like I normally do, but when I went to tune the truck I got a message saying that the ECM was locked and to make sure that I was using the same flashscan that the truck was locked to, which I am. I was able to license the truck before I had all my previous problems with the Flashscan disconnection, but that's as far as I got.
What is the deal now??? I am guessing that the VIN licenses didn't transfer over, even though the update process was successful. It's like my V2 won't recognize the previous VIN's I've had locked to it.

[Tordne]

The first thing to check is that both your software and firmware are up-to-date. Please see these guides that may assist with software and firmware updates:
- Software updates (http://support.efilive.com/kb_article.php?ref=5404-IJZV-0820)
- Firmware updates (http://support.efilive.com/kb_article.php?ref=7243-SFGL-2949)

Install the software updates first as the V8 software incorporates the new bootblock and firmware updates for your device.

If you have very old 2.04.x firmware please see the bottom section of the firmware updates article. If you are on this very old release it is imperative that you first upgrade to 2.07.72 prior to upgrading to the later bootblock and firmware versions. This is outlined in the document.

[Burnt_Bizcut00]

In my previous post I had mentioned that it was my software and firmware were up to date. I have Software V7.5.7 (build 211) FW 2.07.35 and BB 2.07.04. Shouldn't this work perfectly now? Why do I keep running into problems? I did upgrade from 2.05.08 to 2.07.04 as I mentioned in post #14. In post #15 Tordne said to go ahead and do it, but in post #16 joecar said i shouldn't. Did I mess something up when I did that upgrade?

[joecar]

Did you read the pdf in this thread: Upgrading-from-older-bootblock-firmware (http://forum.efilive.com/showthread.php?20952-Upgrading-from-older-bootblock-firmware)




Related threads:
Upgrading-from-older-bootblock-firmware (http://forum.efilive.com/showthread.php?20952-Upgrading-from-older-bootblock-firmware)
2011-gmc-2500-hd-bootloader-rejected (http://forum.efilive.com/showthread.php?21005-2011-gmc-2500-hd-bootloader-rejected)
Updating-V2-firmware-bootblock (http://forum.efilive.com/showthread.php?20954-Updating-V2-firmware-bootblock)

[Burnt_Bizcut00]

Yes that is the pdf that I used to guide me through the upgrade. I can't believe that this thing is still not working.