MG4 Software Update Thread

[Diggsy]

So the capacity is preventing the maps install. Wonder is there a way to remove the maps for countries you don’t need, even just to test?

 

[the happy bunny]

So the capacity is preventing the maps install. Wonder is there a way to remove the maps for countries you don’t need, even just to test?

I've been tinkering with the map files for a few days now and have concluded that breaking a map into parts isn't practically feasible.

As for the storage capacities, if a genuine Trophy shows 32GB or 64GB, that's a dealbreaker. However, if it also shows 8GB (which wouldn't surprise me), there might be another storage option that's not accessible. This could be surface-mounted storage, in which case the capacity would likely be the same, or it could be a microSD card, which could have either the same or a different capacity.

I’m now pretty sure the maps are not stored here because I just installed Middle East maps - which obviously don’t have the same exact size as the Australian ones and the used space is exactly the same : 5.05 out of 8 GB…

 

[leonkernan]

There are a few different partitions that get mounted:

/userdata
/map <- This one is what you're saving the maps to
/fota
/configure <- this is where the car setup lives.
/online

 

[the happy bunny]

Thanks, how did you manage to access them?

 

[leonkernan]

Thanks, how did you manage to access them?

I looked at the fstab file.

# Android fstab file.
/dev/block/platform/11230000.mmc/by-name/boot /boot emmc defaults defaults slotselect
#/dev/block/platform/11230000.mmc/by-name/system / ext4 ro wait
#/dev/block/platform/11230000.mmc/by-name/vendor /vendor ext4 ro wait
#/dev/block/platform/11230000.mmc/by-name/userdata /data ext4 noatime,nosuid,nodev wait,encryptable=footer
/dev/block/platform/11230000.mmc/by-name/userdata /data ext4 noatime,nosuid,nodev wait,quota,resize,fileencryption=aes-256-xts
/dev/block/platform/11230000.mmc/by-name/Map /Map ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,formattable,encryptable=footer
/dev/block/platform/11230000.mmc/by-name/vr /vr ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,formattable,encryptable=footer
/dev/block/platform/11230000.mmc/by-name/online /online ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,formattable,encryptable=footer
/dev/block/platform/11230000.mmc/by-name/fota /fota ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,formattable,encryptable=footer
/dev/block/platform/11230000.mmc/by-name/configure /configure ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,formattable,encryptable=footer
#/dev/block/platform/11230000.mmc/by-name/userdata /data ext4 noatime,nosuid,nodev wait,encryptable=/dev/block/platform/11230000.mmc/by-name/metadata
#/dev/block/platform/11230000.mmc/by-name/cache /cache ext4 noatime,nosuid,nodev wait
/dev/block/platform/11230000.mmc/by-name/misc /misc emmc defaults defaults
/dev/block/platform/11230000.mmc/by-name/expdb /expdb emmc defaults defaults
/devices/platform/112c1000.usb/112c0000.xhci/usb* auto auto nosuid,nodev voldmanaged=usb:auto,encryptable=userdata
/devices/platform/11271000.usb/11270000.xhci/usb* auto auto nosuid,nodev voldmanaged=usb:auto,encryptable=userdata
/devices/platform/11240000.mmc/mmc_host* /storage/sdcard1 vfat nosuid,nodev voldmanaged=sdcard1:auto,encryptable=userdata
/devices/platform/11250000.mmc/mmc_host* /storage/sdcard1 vfat nosuid,nodev voldmanaged=sdcard1:auto,encryptable=userdata

 

[the happy bunny]

Well thought!!!

But I don’t think we can see the size of the partitions from the fstab file, can we?

 

[leonkernan]

Well thought!!!

But I don’t think we can see the size of the partitions from the fstab file, can we?

No and at the moment a terminal just gives a permission denied error.
I'm working on getting better access but not quite ready yet.

 

[Spaniard]

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.

Nope!

I made same mistake and got MD5 errors! Only when I used HDD formatted to NTFS everything went fine. Try again with the maps that gave you md5 error using actual hdd with ntfs.

That system screws the USBs badly as it does not eject them and touches files constantly.

I'm talking about updating maps in a Trophy without any "hack". Native regular update.

 

[the happy bunny]

It seems a lot of people have faced formatting issues. I’m going to try using NTFS and Ext4 partitions on SSDs tonight to see if it helps.

 

