June 25, 2024, V8.4.58 Public Release - Update 4

[Blacky]

V8.4.58 Public Release - Update 4

Pay particular attention to the warnings below - once you have updated your FlashScan/AutoCal firmware to this latest version you will not be able to "go back" to using previous firmware or software versions.

WARNING for FlashScan/AutoCal V2 users:
Firmware version V2.08.209 is fully compatible with the EFILive V8 software.
If your V2 firmware is between versions V2.08.199 and V2.08.208 (inclusive), then it is not compatible with any version of the V7.5 software.
If your V2 firmware is V2.08.209 (or later), then it is compatible with the latest V7.5.49 software - except for reading and flashing tune files. All reading and flashing duties must be performed with the V8 software or in standalone mode.
NOTE: The V7.5 software is no longer actively supported - EFILive does not provide technical support for the EFILive V7.5 software.


NOTE for FlashScan/AutoCal V3 users:
Firmware versions V3.00.115-V3.00.126 may be rolled back to firmware version V3.00.114.


NOTE for all users:
Tune files saved using the latest EFILive V8 software(V8.4.58) can now be used with the latest EFILive V7 software (V7.5.49) and vice-versa.



Full Release Notes:
What's New (https://download.efilive.com/Software/whatsnew_8_4_58.htm)


Version Numbers:

After installing this release you should have the following software and firmware versions installed:



[*=1]EFILive V8 software: V8.4.58
[*=1] FlashScan/AutoCal V3 Firmware: V3.00.126
[*=1] FlashScan/AutoCal V2 Firmware: V2.08.209


Download here:

Download V7.5.49_Setup (https://download.efilive.com/Software/V7.5/EFILiveV7.5.49_Setup.exe)
Download V8.4.57_Setup (Update 4) (https://download.efilive.com/Software/V8/EFILiveV8.4.58_Setup.exe)



Known Limitations:


Limitation #1: When logging DMA PIDs (i.e., PIDs whose names end with "_M" or "_DMA"), if the ignition is switched off for an extended period while data logging but data logging is not terminated, then when the ignition is switched on again the data log automatically continues. However, the DMA PIDs may no longer return valid data.
Workaround: EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.

Limitation #2: When logging DMA PIDs (i.e., PIDs whose names end with "_M" or "_DMA"), that are specific to a custom operating system such as DSP2 or DSP5 PIDs when running a stock operating system, the values returned by those DMA PIDs will not contain valid information and should be ignored.
Workaround: Ignore unsupported DMA PIDs.



Known Issues:


None.



Regards,
The EFILive Team

[juddski88]

I noticed that you said you had issues with LBZ/LMM Flashing Errors, did you receive complaints since V8.4.54 about "no data received" or "locked with a custom key" errors with LB7 and LLY controllers as well? I have an otherwise working version, that I know of, of v8.4.54 that could not read a couple stock lb7s and one lly last week until I tried with my non-updated v2 and v7.5. I had tried with v8 about 6 times each and v7.5 read it first try.

[Blacky]

I noticed that you said you had issues with LBZ/LMM Flashing Errors, did you receive complaints since V8.4.54 about "no data received" or "locked with a custom key" errors with LB7 and LLY controllers as well? I have an otherwise working version, that I know of, of v8.4.54 that could not read a couple stock lb7s and one lly last week until I tried with my non-updated v2 and v7.5. I had tried with v8 about 6 times each and v7.5 read it first try.

Can you please create a support ticket for the failures: https://service.efilive.com/new-ticket
And include the relevant trace files. If you are using a V3 device, the most useful trace files are the *.xalm trace files that you must save manually on the V3 device using: Scan Tool-> F3: Scan Options -> F1: Save Trace File after the error occurs during a pass-thru operation and before disconnecting from the vehicle.
If you are using black box (stand alone) flashing, the *.xalm trace files are saved automatically when an error occurs during reading/flashing.


Regards
Paul

[Highlander]

Thanks for this update!