Dragon Cam Tools

[bab.elouad.cite]

PredEdit v1.1
**************
WHAT'S NEW IN THIS RELEASE ?
--------------------------------------------------------------------------------
1. Import keys from SOFTCAM.KEY
--------------------------------------------------------------------------------
a) Seca/Viaccess/Nagra/Nagra2/Betacrypt/DCW/BISS keys can be updated
automatically now !
- If a provider is not existing in the DRA file, no key update
will be made for this provider because new providers are not
added during key import!

- DCW import:
Keys with the following pattern/structure will be imported:
1. D aaaa:------:bbbb:cccc:----::xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ;<provider>
(= included in SOFTCAM.KEY created by "PredEdit" -> DCW and Biss)
2. D aaaa:------:bbbb:----:----::xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ;<provider>
(= included in other SOFTCAM.KEY )

aaaa = CAID
bbbb = SID
cccc = VPID
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx = key
---- = any hex digits!

- BISS keys import:
Keys with pattern "F xxxx1FFF 00 " are imported ,
but only if the left 3 hex digits of xxxx (=SID) are not
equal to "000" :

F 00011FFF 00 1000000000000000 (not unique!)
F 00011FFF 00 210598BE00000000 (not unique!)
F 00011FFF 00 1AEB2E33F53D0032 (not unique!)
F 00021FFF 00 A1B2C316D4E5F6AF (not unique!)
F 00021FFF 00 27121049208517BC (not unique!)
etc ...

Biss provider names are very often not included, so an update is impossible!


(The imported keys are saved automatically in the DRA file
and the checksum is fixed at the end of the import process.
No file reload is needed!)



b) Cryptoworks keys are not updated automatically!
- Cryptoworks keys cannot be updated automatically because
Dragon/T-Rex/Super T-Rex CAM use their own 8 byte keys !
(not the usual 16 byte ones included in SOFTCAM.KEY!)


(The logfile "UpdatedKeys.txt" is created during this update process
in the directory where the updated DRA-file is located !)


--------------------------------------------------------------------------------
2. Export keys to SOFTCAM.KEY
--------------------------------------------------------------------------------
- Seca/Viaccess/Nagra/Nagra2/Betacrypt/DCW/BISS keys can be exported now!
- Cryptoworks keys are not exported!


--------------------------------------------------------------------------------
3. Firmware Checker
--------------------------------------------------------------------------------
- Compares the checksum stored in any DRA file and the calculated by
"PredEdit".

Notice: "PredEdit" verifies the checksum of any DRA file on opening!
If the stored and the calculated are not equal a message appears
on the screen and you decide whether to load the DRA file or not!

--------------------------------------------------------------------------------
4. Hex2Dec KeyConverter
--------------------------------------------------------------------------------
- Converts a single HEX key to a DEC key and the other way round

Notice: If the option "Create IdentsList.txt on closing" is true,
the file "DRAKeys.TXT" will be created too. This file includes
all exported keys in HEX a n d DEC format!


That's all !

[kolorado]

New PredEdit v1.1.

[passete]

Keyeditor for predator and predasaur files !
New bug fix !

Fixed bug
- PredEdit v1.1 didn't change the values of byte 63
and 64 in an opened DRA-file until now!
But only if these two bytes are changed, it is
guaranteed that the updated keys are really written
to the CAM by the dragon loader program!

Depending on the DRA-file used the last time for
programming the CAM, it could have been that the
updated keys in the predator/predasaur files were
okay, but after loading the file/module up to the
CAM, the old keys still were stored in the
CAM's memory ( -> DEBUG menu).

Now this bug is fixed!

[passete]

ABSat354 Tool
Content of the ZIP-archive
**************************

1. ABSat354.exe ... for updating daily ABSat keys in predator354
2. sha256.dll ... for calculating checksum (used by ABSat354.exe)
3. predator354.dra ... lastest predator file
4. t*sCRYPT2.txt ... ABSat keyfile

Copy the 4 files in the same dirctory and start EXE !

Notice:
You can use ABSat354.exe for fixing the checksum of ANY predator file
by drag and drop in windows explorer !!!

[passete]

ABSat354 v2.0 (24.04.2007)

**************************************

How to update AES Keys in Predator354:
--------------------------------------
1. Start "t*sBin Decrypter.exe"
2. Load daily "t*s.BIN"
3. Press "Decrypt"-button
4. EXIT program
5. Start "ABSat354.exe"
6. Open predator354 file
7. Open keyfile t*s.TXT
(was created by "t*sBin Decrypter" before and
is located in the same folder as t*s.BIN!)
8. Select default option "PostSE" (start column =87)
9. Press "Update Predator354"-button



