SW update for MIB2 infotainment system?

[Tell]

Well the prize goes to @jpmedia who created a dummy patch module for me that I put in the patch folder, then ran the addFeC from the module he created - no ambiguity there . So I'm still at 1338, kept my radio presets, graphics etc etc.

That went in without an issue, FeCs appeared. I can see the map 192 download now in SWDL marked up with Y for updates now . Have Seat and Skoda navigation FeCs.

Just got to take it for a spin tomorrow to make sure it reads traffic signs OK (TSR) then I'll do the map update.... & TSR is fine.

Thanks all.

 

[MIB-Wiki]

Yea, same as suggested before.


Gesendet von iPhone mit Tapatalk

 

[Chillout]

I feel sad that we put so much time into writing down stuff here, only to hear "I'm ignoring you"... But it's a free country, and i guess some people make a good living because of stuff like this

 

[Tell]

Well

I feel sad that we put so much time into writing down stuff here, only to hear "I'm ignoring you"... But it's a free country, and i guess some people make a good living because of stuff like this

Well Mib-wiki's didn't work... came back in having found it didn't work and had JPMedia post that did work.

Mib-wiki wasn't clear whether it needed just the Skoda FeC or what. Tried the Skoda FeC but couldn't find it. Went on about back up. I had backed it up... wanted to take it from there but where.

I had an agreement with JPMedia that he was going to do the bits for me yesterday, so once something is agreed you do it. Put me in an odd situation when parties were chopping and changing about whether I should go for 1447. Chillout at one point indicating since it was a retrofit then I could run into an issues. M.I.B. documentation written as if you couldn't run it if you were not on the firmware release. Wrong. Just needs GEM above 4.1 then you can back up and start thinking about doing things.

The navigation FeC update command not clear about where the FeCs should be and whether to include the old or whether it was an update.

The problem is DEB is all in German. The 1447 release isn't documented too well since it's got live forum chatter that's superseded in the files. So you read issues... but they have been fixed.

I know two others here that want to update but having read the DEB and Mib Tools before I said anything decided not to touch it. Too complicated. I suspected they would be happy with the JPMedia approach of keeping their current release but just extending the FeCs but then I'm not sure that it is universal. Needs documenting rather than barking AddFeCs but to where etc etc etc.

I feel sad we have good software but needs to be better documented. Less use of spoilers in posts and just clear documentation with diagrams etc.

As for the statement of trying to push people to commercial retro-fitters by worrying them. Few things going on here. Poor documentation of the product and you know what.

I'm not sure whether @jpmedia want to be deluged by people wanting just the FeC upgrade to an unlisted firmware release in M.I.B. or whether the solution I got was because the retrofitter had left it not locked down to mod.

Btw just got to test TSR tomorrow.

 

[MIB-Wiki]

@Tell

Maybe you should have started with reading:

Spoiler: README.txt

NOTE:
M.I.B. is running on Harman MHI2(Q) units (MIB 2.x) only.
Minimum requirement to run M.I.B. in GEM is GEM version 4.1+
Use M.I.B. via Putty on older GEM versions or update FW.

CAUTION:
Ensure that a external power is connected to the car during any flash or programming process!
It is not recommended to flash with running engine!
Power failure during flasing/programming will brick your unit.
All you do and use at your own risk!

Prepare SD card:
Extract all files of the M.I.B. to the root directory of a clean SD-Card (FAT32 formatted is requirement!!!)
Patched IFS-stage2 images have to be placed on the SD card in the folder /patches
Pre-patched (CP, FEC and EL) ifs-root-stage2 images can be found for all recent MHI2 FW versions here: https://bit.ly/3nPIHl8
You only have to copy the folder(s) you need for your car(s) - e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH
They are already prepared in the right way, so that the tool can use them right away
In case you want to use your own patches (not recommended) - ask us first to help you:
For each SW-train a seperate folder is needed e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH
The folder has to contain the patched ifs-root-stage2 image with the following naming syntax:
"MU-version"-ifs-root-part2-"image start address in hex within RCC"-"image length in hex" --> e.g. MU1440-ifs-part2-0x00ba0000-1C06F300.ifs
image length is on byte 0x20 position 04-07 in little Endian of the original ifs-root-stage2 image (e.g. fresh from FW update)

