PDA

View Full Version : Old Toyota, Lexus, doesn't go in fob programming mode - what to do?



ranchero
8th October, 2020, 11:15 PM
Here's very common problem.
Old Toyota and Lexus (1998-2001 4Runner, Land Cruiser, RX300 and many more) require to cycle power lock 10 times in order to get in fob programming mode. With years power lock actuators get "tired" - they are still able to lock and unlock the car, but after second or third cycle they stop moving, as result car does not get in fob programming mode. Some sources suggest to do these 10 lock-unlock cycles manually by the door switch, but I never got this to work either. Everything else is working fine, including original customer's remote, no error lights on the dash.

What is most unusual - sometimes (with some cars) even with such "tired" power lock actuators it's still possible to get in fob programming mode after few tries, so I'm not 100% sure if this problem strictly related to power locks or might be related to other things (for example, to door switches etc).

What are the solutions? I couldn't find alternative ways of going into programming mode. Couple of times I even tried Techstream (for 1999 Land Cruiser) - for that year Techstream only has option of key programming, no remote programming.
Are there any tricks or tools which still will allow to get into programming mode? Obviously, customer will not be willing to replace all power lock actuators on 20 years old car in order to get second remote programmed.

joze
8th October, 2020, 11:31 PM
Hello mate, thanks for your information. Now I’m working on Toyota avensis 2.0 td error code 99 immobilized fault or similar ( now don’t remember exactly ) , the case is I tried with carprog reading mcu on immo antenna hc05e6 without success.

I found one ecu kit from scrapyard with immo antenna key and engine ecu, the only issue is ecu it’s from other engine type and connections are different, so I decided to clone the 93c56 from ecu of scrapyard to correct ecu, now the car no present error 99 but sometimes show error 18 and sometimes error 32(1), I’ve got techstream but when I do a general scan, the system only detect engine ecu.

Do you think if I restore original dump to ecu and resinchro with pin 4 & 13 and later do your process the system will go fine ?

Thanks in advance

Regards


Enviado desde mi iPhone utilizando Tapatalk

ray-ray
9th October, 2020, 12:19 AM
Door lock actuators each door has one. (5lock and 5unlocks=10cycle) if 1 actuator fails it close the loop cycle and your out of programming mode. In most case type1 system obd2 commands are spotty, manual method has it problem also.

ranchero
9th October, 2020, 07:05 AM
Door lock actuators each door has one. (5lock and 5unlocks=10cycle) if 1 actuator fails it close the loop cycle and your out of programming mode. In most case type1 system obd2 commands are spotty, manual method has it problem also.

So basically there is no way around it, door actuators (or at least motors in them) must be changed?