There are few minor changes that need to be made for functionality. You just have to find a NAV enabled Sync 3 APIM/Touchscreen, switch out the hub and add the GPS antenna
From Post #1, first page of this thread...
Sound like a little girl with hurt feelings. :ford:
read the first few pages of this thread... everything is covered pretty good.... a little programming is required, but not difficult.
If your APIM isn’t from a Mustang changing the code lines is required. Not because your radio won’t play but because you’ll get a bunch of errors and DTCs. The programming is the easy part and is required for full functionality. Each car is a little different though so if you get your equipment I can help with the data you need.
Do you have the VIN for the car your APIM came from? If so register that VIN on myford.com and if the release has been finalized for your "new" VIN it will let you download it. That's what I did and I just updated tonight with no issues.
The bootleg version makes me a little nervous.
No, they are the same software but the VIN number for the “new” car is embedded in the hex code. Registering someone else’s vehicle as yours could cause an issue. It will read your VIN during the update and store it as part of a new file that must be uploaded to Ford after updating. So when you do the update you have to actually open the file that is produced and change that line of code from your “old” VIN back to the “new” VIN in order to tell Ford it was updated. If not it won’t allow you to update in the future.
Thank you for the info. I will check again tonight to see if the automatic update is still not working. If not maybe I will contact the place I purchased the unit from (fordpimods) to see if Jason has an idea on what I could do. I was really hoping the auto updates would work. But I’m guessing it’s not validating with fords servers properly.
Unfortunately OTA updates will never work because of the servers. You could risk it and use a VIN from a car on a dealer lot but if you do it will mean you have to do it that way everytime because you won't be able to send the file to Ford that tells them the "new" VIN has been updated. whether that would cause an issue with Ford, the other car's owner or a judge.... I don't know.
Wow, I didn't think my swap for car play was going to be such an issue. LOL Unfortunately, non of my friends own a mustang. I sent a e-mail out to the place I purchased the kit. Hopefully they can help me out. Now I'm wondering if I should wait for the official release of version 3.0 since this is becoming such an issue.:headbonk:Unfortunately OTA updates will never work because of the servers. You could risk it and use a VIN from a car on a dealer lot but if you do it will mean you have to do it that way everytime because you won't be able to send the file to Ford that tells them the "new" VIN has been updated. whether that would cause an issue with Ford, the other car's owner or a judge.... I don't know.
Do you have a friend with a premium? He could download the new update to a USB and then do his update OTA leaving you with the actual file. Once you update just don't do the last step of telling Ford it has been updated. That's basically what the bootleg versions are. I just don't trust them, especially now that Sync 3 vulnerabilities have been partially exposed.
This just highlights my number one rule: DO NOT BUY APIMs WITHOUT VINs.