[124geek]

I haven't seen this covered anywhere, so I figured it might help someone else out...

In preparation for adding CarPlay support I upgraded my CMU firmware to 70.00.100 and used Ameridan's (and others) great MazdaToFiat70 files to re-Abartize. When my CarPlay hardware came in and I had everything apart and could get back into the CMU serial port I decided "what the heck, might as well update further." I researched that the Mazda tweaks were OK (if using AIO 2.8.6) up to 70.00.352, but not to try 70.00.367. So update I did, being sure to include ID7 Recovery V2 (the XX package). I did NOT recall that Ameridan specifically said not to go beyond 70.00.100. I ran into two problems... the first reboot attempted to run MazdaToFiat, but failed out because the install script checked the CMU firmware version. I edited the script to allow any version and was prepared to be happy. Happy didn't happen. The seven stages of grief happened. After that first time the MazdaToFiat install would not even start. I tried a lot of things (including downgrading from 352 to 335), finally realizing I would have to live with a Mazda looking CMU and no nav. After an evening wallowing in self pity I decided to go ahead and hope the Mazda tweaks might install to at least get rid of the nanny warnings. Indeed they did install! Hmmm... why would that work and the MazdaToFiat not? On a whim I edited the MazdaToFiat script a little more and put it along with the config folder onto my Mazda AIO USB stick. SUCCESS!!! I now have a re-Abarthized CMU running on 70.00.335 firmware! Happy Happy!

