Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Bricked KOMBI Module with WinFKP ?
27-01-2022, 15:46 PM,
Post: #31
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
I already tried a lot of things for this bricked Kombi. Winfkp a lot of settings, expert mode, develop mode with manually program data, with charger on car, with engine started, i always got that error ERROR_ECU_SECURITY_ACCESS. So another KLUSTER.
Do i need only to make KM 0 and put VIN on new Kluster? or what else? |
|||
27-01-2022, 15:59 PM,
(This post was last modified: 27-01-2022, 21:15 PM by Node.)
Post: #32
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Your error clearly says - no response from control unit. That is a problem. NOT SOME kind of security. That means it's brain dead. Well, not in hardware sense, but in CPU operation. The only way to revive it if it would be possible to reflash main CPU or it's flash chips directly. But I never tried so don't know if it's possible.
It's DEFINITELY not possible to do it by outside connection anymore. |
|||
27-01-2022, 21:07 PM,
Post: #33
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
|
|||
28-01-2022, 06:08 AM,
Post: #34
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
(27-01-2022, 21:07 PM)Spitfire555 Wrote:(27-01-2022, 15:46 PM)JuiCe Wrote: Do i need only to make KM 0 and put VIN on new Kluster? or what else? Thank you. Actually clearing odometer to FFF, to 0 will make 0 km VO coding means SG_Codieren with NCSExper nothing else ? |
|||
29-01-2022, 10:17 AM,
Post: #35
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
(28-01-2022, 06:08 AM)JuiCe Wrote: Actually clearing odometer to FFF, to 0 will make 0 km Clear to value 00h for address 0x00h - 0x1Fh. Then you have 0km and the odo from CAS will written into your replacement cluster. (28-01-2022, 06:08 AM)JuiCe Wrote: VO coding means SG_Codieren with NCSExper nothing else ? Yes, start NCS, read VO, select cluster, use "SG_Codieren" job. |
|||
30-01-2022, 08:49 AM,
(This post was last modified: 30-01-2022, 08:50 AM by JuiCe.)
Post: #36
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Thanks guys.
SO in the end i fixed the thing with KOMBI, but not after that flash attemt and car code attemt, now MOST fiber components dont respond anymore. Here is an ISTA screen. What should i Do/try/test next ? Any fuse on ASK unit ? Do i need Icom with MOST ? |
|||
30-01-2022, 08:52 AM,
(This post was last modified: 30-01-2022, 08:53 AM by Node.)
Post: #37
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Have you connected MOST to a new kombi (and not broke it in the process as you can't bend it too much)?
|
|||
30-01-2022, 09:01 AM,
Post: #38
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Yes, connector is attached fully to the new cluster, i did not even open new KOMBI cluster, just was testing functionality, everything works perfectly.
Want to relate a thing, so first time when i put DCAN cable on car and i hit Process car + Code care, instead of processing every ecu separate, after that, no more navi no more sound. So i guess something happened during that general coding, or during KOMBI reflash after. I just need some hints where to start to investigate/diagnose, without start spend money on parts, because everything worked perfectly and normal (radio ,cd, cdchanger, navi) |
|||
30-01-2022, 09:44 AM,
(This post was last modified: 30-01-2022, 09:52 AM by Node.)
Post: #39
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
Well, if coding broke it, then most probably your coding data was invalid. AFAIR display unit is the MOST gateway on E65 so that could mean that you coded it with wrong settings disabling the MOST. Or maybe you could try battery reset.
|
|||
30-01-2022, 13:55 PM,
Post: #40
|
|||
|
|||
RE: Bricked KOMBI Module with WinFKP ?
|
|||
« Next Oldest | Next Newest »
|
Users browsing this thread:
3 Guest(s)
3 Guest(s)
Return to TopReturn to Content