More and more problems with V2

When I bought my V2 about 2 years ago it was rock solid but everytime I do an update it gets worse and worse. Thought the purpose of doing updates was to improve it. I have problems reading LMM now i'm having problems with flashing/reading LB7 that I never had before. I used to just hook it up and go now it keeps giving me bootloader errorrs and what not. The only way I can flash and read it is unclick high speed and click on try alt keys. Whats the deal? I'm afraid to do anymore updates now as everytime I do one it gets worse and more errors pop up.

Each time you update the V2 firmware do you also do BBx Program All...?

Quote:

---

Originally Posted by pavetim

When I bought my V2 about 2 years ago it was rock solid but everytime I do an update it gets worse and worse. Thought the purpose of doing updates was to improve it. I have problems reading LMM now i'm having problems with flashing/reading LB7 that I never had before. I used to just hook it up and go now it keeps giving me bootloader errorrs and what not. The only way I can flash and read it is unclick high speed and click on try alt keys. Whats the deal? I'm afraid to do anymore updates now as everytime I do one it gets worse and more errors pop up.

---

You're right, recently there have been problems that have crept into the V2 firmware. I've spent the past month tracking them down and fixing them. An internal update is being tested right now that addresses the read/flash problems on VPW based controllers. That should fix any problems that you have with the LB7.

As for the LMM failures can you please send me any trace files of any failed LMM reads/flashes as per the last part of this page:
http://support.efilive.com/kb_articl...8254-QOGC-9586

Send to [email protected]

Regards
Paul

The problem with reading a dsp out of LMM is a known problem though isnt' it? How do I do a trace file? So what build should I update too? Right now I have builds 180 and 170

Quote:

---

Originally Posted by pavetim

The problem with reading a dsp out of LMM is a known problem though isnt' it? How do I do a trace file? So what build should I update too? Right now I have builds 180 and 170

---

Oh I see, the reading of a DSP5 tune is not so much a problem as a purposely added security measure.
Regards
Paul

Mine is all jacked since trying to update firmware. I think I'm cursed with efilive. I was one of the first to lose a lbz ECM due to flashing. I can't get my flash scan to be recognized by my computer. When I check the firmware it says it is good. Restarted the computer tried all kinds of things went to documents and tried to load the other firmware and it is not working. It is stuck in dead-poll mode can't get it out.

Quote:

---

Originally Posted by derrickmanx1

Mine is all jacked since trying to update firmware. I think I'm cursed with efilive. I was one of the first to lose a lbz ECM due to flashing. I can't get my flash scan to be recognized by my computer. When I check the firmware it says it is good. Restarted the computer tried all kinds of things went to documents and tried to load the other firmware and it is not working. It is stuck in dead-poll mode can't get it out.

---

After installing the latest software you can find recovery instructions that may help you get your FlashScan operational again here:
\Program files (x86)\EFILive\Drivers\V8\Firmware\EFILiveRecovery
Look in that folder and open the file called ReadMe.txt, try following the instructions in that file.

Regards
Paul

Quote:

---

Originally Posted by Blacky

After installing the latest software you can find recovery instructions that may help you get your FlashScan operational again here:
\Program files (x86)\EFILive\Drivers\V8\Firmware\EFILiveRecovery
Look in that folder and open the file called ReadMe.txt, try following the instructions in that file.

Regards
Paul

---

I wish it worked. I get a error$008E attempt to overwrite firmware with an older version.

