fumundacheze

I need a copy of 1110, My version was 0600 and tried updating to 3360 everything looked good until I got an error, I clicked the retry option and still came back with an error, I red it may be related to some sort of protection. I decided to click continue and it went on through the motions until it started "flashing" then it would hang and said it was unable to flash. I am hoping that trying to use 1110 may help me, if not I guess I will need to puirchase a new MMI controller. I have yet to use Vag-Com to scan for any codes that may be relative. This is my next step as I continue the hunt for 1110.

Any advise would be much appreciated.

fumundacheze

Attached is a photo of where my journey ends. I have searched for a good while but no specific issue relative to my situation has been found.

mishar

Is your update CD OEM or copy?

fumundacheze

You fished me out very quickly, the disk is a burned image.

mishar

I would try OEM CD first. Part number 4F0 998 961

fumundacheze

Found version 1110 on audi-resource.com and burned the image, mmi bootloader recognized the disk and read the metadata and binary fine, it went to flash just like 3360 did and hung after 6 bars. I have a strong feeling that if I order an OEM disk I will receive the same result. If I do order an OEM disk should I order 1110 since I started off with 0060 or order 3360 and the newest (4160?) update? The 3360 is what I initially started off with since that is what I was under the impression to use. It seemed to go through things fine until this happened initially.

Any help is appreciated, especially considering my circumstances, at least the car is drivable, quite daily commutes and disconnecting the battery is getting old already though. I had no idea the mmi was so sensitive, a fresh format and clean install option would have been nice.

mishar

Did you scan it? You should be sure there are no faulty codes in any MMI component. Clear whatever you get and check again if anything is back. If there is something you should fix it before update.

You can go directly to 4610. No need for increasing risk doing update in few steps. OEM CD's are more reliable. Your CD Changer may be a problem too. You may want to run one of those head cleaning discs before the next attempt.

fumundacheze

I ran a quick VCDS Lite scan (Too cheap to buy Hex-Key setup), not sure if it hit all the modules since I need to make a custom profile that scans all the modules for the D3 A8, I used the B6 A4 profile since it seamed like it would have been the closest profile in the default list. Anyways, There was no communication with anything other than the engine modules, I will work on getting a legit scan with effective results that I can post this evening to help with a definitive solution. I do appreciate your help on this matter.

fumundacheze

Below is the results of my scan, No modules are responding when VCDS is trying to communicate, engine 01 is the only module responding when running a scan. This seems bad.


VCDS-Lite Version: Release 1.2
Wednesday, 15 January 2014, 20:20:18.


Chassis Type: 4E - Audi A8 D3
Scan: 01,02,03,05,06,07,08,09,0E,0F,13,15,16,17,18,19,1E ,28,34,36,37,38,42,46,47,52,53,55,56,57,61,62,65,6 7,69,6C,72,76,77

-------------------------------------------------------------------------------
Address 01: Engine Labels: None
Controller: 4E0 910 560 A
Component: 4.2L V8/5V G 0050
Coding: 0007773
Shop #: WSC 02313
VCID: 1F31607F8EA5
5 Faults Found:
17983 - Right Engine Mount Solenoid Valve (N145): Short to Plus
P1575 - 001 - Upper Limit Exceeded
18282 - Valve for Torque Support Mount: Short to Plus
P1874 - 001 - Upper Limit Exceeded
18010 - Power Supply Terminal 30: Voltage to Low
P1602 - 002 - Lower Limit Exceeded - Intermittent
16523 - Oxygen (Lambda) Sensor B1 S2: Response too Slow
P0139 - 004 - No Signal/Communication
16543 - Oxygen (Lambda) Sensor B2 S2: Response too Slow
P0159 - 004 - No Signal/Communication
Readiness: 0010 1001

End --------------------------------------------------------------------------------------------------

ltooz_a6_a8_q7

When you can't erase the flash, it sometimes means that the flash is the wrong part or the power is NOT on. Make sure you have charger charging the system or have engine running.