[NLMGSAN]

The only way it accepted the map updates was using ntfs.

 

[the happy bunny]

Thanks!
I’m currently copying files to an NTFS formatted SSD…

 

[Diggsy]

Thanks!
I’m currently copying files to an NTFS formatted SSD…

Good luck!!

 

[the happy bunny]

Failed…

 

[the happy bunny]

I finally managed to install the maps

Range-anxious wifey is happy… and so is the Bunny!

I used the same USB stick that had failed before, but this time, I downgraded first. Here’s what I did:

- Downgraded to 1100R33.

- Accessed the engineering menu, enabled secret mode (five taps in the lower right corner and entered the code from this link)

- Disabled “verify updates” in the secret menu

- Upgraded back to 1300R59.



And Voilà!

I currently have 22q2 installed. I’m now trying to upgrade to 23q4… let’s hope I don’t brick everything!

 

[wjohnson12321]

I finally managed to install the maps

Range-anxious wifey is happy… and so is the Bunny!

View attachment 32076

I used the same USB stick that had failed before, but this time, I downgraded first. Here’s what I did:

- Downgraded to 1100R33.

- Accessed the engineering menu, enabled secret mode (five taps in the lower right corner and entered the code from this link)

- Disabled “verify updates” in the secret menu

- Upgraded back to 1300R59.



And Voilà!

I currently have 22q2 installed. I’m now trying to upgrade to 23q4… let’s hope I don’t brick everything!

This is unbelievably exciting. I don't suppose you could write a tutorial on how to do it from a stock R33 SE? Really tempted to have a go as long as I can downgrade to R33!

 

[the happy bunny]

This is unbelievably exciting. I don't suppose you could write a tutorial on how to do it from a stock R33 SE? Really tempted to have a go as long as I can downgrade to R33!

Yes, it’s possible to revert to R33. The files are provided, and the upgrade/downgrade process is quite seamless.

For more details, check out posts #4085 and #4120 in this thread—they’re already pretty much detailed.

 

[Wadda]

Yes, it’s possible to revert to R33. The files are provided, and the upgrade/downgrade process is quite seamless.

For more details, check out posts #4085 and #4120 in this thread—they’re already pretty much detailed.

Wow this is impressive. Good work. You need to do a step by step guide for doing this for anyone else brave enough to do it.

Would you not have been better trying to up the maps to 2023 before upgrading to r59?

 

[the happy bunny]

Wow this is impressive. Good work. You need to do a step by step guide for doing this for anyone else brave enough to do it.

Would you not have been better trying to up the maps to 2023 before upgrading to r59?

Wow this is impressive. Good work. You need to do a step by step guide for doing this for anyone else brave enough to do it.

Would you not have been better trying to up the maps to 2023 before upgrading to r59?

I’ve already posted two detailed updates, but I can put together a step-by-step tutorial if it’s helpful. That said, I’d prefer not to go into too much detail because I don’t want people diving in blindly. It’s essential to fully understand what you’re doing.

The only tricky part was installing the maps; the rest was relatively straightforward. I’ve upgraded and downgraded a dozen times without issues, but entering the engineering menu carries some risk. you could potentially brick something.


I know that people in Australasia, for instance, have different firmware releases. Technically, they could update their car to European specs like R59, but it wouldn’t give them functional maps. I tried installing the AUS-NZ maps and encountered an error due to the localisation differences across releases. Worse still, they could end up with a system that isn’t adapted to local road specifications. Since earlier versions like R05 and R11 haven’t been leaked online, their only option for reverting to the original firmware would be to piteously visit a dealer for assistance.

You can’t install maps while running R33 by the way, the upgrade system doesn’t even check for map files.

I found out something interesting:

As I mentioned earlier, my car passed activation when I first installed R59. MG’s policy is to provide five years of free connected services, and after installing R59 on 3 November 2024, I noticed these services are now active until 2 November 2029—unless they decide to remove my VIN from the activated list.

 

[Wadda]

Wow this is impressive. Good work.

I found out something interesting:

As I mentioned earlier, my car passed activation when I first installed R59. MG’s policy is to provide five years of free connected services, and after installing R59 on 3 November 2024, I noticed these services are now active until 2 November 2029—unless they decide to remove my VIN from the activated list.

Just don’t post vin on here.

 

[the happy bunny]

Just don’t post vin on here.

It begins with an L