2017/2018 radio swap in 2016 ultimate?

[Sebastian4k]

Let’s continue the saga
View attachment 24337

Plug it in man and send results! Only took me 20 mins to install

 

[Suburbazine]

Plug it in man and send results! Only took me 20 mins to install

results same as yours.
The amp is actually not receiving the correct commands. It’s remaining asleep. I was able to briefly wake it up with GDS for a diagnostic run and it passed music...for about 3 seconds. MOST ring is good the whole way around.

this newer unit is running MeeGo still. Just different firmware inside. Hardware is looking the same.

 

[Mr. Incredible]

results same as yours.
The amp is actually not receiving the correct commands. It’s remaining asleep. I was able to briefly wake it up with GDS for a diagnostic run and it passed music...for about 3 seconds. MOST ring is good the whole way around.

this newer unit is running MeeGo still. Just different firmware inside. Hardware is looking the same.

sounds like that means Hyundai intentionally decided not to allow the higher end units to be upgraded

 

[Suburbazine]

sounds like that means Hyundai intentionally decided not to allow the higher end units to be upgraded

Gotta leave a hook to pull you over to the actual Genesis brand, right?

 

[Suburbazine]

For science! To go where no consumer has gone before!

going to image this drive then delve into Hyundai’s MeeGo implementation.

There’s 59GB unallocated space on this 111GB drive. So 52GB of usable space, minus the 28GB Jukebox partition, so around 24GB system files, of which 22GB is probably nav data. So the MeeGo files are probably around 2GB

 

[Suburbazine]

If I knew what I was doing I could bring Carplay to the older head units. I'm going to attempt booting from the newer head unit's drive to see what happens on the old head unit.

 

[Suburbazine]

If some linux lover wants to doodle, here's the most interesting looking partitions.

https://xtremission.s3-us-west-2.amazonaws.com/Genesis+G80+Radio/1.6gb.zip

https://xtremission.s3-us-west-2.amazonaws.com/Genesis+G80+Radio/214mb.zip

https://xtremission.s3-us-west-2.amazonaws.com/Genesis+G80+Radio/3.2gb-2.zip

https://xtremission.s3-us-west-2.amazonaws.com/Genesis+G80+Radio/3.2gb.zip

 

[skipgen]

If I knew what I was doing I could bring Carplay to the older head units. I'm going to attempt booting from the newer head unit's drive to see what happens on the old head unit.

View attachment 24355

Man... that's turning into a full blown hack!

 

[skipgen]

results same as yours.
The amp is actually not receiving the correct commands. It’s remaining asleep. I was able to briefly wake it up with GDS for a diagnostic run and it passed music...for about 3 seconds. MOST ring is good the whole way around.

this newer unit is running MeeGo still. Just different firmware inside. Hardware is looking the same.

Great research!

Supports my initial assumption that it was a software thing. Hyundai could have spread a little good will & allowed for 2015 - 2016 Ultimate owners to update their systems. I'd imagine that quite a few owners would have sprung for it, even if it was a dealer install thing for a predetermined cost...

 

[SuperKing]

This is getting interesting again... lol... if the old deck boots with the newer SSD then it's just a matter of imaging the SSD with the newer firmware. I don't know how the newer firmware is going to talk to the old amp though.

______________________________

Help support this site so it can continue supporting you!

 

[Suburbazine]

This is getting interesting again... lol... if the old deck boots with the newer SSD then it's just a matter of imaging the SSD with the newer firmware. I don't know how the newer firmware is going to talk to the old amp though.

I found some CANbus mappings that may be the issue.

 

[Whitey]

This is getting interesting again... lol... if the old deck boots with the newer SSD then it's just a matter of imaging the SSD with the newer firmware. I don't know how the newer firmware is going to talk to the old amp though.

I found some CANbus mappings that may be the issue.

The plot thickens, lol...

 

[skipgen]

I found some CANbus mappings that may be the issue.

If anyone wants to do some light reading, the below link can give you some insight on how this stuff works. It's so far above my head, I can barely see the bottom of it! So, kudos to Sub for delving into it!

CAN Bus Explained - A Simple Intro (2019).

 

[Sebastian4k]

Hey it’s me again. New idea.. how about getting a 2017/2018 sd card update and potentially getting ACP through that method..? Or maybe buying NavTool interface?

 

[vend]

I wonder what would happen if we copied over the CarPlay app files from the newer unit to the 2015/2016 unit's hard drive file structure? If we get an image of both hard drives a comparison could be completed to see differences and uniques to possible piece in the files needed while leaving the settings/files needed for amp to work unchanged

