2004 to 2020 Mazda 3 Forum and Mazdaspeed 3 Forums banner
181 - 198 of 198 Posts

· Registered
Joined
·
3 Posts
My chip is not able to be detected. I tried wiring from the 16-pin - 16 pin adapter to the chip and also the 16 pin clip cut and clamped into the connector pins. This did not work either. What's going on and is my chip just totally gone? I really don't want to have to buy a new unit.
 

· Registered
Joined
·
4 Posts
Hey all, I unblocked my unit after a failsafe fail on my part. Can't believe I turned off the car when it finished... Anyhow these forums and posts were amazing! I am not tech savvy at all, trust me, and I got it done. I used the CH341A programmer that puts out 5V instead of the 3.3 its supposed to. The work around was where I drew the line to get it to properly output the 3.3. I didn't care anymore at that point and if it messes up the chip I will just order a used CMU for $200 on eBay in the future.
 

· Registered
Joined
·
13 Posts
Hello everyone. I sucessfully installed tweaks but I have 2 problems.

1) When I plug my phone, I see notifications on my phone says "android auto connected" again and again and mazda's screen goes to black. I tried with another phone and bought new high quality cable but the result hasn't changed. After trying a couple of things on android auto app on the phone (forget all cars, connecting wireless etc), my phone says "connecting to android auto" but nothing happens.

2) After downgrade & upgrade I saw all my previous bluetooth connection list and I cannot remove them.

I would be happy if anyone could help me to fix these problems.

Thank you
 

· Registered
Joined
·
13 Posts
I found a message on this forum that complains about black screen issue after updating to 70.00.100 and says the problem was fixed after downgrading to 59.00.545. This could help someone on this post who tries to fix the cmu.

By the way, I found 59.00.545 but it was broken. Is there anyone that can help me to find that version please?

-------------------------------------------------------

I downgraded the firmware from 70.00.100 to 59.00.545 and android auto black screen issue is fixed.
 

· Registered
Joined
·
1 Posts
Hi,
So I recently attempted and succeeded at upgrading my 2016 Mazda 3 GS with Apple CarPlay/Android Auto. However my experience was not as smooth due to my ignorance, but with the help of many sources I got it figured out. I wanted to write this post to share my personal experience and to kind of put together the different posts that I used to figure this out.

Part 1: Firmware Update
My firmware version was 56.000.xxx on my original unit so I would only have to do the single update (2 files) to get to 70.000.100. I started off by following this guide on YouTube:
until I stupidly decided to turn the car off between the firmware update file and reinstall package. As many of you probably know this BRICKS your CMU and you will be left with a black screen and audio from the last radio station you had open.

Part 1b: Unbricking your CMU
So now I’ve bricked my CMU. There are people here who explain the situation way more in detail and properly compared to what my understanding is so look around if you want a run down of the problem. But now I had to take out the CMU. Which is nicely explained here:
Once I had the unit out, I undid ALL the screws which are a combination of phillips and torx 20 screws. (They are also cleverly color coded from Mazda) After taking out the torx screws I popped off the metal cover and revealed the SPI NOR flash chip:
View attachment 287640

