[cossie1]

Originally Posted by muniz_ri

Thank you for this.

For everyone's knowledge...it seems that Bimmertech began locking down their updates with this version (10.2.18.15). I changed the MCU name to upgrade.bin and flashed it onto my Carlinkit unit. The screen turned black and the unit became completely unresponsive.

Flashed back to the latest available Carlinkit MCU and all is good once again.

Well that saves me a job of trying it then

[Minims]

Ok So it seems the last BimmerTech MCU update we can use on an Andream Unit is the one from 4.1.2020 ? Or this for Carlinkit only ?

[cossie1]

Originally Posted by Minims

Ok So it seems the last BimmerTech MCU update we can use on an Andream Unit is the one from 4.1.2020 ? Or this for Carlinkit only ?

It's the same as the carlinkit mcu and yes you can use it on the andream unit.

[muniz_ri]

Originally Posted by Diirek

Soooooo.... I loaded the update, connected to iDrive bluetooth, reset everything and made my first successful phonecall with no echo. The call is being routed through the iDrive but is still being controlled through AA.

Say what you will about Bimmertech, but we've been troubleshooting this issue for almost a week now. The best part is that they're taking my input/suggestions and we've come to a working resolution.

I only had a few minutes to test but so far didn't run into any bugs. Link to the download is here:

https://drive.google.com/drive/folde...CAFsdAcMzohc6Q

I'm probably not supposed to be sharing this beta update, so please use at your own risk. Once again, this is for the Bimmertech MMI Prime running the latest MCU I shared a few pages back.

Do you know if they completely disabled the mmi's bluetooth signal or somehow just gave the iDrive bt priority over the mmi's bt signal?

[corduroy]

How can you tell if the phone call is going through idrive and being controlled through AA? I want to try something and just want to be sure. Thanks!

[Diirek]

Originally Posted by muniz_ri

Do you know if they completely disabled the mmi's bluetooth signal or somehow just gave the iDrive bt priority over the mmi's bt signal?

It seems like they disabled the autoconnection of the bluetooth that happens when you connect via usb (or wirelessly).. I deleted the mmi from my list of bluetooth devices and it no longer connects.

Looking at my phone when I'm connected, the only bluetooth connection is to my iDrive.

[Diirek]

Originally Posted by corduroy

How can you tell if the phone call is going through idrive and being controlled through AA? I want to try something and just want to be sure. Thanks!

I tried to make a call before reconnecting to the idrive bluetooth to see if it would work over usb, but it only gave me an option to use speakerphone on my phone.

Once i connected BT to my idrive, it worked through my car audio again.

Also, when i was making calls before with the echo, the sound quality was not great - it popped and cracked. Now it sounds much better, just like it did before i installed the mmi.

[muniz_ri]

Originally Posted by Diirek

It seems like they disabled the autoconnection of the bluetooth that happens when you connect via usb (or wirelessly).. I deleted the mmi from my list of bluetooth devices and it no longer connects.

Looking at my phone when I'm connected, the only bluetooth connection is to my iDrive.

Originally Posted by Diirek

I tried to make a call before reconnecting to the idrive bluetooth to see if it would work over usb, but it only gave me an option to use speakerphone on my phone.

Once i connected BT to my idrive, it worked through my car audio again.

Also, when i was making calls before with the echo, the sound quality was not great - it popped and cracked. Now it sounds much better, just like it did before i installed the mmi.

That makes sense. I was wondering if the bt "auto-connection" was an android function or a function of the mmi. Sounds like it's a function of the mmi which is how they were able to turn it off.

I had my mmi in a faraday bag for a while but it apparently wore out and stopped blocking the mmi's bt signal. While it worked, I was able to make and receive calls exclusively over the iDrive bt connection and control the phone using either the iDrive menu or the mmi. It worked very well which sounds like your experience now with this beta update.

[Len_Beach]

Has anyone tried to update the Boot and/or CarPlay logos?

I was playing with settings today and noticed the options in settings.

[corduroy]

Originally Posted by Diirek

It seems like they disabled the autoconnection of the bluetooth that happens when you connect via usb (or wirelessly).. I deleted the mmi from my list of bluetooth devices and it no longer connects.

Looking at my phone when I'm connected, the only bluetooth connection is to my iDrive.

