Is there any why to pick inside the current firmware for stored images ?
Or
Extract them, edit via photoshop and put back
Sent from my SM-G965F using Tapatalk
Or
Extract them, edit via photoshop and put back
Sent from my SM-G965F using Tapatalk
Will check shortly.
As above.Boyracer's value is the key. If he's not got a 2 or 0 or something else then we are looking at another field.
Hmmm. How do I do that @Tell ?
Is that different to the VCDS map mentioned above?Ok I changed that value, first image 0, second image 2 on the boot screen of the unit. Didn't notice a big change in the cars image. Of course we don't know whether production Ateca Cupra use the value of 2 and my firmware probably is pre Ateca Cupra... this is a carry over from the Seat model range. Mines a high unit with the firmware mentioned above. So I get that graphic in the second image with a supposed Ateca Cupra on the carry over coding from the model range. Wonder if its anything like Boyracers ?. Need his codes to resolve for you people with issues with the standard unit.
I guess the standard unit Ateca Cupras need something other than a zero in byte 18 . Set mine back to 0.. If you got a zero then yes that isn't right for a Cupra.
The other avenue to explore is to find the long coding for the infotainment unit of a Seat Ateca posted online.
Related post below, see post 8, points to bytes 1 to 2 as well. I have added my screen on that. We need Boyracer or anyone with a correct working graphics. My screen is the defacto non Cupra Ateca with a high unit. That the contents. I'd expect an Ateca Cupra to have different values.
You need to explore these against an Ateca Cupra's to resolve the image as well. A bit loath to change what I have working in bytes 1 and 2.So I reckon byte 18, byte 1 and 2 are the ones to concentrate on for comparison.
Something else for me to do then?Best bet at the minute till a Cupra Ateca owners shows up with their 5F code map is a Google for one. Haven't found one yet thou. Reckon those byte codes would be transferable on model. If identical to yours then it would seem Seat left the images out of the standard unit.
I have Cupra images in both.To me, the image that Boy Racer posted looks like it is from the Active Info Display and not the Infotainment unit. I wouldn’t be surprised to find that he probably has the SEAT image on the Infotainment as well.
Hopefully this will help for the time being:-Great that's what we want.
I can then try those settings in my high just in case the firmware is populated with those and the standard owners can try your values in those key slots. I have sneaky suspicion that the standard unit fitted to a Cupra isn't populated with the images or left the factory wrongly setup..
If you can get VCDS to oblige with these and byte 18 plus the long code map for study although that will have high stuff in it beyond the standard. View attachment 16813
Hopefully this will help for the time being:-
Address 5F: Information Electr. (J794) Labels:| 5F0-035-MIB-HGH2.clb
Part No SW: 5F0 035 020 H HW: 5F0 035 020
Component: MU-H-ND-EU H55 1409
Serial number: A678K0JB014463
Coding: 04230601FF00000011110101008808212F050AE601200400DE
Shop #: WSC 33361 790 00111
ASAM Dataset: EV_MUHig6C1Gen2HBAS 001001
ROD: EV_MUHig6C1Gen2HBAS.rod
VCID: 1D67D8EFFD3D620358D-8048
Operating And Display Unit 1:
Subsystem 1 - Part No SW: 575 919 606 HW: 575 919 606
Component: ABT_High-2_N H41 1041
Serial number: SEZ8Z9V1S02LVR
Data medium:
Subsystem 2 - Part No SW: V03 959 802 MN HW: -----------
Component: ECE 2019 --- 0172
Serial number: --------------------
Compact Disc Database:
Subsystem 3 - Part No SW: V03 959 800 EG HW: -----------
Component: Gracenote2 --- 1017
Serial number: --------------------
------------------------------------------------------------------------------------------------------------------------------
View attachment 16815
As for the byte 18, I seem to think there was a lack of information other than car brands and a few car types - of which the Cupra wasn't one of them. Will need to update on this tomorrow as there was also a mention about Developer Mode when I started VCDS and I said no to that. Will next try a yes to see if any other info comes up.
You don't appear to have the current VCDS - unless that is the latest version in your language?
Thanks.Your pictures show that you were using the newer connection protocol UDS/ODX/ASAM.
Try to connect with the old protocol and you will see that the Byte data is like mine and contains more data.
Carbon backgroundBoyrace, he has changed the skin on 17, I noticed that . He's got the diamond pattern that is called something or other matches what you could get in the old FIS. Keep mine pure and simple for visibility.
quid pro quo 4 sureOh must be the high spec one... that's quid pro quo for the missing images .