langers2k

I'm afraid I didn't keep the script, it was just something I threw together quickly as it's the only time I've tried VCDS scripter. Generally speaking I'd much prefer doing things step by step... You can find more about VCDS scripter here: https://forums.ross-tech.com/index.php?threads/16993/ The scripting language is super simple. If I remember correctly, the issues I had were: - you need to set a non-zero equipment number in VCDS first (otherwise the module complains about 00000 not being valid) - it would do 'some number' of changes then freeze or get confused depending how quickly the module responded In the end I think I had to run the script 6-7 times, removing whichever commands were success to get all the channels changed...

Yup and yup Assuming you have 10 colours at the moment, the 11-30 adaption channels will be set to 0. As soon any are non-zero, it should use all 30 rather than 10. TBH, it's a bit of a pain to do this via VCDS as you need to change each adaption channel separately - If you just want the colours on the headunit, that's ~90 changes - If you have ambient lighting and want them to match, that's ~180 changes If you have the 'automatic' option, that's another ~5-8 changes to correct the preset for each driving mode too. When I did this, I made my own colourset by interpolating the extra colours between the stock values: I think I used VCDS scripter to help my sanity but it still needed a little bit of hand holding...

If you're problem free, there is no need to update. If you do develop problems later, you can always update at that point As for the virtual sub, that'll need coding with VCDS or similar. Might be worth checking the VCDS section for a local member as they can probably help.

What VCDS cable are you using? If it's not a Hex-v2 that might cause issues...? Might be worth contacting Rosstech for advice

I don't think there is a 'correct' byte 18 value for the Octavia. Might be worth finding someone with VCP or ODIS-e who can fix the EEPROM for you

The fix is a MIB2.5 radio

At a guess, 5C0035680C or 5C0035680E would be the obvious choices but you'll need to deal with component protection... Might be worth seeing if @pab567 has any advice as this is very much his area

Not sure if there are any OE 17" steels. At a guess, you'd need: - 7,0J x 17" - ET49 - 5x112 PCD - 57.1mm centre bore That'll match a Trius alloy which was a stock option for the MK3 with 225/45 R17's fitted, they look like this: https://eshop.skoda-auto.sk/en_SK/alloy-wheel-trius-17-for-octavia-iii/p/5E0071497L+8Z8 You might need to drop to 16's if you want a few more options... It'll depend on your front brakes if they'll fit

It'll depend exactly which part number is fitted... IIRC, not all headunits don't have the video circuitry required for a reversing camera but at least some Bolero certainly do

That's correct, 4C is a 'virtual' module created by the ABS module so it doesn't really do much diagnostics wise. Fitting a TPMS button is much easier than a MK70 to MK60EC1 swap so that's definitely the simpler plan! A MK70 already supports ASR too

Oops... Should be sorted now

Couple of pics from today.... Google maps showing both the speed limit and a speed camera: Waze showing an ad for a M&S at a service station, I think if you stop it might show a banner too:

That's because the front fogs aren't part of the normal lighting config block They are earlier in the EEPROM but only seem to support bulb diagnosis on or off...

If you stop they might show a banner? But I can't say I've noticed one recently. Maybe they don't work in Android auto 🤣

Are you in the right section? Pretty sure there is no MIB1 suitable for a MK2 Superb...?

There are occasional ads on Waze but it's not a banner or anything like that. It'll just be a poi for KFC or similar on the map. Certainly nothing intrusive and easily ignored 👍 Both Waze and Google maps use live traffic for route planning/redirection. Checked my settings for Google maps and it seems there is a speedometer option. I'll give it a bash tomorrow and see if it does anything over AA...

Assuming you have halogen headlights, you'll need to replace the headlights for xenon versions along with headlight washers and the levelling system. Anything else won't pass the NI MOT Could get expensive depending if you can find used parts or not...

Should be fine assuming you pick the right sized camera

Then you'll need VCP or ODIS to reprogram the light outputs and move the rear fog light to a new pin. The footwell lighting is always on B50 and cannot be moved... If there are no spare pins, you may need a replacement BCM with some extra outputs

It'll be B50 just like a FL Octavia with a BCM:

Are you sure google maps supports those features? I know Waze does either over Android Auto or via the app

A dealer should be able to restore it. Otherwise, a full unedited VCDS autoscan might help someone create one for you

Assuming your VCDS cable is genuine, it's probably worth posting on Rosstech forums too: https://forums.ross-tech.com/ They will have more experience with a Audi TT that most people here

I retrofitted a VC on to a MY18 so it already had a MIB2.5 Amundsen so I didn't need to upgrade/change anything apart from adding a MOST (optical) cable and buttons with 'View' rather than 'Phone'. I think you'll miss out on: - Map display on the VC - VC options screen on the radio Not sure about what else or if anything else on a MY16 would need replacing. @pab567 can certainly rework various MIB2 into a MIB2.5 so it would just be finding a 9.2" screen, most have a hardware fault which causes a vertical line unfortunately...

@bubib5 I don't think Skoda Connect will work with a retrofitted MIB2.5... As you say, your VIN won't be listed as compatible on the VAG/Skoda servers so I'd be very surprised if it did