# Update old APIM

**URL:** <https://community.cyanlabs.net/t/update-old-apim/15911>\
**Category:** CyanLabs Update Support\
**Tags:** retrofit, nav, na, pre-my20, SYNC3, APIM\
**Created:** [22 November 2024 06:56 UTC](https://community.cyanlabs.net/t/update-old-apim/15911 "2024-11-22T06:56:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MilesS931](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/miless931/32/14686_2.png) [@MilesS931](https://community.cyanlabs.net/u/MilesS931)\
**Post date:** [22 November 2024 06:56 UTC](https://community.cyanlabs.net/t/update-old-apim/15911/1 "2024-11-22T06:56:13Z")

</div>

I have an older Nav APIM. I have been trying to update the sync version on it. I have another non nav APIM that works fine with the updater program but the nav one is on version 1.0.15139 and keeps giving me invalid or unsigned file errors. It will not respond to the interrogator or any file I have given it. I tried to jailbreak it and get it updated that way but I have been unsuccessful in doing that as well. Any ideas on how to get it to update will be helpful. I have also tried a different USB and USB hub.

* * *

**SYNC Region:** NA

**Navigation Variant:** Nav

**Manufacturer Year:** Pre MY20

**Install Type:** Retrofit

**Old SYNC Version:** 1.0.15139

**New SYNC Version:** 1.0.15139

**Do you have a error message, if so what is it?**  
Invalid or Unsigned File

**Update Method:** CyanLabs Manual Method

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [27 November 2024 21:31 UTC](https://community.cyanlabs.net/t/update-old-apim/15911/2 "2024-11-27T21:31:29Z")

</div>

If it is a -CFC unit they are known for issues. I would not rely on it, unless just for a test mule.

---

<div class="post-metadata">

**Author:** ![MilesS931](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/miless931/32/14686_2.png) [@MilesS931](https://community.cyanlabs.net/u/MilesS931)\
**Post date:** [27 November 2024 21:50 UTC](https://community.cyanlabs.net/t/update-old-apim/15911/3 "2024-11-27T21:50:50Z")

</div>

I believe it is a -bfc. It’s the same as my other non nav one. It doesn’t have any of the stickers though. So I don’t know for sure. That’s what the bezel diagnosis reports it as though.

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [27 November 2024 22:03 UTC](https://community.cyanlabs.net/t/update-old-apim/15911/4 "2024-11-27T22:03:05Z")

</div>

BFC is non-nav  
CFC is nav

You might have a corrupted firmware. This is common on those units. You could see if this would work.  
[APIM Firmware Flash Rescue - Ford / Information - CyanLabs Official Community](https://community.cyanlabs.net/t/apim-firmware-flash-rescue/4691)

---

<div class="post-metadata">

**Author:** ![MilesS931](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/miless931/32/14686_2.png) [@MilesS931](https://community.cyanlabs.net/u/MilesS931)\
**Post date:** [27 November 2024 22:15 UTC](https://community.cyanlabs.net/t/update-old-apim/15911/5 "2024-11-27T22:15:05Z")

</div>

Ah OK. I just read the one off my apim in my car. I thought they were the same. I’ll look at the apim when I get home and have it in my hand

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [4 December 2024 22:15 UTC](https://community.cyanlabs.net/t/update-old-apim/15911/6 "2024-12-04T22:15:37Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.