Please help!! W600i May have wrong GDFS?

[Gigman]

I cant get my W600i to flash and work. It has WSOD. It takes the Main and Fs in setool but I get "wrong response, break. loader fs startup failed, that is fatal" when trying to load custpack. I put the custpack in the "misc files" window but it wont finish I get that error. I tried to use XS++ Darwin and got this error when trying to flash FS:

XS++ LOG

Header type: BABE

16:52:29| 261 flashblocks

16:54:28| Failed sending flashblock 114. Returnvalue 0x45

16:54:28| Finishing flash

16:54:43| Error: Flashing failed

Setool log:

Trying to launch embedded bootloader...
INT LDR:COMPACT_ID_LOADER_CRIPPLED_SETOOL2_R2
Flash ID check:890D
Flash props sent ok
FOUND: R7CA017_CXC1123106_NAM_2_EE
Restore from:R7CA017_CXC1123106_NAM_2_EE
CSloader version:
SETOOL2 LITE COMPACT_SEMC_FS_LOADER (FAT V26)
loader startup: executed
wrong response, break.
loader fs startup failed, that is fatal
Elapsed:330 secs.


I dont know what to do to get it working now. I tried to write the GDFS back to the phone using the GDFS I backed up and got this from setool:


OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

Trying to launch embedded bootloader...
INT LDR:COMPACT_ID_LOADER_CRIPPLED_SETOOL2_R2
Flash ID check:890D
Flash props sent ok
FOUND: R7CA017_CXC1123106_NAM_2_EE
Restore from:R7CA017_CXC1123106_NAM_2_EE
CSloader version:
SETOOL2 LITE COMPACT_SEMC_FS_LOADER (FAT V26)
loader startup: executed
loader GDFS startup: executed
Will write GDFS now.
will write 1250 variables
gdfsWrite err:11,block:1,unit:3CA
gdfsWrite err:11,block:2,unit:CF0
gdfsWrite err:11,block:2,unit: D1C
gdfsWrite err:11,block:2,unit: D26
gdfsWrite err:11,block:3,unit:FA1
gdfsWrite err:11,block:3,unit:1389
gdfsWrite err:11,block:3,unit:138C
gdfsWrite err:11,block:4,unit:1773
gdfsWrite err:11,block:4,unit:1B5E
gdfsWrite err:11,block:5,unit:1F57
gdfsWrite err:11,block:5,unit:233F
done
Phone detached
Elapsed:74 secs.


I read the post about repairing gdfs but dont understand. Can someone please help? I hope I'm posted in the right place!

[hyperion17]

Flash ONLY MAIN , by pressing "2" and "5" instead "C", when you connect with Setool.
If it still not works, flash the FS without CDA. If it turns on and gives configuration error, flash CDA.

[philzfog]

show a read out from se tool lite if it has a imei missmatch then that is becuse uv wrote a diffrent gdfs to the phone and killed it the only way to fix is with se tool box and test point or buy a log for D-Ultimate Unlocker and press press unlock and fix sec units these are the only 2 ways to fix it or wright the gdfs back up from that phone if u still have

[Gigman]

Thank you for your quick reply Hyperion. I flashed the main by pressing 2+5 and still nothing. Flashed FS without CDA "That's the zip file I assume?" Still WSOD. I held down 2+5 when connecting and flashing FS also. I had a different result than last time when flashing FS file. See log file?

LOG FILE:

OTP LOCKED:1 CID:49 PAF:1 IMEI:35744600583447 CERT:RED
LDR:051207 0928 NPACXC1250165_1_SEMC_COMPACTFLASHLOADER R2B
Flash ID check:890D
Flash props sent ok

DETACH CABLE FROM PHONE.
REMOVE BATTERY FROM PHONE, THEN INSERT IT BACK
THEN PRESS "READY"


OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

Trying to launch embedded bootloader...
INT LDR:COMPACT_ID_LOADER_CRIPPLED_SETOOL2_R2
Flash ID check:890D
Flash props sent ok
FOUND: R7CA017_CXC1123106_NAM_1_EE
Restore from:R7CA017_CXC1123106_NAM_1_EE
writing D:\W600_R7CA017_MAIN_NAM_1_EE_RED49\W600_R7CA017_M AIN_NAM_1_EE_RED49.mbn
CURRENT FLASH FILE CID:49
SSW uses dynamic hash, dynamic hash len is:348
Will flash 348 blocks...
SSW loading returns:0
exception while closing port
Elapsed:412 secs.
ChipID:8040,EMP protocol:0301

OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35744600583447 CERT:RED
LDR:051207 0928 NPACXC1250165_1_SEMC_COMPACTFLASHLOADER R2B
Flash ID check:890D
Flash props sent ok

DETACH CABLE FROM PHONE.
REMOVE BATTERY FROM PHONE, THEN INSERT IT BACK
THEN PRESS "READY"


OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

loader prologue not accepted
Elapsed:28 secs.
ChipID:8040,EMP protocol:0301

OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35744600583447 CERT:RED
LDR:051207 0928 NPACXC1250165_1_SEMC_COMPACTFLASHLOADER R2B
Flash ID check:890D
Flash props sent ok

DETACH CABLE FROM PHONE.
REMOVE BATTERY FROM PHONE, THEN INSERT IT BACK
THEN PRESS "READY"


OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

Trying to launch embedded bootloader...
INT LDR:COMPACT_ID_LOADER_CRIPPLED_SETOOL2_R2
Flash ID check:890D
Flash props sent ok
FOUND: R7CA017_CXC1123106_NAM_1_EE
Restore from:R7CA017_CXC1123106_NAM_1_EE
writing D:\W600_R7CA017_FS_AMERICA_1_RED49\W600_R7CA017_FS _AMERICA_1_RED49.fbn
CURRENT FLASH FILE CID:49
SSW uses dynamic hash, dynamic hash len is:261
Will flash 261 blocks...
verify block error
last blk:50010000,00010000
Elapsed:156 secs.

[philzfog]

u wont be able to fix it by flashing if u have wrote the wong gdfs to it :(

[Gigman]

How can I tell if its the wrong GDFS?

[philzfog]

u said that u had wrote a dif gdfs to it ? try to get a full read out from se tool and se if it say imei missmatch

[Gigman]

Ok I did a GDFS read and a Flash read

Log Results:


PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35744600583447 CERT:RED
LDR:051207 0928 NPACXC1250165_1_SEMC_COMPACTFLASHLOADER R2B
Flash ID check:890D
Flash props sent ok

DETACH CABLE FROM PHONE.
REMOVE BATTERY FROM PHONE, THEN INSERT IT BACK
THEN PRESS "READY"


OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

Trying to launch embedded bootloader...
INT LDR:COMPACT_ID_LOADER_CRIPPLED_SETOOL2_R2
Flash ID check:890D
Flash props sent ok
FOUND: R7CA017_CXC1123106_NAM_1_EE
Restore from:R7CA017_CXC1123106_NAM_1_EE
CSloader version:
SETOOL2 LITE COMPACT_SEMC_FS_LOADER (FAT V26)
loader startup: executed
loader GDFS startup: executed
stated number of vars:1250
Found:1039 variables
Found:177 variables
Found:34 variables
GDFS read all done, GDFS_35744600583447.BIN written
Phone detached
Elapsed:135 secs.
ChipID:8040,EMP protocol:0301

OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35744600583447 CERT:RED
LDR:051207 0928 NPACXC1250165_1_SEMC_COMPACTFLASHLOADER R2B
Flash ID check:890D
Flash props sent ok

DETACH CABLE FROM PHONE.
REMOVE BATTERY FROM PHONE, THEN INSERT IT BACK
THEN PRESS "READY"


OBSOLETE EROM,FORCING COLOR -> RED
OBSOLETE EROM,FORCING CID -> 49

Trying to launch embedded bootloader...
INT LDR:COMPACT_ID_LOADER_CRIPPLED_SETOOL2_R2
Flash ID check:890D
Flash props sent ok
FOUND: R7CA017_CXC1123106_NAM_1_EE
Restore from:R7CA017_CXC1123106_NAM_1_EE
Will read 00020000 bytes from 44000000
Reading:131072 bytes
Done
Phone is detached.
Elapsed:47 secs.

[Gigman]

I dont see anything saying missmatch but during FS flash it seems there is a Block error.....block error last blk:50010000,00010000. What does this mean? And I have been working a trojan issue with qmaker.exe. I dont think its affecting this, I hope. I have made an exception to ignore it in Norton AV.

[SeaMonkey]

Use jdflasher instead Setool2lite,but first post log from XS++ here