MMI Update - Dealer can't get it to work. Want to charge me to replace components!
#12
Re: That is the error screen I get on both CDs!
Yes to - MMI version 2750.
I am working on a solution but will wait for the second CD which is in the mail. I don't think it is a hardware problem but rather a software block put in place by Audi to protect the MMI from incorrect installation.
I should say that the Dealer was trying to do the update for me, a promise made to me due to phone problems, but they ran into the same problems. They were in touch with Audi but, so far, have not offered any solution. I'm hoping the new CD will correct the problem. I will wait and see.
I am working on a solution but will wait for the second CD which is in the mail. I don't think it is a hardware problem but rather a software block put in place by Audi to protect the MMI from incorrect installation.
I should say that the Dealer was trying to do the update for me, a promise made to me due to phone problems, but they ran into the same problems. They were in touch with Audi but, so far, have not offered any solution. I'm hoping the new CD will correct the problem. I will wait and see.
#14
Audiworld Junior Member
Thread Starter
Join Date: Jan 2007
Posts: 22
Likes: 0
Received 0 Likes
on
0 Posts
I debuged the Meta file on the CDs and believe I found the issue.
The Meta file tells the system which versions it can upgrade the EEPROM from. The EEPROM does not relate to the MMI version. It appears to be some base file for the headunit. There are alot of versions listed in the file. Our version (1.1.18.25.7.27.11.2) shows in both files shows a CRC of 0xbe87c369. However, our cars have a CRC of 0x61435738. I believe that a mistake was made in the file for our particular version. This file is changable and I could correct the CRC to match our cars so the install would continue but, I'm not quite that brave yet. I'm going to the dealer to compare the file with several of their cars on the lot to see what other versions of the EEPROM show before I make a decision to mess with the file. The problem is definitely with the Headunit. A new headunit with a later or older EEPROM version would work. I was able to change the Meta file to fool it into thinking the headunit did not need an update. When I ran the CD in the car, it did skip the headunit and showed the other components were ready to update. Send me an email and I'll give you more details and keep you up to date with what I learn.
Thread
Thread Starter
Forum
Replies
Last Post
pierreb
A6 / S6 (C6 Platform) Discussion
4
02-14-2007 03:18 PM
Hugh
A4 (B5 Platform) Discussion
5
07-02-1999 07:18 AM