Skip to content

Radio stations Logos database updates

Featured Replies

On 19/05/2025 at 10:25, fuze said:

Hello, I wrote to <email address removed> waited a long time, but today I received a response from <email address removed> that: We have considered these new logos in our next update version v1.31.58 and you can download them from 21-May-2025. I hope there will be an update from Skoda. @vegarz you helped me update, I hope there will be a new update here too 😄

Hello.

Can you please tell me to what mail address did you write, because I would like to write to them too and see if they can add logos for Bosnia radio stations.

You can send me PM also.

Thanks

  • Replies 240
  • Views 72.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Hello, I wrote to <email address removed> waited a long time, but today I received a response from <email address removed> that: We have considered these new logos in our next update versi

  • Thanks MartiniB.   The MIB3 (Superb etc) file loaded successfully into my Karoq's MIB3 Amundsen, and seems to have created some of the missing radio logos. (Pity I still haven't got any for

  • links in head post have been updated

Posted Images

  • Author

@djukak

link under picture in the head post

2 minutes ago, MartiniB said:

@djukak

link under picture in the head post

Thanks, found it :)

Wondering if someone saw more recent version of the MS2P/MH2P RSDB v1.20.xx series package? I believe those files are used in VW Touareg and in Audi MMI systems since those systems are using higher resolution of graphics (320x240 instead of 160x120). I could only find v1.20.20 from 2020

  • 2 weeks later...
On 25/06/2025 at 18:02, Tell said:

Suppose to be a digital ID but he's corrected me in the past and may be over the air jpeg for DAB. If the logo as a jpeg is never transmitted then you can see you are a bit stuffed when the station ID is recycled. Seen that in the UK. Think actually the logos are not transmitted just a station ID.

You can inspect the mib2 ones via sql light or whatever its called. I'm travelling at the minute so can't check. It's the SQL commonly used so if you have database skills you can poke about in the tables but no good to change anything. All locked down.

Here we do not have DAB. We have very good FM.

I tried opening file, but I got message, that this file is not a DB.

I would like to see some kind IDs, then maybe it is possible to change it.

2 hours ago, strongiukas said:

Here we do not have DAB. We have very good FM.

I tried opening file, but I got message, that this file is not a DB.

I would like to see some kind IDs, then maybe it is possible to change it.

You won't be changing mib3 files. Locked down. Mib2 logo files are available and can be imported

14 hours ago, Tell said:

You won't be changing mib3 files. Locked down. Mib2 logo files are available and can be imported

Just the other day I checked and found the same thing - MIB3 sqlite file is password protected. But the password needs to be stored/hardcoded somewhere in MIB3 firmwares, right?

Can you guys help me. I'm not sure which version of MIB is mine. I have Kodiak iV 2025 with 10" display (smaller). Where should I look in infotainment? or somewhere else?

Check the installed firmware version (might be called SW Train or SoftWare Train). Should be visible somewhere in setup/settings. And in hidden menu.

50 minutes ago, mrfix said:

Just the other day I checked and found the same thing - MIB3 sqlite file is password protected. But the password needs to be stored/hardcoded somewhere in MIB3 firmwares, right?

Two things go on here is the password on the SQL database the second one is an SHA lock to stop the files being tampered with.

https://en.m.wikipedia.org/wiki/SHA-1

54 minutes ago, mrfix said:

Just the other day I checked and found the same thing - MIB3 sqlite file is password protected. But the password needs to be stored/hardcoded somewhere in MIB3 firmwares, right?

SHA-1 was the one used in mib2. That one can't be home defeated unless you got security service hardware by brute force methods. Vag upped the anti by improving that further with longer keys. Those you see in the mib3 firmware. Currently in bed but i'd be very surprised that the SHA key lock isnt in the radio files as well. Vag got tired of hobbyists hacking the software.

Mib2 firmware was only re-written by hobbyist enthusiasts because of a mistake in the turnstile of how POIs were imported in mib2. It was found that whilst the POI part was sealed with SHA-1 against change anything after it slipped in without checking. Only the hashes had to sum. Like someone sliding in behind you on an automated ticket barrier.

The mib enthusiast group(s) then wrote all of the mods on that basis. All in one firmware (AOL). You can check whether your firmware is original in mib2 by inspecting for the signature lines at the end. No signature it's modded.

