Translated from German to English - www.onlinedoctranslator.

com
Table of contents
1 Introduction ............................................... .................................................. ................................................ 2

2. Optional: Firmware update ................................................ .................................................. .................. 3

2.1. Activation of the engineering mode with VCDS ................................................ ................................ 3

2.2. Import firmware update................................................ .................................................. ........ 4

3. Preparatory measures for the patch......................................... ................................................ 5
3.1. Required software for the patch................................................. .................................................. 5

3.2. Installation Linux (under Windows 10) ................................................ ................................................ 5

3.3. Creating a working directory................................................. ....................................... 6

3.4. Installation dumps ................................................ .................................................. ................... 6

4. Access to the console ........................................ .................................................. ................................ 7

4.1. Utensils needed................................................................ .................................................. ................... 7

4.2. Passwords Audi Europe................................................. .................................................. ............. 7

4.3. Login options on the MIB ..................................................... .................................................. .. 7

5. Backup/Dump MIB ............................................ .................................................. ................................ 8th

6. Patch MIBRoot ........................................ .................................................. ................................ 9

6.1. Extracting the MIBRoot file ................................................ .................................................. .... 9

6.1.1. Extraction of ifs-root-part2.ifs from file rcc_fs0..................................... ................... 9

6.1.2. Extracting the MIBRoot file from the new.ifs file ........................................ ................ 11

6.2. Patch MIBRoot ................................................ .................................................. ..................... 14

6.3. Integrate Patch................................................ .................................................. ...................... 22

7. Install patches................................................ .................................................. ....................... 23

8. Adaptation of FecContainer................................................. .................................................. ................... 24

8.1. List of FEC codes ........................................ .................................................. .................... 24

8.2. FEC code for card support........................................................ ....................................... 24
8.3. Creating a new FEC file with WhatTheFec ................................................ ........................ 25
8.4. Copying the customized FEC file to the MIB ........................................ ............................ 26
9. Adaptation control unit 5F ................................................ .................................................. ................. 27

MIB1 MIB Root Patch Page2from27

1 Introduction

This Quick Start Guide is largely based on the wonderful work of the authors of the
InstructionMIB2.pdf and MIB2_Patch_EN_v0.7.pdf files, some information has been
omitted and little has been added. The credits therefore go to the authors of these
documents!

The purpose of this document is to demonstrate the theoretical possibility of modifying

firmware to accept generated Feature Enabling Codes (FECs) without a signature. Except for
test purposes, it should therefore not be used.

MIB1 MIB Root Patch Page3from27

2 Optional: firmware update

Everyone has to decide for themselves whether a firmware update should definitely be carried
out on the vehicle. In principle, a backup of the existing software is sufficient for patching the
MIB.

2.1 Activation of Engineering Mode with VCDS

This step isoptionalrequired if the "friendly" has set access to the engineering mode to
"not active" during an update.

The key combinations to switch to Engineering Mode vary depending on the year of
manufacture and the vehicle.

On the 2016 Audi A3 8V Sportback it works as follows:

- Switch to the CAR menu (press the menu button, go to the CAR setting)

- Press the key combination BACK + upper left function key (next to the multi-wheel) at the same
time.

- After a few seconds, the so-called RED menu appears

If it doesn't work immediately, try several times. Pressing them at the same time doesn't
always work immediately. However, if it does not work at all, then the engineering mode
must be enabled via VCDS/VCP etc.

Basically, the desired setting is in control unit 5F. However, in the example vehicle, the
parameter IDE02122 Developer Mode is not active. The attempt to set this to active is
acknowledged with an error (invalid value). VCDS does not show any code under Access
Permissions. Even when entering the security number "20103", which is acknowledged
as valid, the behavior does not change.

The following steps are necessary once for VCDS to display the developer code:
• Note the VAG number in the STG 5F (top left). In my case "8V0 035 019".
• In the Labels directory (C:\Ross-Tech\VCDS-DRV\Labels) look for the file corresponding to
the installed MMI, in my case 8V0-035-MIB-HIGH1.clb. Duplicate the file and rename it to
the controller's name, i.e. 8V0-035-019.clb.
• Restart VCDS
• Select STG 5, the necessary code should now appear under ACCESS
AUTHORIZATION 16, in my case "S12345"

