Upgrade Sync 3 V3.0 to V3.4 instructions
12-29-2019, 03:25 PM
#1401
12-29-2019, 04:15 PM
#1402
Frelling idiot member
I remember reading in one of the F-150 SYNC 3 threads about music (sometimes Gracenote can't ID something and defaults to Tom Petty and the Heartbreakers and I was trying to nail down the filename structure) of someone who has their music on a USB hard drive and it worked fine. But not finding the posts now...
12-29-2019, 04:23 PM
#1403
Frelling idiot member
12-29-2019, 04:27 PM
#1404
Senior Member
Originally Posted by Airborne_Ape
I honestly can't.
I think part of the problem was this is a gen 1 Sync 3 assembly from a 2016 Ford Focus. At least now I can rule out ForScan 2.4.0 and the ELS27 as part of the problem.
ACOOL encouraged me not to give up and that trying random XXXX-14G374-XX .vbf files can bring a Sync 3 APIM's back to life. His wisdom was: " ForScan program load success only means that the module received the data from ForScan; not that it will execute properly. I've always been able to unbrick APIM's but sometimes I've had to use firmware different from the original".
As messed up as that is, it worked for me!
A similar strategy was also mentioned by user 'AmigaSurfer' on the UCDSYS and German Mustang Forums. I copied GB5T-14374-CB from his posts, which I know are incorrect for North America, but they worked and now I'm back in business.
Au{R}oN never pitched in directly per-se, but I found his old posts on this topic that led me in the right direction.
I think part of the problem was this is a gen 1 Sync 3 assembly from a 2016 Ford Focus. At least now I can rule out ForScan 2.4.0 and the ELS27 as part of the problem.
ACOOL encouraged me not to give up and that trying random XXXX-14G374-XX .vbf files can bring a Sync 3 APIM's back to life. His wisdom was: " ForScan program load success only means that the module received the data from ForScan; not that it will execute properly. I've always been able to unbrick APIM's but sometimes I've had to use firmware different from the original".
As messed up as that is, it worked for me!
A similar strategy was also mentioned by user 'AmigaSurfer' on the UCDSYS and German Mustang Forums. I copied GB5T-14374-CB from his posts, which I know are incorrect for North America, but they worked and now I'm back in business.
Au{R}oN never pitched in directly per-se, but I found his old posts on this topic that led me in the right direction.
12-30-2019, 02:14 PM
#1405
US Army Medic
Are folks getting the per channel logos for SiriusXM? I updated my F250 using the instructions listed here and on the SuperDuty forum but no logo just a generic XM. Otherwise I have nothing but praise for the new version.
12-30-2019, 02:15 PM
#1406
Senior Member
Originally Posted by Hawkeye
Are folks getting the per channel logos for SiriusXM? I updated my F250 using the instructions listed here and on the SuperDuty forum but no logo just a generic XM. Otherwise I have nothing but praise for the new version.
12-30-2019, 02:40 PM
#1407
US Army Medic
12-31-2019, 08:55 AM
#1409
No going back. If you don’t want 3.4, switch the 3.4 app file and use the latest 3.3 when reformatting the system.
12-31-2019, 08:55 AM
#1410
Senior Member
