'15 headlights won't shut off

Haydenatx

Member
Recently my '15 trail headlights started acting up. I have the TRS HID kit.

When I shut off the truck and lock it the headlights remain on. They used to shut off in like 30 seconds or when double clicking the lock button.

I'm afraid the HID kit may be the root of it. Anyone else have this issue? I couldn't find any other threads about it.

https://vimeo.com/185889271
 
Register to hide this ad
If you can't get them to shut off at all no matter what, my guess would be the relay in your kit is bad. If the coil on the relay isn't getting voltage, and the lights are on, then that is the problem.
 
Sounds like the control circuit for the TRS HID kit is malfunctioning. It should be getting a signal from the headlight circuit, which would tell it "Turn off after 30 seconds, or when you Press Lock Twice" since a lot of those kits tap into the headlight switch circuit to activate the lights.
 
If you can't get them to shut off at all no matter what, my guess would be the relay in your kit is bad. If the coil on the relay isn't getting voltage, and the lights are on, then that is the problem.



They'll shut off if I turn the switch in the truck to off. They just don't automatically shut off anymore. Thanks for the info! Sounds like I need to contact TRS.
 
Sounds like the control circuit for the TRS HID kit is malfunctioning. It should be getting a signal from the headlight circuit, which would tell it "Turn off after 30 seconds, or when you Press Lock Twice" since a lot of those kits tap into the headlight switch circuit to activate the lights.



Thanks for the reply! Probably time to reach out to TRS customer service
 
Hi Haydenatx,

Make sure that the stalk selector switch is in the AUTO position; and not in the manual ON/OFF mode! If that checks out okay, disconnect the NEG battery cable for a minimum of four hrs... doing this will MASTER RESET the main body ECU compu network, and forcing it to function in it's default (factory) protocol parameters! Just like your windows OS every now-and-then, the computer needs an opportunity to delete it's temporary files and history logs stored in it's registry (Cashes); your ECU CANbus system stores temp files/hist-logs too! ...More than likely that's what is causing the problem, Please let us know!

rig, Cheers!
 
Hi Haydenatx,

Make sure that the stalk selector switch is in the AUTO position; and not in the manual ON/OFF mode! If that checks out okay, disconnect the NEG battery cable for a minimum of four hrs... doing this will MASTER RESET the main body ECU compu network, and forcing it to function in it's default (factory) protocol parameters! Just like your windows OS every now-and-then, the computer needs an opportunity to delete it's temporary files and history logs stored in it's registry (Cashes); your ECU CANbus system stores temp files/hist-logs too! ...More than likely that's what is causing the problem, Please let us know!

rig, Cheers!

No auto on/off lights on mine. I sometimes leave mine in the on position and the lights will go off like 30 seconds after I lock the car or right away if I press lock twice and I got an HID kit on mine as well. There has to be something wrong with his relays on the HID kit.
 
Do the parking lights stay on also? If so I would lean toward it being a problem on the 4runner programing side. If the parking lights go off, I would say its an HID kit issue..
 
Do the parking lights stay on also? If so I would lean toward it being a problem on the 4runner programing side. If the parking lights go off, I would say its an HID kit issue..

Ah! The parking lights do stay on (I just noticed that on the video above). Maybe I should unplug the neg terminal and let the ECU reset?
 
This has happened to me a few times, randomly. In each case I just had to start the truck up and shut it off again, and then they turned off as normal when I locked it.

It has not happened enough to bother me, and it's possible it's happened more than I realized - but maybe eventually shut off, as my battery has never died as a result.
 
I would look at the program of the delay (instructions in owners manual) and make sure it is set correctly. If it is I would do an ECU reset.
 
Negative terminal has been unplugged. Now I wait... Will post update when finished. Thanks everyone for the input
 
Alright, resetting the ECU by unplugging negative terminal for 4 hours worked!:reddance:

It sputtered on the first start up and died. But on the second go it started up and remained running. Flipped the lights on, shut down the engine and everything was back to normal.

Thanks again for everyone's help!
 
Welllll it happened again unfortuntely. I shut the truck off this morning and walked away. Double clicked the lock button on the remote, it locked but the lights stayed on. I started the truck and shut it off, tried again and it worked. This is sketchy.
 
Welllll it happened again unfortuntely. I shut the truck off this morning and walked away. Double clicked the lock button on the remote, it locked but the lights stayed on. I started the truck and shut it off, tried again and it worked. This is sketchy.

Time to give TRS a call to see if they have encountered this before.

TEST TIME:
Remove the HID bulbs and the HID trigger wire from the OEM headlight plug.
Install OEM bulbs, push OEM headlight plug harness back on.
Run for a couple weeks (if need be) like this and see it the situation duplicates.

It is strange that the running lights are staying on....sounds light lighting system error, not HID error.
 
It sputtered on the first start up and died. But on the second go it started up and remained running. Flipped the lights on, shut down the engine and everything was back to normal.
!

this happens every time you unhook the battery. Get used to it if you plan to unhook the battery for frequent electrical mods!

freaked me out the first time when i traded out the battery at the dealership with the battery from the vehicle i traded in, sputtered and turned off, started it again no issues.
 
So bringing up an old thread but was this resolved? My 16' is currently doing the same thing [MENTION=118406]Haydenatx[/MENTION]
 
Last edited:
I have been dealing with this same problem. It’s random but happens about once a week. 49k miles of no issues and now this. Ugh
 

Members online

Forum statistics

Threads
278,312
Messages
3,554,083
Members
248,016
Latest member
Advally Service

Trending content

Back
Top