Can't read release info

[javigody]

When i try to install this on mi unit, the updater give an error, "can't open/read release info" SEAT MIB High with SW 1308

[peterbensch]

Same error with fw 1163 (skoda)

[jilleb]

Make sure you have your SD card formatted as Fat32

[javigody]

I have try in fat, FAT32 and exFat

[jilleb]

Try a more recent firmware version. We tested on 1409, works.

[jilleb]

@javigody , I put up a zipfile in the releases-section. Can you try it again with this zip-file unzipped on your SD-card?

[javigody]

@javigody , I put up a zipfile in the releases-section. Can you try it again with this zip-file unzipped on your SD-card?

Ok, I will try ASAP

[javigody]

I have tried with the same result

[javigody]

With the last metainfo2.txt gives another error, "Regions do not match. '*' Europe."

[peterbensch]

I'm getting the same error as @javigody . "Regions do not match. '' Europe." I guess the problem is on line 12 ` variant = "FM?-H---"`

[jilleb]

@peterbensch, no, it's not that line.

Check out the latest commit a4c7f75c604472bfc9419a558b764a6bb4fc1bd8, should work.

Tested it in 3 different radio's today: latest Skoda, Seat and VW MIB2 High.

[olli991]

Same issue on seat fw 1338 with new zip file on fresh formatted SD card in fat32.

SW Train Version: MHI2_ER_SEG11_P4705 SW MU Version: 1338 Partnumber: 5F0035020G HW-Version: 5F0035020 SW-Version: H29.344.49_HIGH2_EU

[1LucKyLuke]

Same issue on Seat Leon MIB2High

SW Train Version: MHI2_ER_SEG11_P4708 SW MU Version: 1409 Partnumber: 5F0035020H HW-Version: 5F0035020 SW-Version: H29.344.59_HIGH2_EU

[olli991]

Same issue on seat fw 1338 with new zip file on fresh formatted SD card in fat32.

I checked against a normal, working POI-Import and came across some differences in the "Update.txt". I don't know if this maybe is a point... Left one is MIB-Toolkit V2 update.txt. Right one is from SCDB manual POI-Import generated with the Excel-Tool there.

[jilleb]

I tested it on a 1338 unit, no issue.

I'm pretty sure it's in the way you're copying the files or something. Or github puts CrLf at the end of each line? I don't know.

[olli991]

I tested it on a 1338 unit, no issue.

I'm pretty sure it's in the way you're copying the files or something. Or github puts CrLf at the end of each line? I don't know.

How should i copy them. I'm on Windows copy pasting them. What way would you suggest to do it "the right way"?

[jilleb]

Take the zip file from the release.

[olli991]

Take the zip file from the release.

Okay I tried it again. Source-Code ZIP-File and also the release ZIP. Directly into the main folder of the SD-Card. MIB-System instantly shows "New files for update available" but everytime there is the same error as above. Tried to copy the files via Windows and via Mac now.

Updates should work for me and worked in the past. Successfully updated Personal POIs two times (speedtraps) and updated the maps to 2019 (mapcare is active).

[dfs-]

I can confirm the same issue with an MIB2 Columbus, with K firmware (updated by dealer from 0702 to 1233)

Adresse 5F: Informationselek. I (J794) Labeldatei:| 3V0-035-MIB-HGH2.clb Teilenummer SW: 3V0 035 021 C HW: 3V0 035 021 Bauteil: MU-H-LND-EU H50 1233
Seriennummer: A674F0G7505438

I have tried different SD cards and also with USB stick, all formatted as FAT32.

[jilleb]

Seat: update to the latest firmware, we tested it successfully with 1409.

[1LucKyLuke]

I'm on 1409 but I'm not able to get it to work. I've tried multiple FAT32 formatted SD cards, each of them freshly formatted and have worked in the past for importing POIs or updating map data.

[jilleb]

And you get the same error?

[1LucKyLuke]

Yes, always showing the error that it is unable to open/read the metainfo2.txt

[jilleb]

Okay, I noticed 1 difference that could be interesting.. my metainfo2.txt didn't have CR/LF at the end of it, and it could be that it's an issue in some cases...

