MyFord Touch Navigation Activation Only

Search This thread

seadiel

Senior Member
Dec 30, 2008
51
22
How to active MyfordTouch Navigation

As noted by flsdiver in the previous myfordtouch thread
(http://forum.xda-developers.com/win...rd-touch-hack-enable-features-t3321397/page13)

Modify the APIM as-built data using Forscan (you will need to request an extended license for Forscan)
You will also need a ELM327 device that can do HSCAN/MSCAN.

1) Program APIM using Forscan & ELM327 device. Change the as built data bit with
(7d0-01-02. Byte 1 = 00 No Nav. Byte 1 = 04 with Nav)
Turn key off, turn on, sync black screen for a bit, then performing routine system maintenance.... for about 2 mins.

*Unknown if ACM as built data bit needs to be changed yet.
2) Program ACM as build with bit mentioned in this thread. Not sure needed/what it does but I did it anyway.

3) New method seems to be either getting a license file from vincentka post 535 (http://forum.xda-developers.com/showpost.php?p=68993515&postcount=535)
OR
Using the PNG file described here https://www.drive2.ru/l/10018006/ posted by rmcgry
http://forum.xda-developers.com/showpost.php?p=69046248&postcount=545

Download license (BT4T-14F500-BE) from URL attached in the excel document. You will need to replace “YAABBCCD” in the URL section and provide your vehicle’s ESN number otherwise it won’t work. This appears to be case sensitive so make sure it is all uppercase letters.
You can get the ESN number in the settings section on the myfordtouchunit. You do not need to change anything else in the URL.

*To do non-north america and non-latest software you will need all the proper field values for your vehicle from the as build and from the current software installed on the vehicle.
All credit goes to flsdiver for the URL/Excel doc/steps needed.
*Ford could change this URL and this would no longer work!


4) *This step may not be needed depending on if you are using the PNG file method. Create the USB device and edit the autoinstall.lst file to only install the BT4T-14F500-BE file.
5) Stick in A7 nav SD Card.
6) Enjoy the trip!
 
Last edited:

flsdiver

Member
Mar 29, 2016
49
35
For the long winded explanation, and those that what to put the pieces together...

