do you think they will come out with a CarPlay compatible version for the 2014 Hyundai Elantra Limited?

 

There has been no news about CarPlay coming out for the 2014 models. ****, it took them almost 2 years to introduce it for the 2015 models!

 

I have a 2015 Sport Ultimate, in Canada. Just downloaded and will try today. I will post back if I was successful or not!

Thanks for the link!!

 

So this did not work. First off, I had one **** of a time trying to get the software onto the SD card as the update tool would fail every time it tried to reformat the card during the install process.

I finally ended up reformatting it myself and running it again which worked and I was able to install the update onto the SD card. But once I tried to apply it to the car it would not take. I just kept receiving a "not compatible with hardware version" error.

Looks like we must again wait for Hyundai. Hope they actually deliver to us up here. Does any one in Canada even have AA running yet?

 

Unfortunately my 2014 Elantra has a totally did interface than the 2015

 

tx a ton man, still downloading it, jeez its slow

 

but I found the URL after digging around in the source code on myhyundai.com.

Thank you!!!
What is there more files for download? You can put them here too?

 

Thank you for the download link! I will take a look into this today and see if I can get it working on my Canadian model. *fingers crossed*

 

Maybe there are other firmware? We need them to try.

 

I contacted Hyundai Canada 5 days ago mentioning that Carplay was now available in the US, and when will the Canadian Sonata's get it. Below is the reply I received.

Also noticed that AA is now officially on the Hyundai Canada website, but they only seem to be limiting AA to 2017 models.




---------------------------------------------------------------------------------------------------------------------------------------------------
Thank you for contacting Hyundai Auto Canada.

We are sorry to hear of the inconvenience this has caused you. We understand it could be frustrating. Apple CarPlay has not yet been launched in Canada. There is no timeline for launch and the company cannot guarantee the feature will be applied retroactively to Hyundai vehicles in Canada. Thank you for your understanding.
---------------------------------------------------------------------------------------------------------------------------------------------------

 

We wil never get it

http://www.hyundai-forums.com/2016-...m/2016-tucson-ix35-models/400937-android-auto-apple-carplay-14.html#post4321225

 

Hi there,

i tried to update my Sonata 2015 to Carplay and download that link from first post and downloaded 9.5GB software , but when i put my SD card into my car ,i met with an error displayed " Not Compatible with hardware Version, Please check and try again"

My car is ordered from OMAN , and my Frimware ver is " MICOM,ST,LF,MES,0050.14040,SUBMB,ST,LF,1025,140115"

and S/W ver is " ST,LF,MES,E424,140623"

and Device ID "1879955196"

please help me to download the update tool , i need it.

 

Its only for USA, not any other country

 

Evolving updates?

Since my initial download from myhyundia.com for my VIN and successful install of CarPlay/AA onto my 2015 Sonata Limited, I have downloaded the update file to my PC several times and see the file size has changed so I wonder if they're tweaking the update over time (I.e. Patching it).

I might try to install the latest, but wondered if anyone had done this and seen a minor version change afterward?

 

Evolving updates?

Since my initial download from myhyundia.com for my VIN and successful install of CarPlay/AA onto my 2015 Sonata Limited, I have downloaded the update file to my PC several times and see the file size has changed so I wonder if they're tweaking the update over time (I.e. Patching it).

I might try to install the latest, but wondered if anyone had done this and seen a minor version change afterward?

Hello, the download link is no longer available. Would you be able to send the file(s) to me? This has been a major source of frustration as I have been trying to get apple CarPlay on my car for a while.
Thanks!

 

I downloaded and installed the direct update from Smiley. Everything worked fine and I even got a later map update. But, if I look at the myhyundai site, there is a CarPlay download available but dated Sept 2015 and with a number lower than the one I got from Smiley dated May 2016. Anyone know why the myhyundai site is not showing a later download available? I have a 2015 Sonata Limited.

 

whats the smiley link?

 

See page one of this subject.

 

Guys,

I do not have an SD card. Would anyone put a download link for the version that can be installed on a USB stick? I would really appreciate it.

 

downloading update now...... fingers crossed.
I have a 2015 sonata sport with navigation.
I hope this works.

 

Jeremy, did it go okay?

 

I diddnt get the chance to try it out yet.
Download took long to complete because my internet was a lil slow.
im currently out of town. i will return in a week.
i will post updates when i get back to my car.
cant wait.

 

hey guys... im back in town and guess what.........

I got the update to work on my car


(sorry guys. i just noticed all the images were flipped)

 

Sovled 112 error when forcefully ! updating AVN 4.0

