Xoutpost.com

Xoutpost.com (https://xoutpost.com/forums.php)
-   X5 (E70) Forum (https://xoutpost.com/bmw-sav-forums/x5-e70-forum/)
-   -   BRICKED!!!! A Cautionary Tale. UPDATE! (https://xoutpost.com/bmw-sav-forums/x5-e70-forum/108117-bricked-cautionary-tale-update.html)

Zulu95 04-19-2018 10:29 AM

Quote:

Originally Posted by lordshin808 (Post 1132944)
Why don't you give the name and location of your "Expert" so others know not to use his services?

All in good time. I'm still waiting to present the final bill.

740iS 04-19-2018 12:00 PM

Quote:

Originally Posted by Zulu95 (Post 1132938)
The proximate causee of the event has ceased communication and gives every sign of evading financial responsibility.

I sure hope he doesn't pull a disappearing act on you. If so, sing his name/handle/etc... on every forum/FB group you can find. This kind of thing can't go onto the next guy.

blue dragon 04-19-2018 06:58 PM

Let me play the role of devil's advocate, you chose to assume the risk of using an independent coder for a less expensive price than BMW. Was there no communication about the possibility of modules being bricked and you being responsible if that happened? Did you assume that the coder would pay if there was an issue?

Its a well known fact that modules can get bricked, even when BMW does the coding. The FRM3 module warranty extension was due to his exact type of behaviour, but how many people paid out of pocket before BMW chose to acknowledge the problem.

I am not saying that you getting reimbursed is not the right thing, I am asking did you just assume that would happen?

Zulu95 04-19-2018 08:04 PM

No mention of "Brick" potential. "Simple process where I read the CAS and then code a key and enter it into the module. After that I cut the key on my laser cutter. Does not take long at all." That is the best of what I remember.
After it happened: "Don't worry this is on me." followed by "Do not understand what happened. This should not have happened. It's on me."
If we assumed anything it was that the "expert" would most likely disappear into the night and we would have to eat his mistake. We assumed that from the moment he left to go program keys for somebody else. Then we got right on to dealing with it and arranging to get the vehicle to BMW to get it fixed.

pshovest 04-20-2018 07:42 AM

Reading modules doesn't brick them. Writing to modules with wrong code, low voltage or interrupting writing, bricks them. BMW says 13v minimum for coding/programming. Ignition on, DRL's lit and fan running can put system voltage in low 12's, very risky for coding/programming.

Zulu95 04-20-2018 08:05 AM

pshovest:
Any or all of the above could have been part of the conditions present at the time of "Bricking".


ard 04-20-2018 11:10 AM

As I recall, BMW procedures call for use of a battery charger to be attached to car when coding, no?

Zulu95 04-20-2018 03:12 PM

You are correct. Most BMW coding I have experienced ran for many hours. I guess, as the usual run of key coding lasted only minutes, hubris and or ignorance of voltage requirements prompted the elimination of this safety factor.

ard 04-20-2018 05:39 PM

I am thinking at some point a module here or there switched on or something happened to allow the voltage to drop- not really 'running out of power' per se, but enough to corrupt whatever was being done at that moment. Bummer

Zulu95 04-24-2018 02:14 PM

BMP.


All times are GMT -4. The time now is 10:09 PM.

vBulletin, Copyright 2026, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.6.0
© 2017 Xoutpost.com. All rights reserved.