6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHBroken Key Success!
Leading reported evidence
Use of the 3 options at different times
Performed · outcome unconfirmed
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 performed work without a confirmed outcome
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.
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
2) As the remote uses a rolling code (new code every lock cycle) if the remote sender has been activated more than 256 times and less than 1024 times with the receiver out of range or while the vehicle battery is disconnected the unit must be resynchronized as follows:
Leading evidence: 'Use of the 3 options at different times' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Disconnect unit must be resynchronized as follows' (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.
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 performed work without a confirmed outcome
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.
Performed · outcome unconfirmed · Original poster
I used the procedure shown on the post from here by GT4.
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
2) As the remote uses a rolling code (new code every lock cycle) if the remote sender has been activated more than 256 times and less than 1024 times with the receiver out of range or while the vehicle battery is disconnected the unit must be resynchronized as follows:
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.
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
You should try these in order, but note that if 3) is used, 1) and 2) will need to be run again.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Disconnect unit must be resynchronized as follows
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
2) As the remote uses a rolling code (new code every lock cycle) if the remote sender has been activated more than 256 times and less than 1024 times with the receiver out of range or while the vehicle battery is disconnected the unit must be resynchronized as follows:
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.
6 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261026T161109Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
When I bought my 996 neither of the keys worked with the remote central locking, they were fine to open the driver's door but this didn't open the passenger side and you needed the key in ignition quickly to avoid the alarm being triggered.
I sorted one last year with a process of recoding it to the car that I'd read on the forum here - so thanks for that info. The other key needed a bit more work which I finally sorted today.
When I opened it up I noticed that the layout was different from the working keyfob and found that a micro switch had broken off. I bought a set of 3 from eBay for £2.49 that have sat in the garage since last year but thanks to the lockdown I finally got motivation to sort it. It was pretty straightforward and I just needed fine tweezers to hold the switch in place. I'd suggest very fine solder - I didnt have this and had to make small dabs from the thicker strands.
Switch in place and tested on car - all works fine, in fact too well. I've seen comments that the 996 remote range is too short but it still triggered through multiple walls and locked the car in the garage!
I did a short video if it helps anyone else in future
I used the procedure shown on the post from here by GT4. I've used all of the 3 options at different times
http://www.911uk.com/viewtopic.php?p=790556
RESET PROCEDURE
1) Reset by manually unlocking the car door and whilst the key is still in the door, press the button, lock/unlock button. This re-syncs the electronics if it is time that has caused the car to forget the remote.
2) As the remote uses a rolling code (new code every lock cycle) if the remote sender has been activated more than 256 times and less than 1024 times with the receiver out of range or while the vehicle battery is disconnected the unit must be resynchronized as follows:
- Switch on the ignition (ignition key must have the correct transponder).
- Switch off the ignition.
- Remove the key and press the remote sender button within 6 seconds after the ignition key has been removed
The activation counter will then be reset to zero.
3) If the fault lies with the remote, you can reset the remote fob's chip by inserting the button battery in reverse (wrong way round) for a couple of seconds. (ie -+, +-)
You should try these in order, but note that if 3) is used, 1) and 2) will need to be run again.
This is a source reference. Confirm exact model applicability in the original material.
