MG4 Software Update Thread

[Diggsy]

This is fast becoming the most interesting thread on here! Keep up the great work

 

[the happy bunny]

I didn’t manage to get the navigation working but I think it’s probably not going to be an easy task, if it’s even possible.

Knowing it was an MD5 issue, I dug into the MD5 manifests and found this line at the end of \maps\TeleNavMapData\map\tiles\md5manifest.txt:

96961c2db9b718c087e447e6013Bc973 MULAN_EU_HERE_2304_RC.sig 2210903

Which refers to the MD5 checksum of a 2210903 byte file by the name of MULAN_EU_HERE_2304_RC.sig



There is no such file in the update package, so I guess this file is already supposed to be in the iSmart system and is part of the verification process.

After a few trials and errors, I discovered that all file sizes are checked in file_index.csv, which itself can’t be modified since its integrity is controlled elsewhere—possibly in the file_verification binary.

I attempted to remove the line and replace it with the same number of line breaks to maintain the file size, but, as expected, that didn’t work. I’ll look for a workaround later, but it’s clear the update didn’t fail due to a bug. it was blocked intentionally as part of a security check. Cracking it likely involves much more than just tweaking the update files.

 

[mg4mc]

I don't think the MULAN_EU_HERE_2304_RC.sig file is part of the car system because it contains the map version/date. The 23Q3 zip has MULAN_EU_HERE_23Q3_RC.sig in the mdmanifest.txt file.

That file is not in the manifest for the 22Q2 zip, it only appears in the "new" files. I recall the ZS folks also have problems using the new map zips, and have to delete a couple of files from the zip for it to work...

After a few minutes if failed with message ‘Failed to verify the map files in md5 mode!’

On another thread was the suggestion to remove ‘file_verification’ and ‘VN.txt ‘ in the USB root folder ‘maps. I did this and tried again – this time it worked.

 

[the happy bunny]

I don't think the MULAN_EU_HERE_2304_RC.sig file is part of the car system because it contains the map version/date. The 23Q3 zip has MULAN_EU_HERE_23Q3_RC.sig in the mdmanifest.txt file.

That file is not in the manifest for the 22Q2 zip, it only appears in the "new" files. I recall the ZS folks also have problems using the new map zips, and have to delete a couple of files from the zip for it to work...

Yeah I’ve read that thread, and also tried to remove the files, but unfortunately to no avail…

 

[the happy bunny]

File_verification at root is basically a Base64 string.
I found out that the MD5 hash of this file is the same as this unknown file MULAN_EU_HERE_23Q4_RC.sig
So it’s part of the verification process… I still need to understand how it works.

Does anyone know if it’s possible to download an older 2022 map update? I’d like to make some further comparisons.

 

[Diggsy]

ignore, think you have already done that a while ago

 

[mg4mc]

Does anyone know if it’s possible to download an older 2022 map update? I’d like to make some further comparisons.

PM sent

 

[the happy bunny]

Thanks to @mg4mc, I managed to get my hands on the previous version of the maps.

This version doesn’t include VN.txt, the file_verification binary, or any references to the “Mulan” file. When I tried to install it, the process failed in exactly the same way as with 2023Q4.

The simplest approach might be to downgrade to a legacy release, older than R46, install the maps, and then reinstall R59. However, as far as I know, no installation files for versions that old have leaked.

 

[Diggsy]

I take it you’ve tried different memory sticks, different types of format etc.?

Also, are you doing this on a Mac or a PC? Have read that doing it on a Mac caused issues for some updating ZS maps.

 

[the happy bunny]

I take it you’ve tried different memory sticks, different types of format etc.?

Also, are you doing this on a Mac or a PC? Have read that doing it on a Mac caused issues for some updating ZS maps.

Yes, I’ve been using USB 3.1 and older sticks formatted to FAT32 or vFAT, all from a PC running on Windows 11.

In the end, I managed to install the Australian maps… they would have been useless for me, but they didn’t work anyway because of regional limitations.

 

[Diggsy]

Yes, I’ve been using USB 3.1 and older sticks formatted to FAT32 or vFAT, all from a PC running on Windows 11.

In the end, I managed to install the Australian maps… they would they have been useless for me, but they didn’t work anyway because of regional limitations.

View attachment 32043View attachment 32044

Progress! You just need to suss why the EU one isn’t working now…good luck! Great work to this point

 

[Tomg4]

The advantages are fairly minor, especially without nav, but since it just works, I’m keeping my car on 1300R59 for now and will plan to downgrade back to 1100R33 a couple of days before it goes in for servicing.

To get the navigation working, I’d need either an older MPU version, like 1300R40, or a different version of the maps—which I currently don’t have. However, this experiment has been useful in understanding what happens when you install a Trophy firmware on an SE model: what works and what doesn’t.

If a future Trophy firmware with enhanced features gets leaked, it might be worth trying on the SE.

——

My current configuration:

