Dead phone! GDFS flashing problem

[jb00gie]

Hey everyone, I'm new here.

Here's the history and what happened. I did this all with XS++ Ver2.2 and setool2 lite following Wally_Dog and ask_win's tutorials on the SE-NES forums.

1. Bought my phone off ebay- A branded Cingular phone. (never backed up the GDFS)

2. Flashed Main with W810_R4EA031_MAIN_GENERIC_HN_RED49.mbn,
flashed FS with W810_R4EA031_FS_EUROPE_2_RED49.fbn,
and used Europe 2 custpack (CDA2102555/11)

3. backed up my GDFS

4. added camera and acoustics driver, flash themes, and different media skin

when I plugged it into XS++ it read-

baseband ID: DB2010
OTP CID: 49
EROM CID: 49
EROM Color: Red
Network: EUROPE_2
CDA: CDA102494/77 R3A <---- (That's odd?! it didn't say CDA102555/11, the custom pack I used)
Firmware Version: R4EA031

5. I was about to add some patches with setool2 lite, but decided to back up my GDFS (even though I already backed it up using XS++) like on Wally_Dog's tutorial before adding the patches.

And here is where the problem began.

While setool2 lite was backing up the GDFS, some error occurred (I don't remember what it said). All I remember it saying was something like "that is fatal" or "could be fatal." I disconnected my phone and tried to write my backed up GDFS from XS++ (following Wally_Dog's "Clean GDFS Flashing") but for some reason it cannot open the backed up GDFS file?!?

here is what setool2 lite reads:

-------------------------------------------------------------------------------
Chipid8040, EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
Trying to launch embedded bootloader...
ebedded flashloader:
COMPACT_IC_LOADER_CRIPPLED_SETTOOL2_R2
Flash ID check:897E
Flash props send ok
FOUND: W810_R4EA031_CXC1250316_GENERIC_HN
Restore from:R4EA031_CXC1250316_GENERIC_HN
Can't open file "C:\Documents and setting\Owner\My Documents\W810_35235001xxxxxx_GDFS_BACKUP
Seting up GDFS...
Abort all operations.
set_gdfs_props failed, exiting
Elapsed:41 secs.
-------------------------------------------------------------------------------------

When I plug it in to try to write the GDFS with XS++ it reads this:

-------------------------------------------------------------------------------------
BasbandID: 8040
Hardware Platform: DB2010 Marita compact
Protocol Version: 3.1

Sending db2010_cid00-prodid_p3l.bin...
Applet ID:061113 1250 ALUCXC155872_COMPACTPRODUCTION_IC_LOADER P3L
This is a PRODUCTION_ID loader
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Cannot open GDFS
Warning: IMEI name does not match GDFS name (IMEI:w810 GDFS:n/a)
...using IMEI name

profiling SEMC phone...
Baseband ID: DB2010
OTP CID: 49
EROM Color: Red
IMEI: 352350001xxxxxx
Phone ID: W810
Network: n/a
CDA: n/a n/a
Firmware Version: n/a
EROM: n/a
Ready for operation!

Sending db2010_cid49red_cs_r3a010.bin...
Applet ID: 070524 1030 AN2CXC1327364_COMTACT_SEMC_CS_LOADER_R3A010
This is a CHIPSELECT loader
Activating loader...
Activating GDFS...
---------------------------------------------------------------------------------------------

Then it hangs on FOREVER reading "Sending Applet CSloader" on the bottom and the progress bar is full. I let it sit there for 3 hours and it still said the same thing so I pressed "STOP" and aborted.


So I tried writing the "Clean GDFS' file that Wally_Dog has in his esnips but setool2 lite says the same thing.

WHY CAN'T SETOOL2 LITE OPEN THE BACKED UP .BIN FILE? IS MY PHONE DEAD? IS THERE ANYWAY TO REVIVE IT?

PLEASE HELP!!!

[adam234]

ARE YOU CHECK YOUR CURRENT IMEI match THE FLASH IMEI?? IF the imeis are different , it is possible to have this problem

[themovefoward]

Try to hold 2+5 when connecting your phone to XS++.

[yener90]

perhaps wotan server can do it. you can repair erom with it free.

[MAPLE GSM]

first you need erom upgrading and than flash the phone with correct flash file no need to touch gdf

[DXX-T]

Since it said errors while backing your GDFS up, then you're so called "backed up" GDFS is corrupt.
And if you tried to flash that one to your phone, then of course it will kill your phone..

Correct me if I'm wrong.

