Mem_err01 again


I am the first owner of a Ford Kuga that was delivered to me in January 2022.
Until recently I was able to update my car’s software and maps using official Ford downloads. However, sometime around summer time 2022 I downloaded yet another map update - and being unaware that one shouldn’t interrupt updating process (formerly Skoda owner - updates straightforward and hasslefree, if interrupted - would resume from where it left off.) I started the update process, went for a approximately 30 min. drive and then stopped and switched the car off. I was since getting the infamous Mem_err01. Took it to Ford - they apparently managed to update my maps under warranty. Month later I checked Ford website and there was another update ready - downloaded it and - Mem_Err01 again.
I decided to give Cyanlabs tool a go, these were the steps I took:
Used Gracenote removal - still error
Used small voices removal - still error
Used downgrade option from fix section - downgraded - lost screen - panicked a little.
Downloaded latest Sync and Map verison using Cyanlabs tool
Successfully installed - screen back on - System software showing 3.4.22200, Maps F11, Gracenotes
Now, Ford website tells me there is new maps update - approximately 8.0GB in size - downloaded - and - got mem_err01 again…
Using interrogator tool - I have 14GB free space (64GB device).
Any ideas?

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: MY20

Install Type: OEM

Old SYNC Version: 3.4.22200

New SYNC Version: 3.4.22200

Do you have a error message, if so what is it?

Update Method: Official Ford

Give us more details, you should not mix upgrade methods.
Use either Ford’s or Cyanlabs’

Apologies, I have now updated the post with more details, I thought the template would have more space to include those at next page.

Sorry unrelated, what was you expecting to have more room for, I can modify the form accordingly :grinning::thinking:

If you have F11 maps for EU, those are the lastest ones.
I assume that after you performed all those actions without Ford knowing, they think you have older maps.
But if you are running F11 maps, you are ok.
What you could try is running the interrogator log and check which packages are installed. Based on that, we can see if there’s anything to do.

Also, I’m late to recommend not messing with your unit, because it’s MY20 and under warranty.

To which version is trying Ford to upgrade?.

Sorry, I assumed that the template was just a sort of introduction and I would be then taken to another screen where I would put all the details. You can tell I don’t use forums too often :joy:

1 Like

To be honest, I don’t think that the Ford dealership actually updated my maps, they were showing F10 and that was in November 2022. They did update the sync to 3.4.22200 however.
So in early December I went to Ford website and it showed 29.8 GB map update - I got mem_err01 when I tried installing. I left it be for some time, then I went ono Ford website and it told me to download the 8GB map update then. Somewhen in the process the Sync was automatically updating over WiFi on my driveway - but sfter successful update the sync is still 3.4.22200 but I noticed that maps were showing F11 (I was never successful in installing any udpates since the summer 2022).
This is when I resorted to using Cyanlabs tool.
I will run the interrogator tool again soon and post it here.

That’s exactly my point, if the F11 update was performed outside Ford that’s why they are telling you there’s an update pending.

The interrogator log will show which packages are installed .

Hello, I apologise for wasting your time, I should have done this the following way in the first place.

Event Log:

January 2022 - car delivery, first owner of Ford Kuga
March/April - first successful Sync update using official Ford website - log created - Ford website accepting the update
June 2022 - New map update - installation failed due to me switching the car off in the middle of the update. Re-attempted installation - MEM_ERR01.
Somewhen between June 2022 to November 2022 - Sync automatic OTA update happening while car sitting on a driveway connected to home WiFi
After successful automatic update I attempted to install June maps - MEM_ERR01
November 2022 - took the car to Ford dealership - under warranty they were meant to update the system and the maps. After leaving the car with them for a whole day - I was told the car was updated. I have my doubts whether they actually updated the maps as the car info was still showing F10 (I read somewhere online that the latest were F11)but they did update the Sync to 3.4.22200. Bit off-topic but they left the car in appalling dirty state, but my point is that the Ford so far have been rather disappointing - both customer service and all this kerfuffle with software updates.
Early December 2022 - Went to the Ford website - 29GB update became available - downloaded - installation failed - MEM_ERR01
Late December 2022 - Went on the Ford website - 8GB update became available - downloaded - installation failed - MEM_ERR01
Early January 2023 - automatic updates OTA when connected to home WiFi - successful update - but Sync still showing 3.4.22200, maybe unrelated but I did notice however that maps were now F11 from F10 - I then attempted 8GB installation - MEM_ERR01

I have now resorted to Cyanlabs Syn3updater -
Generated a interrogator file that showed 14GB free space.
Using troubleshooting section of the tool I:
Removed Gracenotes - attempted installation of official 8GB update - MEM_ERR01
Removed Small Voice Package - attempted installation of official 8GB update - MEM_ERR01
Created downgrade USB - successful - however after re-starting the car the screen was not working.
Using Syn3updater - I downloaded Sync 3.4.22200 and 29GB Map package - installation successful - screen working again.
I was unable to generate Interrogator Log using Syn3updater - PKG_ERR04
I was unable to generate Interrogator Log using official Ford tool - PKG_ERR04
I was able to generate Interrogator Log after slightly modifying GB5T-14G386-AC (combined official Ford tool’s autoinstall.lst with the AC tool)
Performed Master reset
Attempted to install official Ford 8GB update - MEM_ERR01

I also mistakenly told you that the latest interrogator tool showed 14GB - that was the amount of space before successful Cyanlabs update. I currently have 11GB free space.

Sorry for super long post, hope it does make things less confusing.
Here is the Interrogator Log:

Version NU5T-14G381-AA
APIM Model: LU5T-14G371-GNC
APIM Type: Navigation
APIM Size: 64GB
APIM Free Space: 11G
10.01.2023 23:05:22 +00:00

Partition Type = Free / Total
/fs/sd/MAP/ = 1.0M / 1.1G
/fs/sd/MAP/ = 14M / 2.8G
/fs/sd/MAP/ = 14M / 2.3G
/fs/sd/MAP/ = 7.8M / 1.5G
/fs/sd/MAP/ = 17M / 2.2G
/fs/sd/MAP/ = 21M / 3.8G
/fs/sd/MAP/ = 336K / 38M
/fs/sd/MAP/ = 5.6M / 3.2G
/fs/sd/MAP/ = 25M / 3.2G
/fs/Nuance/ = 27M / 4.6G
/fs/Nuance/ = 29M / 4.8G
/fs/Nuance/ = 25M / 4.3G
/fs/Nuance/ = 35M / 3.6G
/fs/Nuance/ = 8.4M / 1.9G
/fs/Nuance/grace = 21M / 1003M
/fs/rwdata/ = 832M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/mp/resources = 332K / 72M
/fs/images/ = 11G / 54G

Installed Packages


APIM AsBuilt
DE00: 8A6A01DA50220E048082
DE01: 554B010EC00ADC90ACB04E05
DE02: 0007000000
DE03: 00000680250102
DE04: 18061810295F
DE05: 20
DE06: 17003300000000A175000056567B0088

Thank you for the information.

So, long story short, your unit has the latest map version for EU, which are packages


Sync3 is the N-1 version 22200. There’s a 22251 available, but since your unit is under warranty and updates seem to be working, I would not change that (bedsides, it’s not worth it, really).

I’m not sure if I would touch your unit.

To be honest I was slowly getting to that conclusion.
Thanks for your help and patience with me!

No problem, you are welcome.

What I would suggest is performing a master reset, since the update history of the unit has been a bit chaotic and all over the place.

It’s not necessary to be honest, but I would do it nonetheless.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.