SW update for MIB2 infotainment system?

Red_Fins · May 4, 2021

Very happy and grateful for all the advice and "how to" info on these pages.
By following the instructions I have successfully managed to update both my MIB2 software and updated to the latest navigation maps.
Big thanks to all the efforts made to putting the instructions together so that they are easy to follow (yes I know that some of it is on the spanish seat forum) but it still needed translating!
People sometimes take all this for granted and dont appreciate the effort it takes to keep this info up to date. Just wanted to say Thanks to those who regularly follow, reply, advise and udpate these threads.

Walone · May 5, 2021

Red_Fins said:
Very happy and grateful for all the advice and "how to" info on these pages.
By following the instructions I have successfully managed to update both my MIB2 software and updated to the latest navigation maps.
Big thanks to all the efforts made to putting the instructions together so that they are easy to follow (yes I know that some of it is on the spanish seat forum) but it still needed translating!
People sometimes take all this for granted and dont appreciate the effort it takes to keep this info up to date. Just wanted to say Thanks to those who regularly follow, reply, advise and udpate these threads.

Well said, too often people post for help and are given advice but don't even respond as to whether it has helped or not.

Tell · Jun 6, 2021

Anybody got the mib2 high navigation release 192 loaded on their modded units yet ?. On the navigation thread I determined that it was @Chillout who was posting with it working on Drive2 using his mib tool box project

Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1

If it's a genuine Skoda 32GB it will. Mine was made in Germany but I did import it before Brexit and the caper that would exist now on imports. Was sold as 32GB Version 2020 Skoda Gen 2 MIB2 (Amundsen 2) Card Sat Nav SD Navigation Map UK. £39 at the time, postage free February 2020. It had an...

www.seatcupra.net

