Problems unlocking K810

hey guys,

after alot of searching and messing about i finally managed to debrand my k810, looks great. Now i want to unlock it, using the method mentioned in this post: http://www.topsony.com/forum/showthread.php?t=6329

Now, i followed all instructions, by using the ORIGINAL MAIN FIRMWARE (one i downloaded from topsony) file to generate all files. I get to the part that tells me to press "flash" and to "Follow the instructions given by SETool2 Lite"

However, i dont get any instructions when I press flash, instead, the progress bar just keeps going from left to right, its done it about 100 times now. Am i doing something wrong here?

i have posted a screenshot with this post if it helps.

Thanks in advance.

have you added usb flash drivers.

try and post a log here from setools

lav

Yes I have added the flash drivers, I dont think debranding would have worked otherwise (am I right?)

Below is a log of what SEtool does when I connect the phone and try to flash it

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 Index of ./ and buy FULL.

ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
Flash ID check:897E
Flash props sent ok
OTP LOCKED:1 CID:51 PAF:1 IMEI:35612701611787 CERT:RED
FLASH CID:52 COLOR:RED

Model:K810i
Brand:Sony Ericsson
MAPP CXC article: R8BA024 prgCXC1250811_GENERIC_SM
MAPP CXC version: R8BA024
Language Package:EUROPE_5
CDA article: CDA102568/14
CDA version: R6A
Default article: cxc1250813
Default version: R8BA024

Extended LOCKED
Operator: MULTIPLE

Elapsed:10 secs.
Abort all operations.
phone pre-boot failed,possible RECOVERY needed.
Elapsed:68 secs.
ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
Flash ID check:897E
Flash props sent ok
OTP LOCKED:1 CID:51 PAF:1 IMEI:35612701611787 CERT:RED
FLASH CID:52 COLOR:RED

Model:K810i
Brand:Sony Ericsson
MAPP CXC article: R8BA024 prgCXC1250811_GENERIC_SM
MAPP CXC version: R8BA024
Language Package:EUROPE_5
CDA article: CDA102568/14
CDA version: R6A
Default article: cxc1250813
Default version: R8BA024

Extended LOCKED
Operator: MULTIPLE

Elapsed:9 secs.

Follow the How to apply the generated patches to DB2020 CID52 phones section carefully in first post of Remove SIM-lock patch generator thread. Should work then...

I dont know if this is something thats wrong with my phone or whether it is normal, but when try to read GDFS to make a backup of the phone, it doesnt seem to work. How long does it normally take to make a backup? the progress bar keeps cycling and no file is generated even after waiting a long time.

The GDFS backup should be done in a couple of ten seconds.

Quote:

---

the progress bar keeps cycling and no file is generated

---

Have you installed the USB Flash Driver? If yes, have you installed it from the [setool2lite_folder]\drivers\USBFlash_driver\ folder? It is highly recommended to use this driver!!!

OK I had a look at drivers and stuff to make sure they were where they are meant to be. Now when I start SEtools, i get this error:

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 Index of ./ and buy FULL.

Abort all operations.
Can't load ID loader !
Elapsed:12 secs.

Just to make sure, I copied the "ggsemc" from
C:\Documents and Settings\Admin\My Documents\Phone\SETool\drivers
to
C:\WINDOWS\system32\drivers
this is what everyone else says to do. But when I press the Identify button on SEtool, it doesnt tell me that I have 30secs to connect phone as it always has done. and when it is connected via usb...nothing happens

You should install it like in USB Flash Driver Installation - Guide but use this driver.

ok, did what it told me to do do, windows installed about 3 - 4 files and it picked up something called SEMC Flash device. SEtool now can see my device, which is better that what it was doing earlier, but still doesnt read GDFS.