I expect that your device has 2.05.08 bootblock and somehow has 2.07.x firmware? If so I believe you will have to send the device into a service agent to be recovered. I tried via remote access for one customer recently and was fla out not able to recover the device ion the field (and I'm pretty good at it ;)).

Please go across to our helpdesk (http://suppot.efilive.com/) and log an RMA case and I can advise where to contact.

Nope showing boot block 2.07.04
And firmware 2.07.29
Just not acting right though. When I plug it in it powers up with no display and all led's come on. Then it goes to flashing the orange led's alternatively.

Thats dead poll mode which means its still alive! Open V8 S&T, then open the EFILive Control Panel. Click F6 Firmware, then click Program firmware (again). Sounds like the firmware checksum isnt correct so the V2 is defaulting to dead poll aka recovery mode.

Please let me know if Erik's suggestion above (which is what I'd also recommend) doesn't work.

Done that like 10 times to see if I could get something to work but no luck.

Try reprogramming the bootblock first, then doing the firmware after the V2 reboots following the bootblock upgrade. You might need to use EFILive Explorer to flash the bootblock again, not sure the EFILive Control Panel will let you do it again. Open EFILive Explorer, click the F12 Firmware tab, click Browse. Open the Boot Block folder, click FSBootV2_07_04.efw and press Open. Click the checkbox that says Bootblock, then click Program. Wait for your V2 to reboot. You can also program the firmware from EFILive Explorer, follow the above steps but dont go into the Boot Block folder and make sure the Bootblock checkbox is NOT checked.

Hope that helps, let us know how it goes.

Quote:

---

Originally Posted by ScarabEpic22

Try reprogramming the bootblock first

---

Unfortunately, unless the firmware is running the boot block can't be programmed. The boot block can't program itself and the firmware can't program itself. So the boot block must be running (i.e. in deadpoll with the two orange LED's flashing) in order for the firmware to be programmed. The firmware must be running (i.e. showing the normal menu options on the LCD) in order for the boot block to be programmed.

What happens when the firmware is programmed is the version number of the most recently programmed firmware is stored into the boot block's non-volatile memory. That way the boot block "knows" what the last version of firmware in the device was - even if the firmware gets erased. The boot block won't allow a version of firmware that is older then the number stored in the boot block.

This is just a guess at what might have happened...

If during the boot block upgrade, that non-volatile memory area did not get updated correctly it could hold a value like: $FFFFFFFF which is what erased flash memory is set to. That would make the version number V255.255.255 (build 255) i.e. the highest version number possible. That makes it impossible to flash any firmware into the device. The only way to fix that is to have the device reset by EFILive.

Regards
Paul

Ah I see Paul, dang it was hoping that could be a quick and easy way to recover it. Now that you mention it, that makes sense to me with regards to fw versioning.

derrickmanx1

Give me a call and I'll remotely log into your PC and see if we can fix this. I had one like this last week I was able to recover.

Guy

SoCal Diesel

Hey Guy,

If you can let me know how mate cause I had one (perhaps slightly different symptom) and I just could not get it recovered.

Hi Andrew,

I'll see if the same fix will work on this one and then I'll send you a summary.

Guy

To All,
The unit was stuck in Dead Poll mode when I logged in. I used EFILive Explorer to reprogram the latest boot block, which is exactly what the unit said it already had, then reprogrammed the latest firmware, again the same version the unit displayed when we started. Success! The unit is now completely functional.

Guy

Thanks Guy. My issue is resolved.

Quote:

---

Originally Posted by Blacky

After installing the latest software you can find recovery instructions that may help you get your FlashScan operational again here:
\Program files (x86)\EFILive\Drivers\V8\Firmware\EFILiveRecovery
Look in that folder and open the file called ReadMe.txt, try following the instructions in that file.

Regards
Paul

---

Paul -- Followed the readme file to a point to fix my screwed up V2 and managed to get it all fixed up with the latest boot block and firmware. Did run into a few glitches following the readme process -- After successfully performing Steps 2 & 3, Step 4 wouldn't work as it didn't like flashing an older boot block version. Deviating at that point from the readme, I fired up V8 Scan & Tune, clicked the "Check Firmware" button and used it to successfully update the boot block and firmware.

Have I told you lately how much you rock? :thumb_yello:

SinisterSS, thanks for the feedback :cheers:

Guy, I will call you Monday and hopefully, we can do the same with my V2...it is also "stuck". I purchased it from you in Dec. 2006. Firmware 2.04.47 Boot 2.04.10
Thank, you Jim

the screen on my V2 Flashscan is broke so now i cant use it how or who do i talk to about getting it fixed

Ho across to our help desk (http://support.efilive.com/) and log an RMA type incident, entering the serial number etc. Please not also if you are in the USA or elsewhere and we can advise the appropriate location to send the device.

When I plug in its power does not show all of the LED to. Then it will flash alternately orange LED.

Sounds like dead poll mode. Launch EFILive explorer and go to the firmware tab and see what firmware and boot block is displayed.

I had the same trouble and i was able to fix it.