• MPU: 1300R59
• MCU: 69.3.8.0 (I chose to revert to the original MCU from R33, I’ve experienced no ill effects so far)

New Features in 1300R59 (previously unavailable in 1100R33)

• Weather display
• Amazon Music
• Ability to restrict charging to a certain percentage even with the LFP battery
• 4G Hotspot/Wi-Fi
• MG TouchPoint

Features unavailable in 1300R59 (previously available in 1100R33)

• As far as I’ve tested: None, but the “switch off car” button is not readily available on the drop-down menu anymore (it’s still located of course in the menus)

Trophy features not (yet?) available due to software limitations:

• Navigation: The elephant in the room.
• Voice control: Pressing the voice command button brings up the voice UI, but it’s not functional since the voice engine isn’t installed. It may be possible to install it using the “Map & VR data USB upgrade” option in the system menu if we can grab the correct file.
• Navigation/ display in the instrument cluster: Requires an additional ECU upgrade.

Trophy features not functional on the SE due to hardware limitations

• Heated steering wheel: The SE model doesn’t have a heated steering wheel, so the icon in the A/C panel is inoperative.
• Immersive sound system: The SE lacks a subwoofer and some speakers, so this feature is not available.
• 3D cameras: Not installed in the SE. The UI only shows a diagram similar to R33’s, using the ultrasonic sensors (including distance).

View attachment 32005View attachment 32006View attachment 32007View attachment 32008View attachment 32010

Do heated seats work? In the Netherlands the SE version doesn't have heated seats. But I can imagine that MG used the same seats (with heating elements) for all models. Also because the Scandinavian SE model has heated seats (and a heated steering wheel)

 

[the happy bunny]

Do heated seats work? In the Netherlands the SE version doesn't have heated seats. But I can imagine that MG used the same seats (with heating elements) for all models. Also because the Scandinavian SE model has heated seats (and a heated steering wheel)

It’s a pity they aren’t included—heated seats are much more efficient than the cabin heater.

I’m not sure whether the seat heating resistors are present and wired, but even if they are, they’re managed by a separate ECU, which isn’t affected by these upgrades.

The MPU and MCU updates only upgrade the infotainment.

There is a steering wheel heating icon in the A/C panel by the way, but it’s not functional.

 

[Evgen K]

The installation began as expected, but about halfway through, it was interrupted by an MD5 check error, causing it to abort.

The map update packed contains MD5 file, if i remember right it's "maps\file_verification". It's possible that if you delete it, the car's installer will install map data without MD5 verification.

 

[the happy bunny]

The map update packed contains MD5 file, if i remember right it's "maps\file_verification". It's possible that if you delete it, the car's installer will install map data without MD5 verification.

Thanks, I tried that too, of course… but no luck.

I did manage to install the stock Australian maps without modifying anything. While it wouldn’t display the map due to location issues, the installation itself was successful.

One key difference is that the Australian maps are a mere 1GB large, while the European maps are a hefty 20GB…

 

[Evgen K]

What advantage do you see in co-opting the Trophy navigation system?

preheating the HV battery when you go to the DC charge station

 

[haloweenhamster]

Thanks, I tried that too, of course… but no luck.

I did manage to install the stock Australian maps without modifying anything. While it wouldn’t display the map due to location issues, the installation itself was successful.

One key difference is that the Australian maps are a mere 1GB large, while the European maps are a hefty 20GB…

Have you gone into the android system, storage to see what the internal capacity is?

 

[tommasov]

Yes, I’ve been using USB 3.1 and older sticks formatted to FAT32 or vFAT, all from a PC running on Windows 11.

In the end, I managed to install the Australian maps… they would have been useless for me, but they didn’t work anyway because of regional limitations.

View attachment 32043View attachment 32044

Has the navigator been activated in the settings?
The navigator has a remote activation and I assume it is linked to the VIN of the car.
The string that corresponds to that message is "SdcardNotValidForVehicleErrorMessage" and comes from telenav, but "Sdcard Not Valid For Vehicle" does not make much sense, but perhaps it is just a side effect of the discrepancy in the version of the car (or they just put a name to the string)

 

[the happy bunny]

Has the navigator been activated in the settings?
The navigator has a remote activation and I assume it is linked to the VIN of the car.
The string that corresponds to that message is "SdcardNotValidForVehicleErrorMessage" and comes from telenav, but "Sdcard" does not make much sense, but perhaps it is just a side effect of the discrepancy in the version of the car

Yes, navs and avn are both validated

 

[the happy bunny]

Have you gone into the android system, storage to see what the internal capacity is?

That’s what I plan to do tonight, using the @ method

It shows 8GB… but it’s almost empty, and I can’t find the Australian maps that are currently installed, nor anything from the system, very few logs, nothing.

I suspect there’s another partition we can’t access from the storage app, and this one might just be the Android partition. When you consider that this car was built with OTA updates in mind, 8GB sounds extremely limited!

How much capacity is there in the Throphy?