Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I still am told that 2021.01.08 is the most recent OTA version. I’m not up for loading custom firmwares unless they are an improvement over stock for bug fixes.
 
I use a cplay2air with an XAV-AX1000. The head unit *must* be on the older Sony 1.01 firmware. If it has the 1.2x Sony firmware my experience is that the head unit will just go into a reboot loop as soon as the cplay2air adapter is connected. That said, there are some issues: #1 - You can "Hey Siri <ask something>" in a single command and it works, but if you do any Siri requests that require "back and forth" it acts like the mic isn't working when you try to respond. So, "Hey Siri text so and so" prompts siri to ask "what do you want to say" .... but it will never pick up your response. Additionally, the mic doesn't work for phone calls. Other than those 2 (rather large - depending on your use case) issues, it has worked pretty well for me. I personally make due by switching to "speaker" on the phone if I have to make or receive a call, and using my apple watch for more complicated Siri commands that I can't ask in a single request. You can trick the Sony into downgrading the XAV firmware pretty easily if you get a copy of the 1.01 firmware and then rename the file so the Sony thinks it's one version ahead of what's currently on the unit, and by using a hex editor on the first 2 bytes of the file to set the "version" that is embedded there to also be one above whatever firmware version number is currently on the radio. For example, if you have 1.20 installed, you'd rename the 1.01 files to be 1.21, and change the first 2 bytes of the firmware from "01 01" to "01 21".
Hey I have a Sony XAV-AX8000 with 1.25 and I get the boot loop. Tried cplay2air 1.08.2021 and 2.02.2021. Do you know how I could get my hands on the 1.01 Sony firmware? Can't find it on google. It's probably different from the 1.01 firmware for the XAV-AX1000 but do you have a copy I could try for the heck of it?
 
I was actually shocked today. I completed the cplay2air survey they sent me yesterday. I was honest and said while it works great 90% of the time I do get the occasional drop out. Someone in customer support emailed me today and said they got my feedback on the survey and want to help solve this for me. Their first question was what firmware I was running. We will see if they know about it or recommend another version.
 
hi I have no problem with the MMB Carplay it worked perfectly, I did a reset and when it was restarted it no longer worked the red led keeps flashing. how can i solve?
 
ANYONE OF FORD SYNC 3.0 READ THE FOLLOWING BELOW

Just a quick update to those that are still on Ford Sync **3.0** (not 3.1, 3.2, 3.3 or 3.4) just received my dongle and its working nicely on update (2020.12.25.1731)

Steering Wheel controls work with Siri Button

Touch Wood (Good Luck) -
Remember if something is working for you DO NOT UPDATE as you could break it
 
A question does anyone notice any difference between setting to CD instead of DVD in settings for slight latency in switching tracks using apple music on this wireless carplay dongle
 
Amazing! After reading this comment I realized that mine was not updated, so I got it upgraded to the latest (2021.02.02) and it finally worked! Still having the same issue as you on reboot, but I will use the same script for now, thank you Renato.
The official firmware (2021.02.02) does not run scripts on pendrive. Just the changed firmware does it. The ludwig user made changes on that firmware.
 
I received an email from Carplay2Air in November that they added support for Nissan 2017+. I have a 2017 Maxima so I was excited and decided to try it out. It was delivered yesterday but I can't even get it to setup at all :(

Every time I plug it in I just get the "Failed to start carplay" message and then it reboots and does the same thing over and over. I've tried removing my phone from the car and everything but I can never get it to boot up correctly. I can't even see a WiFi or Bluetooth connection for it. This is beyond frustrating.

@AMTYVLE @Quiver

I got this working on my 2017 Nissan Maxima. I worked out two separate solutions to solve the same problem. The issue is that not enough power was getting to the device. I noticed that the red light would shut off once it booted up connected to the car, which it did not do on a separate Pioneer headunit with Carplay installed.

Here is my first (old) solution:

Using USB 1 and USB 2 ports in the Maxima with a y-splitter cable.

