Can't read release info

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

Same error with fw 1163 (skoda)

Make sure you have your SD card formatted as Fat32

I have try in fat, FAT32 and exFat

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

@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 , 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

I have tried with the same result

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

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

Check out the latest commit, should work.
Tested it in 3 different radio's today: latest Skoda, Seat and VW MIB2 High.

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

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

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.

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.

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"?

Take the zip file from the release.

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).

I can confirm the same issue with an MIB2 Columbus, with K firmware.
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.

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

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.

And you get the same error?

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

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

Not working with Skoda 565035021B 1240 firmware

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?

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

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

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

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.

Hi,
Seat Leon FR 2017 ver. 0462.
H<IP_ADDRESS>_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!!!

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

@dfs- Thanks!

@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?

@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.

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?

Build in October 2018, delivered Dezember 2018. No visit at the dealer since delivery pickup

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

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

@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.

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

@jilleb if we can help somehow with some informations from unit(received from OBD11) let us know...

I Help top. VCDS and VCP.

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).

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)

@jilleb how can we help you?

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

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:
Adressword  : 5F (Informationselektronik 1} - J794  MU-H-LN-EU
VAG Nr. SW: 5NA035042A  HW: 5NA035042
SW Version 1121
Codierung<PHONE_NUMBER>0000005111000200080A101F0107F4012004009F
ASAM: UDS, EV_MUHig4CGen2HBAS 001001
DATASET: V03935262VW
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:<PHONE_NUMBER>0000005111000200080A101F0107F4012004009F
ASAM Datensatz: EV_MUHig4CGen2HBAS 001001

@dirk3012 Would you share firmware with us? 🤔 Need Poi at the AID 😊

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:<PHONE_NUMBER>0000005111000200080A101F0107F4012004009F
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:<PHONE_NUMBER>0000005111000200080A101F0107F4012004009F
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 :)

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

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:<PHONE_NUMBER>00000041110002000802002F0100E401200400DF
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?

Another few hours spent, nothing works with this damn unit. I did a complete reflash again with SW 1440, still doesn't work.
Unfortunately I don't know the root pw for SW 1440, I just can read the log. Just the SD card inserting is logged with MEDIUM_UNKNOWN -> MEDIUM_INSERTED, but the update start or error is not logged.
@jilleb I attached the Putty log, maybe anything useful for you?
putty.log

I'll have a look. Can you maybe try to install the toolbox SD by enabling SWDL Ignore region/variant from green menu?
I'll look for a pass so you can install the toolbox manually.

@jilleb just to be clear we normaly install this update by holding menu button for around 5 seconds until it open yellow menu(Service mode) and select first option for software update(Software update/versions)?
Or we must normaly install this toolbox from some other option(SWDL in Testmode menu)? Or somewhere in green menu?
Does this file help you?
AllVersionInfo.txt

@jilleb Unfortunately there's no "Ignore region/variant" checkbox in GEM of this unit. The GEM version is 4.12st, there is only one entry "User Defined SWDL" in the production/rcc_prod/swdl_prod menu.
@DejanBukovec I think it should be the same, SWDL in Testmode just redirect you to the update screen. The difference ist that going through Testmode you can enable "Software download manual download".

Skoda Octavia 5E
Build date : 5.12.2017
GPS up to date (2019/2020)
Tried with Skoda Kodiaq too, same FW (1163), without success
AllVersionInfo.txt

@hxigor I am also on GEM 4.12st in a  2018 A5 B9. MIB version is MHI2Q_ER_AUG22_P4212 with MU software 1177. It appears this is a newer qualcomm chip which replaced the old nvidia.
When attempting to load the update from the SD card, I was faced with the following error:
A variant conflict has occurred! Main Unit version: FMQ-P-TNDL-EU-AU-MLE. Release metainfo version ...........
It appears the skipCheckSignatureAndVariant tag in the metainfo2.txt file is being ignored.

Variant MIB2P wasn't supported, but in my most recent commit I included the variant for P as well.

@jilleb Thanks. I need to download the latest version then. I'll post back with my results.

My unit in green mode show also in left top corner GEM 4.12st ...

@jilleb so re-downloaded all files to include the latest commit. I am now faced with metainfo2.txt signature is not correct error.
Should I have "User Defined SWDL" enabled in the production/rcc_prod/swdl_prod menu?

Another few hours spent, nothing works with this damn unit. I did a complete reflash again with SW 1440, still doesn't work.
Unfortunately I don't know the root pw for SW 1440, I just can read the log. Just the SD card inserting is logged with MEDIUM_UNKNOWN -> MEDIUM_INSERTED, but the update start or error is not logged.
@jilleb I attached the Putty log, maybe anything useful for you?
putty.log

Please do you share 1440 firmware?

Let's bring a little more structure into this topic, and please don't ask for firmware here. Drop me a message on facebook if you need anything.
Signature is not correct error: Can you check the metainfo has checksum cb48da84e8eb0a4f99e3c89e9a2c1e911eadd7ff inside it?
We tested on MIB2P with this metainfo, and it allows installation of the new files. The only thing that doesn't seem to go well is the placement of new scripts after install, but that's something we will investigate.

SW Train Version: MHI2_ER_SEG11_P4708
SW MU Version: 1409
Partnumber: 5F0035020H
HW-Version: 5F0035020
Address 5F: Information Electr. (J794)       Labels:* None
Part No SW: 5F0 035 020 H    HW: 5F0 035 020
Component: MU-H-ND-EU    H54 1409
Serial number:
Coding: 04738001FF0A00001111110100890A232F0102F401200400BE

With Jillie's help i updated my VW infortainment to 1367 but sadly still same metainfo2.txt error 😥

@jilleb I tried checking User defined SWDL in GEM, didn't help. I compared the AllVersionInfo.txt files posted by people who have problem with my AllVersionInfo and I can't find any relation. What's somewhat interesting that I have a Skoda unit and my branch is rel/CLU8_SEAT, @peterbensch has also Skoda unit but his branch is rel/CLU8 and finally @DejanBukovec has a Seat unit with a branch rel/CLU8_AU. What's interesting, people who report a problem have H54 units, so I have a bad feeling that our problem could be hardware specific? Is there any successful installation of the toolbox on a H54 unit?
Added after another hour or two:
I was playing with metainfo2.txt from the latest commit. It seems the problem is with the latest entry containing the payload. When I removed it completely, I got no error and I can choose the MQB Coding Toolbox V2. As I like to play, I continued and have found out that the problem is in the destination! When I change the Destination value to (obviously stupid) /net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd, I get no error! Changing back to default /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd brings the error back. So the question is, what's wrong with this destination path?

The issue is not with the H54 units, because my own unit is one of them.... 😏
Good research on the path. Let's try one with path traversal,
/net/mmx/mnt/navdb/PersonalPOI/../../../../../../../../../../../../../../../net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd

Sooo...  But we're still not at the finish line, the payload update fails with error 131 :-(

Okay, that's something.
I've seen error 131 before. Can you retry in manual swdl mode and select the poi update and payload?

Same error with manual checked and just personal poi with payload selected

I can confirm that checksum is as described.

We tested some more, and it turns out that the following is happening:
If you update the io controller to the latest version, it's working. If you use an old version, metainfo error. So I guess updating firmware doesn't update ioc... I'll look some more into this.

Is possible update io controller by same methode as fw(by sd card)? Or dealer must do this?

How is possible update io controller? if is possible to update send me files i will try

Regarding the signature not correct error, can you please advise how the checksum is calculated? Perhaps the calculation is different for my version. Thanks

Signature is something other than checksum.
Checksum is calculated over entire metainfo, excluding the line with checksum

@jilleb OK, I understand. so it appears this version ignores the skipCheckSignatureAndVariant = "true", requiring the file to contain the proper signature. I am guessing this is impossible without the private key.

@jilleb The question is how to update the IO controller... I did a complete SW 1440 flash with everything checked and if this didn't update the IOC, then there must be some other way.
Just an idea I'm going to try this evening:
Modify the original 1440 update, add skipCheckSignatureAndVariant and skipMetaCRC properties to metainfo so the changes in files would be accepted. Then modify the finalscript to copy the payload.sh to /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd? I'm just curious about the finalscript, it's calling DisableGEM for disabling GEM? I wish I had a root pass for 1440...
@DejanBukovec The dealers can make updates the same way as we do - through SD card. They are not skilled enough to do it other way.

I played with the original script round and round and when I changed the payload destination to previously mentioned bad location/net/mmx/mnt/navdb/PersonalPOI, the script finished succesfully. It seems to me like the /net/mmx/mnt/app/eso/hmi/engdefs directory is not writable or something like that :-(
Regarding the IOC, I checked the SW 1440 and there are IOC files for MQB V850, app version is 8863 while the bootloader is version 210. I compared the update list of succesfully finished complete SW 1440 update, and both app and bolo match the version from the update package...

I played with the original script round and round and when I changed the payload destination  Regarding the IOC, I checked the SW 1440 and there are IOC files for MQB V850, app version is 8863 while the bootloader is version 210. I compared the update list of succesfully finished complete SW 1440 update, and both app and bolo match the version from the update package...

Is possible to contact me please at  " yanqemil (at) gmail.com " about this? Tnx. Not find any possiblity to personal message.

I have updated from 1240 to 1382 and i have same IOC info, app 8863 , bootloader 210.  You have newer 1440 with same old IOC

Does anyone know the root telnet password mhi2q_er_aug22_p4212, or even the hash, and I will try to use hashcat to reverse engineer it. I would like to try an alternative method for installation.

Not Working on:
Model: VW mk7 (Discover Pro, 3G0 035 021 D)
Sw:    H51 0814
Issue: can't read metainfo2.txt

Installing new IO controller can be done from the console. But maybe it can be done by doing Manual SWDL from the dev menu, and selecting MUNIC and IOC stuff

@jilleb For Skoda the latest SW is 1440 and this contains the old IOC (8863+210). Updating through manual update should work, we just need the new version files. Is it possible to extract it from other e.g. VW update? Bypassing signature check we should be able to flash it I hope. IMHO the pass for 1440 would be better :-P

Not working on:
Seat Leon 5F MIB2 high BJ 2016
VAG Nr.
SW: 5F0035020B
HW: 5F0035020
SW Version 0355
Issue: can't read metainfo2.txt

@hxigor How do you go about bypassing signature check? skipCheckSignatureAndVariant appears to be ignored in my version, or am I missing something?

@turboblade I was thinking about using the skipCheckSignatureAndVariant setting in metainfo. If it will work, then we just need to extract the IOC + MUNIC update from other SW (btw who has the latest, VW, Audi or Seat?) and then force update to units with older versions and we should be complatible with M2T.
I had no time to do more tests, I was busy at work and later busy at home building a two deck Lego garage with my kids :-)