M.I.B in Green Engineering Menu - GEM:
Insert the SD card into slot SD1 of your MHI2 unit.
Enter Engineering/Red Menu to start SW Update. Select UPDATE, select SD card, select "M.I.B. Launcher V1.0", START update.
Installtion of M.I.B. on your Unit will start. The unit will restart three time until update process is finished.
GEM will be activated as part of the installation.
SVM error has to be cleared via M.I.B. function in GEM after installation
Enter GEM on your unit and have FUN!
Select ==>>M.I.B.-More_Incredible_Bash<<==

NOTE: SD card has to be placed in unit (SD1) to enable M.I.B. in GEM. --> no SD no M.I.B.
GEM screen layout is fitted to 9.2'' screens - should work OK on 8'', but will have text cutted on smaller than 8''

Update to new M.I.B. version:
No need to reinstall M.I.B if you want to use a new version.
Just create a fresh SD with latest M.I.B. version and insert into unit.

"old" D-Link Method: Connect to MHI2 and start M.I.B.:
D-Link - e.g. DUB-E100 HW rev. D1 - USB-Ethernet adapter is required to connect to your MHI2 unit.
Use Putty/Kitty to connect via UART or Telnet (MIB IP:172.16.250.248) and login into RCC (recommended: port:123) or MMX (port:23).
Login and password for your units SW train has to be known: https://anonymousfiles.io/xzi8Nq2r/
Check your SW-train, a pre-patched ifs-root-stage2 has to be present within the folder /patches
Insert the SD card into slot SD1 of your MHI2 unit and login to the RCC shell:
# Mount SD card in slot SD1
mount -uw /net/mmx/fs/sda0/
# start M.I.B by typing
/net/mmx/fs/sda0/start

Default screen seize of Putty/Kitty is often too small to display the M.I.B. menu in full.
Increase the window seize manually.

You should see (a more colourful) menu with the following content:

******************************************************************************************************************************************
__ __ ___ ___
| \/ | |_ _| | _ )
| |\/| | | | | _ \
|_| |_|ore|___|ncredible|___/ash - V2.7.x "after easter snow"

******************************************************************************************************************************************

** 0 - Advanced Backup
Runs a full backup (RCC, MMX, EEPROM, ...) of your unit and places it into the folder /backup/"your hardware ID"

** 1 - VIM patch (199 km/h)
Writes custom Video In Motion (VIM) speed of 199 km/h (yes, too slow for German Autobahn) to your unit
Unit will automatically restart to save changes permanently

** 2 - VIM Original (6 km/h)
Writes factory default Video In Motion (VIM) speed to unit
Unit will automatically restart to save changes permanently

** 3 - IFS-ROOT-Stage2 flash patched image
Will create a backup if it was not already created before
applies patched IFS Stage 2 image - containing patched MIBRoot - to the unit
Copy FEC and EL List to Unit - like option 5
Unit will automatically restart to save changes permanently

** 4 - IFS-ROOT-Stage2 revert to Backup image
Applies original IFS Stage 2 image - containing original/stock MIBRoot - from your system backup to the unit
Unit will automatically restart to save changes permanently

** 5 - Copy FEC and EL List to Unit
Copies ExceptionList.txt and/or FecContainer.fec placed within
e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH to the unit
if no FEC and/or EL is inside /patch directory, files from /backup folder will be used

** 6 - Developer Menu activation
Developer Menu will be enabled - no need for VCP/VCDS or OBD11
Unit will automatically restart to save changes permanently

** 7 - CarPlay & Android Auto activation
Coding adaption channels for CP & AA as well as USB with iPhone support
with this, all you need for Carplay is coded, you never need some other coding tools ;-)

