April 2021, V8.3.5 RC 3

Printable View

April 12th, 2021
Blacky

April 2021, V8.3.5 RC 3
Release Candidate 3

This version of the EFILive software and firmware is a release candidate. That means it has successfully completed beta testing and may be used in production environments.
The "Check for Updates" options in the V7.5 and V8 software have not been activated yet. They will be activated when the release is promoted to a full public release.

The current public release is available here.

Attention:
V7.5 no longer supports installation to Windows XP or Windows Vista. This change is due to SHA1 having been deprecated by digital certificate authorities. More info on SHA1
V7.5 and V8 are now only supported on Windows 7, 8, 8.1 and 10.
WARNING:
Due to the new security/encryption option in this release, all tune files saved using V7.5.34 or V8.3.5 of the software or V2.07.169 or V3.00.059 of the firmware will no longer be compatible with older versions of the V7 or V8 software. If you distribute tune files to other users (i.e. your customers), the recipients must be:
- using version V7.5.34 or V8.3.5 or a later version of the software.
- using version V2.07.169 or V3.00.059 or a later version of the firmware.
Full Release Notes:

Whats New

Version Numbers:
After installing this beta release you should have the following software and firmware versions installed:
- EFILive V7 software: V7.5.34 To view the installed version, select Help->About (in the V7 Scan or Tune software).
- EFILive V8 software: V8.3.5 To view the installed version, select Help->About (in the V8 Scan and Tune software).
- FlashScan/AutoCal V3 Firmware: V3.00.062 (Mar 25, 2021).
- FlashScan/AutoCal V2 Firmware: V2.08.172 (Mar 25, 2021); Boot Block: V2.08.009 (Feb 27, 2021)
Download here:

Known Issues:
Issue #1:
Importing JTAG E86B files may result in a Boot Software segment checksum error.
Workaround:None.
Don't flash imported files with checksum errors. Don't use the EFILive software to correct checksum errors for the E86B imported files as that does not fix the underlying cause of the checksum error - it just masks the error(s) and causes additional problems.
We are working on a solution to that problem.

Regards,
The EFILive Team
April 15th, 2021
Chavez91

7A5.cax: No [A40] entry in C:\Program Files (x86)\EFILiveProduction\V8\V7toV8_Segments.ini

Is the naming scheme for V8 different for A40? Or do I just need to convert it over by hand?
April 16th, 2021
wesam

Paul it seems there is some thing wrong with 7.5
when trying to open some OSs it will show unrecognized PCM then when I press OK it will open
as example OS 05120003 and 12592425
for 05120003 also it will not show the full flash button but when opened in V8 it will open normally and flashed normally
Also I had another problem when I read from LS1B it happened in two cars that after the read completed successfully a floating point error division by zero is shown and I could not save the file
April 21st, 2021
Blacky

Quote:

Originally Posted by Chavez91

7A5.cax: No [A40] entry in C:\Program Files (x86)\EFILiveProduction\V8\V7toV8_Segments.ini

Is the naming scheme for V8 different for A40? Or do I just need to convert it over by hand?

I think I just got it wrong in C:\Program Files (x86)\EFILiveProduction\V8\V7toV8_Segments.ini

I had section [AL6] defined like this:

Code:

[AL6] ;V7 V8 Segment ;-- -- ----------------------- 0= 99 EFILive Custom Calibrations x= 0 Operating System (was used in V7 for custom cals) 1= 1 Transmission Calibration 3= 1 Transmission Calibration

when I should have had two sections called [A40] and [A50] defined like this:

Code:

[A40] ;V7 V8 Segment ;-- -- ----------------------- 0= 99 EFILive Custom Calibrations x= 0 Operating System (was used in V7 for custom cals) 1= 1 Transmission Calibration 3= 1 Transmission Calibration [A50] ;V7 V8 Segment ;-- -- ----------------------- 0= 99 EFILive Custom Calibrations x= 0 Operating System (was used in V7 for custom cals) 1= 1 Transmission Calibration 3= 1 Transmission Calibration

If you make that change does it work correctly?

Regards
Paul