Testing firmware update function for Ford modules
Re: Testing firmware update function for Ford modules
plz laset ver
Thank you
Thank you
-
Jaafar88
- Posts: 20
- Joined: Wed Mar 03, 2021 2:04 pm
- Vehicle: Ford Explorer Limited, 2021, 2.3 EcoBoost
Re: Testing firmware update function for Ford modules
Hi there.
Please, I need the latest 2.4.x version.
I am aware of all the precautions to use the update function.
Thanks in advance,
Jaafar
Please, I need the latest 2.4.x version.
I am aware of all the precautions to use the update function.
Thanks in advance,
Jaafar
Re: Testing firmware update function for Ford modules
Hello, send an email to Forscan, they will be happy to help you
-
onlygodismyjudge
- Posts: 1
- Joined: Wed Oct 28, 2020 5:11 pm
- Vehicle: Lincoln Navigator 5,4 310 PS 2009
Re: Testing firmware update function for Ford modules
Ich würde gerne mitmachen. Lincoln Navigator 2009 Model 2010.
Laptop und Kabel vorhanden.
Laptop und Kabel vorhanden.
Re: Testing firmware update function for Ford modules
Hi,
who can help me with an as-built for DDM and PDM modules
WF05XXGCC5JY43022
Thank you
who can help me with an as-built for DDM and PDM modules
WF05XXGCC5JY43022
Thank you
- fordsmax471
- Posts: 1302
- Joined: Mon Aug 07, 2017 5:29 pm
- Vehicle: Ford S-Max 2.0 TDCi 2017 PowerShift
- Location: EST
Re: Testing firmware update function for Ford modules
George.I wrote: Thu Aug 26, 2021 10:14 am Hi,
who can help me with an as-built for DDM and PDM modules
WF05XXGCC5JY43022
Thank you
Re: Testing firmware update function for Ford modules
hi can anyone find if there's any as built for KVM for WF0MXXGCDM5B84956 thanks
-
c.ionut
- Posts: 34
- Joined: Thu Jun 19, 2014 8:52 pm
- Vehicle: Mondeo 2.0/96kw 2004 Mondeo 2.0/120kw 2013
Re: Testing firmware update function for Ford modules
here as built
-
warren8r
- Posts: 1
- Joined: Sun Sep 12, 2021 8:16 am
- Vehicle: Ford Mustang GT with Roush Phase 2, 2020
Re: Testing firmware update function for Ford modules
Help!
I was in the process of doing this. 2020 Mustang GT. I made it all the way to the module with 85MB (LONG).
I stayed in contact with all participating devices so that there was no pending interaction. About 1.5 hours into it, it was at 58% and just randomly said, "procedure interrupted." And "ready..." was showing.
I thought there was no way I bricked this thing, I took every measure possible. So I tried to refresh the connection to my car, it connections but then says it can't tell what kind of car.
I decided to uninstall and reinstall 2.4.3 beta...still same message. It asked for the product #, which I am glad I copy pasted, but that didnt. help. I tried to uninstall and install 2.3.42. Still unable to determine vehicle.
The dump file is too large to attach. Here is link:
https://drive.google.com/file/d/1Bu0LwH ... sp=sharing
I was in the process of doing this. 2020 Mustang GT. I made it all the way to the module with 85MB (LONG).
I stayed in contact with all participating devices so that there was no pending interaction. About 1.5 hours into it, it was at 58% and just randomly said, "procedure interrupted." And "ready..." was showing.
I thought there was no way I bricked this thing, I took every measure possible. So I tried to refresh the connection to my car, it connections but then says it can't tell what kind of car.
I decided to uninstall and reinstall 2.4.3 beta...still same message. It asked for the product #, which I am glad I copy pasted, but that didnt. help. I tried to uninstall and install 2.3.42. Still unable to determine vehicle.
The dump file is too large to attach. Here is link:
https://drive.google.com/file/d/1Bu0LwH ... sp=sharing
- Attachments
-
- unabletofind.PNG (54.24 KiB) Viewed 6523 times
-
tractmec
- Posts: 2109
- Joined: Thu May 26, 2016 11:43 pm
- Vehicle: F150 5.4 Triton 2005 Fusion 3.0 2010
Re: Testing firmware update function for Ford modules
Pray that you saved a Profile from before you started this experiment as per the recovery procedure at this link. viewtopic.php?f=13&t=18751 Something you should have read and thoroughly understood before you started!warren8r wrote: Fri Sep 17, 2021 10:08 am Help!
I was in the process of doing this. 2020 Mustang GT. I made it all the way to the module with 85MB (LONG).
I stayed in contact with all participating devices so that there was no pending interaction. About 1.5 hours into it, it was at 58% and just randomly said, "procedure interrupted." And "ready..." was showing.
I thought there was no way I bricked this thing, I took every measure possible. So I tried to refresh the connection to my car, it connections but then says it can't tell what kind of car.
I decided to uninstall and reinstall 2.4.3 beta...still same message. It asked for the product #, which I am glad I copy pasted, but that didnt. help. I tried to uninstall and install 2.3.42. Still unable to determine vehicle.
The dump file is too large to attach. Here is link:
https://drive.google.com/file/d/1Bu0LwH ... sp=sharing
Send your same zip file that you uploaded to google, attached to an email, to this address https://forscan.org/contactus.html with a short description in the message body! Posting it here will give you little help! Hopefully you have a paid license as Paid holders(your log appears to show an activation code?) are the only ones The team responds to now!
You may have just discovered the reason that Forscan recommends wired USB adapters for this purpose!( I noticed several STPX Interruptions in your Log and at one point the connection is dropped completely, common with WIFI and not quite as common with Bluetooth but it does happen) right after a calibration/strategy .vbf file download.
The Forscan team will know more about it!