Skip to content

All Activity

This stream auto-updates

  1. Past hour

  2. danjeyd joined the community
  3. Yigit42 started following MustafaYuqsel
  4. A faulty egr cooler would make the coolant and tank change colour from the soot at least that's why hours of Google searching is telling me , im hoping its that and not the head gasket on mine. As yours not got a leaking hose somewhere ? Also have you tried the charge air cooler ?
  5. I'm replying to this as I have posted a similar issue on the Kamiq forum. Car went into Gearbox Emergency Mode. Dealer replaced mechatronic unit under extended warranty. However, it happened again several months later. This time Skoda said that car required a clutch adjustment so they would not be covering this under the warranty. I said I'd like a second opinion diagnostic test by a speciialist garage, but told that if I did that Skoda would invalidate that section of my warranty!!!!
  6. There is a setting at 11 0'clock that folds the mirrors Lee. The remote doesn't work for the mirrors as it used to. I always use the fob to fold mirrors when parking in a public car park.. Have done since I bought the lady 10 years ago .
  7. Thanks Kenny. I must have used the wrong combination of words.
  8. Just to clarify, my car does not have factory-installed navigation. I’m trying to activate it myself. Regarding the VCRN, does it really show as 1234 on all MIB3 units, or could this indicate a problem with my unit? I just want to make sure this is normal. I’ve also ordered an OBD2 diagnostic device. Do you think it will be possible to retrieve the actual VCRN using it? If so, could you explain how or which software I would need? Thanks for your help!
  9. I think you’d really struggle to get at the bottom one. It’s not difficult to get the air intake out of the road, so maybe take it off and have a feel for the lower pipe. 20mm wasn’t a tight fit at all, you should be fine with a 19mm though and maybe have a couple of spare hose clamps incase the standard clamps aren’t tight enough. No my coolant was always clean.
  10. @Danoid if you don't mind me asking, did you need to change your wiring to suit the product? I've shamelessly copied your purchase and the items arrived look like they would fit perfectly, but the plug and pins are very different sizes. My car has a very narrow plastic plug with tiny pins, and this new light has wide set larger pins. (Image for ref if it actually uplpads) Edit for topic: what have I done to my superb today. Sadly nothing 😁
  11. DRW replied to DRW's topic in Škoda Kamiq
    Further to this I thought it might be advisable to get a second opinion on the mechanical issue (not the warranty decision) so spoke to a reputable German car specialist PSC who are able to carry out a diagnostic check. Willing to do it but advised me to speak to Skoda Warranty people first. This I did. Response was that if I ask PSC to do a diagnostic check that section of my warranty will be invalidated!
  12. In that case, please state from the outset that there is no factory-installed navigation system. Yes, that display is normal for the MIB3 under the FECs; you can only access the VCRN via diagnostics.
  13. Hi beautiful people of the MKIII Superb forum, I'm currently in the unfortunate position of where my MKIII Octavia 2.0TDI Estate is looking like it is condemed after an injector failed and has potentially damaged something with the Cam. That aside I am looking into replacing it with a 2022/3 MKIII 2.0 TDI manual estate, so my question is what are the common issues with the MKIII Superb? How reliable are they? Considering I do about 45,000km. Is it fairly easy to service? I serviced my MKIII Octavia religiously. I appreciate all insight into the MKIII Superb.
  14. Hi beautiful people of the MKIV forum, I'm currently in the unfortunate position of where my MKIII 2.0TDI Estate is looking like it is condemed after an injector failed and has potentially damaged something with the Cam. That aside I am looking into replacing it with a 2022/3 MKIV 2.0 TDI manual estate, looks like I can only get the 115hp version a bit disappointing considering I've been very used to my 150hp MKIII. Rant aside what are the common issues with the MKIV? How reliable are they? Considering I do about 45,000km. Is it fairly easy to service? I serviced my MKIII religiously. I appreciate all insight into the MKIV.
  15. I did the job today, no problems at all. Updated from 270 to 308, then 332. I skipped 330. I was getting worried at one stage where it sat for a very long time seemingly doing nothing, but it did start eventually. So far I can't see any differences visually, but hopefully it will help with a few bugs I've been seeing. Thanks for all the help.
  16. Press the arrow beside LH preview screen returns full screen view.
  17. Today

  18. Thanks! I’d never really thought about this side of Skoda’s history. Pretty interesting! I just came across some photos of 1950s Skoda cars online. Not sure if they’re the exact model mentioned above but they look pretty cool and funny!
  19. I don't think I am mistaken but when I bought my Karoq SE L DSG in July this year, the rear view camera image filled the full screen when I selected reverse. For some reason, it now fills about three quarters of the screen and various icons appear down both the left hand and right hand side of the screen image making the camera view smaller. I haven't made any adjustments that I know of. So my question is have the icons at the side of the image always been there and, if not, how can I get rid of them so the image is full screen again? Thank you.
  20. One more question: Is it normal for all MIB3 units to show VCRN 1234 in the FEC details, or could this indicate a problem? All the FECs currently active on my unit are working without any issues. I also tried a forced reboot by holding down the power button until the screen turned off and came back on, but it didn’t help.
  21. All sorted by local skoda dealer The new Headlight unit was faulty and another new headlight ordered , fitted and adjusted by my local dealer under a parts warranty claim Phew
  22. Just to clarify, the factory navigation was never activated on my car. I was trying to activate it myself, which is how I discovered this issue. Everything else works perfectly, including Apple CarPlay and Android Auto. My MIB3 Preh unit has never been modified, patched or updated with unofficial software. It is still running its original software. While checking the FECs to find my VCRN and prepare a suitable navigation patch, I noticed that every FEC shows an incorrect VIN, VCRN 1234 and the date 01.01.1970. The EEPROM/eMMC issue was only a possibility suggested by ChatGPT, not a confirmed diagnosis. I’m simply trying to understand why this is happening before making any changes. If by a forced reboot you mean holding down the power button until the screen turns off and comes back on, then yes, I tried it, but it didn’t work.
  23. A sad update on this issue, after being with the mechanic for over a week, having an engine flush and oil change it appears that something under the cam cover is the cause of the ticking, potentially caused by hydro locking when the injector failed. I am going to try and get a second opinion before condemning it but it is starting to look like the end of the road for my MKIII Estate.
  24. Yes, it’s normal for the MIB3 system that data is no longer stored in plain text. The "navigation unavailable" error indicates a discrepancy between the EEPROM and the eMMC. Have you tried a forced reboot? You can patch software version 0324 yourself via USB, but you will need a diagnostic tool.
  25. Hi there! Of course I'm here because of my 2021 Octavia's infotainment system has the same weird behavior described in this topic. On yesterday I was at Skoda Service and they updated the software version to 1989. And of course it did not get resolved. On some reddit an user posted a video where he solved this issue by unmounting and replacing the sticky link below the volume bar (@mods: can I put the link to both reddit and the video here?). Just wanted to ask if someone here knows about and tried his procedure (and, of course, if it works). Thank you all, Max
  26. Lee01 replied to meee's topic in Hellos and Goodbyes
    Welcome to Briskoda 👋
  27. meee posted a topic in Hellos and Goodbyes
    Hi there 👋 I'm from Italy and joined because of my Octavia's infotainment weird behavior... 😅 Despite this, just love the car! 😍 Cheers! Max
  28. meee joined the community
  29. Source: OBDeleven screen recording dated 17 November 2026 (75.67 s). The parameters visible on screen have been transcribed in the order in which they appear. Where a field is marked “[truncated]”, the app displays only the beginning of a multi-part value. Missing portions have not been reconstructed. Header and long coding • Saved backup name: “All control units” (original: “Wszystkie jednostki sterujące”) • Backup date: 2026-11-17, 11:18 • Odometer reading: 199735 km • Module: Multifunction Module • Long coding (60 HEX characters): 000000020100066A00003F00000000000000000000000000000000000000 Adaptation – 16 channels |Channel|HEX value | |-------|--------------------------------| |2306 |62090200 | |11543 |622D1700 | |11561 |622D2900 | |11542 |622D1601 | |11558 |622D2601 | |11583 |622D3F64 | |11584 |622D4000 | |11617 |622D61000000000000 | |11618 |622D62000000000000 | |1278 |6204FE000000 | |1276 |6204FC000000 | |1296 |62051000 | |2778 |620ADA1E1E1E32323232324B4B5050| |1297 |62051100 | |1298 |62051200 | |1187 |6204A303 | Live parameters / measured values |No.|Parameter |Reading | |--:|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| |1 |Output test status |Inactive | |2 |Basic settings status |Inactive | |3 |Security Access: number of invalid keys |0 | |4 |Terminal 30 voltage |12.1 V | |5 |Engine stopped by start-stop function |OFF | |6 |Engine started by start-stop function |OFF | |7 |Terminal 15 status via CAN bus |ON | |8 |Engine status |OFF | |9 |Number of unplanned control-module resets |Watchdog Reset: 0 | |10 |Multifunction Module Application Software Version |Version Routing FCM: 7160; Software Version AFS/MXB: 0065 | |11 |Processor utilization |Total system FCM: 24%; Software component AFS MXB: 13% | |12 |Predictive Route Data Street Class |Not available | |13 |Predictive Route Data Number Of Lanes |Not available | |14 |Predictive Route Data Speed Limit |Not available | |15 |Predictive Route Data Placename Sign |Not available | |16 |Predictive Route Data Intown Flag |Not available | |17 |Headlight levelling control state |Static | |18 |Left dynamic cornering light value |Fault | |19 |Right dynamic cornering light value |Fault | |20 |Front left suspension height sensor, learned value (zero position)|-0.01 % | |21 |Rear left suspension height sensor, learned value (zero position) |46.00 % | |22 |Driving profile selection |Specified value: 0; Actual value: 0; System status: Not available; Compatibility: Yes; Switching p… [truncated] | |23 |High beam |OFF | |24 |Reverse gear status |OFF | |25 |Turn signals |Not activated | |26 |ESP intervention |Inactive | |27 |Ambient brightness |1890 lx | |28 |Low beam |OFF | |29 |Vehicle speed |0.0 km/h | |30 |Steering angle |1.20 ° | |31 |Front body deflection |0.0 mm | |32 |Rear body deflection |-17.2 mm | |33 |Left headlight range control adjustment motor, status |No fault | |34 |Right headlight range control adjustment motor, status |No fault | |35 |Left dynamic cornering light adjustment motor, specified value |32.000000 ° | |36 |Right dynamic cornering light adjustment motor, specified value |32.000000 ° | |37 |Left dynamic cornering light adjustment motor, status |No fault | |38 |Right dynamic cornering light adjustment motor, status |No fault | |39 |Variable lighting adjustment motor, front left, status |No fault | |40 |Variable lighting adjustment motor, front right, status |No fault | |41 |Left headlight range control adjustment motor, specified value |1024.0 mm | |42 |Right headlight range control adjustment motor, specified value |1024.0 mm | |43 |Switching from left-hand to right-hand traffic |OFF | |44 |Dynamic cornering lights |OFF | |45 |Front left suspension height sensor |-0.01 % | |46 |Rear left suspension height sensor |42.40 % | |47 |Light distribution status |Not activated | |48 |Front left variable lighting, specified position |204.70 % | |49 |Front right variable lighting, specified position |204.70 % | |50 |Headlight basic settings status |No command | |51 |Static cornering lights |Left static cornering light, dimming: 0.0 %; Right static cornering light, dimming: 0.0 % | |52 |LED headlight, light distribution commands |Low beam: No command issued; High beam: No command issued; All-weather lights: … [truncated] | |53 |Actual reference segment angle |Horizontal reference segment angle, left side: -500.0 ′; Horizontal reference segment angle, right side: … [truncated] | |54 |Matrix headlight, calculated offset values |Left headlight horizontal offset: -300.0 ′; Right headlight horizontal offset: -300.0 ′; Vertical offset l… [truncated]| |55 |Drift angle |-120.0 ′ | |56 |Axle offsets |Rear axle offset: -400.0 mm; Front axle offset: -400.0 mm | |57 |Matrix high-beam function status |Inactive | Advanced identification |No.|Parameter |Reading | |--:|----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| |1 |Number of programming attempts |Application: 0; Bootloader: 0 | |2 |Number of parameterization attempts |Dataset: 1 | |3 |Number of successful parameterization attempts |Dataset: 1 | |4 |Maximum number of possible software updates |Application: 65535; Bootloader: 65535 | |5 |Detected subsystems |Subsystem designation: Reserved; segment number: 4; subsystem present: Yes; subsystem … [truncated] | |6 |Busmaster / Subbusmaster identification |ECU ID: 4B; ECU Name: Multifunction Module; LOGICAL-LINK SHORT-NAME: Multifunction Module | |7 |Connected component identification |Identification number: 4B; subsystem name: Multifunction Module; Bus information / node address: A9 | |8 |Subsystem diagnostic classes |Systems, diagnostic class 3: Yes; Systems, diagnostic class 2/2F: Yes; Systems, diagnostic class 1: Yes; Syst… [truncated]| |9 |Service code and date of last software module update|Year: 0; Month: 1; Day: 1; Equipment number: 0; Importer number: 0; Partner number: 0; Programming status… [truncated] | |10 |Date of last coding |Year: 22; Month: 18; Day: 5 | |11 |FAZIT identification |Manufacturer plant code: SJ8-FST; Production date: 29.11.16; Manufacturer test station number: … [truncated] | |12 |Parameterization identification |Number of datasets: 16; AFS dataset: 04; MXB dataset: – | |13 |Diagnostic mode |VW diagnostic mode | |14 |VW / Audi part number |3Q0907338 | |15 |Software version |0285 | |16 |Serial number |29111610520147 | |17 |Hardware part number |3Q0907338 | |18 |Supplier software version |FFFF2706201612111700000000000000 | |19 |System designation |FCM MQB Low | |20 |Adaptation service code |Equipment number: 60933; Importer number: 3; Partner number: 12289 | |21 |Date of last adaptation |Year: 38; Month: 17; Day: 19 | |22 |ASAM / ODX file designation |EV_MultiModulContiVW48X | |23 |Parameter dataset part number |V03935248XG | |24 |Parameter dataset version |0001 | |25 |ASAM / ODX file version |001010 | |26 |Hardware version |001 | |27 |Vehicle equipment code |000000000000000000000058 | |28 |Coding service code |Equipment number: 31; Importer number: 770; Partner number: 73216 | |29 |Parameterization service code |Equipment number: 31; Importer number: 770; Partner number: 73216 | |30 |Parameterization date |Year: 22; Month: 18; Day: 5 | |31 |Short system designation |J745 | |32 |Software module versions |Application: 0285; Bootloader: 0106 | |33 |AUTOSAR Standard Applikationssoftwareidentification |Unknown; Software manufacturer ID: IAV GmbH; Major version number: 2; Minor version num… [truncated] | |34 |Flash update data security |Hash value: Not available; Key unlocking mechanism: Not available; Key: No; Key typ… [truncated] | |35 |Programming status |Programmable: Programmable; Program structure: Program available | |36 |EEPROM data consistency |Fault during last dataset download: No fault; Data consistency: Valid EEPR… [truncated] | Notes • “Static” is the control module’s reported status at the time of the recording, not a confirmed adaptation or coding value. In the recording, both engine status and low-beam status are OFF. • The difference between the rear sensor’s learned zero-position value (46.00%) and its current reading (42.40%) reflects two separate values shown in the recording. • The “Fault” indications for the two dynamic cornering light values should be checked against DTCs; the other adjustment motor status readings indicate “No fault”. • Date fields are reproduced exactly as raw values displayed by the application, even when they do not form a valid calendar date.
  30. pelle64 joined the community
  31. Oldchap joined the community
  32. MIB3 Preh – VCRN Showing 1234 on All FECs – What Could Be the Cause? Hi everyone, I have a 2023 Skoda Superb Scout with a Preh MIB3 infotainment unit, and I’m trying to understand an issue with its FEC/SWaP information. Here are my infotainment details: Part number: 3V0035832P Hardware: H22 Software version: 0324 Release version: MOI3_RW_SKMQB_P32400P Navigation database: 22.6 The factory navigation is currently unavailable. When I press the NAV button, the system displays “Function not available”. While checking the FEC/SWaP menu, I noticed something unusual. When I open the details of any installed FEC, the VCRN field always displays 1234. This happens with every installed FEC, not just one particular code. The important thing is that I have never modified, patched, or attempted to activate anything on this infotainment unit. As far as I know, the system is completely untouched. My questions are: Why would the VCRN display 1234 on every installed FEC? Is this a known issue with Preh MIB3 units? Could this be caused by a factory configuration problem, a software issue, or corrupted EEPROM/eMMC data? Is there a way to retrieve the actual VCRN without using VCDS or ODIS? Could this issue be related to the unavailable factory navigation? Has anyone experienced the same issue, particularly with a Preh MIB3 unit running software version 0324? I’d appreciate any technical advice or suggestions. I would prefer to understand the root cause before attempting any software modifications or activation procedures. Thanks in advance!

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.