The following issues were identified during the development, testing and use of FORScan v2.4:
1. There are still enough users who do not realize what the Module Firmware Update process is. They think it's about the same as installing a Windows or Android update. Although any specialist knows that programming a module is always a risk that the module will be bricked. As experience shows, dealership scanners (unlike FORScan) simply do not program many modules and firmware, even although the firmware is available. This way they minimize a risk to brick the module. So, although the firmware is available, it is not really possible to predict if the flash process works smoothly for this module, how the new firmware will work and how to fix the problems in case of something happens. Official dealers and the manufacturer solve these problems in quite a simple way - by limiting the firmware update options and, if this does not help, by replacing the module (sometimes even under warranty). FORScan team isn't ready to bear this responsibility either morally or financially.
2. There are still enough users trying to use non-recommended adapters. Currently recommended adapters for version 2.4 are OBDLink EX, ELS27 (with firmware 5.6.5 or newer), vLinker FS. From the J2534 Passthru, the recommended ones are VCMII (genuine) and Scanmatik SM-2. The remaining J2534 adapters are either limited in their supported functionality and protocols (Tactrix OpenPort 2.0, Chipsoft, UCDS), or do not work correctly (VCMII clones, VCXDiag in VCMII mode, etc.), or we simply do not have reliable statistics on them.
3. In general, experience shows that reliable work with firmware requires certain conditions: an availability of a suitable place or room (box or garage), an ability to connect the car battery to a charger or a power supplier, an ability to connect a laptop to the external network for a reliable power supply, an ability to disconnect or dismount the faulty module or battery if necessary, and etc.
4. Experience shows that operator's skills and competence are very important.
5. Support for the firmware database of new models (from 2018-2020, but especially from 2022) is quite difficult due to the fact that the manufacturer hides information about this in every possible way, tries to control access by transferring the software and databases to the "clouds" and so on. Reliable methods for obtaining this information have not yet been found (although work is underway). For this reason, FORScan development team currently has no ability to keep the firmware database for the latest car models up to date.
6. Users' support for version 2.4 is quite complicated and expensive in terms of time and resources. In some cases we have to spend 1-2 days to help to recover some bricked module. All other work actually stops at this time. The development team currently has no chance to provide the same level of support for version 2.4 that is currently provided for version 2.3, given the low priority work on version 2.4.
Thus, for the transitional period (until these problems are somehow resolved), it was decided to restrict access to versions 2.4 in the following way:
1. The user acknowledges that he understands and accepts all the risks, requirements and limitations of using version 2.4 listed above, and agrees to use the product on an AS IS basis (that is claimed in FORScan End User License Agreement but nobody reads it anyway).
2. The user is paid Extended License owner.
3. The latest v2.4 is available for download in the hidden forum (for registered users only).