jordandev
Well-known member
Thanks. Yeah that's the one I won't be able to do with a Nano anyways since it includes CCM. Will upgrade to a Mongoose if I can get unstuck to see that update I guess.Only ipma update will do that
Sponsored
Thanks. Yeah that's the one I won't be able to do with a Nano anyways since it includes CCM. Will upgrade to a Mongoose if I can get unstuck to see that update I guess.Only ipma update will do that
Did you also have to change 7D0-01-02? I’m curious where you ended up.Mine had a Exxx in that field and that was one of the two lines Jesse had me update to the Fxxx.
To be honest I had a lot of stuff messed up in trying to fix the cameras.Did you also have to change 7D0-01-02? I’m curious where you ended up.
Sounds like you had a lot to do. Glad Jesse was able to come to the rescue. Since you didn’t have to change 7D0-01-02, what was yours originally? Did it start with a 2 or an A?To be honest I had a lot of stuff messed up in trying to fix the cameras.
Jesse gave me two lines to change but they didn't seem to fix it. It could have been the APIM not resetting or not taking the new values even though I confirmed they were in place with forscan. I reset it about 6 times and then started looking at other things and thats when it went downhill fast. Jesse had me do a configuration on the IPMA to fix what I messed up there and the cameras still didn't work. We just left it at that state for the night and this morning they were working.
the two lines he had me change are:
7D0-01-04-03F4-FC20-40AF
7D0-02-01-8616-420A-0244
I feel like this is what fixed the issue I just didn't have my APIM reset enough to make them active.
Mine started with an ASounds like you had a lot to do. Glad Jesse was able to come to the rescue. Since you didn’t have to change 7D0-01-02, what was yours originally? Did it start with a 2 or an A?
7D0-02-01 is a surprise. We have different values in the first block but the checksums are the same.
Mine: 7D0-02-01 0616 420A 0244
Yours: 7D0-02-01 8616 420A 0244
Thanks. This is helpful. We have the same values for 7D0-01-02 and 7D0-01-04. They didn’t do the trick because of issues with your IPMA.Mine started with an A
7D0-01-02 A300-C62B-B927
Try clicking the refresh button on right of the Green Run button for the APIM and then run the APIM update again. This downloaded and installed the next available APIM update for me immediately rather than waiting.
I'm currently in the same boat after getting up to Sync 244. Hoping a long nap and perhaps something in an overnight batch on Ford's servers will get me back in business tomorrow.Nevermind, I gave up for the night and just let everything sit. This morning the update went without a hitch.
Is your automatic updates switch able to be toggled?I just received the car from dealer after updating several modules such as : CCM, GWM, PDM, DDM, SCCM, PSCM, IPMA, TRM and DSP.
Still the SYNC version 21136, Revision: 134.
Any help will be appreciated.
Vin# 1FTFW1E51MFC37912
Yes.Is your automatic updates switch able to be toggled?
If you are concerned, you can always get your own 2-day license to FDRS and type your VIN in. You don’t need an adapter to do this. You just won‘t be able to program. FDRS licenses are available in Kuwait and once you’ve input your VIN, you can not only see if there are software updates available, you can pull up the vehicle history and see exactly what your dealer did. If you find evidence that the dealer did not do something you wanted done, you can print out the evidence and take it in.Yes.
but never received any updates OTA.
I live in Kuwait so maybe the OTA updates is not received because I don't have the wifi network menu.
There is NO UPDATE for JOB 2I just received the car from dealer after updating several modules such as : CCM, GWM, PDM, DDM, SCCM, PSCM, IPMA, TRM and DSP.
Still the SYNC version 21136, Revision: 134.
Any help will be appreciated.
Vin# 1FTFW1E51MFC37912
Can you please announce when JOB 2 will receive a new update.There is NO UPDATE for JOB 2