Actualizaciones de Se Tool Box

*v0.914037*

- added testpoint for db2020 phones.
db2020 testpoint idea made by dre_ambox team.
as i respected that, i not included db2020 testpoint in setool2
for a long time. but anything ends sometime.
now, setool2 users can enjoy gdfs db2020 gdfs repair.

*usage*:
1. it is only and only for professional.
users,advanced users, please go away.
2. testpoint is +3.3 voltage, connected to specific pin.
we suggesting to use +3.3v battery
(battery ground *MUST* be connected with phone's GROUND)
3. go to emptyboard fill & repair.
4. select any db2020 model.
5. press "TP STAGE #1". read instructions and execute them.
6. press "TP STAGE #2". read instructions and execute them.
7. phone is *BROWN* now.
8. staying on "emptyboard fill and repair" write correct gdfs_in_*ssw* format.
9. if flashing went fine, flash db2020 erom with needed CID.
10. phone now retail and repaired. fullflash phone as usual.
testpoint pictures (courtesy of drea_mbox team) included.
after *SETOOL2* db2020 testpoint procedure phone *FULLY*
working in "alternative security bypass" mode withoyt *ANY* restriction.

- *greatly *increased locosto-based SEMC ODM phones security bypass time.
(instead ~50 seconds, now we have ~18 seconds)
- minor bugfixes.

RAPIDSHARE LINK (http://rapidshare.com/files/12611580...14037.rar.html)
---------

Code:
---------
*warning !* our solution can *easily* fix phones, killed with
"kukuruzer zuide software" (based on out stoled solutions)

Esta actualizacion NO es para novatos por favor no lo intente SI no son usuarios expertos en SEtool,

se agrego soporte de REPAIR GDFS por medio de test point.. NO es facil pero si es mas sencillo que con dream BOX.

hare el video tutorial ..


EXPERTOS UNICAMENTE

q:
when i attaching phone using dcu60 i see following messages:

Code:
erom_readvar: error reading unit 1/725
error while reading security units
SECURITY UNITS CAN'T BE READ !
DAMAGED FIRMWARE/GDFS OR EMPTY PHONE

or

erom_readvar: error reading unit 1/851
error while reading security units
SECURITY UNITS CAN'T BE READ !
DAMAGED FIRMWARE/GDFS OR EMPTY PHONE
and process stops,but phone works normally on com/ufs.
what is root cause and what is solution ?

A:
that phone is tampered by d_reambox software.

during their famous method of "testpoint bypass", they writing patched erom with own custom loader embedded, patching simlock signature check and ... erasing simlock signature without any reason, which prevents setool2 from making backup.

i had write a post on their forum, but they too arrogant even to read it.

fix is extremly simple:

using com/ufs write next script in SIGNED MODE (check ONLY "USE SIGNED MODE" on settings)

for db2020:
Code:
gdfswrite:0001085144554D4D5944415441
for db2012:
Code:
gdfswrite:0001072544554D4D5944415441
alas, they custom loader also breaks alternative bypass support using dcu60 cable,
so you only can use SIGNED MODE with dcu60 after their "testpoint".

maybe i will write program (embed option in setool2) to restore tampered by d_reambox erom to correctly patched.

q:
when i flashing/completing/etc phone i got error like
Code:
loader startup: executed
Loader refused to start GDFS services,error is:29
loader GDFS startup failed, that is fatal
Elapsed: 734 secs.
what to do ?

a:
that error can be caused by different problems. lets see all of them

1. user has run "executor" application, which was not deleted after "new altbypass unlock".

solution -
select correct model
on settings check only "use preloader security bypass".
execute any operation, say : "read flash"

2. main software somehow has been damaged (cause of free tools, etc)
solution -
select correct model
on settings check only "use signed mode".
add to firmware area only main part of firmware
press flash (use com/ufs or dcu60 with "2+5" keys if phone not connecting with "C" )
after that, phone should show identify normally.

.... and if not....

3. gdfs area has been damaged (bad flash ic, firmware error,etc)
solution -

a) install empty flash chip and do emptyboard fill procedure
b) try to repair gdfs area with VERY complex testpoints
c) change both mcu+flash chip from other phone

http://www.mobile-files.com/forum/im...cons/icon1.gif
Code:
uploaded c902 r3bh002 firmware,fsimages and custpacks
uploaded z780 r3ba035 firmware,fsimage, all languages file,custpacks
updated w980 firmwares,fsimages,custpacks

Code:
ps.
today i browsed different forums and saw that mizerable kukuruzer idiot
again shitting from his mouth about copycats,killing phones,
"professional kukuruzer solutions",etc.

well, most probably you already know, that you can trust mizerable idiot
only when he telling about next payed update for his copycat "suite".

lets see next kukuruzer update - i'm sure we will find inside
another byte-by-byte copy/paste from setool2 ;)
of course, mizer will write that it is original solution,which was developed
by "great mastermind" , it is safe and not killing phones,etc.

all normal ppls should see mizerable thing as clown in circus.
so, just allow clown to entertain us.


also i noticed that some ppl, who own drea_mbox, accusing me in
"stealing tp solution" and negation of that.
that is not true, cause only thing we used from drea_mbox is testpoint
pictures, that was noted in announce and credits was given for
really great and hard work by drea_mbox team.

uploaded complete pack of RED53 k610 k610im k618 v630 w710 w850 z610 z710 firmwares and fsimages.

uploaded K630-V640-K660 full schematics and repair manual
uploaded K800-K810 full schematics and repair manual

uploaded C702 R3CA033 firmwares and *all_languages_pack*
uploaded C902 R3CA037 firmwares and *all_languages_pack*

uploaded K630-V640-K660 full schematics and repair manual
uploaded K800-K810 full schematics and repair manual

updated C702 R3CA033 firmwares and all_languages_pack
uploaded C902 R3CA037 firmwares and all_languages_pack

let me remember, that all_languages_pack is .zip file,which should be used as custpack.
of course, nobody stops you from deleting unneeded languages from it.