| Author |
K800 cid 52: erom can not be repaired, tried almost everything! |
J-Pro
Joined: Jun 21, 2008
Posts: 3
From: Kishinev, Moldova
PM, WWW
|
Sorry, such thread already is on few russian forums, but I've decided to post also here, on one from the biggest SE forums.
A day ago I've changed screen on my K800(it was broken because one man throwed it into the wall  ) and started to learn the features as patches, new firmwares, menu, etc.(even having some experience since modding Sony J-5, SET610, SEK750, there still was lot of new stuff I've should have learned). As result, I've changed my CID from 49 to 52, flashed the phone with R1KG001 RUS (FS and MAIN), finalized it, added some patches(and the sim unlock patch). After that the phone was working just fine: was correctly turning off/onn, correctly calling, etc. for almost 1 day.
But yesterday I've decided to change the menu layout(menu.ml). While editing the XML, my phone was lying on the table, powered on. But when I've finished - I've turned the phone off, and as a habit - removed/placed back the battery plugged on the DCU-60, holding "C" button, hoping that SETool2 will recognize the phone... which does NOT happend  Tried to power on the phone - no result, just blinking red led at IRDA(6 times).
I've started to read forums and find that it can be very dangerous to plug out the battery right after turning the phone off because possibe EROM failures. So, as I've understood - it's just my case
The first that I've done - downloaded DaVinci 18.4 + loader for it. Also downloaded K800_RED_CID52_R3B021_EROM-FOTA.bin and K800_RED_CID52_R3B021_EROM-FOTA_2006-12-18_15.bin (2 of them, just in case of its difference). Tried to flash it(using 2+5 buttons, because "C" doesn't help), got the log:Code:
| Client Version 18.4 - CID52 supported!
Hold "C" button and plug USB cable.
Phone Attached!
Detected SonyEricsson: K800/K610/Z710/K790/W850.
Status Ok, OTP Close, CID49, PAF1
IMEI: 351707-**-******
Loading Fota File. Ok!
Flash File CID:52
Phone CID:52
Flashing 4 blocks. Ok!
Execution Time - 00:00:20
Done! |
|
as usual, removed the cable, replaced the accum - phone still dead...
Then read at forums that people use also Kulankendi and Wotan. The last one is shareware now, it doesn't work without the password. But Kulankendi is as "useful", as DaVinci, but "makes" the flash for 0 seconds, which I think is very strange. Here is the log:Code:
| Press "5" and "2" keys, hold them together and plug DCU60 USB cable.
Phone Connected...
Detected: DB2020: A1 Series
Flash ID: 0x897E - Supported
EROM CID Detected: 52
Status:3
EROM Update Ok!
All Done! - Time:00:00:00 |
|
Result - phone is still dead...
Tried also and JDFlasher, but while connected, received the log:
Code:
| log started. plugin compiled Jun 9 2008 / 19:47:22
create session object
used script: db2020.xml
turn off the phone, hold "c" button and plug usb cable
found EPIUSB1
connecting...
<- 5A
got response
-> 3F
<- 99 00 03 01 FF FF FF FF
protocol: 0301 baseband: 9900
cid detect
-> 49 43 34 30
<- 63
<- 04
<- 34 00 00 00
-> 49 43 33 30
<- cid=52 color=unknown platform=db2020
error: OpenPlugin(connecttophone(getcid(cant find device info in xml [52unknown]))) |
|
although I've downloaded the plugin WITH db2020 support.
Also I've tried SETool2 recovery, but first made "Identify" and received log:Code:
| Welcome to SEtool2 ( LITE edition ) v 1.11
supported DB2010/DB2012 CID49/50/51/52, DB2020 CID49/51/52
Loaded 51 flash descriptors
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
Flash ID check:897E
Flash props sent ok
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
no ack during gdfs_readvar !
Can't read SCRC unit
Elapsed:88 secs. |
|
then pressed "Recovery buttin" and got the error in the message box: "Failed to find resource" and the log:
Code:
| RECOVERY MODE STARTED
BOOTROM MODE DETECTED
skipping empty loader...
All possible recovery loaders fail. That phone not supported
Elapsed:19 secs. |
|
Also I've tried to flash my GDFS, which I've backuped a day earlier before all experiments, but received this:Code:
| ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
only FLASH operation supported in that mode
Elapsed:9 secs. |
|
Later Darkmen advised to flash GDFS and I've tried to make it with different soft too:
SETool2 lite result (If check the "Bypass db2020 security" checkbox):Code:
| ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
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:7 secs. |
|
If NOT check the "Bypass db2020 security" checkbox:Code:
| ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
only FLASH operation supported in that mode
Elapsed:8 secs. |
|
So with SETool2 I can only flash MAIN/FS or EROM. No availability to flash GDFS
DaVinci flashes GDFS in Advanced options which is available only using their web-site(even with loader):Code:
| Client Version 18.4 - CID52 supported!
Hold "C" button and plug USB cable.
Phone Attached!
Detected SonyEricsson: K800/K610/Z710/K790/W850.
Status Ok, OTP Close, CID49, PAF1
IMEI: 351707-**-******
K800 recognized!
Adding Advanced Features!
Wait while process will be finished!
CsLoader Accepted Ok!
System Initialization. Please Wait...
Getting data from server...
Error connecting to server!
Execution Time - 00:00:35
Error connecting to server! |
|
Kulankendi was also useless, the GDFS backup can not be specified there, or I just didn't find it. What should I use more?
By the way, this phone(with broken screen) was laying on the father's bookshelf earlier. And he tells me now that led blinking, while turning it on, was visible earlier too! But once after it I've visited my father and without any problems turned the phone on and pased all the tests at service menu. SO I think... this phone was heavily throwed into the wall(that's why I've received the phone, that's why I've replaced the broken screen), so maybe the EROM chip isn't properly connected on the system board or something like that? It's just as a possible variant...
But maybe not - that's why I need your advices about how can I restore my GDFS using 2+5 keys combination...
[font=System][size=4][color=#FF0000]ADDED:[/color][/size][/font]
Just found another method, using "se sec var" soft, so tried to:
1. Flash(or just try to...) original MAIN K800_R1KG001_MAIN_GENERIC_RED52.mbn using SETool2 litw v 1.11 and 2+5.
Here is the log:Code:
| ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
CID52 BYPASS PROCEDURE STARTED
Processing part1...
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
Processing part2...
Processing part3....
BOOTROM MODE DETECTED
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
REMOVE CABLE FROM PHONE
REMOVE BATTERY FROM PHONE, THEN INSERT IT BACK
THEN PRESS "READY"
HOLD "C" BUTTON AND ATTACH PHONE
CID52 BYPASS PROCEDURE FINISHED
ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
Trying to launch embedded bootloader...
embedded flashloader not responds !
Elapsed:391 secs. |
|
BUT before it said to me "Processing part3...", SETool again asked: "Hold C and plug the cable". So I've unplugged the cable, WITHOUT replacing the battery, then plugged the cable back, holding 2+5. Process continued till words: "REMOVE CABLE FROM PHONE...". I've did everything like there was asked, then the new phrase appeared: "CID52 BYPASS PROCEDURE FINISHED" and again SETool asked: "Hold C and plug the cable" in the status bar. So I've replaced the cable without replacing the battery again. What happened next - you see above. Seems that it was useless too
But I've tried to finalize using script in SETool2. After pressing "Write Script" and plugging the cable, got the log:Code:
| ChipID:9900,EMP protocol:0301
BOOTROM MODE DETECTED
Speed:921600
OTP LOCKED:1 CID:49 PAF:1 IMEI:351707******** CERT:N/A
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
loader startup: executed
loader filesystem startup: executed
CSloader refused to start GDFS services,error is:29
loader GDFS startup failed, that is fatal
Elapsed:18 secs. |
|
So seems that even this method isn't useful
What should I do, people? As you see, I've tried almost everything what can(and can NOT) be found on SE forums. Unfortunately, nothing helped
I hope that your huge knowledge will help me. I'm sure it will help!
P.S.: After 3 weeks using Nokia, I've missed my stolen K750i, it's menu, it's whole, and was so happy when got K800... So it would be a great loss if this situation will be without any exit
P.P.S.: BIG THANKS to all helpers in advance!
_________________
-=J-Pro=- with respect
>J5(France): 5.4.2/1,fadelght2,rus,abc,OOK3b8_UFIF_ELI,VbrThenRing12,monitor
>T610: R7A011 EU2,Terminator Dongle
>K750i: R1CA021(CID49 RED) EU1,2Gb (stolen)
>K800i
[ This Message was edited by: J-Pro on 2008-06-21 23:20 ] | |
|
J-Pro
Joined: Jun 21, 2008
Posts: 3
From: Kishinev, Moldova
PM, WWW
|
The problem is solved. Seems that having such logs which I have, there is no way but to use DreamBox. So I left my phone at the service center and today it works. The guy said that he just repaired my GDFS area.
Now I'll remember "the rule of detaching the battery from a SonyEricsson phone" for all my life long!
Thanks for any tries to help me!
|
blerk
Joined: Jun 12, 2008
Posts: > 500
From: London, UK
PM |
Wow, that must be quite an experience! As someone who's about to venture the way you did I would like to know what you used to backup your phone, FS/MAIN/GDFS/EROM, etc ,etc
Thanks!
Edit: when trying to make a GDFS backup with XS++ I get this:
16:24:22| Ready for operation!
16:24:37| Sorry, your phone is NOT SUPPORTED
16:24:37| Error: Failed to send CSLoader!
16:24:37| FSX Shutdown!
[ This Message was edited by: blerk on 2008-06-24 16:26 ] |
J-Pro
Joined: Jun 21, 2008
Posts: 3
From: Kishinev, Moldova
PM, WWW
|
On 2008-06-24 17:22:18, blerk wrote:
what you used to backup your phone, FS/MAIN/GDFS/EROM, etc ,etс
Generally, I made GDFS backup, but it wasn't useful, because, AFAIK, when you use DreamBox, you don't need any backups. At least the guy in SC said that. |
strizlow800
Joined: Aug 23, 2006
Posts: > 500
From: Macedonia, Skopje
PM |
On 2008-06-24 17:22:18, blerk wrote:
Wow, that must be quite an experience! As someone who's about to venture the way you did I would like to know what you used to backup your phone, FS/MAIN/GDFS/EROM, etc ,etc
Thanks!
Edit: when trying to make a GDFS backup with XS++ I get this:
16:24:22| Ready for operation!
16:24:37| Sorry, your phone is NOT SUPPORTED
16:24:37| Error: Failed to send CSLoader!
16:24:37| FSX Shutdown!
[ This Message was edited by: blerk on 2008-06-24 16:26 ]
About your phone, I think you got "phone not supported" error in XS++ because of your phone CID... CID53 phones give that error...
|
nathan23
Joined: Jul 15, 2007
Posts: 57
PM |
i used XS++ v3.1 on my k810i phone before and it worked.. i even changed the acoustics to the original w880i acoustics.. but now when i try to connect it thru XS++ v3.1 this is what i get
13:52:30| XS++ v3.1 (Darwin) Ready !
13:52:30| Executed on Microsoft Windows XP
13:52:35|
13:52:35| Attempting to open the interface...
13:52:35|
13:52:35| TURN OFF PHONE!
13:52:35| Hold 'C' button on phone and connect phone NOW.
13:52:35| You have 30 seconds...
13:52:35|
13:52:43| Baseband ID: 9900
13:52:43| Protocol Version: 3.1
13:52:43| Phone name detected!
13:52:43|
13:52:43| Profiling SEMC phone...
13:52:43| Platform: DB2020
13:52:43| OTP CID: 51
13:52:43| EROM CID: 53
13:52:43| EROM Color: Red
13:52:43| IMEI: 35612701xxxxxx
13:52:43| Phone ID: K810
13:52:43| Region: M_EAST_N_AFR
13:52:43| CDA: CDA102568/109 R6A
13:52:43| Firmware Version: R8BA024
13:52:43| EROM: R3A022
13:52:43| Ready for operation!
13:53:07| +++ Sending CERTIFICATE LOADER...
13:53:07|
13:53:07| Sending db2020_cid01_cert_p3g.bin...
13:53:07| Payload: Failed
13:53:07| Unsupported CID!
13:53:08| GDFS operation was successful
13:53:10| Disconnected... Unplug the phone
13:53:48|
13:53:48| Attempting to open the interface...
13:53:48|
13:53:48| TURN OFF PHONE!
13:53:48| Hold 'C' button on phone and connect phone NOW.
13:53:48| You have 30 seconds...
13:53:48|
13:53:53| Baseband ID: 9900
13:53:53| Protocol Version: 3.1
13:53:53| Phone name detected!
13:53:53|
13:53:53| Profiling SEMC phone...
13:53:53| Platform: DB2020
13:53:53| OTP CID: 51
13:53:53| EROM CID: 53
13:53:53| EROM Color: Red
13:53:53| IMEI: 35612701xxxxxx
13:53:53| Phone ID: K810
13:53:53| Region: M_EAST_N_AFR
13:53:53| CDA: CDA102568/109 R6A
13:53:53| Firmware Version: R8BA024
13:53:53| EROM: R3A022
13:53:53| Ready for operation!
13:54:10| Sorry, your phone is NOT SUPPORTED
13:54:10| Error: Failed to send CSLoader!
13:54:10| FSX Shutdown!
13:54:12| Disconnected... Unplug the phone
13:54:21| Shutting down...
so if XS++ v3.1 has worked before (not jus once!!!!) why doesnt it work now??? if it doesnt work for phones that hav CID53 then how did i change my acoustics the last time?? or can it be dat the CID has changed??? its weird..
sum1 plz help... thnx in advance
|
centur
Joined: Jun 10, 2007
Posts: > 500
From: Bulgaria
PM, WWW
|
On 2008-07-26 10:42:13, nathan23 wrote:
i used XS++ v3.1 on my k810i phone before and it worked.. i even changed the acoustics to the original w880i acoustics.. but now when i try to connect it thru XS++ v3.1 this is what i get
..........................
13:52:43| EROM CID: 53
............
so if XS++ v3.1 has worked before (not jus once!!!!) why doesnt it work now??? if it doesnt work for phones that hav CID53 then how did i change my acoustics the last time?? or can it be dat the CID has changed??? its weird..
sum1 plz help... thnx in advance
Read here: http://www.esato.com/board/viewtopic.php?topic=170737&start=0
See steps 2, 9, 10 and 11 but open ifs/settings/acoustic
| |
|
Access the forum with a mobile phone via esato.mobi
|
Posted: 2008-06-22 00:13
Sony Ericsson software/hardware support! 
