Help SE K790 GDFS problem

[vash200708]

My sister gave me a SE k790 which she purchase in canada and brought at Philippines, it was blocked. i went to mobile technician to unblocked it at suddenly the technician installed a wrong firmware k800 and now i cant use my SE k790 anymore and while im charging my mobile it shows on the screen "charging alien battery" so i can't charge anymore my SE K790. And im trying to fix it by myself and i used the software that i have read from the forum XS++ and it display the following message:

12:42:03| XS++ v3.1 (Darwin) Ready !
12:42:03| Executed on Microsoft Windows XP
12:42:09|
12:42:09| Attempting to open the interface...
12:42:09|
12:42:09| TURN OFF PHONE!
12:42:09| Hold 'C' button on phone and connect phone NOW.
12:42:09| You have 30 seconds...
12:42:09|
12:42:17| Baseband ID: 9900
12:42:17| Protocol Version: 3.1
12:42:17| Warning: IMEI name does not match GDFS name (IMEI:K790 GDFS:K800)
12:42:17| ...using IMEI name
12:42:17|
12:42:17| Profiling SEMC phone...
12:42:17| Platform: DB2020
12:42:17| OTP CID: 51
12:42:17| EROM CID: 52
12:42:17| EROM Color: Red
12:42:17| IMEI: 35220801xxxxxx
12:42:17| Phone ID: K790
12:42:17| Region: APAC
12:42:17| CDA: CDA123456/123 R2A
12:42:17| Firmware Version: R1KG001
12:42:17| EROM: R3A022
12:42:17| Ready for operation!

I will really appreciated for your quick response...

[senter]

You must make GDFS restore (if you have GDFS backup).

[vash200708]

i dont have GDFS backup because the mobile technician didn't do so. Is it possible to get a GDFS backup that is compatible to SE k790 in other way (like copying a backup of other k790 GDFS and restore it to my k790) that i can use to restore my GDFS?

thanks for your immediate response...

[senter]

Yes, can use GDFS from other K790, but is dangerous !!!
First read units from phone with Setool, then can restore other GDFS.

how i fixed my gdfs on a k800 and w850i i will not 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 DOINGthis will not work on phones that have been killed by wrighting the wrong gdfs ie / imei missmatchs on se tool read out please take note
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

[vash200708]

sorry for a very late respond to your reply senter.

i just want to clarify one thing before proceeding with the instruction you made for me and for the other that will have the same issue. if i backup my corrupted GDFS before doing the procedure in setool, and lets say after following the steps you made i WRITE a WRONG SCRIPT in my GDFS in other words i crew it up (means i kill my own k790 T_T). now my k790 is DEAD but i have a corrupted GDFS backup before writing the GDFS in setool, can i revive my k790 if i restore the corrupted GDFS backup that i made?

thanks for your kindness in making a procedure that will fix my problem with my SE phone, i know its risky but i really like to try it.

[vash200708]

Big thanks senter. Now my SE phone is revive and functioning well :D