MMI Stuck In Bootloader

Reply Subscribe

Thread Tools

Search this Thread

Oct 13, 2011 | 08:04 AM

#11

05SilverA8

AudiWorld Member

Joined: Mar 2009

Posts: 340

Likes: 2

From: San Francisco Bay Area

Bluetooth

Remove the footrest with a Torx (30?). Move seat to all the way back position. Remove plastic moulding and then lift up the drivers side carpet. It is in a black box under the carpet. See attached photo.

Attached Images

Oct 13, 2011 | 10:24 PM

#12

haloguy628

AudiWorld Member

Joined: Feb 2010

Posts: 316

Likes: 2

From: Castle Pines CO

There is a TSB addressing repair of the Bluetooth module before installing the 4610 update using the CD-1 from the 4610. If the FW and SW are mismatched and you attempt to update to 4610 it may fry the BT module and it has to be replaced. BTW the BT module is Handyvorb in German.

Here, I found the TSB.

RVU - Repairing telephone preparation

Oct 14, 2011 | 09:16 AM

#13

subit0

AudiWorld Member

Joined: Feb 2009

Posts: 215

Likes: 0

From: A2, MI, USA

Telephone RVU TSB

Quote:

Originally Posted by haloguy628

Owners have reported fried or partially-fried BT modules as a result of previous MMI upgrades (it was 3360 that zapped mine). I believe that it only happened to some BT modules, that were likely installed on 2006 and early 2007 MY vehicles (A8's, but also some Q7's). The TSB specifies a replacement BT module, part # "4F0 910 336 H", and says " The replacement phone module will already have the correct firmware and software version", so you shouldn't need to perform the CD#1 "FW and SW upgrade" of 4610 if you install a new BT module (rev H or later).