MIB1 MIB Root Patch Page4from27

The following coding is to be used :

1 Select STG 5F (information electronics).

2 Select ACCESS AUTHORIZATION 16 function, enter the displayed code
3 ADJUSTMENT 10 function
4 Under SEARCH/FILTER, enter the keyword "developer mode" Under
5 ADJUSTMENT CHANNEL select the following item:
1.1 IDE02122: Developer Mode
6 Under NEW VALUE, select the keyword "active" and confirm by clicking on the
Apply button.

2.2 Import firmware update

Firmware update steps:

a Prepare SD card with firmware image, should look something like this:

b Checking that the new version lists the current firmware version under "Supported
Trains". This information can be found in the metainfo2.txt file.

c Switch to engineering mode

ca For Audi A3 8V 2016: MENU – CAR – key combination BACK + top function
key next to the steering wheel.

d Select Update in Engineering Mode and follow the prompts

e When the update is complete, the setup asks for the new firmware information to
be uploaded to the manufacturer's server. Cancel this query.

MIB1 MIB Root Patch Page5from27

MIB1 MIB Root Patch Page6from27
3 Preparatory measures for the patch

3.1 Required software for the patch

Operating system: Windows 7 or higher (commercial product)

Telnet: eg Puttyhttps://www.putty.org/

Dumpifs:https://github.com/askac/dumpifs

Linux:

- Virtual Linux or full installation on the hardware

- on Windows 10: Microsoft Store: Ubuntu

Disassembler with ARM support (e.g. IDA Pro or Ghidra):

- IDA Pro:https://www.hex-rays.com/products/ida/ (commercial product)

- Ghidra:https://ghidra-sre.org/

IFSTool: not freely available

WhatTheFec: not freely available

Hex editor: e.g. HxDhttps://mh-nexus.de/de/hxd/

XOR calculator:http://mib-helper.com/im-so-xory/

VCDS/VCP or similar tools for error clearing in control unit 5F:

- VCDS:https://www.ross-tech.com/vag-com/ (commercial product)

3.2 Installation Linux (under Windows 10)

Preliminary remark: This step is not necessary if the tool IFSTool.exe is used, firmware for
the MIB is available and no dump of rcc_fs0 should serve as a basis. In my opinion, it is
better to start with a dump. After all, this information comes from the functional vehicle.

A Linux environment is required to work with the dumpifs tool. Windows 10 offers an
easy way with the subsystem for Linux. However, it is also possible with a fully installed
Linux. The subsystem is used below.

On Windows 10, install the Windows Subsystem for Linux (Control Panel -> Programs and
Features), then restart the computer.

In the next step, install Ubuntu (development tools for the command line) from the
Windows Store.

After installation click on the Open button. A terminal window opens. Enter a username
and password there.

MIB1 MIB Root Patch Page7from27

After a successful login at the command line, run the following commands:

O sudo apt update && sudo apt upgrade

O sudo apt install libucl1 libucl-dev liblzo2-2 liblzo2-dev

3.3 Creating a working directory

We create a working directory in Windows Explorer or on the command line of Windows

(not Ubuntu). Since this directory will also be accessed under Ubuntu, a short name makes
sense.

O c:

O CD \

O mkdir a

3.4 Installation dumps

Preliminary remark: This step is not necessary when working with the IFSTool.exe tool.

After downloading dumpifs from askac's Github repository, unzip the dumpifs ZIP
archive in the working directory (aka c:\a).

MIB1 MIB Root Patch Page8thfrom27

4 Access to the console

4.1 Utensils Required

- Laptop with network port

- Supported USB network card

O D-Link DUB-E100 HW rev. D1 (0x2001, 0x1a02)

O The following ID should also be compatible (not tested):

§ (0x2001, 0x3c05), (0x2001, 0x1a02), (0x0424, 0x9500), (0x2721, 0xec00),

0x1e2d, 0x0055), (0x1e2d, 0x0060)

- In some vehicles, an adapter cable from the Audi Multimedia Interface -> USB is
required. The other USB sockets are usually marked as "charge only" and cannot
be used.

- Telnet program

4.2 Passwords Audi Europe

There are a number of different passwords for the different vehicles of the VW Group,
most of the access data can be found with a little internet research. Below is a brief list for
the example vehicle:

MU version brand firmware version Hash pw

0356 Audi A3 MHIG_EU_AU_P1531 lVgttd5Ve94w6 eQQYUkCS
0397 Audi A3 MHIG_EU_AU_K1544 lVgttd5Ve94w6 eQQYUkCS
0404 Audi A3 MHIG_EU_AU_K1549 lVgttd5Ve94w6 eQQYUkCS

4.3 Login options on the MIB

The MIB unit offers 2 ways to log in via Telnet. Each of its main components - MMX and
RCC - has its own access. The RCC component is interesting because it contains the
MIBRoot and FecContainer.fec files.

RCC MMX
IP4: 172.16.250.248 IP4: 172.16.250.248
Port: 123 port: 23
Users: root Users: root
Password: see above Password: see above

MIB1 MIB Root Patch Page9from27

MIB1 MIB Root Patch Page10from27
5 Backup/Dump MIB

Creation of a backup of the original MIB software. After successful login to the MIB RCC,
please back up the following files:

- EEPROM

- FecContainer.fec

- Variant.txt

- RCC

- MMX

To do this, run the following commands in the terminal:

O mount -uw /net/mmx/fs/sda0/

O on -f rcc /usr/apps/modifyE2P r 0 10000 > /net/mmx/fs/sda0/eeprom.txt

O cp -r /net/rcc/mnt/efs-persist/FEC/FecContainer.fec /net/mmx/fs/sda0/FecContainer.fec

O cp -r /net/rcc/mnt/efs-persist/SWDL/Variant.txt /net/mmx/fs/sda0/Variant.txt

O cat /net/rcc/dev/fs0 > /net/mmx/fs/sda0/rcc_fs0

O cat /net/mmx/dev/fs0 > /net/mmx/fs/sda0/mmx_fs0

Then transfer the files from the SD card to a safe location. The files "rcc_fs0" and
"FecContainer.fec" are needed in the next steps.

MIB1 MIB Root Patch Page11from27

6 Patch MIB Root

There are different ways of patching the ifs-root.ifs container. The method presented
below is based on the fact that hash value checking is switched off. This means that
unsigned FEC files are also recognized.

6.1 Extracting the MIBRoot file

The process of extracting the MIBRoot file from the created backup, adapting it and
reintegrating it back into an IFS container so that the file can be imported to the MIB is
described below.

Of course, firmware images contain the ifs-root.ifs file. The file can be broken down into the
desired parts using the IFSTool and the "Split" function. You get the two files ifsroot-part1.ifs
and ifs-root-part2.ifs. The ifs-root-part2.ifs file is the most interesting of the two, as this file
contains the MIBRoot and FecContainer.fec files.

DANGER: Many firmware versions have multiple ifs-root.ifs files in different folders, which
have different hashes. If it is not 100% clear which ifsroot.ifs is used in the vehicle, then it is
better to go the more tedious way of extracting it from the backup! Nevertheless, at least
the file size of the ifs-root-part2.ifs file can be an important clue as to whether the correct
file size was extracted in the next step.

6.1.1 Extraction of the ifs-root-part2.ifs from the rcc_fs0 file

a Copy the rcc_fs0 from the backup location to the already created working directory c:\a

b Open the file with a HEX editor (e.g. HxD)

c Search for the beginning of ifs-root

- Most MIBs have their offset start for the second part of the ifs-root at 00BA0000.
But this is no guarantee! It is best to compare with the ifs-root-part2.ifs file. The
same applies to the offset end.

- In the example, the offset start is 00BA0000 and the offset end is 01865CDF

- Danger: In particular, the ending needs to be looked for, since it can and will be
different in each firmware.

- Select the block (offset start to offset end) via the "Edit - Select block" menu:

MIB1 MIB Root Patch Page12from27

 - Save the selection as a new file "new.ifs" via the "File – Save selection" menu (see the
following figure).

MIB1 MIB Root Patch Page13from27

6.1.2 Extraction of MIBRoot file from new.ifs file

There are two ways to extract the MIBRoot file. The first is via the Linux console using the
dumpifs tool, the second option is via the IFSTool tool. The way via the IFSTool is easier
and will be preferred in most cases.

6.1.2.1. Alternative A: Tool dumpifs