1613690022424.png


I installed this and tucked it all away in the small front compartment and it worked without any issues for about 2 weeks before I implemented my second solution.

Here is my second (current) solution:

I tried ordering a Mission Cable for Amazon FireTV from Amazon:

1613690210732.png


However, this was way too large and provided power only and no data connection. Next, I ordered this older Mission Cable which is much smaller and uses 2 capacitors instead of a battery. (Note the model number)

1613690391696.png


The problem I had with this was the same as the first, as it offered only power connection. I ordered this angled USB-A to USB-C cable with data for the Carlinkit 2.0 (with USB-C connection).

1613690567763.png


I removed the case for the Mission Cable capacitor and removed the USB-A and Micro USB red/black cables. Then I sliced open the sheathing of the cable. I did not cut the cable, only removed the outer rubber and left the data connections in tact. I cut the red/black power cables and soldered them to the inside of the Mission Cables board.

What I was left with was an angled USB-A to USB-C cable with a small MC cable in between. This worked perfectly in my 2017 Nissan Maxima. The Carlinkit remains powered on about 10 seconds after it is turned off or unplugged. Unplugging the device for 10-15 seconds shutdown the device completely.

1613691479958.png
1613691506859.png


Hope this helps! This worked in my case when the car would not recognize the device at all. Please let me know if this helps anyone else.
 
Last edited:
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
I prefer your ui than the one I have… so hopefully this is a preview of things to come… seems like that firmware was installed on accident… Have you tried reporting it via the built in webpage report form? Apparently that goes to the developers…
I just received a unit today with firmware version 2020.12.25.1731 with the red UI. I purchased from here on Amazon:


This was the "for Pioneer, Alpine, Kenwood" option. However this is different from the one I purchased 3 weeks ago which was the "Audi" option. I am currently running 2020.11.10.2137 on that one (with no option to update OTA).

Does anyone know how to extract the firmware from a running unit? I would like to install 2020.12.25.1731 on both my units. I wish there was clarity as to what is different in the firmware, as the OTA firmwares are 2021.01.08 and 2021.02.02 and it is a toss-up as to whether my device will offer the update or which one it will allow. I am tracking the issue that some people with the 2020.12.25.1731 do not seem to be able to update OTA or USB. I have not tried as I do not want to lose the firmware I have installed on it right now. Has anyone tried the "Reset" from 2020.12.25.1731? What does it do, and what firmware does it end up on?

The main reason I want to update is because no matter what I do, the Carplay name is NEX-5765. I have tried rolling back the firmware, but have found no way to factory default the device. The new device with the red UI will actually display my car model with numbers after it. I would like to be able to differentiate between my different Carplay cars.

Thanks!
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Has anyone tried the "Reset" from 2020.12.25.1731? What does it do, and what firmware does it end up on?
From memory when I did it, it just resets connections with devices, but doesn’t change any settings or firmware.
You can rollback to an older firmware that still uses the same UI, but has less settings options.

I’m getting sound cut outs that changing the delay setting doesn’t fix, so keen to update the firmware when it’s actually possible, which means a new OTA update.
 
  • Haha
Reactions: Suckfest 9001
From memory when I did it, it just resets connections with devices, but doesn’t change any settings or firmware.
You can rollback to an older firmware that still uses the same UI, but has less settings options.

I’m getting sound cut outs that changing the delay setting doesn’t fix, so keen to update the firmware when it’s actually possible, which means a new OTA update.
Same with me and their customer support reached out to me and ask me to send them the log from the device. I just did that. They said they are working on an update. This is cpaly2air.
 
From memory when I did it, it just resets connections with devices, but doesn’t change any settings or firmware.
You can rollback to an older firmware that still uses the same UI, but has less settings options.