It's a pity that the Service Advisors at my local dealership didn't check to see that my car qualified for this repair while it was still under warranty (they only check if the owner complains about a problem, and I didn't notice that my BT was partially broken until after my warranty expired).

Oct 14, 2011 | 03:48 PM

#14

Mills00013

Thread Starter

Audiworld Junior Member

Joined: Jun 2010

Posts: 20

Likes: 0

Quote:

Originally Posted by haloguy628

Well it already appears that the 3360 update fried the module. The Handyvorb2 that was appearing in my most list is no longer appearing, instead being replaced by the generic hex identifier (0x0FFFFFFFF or whatever). Do you think that the 4610 upgrade might bring it back to life?

I'm really just ready to replace it. I dont think I have much of a chance. Can anyone find me a part number on the bluetooth module?

Oct 15, 2011 | 08:18 PM

#15

subit0

AudiWorld Member

Joined: Feb 2009

Posts: 215

Likes: 0

From: A2, MI, USA

BT module part #

Quote:

Originally Posted by Mills00013

No, if your BT phone module is fried, the 4610 upgrade CD#1 will detect this and not run at all (i.e. no FW or SW upgrade to the BT module). Your only option is to replace the BT module.

Quote:

Originally Posted by Mills00013

I'm really just ready to replace it. I dont think I have much of a chance. Can anyone find me a part number on the bluetooth module?

The part # is listed in my previous post (above).

Oct 22, 2011 | 09:53 AM

#16

Mills00013

Thread Starter

Audiworld Junior Member

Joined: Jun 2010

Posts: 20

Likes: 0

So I've resolved all of my issues except for the amplifier clicking on and off. This now happens every 30 seconds to a minute and the whole sound system will shut off for about half a second. The MMI doesn't close, but the info display in the gauge cluster does black out the radio portion at the top for that split second.

I thought that it was an issue with the battery regulator, but I just purchased an audi battery and recoded the regulator and it is still doing it. Does anyone have any idea which component might be bad or what the issue here could be?

Vag com does tell me that its seeing component protection active on something, but I dont know what. The error is coming up when module 17 (instruments) is scanned.

Oct 22, 2011 | 05:25 PM

#17

greenz

AudiWorld Newcomer

Joined: Oct 2011

Posts: 7

Likes: 0

Quote:

Originally Posted by s4master1

it has all the symptoms of water damage in one of the units, this is very common on the Q7, water gets under the carpet and damages the phone unit causing erratic sound operation and jamming the fiber optic network.
you can run a test thru the system and it will tell you what is not responding properly.

s4master can you elborate more on this. I have an d4 A8 and the 'cowl' got clogged up which caused water leakage onto my rear pass carpet and drivers carpet. Now my MMI is in constant reboot with only the "Audi MMI" display poppin up every 10 seconds after performing a hard reboot 'Tel','****','Right button above ****' Dealer whats $500 just to diagnosis thinkin i can get the parts cheaper and just ask them to replace the specific part. Any thoughts. in the past month it works liked 1 / 2 times

Oct 22, 2011 | 05:40 PM

#18

greenz

AudiWorld Newcomer

Joined: Oct 2011

Posts: 7

Likes: 0

correction d3 gen. for some reason i can't edit the post

AudiWorld Stories

Bringing Audi to Life for Audi Fans

The Highs & Lows of Every Audi C-Class Generation

Joe Kucinski

Top 10 Most Expensive Audis Ever Sold on Bring-A-Trailer

Brett Foote

10 Audi Features & Options We Miss the Most!

Joe Kucinski

Audi Recreates Crazy-Looking Speed Record Breaker From 1935

Verdad Gallardo

Coachbuilder Recreates the 1995 Audi TTS Concept

Verdad Gallardo

Every Audi V10 Car Ranked!

Joe Kucinski

9 Audi Designs That Aged Like Fine Wine

Verdad Gallardo

2026 Audi Q5 Buyer's Guide (Every Model Explained)

Brett Foote

Ranking Every Current Audi 'S' Model From Worst to First!

Joe Kucinski

10 Best Audis That are FINALLY LEGAL to Import to the U.S.!

Joe Kucinski

Oct 23, 2011 | 11:17 AM

#19

greenz

AudiWorld Newcomer

Joined: Oct 2011

Posts: 7

Likes: 0

Here is a Vag Com Diagnostic that the $tealership let me have i copied the ones that related to the MMI

Base: V19.00.00
Audi: V19.32.00
AUX64X 1.171

4E0910611
E0380 BedienteilH01
Dealer Number 00000
4E1919612H
000
0050

1 Event Detected

00384 011
Optic Data bus
Open Circuit
Sporadio

Priority 5
Malfunction Occurrence 165
Drive Cycle 142

19- Data Bus Onboard Diagnostic Interface Gateway
4E0910468A
Gateway H07
Coding long
Dealer Number 03106
4E0907468C
0030

2 Event(s) Detected

00384 011
Optic Data bus
Open Circuit
Sporadic
Priority 5
Malfunction O 105
Drive Cycle 142

00463 004
Digital Sound System Control Module – J525
No Signal/ Communication
Sporadic
Priority 3
Malfunction Occurrence 2
Drive Cycle 110

37 - Navigation System
4E0910887K
MNS US H44
Dealer Number 03109
4E0919887C
000
0570

1 Event(s) Detected

00003 014
Control Module
Faulty
Priority 5
Malfunction Occurrence 52
Drive Cycle 0

Oct 24, 2011 | 06:39 PM

#20

Mills00013

Thread Starter

Audiworld Junior Member

Joined: Jun 2010

Posts: 20

Likes: 0

I'm completely up and running with the exception of my bluetooth module (still being fried in the 3360 update apparently.)

I removed the bluetooth module today and replaced with a MOST optical loop and lo and behold, the entire system works like magic! Thanks so much to everyone for their help! I now have a kick *** W12 for only a fraction of the price!

Does anyone know of a cheap place to get a replacement bluetooth module? The product code on it is 4E0862335. You guys rock!

Reply Share

First
Prev
2 / 3
Next
Last