![]() |
![]() |
![]() |
![]() |
![]() ![]() |
![]() |
BMW Garage | BMW Meets | Register | Today's Posts | Search |
![]() |
![]() ![]() |
BMW 3-Series (E90 E92) Forum
>
Help! Car won't start after accidentally "Process Car" during FA write
![]() |
![]() |
12-26-2024, 05:50 PM | #1 |
VJE90
![]() 13
Rep 31
Posts |
![]()
After 17 years of successfully DIY all repairs on my 2007 E90 328i I'm now about to face defeat for not being able to figure out how to fix it.
Problem: Car won't start, not even crank. I can hear the fuel pump running but that's it. Background: This all started when I replaced a dying lead acid battery with an AGM battery. I installed the battery with no issues and then moved to coding the change of battery type and registration. As I was making the VO change and it was time to FA write I accidentally press "Process Car" and once I saw that it started I knew I couldn't do anything else until I got "coding ended" on all the modules. ![]() Surprisingly I didn't get any NCSExpert errors so I assumed that the modules update with no issues. I ran ISTA+ and all modules were there. There were some errors that I cleared and didn't come back but one A0B4. So I went ahead and replaced the starter with a brand new one but the car still wont start. I also tried to reset the modules individually but no success. BTW A0B4 comes back every time right after clearing it. Request : ![]() I have the Bimmergeeks cable and their BMW Tools download that I have used in the past for other codings and diagnostic with no issues. I'm in the DMV area (Montgomery County) if there is someone local who can help. |
01-26-2025, 10:18 PM | #2 |
New Member
2
Rep 5
Posts
Drives: BMW 325XI
Join Date: Jan 2025
Location: Ohio
|
Similar problem here....started a few weeks before you.
I have also done some programming/coding/module replacement before. This time, I replaced the steering cluster unit, due to errors. I wanted to try to use Ista P. (2006 E90 325xi) x 2.
Bought the second one at an auction and performed body work on it myself. I drove it for 5 months. Ista P showed a "plan" for Programming and coding. Although, I did have a car charger on it, I did not select out modules that really didn't need it. I let it go for almost all of them. Then the errors happened... Only the first 3 modules updated--JBBF, MRS5 and CAS. DME was apparently next and guess what? It lost partial info, car failed to start, but when ignition is on, fuel pump continues to run. I checked the e-box under the hood, replaced the relays, etc. I didn't have an FA or VIN backup. So I had to create one. (It wasn't too hard since I did have the FA from my other car). Still, was unable to reach the DME for communication. I know I'm getting closer to it. i also replaced my battery. I fixed my Airbag issues, cleared other module errors except for a few. The remaining errors that came immediately back pointed to communication or mis-alignment of VO status issues on related modules. Sometimes INPA reads the DME, but no VIN, and sometimes other info. EGS doesn't show up anymore, 2 weeks after the coding failure. So found out that the VO probably didn't match the VIN. Using NCSexpert has helped a lot, but encountering some errors--mostly with the FRM. Decided to look at the FSW-PSW trace file for it. This thing was over 13,000 lines and I looked through it all to the end. On the other car, the FRM was only 2,033 lines! I found that the FRM had several versions, mixed English and German, and even different series coding. (eg, E65, E88, E92, E93...) I am wondering if the FRM module stores the errors as well as the settings for the options. No wonder the car is confused! So that is what I am doing next. Trying to fix the FRM coding. But some advice would be welcome! I have spent 3 days trying to scour through the threads. (Splitting that time between working on the other car's mechatronic.) Hate not being able to drive them. Next thing I will try is default coding the FRM, after getting the VO correct and then Flash, or default code the DME...Not sure If I can delete the FsW-PSW trace file contents.... Always delete as much errors from the INPA information on modules before coding. You might have to do this a few times before moving to coding. Also, code each module individually, not the whole car in one sitting. Battery dies, then coding dies out in the middle. I believe that is what damaged the DME. All following modules did not get updated. ![]() |
Appreciate
0
|
![]() |
Bookmarks |
|
|