MG4 Software Update Thread

[haloweenhamster]

So... These are the only options I have? Where is MCU?

AVN VIP

 

[the happy bunny]

Yes, It’s AVN VIP for the MCU.

After updating the MPU, your system will be upgraded to R59, where you’ll find a different engineering menu. You’ll need to tap “Infotainment System MCU” to upgrade the MCU.

By the way, your MCU is quite old, so even if you stay on R33, you’ll see some improvements with 69.3.8.0

 

[Onehebergeur]

This never worked for me:

You will need to tap “Infotainment System MCU” to upgrade the MCU

what should we do about USB?
I specify that I am already in 69.3.8.0

 

[the happy bunny]

This never worked for me:

You will need to tap “Infotainment System MCU” to upgrade the MCU

what should we do about USB?
I specify that I am already in 69.3.8.0

If you are currently on 1100R33, the ota_update.zip archive must be at the root level.

If you are currently on R1300R46 or 1300R59, the ota_update.zip archive must be in a folder named AVN_MPU.

In order to bypass this requirement, without headaches, you can copy the archive both to the root level and into the specified folder, so it will work regardless of the currently installed version.

If you apply the MPU and MCU upgrades with the files currently leaked on the web:

1100R33
MPU will upgrade to SWI69-29958-1100R33
MCU will upgrade to 69.3.8.0

1300R46
MPU will upgrade to SWI68-29958-1300R46
MCU will upgrade to 68.4.3.0

1300R59
MPU will upgrade to SWI68-29958-1300R59
MCU will upgrade to 68.4.3.0 (unfortunately, not the last one, 68.4.7.0)

 

[wjohnson12321]

Yes, It’s AVN VIP for the MCU.

After updating the MPU, your system will be upgraded to R59, where you’ll find a different engineering menu. You’ll need to tap “Infotainment System MCU” to upgrade the MCU.

By the way, your MCU is quite old, so even if you stay on R33, you’ll see some improvements with 69.3.8.0
View attachment 32234

hmmm oh dear I have hit a snag. So I have put the file in the root as per instructions but it simply wont recognise the file and wont update the MCU from the MCU VIP button. Any thoughts? I guess I could try put on R59 without updating the MCU?

 

[the happy bunny]

hmmm oh dear I have hit a snag. So I have put the file in the root as per instructions but it simply wont recognise the file and wont update the MCU from the MCU VIP button. Any thoughts? I guess I could try put on R59 without updating the MCU?

Is your car in “ready” status ?

 

[wjohnson12321]

Is your car in “ready” status ?View attachment 32238

Yes, and I've used exactly same usb and procedure I successfully updated the MPU to R033 but it just won't work for MCU?

 

[the happy bunny]

Do you get a specific error?

 

[wjohnson12321]

Do you get a specific error?

Just the usual couldn't find the file

 

[the happy bunny]

You may try upgrading MPU to R59 first, then.

 

[wjohnson12321]

Crikey this thing is stubborn! So im on R59 and still unable to update MCU!

 

[Stan1970]

Does anyone else have the problem of downloading the update files? I keep getting files around 480 Megabytes and they all are different sizes and corrupt. " Unexpected end of archive" Errors.

 

[the happy bunny]

That’s weird…

Very temperamental indeed!

Perhaps your MCU is too old for the update to work and might require updates to other modules beforehand (just a supposition).

 

[haloweenhamster]

Does anyone else have the problem of downloading the update files? I keep getting files around 480 Megabytes and they all are different sizes and corrupt. " Unexpected end of archive" Errors.

Have you tried to download from the Google drive?

MG – Google Drive

drive.google.com

Crikey this thing is stubborn! So im on R59 and still unable to update MCU!

Tbh if you're having issues I'd recommend not doing DIY updates/mods
Updates I'd generally say anyone can do as long as they accept there's a small risk
Mods on the other hand you need to be tech savvy and there's more risk involved as unexpected things can happen
I wouldn't want you to attempt something and for it to break

 

[the happy bunny]

Tbh if you're having issues I'd recommend not doing DIY updates/mods
Updates I'd generally say anyone can do as long as they accept there's a small risk
Mods on the other hand you need to be tech savvy and there's more risk involved as unexpected things can happen
I wouldn't want you to attempt something and for it to break

I didn’t mean to suggest that he would update other ECUs himself.

It isn’t possible with these files anyway; it requires a visit to the dealer.

 

[haloweenhamster]

I didn’t mean to suggest that he would update other ECUs himself.

It isn’t possible with these files anyway; it requires a visit to the dealer.

What you have done I'd class as a mod (modification) as it's not standard OEM

Even with USB updates there shouldn't be any real risk but it's still an unlikely possibility

As far as I know no-one has gotten into a recovery boot if the worst should happen

MCU won't have that option

I also have the TBOX USB update files but haven't tried them and I think they could also be more of a risk so haven't shared them

On the trophy there's a few USB update options, I'm hoping to find the DSP files to see if we can modify them for people that add amplifiers etc

 

[wjohnson12321]

I've reverted back to R33. I do know a fair bit about it from a Computer Science background but to be honest I have to agree that all it would take is a mismatch in ECU software and the front end and it could end in tears! Ive seen many android custom roms go wrong in pretty spectacular ways and the device often ended up in the bin so I think everyone needs to tread carefully!

 

[3L3ctroNuc]

Crikey this thing is stubborn! So im on R59 and still unable to update MCU!

I too had problems with the MCU update :
The technician had missed the R46 installation (forgot to update the MCU, resulting in the left star bug) and was unable to correct it despite three other visits.
My own reinstallation of the R46 MCU went smoothly and fixed the bug by upgrading to (68.4.3.0).
Then I wanted to upgrade to R59 (not available in France) to get the charge planning. MPU was installed but after rebooting, I couldn't do the same with MCU.
By redoing the whole procedure and insisting (reformatting in FAT32 with Rufus and reloading the .zip file several times) I succeeded but still in (68.4.3.0) whereas I was thinking of switching to (68.4.7.0).
By formatting in NTFS under Ubuntu, my USB key is recognised as an audio/video key after insertion, whereas in FAT32 it often fails or displays warning boxes.

 

[siteguru]

Maybe I'm not remembering correctly, but does the R59 update package available via here still not have the latest MCU version? Therefore it doesn't matter how many times you try to update, it'll still stay at the same MCU.

 

[the happy bunny]

With R59, the MCU version should be 68.4.7.0.
However, with these files, it only updates to 68.3.4.0.
I haven’t noticed any adverse effects so far.