Jump to content

Advice Needed - ‘08 Sierra

Z71JR
 Share

Recommended Posts

Z71JR New Member

Z71JR

Posted
Posted (edited)

Wanted to get some advice for the current situation I’m in. I have an ‘08 Sierra Z71 with 200k miles that started having a lifter problem recently and knocking badly. It also needs a rear main seal replacement and can barely keep any oil. The shop determined it would make more sense to do a motor replacement, considering labor costs to rebuild and not knowing the extend of damage. 
 

The quote to do the motor swap is about 10k for a brand new re-man with a 3 year warranty. I have looked into other options like a low mileage junk yard motor and that was about 2k plus labor. 
 

It is in good shape on the interior, but feels difficult to pull the trigger on the full swap knowing the trucks value and I will likely have transmission coming as well. Should I look into getting a rebuild and selling? Selling as is and buying another used truck with lower miles? 

Edited by Z71JR
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

It's 6 of one, half dozen of the other in this situation. A used motor is way cheaper than a reman and is likely the route I'd take if I was keeping the truck.

 

If you sell the truck now, it's worth way less than half of what it would be if it was running properly. So you need to take that into account. Even with a clean body I'd only pay a couple grand for a truck with that many miles that needs an engine. Because in the end when I flipped it, I'd only make a few grand for all the work involved.

 

If you buy another truck you could always be stuck with repairs soon after, so it's tough to say what is the best thing to do.

bubbanbrenda Enthusiast

bubbanbrenda

Posted
Posted

It would depend on what shape the rest of it is in. I had an ‘08 Z-71 Sierra that runs great but really bad rusty. I chose to sell it as is and use the money to buy a ’14 Silverado instead of spending the money to fix the rust. 2k plus labor to replace it with a used one isn’t bad. I would replace the rear main and oil pump and probably delete the AFM before putting it in if I was going to keep it. 

KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I have an 02 avalanche that’s very clean. I use it as personal going to town vehicle putting about 7K miles a year on it. I would rebuild mine with mild modifications. In your case with a cylinder deactivation engine the mods would be eliminating that. Buying a used GM after 06 with the cylinder deactivation makes it a crapshoot. Those engines are so dependent on good maintenance for longevity more so than prior years. Used engines for me after 06 I’d be very Leary. 

  • Like 1
Z71JR New Member

Z71JR

Posted
  • Author
Posted
On 12/3/2023 at 9:31 PM, bubbanbrenda said:

It would depend on what shape the rest of it is in. I had an ‘08 Z-71 Sierra that runs great but really bad rusty. I chose to sell it as is and use the money to buy a ’14 Silverado instead of spending the money to fix the rust. 2k plus labor to replace it with a used one isn’t bad. I would replace the rear main and oil pump and probably delete the AFM before putting it in if I was going to keep it. 

I was told by the shop they would delete the AFM for the new motor. IS that possible with junkyard motor? I was under the impression it would require some different parts. 

bubbanbrenda Enthusiast

bubbanbrenda

Posted
Posted

That is correct a proper delete would require replacing the cam and lifters and valley cover just to name a few, if the have the correct software and interface they can turn it off.

Z71JR New Member

Z71JR

Posted
  • Author
Posted
1 hour ago, bubbanbrenda said:

That is correct a proper delete would require replacing the cam and lifters and valley cover just to name a few, if the have the correct software and interface they can turn it off.

 

Understood, thanks for the info. Does 10k for the new motor and turning off AFM sound a little steep? I have received other quotes for more. 

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...