I recently installed an AVIC-W8500NEX receiver in my 2015 Toyota Highlander.  Most of the time it functions normally except every 30-90 minutes it will spontaneously shut down and reboot.  I have checked all wiring, updated the firmware to the latest version (1.03) and reset the microprocessor, all to no avail.  Anyone else have this problem?  Pioneer tech support was essentially useless.  They believe the unit is defective and that I need to exchange it (what a nightmare it will be to uninstall everything - still waiting to hear from the vendor).

The vendor kindly replaced the head unit but the problem recurred within a short time.  Very frustrating.

A you using Carplay / Wireless Carplay ? I've noticed since CP was released, it has done that to to my Avics from time2time

You're not alone. I had a 8200nex for 3 years and loved it. Moved it to my wife's van. Bought the 8500nex in mid December. Within 2 weeks it rebooted 5 times. Contacted Pioneer and they said to return it and replace it because it was likely to fail soon. Checked all wiring connections and had to reflash Maestro with replacement. The second unit seemed to be fine for the past 2 weeks. Then after 2 hours into a 3 hour roadtrip it rebooted. Was using Android Auto wirelessly connected to my Samsung S10E and playing Sirius XM. After reboot seemed fine. 4 days later (today) after just 15 minutes of driving only streaming Pandora (no Android Auto) it rebooted. So no common pattern yet. I have about a week left to be able to return this to Bestbuy... but I really love the unit. This is sad. Will call pioneer first though tomorrow. 

Yeah my 2 month old 8500 has rebooted 3 times so far. Hard to believe for "flagship" model. I also have a Maestro T2.

.

dido on the above, I've had mine for about about 3 months  and thought it was an anomaly until recently.  We are now averaging a reboot at least once a trip.  I'm using the maestro T02 interface as well.  Hopefully others will report in as well so we can isolate if it's a Pioneer or Maestro bug.

Any more feedback on this issue?  Also, can you all post up what vehicle you are using?  This seems to be happening more frequently in Toyota's from what I've see online.  We have this unit  in our 2015 Highlander and it just did one of these reboots for the first time.  Also using Maestro.

The more concerning part... the stock unit was doing this a BUNCH hence why we replaced it with the 8500.

Still seeing occasional reboots with no identifiable pattern.  I too am using the Maestro ADS-MRR with the T02 harness.  I am also using CarPlay so that may be a factor.  I'll be on the road for about 12 hours this weekend, so it will be interesting to see how it goes.

On 2/28/2020 at 4:04 PM, mdgeek said:

Still seeing occasional reboots with no identifiable pattern.  I too am using the Maestro ADS-MRR with the T02 harness.  I am also using CarPlay so that may be a factor.  I'll be on the road for about 12 hours this weekend, so it will be interesting to see how it goes.

What make vehicle are you in?

Ok, after a 12-hour roundtrip in my 2015 Highlander:

• Outbound leg, using CarPlay navigation + TuneIn app.
• First 3 hours, no problem.
• Stopped for gas.
• Reboot within 15 minutes after resuming trip.
• A second reboot within 5 minutes.
• No further reboots for remainder of outbound leg.
• Return leg, using CarPlay navigation + Pandora app.
• Reboot within 1 hour.
• No further reboots for remainder of trip.

So, no real pattern that I can see.

On occasion when the head unit reboots, I catch a glimpse of an error message on the screen, but it never persists long enough to read it.  Earlier this week, the following message popped up without a reboot.  I suspect this is the message that is being displayed during the reboots.  This suggests the Maestro unit may be to blame (or perhaps the wiring harness).

I’m having this same issue in my 2017 Tacoma with the T02 harness. No detectable reboot pattern, but sometimes it is accompanied with a “this Maestro accessory not supported” error before it turns off. I have a AVH-W4500NEX.

problem is the RR not the radio. If you are having to much problems. remove the RR and test again.

So I reflashed the RR from 2.07 to 2.09 so we’ll see if that improves it. What do you mean it is the RR? Do you have experience with it?

I would just connect all the main power wire to the car instead of the rr.

Hey guys, unrelated but im stuck for weeks in this subject matter topic. http://avic411.com/index.php?/topic/83492-password-avh-reset/&page=6

Any help would appreciated.

@bonee if the issue is still occurring they advised I make a jumper from the accessory wire to the power wire into the RR effectively doing what you say to rule out issue with the RR. I will try that if I continue to have issues. 

On 4/10/2020 at 6:09 PM, Tiredhands said:

So I reflashed the RR from 2.07 to 2.09 so we’ll see if that improves it. What do you mean it is the RR? Do you have experience with it?

Let us know if this helps.  Not excited about pulling the unit out to reflash the module, but if it works it would be worth it.

Curious on a fix for this as I have it happening with an 8200NEX, installed in a 2010 Honda Odyssey. Did the reboot a few times on my wife's trip from Ann Arbor to NY. I have the Maestro SW ADS-MSW connected to this unit. 

For the poster with the Toyota. I've installed the 8100 and 8400NEX's in both my Lexus RX330's with Axxess TYTO-1, and Maestro SW ADS-MSW and haven't had this issue.

15 hours ago, spankedmonkey said:

Curious on a fix for this as I have it happening with an 8200NEX, installed in a 2010 Honda Odyssey. Did the reboot a few times on my wife's trip from Ann Arbor to NY. I have the Maestro SW ADS-MSW connected to this unit. 

For the poster with the Toyota. I've installed the 8100 and 8400NEX's in both my Lexus RX330's with Axxess TYTO-1, and Maestro SW ADS-MSW and haven't had this issue.

how are the power wires connected.

The power wires are connected as instructions would have it. However on the first install of the 8100NEX in the Lexus my GPS maps would flip up and down. So I had to go in and separate the grounds:

-Parking Brake on radio harness to body junction on right side kick panel

- TYTO-1 Black, and Black/White with radio harness Black to metal body on right side

- Maestro SW ADS-MSW Black ground to body junction left side kick panel

Problem solved! Not sure if this is the difference but I haven't had reboots on either Lexus installs.

5 hours ago, spankedmonkey said:

The power wires are connected as instructions would have it. However on the first install of the 8100NEX in the Lexus my GPS maps would flip up and down. So I had to go in and separate the grounds:

-Parking Brake on radio harness to body junction on right side kick panel

- TYTO-1 Black, and Black/White with radio harness Black to metal body on right side

- Maestro SW ADS-MSW Black ground to body junction left side kick panel

Problem solved! Not sure if this is the difference but I haven't had reboots on either Lexus installs.

i was talking about the 2010 Honda Odyssey

On the 2010 Honda Odyssey the power wires are connected as instructed with direct-connect harness, per 8200NEX and Maestro SW ADS-MSW manuals.

So the red Accessory wires from the Direct-Connect, 8200NEX, and Maestro connected together. Then the Yellow Direct-Connect 12-volt power to 8200NEX yellow. 

I haven't done the ground separations for this unit/vehicle.

Sorry, following up Again. Made a jumper from the black/red wire to the red wire from the radio and capped the end going Into the RR per Maestro support. This will isolate the issue if it’s actually maestro related or radio related. Pretty sure the power goes directly to the radio now and not though the maestro. We’ll see if this fixes it. 

On 5/3/2020 at 4:34 PM, Tiredhands said:

Sorry, following up Again. Made a jumper from the black/red wire to the red wire from the radio and capped the end going Into the RR per Maestro support. This will isolate the issue if it’s actually maestro related or radio related. Pretty sure the power goes directly to the radio now and not though the maestro. We’ll see if this fixes it. 

Any updates on whether or not this worked?