Page 1 of 1
K800i Broken After Flashing Not turning on and 2+5 trick doesn't work
#1
Posted 20 December 2008 - 06:21 PM
I previously flashed my K800 using the K810 software, but wanted to go back to K800. THis turned out to be a bad choice.
The files i used to flash were:
K800_R8BF003_FS_EUROPE_2_RED52
K800_R8BF003_MAIN_GENERIC_WI_RED52
and a XS++ Customization pack (pursuant to a guide on this forum) ie choose K800 and Europe 2 in the customization section
This was done in XS++3.1 and upon completion there were no error codes. I disconnected the phone, turned it on and it said 'Please Wait'. It seemed to complete but i am not 100% sure as my eye was caught when the SE logo flashed up. When trying to turn the phone on after this i get nothing but a flashing red light. Searching on this forum i found this is a EROM problem and WotanClient or Setool2 could fix this. These are my results
Setool: It finds the phone, and even displays some information, it says 'Preparing Data' and after 10 mins (well 390seconds) the titles have no information in them. This is a copy of what is shown:
welcome to setool2 lite edition v 1.08
supported DB2010/DB2012 CID48/50/51/52, DB2020 CID49/51/52
Loaded 51 flash descriptors
ChipID:9900,EMP protocol:0301
RECOVERY BOOTROM MODE DETECTED
SPEED:921600
Flash ID check:2019
Flash props sent ok
OTP LOCKED: 1 CID:49 PAF:1 IMEI:XXXXXXXXXXXXXXXXXXXXXXXXXXXX CERT: RED
FLASH CID:52 COLOR:RED
MAPP CXC article:
MAPP CXC version:
Language Package:
CDA article:
CDA version
Default article:
Default version:
Operator: 000-00
Elapsed:391 secs
(the latter 9 lines being created in the 10 mins)
WotanClient:
(after downloading and clearing username and password: pressing 2+5=)
Connect your phone, pressing 'C' (i'm pressing 2+5)
waiting.....
phone found.
DB2020 detected
LOADER: OK
FC ID: 20 19
Define login and password!
==FAILED==
Duration:00:00
(NB nothing happens if i press C while connecting)
XS++ 3.1
This is what happens if i press 2+5 (i know this program apparently does not help here but just for info:)
18:15:33| XS++ v3.1 (Darwin) Ready !
18:15:33| Executed on Microsoft Windows XP
18:15:40|
18:15:40| Attempting to open the interface...
18:15:40|
18:15:40| TURN OFF PHONE!
18:15:40| Hold 'C' button on phone and connect phone NOW.
18:15:40| You have 30 seconds...
18:15:40|
18:15:46| Baseband ID: 9900
18:15:46| Protocol Version: 3.1
This is for pressing C
01:09:06| XS++ v3.1 (Darwin) Ready !
01:09:06| Executed on Microsoft Windows XP
01:09:15|
01:09:15| Attempting to open the interface...
01:09:15|
01:09:15| Turn off phone
01:09:15| Hold 'C' button on phone and connect phone.
01:09:15| You have 30 seconds.
01:09:15|
01:09:23| Did not receive 0x5a. Continuing
01:11:45| Disconnected... Unplug the phone
Please help, i don't want to lose this phone
The files i used to flash were:
K800_R8BF003_FS_EUROPE_2_RED52
K800_R8BF003_MAIN_GENERIC_WI_RED52
and a XS++ Customization pack (pursuant to a guide on this forum) ie choose K800 and Europe 2 in the customization section
This was done in XS++3.1 and upon completion there were no error codes. I disconnected the phone, turned it on and it said 'Please Wait'. It seemed to complete but i am not 100% sure as my eye was caught when the SE logo flashed up. When trying to turn the phone on after this i get nothing but a flashing red light. Searching on this forum i found this is a EROM problem and WotanClient or Setool2 could fix this. These are my results
Setool: It finds the phone, and even displays some information, it says 'Preparing Data' and after 10 mins (well 390seconds) the titles have no information in them. This is a copy of what is shown:
welcome to setool2 lite edition v 1.08
supported DB2010/DB2012 CID48/50/51/52, DB2020 CID49/51/52
Loaded 51 flash descriptors
ChipID:9900,EMP protocol:0301
RECOVERY BOOTROM MODE DETECTED
SPEED:921600
Flash ID check:2019
Flash props sent ok
OTP LOCKED: 1 CID:49 PAF:1 IMEI:XXXXXXXXXXXXXXXXXXXXXXXXXXXX CERT: RED
FLASH CID:52 COLOR:RED
MAPP CXC article:
MAPP CXC version:
Language Package:
CDA article:
CDA version
Default article:
Default version:
Operator: 000-00
Elapsed:391 secs
(the latter 9 lines being created in the 10 mins)
WotanClient:
(after downloading and clearing username and password: pressing 2+5=)
Connect your phone, pressing 'C' (i'm pressing 2+5)
waiting.....
phone found.
DB2020 detected
LOADER: OK
FC ID: 20 19
Define login and password!
==FAILED==
Duration:00:00
(NB nothing happens if i press C while connecting)
XS++ 3.1
This is what happens if i press 2+5 (i know this program apparently does not help here but just for info:)
18:15:33| XS++ v3.1 (Darwin) Ready !
18:15:33| Executed on Microsoft Windows XP
18:15:40|
18:15:40| Attempting to open the interface...
18:15:40|
18:15:40| TURN OFF PHONE!
18:15:40| Hold 'C' button on phone and connect phone NOW.
18:15:40| You have 30 seconds...
18:15:40|
18:15:46| Baseband ID: 9900
18:15:46| Protocol Version: 3.1
This is for pressing C
01:09:06| XS++ v3.1 (Darwin) Ready !
01:09:06| Executed on Microsoft Windows XP
01:09:15|
01:09:15| Attempting to open the interface...
01:09:15|
01:09:15| Turn off phone
01:09:15| Hold 'C' button on phone and connect phone.
01:09:15| You have 30 seconds.
01:09:15|
01:09:23| Did not receive 0x5a. Continuing
01:11:45| Disconnected... Unplug the phone
Please help, i don't want to lose this phone
#3
Posted 23 December 2008 - 09:52 AM
Have you tried the "Repair" function in SETool2lt (Connecting using 2 + 5) ??
For helpful posts please use this...
...Thanks! ;)
...Thanks! ;) Keeping K series modding alive: Amir_82111, mc_kibel & Pro - Respect! ;)
#4
Posted 23 December 2008 - 12:21 PM
You'll have to repair the EROM, take a look at this
ACEEL Elfpack Repository | CPP | Advertise Your Link Here (1$)
It's been long, but I'm back on my moddin' BS.
It's been long, but I'm back on my moddin' BS.
#5
Posted 24 December 2008 - 05:11 PM
Thanks for replying.
Unfortunately i am unable to connect to program using the C button, and as you can see from the above copies i get very limited results from using 2+5.
The biggest problem is that no programs recognise the phone when pressing C, this is not a driver issue as i have tried on other computers.
After reading through the link you posted, i see there is a SeTool Lite 1.11, which i have upgraded to and this is the new result for pressing 2+5 (again pressing C does nothing)
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
Flash ID check:2019
Flash props sent ok
OTP LOCKED:1 CID:49 PAF:1 IMEI:xxxxxxxxxxxxxxxx CERT:N/A
FLASH CID:52 COLOR:RED
no ack during gdfs_readvar !
Can't read SCRC unit
Elapsed:84 secs.
I think the key section here may be the lines:
no ack during gdfs_readvar !
Can't read SCRC unit
Searching google came up with this: http://forum.gsmhost...p/t-544454.html , where someone mentions empty fill procedure. Any ideas if this is a valid option?
BTW i have backed up my GDFS so once i can get a program to recognise the phone when pressing C i can reload teh GDFS and reflash, but this is not an option as pressing C does not work, and as shown in my first post (and the paste from Setool 1.11 in this reply) pressing 2+5 at the moment is not working
Thanks for your advice so far
Unfortunately i am unable to connect to program using the C button, and as you can see from the above copies i get very limited results from using 2+5.
The biggest problem is that no programs recognise the phone when pressing C, this is not a driver issue as i have tried on other computers.
After reading through the link you posted, i see there is a SeTool Lite 1.11, which i have upgraded to and this is the new result for pressing 2+5 (again pressing C does nothing)
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
Flash ID check:2019
Flash props sent ok
OTP LOCKED:1 CID:49 PAF:1 IMEI:xxxxxxxxxxxxxxxx CERT:N/A
FLASH CID:52 COLOR:RED
no ack during gdfs_readvar !
Can't read SCRC unit
Elapsed:84 secs.
I think the key section here may be the lines:
no ack during gdfs_readvar !
Can't read SCRC unit
Searching google came up with this: http://forum.gsmhost...p/t-544454.html , where someone mentions empty fill procedure. Any ideas if this is a valid option?
BTW i have backed up my GDFS so once i can get a program to recognise the phone when pressing C i can reload teh GDFS and reflash, but this is not an option as pressing C does not work, and as shown in my first post (and the paste from Setool 1.11 in this reply) pressing 2+5 at the moment is not working
Thanks for your advice so far
#7
Posted 27 December 2008 - 09:39 AM
@Speed
It appears he did.
@Tom
Purchase a service cable and attempt to flash a new MAIN & FS, if the SCRC unit is really corrupted then you'll have to execute an empty fill. (Un)fortunately, I've never attempted to do one because there has never been need for me to do one, but the basic procedure involves writing new SSW-type generic templates for GDFS and EROM or something similar.
I suggest you search Google, preferably for Russian results included, most likely you might find a guide and the files required for your phone. I wish you all the best, and may the Force be with you.
It appears he did.
@Tom
Purchase a service cable and attempt to flash a new MAIN & FS, if the SCRC unit is really corrupted then you'll have to execute an empty fill. (Un)fortunately, I've never attempted to do one because there has never been need for me to do one, but the basic procedure involves writing new SSW-type generic templates for GDFS and EROM or something similar.
I suggest you search Google, preferably for Russian results included, most likely you might find a guide and the files required for your phone. I wish you all the best, and may the Force be with you.
ACEEL Elfpack Repository | CPP | Advertise Your Link Here (1$)
It's been long, but I'm back on my moddin' BS.
It's been long, but I'm back on my moddin' BS.
SE-NSE
#9
Posted 30 December 2008 - 06:25 PM
@wizaj - Thanks for the information. is this empty fill only possible with a service cable? Just if the cable costs a bit it might jsut be better to get a new phone ( a new k800 is about £60 in the UK) anyway. If i do get a service cable does it allow the computer to see the phone even though, at the moment, the phone can't using the 'c' method to connect to xs etc.
@Speeddevil - no worries, this is a newbie forum so to think i might have missed something is understandable. Its just a shame that the standard options don't appear to work in my case. So unfortunately the only update i can give you now is that i still have a bricked k800, a s700i with a cracked screen and no battery cover (legendary phone), and a k610 with a battery that doesn't last a day.
Thanks for all your help and responses everyone
Happy new yaer
@Speeddevil - no worries, this is a newbie forum so to think i might have missed something is understandable. Its just a shame that the standard options don't appear to work in my case. So unfortunately the only update i can give you now is that i still have a bricked k800, a s700i with a cracked screen and no battery cover (legendary phone), and a k610 with a battery that doesn't last a day.
Thanks for all your help and responses everyone
Happy new yaer
This post has been edited by tomstevens08: 30 December 2008 - 06:27 PM
Page 1 of 1

Sign In
Register
Help
Bookmark
Del.icio.us
Digg
Email
Facebook
Google
Mixx
Reddit
StumbleUpon

MultiQuote

