[x5TXguyG05]

Can you revert back to previous version of update? It killed me coding and not sure I can do it again (ASS and ADV)? Also, camera views are acting up.

[mitch57]

Originally Posted by x5TXguyG05

Can you revert back to previous version of update? It killed me coding and not sure I can do it again (ASS and ADV)? Also, camera views are acting up.

Unfortunately no. You can NOT go back to a previous version from a newer version.

Did you try rebooting iDrive after the update?

[FreddyBMW]

Originally Posted by x5TXguyG05

Can you revert back to previous version of update? It killed me coding and not sure I can do it again (ASS and ADV)? Also, camera views are acting up.

Its strange. Mine didn't touch any of my Codings when doing the OTA Update. Was your OTA update process interrupted or restarted? I have ASS and ADV both working. By the way I used BimmerCode App to program it using that Bluetooth dongle.

[ifr]

Originally Posted by FreddyBMW

Its strange. Mine didn't touch any of my Codings when doing the OTA Update. Was your OTA update process interrupted or restarted? I have ASS and ADV both working. By the way I used BimmerCode App to program it using that Bluetooth dongle.

If your fdl/Bimmercode coding persisted then either your OTA didn't work properly, or the coded ECU's were not upgraded.

Istep upgrades usually go 1) program ECU 2) VO code same ECU, wiping fdl coding

[x5TXguyG05]

Originally Posted by mitch57

Unfortunately no. You can NOT go back to a previous version from a newer version.

Did you try rebooting iDrive after the update?

No, I'll try that, thanks

[x5TXguyG05]

Originally Posted by FreddyBMW

Its strange. Mine didn't touch any of my Codings when doing the OTA Update. Was your OTA update process interrupted or restarted? I have ASS and ADV both working. By the way I used BimmerCode App to program it using that Bluetooth dongle.

I don't think it was interrupted, but could've missed it

[x5TXguyG05]

Originally Posted by ifr

If your fdl/Bimmercode coding persisted then either your OTA didn't work properly, or the coded ECU's were not upgraded.

Istep upgrades usually go 1) program ECU 2) VO code same ECU, wiping fdl coding

So, can I restore my coding from a backup after the update?

[ifr]

Originally Posted by x5TXguyG05

So, can I restore my coding from a backup after the update?

I don't recommend you do this.

When you do an i-step update the car coding 'schema' changes, and the local coding tools (esys, bimmercode?) need to update to address those changes.

In esys, a cafd that worked for an earlier i-step such as 07/2019, will be different to a newer one for say 11/2019.70.

I always manually recode everything again after an i-step update, and the i-step upgrade 'should' wipe your coding if its worked correctly.

The issue with esys and I guess also bimmercode, is that each newer i-step requires a newer psdzdata or equivalent to map to the cars 'schema' and coding values. The newer psdzdata needs to be manually mapped by the software provider (bimmercode, esysx, tokenmaster) to address changes to the newer psdzdata - new codes, changed codes etc. Without that the software is blind to what codes are available on the car.

Why do you think you cannot code your car again? Does bimmercode not support the newer i-step yet?

[x5TXguyG05]

Originally Posted by ifr

I don't recommend you do this.

When you do an i-step update the car coding 'schema' changes, and the local coding tools (esys, bimmercode?) need to update to address those changes.

In esys, a cafd that worked for an earlier i-step such as 07/2019, will be different to a newer one for say 11/2019.70.

I always manually recode everything again after an i-step update, and the i-step upgrade 'should' wipe your coding if its worked correctly.

The issue with esys and I guess also bimmercode, is that each newer i-step requires a newer psdzdata or equivalent to map to the cars 'schema' and coding values. The newer psdzdata needs to be manually mapped by the software provider (bimmercode, esysx, tokenmaster) to address changes to the newer psdzdata - new codes, changed codes etc. Without that the software is blind to what codes are available on the car.

Why do you think you cannot code your car again? Does bimmercode not support the newer i-step yet?

I guess I can recode, just new to this so wasn't sure. How do I know when Bimmercode is ready to code after this latest update? I am new to this.

[ifr]

Originally Posted by x5TXguyG05

I guess I can recode, just new to this so wasn't sure. How do I know when Bimmercode is ready to code after this latest update? I am new to this.

I don't use bimmercode. I guess it locks out or displays an error if the i-step version isn't supported.

One of the bimmercode users like LexxM3 should be able to advise.

[hkleyman]

Originally Posted by ifr

I don't use bimmercode. I guess it locks out or displays an error if the i-step version isn't supported.

One of the bimmercode users like LexxM3 should be able to advise.

Bimmercode beta 3.6 does support 03/2020.58. I just finished restoring my changes after being upgraded from 07/2019. I'm not able to test with 3.5 since I have the beta version and am providing feedback to the developer.

[LexxM3]

Originally Posted by hkleyman

Bimmercode beta 3.6 does support 03/2020.58. I just finished restoring my changes after being upgraded from 07/2019. I'm not able to test with 3.5 since I have the beta version and am providing feedback to the developer.

If TestFlight, you can delete app and just download from App Store the current release version. When ready to go back to beta, reverse the process and use TestFight for the app. Your TestFlight invite survives the process.


If in Android, you have to delete app, cancel beta, download released app. When ready to go back to beta, reverse the process (I believe, double check first).