0Done
Update installed successfully.
Do this
Restart the MMI (switch the car off and back on, or hold the power/volume knob until it reboots).
Help & Support
Every answer, in one place.
Everything we get asked about CarPlay and Android Auto on the Audi Virtual Cockpit — what fits, what it costs, how the install works, and what to do when something looks wrong. Search it below, or message us and we'll answer directly.
Update error codes
Find your codeUpdate stopped with a bootstrap error like Error Code 24? Type the number it put on the screen and see what it means and what to do next.
35 answers
Before you buy
17Compatibility, models and what the upgrade covers.
Your order & the client area
10Downloading, installing and using the portal.
Newer answers
2Written for customers from the questions that keep coming up.
CarPlay & Android Auto Cockpit Update Pack
6Questions about this package.
Update error codes
bootstrap error codeWhen an update stops, it usually comes up with a bootstrap error code — a red Download-Client Error panel reading TheNavMan bootstrap · Error Code 24 (older builds show echec (NN)). Type that number below and read what it means.
Good to know: if an update doesn't complete, it's designed to leave your car exactly as it was — nothing is changed or damaged.
Every code we know
60Try again
The update didn't run — your car was left unchanged. Usually the package doesn't match the car it's going onto: the VIN isn't the one the build was made for (or the car reads a bad VIN), the car's software version hasn't been updated to what the package expects, or the files on the card were incomplete.
Do this
Check the package is the right one for your car, that the build was made for your car's VIN, and that any firmware update that has to go on first is installed. Re-copy the unzipped files to the card and try again. If it still happens, send us your VIN and your car's software/version details and we'll confirm the right package.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
20, 24, 25SD card
The car couldn't read from or write to the SD card. In practice it's almost always the card itself: its lock slider being on, or the card catching on the way in so the MMI never reads it properly.
Do this
Eject the card and check the small lock slider on its edge is pushed away from the lock position — with the lock on, the car can't write to it. Then push the card back in squarely, all the way until it clicks, with the radio off while you do it. Make sure it's a good-quality card formatted as FAT32 with the unzipped files at its top level, and if the code comes back, try another card or the other slot.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
113SD card
The car can't read the card. It has to be FAT32 and no bigger than 32GB — a card left as exFAT or NTFS, or a 64GB or larger one, gives this code.
Do this
Reformat the card as FAT32 (not exFAT, not NTFS) and copy the unzipped files back onto it at the top level. If it's a 64GB or larger card, use a 32GB or 16GB one instead — bigger cards normally come as exFAT, which the car won't read.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
10, 31, 32Send us your details
Your car's software isn't one this update supports.
Do this
Nothing was changed. Send us your car's details — your software may be outside what this package covers.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
70Try again
The update was interrupted part-way through.
Do this
Don't remove the SD card or switch the car off while the update is running. Restart and run it again.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
61Try again
The update was applied, but one tidy-up step didn't finish.
Do this
Restart the MMI. If anything looks off afterwards, send us the code.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
11, 30, 33–43, 50–52Try again
The update couldn't finish preparing the car's menu (an internal step). Your car is left safe.
Do this
Try once more. If it repeats, send us the exact code.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
Any other numbere.g. 99Send us a photo
A code we don't recognise — it may be coming from the car's own update system rather than our package.
Do this
Take a photo of the screen showing the number and send it to us.
Send us the install log (.txt) file from the SD card with your support message — it shows exactly where the update stopped.
Still stuck? Tell us the car and what you're seeing.