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.
Related
I looked all over these forums for evidence of this problem, apologies if the solution is here and I'm asking a redundant questions!
Just got an XDA II from a friend and have 2 problems:
:arrow: 1) On a hard reset or simply after removing the battery, I just get the O2 splash screen for about 15 minutes (no button presses or screen taps will affect it), then poof, stuff starts installing and suddenly I have a working PDA.
:arrow: 2) If I put my SIM card in the device, this "poof" never happens, the device stays on the splash screen indefinitely. I've used XDA Unlock which as told me that the device is ALREADY unlocked.
Thoughts? Do I need to install a new ROM or am I simply missing something else? I'd love to be able to use this with ATT here in the US if possible.
Device status is:
ROM: 1.52.OOWWE
Date: 10/23/03
RADIO: 1.05.13
PROTO: 1337.13
EXTROM: 1.03.27
Thanks!
Did this start happening before you used xdaunlock. That program is for the xda1, the unlock for xda2 is a totally different application, when you run the xda2 unlock it gives you the sid number to enter when you put in a sim from a different provider. I think your phone is still locked and it is probably the sim that is hanging it. You need this.
http://wiki.xda-developers.com/wiki/xda2unlock
I did use xda2unlock
Oops, I should have been clearer, this WAS the application I used (It's very clear that it's for unlocking the 2, not the 1). It "worked" in terms of talking to the device, but no results given that it figured it had no work to do.
Is my other other option to unlock this to go to O2?
...and no, the behavior has been consistent...
...before and after using the ap. The other thing the Sim card seems to do is lock the device up, whereas without it the device EVENTUALLY unlocks and lets you use the PDA features. Rather annoying.
Sounds like a faulty unit to me, no way should you be waiting that long for a boot, yes the sim seems to make it worse but its bad to begin with, it should be sent for repair I think. I am sure the xda2 does some hardware checks on boot and maybe its having a hard time getting past one of them, do you have an sd card inserted in the slot? And how does it function once it gets past boot? Does it survive a soft reset ok? Are there any error messages when it begins its install procedure?
It's WORKING!!! It's WORKING!
I'm not sure whether this is SUPPOSED to be a problem or not, but LOCKING the Sim card door down causes this unit to go into this wierd state I've been experiencing...just letting the batttery press it down in place (but not securing it by pulling that little tan lever to the left) makes ALL the difference.
HOW ODD! Or did I miss something that should have told me that this would screw things up?
The phone indeed was already unlocked, picked up my network beautifully. Thanks for your input!
Good morning.
After booting my phone, entering my PIN and pressing OK it reboots. Not every time, sometimes it goes on working as expected. And before the reboot it freezes for a few seconds either when the input-PIN-dialog has just disappeared or whilst it's diappearing.
So that getting the Mini to an usable state can take from one to several tries.
Changing or taking out the SD card changes nothing, but doing this with the UICC (let's say SIM) does.
The problem is present when SIM0 is plugged (my main connection/line/number). It's an 8 pin card I got from my provider two years ago for use with my W980i.
Without a SIM or with SIM1 plugged the phone acts like it should. While SIM1 is a brand new 6 pin card I got cause of a strange take-more-connections-get-more-boni deal. And with both with-SIM-settings I repeated it dozens of times.
Restoring with SEUS doesn't help. And the phone isn't rooted (yet).
So my questions are:
Isn't SIM0 working fine anymore? Is their a chance that my Mini has a defect?
Is there a UICC-integrity-test without the need for special hardware? Could it be that the different SIM format is causing this behaviour?
Later on I'll also call my provider, but preparation is everything, isn't it. And who knows if it's done after that call. But first I'll hug my pillow for a while (7:38 AM yet ).
So your suggestions, ideas or even more knowledge are/is welcome.
Thanks in advance.
I have the same problem (nearly every reboot). But I haven't tried different SIM cards.
I'll try with different ones and if that makes a difference like does in your case.
I'm using o2 Germany Multicard (2 cards (or more), 1 phone number).
It's o2 Germany in my case too. What formats are your cards (8 or 6 pin) of. Although i don't know if that could make any difference.
The call center guy (Guy) i've just talked to didn't have any idea. He offered me to send a new SIM, but I'll head for an o2 shop this evening. I can get one there immediately. And maybe there is an oppurtunity to test some other cards. At least I hope there is.
Also Guy didn't know about any card test facilities. Perhaps I can reach a cell phone repair shop in time after that. I'd like to know what they can do/say.
Oh, I forgot to say, that my W980i still works fine with SIM0. Although it reboots sometimes while playing music ever since. I don't know if there's commonality. I ever thought of a hardware failure in memory.
I'll report.
Now I count three phones - W980i, W800i and some cheap Panasonic or so - that work proper with that suspicious 8 pin card (SIM0)
and four 6 pin cards my X10 Mini works with.
There wasn't any shop staff being able to help me getting closer to the source of that failure. I couldn't get to the cell phone repair shop in time.
Unfortunately I have no more X10 Minis or other two years old 8 pin cards (UICCs) from o2 Germany to do further testing.
same prob here ....
little workarround: when rebooting the phone press the powerbutton and switch to flightmode. unlock the phone. then disable flightmode and enter pin.
Nice to know, though my actual workaround is a new SIM replacing SIM0.
But still left is that annoying ambiguity whether I bought a proper device or not. And I dislike the idea of returning it without a reasonable suspicion.
@inteks
I could not really understand your procedure.
I have similar problem, but my phone does not boot. It vibrates and then nothing. Even if I switch off in airplane mode it will not switch on.
What are the exact steps you are using?
Thanks
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.
Hi everyone, i am currently using Atrix 4g on Dorians Redpill Hybrid V1. I recently went on a trip to China and i put in a chinese company sim card and i get the network unlock screen and i entered a few codes that didnt work which caused my Atrix to hardlock after 10x failed tries. However luckily i was able to use Amil's guide and flashed a special radio that caused my phone to work again.
However after getting my phone back, i tried pressing "#073887*" to try to reach the network unlock screen so I could unlock my phone with an ATT issued PUK code so i could reflash back to my old radio which is better, nothing shows up at all and I press call and you get the called incorrect # auto message because "#073887*" isnt a real phone #.
Please help!!
Thanks!
I'm having a different unlock issue, the code AT&T gave me generates a network error and won't unlock the phone. Since the phone is a refurb, I suggested that maybe the original owner locked it and the refurb didn't clear that. So AT&T bridged in a Moto inside tech rep who SWEARS that even if the phone has been "permanently locked" by using the wrong unlock code 5x, the phone will be cleared and reset by using the factory reset option form the normal menus, or from the power+volume boot sequence. He swears both processes are the same and that either one will reset the SIM unlock code in the phone, so you get five more tries to enter a correct code and unlock it.
Now with your custom code, I couldn't guess. And prior to this "everyone" swears a factory reset won't clear the unlock code. I don't know who is wrong about that.
But it could be worthwhile for you to try. Backup as much as you can, do a factory reset, see if you can unlock it back to AT&T after that.
Rred said:
I'm having a different unlock issue, the code AT&T gave me generates a network error and won't unlock the phone. Since the phone is a refurb, I suggested that maybe the original owner locked it and the refurb didn't clear that. So AT&T bridged in a Moto inside tech rep who SWEARS that even if the phone has been "permanently locked" by using the wrong unlock code 5x, the phone will be cleared and reset by using the factory reset option form the normal menus, or from the power+volume boot sequence. He swears both processes are the same and that either one will reset the SIM unlock code in the phone, so you get five more tries to enter a correct code and unlock it.
Now with your custom code, I couldn't guess. And prior to this "everyone" swears a factory reset won't clear the unlock code. I don't know who is wrong about that.
But it could be worthwhile for you to try. Backup as much as you can, do a factory reset, see if you can unlock it back to AT&T after that.
Click to expand...
Click to collapse
I just did mine a couple of weeks ago, and AT&T warned me before giving me the code that it would become hard locked after 10 unlock attempts. My code worked 1st time, so all is good. I also believe a factory reset does not reset a SIM unlock.
Apparently the following is a fix for a hard locked phone:
http://www.amilkhanzada.com/2012/03/how-to-unlock-permanently-network.html
After my brainless cousin got accepted to work as an ATT Rep, honestly speaking, those ATT people at the stores dont know much about phones other than what mainstream people know and about your billing. Technical stuff they arent really trained to do so and infact they just follow a book of common errors. I have used amil's guide and it worked for me but i just cant open network unlock again so then i could perhaps put in my ATT network unlock code and then hopefully flash back to my old radio. I actually tried flashing a new rom and trying #073887* and it still doesnt work.
So far i am probably just going to have to deal with it having a weaker radio. At least i got my phone working again!
Thanks!
CaelanT said:
I just did mine a couple of weeks ago, and AT&T warned me before giving me the code that it would become hard locked after 10 unlock attempts. My code worked 1st time, so all is good. I also believe a factory reset does not reset a SIM unlock.
Apparently the following is a fix for a hard locked phone:
Click to expand...
Click to collapse
That's the fun about anonymous sources for information on the internet. "It works!" "It bricked my phone!" which happens, when, why? no one knows.
I also don't believe a factory reset will clear an unlock condition, but a second level AT&T rep working with a Moto inside tech rep (available to carriers only) swears it will. Have we ever heard that one before.<G>
Obviously there's a way to unlock them, AT&T swears they can be sent in to Moto for unlocking, but then again, sometimes Moto has access to chip programmers and other hardware that the AT&T shops just won't have.
So this cellular support rep dies and wakes up in Hell. he tells the devil it must be a mistake, he's not a bad man. And the devil says, oh, sure, happens all the time, just use that elevator over there, it goes straight to Heaven, they'll get you all straightened out. And the cellular rep goes over to the elevator and sees there's no UP button, just one that says DOWN and the devil says, don't worry about that, just keep pressing the button.
Couldn't happen to a nicer guy, could it?
I'm not sure whether anyone still looks at these forums, but here goes.
Bought a used Zenfone 4 ZE554KL off Ebay, as I already had one and wanted to have another to tinker with. It was clearly labelled not working and not receiving network service. I thought I would have a look and see if I could do anything about that, and if not, I could still use it to try and (finally) learn how to root this thing without bricking my own!
I have managed the latter (i.e. unlocked the bootloader and then rooted the phone) thanks to some threads on here, but I still cannot sort the no service issue. But it is interesting as the phone shows a baseband, indicates that it has an IMEI (under setting), and it did connect the first time I put my own sim in it (after doing a factory reset through recovery), but then as soon as I turned the phone off and on again, it was no longer getting service, and I haven't managed to get it back since.
Dialling *#*#4636#*#* and looking under device information shows no IMEI, no network, signal strength 0, and the mobile radio power button is off and when turned on, goes back to off as soon as I go away from that screen.
A question I would like answered if anyone can, is whether this is a baseband issue, i.e. a hardware issue, or whether it is worth trying to resolve this in some other way. I have seen suggestions that rewriting the xqcn/qcn (?) file can/might help, but I have run up against problems trying to do this.
So, if anyone has any ideas, I'd be very grateful, but bear in mind, I am pretty new to all this.