[SOLVED] Killed my k800??? Fools Rush in...

[sinclair]

I think i've killed my K800I
Initially after XS++ reported a succesfull flash, the phone said 'please wait' for 40 minutes. I used the K800_R1CE001_FS_VFE_LIVE_2_RED49 firmware file.
So (is this where I went wrong) I turned it off hoping it would 're boot'!! Ouch!
When I turned it back on it displayed the sony logo then a white screen, now the phone won't turn on. PC comms via usb shows a usb storage only and then only intermitently. Sometimes the pc makes the connection beep when you plug the phone in, sometimes it doesn't. XS++ can open ports, but gets no further. I have tried connecting using the 'c' button and 2,5. I don't have (and am having trouble getting, SEtools). The Sony update software attempts to communicate but the fails to find the phone. The i.r. light flashes once when battery is inserted and when usb is connected. I purchased this phone from the original owner who arranged for an unlock code from Vodafone. The phone was unlocked prior to flash. I have the original email from vodaphone via the original owner. I have the GDFS backup file (K800_35170701xxxxxx_GDFS_BACKUP.bin) made through XS++ before the failure. The idea of the flash was to remove vodafone logos.
Can anyone tell me if this can definately be recovered, or is it a total loss...:(
Thanks in advance for any help.....
XS++ log follows:

0:00:53| Baseband ID: 9900

10:00:53| Protocol Version: 3.1

10:00:53| Phone name detected!

10:00:53|

10:00:53| Profiling SEMC phone...

10:00:53| Platform: DB2020

10:00:53| OTP CID: 49

10:00:53| EROM CID: 49

10:00:53| EROM Color: Red

10:00:53| IMEI: Edited Out by me :-)

10:00:53| Phone ID: K800

10:00:53| Region: VFE_LIVE_2

10:00:53| CDA: CDA102511/15 R17A

10:00:53| Firmware Version: R1CE001

10:00:53| EROM: R3A011

10:00:53| Ready for operation!

10:01:02| User chose NOT to update EROM CID!

10:01:21|

10:01:21| Sending db2020_cid01_prodid_p3j.bin...

10:01:21| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J

10:01:21| This is a PRODUCTION_ID loader

10:01:21|

10:01:21| Sending db2020_mem_patcher_cid49_r2a006.bin...

10:01:21| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0

10:01:21| This is a MEM_PATCHER loader

10:01:21|

10:01:21| Sending db2020_cid49red_flash_r2a001.bin...

10:01:22| Applet ID: 060721 1022 HANCXC1329129_DB2020_FLASHLOADER_R2A001

10:01:22| This is a FLASH loader

10:01:22| Now flashing firmware main...

10:01:22| Flashing c:\documents and settings\mycomp\desktop\new folder\semc usb flash driver\xs++\xs++ v3.1(darwin)\files_to_upload\k800_r1ce001_fs_vfe_l ive_2_red49.fbn

10:01:22| Header type: BABE

10:01:22| 357 flashblocks

10:04:16| Finishing flash

10:04:17| Done flashing

10:04:17| Flashing was successful

10:04:19| Disconnected... Unplug the phone

The main problem now is HOW DO I GET IT TO RECONNECT If XS++ via the USB can't fully detect the phone, how can you re-flash it???

Although there are very good XS++ instructions such as XS++ 3.1 Guide-Flashing, Customizing, Recovering - Top Sony Forums
It strikes me that an 'idiots guide' detailing the expected responses from both xs++ and the phone at each stage, including how long the action should take to complete (such as the phone showing 'please wait' at first power on after flash and how long that screen should remain for) would save people like me (who thought they knew what they were doing:-) ) from a lot of pain.
Also, detail of the areas that need to be flashed, in what sequence and why (mains+fs+custpack) etc, along with info on why you would, or would not update to CID 52 would help enormously.
There is obviously A LOT to learn on this subject. Let's be honest, We are all probably trying to avoid having to pay someone else to modify our phones for us. To end up killing your phone HURTS and is financially and emotionally very embarasing!!!
The lesson: if it aint broke, don't try and fix it!

[riders4sia]

restore GDFS, upgrade your EROM to CID 52 and reflash it with CID 52 firmwares again (mains+fs+custpack)

[hkisthebes]

you have to flash the all main, fs, custom

[sinclair]

Thanks for that, however - as stated, I can't get xs++ to connect to the phone....

[sinclair]

The main problem now is HOW DO I GET IT TO RECONNECT??
If XS++ via the USB can't fully detect the phone, how can you re-flash it???

[riders4sia]

did you try reinserting your phone battery?

[sinclair]

I have tried removing and re inserting the battery many times, leaving it out for a while etc etc.
What I need to know is, with the limited connectivity I have, is there anything that can enable a re flash, or will the phone have to go to a repair centre.
I guess that repair centres may be able to connect to the erom at board level to restore the operation.

[SeaMonkey]

First of all you flashed FS instead MAIN (look in log - .fbn). So first try to connect phone like here plz help... k810 is dead what can i do ? - Top Sony Forums and this time use .mbn file. And follow every single step and after that post log from XS++ here

[sinclair]

That looks promising!!! Please can you tell me where I can get setools. Do I have to pay for it??:)

[SeaMonkey]

No-you don't have to pay and if you have antivirus - turn off,because he don't let you to download,but be sure there isn't any virus inside - SeTool2 Lite 1.11 - Top Sony Forums and you need Setoo2lite 1.10 + 1.11 update