Jump to content

Recommended Posts

Posted

A friend of mine bought a 2025 Ff250 with the 7.3 Godzilla, put 2k miles on it and it started making a grinding sound. Took it to the dealer and they said the engine is bad and so they replaced it.  A month later he gets it back and at 500 miles the same sound appears.  Dealer said again, engine shot needs replaced so they did. From the paper work, it shows that the issue was the crank had way to much end play on both engines.  Crazy and so he traded it for another new F250. He just hopes this one is good, not to mention he upgraded from a custom to a Lariat.  It had adjustable peddles. Why did GM get rid of that feature?  It's nice, especially if you have a short wife. LOL

  • Like 1
Posted
1 hour ago, dieselfan1 said:

I don't want a new motor. Too much hassle. I have 52,000 miles on it.  Im pretty sure it was going to pass the "test".

Runs fine. Id rather have the 150k warranty. 

Just remember that the extended warranty only applies if the bottom end fails in the area specified by the recall.

Posted (edited)
14 hours ago, MrLeadFoot said:

Just remember that the extended warranty only applies if the bottom end fails in the area specified by the recall.

The truck may catch in fire if that happens. Know what I mean?

Gap covered. 

Edited by dieselfan1
Posted
1 hour ago, dieselfan1 said:

The truck may catch in fire if that happens. Know what I mean?

Gap covered. 

I hear ya! There are so many fires going on these days in your neck of the woods. 😜

Posted

One of our local dealers claimed they would take recalled L87 trucks on trade with no change in value.  When we started looking into trading one of our recalled vehicles for a new 2025, someone we know with another GM dealer told us to wait because they've had several 2025 6.2 trucks blow in the last few weeks. Knowing that, we hit the brakes on trading for a new one.  If the 2025 motors are still bad, then I doubt anything changes for 2026 either.  Has anyone here tried to trade an under recall 6.2 vehicle to another brand dealership?  I've heard mixed signals on whether anyone will even take one on trade.   

Posted
10 hours ago, tjonesdfw said:

One of our local dealers claimed they would take recalled L87 trucks on trade with no change in value.  When we started looking into trading one of our recalled vehicles for a new 2025, someone we know with another GM dealer told us to wait because they've had several 2025 6.2 trucks blow in the last few weeks. Knowing that, we hit the brakes on trading for a new one.  If the 2025 motors are still bad, then I doubt anything changes for 2026 either.  Has anyone here tried to trade an under recall 6.2 vehicle to another brand dealership?  I've heard mixed signals on whether anyone will even take one on trade.   

My dealer said he couldn't take mine on trade until the recall was taken care of.

I was looking at a 6.6 Gasser 3500.

  • Sad 1
Posted (edited)
17 hours ago, dieselfan1 said:

My dealer said he couldn't take mine on trade until the recall was taken care of.

I was looking at a 6.6 Gasser 3500.

They can easily prioritize performing the recall on their new and used inventory stock, and this is a great opprtunity for them to build loyalty with customers like you. This doesn't sound like a good dealership, to me. Go try another one, and see what they say.

Edited by MrLeadFoot
Posted
On 7/8/2025 at 1:26 PM, MrLeadFoot said:

They can easily prioritize performing the recall on their new and used inventory stock, and this is a great opprtunity for them to build loyalty with customers like you. This doesn't sound like a good dealership, to me. Go try another one, and see what they say.

I wondered if that's why they are so eager to trade at some dealers... I guess once its in inventory, a truck gets priority for  the recall regardless of whether the VIN had come up for a final letter yet?  

Posted
43 minutes ago, tjonesdfw said:

I wondered if that's why they are so eager to trade at some dealers... I guess once its in inventory, a truck gets priority for  the recall regardless of whether the VIN had come up for a final letter yet?  

Not so sure its done by vin# mine is one of the first on the list in 21. Still not gotten anything but the 1st letter!

  • Sad 1
Posted

Just updating from the field a bit.  We've done 3 or 4 customer vehicles in the past couple weeks that got letters.  So far all passed.  Some with over 50,000mi too.  One truck got an engine at 79,000mi on a road trip the year prior on its original engine, came in with 99k on the truck, so about 20,000mi on the replacment engine.  The replacement engine was subject to the recall and passed.  

  • Like 1
Posted (edited)
On 7/14/2025 at 9:17 AM, tjonesdfw said:

I wondered if that's why they are so eager to trade at some dealers... I guess once its in inventory, a truck gets priority for  the recall regardless of whether the VIN had come up for a final letter yet?  

All recalls have to be dealt with before a vehicle is sold. I dont think the dealership wants someone willing to buy a car or truck, but they cant take delivery of it until the recall is done.

 

'Sorry we're waiting for parts, can you pick it up two weeks from tomorrow?'

Edited by revrnd
Posted
1 hour ago, newdude said:

Just updating from the field a bit.  We've done 3 or 4 customer vehicles in the past couple weeks that got letters.  So far all passed.  Some with over 50,000mi too.  One truck got an engine at 79,000mi on a road trip the year prior on its original engine, came in with 99k on the truck, so about 20,000mi on the replacment engine.  The replacement engine was subject to the recall and passed.  

Thanks for the update. Out of curiosity, did that truck that got a repacement engine at 79,000 get the new engine due to the current problem, or was it for some other reason?

Posted
35 minutes ago, MrLeadFoot said:

Thanks for the update. Out of curiosity, did that truck that got a repacement engine at 79,000 get the new engine due to the current problem, or was it for some other reason?

 

 

The engine recall concern was why it got one, but it happened before the recall went live.  The crazy part was their other 6.2 got an engine at 13,000mi.  While it was getting replaced, they took this higher mileage one on their road trip and it blew on the road trip.

  • Sad 2
Posted (edited)
6 hours ago, newdude said:

 

 

The engine recall concern was why it got one, but it happened before the recall went live.  The crazy part was their other 6.2 got an engine at 13,000mi.  While it was getting replaced, they took this higher mileage one on their road trip and it blew on the road trip.

Holy crap, so they got TWO engines in TWO different vehicles for the same problem as the recall? Wow, I feel sorry for them (for their collective headaches).

Edited by MrLeadFoot
  • Thanks 1

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,803 Guests (See full list)


  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...