** 8 - Ambient Light Buttons Original
When you see this, first take a look on https://www.glaskugelservice.de/codierung/ambientbeleuchtung
it is some special coding only for Skoda Octavia 5E, yet!

** 9 - Ambient Light Buttons patch (first, set to Original)
When you see this, first take a look on https://www.glaskugelservice.de/codierung/ambientbeleuchtung
it is some special coding only for Skoda Octavia 5E, yet!

** F - Fix SVM error
Fix SVM Fault on Unit

** G - Install M.I.B. in GEM
Install M.I.B. for use in GEM on Unit

** O - Set OBD Status
Prevent Unit from OBD

** U - Mount USB writeable
makes USB devices writeable

** W - Mountpoints writeable
make some Mounts writeable on the unit

** R - Reboot Unit
restart the Unit

** C - cleanup Logs
delete all inside /log directory

** S - show Log (press Q for exit view)
show all our Logs from this Unit

** H - Help
this here...

** L - GPL License
please take a look and note our license

******************************************************************************************************************************************

Patch Info:
All patches ifs-root-stage2 files in /patches/ (https://bit.ly/3nPIHl8) contain the following patches - all-in-one file:
CP - Component Protection removed
EL - ExceptionList.txt signature check removed (already prepared and part of each patch)
FEC - FECContainer.fec signature check removed
EL patch will re-enable the installation of MIB2Toolbox on latest FW version, as the removed signature check also applies to the POI upload process.

NEW - FEC Generator:
M.I.B is now generating custom FecContainer.fec files based on existing FecContainer.fec and addfec.txt in patch folder.
addfec.txt can be edited with any ASCII editor (Notepad++). Only not yet existing FECs will be added to container during the process.
No need to change FECContainer.fec with WhatTheFec tool. Original FECs in container will continue to work even without patch on unit.
It is recommended to switch to this method and replace existing ExceptionList.txt with original (empty) versions.
Just run "Add new Fecs to FecContainer.fec" script in M.I.B -> PATCH.

Supporting Documents:
https://mibsolution.eu/#/1/9
user: guest
pass: guest

CONTACT:
mailto: [email protected]
Telegram Channel: https://t.me/joinchat/EHt4RRksHcMQk6Xi6tFaBw

Get in contact with us to get support and provide feedback about M.I.B.

The basics, even how to create a "dummy folder" for your FW is in there, also a discription about how to work with addfec.txt
+ all the already included patches it does not take rocket science to get this
+ you could have asked directly

Google Translation of DEB is also very readable...
1st post contains all the information required to update to 1447.
Also this thread has them all further up.

To the other people here struggling with updating and patching.
Making a new patch for a so far not supported FW version only takes a few minutes, after we have a M.I.B backup of that unit.

Get in contact

 

[Walone]

THis error is related to a technisat conversion? meanin install 05xx software on 02 xx 03xx 04xx hW revision units?

If Technisat can be NAV CID CFG file, or conversion .if patched over sd update with right prepared files and later rerun fw update error gone away...

It's not a Technisat unit, it's a Harman MIB2, HW42, originally SW0319 then updated in stages, 0674, 0818, 0897, 1219 then I had the FEC's 'modded' and it then showed that 1556 error. When the FEC 'expired' I had new maps installed by a 'retrofitter' and SW1409 installed.

 

[MIB-Wiki]

Try installing M.I.B and create an advanced backup, share this with me (PN).

You want to stay on the current FW and just fix your FECs? Or also update?

1556 indicates, that you have Mixed FW versions installed on your unit. A full SWDL FW Update should fix it.


Gesendet von iPhone mit Tapatalk

 

[Tell]

@Tell

Maybe you should have started with reading:

Spoiler: README.txt

NOTE:
M.I.B. is running on Harman MHI2(Q) units (MIB 2.x) only.
Minimum requirement to run M.I.B. in GEM is GEM version 4.1+
Use M.I.B. via Putty on older GEM versions or update FW.

CAUTION:
Ensure that a external power is connected to the car during any flash or programming process!
It is not recommended to flash with running engine!
Power failure during flasing/programming will brick your unit.
All you do and use at your own risk!

Prepare SD card:
Extract all files of the M.I.B. to the root directory of a clean SD-Card (FAT32 formatted is requirement!!!)
Patched IFS-stage2 images have to be placed on the SD card in the folder /patches
Pre-patched (CP, FEC and EL) ifs-root-stage2 images can be found for all recent MHI2 FW versions here: https://bit.ly/3nPIHl8
You only have to copy the folder(s) you need for your car(s) - e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH
They are already prepared in the right way, so that the tool can use them right away
In case you want to use your own patches (not recommended) - ask us first to help you:
For each SW-train a seperate folder is needed e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH
The folder has to contain the patched ifs-root-stage2 image with the following naming syntax:
"MU-version"-ifs-root-part2-"image start address in hex within RCC"-"image length in hex" --> e.g. MU1440-ifs-part2-0x00ba0000-1C06F300.ifs
image length is on byte 0x20 position 04-07 in little Endian of the original ifs-root-stage2 image (e.g. fresh from FW update)

M.I.B in Green Engineering Menu - GEM:
Insert the SD card into slot SD1 of your MHI2 unit.
Enter Engineering/Red Menu to start SW Update. Select UPDATE, select SD card, select "M.I.B. Launcher V1.0", START update.
Installtion of M.I.B. on your Unit will start. The unit will restart three time until update process is finished.
GEM will be activated as part of the installation.
SVM error has to be cleared via M.I.B. function in GEM after installation
Enter GEM on your unit and have FUN!
Select ==>>M.I.B.-More_Incredible_Bash<<==

NOTE: SD card has to be placed in unit (SD1) to enable M.I.B. in GEM. --> no SD no M.I.B.
GEM screen layout is fitted to 9.2'' screens - should work OK on 8'', but will have text cutted on smaller than 8''

Update to new M.I.B. version:
No need to reinstall M.I.B if you want to use a new version.
Just create a fresh SD with latest M.I.B. version and insert into unit.

"old" D-Link Method: Connect to MHI2 and start M.I.B.:
D-Link - e.g. DUB-E100 HW rev. D1 - USB-Ethernet adapter is required to connect to your MHI2 unit.
Use Putty/Kitty to connect via UART or Telnet (MIB IP:172.16.250.248) and login into RCC (recommended: port:123) or MMX (port:23).
Login and password for your units SW train has to be known: https://anonymousfiles.io/xzi8Nq2r/
Check your SW-train, a pre-patched ifs-root-stage2 has to be present within the folder /patches
Insert the SD card into slot SD1 of your MHI2 unit and login to the RCC shell:
# Mount SD card in slot SD1
mount -uw /net/mmx/fs/sda0/
# start M.I.B by typing
/net/mmx/fs/sda0/start

Default screen seize of Putty/Kitty is often too small to display the M.I.B. menu in full.
Increase the window seize manually.

You should see (a more colourful) menu with the following content:

******************************************************************************************************************************************
__ __ ___ ___
| \/ | |_ _| | _ )
| |\/| | | | | _ \
|_| |_|ore|___|ncredible|___/ash - V2.7.x "after easter snow"

