This all jives with my experiences as well... been battling it for a few weeks now, trying to install the custom firmware so I can install my custom UI. It seems like they made the v3.0 devices non-rollbackable -- only can install 2020.03.06. Anything earlier won't install. That is probably their new "fail safe" and to protect hacking and easy for them to handle/check in their code.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
CarPlay CarPlay adapter to convert to wireless CarPlay?
- Thread starter MrMister111
- Start date
- Sort by reaction score
This all jives with my experiences as well... been battling it for a few weeks now, trying to install the custom firmware so I can install my custom UI. It seems like they made the v3.0 devices non-rollbackable -- only can install 2020.03.06. Anything earlier won't install. That is probably their new "fail safe" and to protect hacking and easy for them to handle/check in their code.
Not that it helps... But, I did find that if are on 2021.03.06, you can "rollback" using the OTA update to the 2020.12.xx (I forget the day, I want to say 25 or 27)... I've actually got my device running on this version currently. It shows the OTA update available now for 2021.03.06... Figure I'll take baby-steps on upgrades and see if I can find one that might handle my issues a bit better. -- This "old" version no longer shows any "rollback" options. Only to update to later..
Yes, I saw that too... and did get it to run a "blue" UI, but then it started giving me "update failed" when I went back up the upgrade chain... only way to fix it was installing the latest official. So they are doing something wonky on their side... like they weren't expecting the v3.0 to be requesting those files.
The key here is, the custom firmware cannot be installed using the typical v2.0 procedure.
The key here is, the custom firmware cannot be installed using the typical v2.0 procedure.
Good to know. I'll keep an eye-out for that as I update. I'm hoping @VLud has some input... I figure it would be safer to stay on the older version for a day or two until he is able to provide information. I'm totally willing to try anything, to the point it might brick the device if it means it will help eventually get the 3.0 on CFW.
Might be worth starting a Discord channel or something to work through issues... hahahaha
Opened a new issue @ ludwig-v / wireless-carplay-dongle-reverse-engineering: Unable to rollback/upgrade to CFW
I've been using a Carplay2air (integral USB-A, green interface) for just under two weeks, and until a few days ago, it was reliable. Connection then became hit-or-miss when I'd start up, and as of yesterday, it won't connect at all. I OTA updated the firmware right after installing it, and have not updated again until this afternoon as part of troubleshooting.
When I start up (or plug the CP2A into a wall wart), I now only get a red LED, no blue/green LED indicating Bluetooth. The radio (Uconnect 8.4 in a ‘21 RAM 1500) displays “Media files not found.” I can connect to the WiFi on the unit, but Bluetooth never shows up. I've OTA flashed, as well as with a USB thumb drive, with no change in Bluetooth function.
I've read through a lot (>50%) of this thread, and may try the rollback files via USB thumb drive tomorrow. Just posting this here to see if anyone has suggestions on how to get it working again.
UPDATE
I was able to roll back to 2021.03.06.1355, but still have no Bluetooth (no blue/green LED, either). Was unsuccessful in OTA upgrading from that - it hung at about 30% and now will not re-flash via USB, nor is it presenting a wifi or Bluetooth connection. It appears, for all practical purposes, to be well and truly bricked after less than two week's use.
*sigh*
Thanks,
es
When I start up (or plug the CP2A into a wall wart), I now only get a red LED, no blue/green LED indicating Bluetooth. The radio (Uconnect 8.4 in a ‘21 RAM 1500) displays “Media files not found.” I can connect to the WiFi on the unit, but Bluetooth never shows up. I've OTA flashed, as well as with a USB thumb drive, with no change in Bluetooth function.
I've read through a lot (>50%) of this thread, and may try the rollback files via USB thumb drive tomorrow. Just posting this here to see if anyone has suggestions on how to get it working again.
UPDATE
I was able to roll back to 2021.03.06.1355, but still have no Bluetooth (no blue/green LED, either). Was unsuccessful in OTA upgrading from that - it hung at about 30% and now will not re-flash via USB, nor is it presenting a wifi or Bluetooth connection. It appears, for all practical purposes, to be well and truly bricked after less than two week's use.
*sigh*
Thanks,
es
Last edited:
EDIT: Forget all the below. I didn't notice that the first post was edited with a lot of info.
Hello. I’m following this thread from a year ago and updating my Carlinkit v2 when I read about new version here. I must thank you all for your contributions.
I’m reading about a 2021.08.30 version that works very well (even with 350 ms) but vía OTA the last version I receive is 2021.07.05.2308, and this version reboots the dongle every 5 minutes.
Where can I have this version? I suppose that I can upgrade via USB. My car is a european 2020 VW Golf with Discover Pro.
Thank you!
Hello. I’m following this thread from a year ago and updating my Carlinkit v2 when I read about new version here. I must thank you all for your contributions.
I’m reading about a 2021.08.30 version that works very well (even with 350 ms) but vía OTA the last version I receive is 2021.07.05.2308, and this version reboots the dongle every 5 minutes.
Where can I have this version? I suppose that I can upgrade via USB. My car is a european 2020 VW Golf with Discover Pro.
Thank you!
Last edited:
You could try updating via USB but I found OTA to be the safer bet (iPad power adapters, or other USB power adapters with something around 10W, preferable without "smart" features, are the most reliable to properly provide power, updating in the car is risky, as it might cut power during reboot).
If you upgrade form an older version you have to perform the update in multiple iterations - for example, I went from 2020.11.10 to 2021.08.30 and it required 3 updates. (2020.11.10 -> 2021.03.06 -> 2021.07.04 -> 2021.08.30)
I was finally able to to get the device to take a flash again (no idea how - just kept trying different revisions until one worked). Plugged it into the truck, and instead of the "Media files not found" message from before, this time I got this screen:
The three buttons on the left do nothing, nor does the green 'Bluetooth' button at the bottom. Was unable to connect via wifi or Bluetooth, either. Same now that I'm back in the house and plugged into a wall wart.
I tried flashing other versions and nothing will take at this point.
es
The three buttons on the left do nothing, nor does the green 'Bluetooth' button at the bottom. Was unable to connect via wifi or Bluetooth, either. Same now that I'm back in the house and plugged into a wall wart.
I tried flashing other versions and nothing will take at this point.
es
Last edited:
I wonder what number they mean.
the Podofo I got has a red and white inspection sticker but nothing that looks like a serial number
Attachments
Thanks for these!No I didn’t ask.
procedure as is simple as put bin file in as card, rename file ispbooot.bin, plug-in, wait for green flashes then green solid light, unplug, remove sd, plug-in and tada
I will post the img as soon as I can.
43.0.3:
43.03.6
ISPBOOOT43003.BIN
1 file sent via WeTransfer, the simplest way to send your files around the worldwe.tl
ISPBOOOT4306.BIN
1 file sent via WeTransfer, the simplest way to send your files around the world
ISPBOOOT43007.BIN
1 file sent via WeTransfer, the simplest way to send your files around the world
My Podofo never worked and I don't know what firmware it came with but I manually updated to 43.09 and it didn't help.
I installed 43.03 and I finally got it to connect!
I then tried 43.07 and it wouldn't connect so I rolled back to 43.03 and I had success again.
That said, it still doesn't connect reliably. The green light doesn't even come on reliably.
Also, my steering wheel controls don't work and the audio lag when watching videos is worse that the CarLinkit 3.0.
I might try the Podofo again when a new firmware comes out but for now I'm sticking with the CarLinkit 3.0.
I've been running version 2020.12.25.1732 on my CarLinkit v3.0 (with Broadcom WiFi5/AC). This is the oldest firmware I could rollback to after my testing trying to load CFW. It has been running for 1-2 days now, and by far is the most stable it's ever been... I’m very surprised!
Interesting… What kind of stability issues are the other (newer) versions causing?
I was having a ton of predictable (based on location during commute) packet loss. I imagine it’s due to interference. It would cause music to stutter, not respond to touch, maps lag… all the usual stuff. Sometimes to the point of the iPhone disconnecting from CarPlay all together (every time at an intersection if I got stuck on a red light).
Since running this version, I haven’t noticed and music skips or lag, nothing. Seems a lot better. Drove past a section the the freeway today where things would always skip and I’d see packet loss… didn’t experience any issues. That said, maybe what we causes the interference wasn’t transmitting as much today. But over all, I could go on a single drive without some skips previously.
Since running this version, I haven’t noticed and music skips or lag, nothing. Seems a lot better. Drove past a section the the freeway today where things would always skip and I’d see packet loss… didn’t experience any issues. That said, maybe what we causes the interference wasn’t transmitting as much today. But over all, I could go on a single drive without some skips previously.
The back of the box the device came in has some numbers. I used that and they approved my request to join the group. Honestly no one has realt posted in the group and you’re not missing much. This thread is more useful.
I only tried flashing .09 and although my car was able to recognize the device as a carplay device the first time allowing me to enable it, it hasn’t worked again. It just flashes on and off now so I gave the podofo to my gf who does not experience issues on her Honda Civic except for the airplay casting.
I have upgrade the Carlinkit following your instructions. Then, I have driven for 15 minutes and the Carlinkit does not work well in 2021.08.30, the device is delaying to a point that it reboots. I have modified the delay to 350 so I backed to 1000 and get back to home... and another reboot. The same happened with 2021.07.05 version, last shown via OTA.
The rest of the story is me trying to rollback via USB unsuccessfully until I have seen that it was possible to rollback from the OTA option.
Now my Carlinkit is back in 2021.03.06 and I think it is working like before (not tested... but it's the previous version)
Thank you for your help!
Edit: in case it can help someone, my Carlinkit is a V2 version, my car is a european 2020 VW Golf with Discover Pro (I don't know if europeans are different from US, just in case) and my iPhone a 12 Pro running iOS 15 RC.
I sometimes have issues after OTA updates. It usually helps to re-pair the phone.
(Remove the Carlinkit from your Bluetooth devices on the iPhone, then on the Carlinkit press and hold the name of your phone in the connection menu to remove it)
@VLud 's instructions for installing custom firmware on anything newer than 2021.03.06 advise rolling back to 2020.11.10.2138 first and then upgrading to CFW; I think where this goes south for the V3 devices is that I don't believe they can run the 2020.11.10 firmware as they are too new. (I am not brave enough to attempt installing the 2020.11.10 firmware on my V3 as I don't want to inadvertently brick it.) So it's a chicken and egg problem where the encryption prevents CFW installation but there isn't a compatible non-encrypted version to roll back to. Does that sound like it makes any sense?
That does make sense. It does seem like a compatibility issue between the v3.0 and the older software. Luckily I didn't brick anything.
Still waiting for a response from @VLud, I'm hoping he might have some idea. If it's the encryption, we might just be SOL, presuming we cannot crack it.
Fingers crossed! Also neither here nor there but I just updated my V3 from 2021.07.05.2319 to 2021.08.24.1817. On 07.05 I had to keep it at 450-500ms latency to avoid audio skipping; on 08.24, I can keep it all the way down at the minimum 300ms and not hear any skipping. Seems like even with 2x2 MIMO disabled on the newer firmware they've improved performance tremendously. I have both Podofo and CheerDriving dongles on order from Ali but I honestly might just return them both given how well the V3 Carlinkit is performing these days (at least with my VW, I know experiences vary widely in this thread.)That does make sense. It does seem like a compatibility issue between the v3.0 and the older software. Luckily I didn't brick anything.
Still waiting for a response from @VLud, I'm hoping he might have some idea. If it's the encryption, we might just be SOL, presuming we cannot crack it.
Just a FYI - top marks to CPlay2Air Dongle....
I've had this since getting our 2019/2020 Mazda 3 (the version 1 i guess) - it's been very good indeed, and have done updates occasionally before. Also - the USB-A power output from it is great... i've got a Qi charger pad connected to the dongle output, so get in car dump phone on the Qi mat and car on and go...
Most recent update... first one was to fix an 'OTA bug' or something - that updated fine amd connected immediately afterwards.
I went ahead and checked for update again, since I was in the mood. ;-)
This update unfortunately ended up with it not connecting fully - it would connect by bluetooth but then loop continuously trying to finish - and so not create the usual Mazda wifi signal for the Carplay connection. Dongle red led was flashing.. but no reboots dongle/phone/bluetooth etc etc worked.
Contacted CPlay2Air by email - got a reply, and after some checks got the link to a firmware image and clear instructions.
Forratted a random old thumb drive to FAT32 on my Mac (no specail settings at all) and followed the instructions - worked perfectly.
I've had this since getting our 2019/2020 Mazda 3 (the version 1 i guess) - it's been very good indeed, and have done updates occasionally before. Also - the USB-A power output from it is great... i've got a Qi charger pad connected to the dongle output, so get in car dump phone on the Qi mat and car on and go...
Most recent update... first one was to fix an 'OTA bug' or something - that updated fine amd connected immediately afterwards.
I went ahead and checked for update again, since I was in the mood. ;-)
This update unfortunately ended up with it not connecting fully - it would connect by bluetooth but then loop continuously trying to finish - and so not create the usual Mazda wifi signal for the Carplay connection. Dongle red led was flashing.. but no reboots dongle/phone/bluetooth etc etc worked.
Contacted CPlay2Air by email - got a reply, and after some checks got the link to a firmware image and clear instructions.
Forratted a random old thumb drive to FAT32 on my Mac (no specail settings at all) and followed the instructions - worked perfectly.
- Everything's working perfectly again.
Just FYI:
I purchased a new Carlinkit V3 adapter. This one works without any issue in my Mercedes E-Class from 2019. The version 2.0 with USB-C was rebooting randomly. Now I drove with the new adpater more than 1.600 km without any randomly reboot.
This may be for interrest for Mercedes owners
I purchased a new Carlinkit V3 adapter. This one works without any issue in my Mercedes E-Class from 2019. The version 2.0 with USB-C was rebooting randomly. Now I drove with the new adpater more than 1.600 km without any randomly reboot.
This may be for interrest for Mercedes owners
I’m another Mazda owner. Could you please specify by date which update did not work for you and then which one did work?