ECU and SRS Configuration Reset Script for Toyota / Lexus (iProg Pro)
The configuration (vehicle specification) reset script is designed for operation with ECU (Electronic Control Unit) and SRS (Supplemental Restraint System / Airbag) modules in Toyota / Lexus vehicles. The solution is intended for vehicles manufactured approximately from 2016 and is used in conjunction with the iProg Pro programmer..
The script only works with original iProg Pro programmer! Please write Serial Number and UID in the order.
The scripts allow correct clearing and restoration of configuration data without causing conflicts between vehicle systems. All operations are performed via memory dump.
Supported Modules and Technical Details
SRS support:
- SRS modules based on Renesas R7F701A223 microcontroller
- Dump-based operation
- No similar issues observed on other hardware revisions
ECU (Engine Control) support:
- Engine control units with 95320 EEPROM
- Dump-based operation
The script is optimized to eliminate configuration conflicts between the engine ECU, instrument cluster, and active safety systems.
Application Scope and Solved Issues
Typical scenario: after resetting the configuration (vehicle specification) in the instrument cluster, the adaptive cruise control stops working correctly. When activated, related error messages appear on the dashboard due to configuration mismatch.
After applying this script:
- adaptive cruise control is correctly converted to standard cruise control;
- configuration conflicts within the engine ECU are eliminated;
- SRS module errors related to the PCS (Pre-Collision System) are removed.
The script provides a complete and consistent restoration of configuration data across all involved systems.
List of Tested ECU and SRS Modules
Engine Control (ECU):
- ECU 89666-60P10 — LC-300, EEPROM 95320
- ECU 89661-78F40 — NX300, EEPROM 95320
- ECU 89661-78720 — NX300, EEPROM 95320
SRS:
- SRS 89170-0E450 — V70
- SRS 89170-33D30 — ES300
Open the program and click “Help” -> “About”.

Copy data from the program when placing an order

After completing the order, you will receive files, they must be added to the Scripts folder..

Launch the program and on the left side of the screen you will see the added scripts.

1. No Refunds or Modifications for Digital Licenses
Activated modules or licenses cannot be returned or refunded.
If an incorrect key or device number is entered by the customer, the purchase is not eligible for return.
Licenses cannot be modified, transferred, or reissued for another device under any circumstances.
2. Irreversible Order Processing
After the order status changes to “Waiting for activation”, the data has already been sent to the developer.
From this point onward, the order cannot be canceled, edited, corrected, or refunded.
3. Responsibility for Software Functionality
Our store is not responsible for the functionality, performance, or declared features of any software module.
We do not guarantee the listed functions because we are not the developer.
4. Accuracy of Product Information
Module and script descriptions are provided directly by the manufacturer.
IOBD.io is not responsible for any inaccuracies, missing details, or differences between the description and actual operation.
In disputed situations regarding functionality or listed features, the customer must contact the manufacturer.
5. Customer Responsibility for Installation
IOBD.io sells professional automotive diagnostic software and equipment.
Installation, setup, configuration, and compatibility checks must be performed by the customer.
We do not provide remote installation, programming, or setup services unless explicitly stated otherwise.
6. Required Technical Knowledge
These products are intended for users with basic technical knowledge in automotive diagnostics.
The customer is fully responsible for understanding the installation process and using the software and hardware correctly.
7. No Liability for Incorrect Usage
IOBD.IO is not responsible for issues caused by:
incorrect installation
unsupported or incompatible hardware
improper configuration
third-party interference