Sorry for this funny question but from what I think unlocked phone can not be locked again (not iphone). One of my friend keep saying he got locked after couples day using unlocked phone. Could be?
Thank you.
ihowil said:
Sorry for this funny question but from what I think unlocked phone can not be locked again (not iphone). One of my friend keep saying he got locked after couples day using unlocked phone. Could be?
Thank you.
Click to expand...
Click to collapse
Hm, you might be onto something.
I had unlocked my Vibrant using an AT&T SIM a few weeks ago (code provided by T-Mobile), but when I was on vacation in Central America last week, I tried a local SIM and it asked me for an unlock code again.
I never did bother trying to unlock it again, but it was kind of weird. Will test it again with AT&T when I get a chance.
I travel to canada once a week and switch my Tmobile sim to a rogers sim. Has been working for almost 2 months now. Tmobile provided code.
Just re-enter your orig unlock code again
I had similar issues some time ago and posted a question about it but no one responded. I have sinced re-flashed the stock rom again (2nd time) and I have not seen the issue again. It would usually pop up after having to force reboot the phone or do a battery pull after an app hung. I was beginning to think it was related to being rooted and an issue with the mount rw-read only. The first thing I did after the re-flash was to unlock, then did the root etc. It has not come back. One possibly related thing is that sometimes when I have to reboot, it shows missed called after it boots. These are calls that were from a day or 2 before. Its almost like some info isn't being "committed" when a force reboot is done.
Fortunatly it seems that it is just a matter of entering teh unlock code again. Just really strange though...I have always been told that once it is unlocked, it is always unlocked.
Well, it happened again yesterday. Phone was acting wierd, lagging, apps hanging, so I rebooted and got the sim unlock screen again. Entered the code and it unlocked ok.
Very annoying....
My previous Vibrant that I had unlocked re-locked itself somehow as well. I noticed this after I had re-flashed the JFD firmware with ODIN. I popped my AT&T sim and was prompted for the unlock code (again). Which I then entered but unfortunately it didn't take. What's up with that?
I checked my nv_data.bin once again and the code was still the same. I could never get the thing to unlock again though either with the unlock or unfreeze code. It didn't appear to be frozen either; if it was it didn't indicate that.
While flashing via ODIN I never even checked the box related to "efs". I just reloaded the JFD/stock firmware which worked fine. I can't explain it. All I know is I haven't unlocked this new phone yet. I have the code but I will worry about it when the time is come that I need another network to use.
I did notice on the samfirmware.com site they mention to "check your simlock" before flashing a new firmware. Anyone know what that means other than something obvious?
This just happened for the second time to me on two different vibrants from TMO. Is the consensus that the phone needs to be reflashed?
FYI, I have flashed mine twice back to the stock rom and it continues to happen. Also, I opened a ticket with Samsung and even got an RMA to send it in so they could "reflash it". I never sent it in because I knew that would not fix it.
Again, this seems to happen when the phone starts to lag or apps start to hang and I reboot. This has got to be related. I wonder if anyone has had it re-lock while running a lag fix? FYI, Mine is the stock rom rooted and thats it. I wonder if this is only happening on rooted phones?
It really scares me that there is at least one account of it not unlocking with the correct code after it re-locks.
Really would like to find out a solution for this.
I've read that this happens with a lot of Samsung phones, they'll just randomly lock.
Sometimes it appears to make sense (after a ROM flash .... even an official one), sometimes it doesn't. Sometimes it'll only unlock for the SIM you put in, but when you put another in, it'll lock again.
Just make sure you keep your code & have it ready to enter at any given time. Seems to be a Samsung glitch (like the many others we have to deal with).
Yeah same here. When my old vibrant relocked i could never get it unlocked again with the same code. I also highly recommend if your phone is rooted to make a backup copy of /efs which is where that nvram data is stored.
Surprised Here Too!
I went out of my way to go to an AT&T store. Then I read a thread here about proving Vibrants are unlocked. Pissed! Now you're telling me that it may never un-lock again?
"Open the dialer and key in *#7465625#. For an UNLOCKED Vibrant you should get the following result: Network Lock [OFF], Network Subset Lock [OFF], SP Lock [OFF] CP Lock [OFF], press OK to exit that menu"
IrieBro said:
I went out of my way to go to an AT&T store. Then I read a thread here about proving Vibrants are unlocked. Pissed! Now you're telling me that it may never un-lock again?
"Open the dialer and key in *#7465625#. For an UNLOCKED Vibrant you should get the following result: Network Lock [OFF], Network Subset Lock [OFF], SP Lock [OFF] CP Lock [OFF], press OK to exit that menu"
Click to expand...
Click to collapse
They don't come unlocked, you have to unlock them.
I unlocked my vibrant & what you wrote above is what I see.
Hello,
I have a UK version of the S3 (i think its the I9300) About a month ago I had it unlocked from the 3 network (UK) by one of the hundreds of shops that offer unlocking services.
When the phone was unlocked I could enter *#7465625# and it would say that the phone was unlocked to all networks ( I don't remember the exact words) Anyway all was good until last night when my phone upgraded something (I got a reminder in the notification bar that there was an upgrade available) - I've done this before. Now it is saying that the phone is SIM network locked again. And I am unable to enter the code to see whats up.
When I got it unlocked, I was told (obviously incorrectly) that once the code has been entered the phone can never lock itself to a network.
It seems to me, that somewhere in the upgrade 'Three' (who the phone was locked too) has made the phone relock itself.... Has anyone else had this problem, or can point me to the right forum. FYI I am on the O2 network.
Thanks in advance.
Seems like a bit of a nuisance, if every time the phone upgrades it relocks... Perhaps I need to Root the phone..
Known issue on some phone with the latest ICS updates from samsung
Use GalaxSim Unlock to re-unlock your phone
(needs to be rooted)
Update make your phone lock it self common thing.Mate this shops ripe u off. Just root your phone and take simlock using one of the apps from market or voodoo unlock. There is pleanty tutorials how to do it on xda. Its not really complicated o and u can try galaxy S 3 toolkit I think u can take simlock as well using that program hope t helped
Sent from my GT-I9300 using xda app-developers app
Hello all. Tried searching for this, but can't find other similar threads on this. I hope someone can shed light on to this annoying issue.
I have an Atrix 16GB which I got off of T-Mobile UK. Several months ago I decided to purchase one of those network unlock codes off of eBay so I could use this phone with O2, as I have a Nexus 4 16GB which I'll be using my T-Mobile line with.
The code worked.
And that was the last time the phone functioned properly.
Now what I have is the following:
Won't accept any SIM.
Won't connect to any network.
Battery discharge is CRAZY. Even on Airplane mode, it lasts 3/4 day.
The thing is, the code DID work. I mean, the phone accepted it, and then it restarted itself. After that, it kept rebooting at the start screen. I had to go through the "rooting" and "unlocking the bootloader" process to get the phone out of the boot loop.
I was already on CM7.2 when I did the unlock code. Did that cause the issue? Should I have reverted to stock settings and locked the bootloader before unlocking the phone?
Anyone here have any idea what caused this, and more importantly, what the solution may be?
The reason I still like the Motorola Atrix is:
1. Replaceable Battery.
2. MicroSD Slot - I have a 32GB Class 10 card I'd like to use.
3. CM7.2 + DSP - Produces some of the BEST audio I've ever heard on a phone. I like it.
Thanks in advance for the help! :crying:
Hey,
Even though we're a phone unlocking business ourselves, this isn't something we've come across before but I have a thought which might help.
I'm unsure if your phone was rooted before you entered the unlock code, but if so, then it might have read "accepted" but in reality - it might not have been.
I've seen numerous occasions when someone has received a code from us and then entered it - the phone "accepted" it but still didn't work with the new SIM card. If the phone was rooted, this meant that the software in the phone caused the phone to react unexpectedly and essentially reject the switch (from locked to unlocked).
I'm wondering if the software on your phone flipped for some reason, causing the issues you've had.
The best bet is to make sure that when entering an unlock code, the original phone software is installed.
I'm unsure if that helps directly, but it might help in your style of thinking and where the issue may have stemmed from.
So I found this phone in the street. It's a Samsung Galaxy S Mesmerize, (US Cellular) it's also sold as a Samsung Galaxy S Fascinate (Verizon). The phone is beat to hell, screen cracked all over, back is missing, but it's still activated. I've looked all over the internet on how to bypass the lock screen, so I can call numbers in the phone to try and return it, but nothing I've done has worked. I DO NOT want to wipe it, or I'll never be able to return it. I've had it for a day, and no calls have came to it, but texts have. I know it's possible to bypass lock screen by calling the phone, answering and hitting the home button. But I don't know the phone number.
Any help would be appreciated. Again, it's not stolen. I'm trying time return it.
ADB won't work. USB debugging is not enabled. I'm pretty sure this phone isn't rooted.
My Galaxy Tab S3 LTE is not accepting my pin code.
I have hard rebooted the tablet but it still won't take my pin code.
I am 100% sure that my pin code is correct.
This issue occurred after recharging the tablet.
I have documents on the tablet that I don't want to lose so I would like to avoid a factory reset.
Any idea how I can resolve this issue?
Never mind.
Managed to solve the issue by using findmymobile.
I have the same issue with the new android 9 update cannot log in.