[sobanoodle]

Hey good people!

Have a few questions re: Japan to ECE conversion (I managed to stuff up my converted by someone else CIC and it is back to Japan specs )

1) What needs to be coded to make it ECE spec?
2) Do I need to flash it? Can it be done with ISTA/P or I'll have to use E-sys?
3) At what stage do I need to swap ECE HDD image over?

Thanks in advance!

[Fx82]

There is also a thread if you use the search function.

You need to flash the unit to ece specs and use a eu dump for the harddisk.

[sobanoodle]

There is also a thread if you use the search function.

You need to flash the unit to ece specs and use a eu dump for the harddisk.

I've read all the threads on here and beyond.

So far I've done the following:

VO-coded the following: 852 to 853 and 807 to 810 - this at least returned the extended radio frequencies and much nicer large font (what I used to have).

Then flashed the unit with E-sys (Ista/P now only offers "replace option") - any way to check that it is definitely ECE spec now?

I guess the next step will be to swap ECE HDD clone.

And then activating navigation menu as it is greyed out at the moment. Are there any other options than running scripts?..

FSC status:

ootCertStatus accepted
SWSigStatus accepted
SWTApplications
<--
FSCSCertStatus accepted
FSCStatus rejected
AppNr./UpgrIdx 23(0x17)/1(0x01)
SWTType SWTclassic full

<--
FSCSCertStatus accepted
FSCStatus rejected
AppNr./UpgrIdx 25(0x19)/1(0x01)
SWTType SWTclassic full

<--
FSCSCertStatus accepted
FSCStatus rejected
AppNr./UpgrIdx 27(0x1B)/1(0x01)
SWTType SWTclassic full

<--
FSCSCertStatus accepted
FSCStatus rejected
AppNr./UpgrIdx 111(0x6F)/1(0x01)
SWTType SWTclassic full

<--
FSCSCertStatus accepted
FSCStatus not available
AppNr./UpgrIdx 156(0x9C)/1(0x01)
SWTType SWTclassic full

<--
FSCSCertStatus accepted
FSCStatus not available
AppNr./UpgrIdx 155(0x9B)/1(0x01)
SWTType SWTclassic full

<--
FSCSCertStatus not available
FSCStatus rejected
AppNr./UpgrIdx 48(0x30)/42(0x2A)
SWTType SWTshort

RoutineResult: OK

[sobanoodle]

The conversion is now complete.

Followed the following steps:
1. VO-code: [852 instead of 853] and [807 instead of 810] for AU/NZ market
2. Flash HU_CIC using E-Sys (check HW-IDs from SVTactual after SVT Target calculation)
3. Replace Japanese HDD with a ECE image
4. Use SWTPatcher-v2 to activate FSCs
5. Use BMW-FSC-Generator_1_0_1_0 for map update code
6. Load 2018 AU/NZ Premium maps

The only thing I am missing now is messages/emails in Office, have contacts only in there :/

[Loliceman]

The conversion is now complete.

Followed the following steps:
1. VO-code: [852 instead of 853] and [807 instead of 810] for AU/NZ market
2. Flash HU_CIC using E-Sys (check HW-IDs from SVTactual after SVT Target calculation)
3. Replace Japanese HDD with a ECE image
4. Use SWTPatcher-v2 to activate FSCs
5. Use BMW-FSC-Generator_1_0_1_0 for map update code
6. Load 2018 AU/NZ Premium maps

The only thing I am missing now is messages/emails in Office, have contacts only in there :/

Good job!
Regarding the email and messages, not many phones are compatible with these types of services. Keep in mind CIC is now getting old and BMW haven't pushed a compatibility patch for modern phones in a long time.
That's probably why you can't see it.

[sobanoodle]

The conversion is now complete.

Followed the following steps:
1. VO-code: [852 instead of 853] and [807 instead of 810] for AU/NZ market
2. Flash HU_CIC using E-Sys (check HW-IDs from SVTactual after SVT Target calculation)
3. Replace Japanese HDD with a ECE image
4. Use SWTPatcher-v2 to activate FSCs
5. Use BMW-FSC-Generator_1_0_1_0 for map update code
6. Load 2018 AU/NZ Premium maps

The only thing I am missing now is messages/emails in Office, have contacts only in there :/

Good job!
Regarding the email and messages, not many phones are compatible with these types of services. Keep in mind CIC is now getting old and BMW haven't pushed a compatibility patch for modern phones in a long time.
That's probably why you can't see it.

I had emails and messages prior to the reflash, so I am guessing it is a software related issue. There were number of small updates issued to address phone compatibility issues, have downloaded a few but none would load from a USB stick in a glovebox.

Another issues I noticed this morning - every time I start the car/reboot CIC the initial navi position is always the same (my home address), even if I am miles away. Start moving and it updates to the current location after a few moments

[Loliceman]

The conversion is now complete.

Followed the following steps:
1. VO-code: [852 instead of 853] and [807 instead of 810] for AU/NZ market
2. Flash HU_CIC using E-Sys (check HW-IDs from SVTactual after SVT Target calculation)
3. Replace Japanese HDD with a ECE image
4. Use SWTPatcher-v2 to activate FSCs
5. Use BMW-FSC-Generator_1_0_1_0 for map update code
6. Load 2018 AU/NZ Premium maps

The only thing I am missing now is messages/emails in Office, have contacts only in there :/

Good job!
Regarding the email and messages, not many phones are compatible with these types of services. Keep in mind CIC is now getting old and BMW haven't pushed a compatibility patch for modern phones in a long time.
That's probably why you can't see it.

I had emails and messages prior to the reflash, so I am guessing it is a software related issue. There were number of small updates issued to address phone compatibility issues, have downloaded a few but none would load from a USB stick in a glovebox.

Another issues I noticed this morning - every time I start the car/reboot CIC the initial navi position is always the same (my home address), even if I am miles away. Start moving and it updates to the current location after a few moments

You need to load the latest update for CIC/COMBOX (upd01008.bin) on the "armrest" USB that goes to Combox (if you have one installed). Glovebox USB goes directly to the HU and is not able to be "updated" with upd01008.bin.
So the patch is in fact used for the Combox, not the CIC.

About your second issue, could be a low quality GPS antenna. But you should do diagnostics on ISTA and/or clear navigation cache with tool32.

[sobanoodle]

You need to load the latest update for CIC/COMBOX (upd01008.bin) on the "armrest" USB that goes to Combox (if you have one installed). Glovebox USB goes directly to the HU and is not able to be "updated" with upd01008.bin.
So the patch is in fact used for the Combox, not the CIC.

I actually got it sorted semi-accidentally
Was browsing through HU_CIC and found NOTEPAD parameter in 3000 HMI which was set to nicht-activ. Coded that for activ and messages are now displayed in the Office.

And yes I suspected that those updates are only able to be loaded through an armrest USB, which I do not have :/

About your second issue, could be a low quality GPS antenna. But you should do diagnostics on ISTA and/or clear navigation cache with tool32.

I have a completely factory CIC set-up, not retrofitted and had no issues with the reception whatsoever. Nor that I have any signal issues at the moment either. As soon as you start driving the map gets quickly updated to a true position. It's just on start up that it always shows the same position (home address), no matter where I am. More of a software glitch I reckon.

Never used tool32 before, is it quite straightforward?

[sobanoodle]

Another issues I noticed this morning - every time I start the car/reboot CIC the initial navi position is always the same (my home address), even if I am miles away. Start moving and it updates to the current location after a few moments

This just got resolved by itself, the wag'o probably needed a bit of time to relax after all the "abuse" .