Vag closed off this weakness by taking it away. Some people believe this is why poi import isnt allowed in mib3 although it appeared in the first manuals. Phonostar have the manufacturer keys to generate the import. The mib2 public key is the same whether firmware or maps. There is a method where you can hand run the software check in SHA-1 which mimics how it's done in the device. Degree level pure mathematics. Branch of cyptology that was developed within "pure" maths... it stopped it being pure then 😉. I've run that check and found the mib2 firmware is all manufactured with the same private key which will be closely guarded (due to the public key being the same). At that point after understanding how the files were locked up I gave up trying to twiddle with them. Then subsequent to that the turnstile weakness was found in mib2. The toolboxes of putting the green menu in the car all use the same turnstile hack. It sporned the AOL firmware and the in car tool boxes in mib2.

So anyhow if you see banks of signature lines in the files that's what they are. A difference in those to the hash row which can be recomputed. Signature rows can't be.

I thought that the AIO, m.i.b., toolboxes, etc. used bug that was not checking the metainfo2.txt content below the signature, which allowed to add more installation commands to the update procedure as long as those were added below the original unmodified signed lines.

Anyway, I'm interested currently only in the MIB3 RSDB sqlite database alone, because my unit (Audi MHI2) is using the 320x240 pixel logos. For MIB2 there's 1.20.20 RSDB update which is 5-year old now. And I believe the the MIB3 database could be used as a up-to-date source for Audi MHI2 RSDB. That's if the MIB3 sqlite db password is known. And of course translation might be needed if the db structure match.

3 minutes ago, mrfix said:

I thought that the AIO, m.i.b., toolboxes, etc. used bug that was not checking the metainfo2.txt content below the signature, which allowed to add more installation commands to the update procedure as long as those were added below the original unmodified signed lines.

Anyway, I'm interested currently only in the MIB3 RSDB sqlite database alone, because my unit (Audi MHI2) is using the 320x240 pixel logos. For MIB2 there's 1.20.20 RSDB update which is 5-year old now. And I believe the the MIB3 database could be used as a up-to-date source for Audi MHI2 RSDB. That's if the MIB3 sqlite db password is known. And of course translation might be needed if the db structure match.

First paragraph yes. They put dummy code in first, then the real code. The dummy code was to fake a poi import.

The hashes intricately have the size of file in them so I reckon you might be snookered. Need that password... best of luck. Anything mib3 more thought went in to stop tinkering.

The logos in the phonostar mib2 files are open as recall.

The other one on the logos which Chillout liked (the guru of mib2 hacks) was this

https://www.seatcupra.net/forums/threads/station-logo-downloader.465980/

The poster had written a script to scrape all of the media.info logos. The script probably now needs changing to reflect any web page changes. This was in the days of mib2 only. The media.info ones will be more complete than the Phonostar ones. Really for mib2 people. I just do the odd one by hand on the in fill basis. This logo extraction is for that.

Mib2 files in the Phonostar database may be useful for your purpose. I dont profess to know Audi systems.

Gone a bit off topic.

  • 2 weeks later...

@MartiniB it's become apparent that out of contract Seat mib3 people are getting radio logo updates over air. Whether they get these after an over the air firmware update out of contract then comes thd radio station logo update or whether they get these irregardless. Are Skodas getting out of contract firmware and radio logo updates on mib3 or is this something that Seat / Cupra get. Any views. You have to be logged in as primary user and not hiding yourself.

Apologies for not wading through all eight pages, but is there an update for a current Karoq with Columbus? I've no idea how that reconciles with "MIBs".

I downloaded a MIB3+ from the first post & extracted it, but it bore no resemblance to the instructions. The extracted files were simply a collection of logos in .png format, whereas the instructions show "Data" & "Meta" folders.

All I'm missing is a logo for LBC in the UK, which is odd as it was also absent from my 2015 Polo until I added it manually. But no manual option is available.

3 hours ago, Rbz5416 said:

Apologies for not wading through all eight pages, but is there an update for a current Karoq with Columbus? I've no idea how that reconciles with "MIBs".

I downloaded a MIB3+ from the first post & extracted it, but it bore no resemblance to the instructions. The extracted files were simply a collection of logos in .png format, whereas the instructions show "Data" & "Meta" folders.

All I'm missing is a logo for LBC in the UK, which is odd as it was also absent from my 2015 Polo until I added it manually. But no manual option is available.

I would say you have a mib3... this one from above

Mib3 (Superb Mk3.FL and similar) Tiguan 3G5 035 820 Q

