# 2016 Ford Escape Sync3 1.0 updated to 3.0 and no Apple Carplay! **URL:** \ **Category:** CyanLabs Update Support\ **Tags:** oem, non-nav, na, APIM, SYNC3, Syn3Updater, pre-my20\ **Created:** [4 March 2025 20:19 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518 "2025-03-04T20:19:25Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![reyes2324](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/r/a6a055/32.png) [@reyes2324](https://community.cyanlabs.net/u/reyes2324)\ **Post date:** [4 March 2025 20:19 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/1 "2025-03-04T20:19:25Z")
Hello. Will really appreciate any help here. I’ve just updated my 2016 Ford Escape from Sync 3 V1.0.15139 directly to V3.4.23188. Everything went fine with the upgrade but I had a pop up related to the media hub. I went ahead and replace the old one with PN HC3Z19A387F. Pop up is gone but I have no CP or AA. I’ve tried master reset multiple times and changing phones and cables. Nothing has worked. I’ve read in another thread (2016 Mustang Sync3 1.0 updated to 3.0 and no Apple Carplay!) that this could be related to not installing an intermediate version before moving to V3.4. I’ve follow those instruction to revert back to 2.2 before going back to 3.4 but get Error Code: PKG\_ERR04. I’m running out of ideas here. Could I please get some help on what to do next? Much appreciated * * * **SYNC Region:** NA **Navigation Variant:** Non Nav **Manufacturer Year:** Pre MY20 **Install Type:** OEM **Old SYNC Version:** 1.0.15139 **New SYNC Version:** 3.4.23188 **Do you have a error message, if so what is it?** Error Code: PKG\_ERR04 **Update Method:** CyanLabs Syn3 Updater **Syn3 Updater Version:** 2.13.1.0 **Syn3 Updater Documentation Read:** yes **Syn3 Updater Log File** ```no-highlight CYANLABS - SYN3 UPDATER - V2.13.1.0 Branch: Stable Operating System: Microsoft Windows 11 Home (2009) PREVIOUS CONFIGURATION Version: 1.0.15139 Region: NA Navigation: False Install Mode: Auto-Detect (reformat) Install Mode Overridden: False My20 Protection Enabled: Auto-Detect DESTINATION DETAILS Mode: Drive Model: Seagate Expansion SCSI Disk Device Size: 931.5GB FileSystem: exFAT Partition Type: MBR REFORMAT.LST VOICE=5U5T-14G391-CS_1660783942000.TAR.GZ GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ APPS=NU5T-14G381-AD_1689364279000.TAR.GZ AUTOINSTALL.LST ; CyanLabs Syn3Updater 2.13.1.0 Stable - reformat Mode - Sync 3.4.23188 NA [SYNCGen3.0_ALL_PRODUCT] Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ Item2 = REFORMAT TOOL - 1u5t-14g386-cb.tar.gz Open2 = SyncMyRide\1u5t-14g386-cb.tar.gz Options = AutoInstall FILES (5) 1u5t-14g386-cb.tar.gz (8.5MB) PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB) 5U5T-14G391-CS_1660783942000.TAR.GZ (385.5MB) 4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB) NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB) LOG [3/2/2025 12:39:32 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Non Nav APIM [3/2/2025 12:39:32 PM] Install Mode: Auto-Detect (reformat) Forced: False [3/2/2025 12:39:32 PM] MY20 Protection: Auto-Detect [3/2/2025 12:39:32 PM] Formatting USB drive [3/2/2025 12:39:32 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive [3/2/2025 12:39:59 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz [3/2/2025 12:39:59 PM] Downloading: 1u5t-14g386-cb.tar.gz [3/2/2025 12:40:01 PM] Validating: 1u5t-14g386-cb.tar.gz [3/2/2025 12:40:01 PM] Downloaded: 1u5t-14g386-cb.tar.gz [3/2/2025 12:40:01 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:40:01 PM] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:40:02 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:40:02 PM] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:40:02 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:40:02 PM] Downloading: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:40:22 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:40:23 PM] Downloaded: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:40:23 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:40:23 PM] Downloading: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:40:51 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:40:52 PM] Downloaded: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:40:52 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:40:52 PM] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:03 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:06 PM] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:06 PM] Preparing USB drive [3/2/2025 12:41:08 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz [3/2/2025 12:41:08 PM] Copying: 1u5t-14g386-cb.tar.gz [3/2/2025 12:41:08 PM] Validating: 1u5t-14g386-cb.tar.gz [3/2/2025 12:41:08 PM] Copied: 1u5t-14g386-cb.tar.gz [3/2/2025 12:41:08 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:41:08 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:41:08 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:41:08 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ [3/2/2025 12:41:08 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:41:08 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:41:11 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:41:14 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ [3/2/2025 12:41:14 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:41:14 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:41:19 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:41:24 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ [3/2/2025 12:41:24 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:24 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:31 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:38 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ [3/2/2025 12:41:38 PM] Generating reformat.lst [3/2/2025 12:41:38 PM] Generating autoinstall.lst [3/2/2025 12:41:38 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY! ``` ---
**Author:** ![reyes2324](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/r/a6a055/32.png) [@reyes2324](https://community.cyanlabs.net/u/reyes2324)\ **Post date:** [4 March 2025 20:23 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/3 "2025-03-04T20:23:30Z")
![20250302_134653](https://community.cyanlabs.net/uploads/default/original/2X/3/38df9c2bdb8616b55481ccc28dfc6592feebc7ca.jpeg) ![20250302_134709](https://community.cyanlabs.net/uploads/default/original/2X/e/eeb87adfe09e2f63a60509ec7b7a0245375e175c.jpeg) ![20250303_183934](https://community.cyanlabs.net/uploads/default/original/2X/0/055c238c024c7197ac3c3ff7a3e22edd81b6d363.jpeg) ---
**Author:** ![warlock12118](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/w/e95f7d/32.png) [@warlock12118](https://community.cyanlabs.net/u/warlock12118)\ **Post date:** [4 March 2025 23:43 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/4 "2025-03-04T23:43:13Z")
You have to replace the USB media hub in the console for CP & AA to work on a 2016 Escape. Part number is HC3Z-19A387-F, it takes about 15 minutes to swap it out ---
**Author:** ![SaNdMaN](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/sandman/32/3220_2.png) [@SaNdMaN](https://community.cyanlabs.net/u/SaNdMaN)\ **Post date:** [5 March 2025 00:09 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/5 "2025-03-05T00:09:39Z")
> [@warlock12118](#): > > You have to replace the USB media hub in the console for CP & AA to work on a 2016 Escape. > Part number is HC3Z-19A387-F, it takes about 15 minutes to swap it out Honest question: do you even read people’s messages before replying?, or you just start writing? 👇 > [@reyes2324](#): > > I went ahead and replace the old one with PN HC3Z19A387F ---
**Author:** ![warlock12118](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/w/e95f7d/32.png) [@warlock12118](https://community.cyanlabs.net/u/warlock12118)\ **Post date:** [5 March 2025 00:22 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/6 "2025-03-05T00:22:49Z")
Check the edit time stamp. His post was edited after I posted. ---
**Author:** ![SaNdMaN](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/sandman/32/3220_2.png) [@SaNdMaN](https://community.cyanlabs.net/u/SaNdMaN)\ **Post date:** [5 March 2025 00:30 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/7 "2025-03-05T00:30:13Z")
> [@warlock12118](#): > > Check the edit time stamp. > His post was edited after I posted. I’m not sure what you are talking about, the 1st message (where he mentions swapping the hub) was not edited… Which ironically circles back to my original question… That’s ok, you can say “my mistake”, “I was wrong”, “I got confused”… We can all do that… And my question was honest, because it’s not the first time I’ve seen “random responses” that do not correlate directly to what the user asks… I hope I do not come out hard, but again, honest question. ---
**Author:** ![SaNdMaN](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/sandman/32/3220_2.png) [@SaNdMaN](https://community.cyanlabs.net/u/SaNdMaN)\ **Post date:** [5 March 2025 00:58 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/8 "2025-03-05T00:58:40Z")
> [@reyes2324](#): > > Pop up is gone but I have no CP or AA. I’ve tried master reset multiple times and changing phones and cables. Nothing has worked. Have you made the phones forget about Sync3 as well?. If you haven’t done so, do that and try again. If you: - have replaced the hub for a compatible one ([Media Hub, CarPlay Compatible - 2015-2020 Ford/Lincoln - SYNC 3](https://community.cyanlabs.net/t/media-hub-carplay-compatible-2015-2020-ford-lincoln-sync-3/4683)) - have performed a master reset - have made the phones forget about sync3 - have tried both android auto and car play Then there’s really not much to try. You can’t go back to 2.2, that’s why it’s always recommended to make sure AA/CP works on 3.0 or below before going to 3.4. > [@reyes2324](#): > > changing phone Does this mean brands or you tried 2 iphones?. I’m asking because Android Auto is more forgiving, you could actually get AA to work with older unsupported hubs… But not CP… ---
**Author:** ![reyes2324](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/r/a6a055/32.png) [@reyes2324](https://community.cyanlabs.net/u/reyes2324)\ **Post date:** [5 March 2025 02:39 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/9 "2025-03-05T02:39:58Z")
Forgetting the sync3 on the phones did the trick. Thank you ---
**Author:** ![kodymcclellan](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/kodymcclellan/32/15807_2.png) [@kodymcclellan](https://community.cyanlabs.net/u/kodymcclellan)\ **Post date:** [5 March 2025 13:08 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/10 "2025-03-05T13:08:12Z")
> [@SaNdMaN](#): > > Then there’s really not much to try. > You can’t go back to 2.2, that’s why it’s always recommended to make sure AA/CP works on 3.0 or below before going to 3.4. I unfortunately didn’t know this before updating to 3.4. Is it possible to use forscan to factory reset the APIM to as built condition? ---
**Author:** ![warlock12118](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/w/e95f7d/32.png) [@warlock12118](https://community.cyanlabs.net/u/warlock12118)\ **Post date:** [5 March 2025 13:47 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/11 "2025-03-05T13:47:53Z")
You can use ForScan to reload the factory AB, but it’s not going to get you back to 3.0 v2.2. Going from 3.0 to 3.4 is a bit like reformating a PC to go from Windows 7 to Windows 10 and throwing away the old Win 7 hard disk controller to have one compatible with Windows 10. Going back to 3.0 is either going to require a new APIM or someone very skilled at benchwork. ---
**Author:** ![system](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/s/bcef8e/32.png) [@system](https://community.cyanlabs.net/u/system)\ **Post date:** [7 March 2025 22:30 UTC](https://community.cyanlabs.net/t/2016-ford-escape-sync3-1-0-updated-to-3-0-and-no-apple-carplay/19518/13 "2025-03-07T22:30:27Z")
Closed on 7 March 2025 22:30 UTC This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.