$theTitle=wp_title(" - ", false); if($theTitle != "") { ?>
About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
If you have read my earlier blogs about the RNS 510 then you may know I have been working on creating custom startup logo’s for some time.
For some time now I know how the images are encoded and decoded between Windows bitmap and the native RNS 510 image format.
Recently I identified the checksums in the image data, and the differing parameters for the Seat, Skoda and VW versions of the RNS 510 firmware.
But yesterday I noticed that there’s now an online tool that can create an iso image with a custom startup logo.
Nice? Well I am not sure!
First of all the person who wrote this online tool seems to have good intentions and he wants his tool to be freely available.
However he just reversed the ISO images that float around the net. Note that I did NOT create those images, they are most likely created with Josi’s SetConfig tool:
He calls the Author from this tool, a guy that has done very much for the RNS 510 community, an Idiot.
But back to the site, it is published here and this is a screenshot:
My quick observations from the tool:
Original from site:
As seen in the Logo.fli:
Just my 5 cents.
Related articles I wrote earlier:
5 Responses for "RNS 510 Startup Logo–My thoughts"
Hi Remko,
Thanks for the review of my site.
Just some response on your constructive feedback.
* Seat option is added since yesterday
It has been reported that it works for seat too
* I called the guy an “Idiot” because he is -selling- that tool
for a LOT of money, in my opinion we are all community members and why not profit from someone’s findings.
* Since the BMP to logo.fli conversion is a conversion from Truecolor to RGB555 you indeed lose details, this cannot be changed as the unit only accepts RGB555
* Please also read my techincal info page as it contains some info on the crc16 inside the version.txt
I fully understand how it is calculated, however I have promised the person who told me how to calculate to not make it public.
That is why in my technical page you will find the answer on the brute force CRC collisions.
Wouter D’Haeseleer: don’t be so arrogant and stop writting bullshit on your site like “We have spent about a week in bewilderment interspersed with brief flashes of partial awareness in this reversing effort”, “All this effort was done by two friends trying to understand more”.”
In fact you only exploited Remko, Jiri and my findings and efforts, which certainly took more than year.
Hi Josi,
I have reversed the ISO’s which are already on the net that is true, however this kind of stuff should be free and open in such way that other technical people like me are able to contribute to this kind of stuff.
Therefore opening the technical details is the only option.
And as far as I can see the community does not think is bullshit, they all like the idea…
In fact I have contacted a few people to work with me together and they all refused, no problem for me but then I’m doing it on my own…
So please think again when saying that I’m arrogant.
I will change my mind only when I will see some real contribution from you, not dumbly copying others work without giving credits to people who deserve it.
Until now I only have seen stupid things like adding non-existing “support for older units”, or half-working support for chinese version of RNS.
Ok, no problem.
Just to point out that I figured out a lot of info.
So it is not that I need to credit anyone for this.
Examples are:
* how the CRC16 inside the version.txt works
* Which type of CRC16 is used.
* How the logo format is encoded en decoded, I did this based on what is inside the Firmware CD…
Actually the only thing I have used from the ISO’s which are on the net (Without your name in BTW) is the correct line inside the ecuorder.txt
Also created a web tool arround this technical stuff, which is also my credit.
But I’m open for collaboration together with you guys, I think we can help each other…
Leave a reply