Sync3 Udate Fails Due to Error in .xml File

Thanks, I FINISHED Step 2 and it NEVER did anything in Step 3. The screen was black before Step 3 started. So, in my opinion, it did NOT reach Step 3, since it never entered it.

However, I really think the APIM itself is bricked. I cannot get it to read the update USB more than about 5-10 secs. It does not respond to my music USB at all. It is not giving me any radio output. And, my cell phone is unable to connect to SYNC. This all points to the APIM in my, admittedly uneducated, opinion, not just the screen. Shouldn’t I be able to connect using blutooth to the APIM if it was working, regardless of the screen status? Wouldn’t Audio come through despite the screen being off?

And, when you say, “The unit is easily recoverable.” What do you mean? Are you talking about a screen or the APIM? I’ve decided to get a new APIM and I will mount this screen on it. Are you saying that will not work? Do you really think, after what I described here, that the screen itself is at fault?

I don’t really want to go back to Sync2, because Sync3 gives me so much more with Android Auto.

This unit was sent to me with 3.423088 installed. Could it be possible that this firmware makes the update “see it” as a post MY20 unit?

  • Jack