First we need to find out the offset address of the MIBRoot file as well as the file length. This is
done using the "dumpifs" tool.

To do this, we go to the Linux console, change to the working directory and execute the following
command:

Linux > ./dumpifs new.ifs

Decompressed 13391738 bytes -> 36533124 bytes

offset Size Surname

0 100 Startup header flags1=0x8 flags2=0 paddr_bias=0x7ffa00000000

100 4 startup.*

104 5c Image header

160 2528 Image directory

...

164b000 4c688 opt/sys/bin/Persistency

1698000 a66c54 usr/apps/MIBRoot

20ff000 387ec usr/apps/dev-irc

...

Checksums: image=0x8bd32d53 startup=0xfbfeaeac00000000

Image startup_size: 260 (0x104)

Image stored_size: 13393120 (0xcc5ce0)

Compressed size: 13392856 (0xcc5bd8)

Dumpifs decompresses the new.ifs file and then lists both the start offset of the contained files
and the respective file length. We are interested in the MIBRoot file, which in the example
above is in theOffset address 01698000starts and oneFile length of a66c54 having. We
remember these two values.

It should be noted that the offset address and file length refer to the decompressed/
unpacked version of the new.ifs file, which we need to create in the next step.

MIB1 MIB Root Patch Page14from27

Extract the new.ifs file:

Linux > ./dumpifs /mnt/c/a/new.ifs -f -vxd -u /mnt/c/a/new_dk.ifs

Image startup_size: 260 (0x104)

Image stored_size: 13393120 (0xcc5ce0)

Compressed size: 13392856 (0xcc5bd8)

LZO Decompress @0x104

lzo1x_decompress(buf, 9393344...)

...

Decompressed 13391738 bytes -> 36533124 bytes

The MIBRoot file can now be extracted from the decompressed file using the hex editor.

- Use the Edit - Select Block menu (CTRL E) to specify the range of data to
extract. For this we need the offset address and the file length, which we
have noted.

- In the example, the dialog would look like this:

- Save the selection as a new file "MIBRoot" via the menu "File - Save selection".

6.1.2.2. Alternative B: Tool IFSTool

With the IFSTool, the steps to extract the MIBRoot are much easier and more convenient. After
starting the tool, we load the new.ifs file and extract it by clicking on the “Extract” button. The
IFS tool now unpacks the contents of the new.ifs file into the new subfolder.

MIB1 MIB Root Patch Page15from27

If we have carried out this step in our working directory "a" on the C drive, then the
MIBRoot file can now be found in the following path:

C:\a\new\usr\apps

The MIBRoot file was extracted correctly. The only problem is if you try a direct "repack" at this
point, then the file size will vary from the original file. An extraction from the previously
unpacked new.ifs in new-unpacked.ifs failed in the version of the IFS tool available to me with
an exception error message. Therefore, the only way to do it is to integrate it later manually
using a hex editor.

The following way would be possible at this point:

Extraction of MIBRoot file from new.ifs file. Unpack the new.ifs file into new-unpacked.ifs.
Rename the new-unpacked.ifs file to new_dk.ifs (so that the file names below match).

It is important that you write down the offset address and the file length from the IFSTool
at this point - for later reintegration of the patched MIBRoot file. Otherwise, putting the
patched MIBRoot's code into the decompressed new_dk.ifs file will fail.

This means that the two files required for the rest of the process are available:
a..1 new_dk.ifs
a..2 MIB Root

MIB1 MIB Root Patch Page16from27

6.2 Patch MIB Root

Regardless of whether the path was chosen via dumpifs or via IFSTool. The original
MIBRoot file must now be available as a result. In the following steps we need a
disassembler to find out the places that need to be modified. The disassembler must
support the ARM platform.

The path using the disassembler IDA is described below. In theory, it should work just
as well with other disassemblers.

After starting IDA we create a new project:

Click on the "New" button.

In the file selection window that opens, we set the file extensions to * and select the MIBRoot file
from the working directory. IDA now recognizes the file type and presents the following window:

The preselected settings can be accepted by clicking the "OK" button. The next step may
take a while as IDA will now start disassembling the MIBRoot file.

MIB1 MIB Root Patch Page17from27

When IDA has completed the disassembly, we switch to the "IDA-View A" window if
necessary and call up the search via the "Search - Text" menu.