I’m getting sound cut outs that changing the delay setting doesn’t fix, so keen to update the firmware when it’s actually possible, which means a new OTA update.
I was timing the connection on 2020.12.25 compared to 2021.02.02 on my other device and was consistently getting 60-90s to connect vs 20s. I rolled back the FW and now I get 25s connection time and same UI. It is strange that this version cannot be manually updated to the other UI version. Looking forward to future testing with it.
 
I tried unsuccessfully to update my CP-21 using the MMB FW, I got a popup in the UI to launch the UPdate, but the system told me the imager was wrong. Certainly a diff in the .ini files.
I follow the proposed cross FW solution found at #5167 and #5168
Update:
Seller send me a new firmware (Ver.210106) as a zip file (#5173 reveal the full image). Can confirm that there is a small difference in system_version.ini within the update .zip (CP-21 = ABUPDATE_FOTA_DEVICE=107_mj_abr_ty; MMB = ABUPDATE_FOTA_DEVICE=107_mj_abr_zyd).


Can someone shares the lastest FW for CP-21 (not the one from MMB)?

Thanks
 
I tried unsuccessfully to update my CP-21 using the MMB FW, I got a popup in the UI to launch the UPdate, but the system told me the imager was wrong. Certainly a diff in the .ini files.
I follow the proposed cross FW solution found at #5167 and #5168
Update:
Seller send me a new firmware (Ver.210106) as a zip file (#5173 reveal the full image). Can confirm that there is a small difference in system_version.ini within the update .zip (CP-21 = ABUPDATE_FOTA_DEVICE=107_mj_abr_ty; MMB = ABUPDATE_FOTA_DEVICE=107_mj_abr_zyd).


Can someone shares the lastest FW for CP-21 (not the one from MMB)?

Thanks
Does anyone have a place to download the latest firmware for the CP-21 adapter? Just received mine from Aliexpress last week and working pretty good so far except the skip forward and back buttons on my steering wheel don’t work (2019 Chevy Traverse).

Current firmware is v1.0_107_003_2021010617.
 
Does anyone have a place to download the latest firmware for the CP-21 adapter? Just received mine from Aliexpress last week and working pretty good so far except the skip forward and back buttons on my steering wheel don’t work (2019 Chevy Traverse).

Current firmware is v1.0_107_003_2021010617.
There is a thread in XDA Developers forum where one CP-21 user states that Joyeauto has the same dongle, but ofcourse reBranded as Joyeauto.

The user further states that Joyeauto provides firmware for that dongle in their download section so you might want to check that out.

update : I just made a quick look on that thread as to what thay are discussing, and found out that they are actually sharing/exchanging firmware files.
 
Last edited:
There is a thread in XDA Developers forum where one CP-21 user states that Joyeauto has the same dongle, but ofcourse reBranded as Joyeauto.

The user further states that Joyeauto provides firmware for that dongle in their download section so you might want to check that out.

update : I just made a quick look on that thread as to what thay are discussing, and found out that they are actually sharing/exchanging firmware files.
The only thread I could find at XDA was for the Android box, not just the wireless CarPlay plus device. Can you post or send me a link? Not having any luck finding at the moment.

Overall, even without the skip forward/back buttons on my steering wheel this is a huge step up from the first gen carplay2air adapter I had. Haven’t had much time to play with it other than a quick trip to Costco this weekend, working from home has its benefits but don’t get to spend nearly as much time in the car.
 
I've just received mail from my vendor and the latest FW for CP-21 is still 2021010617.
 
Amazon Lightning Deals $25 off. That is $74 for the next 3 hours if you act quick.
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Amazon Lightning Deals $25 off. That is $74 for the next 3 hours if you act quick.
That’s a good deal!
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Need a little help as I have never had an issue. I am using a Carlink Kit 2. I was flashing the latest firmware 2/2 from 1/28 Vlud (I had a skipping/pause issue with music). I have done this many times over the months. Today however it went sideways. The flash went just like it normally does however I get the following on power up

Hardware Error: Wi-Fi

In the bottom right of the screen I have:

0650c80150deCMP

Any suggestions, I have been fortunate the updates always work great... @VLud
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.