Sat Nav (overall.nds)

Nov 9, 2021
4
0
So as my Leon is now 3 years old and I use the Sat Nav a lot for work I looked at updating the maps. I followed the instructions on the Seat website which looked pretty easy and managed to update the SD card. I put the card back in the car and yes, "Navigation Database Not Available" So after some searching on various forums I now realise II should have kept the original overall.nds file and copied it back to the card. Which wasn't mentioned on the Seat Website, So am I completely stuffed? Can I get the original file somewhere, or buy a new Seat SD card from EBAY?
 

Daggerw9

Active Member
Mar 9, 2020
14
4
An idea here on the navigation thread....


Worked for them.
thanks will get one and try that
 

Daggerw9

Active Member
Mar 9, 2020
14
4
An idea here on the navigation thread....


Worked for them. All the VAG cards are interchangeable whether Seat, Skoda or VW. The newer 32gb you can get the all Europe map on which you cant these days and have to use the zoned areas.
hi Tell so i ordered a new VAG sd card from the link i popped it into my car and did the overall nds trick the card reads the navigation data but cant seem to load them up. any other ideas you know
 

Tell

Full Member
Staff member
Moderator
hi Tell so i ordered a new VAG sd card from the link i popped it into my car and did the overall nds trick the card reads the navigation data but cant seem to load them up. any other ideas you know
Take a copy of it as is.

Then you could try the Seat Mib2 year 1 trick from the resource. Some units had a "funny" original overall.nds file which causes the upgrade not to work so you load up the earliest release which is the Skoda link, use the overall.nds file on that. That kick starts the unit. Then take the overall.nds file from that release and copy across to the most recent release. So essentially you aren't using the overall.nds file that was on the car when you got it, but a historic one.

This is sometimes required with one particular release of the original map card. That's been successfully deployed on the board a few times. The wrinkle was spotted by a Spanish board. Essentially the card when paired sets up the FeCs in the unit. Moving the overall.nds file frigs it to refresh the FeCs with another set (may get two, the source of the flag being set that you don't need to worry about, and if you aren't worried ignore that bit). For one year only this additiinal process was required.

See lost and found section of the resource:


This text:

》》

Lost, Stolen and Missing Cards from a Mib2 Standard Unit

Godzzi and myself covered on the thread the process of getting back a card that was lost or stolen out of the unit. Buy a card and put back the overall.nds file from the year or one before. For good measure you can go back to V1 Seat map release rather than playing lucky dip with the download releases if you don't know which release was paired with the car, link below and use the most recent map update over writing the overall.nds file with the V1 one.

V1 link (Credit Markobc with that one):

http://infotainment-cdn.skoda-auto.com/base/maps/0430_MP143-1248.0EUR.zip

Godzzi tested for me that going back beyond the paired overall.nds file worked. So if in doubt jump back releases if you don't know what the release was. Then do the workaround using the overall.nds file. (I did test that with a unit with the overall.nds of 1030 and works fine with 0430)

Variation of the workaround but going back to the Seat base year for mib2 if no more information on what was in the car. Full credit goes to Exciter for the workaround. Basically now identified that these overall.nds files contains effectively a release date stamp as well as a general database index. For other VAG cars you might want to go back to 0235 (2014/15) which is the very first release ahead of it coming to Seat.

The card needs to be a Standard Mib2 card, can be Seat, Skoda or VW. Might wish to consider the recent 32GB card planning ahead.

《《

Current map release is this, not what Seat put up on their site, that's old.


That may be newer than what was on your bought card or the same.

Kick start with the old maps as is (Skoda link). Shift that overall.nds file onto the latest maps. Reboot of the unit with the long press is always good so it reads in everything a new.

Fingers crossed.
 

Tell

Full Member
Staff member
Moderator
The overall.nds file that gets you out of trouble I attached here:


That is just overwritten onto the update as per the normal workaround instructions.
 

DEAN0

Old Git
Feb 1, 2006
5,288
300
Preston - UK
If anyone is looking for the latest V18 map card - I have just bought this one and put it in my 2018 Cupra 300
It was running a V6 map card.
This one works perfectly - doesn't need any coding.

 

Tell

Full Member
Staff member
Moderator
That Cupra might have been at the end of the mib2 standard period when Seat relented on Mapcare why it didn't need any coding. Failing that you do the overall.nds trick. I did post up on the board somewhere the life time standard FeCs on that unit from a German forum when this happened. We do come across some cars with that on it. I get people to check their FeCs and they say, oh yes I do have that. It applied to standard and high units and may be only Cupra.

Edit. This table. Units started appearing with the trailing EE codes on their navigation FeCs which meant they were not capped to period. Normally they were shipped with the date of the map card. The overall.nds trick leads the unit to compute a new FeC which allows the update. Also a period when you were allowed one complementary update within a year. If in doubt you look at your FeCs. That's the long menu hold till the menu appears to show installed FeCs. The boot and braces approach.

Screenshot_20230907-180803.png
 
  • Like
Reactions: Walone
Progressive Parts, performance parts and tuning specialists