To re-Abart-ize (or Fiat-ize if you roll that way):
Get MazdaToFiatV70AIO from Universal Version 70 Fiat AIO Tweak
Start with a tweaks USB drive generated with MZD-AIO v2.8.6. Load a tweak into your CMU to make sure it works!
Replace the config folder on the AIO USB with the config folder from MazdaToFiatV70AIO
Replace tweaks.sh on the AIO USB with tweaks.sh from MazdaToFiatV70AIO
Edit tweaks.sh on the AIO USB:
Change variables listed below (not sure if necessary, but didn't try without)
# AIO Variables
AIO_VER=2.8.6
AIO_DATE=2020.04.04
# Android Auto Headunit App Version
AA_VER=1.13
# Speedometer Version
SPD_VER=6.1
# AIO Tweaks App Version
AIO_TWKS_VER=1.0
In compatibility_check() change VER_EXT comparison at line 161 from 100 to 360:
159: elif [ $_VER -eq 70 ]
160: then
161: if [ $_VER_EXT -le 360 ]

Save tweaks.sh, then safely eject the USB drive from your computer. Follow Ameridan's instructions to de-Mazda your CMU.

Enjoy!

 

[68wooley]

I haven't looked at this in a while. Any idea what firmware 70.00.352 adds over 70.00.100? If it's a worthwhile update I'll work your suggestions in to the 'official' instructions and AIO files.

Good effort doing this.

 

[124geek]

I haven't looked at this in a while. Any idea what firmware 70.00.352 adds over 70.00.100? If it's a worthwhile update I'll work your suggestions in to the 'official' instructions and AIO files.

Good effort doing this.

The main thing I'm aware of is a fix for Bluetooth echo. That's not a big deal, but this AIO patch may help others who do like me and go An Update Too Far.

 

[cadams155]

Nice work!

 

[124geek]

I haven't looked at this in a while. Any idea what firmware 70.00.352 adds over 70.00.100? If it's a worthwhile update I'll work your suggestions in to the 'official' instructions and AIO files.

Good effort doing this.

I found a detailed change log that covers 70.00.335C and .352B. Adding it here for future generations.

 

[68wooley]

To be honest, I'm not aware of anyone suffering from the BT echo issue. Looking through the release notes, I'm not seeing many issues I've experienced personally. If 70.00.367 is the latest release and we can't use it, we're not going to gain much here, however I may update the instructions to use ID7 V2 to protect people as much as possible from unintended lock outs.

 

[teddysbeer]

is wireless connection working smoothly here or still laggy?

 

[124geek]

is wireless connection working smoothly here or still laggy?

I've been using Pandora via my iPhone and Bluetooth. Haven't noticed any issues.

 

[SJWhiteley]

I sure would like to see the source code SVN check-ins to see what actually changed that wasn’t documented...I know all programmers do it: “fixed a div zero bug” - 15 files have changed, code added, deleted and modified.

 

[Bob124]

Halo everyone. I have issue by using boot animation. I have abarth logo but sometimes Mazda logo is showing. Does anyone have same problem? Also my system work really slow after tweaking. If anyone have some ideas please help me.

 

[frankmar]

Halo everyone. I have issue by using boot animation. I have abarth logo but sometimes Mazda logo is showing. Does anyone have same problem? Also my system work really slow after tweaking. If anyone have some ideas please help me.

When you reboot, sometimes you may get the Mazda Logo, while before we might have got the Fiat Logo. I think when it reboots it will take a little longer, but normal operation it will be faster. The warning sign stays a little longer, but once moving it goes away, maybe I forgot or there's is a an option in the 2.86 tweaks to make it go away faster.

 

[Bob124]

So there is no chance to change boot/start Mazda logo (with is before fiat/abarth logo)?

 

[frankmar]

So there is no chance to change boot/start Mazda logo (with is before fiat/abarth logo)?

Only the Gods can make it disappear, I got use to it, so it is no bother for me. I had bigger issues with the S10, now solved. Mind you I haven't used much the AA, I being there it's a confort.

 

[Paolodo89]

Only the Gods can make it disappear, I got use to it, so it is no bother for me. I had bigger issues with the S10, now solved. Mind you I haven't used much the AA, I being there it's a confort.

Hi, I have an issue with s10+ when i connect to usb my cmu went black, AA not open and my phone reboots in a few seconds. Have you any suggest?
V70. 00.100

 

[frankmar]

clear the S10 cache

 

[funkyman]

I haven't seen this covered anywhere, so I figured it might help someone else out...

In preparation for adding CarPlay support I upgraded my CMU firmware to 70.00.100 and used Ameridan's (and others) great MazdaToFiat70 files to re-Abartize. When my CarPlay hardware came in and I had everything apart and could get back into the CMU serial port I decided "what the heck, might as well update further." I researched that the Mazda tweaks were OK (if using AIO 2.8.6) up to 70.00.352, but not to try 70.00.367. So update I did, being sure to include ID7 Recovery V2 (the XX package). I did NOT recall that Ameridan specifically said not to go beyond 70.00.100. I ran into two problems... the first reboot attempted to run MazdaToFiat, but failed out because the install script checked the CMU firmware version. I edited the script to allow any version and was prepared to be happy. Happy didn't happen. The seven stages of grief happened. After that first time the MazdaToFiat install would not even start. I tried a lot of things (including downgrading from 352 to 335), finally realizing I would have to live with a Mazda looking CMU and no nav. After an evening wallowing in self pity I decided to go ahead and hope the Mazda tweaks might install to at least get rid of the nanny warnings. Indeed they did install! Hmmm... why would that work and the MazdaToFiat not? On a whim I edited the MazdaToFiat script a little more and put it along with the config folder onto my Mazda AIO USB stick. SUCCESS!!! I now have a re-Abarthized CMU running on 70.00.335 firmware! Happy Happy!

To re-Abart-ize (or Fiat-ize if you roll that way):
Get MazdaToFiatV70AIO from Universal Version 70 Fiat AIO Tweak
Start with a tweaks USB drive generated with MZD-AIO v2.8.6. Load a tweak into your CMU to make sure it works!
Replace the config folder on the AIO USB with the config folder from MazdaToFiatV70AIO
Replace tweaks.sh on the AIO USB with tweaks.sh from MazdaToFiatV70AIO
Edit tweaks.sh on the AIO USB:
Change variables listed below (not sure if necessary, but didn't try without)
# AIO Variables
AIO_VER=2.8.6
AIO_DATE=2020.04.04
# Android Auto Headunit App Version
AA_VER=1.13
# Speedometer Version
SPD_VER=6.1
# AIO Tweaks App Version
AIO_TWKS_VER=1.0
In compatibility_check() change VER_EXT comparison at line 161 from 100 to 360:
159: elif [ $_VER -eq 70 ]
160: then
161: if [ $_VER_EXT -le 360 ]

Save tweaks.sh, then safely eject the USB drive from your computer. Follow Ameridan's instructions to de-Mazda your CMU.

Enjoy!

Hi my friend I did the new CMU upgrade to my 2017 Spyder 124 with the 70.335 firmware so no Navi and Mazda icon on start up.Can you do a YouTube video please on how to Abarthise the infotainment and have my fiat navibad card working again with the fiat boot up animation.Below instructions are aittle complicated

 

[ameridan]

I haven't seen this covered anywhere, so I figured it might help someone else out...

In preparation for adding CarPlay support I upgraded my CMU firmware to 70.00.100 and used Ameridan's (and others) great MazdaToFiat70 files to re-Abartize. When my CarPlay hardware came in and I had everything apart and could get back into the CMU serial port I decided "what the heck, might as well update further." I researched that the Mazda tweaks were OK (if using AIO 2.8.6) up to 70.00.352, but not to try 70.00.367. So update I did, being sure to include ID7 Recovery V2 (the XX package). I did NOT recall that Ameridan specifically said not to go beyond 70.00.100. I ran into two problems... the first reboot attempted to run MazdaToFiat, but failed out because the install script checked the CMU firmware version. I edited the script to allow any version and was prepared to be happy. Happy didn't happen. The seven stages of grief happened. After that first time the MazdaToFiat install would not even start. I tried a lot of things (including downgrading from 352 to 335), finally realizing I would have to live with a Mazda looking CMU and no nav. After an evening wallowing in self pity I decided to go ahead and hope the Mazda tweaks might install to at least get rid of the nanny warnings. Indeed they did install! Hmmm... why would that work and the MazdaToFiat not? On a whim I edited the MazdaToFiat script a little more and put it along with the config folder onto my Mazda AIO USB stick. SUCCESS!!! I now have a re-Abarthized CMU running on 70.00.335 firmware! Happy Happy!

To re-Abart-ize (or Fiat-ize if you roll that way):
Get MazdaToFiatV70AIO from Universal Version 70 Fiat AIO Tweak
Start with a tweaks USB drive generated with MZD-AIO v2.8.6. Load a tweak into your CMU to make sure it works!
Replace the config folder on the AIO USB with the config folder from MazdaToFiatV70AIO
Replace tweaks.sh on the AIO USB with tweaks.sh from MazdaToFiatV70AIO
Edit tweaks.sh on the AIO USB:
Change variables listed below (not sure if necessary, but didn't try without)
# AIO Variables
AIO_VER=2.8.6
AIO_DATE=2020.04.04
# Android Auto Headunit App Version
AA_VER=1.13
# Speedometer Version
SPD_VER=6.1
# AIO Tweaks App Version
AIO_TWKS_VER=1.0
In compatibility_check() change VER_EXT comparison at line 161 from 100 to 360:
159: elif [ $_VER -eq 70 ]
160: then
161: if [ $_VER_EXT -le 360 ]

Save tweaks.sh, then safely eject the USB drive from your computer. Follow Ameridan's instructions to de-Mazda your CMU.

Enjoy!

I just saw this, and added a link to this post in my article, for others finding themselves in this predicament. Thank you for the post!

 

[funkyman]

I just saw this, and added a link to this post in my article, for others finding themselves in this predicament. Thank you for the post!

Need a step by step YouTube tutorial.

 

[funkyman]

I just saw this, and added a link to this post in my article, for others finding themselves in this predicament. Thank you for the post!

Make a YouTube video pls

 

[funkyman]

I haven't seen this covered anywhere, so I figured it might help someone else out...

In preparation for adding CarPlay support I upgraded my CMU firmware to 70.00.100 and used Ameridan's (and others) great MazdaToFiat70 files to re-Abartize. When my CarPlay hardware came in and I had everything apart and could get back into the CMU serial port I decided "what the heck, might as well update further." I researched that the Mazda tweaks were OK (if using AIO 2.8.6) up to 70.00.352, but not to try 70.00.367. So update I did, being sure to include ID7 Recovery V2 (the XX package). I did NOT recall that Ameridan specifically said not to go beyond 70.00.100. I ran into two problems... the first reboot attempted to run MazdaToFiat, but failed out because the install script checked the CMU firmware version. I edited the script to allow any version and was prepared to be happy. Happy didn't happen. The seven stages of grief happened. After that first time the MazdaToFiat install would not even start. I tried a lot of things (including downgrading from 352 to 335), finally realizing I would have to live with a Mazda looking CMU and no nav. After an evening wallowing in self pity I decided to go ahead and hope the Mazda tweaks might install to at least get rid of the nanny warnings. Indeed they did install! Hmmm... why would that work and the MazdaToFiat not? On a whim I edited the MazdaToFiat script a little more and put it along with the config folder onto my Mazda AIO USB stick. SUCCESS!!! I now have a re-Abarthized CMU running on 70.00.335 firmware! Happy Happy!

To re-Abart-ize (or Fiat-ize if you roll that way):
Get MazdaToFiatV70AIO from Universal Version 70 Fiat AIO Tweak
Start with a tweaks USB drive generated with MZD-AIO v2.8.6. Load a tweak into your CMU to make sure it works!
Replace the config folder on the AIO USB with the config folder from MazdaToFiatV70AIO
Replace tweaks.sh on the AIO USB with tweaks.sh from MazdaToFiatV70AIO
Edit tweaks.sh on the AIO USB:
Change variables listed below (not sure if necessary, but didn't try without)
# AIO Variables
AIO_VER=2.8.6
AIO_DATE=2020.04.04
# Android Auto Headunit App Version
AA_VER=1.13
# Speedometer Version
SPD_VER=6.1
# AIO Tweaks App Version
AIO_TWKS_VER=1.0
In compatibility_check() change VER_EXT comparison at line 161 from 100 to 360:
159: elif [ $_VER -eq 70 ]
160: then
161: if [ $_VER_EXT -le 360 ]

Save tweaks.sh, then safely eject the USB drive from your computer. Follow Ameridan's instructions to de-Mazda your CMU.

Enjoy!

Any chance you could do a thorough YouTube tutorial please i have the 335 firmware with prior tweak Id installed