mmi updating issues....
#1
AudiWorld Member
Thread Starter
Join Date: Mar 2015
Location: Grand Rapids Michigan
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
mmi updating issues....
mmi has been on this screen for 45 min now.... i'm thinking somethings up. any advise on where to go from here?
#3
AudiWorld Member
Thread Starter
Join Date: Mar 2015
Location: Grand Rapids Michigan
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
ok... new problem. it was like this for over an hour.. i thought it was locked up. so i disconnected the battery because i couldnt get the mmi to restart. now it wont turn on...... it locked on this screen at about an hour into the update
#5
AudiWorld Super User
Wow, I sure hope I'm wrong but this sounds like a "bricked" control module. Were the discs true Audi originals purchased from an authorized Audi Dealer's service parts department?
The "MOST Ring" in the top right corner may lead somewhere. I have never updated my MMI. I posted the reasons why in a thread here that discusses the MMI update. There are several that you can find using the "search" function.
The "MOST Ring" in the top right corner may lead somewhere. I have never updated my MMI. I posted the reasons why in a thread here that discusses the MMI update. There are several that you can find using the "search" function.
#6
AudiWorld Member
Thread Starter
Join Date: Mar 2015
Location: Grand Rapids Michigan
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
the discs were purchased from another forum member, the dealership here in grand rapids told me my software was up to date and they didnt have anything newer, also that i didnt need to update to use the current map disc. my sw version was back at 0600
#7
AudiWorld Super User
VCDS scan it, including Optical Ring scan, and post it here.
By interrupting update (disconnecting battery) you probably bricked it. There may be a chance to save it by stating update from Bootloader. To do so you need access to Hidden Menu.
By interrupting update (disconnecting battery) you probably bricked it. There may be a chance to save it by stating update from Bootloader. To do so you need access to Hidden Menu.
Trending Topics
#8
AudiWorld Super User
Which specific part # on disk?
As 0600 BTW, you might need other patches too (sub 1000 has some TSBs as I recall), but it still should have restarted with most functionality given prior user posts/input. And as a 2005, you should have found at least a v5 Nav disk in it; might have been later if a prior owner already replaced it. The minimum version in any MMI vehicle should be at least its model year as shipped from factory, unless somebody previously played games with the Nav disk. Net, what I am saying about the MMI is consistent w/ what I think dealer was telling you. Anything from v5 up works with later MMI updates, which in turn relate to getting AMI (aka the iPod/MP3 system) to work.
Last edited by MP4.2+6.0; 03-21-2015 at 03:11 PM.
#9
AudiWorld Member
Thread Starter
Join Date: Mar 2015
Location: Grand Rapids Michigan
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
I received the following,
33.6.0
• 4F0906961AB CD
46.1.0
• 4F0998961 CD1
• 4F0998961 CD2
the lock up happened about an hour into the first update disc i put in to get the sw to 33.6.0, once it locked i let it sit for 45min - an hour (not exactly sure, but at least 45 min)
my 7 and 8 yr old daughters are convinced the radio broke so it didnt have to here me sing any more :/ its turning into a rough day lol.
Jack88 is shipping me his VAG-CON so i can run the scans in a few days, till then it looks like i'll be singing without the background music
33.6.0
• 4F0906961AB CD
46.1.0
• 4F0998961 CD1
• 4F0998961 CD2
the lock up happened about an hour into the first update disc i put in to get the sw to 33.6.0, once it locked i let it sit for 45min - an hour (not exactly sure, but at least 45 min)
my 7 and 8 yr old daughters are convinced the radio broke so it didnt have to here me sing any more :/ its turning into a rough day lol.
Jack88 is shipping me his VAG-CON so i can run the scans in a few days, till then it looks like i'll be singing without the background music
#10
AudiWorld Super User
I received the following,
33.6.0
• 4F0906961AB CD
46.1.0
• 4F0998961 CD1
• 4F0998961 CD2
the lock up happened about an hour into the first update disc i put in to get the sw to 33.6.0, once it locked i let it sit for 45min - an hour (not exactly sure, but at least 45 min)
my 7 and 8 yr old daughters are convinced the radio broke so it didnt have to here me sing any more :/ its turning into a rough day lol.
Jack88 is shipping me his VAG-CON so i can run the scans in a few days, till then it looks like i'll be singing without the background music
33.6.0
• 4F0906961AB CD
46.1.0
• 4F0998961 CD1
• 4F0998961 CD2
the lock up happened about an hour into the first update disc i put in to get the sw to 33.6.0, once it locked i let it sit for 45min - an hour (not exactly sure, but at least 45 min)
my 7 and 8 yr old daughters are convinced the radio broke so it didnt have to here me sing any more :/ its turning into a rough day lol.
Jack88 is shipping me his VAG-CON so i can run the scans in a few days, till then it looks like i'll be singing without the background music
I'm guessing maybe you didn't have Hidden Menu enabled? Had to be done via a VCDS tweak before it broke. If you did, see what Misha's ideas could add. Also of course, try the basic three button reset (I'm far away from my car and manual, but someone can chime in with it if you don't know it). After that, you might first just stick the 3360 disk back in there and see what happens. Literally give it at least an hour, maybe two. Definitely hook a charger to it--I remember starting to panic on one when it was taking forever and I was afraid to even open the door when I had it updating w/out a charger. After that, I suppose try loading the 4610 disk #1 and see if it will take, and after that the #2 clean up disk. 4610 did not need 3360 as an absolute prerequisite (unlike 4140), so there is a small chance you could work around it. I'm not sure anyone has brought it back in a 4610 context; it was 100% fatal with 4140, including by dealer mishaps.
Finally, same core MMI and software was used with C6 (last gen) A6 and Q7, so when you are up against the wall on something like this, worth looking at those boards too. It was the intersection of two DOA Audis on the D3 and Q7 boards that essentially confirmed the flaw in 4140. It was buried in the Audi 4140 update instructions, but Audi didn't really warn of the consequences there.
Last edited by MP4.2+6.0; 03-21-2015 at 04:01 PM.