[Bossweb]

In that case link expires tomorrow: 8S0906961AD

AU_C1_AU334_0295_0783_prod_8S0906961AD (mod TT).zip

View and download from Yandex Disk

disk.yandex.com

I highly recommend either rebooting the VC via ODIS or disconnecting the battery terminals to ensure the VC is restarted as soon as the update is finished.

With this VC SW 295, can you update directly from old versions 221-265? 🤔

Yes this is so 📝, it is very good news for people who had VC with very old SW versions and could not update to SW version 296 👏🏻 (AU_C1_AU334_0296_0790_prod_8S0906961AE.7z)

 

[afonsoocosta]

With this VC SW 295, can you update directly from old versions 221-265? 🤔

Yes this is so 📝, it is very good news for people who had VC with very old SW versions and could not update to SW version 296 👏🏻 (AU_C1_AU334_0296_0790_prod_8S0906961AE.7z)

Yes you can, I managed to put it together and update my 221 to 295 and get Car play fully working.
I will try to write a full guide on how to do it with the MIB toolbox

 

[Bossweb]

Yes you can, I managed to put it together and update my 221 to 295 and get Car play fully working.
I will try to write a full guide on how to do it with the MIB toolbox

Great! 👏🏻

The exact reference of your VC was this, true? 🙄
8S0920790 (no letter) - HW: H32 - SW: 0221

Well, if you make a guide, it would be very good for people who have doubts about how to update an old SW like the one you had at 295 📋, to then be able to activate CP/AA 😉

 

[New_TT_owner2015]

Hi folks,
My partner just impulse-bought an early 2015 TT (😁) and I've been reading this thread (and others, although this one's a gold mine) with interest to try to install CarPlay for her. I've found various places that charge for the required update files but I feel uncomfortable paying the money when I know there's a community like yours that can help out.

I don't have any car interface hardware (like OBD11) so I'm struggling to find out the VC version (I tried the 2x/3x 0.0 button trick to no avail) but we don't have the Audi Smartphone icon on the dash so I'm assuming I need a VC update before having access to CarPlay.

MMI version: MHI2_ER_AUG24_P0530 MU 0139

I initially tried using MIB to patch the MMI but realised there are no patches for that MMI version. The download links for the AU43x firmware updates all seem to be dead, so I am struggling to update in order to patch the MMI, but I assume that even if I can perform this update, I'll still need the VC update to see the CarPlay icon and therefore access that service, correct?

It seems I'm in the same position as afonsocosta above. If there's no way of reading the VC version without OBD11 or something similar (which would cost a similar amount to buying a VC update online), what is the "top protection" removal that is mentioned here:

No real need to take it all out, you can just remove the top protection and check the label.
I've checked and it's just ending in 790, no extra letter after it.

Is that a removal of the dash plastic?

Thanks all for the awesome thread - it seems I'm so close but I'm trying hard to avoid paying someone a couple of hundred quid for the benefit of CarPlay!

 

[Bossweb]

Hi folks,
My partner just impulse-bought an early 2015 TT (😁) and I've been reading this thread (and others, although this one's a gold mine) with interest to try to install CarPlay for her. I've found various places that charge for the required update files but I feel uncomfortable paying the money when I know there's a community like yours that can help out.

I don't have any car interface hardware (like OBD11) so I'm struggling to find out the VC version (I tried the 2x/3x 0.0 button trick to no avail) but we don't have the Audi Smartphone icon on the dash so I'm assuming I need a VC update before having access to CarPlay.

MMI version: MHI2_ER_AUG24_P0530 MU 0139

I initially tried using MIB to patch the MMI but realised there are no patches for that MMI version. The download links for the AU43x firmware updates all seem to be dead, so I am struggling to update in order to patch the MMI, but I assume that even if I can perform this update, I'll still need the VC update to see the CarPlay icon and therefore access that service, correct?

It seems I'm in the same position as afonsocosta above. If there's no way of reading the VC version without OBD11 or something similar (which would cost a similar amount to buying a VC update online), what is the "top protection" removal that is mentioned here:



Is that a removal of the dash plastic?

Thanks all for the awesome thread - it seems I'm so close but I'm trying hard to avoid paying someone a couple of hundred quid for the benefit of CarPlay!

Welcome friend! 🖐🏻

The cheapest way to know with certainty the reference and SW of your VC is to buy an OBD such as this one 👌🏻:

https://a.aliexpress.com/_EysoL1N

Then, with an application like "Car Scanner ELM OBD2" you can obtain that information 📝

However, if you install the SW 295 Mod TT that was published above, you should be able to update your VC without problems 😉

 

[New_TT_owner2015]

