MG4 Software Update Thread

Out of curiosity what do people have for SW P/N? Displayed like 11-64-30-76-1
Especially for 2024 versions as it has been said although the R** is the same the actual software is different, maybe also good to see how the Australian versions compare

For my UK 2023 trophy this software list came up for my VIN, but going through some posts I've matched a couple of R**
11836446 20/08/24 is R59
11643054 01/02/24 is R46 (rare)
11643076 19/07/23 is R46 (common)
11599376 15/06/23
11580882 07/04/23 is R40 show as 11-58-8-82-1
11545575 25/03/23
11517319 28/11/22 is R33 (common)
11479398 17/10/22 is R33 (rare)
11464913 23/08/22
11430170 23/07/22

MCU is
68.4.7.0 is R59
68.4.3.0 is R46
68.3.8.0 is R40
68.3.3.9 is R30
68.3.3.6 is R24

If I knew how to find random VIN numbers for the different variants & locations I'd just pull up the software list from MG but without VIN's I can't

Why can't we just give you our VIN's? It's publicly displayed on the car I don't think it's a big deal
 
Sorry, do you have MG service subscription and special SAIC software so you can update your modules via SIPS?
You can see info here

SIPS is the software, subscription through RMI
 
Why can't we just give you our VIN's? It's publicly displayed on the car I don't think it's a big deal
You could if you wish but like people generally block their reg, it can be used by a small minority for malicious reasons, to the majority it makes no difference

I'll buy a subscription later today to check for updates & I'll send the software list etc to those that have sent their VINs
 
If you update via USB the MCU will be as listed, if you update via SIPS (as dealer instructions recommend) the it'll be the latest
I've got 68.4.7.0 with R46 as I updated to R46 using USB but updated MCU via SIPS
For DIY updates it should be as listed but I'd recommend checking the current version and if the MCU is already a higher no. then leave it
that means for DIY flashers only flash "AVN MPU" and NOT "Infotainment System ECU" if MCU is 68.4.7.0 or higher?
 
If you update via USB the MCU will be as listed, if you update via SIPS (as dealer instructions recommend) the it'll be the latest
I've got 68.4.7.0 with R46 as I updated to R46 using USB but updated MCU via SIPS
For DIY updates it should be as listed but I'd recommend checking the current version and if the MCU is already a higher no. then leave it
Will you go to R59 or stick with R46?

Just trying to figure out where the sweet spot is for everything right now.
 
that means for DIY flashers only flash "AVN MPU" and NOT "Infotainment System ECU" if MCU is 68.4.7.0 or higher?
you can update the MCU by yourself via USB like you do with MPU. The MCU is included in the package and has its own updater in the menu

68.4.7.0 is what included in R59, this is the higher we have
 
that means for DIY flashers only flash "AVN MPU" and NOT "Infotainment System ECU" if MCU is 68.4.7.0 or higher?
That's correct

Will you go to R59 or stick with R46?

Just trying to figure out where the sweet spot is for everything right now.
Although Bluetooth is worse on R46 compared to R40 for the moment I'll stick with R46
As people have gotten into the android system now & have updated some apps & sideloaded others I might look at updating the settings APK to see if that gives ELK shortcut
 
Although Bluetooth is worse on R46 compared to R40 for the moment I'll stick with R46
As people have gotten into the android system now & have updated some apps & sideloaded others I might look at updating the settings APK to see if that gives ELK shortcut
Indeed, I do wonder if there is a way via the Android Sub-system menu to trigger ELK off or even some sort of "automation" from an App to turn it off each time you startup... but I am no APK dev
 
Indeed, I do wonder if there is a way via the Android Sub-system menu to trigger ELK off or even some sort of "automation" from an App to turn it off each time you startup... but I am no APK dev
Yes, it is possible to make an apk that launches after boot and calls android automotive classes related to LKA, i'm working on it.

I don't want to get too technical in this thread, but the code that manages the vehicle settings is here:
sources\com\saicmotor\sdk\vehiclesettings\manager\VehicleSettingManager.java

Function that sets the value:

public void setLaneKeepingAsstMode(int signalValue) {
sendMessage(VehicleSettingConst.SIGNAL_LANE_KEEPING_ASST_MODE);
IVehicleSettingService iVehicleSettingService = this.mVehicleSettingService;
if (iVehicleSettingService != null) {
try {
iVehicleSettingService.setLaneKeepingAsstMode(signalValue);
} catch (RemoteException except) {
except.printStackTrace();
}
}
}

Possible values:
public class LaneKeepingAsstMode {
public static final int LANE_KEEPING_ASST_ELK = 5;
public static final int LANE_KEEPING_ASST_LDP = 3;
public static final int LANE_KEEPING_ASST_LDW = 2;
public static final int LANE_KEEPING_ASST_LKA = 4;
public static final int LANE_KEEPING_ASST_OFF = 1;
public static final int LANE_KEEPING_RESERVED = 6;
public static final int LANE_KEEPING_TWO_RESERVED = 7;
public static final int LANE_KEEPING_UNAVAILABLE = 0;
public LaneKeepingAsstMode() {
}
}

The main problem is debugging, not having a proper emulation environment complicates things.
 
Last edited:
For people that have provided vin's I'll try again tomorrow but at the moment I'm £50 down as I've tried to get a subscription 3 times, been charged every time but got "unknown error, please contact the administrator for handling" and no SNW login provided
 
you can update the MCU by yourself via USB like you do with MPU. The MCU is included in the package and has its own updater in the menu

68.4.7.0 is what included in R59, this is the higher we have
Hi,
I installed R59 when the MCU in my R46 version was at 68.4.3.0 and it remained at this version despite two applications of the R59 MCU.
I also tried the T-box update but neither the MPU nor the MCU could be changed because it was rejected (package not recognized).
However, I read that a participant had managed to do it.
What do you think is wrong?
 
Hi,
I installed R59 when the MCU in my R46 version was at 68.4.3.0 and it remained at this version despite two applications of the R59 MCU.
I also tried the T-box update but neither the MPU nor the MCU could be changed because it was rejected (package not recognized).
However, I read that a participant had managed to do it.
What do you think is wrong?
Nothing is wrong. The R59 package has 68.4.3.0 included and not the later version available via sips.
 
Nothing is wrong. The R59 package has 68.4.3.0 included and not the later version available via sips.
I don't understand your answer when I read that :
you can update the MCU by yourself via USB like you do with MPU. The MCU is included in the package and has its own updater in the menu

68.4.7.0 is what included in R59, this is the higher we have
MG4 Software Update Thread
 

Are you enjoying your MG4?

  • Yes

    Votes: 911 77.7%
  • I'm in the middle

    Votes: 171 14.6%
  • No

    Votes: 90 7.7%
Support us by becoming a Premium Member

Latest MG EVs video

MG Hybrid+ EVs OVER-REVVING & more owner feedback
Subscribe to our YouTube channel
Back
Top Bottom