Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
@CarlinKit Please address the problem several users have reported here about the the device rebooting when pressing the steering wheel voice button on Ford Sync systems. As soon as I press the button, Siri is summoned, but the Carlinkit V2 crashes and reboots. Makes the system difficult to use.
 
@CarlinKit Please address the problem several users have reported here about the the device rebooting when pressing the steering wheel voice button on Ford Sync systems. As soon as I press the button, Siri is summoned, but the Carlinkit V2 crashes and reboots. Makes the system difficult to use.
I have the CPlay2Air version with the same problem with Ford Sync 3.4+. I've heard rollback to last August's release, but I haven't tried it. I'm frustrated that so many have this problem but they have not addressed it in months!
 
I have the CPlay2Air version with the same problem with Ford Sync 3.4+. I've heard rollback to last August's release, but I haven't tried it. I'm frustrated that so many have this problem but they have not addressed it in months!
Hi, august version works fine on Ford Puma 2021 with Ford Sync 3.4
Other versions crash it when you say "Hey Siri" (or press vocal button)
 
I have the original CarLinkIt v1 dongle and it’s working ok in my car, the one that looks like this...
eab9c2882300ed7a4f3ce07fbd1c2311.jpg



However I’ve seen what looks like a copy/3rd party in Amazon that looks identical as the CarLinkIt v2 type, it says same size, removable USB-C cable, same 192.168.50.2 for updates etc. Pic of the one I’ve seen is below.

It’s very cheap, and wondering if I should buy, even for a backup etc. Is there any point in getting this v2 if my v1 is working anyway? Is there any benefits of the v2?

Has anyone had the v1 type of any of these dongles and bought the v2 and found any difference in anything.

e9f049e18ee8f5308847cf9dfca1edee.jpg


@VLud you seem to be very well knowledgeable on theseX not sure but seem to remember someone cracking some open and looking inside for differences, was that you, if so notice any?

Thanks
 
Last edited:
I have the original CarLinkIt v1 dongle and it’s working ok in my car, the one that looks like this...
eab9c2882300ed7a4f3ce07fbd1c2311.jpg



However I’ve seen what looks like a copy/3rd party in Amazon that looks identical as the CarLinkIt v2 type, it says same size, removable USB-C cable, same 192.168.50.2 for updates etc. Pic of the one I’ve seen is below.

It’s very cheap, and wondering if I should buy, even for a backup etc. Is there any point in getting this v2 if my v1 is working anyway? Is there any benefits of the v2?

Has anyone had the v1 type of any of these dongles and bought the v2 and found any difference in anything.

e9f049e18ee8f5308847cf9dfca1edee.jpg
Can't answer your question, but I have just pulled the trigger on one of these for 20GBP on Amazon. If it doesn't work, just send it back, no risk
 
I have the CPlay2Air version with the same problem with Ford Sync 3.4+. I've heard rollback to last August's release, but I haven't tried it. I'm frustrated that so many have this problem but they have not addressed it in months!
Yeah, I think @CarlinKit is in for a bunch of bad reviews and returns on Amazon if they don't address it. Seems like it shouldn't be that hard, but I do understand they're trying to support hundreds of different car types.
 
Thanks, I have tried it but still unable to rollback to CFW 02.02. I have put ARMimg_maker, U2W.sh and U2W_Update.img ( I have also tried renaming to U2W_AUTOKIT_Update.img) but my dongle has no green light.

Anyone has any success?
Hello @briancheng82 ,
I had succes downgrading from 2021/03/06 - Autokit CFW to 2021/02/02 Autokit CFW.
Please ensure:
- you really have a 'Custom Firmware' on your interface, if not the U2W.sh script will not be executed and a downgrade is impossible
- you create the U2W.sh script yourself by a text editor ensuring it's really a text file and not a html file, made the same mistake by downloading a different script file for getting the memory information, finally it turned out that my text file contained additional html code and therefore the intended function didn't happen.

@VLud , again something special for you...
after the downgrade the memory usage was equal to previous version though the last version is 1.1 MB bigger because of new drivers included. Is there a way to clean up the interface and get rid of unnecessary data? On you Github page I found a script but is this up to date for this application? Many thanks as usual! 👍 :)
 
Can't answer your question, but I have just pulled the trigger on one of these for 20GBP on Amazon. If it doesn't work, just send it back, no risk

That’s the one! £20 not sure on it, but also from Amazon as you say so should be ok for returns.

Have you got a current dongle? Which type?

I’ve just read about and some say the v2 comes with 5.8GHz WiFi to supposedly help. Apart from that seems same.
 
Who has the Carlink 2.0 USB-C adapter in use with a Mercedes A-class (W177) or CLA (C118) with MBUX?

If I use it directly from USB-A with the USB-C port of the car nothing happens. If I use it from USB-C with an USB-C adapter directly with the car then I can see the message that Carplay starts and after a few seconds there is a message that Carplay could not start.

In both cases the light from the adapter is permanent in red color. The Carplay adapter works perfect with my Mercedes C-class and has the version from February 2021.
 
That’s the one! £20 not sure on it, but also from Amazon as you say so should be ok for returns.

Have you got a current dongle? Which type?

I’ve just read about and some say the v2 comes with 5.8GHz WiFi to supposedly help. Apart from that seems same.
I have a CarPlay2Air at the moment. I have ordered 2 of these, one as a spare and if they don't work just send them back. If they are OK, I'll move on my CP2A on eBay or similar. I prefer them as you can change/replace the USB cable, I think long term the fixed cable on my current one and the original CarLinkit may cause a problem as cables/ connections are usually the weak link.
 
