yes i hope soo
I know that you don't have free time to continue modding E680/i, but you know, we really need better firmware, so why don't you try to write down some instruction show us how to mod, then we will do it together.
Just my opinion, hope you will reply soon, thank you...
yes i hope soo
SxU
d same wid 'em..
I was part of that strange race of people aptly described as spending their lives doing things they detest to make money they don't want to buy things they don't need to impress people they dislike. -- Emile Henry Gauvreay
hey guys... been a long time i know... and i haven't been around here much... hopefully that'll change (trying to change it)... but work's a killer...lol!! anyhow... i'll put in some time to compile a little doc to explain motomodding for the e680/i/A780.... anyhow... glad u guys like my work...
** SANDMAN **
--------------------
Craig A.C. Gomez
Software Engineer (Developer)
SkillNet Solutions Inc.
http://www.skillnetinc.com/
THERE ARE NO STUPID QUESTIONS... BUT THERE ARE A LOT OF INQUISITIVE IDIOTS...
Great.....
Will be waiting.
I found some program that may be useful to compile new firmware.
from this
http://ezxcodec.medoosa.ru/
Ps. don't ask me about how to use Because i don't know too :PEZX-based cellphones firmware editing in Windows environment.
What program can do at the moment:
- decompile firmware file (*.SBF) to separate codegroups (known supported SBF files are E2, E6, A1200);
- decompile CramFS codegroups to files and folders;
- compile CramFS codegroups from files and folders keeping original properties and codegroup size;
- compile firmware file from codegroups;
- work with Motoskin v1.00 and 1.10 (iconres.ezx file and *.skn files) from E2, E6, A1200, Z6, V8;
- extract and change bootscreen picture in CG39 (known to work with at least A1200 and E6);
- script support - it is possible to launch commands from special text files to apply patches replacing, adding or deleting files from CramFS codegroups or from Motoskin (iconres.ezx) files, or editing configuration files in CramFS codegroups.
Just try together
thanks, man, it's really help