View Full Version : DEAD W810i by SEtool!!!
Speedymobile
10-07-2006, 13:33
Guys, I have here 1x SE W810i killed by Setool3....
All I done was read GDFS and when it said "remove battery, re-insert and press Test Point OK".. It died.. now phone is dead and won't turn on.
Doesn't seem to be recognise by SETool at all as when it says to press power on button briefly, it doesnt recognise it as phone is dead :o
Phone was working fine before I use this tool.... Any way to repair it? :rolleyes:
Speedy
blaiseid
10-07-2006, 13:55
I fix W810 almost everyday with setool3_ufs, I ve done more than 500 W810s, Not even a single problem both unlocking and flashing.
Another, point, all setool users know where to post their problem.
Speedymobile
10-07-2006, 14:02
I fix W810 almost everyday with setool3_ufs, I ve done more than 500 W810s, Not even a single problem both unlocking and flashing.
Another, point, all setool users know where to post their problem.
Please explain how to fix it then using SEtool box, MT S.E, or Cruiser ;)
I don't have UFS
BTW... SEtool forum is slow with responding which is why I am here :rolleyes:
Speedy
mike_hodgson
10-08-2006, 01:06
have u downloaded the rest pack and extracted it into your setool rest folder.
07heaven
10-08-2006, 02:14
If you press the Identify in SETOOL does anything happen?
Does the phone attach with Cruiser?
Rest Files are for Unlocking purposes
mike_hodgson
10-08-2006, 09:24
i thought they were for restoring the colour of the phone.sorry.i used usb smart to repair my w810 after se tool did the same to my phone
Guys, I have here 1x SE W810i killed by Setool3....
All I done was read GDFS and when it said "remove battery, re-insert and press Test Point OK".. It died.. now phone is dead and won't turn on.
Doesn't seem to be recognise by SETool at all as when it says to press power on button briefly, it doesnt recognise it as phone is dead :o
Phone was working fine before I use this tool.... Any way to repair it? :rolleyes:
Speedy
If you want to find the quick answer for your problem, maybe try in other place.....maybe in setool support forum!!!
Speedymobile
10-08-2006, 20:35
have u downloaded the rest pack and extracted it into your setool rest folder.
Yes, not that that makes any difference im afraid
If you press the Identify in SETOOL does anything happen?
Does the phone attach with Cruiser?
Rest Files are for Unlocking purposes
Identity button does brings up phone description yes, thats all though :( ..here's the log it reads:
GUI v0.91380042/UNI
Card serial:0000xxxx
Loaded 51 flash descriptors
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
Flash ID check:897E
Flash props sent ok
FLASH CID:49 COLOR:RED
OTP LOCKED:1 CID:49 PAF:1 IMEI:3590630058xxxx CERT:RED
Elapsed:10 secs.
... phone won't power on to let soft recognise the phone to flash the files though
Not yet tried with cruiser.. will maybe have to try if no solution with SETool by tomorrow
i thought they were for restoring the colour of the phone.sorry.i used usb smart to repair my w810 after se tool did the same to my phone
Will also try with Zulea usb smart... never know :D :D
If you want to find the quick answer for your problem, maybe try in other place.....maybe in setool support forum!!!
If I wanted to find a quick answer i'd buy another phone.
SETool forum is crap.. wait forever for replies, then get the most stupid answers you can get. After explaining to them in full detail what is the problem, they then reply asking "Have you done this?" "Have you done that?" when it's quite clearly stated in my FIRST post.
Now then.. maybe YOU should try reading the WHOLE of this thread, then consider posting elsewhere your stupid post! :mad:
Thanks guys,
Speedy
Where is the full log? which SETool version are you using?
Pd. you never posted at SETool support forum, how do you know is slow?
Speedymobile
10-08-2006, 21:37
Where is the full log? which SETool version are you using?
Pd. you never posted at SETool support forum, how do you know is slow?
Using latest version. see my log please ;)
And yes.. have posted at setool support forum some time ago... but lack of response brings me here to resolve my troubles.
Here is full log, including what I have done to try and get phone working again..
Grab a cup of coffee, sit back, relax, and read away "The adventures of trying to recover this w810i" :D :
When press "get identity":
GUI v0.91380042/UNI
Card serial:0000xxxx
Loaded 51 flash descriptors
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
Flash ID check:897E
Flash props sent ok
FLASH CID:49 COLOR:RED
OTP LOCKED:1 CID:49 PAF:1 IMEI:35906300585837 CERT:RED
Elapsed:10 secs.
When press flash:
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:115200
FLID fail
Elapsed:5 secs.
Then another try....
GET Identity:
GUI v0.91380042/UNI
Card serial:0000xxxx
Loaded 51 flash descriptors
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:115200
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Can't load id loader !
Elapsed:13 secs.
after pressing "recovery":
RECOVERY MODE STARTED
Open COM port OK
Abort all operations.
Elapsed:99 secs.
(Didn't work, so pressed stop)
Pressed "IDENTITY":
GUI v0.91380042/UNI
Card serial:0000xxxx
Loaded 51 flash descriptors
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:115200
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Can't load id loader !
Elapsed:11 secs.
AFTER PRESS "RECOVERY":
RECOVERY MODE STARTED
Open COM port OK
Open COM port OK
llbug: trashed answer.
All possible recovery loaders fail. That phone not supported
Elapsed:100 secs.
...
Now I add these two files to flash:
r4ck003_generic_main.ssw.cry
W810_r4ck003_eu1_fs.cry
Press "FLASH", And this happen:
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:230400
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:13 secs.
Flash:
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:230400
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:16 secs.
Flash:
Open COM port OK
Abort all operations.
Elapsed:66 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
prologue block NAK
Elapsed:12 secs.
Flash with "complete phone" checked in settings menu:
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
llbug: trashed answer.
ldr_on_ldr payload error
Elapsed:69 secs.
Now see this after finally getting "recovery" to work (I had complete phone, unlock after flash, patch OTP, and allow to change IMEI when unlocking all checked (IMEI Needs changing):
GUI v0.91380042/UNI
Card serial:0000xxxx
Loaded 51 flash descriptors
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:115200
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Can't load id loader !
Elapsed:11 secs.
RECOVERY MODE STARTED
Open COM port OK
Open COM port OK
llbug: trashed answer.
All possible recovery loaders fail. That phone not supported
Elapsed:100 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:230400
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:13 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:230400
loader payload not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:16 secs.
Open COM port OK
Abort all operations.
Elapsed:66 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
prologue block NAK
Elapsed:12 secs.
Open COM port OK
Abort all operations.
Elapsed:45 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
llbug: trashed answer.
ldr_on_ldr payload error
Elapsed:69 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
prologue block NAK
Elapsed:14 secs.
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:50 secs.
RECOVERY MODE STARTED
Open COM port OK
loader prologue returns invalid status
Open COM port OK
Recovery:060330 1434 NPA4_CXC1326739_DB2010_SEMC_RECOVERY_R2A
Fetching phone data from OTP
OTP LOCKED:1 CID:49 PAF:1 IMEI:35906300585837 CERT:RED
THAT WILL KILL YOUR PHONE, ABORTED
Elapsed:69 secs.
Now with only "complete phone" and "unlock after flash" checked, i click "flash":
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
Loader:060718 0842 LIE_DB2010_FLASHLOADER_R2A003_CXC1326738
OTP LOCKED:1 CID:49 PAF:1 IMEI:35906300585837 CERT:RED
llbug: trashed answer.
fout_ssw hdr no ack
prepare failed,that is FATAL
Elapsed:78 secs.
Any Ideas? :rolleyes:
07heaven
10-09-2006, 01:59
U tried do anything with Cruiser?
Recovery can't be applied to CID49 phones (only exception is Z530), by doing so your phone could be killed in the process.
Iam not sure about your cable, looks to me that you aren't getting a stable connection, when you get sure about your cable try to flash main->fs->gdfs_in_ssw_format->unlock->complete
This info is already posted at official support forum from a very long time
Speedymobile
10-09-2006, 10:52
U tried do anything with Cruiser?
Not yet.. but shall try today with Cruiser, USB Smart or MT S.e... surely one box can repair this phone :rolleyes:
Recovery can't be applied to CID49 phones (only exception is Z530), by doing so your phone could be killed in the process.
Iam not sure about your cable, looks to me that you aren't getting a stable connection, when you get sure about your cable try to flash main->fs->gdfs_in_ssw_format->unlock->complete
This info is already posted at official support forum from a very long time
Connection is fine as Ive tried with 4 different cables now.
I am using box version SETool with RJ45 Cable.. have also tried with Cruiser cable but no joy.
I have no troubles flashing other phones with this box, only this W810i
Try with different cable and not with UFS.
Speedymobile
10-09-2006, 10:57
Have done so already.. Tried all different cables.
Managed to get phone to connect now as you can see by the logs.. but its just not doing something right :rolleyes:
USB Smart flash it easy..... :)
Speedymobile
10-09-2006, 11:34
USB Smart flash it easy..... :)
From dead phone?
BR,
Speedymobile
mike_hodgson
10-09-2006, 14:20
i'd reflash it with usb smart and complete the phone then unlock it with se tool,thats how i got mine working,basically its more or less same the same repair technique as the k750i/w800,repair crc and sp lock then unlock.
i hope this works for you.
ViperGSM
10-09-2006, 14:25
Flash w810_erom_red49.cry,without anything checked,than flash r4db005_CXC1250316_GENERIC_HN.ssw.cry,and r4db005_s_e_europe_fs.ssw.cry with complete and unlock after flash checked
Speedymobile
10-09-2006, 15:24
"unlock/ flash":
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
loader header not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:13 secs.
"Flash":
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
loader header not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:14 secs.
(Complete phone marked in settings)
was trying to flash these files:
R4EA031_1250320_VODAFONE_HN.ssw.cry
R4ED001_EUROPE_2_fs.ssw.cry
___________________________________
When press "Recovery", I get this:
RECOVERY MODE STARTED
Open COM port OK
loader header not accepted
Open COM port OK
loader header not accepted
All possible recovery loaders fail. That phone not supported
Elapsed:102 secs.
ViperGSM Flash w810_erom_red49.cry,without anything checked,than flash r4db005_CXC1250316_GENERIC_HN.ssw.cry,and r4db005_s_e_europe_fs.ssw.cry with complete and unlock after flash checked
Will try this now mate ;)
mike_hodgson i'd reflash it with usb smart and complete the phone then unlock it with se tool,thats how i got mine working,basically its more or less same the same repair technique as the k750i/w800,repair crc and sp lock then unlock.
i hope this works for you.
Will also try this if no joy in other method ;)
===================
Have tried Cruiser, but no luck there either..
Speedy
mike_hodgson
10-09-2006, 15:37
if you have no luck ill buy it off you.lol
Speedymobile
10-09-2006, 15:40
Flash w810_erom_red49.cry,without anything checked,than flash r4db005_CXC1250316_GENERIC_HN.ssw.cry,and r4db005_s_e_europe_fs.ssw.cry with complete and unlock after flash checked
Where you get this file "w810_erom_red49.cry" from?... Not on SETool support site :confused:
If you have... please upload.. thanks ;)
EDIT: Thanks to Mick Hogdson, I now have this file.. Cheers mate ;)
@ ViperGSM- I tried what you said, but after trying to flash that w810_erom_red49.cry file, I got this error:
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
loader header not accepted
failed to load CERTLOADERS,try to use RECOVERY.
Elapsed:14 secs.
Any idea's?
May be change speed to 460800?
Speedymobile
10-09-2006, 17:19
After try to flash with USB Smart, I get this:
Switch phone ON
Get phone info
Flash CID: 49
Phone KEY: A1_DB2010_49_RED
ERROR: 305013
Or sometimes these error codes:
305010 / 305011
Speedymobile
10-09-2006, 17:20
May be change speed to 460800?
tried this also.... thanks anyway
GUI v0.91380042/UNI
Card serial:0000xxxx
Loaded 51 flash descriptors
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:921600
Flash ID check:897E
Flash props sent ok
FLASH CID:49 COLOR:RED
OTP LOCKED:1 CID:49 PAF:1 IMEI:35906300585837 CERT:RED
Elapsed:10 secs.
When press flash:
Open COM port OK
ChipID:8040,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:49
Speed:115200
FLID fail
Elapsed:5 secs.
Hardware problem, flash chip is faulty.
And again ...
Recovery can't be applied to CID49 phones (only exception is Z530), by doing so your phone could be killed in the process.
Speedymobile
10-09-2006, 18:04
Hardware problem, flash chip is faulty.
OK Thanks..
Never knew it was possible to damage hardware with SETool... learn something new everyday ;)
Anyone have this part in stock? (Flash chip for S.E W810i)... If so.. Please PM with a price as I MUST fix this phone :o
And again ...
Recovery can't be applied to CID49 phones (only exception is Z530), by doing so your phone could be killed in the process.
So you said :rolleyes:
Cheers,
Speedy
Hardware can't be damaged with SETool ... ... try to reflaw the chip, a little heat could improved the contact with the PCB.
Hi,
Try this one last time before doing the hardware thing,
1. Use a fully charged battery when flashing.
2. Check the phone contact-terminal carefully for stubborn dirt / oxide.
hope this help.
regards
beega
reflash it .... try other version
Speedymobile
10-10-2006, 14:04
Hardware can't be damaged with SETool ... ... try to reflaw the chip, a little heat could improved the contact with the PCB.
Do you have image/ diagram to show me exactly what chip you are referring to?
Cheers
Hi,
Try this one last time before doing the hardware thing,
1. Use a fully charged battery when flashing.
2. Check the phone contact-terminal carefully for stubborn dirt / oxide.
hope this help.
regards
beega
Tried this this morning mate.... made no difference :(
Was brand new, working phone before I use SETool with it :rolleyes:
reflash it .... try other version
Tried this also... no joy
WBR,
Speedy
setool is working file with W810
I have tried few pieces
Speedymobile
10-10-2006, 14:09
setool is working file with W810
I have tried few pieces
Yes, but with this one.. no joy... it's dead phone now :(
Speedy
ViperGSM
10-10-2006, 22:54
Do you have image/ diagram to show me exactly what chip you are referring to?
Cheers
Tried this this morning mate.... made no difference :(
Was brand new, working phone before I use SETool with it :rolleyes:
Tried this also... no joy
WBR,
Speedy
I am sure its not hardware fault,if it is phone would refuse to accept loaders...you are doing something wrong...
You should also try to flash it with UFS as interface...
About Flash IC location,its directly under CPU but as far as i know its always glued,so reflowing it is not a solution:(
kingmobilephone
10-10-2006, 23:07
I guess it's becuase the erom is damaged (due to a bad flashing ?)...with damaged cid49, u can only flash it back via testpoint ...once the erom is flashed - reflash and the phone should alive..
anyway, quote by laser "tp is your friend now" ...
reaz.com
10-10-2006, 23:22
Try to Flash usb-smart
usb-smart good for Sony-Ericsson
unfortunately, there isnt any testpoint for the W810
Speedymobile
10-11-2006, 00:15
W810i for spares it is then :mad:
Wife's gonna kill me :eek: .. Was her new phone
Cheers guys,
@ luzer
Do you mean that there is really no TP on this model or TP is not yet found??
Could you pls give us other SE phone models that has no TP also (or no tp
yet)... tnx
There is not known TP for this phone ... actually this is the problematic one, many people using SETool, Cruiser, MT-Box, UB, etc. have problems with this phone.
I think part of the problem could be a poor quality control from SE, the flash chip probably give problems due to the flashing process, during this process the chip get hot lost contact with the surface of the PCB and there you go inmediate failure.
If this is true we can really blame SE, after all they are not expecting or care for that matter that a bunch of unlockers are going to mess with the phone. ;)
07heaven
10-12-2006, 03:57
W810i for spares it is then :mad:
Wife's gonna kill me :eek: .. Was her new phone
Cheers guys,
Atleast it weren't a customer's phone!!!
Speedymobile
10-12-2006, 10:46
For sure :D :D
To date... only 1pc customer phone has died and we have been unable to recover... not bad statistics that huh ;)
send it back to sonyericcsson m8
@luzer
And the list of dead w8xx is growing.
Im not so sure about the Quality Ctrl problem though.
Reading/Writing info to the phone uses certain required voltages, and it is unlikely that this action(assuming Rd/Wr supply used is correct) will cause parts breakdown unless that ic has some sort of problem beforehand. Also, this phone is Lead free compliant which means higher heat stress tolerance on parts-pads connection.
Unless SE did this on purpose. Like a small experiment to improve phone security (now they also remove/hide? TP).
And I think they expected us to mess with all their phones.
just my opinion....
BR
beega
Yes, not that that makes any difference im afraid
Identity button does brings up phone description yes, thats all though :( ..here's the log it reads:
... phone won't power on to let soft recognise the phone to flash the files though
Not yet tried with cruiser.. will maybe have to try if no solution with SETool by tomorrow
Will also try with Zulea usb smart... never know :D :D
If I wanted to find a quick answer i'd buy another phone.
SETool forum is crap.. wait forever for replies, then get the most stupid answers you can get. After explaining to them in full detail what is the problem, they then reply asking "Have you done this?" "Have you done that?" when it's quite clearly stated in my FIRST post.
Now then.. maybe YOU should try reading the WHOLE of this thread, then consider posting elsewhere your stupid post! :mad:
Thanks guys,
Speedy
TRY TO LOWER YOUR FLASHING SPEED BRO...JUST TRY IT.;)
Speedymobile
10-15-2006, 13:06
TRY TO LOWER YOUR FLASHING SPEED BRO...JUST TRY IT.;)
Yeh tried that mate.. thanks anyway
i have same problem trying to change imei in w810 with setools but fone dead 2fones for that neway i revived it with usbsmart by just reflashing the mcu make sure battery is charge
I fix W810 almost everyday with setool3_ufs, I ve done more than 500 W810s, Not even a single problem both unlocking and flashing.
Another, point, all setool users know where to post their problem.
PLZ CAN U TELL ME HOW TO REVIVE MY DEAD W810 DEAD WITH USB-SMART
just flash it with main sw and fs sw but with setools download the the necessary flash files from support and also down load the recovery file from main software section the unzip and place the rest file in the setools dir lunch setool in the add section add the main and fs files then in seting select complete fone and then select flash this is how i fixed mine 2day hope it helpful
br
bitihel
magixian
11-23-2006, 01:04
Guys, I have here 1x SE W810i killed by Setool3....
All I done was read GDFS and when it said "remove battery, re-insert and press Test Point OK".. It died.. now phone is dead and won't turn on.
Doesn't seem to be recognise by SETool at all as when it says to press power on button briefly, it doesnt recognise it as phone is dead :o
Phone was working fine before I use this tool.... Any way to repair it? :rolleyes:
Speedy
you can alway revive any S.E phone with usb smart (not cracked) using tp.
it is best for these models!
for new model like w810 there is no test point
Dr cellular uk
11-23-2006, 16:23
yes even when you identify phone on se-tool the moment you remove and install battery and press test point ok it automatically goes off take note of the software version,then flash it with generic flash files.
tunjay-gsm
11-25-2006, 10:20
i like honest person no test point any w810i
infozohaib
11-30-2006, 12:12
Hello bro,
everyone want to know how to repair this problem.:confused: :confused: we hope u will share ur expiriance with all other Mates of this Forum.
we r waiting ur nice and usefull reply
thakns
:) :)
I fix W810 almost everyday with setool3_ufs, I ve done more than 500 W810s, Not even a single problem both unlocking and flashing.
Another, point, all setool users know where to post their problem.
Dr cellular uk
12-01-2006, 21:07
i have no problem flashing w810"s all mine are perfect even if i repair gdfs which i hardly do,i mainly flash them using se-tool2....
Kashif Khan
12-01-2006, 21:17
i have no problem flashing w810"s all mine are perfect even if i repair pds which i hardly do,i mainly flash them using se-tool2....
Repair PDS what do you mean ? ?
JayDee78
12-01-2006, 21:42
He is mixing up motorola w810 with sonyericsson w810...
Crazy_ratata
12-01-2006, 22:20
Try with cruiser or USB Smart... Should be easily fixed...
Wbr
muslimlife
12-11-2006, 18:10
Hello Every on how you doing i hope you are well. problem is were not getting any way with the w810i. is there no way of contacting se tool for assistance regarding this issue.
i have a w810i the virsion was R4db005 when i unlocked it, it failed to power on. then i flashed it with the recovery it recovered the phone sucessfullly but then i downgraded to rck003 file and the fls003 phone was back on line but as it loaded up with sim card inserted
Configuration Error. Please Contact Your Network Operation Or Service Centre.
If you have come accross this messege.
Please help....
Hello Every on how you doing i hope you are well. problem is were not getting any way with the w810i. is there no way of contacting se tool for assistance regarding this issue.
i have a w810i the virsion was R4db005 when i unlocked it, it failed to power on. then i flashed it with the recovery it recovered the phone sucessfullly but then i downgraded to rck003 file and the fls003 phone was back on line but as it loaded up with sim card inserted
Configuration Error. Please Contact Your Network Operation Or Service Centre.
If you have come accross this messege.
Please help....
just complete phone ;););)
williamwallace4
12-11-2006, 23:00
can anyone help k800i dead after taking battery out and changing sim card
plz help
1/1/2009 9:31:07 AM v0.915030/UNI
1/1/2009 9:31:07 AM CARD SERIAL: 00094574
1/1/2009 9:31:07 AM Loaded 51 flash descriptors
1/1/2009 9:31:14 AM SIGNED MODE (USING SERVER)
1/1/2009 9:31:14 AM TESTPOINT REPAIR STAGE #1 STARTED
1/1/2009 9:31:15 AM Open COM port OK
1/1/2009 9:31:48 AM ChipID:8040,EMP protocol:0301
1/1/2009 9:31:48 AM NEW SECURITY (MARITA RESPIN) PHONE
1/1/2009 9:31:48 AM
1/1/2009 9:31:48 AM PHONE STATE: "RETAIL"
1/1/2009 9:31:48 AM FLASH CID: 0050
1/1/2009 9:31:48 AM Speed:921600
1/1/2009 9:31:49 AM OTP: LOCKED:1 CID:50 PAF:1 IMEI:35190102277615 CERT:RED
1/1/2009 9:31:49 AM FLASH CID:50 COLOR:RED
1/1/2009 9:32:07 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:32:07 AM setGDFS_params failed
1/1/2009 9:32:07 AM failed to setup GDFS
1/1/2009 9:32:07 AM SETOOL2 CAN'T FIX THAT PHONE
1/1/2009 9:32:07 AM PLEASE FLASH MAIN PART OF FIRMWARE AND RETRY
1/1/2009 9:32:07 AM Elapsed: 53 secs.
1/1/2009 9:34:20 AM SIGNED MODE (USING SERVER)
1/1/2009 9:34:20 AM TESTPOINT REPAIR STAGE #1 STARTED
1/1/2009 9:34:20 AM Open COM port OK
1/1/2009 9:34:32 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:34:32 AM Speed:921600
1/1/2009 9:34:32 AM OTP: LOCKED:1 CID:51 PAF:1 IMEI:35934601710517 CERT:N/A
1/1/2009 9:34:33 AM FLASH CID:52 COLOR:RED
1/1/2009 9:34:34 AM LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
1/1/2009 9:34:34 AM PREPARING...
1/1/2009 9:34:40 AM ATTACH TP #1 AND PRESS "READY"
1/1/2009 9:35:47 AM RELEASE TP #1 AND PRESS "READY"
1/1/2009 9:35:52 AM TP #1 INCORRECT
1/1/2009 9:35:52 AM Elapsed: 92 secs.
1/1/2009 9:35:54 AM SIGNED MODE (USING SERVER)
1/1/2009 9:35:54 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:35:54 AM Open COM port OK
1/1/2009 9:35:54 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:35:54 AM Speed:921600
1/1/2009 9:35:55 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:35:58 AM Trying to launch embedded bootloader...
1/1/2009 9:36:00 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:36:00 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:36:01 AM Elapsed: 6 secs.
1/1/2009 9:36:02 AM SIGNED MODE (USING SERVER)
1/1/2009 9:36:02 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:36:02 AM Open COM port OK
1/1/2009 9:36:08 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:36:08 AM Speed:921600
1/1/2009 9:36:09 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:36:13 AM Trying to launch embedded bootloader...
1/1/2009 9:36:20 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:36:20 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:36:21 AM Elapsed: 19 secs.
1/1/2009 9:36:24 AM SIGNED MODE (USING SERVER)
1/1/2009 9:36:24 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:36:24 AM Open COM port OK
1/1/2009 9:36:36 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:36:36 AM Speed:921600
1/1/2009 9:36:37 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:36:40 AM Trying to launch embedded bootloader...
1/1/2009 9:36:45 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:36:45 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:36:46 AM Elapsed: 21 secs.
1/1/2009 9:36:52 AM SIGNED MODE (USING SERVER)
1/1/2009 9:36:52 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:36:52 AM Open COM port OK
1/1/2009 9:36:59 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:36:59 AM Speed:921600
1/1/2009 9:37:00 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:37:06 AM Trying to launch embedded bootloader...
1/1/2009 9:37:41 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:37:41 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:37:42 AM Elapsed: 49 secs.
1/1/2009 9:37:49 AM SIGNED MODE (USING SERVER)
1/1/2009 9:37:49 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:37:49 AM Open COM port OK
1/1/2009 9:37:51 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:37:51 AM Speed:921600
1/1/2009 9:37:52 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:38:13 AM Trying to launch embedded bootloader...
1/1/2009 9:38:17 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:38:17 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:38:18 AM Elapsed: 28 secs.
k550i dead
/1/2009 9:31:07 AM v0.915030/UNI
1/1/2009 9:31:07 AM CARD SERIAL: 00094574
1/1/2009 9:31:07 AM Loaded 51 flash descriptors
1/1/2009 9:31:14 AM SIGNED MODE (USING SERVER)
1/1/2009 9:31:14 AM TESTPOINT REPAIR STAGE #1 STARTED
1/1/2009 9:31:15 AM Open COM port OK
1/1/2009 9:31:48 AM ChipID:8040,EMP protocol:0301
1/1/2009 9:31:48 AM NEW SECURITY (MARITA RESPIN) PHONE
1/1/2009 9:31:48 AM
1/1/2009 9:31:48 AM PHONE STATE: "RETAIL"
1/1/2009 9:31:48 AM FLASH CID: 0050
1/1/2009 9:31:48 AM Speed:921600
1/1/2009 9:31:49 AM OTP: LOCKED:1 CID:50 PAF:1 IMEI:35190102277615 CERT:RED
1/1/2009 9:31:49 AM FLASH CID:50 COLOR:RED
1/1/2009 9:32:07 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:32:07 AM setGDFS_params failed
1/1/2009 9:32:07 AM failed to setup GDFS
1/1/2009 9:32:07 AM SETOOL2 CAN'T FIX THAT PHONE
1/1/2009 9:32:07 AM PLEASE FLASH MAIN PART OF FIRMWARE AND RETRY
1/1/2009 9:32:07 AM Elapsed: 53 secs.
1/1/2009 9:34:20 AM SIGNED MODE (USING SERVER)
1/1/2009 9:34:20 AM TESTPOINT REPAIR STAGE #1 STARTED
1/1/2009 9:34:20 AM Open COM port OK
1/1/2009 9:34:32 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:34:32 AM Speed:921600
1/1/2009 9:34:32 AM OTP: LOCKED:1 CID:51 PAF:1 IMEI:35934601710517 CERT:N/A
1/1/2009 9:34:33 AM FLASH CID:52 COLOR:RED
1/1/2009 9:34:34 AM LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
1/1/2009 9:34:34 AM PREPARING...
1/1/2009 9:34:40 AM ATTACH TP #1 AND PRESS "READY"
1/1/2009 9:35:47 AM RELEASE TP #1 AND PRESS "READY"
1/1/2009 9:35:52 AM TP #1 INCORRECT
1/1/2009 9:35:52 AM Elapsed: 92 secs.
1/1/2009 9:35:54 AM SIGNED MODE (USING SERVER)
1/1/2009 9:35:54 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:35:54 AM Open COM port OK
1/1/2009 9:35:54 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:35:54 AM Speed:921600
1/1/2009 9:35:55 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:35:58 AM Trying to launch embedded bootloader...
1/1/2009 9:36:00 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:36:00 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:36:01 AM Elapsed: 6 secs.
1/1/2009 9:36:02 AM SIGNED MODE (USING SERVER)
1/1/2009 9:36:02 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:36:02 AM Open COM port OK
1/1/2009 9:36:08 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:36:08 AM Speed:921600
1/1/2009 9:36:09 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:36:13 AM Trying to launch embedded bootloader...
1/1/2009 9:36:20 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:36:20 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:36:21 AM Elapsed: 19 secs.
1/1/2009 9:36:24 AM SIGNED MODE (USING SERVER)
1/1/2009 9:36:24 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:36:24 AM Open COM port OK
1/1/2009 9:36:36 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:36:36 AM Speed:921600
1/1/2009 9:36:37 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:36:40 AM Trying to launch embedded bootloader...
1/1/2009 9:36:45 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:36:45 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:36:46 AM Elapsed: 21 secs.
1/1/2009 9:36:52 AM SIGNED MODE (USING SERVER)
1/1/2009 9:36:52 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:36:52 AM Open COM port OK
1/1/2009 9:36:59 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:36:59 AM Speed:921600
1/1/2009 9:37:00 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:37:06 AM Trying to launch embedded bootloader...
1/1/2009 9:37:41 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:37:41 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:37:42 AM Elapsed: 49 secs.
1/1/2009 9:37:49 AM SIGNED MODE (USING SERVER)
1/1/2009 9:37:49 AM TESTPOINT REPAIR STAGE #2 STARTED
1/1/2009 9:37:49 AM Open COM port OK
1/1/2009 9:37:51 AM ChipID:9900,EMP protocol:0301
1/1/2009 9:37:51 AM Speed:921600
1/1/2009 9:37:52 AM ATTACH TP #2 AND PRESS "READY"
1/1/2009 9:38:13 AM Trying to launch embedded bootloader...
1/1/2009 9:38:17 AM PROCEDURE WAS STOPPED BY USER
1/1/2009 9:38:17 AM TP #2 INCORRECT OR STAGE #1 NOT EXECUTED
1/1/2009 9:38:18 AM Elapsed: 28 secs.
Yeh tried that mate.. thanks anyway
Mate based in my experience with db201X and db2020 when any phone dont power on after flash and you reflash and reflash and nothing try to rehot CPU and flash IC not too much, assembly the phone again and you could be surprised
BR. Celutek