Hi ,
For anyone out there having the same problem and searching the internet desperately
i have sonata lf hybrid 2017 and i wanted the Carplay and Android Auto .
i sort of figured out download path for the the ST_LFHEV_NA latest firmware , wrote a program to download all the files (there was no installer or i couldn't figure out the code so i reverse engineered one of the installers in hyundaisoftwareupgrade.ca !!)
copied the files into update folder of a usb drive , edited update.inf and version.000 files changing ST_LFHEV_NA to ST_LFHEV_MES and type of car and fixing md5 hashes (that are really SHA512 hash not MD5) !! to get the headunit to start installing the update .
update went through and after 15 minute an error appeared => Error Code:[112] Update information is wither damaged or does not exist. Check and try again
i couldn't do anything anymore !! the headunit was bricked ... and nobody knew what to do ...
and after 48 hours banging my head to the wall the solution was : when the error appeared , touch every corner of the screen (specially on system icon) repeatedly 5 , 6 times . touch everywhere repeatedly !!! (i was kind of desperate for a secret backdoor access ! and it worked ) and after 10 to 20 seconds headunit start showing some diagnostic and command line stuff and after 5 minutes headunit shows no error .
i have the latest firmware with Carplay and Android auto and everything is working perfectly .
the main reason for this post is to create some keywords in google , so anyone facing this problem could find this .

 

Hi ,
For anyone out there having the same problem and searching the internet desperately
i have sonata lf hybrid 2017 and i wanted the Carplay and Android Auto .
i sort of figured out download path for the the ST_LFHEV_NA latest firmware , wrote a program to download all the files (there was no installer or i couldn't figure out the code so i reverse engineered one of the installers in hyundaisoftwareupgrade.ca !!)
copied the files into update folder of a usb drive , edited update.inf and version.000 files changing ST_LFHEV_NA to ST_LFHEV_MES and type of car and fixing md5 hashes (that are really SHA512 hash not MD5) !! to get the headunit to start installing the update .
update went through and after 15 minute an error appeared => Error Code:[112] Update information is wither damaged or does not exist. Check and try again
i couldn't do anything anymore !! the headunit was bricked ... and nobody knew what to do ...
and after 48 hours banging my head to the wall the solution was : when the error appeared , touch every corner of the screen (specially on system icon) repeatedly 5 , 6 times . touch everywhere repeatedly !!! (i was kind of desperate for a secret backdoor access ! and it worked ) and after 10 to 20 seconds headunit start showing some diagnostic and command line stuff and after 5 minutes headunit shows no error .
i have the latest firmware with Carplay and Android auto and everything is working perfectly .
the main reason for this post is to create some keywords in google , so anyone facing this problem could find this .

HI Soheilvb
can you share your usb image i am having hard time getting sha checksum to pass on y update of 2016 Sonata
thanks

 

Posted this in the AA thread, but it is more relevant here.

The installation part is easy in terms of changing the update files. I'm quite curious as to this backdoor he has found. I think I would need a little bit more than simply tapping all over the screen to go ahead and try this myself. Perhaps, I will try to see if one can access this backdoor without doing an update. If that is the case, it would most likely be easy to replicate what he did.

Basically, for the initial install part, in the update.ini file, there is a list of all the cars - we are ST_LF_CA and our ID is 29. Up at the top, we'd update the config_product_model_type to 29 and config_product_sw_version to CA from the NA (US version). Also would need to update the version.000 file with the same thing. After, could generate new checksum numbers for those files and throw them into the checksum doc. Anyways, that tricks the software into updating the system. The problem comes after that with the error. There was a guy from Dubai that tried this back on post #653 or something like that and bricked his head unit. Sounds like this guy thought he did the same, but then magically found a way to bypass the error screen with some backdoor tomfoolery.

What is really interesting is if they are just dropping these units in the cars and the software is all the same. If he truly got AA and Carplay working on a 2017 Sonata in the Middle East, one would have to think that the software is the same across models and certain regions. Crazy!

Edit: Found another thread where he posted a screenshot of the error: ???? ??? ??????? ??????? ?????? LF ?????? 2017 - ??????? ??? - ???????? ????? use the google translate if you're using Chrome. It is a bit jumbled, but you get the idea. Man, I wish we knew exactly how he bypassed this. If I wasn't heading to Jasper this weekend (need working radio!!), I would go home and give this a go.

Edit #2 (and most important): Just re-read his post. He downloaded the 2017 version from Canada.

So we would definitely download Direct Download for 2015 Sonata CarPlay Update Tool the update tool from there and download the files like that. You guys tried it before, but didn't change the update.ini files nor the version.000 files, and the checksum to fool the software. Judging by the read me document - https://hyundaisoftwareupgrade.ca/assets/pdf/nav.pdf - if you get errors, you can hit the reset pin or you could try the touch the screen everywhere trick like our friend up above. I might give this is a go. Haha.

We should note that this could brick the head unit though before anyone goes and tries this. Hahaha.

Back up your original SD card without doubt.

 

I'm on a Mac, how can I edit those files? I think I still have them from when I tried to update before

 

Should be this from terminal to the file path (/tmp/1.iso for example):

You'd want md5 and if the other guy was correct, 512. Just cross compare the length in the checksum files as md5 will be shorter and 512 (the one not named md5) will be quite long but should match the other ones.

Edit: after you edit the files, and then produce the new checksum, just copy and paste the output to the checksum files and save those as well. Then the car shouldn't question you when you initialize the update.

Calculate MD5 checksum:

md5 /tmp/1.iso

Calculate SHA-1 checksum:

shasum -a 1 /tmp/1.iso

Calculate SHA-256 checksum:

shasum -a 256 /tmp/1.iso

Calculate SHA-512 checksum:

shasum -a 512 /tmp/1.iso

Example md5 output: 1237c5281949928ed782d914c40fce61
Example 512 output: 025963814087D596CF4AD5F9332D5C72263F4827FE3C86E9E730D82617430E03A99AF0A91C248DD2F9747CC8BFF8A391813F57E306649E461086C925880CE7EB

 

Should be this from terminal to the file path (/tmp/1.iso for example):

You'd want md5 and if the other guy was correct, 512. Just cross compare the length in the checksum files as md5 will be shorter and 512 (the one not named md5) will be quite long but should match the other ones.

Calculate MD5 checksum:

md5 /tmp/1.iso

Calculate SHA-1 checksum:

shasum -a 1 /tmp/1.iso

Calculate SHA-256 checksum:

shasum -a 256 /tmp/1.iso

Calculate SHA-512 checksum:

shasum -a 512 /tmp/1.iso

Beauty! Thanks again!! I am probably going to **** this up, but I will keep everyone updated! Really appreciate all of your help with this!!

 

Just added examples and also where to put the generated checksums. Here are the parts of the checksum documents you'll want to update (the ones here are only examples, don't use them or you'll get the message that you can't update):

in the md5 doc (replace the long digit/letter strings):

/update/version.000 : 1237c5281949928ed782d914c40fce61

/update/update.ini : fef109019de75bd726703de3eeca7060

In the other doc (replace the long sha512 strings):

/update/version.000 : 67E77ABF3C51E94D257D905E3A2C4EAD2017438D7B3FE7C2807870014C374A4EECA6A594E39EA43330EE80982813684CE4EE1C3E9D2A5B4359C7C84F7A8C324D

/update/update.ini : 025963814087D596CF4AD5F9332D5C72263F4827FE3C86E9E730D82617430E03A99AF0A91C248DD2F9747CC8BFF8A391813F57E306649E461086C925880CE7EB

 

Let us know how it goes man. I really hope it works, even if we have to do the pin reset a few times or the magic touch screen trick!! Just be patient and don't turn your car off or remove the SD card if you get to the actual part where it is updating.

 

Hey Moodib, thank you very much for the 2016 update installer. Could you tell me how you got the source URL though?

 

I just changed the 2015 in the url to 2016 and then at the end changed the file to 2016 and it worked, so you're getting the correct file. You're right that the 2016 file name is different though, so adjust accordingly when renaming.

What line do I put them into?

I compared the long 512 numbers before/after the checksum and my output was 128 as opposed to 130 characters in the original. I didn't know what to do with that so I just left it.

I also did try to apply the update in my car anyways and no go. I got an error code, see attached picture, but after a press of the reset button everything was back to normal (no bricking, yet). So I obviously did something wrong because it fails while "checking the update file".

I think I am almost in over my head here, but I don't care. Someone tell me what to do and I'll do it. I just have no idea what I'm doing on my own [emoji52]

Sent from my iPhone using Tapatalk

That looks to be where the other guy got to as well. Nice to know that we can hit the reset button and all goes back to normal though. I'm going to give this a go knowing that and try the old press everywhere trick to see what I can conjure up. Does this delete the maps off the SD card?

 

Wow this is really strange. I'm comparing the Hashes before even modifying the files and to my biggest surprise, they do not match with those in the checksum.md5 file.

From the file I am getting:
/update/version.000 : 7862B1AF3E2F569F08DDFFD3599579A0B6DC04121C763B92EB454D0AE9E8761509FC7B51FCE4D4479BD0EAFAE89A3E9AD155557DA565322C51EA68968FD80EBD

/update/update.ini : DA5D26CE57F29B1A9BA72AC4CE23F85CDE8C3313D93E310158F6860550CC676A99DB51F41141C589D6E54D1BA8C533AB64AA7610E4C369563DDCD4F281B8E1B8

And from my check:
/update/update.ini :
5278118029f2e083d588416536bbf6ccd3049abc586cdf1cd7ad41b7bc74955269f2c233ed8d82f32be6a2a31a170903f9b2397ece9ad2e6443d4c68a54d378b

/update/version.000 :
d2b75c332f3717f4638e6b337d3aaddb8e129f0d98f383ab69df7ff31f69f0597a9ccc424595ed86e389bfbb44864bfd0ab6f7902ad96bd249c94a60e35ef779

Is this normal?

Anyhow, I have noticed that the file structure is also different with the 2016 update downloader. For instance, there no longer is a checksum file but only the checksum.md5

Also, I don't know if you matched the model S/W with that of the head unit but mine is different: ST_LF16_CA