this is the chip that you need to read and flash. As far as I found there are two ways to do this.
1. With a cheap USB programmer
2. With a raspberry pi
Your mileage may vary, but the USB programmer did not work AT ALL and I only succeeded when using the raspberry pi. This forum post (up above explains how to use the raspberry: Black Screen MZD

Here’s what happened to me. Because I did not have access to a raspberry pi I decided to try the USB Programmer method explained here:
This process requires you to erase the original contents of your chip after you do a backup. (DO A BACKUP) Now I’m not sure if it was because of the USB programmer, or if it was the test clips I was using but I had problems reading and writing and essentially ended up with corrupted files and an empty chip. So now is when I went for help. Find someone who not only has but KNOWS how to use a raspberry pi. In the video that uses the USB Programmer there is a link to a google drive in the description with a copy of the users own modified file of the flash chip. Essentially I used the raspberry to flash that file from the google drive onto my chip. It’s not crazy complicated, but you can use the code from the forum post above:
to achieve this. Go to the line where the user writes “Now it’s time to write the modified file to the flash” and in the line of code below replace “cmu-mod.bin” with the file name of the modified version posted in the Google Drive. You can verify if it worked by switching the file names in the other lines of code, but once I installed the CMU back into the car I was prompted to insert the USB containing my reinstall package to which the installation went off without a hitch. (Pressing the clutch (manual) every 15 minutes). , I was left with a successful update to firmware 70.000.100

Side note: I also tried various ways the attach the flash chip to the raspberry pi. Ideally, you get an SOC16 Test Clip, but there are pretty hard to find in Canada so I opted to use an SOC8 Test clip for half the connections and used individual test clips for the other half of the connections:
View attachment 287641



Part 2: Installing the USB Hub
So there are plenty of tutorials online for how to Install the USB Hub when it is located in the center armrest, but my hub was located in the front of the Center console under the climate controls making the removal of the old hub more difficult. There is the hack to drill through the 4 clips, but I decided to opt out of that wanting to save my OEM part. To my surprise, taking it out properly wasn’t that difficult despite the lack of tutorials online.

Essentially, I had to slide the entire center console back which is well shown in this video here:
Now I’m this video the guy gets to a point where he takes out completely the center console including the arm rest, I DID NOT have to do this. Once I had the center console slid back about 5 inches, I was able to reach in and undo the 2 top clips of the USB hub and get the top edge poking out of the hole while keeping tension. Next with my other hand and a flathead screwdriver, I was able to reach in and pop one of the bottom clips and once that clip was free I was able to wiggle the USB hub out without undoing the last clip. What comes next is relatively easy, you run the new cables through the glove box up to where the touchscreen is wrapping everything in sponge tape. Next I tested everything to make sure everything was working then zip tied the cables to parts of the interior so that they wouldn’t wiggle or rattle around. Note: you should take the ends of the old USB Hub cable and zip tie/sponge tape it to the new cable so that the loose connector doesn’t rattle around either. Closing everything back up in the opposite way it was installed I finally had CarPlay in my car.

Obviously, don’t be an idiot like me and brick your CMU and you could have this whole process done in 2-3 hours, but for the few who do I hope my experiences help. For the USB hub installation, it is more difficult when it’s in the front, but still only took and hour, plus I got to save my OEM Hub.

Again hope somebody can benefit from this!
How did you go about downloading the modified file to the raspberry pi? When I try to simply download it and change the command line to the name of the file, it says it cannot find the file. I have tried the ch341a programmer many times with both the clip and separate jumpers to verify my connection was good. I am in a constant boot loop on the firmware failure menu after my Mazda dealer bricked the system. A different mazda dealer said they were able to read the contents and said the dealer who did it accidentally downgraded me to v33 from v59 instead of upgrading like I requested. I have tried flashing v59, v70, v56, v31 .bin files to my chip with ch341a with no luck so I moved onto the raspberry pi. I modified the file as outlined in post on page 1 but still in a boot loop. Your method is the only one I have yet to try. Any help would be appreciated.
 

· Registered
Joined
·
2 Posts
After trying to upgrade from 56.00.240 straight to 74.00.311 I made cmu brick. I followed this tutorial, changed FF to 00
I plugged in the usb to install the firmware 70.00.100 like in the video, but the system shows verifying package and then rebooting, then verifying again, … Someone help me pls
 

· Registered
Joined
·
5 Posts
Hopefully someone can help me...my 2016 cx5 infotainment crashed, it kinda died via cold weather.. it just kept rebooting itself.... I found threads like this and bought the parts etc. I used ride & lives Modified file...and I can get the screen to the insert usb etc..etc. I found a few .up files...but that don't load..they verify and then reboot and try again and again. I have no clue what version I was as ...I just want my infotainment and back-up camera back. Anyone know what I could try?
 

· Registered
Joined
·
126 Posts
Hopefully someone can help me...my 2016 cx5 infotainment crashed, it kinda died via cold weather.. it just kept rebooting itself.... I found threads like this and bought the parts etc. I used ride & lives Modified file...and I can get the screen to the insert usb etc..etc. I found a few .up files...but that don't load..they verify and then reboot and try again and again. I have no clue what version I was as ...I just want my infotainment and back-up camera back. Anyone know what I could try?
If it’s a hardware failure you can find a replacement CMU on eBay. They are pretty much all the same unit and don’t require any programming.
 

· Registered
Joined
·
5 Posts
No, the infotainment started Boot looping randomly. It has never been modded previously.

I looked online and decided to try to "fix it"

I bought the ch416 programer thing and got it to this screen now.

Maybe I should try using this file?

'rom-513b.bin'
 

· Registered
Joined
·
327 Posts
System is searching for a compatible firmware to continue, do you know what firmware was running originally? and what version failsafe you have program? Put in the flash drive a bunch of firmwares versions, all you can fit on it and maybe it will recognize one of them. Try another flash drive. If you saved the original SIP ROM file PM it and I'll tell you what version you have running.
 

· Registered
Joined
·
5 Posts
System is searching for a compatible firmware to continue, do you know what firmware was running originally? and what version failsafe you have program? Put in the flash drive a bunch of firmwares versions, all you can fit on it and maybe it will recognize one of them. Try another flash drive. If you saved the original SIP ROM file PM it and I'll tell you what version you have running.
Is the SIP ROM the backup file? I did that not sure if it backed up properly. Will send to you thanks.

No idea what it was running in the past
 
181 - 198 of 198 Posts
Top