From a recent Lyriq TSB, we finally got confirmation from GM that the infotainment updates are incremental, meaning that each software update must be applied on top of one another.

GM has also fixed the delivery issue where SPS2 prematurely sends out Android 14 to infotainment unit with SQBR5-180. Now SPS2 properly detects infotainment version, and sends out the corresponding package. In order to get to Android from SQBR5-180, one needs to run USB update twice. However, we do not have confirmation that the delivery issue has been fixed for ZDX/Prologue as well, so do not take the leap unless your car has SQBR5-250. The TSB confirmed that updating from SQBR5-250 is safe.

The TSB also mention that bricked infotainment unit can be restored, but one needs to contact Techline Connect to get the logistics set up from the server.

I hope this ends the fiasco once and for all. It no doubt highlights the silo culture of GM, and is entirely GM's fault. But at the end of the day, Honda/Acura should take the lead and give dealerships and owners clear guidelines.

https://static.nhtsa.gov/odi/tsbs/20...26864-0001.pdf

 

So, GM is bricking cars because they don't know how to properly patch software. Wow.

 

Amazing, right? Their oversight did not brick that many GM EVs because there was a recall OTA on Lyriq that brought most cars up to SQBR5-250, and most Equinox/Optiq already had 250 from the factory.

 

Is there a way for us to know if our own car has that already? (don't know what these SQBR's are).

 

Just wait, Acura/American Honda furloughed almost the entire tech development dept. This with a loads of bugs/glitches in the new ADX.

 

It's in the Settings>>System>>About pathway.

 

Wait, did they REALLY get rid of most of the entire tech development department? Ugh!!!!

 

Yup!!

This crosses all Acura/American Honda models. Not just the ZDX.

 

I'm on Android 12, security patch from 1/5/2024. SQBR5-180.2 38.

I'm eyeing a particular Lyric. I own the ZDX outright. Looks like it would cost me $35,000 to trade it in and buy the Lyric. Ugh.

 

Perplexity tells me the furloughs are just a rumor and there is no supporting evidence for this.

 

The 1st VWP will update you to the SQBR5-250 version like mine. Still on Android 12.

I'm giving Acura 1 last chance to fix the bugs/glitches next week. That attempt will put me over the 30 days in the shop threshold to trigger the CA Lemon Law After that I'm filing for a CA Lemon Law refund and getting the BMW iX.

 

3 different Acura service managers all state it is no rumor.

 

Back to the issue with the bricking. Does this apply to TSB 25-033 (Radio Control Module) or 25-034 (Telematics Control Module Software). Thanks. Seems like I would need to get updated from 180 to 250 first, then get the final update, to be safe.

EDIT -- answered above, this applies to VWP.

 

Good Luck!!!

 

I wouldn't be surprised if this is true. ASIMO OS is still a vaporware. The only time it was shown, it was glitchy as hell. RSX is launching in 6~9 months, and no live demo yet? BMW demoed iDrive X well over a year ahead before launch.

Acura has been eerily silent for a pivotal product - something must not be right.

 

I just hope they get this figured out, i was on Android 12, security patch from 1/5/2024. SQBR5-180.2 38 and of course they bricked it and couldn't figure it out, so they ordered a radio and I'm now waiting two weeks already with this:

 

Good luck!!!

With the number of bricked infotainment systems, the backlog is quite long. A nearby dealer has a bricked ZDX in the back of the shop for 3 months so far waiting for a new system.

 

I kind of figured as much, when it came up as back ordered and no date. Is there really no way to bring this thing back to life??

 

Supposedly an Acura tech can use GM Connect to rollback the update and restore the functionality. This will work on any GM bricked system. The software is the same and in theory, it should also work on the ZDX.

 

This is making me really question if I go through with this on Tuesday morning. I'm on 180.2 as well. Do I want to trust that the Acura tech knows how to do this? Even if I tell him about this issue?

 

I have an appointment on Wednesday to get the last update and another attempt at a bug/glitch fix. Since my ZDX is on build 250 already, I'm willing to risk it. The previous VWP update I received in early September corrected a few bugs/glitches(brakes slamming on in the rain in reverse, rear hatch randomly opening, less violent braking with the adaptive cruise control). Most likely the camera/sensor calibration fixed the random braking when passing a semi on the freeway after my unsuccessful attempt to push a Ram p/u into a traffic circle.

If it fails, I'll be at the courthouse the following Monday to file a CA Lemon Law case, since I'll be over the 30 days in the shop trigger on Wednesday. .

As to trusting an Acura tech to perform work on a ZDX...

GOOD LUCK!!!

 

