For clarity: I have a NAV APIM with a build date of 01/27/2020. However, it’s attached to a screen with a build date of 04/24/2018.
Can I use the REFORMAT tool to update the APIM to the latest version (I’m currently at 3.4.19274, NA 1.18 maps, Gracenote 1.1.1.1332 (NA-0010)) WITHOUT bricking the APIM? Or is the difference with the APIM and Screen build dates irrelevant and the 2020 build date of the APIM (came out of a Fusion, unknown actual model year/VIN) mean that I can’t use Reformat?
I ask because I’m getting a MEM_ERR01 message when I tried to use the autoinstall and it hung for nearly an hour. And trying to update Maps only is giving me a download error in Syn3 Updater.
Please advise: I have not yet pulled a log, but will do so if/when my latest attempt to build a Maps only flash-drive completes.
Here’s my log tool results: I was trying the full install (without the forced option- MY20 protection enabled), and when that did nothing, I reformatted the same drive and tried installing just Maps. (Vehicle is a 2015 F-150 Lariat SCrew)
You don’t have enough storage left to perform updates. We need to make room first before you can recover the unit. Delete Gracenotes by using this procedure…
Additional storage can be gained by downgrading to 3.3.19052. You can get another 700MB, giving you a total of 2.7GB. To manually downgrade the unit to Sync 3.3.19052, download 4U5T-14G381-AN_1552583626000.TAR.GZ. The file can be found in the APIM IVSU Database.
Follow the instructions below:
Create a USB drive (format as EXFAT) with a SyncMyRide folder.
Copy the utility file downloaded above into the SyncMyRide folder.
In the root of the USB is the autoinstall.lst and DONTINDX.MSA files which you can obtain from any upgrade you previously performed.
You will need to edit the autoinstall.lst file so it looks like the example below:
Insert USB in vehicle and wait for the installation to complete. You should see a message indicating completion.
Remove the USB drive and reboot the APIM.
This will give you 2.7GB total free storage which should be enough to start an update.
Now to the real problem:
The updates were actually working when you stopped them. This is evident by the number of maps you have installed, as there are only 9 map file for 1.19 or 2.20 packages. You have 13 map files installed. But only 1 NAV_Voice file. So now we need to fix this.
With the unit at 3.3.19052 with no Gracenotes, run a stand alone map update for 2.20 NA maps. You can follow this procedure or use the Syn3 Updater…
Here’s the log after removing Gracenotes and downgrading to 3.3.19052. Now it shows that I have 7.4GB free; so using the regular update should function- as long as I leave it the heck alone!
Looks much better. Just use the Autoinstall mode for MY20. (Honestly I am not sure if reformat would brick it or not, but better safe than sorry.)
Looks like the installation is cleaned up, so you should be fine following the tutorial or the Syn3 Updater.
Before you install anything, go to the APIM IVSU screen and see what it reports your map versions
Hold down the FF> key on the steering wheel and FF> key on the panel at the same time for at least 8 seconds. The unit will go into ‘speaker test’, Cancel test. You will be in the test menu. Select 'Bezel Diagnostics" and navigate to the APIM IVSU version screen. Post a pic if possible.
So against your suggested COA, I did a ‘reformat’ install of 3.4.21098. Here’ s Interrogator file following the successful completion of that install (no issues that I can see):
I went into Bezel Diagnostics/APIM/Configuration Status and noted a few things that piqued my interest though:
First, “Extended Play” says it is “Off”, then the Extended Play Time is “30 minutes (FNA)”
“Navigation Application: Navigation Application Turned Off”
SD Slot: “SD Slot Present” (it isn’t any longer: the Sync2 USB/SD/AUX connector was replaced with a dual USB connector intended for Sync3
Non-Metric Units for NAV: Miles/Yards (I thought my As-Built was set to Miles/Feet)
Fuel Type: Diesel (my truck is a gasser)
Surround Sound in Occupancy Mode: Available (though it doesn’t appear to do anything when selected)
Travel Link: Off (It is present in Apps, and functional)
BT Pairing Timeout: 0 (I thought I’d set it to 5 secs on FORSCAN)
GPS Mount Type: Roof Mount (I set this to IP mount)
Drive Type: FWD (I have a 4X4 F-150 Lariat)
Fan Repeater: “blank”
Temperature Repeater: Off
BT Vehicle Nameplate ID: Ford Fiesta (I have Ford F-150 as the actual BT name that I could/did select when pairing)
Front/Rear track inches are all zeroes, the Wheel Base shows as 0.200000 in)
Odd, but outside the scope of this thread.
Attached is the IVSU versions following the Reformat/Installation of 3.4.21098 as well.
That’s ok, glad it worked. Good info. The install looks good, all files are accounted for.
As far as the other things…
Note: DE00 is 7D0-01-xx, and so on. The asbuilt in the Interrogator log does not include parity bits. (last 2)
Extended Play - this is turned off in your asbuilt. If you want it on, change 7D0-01-01 xx## xxxx xxxx from AA to 2A. (6A will set it to 60 min.)
SD Slot Present - Change 7D0-01-02 xx#x xxxx xxxx from 2 to 8. (You have a non-SSV (Start/Stop Vehicle.)
GPS Mount Type: Roof Mount (I set this to IP mount), Should be set to roof mount for F-150, even though the antenna is under the dash.
Drive Type: FWD (I have a 4X4 F-150 Lariat): Your asbuilt is set correctly. 7D0-03-01 xxxx xxx# xxxx is set to 3 (4WD).
Front/Rear track is set correctly in the asbuilt: DE04: 1A681A682FA8
The following are just default values, no issue:
“Navigation Application: Navigation Application Turned Off”
Non-Metric Units for NAV: Miles/Yards (I thought my As-Built was set to Miles/Feet)
Fuel Type: Diesel (my truck is a gasser)
Surround Sound in Occupancy Mode: Available (though it doesn’t appear to do anything when selected)
Travel Link: Off (It is present in Apps, and functional)
BT Pairing Timeout: 0 (I thought I’d set it to 5 secs on FORSCAN)
Fan Repeater: “blank”
Temperature Repeater: Off
BT Vehicle Nameplate ID: Ford Fiesta (I have Ford F-150 as the actual BT name that I could/did select when pairing)
Front/Rear track inches are all zeroes, the Wheel Base shows as 0.200000 in)
Awesome, thanks for the decoding of the AsBuilt (and applying it to what the Sync APIM is reporting)!!
I appreciate the help- and given the screen build-date, I felt comfortable with the reformat/install option since a few different posts (here and on the F150Forums) seemed somewhat confident that MY20 screens were the problematic part of the MY20 equation.
