Страница 1 из 3

Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 05 апр 2018, 19:35
natcorporation
Hi everyone

I have problem with Ford Fusion 2017. I read original configuration file from BCM.
Mistakely I write wrong configuration file from another Ford - I have file in the same folder ( nevermind ).
Now - Car won't start and don't see key. I flash BCM with vbf loader but I must write original configuration. Please help me - is option to write conf file to BCM without ignition ?

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 06 апр 2018, 00:47
sev611
you can use the hazard ligth to wake the systems up with
when we are using fdrs it tells us to turn igition on and if not possible turn hazard ligth on and go on so i think it migth be the way to do it and load the asbuilt data from etis
rgds sev

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 06 апр 2018, 01:16
natcorporation
I see on the forum few person with the same problem. I need list with vbf files to make refresh BCM - with the last config file per vin. Anybody can help?

VIN: 3FA6P0HD8HR128405

BCM PART NUMBER : GU5T-14B476-CAJ

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 09 апр 2018, 19:01
natcorporation
Aanybody can help ?

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 15:33
kroligoff
For you BCM GU5T-14B476-CAJ:
SBL: DG9T-14C187-AB
1: GU5T-14C184-AAJ
2: FU5T-14F391-AAA
3: HG9T-14F390-AB
4: HG9T-14G163-AA
5: HP5T-14F389-BC
6: HS7T-14C636-BF
7: HS7T-14G162-CC

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 15:41
kroligoff
Try load from ETIS (use VIN) or
Load from file
Direct_BCM_100418_.xml

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 21:09
natcorporation
I cant write only configuration right now I have errors on writing. I Upload files from you and tray.

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 22:48
SebastianD88
Hello,

can the BCM with part number FU5T-14B476-BAL (model year December 2015) be flashed with the VBF files of a Mondeo from 2017?

I would like to flash the BCM with the following VBF files:
1_DG9T-14C187-AB
2_HU5T-14C184-AAR
3_HG9T-14C636-GC
4_HU5T-14F391-AAA
5_HP5T-14F390-DAA
6_HP5T-14F389-CAB
7_HP5T-14G163-FAA
8_HP5T-14G162-AEA

Is this possible or could the BCM module be destroyed by it?
Are the stored keys lost after the update, so that the ignition is no longer on?
Does anyone know if the hardware (BCM) has been changed?

Who can help? Many Thanks!

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 23:37
natcorporation
Ok now flasing is ok. It will see on picture. But after flashing I can not load direct configuration to bcm - errors - conditions not correct, finishing with 62 errors. Remote key is working but ignition won't - " KEY NOT DETECTED".

Flashing files from Kroligoff list - OK. Many thanks.

Please anybody have any idea ?

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 23:38
natcorporation
Another pics

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 10 апр 2018, 23:39
natcorporation
The last one.

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 11 апр 2018, 08:36
SebastianD88
What happens if you put the key in the backup slot in the center armrest?

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 11 апр 2018, 11:12
natcorporation
nothing - it's the same no key detected.

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 11 апр 2018, 16:41
SebastianD88
I think you need Ford IDS to restore the key Data.

Re: Ford Fusion 2017 bricked BCM - Wrong conf file loaded

Добавлено: 13 апр 2018, 15:33
natcorporation
Anybody have any idea ????

Please