K800i flashing problem :(
Kinda old Phone! Hope somebody still knows...
Well I turned off my phone..changed SIM-Card and when trying to turn it On there are some red light on de IrDA.
Googled...smth with EROM.
Downloaded & executed SETool2 (lite) coneccted phone pressing "5+2", pressed "bkacup/repair" and it worked again!! :D
Then I said...hmmm ok i will flash a new FW on it.
I flashed:
a) K800 R8BF003 FS CENT EUROPE RED52
b) K800_R8BF003_MAIN_GENERIC_WI_RED52
Then it wont turn on anymore :(
Did a backup of the GDFS.
Log flashing CID52
Code:
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:2019
Flash props sent ok
writing C:\Users\okorn\Desktop\K800_R1JG001_FS_HONG_KONG_RED52\K800_R1JG001_FS_HONG_KONG_RED52.fbn
CURRENT FLASH FILE CID:52
SSW uses complete hash, hash len is:4580
Will flash 229 blocks...
SSW loading returns:0
writing C:\Users\okorn\Desktop\K800_R1JG001_MAIN_HONG_KONG_WI_RED52\K800_R1JG001_MAIN_HONG_KONG_WI_RED52.mbn
CURRENT FLASH FILE CID:52
SSW uses complete hash, hash len is:9200
Will flash 460 blocks...
SSW loading returns:0
Elapsed:364 secs.
file can't be found or opened
Elapsed:0 secs.
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:2019
Flash props sent ok
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
loader startup: executed
CSloader refused to start GDFS services,error is:29
failed, that is fatal
Trying to flash GDFS...
Code:
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:2019
Flash props sent ok
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
loader startup: executed
CSloader refused to start GDFS services,error is:29
failed, that is fatal
Elapsed:11 secs.
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
Flash ID check:2019
Flash props sent ok
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
set_gdfs_props failed, exiting
Abort all operations.
Elapsed:30 secs.
Did i to wrong flashing a CID52?
I have no idea...
I dont know what this means:
Quote:
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
Did the other owner...update CID49 to CID52???
What should i do?
Flashed with CID49...
Code:
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:2019
Flash props sent ok
writing C:\Users\okorn\Desktop\CIDdd\cb\K800_R1CB001_FS_HONG_KONG_RED49.fbn
CURRENT FLASH FILE CID:49
SSW uses complete hash, hash len is:4420
HDR block not accepted,error:19
Elapsed:11 secs.
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:35170801164908 CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:2019
Flash props sent ok
writing C:\Users\okorn\Desktop\CIDdd\cb\K800_R1CB001_FS_HONG_KONG_RED49.fbn
CURRENT FLASH FILE CID:49
SSW uses complete hash, hash len is:4420
HDR block not accepted,error:19.
:(
Any ideas?
Thanxsss :D
Re: K800i flashing problem :(
This error CSloader refused to start GDFS services,error is:29 = go to service centre!
Re: K800i flashing problem :(
Sure? :(
Im in Argentina...kinda expensive :S
Re: K800i flashing problem :(
Quote:
Originally Posted by
okorn
Sure? :(
Im in Argentina...kinda expensive :S
No other way.
Re: K800i flashing problem :(
Re: K800i flashing problem :(
set_gdfs_props failed, exiting
Try flashing main without Identify. Connect holding 2+5
Use CID52 files.
If it doesn't work, then it's damaged GDFS, you can only repair with box.
Re: K800i flashing problem :(
Well flashed with CID52
only main!!
Code:
Welcome to SEtool2 ( LITE edition ) v 1.11
supported DB2010/DB2012 CID49/50/51/52, DB2020 CID49/51/52
Loaded 51 flash descriptors
if you like LITE edition - please visit www.setool.net and buy FULL.
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:RT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:2019
Flash props sent ok
writing C:\Users\okorn\Desktop\K800_R1JG001_MAIN_HONG_KONG_WI_RED52\K800_R1JG001_MAIN_HONG_KONG_WI_RED52.mbn
CURRENT FLASH FILE CID:52
SSW uses complete hash, hash len is:9200
Will flash 460 blocks...
SSW loading returns:0
Elapsed:239 secs.
But...GDFS still wrong :S
Re: K800i flashing problem :(
Hi just joined -- don't know how to create new post yet, any help would be appreciated.
Problem: Sony K800i will not power up correctly, bright white light come on for 4-5 secs then goes out then, continuues to flash at this 4-5 sec cycle.
I power down, remove the battery, remove and clean SIM card, reassemble and hold on/off sw for a longish time
Same result for three different batterys.
Can anyone point me in the right direction to fix this problem,
Thanx in advance
cfm
Re: K800i flashing problem :(
@cfmiT connect to XS++ and post log here.
Re: K800i flashing problem? WSOD!
Hi there! I'm a massive UK based n00b at this and need some guidance please! Trying to make sense of varying advice from many websites has landed me here after recommendation.
I have k800i with white screen of death. initially had red light blinking, updated on SEUS then attempted to start a fix with XS++ v3.1, I accepted the CID update from 49 to 52 (thinking it would help!) which left it as a hopeless brick: XS++ wouldnt connect again.
So I updated the EROM automatically with Kunlankendi client from r3a011 to r3a016 now I'm back with WSOD, but not as much red light.
- Tried setool2lite and it connects so reset the user lock in case. Now connecting pretty ok (sometimes difficult - driver issue? (I thought SEUS would have loaded those)) with XS++ also, and have backed up my GDFS with it in case of further complications (although whether that's a full back up in my mob's current state I'm unsure).
my latest XS++ log:
TURN OFF PHONE!
16:55:36| Hold 'C' button on phone and connect phone NOW.
16:55:36| You have 30 seconds...
16:55:36|
16:55:42| Baseband ID: 9900
16:55:42| Protocol Version: 3.1
16:55:43| Phone name detected!
16:55:43|
16:55:43| Profiling SEMC phone...
16:55:43| Platform: DB2020
16:55:43| OTP CID: 49
16:55:43| EROM CID: 52
16:55:43| EROM Color: Red
16:55:43| IMEI: 35170801xxxxxx
16:55:43| Phone ID: K800
16:55:43| Region: EUROPE_2
16:55:43| CDA: CDA102511/41 R10A
16:55:43| Firmware Version: R1CB001
16:55:43| EROM: R3A016
16:55:43| Ready for operation!
16:56:07|
16:56:07| Sending db2020_cid01_prodid_p3j.bin...
16:56:08| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J
16:56:08| This is a PRODUCTION_ID loader
16:56:08|
16:56:08| Sending db2020_mem_patcher_cid52_r2a006.bin...
16:56:08| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0
16:56:08| This is a MEM_PATCHER loader
16:56:08|
16:56:08| Sending db2020_red52_cs_r3a009.bin...
16:56:10| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
16:56:10| This is a CHIPSELECT loader
16:56:10| Activating loader...
16:56:10| Activating GDFS...
16:56:24| This loader is UNLOCKED
16:56:24| Backing up the GDFS...
16:56:26| Stated variables: 1678
16:56:28| Variables found: 526
16:56:31| Variables found: 723
16:56:32| Variables found: 235
16:56:33| Variables found: 194
16:56:33| Wrote backup to .\Backup\K800_35170801xxxxxx_GDFS_BACKUP.bin
16:56:33| GDFS was backed up successfully!
16:56:33| GDFS operation was successful
16:56:35| Disconnected... Unplug the phone
16:57:12|
16:57:12| Attempting to open the interface...
16:57:12|
16:57:12| TURN OFF PHONE!
16:57:12| Hold 'C' button on phone and connect phone NOW.
16:57:12| You have 30 seconds...
16:57:12|
16:57:19| Did not receive 0x5a. Continuing
16:57:33| Disconnected... Unplug the phone
16:57:52|
16:57:52| Attempting to open the interface...
16:57:52|
16:57:52| TURN OFF PHONE!
16:57:52| Hold 'C' button on phone and connect phone NOW.
16:57:52| You have 30 seconds...
16:57:52|
16:57:56| Baseband ID: 9900
16:57:56| Protocol Version: 3.1
16:57:56| Phone name detected!
16:57:56|
16:57:56| Profiling SEMC phone...
16:57:56| Platform: DB2020
16:57:56| OTP CID: 49
16:57:56| EROM CID: 52
16:57:56| EROM Color: Red
16:57:56| IMEI: 35170801xxxxxx
16:57:56| Phone ID: K800
16:57:56| Region: EUROPE_2
16:57:56| CDA: CDA102511/41 R10A
16:57:56| Firmware Version: R1CB001
16:57:56| EROM: R3A016
16:57:56| Ready for operation!
16:58:18|
16:58:18| Sending db2020_cid01_prodid_p3j.bin...
16:58:18| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J
16:58:18| This is a PRODUCTION_ID loader
16:58:18|
16:58:18| Sending db2020_mem_patcher_cid52_r2a006.bin...
16:58:19| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0
16:58:19| This is a MEM_PATCHER loader
16:58:19|
16:58:19| Sending db2020_red52_cs_r3a009.bin...
16:58:20| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
16:58:20| This is a CHIPSELECT loader
16:58:20| Activating loader...
16:58:20| Activating GDFS...
16:58:35| This loader is UNLOCKED
16:58:35| Resetting Lock Code...
16:58:35| Lock Code...Reset to '0000'!
16:58:35| Terminating GDFS Access...
16:58:35| GDFS operation was successful
16:58:37| Disconnected... Unplug the phone
17:38:26| Shutting down...
17:42:37| XS++ v3.1 (Darwin) Ready !
17:42:37| Executed on Microsoft Windows XP
Please advise what next to get it working!
I presume it'll be flashing on XS++ but I'm not even sure if I have a combination of firmware, erom and cid that are compatible??!!!
I'll likely be able to follow a tutorial if I do get the right files. I'm in UK and currently show euro2 region. Also I've read elsewhere that my old EROM was the culprit for this WSOD, but I'd also prefer to update my firmware if it'll help stop WSOD in future
many thanks!
