iDrive 6 (mostly) working on MY2016

[packetpilot]

(The drivetrain error is unrelated, the B&O menu is a matter of personal DSP preference--did you know the same white-label amplifiers are seemingly 'branded' with software/DSP alone?)

Still got some work to do, but to reiterate what's loosely available around the web, it's indeed possible, and will require an updated FSC for Nav, seemingly a new one for CarPlay, and a decent bit of patience and hair-pulling.

Anyone who can provide select files (btld/ibad/swfl) from 57.5 (I've only got 59.5 at the moment) will help me out a whole bunch. :-)

[lemetier]

Originally Posted by packetpilot

. B&O menu is a matter of personal DSP preference--did you know the same white-label amplifiers are seemingly 'branded' with software

Harman purchased Bowers & Wilkins in early 2015 and also purchased Bang & Olufsen Automotive a few months later. BOTH systems will become available sometime in the near future. Only one main amp and one bus network is now required instead of two with both systems and more compatible with DRIAC DSP.

Now, are you sure your trying ID6 or ID5? The missing GWTB files used with ID6 would be an issue.

[dr.mba]

Is this a typo?? I thought the most recent idrive is 5?

M

[lemetier]

Originally Posted by dr.mba

Is this a typo?? I thought the most recent idrive is 5?

M

G30 is ID6.

[packetpilot]

Originally Posted by dr.mba

Is this a typo?? I thought the most recent idrive is 5?

M

To clarify, I'm running ID6_Light, which isn't the full ID6. The state of the unit will let me dual-boot ID5_plusplus (the full version) or ID6_light.

[dr.mba]

How can we do this? Or is this something that only people with access to BMW personnel can have such as developers?

M

[packetpilot]

Originally Posted by dr.mba

How can we do this? Or is this something that only people with access to BMW personnel can have such as developers?

M

You can do this by executing a TAL that updates the NBT Evo to v 003 over v 001. It's not exactly recommended since you lose 4G connectivity and Nav, and is irreversible.

EDIT: Also, it's likely not something you can do to a 535i from 2011 unless you've retrofitted an Evo unit into it.

[dr.mba]

interesting facts... I wouldn't want to lose these functions. Thanks for sharing.

M

[banff]

Neat, so you're stuck here?

[Brady1984]

I want this so bad; I hope BMW offers an upgrade or retrofit for the older models. Just not going to go off the deep end and lose nav for it.

[Acturater]

Nice. It definitely looks upgraded from the current idrive. This is what I love about the forums!

[packetpilot]

Originally Posted by THEANCHORED

Neat, so you're stuck here?

For now, yep. Apparently if I can have someone shoot me v002 of the bootloader (or an old, e.g. 57.5, psdzdata), then I can put it into a state where I can delete an old FSC and put it into a state where it'll accept a new one.

There seems to be debate over whether it's necessary to delete the old one at all.

Purchasing an FSC for nav, and car play, seems to be in my best interest. Hopefully BMW allows it.

[banff]

Any update?

[packetpilot]

Originally Posted by THEANCHORED

Any update?

No update, not one involving success anyway. I still have yet to successfully virginize the ECU as far as I can tell, but I may have done it when reverting to am earlier bootloader (002) and carrying out the steps in tool32. Unfortunately at one stage I also deleted my map updates via tool32 so that may be the cause for having a "map data missing or incomplete" error message promoting me to insert a flash drive with the map data.

Tried NEXT maps on a drive but that is apparently not what my car wanted (just what I could get my hands on).

Been getting by with using my phone as GPS (Google assistant via talking head long press is pretty cool) so I haven't paid much mind as yet.

Recent updates have brought me to bootloader v005. I'm guessing I need to run a cable that the 2016's don't have in order to get telematics working (Ethernet between atm and hu iirc, but my brain is just waking up).

Got to work on a 2017 whose CAF I copied with a great deal of hope that just changing the spi/apix1/zbehardkeylayout would do the trick. No dice.

Suggestions on map data are welcomed.

[packetpilot]

Originally Posted by THEANCHORED

New Map data is injected into the cars that have EVO.

Then I suppose it's my inability to use ATM (in telematic_ecu configuration) that's blocking my ability to get the map data.

[faiz]

I just want to applaud you effort. I am sure you will get there. It would be really nice if you can do a step by step for the community when you figure it all out!

[packetpilot]

Originally Posted by faiz

I just want to applaud you effort. I am sure you will get there. It would be really nice if you can do a step by step for the community when you figure it all out!

I agree; I just worry that since the steps have been spread out over a couple months, my memory might be fuzzy and documentation sparse... will keep it in mind though. :-)

[lstoker]

Originally Posted by lemetier

Harman purchased Bowers & Wilkins in early 2015 and also purchased Bang & Olufsen Automotive a few months later. BOTH systems will become available sometime in the near future. Only one main amp and one bus network is now required instead of two with both systems and more compatible with DRIAC DSP.

Now, are you sure your trying ID6 or ID5? The missing GWTB files used with ID6 would be an issue.

I don't think the Harman info is correct... HK bought B&O, but Bowers and Wilkins sold out to EVA Automation owned by Gideon YU. Not the same as HK...

[lemetier]

Originally Posted by lstoker

I don't think the Harman info is correct... HK bought B&O, but Bowers and Wilkins sold out to EVA Automation owned by Gideon YU. Not the same as HK...

Automotive divisions of both which include Brand and Technology Licensing. Consumer Electronics were not part of either.

[lemetier]

Originally Posted by packetpilot

Suggestions on map data are welcomed.

Nigh on impossible. Map Data is only available through the ConnectedStore (for both owners and dealer) and OTA. FSC is completely new format and the system performs wireless configuration continuity checks with the main Vehicle Data Storage Server.

[mstevens]

I'm currently using "id6_light" on my 2017 M4 that was delivered with iDrive 5 and has the HU_NBT2 ECU.

I just had to change from the default "id5_plus_plus" to "id6_light". In my case this did not affect navigation, CarPlay, or ConnectedDrive features, but I think that's because iDrive 5 was native on my system and iDrive 6 "light" seems mostly to be a different skin for the interface.

iDrive 5 compared to 4 is a major evolution and I greatly prefer it. I slightly prefer iDrive 6 "light" over 5. I like the live tiles and find the typography a bit prettier overall, but apart from that I don't think "id6_light" is much different in terms of functionality. The live tiles, for me, make it worth coding this when it's quick and easy but I really doubt there's enough difference here for anyone to lose sleep over.

I'm not sure what the difference is between "light" and not-light. I haven't tried coding to "id6" because I really don't want to be messing with FSC's on this system.

Edit: At this point I greatly prefer the live updating tiles of iDrive 6 to the main menu of iDrive 5. On my M4 there's really no other difference, but in a short time I've really come to love the home screen and use it practically all the time. I guess it really is deserving of a major version number!

[packetpilot]

Originally Posted by mstevens

I'm not sure what the difference is between "light" and not-light. I haven't tried coding to "id6" because I really don't want to be messing with FSC's on this system.

There's no risk here AFAIK; id6 hasn't worked on MY2016 cars from what I understand, so it might be worthwhile just to see if you can load it up.

I coded a friend's MY2017 to id6_light and he's pretty pleased with the flat design language on 6 as opposed to 4/5.