Apply custom images to Ford Convers+

[Gwe89]

Could some one please help the bytes in main at address 145B5 145B6 145B7 145B8
Standard logo is 30 08 EF BC
When there is a custom logo these bytes are always different what are these bytes doing
I know the 30 points it to flash

Custom logo is the same offset ?

No I dont think so

[peter]

Standard logo is in extended bin. 08EFBC.
This offset can be used in convershacker.
Location of this info is in the main bin 014198.

[Gwe89]

Standard logo is in extended bin. 08EFBC.
This offset can be used in convershacker.
Location of this info is in the main bin 014198.

30 08 EF BC is in the main it tells it where the stock logo is in the flash

[peter]

With This addres my CH is not able to show Picture in main. With ext no problem.

[drobec.eu]

With This addres my CH is not able to show Picture in main. With ext no problem.

Yes if is original logo this is in flash.

Custom logo aka m...ral have logo on main.

IMG_20191225_232202.jpg

But have custom BGR.
If extract BGR on main firmware, image logo is OK:

IMG_20191225_232225.jpg

[Gwe89]

facelift address for stock logo without vbf header 0x14198 0x14199 0x1419A 0x1419B bytes 30 08 EF BC if its a custom logo in flash at address 120000 the last 3 bytes are different so 30 12 XX XX

example of one custom logo i have address for logo 0x120000 in flash without vbf header, bytes in main 30 12 F0 58
example of another custom logo i have address for logo 0x120000 in flash without vbf header, bytes in main 30 12 F5 10

i belive 30 is flash 12 is address 0x120000 but no one will confirm this, ???(and the last 2 bytes possbily the start of image offset, start offset of its header)???

[DGAlexandru]

@Gwe89
You have different implementation of Custom Start Logo.
I think your Main FW looks at the 4 bytes starting from 0x30 11 FF FC to find out where the header of CustomLogo is; to this number it adds another bytes just to make it harder to understand, in order to get the real address of that header.
Anyway, from your own modded External Flash file I see you have done something wrong - you deleted more that you should have.
I'll do a custom VBF for you, with your Logo, just to see if it is as I'm expecting.
Later edit
Here you go! .. VBF and also BIN for you to understand how it should look like

gwe89.7z

I've been busy with improving CH .. a new version is out.. still a lot of things to do.
The VBF it produces is NOT ok for all versions of FW with Custom Logo Enabled. Also THIS VBF SHOULD NOT BE USED with "IPC Update" program as this one doesn't take into consideration the start and end address from VBF on which to erase and then to program - it deletes the entire flash. I'm using this VBF with UC DS and there it works as expected. Also, this VBF is OK only if the image converted is smaller that the one it replaces.. if not, then, again, Main FW won't know to look at the new header.
Convers Hacker is only the half part of the Custom Logo Modding Process; Main FW modification is the second one in most cases.

The file is still password protected (with the password shared with only some users) as it is still in early development process and it's better not to have it if you're not experienced and you don't know what to do in the case you break something in your Convers.

ConversHacker.7z

ConversHacker_26.12.jpg

[Gwe89]

@Gwe89
You have different implementation of Custom Start Logo.
I think your Main FW looks at the 4 bytes starting from 0x30 11 FF FC to find out where the header of CustomLogo is; to this number it adds another bytes just to make it harder to understand, in order to get the real address of that header.
Anyway, from your own modded External Flash file I see you have done something wrong - you deleted more that you should have.
I'll do a custom VBF for you, with your Logo, just to see if it is as I'm expecting.
Later edit
Here you go! .. VBF and also BIN for you to understand how it should look like
gwe89.7z


I've been busy with improving CH .. a new version is out.. still a lot of things to do.
The VBF it produces is NOT ok for all versions of FW with Custom Logo Enabled. Also THIS VBF SHOULD NOT BE USED with "IPC Update" program as this one doesn't take into consideration the start and end address from VBF on which to erase and then to program - it deletes the entire flash. I'm using this VBF with UC DS and there it works as expected. Also, this VBF is OK only if the image converted is smaller that the one it replaces.. if not, then, again, Main FW won't know to look at the new header.
Convers Hacker is only the half part of the Custom Logo Modding Process; Main FW modification is the second one in most cases.

The file is still password protected (with the password shared with only some users) as it is still in early development process and it's better not to have it if you're not experienced and you don't know what to do in the case you break something in your Convers.
ConversHacker.7z

ConversHacker_26.12.jpg

Thank you I will take a look

[paxtonix]

What i work on is a webservice where one can upload an arbitrary image and get a VBF in return. Then he needs an uploader where i think of an EXE written in C++ and using plain ELM. OMG, wait! this would break somebodys business...

Yep. I want to do the same. I also want to implement a watermark in my image converter which will refer to this forum. I hope that @dgalexandru will implement the same solution in its C + H extension. anyone who wants to upload a logo without a watermark will have to make an effort.

[DGAlexandru]

Even if I could understand Ursadon source code for Convers Hacker and I was also able to develop it further, I'm not that good with graphics engine and QT Creator doesn't have a built-in function for watermarking images, so I don't think I'll go that way.
Anyway, CH still has a flaw in its encoding algoritm and doesn't produce good quality images when it comes to a lot of shades.. so it isn't of real use at this time.
I''m playing with it in order to have my programming skills refreshed in order to be able to do another app that will take care of Main FW.