1. Welcome to Tundras.com!

    You are currently viewing as a guest! To get full-access, you need to register for a FREE account.

    As a registered member, you’ll be able to:
    • Participate in all Tundra discussion topics
    • Transfer over your build thread from a different forum to this one
    • Communicate privately with other Tundra owners from around the world
    • Post your own photos in our Members Gallery
    • Access all special features of the site

P0420 and P0430

Discussion in '1st Gen Tundras (2000-2006)' started by socomoby, Apr 5, 2024.

  1. Apr 5, 2024 at 5:15 PM
    #1
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD
    Back again folks. I’m getting the dreaded P0420 and P0430 codes. Been doing a lot of reading and it seems the consensus was that these two showing up together is usually a red herring for bad upstream sensors. To be thorough, I replaced all 4 sensors with Denso’s and yet I’m still getting the codes. I don’t have a fancy reader but what I have noticed is that the two upstreams read the nearly identical outputs under load and idle.

    The downstream, though once all over the place, are both now near identical under load; however at file, B2S2 is still erratic. Not nearly as much before the replacing, but still so.

    Open to any suggestions. Luckily my county doesn’t perform monitoring anymore so I have all the time to figure this out at the expense of maybe burning more fuel and possibly a cat. I’m leaning more toward there being a bad cat myself
     
  2. Apr 5, 2024 at 5:22 PM
    #2
    shifty`

    shifty` I’ll teabag a piranha tank

    Joined:
    Jun 20, 2020
    Member:
    #48239
    Messages:
    28,243
    ATL
    Vehicle:
    '06 AC Limited V8/4WD
    (see signature for truck info)
    Them showing up individually is likely a sign of one sensor on the impacted bank being being bad, and I'd replace both upstream and downstream on the affected bank.

    Seeing them show up together is a whole other can of worms IMHO. I'd expect to see that if the truck had aftermarket cats, aftermarket headers/exhaust, a ground/wiring fault, or potentially other stuff in that vein (exhaust leak, or similar). We've seen people post that throw both codes and used aftermarket cats or are running shorties/long tube headers.

    If it was a bad cat, I'd be shocked to see BOTH clogged at the same time, unless a previous owner (or original owner) ran with bad upstream sensors or some other condition that would cause excess clogging of the cat.

    I'd start by really taking a close look at wiring based on your middle paragraph.
     
  3. Apr 5, 2024 at 5:34 PM
    #3
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD

    Man I really hope it isn’t wiring. That seems like a major pain in the ass to re-wire if it is. I will say B2S1 was surprisingly easy (ish) to get to. Don’t know if that’s factory design or not. It didn’t look tampered with though. I’d say it also be strange if both banks had bad wiring, no?
     
  4. Apr 5, 2024 at 5:36 PM
    #4
    shifty`

    shifty` I’ll teabag a piranha tank

    Joined:
    Jun 20, 2020
    Member:
    #48239
    Messages:
    28,243
    ATL
    Vehicle:
    '06 AC Limited V8/4WD
    (see signature for truck info)
    I'm thinking more along the lines of ground issue for wiring. It'd be something that was shared between both. But I think a leak is more reasonable. Do you know if the cats are OEM? Any evidence they've been replaced or had been cut out/stolen at any point?
     
    FrenchToasty likes this.
  5. Apr 5, 2024 at 5:37 PM
    #5
    FrenchToasty

    FrenchToasty The Desert rat, SSEM #5/25, 6 lug enthusiast

    Joined:
    Sep 15, 2019
    Member:
    #36156
    Messages:
    18,319
    First Name:
    Mo
    The SoAz….. big surprise
    Vehicle:
    2006 DC 4.88s Elocker and some other trippy stuff
    Bone stock
    Those codes can also be thrown by intake vacuum leaks, so check for those as well. Or even exhaust leaks can cause that too
     
  6. Apr 5, 2024 at 5:39 PM
    #6
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD

    No cats look stock. The triangular flanges also are the most rusty spot on the ole gal despite being a relatively clean frame truck.
     
  7. Apr 5, 2024 at 5:41 PM
    #7
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD

    I thought about this but I didn’t see any infiltration via the IAT, Throttle response and MAF live data.

    I did have an Expedition in the past that had manifold leaks and ticked. I have noticed what sounded like a manifold leak but I can’t find a crack anywhere
     
  8. Apr 5, 2024 at 5:45 PM
    #8
    FrenchToasty

    FrenchToasty The Desert rat, SSEM #5/25, 6 lug enthusiast

    Joined:
    Sep 15, 2019
    Member:
    #36156
    Messages:
    18,319
    First Name:
    Mo
    The SoAz….. big surprise
    Vehicle:
    2006 DC 4.88s Elocker and some other trippy stuff
    Bone stock
    Check hoses for cracks visually or spray around injectors and intake with carb or propane. Power steering and brake booster use vac as well
     
    des2mtn likes this.
  9. Apr 5, 2024 at 5:46 PM
    #9
    shifty`

    shifty` I’ll teabag a piranha tank

    Joined:
    Jun 20, 2020
    Member:
    #48239
    Messages:
    28,243
    ATL
    Vehicle:
    '06 AC Limited V8/4WD
    (see signature for truck info)
    I mean, I feel like that's pretty typical. Anything iron from the heads to just past the cats is seeing the most heat and tends to rust/freeze on anything, in any climate. Is it possible you may be leaking at any point between the two sensors?
     
  10. Apr 5, 2024 at 6:04 PM
    #10
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD

    I thought that but I didn’t see anything. I’ll try to get another look tomorrow. Like you said, it’s weird that both bank’s sensors and their sisters are behaving near identical on the live data. That’s quite the coincidence.
     
  11. Apr 5, 2024 at 6:04 PM
    #11
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD

    I’ll get some carb clean and check it out. I doubt that’s the case but you can never be sure, especially with a vac leak
     
  12. Apr 6, 2024 at 7:49 AM
    #12
    2003DC

    2003DC New Member

    Joined:
    Feb 3, 2022
    Member:
    #74093
    Messages:
    73
    Be 100% sure that you do not have leaks anywhere in the exhaust system. The connections between each pipe must be tight and the gaskets at the fitting must be sealing. I've had codes on two different occassions that were caused by a loose connection between the y-pipe (after the cat) and the next pipe that connects to the muffler. I also had a code because one bolt holding an oxygen sensor had come loose.
     
    socomoby[OP] likes this.
  13. Apr 6, 2024 at 7:50 AM
    #13
    2003DC

    2003DC New Member

    Joined:
    Feb 3, 2022
    Member:
    #74093
    Messages:
    73
    (each causing air (oxygen) to be drawn into the system and triggering a code)
     
    FrenchToasty likes this.
  14. Apr 6, 2024 at 11:26 AM
    #14
    shifty`

    shifty` I’ll teabag a piranha tank

    Joined:
    Jun 20, 2020
    Member:
    #48239
    Messages:
    28,243
    ATL
    Vehicle:
    '06 AC Limited V8/4WD
    (see signature for truck info)
    I mean, in theory, you would expect the upstream to be nearly identical, combustion should nearly identical between both banks. And in truth, what's seen on the other side of the cat should be identical also, if both cats are identical. But say someone replaced or even just removed the cats at some point, and there's a gasket required between the flanges, but it had disintegrated so the person doing the work didn't realize one was required ... or the O2 sensors are supposed to use a gasket. Or maybe on of the three studs on the flanges is broken, but you can't see it. Lots of stupid shit could happen to allow air in.

    This isn't me telling you to go tear it all apart. Just spitballing some scenarios where I could see the ECU getting bad reads from the sensors.
     
    socomoby[QUOTED][OP] likes this.
  15. Apr 6, 2024 at 5:51 PM
    #15
    socomoby

    socomoby [OP] New Member

    Joined:
    Jan 25, 2024
    Member:
    #110844
    Messages:
    88
    Gender:
    Male
    Vehicle:
    2006 DC V8/2WD SR5 LSD
    Thanks fellas. I couldn’t find a compromise in the system anywhere. The flange bolts were a little loose when I PB pissed the surface crud off. Waiting to see if that will do anything. Like I said, we don’t test here so it’s not urgent but I’m OCD and seeing that light on with the possibility of getting even worse mileage definitely screws with my mind.

    The only other off-hand scenario I can think of is that the original owner Pitt a cold intake on and moved the MAF location. The second owner (his son ironically) took it back to stock before I got it. Right back in stock’s location. However I figured if there was an issue there it’d be either with the sensor or the intake itself.
    @FrenchToasty i checked and saw no intake issues. MAF is clean and live data reads smooth as well.
     
    FrenchToasty likes this.
  16. Apr 6, 2024 at 7:03 PM
    #16
    shifty`

    shifty` I’ll teabag a piranha tank

    Joined:
    Jun 20, 2020
    Member:
    #48239
    Messages:
    28,243
    ATL
    Vehicle:
    '06 AC Limited V8/4WD
    (see signature for truck info)
    Just for shits and giggles, if you've never had the negative battery cable off for 10min, you may want to do that, just to force a re-learn. Not remotely suggesting it'll fix issues - may make codes go away. But will at least force a baseline relearn of EFI operation. You should do same if you kill the CAI.
     
    socomoby[OP] and FrenchToasty like this.

Products Discussed in

To Top