3.0 Misfires due to MAF?

[Dan255]

I have an 04 3.0 6MT that was having misfires on every cylinder. I thought this was due to the MAF seeing as when I unplugged it, the misfires all cleared up and I had no codes other than MAF/IAT codes. So I replaced the MAF with an aftermarket one and it seemed to be ok for about 100 miles, but now I'm having the same issue, rough idle with codes for every cylinder, but they clear up when I unplug it. I was thinking it might be a faulty aftermarket MAF so I took one out of a 2.7t to try, and no luck with that either. The car has an EVO MS intake, JHM catless downpipes, and a Milltek exhaust, otherwise the engine is stock with 170k. Any ideas? Thanks, Dan

[imnuts]

First thought is to get an OEM MAF. To verify that is your problem though, see what code or codes you have stored on the ECU. If it's just misfire codes, log your car and see what the MAF readings are as well as the AFR or lambda and your fuel trims.

Sent from my Pixel XL

[Dan255]

I did have bank 1 and 2 system too lean codes this morning, but I cleared them because I figured that's due to the fact that my cats are gone and I haven't had the car tuned yet (I did the DPs when I put the new MAF in, will be doing a JHM tune). I just don't think it has anything to do with the sensor itself seeing as I've had 3 different sensors (2 of which were OEM) and I even tried putting the aftermarket sensor in the running 2.7t to test it and it ran fine. I'm leaning towards primary o2s now but I don't really want to invest in those until I have a pretty solid idea that that's my issue.