iDrive refuses to boot?
11-01-2007, 03:59 PM
#11
Members
Join Date: Feb 2005
Location: Sao Paulo, Brasil
Posts: 13
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 535d, orient blue, Dakota beige, Dynamic Drive, Xenon, Nav Prof, Bluetooth, comfort seats, PDC, curve lights, 135M wheels
Originally Posted by jkava' post='488480' date='Nov 1 2007, 04:29 AM
Hi everyone,
I did a search and it seems at least one other person has experienced this same problem - but I'm anxious to know what needs to be done to fix the issue.
The problem description is that when the car is shut off briefly, such as when you are filling up the gas tank, upon restarting the car, iDrive wont boot up. The problem is intermittent, of course
, and when it does happen, iDrive will not respond to anything. Manually forcing a reboot (eject CD, eject DVD, radio on/off) doesn't help either. When it is in this condition nothing is responsive - no radio, no nav, no bluetooth, nothing... Only after the car has rested for a significant period has the problem cleared itself. It seems as the system logs an error and requires the car to go to "sleep" before the error is cleared???
The dealer has tried to fix this issue once before by replacing the fiber optic cable from iDrive to the CCC because of communication errors in the fault log. However, this problem is still occuring although not as often.
Anyone else experience the same issue, and if so was it resolved? How?
Thanks for any suggestions.
I did a search and it seems at least one other person has experienced this same problem - but I'm anxious to know what needs to be done to fix the issue.
The problem description is that when the car is shut off briefly, such as when you are filling up the gas tank, upon restarting the car, iDrive wont boot up. The problem is intermittent, of course
, and when it does happen, iDrive will not respond to anything. Manually forcing a reboot (eject CD, eject DVD, radio on/off) doesn't help either. When it is in this condition nothing is responsive - no radio, no nav, no bluetooth, nothing... Only after the car has rested for a significant period has the problem cleared itself. It seems as the system logs an error and requires the car to go to "sleep" before the error is cleared???The dealer has tried to fix this issue once before by replacing the fiber optic cable from iDrive to the CCC because of communication errors in the fault log. However, this problem is still occuring although not as often.
Anyone else experience the same issue, and if so was it resolved? How?
Thanks for any suggestions.
11-03-2007, 07:52 AM
#12
Members
Join Date: Sep 2007
Location: Austin, TX
Posts: 13
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 2004 545, MT, Black Sapphire, Auburn, Cold Weather, NAV, Bluetooth, mp3
My idrive just crapped out on me right now. I got the latest software upgrade about a month ago and this is the first time it's done it. I parked the car for about 15 min and when I came back and started the car the screen was black. I haven't tried rebooting yet. I'll let it sit for a while and then fire it up. If it still doesn't come on i'll try to reboot.
11-11-2007, 11:21 AM
#13
Members
Thread Starter
Join Date: Aug 2003
Location: Silicon Valley, CA
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: '04 545i SMG, silver grey, grey Dakota leather, dark poplar, 124's, Nav, Logic 7, PDC, CWP, xenon adaptive lights, comfort seats, electric rear sunshade, hardwired V1, Bluetooth, Aux input, Progman 25, poplar wood trim front lower dash and rear cente
Originally Posted by Rudy' post='488494' date='Oct 31 2007, 11:30 PM
Can't say I have an answer but I do have one question. Are you able to force a reboot (eject/eject/mute) when things are working properly? I'm just trying to establish that you are performing that procedure properly since it sometimes a bit tricky to get it to work...
Hi Rudy,
Sorry the delay in responding - I've been out of town. Yes, under normal operation, I can get the system to reboot fine by pushing both eject buttons and power at the same time.
Thanks,
11-11-2007, 11:24 AM
#14
Members
Thread Starter
Join Date: Aug 2003
Location: Silicon Valley, CA
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: '04 545i SMG, silver grey, grey Dakota leather, dark poplar, 124's, Nav, Logic 7, PDC, CWP, xenon adaptive lights, comfort seats, electric rear sunshade, hardwired V1, Bluetooth, Aux input, Progman 25, poplar wood trim front lower dash and rear cente
Originally Posted by moema535d' post='488782' date='Nov 1 2007, 06:59 PM
Do you happen to have a Sony Ericsson Bluetooth phone and was it switched on when you started the car?
Nope, I don't have a Sony Ericsson Bluetooth phone. I do use a Bluetooth Blackberry though - have you seen a direct correlation between iDrive not booting up and having a Bluetooth device paired?
Thank you,
11-11-2007, 07:28 PM
#15
Members
Join Date: Jun 2007
Location: North Texas
Posts: 26
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by jkava' post='492963' date='Nov 11 2007, 02:24 PM
Nope, I don't have a Sony Ericsson Bluetooth phone. I do use a Bluetooth Blackberry though - have you seen a direct correlation between iDrive not booting up and having a Bluetooth device paired?
Good luck...
11-18-2007, 01:04 AM
#16
Members
Join Date: Jan 2005
Location: PARIS - FRANCE
Posts: 204
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 535 D - to be delivered end Feb 2005 - color E08 - comfort seats - executive leather balck - 122 wheels - dynamic drive - active steering - pack luxe - tecnology pack - moon roof - 6CD player - hifi system - spare wheel - BT phone
Originally Posted by moema535d' post='488782' date='Nov 2 2007, 01:59 AM
Do you happen to have a Sony Ericsson Bluetooth phone and was it switched on when you started the car?
11-18-2007, 02:54 AM
#17
Members
Join Date: Feb 2007
Location: Norway
Posts: 114
Likes: 0
Received 0 Likes
on
0 Posts
my old 320d (2006) had a similar problem. it refused to boot after I shut down the engine. (It worked fine in the mornings, when engine was "cold")
Got a software update but the problem stayed on.
They ordered the whole cd/dvd player (nav pro) and installed it and the problem was solved.
Got a software update but the problem stayed on.
They ordered the whole cd/dvd player (nav pro) and installed it and the problem was solved.
11-19-2007, 11:59 AM
#18
Members
Join Date: Feb 2005
Location: Sao Paulo, Brasil
Posts: 13
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 535d, orient blue, Dakota beige, Dynamic Drive, Xenon, Nav Prof, Bluetooth, comfort seats, PDC, curve lights, 135M wheels
Originally Posted by FJPM' post='495847' date='Nov 18 2007, 11:04 AM
Yes a T610 and as you, I suspect it is related with this phone, because I never happened when the phone is swichted of.
I am not so sure.
Currently, I live in South America and use my car, which is 'parked' in Germany, only a few times per year when I am in Europe for business or vacation.
In April this year, the software was updated to version 25.xx. After that, I made a three week trip covering eleven countries and more than 10000km. I continued to use the 'old' Siemens S65 I had been using before both in this and other cars. No problems with the phone or the Idrive whatsoever.
Before my next visit in June, I switched to a Sony Ericsson W810i phone because it supports sending the addressbook (with multiple numbers per name) to the Idrive. During that trip, I had four incidents:
Twice - Idrive first 'freezes' then goes black after toggling the <INCOMING CALLS in Handsfree/In Phone> setting during active calls.
Twice - Idrive stays dark when starting the car with the phone switched on.
For the third trip this year I simply turned off the BT communcation and used the phone the old fashioned way. During 5 weeks of daily use I had no problems at all.
So, yes - at least in my case I think the phone plays some part in the problem
12-04-2007, 10:18 AM
#19
Members
Thread Starter
Join Date: Aug 2003
Location: Silicon Valley, CA
Posts: 57
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: '04 545i SMG, silver grey, grey Dakota leather, dark poplar, 124's, Nav, Logic 7, PDC, CWP, xenon adaptive lights, comfort seats, electric rear sunshade, hardwired V1, Bluetooth, Aux input, Progman 25, poplar wood trim front lower dash and rear cente
Latest update... the saga continues. My dealer updated the Progman to the latest version 27.02 (I think). Anyway, all was good for a couple weeks and now the same issue is occurring randomly again. I will call for another service appointment and request that a PUMA case be opened. There must be a permanent fix for this known issue... 
Originally Posted by moema535d' post='496487' date='Nov 19 2007, 03:59 PM
Some people on this and other (German) forums think that this problem only has to do with software version 25.xx.
I am not so sure.
Currently, I live in South America and use my car, which is 'parked' in Germany, only a few times per year when I am in Europe for business or vacation.
In April this year, the software was updated to version 25.xx. After that, I made a three week trip covering eleven countries and more than 10000km. I continued to use the 'old' Siemens S65 I had been using before both in this and other cars. No problems with the phone or the Idrive whatsoever.
Before my next visit in June, I switched to a Sony Ericsson W810i phone because it supports sending the addressbook (with multiple numbers per name) to the Idrive. During that trip, I had four incidents:
Twice - Idrive first 'freezes' then goes black after toggling the <INCOMING CALLS in Handsfree/In Phone> setting during active calls.
Twice - Idrive stays dark when starting the car with the phone switched on.
For the third trip this year I simply turned off the BT communcation and used the phone the old fashioned way. During 5 weeks of daily use I had no problems at all.
So, yes - at least in my case I think the phone plays some part in the problem
I am not so sure.
Currently, I live in South America and use my car, which is 'parked' in Germany, only a few times per year when I am in Europe for business or vacation.
In April this year, the software was updated to version 25.xx. After that, I made a three week trip covering eleven countries and more than 10000km. I continued to use the 'old' Siemens S65 I had been using before both in this and other cars. No problems with the phone or the Idrive whatsoever.
Before my next visit in June, I switched to a Sony Ericsson W810i phone because it supports sending the addressbook (with multiple numbers per name) to the Idrive. During that trip, I had four incidents:
Twice - Idrive first 'freezes' then goes black after toggling the <INCOMING CALLS in Handsfree/In Phone> setting during active calls.
Twice - Idrive stays dark when starting the car with the phone switched on.
For the third trip this year I simply turned off the BT communcation and used the phone the old fashioned way. During 5 weeks of daily use I had no problems at all.
So, yes - at least in my case I think the phone plays some part in the problem
12-04-2007, 12:10 PM
#20
Members
Join Date: Oct 2005
Location: France
Posts: 218
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 520d
Originally Posted by jkava' post='502570' date='Dec 4 2007, 08:18 PM
Latest update... the saga continues. My dealer updated the Progman to the latest version 27.02 (I think). Anyway, all was good for a couple weeks and now the same issue is occurring randomly again. I will call for another service appointment and request that a PUMA case be opened. There must be a permanent fix for this known issue...
That was what my dealer told me anyway...