Sync 3.2/3.3 to 3.4 Upgrade Tutorial

Tue Oct 15, 2019 6:53 pm

trotsky wrote: ↑Fri Oct 11, 2019 3:53 pm
glockss wrote: ↑Thu Oct 10, 2019 8:11 pm Pretty sure Sync 3.0 is not possible to upgrade to 3.2 and up.
Since APIM hardware is different.
I don't believe the hardware is that different between versions as there is a tool that can re-partition the emmc so that an APIM with 3.0 can be upgraded to 3.2 and beyond.
The main differences seem to be between number of USB ports soldered on (1 or 2), Non Nav (8GB), Nav- most of the world (32GB) and Nav- Europe (64GB).

There are people in the US, Asia, Europe and Russia doing this with their 3.0 APIMs......Nav and non-Nav.
We seem to be the only ones not doing it.....

The hardware is different and the part number is different. Do what ever you want to it but the old part number will stay. If you had access to the full file system you would understand and the part number cannot be changed, this will lead to many with no to little knowledge causing untold amount of messages to me to sort out, hence why it will not be posted here. I have had many disassembled on the bench over the last few years.

Tue Oct 15, 2019 6:58 pm

Corndog wrote: ↑Fri Oct 11, 2019 3:11 pm From the ford website I was on 3.3, and said an upgrade was available. Downloaded it and installed it. Car still reports 3.3. Ford website now reports I'm on 3.3 and is the latest available. Yet turn the wifi on and it starts to download an update jr3t-14g381-as_1564487023000.tar.gz. So slow and don't think it completes.

Your vehicle is trying to download ver 3.0 . Turn auto update off.

Tue Oct 15, 2019 7:01 pm

D Marty wrote: ↑Mon Oct 14, 2019 5:08 pm Hi all, I am at a total loss as to what I am doing wrong. I download both Sync_3.4_Upgrade.zip and http://bit.ly/2ohn7fG to my hard drive. I then copy Sync 3.4 to my USB drive, then copy http://bit.ly/2ohn7fG into the SyncMyRide folder. The Sync 3 unit finds the USB and goes no further. If I extract Sync_3.4_Upgrade.zip onto the USB then copy http://bit.ly/2ohn7fG into the SyncMyRide folder I then get an error message on the Sync 3 unit. Any help is appreciated. My Sync is a Ver 3.3 I have renamed the file as in step 4. Thanks

The error message is?

Try a different USB drive or also try FAT32 format.

Syncmyride should be at the root of the drive, no other folders should be visible.

Logzy · Wed Oct 16, 2019 6:51 pm

Searched but no sucess.
Is there any way to change the preset txt message replies on the Sync 3.3
I came across an article whilst googling about creating a txt file on a usb stick etc but that doesnt work.

trotsky · Thu Oct 17, 2019 3:10 pm

saeb wrote: ↑Tue Oct 15, 2019 6:53 pm The hardware is different and the part number is different. Do what ever you want to it but the old part number will stay. If you had access to the full file system you would understand and the part number cannot be changed

I agree that there are differences and that the part number won't change. The 'upgrade' from 3.0 to >3.2 appears to really only be a workaround.

this will lead to many with no to little knowledge causing untold amount of messages to me to sort out, hence why it will not be posted here.

Totally understand.
I'm only trying it out on spare APIM I have, so I can revert to my original if I brick the spare.

Fri Oct 18, 2019 7:03 am

Logzy wrote: ↑Wed Oct 16, 2019 6:51 pm Searched but no sucess.
Is there any way to change the preset txt message replies on the Sync 3.3
I came across an article whilst googling about creating a txt file on a usb stick etc but that doesnt work.

No mate.

rjorjg · Thu Oct 31, 2019 8:27 am

Thanks for the easy to follow tutorial and links.
Upgraded my '19 XLT with ease last night - now on 3.4.
Had the 'maps error' as well the first time i fired up the vehicle. second time round all was back to normal - just had to give it some more time.

Thanks again.

Bentranger · Wed Nov 06, 2019 8:36 am

Hi All,

Upgraded my 19 WTrak, all went well, had the map issue but after a restart it was fine.

Thanks for your hard work in running a great site.

buzurk · Sun Nov 17, 2019 4:46 pm

Hi,

Will these ever be released on ford site for auto updating/USB or purely from the link posted?

My ranger raptor is on 3.3 now, any issues following your guide for that one too with ANC and all the jazz
Will it overwrite the ANC settings we turned off for my sub?

Also, are there still other colours available in the new UI, i dont think im a fan of that blue

badboybubby · Sun Nov 17, 2019 8:34 pm

Works great , thanks Stewart!

Mon Nov 18, 2019 12:24 pm

buzurk wrote: ↑Sun Nov 17, 2019 4:46 pm Hi,