Background:
APIM = Accessory Protocol Interface Module it is what holds the software that runs MFT.
ACM = Audio Control Module (Radio)
IPC = Instrument Panel Control Module
ESN = APIM Serial Number.
The Module Id of the APIM is 7D0 on the can-bus.
The APIM must be programmed with as build data to turn on NAV, more on that later.
I programmed the APIM bits via obdII 1st then did the nav/license install, not sure order matters or not.
Optionally the ACM bit can be set (this is very vehicle specific).
The NAV software license must be installed on the APIM via a normal USB update process.
The NAV software license must be digitally signed by f0rd for the serial number (ESN) that is on your APIM.
See other discussions for why one license file does not work in all vehicles (or you wouldn't be reading this thread, everyone would have NAV)
When done correctly you will see the license show up on the MFT license screen.

Sources of data regarding your APIM:

1) Get the As Build data for your vehicle.
this contains some of the values needed to build the software unlocker url and contains the 7d0
motorcraftservice.com/AsBuilt put in VIN
download file and save as xml (it's easier to read than .ab with simple browser)
also, i save this page as html file (ctrls) so that i can easily reference the modules/addresses and compare data for apim/acm.

this is sample of 7d0 apim as build data that determines what is or is not installed on your vehicle
Code:
	APIM
		7D0-01-01 	2AAA 	0006 	03B6 	 
	 	7D0-01-02 	0409 	0604 	8071 	 
	 	7D0-02-01 	5553 	0103 	8006 	 
 		7D0-02-02 	0200 	0000 	00DD 	 
	 	7D0-02-03 	0000 	DC 	 	 
 		7D0-03-01 	2055 	5203 	00A5 	 
	 	7D0-04-01 	0103 	0201 	00E3 	 
 		7D0-04-02 	0101 	DF 	 	 
	Instrument Panel Control Module
	IPC 	720-01-01 	2C0B 	1064 	6034 	
	IPC 	720-01-02 	2013 	106D 	 	
	IPC 	720-02-01 	4DC0 	3C31 	3CE0 	
	IPC 	720-02-02 	1000 	A9E4 	 	
	IPC 	720-03-01 	2805 	5400 	00AC 	
	IPC 	720-03-02 	C848 	013D 	 	
	IPC 	720-04-01 	C441 	0000 	0031 	
	IPC 	720-04-02 	5553 	00D5 	 	
	IPC 	720-05-01 	0000 	0000 	002D 	
	IPC 	720-05-02 	0000 	113F 	 	
	IPC 	720-06-01 	0000 	0000 	002E 	
	IPC 	720-06-02 	0000 	002F 	 	
	IPC 	720-07-01 	8401 	88A0 	603C 	
	IPC 	720-07-02 	0000 	0030 	 	
	Audio Control Module
	ACM 	727-01-01 	1801 	1808 	0069 	
	ACM 	727-01-02 	0600 	37 	 	
	ACM 	727-02-01 	5B8C 	 	 	
	ACM 	727-03-01 	1446 	 	 	
	ACM 	727-04-01 	0001 	0155 	53DD
This is an excerpt from the as build file that contains the software values for the apim, you will need this to build proper software download url.
Code:
	<NODEID>
	7D0
	<F110>DS-ET4T-14D212-AB</F110>
	<F111>ES7T-14F130-BA</F111>
	<F113>ES7T-14D212-DA</F113>
	<F188>EM5T-14D205-AD</F188>
	</NODEID>
2) Software Installation Report
this comes from the usb stick that you used to do your last update.
or you may put the SYNCStatusChecker.zip on a usb stick, put it in your car, turn on key, it will install the report on your usb stick.
look in the syncmyride folder for xml file that is in the format Sync_<esn>_<vin>.xml
this file contains all the information you should need to do the software download!
below is an excerpt from this software report.
<VIN> <ESN> <HardwareFordPartNumber> <ImageFPN> <VMCUFordPartNumber> <FPN> (2nd application is for nav in this case)
Code:
  <Vehicle>
	<VIN>1FTEW1EG2FFA47262</VIN>
		<DisplayType>0A</DisplayType>
	<ModuleHW>
		<ESN>YAABBCCD</ESN>
		<MACAddress>001122334455</MACAddress>
		<WIFIMACAddress>0011223344</WIFIMACAddress>
	<HardwareFordPartNumber>ES7T-14F130-BA</HardwareFordPartNumber>
	<CCPU>
		<ImageFPN>EA5T-14D544-AD</ImageFPN>
		<Version>6.0.15065.0.0</Version>
		<OEMVersion>3.08.15128.EA.10_PRODUCT </OEMVersion>
   <Applications>
	<Application>
		<GUID>{00000000-0000-0000-0000-000000000000}</GUID>
		<FPN>EA5T-14F496-AD</FPN>
		<Version>0.0.0.0</Version>
		<Name>EA5T-14F496-AD</Name>
	</Application>
	<Application>
		<GUID>{00000000-0000-0000-0000-000000000000}</GUID>
		<FPN>EA5T-14F657-AD</FPN>
		<Version>0.0.0.0</Version>
		<Name>EA5T-14F657-AD</Name>
	</Application>
   ...
   <VMCU>
	<VMCUFordPartNumber>EM5T-14D205-AD</VMCUFordPartNumber>
	<Version>Vector_VMCU_02.04.31</Version>
   </VMCU>
3) Alternatively you can get most of this same information from the diagnostic screen.
Radio off, key on, eject button hold, still holding eject hold the right (next ) button.
Cancel tone test
Goto APIM Diagnostic/Part Numbers
Find on screen -
APIM Serial Number: <ESN>
H/W Part Number: <HardwareFordPartNumber>
CCPU S/W Part Number: <ImageFPN>
VMCU S/W Part Number : <VMCUFordPartNumber>
This would leave you to guess your particular NAV pack. <FPN>, usually EA5T-14F657-AD for north america.

You can use all of this data above, from your vehicle, map it to line 7 of excel, it will generate the url on line 8 for you.
Download the software, confirm that you have BT4T-14D546-EE in the zip, this is the NAV software license.
Unzip to USB stick, let this install run just like any normal sync update.
After update you should be able to go to Settings/System/Install Applications/View Software License and see the nav license on your MFT.


APIM Programming
You will need to download Forscan software.
You will need a good OBDII Forscan compatible OBDII interface.
Old Real Elm327s with MSCAN/HSCAN switch, or other good interfaces, not the cheap $5 elms on ebay 99.9% will not work.
Consult Forscan site for more on compatible interfaces.
Connect Interface and Forscan, let it scan modules.
Configuration Programming select APIM as build.

