17 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHLight on keyfob stays on???
Leading reported evidence
Clean terminals - and voila, back in service
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.
Performed · outcome unconfirmed
So I cleaned the terminals - and voila, back in service.
Leading evidence: 'Clean terminals - and voila, back in service' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'battery and put in a new one' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Clean terminals - and voila, back in service' (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
I opened the key using my little Swiss Army knife, removed the battery, installed a new one, tested the remote feature with my car, and I'm good to go.
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 suspect a cause
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.
Suspected cause
I assumed it was the battery and put in a new one, but that didn't fix it.
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 suspect a cause
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.
Suspected cause
I don't know if it was the battery now but at least there's a fresh one in there.
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
and push the tip into the gap and slide the tip around the key and use more force until the halves separate.
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
I opened the key using my little Swiss Army knife, removed the battery, installed a new one, tested the remote feature with my car, and I'm good to go.
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.
17 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.
5 acknowledgements have no verified action link; they do not establish a repair result.
Carefully separate the 2 halves of key fob head and remove the battery. Reverse the battery and reinstall it in the key fob. Then press a button on the key fob. Release the button remove the battery and install it the right way again and put the two key fob halves back together. There's tiny o-ring that can get out of place and make the reassembly difficult.
This 'technique' is supposedly in a Porsche TSB somewhere.
I've used it, but I've also used with success simply removing the battery and pressing one of the buttons. But if this doesn't work for you do the battery reversal thing.
Sincerely,
Macster.
Thanks Macster, just had the problem, followed your instructions, and it worked! I doubt I will, but now let's just hope that I don't have to get the key head re programmed!
That happened to me last week too. I assumed it was the battery and put in a new one, but that didn't fix it. So I cleaned the terminals - and voila, back in service. I don't know if it was the battery now but at least there's a fresh one in there.
I followed the lead from Macster by shorting the battery terminals when the battery was removed. It immediately fixed the problem.
This was a great, immediate help, thanks!
I use the screw driver blade tip of my small pocket Swiss knife (see link)
http://www.swissknifeshop.com/swiss-...FYJzMgod-mcATg
and push the tip into the gap and slide the tip around the key and use more force until the halves separate. I just did this with a Turbo key I've never had apart before. The cover lets go with a nice snap.
Well. That was a bad time. Got it open but can't get it to seat back together and the light is out but the remote isn't working even with a new battery.
Old thread revival, but this happened to me yesterday. Followed some of the advice here: pried apart the fob and removed the battery. Left it out for an hour or so, then replaced it. Had a heck of a time getting the two sides to re engage. Finally figured out the way to do it is to seat the circuit board side first with the half of the fob case with the 'pegs'. Once that snaps in, the other side will seat easily. This from a guy with 10 thumbs.
Interesting that this thread is almost 7 years old, so it's not a new issue. I've had my '02 911 for over 3-1/2 years and never experienced it, until today. I opened the key using my little Swiss Army knife, removed the battery, installed a new one, tested the remote feature with my car, and I'm good to go. Biggest issue was getting the two key halves back together. Make sure everything is in place in both halves, then carefully mate the two. "tcc"......thanks for the tip.
This is a source reference. Confirm exact model applicability in the original material.