Thanks, that's good to know! I haven't got the radio removal key so I've been fiddling around with an endoscope to try to see the back of the VC module 😂

The link for the SW 295 Mod TT was a limited time link, so I don't have access to it any more. Any chance you could re-share...? Thanks again

 

[New_TT_owner2015]

I've got the files for MMI and VC updates from the handy Drive folder links @pcbbc, so I'll test the SD card with the MMI updates now. When I have access to the SW 295 mod file, is that a similar process as the MMI updates (copy to root on SD > red menu > update)? Or do I trigger the VC update from somewhere else? From reading between the lines on the recent @afonsoocosta posts I assume it's using the red menu, and the car just knows it's a VC update rather than MMI due to the file types

 

[New_TT_owner2015]

Thanks for the link.
Should I update Vc first or in the end of MMI?
Can I restart the VC via OBD with the Car Scanner APP?

EDIT: To update the VC do I need to connect via telnet or just SD card on slot 1 and red menu in the car?

@afonsoocosta or @m4k4r0vbf , any chance one of you folks could re-share the SW 295 mod file? 🙏 Thanks

 

[pcbbc]

if it’s the update for letterless VC, there’s a copy over at mibsolution.one

VC update TT Letterless 295 mod NB H31 or hight (h30=brick)

Be warned you MUST check you have H31 or greater before starting or you will have a brick - EVEN THEN YOU PROCEED ENTIRELY AT YOUR OWN RISK
Advice is to disconnect battery after update and reconnect

 

[pcbbc]

Or do I trigger the VC update from somewhere else?

VC update is from Engineering menu, just like MIB.
It‘s normal for VC to light like a Christmas tree and screen to change a washed out low res mode - ignore it and wait.
If the upgrade fails due to error: "Device reporting error FPK:0 Error Code 142" you have to hold your key fob against the sensor on the steering column to continue.

 

[pcbbc]

The download links for the AU43x firmware updates all seem to be dead

You can find links to everything, including working downloads, in my post here.

You can use a MIB toolbox to do this also, but I don’t use that method so can’t advise.

If you live in or around SE London or Horsham West Sussex I can do this update and coding for you. I have done many dozen forum members vehicles now at a small fraction of the aftermarket installers prices. Just a small donation to my beer fund, if you are happy. Send me a PM.

 

[New_TT_owner2015]

Thanks, I found your post and have the MMI updated with CarPlay working 👍 The only thing I don’t have now is the VC update with the CarPlay icon. I can run CarPlay and have found that if I accidentally exit back to the main MMI menu I just need to command Siri to open an app and I get back into the CarPlay screen, without having to unplug the phone.

I appreciate the offer for hands-on help but unfortunately I’m in Bristol! I guess my options are to either live with it as it is, order one of the cheap diagnostic units to check my VC version or order a radio removal key to pop the top off and look at the sticker on the back. I’ll mull it over this evening. Thanks for all the help and links so far!

 

[pcbbc]

You could check the forum VCDS members map, but I don’t know how up to date it is.

 

[afonsoocosta]

So as promised and to give a little back, where's how I've managed to update my MIH2_ER_AUG24_S0530 with main version 0139 and VC H32 with version 0229 to the latest and running car play with the icon on the dash.

Things you'll need for the update:

• 32GB SD card fresh formatted with FAT filetype
• ODB2 Scanner to activate developer mode on the car, I've used this one because one of my friends had one and worked as needed.
• Scanner app if the ODB2 scanner you have don't have one. I've used Car Scanner Pro, it's 7€ lifetime and it's worth the money.

First step
We'll start to update the MMI to the latest version that its available and thanks to @pcbbc here you have the link to the update. I've updated directly from 0139 to 1339 without a problem but I couldn't update to the 0884, so to save time you can update to the 1339 directly.
Just download the version that you want to install and put it on the fresh formatted SD card, don't forget that the SD card should have the files in it and the folder. If you unzip the content that you downloaded just pick the content of the folder to the SD card and not the folder.
After having the update on the car, you just go to the car, turn it on and go to the engineering mode, here you have how to access it.
After that you can follow this guide on how to do an update. It's pretty much the same thing and you even have the photos to follow.

Second Step
You'll need to check the hardware that you have on the Virtual Cockpit to see if its possible to update it. I've manage to check the version I have by removing the top part of the dash that's pretty easy and you can see the tag with the information of the Virtual Cockpit. My just end in 790 so it's safe to update to the 295 version.
If you don't check this and your Virtual Cockpit is refurbished you can brick your can and it will be expensive to repair.
Here you have an image of the cover you need to take out to check the number of the Virtual Cockpit. You just need to remove 1 screw and do a bit of wiggle to take it out, very easy and can safe you a lot of money.