If you've got a keyfile where "PostSE keys" are stored seperately
from column 1 to column 32 open this keyfile in "ABSat354" and
select the third option "Another valid keyfile" !

[passete]

Extract Offset of AES Key in Predator/Predasaur firmware


Files Extension:
DRA -> Predator or Predasaur firmware (example Predator356.DRA)
TXT -> t*sCRYPT2.TXT include dailly AES keys List
INI -> AES Offset Adress in Predator/Predasaur firmware (example Predator356.ini)


How To:
1.Create a t*sCRYPT2.TXT of the day with our t*sBIN Decrypter v1.06
2.Open a DRA File ALREADY updated with keys include in t*sCRYPT2.TXT
3.Press "Extract" Button
4.File DraAESOffset.ini will be created. Inside all AES key found in DRA file
Possible to drag file directly in main window (DRA, TXT)

ps: You can use this method for fixing an Original Firmware with AES key.

NOTA:
If in file you get a keys with an offset = 0, it mean key not present in file or key already used by another offset adress
Erase this line in file DRAAESOffset.ini and found the problem
Example of key not present in DRA File
00010203040506070809101112131415 --> 0x00000000

[passete]

DRA AES Updater
(C)MASARE TEAM - Saoud007
(C)FullDump TM


Update dailly AES keys list in Predator/Predasaur firmware

EXCLUSIVE: for the first time you can patch Pred356, Predasaur 211, 212, 213 and the pred354 First release (not release 17/11/2006)



Original Firmwares Tested
-Predator354 : 249512 bytes Release date 22/10/2006
-Predator355 : 249336 bytes Release date 21/12/2006
-Predator356 : 239120 bytes Release date 05/02/2007
-Predasaur211 : 239752 bytes Release date 08/01/2007
-Predasaur212 : 240488 bytes Release date 09/01/2007
-Predasaur213 : 240692 bytes Release date 05/02/2007


Joined First Release for each original firmware
All versions never updated (NO DATE in Predator firmware name, based on first release)
-Predator354 : AESOffset=133 keys -> TPSCrypt2.txt=120 keys -> ALL Keys can be updated
-Predator355 : AESOffset=129 keys -> TPSCrypt2.txt=120 keys -> ALL Keys can be updated
-Predator356 : AESOffset=125 keys -> TPSCrypt2.txt=120 keys -> ALL Keys can be updated
-Predasaur211 : AESOffset=130 keys -> TPSCrypt2.txt=120 keys -> ALL Keys can be updated
-Predasaur212 : AESOffset=132 keys -> TPSCrypt2.txt=120 keys -> ALL Keys can be updated
-Predasaur213 : AESOffset=132 keys -> TPSCrypt2.txt=120 keys -> ALL Keys can be updated


Files Extension:
DRA -> Predator or Predasaur firmware (example Predator356.DRA)
TXT -> TPSCRYPT2.TXT include dailly AES keys List
INI -> AES Offset Adress in Predator/Predasaur firmware (example Predator356.ini)


How To:
1.Create TPSCRYPT2.TXT with our tool TPSBIN Decrypter v1.06
2.Run DRA AES UPDATER
3.Load Predator or Predasaur firmware
4.Load TPSCRYPT2.TXT
5.Load Predator or Predasaur INI File (example Predator356.ini -> include AES Offset Adress in firmware)
6.Press "Update" button
PS: Possible to drag file directly in main window (DRA, TXT, INI)


With this tool you can fix ALL version of Predasaur/Predator firmware if you know to extract AES Offset adress.

[iain1965]

I hope this is what you're looking for

[passete]

Tool for Predator3.25
Updating D+ OR C*bo key

* You can create updated predator325 for D+ or C*bo
(It is not possible to create one file for both !)

Thanks to cherubim1

[zoris]

DragonCrypt
(C)MASARE Team - Saoud007
(C)FullDump TM
Release Date : 07/06/2007

KEYS EDITOR FOR DRAGON CAM MODULE (ALL in ONE: no external tools needed)

Supported versions:
Predator 215 to last firmware
Predasaur ALL versions

PENTA Version 1.13:
- Added DRA AES Updater (INI file on folder ..\DragonCrypt\DCAesIni)
- Caids Function modified Again (same functions as Fausto, much better)
- Languages files Datas Updated (waiting your translation)

NOTA: Cryptoworks keys managment modified on version 1.11

