Hi!
Attached DB2020 working GDFS:
K550/W610
K610/V630/K618
K790
K800/K810
W710/Z710
W850 (SSW and BIN format)
W880
S500/W580
Download :http://www.sendspace.com/file/usorvb
NEVER write GDFS into DB2020 phones before read this:
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!
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)
- Check "Format GDFS" in "Settings" and write it to the damaged phone by selecting it in the MISC-field and pressing "Write GDFS".
if you have CID52 phone, NOT CHECK "format GDFS"
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.
I'll ask the_laser to produce some DB2020 GDFS files in case you don't have a working phone to read from.
another method of quick recovery (without all mess with gdfs backup/write/etc)
create and execute following script
gdfswrite:000000ACXX
set XX to valid for your phone:
;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
Note: This metodh only works if your phone is CID49/51. Not works if is CID52 (can't format GDFS area)
Please, use this thread ONLY to ask for a GDFS file.
Will be updated
Thanks
Regards!
Home 
