I did that and then I failed. How do I connect to the Audi. How do I start the program on the Mac. What commands do I have to execute. Somehow I can't find any instructions :-(
Everybody said it will not work. Then someone came and just did it
Hi LOL.
Don't worry, I've been on these forums for about 2 weeks now and I've searched another forum and combined the two records together. Few things.
I haven't used a Mac in a while now, but in short, yes, you can use Terminal and do pretty much anything. The downside is, whether or not you patch your device, the Mac may or may not put extra files and settings into the files.
So I would be careful. Best of all, if it is an Intel-based MAC you can just run a VM box with Windows and proceed from there. I did everything through Linux VM.
To start you now need VCDS or OBD11
1. Activate the green menu. The red menu is available by default, but there's not much you can do other than view the software settings and watch for the MIB toolkit update after you've met the requirements.
2. Once activated, purchase an Ethernet to USB adapter. I bought two just in case; like before i read this thread:
Sorry for the English post, but I wanted to post this here for everyone's benefit. Feel free to edit the post and translate it to Deutsch if you want. Per Du musst angemeldet sein, um das Element zu sehen. compatible USB adapters are: D-Link DUB-E100 (0x2001, 0x3c05) D-Link DUB-E100 (0x2001...
www.digital-eliteboard.com
I've theorized that you could possibly buy the same "chipset" and, in short, plug it in and use it because the system will see the same chipset. Then I saw the thread above was able to change the chipset name to the actual dlink and it worked with no problem.
The list gives you an idea of which USB to Ethernet adapters actually work already. But I think you can find everyone who has the chipset from: ASIX AX88772, and ethtool allows you to make the changes by following this exact thread. The first one I bought was identical to this thread's OP in terms of the EEPROM dump, so I made the changes. The second didn't, so I still made the same changes in the same areas and saved it. When I ran ethtool again it showed up as Dlink E100.
And yes, both worked in the car.
As for the car. Here are some tips:
1. With the green menu enabled, go to the IP range and make sure you are on FIXED IP. Save the MMI and restart it.
2. Access your adapter and change the IPV4 settings to match those of the MMI. The last three digits have been changed to 123 instead of the MMI. At 255.255.0.0, leave DG and DNS alone and save them. I'm running ipconfig or ifconfig on Linux should be the same for you in the terminal. To see that the new settings are actually in.
3. use CM; Ping the MMI IP address. If you don't get any responses, you'll need to perform step 1 again. Go back to the selected dynamic restart, go back to the selected hard and reboot. You can use:
cmd> ping xxx.xxx.xxx.xxx -t in Windows to send the ping command until you cancel it.
4. Open Putty, enter the MMI-IP, click on Telnet and change the port to 123.
5. The login is displayed.
At this point, download the PDF which shows the hash / pass of all the different versions. I haven't gone so far as to find my own softwawr train:
MHI2Q_Aug22_Pxxxxxx etc. I just found the MU version that is mine 1178 and found this on the list and used it:
root as the user
pass as whatever it was that matched my version and it showed connection with the MIB ascii art.
From there, go to backing up etc or whatever you're trying to do. Good luck!