Sync3 22251 and Interrogator

Hi !

As many of yours, I’ve the issue with 3.4.22251 version and, probably, rwdata partition which is full.
I used Syn3 to create an USB key with RWData cleaner, but it doesn’t work, event with key cycle or two consecutive soft reset.
So I’m trying to use the Interrogator to get a log and check my issue is due to rwdata partition.
When I plug the USB key after the start, I get an immediate INST_ERR12 error, there is no log on my USB key.
I do two soft reboot, and I plug again my key and, this time, the “Upgrading software” stays many minutes. At the end, I get again the ERR12 error. If I unplug/replug the USB key, I get a message saying “success”, but I don’t have any log on the key.

Are you aware that the Interrogator is not working with the 22251 bug ? Even after two soft reboot ?
Is there any other thing to do before trying to jailbreak my Sync ?

Thanks for your help, I’m trying lot of things since two days on my GT350, but nothing is working :frowning:


SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.22251

New SYNC Version: 3.4.22251

Do you have a error message, if so what is it?
INSTLL_ERR12

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

N/A
  1. make sure nothing else is plugged into the other USB port
  2. try using the other usb port if you have one
  3. use a good quality USB drive (eg PNY/SanDisk/Lexar)
  4. perform a MASTER RESET, not a soft reset before trying to run the cleaner

Thanks for your answer !

  1. Only the USB key is plugged.
  2. Ok, will try on the second one.
  3. I’m using only good USB keys (sandisk)
  4. I’m not able to do a Master Reste, when I click on continue the unit hangs, and I have to force the reset.

I will test the second point and come back to the forum.

Hello.

If none of the proposed solutions in the guide work, we do not have anything else to recommend at the moment.

Too bad, nothing is working at this time.
Thanks for your answers and this great tool !

IF this was not a Sync 3.0 to 3.4 mod (as in you didn’t do a reformat at anytime to get to 3.4) Ford does have a TSB out for this (and a CSP here in the states).
A dealer tech can use FDRS to clear the RW data partition and then bring the APIM up to 3.4.23188 using FDRS with a universal update USB.

Thanks, I will try again this weekend and, if not working, I will go the Ford dealer.
I just hope they will be able to solve it without changing the APIM, and if they have to, that Ford is assuming its bad development.

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