The important thing to set is one bit at 7D0-01-02 00 needs to be 7D0-01-02 04 in all cases we have seen so far.
7D0-01-02 0009 0604 806D No Nav
7D0-01-02 0409 0604 8071 Nav
The checksum (last byte), is the sum of all other bytes on that line
Checksum for this can be simple, just add 04 hex, so 6D + 04 = 71. See post #7 for good explaination on checksum.
Your numbers will be different for your vehicle.
The 1st byte 00/04 and the last checksum are all that need be changed.
Forscan may or may not calculate this checksum dynamically, i don't remember.
After doing this the MFT will reboot.
At which time, you should have nav.

You will need an SD map card (A7 is current) in the vehicle to use NAV. Go buy one, so that Here maps gets paid.

Please do not post the url in this thread. Build and download your own.

Attached a simplified excel with clearer header with entries attached.


Edit:
Climate in lower right quadrant can also be enabled. Post #69
 

Attachments

  • syncsoftwaredlurl.zip
    7.5 KB · Views: 4,830
Last edited:

adyboss

Member
Jan 5, 2010
34
0
Bucharest
You said:
4) Create the USB device and edit the autoinstall.lst file to only install the BT4T-14F500-BE file.
But in the "original" flsdiver instructions we had:
3) Download license (BT4T-14F500-BE) and nav software pack (EA5T-14F657-AD hint! in my case)..
How it is? It is not needed the "nav software pack"?
 

seadiel

Senior Member
Dec 30, 2008
51
22
You said:
4) Create the USB device and edit the autoinstall.lst file to only install the BT4T-14F500-BE file.
But in the "original" flsdiver instructions we had:
3) Download license (BT4T-14F500-BE) and nav software pack (EA5T-14F657-AD hint! in my case)..
How it is? It is not needed the "nav software pack"?

All the myfordtouch update files already have NAV included so it should already have NAV installed you just need to change the as built data and run the license activation.
 

adyboss

Member
Jan 5, 2010
34
0
Bucharest
All the myfordtouch update files already have NAV included so it should already have NAV installed you just need to change the as built data and run the license activation.

And what if my system is not updated to the latest version (having 3.07 instead of 3.08)? And of course don't want to update it...
Can be activated?
 

seadiel

Senior Member
Dec 30, 2008
51
22
And what if my system is not updated to the latest version (having 3.07 instead of 3.08)? And of course don't want to update it...
Can be activated?

Yea the update prior to 3.08 you should be fine. Just note the SD card's below per version. I am thinking older versions than 2012 may have problems unlocking.

Build Version Released Date:

12023 3.0.2 SYNCGen2 Released 05 Mar 2012
unknown 3.1.3 SYNCGen2 Released September 2012 (BEV vehicles only)
12156 3.2.2 SYNCGen2 Released September 2012 (Limited release)
12285 3.5.1 SYNCGen2_4.29.12285_PRODUCT Released December 2012 + GPS Update (A4) new SD card
13171 3.6.2 SYNCGen2_4.30.13171_PRODUCT Released August 2013 (Can use A3 & A4 SD cards)
14122 3.7.11 SYNCGen2_4.32.14122_PRODUCT Released September 2014 (Can use A5 SD card, A3 and A4 untested)
15128 3.8 SYNCGen2_3.08.15128.EA.10_PRODUCT Released October 02 2015 (Compatible with A3, A4, A5, A6 and A7 SD cards only.)
 

sheltonfilms

Senior Member
Mar 29, 2016
68
12
The important thing to set is one bit at 7D0-01-02 00 needs to be 7D0-01-02 04 in all cases we have seen so far.
7D0-01-02 0009 0604 806D No Nav
7D0-01-02 0409 0604 8071 Nav
The checksum (last byte), is the sum of all other bytes on that line, just add 04 hex, so 6D + 04 = 71. - i need to confirm this statement.
Your numbers will be different for your vehicle. the 1st byte 00/04 and the last checksum are all that need be changed.
Forscan may or may not calculate this checksum dynamically i don't remember.

Total checksum is computed as so for the NAV line: 07 + D0 + 01 +02 + 00 + 09 + 06 + 04 + 80 = 16D (only use last two digits)

But yeah adding 4 in hex should work fine as a quick shortcut.

Forscan says it does calculate the checksum automatically.
 

wangks18