(Background VAG left the Seat part number out of the map release 192 so it won't load up on stock firmware with Mapcare or regular Seat navigation FeCs.... some say Seat will fix it, doubt it myself, think they have junked Mapcare updates for Seat)

All you need is 1447 or one of the other two before + The mib tool box... I did ask for a link to the software but I think @MIB-Wiki PMed me one a few months back. Chillout doesnt say what FeCs are required....

Meanwhile Jose the Spanish Seat guy I found has it working as well on a retrofit he got done, didn't do it himself. I got him to reveal what FeCs it has in it.

So we get to this point... we don't know exactly what Jose has in his exactly but I suspect it's one of the Mega files.

There is a Digital Eliteboard thread in German which I believe may be the key ?

Support - [SEAT CUPRA] MIB2 Navi Plus AIO MHI2_ER_SEG11_P4709 MU1447_1 | CarPlay Android Auto | ifs-root EL Patch

Thema: In diesem Thema geht es um das richtige Vorgehen beim FW-Update, sowie Patchen der aktuellen SEAT MIB2 Navi Plus MHI2_ER_SEG11_P4709 MU1447 Firmware. 100% über SD Karte und alles (Patch, Kodierung, usw.) als Teil des FW Updates. AIO - Custom All-In-One FW Updates...

www.digital-eliteboard.com

Plenty of pitfalls thou and checks to be made before you start off.

It seems a patch is made after the firmware is installed, which is patched... with all desired FeCs in it. I suspect this is the one that Jose has in his. Use of Mib Tool post 133 on that. So Jose said he doesn't have it but suspect it is in the green menu unbeknown.

Never done a mib2 firmware update in my life since I have no wish to brick my unit but may be forced into it. Those with Seats have you got 192 working by following this guidance and software. Seems to be some good material in that thread. Is something else needed as well to get 192 working rather than just having mib tool loaded ?.

What about TSR, my last retrofitter made a pigs ear of getting TSR to work in MPH, took them fours hours to sort it out after changing the navigation FeCs. Any UK based people followed this with TSR. It kept reading the signs in KPH warning at half the speed. Not wanting to re-introduce this fault again.

CupraRST · Jun 7, 2021

Tell said:
Anybody got the mib2 high navigation release 192 loaded on their modded units yet ?. On the navigation thread I determined that it was @Chillout who was posting with it working on Drive2 using his mib tool box project

Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1

If it's a genuine Skoda 32GB it will. Mine was made in Germany but I did import it before Brexit and the caper that would exist now on imports. Was sold as 32GB Version 2020 Skoda Gen 2 MIB2 (Amundsen 2) Card Sat Nav SD Navigation Map UK. £39 at the time, postage free February 2020. It had an...

www.seatcupra.net

(Background VAG left the Seat part number out of the map release 192 so it won't load up on stock firmware with Mapcare or regular Seat navigation FeCs.... some say Seat will fix it, doubt it myself, think they have junked Mapcare updates for Seat)

All you need is 1447 or one of the other two before + The mib tool box... I did ask for a link to the software but I think @MIB-Wiki PMed me one a few months back. Chillout doesnt say what FeCs are required....

Meanwhile Jose the Spanish Seat guy I found has it working as well on a retrofit he got done, didn't do it himself. I got him to reveal what FeCs it has in it.

View attachment 24969
View attachment 24970

So we get to this point... we don't know exactly what Jose has in his exactly but I suspect it's one of the Mega files.

There is a Digital Eliteboard thread in German which I believe may be the key ?

Support - [SEAT CUPRA] MIB2 Navi Plus AIO MHI2_ER_SEG11_P4709 MU1447_1 | CarPlay Android Auto | ifs-root EL Patch

Thema: In diesem Thema geht es um das richtige Vorgehen beim FW-Update, sowie Patchen der aktuellen SEAT MIB2 Navi Plus MHI2_ER_SEG11_P4709 MU1447 Firmware. 100% über SD Karte und alles (Patch, Kodierung, usw.) als Teil des FW Updates. AIO - Custom All-In-One FW Updates...

www.digital-eliteboard.com

Plenty of pitfalls thou and checks to be made before you start off.

It seems a patch is made after the firmware is installed, which is patched... with all desired FeCs in it. I suspect this is the one that Jose has in his. Use of Mib Tool post 133 on that. So Jose said he doesn't have it but suspect it is in the green menu unbeknown.

Never done a mib2 firmware update in my life since I have no wish to brick my unit but may be forced into it. Those with Seats have you got 192 working by following this guidance and software. Seems to be some good material in that thread. Is something else needed as well to get 192 working rather than just having mib tool loaded ?.

What about TSR, my last retrofitter made a pigs ear of getting TSR to work in MPH, took them fours hours to sort it out after changing the navigation FeCs. Any UK based people followed this with TSR. It kept reading the signs in KPH warning at half the speed. Not wanting to re-introduce this fault again.

Hi @Tell ,
I tried to install the 0192 maps on my 2019 Cupra R ST with liefetime map updateservice. After inserting the card a message came up, telling that update files were found. I started the update, but after a long search a message came up, telling that no update files were found.
Tried again, but the same result. Tried again with new downloaded and unzipped files, still no success.

Then tried the 0189 files (coming from 0187) and these installed straight away. So there seems to be a problem with the 0192 files. I wonder if this will be repaired. I could only download the 0192 files from the provided link, could not find it anywhere on the vag sites.

Tell · Jun 7, 2021

CupraRST said:
Hi @Tell ,
I tried to install the 0192 maps on my 2019 Cupra R ST with liefetime map updateservice. After inserting the card a message came up, telling that update files were found. I started the update, but after a long search a message came up, telling that no update files were found.
Tried again, but the same result. Tried again with new downloaded and unzipped files, still no success.

Then tried the 0189 files (coming from 0187) and these installed straight away. So there seems to be a problem with the 0192 files. I wonder if this will be repaired. I could only download the 0192 files from the provided link, could not find it anywhere on the vag sites.

Yes the Seat part number 4 is missing from the 192 download which can be found in the dbinfo file. What that means is the units firmware doesn't know what to do with the download. The map upload files to the unit are sufficiently protected from users editing those files to put the part number back in and a mute point as to what else is missing even if you got the the part number in.

Those who have the 192 maps loaded on Seats use custom firmware. They have an exception list method which basically as understand it uses the correct part number, if not will then try for another and has the associated navigation FeCs for that. That's why you see in Jose's screen no Seat part number shown.

The only doubt in my mind with loading up this project software contained in the link is my last retrofitter statement "that after I do this you won't be able to load up firmware yourself". If it's original firmware you are coming from that's not an issue. Although the firmware that I'm on went in on a manufactured SD card rather than a D-link box. They did use the front camera port of the unit to read the units settings then went on to manufacture the upload via SD card for the firmware. Anyone, does that sound like the "D-link method" ?. Am I alright or has the retrofitter made things difficult for me ?.

Back to whether 192 is an aberration. I suspect it's not and Seat have dumped Mapcare. Either they badly got their wires crossed in the spec of 192 on what you are seeing. The release was manufactured six months ago as part of their testing programme, so for six months Seat knew that it didn't work on their units.... or should have known if it was a mistake. I can only think that the Seat Mapcare market was so small they opted to withdraw internally from the VAG project. Both VW and Skoda don't charge customers for Mapcare. May be it's an internal charging squabble that we are seeing. Now VAG have moved to mib3 they have no production requirement for the maps for mib2 high, just Mapcare.

Anyhow if people can comment on whether my old retrofitter has left me a problem in there way of working.

CupraRST · Jun 7, 2021

Tell said:
Yes the Seat part number 4 is missing from the 192 download which can be found in the dbinfo file. What that means is the units firmware doesn't know what to do with the download. The map upload files to the unit are sufficiently protected from users editing those files to put the part number back in and a mute point as to what else is missing even if you got the the part number in.

Those who have the 192 maps loaded on Seats use custom firmware. They have an exception list method which basically as understand it uses the correct part number, if not will then try for another and has the associated navigation FeCs for that. That's why you see in Jose's screen no Seat part number shown.

The only doubt in my mind with loading up this project software contained in the link is my last retrofitter statement "that after I do this you won't be able to load up firmware yourself". If it's original firmware you are coming from that's not an issue. Although the firmware that I'm on went in on a manufactured SD card rather than a D-link box. They did use the front camera port of the unit to read the units settings then went on to manufacture the upload via SD card for the firmware. Anyone, does that sound like the "D-link method" ?. Am I alright or has the retrofitter made things difficult for me ?.

Back to whether 192 is an aberration. I suspect it's not and Seat have dumped Mapcare. Either they badly got their wires crossed in the spec of 192 on what you are seeing. The release was manufactured six months ago as part of their testing programme, so for six months Seat knew that it didn't work on their units.... or should have known if it was a mistake. I can only think that the Seat Mapcare market was so small they opted to withdraw internally from the VAG project. Both VW and Skoda don't charge customers for Mapcare. May be it's an internal charging squabble that we are seeing. Now VAG have moved to mib3 they have no production requirement for the maps for mib2 high, just Mapcare.

Anyhow if people can comment on whether my old retrofitter has left me a problem in there way of working.

Hi @Tell ,

Thank you for explaining!
I still have the OEM firmware in the Navi Plus. So far updated the maps successfully from the original 0172 to 0176 to 0187 and now to 0189.
0192 is the first one that failed.

Could it be that, if there is a way to include the missing SEAT code in a specific 0192 file, writing it back with the same date and time stamps as original could do the trick?

SEAT is always far behind with the map updates, compared to the other VAG brands. Maybe they still don't know that this 0192 version doesn't work? After all it still isn't mentioned on their servers as far as I know.

Why would SEAT bother with making map updates impossible on already sold cars with a license, being it mapcare or lifetime? It would only make the navi system unusable within a few years......

Tell · Jun 7, 2021

CupraRST said:
Hi @Tell ,

Thank you for explaining!
I still have the OEM firmware in the Navi Plus. So far updated the maps successfully from the original 0172 to 0176 to 0187 and now to 0189.
0192 is the first one that failed.

Could it be that, if there is a way to include the missing SEAT code in a specific 0192 file, writing it back with the same date and time stamps as original could do the trick?

SEAT is always far behind with the map updates, compared to the other VAG brands. Maybe they still don't know that this 0192 version doesn't work? After all it still isn't mentioned on their servers as far as I know.

Why would SEAT bother with making map updates impossible on already sold cars with a license, being it mapcare or lifetime? It would only make the navi system unusable within a few years......

It's the SLA1 signature on the end of each metaindex2.txt protects each file from tampering / download issues. They are signed with a private key but read as valid with the public key. Not convinced that something else isn't missing from those files in the Seat part number in any case. I did spend a long time looking at those files at times.

Normally you re compute the check sums but the signed SLA1 signatures if being used on that part of the update are the stumbling block. Navigation update is one of the ones that requires the signatures to be valid. POI updates, no which is how POI developers generate update files.

The VAG public key is known whilst the private key isn't. It's the same key on all VAG products.

My journey on the subject is here:

Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1

The MIB2 cards at least have a hidden partition on them, they are special SD cards http://www.seatcupra.net/forums/showthread.php?t=388586&page=26 It was notabenem in November started this one off in post 501 with those key filenames. Then it was Exciter that found the patent to the...

www.seatcupra.net

Mathematical algorithm is used with the public key to validate the signature but you can't create the signature if you dont have the private key. All VW private keys are the same since the public key is the same. You need a fair bit of computer power, £100,000 of it was a quoted figure on sla1 signatures a few years back to decode the primary key.

I did try a published exploit which is used to get mib tools into the unit to put the part number in. I think that said exploit has limitations so it didn't work. Mib tools rides into the back of a radio station update by putting the payload after the signature.... They forgot about that one in the mib2 design. If the signature was to protect the payload above that's achieved, but not anything going in after. So whilst it works to get that code in, doing that on a big map upload it didn't. They did have teething problems getting mib tools in, you can read that online before they perfected the SD import. It generated assorted error codes.

Seat are now pretty timely with the publication of the maps. They have been known to publish quarters outside of the main six month cycle on production cars. May be if it was a terrible mistake then you might see a 193 or 194 or something. I doubt it thou.

Custom firmware is the way ahead for 192 and Seat mib2 high. I could be surprised and see Seat producing the map download and it's all been a big mistake but doubt it. As far as Mapcare is concerned that will be running out on many units which is the advantage of custom software. Mib2 updates have another four years to run following published mib1 timelines. + 5 years onto discontinuation. 2025. VW and Skoda will enjoy that.

I'm still bugged by whether a full list of FeC codes messes up TSR. I'm told by a UK retrofitter that the issue of MPH signs being read as KPH is due to too many FeCs in the payload (known issue in the retrofitter world apparently). Whilst this issue may not bother drivers in Europe or those without TSR in the UK, it would otherwise. Took my previous retrofitter all afternoon to correct it with many goodbyes and returning again 10 mins latter (speed warnings at 1/2 the legal speed are pointless). Would be interesting to hear whether any Seat UK drivers with TSR have had success with this. Intend to use a retrofitter now to manage this issue in the firmware change. Others have pointed to the FeC being a European one in the past. Previous retrofitter went back to my old settings and reloaded. That fixed it (could be they studied what was in the working FeC container file and the one they put in, corrected but said nothing of their error).... hence why professional are a good idea at times

. Mind you they introduced the problem.

Easynote530 · Jun 9, 2021

Hey ! Can someone help me with an update ?
I have some issues with CarPlay the correspondent hear in echo maybe update will resolve that

CupraRST · Jun 9, 2021

Tell said:
It's the SLA1 signature on the end of each metaindex2.txt protects each file from tampering / download issues. They are signed with a private key but read as valid with the public key. Not convinced that something else isn't missing from those files in the Seat part number in any case. I did spend a long time looking at those files at times.

Normally you re compute the check sums but the signed SLA1 signatures if being used on that part of the update are the stumbling block. Navigation update is one of the ones that requires the signatures to be valid. POI updates, no which is how POI developers generate update files.

The VAG public key is known whilst the private key isn't. It's the same key on all VAG products.

My journey on the subject is here:

Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1

The MIB2 cards at least have a hidden partition on them, they are special SD cards http://www.seatcupra.net/forums/showthread.php?t=388586&page=26 It was notabenem in November started this one off in post 501 with those key filenames. Then it was Exciter that found the patent to the...

www.seatcupra.net

Mathematical algorithm is used with the public key to validate the signature but you can't create the signature if you dont have the private key. All VW private keys are the same since the public key is the same. You need a fair bit of computer power, £100,000 of it was a quoted figure on sla1 signatures a few years back to decode the primary key.

I did try a published exploit which is used to get mib tools into the unit to put the part number in. I think that said exploit has limitations so it didn't work. Mib tools rides into the back of a radio station update by putting the payload after the signature.... They forgot about that one in the mib2 design. If the signature was to protect the payload above that's achieved, but not anything going in after. So whilst it works to get that code in, doing that on a big map upload it didn't. They did have teething problems getting mib tools in, you can read that online before they perfected the SD import. It generated assorted error codes.

Seat are now pretty timely with the publication of the maps. They have been known to publish quarters outside of the main six month cycle on production cars. May be if it was a terrible mistake then you might see a 193 or 194 or something. I doubt it thou.

Custom firmware is the way ahead for 192 and Seat mib2 high. I could be surprised and see Seat producing the map download and it's all been a big mistake but doubt it. As far as Mapcare is concerned that will be running out on many units which is the advantage of custom software. Mib2 updates have another four years to run following published mib1 timelines. + 5 years onto discontinuation. 2025. VW and Skoda will enjoy that.

I'm still bugged by whether a full list of FeC codes messes up TSR. I'm told by a UK retrofitter that the issue of MPH signs being read as KPH is due to too many FeCs in the payload (known issue in the retrofitter world apparently). Whilst this issue may not bother drivers in Europe or those without TSR in the UK, it would otherwise. Took my previous retrofitter all afternoon to correct it with many goodbyes and returning again 10 mins latter (speed warnings at 1/2 the legal speed are pointless). Would be interesting to hear whether any Seat UK drivers with TSR have had success with this. Intend to use a retrofitter now to manage this issue in the firmware change. Others have pointed to the FeC being a European one in the past. Previous retrofitter went back to my old settings and reloaded. That fixed it (could be they studied what was in the working FeC container file and the one they put in, corrected but said nothing of their error).... hence why professional are a good idea at times . Mind you they introduced the problem.

Hi @Tell , thank you again for all your efforts!
I guess it will come down to just wait and see wether SEat will bring a new working update to the 0189 maps in the next months, or not.
The way I see it SEAT can't just let down all customers that bought a new SEAT just a short time ago, some in 2020. I even think that would be illegal.

Tell · Jun 9, 2021

CupraRST said:
Hi @Tell
The way I see it SEAT can't just let down all customers that bought a new SEAT just a short time ago, some in 2020. I even think that would be illegal.

You never know. Their screens tell you that 189 is out of date but give you 189 to update too

.

If they have pulled the rug from peoples feet they could always get people to visit their dealers with valid Mapcare and upgrade the system to work with valid FeCs, the Audi ones. If it's another update of the maps that would put it at 3 months time or less since we know they have access to all quarters of the year, not just the six month ones... or they could tough it out. Personally I reckon the brand has had a strop with VAG on paying the going rate so got dropped out of the production cycle or management at Seat didn't fully understand what they were doing on the product cycle... missed the meetings

.

Either way pretty major to leave the Seat part number out of the build... not something you accidentally do. Least there is a fix for those that have retrofit software on their equipment although the hassle of getting it sorted out. For those that had the more modern incarnations of the retrofit software weathered the storm better than others that didnt'. I'm waiting for a UK based retrofitter to get it working. I have no wish to kill my box or get it beeping on MPH signs read as KPH. Been there done that... although it feels tempting at times. I'd like the ability to use Mib Tools but professionally installed... I know those that work on this detest retrofitters charging for their work.

MIB-Wiki · Jun 9, 2021

Wait as suggested by you or use M.I.B to enable supported FEC for latest maps.

M.I.B already has the SKODA Fec included for patching of Seat FW.

Alternative could be to use metainfo2 exploit and add Seat Fec to latest map update.
Somebody just would have to take the time to edit it in

.

Gesendet von iPhone mit Tapatalk

Tell · Jun 10, 2021

I can't enable Mib Tools because of the release I'm on so a catch 22 situation. Metainfo2 exploit if it went wrong would delete the FeCs that work....

Placing my bets in a retrofitter at the minute. I liken it to if your boiler went wrong would you take it apart and work on it yourself or get an expert in. Mib2 standard is all together more simple and if it's the original software you know what you are dealing with.

MIB-Wiki · Jun 10, 2021

Which train do you have installed on your unit?

How do you see a connection between metainfo2 exploit and FECs installed on your unit?

Gesendet von iPhone mit Tapatalk

Tell · Jun 10, 2021

What RCupre said at the time of a retrofitter messing up TSR in the work they did

SW update for MIB2 infotainment system?

Has anyone else had the issue of losing the driving mode screen (When you push the Cupra button) Updated mine to 346 at the weekend, Drove to work on Monday and it worked fine. Got in after work and it wouldn't bring up the selection screen when I push the Cupra button. Do you still have this...

www.seatcupra.net

Question is are UK FeCs being used (in Mib Tool) if that was the case. Adverse to driving around with TSR misreading speed signs and road conditions. My other theory was it was because they loaded the FeCs when no navigation map was valid which might fall into @RCupra first line of text. Other theory from a UK retro-fitter that I suspect RCupra works with is that too many FeCs were being presented in what the said old retrofitter was doing. Three theories on this one. It's no joke when TSR isn't working correctly.

Your second line thought you meant I should use that exploit I had already mentioned.

On 1338. I see OBDEleven people are on 1447 now shown as the latest... they hadn't till recently shown that one. Probably said software.

Walone · Jun 10, 2021

Tell said:
What RCupre said at the time of a retrofitter messing up TSR in the work they did

SW update for MIB2 infotainment system?

Has anyone else had the issue of losing the driving mode screen (When you push the Cupra button) Updated mine to 346 at the weekend, Drove to work on Monday and it worked fine. Got in after work and it wouldn't bring up the selection screen when I push the Cupra button. Do you still have this...

www.seatcupra.net

Question is are UK FeCs being used (in Mib Tool) if that was the case. Adverse to driving around with TSR misreading speed signs and road conditions. My other theory was it was because they loaded the FeCs when no navigation map was valid which might fall into @RCupra first line of text. Other theory from a UK retro-fitter that I suspect RCupra works with is that too many FeCs were being presented in what the said old retrofitter was doing. Three theories on this one. It's no joke when TSR isn't working correctly.

Your second line thought you meant I should use that exploit I had already mentioned.

On 1338. I see OBDEleven people are on 1447 now shown as the latest... they hadn't till recently shown that one. Probably said software.
View attachment 25115

Strange that you have user updates from 2012/2013?

Tell · Jun 10, 2021

Walone said:
Strange that you have user updates from 2012/2013?

Ah well I thought everybody would know what they are so didn't say

. They are the Poinspector imports. Get one each time I import user POIs.

GPS and satnav - Uploading Speed Camera (Safety Camera) & User POIs

Getting Going Overview The infotainment unit's map system comes with a set of assorted in built Points of Information (POIs) Fuel stations, cafes etc you can also add your own POIs to the internal system which is normal for navigation systems...

www.seatcupra.net

MIB-Wiki · Jun 10, 2021

Updating to latest FW 1447 is easy and safe.

Just grab your copy on mibsolution.eu

Afterwards, you can easily patch your unit with M.I.B.

22 byte file on MEGA

bit.ly

Just a SD card needed.

And update to latest maps.

Feel free to open a new thread on 1447 FW Update I‘m happy to support this for you and all the others.

BTW, there is no connection between FECs and mph or km/h, this is 100% coding/adaptions gone wrong.

Gesendet von iPhone mit Tapatalk

Tell · Jun 10, 2021

MIB-Wiki said:
Updating to latest FW 1447 is easy and safe.

Just grab your copy on mibsolution.eu

Afterwards, you can easily patch your unit with M.I.B.

22 byte file on MEGA

bit.ly

Just a SD card needed.

And update to latest maps.

Feel free to open a new thread on 1447 FW Update I‘m happy to support this for you and all the others.

BTW, there is no connection between FECs and mph or km/h, this is 100% coding/adaptions gone wrong.

Gesendet von iPhone mit Tapatalk

Thanks.

Presume the 1447 link in German I posted early is the same.

May be forced into doing it myself since the retro-fitter I had in mind hasn't a Seat unit and hasn't found one yet as a test bed they can sell on. So I'm thinking get my July trips out of the way and if I can do it myself I will and failing that get them to sort out any mess but obviously I will take the boards kind help including you.

It seems a common issue is fixing the Seat screen once the software is loaded. @Chillout did make a passing mention to that I believe. That appears on the German board. So obviously a good idea to find that (again).

Car image in infotainment

Is there any why to pick inside the current firmware for stored images ? Or Extract them, edit via photoshop and put back

Sent from my SM-G965F using Tapatalk

www.seatcupra.net

I think with that lined up when you can't read the screen that should bring it back.

I did find another thread on TSR issues with MPH / KPH in the US down on that thread:

Ross-Tech VCDS support and DIY for the Atlas

www.vwvortex.com

MIB-Wiki · Jun 12, 2021

MU1447 on both sources should be the same.

Regarding the skin issue after update (unit does not boot), just change skin with VCP/VCDS/OBD11 and unit will boot through normally.
Change Byte 17 to Skin 4 (only this one is working!)

The relevant threads on the german board are:
(I hope this is OK)

M.I.B

Support - [Audi/VW/Skoda/Seat/CUPRA/Porsche] M.I.B. - More Incredible Bash - nur für Harmann MHI2(Q) - VIM, IFS-root Patcher, GEM enabler +++

Thema: Vorstellung von M.I.B. - More Incredible Bash Zusammenstellung skriptbasierter Tools, die DIREKT und NUR auf der MHI2 Hardware im Green Engineering Menu - GEM- und auch in der RCC Konsole laufen! D-Link USB zu Netzwerk-Adapter wird nicht mehr benötigt. Sprache/Language: Bitte beachtet...

www.digital-eliteboard.com

Download (always latest version):

22 byte file on MEGA

bit.ly

M.I.B is NOT just patching:

Running from SD card only (NO"D-Link"/PC/Putty required)
- during installation of M.I.B the list of supported USB devices is expanded. Cheap 5-10 GBP "D-Link" alternatives can be used afterwards.
Automated system backup to SD card before patching is even possible
Fully automated patching, with multiple safety measures, to make sure, that only the right patch can be applied to the FW on unit
Fully automated editing of FECContainer.fec
- Adding SKODA MAP Fec to enbable latest map Update on SEAT
- Only Fecs not already enabled on the unit will be added. All other Fecs stay original and will continue to work even after removal of patch.
Fully automated activation of coding (long cooding and adaptions) to enabe CarPlay and AA
and much more, check picture below:

Find attached files with:

List of supported FW versions (all MHI2/Q)
Overview over common FECs and their function
Password list for MHI2/Q units.

MHI2_ER_SEG11_P4709 MU1447

Support - [SEAT CUPRA] MIB2 Navi Plus AIO MHI2_ER_SEG11_P4709 MU1447_1 | CarPlay Android Auto | ifs-root EL Patch

Thema: In diesem Thema geht es um das richtige Vorgehen beim FW-Update, sowie Patchen der aktuellen SEAT MIB2 Navi Plus MHI2_ER_SEG11_P4709 MU1447 Firmware. 100% über SD Karte und alles (Patch, Kodierung, usw.) als Teil des FW Updates. AIO - Custom All-In-One FW Updates...

www.digital-eliteboard.com

@Tell feel free to move this post into a new thread related to MHI2_ER_SEG11_P4709 MU1447 updating and patching!

Based on the metainfo2 exploit, it would be possible to create a custom FW update, which could:

automatically patch during installation
automatically change FecContainer.fec during installation
Change Skin during installation
...

This was already done once for the Audi 3663 update.

Support - [Audi] MIB2/MHI2 - AUG 11 & AU57x FW Update | MHI2_ER_AU57x_K3663 | A6-A7-A8 | ifs-root Patch (ASI, CarPlay, Android Auto, Map Update)

Thema: [Audi] MIB2/MHI2 - AUG 11 & AU57x Firmware Update | MHI2_ER_AU57x_K3663 MU1425 | A6-A7-A8 | ifs-root Patch (ASI, CarPlay, Android Auto, Map Update) In diesem Thema geht es um das richtige Vorgehen beim FW-Update und Patchen der MHI2 AUG11 & AU57x SW-Train Reihe - dazu gehören...

www.digital-eliteboard.com

So, if someone from the community is eager to do this

Tell · Jun 12, 2021

Obtaining the Skoda Lifetime Navigation FeC for the Mib2 High (Europe 08300008) to enable the upload of June 2021 map release 192 to the unit and may be beyond

Notes

For DIY method using Mib Tool two main options:

Update to one of the Mib2 High firmware releases where a Mib Tool patch is available for FeCs
Stay on Current firmware but update FeCs as above (currently 1447, 1409, 1376, 1338, 1219)

Elements of the second option are covered in the first. A firmware update can be more problematic than just a FeC update. The second approach is dependent on whether the patch has already been created by the M.I.B. team that supports Mib Tools this is determined when the back up is made on Mib Tools. If the patch has not already been created then an invitation to submit the backup and website is provided. The M.I.B. people can create a custom patch where you only AddFecs or a full patch. Existings patches can be found in the patches directory and have the run in name MHI2_ER_SEG11....

Firmware Update to 1447

(Notes so far gleaned from DEB forum and Angelixx see post 941 here. Considerable misdirection on the DEB site.

You need to check you have a valid route from current firmware to this release, staged may be required (see thread 01xx-> 06xx ->08xx -> 1447).

Take the links from the DEB board, you need to register. You need to run Google Translate or Chrome on a separate tab if you don't speak German to read the instructions.

Support - [SEAT CUPRA] MIB2 Navi Plus AIO MHI2_ER_SEG11_P4709 MU1447_1 | CarPlay Android Auto | ifs-root EL Patch

Thema: In diesem Thema geht es um das richtige Vorgehen beim FW-Update, sowie Patchen der aktuellen SEAT MIB2 Navi Plus MHI2_ER_SEG11_P4709 MU1447 Firmware. 100% über SD Karte und alles (Patch, Kodierung, usw.) als Teil des FW Updates. AIO - Custom All-In-One FW Updates...

www.digital-eliteboard.com

Firmware link is shown after "FW update MHI2_ER_SEG11_P4709 MU1447" when registered under the German language tab. See post 743 for 1409 software, you need this to supplement missing language files from 1447. SWDL incremental manual download is used to install the missing files.

You need to switch to skin 4 to avoid fiddling mid process. If the skin is not changed the unit may boot up with a blank screen then the Obdeleven / VCDS coding can be made then. Better to do it in advance

MIB Tool + Patch

There is a forum DEB thread devoted to that

Support - [Audi/VW/Skoda/Seat/CUPRA/Porsche] M.I.B. - More Incredible Bash - nur für Harmann MHI2(Q) - VIM, IFS-root Patcher, GEM enabler +++

Thema: Vorstellung von M.I.B. - More Incredible Bash Zusammenstellung skriptbasierter Tools, die DIREKT und NUR auf der MHI2 Hardware im Green Engineering Menu - GEM- und auch in der RCC Konsole laufen! D-Link USB zu Netzwerk-Adapter wird nicht mehr benötigt. Sprache/Language: Bitte beachtet...

www.digital-eliteboard.com

The associated firmware download (MIB Tool) which is up-to-date is on the link, 7z under M.I.B. directory:

MIB Solution :: Login

guest, guest

-----

Option 1 - Firmware Update to 1447 and use of MIB Tool

Distilled stages

1. Fix screen first before processing for 1447

From DEB 1447 forum: "It has already been observed twice that a unit gets stuck in the boot screen immediately after the firmware update.
If this happens to you via VCDS / VCP / OBD11: change byte 17 to skin 04 (carbon skin) and restart the system."

Pre-empt, change long string of 5F module to Byte 17 to Skin 4, save and long reboot VCDS or OBDEleven (check)

VCDS method:

OBDEleven Method:

2. Take a copy of the 5F long string before starting for comparison at end to resolve any issues + photograph FeCs

3. Clear SVMs with OBDEleven / VCDS before we start

May not actually be required.

4. Check climate background

??
From DEB 1447 forum "That helped me a lot, Byte2 = 0x80, otherwise I had no background image in the climate, my original value was 0x03"
??

5. Install MIB Tool + Patch

GEM version should be above 4.1 for MIB Tool to install via SD.

Prepare SD card:
Extract all files of the M.I.B. to the root directory of a clean SD-Card (FAT32 formatted is requirement!!!)
NEW - GEM Method: use 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<<==

See README.TXT file on the download for presentation on the SD

User video here of (similar

) installation... stops before clearing the SVM but shows installation:

6. Backup current firmware

At this point a branch exists as to whether you really want to update the firmware or continue with your existing firmware. A screen is returned from MIB Tool if the current firmware is not in the patch database on the SD card. The patches are held in the patch directory. You are invited to submit the backup you have made to the M.I.B. team if the firmware does not exist for patches in the patch directory (e.g. not seen before).

In this instance at this time the software 1338 was unknown to the team. Check log file for errors as it tells you.

Goto option 2 below if you are not changing the firmware release.

7. Fix SVM errors with MIB Tool Again

8. Install MHI2_ER_SEG11_P4709 MU1447 & top up language files if required from MHI2_ER_SEG11_P4708_MU1409 using SWDL manual download, start. Must copy across missing files from 1409 not in 1447 !.

9. Back up with MIB Tool

10. Install Patch from MIB Tool

IFS Root STAGE 2 Patch for Seat 1447 in MIB Tools patch directory MHI2_ER_SEG11_P4709_MU1447_PATCH

(If RoW navigation FeC is required edit txt in the patch with RoW FeC using notepad - see FeC list attached. Patch is setup for Europe)

11. Check TMC parameter 15 is still present (check before the update as well, should be no slash through TMC icon top left if a signal is being received), no bar across it. (Free service used in UK)

Hint. read this and make a note before you start on the process within your VCDS tool so you can put back the desired code if it is changed

12. Clear SVMs with MIB Tool

13. Take out for a drive to test TSR if TSR is configured in the car

Highly unlikely to be an issue

14. Update Maps (e.g. 192)

----

Option 2 - Stay on Current firmware but update FeCs Using Mib Tool Only

Follow points 5 and 6 above.

You only need to download Mib-Tool since you are retaining the firmware but you may need to obtain a patch file for Mib-Tool if the existing software is not recognized at the end of the backup - see message and check log file. Although dummy patch files can be generated yourself some skills is required. @jpmedia generated the one I used by sending them a copy of the backup and they returned the file to be dropped into the patches directory on the SD card of MIB Tool.

Patches already exist for 1219, 1338, 1376, 1409 and 1447 (as of 24/06/2021). An existing patch matching the SW needs to be flashed. If a dummy patch is supplied by the team as a fix, go to addfec button direct in this menu.

The additional FeCs are populated from within the txt file in the patch. The 08300008 life long FeC code should be in that already. See FeC list attached.

Enter patch_ifs-root option and hit Add new Fecs to FecContainer.fec. After reboot the unit, long press on / off button (20 second or so) to get a reboot so they take effect and check installed FeCs. The add FeC is shown below.

If the backup is recognized, the firmware hit flash patch image.

In both sub options check the Skoda FeC has been added. Reboot then hold for couple of seconds the menu button to find installed FeC list and check. Correctly enable navigation should find a selected route for more than 30 seconds without telling you the navigation database is not valid. If the wrong navigation FeC is being used on an installed map this error occurs. If OK can now update maps.

--------

Option 3 1447 AIO (subsequent late entry to the listed edited in May 2022)

This option is firmware "1447" but adjusted for the issues covered in option 1 e.g.. missing language files, start up screen issue, plus all FeCs.

Success reported with this by users in April / May 2022. See thread posts. Some users updated directly to 1447AIO from 01xx.

The 1447AIO software:

MIB Solution :: Login

guest, guest

--------

- OBDEleven / VCDS programming tool to clear the initial SVM. Changing the skin and making corrections.

- Knowledge of infotainment updates on the mib2 high. Ideally, use a PC and 7 zip for unpacking. macOS can generate hidden file characters, use CleanMyDrive and Keka for the Unzip. Probably safer not to use a MAC. Use of SWDL.

- Recommended using a battery charger since interruption of the firmware update can make the unit unbootable. Possible to keep the engine running as an alternative if confident it will not stall.

- Study MIB Tools documentation

- See FeC list attached for alternative RoW navigation lifetime FeCs

- Additional FeCs can be added see addFecs.txt in patch, notepad editor. Default FeCs shown in green on FeC list.

-----

Thanks to @Chillout @MIB-Wiki @jpmedia @Rsjay and especially @Angelixx. All risk is down to the individual in changing firmware / updating FeCs.

Edited from all comments and experience to 14/07/2021... these are taken on board. Ignore below to then.

SW update for MIB2 infotainment system?

Active Member

Active Member

Full Member

Active Member

Full Member

Active Member

Full Member

Attachments

Active Member

Full Member

Active Member

Full Member

Active Member

Full Member

Active Member

Full Member

Active Member

Full Member

Active Member

Attachments

Full Member

Attachments

Similar threads