Jump to content

2014 Silverado Crew Cab Driver Rear Door Lock Not Working

awright2009

By awright2009
in Troubleshooting & Recalls

 Share

Recommended Posts

awright2009 Enthusiast

awright2009

Posted
Posted

So coming back from the gym I unlocked the two or so times to open all the doors and the driver side rear door did not unlock. Started messing with it today, if I roll down the window and open it from inside, the door will unlock. And while hitting the lock / unlock buttons it will not move up or down, but I do hear a electronic actuator moving inside the door from somewhere below the lock. I'm thinking the actuator arm or something similar came loose some how, but am not sure.

 

Anyone have a similar issue? Any good videos / instructions on pulling off the door panel and taking a look? Maybe the location of the fuse for the door locks?

spenpet Enthusiast

spenpet

Posted
Posted

Dude...I  have 3 out of my 4 doors gone out...it is ridiculous!  it started with the front passenger, then the rear passenger, now the driver rear...I have heard you can get an actuator motor and repair the actuator for $30 each or so...This truck has had more issues than any of my previous chevys...

davester Senior Enthusiast

davester

Posted
Posted

For my truck, the rod going to the interior lock/unlock manual lever was sticking a bit in the plastic guides, so when I hit the lock power button, it would briefly lock, then unlock right after that.  I fixed it by greasing the guides and making sure the rod could go back and forth easily, and it's worked fine for me since then.

Sirlukeman New Member

Sirlukeman

Posted
Posted

Almost the same thing just happened to me.  My rear left door won't unlock or lock with the key fob or interior lock switches.  I have to reach back and pull the interior door handle to open the door and have to manually lock the door before I use the key fob to lock the rest of the doors.  The difference is I hear no actuator working at all.  I did find a you tube video that looked helpful.  At least it shows the door opened up and the lock assembly removal process.  Hope it helps!

 

https://www.youtube.com/watch?v=3VbMpuJIW9A&list=PLEFoHD2HG7DyrazWpLssTHhwn2C5lHJ4-&index=7&t=0s

 

Newton86 Enthusiast

Newton86

Posted
Posted

Had the same problem with my truck. It was just the lock actuator. Replaced it and had no problems since then. 

  • 2 weeks later...
  • 11 months later...
Paul J New Member

Paul J

Posted
Posted

2014 Silverado, Are the front and rear door actuators the same?  Drivers side rear door actuator isn't working with fob or switch on door.

  • 1 month later...
awright2009 Enthusiast

awright2009

Posted
  • Author
Posted

So I have the truck at the dealer right now for the condenser and told them to look at this lock finally. They said about $400 something and it was the latch.

 

Think this is what they will do:

https://www.youtube.com/watch?v=nBKsL6o0qc4

 

At first I was like $400, that's too much, but after watching the above video, and seeing the part is like $120, I was like alright, let them do it

 

I'll get the part numbers when they wrap it up

  • 3 years later...

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

    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?
    • Snowcamo
      Replacement Radiator

      By Snowcamo · Posted

      Rockauto bud. I pass local stores for parts.   Findya something online. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...