@samg83 -- I have two observations (and a couple comments) -- first, thanks for posting the text log to a shared Google Drive link.

Now, your MMI3GP system is missing the acios_db.ini file associated with the EUR 6.33.1 nav database. Look at my SD script for creating the acios_db.ini file in-place using the installed navdb PKG file information: GitHub - DrGER2/Make-MMI3G-acios_db.ini: H-B MMI3G SD script to create acios_db.ini from the installed PKG file info

Next, when you get this navdb to initialize successfully, you should be able to update to 8R0060884KL (EUR 6.36.0 2023) directly.

Report back with your results -- you should also consider documenting your JP to EU conversion here. --g

 

@DrGER Thanks for the quick response. I found your create acios_db.ini repo on your GitHub page not long after I created this post.. needless to say It worked

The steps I've been using to convert these units is as follows:

1. 1. Activate green menu (VCDS, VCP or script on SD card)
2. Green menu: Set internal region code to RoW and Nav region to EU, SWDL -> Ignore Region/Variant and User Defined Mode.
3. Run the firmware update from SD card using latest EU Firmware
4. Use a screwdriver to pull out the slot on the side of the unit to attach a card edge reader to USB serial connector made following the How to recover a bricked MMI guide.
5. Boot MMI in IPL and run the flash commands:
   flashit -a 0x00040000 -d -f /mnt/sdcard10t12/MU9498/fpga/51/default/SystemFPGA.hbbin
   flashit -a 0x00100000 -d -f /mnt/sdcard10t12/MU9498/fpga-emg/51/default/SystemFPGA.hbbin
   flashit -a 0x001C0000 -d -f /mnt/sdcard10t12/MU9498/ifs-emg/51/default/ifs-emg.ifs
   flashit -a 0x00680000 -d -f /mnt/sdcard10t12/MU9498/ifs-root/51/default/ifs-root.ifs
   flashit -a 0x03100000 -d -f /mnt/sdcard10t12/MU9498/efs-extended/51/default/efs-extended.efs
   flashit -a 0x03D00000 -d -f /mnt/sdcard10t12/MU9498/efs-system/51/default/efs-system.efs
   Note that 51 generally works for 2012/13/14 year units, however later 2015 units seem to require the 61 variant.
6. Use VCP to upload / flash the eeprom with EU languages and reboot.
7. Re size HDD partition using your script with the MJan implementation.
8. Re-install firmware to get SSS and other missing bits onto the HDD
9. Install maps
10. Run nav db unblocker.

I have just made a image of the HDD using dd at step 9. I need to test it but I think I can burn it using etcher (on a mac) and this would cut the time down considerably.. I plan to just take the drive out of the next unit I convert before step 1, burn the image to it and put it back in the unit. Then presumably I can just run the create acios_db.ini script after step 6 and I will have saved 2 hours waiting for the map install. What are your thoughts?
The above is for the A4/A5/Q5 units, I've got an A1 unit I'm going to test it out with in a few weeks as well.

 

after 95 mins and a sore back , all done.


View attachment 190513

Hey mate,

I'm currently trying to update the firmware on my Audi A1 2011 too.

It's currently running on HN+_JP_AU210_K0642 according to ChatGPT and needs to be upgraded:

Solution: Convert MMI from Japan to EU Firmware

To unlock full Bluetooth functionality (A2DP, NAV, Radio Frequencies, etc.), you'll need to:
1. Convert your MMI from Japan (JP) to Europe (EU) region

• This involves flashing EU firmware — such as HN+_EU_AU3G_K0942 or higher.
• You may also need an EU navigation database and region change activation script.

I have myself managed to find the K0942 file myself but apparently I need to run the JP to EU conversion script first to stop everything effing up lol. I can't seem to find this script online anywhere.

If anyone could point me in the right direction it would be much appreciated, willing to pay if necessary. Thanks very much

Sorry I'm a newbie at all this stuff, trying to learn/teach myself.

 

Post 3 may help