When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Reformatted and expanded the rar directly to the USB drives, and for USB 1, I get "Error update packages not found..." Now the APIM is stuck in update mode and always asks to install an update USB drive, and regardless of which of the update drives I insert (1, 2, or 3) it gives me that error screen:
So I have left it with USB 1 on that screen with a battery charger on it to see if perhaps this message is in "error" and an actual update is working in the background. In the meantime, I'm redownloading all the files...
And YES, I expanded all rar's so that SyncMyRide directory and the lst file are at the root level of the flash drives.
UPDATE: Redownloaded and unrar'd (using WinRAR) to desktop, then copied "SyncMyRide" and autoinstall.lst to root of freshing erased flash drive, went back to truck (which was still stuck on the orange error screen) and inserted the newly download flash drive but got the same error. I've shut everything down and locked truck, but the screen is still on asking to insert USB stick (with rotating Mustang backgrounds):
A update package not found error means the install.lst file (the text file with the file names in it) is either missing or the file listed in the .lst file is not present on the USB drive. Try unhiding file name extensions on your computer and make sure that the .lst file is not .lst.txt or something like that.
A update package not found error means the install.lst file (the text file with the file names in it) is either missing or the file listed in the .lst file is not present on the USB drive. Try unhiding file name extensions on your computer and make sure that the .lst file is not .lst.txt or something like that.
I'm pretty sure I scrutinized the actual file names to ensure proper file extensions (Windows usually hides the extensions of known application files) but l'll double-check later when I get home from work. In the meantime, I pulled fuse 2 to turn off Sync/Screen as I awoke to a drained battery that wouldn't start the truck. FYI, I tried the hard reset (Volume Power/Next Track) but after restarting it went back to the insert USB screen.
Question: Should the .lst file for USB 1 be named "install.lst" or "autoinstall.lst"? The actual rar and instrux show "autoinstall.lst", though I'm willing to try "install.lst" if nothing else works.
My last resort is to go in with FORSCAN to try a master reset, or at least reprogram the APIM specifically for my truck (hadn't yet done that as it's still programmed for the donor vehicle; Airborne Ape recommended using original AS BUILT before performing the upgrade which is why I didn't reprogram after new installation).
UPDATE: I just remembered I brought my laptop with me to work that I had used to unrar and write to the flash drives and I've confirmed all file names and extensions are correct, and I opened the autoinstall.lst file and confirmed that all listed file names are exactly the same.
LAST UPDATE FOR NOW: I tried every method I could, three different USB drives (two USB 2.0 and a USB 3.0), finally changed the .lst file name to "install.lst" to no avail, then programmed the APIM with FORSCAN with the settings I wanted, and even though Sync/screen will now turn off when I shut down and lock the truck, it still remains stubbornly stuck in update mode. I tried doing a forced reset in FORSCAN, but that appears to be the same as the Power/Volume+Next Track function. As FORSCAN is really only a tool for changing parameter settings (and firmware for the developer alpha/beta version), it can't resolve resetting/unlocking the update mode that this APIM is stuck in; loading a completely fresh or different As-Built will not, in my opinion, fix the mode that it is perpetually looping in.
So I installed my second, slightly older (by two months) Sync 3.0 APIM and programmed the parameters via FORSCAN and all works perfectly: Carplay/iOS Apps, Ambient Lighting, HVAC controls, Heated/Cooled Seat controls, Voice NAV, HD Radio, Sirius, 911 Assist (did not enable "Nav in motion"), Backup Camera, steering wheel controls (including visual volume changes), and full shutdown when the truck is off and locked. I'm now absolutely terrified to perform the 3.2/3.4 Sync upgrade until I can figure out how to "unbrick" the first APIM...
I'm pretty sure I scrutinized the actual file names to ensure proper file extensions (Windows usually hides the extensions of known application files) but l'll double-check later when I get home from work. In the meantime, I pulled fuse 2 to turn off Sync/Screen as I awoke to a drained battery that wouldn't start the truck. FYI, I tried the hard reset (Volume Power/Next Track) but after restarting it went back to the insert USB screen.
Question: Should the .lst file for USB 1 be named "install.lst" or "autoinstall.lst"? The actual rar and instrux show "autoinstall.lst", though I'm willing to try "install.lst" if nothing else works.
My last resort is to go in with FORSCAN to try a master reset, or at least reprogram the APIM specifically for my truck (hadn't yet done that as it's still programmed for the donor vehicle; Airborne Ape recommended using original AS BUILT before performing the upgrade which is why I didn't reprogram after new installation).
UPDATE: I just remembered I brought my laptop with me to work that I had used to unrar and write to the flash drives and I've confirmed all file names and extensions are correct, and I opened the autoinstall.lst file and confirmed that all listed file names are exactly the same.
LAST UPDATE FOR NOW: I tried every method I could, three different USB drives (two USB 2.0 and a USB 3.0), finally changed the .lst file name to "install.lst" to no avail, then programmed the APIM with FORSCAN with the settings I wanted, and even though Sync/screen will now turn off when I shut down and lock the truck, it still remains stubbornly stuck in update mode. I tried doing a forced reset in FORSCAN, but that appears to be the same as the Power/Volume+Next Track function. As FORSCAN is really only a tool for changing parameter settings (and firmware for the developer alpha/beta version), it can't resolve resetting/unlocking the update mode that this APIM is stuck in; loading a completely fresh or different As-Built will not, in my opinion, fix the mode that it is perpetually looping in.
So I installed my second, slightly older (by two months) Sync 3.0 APIM and programmed the parameters via FORSCAN and all works perfectly: Carplay/iOS Apps, Ambient Lighting, HVAC controls, Heated/Cooled Seat controls, Voice NAV, HD Radio, Sirius, 911 Assist (did not enable "Nav in motion"), Backup Camera, steering wheel controls (including visual volume changes), and full shutdown when the truck is off and locked. I'm now absolutely terrified to perform the 3.2/3.4 Sync upgrade until I can figure out how to "unbrick" the first APIM...
I just checked my files and the .lst file for actually installing the files is called reformat.lst - try renaming yours to that and see if it works.
I also grabbed a screenshot of the calibrations on my APIM - this is a late 2018 APIM that has no backlight issues/backlight does not stay on.
I just checked my files and the .lst file for actually installing the files is called reformat.lst - try renaming yours to that and see if it works.
I'm currently reading through that massive 145 page Sync 3.4 upgrade thread (currently on page 40) and those who experienced similar error screens (all with USB 2 as far as I've read and none with USB 1) came down to either a dependent file naming issue or, as one post suggested, ensuring the flash drive name is blank (unnamed) when reformatting as well as to use USB 3 drives to ensure the speediest of upgrades.
So I've got three new 32GB USB 3.1 Samsung flash drives enroute tomorrow and will first try leaving the flash names blank, try naming the .lst file to "reformat.lst" as you suggested, then try shortening the file names to something simple (so long as file names match on the paths as well as in the .lst file, it should be good-to-go). I'll give this all a shot on the weekend since I have to pull the yet dash again to swap in the first APIM as I hate pulling stuff apart at night where it's harder to see and bolts can easily get lost...
I wanted to document how I performed my Sync 3 retrofit as numerous questions went unanswered regarding an OEM satellite roof antenna install. Resources were scarce in describing how to replace the satellite antenna for the 12th Gen F150, and my only visual guidance was a sunroof track assembly R&R video at the 16:06 mark, which gave me a clean interior shot of the antenna attachment and cable. This helped me to familiarize myself what to look for and where:
For those embarking on the same path, my journey begins here
Spoiler
Parts List for My Retrofit:
1x PN JR3T-14G370-ACH, APIM (2018 Mustang)
1x PN HC3T-18B955-SC, Touch Screen Display (2018 F250 King Ranch-no modifying of stock brackets needed)
1x PN HL3Z-10E893-AA, 2015-2017 Satellite Antenna (combines both the Sirius and GPS antennas into one)
1x PN GL3Z-10E928-AA, 2017-2019 GPS Antenna, Wire Splitter, Navigaton (splits combined satellite signals into separate Sirius/ACM connector and GPS/APIM connector)
1x PN FL3Z-19A397-B Cable - Ford, With Satellite Radio, Lower (optional - to extend GPS antenna to reach upper satellite cable)
1x PN HC3Z-19A387-B, Dual USB Interface Module
1x PN GC3Z-19C149-A, Control Module Bezel
1x Power Harness Adapter
1x Roll of Electrical Tape
Tools Used:
Laptop with licensed FORScan application (installed within VirtualBox Windows 10 VM, running on OS X)
ELM327 OBD2 USB Adapter
Cordless Driver with Phillips bit
Headlamp
Scissors
Magnetic Parts Tray
Magnetic Telescoping Pick-up Tool
Ratchet, 1/4" Drive
Extension, 1/4" Drive, 3"
Extension, 1/4" Drive, 1.5" Wobble
Sockets, 1/4" Drive: 7mm, 8mm, 10mm
Hex Driver 6" Adapter, 1/4" Drive
Hex Driver 3" Adapter, 1/4" Drive
Combination Wrench, 10mm (for battery cable)
The Procedure I: I started with the lower splitter cable swap first after reviewing Infotainment's
video, deviating from their procedures by removing both the airbag and glovebox assemblies entirely, and removing the ACM in order to replace the Sirius antenna cable.
II: With everything out, I unmounted the lower satellite cable assembly from the two attachment points; it's assembled with the thick orange FM/AM radio antenna cable:
III: I removed the one factory attachment taped onto the new lower satellite antenna splitter cable before routing it through the center stack opening:
IV: Once I laid the new cable along the path of the old lower satellite antenna cable to ensure everything fits and will reach all connection points, I transferred the foam padding to the new cable, taped the new cable to the original plastic attachment mounts, then remounted the assembly:
V: Following Ford's Service Manual procedures for satellite antenna R&R, I removed the RH A-pillar trim panel using an interior pry tool and 7mm socket; the RH sun visor using a phillips screwdriver and disconnecting its electrical connector; then lowered the front corner of headliner to gain access to the antenna's 10mm retaining bolt. I accessed the bolt through the sunroof opening in the headliner with a short wobble extension, and then disconnected its cable through the front edge of the headliner; I had to get both hands up in there to depress the locking tab with one hand while pulling on the antenna-side connector with the other.
VI: With the old antenna out, I discovered that the new antenna's cable lead was shorter; the old antenna needed all that length of cable lead to reach the upper satellilte cable:
Luckily, I had initially ordered part FL3Z-19A397-B by mistake, thinking it was the cable splitter, but it was simply an extension. I was able to utilize this part to extend the new antenna's cable lead:
Otherwise, the old lower satellite cable can be reutilized to extend the antenna's cable:
VII: I attached the new Sirius antenna connector, along with the other connectors to the ACM, then reinstalled the ACM. I attached the new GPS antenna connector, and the remaining connectors to the APIM, then reinstalled the APIM/Screen assembly.
VIII: I performed a function check, all necessary upgrades and programming via FORScan first, and only after I was satisfied that everything was functioning, reinstalled the trim panels, airbag, and glove box.
For anyone interested, my APIM block 1-4 codes to match my Platinum features and functions are included here, with descriptions
Spoiler
Block 1:
AA21 0103 02AA
A=Sony Processor: Enabled; A=Reverse Camera: enabled with obstacle detection 2=Stereo Extended Play:20 mins 1=CAN Steering Wheel Control Switches
0=Aux Input & Volume **** Display: Audio Only & Rotary Volume 1=Aux Input Installed: AII present & IT key start & Fader enabled 0=Tuner Type Single, & Vehicle Driver Location, LHD, & WOW Seat, Not Present, & TMC, Disabled 3=Climate Front Zone & HD Radio: Dual Zone & HD Radio Available
0=Brand: Ford A=USB2 Enabled & NAV Enabled 8=Transmission Type: Automatic & non-Special Service Vehicle B=Door Keypad Menu Enabled & Ambient Light Enabled
0=Fuel Type: Gasoline 0=Mode Man Icon (Climate) Disabled; Climate Control Type Automatic & Surround Sound Available in Occupancy Mode Available & NAV Repeater Format Motorola format 4=Plug-in/Hybrid Vehicle Not Available & Recirc Icon Enabled & Ford Works Not Available & Front Camera Not Available 0=DM6 off & 9 Bladders & External CD Not Present
0=Rear Climate Type: ??? (Perhaps should be 8) A=Multi-Contour Seats Disabled & Travel Link Enabled B9=Checksum
4=Rear View Camera Split View Not Available & 360 Camera View Not Available & Smart Data Link Connector Absent 0=DAFVC Disabled C6=Checksum
0200 8000 0050
0=List Browser: Nav & Media 2=Outside Air Temp Human Machine Interface: On 0=Park Brake Type: Mechanical 0=Rear Defrost: Enabled; Trailer Backup Assist: Disabled
8=Deep Sleep: On; REVEL Sound System: Not Present; PDC Architecture: 1.3; Telematics Control Unit: Not Present 0=Camera Toggle Button: Hard; Trailer Reverse Guidance: Disabled; CHMSL Camera: Disabled; Aux Camera: Disabled 0=??? 0=???
0=??? 0=CD Alert Popup: Disabled; Cross-Traffic Alert: Disabled; Number of Personalizations: Disabled 50=Checksum
0005 E1
0=WACM: Not Present; Hotspot Capable Modem: Not Present; Rear View Camera Split-View: Not Present; Online Traffic: Not Available 0=Online Traffic Modem & Calm Screen & Enhanced DAB & AA OE Channel Feature: ??? 0=??? 5=???
E1=Checksum
Block 3:
0000 0003 00DE
0=Wheel Tick Frequency: 20ms 0=GPS Mount Type: Roof Mount 00=Vehicle: Non Hybrid Electric Vehicle
11=Bluetooth Audio Profile Index Continued: Ford F150 0=??? 0=Climate: Enable Climate Control Repeater for Dual Climate Control
0E=Bluetooth Pairing Name: F150
FC=Checksum
0004 E1
0=??? 0=??? 0=??? 4=Parking Assistance: Rear/Semi-Auto Parallel Park (EU HMI)
E1=Checksum
None of this could have been possible without the hard work, dedication, and most importantly, the sharing of their experiences by 2018Raptor, Livinitup, jdunk54nl, Airborne_Ape, and the countless others in this thread, other threads, and other forums. Thank you all!
145 pages takes no time to read through when you consider half of it is multiple repetitive quotes and web forum ads. Everything you need is on the first page.
USB - 1 is a format utility for Sync 3. Which clearly worked for you.
USB - 2 is the content you need to load when you are at the Mustang screen.
USB - 3 is an optional update once you are on V3.4
When in doubt, the best Sync 3 troubleshooting tool I recommend is a ball peen hammer, but I would also question which USB hub you installed and the integrity of your flash drives.
Last edited by Airborne_Ape; 01-08-2020 at 08:22 AM.
145 pages takes no time to read through when you consider half of it is multiple repetitive quotes and web forum ads. Everything you need is on the first page.
USB - 1 is a format utility for Sync 3. Which clearly worked for you.
USB - 2 is the content you need to load when you are at the Mustang screen.
USB - 3 is an optional update once you are on V3.4
When in doubt, the best Sync 3 troubleshooting tool I recommend is a ball peen hammer, but I would also question which USB hub you installed and the integrity of your flash drives.
Ah yes, the ball peen... our go-to tool of persuasian on the M1...
I had finished reading all now 150 pages of that thread, and there was much in there from other's experiences that has provided me valuable insight to what may be causing the problem I'm having, which is definitely not contained on the first page or immediate pages. It also forced me to truly understand the syntax and purpose of the .lst file and the update files. Like you said, I discovered that a rotating Mustang background indicates that Sync may now be completely wiped out indicating a successful reformat, but this very specific valuable nugget of a clue was only clearly gleaned from the last few pages (post #1383 on page 139, to be exact).
When I first installed what appeared to be a recognized USB 1 reformat utility, I don't recall seeing any reformat status update screen, nor any message indicating to remove the USB drive to insert the next one (though I must admit I may have quickly stepped out of the truck or looked away for a moment to do something); I just remember coming back to the full orange screen with the message that no packages were found. And although I then proceeded to insert USB 2, USB 3, then back to USB 1, I kept getting that orange screen.
After that, I was then entirely focused on rebuilding USB 1 and using different sticks for USB 1. Those 150 pages, though, gave me troubleshooting tips into USB 2 where others were stuck until they used exFAT format and/or a USB 3.x spec'd stick (my "USB 2" was loaded on a USB 2.0 stick formatted FAT32, which I only inserted once in my whole troubleshooting process). Now that I've received new USB 3.1 sticks, I will format one for "USB 2" in exFAT, while also rolling the newest update contained on USB 3 into USB 2 to go straight to build 19274 (heh, I wouldn't have learned about that "shortcut" unless I fully read that thread!). Hopefully, I will report back a positive conclusion with a "revived" APIM, just as you were eventually successful in reviving that Gen 1 APIM from that FW SNAFU!
BTW, the USB hub is a brand new Ford part. Yea, during my freak-out moments, I also became suspicious of its functionality, but with the second APIM having flawless Carplay functionality thus far (which requires hardwired iPhone connection via the hub), I'm confidant that the hub is not the source of the upgrade problems.
I'm currently reading through that massive 145 page Sync 3.4 upgrade thread (currently on page 40) and those who experienced similar error screens (all with USB 2 as far as I've read and none with USB 1) came down to either a dependent file naming issue or, as one post suggested, ensuring the flash drive name is blank (unnamed) when reformatting as well as to use USB 3 drives to ensure the speediest of upgrades.
So I've got three new 32GB USB 3.1 Samsung flash drives enroute tomorrow and will first try leaving the flash names blank, try naming the .lst file to "reformat.lst" as you suggested, then try shortening the file names to something simple (so long as file names match on the paths as well as in the .lst file, it should be good-to-go). I'll give this all a shot on the weekend since I have to pull the yet dash again to swap in the first APIM as I hate pulling stuff apart at night where it's harder to see and bolts can easily get lost...
When upgrading firmware on other vehicles (e.g Toyota), I always had errors with different/newer USB drives. I had an old drive (~6 years old) in a storage container and used that, ever since then, I kept that one because its been the only reliable drive for upgrades. If you find one that works, keep it.
When upgrading firmware on other vehicles (e.g Toyota), I always had errors with different/newer USB drives. I had an old drive in a storage container and used that, ever since then, I kept that one because its been the only reliable drive for upgrades. If you find one that works, keep it.
I had similar experiences: non-PC devices can be very finicky with which flash drives it will interact with, and I do keep those that worked reserved just for those devices and don't use it for anything else. For one of my media players, it would only work with a specific older Sandisk flash drive, so now that Sandisk is kept and used only with that media player for updates.
01-06-2020, 11:41 AM