In the dialog that opens, “aCalculatedHash” is entered as the search string and – if not
already preselected – the “Find all occurrences” box is checked. The search is started by
clicking the "OK" button. Of course, this also takes some time.

MIB1 MIB Root Patch Page18from27

After a while, IDA presents the result of the search in the "Occurrences of:
aCalculatedHash" tab. Overall, there are two places where you have to intervene to
deactivate the FEC check.

Double-clicking on the first line (LOAD:006A4818…) opens the tree view in IDA View-
A at the relevant point in the first search result.

In this case, the tree view is not very clear, so you switch to the text view. Right-clicking
on the gray frame opens a pop-up window in which "Text view" is clicked.

MIB1 MIB Root Patch Page19from27

After that, the display in IDA View A looks like this:

First of all, the address highlighted in yellow is important. From the instruction

LOAD:006A480C MOVNE R4, #0

Must after editing

LOAD:006A480C MOVNE R4, #1

become. To do this, switch to the HEX view and get the following view:

After pressing the "F2" function key, the editing mode is enabled and the HEX values 00 40
A0 13 can be changed to 01 40 A0 13. To complete the editing, press the "F2" key again and
switch to the "IDA View-A" view, in which the result of the editing can be seen:

MIB1 MIB Root Patch Page20from27

In the next step, the following section of the first block must be changed:

LOAD:006A4880 BL MEMCMP
LOAD:006A4884 RSBS R4, R0, #1
LOAD:006A4888 MOVCC R4, #0

Will be modified to:

LOAD:006A4880 NOP
LOAD:006A4884 NOP
LOAD:006A4888 MOV R4, #1

View in hex viewbeforethe change

View in hex viewafterthe change

The end result of the first block in IDA View-A looks like this:

MIB1 MIB Root Patch Page21from27

This completes the first section. In the "Occurrences of: aCalculatedhash" tab, click on the
second occurrence of the search string.

Here the process begins again. Then make the changes according to the generated
screenshots.

First digit block 2 unmodified:

First digit block 2 modified:

Second digit block 2 unmodified

Second digit block 2 modified

MIB1 MIB Root Patch Page22from27

The end result of the second block in IDA View-A:

After completing the work in the IDA View-A window, scroll up and mark an address, see
the following excerpt:

MIB1 MIB Root Patch Page23from27

Now the patches that have been made must be saved, for this we select from the menu "Edit -
Patch program - Apply patches to input file..."

In the following dialog, I also select the "Create backup" checkbox and confirm the dialog
by clicking on the "OK" button.

If everything runs correctly, then I should find the following notice in the "Output Window" (below):

This completes the modified MIBRoot file.

MIB1 MIB Root Patch Page24from27

6.3 Integrate Patch

The goal here is to reintegrate the patched MIBRoot file into the IFS container.

The files new_dk.ifs and MIBRoot are opened in a hex editor. The entire contents of the
MIBRoot file are selected and copied to the clipboard.

Now we need the offset address and the file length of the previously extracted MIBRoot
file, which we noted. In this case it was heroffset address 01698000 and a file length of
A66C54.

In the new_dk.ifs file, select the above area using the Edit - Select Block (CTRL E) menu. Then
paste the contents of the clipboard (the contents of the new MIBRoot) (CTRL V) and save the
modified new_dk.ifs file and close the hex editor.

Finally, the new_dk.ifs file must be compressed again. The easiest way is via the IFSTool.
There we load the new_dk.ifs file and click on the “Pack” button.

If everything worked correctly, the new file new_dk-repacked.ifs and the base file new.ifs now
have the same file size. In this case it is 13392853 bytes aka 13080 kb.

Finally I renamed the new_dk-repacked file to patched_ifs.ifs.

MIB1 MIB Root Patch Page25from27

7 install patches

In the crucial step, the patched version of the second part of ifs-root.ifs is transferred to the MIB. To
do this, we place the SD card with the patched file in slot 1 of the MIB and execute the following
commands on the MIB RCC console:

O mount -uw /net/mmx/fs/sda0/

O flash unlock

O /usr/bin/flashit -v -x -d -a 0x00BA0000 -f/net/mmx/fs/sda0/patched_ifs.ifs

O flash lock