"FM3-E3-DWBC4-EU-SE-MQB-PC",

"FM3-E3-DWBC4-EU-SK-MQB-PC",

"FM3-E3-DWBC4-EU-VW-MQB-PC",

"FM3-E3-WBC4-RW-SE-MQB-PC",

"FM3-E3-WBC4-RW-SK-MQB-PC",

"FM3-E3-WBC4-RW-VW-MQB-PC",

"FM3-E3-WBC4-US-VW-MQB-PC",

"FM3-E3-DWBY4-EU-FO-MQ2-PC",

"FM3-E3-DWBY4-EU-SK-MQ2-PC",

"FM3-E3-DWBY4-EU-VW-MQ2-PC",

"FM3-E3-DWBY4-W2-FO-MQ2-PC",

"FM3-E3-DWBY4-W2-SK-MQ2-PC",

"FM3-E3-DWBY4-W2-VW-MQ2-PC",

"FM3-E3-HWBC4-RW-VW-MQ2-PC",

"FM3-S-NDWBY4-EE-SK-MQ2-PC",

"FM3-S-NDWBY4-EE-VW-MQ2-PC",

"FM3-S-NDWBY4-EU-SK-MQ2-PC",

"FM3-S-NDWBY4-EU-VW-MQ2-PC",

"FM3-S-NWBY4-R2-SK-MQ2-PC",

"FM3-S-NWBY4-R2-VW-MQ2-PC",

"FM3-S-NWBY4-RW-SK-MQ2-PC",

"FM3-S-NWBY4-RW-VW-MQ2-PC",

"FM3-S-NWBY4-W2-SK-MQ2-PC",

"FM3-S-NWBY4-W2-VW-MQ2-PC",

"FM3-S-NWBY4-W3-SK-MQ2-PC",

"FM3-SM-NDWBY4-EE-SK-MQ2-PC",

"FM3-SM-NDWBY4-EE-VW-MQ2-PC",

"FM3-SM-NDWBY4-EU-SK-MQ2-PC",

"FM3-SM-NDWBY4-EU-VW-MQ2-PC",

"FM3-SM-NWBY4-R2-SK-MQ2-PC",

"FM3-SM-NWBY4-R2-VW-MQ2-PC",

"FM3-SM-NWBY4-RW-SK-MQ2-PC",

"FM3-SM-NWBY4-RW-VW-MQ2-PC",

"FM3-SM-NWBY4-W2-SK-MQ2-PC",

"FM3-SM-NWBY4-W2-VW-MQ2-PC",

"FM3-SM-NWBY4-W3-SK-MQ2-PC",

"FM3-S-NWBY4-RW-SK-MQB-PC",

"FM3-S-NWBY4-RW-VW-MQB-PC",

"FM3-SM-NDWBY4-EE-SK-MQB-PC",

"FM3-SM-NDWBY4-EE-VW-MQB-PC",

"FM3-SM-NDWBY4-EU-SK-MQB-PC",

"FM3-SM-NDWBY4-EU-VW-MQB-PC",

"FM3-SM-NDWBY4-RW-SK-MQB-PC",

"FM3-SM-NDWBY4-RW-VW-MQB-PC",

"FM3-SM-NDWBY4-W2-SK-MQB-PC",

"FM3-SM-NDWBY4-W2-VW-MQB-PC",

"FM3-SM-NWBY4-R2-SK-MQB-PC",

"FM3-SM-NWBY4-R2-VW-MQB-PC",

"FM3-SM-NWBY4-RW-SK-MQB-PC",

"FM3-SM-NWBY4-RW-VW-MQB-PC",

"FM3-SM-NWBY4-W2-SK-MQB-PC",

"FM3-SM-NWBY4-W2-VW-MQB-PC",

"FM3-SM-NWBY4-W3-SK-MQB-PC",

"FM3-S-NDWBY4-EE-SE-MQB-PC",

"FM3-S-NDWBY4-EE-SK-MQB-PC",

"FM3-S-NDWBY4-EE-VW-MQB-PC",

"FM3-S-NDWBY4-EU-SE-MQB-PC",

"FM3-S-NDWBY4-EU-SK-MQB-PC",

"FM3-S-NDWBY4-EU-VW-MQB-PC",

"FM3-S-NDWBY4-R2-SE-MQB-PC",

"FM3-S-NDWBY4-R2-SK-MQB-PC",