Main Functions:
-Keys: edit, modify, clear
-Idents: add, clear, move
-Key Converter -> HEX/DEC format supported & vice versa (default len key=16)
-Export keys:
DRA_KEYS.TXT -> keys in hex/dec
Softcam.key -> softcam based format
Keys_Updated.txt -> All new keys updated in hex/dec format
Idents_List.txt -> All idents present in firmware by system crypt
-Import keys from: Softcam.key, DRA_KEYS.TXT, FuN6in1
irdeto keys not available in import with softcam -> 00 is not an ident
and import by Ident name not sure a 100% -> if you replace ident name completely function cannot import keys
-Firmware checker: all file checked before loading
You can use this function to certifiate ORIGINAL firmware or verify DragonCrypt Patch (DragonCrypt.ids certificate file)
-Funcard producer: HEX & BIN format supported
-Files Repair: Loader file for PIC & FUn7 cards
-Serial Dragon Loader: FuN7 & PIC Based cards, com port autodetection, card erase...
-DROP File function:
DRA file in main window
DRA File in Dragon Serial Loader
DRA File in Funcard Producer
DRA File in Firmware Checker
SoftCam.key File in Edit Softcam
SoftCam.key, DRA_KEYS.TXT, EEprom6in1.hex in import form
Report to HOW TO text file for more details.

Default Directories
- DCAesIni -> AES Offset INI table
- DCDra -> Store Dragon Firmware
- DCCaids -> Tables for caids
- DCThemes -> Themes apparences for application
- DCFuncard -> Store funcard produce
- DCLanguages -> Store multi language support files
- DCFileKeys -> SaveAS: *.BIN, *.DRA
DRA_KEYS.TXT, IDENTS_LIST.TXT, DRA_KEYS to SOFTCAM.KEY, SOFTCAM.KEY to DRA_KEYS,
KEYS_UPDATED.
Destination Directory will be open after file creation by the application
Directory automatiquely created if not exist.
- DCRepairFile -> PIC/FunFlash
Destination Directory will be open after file creation by the application
Directory automatiquely created if not exist.
- DCDatas -> Idents Table
- DCTables -> Firmwares Table
- DCSettings -> Serial loader settings (Com port, port auto detection, Erase card, PIC Based card)
Predator Table used by default
- DCids -> Original Version and patched version checked.
- DCTutorials -> All documentation about DragonCrypt Or DragonCam. PDF file format.

FAKE FILE:
Impossible to load Fake File (Check Firmware)
Impossible to Create Funcard from Fake File (Check Firmware)
Impossible to Programming Dragon Card Loader with Fake File (Check Firmware)
100% Secure and Safe.

Language Files include:
01-Albanian
02-Arabic
03-Bulgarian
04-Croatian
05-Deutch
06-English
07-French
08-German
09-Hungarian
10-Italian
11-Polish
12-Portugues
13-Spanish
14-Turkish
15-Russian
16-Norwegian
17-Swedish
18-Greek

Possible to Edit/Create new language file with Wordpad

Multi-Themes:
Differents themes to changes application apparence.


Tools written for Dragon Cam:
-DragonCrypt Keys Editor
-CIW Loader Dragon
-DragonCrypt CAIDs Updater (caids function include now on DragonCrypt)
-DRA AES Updater
-DRA AES Explorer

AES Updater how to:
==================
I-UPDATE AES KEYS
1.On TOOLS clic on Icon "DRA AES UPDATER"
2.Load or Drag File TPSCRYPT2.TXT
3.Load AES ini File (example predator357.ini)
4.Press Update button (Checksum updated after update)

II-EXTRACT AES KEYS
1.On TOOLS clic on Icon "DRA AES UPDATER"
2.Load AES ini File (example predator357.ini)
3.Press Extract Button
Read keys stored in DRA file

III-Save Log File
After keys updated or after keys extracted
TPSCRYPT2.TXT created in folder ..\DragonCrypt\DCFileKeys

Caids Updater how to:
====================
"Caids infos" include datas in file Caids.ini
"DRA Caids" is Caids Datas present in DRA File
Number of caids in DRA file showed near "DRA CAIDs"
2 Lists are ALWAYS SORTED and datas will be saved sorted in DRA file (more logical).
Impossible to duplicate caids
If file opened come with duplicate Caids only one will be used second removed
Press -> button = add new Caids in DRA File
Press <- button = remove Caids in DRA File
"DEL" keyword in "DRA CAIDs" list = remove caid
Drag Item From "Caids Infos" to "DRA Caids" = add new Caids in DRA File
Drag Item From "DRA Caids" to "CAIDs Infos" = remove Caids in DRA File
Button New Datas -> Restart with virgin caids datas
Button Update -> apply changes
Button Exit -> close window

Possible to add any NEW caids by editing file Caids.ini in folder ..\DragonCrypt\DCCaidDatas
(example added caids: 09B3, 0B01, 0B02,..)


Enjoy.