[Garrettt93]

Hi All,

I was wondering if anyone else had gone this route. I have installed the OFW for the Mazda CMU for a few reasons since this is the path I have started I have no options to backtrack to the back to the Fiat/Abarth OFW. Today I installed the M OFW 74.00.230 NA. I have immediately noticed some improvements to overall stability and smoothness of overall operation. It seems that there was ajump in firmware version recently. This didn’t add any new features (Wireless CarPlay)

I know loosing the Abarth animations is a deal breaker for most people. Just wondering if anyone else has chose this update path for stability?

Also does anyone know if there is a way to inject the Abarth animations into the M OFW prior to install? (Creating a Custom Firmware) I am not a big fan of tweaks and prefer performance stability.
@ameridan

 

[ameridan]

Garrett, I found this:
"Wireless CP requires special hardware inside the CMU. It is not just a software solution, even if both new CMUs part numbers (with and without CP) have the same firmware. So it is about the same as with wired CP/AA (same firmware, but requires hardware to be activated). You can not activate Wireless CP in a CMU which does not have the wireless CP hardware in it."

I don't think you can intercede with id7 on this version, so I don't believe you are going to be able to customize. I honestly don't know why you need to upgrade to this version?

 

[Garrettt93]

Garrett, I found this:
"Wireless CP requires special hardware inside the CMU. It is not just a software solution, even if both new CMUs part numbers (with and without CP) have the same firmware. So it is about the same as with wired CP/AA (same firmware, but requires hardware to be activated). You can not activate Wireless CP in a CMU which does not have the wireless CP hardware in it."

I don't think you can intercede with id7 on this version, so I don't believe you are going to be able to customize. I honestly don't know why you need to upgrade to this version?

Yes,
Hardware is needed for wireless CP. That portion was included as more of a FYI to those who may have been asking the question. My question is can the firmware be modified prior to a update so that when the update installed it is pre modify with the Abarth/Fiat logos? Not to include tweaks but to “reskin” the newer firmware.

Sorry Oversimplification process** unpack the .up file from Mazda replace the related cosmetic files within the OS then repack the .up for deployment. I have "unzipped" the .up but this is about as far as I could get not knowing more of the interworking os the files system/OS

 

[NE_Fiat]

@Garrettt93, please report back on whether it is actually smoother and more stable. I don’t have problems with mine, but always gathering data on how things work.

also, are Apple Car Play or Android Auto included in the upgrade as standard?

 

[Garrettt93]

Hello,
I am reopening this topic. I was able to find the "conversion files"This includes the boot animations and CarPlay icons. As the CMU OS is is "This is obviously a linux-based OS running on an ARM chip." Other than @ameridan do we know of any Devs that have had experience with modifying the CMU OS or that would at least be willing to chat about this topic? I would be willing to put some time and $ to this "project". LMK

Again to reiterate my intention would be to create a custom firmware to apply to any Fiat/Abarth CMU.

This would include only the rebranding not to enable tweaks or other modifications. I have found that the newest version has less hangups and seems to run a bit better on my CMU.
I was having a few issues with freezing after the ACP install on 70.00.100

 

[winterarmada]

Sorry for reviving this old thread. From what I can see here we can modify the FW to its core components.. We need to find a proper way to decrypt/read the .dat files and from there do it slowly on how to proceed with the actual modifications.

 

[Garrettt93]

Sorry for reviving this old thread. From what I can see here we can modify the FW to its core components.. We need to find a proper way to decrypt/read the .dat files and from there do it slowly on how to proceed with the actual modifications.

I am glad you are here to help! I found the key a while back let me see if I can find it again after some googling.

Update*
I was unable to locate the key as the site that was hosting all the firmware data is bunk. I don't know if they key I had found is the same thing you were looking for though.

HiDrive

my.hidrive.com

HiDrive

web.archive.org

Hope this helps in anyway.

 

[winterarmada]

I was able to extract the data from the .up as archive with the code provided in your previous post/image. They are in .dat file format. I am assuming Mazda is using a particular "Firmware editor" to create the image in an ".up" package. I will start my initial steps in identifying a proper way in decrypting the .dat files presented in each folder and see how we could proceed further. We need more devs as you stated to see how can this progress forward

 

[anhnga]

I was able to extract the data from the .up as archive with the code provided in your previous post/image. They are in .dat file format. I am assuming Mazda is using a particular "Firmware editor" to create the image in an ".up" package. I will start my initial steps in identifying a proper way in decrypting the .dat files presented in each folder and see how we could proceed further. We need more devs as you stated to see how can this progress forward

That .dat is fake, these files are actually .gz files renamed .dat file, so if tyou rename it to .gz you will be able to extract it... Most hard work part i think is how to repack it and modify checksum to original file (like it never been edited before) because the flash app have checksum function on rest of upgrade firmware, if checksum error, it will fail to upgrade CMU....
That what i know for now after try to modify CMU firmware for many time, and not pass the checksum function of upgrade prcess...
Hope some one has solution for it....