That's great, thanks! I just tested it on my phone and while connected via USB, I disconnected the Bluetooth from AA and it made the call with idrive and showed in AA (also said that Bluetooth was disconnected). But yeah, AA kept on reconnecting Bluetooth. Hopefully this makes it to the other units (I think it will).

[Unspec]

Originally Posted by muniz_ri

Thank you for this.

For everyone's knowledge...it seems that Bimmertech began locking down their updates with this version (10.2.18.15). I changed the MCU name to upgrade.bin and flashed it onto my Carlinkit unit. The screen turned black and the unit became completely unresponsive.

Flashed back to the latest available Carlinkit MCU and all is good once again.

How did you force update the MCU?

[muniz_ri]

Originally Posted by Unspec

How did you force update the MCU?

To flash back the compatible mcu you insert the usb stick and press and hold the back button until it reboots. It will automatically flash the mcu file from usb.

[Unspec]

Originally Posted by muniz_ri

To flash back the compatible mcu you insert the usb stick and press and hold the back button until it reboots. It will automatically flash the mcu file from usb.

For me it just goes straight to "Invalid update" screen :/

[Diirek]

Originally Posted by muniz_ri

That makes sense. I was wondering if the bt "auto-connection" was an android function or a function of the mmi. Sounds like it's a function of the mmi which is how they were able to turn it off.

I had my mmi in a faraday bag for a while but it apparently wore out and stopped blocking the mmi's bt signal. While it worked, I was able to make and receive calls exclusively over the iDrive bt connection and control the phone using either the iDrive menu or the mmi. It worked very well which sounds like your experience now with this beta update.

I tried your recommendation of the faraday bag but couldnt find a good way to seal it with all of the cables and it def didn't block the BT connection. There was no way I was pulling out my glovebox again unless it was to pull the mmi out to return the f$cking thing...

[muniz_ri]

Originally Posted by Unspec

For me it just goes straight to "Invalid update" screen :/

You likely have to wait until the car goes to sleep or pull out then plugin the can/power plug from the mmi before rebooting.

[muniz_ri]

Originally Posted by Diirek

I tried your recommendation of the faraday bag but couldnt find a good way to seal it with all of the cables and it def didn't block the BT connection. There was no way I was pulling out my glovebox again unless it was to pull the mmi out to return the f$cking thing...

The faraday bag wasn't the ideal solution. The extra heat will likely shorten the life of the mmi's components.

[Unspec]

Originally Posted by muniz_ri

You likely have to wait until the car goes to sleep or pull out then plugin the can/power plug from the mmi before rebooting.

If all we're doing is cycling the power it seems much easier to just pull the battery for a hot sec. Gonna try that before I rip my dash apart

[muniz_ri]

Originally Posted by Unspec

If all we're doing is cycling the power it seems much easier to just pull the battery for a hot sec. Gonna try that before I rip my dash apart

That should work. Insert the usb stick before plugging the battery back in then turn on the car and hold the back button for about 5 secs.

[Unspec]

Originally Posted by muniz_ri

That should work. Insert the usb stick before plugging the battery back in then turn on the car and hold the back button for about 5 secs.

Same deal unfortunately. I suspect my device is well and truly bricked.

[muniz_ri]

Originally Posted by Unspec

Same deal unfortunately. I suspect my device is well and truly bricked.

I doubt it. I have soft bricked after flashing both the Bimmertech ispbooot and mcu and have been able to recover every time. But it sounds like you will have to take apart your glove box.

Also, try reformatting the usb stick and try again.

[cossie1]

Power the car off, let it shutdown (you will hear the MMI click when it powers down).

Then put the usb stick in, and then press and hold the back button before you turn the ignition on.

Wait until you hear the unit click and then release.

BTW I could only get this method to work using a 16gb usb stick, it wouldn't do it with my 32gb or 8gb stick.

[Unspec]

Originally Posted by muniz_ri

I doubt it. I have soft bricked after flashing both the Bimmertech ispbooot and mcu and have been able to recover every time. But it sounds like you will have to take apart your glove box.

Also, try reformatting the usb stick and try again.

How did you recover? I updated to the last working versions of bimmertech software and mcu before updating to the new locked MCU, I wonder if that makes a difference.