Robaizkine - Car Electronics Store

After experiencing issues multiple times with both genuine AVDI and FVDI/SVCI, we discovered that on some JC BSI units, FVDI/AVDI can corrupt the flash when attempting to read it. To enable it to read the EEPROM, it writes a new flash, but when it tries to put the original flash back, it fails the checksum because it’s corrupted, leaving the BSI dead in boot mode.

Adding power by jumpleads doesn’t seem to make any difference, as reported by others. Some versions of software always seem to corrupt, even if the flash is read before the pincode is read. The flash that FVDI/AVDI reads is stored in the “My Documents” folder, under “ABRITES software for ID ******/psa”. The location may vary slightly depending on the version of Windows you’re running, but you can search for “psa” in “My Documents” or view by date modified, and it will be obvious.

At this point, you need an undamaged flash. Some undamaged flash files are available on various forums, but a few can be difficult to find. Don’t write the flash or it will wipe the EEPROM and require reconfiguration.

Here’s a solution that has been tested and works 100% on numerous vehicles:

Find your flash ID by opening BSI with FVDI and get a 4-digit software signature. Then obtain a good file with this ID.
Go to the file location and replace the corrupt file with the good one. Make sure to make this file write-protected, and it must have the exact same name as the original (e.g., JCI_BSI_7F0B.bin).
Perform the pin read again with FVDI, and it will work correctly, giving you the pincode, and the car will come back to life. You can then program keys or whatever you wanted to do in the first place.
As long as you keep the good file in its location and write-protected, FVDI will always work okay for any BSI with the same software signature.]

We have a collection of good BSI flash dumps, you can contact our live support or email us at: [email protected]