Jump to content

Recommended Posts

Posted

Anyone find a resolution? The battery went dead and now remote start doesn’t work (always had original one that came with truck). Now service theft comes on. So frustrating when I purchased the truck new in 2015 and now the warranty is out. I have always used original key that came with truck as well.

Posted (edited)

I bought a used 2015 Sierra about a year ago.  I had absolutely no issues until I took the truck in for service which included a recall (a year later with no previous issues).  About 2 weeks after service, I encountered the Theft Deterrent System light, power flickered, clock reset, and the vehicle wouldn't start.  I pulled back the key, waited, and tried again.  It finally started, but the dash light (vehicle with lock) remained on.  The next time I turned it on, everything was working.

 

I took the truck back to the dealership.  They verified my battery was working perfectly, but they found a random wire that they said was causing a short.  After 2 hours waiting at the shop, they rerouted this wire and sent me on my way.

 

Today, it happened again.  Same symptoms.  Same outcome.  I am getting irritated with something that seems to be so simple.  I actually installed a FIXD device a few days ago.  When this happened, I had the app scan for codes.  No alerts!  Nothing.  I did it a couple more times, but still nothing.  The app allows for submitting for unlisted codes, but it only allows for choosing from a limited list of dash lights which did not include this one.

 

 

image1.jpeg

Edited by kryptoknight
spelling & added image
Posted
On ‎2‎/‎8‎/‎2020 at 11:35 AM, Nurse30153 said:

Anyone find a resolution? The battery went dead and now remote start doesn’t work (always had original one that came with truck). Now service theft comes on. So frustrating when I purchased the truck new in 2015 and now the warranty is out. I have always used original key that came with truck as well.

I am just now researching this issue, but I wonder if the GM mechanic messed something up during one of my services.  I had it a year before any issues arose.

Posted

I have a 2013 GMC Sierra.  For the past several months I have had the same intermittent problem with it not wanting to start.  Both are original keys.  At first I thought it was an issue with 1 of the keys that maybe the chip inside was failing, but after talking to the service guys at the dealership they said there is no chip, it's just a key.  I started using the 2nd key and didn't have any more problems...until last night.  It didn't start again.  I thought maybe the starter was going bad so I banged on it but that didn't help.  Then I noticed the symbol and message on the dash about checking the theft deterrent system.  I disconnected the battery for a couple minutes and then reconnected it to see if that would reboot everything.  It didn't help.  I tried using the remote start but still nothing.  After dozens of tries locking and unlocking the truck and trying to start it, it finally started (about a half hour after it first wouldn't).  Each time it wouldn't start over the past several months it would take 20 to 30 minutes and dozens of tries before it would finally start.  I could take it in to the dealer but I'm afraid they will find nothing wrong as long as the problem is not occurring.  Any real answers would be greatly appreciated.

  • 4 weeks later...
Posted

i have had this issue random no start,went over all grounds,grounds under front dash panel,had GM dealer reprogram both fobs and three keys,worked good for three weeks then out of no where it would not start after sitting for less then three minutes,stopped for gas this morning,would not start after filling tank,remote start would work till putting key in and turning on stalled.got out of truck hit lock three times and unlosk three times on remote and it started.WTF.contacted GM looking into it.They have a problem with 14 thru17 with this happening.they need to fix this problem,they built the thing.

  • 6 months later...
  • 3 weeks later...
Posted

Dealership had to reprogram both keys. It was almost as if the truck just deleted them. I don't have the original paperwork as I traded the truck about two years ago so I don't know exactly what they put on there.

  • 1 year later...
Posted

Still no fix for this? Com'on GM. Makes me not want to upgrade to a new GM truck when I trade this one in soon...

 

Having same issues with my '15 Silverado, but the most worrisome aren't listed enough so I'm emphasizing them... The damn truck dies (briefly) running down the highway when I use my turn signal and dies or almost dies when I make slow moving turns (i.e. in parking lots, driveways, etc). Also notice headlights dim a lot when experiencing this behavior.

 

Been struggling with this for the better part of a year. Very intermittent, sometimes I've gone months with no issue, sometimes, it happens multiple times in one day.

 

For me, the most likely explanation seems to be some kind of wiring issue or battery terminal connections. The last 3 or 4 times I have had immediate success after popping the hood, knocking hard a few times on the plastic housing mounted on top of my battery, then slamming my hood shut. As a bonus, it's also a nice way to relieve some of the frustration from the situation. Hopefully this helps save someone from wasting money on a new battery or tow!

  • 3 months later...
Posted

New to the forum. Thanks for sharing all your stories! We bought this last year and this has occurred about two dozen times. Haven't panicked yet, as it always starts after a second attempt. Sometimes the radio is on a null station, sometimes the clock loses time. Just that hesitation to start like a dead battery, and all the dealership could do was sell us a new battery. Okay, like many have said, and we did at the time, a new battery is better than an aging one...shrug. But no change in this symptoms. We haven't been stuck by it, and have taken it to Florida and the Poconos numerous times. The only aftermarket wiring I can find was the hookup for a sat phone or something that's not in there, just the dock in the center console, so it's not pulling any current, just created a leak in the third brake light housing through which they ran the antenna wire! I like the corroded wiring at the starter motor in an earlier post; I'll look there. But why do current-pulling issues work backward to the system that verifies the key is correct? Once it gets that signal shouldn't it be satisfied and get outta the way?

  • 10 months later...
Posted

I have a 2015 Chevrolet Silverado and my theft deterrent light comes on, no power at all. If I move my driver seat , my power comes on and I'm able to start the truck, but will loose power while slowly turning. Not throwing any codes.

  • 1 month later...
Posted

I'm having this issue now, both remote start and key in the ignition, replaced starter, battery,alternator, batter ground cables and short positive the dealer threw the last 2 parts at it for 600$, goes in again next week, anyone have an idea???

  • 2 years later...
Posted
On 9/29/2023 at 10:08 AM, Tyson Lotz said:

I'm having this issue now, both remote start and key in the ignition, replaced starter, battery,alternator, batter ground cables and short positive the dealer threw the last 2 parts at it for 600$, goes in again next week, anyone have an idea???

Did you figure it out? I'm in the same spot.

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

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...