When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
What firmware did you load? I’m guessing you flipped the last two files. Try rolling back to the latest -BA part calibration level if the latest -BB isn’t working.
Could also be your ELS27. There is more to J2534 than simply “speed” which is why it is used for flashing. Flashing modules inherently error prone, and there is very little error correction in the modules themselves. I’ve had bad flashes even with J2534 that appeared to go ok. Reflashing in that case fixed the issue.
The files that indicate (USB) are just that and don’t load over the CAN bus, way too slow.
After hours of troubleshooting I've reached the conclusion it's likely the ELS27 or possibly ForScan itself.
The files appear to load fine, but when I look at the APIM to validate them it shows all the old content.
Oh well, at least now I know what not to recommend. Anyone have a spare APIM laying around for sale? LOL
Here's my current load. I believe it's the BAG calibration. The only thing different is the Image and App/Grace Note files and I can't get those to update through FORScan anyway. Your part number is probably different than mine so IDK if this will even help you. I wish I would have kept track of the steps I took cause I was in the exact boat as you. This was when I was first starting out and still learning these files and I just can't remember what I did. Sorry...
After hours of troubleshooting I've reached the conclusion it's likely the ELS27 or possibly ForScan itself.
The files appear to load fine, but when I look at the APIM to validate them it shows all the old content.
Oh well, at least now I know what not to recommend. Anyone have a spare APIM laying around for sale? LOL
One thing I remember for sure is I did *NOT* get a successful message. My log most definitely showed procedure failed.
Are you getting the "USB Hub Not Supported" message at startup, or other errors related to playing music off a usb flash drive? Since upgrading to sync 3.4 I'm now am getting a very occasional usb read error but it soon works anyway, as well as voice commands for playing music not always understanding a request.
Yes I am getting the same messages and voice commands for music not working correctly.
I think part of the problem was this is a gen 1 Sync 3 assembly from a 2016 Ford Focus. At least now I can rule out ForScan 2.4.0 and the ELS27 as part of the problem.
ACOOL encouraged me not to give up and that trying random XXXX-14G374-XX .vbf files can bring a Sync 3 APIM's back to life. His wisdom was: " ForScan program load success only means that the module received the data from ForScan; not that it will execute properly. I've always been able to unbrick APIM's but sometimes I've had to use firmware different from the original".
As messed up as that is, it worked for me!
A similar strategy was also mentioned by user 'AmigaSurfer' on the UCDSYS and German Mustang Forums. I copied GB5T-14374-CB from his posts, which I know are incorrect for North America, but they worked and now I'm back in business.
Au{R}oN never pitched in directly per-se, but I found his old posts on this topic that led me in the right direction.
VCM II clone but that wasn't the problem. The hardware has been rock solid across many flashing operations. It was one of the files I was loading. I re-read the test version release notes and they said right there in a big warning that sometimes FORScan will pick the wrong file and you need to be sure you know what you are doing. I didn't and still don't but looking at the first 4 characters of some of the loads FORScan picks for me they aren't even close. Did you try a force write yet to an older calibration?
12-29-2019, 12:47 AM