@hxigor Let me know how that goes. On my version, even when skipCheckSignatureAndVariant is used, update still fails on signature.

@turboblade Unfortunately it seems the skipCheckSignatureAndVariant setting doesn't exist or is ignored. I searched all skip* strings in the MIBRoot and found just these:
skipSaveMuVersion skipSaveTrainName skipCRC skipCBConsistencyCheck skipCBConsistencyRccCheck skipCBConsistencyMmxCheck skipCheckVariant skipCheckRegion skipMetaCRC skipMetaChecksum skipRollback skipChecksum skipScriptCRC skipScriptChecksum skipMostPopup skipFileCopyCrc skipFileCopyChecksum skipInvalidateTransactionImageByMmx skipCheckConsitencyImages skipRccInMmxDependencyError skipCheckMmxEmergencyValid skipEraseOrphanedEfsHeaders skipEraseOrphanedImageHeaders skipFile skipResolve skipResolveFiles skipRestore skipRestoreFiles skipSendErase skipReceivedErased skipSendData skipReceivedData skipSendTransferDataExit skipReceiveTransferDataExit skipSendCrc skipReceiveCrc skipBehaviourAvail skipDir skipDirection skipScope skipRequest
There's no trace of skipCheckSignatureAndVariant .
@jilleb Can you please share information what is the minimum version of IOC we need?
I have ordered another MIB unit, this time 565 035 021 D with H55 and SW 1382 and we'll see. Don't ask me how many MIB units I have and in any case don't tell my wife 😇

@jilleb:
I have another incompatible unit :-(
SW Train Version: MHI2_ER_VWG11_K0261
SW MU Version: 1100
Original part number: 3G0035043 H33 with SW 0078
After update to latest available version:
3G0035043 H33 with SW 1100, IOC version is 146 BOLO and 3205 APP

SW Train Version: MHI2_ER_SEG11_P4708
SW MU Version: 1409
Partnumber: 5F0035020H
HW-Version: 5F0035020
Address 5F: Information Electr. (J794) Labels:* None
Part No SW: 5F0 035 020 H HW: 5F0 035 020
Component: MU-H-ND-EU H54 1409
Serial number:
Coding: 04738001FF0A00001111110100890A232F0102F401200400BE

Today I had success with a VW MIB2.5 unit. And was unsuccessful with different MIB2.5 unit.
Successful:
Part No SW: 5NA 035 043 C    HW: 5NA 035 032
Component: MU-H-N-EU     055 1161
Application Version: 16909592
Bootloader Version: 210
Application Version: 8763
Unsuccessful:
Part No SW: 5NA 035 043 A    HW: 5NA 035 043
Component: MU-H-N-EU     H54 1161
Application Version: 16909592
Bootloader Version: 210
Application Version: 8863
My SEAT unit Unsuccessful:
Part No SW: 5F0 035 020 H    HW: 5F0 035 020
Component: MU-H-ND-EU    H54 1409
Application Version: 16909592
Bootloader Version: 210
Application Version: 8863
Could it be that newer IUC application doesn't support this script?

That sounds very very plausible.

okay... new idea, I just need someone to test it ;-)
@hxigor , can you test if the following works:

remove the payload stuff from the metainfo2.txt
change the [PersonalPOI\InfoFile\0\default\File] section so the destination goes from /net/mmx/mnt/navdb/PersonalPOI/Update.txt to /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd
recalculate metainfo checksum
retry installing

Maaaaaybe we don't need the payload, but we can use the copy mechanism from the Update file ;-)

@jilleb Maybe you could open a test branch with those modifications ?

Good idea. I'll have to see(tomorrow) how that works with git, but let's try :-)

I tried above method, but doesn't work. Soon as the destination is changed doesn't work. With just payload removed(And checksum ofc) metainfo is read, but when destination is changed, doesn't work.

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

For the list:

I ran on Seat FW 1338 with an already installed IOC App 8863 from factory which wasn't compatible.
Updated to 1409 with no problems. IOC App still is 8863.

8863 seems to be a newer version than 1409 comes with so there is no downgrade option. like listed above, 8763 is the compatible version for this. I think we have to find a way down or there maybe is a even never IOC-Version which brings back the backdoor (unlikely).

@hxigor , can you test if the following works:
* remove the payload stuff from the metainfo2.txt

* change the [PersonalPOI\InfoFile\0\default\File] section so the destination goes from /net/mmx/mnt/navdb/PersonalPOI/Update.txt to /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd

* recalculate metainfo checksum

* retry installing

I tried it with 3G0035043 H33 SW 1100, IOC version 146 BOLO and 3205 APP - no luck :-(

@jilleb Hi jilleb
You know how can be the ignore region and variant activated in green menu?

Although not a solution waited for, but for me I got Android Auto patched running the script from shell.
Could it be maybe possible to install toolbox also from shell?

Although not a solution waited for, but for me I got Android Auto patched running the script from shell.

that's great news :-)

Could it be maybe possible to install toolbox also from shell?

Yes. Copy the payload.sh to /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd
Then go to the green menu, you will find a new menu: mqbcoding. Install the scripts from SD-card by running the script button. Done :-)

@jilleb I tried to use these options but it still does not work:
SkipSaveTrainName="true"
skipCheckSignatureAndVariant="true"
skipCheckRegion="true"
skipCheckVariant
skipCheckRegion
skipMetaCRC
skipMetaChecksum
skipRollback
skipChecksum
Did you find any solutions for Discover Pro MIB 2.5?
Can you tell me where can I get the latest MIB 2.5 firmware without going to a Volkswagen Dealer?
Thanks

Is There a newer Firmware Than 1367 for Vw mib ?

@jilleb I tried to use these options but it still does not work:
SkipSaveTrainName="true"
skipCheckSignatureAndVariant="true"
skipCheckRegion="true"
skipCheckVariant
skipCheckRegion
skipMetaCRC
skipMetaChecksum
skipRollback
skipChecksum

Great work. Thanks.

Did you find any solutions for Discover Pro MIB 2.5?
Can you tell me where can I get the latest MIB 2.5 firmware without going to a Volkswagen Dealer?
Thanks

It is developed by me on a MIB2.5 so yes, it's compatible. Just not all ioc versions, so it seems. It seems to be more common that it's not compatible with units patched by APG and such.
The latest firmware I know of is 1367.

Another one with same error. Unit info:

SW train version: MHI2_ER_VWG11_P2103
SW MU version: 0317
Part number: 3G0035020B
SW version: H25.14.38_HIGH2_EU
IOC (bootloader/app): 206/5723

This 0317 firmware is quite old (2015?), never updated as you can imagine. Based on the list of working firmwares, I was expecting this old one to sideload the toolbox seamlessly. But it didn't.
I tried the path traversal trick and managed to avoid the metainfo2.txt error, but sadly it fails after a reboot with error code 137 (any different from @hxigor 131 error?). I dumped MMX/RCC core files and error logs to SD right after failing with the toolbox, if they help you @jilleb to reverse engineer the issue or if I can help you out with anything else just let me know.

Another one with same error. Unit info:

SW train version: MHI2_ER_VWG11_P2103
SW MU version: 0317
Part number: 3G0035020B
SW version: H25.14.38_HIGH2_EU
IOC (bootloader/app): 206/5723

This 0317 firmware is quite old (2015?), never updated as you can imagine. Based on the list of working firmwares, I was expecting this old one to sideload the toolbox seamlessly. But it didn't.
I tried the path traversal trick and managed to avoid the metainfo2.txt error, but sadly it fails after a reboot with error code 137 (any different from @hxigor 131 error?). I dumped MMX/RCC core files and error logs to SD right after failing with the toolbox, if they help you @jilleb to reverse engineer the issue or if I can help you out with anything else just let me know.

Question: does this unit have a component protection patch installed?

AFAIK no, it is stock.

Okay good to know that. I've seen many reports from people having this issue and most of them had a unit that came from APG, and wasn't originally installed in their car. Still makes it hard to pin down the cause of the error haha.

Nah, this unit came with the car, all FeC are genuine 😅
Do you think those logs may come handy, or are they just useless? Also, I must say that when I did the path traversal I didn't change any checksum, but I suspect I should have done so...

Great :-)
If the checksum wasn't right, the swdl wouldn't start, it will throw a checksum error.
If only we knew what those error numbers meant haha. I havent been able to find it anywhere.
Can you check your ioc version?

Ouch, I must correct the checksum then. I am afraid I don't know the algorithm it uses. SHA-1 or MD5 maybe?
My IOC bootloader is 206, app 5723. I am still wondering why all the guys that face the metadata2.txt error have much newer firmware than me...

@jilleb Do you have the VW MIB 2.5 1367 firmware to share with me, cause I'd like to update my unit.
Let me know.
Thanks

@jilleb did you also try to use these options in the release info file?
skipMetaChecksum = "true"
skipFileCopyChecksum = "true"
UserSWDL = "true"
Do you have the VW MIB 2.5 firmware 1367 to share with me?

@jilleb After some research, I'm writing a script to toggle options in metainfo2.txt and correct checksums automatically, based on info here: https://github.com/jimmyH/mypois
File checksums are pretty straightforward, SHA-1 digest, that's it. Directories checksums are a bit tricky, you create a hashes.txt file containing 512KB SHA-1 digests of all files in that dir and subdirs, with a particular structure. Then, the dir checksum is the digest of the hashes.txt file. Finally, the MetafileChecksum is, as you said previously, the digest (SHA-1 again) of metainfo2.txt before adding the MetafileChecksum line. However, I still have some questions in my head, maybe you @jilleb know the answer:

What is the right way to terminate lines in hashes.txt and metainfo2.txt? I am using \r\n, but I've seen POIs in some VW forums just using \n.
Do you have to add new lines at the bottom of hashes.txt and/or metainfo2.txt? At the moment I'm adding \r\n\r\n in hashes.txt and \r\n in metainfo2.txt, to mimic what is inside your commit.
Is it necessary to keep the comments in header of metainfo2.txt? I see it is a ini file, so comments should be totally irrelevant, but actually it makes a difference in MetafileChecksum if you keep or remove comments. Again, I've found POIs with and without this header.
You've got (intentionally?) a blank line at [PersonalPOI] section in metainfo2.txt. I know it doesn't change anything for a parser to read the options, but again that blank line changes MetafileChecksum.
In section [PersonalPOI\PayLoad\0\default\File] you wrote the checksum in upper case. Using lower case as in other checksums lead to a different MetafileChecksum.
Last but not least, is there any particular order for preferences in metainfo2.txt? A different order in any entry leads to a different checksum.

