Yes.Quote:
Originally Posted by johnrando
No rebed.
"No flamesuit required"
Printable View
Yes.Quote:
Originally Posted by johnrando
No rebed.
"No flamesuit required"
JR not sure bout you but I'm picking this up tomorrow AM.
Permatex[emoji768] CeramicExtreme Brake PartsLubricant
Attachment 16484
Thanks Seth. I've got some of the red anti-squeal grease from when I did the brakes the 1st time.
That is exactly what I used on the Mini. Green goo.Quote:
Originally Posted by UdubBadger
"No flamesuit required"
This is the supercalifragalisticpurple goo rated to -65 deg which I am sure we will see here in about 2-3 weeks.
:roflQuote:
Originally Posted by UdubBadger
"No flamesuit required"
I usee Neverseez.
http://www.neverseezproducts.com/purenickel.htm
My dad's 04 M54B30 ZSP with 60k miles had an SES light with a P2237 code, O2 sensors. Looked into it. Seems like 50% of cases are fixed from a software update.
He went to a mechanic that said he could do it. Mechanic started it and got the warning that if they continue the update could damage the DME controller. So he stopped. I guess he hasn't seen that before? Software was AutoLogic.
Is that a generic warning, like Shark Injector could corrupt the DME if done wrong as an example.
Any ideas?
Hmmmm, it could be or it could actually be a bad O2 sensor. I've not personally heard of software throwing a code like that but I suppose it's possible. I mean I used to throw vacuum codes on my E90 when I had a cold air intake and muffler delete. :dunno
Was more looking for insight on the software update itself. My dad's car was built in 2003, I don't think it's had any updates since then, so it's possible there's newer stuff out there.
Question is, why would an update corrupt the DME?