I made an update with commit a3c4b24d30efc9a6dfe3de9d59111ca433a99922 Can you try again, with the metainfo from here: https://github.com/jilleb/mib2-toolbox/archive/master.zip

[driver975]

Not working with Skoda 565035021B 1240 firmware

[olli991]

Tested it: New file doesn't work for me aswell. The new file has the same checksum as the old one, could this be the problem now, because we added a line and checksum is still the same?

[R0bbieJ]

Not Working on: Model: VW mk7 (Discover Pro 9.2) Sw: 1161 Issue: can't read metainfo2.txt

[1LucKyLuke]

@jilleb Tried the new metainfo file but sadly it's still throwing the error.

[DejanBukovec]

Today Im try it with commit a3c4b24 and d84dd9e and both produce same error as for others "Error with reading metainfo2.txt" ... Im try on "Supported firmware version".

SW Train Version: MHI2_ER_SEG11_P4517 SW MU Version: 1219 Partnumber: 5F0035020F HW-Version: 5F0035020 SW-Version: H29.319.43_HIGH2_EU

[jilleb]

I'll make an SD-card image you can write to SD-car with Balena Etcher (https://www.balena.io/etcher/). That should rule out any issues.

[vldsmn]

Hi, Seat Leon FR 2017 ver. 0462. H29.204.28.4_STD2Plus_EU

Getting this message: Error: variant conflict. Medium: Device doesn't support this (MainUnit: variant)

SD CARD: fat32.

My location is Israel if it helps somehow. Thanks for this tool and for the Performance monitor!!!

[dfs-]

@vldsmn - MIB2STD is not supported by the toolbox, so the error you receive is correct and not related to this issue.

[vldsmn]

@dfs- Thanks!

[DejanBukovec]

@jilleb if you need some testers of image Im availible :) Do you maybe have some estimated time when image will be availible? I need to enable 3rd party apps on android auto and this make me crazy because there is no way to root my phone(Huawei Mate RS) and would like use some diagnostic apps on my headunit display(MIB2 HIGH)... Do you think that installation of your scripts do not work because maybe we use different unit language/localization? What language/units/datetime settings do you use?

[jilleb]

@DejanBukovec , it's already done: https://www.dropbox.com/s/ien7m3gif6qt88i/Toolbox.zip?dl=0 But the first test wasn't succesful, still the same error, while it's working on other units. But feel free to try it.

I highly doubt it's because of language/localization, because I tested it with Dutch, German, Spanish and English units, all with success.

[jilleb]

okay.. new theory: Maybe the backdoor I'm using got fixed by the developers? I am using the payload feature in SWDL. it could be that the devs noticed this was a security flaw in their units.

I would like to know: did any of you people got their radio's/cars very recently, or got any updates done by their dealers?

[olli991]

Build in October 2018, delivered December 2018. No visit at the dealer since delivery pickup. So it's a Modelyear 2019 car with already copper emblems (cupra)

[dfs-]

As stated above. Mine got updated from 0702 to 1233. This was done on 01.08.2018.

[1LucKyLuke]

Got mine freshly build in May this year. No visits to the dealer since then.

[DejanBukovec]

@jilleb Im try it on to different sd cards and produce same errors. Also changing language from Slovenian to English do not help.

My car has been builded in may 2018 and came with FW 1219 and maps 0166 in januar 2019 I have it at dealer to activate MapCare and after that manualy update maps to P175 and few months ago to 177. FW of device is all time same. Green menu Im enable few days ago with OBD11 app.

[jilleb]

Okay I'll test some things tonight. I have some new inspiration

[DejanBukovec]

@jilleb if we can help somehow with some informations from unit(received from OBD11) let us know... Maybe with some test image which do not include full toolkit but only some debuging info and can be later overwritten by full toolkit ...

[dirk3012]

I Help too. VCDS and VCP.

[hxigor]

I can confirm the "can't read metainfo2.txt" error on Skoda 1163. I tried the unzipped zip file of downloaded repo as well as the etcher image above - same result. Maybe an interesting information - my unit is unblocked (hacked FECs), it's completely visible for diagnostics and green menu is available (according to some informations a lot of hacked units don't have green menu and are invisible for diagnostics unless put into special mode).

[jilleb]

