wolftje
DW Regular +
- Joined
- Dec 12, 2008
- Messages
- 1,098
- Reaction score
- 385
@Digi & Phantom.
Why is the tm3000D using HEX & AScii in a softcam.key file ? Any Idea ?
Freaking impossible to make a keyfile just from Ascii.
(of course you can edit the key with the remote but that is not always wanted)
Anyway.
I have used Phantompatch-TM-3000D-P-V3.63 06-01-2011.bin
coz that date seems to go well for ORF & NL digitaal
You cannot use a normal Key file that is used
I took a backup with magicloader for the 3000 series 1.1.4
then I came to the conclusion that you cannot edit directly as the
4 Last Hex codes are HEX encoded instead of Ascii. Above this, the first hex code is displaced to the front....(notice B0 has moved to the front)
I'm talking about this 4 codes : " B0DFAD50"
The normal TM key looks like this : (working nl digitaal at this moment)
; SLOT 22 - Canaldigit. NL (019.2E) - <2011-05-20 09:33:55>
I 062200 06 CB8C5E7BC42F4B0E
I 062200 56 3E3D6CD8B0DFAD50
A tm5300d key file looks like this(copy & pasted, I don't know if this gonna work as it are hex -> ascii conversion but y got the point ...)
I 0000 51 00000622154A1A865DF48DED7115CDFF ;—w…Canal Digi
I 61616C00 B0 00000622CB8C5E7BC42F4B0E3E3D6CD8 ;ß*PCanal Digi
(Notice, after D8 we have always "HEX 20 HEX 3B" = " ;"
(then the 4 hex codes only B0 is moved to the front, the following three DF AD 50 are inputted in HEX thus representing an Ascii code in a textfile)
Anyway, I did a Hexedit on the keyfile.
I do not like to input it on Tv.
I have highlighted in hexedit where the actual active key for nl digitaal resides.
Hope you understand my Info a bit ...
I hope by posting this we can get the tm3000 back "live". naah kiddin i was just playing around a bit and pooking into the poor thing. Amazingly it has some potential ... ! lol
Why is the tm3000D using HEX & AScii in a softcam.key file ? Any Idea ?
Freaking impossible to make a keyfile just from Ascii.
(of course you can edit the key with the remote but that is not always wanted)
Anyway.
I have used Phantompatch-TM-3000D-P-V3.63 06-01-2011.bin
coz that date seems to go well for ORF & NL digitaal
You cannot use a normal Key file that is used
I took a backup with magicloader for the 3000 series 1.1.4
then I came to the conclusion that you cannot edit directly as the
4 Last Hex codes are HEX encoded instead of Ascii. Above this, the first hex code is displaced to the front....(notice B0 has moved to the front)
I'm talking about this 4 codes : " B0DFAD50"
The normal TM key looks like this : (working nl digitaal at this moment)
; SLOT 22 - Canaldigit. NL (019.2E) - <2011-05-20 09:33:55>
I 062200 06 CB8C5E7BC42F4B0E
I 062200 56 3E3D6CD8B0DFAD50
A tm5300d key file looks like this(copy & pasted, I don't know if this gonna work as it are hex -> ascii conversion but y got the point ...)
I 0000 51 00000622154A1A865DF48DED7115CDFF ;—w…Canal Digi
I 61616C00 B0 00000622CB8C5E7BC42F4B0E3E3D6CD8 ;ß*PCanal Digi
(Notice, after D8 we have always "HEX 20 HEX 3B" = " ;"
(then the 4 hex codes only B0 is moved to the front, the following three DF AD 50 are inputted in HEX thus representing an Ascii code in a textfile)
Anyway, I did a Hexedit on the keyfile.
I do not like to input it on Tv.
I have highlighted in hexedit where the actual active key for nl digitaal resides.
Hope you understand my Info a bit ...
I hope by posting this we can get the tm3000 back "live". naah kiddin i was just playing around a bit and pooking into the poor thing. Amazingly it has some potential ... ! lol
Last edited: