Ayham Kutit

I've seen a Russian guy getting telnet connection to the QNX on a live system, I asked him how he done it he just said that we need to files to the factory update image and flash it.
does anyone know how to add anything to the update file/image?

​​​

ljworcs

Thanks for that. I did as you suggested and the install completed in less than 15 minutes.
Hopefully one of the technical minds on here will come up with a solution to also install the update with the 2.3 voice recognition

Acool

Did Ford know your entire upgrade/downgrade path? My guess is MY16 and MY17 is more of a software thing than hardware. MY16 likely started life as 1.0, and MY17 may have started as 2.0. If an unofficial path was taken MY16 may need to be treated as MY17. ***** Has anyone with the MEM error tried to install the MY17 version instead of MY16?

Would you please do an APIM test and post a photo (scroll down too) of your part #s/SW versions (feel free to blur out your VIN and APIM serial#s)? Hold eject and right seek at the same time, end the speaker test, and then there's something like Bezel diagnostics/APIM/part #s or something. Make sure to scroll down and get it all.

TexasRebel05

I attempted to install just the *-BB.tar.gz to get the voice up to date... no luck.

Next step is a Master reset and another try.

Acool

I grepped the MEM_ERR03 error from the file system. Confirmed it's a copy space error:

Error is MEM_NOSPACE_TO_COPY. Sending error code %s MEM_ERR03

I mentioned install cache lies in the same partition as voice and GN. I would see about searching for any package old or new that seems to do the proper cleanup of the install cache, whether it's voice, GN or otherwise.

TexasRebel05

I did a master reset this morning and tried to install just the *-BB tarball... It took more than the 30 minute drive and was still running, so that's a possible good sign. We'll see if it finishes at lunch.

ljworcs

How did it go. We’re you able to complete the install

TexasRebel05

next start showed an MEM_ERR03

firecadet613

Thanks. This fixed my upgrade issue.

Severe

Good Morning All, Thanks for all the work you're doing to sort this out. I'm hoping I can get a hint on where to go to 'fix' my current issue.

I have a 2016 F150 XLT non-Nav Sync 3 unit that was previously running 2.0. No OTA updates ever worked.

The other day, I downloaded the v2.3 update from owners.ford.com. The upgrade appeared to be going well, but is now stuck. On the initial attempt, I let the truck run for 1.5 hours; it was in the Update System Software... It still is after at least 5 hours of run time and multiple stop/starts.

I'm an IT guy by trade so I started researching. What I found is at least four (4) versions of the upgrade files floating around the interwebs.

From owners.ford.com, I downloaded:
JL1T-14G381-AJ.zip - Size is 1,114,742 KB. MD5 (Quick Hash) 66DFBB01E8A922E9E841AB1BFB69731D
What caught my eye was ACools comment on tbird2003's '16 truck with a My 17 file. I think I'm in the same boat. My autoinstall.lst file shows
Notice how it does not have the Option 4 and matches Dakota62's suggested edit.

The other versions I've found are sourced from https://www.4dtech.com/software-updates/ but have very different sizes. They also mention a hardware version number which I do not know how to check what I have.

Any suggestions on what to do with this extremely long running software update and how to get it v2.3?

**Edit**
Still poking around for a solution. Did a master reset and lost GN. Attempted the upgrade with the files from 4dtech and hit the Mem error quickly. In looking at a piecemeal approach it occurred to me that the autoinstall.lst file as provided from owners.ford is showing SYNCGen3.0_2.0.16074_PRODUCT (v.2.0 16074); I was expecting to see a 2.3_17109 like the examples above. Can someone confirm the same in their MY17 file? Wonder if this is an error or if it has any effect.