74.00.230A NA N is available on HiDrive. There is no change log and the instructions still mention the older version, so I don't think I'm going to upgrade yet.
I am not updating instructions as the install process is Identical to all other single file update.up files.
Changelog is not available and maybe sometime, 70.00.367A is the outdated firmware now, all US Dealers are installing 74.
Might update instructions next year when MZD Connect is finished with updates from Mazda as it will no longer be in use, I expect you may see 1 possibly 2 in the wild releases.
Once all models are out of production there will be no more.
Mazda 6 ends late this year for all new Gen start for 2022.
CX-3 ends early 2022....I believe will be discontinued.
MX-5 gets the 10 inch screen .kwi update like CX5 and 9 later next year.
That leaves the long in tooth Mazda 2 (Demio) only one with MZD, if EU discontinues and looks like AU will also that only leaves the Japan Demio.
The end of MZD.
Just as info: I updated to 74.00.230 NA from my 70.00.367 EU at my bench (not in the car), and it worked perfectly. Also a downgrade back to 70.00.352 EU worked. I used an "old" CMU from 2015. I did not perform any other feature/function tests.
74.00.230 is said to be the official update for 70.00.367 (and for 74.00.200 which is installed at new CMUs from factory only).
No, I can not. 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.
No, I can not. 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.
Hey Tristan. This is something I'm not clear on. I have a '16.5 GT CX-5 and have been using AIO Tweaks almost since it came out. I see that WiFi gets enabled via the tweaks. So wouldn't this allow for AA/Carplay to work wirelessly? Especially if you had the USB hub update?
No, the AIO tweak for enabling WiFi will not enable Wireless AA/CP. This tweak simply enables WiFi at the MZD, which is disabled for some regions (NA at least). In other regions you can buy some subscription for online services of Mazda, which require WiFi. But even when WiFi is enabled (like in my EU region) at the CMU/MZD this does not enable Wireless AA/CP and there is no way to do so. Unfortunately.
I am waiting for the 4A N release of the 74.x firmware for my 2017 Mazda6 GT and my wife's 2018 Mazda2 .
Currently we are on the 70.00.100 firmware on both cars, and we are having 2 minor issues detected with CarPlay:
When I am listening to FM radio and answer a call on CarPlay, after the call ends, sometimes the radio stays silenced. I have to manually choose again the FM radio, and that's annoying. This doesn't happen when you are listening to Spotify
Also, I am having problems with Waze and the dark/light mode map color. Sometimes, when you enter the App, it stays in light mode, others, it choose dark mode
It is anyone else having these issues? Or, do you know if these problems are fixed in .367?
I can choose to upgrade now to .367 or instead wait for 74.x.
If I'm coming from 55.x do I still need to go to 70.00.100 before v74? I am getting conflicting information that the latest updates without the failsafe can be install from any version above v31?
Mazda`s recommendation is to install 70.00.100 if you are coming from FW 55 and want to install any FW above 70.00.100 - so this also counts for your desired 74.00.230.
Is anyone getting GPS related errors with this update? For example, I turn on my 2016 Mazda 3 iSport (US) and the clock sometimes is off by a lot (I'm assuming the time is when the car was off) until it gets GPS signal. It seems there are issues with the GPS sync setting. Also I'm losing GPS signal sporadically where the Mazda compass doesn't even work. I don't have Mazda nav, but when I'm using Android Auto these issues become noticeable.
I did factory reset after the upgrade, but I'm still having issues, would re-installing the firmware have a chance to do a deeper reset? I also re-seated the GPS antenna and cable.
Mazda navigation screen stuck in a loading cycle after updating to v70.00.100A. The hub was replaced with the new module to allow for AA/CP. AA/CP work just fine. SD card removed/reinserted. Tried soft-reset while holding the 3 buttons and also updated my SD card through Mazda toolbox and still no luck. Would upgrading the firmware v74 fix this issue or is this something that needs to be addressed separately? I am not sure if my SD card is having a compatability issue with the firmware or new usb hub. I am contemplating ordering another SD card, but want to explore all options before I pull that trigger. I do have a backup of my SD card through toolbox.
As far as I know there isn't any navigation compatibility with any of the firmware versions. Make sure SD card has the write enable ON
I wouldn't go to version 74.00.230 not yet anyway. I've read sometimes people had this issue but after a few reset and letting the system go to sleep eventually would work.
As far as I know there isn't any navigation compatibility with any of the firmware versions. Make sure SD card has the write enable ON
I wouldn't go to version 74.00.230 not yet anyway. I've read sometimes people had this issue but after a few reset and letting the system go to sleep eventually would work.
I just updated a new to me 2015 mazda3 from 55.00.753 NA N to 70.00.100 . I'm unsure whether to update directly from here to 74.00.230 version because when I tried that, it said license not recognized. You've also removed the 70.00.367A (NA N) from hidrive. What is the next update I should do?
I am not updating instructions as the install process is Identical to all other single file update.up files.
Changelog is not available and maybe sometime, 70.00.367A is the outdated firmware now, all US Dealers are installing 74.
Might update instructions next year when MZD Connect is finished with updates from Mazda as it will no longer be in use, I expect you may see 1 possibly 2 in the wild releases.
Once all models are out of production there will be no more.
Mazda 6 ends late this year for all new Gen start for 2022.
CX-3 ends early 2022....I believe will be discontinued.
MX-5 gets the 10 inch screen .kwi update like CX5 and 9 later next year.
That leaves the long in tooth Mazda 2 (Demio) only one with MZD, if EU discontinues and looks like AU will also that only leaves the Japan Demio.
The end of MZD.
70.00.367 NA is still there, just in another folder called zDevelop/Outdated: HiDrive
As far as I know, officially 74.00.230 is the update to 70.00.367 (and previous versions). Wondering why it states the license issue if you try to update. So far you have done everything right... coming from FW 55 you updated to FW 70.00.100 first, before going on. I would try to update to .230 again - if this does not work, to .367 first... but remember that every FW update drains the battery. Use a charger or do some drives in between the updates, just to minimzine the risk of bricking your CMU during an update due to a dead battery.
As far as I know only via OBD-Adapter (e.g. ELM327) and apps on your mobile device or via laptop (e.g. ForScan). There is no "hidden" menu in the MZD to show the BATT_SOC value (battery state of charge) - and I guess this is because our cars have a battery management, which sometimes lets the battery drain a little to be able to charge it afterwards more... and this behaviour is not understandable for most users - so displaying the BATT_SOC would irritate more people than help them.
Is anyone getting GPS related errors with this update? For example, I turn on my 2016 Mazda 3 iSport (US) and the clock sometimes is off by a lot (I'm assuming the time is when the car was off) until it gets GPS signal. It seems there are issues with the GPS sync setting. Also I'm losing GPS signal sporadically where the Mazda compass doesn't even work. I don't have Mazda nav, but when I'm using Android Auto these issues become noticeable.
I did factory reset after the upgrade, but I'm still having issues, would re-installing the firmware have a chance to do a deeper reset? I also re-seated the GPS antenna and cable.
Yes I'm having the exact same issue on my 2020 CX-5 GT after upgrading to firmware 74.00.230A. Happens ~every other time I start my car. So frustrating.
Flipping "GPS Sync" off and then back on fixes the clock, but it's annoying to have to do so frequently.
I did come across this related TSB, but nothing actionable on it other than toggling the GPS Sync
70.00.367 NA is still there, just in another folder called zDevelop/Outdated: HiDrive
As far as I know, officially 74.00.230 is the update to 70.00.367 (and previous versions). Wondering why it states the license issue if you try to update. So far you have done everything right... coming from FW 55 you updated to FW 70.00.100 first, before going on. I would try to update to .230 again - if this does not work, to .367 first... but remember that every FW update drains the battery. Use a charger or do some drives in between the updates, just to minimzine the risk of bricking your CMU during an update due to a dead battery.
I tried both 70.00.367 and 74.00.230 again. I got message saying Validation Failed--Failed to validate package certificate. I currently have version 70.00.100 NA N.
This didn't happen when updating to 70.00.100 NA N. I'm using a Kingston 2Gb pen drive. I'm debating whether an update beyond this point is worth it. Should I install the new usb(Carplay) unit with 70.00.100?
@2015mzd3owner : Perhaps your downloaded files are not exactly the ones which are on the server. Perhaps you have to download them again. Before doing so, I would check the checksum/hashes of the downloaded files - see instructions in this folder: HiDrive
If the update to a higher version is worth it, you have to decide by yourself. You can search the forum for each firmware version thread - often there are changelogs mentioned in a post. I can not tell you what you should do, but you can install the new/official AA/CP hardware with 70.00.100 and AA/CP will work.
that is a sign that the file was corrupted, either when you downloaded it or on the usb stick. The installation software is checking against a checksum to discover exactly this.