Tell
Members
-
Joined
-
Last visited
Everything posted by Tell
-
I think the Briskoda board has a list of hobbyists that do coding for each other. Somewhere on here. If it's not a mib2 high ( Columbus) or mib1 then it's not coding but using an old copy of the maps and a copy of modules to overwrite them. One splits into purely computer skills if it's an Amundsen (links on the thread) the other VCDS / Obdeleven Pro coding or the like just to change the TMC group and a reboot (mib2 high and mib1). Link on the thread for both... we thank all those involved.
-
That will be much older than your online connected services one. Above after I'd asked for a bright spark to crack the files one came forward: For the technically minded and with a bit of SQL skills. Basically the mib3 files rolled out through Vag portals but not via connected services keep to the six month release. June / November but signed off six months before. Then the connected services are monthly. Always uptodate with Here Maps material. On top of that the Vag six monthly files can be out of date and not what they seem. Hence the code above to peak at them.
-
I got fed up with things falling off the dashboard, glass etc. Happy with the built in systems since 2016. The demise of Trafficmaster over the air but the mod to shift it to Inrix on Vag equipment works fine 👌. User POI import programs can turn mib1 and 2 inbuilt systems into fully fledged satnavs of old. Mib3 you can't do that. I imported my old user destinations into the car... all 200 of them building them up. So you can get the older systems running as if a GPS system. Was an old Vag user trick. Depends alot on what roads you drive on whether you need real time re-routing which is more Google side or more relaxed traffic information more Inrix. That one tells you what the problem is together with re-routing. Map updates are still available for mib2 and there is a mib1, one to 2023 which isn't bad. Mib1 and mib2 high inrix solution of changing the parameter with a coding device. Mib2 standard for inrix two year older maps. It's all on the thread. Life in the built in systems yet. Apple products are banned from this household 🤣.
-
-
Any advance on 23.12 with that file release above means it's taking it over the air. You lag with a 6 to 12 month period if you use the file loads rather than over the air but saves money on connect services (get out of contract). If you live in a 4g black hole like where I live it also has merit. Quite large down loads over problematic 4g, fine for people living or traveling in good 4g locations. Horses for courses.
-
-
At the minute for mib1 high. Always a possibility that something might be put out outside the standard support timescale for the free updates. That's taken to be 5 years onto the last fitting of the mib model. Mib1 standard got that 2023 map update which was 3 years after the regular update period ended. So you never know. Mib2 high is reckoned to go on after 2025 due to Audi TTs still having the unit fitted after 2020. Mib1 high road on the back of the combined production for mib2 high so had that the longer life till they pulled the production of the combined file. At that stage the cut down file came to the other brands in mib2 high form although Audi had always had the three flavours. Just nobody is offering that mib1 high flavour at the minute. 2023 mib1 standard was a special flavour... Ice cream parlour. You never know. That was a paid for update within mapcare well outside the 5 years. They could always do that for mib1 high in the future.
- 142 replies
-
-
- 1
-
-
- columbus
- discover pro
- maps
- mib
-
Tagged with:
-
Yes by 370 it became mib2 only, prior the standard release across Skoda, Seat and VW was a combined mib1 / 2 release the installation recognised whether it was mib1 or mib2 and just took the files it required although these were jumbled across directories they called mib1 and mib2 but it did dive across irrespective. Audi released the files in two or three flavours combined, mib1 and mib2 historically. 370 only mib2 as far as what is on the net that I've seen. The three others or one or two then released the same materiel but just built differently with checksums, same data, but still just mib2 only. Why the files reduced from circa 32gb to 17gb or so as they dropped mib1 high support. So you know just by the download it's not a combined file. Now that isn't to say a mib1 high version of 370 isn't out there somewhere. I haven't seen it though. The ones that appear from Audi on sites seem to be the ones from behind the Audi mapcare pay wall. Audi running a pay wall on the VIN whilst others don't. Why Audi owners came to this board for the file link after hacking their navigation life long FeC. The downloads work across the brands.
- 142 replies
-
-
- 1
-
-
- columbus
- discover pro
- maps
- mib
-
Tagged with:
-
Just to clarify the Skoda good news stories with this are here: https://www.briskoda.net/forums/topic/511425-amundsen-mib1-maps-update/?do=findComment&comment=5871771 Seat people found the Seat 480 firmware was what they needed, Skoda people the Skoda 490 so it appears. That was my conclusion as to how it's done. The edits as shown in the link plus having the relevant firmware installed then you can enjoy 2023 Here Maps release on your mib1 standard. Mib2 SD card saves hacking the files around to fit the mib1 16gb card and lastly don't do anything without backing up your existing mib1 card if you aren't prepared to buy a mib2 card. Either way take a copy else it may end in tears.
-
Yes it has been done on Skodas since I recall mentioning the Seat firmware code and the one it worked on was in a similar sequence but Skoda. So it updates definitely if on a more recent version of the firmware mentioned, the map release and workaround but you need to take a copy of the existing maps before you start. People delete the maps and you need information from it... then you have to ask others for a copy. A 32gb mib2 card is useful in the process saves hacking down the maps to fit the existing mib1 card which is 16gb. Any old Ebay mib2 card. The CID of these cards is recognised by mib1. The maps themselves were an Audi release for their customer base which is interchangeable. The success seems to be on using the more recent firmware. The text above of carrying forward your old part number enables the update with the firmware. It's what Seat people have been doing but also works with Skoda units. My old contribution on this one is buy an old mib2 card just to smooth out the process rather than fiddling copying stuff backwards and forwards in test. You do need to get a reboot in of the unit in changing maps cards, that long press on the on/off switch else it won't read the card a fresh. Think some may stumble on that as well.
-
If you have managed to load 370 onto a mib1 and you want to go backwards if it's like mib2 which it will be, you need to use the SWDL of the developers menu. For mib1 my understanding is that the developers menu is not protected. Mib2 you have to enable it, mib1 it's not. You hold onto the menu button. A menu will open. Keep holding another menu will open and you'll see SWDL on it (if its like a mib2 high). Taking your 350 download you dance your fingers around the menu to select all, that way it will go backwards or re-install a version already installed. You have to keep the door open to retain power to the unit or open it at 15 minute intervals to retain power to the unit. Unlike a standard mib high update when the unit's power is interrupted you have to start all over again. There is mib1 high swdl talk online where I first got the knowledge from for using it on mib2 high.... this was back in 2017 when I first got into the SWDL menu (software developers menu). It's how retrofitters update firmware, maps etc.
- 142 replies
-
- columbus
- discover pro
- maps
- mib
-
Tagged with:
-
Well I reckon 370 is where they stopped supporting mib1 high, 350 is fine. On the subject I reckon we might be getting close to the "390" early release if it's going to have that reference code. The Audi originated one for 350 appeared at the end of September last year so all eyes of those in the know.
- 142 replies
-
- columbus
- discover pro
- maps
- mib
-
Tagged with:
-
-
Ask whether anybody is seeing Radio X ?. You won't find anything upto 24.8 on those maps for another 12 months or so. That's the penalty for not paying for connect services. It tends to be the commercial stations which have the missing logos. It's fair to say if you look in the mib2 files that you can get via that phonostar website using SQLite and you can't see a Radio X in there, then it won't be in the Mib3 files.
-
Not the right button but the right button... it's down on an information menu. It's gives you the relative files installed, map, radio icons etc. It's going to be lurking where the map release information is I guess. Those updates come over the air until you severe your connected services contract then load them up manually. This phonostar one has been talked about across European boards. It's signposted for VW but falls out of the signposting for Skoda via that website. The map files they don't hide away for general download. The radio icons they do. They are maintained by phonostar which is a German Internet radio provider so the VW contract gets them from their as an offshoot of their Internet radio icon library.
-
It is a mib3 isn't it. They are shown on the screen by pushing the right button. It's what the Seat folk have been doing but unlike Skoda they can't update since it's not in the manifest file. It could be your unit isn't in the manifest file. This was an old issue with mib2 POI import VW left off particular units so they never kept the POI import up to date on their website. People on mib2 high found a way of circumventing that. Mib3 is locked down so no tinkering with import files they are all encryption signed. I showed an example of the manifest file on the Seat link. It's MartiniBs original link file from the phonostar website. You use to be able to look at the firmware files and deduce the code missing. I think when I checked those I couldn't find a manifesto file in the firmware that tallies, but somebody may have done that now. Perhaps I was looking in the wrong place. The IDs you'd think you would find in the firmware file. You did with mib2. Probably in an SQL database in the firmware. Something for the youngsters to look for. You say, yep this is the firmware file, where is the ID that this works with this. How mib2 worked anyhow and VWs repeated mistake.
-
Whilst you won't find it listed on the phonostar site the question is whether your units infotainment is defined by the SK in the file that steers it. Presentation is covered in the PDF that @MartiniB referenced in the original post. It has to be exact. If the file is presented one layer down in the file tree it won't see it. So two issues is the infotainment unit identified in the file... tricky to find out and secondly presentation. For Skoda you are looking at the SKs https://www.seatcupra.net/forums/threads/radio-logos-update.472858/#post-5048490 But the issue is you don't really know the code for the unit. Somebody probably does. It wouldn't work if it's not in the manifest. I asked about Mac because they put in additional characters which stops the validation if CleanMyDrive isn't used. That was OK for you but you can't poke about in these files and re save them.
-
-
-
Every ŠS Mk3.FL came with one... 😉. I joke. Perhaps his dealer left it in by accident. It's these ones that skip the adapter out https://www.google.com/search?q=usb+c+sandisk+reversible&client=firefox-b-m&sca_esv=1c4a2bf3bd651b6a&sca_upv=1&sxsrf=ADLYWII5nNY_f_7GelplCpJB6kXnJiFcPQ%3A1725460041460&ei=SW7YZo3gG8OUxc8P4LbjuAk&oq=usb+c+sandisk+reversible&gs_lp=EhNtb2JpbGUtZ3dzLXdpei1zZXJwIhh1c2IgYyBzYW5kaXNrIHJldmVyc2libGUyBRAhGKABMgUQIRigATIFECEYoAEyBRAhGKABSKxDUNgMWJg9cAB4ApABAJgBrAOgAfQSqgEJMC44LjIuMS4xuAEDyAEA-AEBmAIMoALBEsICBBAAGEfCAgYQABgWGB7CAgsQABiABBiGAxiKBcICBBAhGBXCAgcQIRigARgKmAMAiAYBkAYIkgcJMS44LjEuMS4xoAfBOw&sclient=mobile-gws-wiz-serp
-
Ah but one adaptor isn't like the next... that's the issue. On the Seat side a Retrofitter fitter that was selling firmware updates had one client with one of the ones that didn't pass data... I asked "what was the solution". The guy said 50% of them don't work with data. Then as I said or didn't one guy said get one with a "flashing data light". Seems an awful hassle, a Sandisk reversible dual stick is the answer or if you got a modern laptop just a USB C stick. Other than that it's pop luck with adaptors or find one that says in the spec for data.... you might even find one with a data light 🫣. It will be the "charge only" one that are sold only for charging. Not all pins wired. Chinese parts bin which people drop their hands on.
-
It's adapters that cannot work sometimes due to all the pins not being connected for data. Best to treat yourself to a dual / reversible stick with USB C on oneside, USB A on the other. Suppose to be adaptors which flash for data, I'd just buy a drive for the job. It's been said to me get a "data adaptor" but Skoda folk on mib3 map upgrades say get a dual reversible stick. It's the data bit that is missing. I'd splash the cash to get the job done. We're assuming the file is unzipped and presented correctly. The unit's themselves have a Skoda ID that matches up with the download so as long as the Superb Mib3 has the correct ID the file expects, presentation is correct and it's not hampered by the pin connections it will work.
-
They have probably just downgraded their servers. The other thing is to factory reset your dongle thing if you haven't done it already. Skoda car stick. Presumably that puts out wifi to the car.
-
That's a possibility.
-
Rural here going to the big Welsh smoke on the M4 so those hold ups are usefull and any local rural ones we now see. Mib2 high for trips to England so see the new road and traffic reports... mind you using my car on the our NHS tourists trips to get treated. More comfy but get to see the rural ones on our local run around. Probably Skoda's end of life service on mib2 connected services. Guess it will be the same for mib3 eventually. I'd put your issues down to Skoda internal mib2 connected services being run down on old hardware. Could be a minority of Skoda drivers took mib2 connected services and still use them. They never came to Seat in that form.