[superskipp]

What version of XS are you using?
Try V1.0.
I had a similar problem, and for some reason only V1.0 worked (V2.2 didn't).

I see that you used V2.2, sorry

[xulos]

i have k550 and i want to change imei to w610 and all that is necessary because i want to download newest firmware with sesus .. now when i go to update new firmware seus turn it back to k550i .what should i change ?

[mackydon]

Hey everyone, I'm new here.

Here's the history and what happened. I did this all with XS++ Ver2.2 and setool2 lite following Wally_Dog and ask_win's tutorials on the SE-NES forums.

1. Bought my phone off ebay- A branded Cingular phone. (never backed up the GDFS)

2. Flashed Main with W810_R4EA031_MAIN_GENERIC_HN_RED49.mbn,
flashed FS with W810_R4EA031_FS_EUROPE_2_RED49.fbn,
and used Europe 2 custpack (CDA2102555/11)

3. backed up my GDFS

4. added camera and acoustics driver, flash themes, and different media skin

when I plugged it into XS++ it read-

baseband ID: DB2010
OTP CID: 49
EROM CID: 49
EROM Color: Red
Network: EUROPE_2
CDA: CDA102494/77 R3A <---- (That's odd?! it didn't say CDA102555/11, the custom pack I used)
Firmware Version: R4EA031

5. I was about to add some patches with setool2 lite, but decided to back up my GDFS (even though I already backed it up using XS++) like on Wally_Dog's tutorial before adding the patches.

And here is where the problem began.

While setool2 lite was backing up the GDFS, some error occurred (I don't remember what it said). All I remember it saying was something like "that is fatal" or "could be fatal." I disconnected my phone and tried to write my backed up GDFS from XS++ (following Wally_Dog's "Clean GDFS Flashing") but for some reason it cannot open the backed up GDFS file?!?

here is what setool2 lite reads:

-------------------------------------------------------------------------------
Chipid8040, EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
Trying to launch embedded bootloader...
ebedded flashloader:
COMPACT_IC_LOADER_CRIPPLED_SETTOOL2_R2
Flash ID check:897E
Flash props send ok
FOUND: W810_R4EA031_CXC1250316_GENERIC_HN
Restore from:R4EA031_CXC1250316_GENERIC_HN
Can't open file "C:\Documents and setting\Owner\My Documents\W810_35235001xxxxxx_GDFS_BACKUP
Seting up GDFS...
Abort all operations.
set_gdfs_props failed, exiting
Elapsed:41 secs.
-------------------------------------------------------------------------------------

When I plug it in to try to write the GDFS with XS++ it reads this:

-------------------------------------------------------------------------------------
BasbandID: 8040
Hardware Platform: DB2010 Marita compact
Protocol Version: 3.1

Sending db2010_cid00-prodid_p3l.bin...
Applet ID:061113 1250 ALUCXC155872_COMPACTPRODUCTION_IC_LOADER P3L
This is a PRODUCTION_ID loader
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Activating GDFS...
Cannot open GDFS...
Cannot open GDFS
Warning: IMEI name does not match GDFS name (IMEI:w810 GDFS:n/a)
...using IMEI name

profiling SEMC phone...
Baseband ID: DB2010
OTP CID: 49
EROM Color: Red
IMEI: 352350001xxxxxx
Phone ID: W810
Network: n/a
CDA: n/a n/a
Firmware Version: n/a
EROM: n/a
Ready for operation!

Sending db2010_cid49red_cs_r3a010.bin...
Applet ID: 070524 1030 AN2CXC1327364_COMTACT_SEMC_CS_LOADER_R3A010
This is a CHIPSELECT loader
Activating loader...
Activating GDFS...
---------------------------------------------------------------------------------------------

Then it hangs on FOREVER reading "Sending Applet CSloader" on the bottom and the progress bar is full. I let it sit there for 3 hours and it still said the same thing so I pressed "STOP" and aborted.


So I tried writing the "Clean GDFS' file that Wally_Dog has in his esnips but setool2 lite says the same thing.

WHY CAN'T SETOOL2 LITE OPEN THE BACKED UP .BIN FILE? IS MY PHONE DEAD? IS THERE ANYWAY TO REVIVE IT?

PLEASE HELP!!!

Try repairing erom and imei with with SeKing 3.0.6.6 (free)
Try reflashing both the main and fs and custompack

[endz]

i ever have this problem
then, i reflash fs+main again with SeKing
the custpack i use XS++ 3.1

then it work again