BMW Forum - BimmerFest BMW Forums banner

Problems with Headunit / IDrive after BimmerCode coding

6.4K views 15 replies 4 participants last post by  br33zy  
#1 ·
Hoping someone may be able to provide some assistance / insight..

The situation…

Vehicle: ’23 F56 Mini Cooper S
Tools: Bimmercode on iPhone 13 Pro and vLinker BM+ Bluetooth tool

Attempted last night to make a few changes and code them to the Headunit module (remove nag screen, remove volume displayed when changing volume). Upon coding, it got right to the 100% mark then failed…

This left the Headunit inoperable (Screen is dark, not functioning, etc..). Just to say, with the vehicle on I can see the screen backlight so clearly getting power, etc..

When I connect with Bimmercode, that module (Headunit) has a red circle. When I enter, it recommends restoring from backup. Gets interesting here. Majority of the time, no backups are shown available, but if I keep trying I can occasionally see the backups listed. When the DO appear, coding it back has failed each time. Looks like its about to complete then errors out with no change to the functioning of the head unit / iDrive.

I don’t yet have a ENET cable, but do have one on order to arrive on Friday.

I do have files for Esys, BimmerUtility, and the PSdZData_Lite data. Would LOVE to get this fixed before the cable arrives Friday, but if not, any other insight would be appreciated as well. Still not 100% clear on the utility (labeled as E-Sys_Setup-3.40.1-BimmerUtility and the E-Sys_Setup-3.39.1-09f7b0_64bit-JDK11) files (do I need, one, the other, both for this).

Hopefully all of that makes sense and any assistance / insight anyone can offer would be greatly appreciated.

@shawnsheridan , hope you don’t mind a tag as you seem to be a resident expert..
 
Discussion starter · #13 ·
Alright… found the tip to add empty dist files in the chassis folders and now see them listed. Not sure which of the F056 I should select, one shows F056_22_03_564…. Other starts with F056_21_11_565.
According to a screen shot I kept from BimmerCode the current I-level in the car is F056-22-3-540. Safe to use the 565 version??

I did try that one, connected fine, read and activated FA, got an error reading VCM but could read ECU. Is it ok to do this (code to inject missing CAFD) using the ECU read?

@shawnsheridan going to try one last time to snag a min of your time as I’ve seen you post in pretty much every place I’ve seen someone encounter these issues.

just to keep together I’m trying to perform the steps below on the head unit module. If anyone can confirm the naming convention I should see that as in a F56 as well that’d be appreciated.
 
Discussion starter · #12 ·
Next problem… When I go to connect to the vehicle, I can see the VIN in the window so I appear to be connecting properly however I cannot see any of the various series listed in the top portion of the window to select from. I did decompress the most current PSdZData_Lite data and it is located in C:\Data\psdzdata

Version file in the PSdZData folder says its 4.36.12.

Any thoughts as to why I would not be able to see them listed? Did also confirm in settings that the path is set to c:\Data. If I change that it recognizes the data doesn’t exists and asks to correct so it would “seem” that E-Sys is finding it..

Again, help is appreciated!
 
Discussion starter · #9 ·
Looks like the cable should be arriving today (bonus!).

My understanding / approach at this point will be to install E-Sys, copy the data files into the appropriate folder, connect, launch, and follow the steps I posted earlier (for the appropriate Headunit module). Pasted again below.

Anything else I should be aware of before I attempt? Surely don’t want to risk going from bad to worse here.

@shawnsheridan , sorry, but tagging you one more time before I attempt in case you have any input as well since it looks like you’ve guided others in similar scenarios.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on FEM_BODY => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on FEM_BODY (the ECU itself not the underlying CAFD) => Select CODE

EDIT - Vehicle also came with factory wireless CarPlay, should I expect this would be properly restored in this process or is that potentially another separate bridge to cross…?

Truly hoping I can get this up and running again later today..
 
Discussion starter · #4 ·
Lesson learned, indeed… Can you help me understand the difference between esys and BimmerUtility?

Still learning here, but I’m usually a pretty quick study. ;)


The bricking cases with these pseudo tools are increasing. Avoid these especially in last two years cars.
If there is a chance for resurrection, you dont need bimmerutility but only esys
 
Discussion starter · #2 ·
Just to add, I did stumble on this set of instructions (different module clearly), but is it fair to say this should be the appropriate steps to inject CAFD back for the Headunit module / that is the likely best first step toward resolving?

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on FEM_BODY => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on FEM_BODY (the ECU itself not the underlying CAFD) => Select CODE