Cuch

telnet, no. SSH on a QNX VM, yes.

Acool

This may be totally trivial, but I noticed the official 2.2_17011 Non-Nav voice_new.img file has limited write permissions as compared to say 2.3, and also lists a username and group. I wonder if the MEM error is due to a write permission issue where the previous voice or temp voice file cannot be overwritten via the steps in the script. Voice is not held in the root partition and so installing it (i.e., copying it - it's a simple copy) may be done without administrative privileges once the signature of the bash script is verified as authentic.

bamorris2

I have a 2016 non-nav and this has been my progression over the last several months.

* Truck came with 1.0
* Upgraded to 2.2 using the early leaked files on this forum. Lost Gracenote.
* Upgraded to early build 3.0 from this forum. Got Gracenote back.
* Downgraded back to 2.2 from this forum

Ford Owner site now shows 2.3 for my truck and I would like to install it. My question is, will I lose Gracenote and/or get the memory error? In other words, is there a high likelihood that the 2.3 upgrade will not be successful because I’ve used unofficial updates previously? Things are ok now and I’d rather stay at 2.2 than screw up 2.3. Buy would like 2.3 if high likelihood of success.

tbird2003

Some basic details MY16 Sync 3 Non-Nav

I've upgraded along the same path many have done here.

1. 2.0 to 2.2
2. 2.2 to 3.0 (17194)
3. 3.0 back to 2.2
4. 2.2 to 2.3 via FMCO official release

After the 3.0 to 2.2 downgrade, the GN versions was 1.1.1.797.

I received the official 2.3 notice on Monday and installed the next day. The install went without a flaw. When completed, everything worked. I notice a few days later, that the GN version was still 1.1.1.797. The 2.3 upgrade didn't change the GN version.
So my questions,

1. Did the 2.3 upgrade not alter the GN version?
2. What should the GN version be after the 2.3 upgrade?

Cuch

Still waiting for my owner profile to show 2.3 - still says 2.2 is latest. Same for my Dad's M/Y 17 2.0 Nav.

Anyway, 1.1.1.797 for GN is the correct version for 2.3. Unchanged from 2.2, even though 2.3 installs it -- 2.3 assumes users are running 1.0, 2.0 as well, which do have older versions of the GN DB, IIRC ;-)

tbird2003

Thanks for the confirmation on GN.

One other odd note. The first line of the autoinstall has a comment that denotes release details. It has the reference to MY17. My F150 is a MY16.
Do you have any insight? My truck was built late in the MY16 production run. August 2016. Do you think I have a MY17 APIM?

Cuch

hmmmm interesting! It’s possible that they slipstreamed model year 17 APIMs into the late-build 16’s production.

I’m not sure. Anyone else have any insight?

TexasRebel05

_16280 was released for Lincoln vehicles, but not Fords.

Theocoog

My F150 is a 2016 (June build) Sync 3.0 Non-Nav. My upgrade path was a little more winding, but I ended up having an early 2.2 release get registered with Ford in July this year and the 2.3 download I received this week is different than yours, even though we're both MY16 Sync 3.0 Non-Nav. You must have a later APIM.

My upgrade path:

• 1.0 to 2.2.xxxxx (unknown release, registered itself with Ford)
• 2.2.xxxxx to 3.0.17194 (multiple issues with this 3.0 release)
• 3.0.17194 to 2.2.17011 (Thanks again Cuch!!)
• 2.2.17011 to 3.0.17276 (working great so far...)

I haven't checked for an update from the truck since I started fooling around with 3.0, so I'm still registered as running 2.2.xxxxx, and I got prompted to download the 2.3 update this week . My AutoInstall.lst says:

This makes sense to me since I am a MY16. The 2.3 release is listed as 2.3.17109. I'm interested to know if your release number the same...

stang18

Hello,

Regarding the possibility to telnet / ssh did you try like in this article : http://www.happyhacking.org/HappyHac...uh-and-go.html

Even if it's toyota the system is qnx car just like us.

Something else, as you're frequently updating / downgrading did you try to access the system through wifi / bluetooth / USB ethernet while in update mode. Maybe the firewall is down during update process or the network is behaving differently during this process.