There've been a number of threads for the various Connected updates, and in each of the threads there have been a handful of replies (like my own) saying that they cannot perform the update. I wanted to dig a bit more and start understanding what's going on.

My current software version is MX-2.7.3/TX-2.7.3 (which I believe that the others having problems are at the same level). This seems to have been a popular version for those MINIs purchased in early 2011 (current working theory) regardless of the body type (I've seen some MCS' with the same issues).

First off, the MINI Connected Update website is absolutely horrid. Looking at the bimmer forums, I found a link to the ConnectedDrive website which is a lot more useful (IMO). This allowed me to put in my VIN and find all versions available to download.

As a few others have found, I downloaded the version from the BMW website and compared it to the downloads from the MINI website and found that they're exactly the same (so I feel safe proceeding with looking at the BMW websites options). For giggles, I downloaded the latest (again) and tried; unsuccessful (I like to start these things with a little bit of dashed hope).

I then downloaded all the available versions and found that they're all compressed tar files containing an XML file and the various updates. Opening the XML file I was able to start forming some theories; but first the facts. Each update's XML file contains a listing for the min/max versions associated with the updates available in that package. As such I found the following versions looked for by each update (in parenthesis is the version of the associated update):

UPD01000 -- 1.10.21 or 1.11.1 (1.12.0)
UPD01004 -- 3.4.31 (MX/TX3.5.4), 2.5.21 or 2.5.25 (2.6.4), 1.10.21 or 1.11.1 (1.12.0)
UPD01005 -- 3.4.31 (MX3.5.4, TX3.5.5), 2.5.21 or 2.5.25 (2.6.5), 1.10.21 or 1.11.1 (1.12.0)
UPD01006 -- 3.4.31 (MX3.5.4, TX3.5.6), 2.5.21 or 2.5.25 (2.6.6), 1.10.21 or 1.11.1 (1.12.0)

(While they do call out min and max separately, they set each to the same version number.)

So, what does this tell me (current theories):

• For a car (like mine) with the 2.7.3 software installed, it's at a higher level than all associated versions (2.6.6 being the highest released so far).
• A "jump" to the 3.5.* update line doesn't seem to be as automatic as I'd hoped.

I've read in other threads that the only remedy is to take it to MINI and have them flash; has others done so? If so, what version did they ultimately receive? I'd like to think there's a way to do this without having to make a trip to the support bay.

 

When I updated mine, I went through the Mini Connected site and downloaded the appropriate file. If I remember correctly, the file was a .BIN or .ZIP file. I did not uncompress it prior to copying the file to a USB flash drive.

Not sure if you are using the same file that I did...but I had no problems updating.

 

Sorry if I didn't mention (and added to confusion), when I attempt to update the firmware I have used the .BIN file as written in the manual (save the .BIN file to the root of the USB stick). Some have said you need a USB drive with FAT32 or other incantations, all of those have resulted in the same message:



FYI, the latest UPD01006 update downloads from MINI as a .ZIP file that needs to be uncompressed (or else the car can't find any available updates). Doing so still doesn't allow my car to update from 2.7.3, but just wanted to mention.

 

I am having the same issue and am dreading having to go to the dealer to update it. Have you tried to edit the XML file to allow for our versions? Just a thought.