fullymatted.
Back to search
Rennlist

Immobilizer Water Damage and Reverse Engineering

Add to repair workspace
Open repair workspace
Original source
4 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHImmobilizer Water Damage and Reverse Engineering

Leading reported evidence

Use remotes

Suggestion or failed attempt

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context

Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.

Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

The highlights are that you can easily clone a water damaged module with just an EEPROM reader, the key learning code is stored plaintext and easily accessible, and one day I hope to be able to program used remotes that don't have their original programming codes.

Original post Read captured discussion
Immobilizer Water Damage and Reverse Engineering
Read full discussion summary

Leading evidence: 'Use remotes' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Use remotes' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.

Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.

Read captured replies

1 matching discussions · 4 captured posts examined · 0 partial discussions

Frequently discussed actions (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Use remotes

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1

0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.

0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.

Suggestion · Original poster

The highlights are that you can easily clone a water damaged module with just an EEPROM reader, the key learning code is stored plaintext and easily accessible, and one day I hope to be able to program used remotes that don't have their original programming codes.

Original post Read captured discussion
Immobilizer Water Damage and Reverse Engineering
Coverage and how to read this overview

Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.

4 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Rennlist: 1 discussions

0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.

0 acknowledgements have no verified action link; they do not establish a repair result.

Generation: 20261026T191851Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

Earlier this year I came back from a trip to find that a parking lot had flooded and that I was going to have a much more annoying journey home than hoped. This combined with the desire to have a second key and not pay a dealer a ton of money resulted in a lot of learning about the immobilizer. Since all the information I could find was scattered and some important stuff was missing from the internet, I've collected my notes here. https://github.com/bdm310/996-Immobilizer The highlights are that you can easily clone a water damaged module with just an EEPROM reader, the key learning code is stored plaintext and easily accessible, and one day I hope to be able to program used remotes that don't have their original programming codes.

POST 2Original post

It's all way above my head, but I dig what you've done - I'll need one of the EE's at work to translate into my idiot speak.

POST 3Original post

All the more reasons to get the waterproof immobilizer box from ECUDoctors!

This is a source reference. Confirm exact model applicability in the original material.