New member
Apr 29, 2016
1
0
Success on my 2015 escape ,I‘m In China
For escape ,I compaired the nav/nonnavi
ACM 727-04-01 has no difference
I changed 7D0-01-02 2th hex to 4 to enable navigation
and 7D0-02-02 4th hex to 8 to enable the "speed point warn "
Thanks
 
Last edited:

COMpulse

Senior Member
Feb 21, 2011
320
97
Detroit
www.CompulsiveCode.com
I can't take any credit for it. Someone here was kind enough to point me in the right direction to find a crack.
I assume XDA frowns on any discussions involving cracking or circumventing paying for commercial software.
With that said, if you want to PM me, I can go into detail.
 

TScott69

Member
Apr 5, 2016
31
2
I can't take any credit for it. Someone here was kind enough to point me in the right direction to find a crack.
I assume XDA frowns on any discussions involving cracking or circumventing paying for commercial software.
With that said, if you want to PM me, I can go into detail.

Sent you a PM
 

jethoss

Member
May 1, 2016
5
0
Got the license file successfully installed in a '15 Taurus! I set the bit in the APIM as noted and loaded the license file without issue after finally getting the URL right. I had to do a regular SYNC update to get the software current enough to work with the URL, so that was a stumbling block for a while. The screen still says "Information" instead of "Navigation" but I suspect there's something I've overlooked somewhere. In any case, the hard part is done, and many thanks to those who did the heavy lifting.
 

lucasb8888

Member
Apr 4, 2016
26
5
Detroit
Got the license file successfully installed in a '15 Taurus! I set the bit in the APIM as noted and loaded the license file without issue after finally getting the URL right. I had to do a regular SYNC update to get the software current enough to work with the URL, so that was a stumbling block for a while. The screen still says "Information" instead of "Navigation" but I suspect there's something I've overlooked somewhere. In any case, the hard part is done, and many thanks to those who did the heavy lifting.
After you change the APIM data it should say insert nav sd card. Then the info is moved to next to the home button
 
  • Angry
Reactions: Rijaj brian

jethoss

Member
May 1, 2016
5
0
After you change the APIM data it should say insert nav sd card. Then the info is moved to next to the home button

My error - that's what I was looking for, but it's still stuck on "Information." The license file is there, now I just need to check the APIM. I might try to set the bit back to 00 again, then reset it to 04 and see if that helps.

