How to Repair a db2020 GDFS

[NADEEM GONDAL]

This is a last resort to a broken gdfs, first try flashings the phone, or repairing the erom to make sure you 100% have a gdfs problem.
me or SE Users take no responsibility for anything you try to do from this Guide, TAKE A GDFS BACK UP FROM UR PHONE !!!!!!! YOU WILL KILL UR PHONE IF YOUR NOT SURE OF WHAT U ARE DOING.
Case: Let's say you have a DB2020 phone with some GDFS issue.
Solution: You'll have to rewrite your GDFS back-up. 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 or xs++3.1, btw . it will produce a .bin-file named with the phones IMEI and can be found in your SETool or xs++ 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:
What you will need
setool2 lite 1.11: SE Tool Lite 1.10 + update 1.11
usb drivers: In the setool lite folder go to drivers/USBFlash_driver/ right click on ggsemc.inf and press install.
A working Db2020 Gdfs of the same model.
With se tool lite just make sure u dont turn ur phone on at all till it is FISNISHED.
1 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 but it must have a .txt extension. 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 of the same model.
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.
You may have to hold the 2 and 5 button to get setool lite to recognise your phone not the c button.

[GNS_KUMAR73]

i have a k530i dead set all flash is done not complete in gdfs exiting err. plz help me its urgent

[mr.Dubai]

plz fast chack cd . after full flash............................................. .

[Ganja22]

won't work m8, you should have copied the whole text which said as well to write db2020 gdfs with option 'format before writing gdfs' which won't work on cid52 or cid53, this failed to work for me on cid49 phones as well though.

if db2020 gdfs permanently damaged do what laser said again and again
- use other tool and testpoint
- change flashchip and do emptyboard procedure
- remove flashchip and erase in external programmer, program with marika_brown_49v5.bin and put back in phone. after that phone will be brown and you can use emptyboard procedure although OTP already programmed

Regards,
Ganja

[AlexRussell]

Help, it doesn't work, my phone is detected as K700.
I tried multiple firmwares, still can't get it working.
The screen goes white and black white and black and so on, though vibrates 1 time when I switch it on.
HEEELP!
The problem is not with the display, cause I changed it.