If I mimic your commit in all the above points I get the same checksums you typed in the files. However, a change on any of these points or even using the script in https://github.com/jimmyH/mypois leads to completely different checksums in dirs and MetafileChecksum.
Any clue of the right settings? Could the checksum check be more "sensible" to any of the above points in some units/firmwares, and be the reason why some of us get an error when loading your toolbox?

@jilleb After some research, I'm writing a script to toggle options in metainfo2.txt and correct checksums automatically, based on info here: https://github.com/jimmyH/mypois

Great work!! :-)

However, I still have some questions in my head, maybe you @jilleb know the answer:

What is the right way to terminate lines in hashes.txt and metainfo2.txt? I am using \r\n, but I've seen POIs in some VW forums just using \n.

All of the metainfo files I've seen have CR/LF, so I think the safe way to go is \r\n

Do you have to add new lines at the bottom of hashes.txt and/or metainfo2.txt? At the moment I'm adding \r\n\r\n in hashes.txt and \r\n in metainfo2.txt, to mimic what is inside your commit.

I've had issues when I removed the final \r\n from the metainfo.txt, so it's best to keep the CR/LF:

hashes.txt I rarely ever touch, I used a POI-distribution generator to generate the correct files. I think it's safe fo use \r\n\r\n indeed.

Is it necessary to keep the comments in header of metainfo2.txt? I see it is a ini file, so comments should be totally irrelevant, but actually it makes a difference in MetafileChecksum if you keep or remove comments. Again, I've found POIs with and without this header.

No, you  can remove them. I kept them because of consistency with regular metainfo's and lazyness ;-)

You've got (intentionally?) a blank line at [PersonalPOI] section in metainfo2.txt. I know it doesn't change anything for a parser to read the options, but again that blank line changes MetafileChecksum.

Oh that was not intentional, it was just there in the file I used as a base, I guess. It shouldn't make a difference if you remove it :-)

In section [PersonalPOI\PayLoad\0\default\File] you wrote the checksum in upper case. Using lower case as in other checksums lead to a different MetafileChecksum.

that's correct. The SWDL mechanism doesn't see lower/upper as a different checksum, but the checksum of the entire file is different when I would change it between upper/lower, of course. I use upper-case in the file checksum, because the tool I use to generate the checksum puts it out in all caps. We could try and see what happens if we put it to lower case, if the releaseinfo errors dissappear, but I would be surprised if that was the case haha.

Last but not least, is there any particular order for preferences in metainfo2.txt? A different order in any entry leads to a different checksum.

Preferences like skipCheckSignatureAndVariant and such? There shouldn't be a difference, as long as they stay in the same sector.

If I mimic your commit in all the above points I get the same checksums you typed in the files. However, a change on any of these points or even using the script in https://github.com/jimmyH/mypois leads to completely different checksums in dirs and MetafileChecksum.
Any clue of the right settings? Could the checksum check be more "sensible" to any of the above points in some units/firmwares, and be the reason why some of us get an error when loading your toolbox?

The strange thing is.. I've checked the mibroot of (for instance) v1367, the version I'm using on my own unit. It has certain swdl preferences-flags and sections like payload that are supported. But for some reason some people have difficulties when using the same v1367 firmware... I have no clue why that happens... but I'm sure your tool will make testing various scenarios easier!
It is also strange that all the guys here with issues share a narrow range of fairly new firmwares, but I have a very old one and a similar situation. And even more strange is that just a path traversal trick with no checksum update skips the metainfo2.txt error (why? checksum is wrong!) and some steps further it throws an undefined error 131 for some guys and 137 for me.

I'd be very keen to check my file system, but I don't have pass for root in my unit, so telnet is not an option for me. I will keep working on the checksum calculation with different combinations of new line terminators, upper/lower cases, etc, and will report the results.

@Alreiber , what firmware is it?

@jilleb  I tried several units, VW, Skoda, even crossflashed ones, different versions, oldest was VW 0199 and newest VW 1367 or 1427, SK 1440 and I was not lucky to install M2T using the easy way - I had to use terminal and copy the files to desired locations... All of these units had stock sw, no component protection removal patch. Later I patched just the FEC check to activate all features these units can have, but this had no influence and always I got the metainfo error.

@hxigor interesting... it's such a weird issue haha

@Alreiber , what firmware is it?

All stock.

Fw 0317. All stock.

3mgaGO4k

Do you know password on FW 0814 firmware?

Although not a solution waited for, but for me I got Android Auto patched running the script from shell.
Could it be maybe possible to install toolbox also from shell?

@magna413 Do you have some instructions how to connect shell to unit and install android auto patch?

Fw 0317. All stock.

click for password

Great, I'll see if that works. Anyhow let's see if any change in checksums and metainfo2.txt/hashes.txt format makes it work too. Sideloading with SWDL should be a less fragile way to access the file system than relying on firmware-specific passwords (=on firmware updates that most of us will never have access to).

Great, I'll see if that works. Anyhow let's see if any change in checksums and metainfo2.txt/hashes.txt format makes it work too. Sideloading with SWDL should be a less fragile way to access the file system than relying on firmware-specific passwords (=on firmware updates that most of us will never have access to).

Fingers crossed! :-) If you have any questions, let me know :-)

@jilleb did you also try to use these options in the release info file?
skipMetaChecksum = "true"
skipFileCopyChecksum = "true"
UserSWDL = "true"

Yes.
UserSWDL is already in there
The others didn't seem to do much.

Do you have the VW MIB 2.5 firmware 1367 to share with me?

Yes I do. But let's not turn this into a "send me a firmware" topic 😄

@jilleb just tell me where can I contact you via PM and let me know, cause I have another MIB2.5 unit and I'd like to try with a newer firmware.
I still try every time with different metainfo2.txt options ;)

@jilleb just tell me where can I contact you via PM and let me know, cause I have another MIB2.5 unit and I'd like to try with a newer firmware.
I still try every time with different metainfo2.txt options ;)

jjberends gmail

@jilleb thanks dude, but I also found your email by hacking the GitHub APIs.
Let me know how can I help you with this issue, I have 2 Discover Pro MIB2.5 and a Discover Pro MIB2.5 (Japanese Version) ;)

Fingers crossed! :-) If you have any questions, let me know :-)

It did the trick, telnet done! I've written the output of find . ! -type l at the root dir to the SD to see at home if somewhere there is anything relevant. For a moment I though about dumping the whole filesystem to the SD card to do some research at home, but I guess it will take a huge amount of time. If you think that should be doable, just let me know - I'm familiar with Linux but not with QNX.

@Alreiber, we can try and add a section like this instead of the payload part that is currently causing release-info issues on units:
CheckSumSize = "524288"
CheckSum = "fc19612fbd5cb85d4f36e55f01083e78925baefb"
FileSize = "640"
Version = "3"
Source = "somefile.txt"
Destination = "/net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"
DisplayName = "Database Information"
DeleteDestinationDirBeforeCopy = "true"
UpdateOnlyExisting = "false"

Sure, let me finish the tool first. I'm doing it more versatile to quickly generate all different combinations of metafile/hashes formatting. Hopefully it will be ready by the end of the week.

same on Seat Leon MIB2High
SW Train Version: MHI2_ER_SEG11_S2130
SW MU Version: 0355
Partnumber: 5F0035020Z
HW-Version: 5F0035020
SW-Version: H25.14.70_HIGH2_EU
i try to login per telnet but i dont have the root password
Does anybody know this?

Hi guys! I'm another one who got metainfo read error on VW MIB2.5 v1367 (bootloader 210, application 8863)
@jilleb is it possible to add script files manuall?
Mount sdcard and cp all of it to mib filesystem?
Thank you!

Hi guys! I'm another one who got metainfo read error on VW MIB2.5 v1367 (bootloader 210, application 8863)
@jilleb is it possible to add script files manually?
Mount sdcard and cp all of it to mib filesystem?
Thank you!

Yes it's possible. Just copy payload.sh to mqbcoding.esd in the eso/hmi/engdefs folder. I'll add it to the readme.

And all scripts from /Phone/Apps/0/default/ to /eso/bin/PhoneCustomer/default/?

No, these will copy as soon as you press the button in green menu.

@jilleb  Maybe it would be a good idea to add also "Toolbox update" as another option - for units which the payload trick doesn't work it's necessary to install the toolbox using console. Each time there's a new toolbox, the unit has to be updated by computer. If there would be an "update_toolbox.sh" script, it could copy the new mqbcoding.esd file from sd card to the correspoding location :-)