Are there multiple VWPs? We got one quite a while ago when there was a recall for an issue with the backup camera. It seems that VWP mostly solved the issue were the car would slam the breaks when packing out of our driveway. So we got this mostly fixed due to the recall and not because of the backup issue which the dealer could not reproduce.

 

I would point the dealership to the Lyriq TSB, and ask them to bring the TSB to the attention of Honda Techline, so the HQ people can contact their counterpart at GM (Techline Connect - confusing, right?) and see if they can get the procedure to restore infotainment.

 

I had to move a large chunk of lava rock in my landscaping to be able to back out of my driveway before the first VWP update. In the rain, the brakes would slam on no matter what I tried.

The first VWP I received in Sept 2025, this one limited the over sensitive braking issue.

 

Yeah i am being told First week of February but not holding my breath

 

Let's hope GM engineering comes to sense, and starts working with the supply chain to provide refurbished infotainment unit recycled from those bricked units.

 

Engineering? They might get 500 Bravo points worth $5 or a small Starbucks latte. Not worth talking to the supply chain people who just work 9 to 5 and couldn't care less...

 

Having two ZDXs lacking software support from Acura OTA/dealers and the Lyriq receiving regular updates I tried my hand at ACDelco TDS and SPS2. I updated almost all the modules in both cars including the A11 Radio module, so it looks like the SPS2 issues may have been resolved. I was starting with SQBR5-180, ran the full update process the first time (USB, Programming 1, Programming 2); the USB files were with 85xxxxxx.mnf so that gave me the confidence to proceed since the AA14 files were 86xxxxxx.mnf. That brought it to SQBR5-250, then I ran the full update process again with second round USB download files including 86xxxxxx.mnf. Then after the final programming steps the system was on AA14. I also updated the Image Processing Module which made me a bit nervous since it took about hour and fifteen minutes. The update time remaining went to 0 and it sat for about 25 minutes seemingly doing nothing then it suddenly finished up, whew! Fortunately I had a battery maintainer otherwise I really would have been sweating, I wouldn't attempt this without one. When I was first messing around in SPS2 I had an extra fully charged 12V battery hooked up to the car battery and the voltage dropped below 12 volts in 30-40 mins. Fingers crossed, looking forward to less bugs/errors, I've already noticed smoother starts/stops and power delivery making the vehicle feeling more refined.

 

I'm think they made progress also (fingers crossed) i have noticed the same the Lyriq is not having these issue. If your near NY you want to unbrick mine from that mess

 

Yikes, good luck! I wouldn't know where to start, but it seems a willing tech and a long call to the TDS Techline could get it sorted out. It's a shame we have to deal with issues like this, the car is a great piece of hardware that could be a great car with better software and service support.

 

Glad to hear your success story, and thanks a lot for sharing the experience with updating IPM. I never realized that updating IPM would take this long. Did you see difference in calibration numbers for both K124AA/AB, or just K124AA?

Also surprised to hear that the voltage drops that much with a 12V piggybacked. What is the size of that 12V battery?

 

Acura Tech support hasn't authorized the GM rollback to unbrick the ZDX's. Supposedly, Acura is working on a patch to make the rollback themselves, since the replacement infotainment systems are rolling out so slowly.

 

Hopefully so and slooooowly is more accurate. Yeah the hotline was pretty quick to authorize the replacement they said. Guess ill have to go talk the tech again tired of waiting. thanks

 

Dare I say it I used an aftermarket J2534 pass through box, so it may be slower than the MDI. Interestingly I could connect to almost all the modules with my J2534's standard driver except the BCM and IPM modules, but my J2534 also had a "DOIP" driver that was able to connect and program them. I didn't use any ethernet cables or adapters, so who knows what the difference was. As for the IPM it programmed both K124AA and AB, I didn't take any screen shots but I recall three tabs of calibration files and probably I'd guess around 2/3's of the selected files were different than the current ones.

The piggyback 12V battery I used before I got the maintainer was a relatively new 26R. I suppose my car's battery could have been weak, I'll keep an eye on it. I had some limited seat time today but I felt like the Super Cruise steering was smoother and more stable. I'm also hoping there are significant improvements to the forward collision mitigation. I had enough instances of unexpected brake events in stop and go driving and parking lot maneuvering that I turned it off. I turned it (and the reverse collision mitigation) back on, so we'll see.

 

Well this radio drama seems to be over. Got the call from the dealer the radio was released 3/8. When i took the the car in the techline made my car a test subject. They told the dealer to try the rollback first and almost a whole day later now the radio works and is updated to android 14. So it seems they could have solved this a lot sooner, but at least all of us waiting months should now have a working radio. I'm glad the rollback worked, its quite a bit of work to replace the actual radio.