"FM3-S-NDWBY4-R2-VW-MQB-PC",

"FM3-S-NDWBY4-RW-SK-MQB-PC",

"FM3-S-NDWBY4-RW-VW-MQB-PC",

"FM3-S-NDWBY4-W2-SE-MQB-PC",

"FM3-S-NDWBY4-W2-SK-MQB-PC",

"FM3-S-NDWBY4-W2-VW-MQB-PC",

"FM3-S-NWBY4-R2-SE-MQB-PC",

"FM3-S-NWBY4-R2-SK-MQB-PC",

"FM3-S-NWBY4-R2-VW-MQB-PC",

"FM3-S-NWBY4-W2-SE-MQB-PC",

"FM3-S-NWBY4-W2-SK-MQB-PC",

"FM3-S-NWBY4-W2-VW-MQB-PC",

"FM3-S-NWBY4-W3-SK-MQB-PC"

Content Downloadable Size

2023.12.20 2023.12.20 162 MB https://www.phonostar.de/download/vw/MQB3_OI_JND_Europe_v1.31.48b.zip

2024.05.17 2024.11.07 1,13 GB https://www.phonostar.de/download/vw/MQB3_OI_JND_Europe_v1.31.50.zip

2025.01.14 2025.02.20 166 MB https://www.phonostar.de/download/vw/MQB3_OI_NonGP_JND_Europe_v1.31.56.zip

2025.01.08 2025.05.26 833 MB https://www.phonostar.de/download/vw/MQB3_OI_JND_Europe_v1.31.56.zip

2025.03.19 2025.06.11 167 MB https://www.phonostar.de/download/vw/MQB3_OI_JND_Europe_v1.31.58.zip

What I did become aware of and waiting for @MartiniB comment is that firmware and logos get pushed to people out of contract if you are the primary user and chosen not to go incognito. The thread is where you want to upload the logos yourself and out of contract, but I suspect you might get thd logo uodate if the firmware is updated out of contract.

You can fumble with the information screens to find what radio logo database you are on and compare with the above. There is no way to manually enter your own png image for missing logos. VAG closed that route down. Its a gripe of mib3. Haven't got mib3 myself. What I would say is you just unzip those files and present correctly. You can't tinker with mib3 files. It won't see them if you do. Use the latest 7zip for unzip or the latest windows file manager to drag and drop the files onto a blank USB-C. Adapters for type a to c are not recommended since some are not fully wired for data. Reversible memory sticks are liked with a data flashing light on them.

So basically if you are in connected services contract, the mib3 file wont be required and it seems least for Seat updates are pushed over the air even if you aren't in contract, but that might be as part of a firmware update. I'd be interested to know whether Skoda out of connect services contract users are getting firmware updates and whether they get the radio logo one as well over the air.

  • Author
5 hours ago, Rbz5416 said:

The extracted files were simply a collection of logos in .png format, whereas the instructions show "Data" & "Meta" folders.

downloaded compilation from Å koda portal is useless

because Mib3 units have lost option of manual upload for particular stations

try

https://www.phonostar.de/download/vw/MQB3_OI_JND_Europe_v1.31.58.zip

https://www.phonostar.de/download/vw/MQB3_LGe_Europe_v1.31.58.zip

https://www.phonostar.de/download/vw/ICAS3_LGe_Europe_v1.31.58.zip

and report result, on my 2023 Mk3.FL Å S it stopped work

MQB3_OI_JND_Europe_v1.31.56 - OK