******************************************************************************************************************************************

** 0 - Advanced Backup
Runs a full backup (RCC, MMX, EEPROM, ...) of your unit and places it into the folder /backup/"your hardware ID"

** 1 - VIM patch (199 km/h)
Writes custom Video In Motion (VIM) speed of 199 km/h (yes, too slow for German Autobahn) to your unit
Unit will automatically restart to save changes permanently

** 2 - VIM Original (6 km/h)
Writes factory default Video In Motion (VIM) speed to unit
Unit will automatically restart to save changes permanently

** 3 - IFS-ROOT-Stage2 flash patched image
Will create a backup if it was not already created before
applies patched IFS Stage 2 image - containing patched MIBRoot - to the unit
Copy FEC and EL List to Unit - like option 5
Unit will automatically restart to save changes permanently

** 4 - IFS-ROOT-Stage2 revert to Backup image
Applies original IFS Stage 2 image - containing original/stock MIBRoot - from your system backup to the unit
Unit will automatically restart to save changes permanently

** 5 - Copy FEC and EL List to Unit
Copies ExceptionList.txt and/or FecContainer.fec placed within
e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH to the unit
if no FEC and/or EL is inside /patch directory, files from /backup folder will be used

** 6 - Developer Menu activation
Developer Menu will be enabled - no need for VCP/VCDS or OBD11
Unit will automatically restart to save changes permanently

