SETool2 Lite, [DB2010 CID49 Tool]

dengel

Posted on 27/8/2007, 10:33

User deleted

CITAZIONE

allow me to introduce setool2 lite.

it is reduced version of full setool2.

limitations:

- working only with cid49 db2010 phones (of course, sibley-based phones is supported)
(identify works on all db2010/db2012 phone, so you can at least see usercode...)
- unlock/repair and recovery functions removed.
- ufs interface removed
- no single setting is saved

no other limitations.

v 1.06
- now working with DB2020 CID49/51/52 phones.
FREE flashing, FREE files WRITE, FREE GDFS read/write.
- NO .VKP, NO FILES READ, NO CROSS-CID FLASH

v 1.07
- now working with DB2012 CID50/51 phones.
FREE flashing, FREE files WRITE, FREE GDFS read/write, FREE USERCODE READ
- NO .VKP, NO FILES READ, NO CROSS-CID FLASH
- now file in misc.edit during flash procedure first treated as package,
if it not recognized as package, it treated as script.
- added db2020 usercode reset (because gbrooks sniffed out
string "06 89 01 01 00 0D 8B", GJ, gbrooks )

Download SeTool 2 Lite 1.07 Free

Short Help

first, you must select interface.
USB is dcu60.
UFS is nothing.
COMx - comport (you should use ftdi-based service cable to achieve speeds more that 115200)

then select phone model.
it is important.

then press desired operation.

"identify" will show phone information, lock state and usercode.
also, identify will show if you have REST file for your phone.

"read gdfs" will read gdfs from phone in BINARY format.
ALWAYS BACKUP YOURS GDFS AND KEEP BACKUP IN SAFE PLACE
"write gdfs" will write gdfs to phone in BINARY format
file, selected in "misc. edit" will be assumed as gdfs in binary format.

"read flash" will read flash.
start and len of readed area must be filled in "read setup".
if you want to produce "flasheable" readout, check "read SSW" checkbox.
IT IS NOT WORKING WITH DB2020 PHONES

"flash" will flash phone firmware with possible package uploading.
notes:
if anything selected in "firmware upgrade pack" edit, attempt to handle it as SFA file will be made during flash.
if anything selected in "misc. edit", attempt to handle it as package (.zip) will me made during flash.
if anything selected in "restore file" edit, it will be assumed as "firmware restore" file.

"write script"
is most powerful and usable tool for sense users.

first, it can process .vkp script files.
just select "anyfile.vkp" in "misc. edit" and press write script.
.VKP PROCESSING IS NOT SUPPORTED FOR DB2020 phones

second, it can process "script" file. "script" file is usual text file with following commands:

CODICE

command
readpkg:/dir/in/phone

makes a file package for transferring to other phones/etc
NOT SUPPORTED IN DB2020 PHONES

example:
readpkg:/tpa/user

command:
writepkg: \package\on\pc

write previously backuped files back to phone

example:
writepkg:c:\package\k600\emea1.pkg

command:
readdir:/starting/dir/in/phone

extracts all files and directories from phone to ph_out/ folder in setool2 directory
NOT SUPPORTED IN DB2020 PHONES

example:
readdir:/tpa/user

command:
readfile:/file/in/phone

extract file from phone into ph_out directory
NOT SUPPORTED IN DB2020 PHONES

command:
mkdir:/dir/in/phone

command:
rmdir:/dir/in/phone

command:
delfile:/file/in/phone.ext

changed command:to write a file into phone filesystem now use
wrfile:file\on\pc,/file/in/phone

command:
gdfsread:BBBBUUUU

; read gdfs block BBBB unit UUUU. variable will be written as ready script.

gdfsreadbinary:BBBBUUUU

; read gdfs block BBBB unit UUUU. variable will be written in raw binary form.

gdfswrite:BBBBUUUUDDDDDDDD.....

; write gdfs block BBBB unit UUUU bytes DDDDD.... (hex form)

now, short script example with explanations:

CODICE

gdfsread:00000013
; read gdfs block 0 unit 0x13. variable will be written as ready script.
gdfsreadbinary:00000013
; read gdfs block 0 unit 0x13. variable will be written in raw binary form.
gdfswrite:00020CBF31323334
; write gdfs block 2 unit 0xcbf bytes 0x31323334 (ascii 1234)
chdir:/
; change dir to root
readfile:/tpa/preset/log.txt
; readfile sample
readfile:/tpa/preset/system/language/ru.lng
; readfile sample
readfile:/tpa/preset/custom/customize.xml
; readfile sample
chdir:/tpa
; change dir to /tpa
listdirs:
; show all directory and filenames
mkdir:/ifs/security/tester
; make directory example
wrfile:cora.fps,/ifs/security/tester/test.txt
; write file .\cora.fps to /ifs/security/tester/test.txt
makepkg:/ifs
; make package from /ifs directory as pkg_your_imei.pkg in current directory
delfile:/ifs/security/tester/test.txt
; delete file
rmdir:/ifs/security/tester
; delete directory (can only be done after all files removed)
writepkg:test.pkg
; write package from test.pkg
chdir:/ifs/security/tester
; chdir
listfiles:
; show all files in /ifs/security/tester
readdir:/tpa/user/
; extract all data to ph_out directory

s you know, cid49 phone requires REST files.
i included "some" ready REST files, also i included REST file making tool.

if you NOT have REST file for yours firmware - download supported firmware and flash your phone.
or, download yours firmware and make rest file with included ssw2rest utility.

example:
get firmware, say R4CE012_1250316_GENERIC_HN.ssw

run ssw2rest R4CE012_1250316_GENERIC_HN.ssw
copy R4CE012_CXC1250316_GENERIC_HN to REST directory.

DB2020 PHONES NOT NEED REST FILES !!!!!!!!!

there is drivers directory where ftdi cable drivers and usb (dcu60) setup file placed.

enjoy.

0 replies since 27/8/2007, 10:33 3687 views