MQB3_OI_JND_Europe_v1.31.58 - NOK :(

-> https://www.briskoda.net/forums/topic/520105-radio-stations-logos-database-updates/page/7/#findComment-5950044

1 hour ago, MartiniB said:

downloaded compilation from Å koda portal is useless

because Mib3 units have lost option of manual upload for particular stations

try

https://www.phonostar.de/download/vw/MQB3_OI_JND_Europe_v1.31.58.zip

https://www.phonostar.de/download/vw/MQB3_LGe_Europe_v1.31.58.zip

https://www.phonostar.de/download/vw/ICAS3_LGe_Europe_v1.31.58.zip

and report result, on my 2023 Mk3.FL Å S it stopped work

MQB3_OI_JND_Europe_v1.31.56 - OK

MQB3_OI_JND_Europe_v1.31.58 - NOK :(

-> https://www.briskoda.net/forums/topic/520105-radio-stations-logos-database-updates/page/7/#findComment-5950044

Eek but what do you think of this ?

https://www.briskoda.net/forums/topic/520105-radio-stations-logos-database-updates/page/8/#findComment-5959372

Seat users getting logo updates out of contract. I'm not sure whether that's a result of getting a firmware update pushed to the unit then the radio logo update. Anyhow it's been happening.

@MartinB @Tell

Thanks.

I downloaded this one & it unpacked to correct format & went through the update process, although reported it as an OTA update. Sadly still no logo for LBC.

MQB3_OI_JND_Europe_v1.31.58

If I can find the energy I report it to Phonostar as a Tiguan owner.

1 hour ago, Rbz5416 said:

@MartinB @Tell

Thanks.

I downloaded this one & it unpacked to correct format & went through the update process, although reported it as an OTA update. Sadly still no logo for LBC.

MQB3_OI_JND_Europe_v1.31.58

If I can find the energy I report it to Phonostar as a Tiguan owner.

Was it really an OTA or gave it a kick to get one. Seems something more is going on with these files.

As far as the logo graphics are concerned Phonostar manage them for Vag so if they have holes in their files then you see those holes in Mib3.

I'm hoping @MartiniB can throw some light on how out of contract Seat's get the firmware updates and logo updates. These seem to be pushed like a digital TV box. Vag decides they are eligible and gets them. May be they see these as critical updates to firmware so are rolled out for free. Question is whether the firmware update then triggers the logo update over air. The files in this thread with no SE in the descriptor aren't seen by Seat or Cupra, why I was surprised to find out units were being updated.

Anyone.... may be it's common knowledge to the inner circle of mib enthusiasts.

Edited by Tell

  • Author
11 hours ago, Rbz5416 said:

MQB3_OI_JND_Europe_v1.31.58

try also other two links, they all are Mib3, just different devices

devices type classification after Mib, Mib2, Mib2.5 isn't clear at all :(

9 hours ago, Tell said:

get the firmware updates and logo updates

OTA and dealer Mib3 Amundsen(2023 Mk3.FL Å koda Superb) firmware updates

gave downgrade if compare to Phonostar releases,

but "upgrade" if compare to factory flashed version

Radio database version:

1.30.36 (factory 2023.01)

1.31.48 (user 2024.01, downloaded from Phonostar.de)

1.30.36 (dealer 2024.01)

1.31.44 (OTA 2024.03.18)

1.31.50 (user 2024.11, downloaded from Phonostar.de)

1.31.56 (user 2025.05, downloaded from Phonostar.de)

1.31.58 failed

On the later I suspect it's like the map updates you are finding ones yet to be "released". If OTA is supported on out of connect service contract then the mib3 logo files beat the OTA becoming available which might be triggered by a firmware OTA. That's my theory.

Yes I've yet to see which mib3 updates streams belong to which. Its going to be on the firmware. That's where you inspect mib solutions to see which hardware they are talking about. LG etc. Ateca / Karoq is on one set. Formentor / Skoda ? (MQB Evo) Is on another. EVs on another... the logos probably associated with the firmware - it's those part numbers you see in the files. The map files seem to be across.

My two pennies worth. I can't see it will be only Seat / Cupra getting OTA out of connect services contract. Bet Skoda and VW are getting them. Those give you firmware, firmware + logos, or just logo. Whether you can get a logo updates out of contract OTA without a firmware update, not sure. These are just reports I'm reading spurred by publishing these logo links on the Seatcupra board.

Edited by Tell

30 minutes ago, MartiniB said:

try also other two links

Neither recognised by the unit, so appears that the JND is correct.

I've raised it with Phonostar & will report back.

Now sorted.

Prompted by Phonostar, I was hunting around the menu for a rescan. Couldn't find one but did go into the previously empty Manage Logo tab & there it was. So just selected it & all is well. I was expecting it to update automatically.

So anyone with a new Karoq with Columbus, the correct download is this one & then you have to select the logo manually.

But was it over the air triggered by the use of that file. Have you got your LBC logo.

Reckon MartiniB issues are round the unzip process. Some pesky implementations of it about. Seems latest 7zip or built in Windows managers does the business. Older zip programs struggle with some of the newer implementations.

The other issue is where it doesn't appear on the virtual cockpit but on the main unit. You delete from favourites and reapply. Another one where that happens on mib3.

Edited by Tell

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.