It looks like there are a handful of references in the files uploaded for app projection and CarPlay:

1.6gb/data/AppProjection/DHPE

/1.6gb/root/AppProjection-0.2.10-1.i586.rpm

/1.6gb/root/CarPlayMeegoFramework-0.1.60-1.i586.rpm

/1.6gb/root/OBS

/3.2gb/app/bin/AppProjection

/3.2gb/app/bin/ProjectionDaemon

/3.2gb/app/lib/libAirPlay.so

/3.2gb/app/lib/libAirPlaySupport.so

/3.2gb/app/lib/libCarPlayAppFramework.so

/3.2gb/app/lib/libCarPlayMediaFramework.so

/3.2gb/app/share/AppProjection

/3.2gb-2/app/bin/ACSTCPConnectorServer

/3.2gb-2/app/bin/airplayutil

/3.2gb-2/app/bin/AppProjection

/3.2gb-2/app/bin/ProjectionDaemon

3.2gb-2/app/lib/libAirPlay.so

3.2gb-2/app/lib/libAirPlaySupport.so

3.2gb-2/app/lib/libCarPlayAppFramework.so

3.2gb-2/app/lib/libCarPlayMediaFramework.so

 

[billybombill]

Hey it’s me again. New idea.. how about getting a 2017/2018 sd card update and potentially getting ACP through that method..? Or maybe buying NavTool interface?

This seems like the most user-friendly route, though the big hurdle is the "Authentication Code" they generate that locks the sd card to your vehicle. Previous threads found it's likely writing it to the SD card's CID/serial number, which adds some complexity. The head unit verifies the auth code mapnsoft generates, even in older vehicles where you had to type it in manually, so I'm sure it's not "phoning home" and is probably just some hash combination of the VIN and Device ID (those used to be the only 2 requirements, though now their online form asks for model code and map version). We do have access to the head unit files now, so perhaps we can find the method of authenticating the SD card. Even if the auth code could be replicated or bypassed, I'm not sure if anyone still has the old sd update for people to tinker with.

I wonder what would happen if we copied over the CarPlay app files from the newer unit to the 2015/2016 unit's hard drive file structure? If we get an image of both hard drives a comparison could be completed to see differences and uniques to possible piece in the files needed while leaving the settings/files needed for amp to work unchanged

Yeah... Comparing the two would be helpful in finding what's changed with the amplifier/canbus mappings Suburbazine mentioned. I imagine modifying the 2018 head unit files to get the amp working is the easiest route, given things seemed to work out of the box with the 2018 aside from sound. I'll try to pull my 2016's SSD out this weekend and see if I can compare with the files posted previously for any clues.

Thanks @Suburbazine for all your work! Definitely interested in the disk image once it's ready

 

[CarlitoGR]

What VM environment are you going to be using so I can have it already installed.

 

[Suburbazine]

What VM environment are you going to be using so I can have it already installed.

I built the images in Ubuntu using gnome-disk-utility, they will be a .img file. I'm not sure what environment to use to launch it, I've been trying to get VMware Workstation to start it but haven't hit upon the magic combination yet. Getting the 2018 image compressed now, nothing is fast about a 128gb file or even whatever it shrinks to. No alteration or washing of the partitions has been performed.

 

[Suburbazine]

Here's the 2018 image:

https://xtremission.s3-us-west-2.amazonaws.com/Genesis+G80+Radio/2018Genesis.zip

Seeing as I was able to deflate it to around 6.5GB, it must be full of a lot of 0s.

I have to pull my 2015 head unit out again, it looks like the disk cloning failed (I'm missing half the disk).

 

[SuperKing]

I built the images in Ubuntu using gnome-disk-utility, they will be a .img file. I'm not sure what environment to use to launch it, I've been trying to get VMware Workstation to start it but haven't hit upon the magic combination yet. Getting the 2018 image compressed now, nothing is fast about a 128gb file or even whatever it shrinks to. No alteration or washing of the partitions has been performed.

View attachment 24781

I'm having the same problem in Parallels and vmWare Fusion. It's looking for hardware that isn't there. I think we may need to test with the head unit itself? Have you tried cloning the drive to another SSD and see if the copy boots the headunit?

Maybe someone can install a SATA extension cable from their head unit to the glove box for testing purposes. So they don't have to tear up their dash everytime they want to test the changes.