After confirming that you have the correct version and that is safe to install the update.
You go to this link and do the login with guest as username and password then download the version "VC update TT Letterless 295 mod NB H31 or hight (h30=brick)" and finally you do the same as to update the MMI.
Be warned that updating the VC does have RISK and that you MUST check you have H31 or greater before starting or you will have a brick - EVEN THEN YOU PROCEED ENTIRELY AT YOUR OWN RISK
As soon as the update ends you should restart the Virtual Cockpit, if you don't have a ODB2 scanner that can do that, just disconnect the negative terminal of the battery. You'll have a lot of errors as soon as you plug the battery back, but just lock the car and let it sit for 10 minutes and they will go away.

Third Step
Now the software you're running in the car is the one you need to have the CarPlay working but we need to activate the CarPlay option and you can do that via ODB2 if you're tool allows you to do it but as mine didn't allowed me to do it, I've opted to try to activate CarPlay via MIB that's a toolbox that allow to do cool stuff in your car as well.
To install MIB you need to go here and download the latest version available. After that you'll install it as an update for the car.

Fourth Step
After installing MIB, you'll need to flash the unit to add the FEC codes so you can see the CarPlay icon on the menu and so that CarPlay actually works when you plug the cable into the car.
You'll need to get the correct patch for your MMI version, so in my case as I've updated to the 1339 version I need to get the patch MHI2_ER_AU43x_P5098_MU1339_PATCH. To get it you'll need to download the patches available here and then select the one you want and get it into the SD card as if it was an update.

Final Step
Flash the patch so the MMI can display the CarPlay icon and the CarPlay actually works when connecting the cable.
To do this you'll enter the green developer menu with the SD card with the patch downloaded, but you'll first do a backup to be sure that you have a backup if needed.
To do the backup just enter the MIB option in the green menu and then go to backup_restore and select backup. Just wait for the backup to finish and then you'll patch the MMI.
To do the actual patch you'll need to go to patch_ifs_root_aio and then select Flash patched image | add FECs | CP/AA coding. As soon as the update finish you can try to connect your phone to the car and you should have CarPlay working.

Don't forget that you can always brick the car by doing updates and there's always risk when doing an update. Be sure that you have enough battery in the car to do the updates or just let it running while doing the updates because if the car turns of while doing the update you'll brick your can and will be hard and expensive to fix.
And don't forget that this is just a basic explanation on how I've managed to update my car and proceed to update your car AT YOUR OWN RISK

Any question just ask and I'll try to help as others have helped me.

 

[New_TT_owner2015]

You could check the forum VCDS members map, but I don’t know how up to date it is.

Looks like there are a couple of Bristol-based people on there. I've managed to confirm 790 letterless VC with some patient endoscopy up the back of the steering column. SW version looks like 02... but I can't get a clear look at the last numbers and I can't see the HW version. I'll have to see if I can get the top off to have a look.

So as promised and to give a little back, where's how I've managed to update my MIH2_ER_AUG24_S0530 with main version 0139 and VC H32 with version 0229 to the latest and running car play with the icon on the dash.

Things you'll need for the update:

• 32GB SD card fresh formatted with FAT filetype
• ODB2 Scanner to activate developer mode on the car, I've used this one because one of my friends had one and worked as needed.
• Scanner app if the ODB2 scanner you have don't have one. I've used Car Scanner Pro, it's 7€ lifetime and it's worth the money.

First step
We'll start to update the MMI to the latest version that its available and thanks to @pcbbc here you have the link to the update. I've updated directly from 0139 to 1339 without a problem but I couldn't update to the 0884, so to save time you can update to the 1339 directly.
Just download the version that you want to install and put it on the fresh formatted SD card, don't forget that the SD card should have the files in it and the folder. If you unzip the content that you downloaded just pick the content of the folder to the SD card and not the folder.
After having the update on the car, you just go to the car, turn it on and go to the engineering mode, here you have how to access it.
After that you can follow this guide on how to do an update. It's pretty much the same thing and you even have the photos to follow.

Second Step
You'll need to check the hardware that you have on the Virtual Cockpit to see if its possible to update it. I've manage to check the version I have by removing the top part of the dash that's pretty easy and you can see the tag with the information of the Virtual Cockpit. My just end in 790 so it's safe to update to the 295 version.
If you don't check this and your Virtual Cockpit is refurbished you can brick your can and it will be expensive to repair.
Here you have an image of the cover you need to take out to check the number of the Virtual Cockpit. You just need to remove 1 screw and do a bit of wiggle to take it out, very easy and can safe you a lot of money.
View attachment 508722
After confirming that you have the correct version and that is safe to install the update, you download this and do the same as to update the MMI.
Be warned that updating the VC does have RISK and that you MUST check you have H31 or greater before starting or you will have a brick - EVEN THEN YOU PROCEED ENTIRELY AT YOUR OWN RISK
As soon as the update ends you should restart the Virtual Cockpit, if you don't have a ODB2 scanner that can do that, just disconnect the negative terminal of the battery. You'll have a lot of errors as soon as you plug the battery back, but just lock the car and let it sit for 10 minutes and they will go away.