The New Tiguan Discovery Pro 2 , got the same failure to read 'metainfo2.txt'
There's some VW workshops to mod this for customer and cost almost $100USD to feature it .
Are they change the firmware?  I can confirm that the HW is supported.
SW MU : 0836
Part: 5NA035032B
SW: H29.319.29_HIGH2GP_TWN
===This is dumped from TestMode===
Current train = 'MHI2_TW_VW48x_P0952'
MainUnit version = '0836'
Exceptionlist:
APP: CLU8_MMX2_VW_TW_G13_026PROD
Branch: rel/CLU8_ASIA
Changelist: 10668084
Framework (MMX): 5.49.12.SR3 MIB2MAIN I199 CI68
Framework (RCC): 5.49.10 MIB2MAIN I199 CI68
GraphicsServices: MIB2CLU8 199.1
J9:DSI: 2_67.1
Navigation: Nav2_TW_VD_CLU8_R7281
NavDB: MapDB_TW_VW2_13_PDB1.0
EggnogDB: TAIWAN_1926_190627113
Truffles:
Truffles.Version=710
Truffles.Variant=main_TW
Truffles.Region=TW
Truffles.Date=201906261348
Truffles.NavDB=HERE_2019_1
Truffles.UOTA_VERSION=2367
Truffles.Generation=MIB2
Truffles.ADMINXML_ZIP_ETF_MOD_DATE=2019-06-25
Truffles.CONVERTER_BUILD_DEPOT=//mib_trf/dev/main/esosearch_converter/...
Truffles.ERMA_ID=27808
Truffles.ADMINXML_FOLDER_ETF_TITLE=MIB2_Truffles_TW_CLU13_PDB1.0
Truffles.CONVERTER_BUILD_TIME=2019-06-26T11:48:21Z
Truffles.CONVERTER_BUILD_CHANGELIST=43685025
Truffles.ADMINXML_FOLDER_ETF_ID=1820181
Truffles.ADMINXML_DOWNLOAD_DIR=/data/truffles_xml/TW_2019-06-25_MIB2__Truffles__TW_CLU13_PDB1.0_v1_1821798_main
Truffles.ADMINXML_ZIP_ETF_ID=1821798
Truffles.ADMINXML_ZIP_ETF_MD5=4cdfd3f44681c10a6214acfda40e5ac2
Truffles.ADMINXML_ZIP_ETF_TITLE=MIB2_Truffles_TW_CLU13_PDB1.0_v1.7z
Speech: 129.1704.1-MIB2MAIN
Speech resources: 129.1647.0
sseProc: 1.4.3
HMI:  H29.319.29
GCT version: <IP_ADDRESS>9
VoiceEncoderApp: v2.1.287_FW5.49.12.SR3_TC17.45.05A
GracenoteDB: 14
Gracenote: Revision gdb-EA-0010-<IP_ADDRESS>3-20160802 GNSDK4Auto.
Nvidia: Nvidia_17.45.06-8589238
MME2 version:exFAT-Library: 2016/02/04-14:42:21-UTC
Radiodata: 2.8.0
Radiodata DB: VW_STL_DB 5.2.7
AWP:  2.8.18_5.49.12
IOC: 8863
RCC version info:
version  =  U8826
ipl-version = 1447226
ifs-emg-version = 951
ifs-root-version = 9334
efs-system-version = 0008164
efs-persist-version = 1999
dsp-version = 655755610
RCC label info:
label  = MIB2CLU8-Trunk_rcc2_B1-17283B
MMX Board information:
BOM: 699
Project: 61852
SKU: 0001
Version: 900
serial number:<PHONE_NUMBER>109
Latest esolutions-changelists per depot:
mib2_bin: 10668099
mib2_com: 10581540
mib2_con: 10616358
mib2_diag: 10581540
mib2_epp: 10581540
mib2_fec: 10581540
mib2_ibr: 10581540
mib2_javatools: 10581540
mib2_mhd: 10638369
mib2_nav: 10627183
mib2_ols: 10648019
mib2_org: 10581540
mib2_rdv: 10583467
mib2_secure: 10581540
mib2_swdl: 10581540
mib2_tools: 10668149
mib_trf: 10600134
sysapp_spj: 10581540

@brianyou0524 , thanks for the info. Can you point me those workshops? I would like to send them an email, because I totally dislike the idea of people making an insanely high amount of money off of stuff I do in my free time...

@brianyou0524 , thanks for the info. Can you point me those workshops? I would like to send them an email, because I totally dislike the idea of people making an insanely high amount of money off of stuff I do in my free time...

I am not sure how they did it , I can't proof if they are using this toolbox or not .
I don't think your warning will be useful.  My idea is to learn how to get my unit done then I can do it free for my friends and let them know this patent is not for sale and for business

Any update here? I can use the same sd that works on a Skoda 1433 but won’t work in another Skoda 1433.
The only difference was the one that workers was patched. The other one isn’t. So I guess it a problem of non patched units that the check of the files are more strict?

Any update here? I can use the same sd that works on a Skoda 1433 but won’t work in another Skoda 1433.
The only difference was the one that workers was patched. The other one isn’t. So I guess it a problem of non patched units that the check of the files are more strict?

Can You check IUC of both?

@andy0172 Who did the patch of the unit, SRT, APG, DJDAR3K, MIB2HAX or somebody else? Properly patched units have disabled also checksum checking so you can freely edit metainfo without need of checksum recalculation

@jilleb I would like to ask if you have already on hand update for VW discover MIB2.5 version 1427? Thanks. David

@jilleb I would like to ask if you have already on hand update for VW discover MIB2.5 version 1427? Thanks. David

That's not for MIB2.5.  and please stay on topic. This is not the firmware info topic

@andy0172 Who did the patch of the unit, SRT, APG, DJDAR3K, MIB2HAX or somebody else? Properly patched units have disabled also checksum checking so you can freely edit metainfo without need of checksum recalculation

It was patched by Mike, a buddy of Jilleb.

I have the same issue.

HW: 3G0035044
Current MU: 1187
HW: H41
Softwareversion: H28.28.199_HIGH2_EU
I was first on FW 199, then 814, now 1187
Neither worked.
If you do manual installation, does this avoid the metainfo error?

@capula I read somewhere that you have PDF that I need it. Plz send it to me

hi, send me your email, to send you a pdf.

<EMAIL_ADDRESS>tnkx man

I installed it with succes by using manual method.
just buy the d-link adaptor and then it's easy
(if you use a macbook, you have to install telnet, because apple removed telnet from the latest OS X)

what manual method? can you provide tutorial?

See the readme file...

