Valeo BSI N0X EEPROM 95256 IMMO PIN Decode, Mileage Correction & Virgin Reset Using ALicar ACT V2
When working on PSA vehicles equipped with Valeo BSI modules, the BSI-N0X-00 (SC667152 + EEPROM 95256) is one of the most commonly serviced units in automotive electronic diagnostic and immobilizer repair. This guide explains how to read and modify internal EEPROM data, extract the IMMO PIN, correct mileage values, edit diagnostic history and prepare a BSI to “Virgin” state for replacement or cloning.
Tools & EEPROM Reading Methods
Multiple programmers can be used to read EEPROM 95256, but not all of them provide stable and verified results:
| Tool | Result | Verification |
|---|---|---|
| UPA 1.3 / SEEPROG | Read errors | Not recommended |
| UPA-S (with power) | OK | Verified |
| Xprog-M | OK | Verified |
| Carprog (with power) | OK | Verified |
| Vellon VP390 (with power) | OK | Verified |
| IO-Terminal | Best option | OBD / Bench + auto PIN decode |
| ALicar ACTV2 | Full support | Read/Write, PIN decode, mileage correction & Virgin reset |
Using ALicar ACT V2 Coding Tool
The entire process—including EEPROM reading, IMMO PIN extraction, mileage correction, checksum calculation, and Virgin BSI preparation—can be implemented conveniently using the ALicar ACT V2 coding tool, which supports both OBD and bench connection modes. It offers secure read/write operations and prevents data corruption issues commonly seen with unstable tools.
IMMO PIN Handling
Two pin structures exist:
| Type | Description |
|---|---|
| Open PIN | Directly visible in dump and editable |
| Crypto/Locked PIN | Encrypted after VIN checksum, requires decoding |
ALicar ACT V2 or IO-Terminal can automatically decode Crypto PIN values without manually reverse-engineering algorithms.
Mileage Correction Structure
Mileage is stored in a 4-byte HEX area with XOR + checksum validation.
Example conversion:
00 00 83 6D → DEC = 3364.5 km
XOR with FF FF FF FF → FF FF 7C 92
To write a new mileage:
-
Convert km ×10 to HEX
-
Calculate XOR
-
Update values in EEPROM
-
Recalculate checksum
Incorrect checksum → BSI rejects the value.
DTC History Editing
Error history and mileage timestamps can be edited manually. Clearing specific sections resets DTC history; incorrect clearing may cause Diagbox to show “error data history is blank”.
Virgin BSI Reset Procedure
To reuse the BSI on another vehicle:
| Area | Action |
|---|---|
| VIN | Set to FF (17 bytes) |
| PIN | Set to FF (all PIN sections) |
| Mileage | Reset with checksum |
| DTC/Event history | Clear if needed |
After Virgin preparation → Use Diagbox to assign new keys & PIN.
Conclusion
This guide provides complete procedures for:
-
EEPROM 95256 reading & editing
-
IMMO PIN decode (including crypto)
-
Mileage correction with checksum
-
DTC history manipulation
-
Virgin BSI preparation and cloning
For reliability and safety, ALicar ACTV2 coding programmer is highly recommended as the primary programming solution.
- Company Info
- Feedback
- Customer Reviews
- About Us
- Contact Us
- News
- User Center
- Forget Password
- My Orders
- Tracking Order
- My Account
- Register
- Payment & Shipping
- Customs & Taxes
- Locations We Ship To
- Shipping Methods
- Payment Methods
- Company Policies
- Return Policy
- Privacy Policy
- Terms of Use