Will these ever be released on ford site for auto updating/USB or purely from the link posted?

My ranger raptor is on 3.3 now, any issues following your guide for that one too with ANC and all the jazz
Will it overwrite the ANC settings we turned off for my sub?

Also, are there still other colours available in the new UI, i dont think im a fan of that blue

You can have blue or blue, its up to you.

Only Ford can answer whether they will release in full, but being it was designated for the US Explorer MY20 then who know. My20 Everest is showing 3.4 images so I will assume it will be availbe to all over version 3.2.

ANC is a totally different module so it will not affect it.

SMEKINGZ · Tue Nov 19, 2019 4:05 pm

Hi Stewart,

Awesome tutorial, thanks!
Is it possible to downgrade back to 3.3 just in case?
Will the modified themes (Raptor, GT...) still apply?

Thank you!

Sat Nov 23, 2019 10:41 pm

SMEKINGZ wrote: ↑Tue Nov 19, 2019 4:05 pm Hi Stewart,

Awesome tutorial, thanks!
Is it possible to downgrade back to 3.3 just in case?
Will the modified themes (Raptor, GT...) still apply?

Thank you!

Yes, you can downgrade to 3.3. modified themes still exist although GT theme removed.

robbrack · Tue Dec 03, 2019 1:09 pm

saeb wrote: ↑Sun Oct 06, 2019 12:37 pm This upgrade applies to those with a current Sync version of 3.3 ONLY.

Hey Mate,

Just giving this a whirl, and getting error code: LST_ERR05 on PX3 Wildtrak, wont work when formatted exFAT only FAT32

And same error in PX2 XLT FAT32 or exFAT
both Sync 3.3 updated by the USB method a few weeks ago via fords website.

Only thing I can think is trying another memory stick?

Cheers

Sat Dec 07, 2019 1:06 pm

robbrack wrote: ↑Tue Dec 03, 2019 1:09 pm
saeb wrote: ↑Sun Oct 06, 2019 12:37 pm This upgrade applies to those with a current Sync version of 3.3 ONLY.

Hey Mate,

Just giving this a whirl, and getting error code: LST_ERR05 on PX3 Wildtrak, wont work when formatted exFAT only FAT32

And same error in PX2 XLT FAT32 or exFAT
both Sync 3.3 updated by the USB method a few weeks ago via fords website.

Only thing I can think is trying another memory stick?

Cheers

Beacuse you have everything inside another folder on the drive probably. Files should not be extracted into another directory on the drive but at the base level. Large file should be placed inside SyncMyRide, do not extract or change it in anyway or again it will fail.

robbrack · Mon Dec 09, 2019 6:09 am

saeb wrote: ↑Sat Dec 07, 2019 1:06 pm
robbrack wrote: ↑Tue Dec 03, 2019 1:09 pm
saeb wrote: ↑Sun Oct 06, 2019 12:37 pm This upgrade applies to those with a current Sync version of 3.3 ONLY.

Hey Mate,

Just giving this a whirl, and getting error code: LST_ERR05 on PX3 Wildtrak, wont work when formatted exFAT only FAT32

And same error in PX2 XLT FAT32 or exFAT
both Sync 3.3 updated by the USB method a few weeks ago via fords website.

Only thing I can think is trying another memory stick?

Cheers
Beacuse you have everything inside another folder on the drive probably. Files should not be extracted into another directory on the drive but at the base level. Large file should be placed inside SyncMyRide, do not extract or change it in anyway or again it will fail.

Hey mate cheers for reply,

Everything is definately in the Root Folder then the large file was renamed only and placed in the syncmyride folder and still the same error tried around 6 times between the 2 different vehicles.

Ill try again today incase I was having a day. and maybe try to hunt down another USB to try

nluongo · Tue Dec 24, 2019 7:32 am

Hello Saeb,

Having a strange issue after upgrade to 3.4 from 3.3, build 19052. The upgrade went fine no issues with Sirius /XM after I did a signal refresh on radio and the 118 Nav maps are working. All the Sync functions seem to to be ok. What has happened is that the Climate icon on the bottom of the touchscreen disappeared. On 3.3 it sat between the Audio and Phone icons. I had 6 icons in total, now 5 with climate missing. A few moths ago, I attempted the upgrade with the same result. I downgraded back to 3.3 and the Climate icon came back. I just did 3.4 again yesterday using an alternate source for the installer files and same thing happened, no Climate.

My Ranger is a 2019 Lariat and the default for Sync has that icon visible and functional. When I downgraded to 3.3 that was all restored but it's gone again. I had even restored the factory APIM .abt setting before upgrade as insurance. Its just not there and I cannot find any information on this issue anywhere.

Some things I tried:

