[Windows Mobile Development and Hacking General] mdl054:
UPDATE: Hey folks, navigation has been figured out. Thank you to everyone who helped and an especially big thank you to the folks in Russia who made it mostly possible!

https://xdaforums.com/windows-mobile/general/myford-touch-navigation-activation-t3368080

There was a thread on this topic a while back and has since been closed. Pending certain developments it has become prudent to open a new thread to discuss these new directions.

The last thread can be found here: http://xdaforums.com/windows-mobile/general/hacking-myford-touch-getting-closer-t2938321

First of all, I want to start this thread by saying this is NOT intended to start fights! One user, jmr061, has figured it all out and currently charges money through his own private website and business in the Wisconsin area. I don't want to hear anything about putting anyone out of business. His business is his own. Its fine if you feel that way but this thread isn't the place to discuss it. He is also the only one thus far who has successfully plumbed the workings of MFT entirely and I have nothing but respect for him. He also happens to be a very helpful poster on many Ford enthusiast websites across the net and doesn't deserve any chastising of any kind. Keep it clean!

Current option for adding Navigation to MFT in a non-Nav equipped vehicle:

Replacing the APIM with a Nav enabled one. The part numbers are different and a few versions exist. To successfully add the new APIM you must match the correct options. By not getting the proper APIM you will very likely lose features such as the backup camera, etc.. To properly check which car came with what options you will need to use Ford Etis. Ford Etis can be found Here. Options that are not enabled by the factory show as "Less XXX" where XXX represents the option. For example, a car without Nav will read "Less Navigation". Similarly, a car with Nav will read "With Navigation". You must match all options.

There are a few downsides to this procedure. First of all, the obvious is finding an APIM that is correctly configured for your car. Secondly you will need to rip the dash apart. It isn't particularly difficult depending on your model but it can lead to a few setbacks. A software update from Ford installed on a USB drive can also remove the nav. I'll get into this later down below. The expense is also a factor as you can rarely get the units for less than a few hundred. Certain sites online sell Nav enabled APIMs for over a thousand or more.

You will also need to purchase a navigation SD card separately. At the time of writing (Feb 2016) the A7 card is newest for North America.

I can independently confirm this method does work. This is my 2013 Ford Fusion SE that was equipped with MFT and no Nav.

What I believe we need to do to unlock Navigation in our MFT systems

The secret to enabling features is going to be in the As Built Data. ABD. It seems as though all MFT cars get the same APIM and what differentiates the features is the ABD. The ABD tells the car which features were purchased and which to be enabled. ABD is not plain text, it exists as bits. Comparing the ABD of cars with Nav vs cars without Nav should teach us what modifications we need to make. The ABD is NOT easy to access or change and will likely involve using proprietary or expensive software to do so. Ford VCM2 and IDS are a guarantee. ABD is not unique to the APIM, in fact its used in many modules on the car. We are unable to manually change values on the APIM ABD.

We should be able to accomplish this without opening the dash up as the solution is within the software, not the hardware.

I found a tool for the Ford Focus that will retrieve ABD and edit it. http://ford.xtlt.ru/

Things to keep in mind:

- Updates for MFT from Ford.com will remove Nav from even a Nav enabled APIM. As happened to me. Probably has to do with the ABD (as stated above).

-It seems as though the update files given to a car with Nav are identical to the update files given to a car without Nav. I could be wrong but my testing of this is very limited. I used the VIN from my car to create an account and download the latest version of the software then I used the VIN from a Nav enabled car and created a separate account and downloaded the latest software. The file name, size, and hash are the same. It is unknown (at least by me) at this time if this is the same across the board. Its possible (and likely) the file for the Fusion will differ from the file for say an Escape.

- A downstream USB port exists on the rear of the APIM. Connectivity achieved by use of a Ford Rotunda OTC Sync Generation 2 Programming Cable.

- Interestingly enough it seems that all Nav enabled APIMs use the same Navigation license.

- Many (possibly most) APIMs are all loaded with the Navigation apps already and simply lack the license. Some users on other forums have sucessfully added the license (again the same on all) but it won't magically run. Probably ABD related as well.

- Modifying the Zip files for the update install will break the signature and verification used by the MFT and will NOT install.

- The MFT system is custom designed from the ground up. No standard file structure exists in other systems.

- In the old thread a user jsalzman took his APIM apart. He took highly detailed pictures. They can be found Here. Thank you!

- Ford IDS cannot be used to change ABD on APIM for MFT.

- It seems jmr061 figured it all out around March 2015. Some of his post history on other forums gives us many clues. Please don't flame him.