As said before, give it some time. It’s strange, but stranger things had happened…
From the files point of view, everything is ok.
1 Like
Hi,
Thank you both for your time and effort.
Altough the system already has been running for a few days now (just created a new log yesterday for upload) I will leave the system running for a few days.
As a side note, I also check the official Ford site from time to time but it seems like it is still running behind somewhat.
I think even if I hadn’t updated just yet I wouldn’t have been offered the updates there.
Could there be a relation to my system not showing F11 yet (let’s say this version with F11 maps should not be made public for my MY20 built 2021 car)?
1 Like
Not really sure but it is possible…
Well it’s been a few days but nothing has changed unfortunately.
Still it shows F10 maps.
Any suggestions?
Since you have a 2021, do you have automatic updates turned on? You could try cycling that setting. I had to do that on an upgrade before on a 2020 vehicle.
Good suggestion.
Did a couple of cycles this morning, connected to wifi and at the end a search for updates from the car.
No updates available and still it shows F10.
Don’t know what to think anymore
Other than that, do you have any other issues?.
If not, I would leave it alone.
I mean, from the package perspective you have everything you should have for F11 maps.
If you want to try to “debug” it farther, this is what I would try:
- perform a master reset
- disable automatic updates
- recreate a maps update usb
- go through the whole process again.
- check the results, check automatic updates are off
If everything is working fine, it’s up to you if you want to spend 2-3 hours redoing the upgrade…
That’s the only think I could think of
Yeah was thinking in the same direction. Everything is working fine.
That’s always the good thing.
I will see about the master reset, and keep in mind to first disable auto updates next time.
Thank you for your support guys!
This may sound stupid, but there’s something else you could try.
Go back to Sync3 3.4.22020, all the packages keeping maps.
So it would be:
- perform master reset
- disable auto updates
- go back to 3.4.22020 keeping maps
- check how things go
- perform master reset
The reason I’m suggesting this to you is that from experience, latest Sync3 version had to be multiple master reset for some people for it to work ok.
It’s a shot in the dark, but going back to a previous sync3 versions without touching maps will be faster than doing everything again. And if it does not work, going back to the latest sync3 version will be faster as well.
And again, not sure if it’s worth it, since everything is working ok.
I will try that, your explanations seem logical.
I just opened syn3 updater, and when I select 22020 version there’s a big warning about radio logos missing.
Would’nt it be better to go back to 21265 then?
Good catch, I was under the impression 22048 had logos missing, not 22020 as well.
But you are right, both have logos missing, so go back to 21265.
Sorry about that.
1 Like
Where? There shouldn’t be
1 Like
Check it here:
Maybe it’s outdated, I was under the impression 22020 was “complete”, but I may be wrong.
1 Like
Oh 22020 yeah, why wouldn’t you use 22110
(Radio logos likely will only work with 22110 as that’s what they are compiled for)
It’s a plan B. He already has 22110 but after upgrading maps it still says f10 instead of f11.
I remember seeing many users (not some) saying that 22110 seems to require many master resets to function properly, so one thing I suggested was for him to downgrade to 21265 keeping maps and see if it still says f10.
Oh right, yeah then he likely won’t have logos
Ah I see you already have the info.
I am going to plan the route suggested by SaNdMaN.
Hi,
I did the exact steps as you suggested.
Install went fine, another complete reset after installation, no auto updates, no Ford Pass App configuration.
But unfortunately still F10.
Maybe it helps, but I created a new log:
VIN: Removed by me
Versie 5U5T-14G381-EU
Model APIM: 5U5T-14G371-GNC
Type APIM: Navigation
Grootte APIM: 64GB
Vrije Ruimte APIM: 11G
22-6-2022 17:30:21 +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/ = 954M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 132M / 1.4G
/fs/mp/resources = 476K / 71M
/fs/images/ = 11G / 54G
Installed Packages
1U5T-14G421-BAJ
1U5T-14G421-BBJ
1U5T-14G421-BCJ
1U5T-14G421-BDJ
1U5T-14G421-BEJ
1U5T-14G421-BFJ
1U5T-14G421-BGJ
1U5T-14G421-BHJ
1U5T-14G421-BJJ
1U5T-14G658-AG
4U5T-14G422-BBG
4U5T-14G422-BDG
4U5T-14G422-BCG
4U5T-14G422-BAG
4U5T-14G423-AC
5U5T-14G391-AR
1U5T-14G424-BL
APIM AsBuilt
DE00: 0A6A019A50027C064082
DE01: 4E4C010BC00B4890ACBC6E05
DE02: 0000010000
DE03: 00001D8002010A
DE04: 190519052653
DE05: 80
DE06: 0B0033000000005EF100005656620061
Sadly, I’m out of ideas.
Since you already had the required MAP files, this was only a shot in the dark…
The only thing I would think of would take 2-3 hours, which does not seem worth it.