Kess 5.017 how to read SD card or create a new SD card

**pocinas** · 25th January, 2019, 01:50 PM

Thanks a lot.for all.

If someone still dont know how this is use... one the forum mhhauto.com is user Kitnoos2002. He can make image under you sd card ID but he charge 20 or 30euro peer image.

**bergbahn** · 25th January, 2019, 02:43 PM

Originally Posted by pocinas

Thanks a lot.for all.

If someone still dont know how this is use... one the forum mhhauto.com is user Kitnoos2002. He can make image under you sd card ID but he charge 20 or 30euro peer image.

Then I will probably always remain poor.
I spent many hours figuring out the encryption and did not really want to do anything else like reading my Opel 1.6cdti ECU.
But I also see that many people publish my work in other forums, I hope they all do it for free

**jekisujoko** · 25th January, 2019, 04:01 PM

Thx Master, i will try to fix my kess SDCARD, i hope all can be fix now.

**AudiA53xxx** · 25th January, 2019, 09:31 PM

Will try this

**forever85** · 26th January, 2019, 09:33 AM

Do you think that the kitnoos user has copied your work? it does not do for free

**bergbahn** · 26th January, 2019, 10:20 AM

Originally Posted by forever85

Do you think that the kitnoos user has copied your work? it does not do for free

By no means did "kitnoos2002" copy anything of mine, he had been successful much earlier with Kess SD cards.
And as far as I know he only needs the SD card CID to create a new image.
I still do not know how to convert the CID to the 13-line KEY.

But my method works, so I do not have to know everything about it !

I'd much rather find out how to decrypt the 5.017 and 5.028 protocol files.

**forever85** · 26th January, 2019, 10:43 AM

Exactly I know KITNOOS and it's a real professional. Unfortunately, not everyone is willing to explain their techniques for free and they are rightly charged. You will have yours and nobody denies the fact that it works ...

**bergbahn** · 26th January, 2019, 10:58 AM

we do not want to discuss other members here !!!

all members who publish here have certainly invested a lot of free time.
We should rather thank these people.

And now please only contributions to the topic.

And a message to all who use my work, it is no shame to press the Thanks button

**morgano** · 26th January, 2019, 12:33 PM

Haven't talked personally with kitnoos2002 (the only pm i sent him about this topic was unanswered, maybe he thought i was trying to learn something from him while i already knew all this since day 1 ktag 6.070 arrived on the scene, was first clone in implement this sd cyphering) but i think he uses same way as you to produce his custom cid images.

My guess is he use a cid changeable card, put on it the requested cid and extract the key in a similar procedure as you, triggering the same bug in the firmware you use on the interface to initialize the new card and grab fron there the encryption key. Then apply the encryption on a ready made clean image.

This method i haven't tested myself cause i don't own a cid changeable card, but knowing how all thing works i'm sure its a workable way to produce custom cid images too.

There is another way to self produce workable image for personal use, no any technical or encryption or programming knowledge needed. I may publish it some day.

As for the cid to key conversion i will keep it for myself a bit more.

with your permission.

Anyway in all that speech i wrote are some clues that can make you go forward in guessing the cid to key thing.

Regards

**kitnoos2002** · 28th January, 2019, 03:09 PM

Originally Posted by morgano

Haven't talked personally with kitnoos2002 (the only pm i sent him about this topic was unanswered, maybe he thought i was trying to learn something from him while i already knew all this since day 1 ktag 6.070 arrived on the scene, was first clone in implement this sd cyphering) but i think he uses same way as you to produce his custom cid images.

My guess is he use a cid changeable card, put on it the requested cid and extract the key in a similar procedure as you, triggering the same bug in the firmware you use on the interface to initialize the new card and grab fron there the encryption key. Then apply the encryption on a ready made clean image.

This method i haven't tested myself cause i don't own a cid changeable card, but knowing how all thing works i'm sure its a workable way to produce custom cid images too.

There is another way to self produce workable image for personal use, no any technical or encryption or programming knowledge needed. I may publish it some day.

As for the cid to key conversion i will keep it for myself a bit more.

with your permission.

Anyway in all that speech i wrote are some clues that can make you go forward in guessing the cid to key thing.

Regards

Hello,
Sorry Morgano I get a lot of messages, I probably missed yours, please do not hesitate to send it back to me.

You're wrong, I have several Samsung SD cards with programmable CID but I do not need it. I do not need Kess / Ktag either.
I coded my own program to generate SD card images from the CID.

I am interested to work with you all to decrypt the protocols in GEN_FILE format (Kess / New Genius) and in LDR_FILE format (Ktag / Trasdata).
They are encrypted with the Kess / Ktag serial number.

And for you bergbahn, if your ECU is a Delco E98, it appear in Ksuite 2.32.
So you need Kess 5.028 firmware working with Ksuite 2.34 or better 2.47.

If you want to work with 5.017 it will be difficult to port protocol from 5.028 to 5.017 because protocols use external functions from firmware.
Depending on firmware, function are located at different addresses.
To port protocols to different firmware, call addresses should be changed inside and also functions in firmware should be available and same.

**bergbahn** · 28th January, 2019, 04:51 PM

Originally Posted by kitnoos2002

Hello,
Sorry Morgano I get a lot of messages, I probably missed yours, please do not hesitate to send it back to me.

You're wrong, I have several Samsung SD cards with programmable CID but I do not need it. I do not need Kess / Ktag either.
I coded my own program to generate SD card images from the CID.

I am interested to work with you all to decrypt the protocols in GEN_FILE format (Kess / New Genius) and in LDR_FILE format (Ktag / Trasdata).
They are encrypted with the Kess / Ktag serial number.

And for you bergbahn, if your ECU is a Delco E98, it appear in Ksuite 2.32.
So you need Kess 5.028 firmware working with Ksuite 2.34 or better 2.47.

If you want to work with 5.017 it will be difficult to port protocol from 5.028 to 5.017 because protocols use external functions from firmware.
Depending on firmware, function are located at different addresses.
To port protocols to different firmware, call addresses should be changed inside and also functions in firmware should be available and same.

Hello, I'm also interested in decrypting the protocols in GEN FILE format.
Unfortunately I have not achieved anything yet.
In the database of Kess 2.47 the E98 ECU is inside, the line is just not active.