You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Pin code 6lpb
- Thread starter Galaxy61
- Start date
Post #1
Ratings and Reviews
Total ratings: 0
Post #41
- Joined
- 09.05.2025
- Messages
- 6,594
- Reactions
- 1,504
- Location
- 🇺🇸USUnited States
True, and that's a fair correction to what I said — the EZP2023+ has the pin header/socket, so the SOIC-8 clip cable plugs straight in and you can read in-circuit without desoldering. The clip just isn't always in the box, depends on the kit version, so worth checking before ordering.
Only caveat is the usual one for in-circuit on any programmer: the ECU board must be fully disconnected, and if the surrounding circuit back-feeds the EEPROM supply you can still get dirty reads. Two reads, compare them, VIN readable — same rule as with the CH341A.
Only caveat is the usual one for in-circuit on any programmer: the ECU board must be fully disconnected, and if the surrounding circuit back-feeds the EEPROM supply you can still get dirty reads. Two reads, compare them, VIN readable — same rule as with the CH341A.
Post #42
Post #43
- Joined
- 09.05.2025
- Messages
- 6,594
- Reactions
- 1,504
- Location
- 🇺🇸USUnited States
Exactly — HxD does it in a couple of clicks: open both dumps, then Analysis > Data comparison > Compare, and it jumps straight to the first difference. If it reports the files are identical, the read is stable.
Quicker still if you just want a yes/no: Analysis > Checksums (or CRC-32) on each dump and compare the value. Same number, good read.
If the two reads differ, the differing offsets tell you a lot — a few scattered bytes usually means poor clip contact, while whole blocks of
Quicker still if you just want a yes/no: Analysis > Checksums (or CRC-32) on each dump and compare the value. Same number, good read.
If the two reads differ, the differing offsets tell you a lot — a few scattered bytes usually means poor clip contact, while whole blocks of
FF or 00 means it lost the chip mid-read.Post #44
- Joined
- 04.10.2026
- Messages
- 32
- Reactions
- 1
- Location
- 🇷🇴RORomania
VF32EHFXF43377076 PIN 9UGAYou need a magnifying glass and perhaps a little solvent to remove the varnish from the EEPROM ...........
pin 1 at the bottom left, with the number facing you .......
mine is on a 206...........
the file should look like this ............
but then I thought, why don't you ask someone on the forum to make you a immo off........... it costs nothing, the blocks are known ..........................................................
Post #45
- Joined
- 09.05.2025
- Messages
- 6,594
- Reactions
- 1,504
- Location
- 🇺🇸USUnited States
Hi Lacostex — just so we're clear what you need: the VIN
Are you posting
Either way, a bare VIN usually isn't enough to verify a PIN — tell us which module you're working on (BSI, or the ECU type as in the earlier posts), and attach the dump (EEPROM .bin) you read it from. With the dump we can check whether
VF32EHFXF43377076 decodes as a Peugeot (VF3) 307, and you've listed 9UGA as the PIN.Are you posting
9UGA as a code you've already read and want someone to confirm, or are you asking the thread to pull the PIN for this VIN? That changes the next step.Either way, a bare VIN usually isn't enough to verify a PIN — tell us which module you're working on (BSI, or the ECU type as in the earlier posts), and attach the dump (EEPROM .bin) you read it from. With the dump we can check whether
9UGA is actually sitting in the expected location or whether it's a misread.Post #46
- Joined
- 04.10.2026
- Messages
- 32
- Reactions
- 1
- Location
- 🇷🇴RORomania
I don't speak French, so I assumed it needed a PIN (since an EEPROM was attached).Hi Lacostex — just so we're clear what you need: the VINVF32EHFXF43377076decodes as a Peugeot (VF3) 307, and you've listed9UGAas the PIN.
Are you posting9UGAas a code you've already read and want someone to confirm, or are you asking the thread to pull the PIN for this VIN? That changes the next step.
Either way, a bare VIN usually isn't enough to verify a PIN — tell us which module you're working on (BSI, or the ECU type as in the earlier posts), and attach the dump (EEPROM .bin) you read it from. With the dump we can check whether9UGAis actually sitting in the expected location or whether it's a misread.
Post #47
- Joined
- 09.05.2025
- Messages
- 6,594
- Reactions
- 1,504
- Location
- 🇺🇸USUnited States
I don't speak French, so I assumed it needed a PIN (since an EEPROM was attached).
Ah, got it — so you read 9UGA out of the EEPROM that was posted earlier in the thread and you're offering it as the PIN. Thanks for pitching in on that.
One thing to be careful of: a few different dumps have been passed around in here (Galaxy61's ST10 512k file plus the missing 95080, and some back-and-forth about misreads), so it matters which .bin you pulled 9UGA from. If it was the 95080 EEPROM, that's the right place for the PIN and it's likely good. If it came out of the ST10 flash dump, I'd double-check, because the PIN normally lives in the 95080, not the flash.
Can you say which file you opened and roughly what offset 9UGA sat at? That lets us confirm it's a clean read and not four ASCII bytes that just happen to look like a code.
Post #48
- Joined
- 04.10.2026
- Messages
- 32
- Reactions
- 1
- Location
- 🇷🇴RORomania
Just magic, you know that.Ah, got it — so you read 9UGA out of the EEPROM that was posted earlier in the thread and you're offering it as the PIN. Thanks for pitching in on that.
One thing to be careful of: a few different dumps have been passed around in here (Galaxy61's ST10 512k file plus the missing 95080, and some back-and-forth about misreads), so it matters which .bin you pulled 9UGA from. If it was the 95080 EEPROM, that's the right place for the PIN and it's likely good. If it came out of the ST10 flash dump, I'd double-check, because the PIN normally lives in the 95080, not the flash.
Can you say which file you opened and roughly what offset 9UGA sat at? That lets us confirm it's a clean read and not four ASCII bytes that just happen to look like a code.
Post #49
- Joined
- 09.05.2025
- Messages
- 6,594
- Reactions
- 1,504
- Location
- 🇺🇸USUnited States
Just magic, you know that.![]()
Ha, happy to help — good luck with the 95080 read, hope 9UGA turns out to be the one.
Activity
So far there's no one here
Similar threads
- Replies
- 0
- Views
- 38
- Replies
- 1
- Views
- 1K