Greetings.
as many ppl noticed, kukuruzer's "read codes" not only fakes you, but also damages phone - very next restart and phone only can do "red blink".
technical details follows:
when you enter lock/unlock code on db2020 phone, firmware change security units (as on old phones) and write raw code into GFDS.
"codes", which is "calculated" by kukuruzer,maded by next algo -
Code:
for i:=0 to 8 do _msg(random($a)+chr($30));
so, they have not any relation to real.
on very next boot, EROM detecting security zone change and looks for
codes (which firmware wrote when you entered code) to make security checks. as "codes" are fake - EROM thinks that it is security violation and says goodbye (red blink).
so, what is "cure" ? the only cure is :
1. restore ORIGINAL LOCK ZONE (because firmware "cleaned" it).
if kukuruzer software NOT creating phone security are backup
BEFORE "codes calculate" - you will need expensive davinci credits or ask
somebody with special setool2 account to revive your phone.
Also, if provider,which phone locked to, is known, there is a very
positive chance to "rebuild" LOCK zone manually
(even in that case you need execute csca unlock with other tools,
because,as far i know, current kukuruzer (11.02) NOT supporting
csca logs)
2. erase "calculated code". that is very simple thing - all you need to do
is erase gdfs unit $850 in block 1.
that can be done also with other tools, because alas, kukuruzer
not supporting user-defined scripts.
as usual, mizer+lead probably will say about that post "bull_****, lie, thief,etc"
but you already understand, that i posting only raw real facts.
hopefully, kukuruzer team will steal db2012 solution without their silly inventions like "read codes"
so your phones will be safe.
(of course, if you spend your money on kuku++)
ps.
kulankendy "authors", probably you will read that post.
you could at least write in your announce about stolen db2020 solutions
"thx and credits to the_laser". Also do security backup before any plays with gdfs - it is not a toy