Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1
- Thread starter metomurti
- Start date
Yes 2019 Leon Cupra 290 DSG. I've given up for today it's making my brain hurt lol. Probably seems silly to you but it's not easy to do unless you know how. The VW 2025 map was too big for my card 16Gb my card is 14.8Gb.
Could I suggest something for idiots like me, when you show the list of steps could you put the important "not to do " things in a sort of warning before the list. That way people like me won't read 75% then start trying to do it and make a huge error like formatting the card rather than deleting the maps and replacing them.
About three years back Vag release all of Europe above the 16gb card. You need the 32gb Vag card that you can get from Ebay but still need the workaround. After about 2-3 years of warning all of Europe wouldn't fit on the 16gb card due to the cartography increasing in size. The zoned regions are released as a substitute but if driving across Europe then you need the 32gb card.
Warnings are fairly liberal but the manual assumes you have mapcare. Saying don't format the card is fairly liberal. Changing the sector size consciencely or via file explorer doing it by accident within the format is another warning.
Basically the unit in the car expects a Vag prepared map card changing the sector size is things that people do when trying to be clever but Vag had thought about that in the zoned release but not the Microsoft bug in some file managers that ignores the existing sector size and chooses one for you which is incompatible... then we have the reformatting trap that hits some people. So best to just delete what's on the card and not treat it like a floppy disk or cartridge...
It did come up once people not pulling out all the cards. I pop them out during an update as a matter of routine. That was their problem. Slot A the left one is the map slot on a mib2 standard.
There is on ebay a seller with this Seat AS V21 MIB2 Gen 2 SD Card Leon Ateca Ibiza Toledo Alhambra UK EU 2025 Maps for £34.95 free postage. ( Hope this is allowed). They have a phone number too so I'll call tomorrow to make sure it will work.
Like all ebay purchases you do it on their marked up satisfaction and volume. My 32gb card is a Skoda one that German Skoda board liked at the time. Now they talk about Chinese rip offs ?. Basically the official ones used by Vag have a re writeable CID. All Vag CIDs are interchangeable. It would only be if the Chinese ones were not re-writeable in the main area or slow. Speeds probably not an issue. They are probably Vag cards but that's where the reputation score comes in on ebay purchases.
Ive just gone to put the maps file onto the Mib2 card I bought of Ebay over a month ago and found its only 8gb. The card I bought is
****Ignore that post, on checking I found that a partition was created on the disk, I can expand it.
Seat V9 MIB2 AS Satellite Navigation SD Card IBIZA LEON ARONA ATECA GENUINE
****Ignore that post, on checking I found that a partition was created on the disk, I can expand it.
Last edited:
When I put the updated card in I get a message something like 'the card contains navigation data', then the system goes to checking navigating data with a spinning symbol. I have left it to do this for 5 minutes with no change (dont have time to sit there longer today and have no journeys planned). I suppose the fact that its not rejected means we're on the right lines but is it possible it will not change from that status?
The key is this one
Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1
What people use to do with mib1 after they messed it up. The motto is back up before changing anything. I provide a link to the mib2 standard overall.nds file which fixes all of those who have lost that file which provides a universal solution that we worked out here, but there is no universal...
www.seatcupra.net
You carry over the old DBInfo.txt but edit the last two lines to so it reflects the update. The unit locks onto the old partnumbers but for display you need the last two lines from the new maps. You also do it by editing in the Audi lines of the old card into the new dbinfo.txt file. Basically it teethers on the old Audi lines. It's says ok you haven't updated it, I can use this SD card... but you have but have fooled it. The mib1 mapcare workaround.
In the dbinfo.txt file of the update:
PartNumber1="8V0919866B " <<< put old Audi code in here
PartNumber="8V0919866B " <<< put old Audi code in here
In this example it was 8V0919866B on another mib1 year it would be something else.
That's @Daz3d method. In your instance we didn't edit the mib1 countries out but used the mib2 bigger card. That just leaves the edit if we think the 480 firmware is not important.
If it is sting hung might be the sector size. I said 4096 for mib2. These system don't like you messing with the sector size. 4096 should / will be good since we have used it on other mib1s.
Last edited:
Really sorry but I don't fully get you. The lines on my old card isThe key is this one
Updating the inbuilt Mib2 Satnav / Mib2 tricks and Mib1
What people use to do with mib1 after they messed it up. The motto is back up before changing anything. I provide a link to the mib2 standard overall.nds file which fixes all of those who have lost that file which provides a universal solution that we worked out here, but there is no universal...
You carry over the old DBInfo.txt but edit the last two lines to so it reflects the update. The unit locks onto the old partnumbers but for display you need the last two lines from the new maps. You also do it by editing in the Audi lines of the old card into the new dbinfo.txt file. Basically it teethers on the old Audi lines. It's says ok you haven't updated it, I can use this SD card... but you have but have fooled it. The mib1 mapcare workaround.
In the dbinfo.txt file of the update:
PartNumber1="8V0919866B " <<< put old Audi code in here
PartNumber="8V0919866B " <<< put old Audi code in here
In this example it was 8V0919866B on another mib1 year it would be something else.
That's @Daz3d method. In your instance we didn't edit the mib1 countries out but used the mib2 bigger card. That just leaves the edit if we think the 480 firmware is not important.
If it is sting hung might be the sector size. I said 4096 for mib2. These system don't like you messing with the sector size. 4096 should / will be good since we have used it on other mib1s.
PartNumber1="8V0060866H "
PartNumber2="5G0919866AH"
PartNumber3="5E0051236 "
PartNumber4="5F0060884BG"
PartNumber="8V0060866H "
ApplicationSoftwareVersionNumber="0075"
SystemName=" ECE 2018/2019"
on the downloaded file it is
PartNumber1="V03959803RQ"
PartNumber="V03959803RQ"
ApplicationSoftwareVersionNumber="0106"
SystemName=" ECE 2023 "
The last 2 lines are
ApplicationSoftwareVersionNumber="0075"
SystemName=" ECE 2018/2019"
so do I replace them with the lines from the update while keeping the other lines?
You need to edit
PartNumber1="8V0060866H "
PartNumber="8V0060866H "
Onto your new file of dbinfo.txt keep everything else as the new parameters. That makes the unit think you haven't changed the card but you have. You have fooled it. Hence why @Daz3d pointed to the new road on his map after the edit.
Use the notebook editor and make sure you get the spaces in.
You'll need the long press on, on/off to force a reboot if changing the cards quickly.
Ive got you now thanks, it cant have been the issue though as the 'checking navigating data' with a spinning is still there.
Back to the cluster size 4096 and whether the cards works with the original map copy. Then did you update to the latest 480 firmware. Jury was out on whether you needed that.
I didn't update the firmware, ive just read through the update firmware section (2 pages) and don't see anything relevant to my 2013 Seat Leon
Similar threads
