Jump to content

Recommended Posts

Posted

So, got off work, hopped into the truck, started up... no radio, no audio of any kind. Tried the "hold end call on steering wheel for ten seconds", no luck. Called dealer service department, guy said "Huh, yeah. Disconnect negative terminal of the battery for 5 minutes, should fix it." What he didn't tell me was that when you do that, and then reconnect the battery, the horn alarm starts going off. WFT?? Does this happen enough that the service department tells you to "disconnect the battery for 5 minutes", even if you don't carry tools in the truck?

 

Got the alarm to shut off. However, my question is how often does the truck's audio (radio, phone, alerts, etc) just randomly shut off? Tried to call the wife... nope!! No audio at all.

 

Yes, I realize the truck is still under warranty, however, the engine issues seem to take priority.

Posted

My truck did this one time. I was able to correct the issue by turning off the truck and letting it sit for 10 minutes. Restarted the truck and have not had any more issues.

  • Like 1
Posted (edited)

Mine did this once. Went to dealer and they fixed. Had to reboot the radio system.   According to the tech that did it, common issue with the current system (took about 15 min). 

 

A friend said Onstar fixed his.  I tired but the Onstar tech did not speaka the good English and I had to hang up because I could not understand him. Very frustrating, he was getting po'd at me because I kept telling him I can not understand you!

Edited by Z45
Posted
24 minutes ago, bobder41 said:

My truck did this one time. I was able to correct the issue by turning off the truck and letting it sit for 10 minutes. Restarted the truck and have not had any more issues.

This was the third time for me. First two the dealer "supposedly" took care of it by reprograming modules. Now I wonder if I will be left hanging with no connectivity with an $85K truck.

 

🤔😬😬

 

Posted

This happened to me for the first time yesterday.  No sounds at all, no radio, no door chimes, no turn signal beeping, etc.  The next time I started it back up all was fine.  I'm not even sure if it sat 10 minutes between issues and restart.  I didn't panic or worry because I've heard this was a known issue.  I suspect something in the computer system isn't launching or starting at start up as it should.

  • Like 1
Posted (edited)

Might need a new radio.

 

There are specific steps a dealer must do to get one shipped in.  

 

Of course it's also possible the steps might correct the problem

 

Required Information for Restricted IOK Radios – TechLink

 

Required Information for Restricted IOK Radios

May 13, 2025

The infotainment system (RPO IOK) on 2022-2025 Silverado, Tahoe, Suburban, Sierra, Yukon, HUMMER EV; 2024-2025 Corvette, Silverado HD and Sierra HD models is on restriction. (Fig. 3) If the radio must be replaced, there are several procedures that must be followed to order a new radio.

 

F03-Radio-3.pngFig. 3

 

The IOK Radio part numbers 85086705 and 85086710 have been put on restriction based on #PIC6602. A PQC case will need to be created prior to ordering the part through Specmo. The PQC phone number is 866-654-7654.

Required Information

PQC will ask for the following information when creating the case:

  1. What is the message displayed on the radio screen? See #PIT6209.
  2. Did the technician confirm the radio software is up to date following:
  • Bulletin #24-NA-261 – 2022-2024 Full-Size Trucks and SUVs
  • Bulletin #24-NA-276 – 2025 Full-Size Trucks
  • Bulletin #24-NA-168 – 2022-2024 HUMMER EV
  • Bulletin #25-NA-098 – 2024-2025 Corvette and 2025 HUMMER EV
  1. If the radio is not at the latest software level, did the technician update the radio, clear all codes and recheck for the concern?
  2. If concerns continue, did the technician disconnect, inspect and reconnect all related connections, clear any codes and recheck for the concern?
  3. What is the current as-built version for the radio?

Once the PQC case is created and the part is released, dealerships can reach out to Specmo to order the radio. Specmo is the only approved supplier of the part. They will verify the PQC case and verify the part can be shipped.

Refer to #PIC6602 for additional information.

Edited by redwngr
  • Thanks 1
Posted
20 hours ago, redwngr said:

Might need a new radio.

 

There are specific steps a dealer must do to get one shipped in.  

 

Of course it's also possible the steps might correct the problem

 

Required Information for Restricted IOK Radios – TechLink

 

 

Thanks for the info! 👍 You gave me the first breadcrumb to follow. LOL

 

While searching for #PIC6602, I also found #PIT6101Q which says

image.thumb.png.13da9d63bea00f4490a8c8fb5c879bcc.png

So, I'm going to see if I can check the software version or I might have a bad/intermittent amplifier.

Posted (edited)

You're under warranty.

Take it in and let them provide the service you already paid for. 

 

If it needs a radio, they will have to go thru the steps anyway.

 

 

 

Edited by redwngr
  • 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
  • Latest Articles

  • Posts

    • 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? 
    • 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. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • 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.
    • 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...