For MIB2 HIGH see the jilleb/mib2-toolbox project
WE ARE NOT RESPONSIBLE FOR ANY DAMAGE OF YOUR UNIT. YOU ARE DOING EVERYTHING AT YOUR OWN RISK! READ THIS README, USE YOUR BRAIN AND BE CAREFUL!
- Train MST2_XX_XX_XX_X0XXXT, where X=any character (to see the train press and long hold MENU button, then press "Software Update")
- Green Engineering Menu (developer mode) enabled in adaptations of block 5F. Use any OBD2 adapter and software that can enable it.
- Empty FAT32 formatted SD card or soldering skills + USB flashdrive, with enough space to save your backups. Everything bigger than 1GB is recommended
- Read FAQ at the bottom of this file!
NOTE: This SD installation method is NOT possible on Seat cars with VC type instrument cluster and HW H40+, H50+ units (firmwares 04xx, 05xx) also known as variants 47213, 47214, 47215, 47216. Metainfo2.txt of the Toolbox does not contain these variant numbers. Metainfo2.txt cannot be edited because has digital signature at the end of the file. The ONLY KNOWN way to install Toolbox onto this kind of units is soldering USB SD card reader to eMMC.
- Unzip
MIBSTD2-Toolbox-vX.X.X.zipto the root of SD card. - IMPORTANT! If your firmware is version 01xx or 02xx having GEM (Green Engineering Menu) version 3.x, you must use special edition of Toolbox to update it. To do this, replace
cpufolder in the root of the SD card withcpufolder from\toolbox\gemfolder. If GEM is version 4.x+, skip this step. - Turn on ignition and insert SD card into SD1 slot of the unit
- Press and hold MENU button to open
Service Mode -> Software Updateand installMIBStd2_Online_Approval. - Open Green Engineering Menu and have fun 🙂
IMPORTANT! By default console/telnet access on all units is disabled and you first need to install Toolbox to enable it!
- Unzip
MIBSTD2-Toolbox-vX.X.X.zipto the root of SD card or USB drive - Delete
metainfo2.txt, this helps to avoid endless reading spinner when connecting USB drive to the unit. - Login via console/telnet as root/root
- Insert SD card or connect USB drive to the unit
- Enter
mountto see where inserted card/connected drive is mounted. Usually /media/mp000 is slot SD1, /media/mp001 slot SD2, /media/mp002 port USB1 and so on. - Run
ksh /media/mp000/install.shto install the toolbox. Old GEM will be automatically updated if found. - Open Green Engineering Menu and have fun 🙂
- Unzip
MIBSTD2-Toolbox-vX.X.X.zipto the root of any USB flash drive. Eject and physically disconnect all USB drives. - Start Neutrino 6.5 Virtual Machine, insert USB SD card reader into any USB port of the PC/laptop and allow to connect to VM
- Insert the USB flash drive with the Toolbox to any USB port of PC/laptop and allow to connect to VM
- Inside VM, open Utilities->Terminal and enter
mountto see where USB drive with Toolbox is mounted. Normally it will be /fs/usb1. - Enter
ksh /fs/usb1/install.sh- If you encounter VM freezes or I/O errors while copying: try to create an .iso (via
AnyToIso Liteas example) from the contents of the toolbox and mount the iso via CD drive. You can then runksh /fs/cd0/install.sh! - OR - use the eMMC backup method.
- If you encounter VM freezes or I/O errors while copying: try to create an .iso (via
- Turn off VM assemble back the unit, Open Green Engineering Menu and have fun 🙂
NOTE: If you do not want to use USB drive but have sshd running inside of the VM and have WinSCP access, just copy
MIBSTD2-Toolbox-vX.X.X.zipcontent to into/tmpfolder inside VM. And runksh /tmp/install.sh
- Unzip
MIBSTD2-Toolbox-vX.X.X.zipto the root of any USB flash drive. Eject and physically disconnect all USB drives. - Make eMMC dump from the unit into raw format for example with USB Image Tool
- Convert backup image to VMDK format
qemu-img convert -f raw backup.img -O vmdk backup.vmdk, add it to Neutrino 6.5 Virtual Machine and start it - Insert the Toolbox USB flash drive to any USB port of PC/laptop and allow to connect to VM
- Inside VM, open Utilities->Terminal and enter
mountto see where USB drive with Toolbox is mounted. Normally it will be /fs/usb0 or /fs/hd10-dos-1. - Run
ksh /fs/usb0/install.shorksh /fs/hd10-dos-1/install.sh- If you encounter VM freezes or I/O errors while copying: try to create an .iso (via
AnyToIso Liteas example) from the contents of the toolbox and mount the iso via CD drive. You can then runksh /fs/cd0/install.sh!
- If you encounter VM freezes or I/O errors while copying: try to create an .iso (via
- Turn off VM and convert VMDK back to raw
qemu-img convert -f vmdk backup.vmdk -O raw new_backup.img - Flash new_backup.img back into eMMC chip, assemble back the unit, Open Green Engineering Menu and have fun 🙂
NOTE: If you do not want to use USB drive but have sshd running inside of the VM and have WinSCP access, just copy
MIBSTD2-Toolbox-vX.X.X.zipcontent to into/tmpfolder inside VM. And runksh /tmp/install.sh
- Use
dumpmenu to copy files from unit's filesystem into correspondingdumpsubfolder on SD card or USB drive - Modify those files as you wish and copy into corresponding
customsubfolder on SD card or USB drive - Use
customizationmenu to copy modified files back to unit's filesystem
NOTE: Every time you copy files to the unit, scripts will make a backup of original files to backup folder on SD card/USB drive. Any time later you can use restore functions to revert changes.
MIB STD2 Toolbox Main
+---About
| +---Disclaimer # Disclaimer and mentioning of involved people
| +---History # Version history of the toolbox
|
+---Customization # Customization features
| +---Adaptation # View and change adaptation of the unit
| +---Car_BAP_device_list
| +---Car_CAN_device_list
| +---Car_device_BUS
| +---Car_menu_operations
| +---Advanced # Patching stuff like SWDL, SWAP, HMI CP and more
| +---GreenMenu # Import custom GreenMenus and scripts
| +---Mirror-link # Unlock apps while driving
| +---Navi # Unlock SD card usage from every brand and more
| +---Skins # Modify skins
| +---Sounds # Modify ringtones and system sounds
|
+---Dump # Dump various data to SD card
|
+---MIB_info # Hardware infos and such
|
+---Network # Telnet activation and more
|
+---Tools # Tools and privacy related functions
| +---Update # Enable manual SWDL
|
+---Update_and_Uninstall # Allows to update & uninstall the Toolbox
| +---Update Toolbox # Update Toolbox from SD card or USB drive"
+ +---Uninstall Toolbox # Completely uninstalls Toolbox
Extracts files from *.mcf skin file containers
Syntax: extract-mcf.py <INPUTFILE> <EXTRACTION-FOLDER>
Example: extract-mcf.py images.mcf .\extracted\
Compresses files from extracted folder back into *.mcf container
Syntax: compress-mcf.py <ORIGINAL-BASEFILE> <NEWFILE> <FOLDER-WITH-EXTRACTED-FILES>
Example: compress-mcf.py images.mcf images2.mcf .\extracted\
Extracts files from *.boot startup screen containers
Syntax: extract-startup_x.boot.py <INPUTFILE> <EXTRACTION-FOLDER>
Example: extract-startup_x.boot.py startup_x.boot .\extracted\
Compresses files from extracted folder back into *.boot container
Syntax: compress-startup_x.boot.py <ORIGINAL-BASEFILE> <NEWFILE> <FOLDER-WITH-EXTRACTED-FILES>
Example: compress-startup_x.boot.py startup_x.boot startup2_x.boot .\extracted\
Converts password to shadow file
Q: I already installed Toolbox and want to install new version do I need to uninstall the old one? What is a proper way to update?
A: No, you do not need to uninstall. Simply do update_and_uninstall->Update Toolbox from SD card or USB drive
Q: I got unit with part number X. How to know if that is Technisat/Preh/Delphi/Harman?
A: Google that part number in picture mode and take a look at the label or look for the letter in software version string.
For example MST2_EU_SK_ZR_P0478T. Letter T at the end means it's Technisat/Preh. If there is no letter it's Harman, correspondingly D=Delphi.
Q: Is Toolbox compatible with non Navi (single SD slot) units?
A: Yes, but to install you need to use eMMC soldering method or console/telnet i
671E
nstallation method.
Q: I installed Toolbox from SD but when I try to use it does nothing and prints errors!
A: Your fw is 01xx/02xx with GEM 3.5. Read installation steps carefully!
Q: Why Toolbox does not work with GEM 3.5 or lower?
A: GEM 3.5 and lower cannot run scripts
Q: Where to find GEM (Green Egineering Menu) version?
A: In the top left corner of the Green Engineering Menu screen.
Q: I already have the Toolbox installed and want to update my firmware from 02xx/03xx to 04xx/05xx/06xx etc version. Will Toolbox remain installed after the update?
A: Yes, but you need to update fw manually via Testmode->SWDL->Software Download Manual Download->Start Download.
Tap on "Select all", open cpu or cpuplus folder there and untick esd_sec module and start the update.
If you forget to untick esd_sec, the update will clean /tsd/etc/persistence/esd folder and delete the toolbox.
Q: How to make screenshots?
A: Press and hold MEDIA key until you hear confirmation sound
Q: Where to find screenshots?
A: In the root folder of SD card. You can also use Tools->Move screenshots from root of all drives to the Toolbox drive to collect them in screenshots folder on the Toolbox drive.
Q: After Toolbox installation I got OBD error 1556. How to fix it?
A: Usually just running Tools->Clean SWDL history and keep only non-duplicated FW updates helps. Then reboot the unit and clear OBD2 error.
If the error still there, long press MENU and enter Testmode->Green Engineering Menu->debugging->additional debug destination.
Select where to save the log onto SD or USB. Open the log from SD/USB and look for strings like SW incompatible. They will contain the reason of the error.
Q: Can I make eMMC backup of my unit?
A: Sure, just use Dump->eMMC content (exFAT/NTFS SD card/USB drive + ~7.3 GB free space required) menu.
As most of the units have 7.3 GB eMMC chips, FAT32 formatted media cannot be used because of 4 GB max filesize limitation.
Also it is strongly recommended to use exFAT/NTFS formatted SD card because USB port on MIB STD2 is capped to 5 MB/s.
Class 10 SD card allows to achieve the dump speed upto 10 GB/s so the process finishes in just ~15 minutes :)
Q: Which firmware trains are currently supported for direct SWDL/SWAP/CP patching?
A: Look lists for SWDL here
SWAP here
, and CP here
IMPORTANT! If you get the error "Unknown file size detected", please use the "Dump necessary files to SD folder /dump/.../support" option in the "Tools" section and open up an issue on GitHub and attach the archive with those files!