Jump to content

Changing the brakes on 2020 GMC Sierra 1500

Charles Busby
 Share

Recommended Posts

Gangly Senior Enthusiast

Gangly

Posted
Posted

There is a requirement to change the brake pad level sensor when you change the pads.  Also, there is a pressure buildup procedure to be done before you start up the engine, and if that is not completed the brake pad service performed will throw codes.

 

"-With the engine OFF, gradually apply the brake pedal to approximately 2/3 of its travel distance for 45 seconds.

-Slowly release the brake pedal.

-Wait 15 seconds, then repeat steps 7–8 until a firm brake pedal is obtained."

 

This helps seat the pads and the piston allowing for proper pressure in the system.

  • Thanks 2
BIGDOGx Senior Enthusiast

BIGDOGx

Posted
Posted

Crazy, brakes on a 2020?? Hell i have over 7 years and close to 50k miles on my oem brakes now....

 

And for the love of god people, please stop buying that china powerstop junk, if you are not going to a big brake setup from Brembo or Wilwood you are wasting your time and money imo! Either spend the premium to get quality or just remain oem imo.

Peterr New Member

Peterr

Posted
Posted (edited)

The service manual directs you to disconnect the negative battery cable before servicing the brake pads. If you don't, by the time you turn the truck on, you'll get two codes: a brake control module code saying it lost hydraulic pressure, and another code telling the ECM to turn on the check engine light. You can clear these codes and restart the truck and it should be fine. The manual states that the brake system on the truck goes through automated self-tests and compressing the calipers with the battery connected messes with the computer. Has nothing the do with brand of brake pads or anything at all, just disconnect the battery for the brake job. At the end of the brake job, you can reconnect the battery terminal and pump the brake pedal before turning the ignition on. Then there's no lights.

Edited by Peterr
  • Like 1
  • Thanks 2
  • 6 months later...
onekama_mi Enthusiast

onekama_mi

Posted
Posted

I find it difficult to understand why GM chassis engineers didn't include a "service brake" option in the settings menu of the driver information center.  Other manufacturers do this and the system backs off the pistons at all four corners.  Throwing codes after a pad change is just bad design, or if you prefer, design for "un-serviceability".

  • 5 months later...
chovaz New Member

chovaz

Posted
Posted (edited)
On 4/22/2022 at 7:16 PM, onekama_mi said:

I find it difficult to understand why GM chassis engineers didn't include a "service brake" option in the settings menu of the driver information center.  Other manufacturers do this and the system backs off the pistons at all four corners.  Throwing codes after a pad change is just bad design, or if you prefer, design for "un-serviceability".

They did. Sort of (just not directly in the menu)

 

 

Edited by chovaz
  • 2 months later...
Bszko New Member

Bszko

Posted
Posted
On 12/20/2020 at 10:26 AM, RWTJR said:

I feel this is one of the biggest shortfall of forums. Too often people post their issues and never come back and share the solution.

So im here to hopefully help. I found this forum after I experienced the same issue after a brake and rotor change out at 50,000 miles. I put my emergency brake into service mode. Did the brake change out. Started my truck and the check engine, abs, trac control,  parking brake were on, as well as a warning for limp mode. So i unhooked my negative terminal for 45 mins, hooked it back up and everything cleares up and pad life indicator reset itself. 

SIDE NOTE: I have a 2022 Chevy trail boss LT. 

  • 2 weeks later...
Zach T. New Member

Zach T.

Posted
Posted

Found out the hard way, but there is a “brake service” mode you can use to change the rear pads. It electronically disengages the parking brake so you don’t have to spin the piston flush with the caliper. 


I removed the caliper completely because I couldn’t get the piston to recede. Lost all brake fluid to that caliper and now I’m waiting for a scan tool to clear codes just so I can bleed the brakes. I love the truck but it’s not easy to work on anything without getting error codes. 

  • 1 month later...
NAH New Member

NAH

Posted
Posted
On 12/3/2020 at 11:21 PM, Charles Busby said:

I changed the front pads and now I have a bunch of warning lights and messages like the speed being limited to 43 mph, traction control is off, abs light is on ect.... What do I need to do next?

I know this is old but just in case anyone else runs in to this problem here is the fix.

 

Put the truck in brake service mode. Do this by turning the ignition on (do not start), press and hold the brake pedal down, pres and hold the parking brake button for 10 seconds, release the brake pedal, release the parking brake button, then press the parking brake button again. You should get a brake like with a wrench on it of done correctly. 

 

Next you want to start the truck, and while in brake service mode, delete the codes. 

 

To exit brake service mode, turn the ignition on again, hold the brake pedal down, press and hold the parking brake button for 5 seconds. 

 

You should be good to go after this. 

 

 

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...