Also of note - Forscan does NOT compute the checksum automatically, at least on my installation.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Some of the information in this post may be sprinkled throughout this thread, but I wanted to figure out how to create the SdCard.key file and how it worked.

    It turns out, there is no magic, and can be done without using dodgy software downloaded from the internet (more on this later).

    The main take-away is that the SdCard.key file is just the SD card Product Serial Number in decimal encrypted with an RSA public key.

    The hurdles to make this happen are #1 obtaining the SD card PSN, and #2 getting the RSA key.

    Hurdle #1:
    The PSN is read out of the SD Card Card Identification (CID) register. To read this register requires an SD Card reader directly connected to the computer as opposed to via the USB bus. I had originally tried my modern HP laptop, but even though it was an internal SD Card slot, it was connected via the USB bus. Same with my Dad's new Dell laptop. I have an old Dell Inspiron 1420 that has an SD card slot, and it was connected directly. It's then possible with Linux to read that register with the command cat /sys/block/mmcblk0/device/cid (if that doesn't work, search the /sys file tree for cid to find it).

    Thanks to Gough Lui [1], using his page, you can quickly grab the PSN.
    The CID register has the following format:
    0x1234567890ABCDEF1234567890ABCDEF
    where
    Code:
    0x 12 3456 7890ABCDEF 12 34567890 ABCD EF
       |    |     |        |      |    |    |
       |  OEM ID  |     Revision  |    |   CRC
       |   Product Name ASCII     | Manufacture Date
     Manufacturer ID     Product Serial Number

    In this case, the PSN would be 0x34567890 and in decimal is 878082192.

    Hurdle #2:
    The public key to encrypt the PSN is all that's needed. Finding it was a bit of a challenge, but both the FordActivator.apk and GenFordKey.exe windows app have the necessary key embedded into them. It's possible to find download links for both of these, but it's usually from dodgy download sites. Both apps do make the process "easy", but FordActivator requires an Android 5 or 6 device with an SD card slot, and a micro SD card. The windows app that I got, the UI was all question marks (probably a missing language pack on my Windows install), but luckily it's super simple with just a text field, 3 radio buttons and a button. To use it, just put the in the PSN in hex without 0x, select the top radio button, and click the button.

    I just happened upon the key from the GenFordKey windows application because the executable was on my NAS, and my old Windows laptop didn't trust my SMB share. When running the UI, Windows asked if I trusted the location, I clicked yes to get the UI.
    Capture.PNG

    Then after putting in the serial number (in hex but without the 0x), and clicking the button, it again asked if I trusted the location, this time to run the included openssl.exe. However, because it paused at this point, it had written out two temporary files (to the directory where GenFordKey.exe was located), in.txt and key.txt which was the RSA private key in PEM format. With this key, it's possible to both encrypt and decrypt the SdCard.key file.

    I was also curious about the FordActivator.apk, and I used http://www.javadecompilers.com to decompile the APK. In sources/com/n0b0dy/fordactivator/Keygen.java is the modulus and exponent for the public key.
    Capture1.PNG


    Using oliv's excellent answer at [2], we can create an ASN1 definition file, which we can give to openssl to create the public key PEM file for use with openssl.

    I could just attach the public key file here, but I'll leave it up to someone else to post the key directly.

    Once you have both the PSN in decimal and a key file (either the public or private key), you can just run openssl to create SdCard.key. Using the example from above, here's a linux command line to create the SdCard.key file:
    If you have the public key:
    echo "878082192" > openssl rsautl -encrypt -inkey publickey.pem -pubin -out SdCard.key

    And with the private key:
    echo "878082192" > openssl rsautl -encrypt -inkey privatekey.pem -out SdCard.key

    If you have the private key, you can verify the results with:
    openssl rsautl -decrypt -inkey privatekey.pem -in SdCard.key -out out.txt

    And you should see the PSN in decimial in out.txt

    [1]: https://goughlui.com/2014/01/02/project-read-collect-decode-sd-card-cid-register-data/
    [2]: https://stackoverflow.com/a/36448243/3362479
  • 14
    people ask what I need to activate the navigation?
    1. update Sync2 system to version 3.8.15128
    US ONLY : HERE
    For EUROPE : HERE
    and others language pack
    Language Pack 1 - German, English (British), Russian, Turkish:
    http://ivsu.binaries.ford.com/swparts/Gen2v38build15128updatepackageEULangpack1Rev4.zip

    Language Pack 2 - German, English (British), Polish, Russian:
    http://ivsu.binaries.ford.com/swparts/Gen2v38build15128updatepackageEULangpack2Rev4.zip

    Language Pack 3 - German, English (British), French, Italian:
    http://ivsu.binaries.ford.com/swpart...gpack3Rev4.zip

    Language Pack 4 - German, English (British), French, Swedish:
    http://ivsu.binaries.ford.com/swpart...gpack4Rev4.zip

    Language Pack 5 - English (British), Spanish, French, Portuguese:
    http://ivsu.binaries.ford.com/swpart...gpack5Rev4.zip

    Language Pack 6 - German, English (British), French, Dutch:
    http://ivsu.binaries.ford.com/swpart...gpack6Rev4.zip

    2. with Forscan Extended License you have to change APIM Navigation configuration (7d0-01-02. Byte 1 = 00 No Nav. Byte 1 = 04 with Nav);
    3. install license (send me PM)
    4. to work you need to have the map A (x) for the United States and F (x) for Europe
    13
    How to active MyfordTouch Navigation

    As noted by flsdiver in the previous myfordtouch thread
    (http://forum.xda-developers.com/win...rd-touch-hack-enable-features-t3321397/page13)

    Modify the APIM as-built data using Forscan (you will need to request an extended license for Forscan)
    You will also need a ELM327 device that can do HSCAN/MSCAN.

    1) Program APIM using Forscan & ELM327 device. Change the as built data bit with
    (7d0-01-02. Byte 1 = 00 No Nav. Byte 1 = 04 with Nav)
    Turn key off, turn on, sync black screen for a bit, then performing routine system maintenance.... for about 2 mins.

    *Unknown if ACM as built data bit needs to be changed yet.
    2) Program ACM as build with bit mentioned in this thread. Not sure needed/what it does but I did it anyway.

    3) New method seems to be either getting a license file from vincentka post 535 (http://forum.xda-developers.com/showpost.php?p=68993515&postcount=535)
    OR
    Using the PNG file described here https://www.drive2.ru/l/10018006/ posted by rmcgry
    http://forum.xda-developers.com/showpost.php?p=69046248&postcount=545

    Download license (BT4T-14F500-BE) from URL attached in the excel document. You will need to replace “YAABBCCD” in the URL section and provide your vehicle’s ESN number otherwise it won’t work. This appears to be case sensitive so make sure it is all uppercase letters.
    You can get the ESN number in the settings section on the myfordtouchunit. You do not need to change anything else in the URL.

    *To do non-north america and non-latest software you will need all the proper field values for your vehicle from the as build and from the current software installed on the vehicle.
    All credit goes to flsdiver for the URL/Excel doc/steps needed.
    *Ford could change this URL and this would no longer work!


    4) *This step may not be needed depending on if you are using the PNG file method. Create the USB device and edit the autoinstall.lst file to only install the BT4T-14F500-BE file.
    5) Stick in A7 nav SD Card.
    6) Enjoy the trip!
    9
    For the long winded explanation, and those that what to put the pieces together...

    Background:
    APIM = Accessory Protocol Interface Module it is what holds the software that runs MFT.
    ACM = Audio Control Module (Radio)
    IPC = Instrument Panel Control Module
    ESN = APIM Serial Number.
    The Module Id of the APIM is 7D0 on the can-bus.
    The APIM must be programmed with as build data to turn on NAV, more on that later.
    I programmed the APIM bits via obdII 1st then did the nav/license install, not sure order matters or not.
    Optionally the ACM bit can be set (this is very vehicle specific).
    The NAV software license must be installed on the APIM via a normal USB update process.
    The NAV software license must be digitally signed by f0rd for the serial number (ESN) that is on your APIM.
    See other discussions for why one license file does not work in all vehicles (or you wouldn't be reading this thread, everyone would have NAV)
    When done correctly you will see the license show up on the MFT license screen.

    Sources of data regarding your APIM:

    1) Get the As Build data for your vehicle.
    this contains some of the values needed to build the software unlocker url and contains the 7d0
    motorcraftservice.com/AsBuilt put in VIN
    download file and save as xml (it's easier to read than .ab with simple browser)
    also, i save this page as html file (ctrls) so that i can easily reference the modules/addresses and compare data for apim/acm.

    this is sample of 7d0 apim as build data that determines what is or is not installed on your vehicle
    Code:
    	APIM
    		7D0-01-01 	2AAA 	0006 	03B6 	 
    	 	7D0-01-02 	0409 	0604 	8071 	 
    	 	7D0-02-01 	5553 	0103 	8006 	 
     		7D0-02-02 	0200 	0000 	00DD 	 
    	 	7D0-02-03 	0000 	DC 	 	 
     		7D0-03-01 	2055 	5203 	00A5 	 
    	 	7D0-04-01 	0103 	0201 	00E3 	 
     		7D0-04-02 	0101 	DF 	 	 
    	Instrument Panel Control Module
    	IPC 	720-01-01 	2C0B 	1064 	6034 	
    	IPC 	720-01-02 	2013 	106D 	 	
    	IPC 	720-02-01 	4DC0 	3C31 	3CE0 	
    	IPC 	720-02-02 	1000 	A9E4 	 	
    	IPC 	720-03-01 	2805 	5400 	00AC 	
    	IPC 	720-03-02 	C848 	013D 	 	
    	IPC 	720-04-01 	C441 	0000 	0031 	
    	IPC 	720-04-02 	5553 	00D5 	 	
    	IPC 	720-05-01 	0000 	0000 	002D 	
    	IPC 	720-05-02 	0000 	113F 	 	
    	IPC 	720-06-01 	0000 	0000 	002E 	
    	IPC 	720-06-02 	0000 	002F 	 	
    	IPC 	720-07-01 	8401 	88A0 	603C 	
    	IPC 	720-07-02 	0000 	0030 	 	
    	Audio Control Module
    	ACM 	727-01-01 	1801 	1808 	0069 	
    	ACM 	727-01-02 	0600 	37 	 	
    	ACM 	727-02-01 	5B8C 	 	 	
    	ACM 	727-03-01 	1446 	 	 	
    	ACM 	727-04-01 	0001 	0155 	53DD
    This is an excerpt from the as build file that contains the software values for the apim, you will need this to build proper software download url.
    Code:
    	<NODEID>
    	7D0
    	<F110>DS-ET4T-14D212-AB</F110>
    	<F111>ES7T-14F130-BA</F111>
    	<F113>ES7T-14D212-DA</F113>
    	<F188>EM5T-14D205-AD</F188>
    	</NODEID>
    2) Software Installation Report
    this comes from the usb stick that you used to do your last update.
    or you may put the SYNCStatusChecker.zip on a usb stick, put it in your car, turn on key, it will install the report on your usb stick.
    look in the syncmyride folder for xml file that is in the format Sync_<esn>_<vin>.xml
    this file contains all the information you should need to do the software download!
    below is an excerpt from this software report.
    <VIN> <ESN> <HardwareFordPartNumber> <ImageFPN> <VMCUFordPartNumber> <FPN> (2nd application is for nav in this case)
    Code:
      <Vehicle>
    	<VIN>1FTEW1EG2FFA47262</VIN>
    		<DisplayType>0A</DisplayType>
    	<ModuleHW>
    		<ESN>YAABBCCD</ESN>
    		<MACAddress>001122334455</MACAddress>
    		<WIFIMACAddress>0011223344</WIFIMACAddress>
    	<HardwareFordPartNumber>ES7T-14F130-BA</HardwareFordPartNumber>
    	<CCPU>
    		<ImageFPN>EA5T-14D544-AD</ImageFPN>
    		<Version>6.0.15065.0.0</Version>
    		<OEMVersion>3.08.15128.EA.10_PRODUCT </OEMVersion>
       <Applications>
    	<Application>
    		<GUID>{00000000-0000-0000-0000-000000000000}</GUID>
    		<FPN>EA5T-14F496-AD</FPN>
    		<Version>0.0.0.0</Version>
    		<Name>EA5T-14F496-AD</Name>
    	</Application>
    	<Application>
    		<GUID>{00000000-0000-0000-0000-000000000000}</GUID>
    		<FPN>EA5T-14F657-AD</FPN>
    		<Version>0.0.0.0</Version>
    		<Name>EA5T-14F657-AD</Name>
    	</Application>
       ...
       <VMCU>
    	<VMCUFordPartNumber>EM5T-14D205-AD</VMCUFordPartNumber>
    	<Version>Vector_VMCU_02.04.31</Version>
       </VMCU>
    3) Alternatively you can get most of this same information from the diagnostic screen.
    Radio off, key on, eject button hold, still holding eject hold the right (next ) button.
    Cancel tone test
    Goto APIM Diagnostic/Part Numbers
    Find on screen -
    APIM Serial Number: <ESN>
    H/W Part Number: <HardwareFordPartNumber>
    CCPU S/W Part Number: <ImageFPN>
    VMCU S/W Part Number : <VMCUFordPartNumber>
    This would leave you to guess your particular NAV pack. <FPN>, usually EA5T-14F657-AD for north america.

    You can use all of this data above, from your vehicle, map it to line 7 of excel, it will generate the url on line 8 for you.
    Download the software, confirm that you have BT4T-14D546-EE in the zip, this is the NAV software license.
    Unzip to USB stick, let this install run just like any normal sync update.
    After update you should be able to go to Settings/System/Install Applications/View Software License and see the nav license on your MFT.


    APIM Programming
    You will need to download Forscan software.
    You will need a good OBDII Forscan compatible OBDII interface.
    Old Real Elm327s with MSCAN/HSCAN switch, or other good interfaces, not the cheap $5 elms on ebay 99.9% will not work.
    Consult Forscan site for more on compatible interfaces.
    Connect Interface and Forscan, let it scan modules.
    Configuration Programming select APIM as build.

    The important thing to set is one bit at 7D0-01-02 00 needs to be 7D0-01-02 04 in all cases we have seen so far.
    7D0-01-02 0009 0604 806D No Nav
    7D0-01-02 0409 0604 8071 Nav
    The checksum (last byte), is the sum of all other bytes on that line
    Checksum for this can be simple, just add 04 hex, so 6D + 04 = 71. See post #7 for good explaination on checksum.
    Your numbers will be different for your vehicle.
    The 1st byte 00/04 and the last checksum are all that need be changed.
    Forscan may or may not calculate this checksum dynamically, i don't remember.
    After doing this the MFT will reboot.
    At which time, you should have nav.

    You will need an SD map card (A7 is current) in the vehicle to use NAV. Go buy one, so that Here maps gets paid.

    Please do not post the url in this thread. Build and download your own.

    Attached a simplified excel with clearer header with entries attached.


    Edit:
    Climate in lower right quadrant can also be enabled. Post #69
    9
    Vinc, your 3.08 Navigation Update file is old and 3.10 is incomplete. Use the following AF / AG Navigation Update as future reference:

    https://mega.nz/#!xtQBCRhY!g4x3KVBFncz0MGraP0i_dNP6uS-M3s4RhTv85JsjozA

    These versions will not require a MFT master reset after NaviPatch.png :)

    Plus, here's the full 3.10.16180 European revised update (EU-Lang pack3 EN-GB_DE-DE_FR-FR_IT-IT) as I got tired of all the trouble versions floating around:

    https://mega.nz/#!M1Jh1LhD!KnpCrzB-xY1FHw2bdvmg0KFNGzwzUm9aGC8ngu0_m4A

    Possible 3.10 EU language packs are:
    1. EULangpack1 DE-DE_EN-GB_RU-RU_TR-TR http://ivsu.binaries.ford.com/swparts/EA5T-14F497-BF_64703.ZIP
    2. EULangpack2 DE-DE_EN-GB_PL-PL_RU-RU http://ivsu.binaries.ford.com/swparts/EA5T-14F497-CF_64704.ZIP
    3. EULangpack3 DE-DE_EN-GB_FR-FR_IT-IT http://ivsu.binaries.ford.com/swparts/EA5T-14F497-DF_64705.ZIP
    4. EULangpack4 DE-DE_EN-GB_FR-FR_SV-SE http://ivsu.binaries.ford.com/swparts/EA5T-14F497-EF_64706.ZIP
    5. EULangpack5 EN-GB_ES-ES_FR-FR_PT-PT http://ivsu.binaries.ford.com/swparts/EA5T-14F497-FF_64707.ZIP
    6. EULangpack6 DE-DE_EN-GB_FR-FR_NL-NL http://ivsu.binaries.ford.com/swparts/EA5T-14F497-GF_64708.ZIP
    by replacing the EA5T-14F497-xF file inside SyncMyRide folder and inside autoinstall.lst

    And here is the full 3.10.16180 US revised update (NA-Lang pack EN-US_FR-CA_ES-US for Ford/Lincoln, VHR discontinued and removed)

    https://mega.nz/#!Jk4hzSZD!NNOw8g9BkciF4GREYnzCL3i5gokxCemgAzykCi47NMw

    Possible 3.10 US language packs are:
    1. South America EN-US_PT-US_ES-US http://ivsu.binaries.ford.com/swparts/EA5T-14F497-HE_64709.ZIP
    2. Australia EN-AU http://ivsu.binaries.ford.com/swparts/EA5T-14F497-LF_64711.ZIP
    by replacing the EA5T-14F497-xE file inside SyncMyRide folder and inside autoinstall.lst

    Ignore the final 3.8 confirmation prompt, it's 3.10. In case anyone wants a different splashscreen, it can be installed easily by modifying autoinstall.lst in the following installation:

    https://mega.nz/#!V44iWKBC!Gflsjkh4gVsz5vFIlPL8_g7r1JmrqSx6Nxp-H3k3tg0

    EA5T-14F496-MA - Custom Animation application (FOR FORD F-150 RAPTOR).
    EA5T-14F496-PA - Custom Animation application (FOR MUSTANG).
    EA5T-14F496-RA - Custom Animation application (FOR LINCOLN BLACK LABEL).
    EA5T-14F496-SA - Custom Animation application (FOR LINCOLN PRESIDENTIAL).
    EA5T-14F496-TB - Custom Animation application (FOR FORD MONDEO VIGNALE).
    EA5T-14F496-UA - Custom animation application (FOR EU MARKET FORD VEHICLES).
    8
    Sync2 USB update package to 3.10 (16180) version for North America.
    Standard Ford splash screen (not Lincoln, Vignale or Mustang...).
    Checked. Seems to work.
    Made on the original packages, so comments on the functioning should be addressed directly to Ford. :cool:

    Please disregard the information on the screen that it is the 3.08 update. Ford didn't do messages about 3.10 update , so I used those messages from 3.08 that everything was as it should be.

    https://1drv.ms/u/s!Ales_ZTMf8IEhORa6Fk_xiVLe3kSEg

    Important note - the contents of the package for real navi license for versions 15128 and 16180 is different.
    If someone will want to order real navi license from me, must clearly indicate to which version license to be generated.