After you reboot the MMI, the patched MIB software is active and should now accept the
adjustments to the FEC file in the following chapter.

In the example vehicle, the MMI can be rebooted/reset using the key combination MENU – WHEEL
– UPPER RIGHT FUNCTION KEY.

MIB1 MIB Root Patch Page26from27

8 Adaptation FecContainer

8.1 List of FEC codes

00030000 — AMI (USB Enable)

00030001 — Gracenote
00040100 — Navigation
00050000 — Bluetooth
00060100 — Vehicle Data Interface 00060200 —
Skoda/Audi Connect, VW CarNet 00060300 —
Mirror Link
00060400 — Sport HMI (Performance Monitor)
00060500 — Sport Chrono – function unknown
00060600 — Logbook – function unknown
00060700 — Online Services
00060800 — Apple CarPlay 00060900 — Google
Android Auto 00060A00 — Baidu CarLife for iOS (China
only) 00060B00 — Baidu CarLife for Android (China
only) 00070100 — SDS (Voice Control)

00070200 — SDS (Voice Control) for Navigation

00070400 — Digital Voice Enhancement

8.2 FEC code for card support

0ABCCCDD—Cards:

A brand 2=Audi, 3=Bentley, 6=Porsche, 7=Seat, 8=Skoda, 9=VW, C=MAN

B MIB version 1=MIB1 HIGH (Harman), 3=MIB2 HIGH (Harman)
ССС region 000 = Europe, 100 = USA and Canada (NAR - North America Region), 400 = Near
East (AGCC - Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, UAE), 401 = AGCC + Turkey, 402 = AGCC
+ Israel, 500 = South Africa, 600 = Australia and New Zealand, 700 = Indie, 800 = Argentina, Brazil and
Mexico, 801 = Chile, 900 = Asia / Pacific, D00 = Rest of the World (ROW - Rest Of The World)
DD valid until year (DD is a hex value)

DD:
- 4c= 2030
- FF = ~2075/Lifetime

MIB1 MIB Root Patch Page27from27

8.3 Creation of a new FEC file with WhatTheFec

First, we load the vehicle's saved FecContainer.fec file.

The signature is green, so it can also be used on unpatched MIBs. Now we add another
FEC (here MAPS extension until 2030).

The signature is now red (invalid) and cannot be used on unpatched MIBs.

MIB1 MIB Root Patch Page28from27

8.4 Copying the customized FEC file to the MIB

After logging in to the MIB RCC, execute the following commands:

O mount -uw /net/mmx/fs/sda0/

O mount -uw /net/rcc/mnt/efs-persist

O cp -r /net/mmx/fs/sda0/FecContainer.fec /net/rcc/mnt/efs-persist/FEC/FecContainer.fec

O mount -ur /net/rcc/mnt/efs-persist

Restart the MMI via key combination (e.g. MENU/WHEEL/UPPER RIGHT FUNCTION KEY).

MIB1 MIB Root Patch Page29from27

9 Adaptation control unit 5F

After the adjustments, I found errors in the 5F control unit, including the error "Software
version management check failed" after the update in the error memory of the 5F control unit.

But since I hadn't made any changes to the type of installation, the errors could simply be
deleted with VCDS without having to resort to tools such as XORechner-XTR etc.

If changes have been made to the type of installation, then the following path leads to the goal with
VCDS:

1 Select STG 5F (information electronics).

2 Select ACCESS AUTHORIZATION 16 function, enter the displayed code
3 ADJUSTMENT 10 function
4 Under SEARCH/FILTER, enter the keyword "IDE02502" Under
5 ADJUSTMENT CHANNEL, select the following item:
1.1 IDE02502: Confirmation of installation
6 change Copy the old value under NEW VALUE
7 Two ways to arrive at an accepted new value
1.1 Sitehttp://mib-helper.com/im-so-xory/ and enter the old value and calculate a
new value
1.2 Alternatively, this also works with the XORechner-XTR tool or similar software.
8thNow accept the new value in the NEW VALUE field of VCDS and confirm the dialog.

9 The controller should now display the new value. The old value may be displayed
again. Then deleting the error memory has proven itself. However, if no design
change has been made, the old value remains. However, the error in the control
unit should have disappeared.

MIB1 MIB Root Patch Page30from27