[five46]

Hello folks!

This is the second time I'm having difficulty with a phone's password. Last time it was with my W810, but thankfully I could retrieve it with XS++.

Now, it's with my K550i@W610i, running on R6BC002, CID53. On inserting another SIM, it asks for Phone Lock Code, which to the very very best of my knowledge, I haven't changed from the default 0000. On entering 0000 it shows 'Wrong Code'.

How do I retrieve this? Or, should I reflash it?

This post has been edited by five46: 21 March 2009 - 06:17 AM

[Norby]

CID 53. It's hard to find tools compatible with CID53, search around. I think SEtool full, can handle your situation, I tried downloading it, but I couldn't find it. Look on Slobodanski, and ask there.

Flashing doesn't change the code, try 1234 if you're confident about that option.

Cheers.

This post has been edited by Norby: 21 March 2009 - 06:34 AM

[nabiladeeb]

no free solution, try davinci website I think they can do it.

[five46]

Funniest thing is how did this PhoneLock appear? Earlier I was using it with my 'xyz' Sim. Then, I gave it to my dad who uses a 'abc' sim. Now, after few days (or months for that matter) when I'm trying my 'xyz' sim again, it's asking for PhoneLock Code. My father says he has never fiddled with the security settings!

Norby, on 2009-03-21 12:03, said:

CID 53. It's hard to find tools compatible with CID53, search around. I think SEtool full, can handle your situation, I tried downloading it, but I couldn't find it. Look on Slobodanski, and ask there.

Flashing doesn't change the code, try 1234 if you're confident about that option.

Cheers.

Are you sure, flashing won't help?
Edit: Tried flashing with W610 Main and FS, not working. Will try with K550 Main and FS.

Would a retrofit with K550 Main and FS help?

nabiladeeb, on 2009-03-21 13:25, said:

no free solution, try davinci website I think they can do it.

This would be new for me. And if I'm not wrong they charge some 10 Euros right? Payment would be a real pain, because I don't carry credit cards.

This post has been edited by five46: 21 March 2009 - 03:13 PM

[SifJar]

From my reading of the topic, your phone is locked to (in your words) "abc" network. Your dad must have accidently locked it to his network. Flashing will not remove the network lock from a phone. There is no free way to get the unlock code. I would say try patch unlocking it, see if that helps. With CID 53 you'll need to use den_po's AnyCID Patching method, search for it. Flashing will not remove the network lock from a phone. Hope that helps.

[five46]

SifJar, on 2009-03-22 01:43, said:

Your dad must have accidently locked it to his network. Flashing will not remove the network lock from a phone.

Thanks for showing your concern SifJar.

Indeed it turned out to be the case that the default 0000 was changed. After a lot of digging, my dad remembered that my elder brother had played with the security settings. Later called him up and procured the pass code. Now its working fine with any other sim.

But anyhow, on a curious note, we can continue with the topic as to can a Simox unlock patch help to overcome such situation?

[SifJar]

i think i misunderstood the topic, in which case a patch probably wouldn't have been any good. I thought you dad had locked the phone to his network by accident, stopping it working with your sim. But it was just a phone lock code, so a patch wouldn't have helped. There are ways to recover a phone lock code though. Just connect to XS++ and select the GDFS tab and press Phone Lock button at the top. This will read out your Phone Lock code, or if its DB2020, reset it to 0000.

[KK§cchaos]

SifJar, on 2009-03-23 19:56, said:

There are ways to recover a phone lock code though. Just connect to XS++ and select the GDFS tab and press Phone Lock button at the top. This will read out your Phone Lock code, or if its DB2020, reset it to 0000.

That only works if the phone is CID52 at the moment, not CID53

This post has been edited by cchaos: 23 March 2009 - 10:10 PM

[SifJar]

Ah, yeah, just reread the first post and realised it was CID53. Oops.