Quote:
Originally Posted by 0taman
Hi, everybody!
I really need your help. I bought a car with CarPlay already installed. Everything was fine before, but now the device has completely stopped seeing my phone, the Bluetooth icon is displayed, but there is no CarPlay icon and it won't open it. I have done everything as per the instructions several times (connected my phone to my BMW head device via Bluetooth, then connected it to CarPlay via Bluetooth) but no result. Most likely the problem is in the firmware.
I would also like to resolve a problem with the sound: when I connected my phone to CarPlay, it would switch to it from the internal car Bluetooth and the music would stop playing until I manually on the phone to bring playback back through the car Bluetooth again. Is there any way to make the music play on the car Bluetooth and CarPlay at the same time? I'm sure it's the firmware and I'd like to update to the latest version, but I'm afraid of turning my device into a "brick". So I am very much looking forward to your help and advice. I attach a photo of my version (I have NBT).
Thanks in advance!
Attachment 3434407
|
Anything you do is at your own risk!
I would first unpair and delete all Bluetooth pairings from the MMI
and the car
and your phone(s). Then re-pair them all again. Make sure if you use iPhone that under your Bluetooth settings for the CarPLay for device you select "car stereo".
Looks like your unit is: RoadTop B2-Version [1] [NBT] Is your pin code 8032?
You could also try to re-install the 152 code. The first page of this thread should have the file and the information on how to update it properly.
If you are willing to risk on your own to try to update to the latest firmware version 176, and you are sure it's a Road Top NBT then use the ISPBOOT.bin file (do not use GEMINI.bin) from here:
https://mega.nz/file/h95hiBbY#eumC9o...mlrgGyOlxYigcs
The car should be running during the update, or at least with ignition ON without a chance of the HU/car going to sleep (turn headlight-switch to "parking" and buckle in seat belt). It may take 2-3 minutes. Do not interrupt, better to wait a few minutes more than to take a chance. It may take a couple of tries. But since you are going from a very old 152 version to 176, there are some increased risks. Also, your MCU version may need to be updated, but best not to mess with that at the same time as the CUST Version.
Again, do it at your own risk! I had my MMI once near bricked when I did this same upgrade and was lucky to have it worked on the second try.
The bonus with the 176 firmware is that you will have an option to use full Bluetooth audio instead of AUX-IN. Read the posts about that in this forum.