tha5150

i searched a bit and i am reading that people are either hearing noises or it just isn't working.

my issue is that when i turn the **** to 4LO or 4HI, i have no 4x4. Got stuck, someone with an 06 pulled me out and said my 4x4 actuator isn't working. when i turn the **** you would hear a very faint click. when he turned his, i heard a motor of sort near his t case, and his 2 front hubs lock. so i am assuming it is this 4x4 actuator.

question is, how can i test and verify what it is for sure? i am told there are several components that could go bad and needing replaced but want to know the culprate before i start throwing money into it.

So how do i go about diagnosing this? if nothing comes up on a system scan, what the heck do i do!?!

gone postal

Lovingly tap the 4x4 actuator motor with a Ford wrench while trying to engage. Takes 2 people, but it has solved the problem for others.

tha5150

assuming this will try to free something up? obviously something is damaged or something.

looking for a way to diagnose this though.

gone postal

That's actually the diagnosis. If the switch engages the relay, but the actuator motor doesn't move, then it's either the wiring to the actuator motor, the relay, or the motor. If the motor engages with the gentle (sarcasm) application of a Ford wrench, then that (the motor) was your issue.

Given the number of times this has popped up on the board, the most likely issue is the motor isn't moving.

tha5150

took the actuator off the t case, turned 4lo and hi and back to 2wd and turns just fine. i guess next up is to check the vaccum lines? how do i test this out properly? i called ford to check my warentee and it just ran out. they said 9 times out of 10 it is the solinoid on the firewall? 40 bucks to replace that but if that isnt the issue i could not return it. would rather test this whole thing out myself first.

so whats next to test and how do i do it?

'08f150stx

http://www.ford-trucks.com/forums/83...then-some.html

tha5150

VERY much appreciated, nice write up. i was thinking this all worked backwards to what it really works. looks like it is either a leak in the lines or the firewall IWE