i tried it with no luck :(

Can you be more clear where the manual process goes wrong?

How do I find out what password I need for the Manuell installation

Can you be more clear where the manual process goes wrong?

i was reading old readme.... when i read current readme, i found that, i dont have tools for this (may i use any usb/lan adapter?) and also dont know how find login information.

I installed it with succes by using manual method.
just buy the d-link adaptor and then it's easy
(if you use a macbook, you have to install telnet, because apple removed telnet from the latest OS X)

Can you explain how you did that with Mac or Windows?
Cause I tried today with the D-Link DUB E-100 connected to the MIB’s USB port and the Ethernet cable connected to my Mac but it was refusing connection via Telnet to IP address: <IP_ADDRESS>

Connect the D-Link DUB E-100 (make sure you have HW B,C or D; others don't work)
Put your mac in fixed ip, f.ex. <IP_ADDRESS> with gateway <IP_ADDRESS>
to check the connection ping in terminal to <IP_ADDRESS>
To enable telnet in terminal on mac, download homebrew, and after installation install telnet in homebrew

I installed it with succes by using manual method.
just buy the d-link adaptor and then it's easy
(if you use a macbook, you have to install telnet, because apple removed telnet from the latest OS X)

And what's the point with the manual install? If you can connect to the terminal, all what toolbox can, you can do it manually too 🤔

because I have a metainfo error when doing an install from an SD card.
What's the point? To have the toolbox on your MIB and you don't need a PC/Mac to make changes

because I have a metainfo error when doing an install from an SD card.
What's the point? To have the toolbox on your MIB and you don't need a PC/Mac to make changes

Okay you don't understand. If you have access, you don't need toolbox.

If anyone who succeeded lives near The Hague let me know.

Connect the D-Link DUB E-100 (make sure you have HW B,C or D; others don't work)
Put your mac in fixed ip, f.ex. <IP_ADDRESS> with gateway <IP_ADDRESS>
to check the connection ping in terminal to <IP_ADDRESS>
To enable telnet in terminal on mac, download homebrew, and after installation install telnet in homebrew

Hey mate, I tried both with Windows and with MAC but I can't open the Telnet connection.

This is what I see from the ip-config of my MIB2:

С уважением, Алексан Алексанян.
От: AndrexOfficial
Отправлено: 31 марта 2020 г. в 0:09
Кому: jilleb/mib2-toolbox
Копия: alexan1988; Mention
Тема: Re: [jilleb/mib2-toolbox] Can't read release info (#1)
Connect the D-Link DUB E-100 (make sure you have HW B,C or D; others don't work)
Put your mac in fixed ip, f.ex. <IP_ADDRESS> with gateway <IP_ADDRESS>
to check the connection ping in terminal to <IP_ADDRESS>
To enable telnet in terminal on mac, download homebrew, and after installation install telnet in homebrew
Hey mate, I tried both with Windows and with MAC but I can't open the Telnet connection.
This is what I see from the ip-config of my MIB2:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Connect the D-Link DUB E-100 (make sure you have HW B,C or D; others don't work)
Put your mac in fixed ip, f.ex. <IP_ADDRESS> with gateway <IP_ADDRESS>
to check the connection ping in terminal to <IP_ADDRESS>
To enable telnet in terminal on mac, download homebrew, and after installation install telnet in homebrew

Hey mate, I tried both with Windows and with MAC but I can't open the Telnet connection.

This is what I see from the ip-config of my MIB2:

The netmask 0xffffffff00 on the MIB unit corresponds to a mask of <IP_ADDRESS> (/24), not <IP_ADDRESS> (/16) as advised earlier. This may be the cause of your issue.

Connect the D-Link DUB E-100 (make sure you have HW B,C or D; others don't work)
Put your mac in fixed ip, f.ex. <IP_ADDRESS> with gateway <IP_ADDRESS>
to check the connection ping in terminal to <IP_ADDRESS>
To enable telnet in terminal on mac, download homebrew, and after installation install telnet in homebrew

Hey mate, I tried both with Windows and with MAC but I can't open the Telnet connection.
[...]
This is what I see from the ip-config of my MIB2:

The netmask 0xffffffff00 on the MIB unit corresponds to a mask of <IP_ADDRESS> (/24), not <IP_ADDRESS> (/16) as advised earlier. This may be the cause of your issue.

I will try with this netmask, in fact 0xffffffff00 corresponds to a different netmask not the one advised earlier.
@djfanatix How did you succeeded with the connection with a different netmask? How did you install the MIB-Toolbox without finding the MIB's login password?

You have given your computer the same IP like the MIB, so it wont work. Computer needs to have <IP_ADDRESS> !!!

You have given your computer the same IP like the MIB, so it wont work. Computer needs to have <IP_ADDRESS> !!!

correct, I used the gateway <IP_ADDRESS> with succes, actually I don't think you need a gateway

Connect the D-Link DUB E-100 (make sure you have HW B,C or D; others don't work)
Put your mac in fixed ip, f.ex. <IP_ADDRESS> with gateway <IP_ADDRESS>
to check the connection ping in terminal to <IP_ADDRESS>
To enable telnet in terminal on mac, download homebrew, and after installation install telnet in homebrew

Hey mate, I tried both with Windows and with MAC but I can't open the Telnet connection.
[...]
This is what I see from the ip-config of my MIB2:

The netmask 0xffffffff00 on the MIB unit corresponds to a mask of <IP_ADDRESS> (/24), not <IP_ADDRESS> (/16) as advised earlier. This may be the cause of your issue.

I will try with this netmask, in fact 0xffffffff00 corresponds to a different netmask not the one advised earlier.
@djfanatix How did you succeeded with the connection with a different netmask? How did you install the MIB-Toolbox without finding the MIB's login password?

You need to have the password.. Google is your friend

today i've tried on my passat b8 ....same error.... :-(

same Problem here. Skoda Karoq

could someone help me? i'm not able to do manual installation and the "normal" way to install got the error "Can't read release info" - i've tried several times without success.

could someone help me? i'm not able to do manual installation and the "normal" way to install got the error "Can't read release info" - i've tried several times without success.

What goes wrong when doing a manual install?

i don't know how to proceed, i've never do that i'm not a "master" in coding and i don't want to brick my discover pro.

there is an tutorial on first page. if you make this like the text you can´t do brick...
you need to buy D-Link Dub-E100

for tutorial you mean that:
"
How to do a manual installation
Put the mib2-toolbox on an SD-card and insert it into the MIB-unit
Make a connection to the debug console of the unit (either via D-Link Dub-E100 on the USB port, or serial interface on the back of the unit)
Log in
make the mmx app volume writable: mount -uw /net/mmx/mnt/app/
copy mqbcoding.esd to /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd:
cp /net/mmx/fs/sda0/PersonalPOI/PayLoad/0/default/payload.sh /net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd
Hold the MENU button, and go to TESTMODE. On older versions you can go to the developer menu by holding the MENU button for about 10 seconds.
 When you see this, the installation was succesful.
Run the "Get new scripts and files from SD-card (slot1)" script, and additional files will be installed.
You're now done.
Enjoy!
"
if you mean that, for example in the point n.2 (Make a connection to the debug console of the unit) i don't know how to do that...maybe with a full video tutorial i can try...
sorry for being a noob

Do you have a D-Link Dub-E100 or a serial interface? If not, then that's the place to start.

i've just bought d-link - amazon will delivery it to me on monday

i can make an video tut for you

thank you so much! i really appreciate your help

Could I have video as well ?
I plug a Dlink Dub-E100 , but MIB2 can't recognize it

another question ?
"Make a connection to the debug console of the unit (either via D-Link Dub-E100 on the USB port, or serial interface on the back of the unit)"
How to access the back of the unit?  open the panel ? and pull it out?

i've just bought d-link - amazon will delivery it to me on monday

first i made an PDF. no time for now for video. maybe later
https://drive.google.com/file/d/1XuruEgeyIqGKiKP4-H46YeYBbTCXO-gr/view?usp=sharing

another question ?
"Make a connection to the debug console of the unit (either via D-Link Dub-E100 on the USB port, or serial interface on the back of the unit)"
How to access the back of the unit? open the panel ? and pull it out?

yes behind the DVD-Unit

first i made an PDF. no time for now for video. maybe later
https://drive.google.com/file/d/1XuruEgeyIqGKiKP4-H46YeYBbTCXO-gr/view?usp=sharing
I´m not shure you should include this last page in the PDF. It´s actually the infos you need to do it but maybe it´s a bit dangerous for this project to get removed. Just thinking.

first i made an PDF. no time for now for video. maybe later
https://drive.google.com/file/d/1XuruEgeyIqGKiKP4-H46YeYBbTCXO-gr/view?usp=sharing

I´m not shure you should include this last page in the PDF. It´s actually the infos you need to do it but maybe it´s a bit dangerous for this project to get removed. Just thinking.

thank... i edit that...

"Sorry, the file you have requested does not exist." @@
I can't access the link

ok! i've successfully installed it....however another problem...when i try to patch android auto it say: script not found /eso/bin/PhoneCustomer/default/patch_gal.sh .... how to solve it?

ok! i've successfully installed it....however another problem...when i try to patch android auto it say: script not found /eso/bin/PhoneCustomer/default/patch_gal.sh .... how to solve it?

Run again the "Get new scripts and files from SD-card (slot1)" script

"Sorry, the file you have requested does not exist." @@
I can't access the link

https://drive.google.com/file/d/17H3N2osC4jb4ajFK31mCbKIdVk_J8HSy/view

ok! i've successfully installed it....however another problem...when i try to patch android auto it say: script not found /eso/bin/PhoneCustomer/default/patch_gal.sh .... how to solve it?

Got this at my first try. Just restart the unit and it should be fixed / possible to move the scripts.

Hello everyone!
Im new in this kind of Sw tricks;  In the past days I have tried run the toolbox for my MIB2.5 recently installed in a golf A7 nevertheless i had  the following problem
"Error when reading /opening the file."
Metainfro2.txt
This is the info of my unit
Harman Kardon
Part Number:  5NA 035 047 A   Golf NAR
SW Train Version: MHI2_US_VWG13_P3640
SW MU Version: 0921
Partnumber: 5NA035047A
HW-Version: ----------
SW-Version: H29.49.45_HIGH2GP_NAR
Model: GuideModel_29.49.36
SW Base: H29.49.45-201608161429
I would like to reset the version a load again all the FECs and Swaps
Thank you in advance for supporting
Alejandro

I just noticed that this POI Import works if your device was patched (ifs-root).
I tried it on a Seat unit 1409 before patching and the error appeared.
After the ifs-root was patched the import works.
So this seems do be some internal check which is disabled on a patched unit.

Yes, but it's also working on non-patched units... I think VW applied a fix to patch the payload, which triggers the metainfo error.

Hello,
I’m from France and I have a MIB2 HIGH(I guess).
It’s on my Seat Cupra 2015 and it has the navigation pro with a hard drive.
I don’t have CarPlay and it has Mirror Link inside.
So I went to see a guy who have a shop in Switzerland, and he cannot update my MIB2.
He tried to upgrade my MIB2 with this MHI2_ER_SEG11_P4708, but after the reboot and after one hour wait, it gets stuck on the Seat Logo and nothing works even if you press the buttons.
So I need some help with this, (If you can guys) because, he’s saying that my MIB2 is almost dead and I’m afraid I have to pay for one new.
Thank you for you help guys !
Greetings from France :)

Same problem here: H25.14.89_HIGH2_EU; 1156 SW MU. I will try with manual installation, but I wanna know if I have to use d-link or can use asus as well? Also another thing, on back side of unit, there is not any USB port, that's mean I can use standard USB port in my console?

Same problem here: H25.14.89_HIGH2_EU; 1156 SW MU. I will try with manual installation, but I wanna know if I have to use d-link or can use asus as well?

No, only the D-link will work (and 2 or 3 others, but those are pretty obscure to come by). You really need the specific PID/VID of the D-link otherwise it will not work

Also another thing, on back side of unit, there is not any USB port, that's mean I can use standard USB port in my console?

Yes, the regular USB port you use for media.

Thank you for fast reply. Is there any other options for my SW via SD card? Did you upgrade any unit with this SW?

Same problem here: H25.14.89_HIGH2_EU; 1156 SW MU. I will try with manual installation, but I wanna know if I have to use d-link or can use asus as well?

No, only the D-link will work (and 2 or 3 others, but those are pretty obscure to come by). You really need the specific PID/VID of the D-link otherwise it will not work

Also another thing, on back side of unit, there is not any USB port, that's mean I can use standard USB port in my console?

Yes, the regular USB port you use for media.

Please tell me, is there any chance to install toolbox via wifi. I have wlan on my unit? I try almost 15 SD card in all type of format. Also try 5 different usb to ethernet adapter, but still doesn't make it. I can't buy anywhere d-link adapter here in Slovenia. Wifi is my last chance.

ok! i've successfully installed it....however another problem...when i try to patch android auto it say: script not found /eso/bin/PhoneCustomer/default/patch_gal.sh .... how to solve it?

Got this at my first try. Just restart the unit and it should be fixed / possible to move the scripts.

move scripts from where to where ?

ok! i've successfully installed it....however another problem...when i try to patch android auto it say: script not found /eso/bin/PhoneCustomer/default/patch_gal.sh .... how to solve it?

move scripts from where to where ?

Read the readme please. You have to run a script from the Green Menu after installation, which will copy all scripts from SD to the unit.

okey I found the problem. Folder "Script" on my MIB is missing (or just copy_phone_customer.sh file) - that's why can not run anyone script. Is any way to fix that ? My MIB is patched already so, looking for they way w/o update.
Thanks jilleb.

I'm step forward, but still without succes. I get in and enter "root" for login, but then is just written password: but I can't type any letters. Somebody know what is problem?

:D this is normal behaviour. You´re writing but it isn`t showing. You have to write it blind and press enter.

Problem is solved. As Olli991 said, terminal not support password typing. Now that part is ok and third app I can see and start, but doesn't work. PM start, but doesn't show value it is just 0. Carstream start but didn't show video, there is just note: click last icon in bottom bar & start. I gave all persmissions for all app but still no success.
Jilleb do you have any solution?

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

Hello all
@jilleb
Im new in this kind of Sw tricks; In the past days I have tried run the mib2-toolbox for my MIB2.5 recently installed in a golf A7 nevertheless i had the following problem
"Error when reading /opening the file."
Metainfo2.txt
This is the info of my unit
Harman Kardon
Part Number: 5NA 035 047 A Golf NAR
SW Train Version: MHI2_US_VWG13_P3640
SW MU Version: 0921
Partnumber: 5NA035047A
HW-Version: ----------
SW-Version: H29.49.45_HIGH2GP_NAR
Model: GuideModel_29.49.36
SW Base: H29.49.45-201608161429
Bootloader: 224001
Application: 214
SD Card used; 64GB, 170 MB/s
Format: FAT32
Playing with metainfo2.txt file I removed the last entry "Payload" and i did not have reading issues; i selected " MQB Coding Toolbox V2.7, but once i was in i could not click "Start" it was disabled... gray mode
Could you guide me about what I should have to do, review or update in the scripts.
If its not a problem i would like to follow u facebook, could you share me your user? (Thanks for)
Thank you in advance for supporting
Alejandro

Hello, Alejandro can you shared with me your root password?

Any news about this issue with "metainfo2.txt"?
I have the same problem with Skoda Columbus Mib2.5 high SW 1440...

No updates here. I can't reproduce this on any of my own devices, so it's impossible to find the solution

Hi,
thanks for your quickly answer :-)
I see in you experimental Brunch that there is some signature inside the File… possible this is the problem?
Kind regards
Sascha

Am 09.08.2020 um 11:17 schrieb Chillout<EMAIL_ADDRESS>No updates here. I can't reproduce this on any of my own devices, so it's impossible to find the solution
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-671028259, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALNPHQAHDYOTKD2FKE43LVDR7ZSRLANCNFSM4IYQ5O4A.

No, that is not the problem 😁

Does anyone could share what D-Link DUB E-100 looks like? Picture?

There you go @brianyou0524

@vniehues
Thanks , I google it before , but Chillout said to get it work need a specific adapter
However, like you've seen.  there are few E100 in the search result .
To find DUB-E100 is not a big deal for me , because I live in Taiwan where related devices are cheap and made from TW
Thanks
Brian

Hi, Thanks for all the hard work that has been put into this! Unfortunately i am getting the same Metainfo2.txt error. I have used my macbook pro to move the files to a 2GB micro sd (in a sd adapter) but i am unable to progress any further :( I am going to try a few things including using a windows PC to copy files over instead of Mac but if you have any pointers please let me know @jilleb i have also attached a few pictures of my headunit info incase i am missing some compatibility issue??
Thanks
D

Ok so i have tried a few things.. transferred files using windows instead of mac, reformatted card to ensure FAT32 file structure and also tried files from previous 2.2 version. No progress :( I am out of ideas now, only thing i haven't tried is a different SD card or full size SD instead of micro SD in an adapter (not that this should matter)

No updates here. I can't reproduce this on any of my own devices, so it's impossible to find the solution

So, give me some infos what you need for debugging, please. I have acces on my Unit threw LAN(USB) and UART and can do all what you want for more deep dive analysing.

Could it make sense, that the pople with issues start posting their Green Menu Version?

On my Skoda Columbus MIB2.5 for example import is working!

For me all the Version’s the same like CaneTLOTW, but it is not working...

Am 18.09.2020 um 07:49 schrieb CaneTLOTW<EMAIL_ADDRESS>Could it make sense, that the pople with issues start posting their Green Menu Version?
https://user-images.githubusercontent.com/35076818/93560846-56c4ee00-f983-11ea-840b-a5c692b0b707.png
On my Skoda Columbus MIB2.5 for example import is working!
https://user-images.githubusercontent.com/35076818/93560914-7bb96100-f983-11ea-872e-0f27c34b1ccb.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-694668038, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALNPHQCIK5JWKKLIRYVXQ4TSGLYH7ANCNFSM4IYQ5O4A.

with UART Login I can see this in Logs after pushed the Update in SWDL Menu:
[AslTargetSWDL] Wrong signature for update: metainfo2.txt

First of all, congratulations on your achievement.
I also have MIB2-hight with version 0199, and the problem "Error with reading metainfo2.txt" appears
I bought update 343,814 and 1187.What is your recommendation to install the toolbox after version 343 or does it not matter?
Thanks for your time

As many others I have not been able to do the automatic installation on my unit. I have a MIB 2.5 with fw 1367. I tried the manual method with a D-Link DUB-E100 but I can not seem to get root login. As far as I know the stock password for my fw is EYaH6Nq8. I have a cracked unit - could this have something to say?

Hi,
Could be that your „expert“ changed the root login.
What is your SW train version?
Sent from my iPhone

Am 12.12.2020 um 17:33 schrieb tamperfinga<EMAIL_ADDRESS>
As many others I have not been able to do the automatic installation on my unit. I have a MIB 2.5 with fw 1367. I tried the manual method with a D-Link DUB-E100 but I can not seem to get root login. As far as I know the stock password for my fw is EYaH6Nq8. I have a cracked unit - could this have something to say?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I am not sure what you mean by "train version". From an vcds autoscan of my
car I can see the following: Part No SW: 5NA 035 020 D    HW: 5NA 035 020.
When holding the menu-button on the unit I get mhi2_er_vwg13_p4521.
Den lør. 12. dec. 2020 kl. 18.46 skrev CaneTLOTW<EMAIL_ADDRESS>
Hi,
Could be that your „expert“ changed the root login.
What is your SW train version?
Sent from my iPhone

Am 12.12.2020 um 17:33 schrieb tamperfinga<EMAIL_ADDRESS>
As many others I have not been able to do the automatic installation on
my unit. I have a MIB 2.5 with fw 1367. I tried the manual method with a
D-Link DUB-E100 but I can not seem to get root login. As far as I know the
stock password for my fw is EYaH6Nq8. I have a cracked unit - could this
have something to say?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-743790683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDDKGBGMRGVS7W6SB5FKQLSUOT6PANCNFSM4IYQ5O4A
.

SW Train: mhi2_er_vwg13_p4521
EYaH6Nq8 should be the pw, right.
Did you try RCC Emergency via UART? (pw =  2yavoUEZ)
Most of the time, this is not changed.

SW Train: mhi2_er_vwg13_p4521
EYaH6Nq8 should be the pw, right.
Did you try RCC Emergency via UART? (pw = 2yavoUEZ)
Most of the time, this is not changed.

Pretty sure my unit does not have emergency function, but yes, I tried 2yavoUEZ as password as well - if by UART you mean the D-Link adapter. Could it be possible that I'm doing something wrong with Putty? I am following this guide posted earlier in the thread https://drive.google.com/file/d/17H3N2osC4jb4ajFK31mCbKIdVk_J8HSy/view.

I think you need some more background on the topic ;)
UART needs to be connected to the back of the UNIT direktly (Quadlock)
Try to find my user name in Telegram

I think you need some more background on the topic ;)
UART needs to be connected to the back of the UNIT direktly (Quadlock)
Try to find my user name in Telegram

Thank you I will look. You're definitely right about that!

Hi all,
I see this discussion is going on for quite a while now. I am fairly new to all of this and is was struggling around the last days to get the toolbox installed as well. I received the same error messages with corrupt metainfo.txt while trying to install through service mode. It simply was not possible at all.
I am on a Seat Leon 5F (Nav Plus/MHI2) and first tried with stock version MU1219. I wasn't able to find root passwords anywhere so only chance to continue was to upgrade to newer FW/MU (which I wanted to do anyway). First I updated to MHI2_ER_SEG11_P4708_MU1409 as I read that some were successfully installing on this FW/MU -> reactivated developer mode with VCDS -> didn't work either. So I continued to update to MHI2_ER_SEG11_P4709_MU1447 -> reactivated developer mode with VCSD again -> still didn't work. As per P4709 / MU1447 I was now having the option to use putty to login to shell and install the toolbox manually. Instantly worked for me (followed the readme instruction for manual installation).
Green Menu was now showing mqbcoding section. I then imported files with "get new scripts from SD card" but still wasn't able to run any scripts from the mqb green menu. So back to putty and checking the folder structure based on payload.sh / mqbcoding.esd. It turned out that the stock file "copy_phone_customer.sh" is not exactly doing what was expected by mqbcoding -> scripts were copied to the internal drive in PhoneCustomer rather PhoneCustmer/default folder. So I created the "default" folder myself and moved everything across. Now it just works fine. I tried to run dump_all.sh for a quick test and received to the output on my sdcard.
copy_phone_customer.txt
As this error seems to be a bit more generic than just FW / MU version of the unit I would gladly investigate a bit more and help to solve this. Does anyone know if there is some kind of log (usually in var folder but I am not too familiar with the folder structure of the MIB unit "yet")? Glad to retry installation from service menu again and debug a bit more on my unit.
I also tried to patch the gal.json to use 3rd party apps via AndroidAuto -> performance monitor works, too. Didn't get all channels up (eg Nm / torque is not working). But that could be based on Seat/VW difference in channels. Have to try again the next few days.
A big thank you to the developer/s. Very much appreciated.
BR Seb

Hello, I have a seat leon fr car hardware: H24
software: 0346 Update 0363 gives metainfo error, what should I do?

What is your full SW Train?
The Unit is Harman?

Dear CaneTLOTW,
I'm not sure who you replied to but in case you were interested in my versions here you go:
cat /net/rcc/dev/shmem/version.txt
Variant = 'FM2-H-ND-EU-SE-MQB'
Current train = 'MHI2_ER_SEG11_P4709'
MainUnit version = '1447'
RCC version = 'U8987'
RCC label = 'MIB2CLU8-Trunk_rcc2_B1-18072B'
cat /tmp/fazit-id
JTH-07616.05.1834040309
Green Menu Version: <GEM 4.12st>
Software Version: H29.344.66_HIGH2_EU
Model: GuideModel_29.344.12
Software Base: H29.344.66-201906171929
Part Number: 5F0035020K (Manufacturer part no: HAN 5F0035020) --> from my understanding this is a Harman device revision K
If you need more information please let me know or contact me directly member1 @ freenet . de happy to help in any way.
I haven't pulled out the device from the glove compartment to see the label on it but certainly could do so. I just have to find those release pins again :-) I'm sure they are somewhere.
BR Seb

@CaneTLOTW I could not understand:(

Something looking like this: MHI2_ER_SEG11_P4709 is your sw-train

@CaneTLOTW  MST2_EU_ZR_P0346T

@CaneTLOTW    MST2_EU_SE_ZR_P0346T

1440 Skoda firmware also. But i found a little solution: Activate Green Menu, goto production/rcc_prod/swdl_prod. Tick User Defined SWDL. Return to Service Modus-testmode-SWDL and start Download. then he finds MQB Toolbox and install is possible.
Good Luck,
Ed

@Carmaffia
hello i read our comment but i couldn't understand how to enable the green menu

Do you have VCP or OBD11? That way you can activate the Green Menu in MIB2.
Op ma 21 dec. 2020 om 00:14 schreef cnkkya<EMAIL_ADDRESS>
@Carmaffia https://github.com/Carmaffia
hello i read our comment but i couldn't understand how to enable the green
menu
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-748685049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASG27XUTU23JDEHPCK5Q7LDSV2ANFANCNFSM4IYQ5O4A
.

Hi, I'm seeing the same issue on an Australian Golf Alltrack discovery pro (with only touchscreen, no physical buttons/dials)
It shipped with firmware:
MHI2_ER_WWG13_P4512_2 (1161)
I've upgraded directly from that to:
MHI2_ER_VWG13_K4525 (1367)
Same error on both, trying Release 2.2B as well as current master (1590c80) copied onto SD card. Each time I formatted the SD card clean as Fat32, tried multiple cards.
I've got green screen enabled (needed re-enabling after firmware update) I also tried the green screen setting to turn on User defined SWDL as mentioned in https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-748604798
I then tried a POICreator tool, made up a SD card using that and it was recognised fine, so started comparing contents of metainfo2.txt
I tried modifying the header/compatibility/names in metainfo2.txt (fixing the hash's each time), no change.
Unfortunately, the only change to the file I've found so far that fixes this error is removing the last block
[PersonalPOI\PayLoad\0\default\File]
CheckSumSize = "524288"
CheckSum = "3A77210AEA6929DD460BE323DA75274F629C611F"
FileSize = "118797"
Version = "3500"
Source = "payload.sh"
Destination = "/net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"
DisplayName = "MQB Coding MIB2 toolbox"
DeleteDestinationDirBeforeCopy = "false"
UpdateOnlyExisting = "false"

Rendering the installer pointless. Once this is removed though, the error no longer occurs.
I've played around with copying off logs via green screen, trying to enable traces (can't copy them to SD though, missing library) but haven't found anything in the logs pointing to specifics of the swdl failure. I did find that a FTDI USB serial cable is recognised and loaded by the system (can see that in the logs) but it doesn't seem to enable a terminal on it automatically unfortunately.
On a different forum I saw you mentioned a POI based update to fix the firewall to allow telnet over wifi/hotspot, are there more details about this I could try?
In the mean time, I'll keep trying different changes in that metainfo toolbox installation block to narrow down exactly what trips this error.
Cheers!

Hi, I'm seeing the same issue on an Australian Golf Alltrack discovery pro (with only touchscreen, no physical buttons/dials)
It shipped with firmware:
MHI2_ER_WWG13_P4512_2 (1161)
I've upgraded directly from that to:
MHI2_ER_VWG13_K4525 (1367)
Same error on both, trying Release 2.2B as well as current master (1590c80) copied onto SD card. Each time I formatted the SD card clean as Fat32, tried multiple cards.
I've got green screen enabled (needed re-enabling after firmware update) I also tried the green screen setting to turn on User defined SWDL as mentioned in https://github.com/jilleb/mib2-toolbox/issues/1#issuecomment-748604798
I then tried a POICreator tool, made up a SD card using that and it was recognised fine, so started comparing contents of metainfo2.txt
I tried modifying the header/compatibility/names in metainfo2.txt (fixing the hash's each time), no change.
Unfortunately, the only change to the file I've found so far that fixes this error is removing the last block
[PersonalPOI\PayLoad\0\default\File]
CheckSumSize = "524288"
CheckSum = "3A77210AEA6929DD460BE323DA75274F629C611F"
FileSize = "118797"
Version = "3500"
Source = "payload.sh"
Destination = "/net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"
DisplayName = "MQB Coding MIB2 toolbox"
DeleteDestinationDirBeforeCopy = "false"
UpdateOnlyExisting = "false"

Rendering the installer pointless. Once this is removed though, the error no longer occurs.
I've played around with copying off logs via green screen, trying to enable traces (can't copy them to SD though, missing library) but haven't found anything in the logs pointing to specifics of the swdl failure. I did find that a FTDI USB serial cable is recognised and loaded by the system (can see that in the logs) but it doesn't seem to enable a terminal on it automatically unfortunately.
On a different forum I saw you mentioned a POI based update to fix the firewall to allow telnet over wifi/hotspot, are there more details about this I could try?
In the mean time, I'll keep trying different changes in that metainfo toolbox installation block to narrow down exactly what trips this error.
Cheers!

In my continued investigations, I modified the [PersonalPOI\PayLoad\0\default\File] block to find what was causing the error - it's the destination path.
If I change
Destination = "/net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"

to
Destination = "/net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd"

I no longer get the metainfo.txt error when starting to install on unit.
I eventually found that this also works - in that it does not trigger the metainfo.txt error:

In my continued investigations, I modified the [PersonalPOI\PayLoad\0\default\File] block to find what was causing the error - it's the destination path.
If I change
Destination = "/net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"

to
Destination = "/net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd"

I no longer get the metainfo.txt error when starting to install on unit.
I eventually found that this also works - in that it does not trigger the metainfo.txt error:

Wow that's progress!!
The ../ path trick was what I used on mib1 but I never got it working on MIB2.
Can you try adding more ../../../ and make the path start at
/net/mmx/mnt/app?

Wow that's progress!!
The ../ path trick was what I used on mib1 but I never got it working on MIB2.
Can you try adding more ../../../ and make the path start at
/net/mmx/mnt/app?

Not sure if this is exactly what you meant, but I just tried this as the final block (everything else as per current master build)

[PersonalPOI\PayLoad\0\default\File]
CheckSumSize = "524288"
CheckSum = "3a77210aea6929dd460be323da75274f629c611f"
FileSize = "118797"
Version = "3500"
Source = "payload.sh"
Destination = "/net/mmx/mnt/navdb/PersonalPOI/../../../../../net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"
DisplayName = "MQB Coding MIB2 toolbox"
DeleteDestinationDirBeforeCopy = "false"
UpdateOnlyExisting = "false"

Unfortunately gave the same error screen as photo'd in my previous attempt

Not sure if this is exactly what you meant, but I just tried this as the final block (everything else as per current master build)

[PersonalPOI\PayLoad\0\default\File]
CheckSumSize = "524288"
CheckSum = "3a77210aea6929dd460be323da75274f629c611f"
FileSize = "118797"
Version = "3500"
Source = "payload.sh"
Destination = "/net/mmx/mnt/navdb/PersonalPOI/../../../../../net/mmx/mnt/app/eso/hmi/engdefs/mqbcoding.esd"
DisplayName = "MQB Coding MIB2 toolbox"
DeleteDestinationDirBeforeCopy = "false"
UpdateOnlyExisting = "false"

Unfortunately gave the same error screen as photo'd in my previous attempt

So still not much progress unfortunately. I tried a bait-and-switch with two SD cards - one configured with Destination = "/net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd" and a second one with the metadata unmodified.
I used the modified one to start the update, then while the unit was rebooting into update mode switched the SD cards.
However it looks like it does the same metedata check on the start of the update mode - it gives a popup with the same "Unable to read the release information file".
Just to be sure I restarted and let the update run right through with Destination = "/net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd" and it worked, as in the installation completed successfully. Obviously I didn't get a running toolbox, but it proves the rest of the PersonalPOI install stuff still works.
I then changed the modded SD card back to Destination = "/net/mmx/mnt/navdb/PersonalPOI/../../app/eso/hmi/engdefs/mqbcoding.esd" and restarted the update, leaving this card in during the start of the update mode until it threw the error 131 screen as before. I then switched out the SD cards with the un-modded one and hit retry on the error screen a few times, but to no avail - I never got past the error screen.
Until I think of something else to try, I'll have a go with ethernet based installs: https://github.com/jilleb/mib2-toolbox/issues/119

So still not much progress unfortunately. I tried a bait-and-switch with two SD cards - one configured with Destination = "/net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd" and a second one with the metadata unmodified.
I used the modified one to start the update, then while the unit was rebooting into update mode switched the SD cards.
However it looks like it does the same metedata check on the start of the update mode - it gives a popup with the same "Unable to read the release information file".
Just to be sure I restarted and let the update run right through with Destination = "/net/mmx/mnt/navdb/PersonalPOI/mqbcoding.esd" and it worked, as in the installation completed successfully. Obviously I didn't get a running toolbox, but it proves the rest of the PersonalPOI install stuff still works.
I then changed the modded SD card back to Destination = "/net/mmx/mnt/navdb/PersonalPOI/../../app/eso/hmi/engdefs/mqbcoding.esd" and restarted the update, leaving this card in during the start of the update mode until it threw the error 131 screen as before. I then switched out the SD cards with the un-modded one and hit retry on the error screen a few times, but to no avail - I never got past the error screen.


Added close_connection

This lets you close the connection to redis

How do I close the connection? I have tried to calling close_connection on EventMachine::Hiredis::Client with no success.
Here is my code:
require 'rubygems'
require 'eventmachine'
require 'em-websocket'
require 'em-hiredis'

EM.epoll
EM::Hiredis.logger
puts "Total descriptors: #{EM.set_descriptor_table_size(10230)}"

EM.run do
  socket = EM::WebSocket.start(:host => "<IP_ADDRESS>", :port => "8080") do |ws|
    ws.onopen do
      @subscriber = EM::Hiredis.connect('redis://<IP_ADDRESS>:6379/0')
      @publisher = EM::Hiredis.connect('redis://<IP_ADDRESS>:6379/0')
    end

    ws.onclose do
      puts "Websocket: closed"

      @publisher.close_connection
      @subscriber.close_connection
    end
  end
end

After onclose I get "Websocket: closed" printed on screen but when looking at redis-server log the two connections remains open.
[7375] 17 Oct 15:48:11 - 2 clients connected (0 slaves), 940192 bytes in use

Ok, my fault. I forgot to add require 'bundler/setup so the wrong version was being load.
Great gem.


vayu: update ACPI

Description
New ACPI update by @degdag
Checklist

[x] Have you tested the change you are submitting?
[x] Is the commits history nice and clean?

thank you Morc, very cool


Updated tags of automounted drives tests

Two updates with this PR:

reclassified automounted drives tests to be 'Feature' instead of 'CI' because this is more accurate;
fixed failures in tests setup caused by "subst.exe" native utility having problems running as child process of powershell process tree run under "runas.exe /trustlevel:0x20000" (in Start-UnelevatedProcess in build.psm1).

@anmenaga,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Use spread to add action codes

It's easier to work with action codes as 12 columns rather than creating rows:
spread(AktieCode, AktieCode)

That way, it's easier to see combinations of codes + the number of records = the number of observations.

Done.


Tooltip on svg misplacement after scrolling the page

Issue happens because:
The Element.getBoundingClientRect() method returns the size of an element and its position relative to the viewport.
Need to extend tooltip position with:
 Tooltip.prototype.getPosition = function ($element) {
    $element   = $element || this.$element

    var el     = $element[0]
    var isBody = el.tagName == 'BODY'

    var elRect    = el.getBoundingClientRect();
    elRect = $.extend({}, elRect, {
        top: elRect.top + window.pageYOffset,
        left: elRect.left + window.pageXOffset
   });
... e.t.c

This is the same as issue #20381 (Positioning error on SVG tooltips/popovers when scrolled, then clicked) that was caused by PR #20313 for issue #20280 (Unit test for tooltip on SVG element fails in Chrome+Safari under jQuery 3).


Reduce unsafe usage

by storing Box<str> rather than &'static str for the owned values in the SymbolTable.
This is mostly a proof-of-concept (as it does not adjust the bstr interner or any documentation that is now innacurate), and not strictly necessary for soundness or any feature addition. Rather, it's primarily because you don't need to do the Box::leak/Box::from_raw dance, and this reduces room for error as Slice no longer requires a manual Drop implementation.
I'm collecting some comparisons between some of the top string interner crates in the vein of Amos's comparison of small strings, and was surprised that an interner that says it works via leaking strings actually doesn't leak anything and properly cleans up after itself.
(Also, you're the only interner of the ones I'm checking that support interning &'static str special without copying the string, so that's cool!)

This is a neat trick. Let me work through how I think this works.

Slice::Leaked always stored an owned Box<str>
Slice::Leaked serialized that Box<str> to a &'static str with Box::leak to extend the lifetime for storing in the Vec.
dropping the owner slice requires a custom drop impl with unsafe that is a bit scary.

Instead:

store an owned Box<str> directly. This does not increase the size of Slice since &str are already fat pointers.
Extend the lifetime “locally” in Slice::as_static_slice.
Drop normally.

To summarize, size of interner stays the same and much less unsafe by only changing an internal representation. Sounds great.
Good catch that the docs don’t make it clear that leaking was an implementation detail and intaglio cleans up after itself. Thanks.
I’d like to take this change. How would you like to proceed @CAD97?
One change is like to make is to move the constructors for Slice to two associated functions on Slice and remove the alloc method to hide any other changes we might make to the internals inside of Slice

Yes, you've got it right.
I've pushed a second commit to do the same improvment for the bytes interner. The implementation work is now ready to be merged, though I'd definitely suggest going through another pass to clean up documentation (internal and external) to make sure that it's not talking about leaking strings anymore. You've much more familiarity with the library to do the work than I.
My quick tour of the bytes module to apply this diff suggests you might be better off just not using BStr. I've had to use Box<[u8]> for the owned variant rather than Box<BStr>, and this caused no (direct) issues, as the Slice is used through as_slice() which returns &[u8] anyway. If you want to keep using bstr, then you can get Box<BStr> by a transmute, implement Debug manually to use &BStr, or wait for upstream to provide the necessary API to create Box<BStr>.

One quick note before I review:
The only reason BStr is included as a dependency in this crate is for its fmt::Debug implementation.
In Artichoke, while symbols are byte strings, they are conventionally UTF-8 and almost always real UTF-8 strings. Without bstr doing dbg!(symbol_table) is mostly unreadable.

I'm collecting some comparisons between some of the top string interner crates in the vein of Amos's comparison of small strings,

If you're interested, the post is out now: https://dev.to/cad97/string-interners-in-rust-797

Thanks for checking out intaglio and contributing back some wonderful improvements.


how to use the trained model ckpt for test?

I've followed your instruction to train the mld model. And I got the checkpoint after 2000epochs. Now I want to use this ckpt for test just like the 1222_mld_humanml3d_FID041.ckpt in your template. But the state_dict is wrong.
RuntimeError: Error(s) in loading state_dict for MLD:
Missing key(s) in state_dict: "denoiser.decoder.layers.0.self_attn.in_proj_weight", "denoiser.decoder.layers.0.self_attn.in_proj_bias", ………………
Is there any additional step to get the right ckpt? or any additional setup in the config file?
您好，我想用我训练好的模型测试性能，但是load 训练的checkpoint遇到了问题，请问我需要添加其他额外的步骤吗？

请问是不是因为训练mld的时候是把vae也存到了ckpt里


Prefer Mixin Module to Base Class

Use a mixin module (HighVoltage::ControllerMixin) instead of a base class (HighVoltage::PagesController).
The base class can of course simply include the mixin module as its complete implementation for backwards compatibility:
class HighVoltage::PagesController
  include HighVoltage::ControllerMixin
  # that's all, folks!
end

There are projects without an ApplicationController class, or with a common controller base class named differently, or with multiple area-specific controller base classes.

I was surprised too
 namespace :foo do
    get "/pages/*id" => 'pages#show', as: :page, format: false
  end

get "/pages/*id" => 'pages#show', as: :page, format: false

module Foo
  class PagesController < Foo::ApplicationController
    include HighVoltage::StaticPage

  end
end

Given default content_path i would expect  GET /foo/pages/about to render app/views/foo/pages/about.html.erb just based on conventions.   I guess the easiest solution is to override  def content_path https://github.com/thoughtbot/high_voltage/blob/main/lib/high_voltage/page_finder.rb#L21
Hard coding the config content_path wouldn't work either because i still want GET /pages/about to work as normal

This worked
module Foo
  class PagesController < Foo::ApplicationController
    include HighVoltage::StaticPage

    layout "foo/layouts/application"

    private
    def page_finder_factory
      DefaultPageFinder
    end

    class DefaultPageFinder < HighVoltage::PageFinder
      def content_path
        'foo/pages'
      end
    end
  end
end


Allow Purchase of Capacity

I would like to allow artists to purchase more capacity when they run out.  When doing so, the award system goes away for their account and it is based strictly on the capacity that they purchase.
What is a good price point for this?  I would like to also give the purchased capacity a time limit so that it's a recurring revenue stream.
Is $0.50 per 1 Flare of capacity for a year a good point? $0.25 per Flare? 🤔🤷♂
Whatever the price, the artist purchases it and their capacity gets increased by this amount.  We should also allow this purchased capacity to transfer between different markets.
Since they are paying for it, do we still charge a capacity tax when a recall is performed?

This is possible now: https://starbeam-one.gitbook.io/home/artists/concepts/capacity#buying-capacity


update readme

This PR adds a Sample StackBlitz to the README.md file so that users can directly start to play around with the library.

It has already been done. Thank you.


Conversion of processed files to MIDI format

I love the processor and the included song files, but I prefer direct MIDI input for a player. Is there a way to reconvert the files to MIDI after processing for use in direct MIDI input mods?

Just pushed support for playing directly from .mid files.


Upgrade Bilibili.app to v2.00

Thank you for the contribution. It was merged directly as f0fc18dffaa703f56d71758c06857abbee84791a to keep commit history cleaner. Your contribution is still credited to you.


Functions watcher Appears Not to Work

Bug report
Describe the bug
After running supabase functions serve on a newly-created hello function, I expect to see the function hot-reload after changing the index.ts file of the function, but nothing seems to happen.
I see this message which indicates that serve worked, but again, hot-reloading the function does not seem to work:
Starting supabase/functions/hello
Serving supabase/functions/hello
Watcher Process started.
Hello from Functions!

To Reproduce

Run supabase functions new hello
Leave everything as-is in the index.ts file
Run supabase start
Run supabase functions serve hello
See 'Hello Functions!' printed - expected result.
Make any change in index.ts - for this example I made a change to the output message
'Hello functions' is still printed, instead of the new output message. Also, there appears to be no status updates from the watcher.

Expected behavior
Expected the function to hot-reload.
System information

OS: [e.g. macOS, Windows] Windows 11
Browser (if applies) [e.g. chrome, safari] Independent
Versions:
CLI version 0.24.2,
Deno: deno 1.20.4 (release, x86_64-pc-windows-msvc) v8 <IP_ADDRESS> typescript 4.6.2
supabase-js: 1.33.3
Version of Node.js: v16.14.0

Additional context
Tried running serve from an Administrative Powershell and Admin. CMD - same result.

This seems to be a limitation of Docker on Windows: https://forums.docker.com/t/file-system-watch-does-not-work-with-mounted-volumes/12038
The workaround mentioned in that thread is to do the file watching ourselves natively, but that involves a lot of work - happy to hear any alternatives.

Facing the same issue here too..

In the thread linked by you @soedirgo there has been an update (after you posted here). Could this work for us? I didn't get it working myself sadly..
http://blog.subjectify.us/miscellaneous/2017/04/24/docker-for-windows-watch-bindings.html

Good find! The mount path thing is a bug - will work on a fix.

hey , a guest from the dystopian '23 here 😀.
the issue still persists on docker windows.
any chance for a patch in the cli?

Hi! Just here to ask for any updates in the issue. Still persist up to date.

I hate to do this, but I third the request to prioritize fixing this issue.

issue on Docker macOs too

Still facing this issue on Mac. Even stopping/restarting supabase does not pickup new function changes. @Bijig0 did you ever solve for mac?

Still facing this issue on Mac. Even stopping/restarting supabase does not pickup new function changes. @Bijig0 did you ever solve for mac?

Unfortunately not, I personally switched to vercel cloud functions

I can confirm that I'm experiencing the same issues. A full Docker restart is required to run updates locally.
Docker Desktop 4.30.0
supabase/postgres <IP_ADDRESS>
supabase/edge-runtime 1.45.2

Also not working for me:
Supabase cli: 1.172.2
Deno: 1.40.3
edge-runtime:v1.53.3

I just upgraded to the latest CLI and still not working.
CLI: 1.176.10
Edge runtime: 1.54.2
FYI I'm using a MacBook Pro with an Intel chip.

@sweatybridge Any chance if this issue will be picked up?

I had the same issue, using a mono-repo structure, and I changed the directory to Supbase root; solving the issue for me.

@sweatybridge Any chance this issue will be picked up?

I had the same issue, using a mono-repo structure, and I changed the directory to Supbase root; solving the issue for me.

@sweatybridge Any chance this issue will be picked up?

That's great, I am also using a monorepo. Could you elaborate on the steps you took?

I had the same issue, using a mono-repo structure, and I changed the directory to Supbase root; solving the issue for me.

@sweatybridge Any chance this issue will be picked up?

That's great, I am also using a monorepo. Could you elaborate on the steps you took?

├── LICENSE
├── README.md
├── frontend
├── package-lock.json
└── supabase

simply cd to supabase and it should auto-refresh as expected.


add neo4j.v1.types to setup.py

I think there are ways of discovering submodules programatically when setup.py is run but this fixes installing the driver with pip for now. Without it the types module does not get installed and it fails at runtime

This has been fixed in a separate commit.


Lack of docker image

We're need to create docker image to run fakehub independently from platform.  I think we can create Dockerfile in project. During the @rultor release push the image to dockerhub

@l3r8yJ Thanks for reporting. Let's do it.

@l3r8yJ Could you get this one?

@l3r8yJ 🎉 Fantastic bug report! You've earned +8 points, boosting your balance to +4. Your keen eye helps elevate our project's quality. Keep spotting and reporting any issues you find - we welcome them!


Support Phoenix 1.7's template telemetry

Instead of using Appsignal.View, Appsignal.EventHandler subscribes to Phoenix 1.7's new template telemetry to gain template rendering insights.

I’ll add docs (https://github.com/appsignal/appsignal-docs/issues/896) and a blogpost (https://github.com/appsignal/appsignal-nextjs-blog/issues/716), but this one’s ready for review.

Will merge and release this next week.

AppSignal for Phoenix 2.2.0 was released, which includes this patch. Note that because template telemetry (https://github.com/phoenixframework/phoenix/commit/f095d1f82cdf18ffc69226fd59ce36a7fc2ffb44) hasn’t been released yet, you’ll need to depend on Phoenix from git to make this work as of right now.