Updating V2 firmware/bootblock

[-X-]

Hi,

I originally bought EFILive back in 2007 and have FlashScan V2. I hadn't used it in about two years. The computer's hard drive that I had it on froze and so I just now installed 8.2 on a new laptop. Obviously, the boot block and firmware are way out of date.

Long story short, it doesn't seem that my FlashScan V2 will accept a new boot block from 8.2, even though the USB driver installed successfully. This is what appears:

14142

After attempting to update the boot block:

14143

The FlashScan V2 device appears to be fine, says it's connected to PC in USB mode.

[-X-]

Whoops, guess this is in the wrong thread. Mods, feel free to move it to the V8 install thread.

[joecar]

Hi -X-

I moved it to here :)

Please read this first:
Upgrading-from-older-boottblock-firmware (http://forum.efilive.com/showthread.php?20952-Upgrading-from-older-boottblock-firmware)

Then when firmware/bootblock/licenses are all sorted out, please see this:
Setting-up-a-FSV2-from-scratch (http://forum.efilive.com/showthread.php?20699-Setting-up-a-FSV2-from-scratch)

[-X-]

Ok, I have FlashScan V2 updated to the latest bootblock & firmware. Thanks for the upgrade PDF, but it was a bit lacking in details, so I'm including exactly what I did so that others won't have to figure a couple of things out along the way like I had to.

01. Installed 7.5 & 8.2 into the same directory (per upgrade PDF)
02. Started Scan 7.5 & selected 'Connect to vehicle'
03. Selected 'OK' when prompted for controller (default: 'FlashScan/Autocal Only')
04. The following was generated in the console (F6) section:


18:39:43.659: EFILive V7.5 Version V7.5.7 (Build 211)
18:39:53.331: Ready.

23:10:49.402: Scanning for EFILive FlashScan V2 HAPI
23:10:49.447: Autodetect interface ...
23:10:50.932: Interface not detected
23:10:51.580: Scanning for EFILive FlashScan V2 USB
23:10:51.601: Autodetect interface ...
23:10:51.777: Interface firmware version: 2.4.65
23:10:51.791: Connection to [FS2] interface is OK
23:10:51.841: Interface firmware model: FS2
23:10:51.871: Interface firmware model: FS2
23:10:51.899: Interface firmware version: 2.4.65
23:10:51.927: Interface firmware date: Oct 02, 2007
23:10:51.960: FlashScan serial number: <removed>
23:10:51.992: FlashScan license number: <removed>
23:11:29.881: Validating PIDs...
23:11:34.243: Initialising PIDs...
23:11:35.307: Initialising Modules...
23:11:35.336: Ready.

05. Closed EFILive Scan 7.5
06. Opened EFILive Firmware Programmer
07. Selected '...' button in the 'Update FlashScan V2' section
08. Selected 'FSProg_V2_4_72.ffw' (NOT .efw as the upgrade PDF states) & selected the 'Open' button
09. Selected the 'Program' button to update the firmware to 2.04.72 (step A1 from upgrade PDF)
10. Used FlashScan's menu option to upgrade boot block to 2.05.08 (step A2 from upgrade PDF)

Here's where I wound up being stuck for a few minutes, as FlashScan appeared to be in dead-poll mode (two alternating orange LEDs blinking). However, the EFILive Firmware Programmer would not let me update the firmware to 2.05.21, it refused to acknowledge that FlashScan was in dead-poll mode. By the way, I had to rename the 2.05.21 file extension to .ffw for the EFILive Firmware Programmer to allow it to be visible as a selection. Anyway, this was a dead end, so I continued as follows.

11. Opened EFILive Explorer 8.2 in order for the EFILive Control Panel to appear in the taskbar system tray
12. Opened EFILive Control Panel
13. Selected 'F6: Firmware'
14. Boot block was showing as 2.05.08 and warned that the firmware needed to be updated
15. Updated firmware in the CP to 2.05.21 (step A3 from upgrade PDF)
16. Updated boot block in the CP to 2.07.04 (step D1 from upgrade PDF)
17. Updated firmware in the CP to 2.07.35 (step D2 from upgrade PDF)
18. Both the boot block version and firmware version were then listed in the CP as OK.

14149

Done. I verified that the VIN license was still active in FlashScan and I should be good to go now. Thanks for the response and the information, joecar.

On to the next 'from scratch' document.

[joecar]

Ok, good deal, thanks for posting back... :cheers:

[Charles]

16. Updated boot block in the CP to 2.07.04 (step D1 from upgrade PDF)
17. Updated firmware in the CP to 2.07.35 (step D2 from upgrade PDF)
18. Both the boot block version and firmware version were then listed in the CP as OK.

Done.

Does this mean that the most current (as of now Dec 2012) boot block is 2.07.04 (dated Dec 12, 2011) and likewise the current firmware is 2.07.35 (dated Jun 22, 2012)?

Also, it appears as though my software is current (again as of Dec 2012) showing the following: Tune - Version 7.5.7 Build 211, and Scan and Tune - Version 8.2.1 Build 203.

Can someone please verify this to make certain that I'm all up to date and don't need to do any further upgrades at this time.

Thanks!

[joecar]

Yes, correct on both.


After you updated the V2 firmware, did you also program the BBx configuration into the V2 (using the V8 software)...?

see post #1 here: Setting-up-a-FSV2-from-scratch (http://forum.efilive.com/showthread.php?20699-Setting-up-a-FSV2-from-scratch)

[Charles]

Thanks for pointing that out, I just completed it. :cheers:

[wkinslely04]

Need help I updated my bootblock and firmware to the latest versions. I thought everything went smoothly but the v2 never rebooted after updateing the firmware. now when i plug it into the computer the lights flash and then everything goes black. In efilive explorer I'm getting error message 0025 can't get semaphore for control of efilive-hapi. any help will be greatly appreciated

[joecar]

Need help I updated my bootblock and firmware to the latest versions. I thought everything went smoothly but the v2 never rebooted after updateing the firmware. now when i plug it into the computer the lights flash and then everything goes black. In efilive explorer I'm getting error message 0025 can't get semaphore for control of efilive-hapi. any help will be greatly appreciated

What version did you flash into the V2...?

Which LEDs flash, and do they alternate...?

If the two amber LEDs flash in alternation then this means V2 is waiting for you to flash in the firmware.

[vectorbundle]

boot block version OK, firmware update froze in the middle with $0101 error (no data received). now can only connect in dead poll mode. firmware update always freezes 1/5 of the way through if i try to update in dead poll mode. screenshoot attached. what do i do fix this? windows 7 x64.

15489

[joecar]

Can you try a different USB port on your PC...


I notified Tech Support.

[vectorbundle]

i tried, no avail. thanks.

[Blacky]

boot block version OK, firmware update froze in the middle with $0101 error (no data received). now can only connect in dead poll mode. firmware update always freezes 1/5 of the way through if i try to update in dead poll mode. screenshoot attached. what do i do fix this? windows 7 x64.

After it freezes, unplug the V2 - does the software unfreeze? If so, save a trace file (on the [F8: Trace] tab page) and send it to me at paul@efilive.com

Regards
Paul

[vectorbundle]

After it freezes, unplug the V2 - does the software unfreeze? If so, save a trace file (on the [F8: Trace] tab page) and send it to me at paul@efilive.com

Regards
Paul

yeah, the update doesn't freeze per se, progress bar just stops and $0101 error window pops up. then i have to dead poll start the box to get it recognized. rinse, repeat, same thing. i will try to install the software and update firmware tomorrow on another machine (that one is dual boot W7/XP so i can try both OSs). if that fails i will email a trace. thank you.

[vectorbundle]

firmware update succeeded on the other system (laptop). i wonder why it failed on my PC, it's a new machine and same W7 x64 operating system.

[GmcLbz]

I am having similar issues with my V2. I just updated to the Nov. 7th V8 and V7 release and tried to update firmware and boot block on V2. Now the blue light stays lit and screen reads EfiLive flashscan V2. It will not update
boot block and does not recognize current firmware or boot block. What am I missing? Current Firmware version 2.05.21 Sept. 25 2008 and boot block version 2.05.04 Oct. 16 2007 on V2.
When I unplug usb cable and plug it back in it says Boot block has been upgraded license will be upgraded now, click ok an It then says Upgrade completed successfully.

[joecar]

Did you read thru the pdf in post #1 here: Upgrading-from-older-boottblock-firmware (http://forum.efilive.com/showthread.php?20952-Upgrading-from-older-boottblock-firmware)


What firmware/bootblock versions did you have prior to updating...?
What did you do...?
What does V2 do now...?

[GmcLbz]

Did you read thru the pdf in post #1 here: Upgrading-from-older-boottblock-firmware (http://forum.efilive.com/showthread.php?20952-Upgrading-from-older-boottblock-firmware)


What firmware/bootblock versions did you have prior to updating...?
What did you do...?
What does V2 do now...?

Firmware/bootblock hasn't changed despite saying it was updated.
I downloaded latest release V8 and V7 onto laptop, then attempted to update bootblock. Now v2 is basically unrecognized.

[GmcLbz]

The firmware/boot block never changed despite saying it was updated. Firmware 2.05.21 and boot block 2.05.04.
I downloaded the latest release of the V8 and V7 software, then attempted to update the boot block. V2 is basically unrecognized now.

[joecar]

Are the amber LEDs flashing on your V2 (flashing in alternation)...?

[GmcLbz]

No, the blue light is on though.

[joecar]

I think you have to send it in.

[GmcLbz]

Okay, where do I send it?

[joecar]

Where are you located...?

[joecar]

When you connect EFILive Explorer what do you see on the Firmware tab...?

[Tordne]

I'm not sure about the blue LED in this scenario but the only time I've ever seen a scenario where the licensing prompt is continually presented is where the user has updated to the 2.05.x bootblock prior to having first upgraded to the 2.04.72 firmware first. This was essential and highlighted in the upgrade documentation.

I've attached a process that was put together some years back that was able to resolve this issue. Note that the instructions are going to be out of date as the V8 software has progressed significantly past this checkpoint. Broadly the steps should be pretty similar however so hopefully you're able to follow them. If you're not able to resolve the issue then you will need to have the device sent in for repair. Please raise an RMA case on our helpdesk (http://support.efilive.com/) and indicate if you are in the USA or not.

If you are able to recover then you should be able to update bootblock and firmware to the 2.07.x series.

16122

[joecar]

GmcLbz,

Please follow the document EFILiveRocovery.txt found inside the zip file that Tordne posted.

[GmcLbz]

Gonna try it in a bit...I'll post back.