KOLEOS DF299 PROBLEM

Hi everybody... i am searching for help to bypass this error... The car is going from one workshop to another... I read ECM MEC121 and UCH xdt384... Someone teach me how to see syncro bytes, so i can see ECM and UCH are in syncro, also ELV seems OK... Card keys are prefectly programmed, all seems to be ok, but immobilizer shows active.
The question is, is there something else that can block system? they told me about PARKING  BRAKE supply can block system... The only other place i have faults are in parking brake, but despite faults it is working. Anyone can help me ? THANKS

whats is story of car

engine

year

whats diag tools you have

whats is story of car

engine

year

whats diag tools you have

Thanks for answer... Year, 2011, 2.5 gasoline engine, that is why it has mec121 computer... What i dont have is car history.. Aparently owner stop the car, and then he try to start it and no engine pulse to coil and inyector because immo active.

Because of df299 fault in UCH, there is literature about ECM losing inmo syncro. Afortunately, i can acess to ecm and uch reads from other koleos and syncro bytes where discover, and that was checked and is fine. Syncro immo data is en microcontroller of ECM, not in serial eeprom.
What tool i have? i have already access to full renault account and clip... and when i try to reestablish inmo, system says is already programmed, and that is correct.
Car is in very good shape... the only faults are in UCH and in electric parking brake.

good . I have the same problem, did you manage to solve it? please help

Enviado desde mi Redmi Note 9S mediante Tapatalk

good .  I have the same problem, did you manage to solve it?  please help

Enviado desde mi Redmi Note 9S mediante Tapatalk

Hello. We managed to start the car today. And the error was the same as in the first post. The problem turned out to be in the UCH block. The dump needs to be written there, not trained. As recorded. three times the ignition is ON / OFF and then you can start. We have been struggling with this error for almost two months.

I think your problem will reappear, I have had a similar problem with the key. Another key was programmed and everything returned to normal. I take the opportunity to ask you, with what tool have you read the motor ecu? Can you tell me have you done a full reading or only the eeprom?
I await your comment