This is a frustrating error... especially since I've gotten reports from people that it's working on units with the same firmware version. 😭

What are the variables here?

• Firmware version (same versions, different results)
• Hardware version (but.. should not be an issue)
• Is the unit original from factory or a hacked/patched one?
• Are there other updates installed? (Maybe VAG group issued a patch? Check the software install history on the unit)

[DejanBukovec]

@jilleb how can we help you?

[AndrexOfficial]

Same issue on Discover Pro 9,2 MIB2 High - "Unable to read release information file" My MIB SW should be supported.

System description	MU-H-LND-EU
SoftwareVersion	1161
HardwareVersion	H54
VW/Audi part number	5NA035022B
Hardware part number	5NA035022
Coding	02731001000000006111010400880A301F0103F401200400FF
ASAM/ODX file identification	EV_MUHig4CGen2HBAS
ASAM/ODX file version	001001

Tried with all types of SD format but still not working

[dirk3012]

My MIB2 from 2017 had the firmware 1121, I updated it myself 4 months ago to 1367, SD with 1367 I have here.

Before I updated it: Adresse 5F: Informationselek. I (J794) Labeldatei:| 5G0-035-MIB-HGH2.clb Teilenummer SW: 5NA 035 042 A HW: 5NA 035 042 Bauteil: MU-H-LN-EU H54 1121
Seriennummer: A847E0HS005836 Codierung: 02731001000000005111000200080A101F0107F4012004009F ASAM Datensatz: EV_MUHig4CGen2HBAS 001001 after updating it: Adresse 5F: Informationselek. I (J794) Labeldatei:| 5G0-035-MIB-HGH2.clb Teilenummer SW: 5NA 035 042 D HW: 5NA 035 042 Bauteil: MU-H-LN-EU H54 1367
Seriennummer: A847E0HS005836 Codierung: 02731001000000005111000200080A101F0107F4012004009F ASAM Datensatz: EV_MUHig4CGen2HBAS 001001

[AndrexOfficial]

My MIB2 from 2017 had the firmware 1121, I updated it myself 4 months ago to 1367, SD with 1367 I have here.

Before I updated it: Adresse 5F: Informationselek. I (J794) Labeldatei:| 5G0-035-MIB-HGH2.clb Teilenummer SW: 5NA 035 042 A HW: 5NA 035 042 Bauteil: MU-H-LN-EU H54 1121 Seriennummer: A847E0HS005836 Codierung: 02731001000000005111000200080A101F0107F4012004009F ASAM Datensatz: EV_MUHig4CGen2HBAS 001001 after updating it: Adresse 5F: Informationselek. I (J794) Labeldatei:| 5G0-035-MIB-HGH2.clb Teilenummer SW: 5NA 035 042 D HW: 5NA 035 042 Bauteil: MU-H-LN-EU H54 1367 Seriennummer: A847E0HS005836 Codierung: 02731001000000005111000200080A101F0107F4012004009F ASAM Datensatz: EV_MUHig4CGen2HBAS 001001

Can you share and send link of the latest firmware you have installed? because I'm looking for that too :)

[dirk3012]

I had paid 80 euros for it. But OK. Let's ask jilleb the link here.

[hxigor]

So here are my details: Control Module Part Number: 565 035 021 B Component and/or Version: MU-H-LND-EU H54 1163 Software Coding: 037302010000000041110002000802002F0100E401200400DF Brand: Skoda Date of production: 20.11.2017 Previous updates: none, was on stock 1163, even the maps were the original 2018 ones

I bought the unit advertised as hacked - which is not true as the component protection got active when I placed it into car today and of course the map database cannot be enabled. So the unit is stock with SW 1163. Component protection was solved at a dealer this afternoon and I still get the same error "can't open/read release info". Tried different file formats, different SD cards, same result.

Just an hour ago I updated the unit to SW version 1440, some things have changed: Control Module Part Number: 565 035 021 E Component and/or Version: MU-H-LND-EU H54 1440

And guess what - same error, still no joy! I have no idea what can be the problem :-( I double checked, the developer menu is on. Could be that it's something about coding or some adaptation? Or the problem is that I have the unit on my table and it's hooked only to a gateway?