Skip to content

MIB3 Preh – VCRN Showing 1234 on All FECs – What Could Be the Cause?

Featured Replies

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:

  1. Why would the VCRN display 1234 on every installed FEC?

  2. Is this a known issue with Preh MIB3 units?

  3. Could this be caused by a factory configuration problem, a software issue, or corrupted EEPROM/eMMC data?

  4. Is there a way to retrieve the actual VCRN without using VCDS or ODIS?

  5. 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!

C1D1453D-7CEA-4540-990D-87A5A9213DA1.jpeg

E6AB1452-0829-4728-B9A0-AFED2858A602.jpeg

F447278B-EE0D-424F-A7D3-1F0248C32A25.jpeg

4A3FA7BB-7DAD-46C7-B8BA-09497C418D0F.jpeg

B94C2C39-BF12-43C6-A4A2-B9C71D6B14F2.jpeg

0C310125-D8DC-40A2-8F6F-737B17F69BD4.jpeg

IMG_3466.jpeg

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.

  • Author

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.

  • Author

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.

Edited by Yigit42
Deleted same things

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.

  • Author
6 minutes ago, Cairus said:

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.

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!

@Yigit42 - VCRN is unique to each car - it is NOT the same for everyone.

it's a 10-digit code that is generated based on a number of things including the vehicle's VIN and MIB identifier.

the same VCRN is used across all the FECs within the car.

a different vehicle will have a different VCRN, which will apply to all its FEC codes.

A VCRN code of "1234" indicates ur VCRN is corrupted.

Edited by JR RS

I’m afraid I have to correct you. It is normal for "1234..." to appear on the MIB3—even on completely legal, official units. Furthermore, the VIN is not contained within that number; rather, the VIN is included—along with a unique identifier (VCRN)—within the FeC/SWaP code.

VW intentionally designed the display in the service menu this way.

All my MIB3 devices at home show the same display with the same date...

The VCRN is registered into the unit at the factory—essentially the radio's unique ID. Every control unit that operates using FeC/SWaP has one.

Edited by Cairus

Yes, everything is still the same, and the VIN provided is incorrect.

IMG20261118144240.heic

  • Author
42 minutes ago, igrozan said:

Yes, everything is still the same, and the VIN provided is incorrect.

IMG20261118144240.heic

If you haven’t installed any updates or patches on your MIB3 unit either, and yours also displays the same information, then I guess this is normal.

What I’m curious about is how some MIB3 users are able to see their correct VIN and VCRN in this section, while others like us only see incorrect information such as VIN and VCRN 1234. Do you know why this happens or what makes the difference?

  • Author
11 hours ago, JR RS said:

@Yigit42 - VCRN is unique to each car - it is NOT the same for everyone.

it's a 10-digit code that is generated based on a number of things including the vehicle's VIN and MIB identifier.

the same VCRN is used across all the FECs within the car.

a different vehicle will have a different VCRN, which will apply to all its FEC codes.

A VCRN code of "1234" indicates ur VCRN is corrupted.

11 hours ago, Cairus said:

I’m afraid I have to correct you. It is normal for "1234..." to appear on the MIB3—even on completely legal, official units. Furthermore, the VIN is not contained within that number; rather, the VIN is included—along with a unique identifier (VCRN)—within the FeC/SWaP code.

VW intentionally designed the display in the service menu this way.

All my MIB3 devices at home show the same display with the same date...

The VCRN is registered into the unit at the factory—essentially the radio's unique ID. Every control unit that operates using FeC/SWaP has one.

I’ve received two different explanations regarding this, and now I’m a bit confused about which one is correct.

If seeing VCRN 1234 and an incorrect VIN is a sign of corruption, how can this be fixed?

On the other hand, if this is completely normal on MIB3 units, I’m wondering why some MIB3 users can see their actual VIN and VCRN in this section, while others like me cannot.

Could someone clarify which explanation is correct?

I am speaking from my own experience. I haven’t encountered a MIB3 unit that displayed it correctly in the standard menu, though it did show up correctly in the update menu.

  • Author
9 minutes ago, Cairus said:

I am speaking from my own experience. I haven’t encountered a MIB3 unit that displayed it correctly in the standard menu, though it did show up correctly in the update menu.

That’s interesting! Do you mean the red and black update menu? If so, I’ve already checked there as well, but the information was exactly the same. It still showed VCRN 1234 and the incorrect VIN.

Is there another update menu you are referring to, or should it normally display the actual VCRN there?

I will check by my Preh MIB3

Create an account or sign in to comment

Recently Browsing 1

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.