SE W810i phone major problems with SEtool

Half_Price_Sky

Over the last couple of nights I've been trying to unlock and debrand my SE W810i (CID49). I succesfully did my gf's W810i last year but this time I've had major problems getting the flash drivers installed properly. I've tried on two laptops and a desktop (XP and Vista) but not much joy.

Last night I had another go on my gf's daughter's XP laptop and I'm worried I might have bricked my gf's phone.

I was using her phone just to elimante whether or not it was my phone being problematic the previous couple of nights.

When pluging the phone in (holding down C button) the wizzard comes up and I go through the usual procedures to install the drivers. The icon of the yellow files transfering appears followed by an error message telling me that there was a problem installing the drivers.

However I've noticied that despite the fact the drivers don't apear to be installing properly, each failed install attempt stangely seems to allow me to have a one time use of SEtool and XS++. Ie. I make a failed attempt to install the drivers after which I can use "Identify" on SEtool. I then disconnect phone and once reconnected attempt to Read GDFS but SEtool again won't recognise the phone until after I make another failed attempt at installing the drivers after which I am able to Read GDFS.

I managed to Identify the phone and Read the GDFS, which is now backed up in my documents. However in a state of tiredness, after reading the GDFS I noticed it said press "Ready" in the display panel so I pressed it before disconnecting the phone. I've since noticed afterwards that it says to disconnect the phone first before pressing Ready. Now no matter how many times I try the phone just won't turn back on again.

PLEASE PLEASE PLEASE tell me I haven't bricked the phone. I had to tell her last night what had happened and she went mad, neither of us currently have the funds to buy a replacement phone right now. Is there a way to bring it back to life again, I thought it was only buttons like the "Write" and the "Flash" or "Unlock" ones that bricked the phone?

Half_Price_Sky

The problems continue!!

I'm currently trying to do my phone. I've successfully done Identify and backed up the GDFS, in between my "failed" attempts of downloading the flash drivers.

I've moved onto XS++, connected the phone and followed all the instructions, putting the relevant files in the right places and selected own custpack. I've clicked Flash and I get the message "Sending db2010_cid49red_flash_r2a003.bin..." in the display panel. This piece of text appears to be merely the first line of the data that normally appears on the display screen when flashing the phone so presumably the flashing has stalled or is not working as it's been like this since I went to bed last night and is showing no signs of progressing.

I'm worried about what to do. Should I press "Stop" and disconnect the phone?

I'm feeling incredibly frustrated with all these problems, any help would be EXTREMELY appreciated.

gaming_guy

you may need a service cable to revive the phone (see ebay) if the 2+5 method won't work (see below).

i have always found the flash drivers to be more stable on XP (i use XP Pro). what happens if you right click the .inf file and select install (without the phone connected or XS/Setool open)?

when connecting the phone, press 2+5 (at the same time) instead of C to see if that works.

you should be able to unplug the phone as XS hasn't sent anything to the phone yet.

Half_Price_Sky

gaming_guy wrote: »

you may need a service cable to revive the phone (see ebay) if the 2+5 method won't work (see below).

i have always found the flash drivers to be more stable on XP (i use XP Pro). what happens if you right click the .inf file and select install (without the phone connected or XS/Setool open)?

when connecting the phone, press 2+5 (at the same time) instead of C to see if that works.

you should be able to unplug the phone as XS hasn't sent anything to the phone yet.

Am I safe to press "Stop" in XS++ before I try that? I currently have my W810i connected to XS++ on my XP laptop (got two W810i's between me and my girlfriend - her's is the one that won't switch on).

Tried flashing / unlocking mine last night after messing up her one. The status just say's "Sending db2010_cid49red_flash_r2a003.bin..." and hasn't moved off that since last night, or should I just press Close or something?

gaming_guy

it should be fine to press stop in xs, as it should only take a few seconds to send the file (which it hasn't sent yet).

on the broken one, does it turn on and display a flashing white screen, or does it give several flashes of the red light inside the infrared port (next to the on/off button)?

Half_Price_Sky

Well I don't beleive it............ My phone's doing the same now. I pressed Stop in XS++ because the flash hadn't worked and now it won't turn on either despite the battery being charged.

I press the on button on both phones and absolutely begger all happens. No white screen (WSOD) or flashing LED on the infared thingy.

This is getting me really depressed I feel like throwing the bloody things at the wall!!

Half_Price_Sky

DELETED Duplicate post.

Half_Price_Sky

Well I've tried SEtool again and it still Identifies both phones and reads the GDFS despite the fact neither of them will turn on anymore. Would SEtool still identify a phone that is bricked?

gaming_guy

reflash the main firmware on one of them WITHOUT the patch to see if that fixes it.

i take it that you have removed the sim card/memory stick from the phone?

(DO NOT flash the GDFS at this point as if you get the wrong one on the wrong phone, then you will need full version of setool to fix it)

SEtool (and XS++) will still detect a phone that won't turn on (providing that the phone starts in flash mode)

i used R4EA031 on my old w810i when reflashing it. the firmware version must match the version that the patch was created for (so if you have a phone with R4EA031 loaded, you must use the r4ea031 patch otherwise you will end up with a 'dead' phone - a main reflash will sort it)

also, make sure that the phone's charging port and the data cable are free from dust & other rubbish that might prevent the pins from fully connecting to the phone

Half_Price_Sky

Mate you are an absolute LEGEND I can’t thank you enough!!! Finally sorted the two phones out tonight round at my mum and dad’s on their XP desktop computer and unlocked and debranded the black T-Mobile one to use with my O2 Simplicity sim (which was my original objective).

The flash drivers began appearing again in Device Manager when I connected the white phone (don’t know why they wouldn’t when connecting the black one). I began by trying to flash the Main and File System + own custpack on both phones but the flashing was getting stuck again so I tried just doing the Main on it’s own, just like you said, and that sorted it all out and got me on my way.

Once again thanks for all your help it’s certainly a relief to be out of the dog house with the missus after breaking her phone.

Going to be keeping an eye out on HUKD now for a good new phone after pay day. The black one’s been in the kitchen drawer for over 12 months, as I’m only using it after I lost my K770i on holiday, but it will do for now!