-
-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
I am attempting to patch firmware from the Korean EV6 to the NAM EV6 (to have wireless CarPlay in their latest update). I have been able to decrypt the tar list and edit, then encrypt again. But I believe inside system_package there is an update_info file that is causing issues. The moment I change the system images the headunit will not install. I have been updating the 2022_EV6_USA.ver file with the updated CRC and file size and still will not install, as well as updating the version.info file. Do I need to resign this version.info file after editing? And will the private key included in this utility pass the headunit checks? Any ideas?
Activity
Helloyunho commentedon Oct 5, 2023
Sorry for the late reply, I missed this one ๐
First of all, the Korean firmware doesn't support the wireless phone projection yet(my dad's car is Korean version so I tested it but nada...)
Though I think they're gonna support it soon
Anyway, about the file
update_info... Hyundai is using RSA signing to check the firmware's integrityThe way it works is like this:
Rather interesting, but surely not a bad way to achieve it
The sad point(and I'm sure Hyundai used this method because of this) is that you don't need to reveal the private key to check the integrity, and that's exactly what Hyundai did: only including the RSA public key to the firmware
And since we only have the public key and not the private key, we essentially cannot make our checksum file
Conclusion
update_infois checksum-ed with RSA signing(making my own keys works and tested, but I still need a way to force update the firmware)
7ikw commentedon Sep 3, 2025
Have any one figure out how to change the Korean sitting to middle east with the new update!?