** 7 - CarPlay & Android Auto activation
Coding adaption channels for CP & AA as well as USB with iPhone support
with this, all you need for Carplay is coded, you never need some other coding tools ;-)

** 8 - Ambient Light Buttons Original
When you see this, first take a look on https://www.glaskugelservice.de/codierung/ambientbeleuchtung
it is some special coding only for Skoda Octavia 5E, yet!

** 9 - Ambient Light Buttons patch (first, set to Original)
When you see this, first take a look on https://www.glaskugelservice.de/codierung/ambientbeleuchtung
it is some special coding only for Skoda Octavia 5E, yet!

** F - Fix SVM error
Fix SVM Fault on Unit

** G - Install M.I.B. in GEM
Install M.I.B. for use in GEM on Unit

** O - Set OBD Status
Prevent Unit from OBD

** U - Mount USB writeable
makes USB devices writeable

** W - Mountpoints writeable
make some Mounts writeable on the unit

** R - Reboot Unit
restart the Unit

** C - cleanup Logs
delete all inside /log directory

** S - show Log (press Q for exit view)
show all our Logs from this Unit

** H - Help
this here...

** L - GPL License
please take a look and note our license

******************************************************************************************************************************************

Patch Info:
All patches ifs-root-stage2 files in /patches/ (https://bit.ly/3nPIHl8) contain the following patches - all-in-one file:
CP - Component Protection removed
EL - ExceptionList.txt signature check removed (already prepared and part of each patch)
FEC - FECContainer.fec signature check removed
EL patch will re-enable the installation of MIB2Toolbox on latest FW version, as the removed signature check also applies to the POI upload process.

NEW - FEC Generator:
M.I.B is now generating custom FecContainer.fec files based on existing FecContainer.fec and addfec.txt in patch folder.
addfec.txt can be edited with any ASCII editor (Notepad++). Only not yet existing FECs will be added to container during the process.
No need to change FECContainer.fec with WhatTheFec tool. Original FECs in container will continue to work even without patch on unit.
It is recommended to switch to this method and replace existing ExceptionList.txt with original (empty) versions.
Just run "Add new Fecs to FecContainer.fec" script in M.I.B -> PATCH.

Supporting Documents:
https://mibsolution.eu/#/1/9
user: guest
pass: guest

CONTACT:
mailto: [email protected]
Telegram Channel: https://t.me/joinchat/EHt4RRksHcMQk6Xi6tFaBw

Get in contact with us to get support and provide feedback about M.I.B.

The basics, even how to create a "dummy folder" for your FW is in there, also a discription about how to work with addfec.txt
+ all the already included patches it does not take rocket science to get this
+ you could have asked directly

Google Translation of DEB is also very readable...
1st post contains all the information required to update to 1447.
Also this thread has them all further up.

To the other people here struggling with updating and patching.
Making a new patch for a so far not supported FW version only takes a few minutes, after we have a M.I.B backup of that unit.

Get in contact

Except Google blocked me from translate for a day, suspicious activity... only DEB translation from German to English achieved the block. You didn't respond to my request of screen shots of MIB Tools. Posted unreadable ones up on here and thought they were fine.

I know I'm talking to the documentor of project but really it needs to be much clearer and questions should be answered.

 

[Walone]

Try installing M.I.B and create an advanced backup, share this with me (PN).

You want to stay on the current FW and just fix your FECs? Or also update?

1556 indicates, that you have Mixed FW versions installed on your unit. A full SWDL FW Update should fix it.


Gesendet von iPhone mit Tapatalk

Thanks for the quick reply, much appreciated! I'm not in a hurry to do anything at the moment, haven't got the time anyway. I also need to have a good read of all the info and try to understand it, LOL

 

[Walone]

Except Google blocked me from translate for a day, suspicious activity... only DEB translation from German to English achieved the block. You didn't respond to my request of screen shots of MIB Tools. Posted unreadable ones up on here and thought they were fine.

I know I'm talking to the documentor of project but really it needs to be much clearer and questions should be answered.

I think some of the problems with the unreadable images may stem from @MIB-Wiki using Tapatalk, not sure though.

 

[jpmedia]

As MIB-Wiki said its to do a full swdl install selecting all, enable develeper mode, enter servicemenu tap on swdl then start manual download select all.
Had to do 3 Times on a upflashed H41 sw0123 to 1447.

 

[Tell]

Mib Tools installed fine for me but unlike a map upload via SWDL.... The bar moves quickly, the reboots are slow during Mib Tool installation, main thing is to keep the power on, engine running or power charger if a weak battery, but only a 5 minute activity in reality.

Now loading up 192 maps.

The FeC update screen:

Note the clear SVM hangs off that screen (haven't tried that yet).

Wow success:

Thanks again.

 

[MIB-Wiki]

@Tell

check https://bit.ly/3nPIHl8 for updated README.txt and high-res pictures of menu structure

 

[Tell]

@Tell

check https://bit.ly/3nPIHl8 for updated README.txt and high-res pictures of menu structure

It's always been like that. It's not one of the new crystal clear screens they subsequently moved to. Probably VW old stock. Dates to 2016, same as the Tiguan at that time.

Ok here in the readme.txt file it says

"You only have to copy the folder(s) you need for your car(s) - e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH "

Well that's miss direction on poor English translation. All preconfigured patches are already prepared and in the folder. You don't need to do anything else if using one of your prepared files.

If however you supply a custom file as Jpmedia did since I wasn't upgrading firmware then it goes in the patch location. Other than that, use the prepared files. The specific one for your firmware is picked up automatically if it exists.

The text in the read me to Mib Tools if a patch doesn't exist as yet on to how to make your own is above the average person:

In case you want to use your own patches (not recommended) - ask us first to help you:
For each SW-train a seperate folder is needed e.g. /patches/MHI2_ER_SKG13_P4526_MU1440_PATCH
The folder has to contain the patched ifs-root-stage2 image with the following naming syntax:
"MU-version"-ifs-root-part2-"image start address in hex within RCC"-"image length in hex" --> e.g. MU1440-ifs-part2-0x00ba0000-1C06F300.ifs
image length is on byte 0x20 position 04-07 in little Endian of the original ifs-root-stage2 image (e.g. fresh from FW update)

So yes it's not recommended you have to do it for the user once that back up is supplied via the web link so you can manufacture it and put it in the patch folder. Now that is recommended .

The patch is either the fix where you just use addfecs but don't import the patch since its already in the memory or you do the two part thing if you had the software release. Like option 1 above in my final edited stuff. Option 2 is keep your firmware and seek a patch if one doesn't exist.

 

[Tell]

run addfec . without prepared folder wont work also...

Very true. Thanks again to @jpmedia for preparing for me. That then is placed in the upload directory as if part of the project on the SD card of MIB Tools. So anybody tracking this route needs someone like Jpmedia to deal with firmware that isn't in MIB Tools / M.I.B. database. It determine which firmware you are running from the backup. The statement just use AddFeCs isn't enough need the module created for you unless you work out how it all hangs together yourself. That would be re-inventing the concept of packages. That goes in as a Mib Patch Ifs-Root under patches. Same location as the already prepared patches are held. See FeC update screen above.

As far as part 4 and the upload is concerned, appears the presence of the Skoda navigation FeC triggers the firmware to take the Skoda part number route on the map import. Feature of how the firmware works.

Note. Don't have kittens if you use a USB SD adaptor on your PC with Mib-tools on, plug the USB in and turn your PC on. Mine tried to boot off it. Must have a boot sector on it created by your Mib unit. Skip past the boot drive.

 

[rageuk]

Help,

I’ve done a software update to my taracco unit and also a map update and have a couple of fault codes that don’t seem to want to go away.

I’ve got the
B126CF2 navigation database not enabled
B201A00 version management

I’ve looked at the many posts and checked the confirmation of changes which gives current value of key BD9A if I’ve read the posts correctly the code I should enter is 7448 as the new key. When I do this it says writing and never changes I’ve left it for 10 minutes but nothing. I’m using iOS with OBDeleven

What am I doing wrong?

 

[Dudept]

Is there any way to add performance menu to my unit? I dont have obd11 just vcds. I got the fec on and on vcds its on but dont show up

Enviado do meu Redmi Note 9 Pro através do Tapatalk

 

[Tell]

Help,

I’ve done a software update to my taracco unit and also a map update and have a couple of fault codes that don’t seem to want to go away.

I’ve got the
B126CF2 navigation database not enabled
B201A00 version management

I’ve looked at the many posts and checked the confirmation of changes which gives current value of key BD9A if I’ve read the posts correctly the code I should enter is 7448 as the new key. When I do this it says writing and never changes I’ve left it for 10 minutes but nothing. I’m using iOS with OBDeleven

What am I doing wrong?

They get nested sometimes so you have to chase them down. I'd agree with your confirm code. Time since I bothered to clear one but I'd check that if using Obdeleven you enter in lower case.... something rings a bell about that. Getting a 10 seconds reboot in. Another scan and keep at it.

My text on it:

OBDeleven Tool for VCDS type of activity... working ones for the Ateca

Great straight to the point answers and fast uploaded examples. FIS Carbon (which version did you pick?) Will wait until you have done Lap timer and tested. Pointer will be doing on the weekend thanks for instructions Looking for Tyre pressure coding was for this...

www.seatcupra.net

Your first one is the result of the "workaround" method aka using the overall.nds release linked to first card put in the infotainment unit which it registered against, just the release. Moving that file makes the system work but it does put that flag up. I do suggest that you do a reboot before putting in a modified release so you dont shock the system by changing live data it's using. 20 mins to power down if you dont reboot. I also suggested reverting back to the release.... Never tried it.

In reality nobody is interested in those codes in a dealership. Other fish to fry.

 

[MIB-Wiki]

Help,

I’ve done a software update to my taracco unit and also a map update and have a couple of fault codes that don’t seem to want to go away.

I’ve got the
B126CF2 navigation database not enabled
B201A00 version management

I’ve looked at the many posts and checked the confirmation of changes which gives current value of key BD9A if I’ve read the posts correctly the code I should enter is 7448 as the new key. When I do this it says writing and never changes I’ve left it for 10 minutes but nothing. I’m using iOS with OBDeleven

What am I doing wrong?

You have a MHI2 unit?

Try to use SVM fix from M.I.B.

For the navigation database... Try to install again...

 

[Tell]

You have a MHI2 unit?

Try to use SVM fix from M.I.B.

For the navigation database... Try to install again...

They have mib2 standard by deduction. The mib2 high was never put on UK Tarracos and that error is caused by moving the overall.nds file. The method was developed here by Exciter (Stephan) in early 2017... Other boards cribbed it . Slightly amusing when you see they are late to the party. Also of the many people that did the workaround only those with VCDS / Obdeleven etc knew that it left a trail. I note the German boards know that now.