Printable View
nece mi se uoaliti mobitel nakon sto sam vratio gdfs. ne prepoznaje mi ga niti xs++. i da...kad hocu pomocu xs-a nac mobitel, ctisnem c i ukljucim usb u mob., gore mi zasvjetli lampica crvene boje. dali mi je mobitel death? ako je dali ga mogu vratit.
mob je k610i. cid52 red
o kojem je mobu rijec,barem si to mogo reci...
Možda ti je prazna baterija,probaj ju napunit ili negdje posudit,pa onda probaj upalit mob i javi da li se išta dešava da znamo kako dalje i postaj zadnji log koji imaš (ovaj kad si vraćao GDFS)
hm.... zvuci kao da je otisao EROM.probaj ga ozivit sa KKClientom
joj sorry,nisam vidio...probaj flashnuti ponovo svoj GDFS,stavit drugu bateriju,ili svoju malo pripunit i onda dugo drzi tipku za paljenje,meni se isto to dogodilo s k750i...
evo sad sam stavio bateriju u drugi mob i pise da je puna do kraja. moze mi neko rec kako da ga ozivim pomocu kkclienta.
EDIT:
evo napravio sam EROM update sa kkclient-om. ali opet mi xs i kkclient ne vide mobitel kad stisnem c i umetnem usb. molim vas hitnu pomoc.
EDIT2:
evo sad sam sa setool-om uspijo podici mobitel. napravio sam ponovan flash i nista. dali bi mi neko mogao dati backup gdfs.?
i kako se radi vraca gdfs sa setool-om?
ne moze ti ga nitko dati jer svaki mob ima svoj jedinstveni GDFS,i ako nemas backup a nesto si zabrljao morat ces na servis s njim
I meni isti problem vratio GDFS (od K610) napravio update EROM-a i isto crveno blinka kad ga hoću upaliti. Na XS++ ga ne mogu spojiti. Mob je K610@W660 CID52.
dali se moze napravit neki test point, kao na motoroli?
Ne znam sto je tocno to, ali mislim da ne moze.
Nema TP-a za SE,ali ako imate dobre živce i dosta vremena ima tutorial kako to napraviti s blank GDFS-om,samo ga moram naći,pa ću ga stavit tu
Evo našao sam
= Citat =:
me or lasyk take no responsibility for any thing u try to do from this link TAKE A GDFS BACK UP FROM UR PHONE !!!!!!!THIS IS NOT FOR A NEWBE CHANGE UR GDFS WILL KILL UR PHONE IF U DONT KNOW WHAT U ARE DOING
Case:
Let's say you have a DB2020 phone with some GDFS issue, say you wrote K800 firmware to a K790 and now you have "no network".
Solution:You'll have to rewrite the original GDFS. Sadly, most users never back it up before proceeding with whatever operation they intended to do in the first place. This is done through the "Read GDFS" button in SETool, btw . it will produce a .bin-file named with the phones IMEI and can be found in your SETool basedir. Take good care of it.
Now, lets say you didn't back up the phones GDFS and did something to screw it up. Then you have a problem, because rewriting it with another phones GDFS will screw the security units and the phone will be bricked. Generally a bad thing, right ?.
Luckily, there is a way to solve this and the procedure is as follows:
Use only COM/UFS interfaces (but i used it with out my setool3 box just used se tool lite just make sure u dont turn ur phone on at all till it is finished )
1 (Optional): Back up the corrupt GDFS (yes, even though it's corrupted, so you have a full backup just in case). Again: "Read GDFS". Move it to a safe place on your HD, this is to avoid accidentally deleting it and for avoiding confusion with all the other txt-files that will appear later on.
2: Create a scriptfile (a normal txt-file will do) with the following contents:
Code:
---------------------------------------------------------------------------------------
gdfsread:00020e5a
gdfsread:00020e48
gdfsread:00010851
gdfsread:00000006
gdfsread:0000000E
gdfsread:00000013
gdfsread:0000001C
gdfsread:00000018
gdfsread:000000AA
---------------------------------------------------------------------------------------
Now save it. Name it "readsecunits.txt" or whatever. Select the file in SETool's MISC-field and press "Write SCRIPT".
All the read units will be stored in a single file named by the phone's IMEI.
rename it as "secunitsbackup.txt" to avoid confusion
3: Apply the GDFS from a working DB2020 phone.
- Read it out from the source phone (it will be stored in the SETool basedir named by the source phone's IMEI)
Do NOT turn the phone on afterwards.
4: Now, you'll have to write back the original units. Apply the "secunitsbackup.txt" you created by selecting it in the MISC-field and pressing "Write SCRIPT".
Voila, it should have done the trick.
u may have to hold the 2 and 5 button to get setool lite to recognise ur phone not the c button
Another method (Without the need for GDFS backup/etc...)
Create and execute the following script:
gdfswrite:000000ACXX
Set XX to whatever corresponds to your phones bandlock:
Code:
---------------------------------------------------------------------------------------
;00 MS_GSM900
;01 MS_EGSM900
;02 MS_DCS1800
;03 MS_PCS1900
;04 MS_GSM900_DCS1800
;05 MS_EGSM900_DCS1800
;06 MS_GSM900_PCS1900
;07 MS_EGSM900_PCS1900
;08 MS_DCS1800_PCS1900
;09 MS_GSM900_DCS1800_PCS1900
;0a MS_EGSM900_DCS1800_PCS1900
;0b MS_GSM850
;0c MS_GSM850_PCS1900
;0d MS_EGSM900_GSM850
;0e MS_DCS1800_GSM850
;0f MS_EGSM900_DCS1800_GSM850
;10 MS_EGSM900_GSM850_PCS1900
;11 MS_DCS1800_GSM850_PCS1900
;12 MS_EGSM900_DCS1800_GSM850_PCS1900
----------------------------------------------------------
thanks to sng i have changed it a bit to use se tool lite
me or lasyk take no responsibility for any thing u try to do from this link TAKE A GDFS BACK UP FROM UR PHONE !!!!!!!
Sorry,zaboravio sam ubaciti K610GDFS link http://filebeam.com/8878e4593c310dea7e9ee7a03ac2b180
engleski mi nije bas jaca strana...XD
pa ako bi neko mogao prevesti ovaj tut. na hrvatski.
sad sam isao na read gdfs i doslo mi je do executing cs loader gdfs startup. i nista se ne desava dalje.
evo log:
ChipID:9900,EMP protocol:0301
RECOVERY BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:51 PAF:1 IMEI:35463901106958 CERT:RED
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
loader startup: executed
loader GDFS startup: executed
smth wrong with usercode reset,error is: 1
Elapsed:53 secs.
ovo boldano i podvuceno me zabrinjava
Sve je to zanimljivo, ali malo me brine ovaj dio:
To bi po meni znacilo da se ne moze koristiti standardni USB kabel... :hm:= Citat =:
Use only COM/UFS interfaces
ako nece sa tipkom c, onda mora sa 2+5.... flashaj prvo gdfs sa xs++ pa onda erom... ja sam tako na svom mobu
naravno da ima TP za SE, doduše ovdje nije potreban= Citat =:
Izvorno postao Ares
E ljudi moj K610 se ni s tipkama 2+5 neće spojiti na XS++... Samo se ovo javi:
EDIT: I tu stane. Koliko bi se brzo trebao učitati?= Citat =:
11:35:04| XS++ v3.1 (Darwin) Ready !
11:35:04| Executed on Microsoft Windows XP
11:35:09|
11:35:09| Attempting to open the interface...
11:35:09|
11:35:09| TURN OFF PHONE!
11:35:09| Hold 'C' button on phone and connect phone NOW.
11:35:09| You have 30 seconds...
11:35:09|
11:35:14| Baseband ID: 9900
11:35:14| Protocol Version: 3.1
ista stvar se i meni desava...
ja sam odustao od svih opcija i odlucio se na najednostavniju soluciju... kupiti novi mob..hhh
pitao bih admine di da stavim toppic za prodaju...htijo bih se rjesit nekih dijelova od mog k610i.
Ej! Zabranjena je trgovina na forumima! Odi na njuškalo, reggaj se i prodaj mob.
BTW, mene zanima kolko bi koštao popravak u serivsu.
Trebao bi ti ili detektirati mobitel, ili iskociti ono dolje da je pronadjen novi hardver. I jedno i drugo unutar sekunde-dvije.= Citat =:
Izvorno postao krac22
@stunk,
Oglasavanje na forumu je zabranjeno. Sto bi i sam znao da si slucajno procitao pravila. :jehon:
Preproucam ti da ih procitas sto prije, da se ne bi opekao bezveze.
isti problem imam :/
Ljudi jel ima mobu pomoći bez servisa? Gore navedeni K610 CID52 RED. Prvo stavio heapshift! patch (mob ima W660 R8BB001 FW) i mob mi ostao 3 dana ugašen nije mi se dalo izvaditi pa vratiti bateriju. Kad sam to nakon 3-4 dana napravio, mob se nije htjeo upaliti. Napravim restore GDFS-a, isto. Napravim update EROM-a, isto. Pokušam ga spojiti na XS++ sa C, blinka crveno. Probam s 2+5, gore navedneo što se događa. Sada, da nisam možda zeznuo EROM? Kako se radi update EROM-a? Jel dovoljno samo stisnuti "Update EROM" na kkclientu?
Probaj ovako: izvadi bateriju na 1-2 minute,vrati ju,otvori Setool2lite,klikni na "identify" i spoji mob sa USB-om tako da držiš 2+5 i pričekaj da čuješ zvuk kao kod spajanja novog hardwera.Odspoji mob,izvadi bateriju,vrati je -spoji se na XS++ i XS bi sad trebao vidjeti mob ( ako ga vidi i ako nema greški flash-ni samo MAIN , ali pazi da ti je baterija puna ,jer tijekom cijelog postupka NESMIJEŠ upaliti mob)
Kod mene je upalilo ( prošli tjedan frendu oživio K610), a postupak sam našao na TopSony-u original post by @senter
Evo i originalni link,ako nekog zanima http://www.topsony.com/forum/showthr...2462#post92462
Ali meni SETool2lite ne radi, samo javlja da nekakav error da nemam pravo na pristup programu.
Probaj ovaj http://www.esnips.com/doc/ba850a45-a...ool2Lite-V1.11 . Taj ja koristim i znam da radi= Citat =:
Izvorno postao .:TailS:.
I isključi antivirusni,jer sa zadnjim update-ima prepoznaju qamaker.exe kao virus
I još jedna stvar-Setool je jako osjetljiv na viruse i ostalu gamad,pa ako nisi skoro pregledao komp - provjeri i tu mogućnost
Došao do SETool-a na drugom kompu i kad sve napravim kad spajam mob sa C on mi kaže ovo:
I tu stane. U čemu je problem?= Citat =:
Did not receive 0x5a. Continuing
2+5 umjesto C i drži skroz dok ne čuješ onaj zvuk,kao za novi hardware= Citat =:
Izvorno postao .:TailS:.
Sorry malo sam i ja krvio napisao - stvar je u tome što to XS++ javlja.