DevSecOps
Well-Known Member
- First Name
- Todd
- Joined
- Sep 22, 2021
- Threads
- 69
- Messages
- 4,740
- Reaction score
- 11,500
- Location
- Sacramento, CA
- Vehicles
- '21 Audi SQ5 / '23 Rivian R1T / '23 M3P
- Occupation
- CISO
- Thread starter
- #1
As always let me preface this by saying that the following is available via FDRS and it is NOT available from your dealer (for free) or via OTA. We assume that one day you should get them OTA, but no clue as to when. Per this post, these are the same modules as in 2.5.2 so if you're in EAP you should get them OTA soon.
These updates are available for both Job1 and Job2 (see warning below) vehicles as of today.
Originally per this post and this post, we had confirmation that Job2 vehicles were left with bricked CCM modules when attempting these updates. Per @benk016 he was able to flash the CCM module successfully with FORScan, but not with FDRS. Also per Ben, even though FDRS failed the IPMA, FORScan is showing it to be completed. This means that on a Job2 car you might need FORScan and FDRS (requiring different adapters as well) to install these updates.
UPDATE: It would appear that those with the Mongoose adapter are having a higher level of success when updating vs other's with other adapters. The experience shared by Ben was NOT using a Mongoose adapter. Others using Mongoose are reporting success without bricked CCMs on both Job1 and Job2. If you do NOT have a Mongoose adapter you might want to read about how to recover the CCM with FORScan.
UPDATE 2: It is reported that IPMA and PSCM don't clear the update list after successful completion. I can confirm this through multiple VINs as well. Expect them to remain.
WARNING: I would not even attempt these updates wihout a connected power supply to the LVB. The IPMA update alone is a long update (186mb). The IPMA is NOT USB, meaning it could likely take hours!
These updates are available for both Job1 and Job2 (see warning below) vehicles as of today.
Originally per this post and this post, we had confirmation that Job2 vehicles were left with bricked CCM modules when attempting these updates. Per @benk016 he was able to flash the CCM module successfully with FORScan, but not with FDRS. Also per Ben, even though FDRS failed the IPMA, FORScan is showing it to be completed. This means that on a Job2 car you might need FORScan and FDRS (requiring different adapters as well) to install these updates.
UPDATE: It would appear that those with the Mongoose adapter are having a higher level of success when updating vs other's with other adapters. The experience shared by Ben was NOT using a Mongoose adapter. Others using Mongoose are reporting success without bricked CCMs on both Job1 and Job2. If you do NOT have a Mongoose adapter you might want to read about how to recover the CCM with FORScan.
UPDATE 2: It is reported that IPMA and PSCM don't clear the update list after successful completion. I can confirm this through multiple VINs as well. Expect them to remain.
WARNING: I would not even attempt these updates wihout a connected power supply to the LVB. The IPMA update alone is a long update (186mb). The IPMA is NOT USB, meaning it could likely take hours!
Sponsored
Last edited: