Jump to content

Programming Key Fob

Jack6389
 Share

Recommended Posts

Jack6389 New Member

Jack6389

Posted
Posted

 

2021 Silverado 1500 RST with 6.2, Push button start/stop.  I had one key fob, tried to program a second one. First locksmith could not get a fob to program. Got to the message that says ready to learn remote 1. Placed new fob in pocket between the cup holders. Press start/ stop button and nothing happened. Drove home and then the original fob stopped working. The original fob would not do anything. DIC kept saying no remote detected. Could not start the truck, etc.  called mobile locksmith, they worked for like two hours, using programmers, their fobs, the gm computer, etc. No Luck! Had trucked towed to dealership. Now five days later, the dealership can’t get anything fobs to program or work. Was able to get truck started once they said but nothing else.  Have had GM engineers investigating as well. Anyone have this happen? Any ideas? Bout ready to just wire a key type ignition in, lol..

 

 
GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted
On 4/25/2025 at 10:07 PM, Jack6389 said:

 

 

2021 Silverado 1500 RST with 6.2, Push button start/stop.  I had one key fob, tried to program a second one. First locksmith could not get a fob to program. Got to the message that says ready to learn remote 1. Placed new fob in pocket between the cup holders. Press start/ stop button and nothing happened. Drove home and then the original fob stopped working. The original fob would not do anything. DIC kept saying no remote detected. Could not start the truck, etc.  called mobile locksmith, they worked for like two hours, using programmers, their fobs, the gm computer, etc. No Luck! Had trucked towed to dealership. Now five days later, the dealership can’t get anything fobs to program or work. Was able to get truck started once they said but nothing else.  Have had GM engineers investigating as well. Anyone have this happen? Any ideas? Bout ready to just wire a key type ignition in, lol..

 

 

This sounds like an upsetting concern, Jack. Our team would like to connect with your GM dealership to learn more, and assist however we are able. When you have a moment, please email us at [email protected] with your full VIN along with the name and address of your dealership so we can reach out. By sending us a message, you consent to the information you provide being monitored and recorded by GM or those acting on GM’s behalf, subject to the GM Privacy Statement: https://www.gm.com/privacy-statement.

scokill Enthusiast

scokill

Posted
Posted (edited)

After this happened to me, this seems to be a somewhat common problem relatively speaking.  I had this issue initially where it wouldn't recognize any fob and was stuck in the program loop.  I could start with app, but couldn't drive.  It ended up working after a couple of hours while a tow truck was on the way.   It turned in to a truck battery issue.  

 

Some have replaced their truck battery and all was well.  Some have a battery drain by itself, or in conjunction the key fob issue.  There is a service bulletin about unexplained key fob issues with no apparent root cause found.  It discusses replacing the drivers window switch/control, the door latch assembly, or both.  Some have replaced the window switch alone and it has gone away.  I replaced the window switch since it's cheap and easy to do.  

 

On the door switch, the theory is that a bad switch send the key lock/unlock signal over and over and puts it in program mode.  Some also attribute this to the battery drain since the system turns on over and over.  Some have said that holding the start button for 15 seconds will take it out of the mode and let you start.  When it happened to me a few times, I just disconnected the negative battery post and all was well until it happened again.  I carried around a 10mm socket.

 

Also if you have something in the OBD2 port, like retractable steps, start stop disable, etc., there are reports of this causing issues.

 

Lastly, which I think was cause of my issue, is the rear glass leaking.  There is a technical service bulletin about that too.  I had noticed that the battery drain happened when it rained.  I started digging around and my headliner was wet.  I found the leak and there are numerous electrical connections below that could have gotten moisture or wet and cause drain, which in turn could cause the key fob issues.  The frame for the rear glass is plastic and cracks.  There are two ways to fix, fill full of silicone or body sealant, or replace the back glass.  This is a known problem.

 

I'm hoping this fixed my issue and my battery was drained to like 5v several times, so I think my new battery may be toast.  It was low again the other day, but haven't had the key fob issue again.  By the way, the dealer had it for 5 days, couldn't find an issue, and several days later of course the battery drained.

Edited by scokill
Jack6389 New Member

Jack6389

Posted
  • Author
Posted
On 4/25/2025 at 10:07 PM, Jack6389 said:

 

 

2021 Silverado 1500 RST with 6.2, Push button start/stop.  I had one key fob, tried to program a second one. First locksmith could not get a fob to program. Got to the message that says ready to learn remote 1. Placed new fob in pocket between the cup holders. Press start/ stop button and nothing happened. Drove home and then the original fob stopped working. The original fob would not do anything. DIC kept saying no remote detected. Could not start the truck, etc.  called mobile locksmith, they worked for like two hours, using programmers, their fobs, the gm computer, etc. No Luck! Had trucked towed to dealership. Now five days later, the dealership can’t get anything fobs to program or work. Was able to get truck started once they said but nothing else.  Have had GM engineers investigating as well. Anyone have this happen? Any ideas? Bout ready to just wire a key type ignition in, lol..

 

  • So it turned out that the Theft Deterrent Module (TDM) or also referred to as Anti-Theft Module or Passive Entry Passive Start Module (PEPS) or just the Immobilizer Module was faulty. GM Part Number 13516352

    Then the new module required advanced EEPROM reprogramming to function correctly. 
    (From web search) In vehicles, EEPROMs are integral to various control modules, including the Theft Deterrent Module (TDM). They store critical data such as immobilizer codes, key fob identifiers, and security algorithms. If the EEPROM within a TDM becomes corrupted or fails, it can lead to issues like:

  • Inability to program or recognize key fobs
  • “No Crank/No Start” conditions
  • Persistent “Service Theft Deterrent System” message

  • Anyways, it is fixed, and I have two new key fobs.

  •  
  • Quote

 

 

scokill Enthusiast

scokill

Posted
Posted

Add this to the list of things that can cause this.  Mine had no problems for awhile and now one trip to the car wash and it happened.  Went away quickly though.  Maddening.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...