varaderoguy

I don't think that everybody ever found the answer to AFS issues. I had the same problem on my 2016 Octavia Scout. The system is speed sensitive and from discussions from the local dealer and having seen a technical bulletin from Skoda on the issue, the behaviour is not described as a fault. The headlights are meant to be sensitive to direction of the steering-wheel and are meant to give you additional visibility and lighting up the edge of the corner you are travelling around. The annoyance seems to be that the lights do not straighten up until you speed up (as opposed to taking direction from the steering wheel that should probably happen). Two potential workarounds: 1) Set-up your driving profile (ie go into Eco, Normal, Sport mode) and select Individual. Select "Sports mode" for Headlights. This improves the reaction of the headlights (but doesn't cure the issue) 2) Take the highlights off AUTO mode and use them in normal mode - which you seem to have discovered already. There might be a firmware update for the Lighting Left and Lighting Right modules, but good luck in getting a Skoda garage to update your car's firmware!!!!

OBDEleven is definatly the way to go in that case. Good luck - if you pay for the Pro veriant, you get Long-Coding made available to you too.

Yes, you can revert to older bluetooth versions. However, if you have Android, you need to active developer mode. Go into Settings -> About Phone-> software. Find out where it states the Build Number - and click on it 10 times. This activates developer mode. Now go back one step and go Settings -> Developer Mode. Scroll down until you reach Bluetooth AVRCP version. Most devices will be fine with AVCRP Version 1.4. If that is not playing nicely, then try Version 1.3.

In terms of whether it is worth it, I have both ODBEleven and VCDS. It really depends on technical competance; if you are good with a PC, then VCDS is definately the way to go. Gives very good granular connectivity. ODBeleven is a good tool, but feel it is slightly clunky interface. Very good for reading diagnostics and for giving your car extra little mods, but not great for anything else.

One of joys of living next to a major road artary is that I get to see all the cars on the low-loaders being trucked up to dealers. I saw my first Octavia MK4 today - an estate in Denim Blue heading up to West End Skoda in Edinburgh. They are coming in; slowly but surely. I'll query my dashcam and see if I can the image of it if anyone is interested.

Generally, a new waterpump will fix the problem - it was just the factory original pumps that were problematic. If it was done 8k ago (along with the timing belt), then all good for another 52k miles.

I would say that if you are coming from a Citroen C5 Estate (I am a former Citroen owner - my first car was a Citroen CX), then you will definately need an Octavia Estate as your replacement car. With the VAG cars, its all dependant on your journey needs. If zooming up and down the M6 is your thing, then you will definately need a TDI...no questions. Generally, 45-55mpg and bulletproof reliability. DSG gearbox are not all bad...it all depends on the previous owner and how they have been used/abused in the past. So - if you have your eyes on a 13 plate early MK3 Octy, then that sounds about the right price. Sounds slightly expensive, but the trouble is that the second hand car market has gone bonkers recently (ie everybody wants a Skoda), so that could be the market trade price. Things I would check - you will *definately* need the waterpump replaced as a matter of urgency - see . Make sure the car has had its minor/major services done and that its log-book is up to date (should have either a standard or digital printout). Check recalls - https://www.gov.uk/check-vehicle-recall and make sure that the dealer has done a proper service prior to selling it to you. There are plenty of good MK3's available....my personal preference is the FL (or face-lifted) versions - cos they are generally put together better, but it all depends on your budget. A good number of taxis drivers cannot be wrong - you have this fantastic resource available too. I wish you good luck on getting your first Skoda! PS....a Rapid will be too small.

Its not hard....just set a value to do with battery voltage level so that auto-stop start never kicks in.

I suspect it maybe the combination of a DSG gearbox interface and its 4 wheel drive....in all honesty, I cannot really answer that question. Best you give him a shout first and get a quote for your vehicle.

Its the boot struts - my first Octy did that. You can either try a light grease on the structs or check the fixings at the top and bottom of the struct to see if they are slightly corroded.

I did make contact with Chris and he was very kind and give me a price via text message. It was £450 for a genuine camera on my 2019 Octavia Scout; my car was going for service at Autohaus in Edinburgh anyhow - and they quoted £475 for the same job. Sadly, the cost in fuel (from Scotland) didn't justify visiting Chris on this occasion, but I will check what the price would be on my husband's Octavia SE1.0 and my mother-in-law's Fabia SE-L in the near future.