- removed negative cable from battery for 1/2 hr. Reconnected, no change
- applied the 2 APIM with ForScan that supposedly allow the Climate option to show.... no change. Again, on a Lariat, no change should be needed at all
- I had previously (in 3.3) added the heated seat icons to the touch screen in ForScan and I am able to add them back now but that setting has no effect on the Climate icon.

Any ideas?? Thank you.

Wed Dec 25, 2019 11:49 am

nluongo wrote: ↑Tue Dec 24, 2019 7:32 am Hello Saeb,

Having a strange issue after upgrade to 3.4 from 3.3, build 19052. The upgrade went fine no issues with Sirius /XM after I did a signal refresh on radio and the 118 Nav maps are working. All the Sync functions seem to to be ok. What has happened is that the Climate icon on the bottom of the touchscreen disappeared. On 3.3 it sat between the Audio and Phone icons. I had 6 icons in total, now 5 with climate missing. A few moths ago, I attempted the upgrade with the same result. I downgraded back to 3.3 and the Climate icon came back. I just did 3.4 again yesterday using an alternate source for the installer files and same thing happened, no Climate.

My Ranger is a 2019 Lariat and the default for Sync has that icon visible and functional. When I downgraded to 3.3 that was all restored but it's gone again. I had even restored the factory APIM .abt setting before upgrade as insurance. Its just not there and I cannot find any information on this issue anywhere.

Some things I tried:

- removed negative cable from battery for 1/2 hr. Reconnected, no change
- applied the 2 APIM with ForScan that supposedly allow the Climate option to show.... no change. Again, on a Lariat, no change should be needed at all
- I had previously (in 3.3) added the heated seat icons to the touch screen in ForScan and I am able to add them back now but that setting has no effect on the Climate icon.

Any ideas?? Thank you.

Did you try writing your apim asbuilt again after you upgraded to 3.4? I only read that you did it after the downgrade.

Basically the OS is totally seperate from the firmware and asbuilt so it shoudn't matter. If you still have no joy then I will guess there is a bug in 3.4 for the US Ranger FCIM unless you have seen others with is working.

Keep in mind that all the Sync 3.4 versions are release canditates and not final releases although I have not seen an issue in any others vehicles.

nluongo · Wed Dec 25, 2019 11:12 pm

Hi thanks for replying,

Pretty sure I did reset APIm to factory after upgrade as well during my trouble shooting. Can you confirm the correct process to do this for me? I'm wondering if I'm actually doing it correctly. What I did was:
Launch ForScan and let it scan everything
Select the APIM (AsBuilt) from modules list
Read in the existing APIM (AsBuilt) Module config
Load the VIN.ab file
Write All

Thank you!

Sun Jan 05, 2020 7:53 pm

nluongo wrote: ↑Wed Dec 25, 2019 11:12 pm Hi thanks for replying,

Pretty sure I did reset APIm to factory after upgrade as well during my trouble shooting. Can you confirm the correct process to do this for me? I'm wondering if I'm actually doing it correctly. What I did was:
Launch ForScan and let it scan everything
Select the APIM (AsBuilt) from modules list
Read in the existing APIM (AsBuilt) Module config
Load the VIN.ab file
Write All

Thank you!

That is correct. PM me your saved APIM abt file from Forscan, I will load it on the bench unit and see what it does.

nluongo · Wed Jan 08, 2020 10:35 pm

Hi Stewart,

Thanks a lot for the insight. I PM'd the APIM.abt file to you

Nick

Sun Jan 12, 2020 7:04 pm

nluongo wrote: ↑Wed Jan 08, 2020 10:35 pm Hi Stewart,

Thanks a lot for the insight. I PM'd the APIM.abt file to you

Nick

Yes you have an issue

: IMG_20200112_185943.jpg (120.04 KiB) Viewed 355 times

: IMG_20200112_185943.jpg (120.04 KiB) Viewed 355 times

Sun Jan 12, 2020 7:16 pm

nluongo wrote: ↑Wed Jan 08, 2020 10:35 pm Hi Stewart,

Thanks a lot for the insight. I PM'd the APIM.abt file to you

Nick

This should resolve your issue.

apim_saeb.abt: (495 Bytes) Downloaded 18 times

apim_saeb.abt: (495 Bytes) Downloaded 18 times

nluongo · Tue Jan 14, 2020 11:02 pm

It worked!

You da man! Thank you for doing that. Something in the .abt file had a wonky setting I guess. Ironically, the .abt i sent you was not the exact one that I had been using. So many attempts to resolve the issue led to too many trial & error files saved. I sent you the wrong one, well at least not the one that was running in the truck. But Climate is back and working so again, thank you!

oguncemir · Wed Feb 12, 2020 4:44 am

Hi my car have sync 3.3 but i don't have navigation. Could i use this update to my car too thanks a lot