Hello @briancheng82 ,
I had succes downgrading from 2021/03/06 - Autokit CFW to 2021/02/02 Autokit CFW.
Please ensure:
- you really have a 'Custom Firmware' on your interface, if not the U2W.sh script will not be executed and a downgrade is impossible
- you create the U2W.sh script yourself by a text editor ensuring it's really a text file and not a html file, made the same mistake by downloading a different script file for getting the memory information, finally it turned out that my text file contained additional html code and therefore the intended function didn't happen.

@VLud , again something special for you...
after the downgrade the memory usage was equal to previous version though the last version is 1.1 MB bigger because of new drivers included. Is there a way to clean up the interface and get rid of unnecessary data? On you Github page I found a script but is this up to date for this application? Many thanks as usual! 👍 :)
I have tried everything and I'm not able to downgrade... says I'm on 03.09.2021... I got there using Custom Firmware (that I installed via USB)... so it's really weird I can't get it to downgrade. I've followed all the instructions here. At least it's not bricked... but man, I just need the steering wheel button for SYNC to work or else this is going right back to Amazon.
 
Stay cool and ensure all files contain the right content.
I included the 2021/02/02 Autokit CFW for downgrade and it worked finally.

Alternative you could try to 'RESET' via the 192.168.50.2 interface site as somebody mentioned before. Should also be a downgrade to previous official version.... but without any warranty.... :rolleyes:

The USB stick has to contain this, check the file size...:
Bildschirmfoto 2021-03-11 um 23.39.28.png
 
  • Like
Reactions: radioboy77
I was running standard 2020-12-10 firmware in a Car2Play with my 2018 Subaru Impreza with the Harmon Karden head unit. There were a couple of small issues, but overall it was performing reasonably well. I decided to try the standard 2021-02-02 firmware and it works fine in my Subaru. I used the USB flash drive upgrade method. I expect it would work well in all Subaru’s that are running with 2020-12-1 firmware0. I didn’t try the Ludwig custom firmware.

I also compared the Car2Play with a Carlinkit CPC200-U2W Plus. They both work with the same firmware, but the Carlinkit appears to be built better and seems to setup to working Car Play a bit faster. I would recommend buying the Carlinkit CPC200-U2W Plus.
 
Stay cool and ensure all files contain the right content.
I included the 2021/02/02 Autokit CFW for downgrade and it worked finally.

Alternative you could try to 'RESET' via the 192.168.50.2 interface site as somebody mentioned before. Should also be a downgrade to previous official version.... but without any warranty.... :rolleyes:

The USB stick has to contain this, check the file size...:
View attachment 1742438
I appreciate the help, but still not working. I double-checked all the files on my USB and they match yours. I even clicked "RESET"... said "Are you sure?" said "OK" and nothing. It's really bizarre. I don't get why this isn't working for me. So frustrating.
 
If we don't find the solution I'm sure @VLud knows what to do.....
Did you ever check the memory usage by putting a different script on the USB stick? Maybe this shows something special.
Content of U2W.sh should be:
 
You should get U2W.txt created when the script is executed, if not the USB Key is not correctly created, send us a screenshot of your USB Key files to confirm
 
You should get U2W.txt created when the script is executed, if not the USB Key is not correctly created, send us a screenshot of your USB Key files to confirm
Oh boy....thank you @VLud *I* am a moron! My U2W file had alllll sorts of extra stuff in it. I copied/pasted the RAW file info from your repo and everything worked RIGHT AWAY! I downgraded to the August FW and can confirm that Ford Sync's steering wheel button does indeed work. I appear to be down now on the green/blue boot interface rather than the Autokit (even though I used the CFW) but at least I can use my steering wheel voice controls.
 
Here's my personalized interface to match my vehicles UI fonts and design language. Thanks to @VLud for making this all possible. I was using the MMB, but given I can customize the U2W based dongles, I'm switching back. I'm using the Car2Play dongle because for some reason, the touch response is better in my vehicle vs the Carlinkit CPC200-U2W Plus. Not sure why the two would perform differently using the exact same firmware.

IMG_7771.jpeg
 
I want to share this information with MAZDA owners. I was on the known working 2021.01.28. Today I brought up the 192.168.50.2 page and it showed that there is a new version 2021.03.06.1343 to "Fix disconnect problem on MAZDA". I decided to let it go ahead with the update in the car because I know the 2021.01.28 would not reboot every 30 seconds. It should be able to finish the update with the car power.
IMG_5929.PNG


It updated and rebooted itself. Looks fine.

I know the 2021.03.06 image has been out for a few days and people have been talking about it. Just want to let MAZDA owners know that this version works for me.
 

Attachments

  • IMG_5930.PNG
    IMG_5930.PNG
    663.6 KB · Views: 119
Last edited:
I just did over the Air 3/6 V1 Carlinkit it in my Palisade 2020 no drivers package, success..... Please wait after it says success on Iphone it’s premature it took almost 1-2 minutes after before it was really done. I actually gently peaked at the blinking lights. I would if that’s not visable wait a solid 2 minutes after upgrade says its done. Normally u know its done cause it disappears from car dash AV and reappears when done. This time it was at least a minute later after before it disappeared and another minute before it came back.
 
<...>
I know the 2021.03.06 image has been out for a few days and people have been talking about it. Just want to let MAZDA owners know that this version works for me.
I also upgraded from the 2021.01.28 (which I had tried to upgrade before to the February code). The upgrade appears to have gone fine, and my Mazda is as happy as before. I may stick with this code unless I am tempted by a nicer boot screen :)
 
  • Like
Reactions: chari
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.