**Updated March 2025** The latest firmware version is: 0480 for SOP4.x hardware. 0363 for SOP3.x hardware. 0253 for SOP2.x hardware. **UPDATED May 2021** **Updated Feb 2024** Minimum size of SD card is now 32G **Please note everything on here - is generally warranty effecting - break it and you'll need to pay to get it fixed** Dear all, I thought I would pen down my experience in terms of upgrading my firmware on my 2019 Octavia Scout. I have cleared me writing this piece with the Briskoda Moderators. I have always berated Skoda for the fact that there are firmware updates available to fix various silly niggles on the Entertainment system. I have a Amunsden system (Bolero with Sav Nat). You have to play silly games with your dealer, just so they can look to see if any of your MIB system faults are displayed as a known issues....which is the measure that they use. The point is that unless your car system is seriously glitchy, dealers won't generally touch the MIB system. I am an IT guy, and this kind of thinking (especially with the more modern connected systems) depresses me....the world is told to patch,patch,patch - but VW group choose not to do so unless absolutely necessary. I now understand why....because the MIB2.5 system upgrade that I managed to get hold of for my Scout - took over an hour to upgrade. Time is money in dealers and this is why when dealers do a firmware update, then charge it as a warranty claim. On my system, there were many many patches for 0475. The version of firmware provided by a member on this forum was for 0478. (May21) There are also different version of firmware available. This is an important thing to note: There are generally (for Bolaro and Amunsden) - different software strands: They are: SOP2.x, SOP3.x and SOP4.x - when you look at a firmware version, you will be presented with a version such as 0472 - this says that it is a SOP Version 4.x . You can only update SOP4.x strands with another SOP4.x strand. Therefore, if you have 0472, you can upgrade to 0478. If you have a SOP3.x - e.g. 0359, then you cannot safely upgrade to SOP4.x 0478 firmware. There are people on here who say they can do it, but this is a risky area and you risk bricking your hardware. Now some legal stuff - because Briskoda cannot officially endorse anything that you do to your car (its a forum for Skoda enthusiasts, not dubiously obtained software) and the fact that the forum doesn't want to be sued by VW Group for posting non-authorised/obtained software, all the dealings for firmware has to done behind the scenes. Its sad that way. The firmware files are generally quite large (my copy was about 3GB). So once you have found the appropriate thread for your MIB system (it could be a Bolero, Amunsden or Columbus system), whether it is a MIB, MIB2 or MIB2.5 system, and you have found the appropriate member who has access to the firmware, you will be asked to take a photo screenshot of the system information. You can find that in System Information in the MIB system under Menu and Settings. This information shows the VW part number and the current firmware level. Do not confuse this with the maps/nav version information. If you are brave enough to do the firmware update, my other caveat is that you need to know your way around a PC. I'm a linux guy (which helps), but a good technical expertise level is useful. You will need: The link to the downloaded software An 32GB SD Card - DOS partition and formatted in FAT32 (Linux land it is called vfat) Download the firmware image - it will have a filename similar to: MST2_EU_SK_ZR_P0478T.7z . Briefly, that equates to: MST2 = MIB2 or 2.5, EU_SK_ZR are all countries (its a Europe and Russia image) and P0478 is the firmware version. The file is given in this case in a 7zip format (highly compressed). I know there are Windows decompression tools available, but I use 7z command line - in this case "7z x MST2_EU_SK_ZR_P0478T.7z". Make you do this in a new directory (otherwise it write files all over the place in your current directory). You should also file scan the files to make sure there are no virus's. After a while, you end up with a directory full of files. You can safely move the .7z master file elsewhere. There will be a new directory created with the same name as the firmware. Go into this directory and copy the content onto your SD Card. This process will take about 30 minutes all told. Eject the SD and go to your car..... Now connect up the battery charger to your battery and start the charging process. Remember, if the MIB system detects voltage levels below 12V (I think it is 11.8V), it will not allow you to upgrade (or its a bad idea anyhow). Think of it doing an Android upgrade with low battery voltage - not advised. Get into the passenger seat, and go into the glove compartment. Remove your current SD cards in SD1 (and SD2 if you have that slot). Switch on the MIB system and insert your SD card with the firmware on it - into SD1. It must be SD1 slot only. With the MIB system on, press and HOLD the Menu button until you get some hidden menus appear. Top option is labelled firmware/updates. Select it (either press screen or use the right hand knob and press your selection). Select Upgrade as the option you need. The system will go away and read the SD Card and see if there is a firmware update available. If all is working well, the system will reboot and put itself into Emergency Update mode (Scary Screen). You will now right here find if your files are corrupted or not. First attempt at my upgrade....it didn't go well, because I use 7z e as opposed to 7z x flag to extract the files. Once that snafu had been fixed (and I stopped panicking) , and I had the files in the right order in the right directories, all started working. I had over 100 updates - these were mainly CPU related and firmware for the bluetooth modules etc. They take time to process....be patient. After about 60 minutes, the upgrades finishes and the radio reboots - once to ask you whether you want to downgrade your system to the previous firmware level (press cancel here). The system then completes and switches itself off. Leave it for about 60 seconds. After 60 seconds, switch it back on...(in my case, the Scout Logo appears) and the system boot up. All seemed to work well, but I had some minor niggles to content with. 1) The GPS module went AWOL for about 10 minutes, then came back to life. 2) I could not get Skoda Connect to work. Skoda Connect was an interesting one - and I fixed it an interesting manner. I ended up doing a car factory reset. Skoda Connect still didn't work. A quick check with the Skoda Connect app showed I was logged out, so re-registered the car with my login. The app showed all was well and re-registered, but still no Skoda Connect. I left it to do its thing....(got bored). Today - I had another look at the problem....I realised that because I re-registered the car, that all the personalisation options had gone back to factory reset. I had to go into Menu-> Personalisation and re-associate the car with my profile....Skoda Connect then started working correctly. I hope this is helpful for somebody to understand the process.

Dear all, I am keen to explore if it is possible (either with ODBC or ODBEleven Long coding) the lights on my Octavia Scout. My new car (2019 Skoda Octavia Scout TDi 184 DSG) has excellent LED headlights, but the fog lights are a waste of time (and get completely lost light wise with the LED headlamps). Has anybody tried/attempted to upgrade their fog lamp units to the style of lights using in the VRS (ie LED Fog Lamps)? My backup plan is to upgrade the front fog lights to LED lamps, but wanted to see if it was even possible to do the lamp upgrade (add it onto my list of growing upgrades!!!) Many thanks Max