Third Step
Now the software you're running in the car is the one you need to have the CarPlay working but we need to activate the CarPlay option and you can do that via ODB2 if you're tool allows you to do it but as mine didn't allowed me to do it, I've opted to try to activate CarPlay via MIB that's a toolbox that allow to do cool stuff in your car as well.
To install MIB you need to go here and download the latest version available. After that you'll install it as an update for the car.

Fourth Step
After installing MIB, you'll need to flash the unit to add the FEC codes so you can see the CarPlay icon on the menu and so that CarPlay actually works when you plug the cable into the car.
You'll need to get the correct patch for your MMI version, so in my case as I've updated to the 1339 version I need to get the patch MHI2_ER_AU43x_P5098_MU1339_PATCH. To get it you'll need to download the patches available here and then select the one you want and get it into the SD card as if it was an update.

Final Step
Flash the patch so the MMI can display the CarPlay icon and the CarPlay actually works when connecting the cable.
To do this you'll enter the green developer menu with the SD card with the patch downloaded, but you'll first do a backup to be sure that you have a backup if needed.
To do the backup just enter the MIB option in the green menu and then go to backup_restore and select backup. Just wait for the backup to finish and then you'll patch the MMI.
To do the actual patch you'll need to go to patch_ifs_root_aio and then select Flash patched image | add FECs | CP/AA coding. As soon as the update finish you can try to connect your phone to the car and you should have CarPlay working.

Don't forget that you can always brick the car by doing updates and there's always risk when doing an update. Be sure that you have enough battery in the car to do the updates or just let it running while doing the updates because if the car turns of while doing the update you'll brick your can and will be hard and expensive to fix.
And don't forget that this is just a basic explanation on how I've managed to update my car and proceed to update your car AT YOUR OWN RISK

Any question just ask and I'll try to help as others have helped me.

Great write-up, thanks. Just a note - the link for the VC (where you say "download this") isn't working. Can I assume this link is the letterless VC mod link on mibsolutions quoted by @pcbbc above?

 

[afonsoocosta]

Looks like there are a couple of Bristol-based people on there. I've managed to confirm 790 letterless VC with some patient endoscopy up the back of the steering column. SW version looks like 02... but I can't get a clear look at the last numbers and I can't see the HW version. I'll have to see if I can get the top off to have a look.



Great write-up, thanks. Just a note - the link for the VC (where you say "download this") isn't working. Can I assume this link is the letterless VC mod link on mibsolutions quoted by @pcbbc above?

Yes, that's it. I've updated the text.

 

[New_TT_owner2015]

Thanks for the tip of removing the top of the dash - managed to get my endoscope down through one of those holes and confirmed it's 790 letterless, 0215 and H32, so I'll try the letter less mod this weekend

I'll keep you posted on my progress.

 

[New_TT_owner2015]

Update:
It’s installed and seems to be working fine! I’ve only just done it, so the warning lights are still on, but CarPlay is fully functional.

Just a note for anyone else trying this method:
After the update finished, it gave me an error message saying something along the lines of “the FPK wasn’t recognised” when it was checking the installation. I had the option to retry checking it or attempt reinstallation and I was worried that I had a corrupt file. I clicked to recheck rather than reinstall, but got the same error message. I kept the faith, clicked to continue despite the reported error, and waited for the system to restart. It came back to a grey screen with blank speed/rpm dials, so I went ahead with the battery disconnect and when I plugged it back in everything booted up properly, back to the normal menu. Big sigh of relief! I’ll go out again to check the warnings disappear but all seems well - you just need to be patient through those squeaky bum moments and trust it’ll figure itself out.

Final note:
Assuming you get to this endpoint, your dashboard will now tell you you’re driving a TTRS. I’m sorry to say, the fact that you have had to go through this process makes this highly unlikely, and you should continue to drive as normal 😉

Big thanks to those above for their patience and advice

 

[kevin#34]

for the FPK error I think it would have been enogh to just put the key on the steering column where there is a symbol

 

[New_TT_owner2015]

Ah, ok. I remember having read that now that you mention it but I forgot in the moment. I’ve just taken it out for a drive and all the error messages seem to have cleared, so hopefully all is well 👍