*** SOLUTION ***
Thank cellzealot for reiterating how to bypass the initial device/account setup wizard, as well as his and a few others' findings with the RadioComm tweaking.
All I had to do was pop my homemade Bell microSIM I cut out from my old fullsize one in, complete the steps outlined for the RadioComm patch and the four corner touch trick to bypass the setup wizard.
(Starting in the upper left corner, simply touch all four corners of the visible screen in a clockwise rotation, ie: upper left, upper right, lower right then lower left).
*** SOLUTION ***
--------------------------
Hey all, just got my D4 in the mail today and have been trying to get the GSM functionality working for a few hours. I live in Canada, bought it used from eBay and so I don't have a Verizon account, nor do I have access to anyone with one.
I had no trouble at all using RadioComm to change the 8-byte string as per the threads on this and a few other forums, but I'm still getting the "This SIM card is from an unknown source" pop-up when I click the Android to begin the initial setup of the phone... and there is no way I can find around it.
I can see the signal bars now that I have a micro SIM that I've activated with my carrier (Bell Mobility) inserted into the microSIM slot in the back of the phone, but it still doesn't want to let me boot up. The only options in the pop-up telling me about the Unknown SIM are either Emergency Call or Power Off.
Anybody have any ideas? I've tried flashing up to the 219 fastboot as well with no luck, and of course applied the RadioComm edit immediately afterwards. I have a feeling that the phone only needs to be initially setup and then I'd be able to boot it up, because as I mentioned I can see that it's getting a signal but doesn't want to let me get into the initial user setup.
(And no, I'm not a n00b. Check the Droid 3 forum... )
Forgot to mention that the eBay seller didn't include their SIM so I don't have a Verizon micro SIM card, unfortunately for me. I have a ****ty feeling that I need to have one in just for the initial device setup then I'd be able to swap it out.
Argh!
You don't need a SIM to go through the setup process. Try it without a SIM. When you've completed the process reboot with the SIM and try to change the network manually. The SIM is unknown pop-up won't go away, I can tell you that much. When I was on 215, 219 and even AOSP/AOKP the pop-up came as soon as I entered my PIN. So don't worry about that. Sometimes it took a few minutes to get a signal. Recheck with RadioComm.
I had Safestrap on my system and that worked immediately. But the non safe system would not connect. Only after a couple of days. I can't remember if this is because I modified my build.prop.
If you're willing, you could try the ICS leak. I applied it and am very happy with it. It has settings for CDMA/GSM/World. Worked right away (had to setup APN). As you may have read, updating COULD take you off the official update path. But for me it was worth it.
It won't go anywhere but the screen that says "SIM Unknown"; the only two options it provides are two buttons on the bottom of the gray screen with the aforementioned message to either go into Emergency Dialer or Power Off. It's really frustrating! If I could just get past the setup part, I know this will work.
I can see the signal bars and can receive calls and receive texts (as well as reply to them, but I can't initiate them).
It also says Bell in the notification bar.
I am pretty tempted to do what you suggested and was debating it earlier, but haven't been able to get a concrete answer: has anyone tried to flash back to .215/.219 after applying the leaked update?
Yes and you will softbrick your phone! After updating to ICS the will phone run on a new kernel. Flashing SBF with an older kernel won't work.
The only thing I can think of is boot without SIM. Then edit your build.prop (you will need root). And hope now you can click "OK" at the bottom of the Unknown SIM pop-up.
Try chaning this in build.prop, reboot and check if you're able to click OK when the pop-up appears:
ro.default_usb_mode=2
persist.ril.modem.mode=2
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.gsm-routes-us-smsc=0
These are the values I changed (apart from increase heap and wifi timing). Hopefully now you can click on OK so the screen goes away.
That's the problem, though, I can't edit any files or change anything because I can't get past the setup screen. I appreciate the help though!
I've tried without a SIM inserted and it just says it needs to have one, then prompts me to either Power Off or Emergency Dial, just like the other message about the Unknown SIM.
At any point in time did you ever have a Verizon SIM card inserted in your phone? I'm really perplexed about this one.
I don't think I'm going to try flashing the ICS leak just yet, just in case. Especially if it's not presently rootable.
I'm sure I'm not the only person this has or will happen to, I bought the phone from an American owner on eBay but I live in Canada and have inserted a Canadian GSM/UMTS carrier's SIM inside.
Nobody from Canada, either with Telus, Rogers or Bell with a D4 out there that managed to get it working?
Well, I plugged away at it long enough and finally managed to get past the initial setup screen, at least into the Settings menu so I could enable adb and installing unknown apps. That's all I needed...
Eventually a Smart Actions notification popped up and actually allowed me to set up a Smart Action without going through the setup, so I just made one that inevitably let me into the Settings menu and that was all she wrote.
Weird that this was happening though. I clearly have the GSM functions working as I can make and receive calls, but the phone is acting as if it is still locked and doesn't want to operate with a non-Verizon SIM.
I'm running .219, in case anyone was wondering.
But now you're passed the screen right? So why not root and try editing the build.prop. Like I wrote, this is all I edited and was able to use the phone with and without a SIM in it.
I did have a Verizon SIM, but I took it out at some point, before I had GSM working! It took me some days to get GSM working on 215 and 219. Wouldn't work without the edited build.prop! If you're afraid of testing, install safeboot. Then flash 215, update to 219 and use that one for testing.
You can bypass the initial setup screen by touching the four corners of the screen going clockwise starting at the top left. That will allow you to use the phone normally after that, but the unknown SIM error will persist.
cellzealot said:
You can bypass the initial setup screen by touching the four corners of the screen going clockwise starting at the top left. That will allow you to use the phone normally after that, but the unknown SIM error will persist.
Click to expand...
Click to collapse
I knew I remember hearing that somewhere. You sir, are a lifesaver. My previously mentioned workaround was okay but this is significantly easier. Especially considering I bootlooped my phone tinkering with build.prop settings and wasn't able to luck out and get that Smart Actions popup while stuck at the initial setup screen.
Thanks a million for your help!
(You too, Die Bruine. Trust me, I'm not afraid of making build.prop tweaks, I've been at this game for a while... )
Related
My Nexus was on 5.0.41, all working sweet, then it stopped "finding" the network. No update, flashing or anything was done prior to the problem.
I tried a SIM from another provider, but still - the "No Service" is written on screen, and when I try to search for networks, it says "Error searching for networks".
I then tried the following ideas (nothing helped):
- Reflashed the Radio image.
- downgraded the Radio image.
- Upgraded it again.
- Flashed the Stock ROM (unrooted and rooted).
- Flashed CM5053.
All was done with wipes as needed.
Any suggestions will be more than welcomed!
Can the device just get bricked like that? with no reason?
It sometimes identifies the SIM's provider (Orange for example) but always with No Service.
It sounds like your SIM card slot isn't holding the card in tight enough to make full contact... try putting a business card, cut down to size, between the SIM and the phone's frame (note, not the contacts side, but the back side) to force the SIM down onto the reader tighter.
If that does nothing, not sure what to tell you?
it didn't help
I'm Italian and I have the same your problem .. I only work in 2G GSM'...ve tried to see if you do so?
I opened another tread here Forum
You need a new SIM.
I just had this problem on Friday. The SIM some how falls of the network and your provider network will not allow it to reconnect.
I can't remember, but if I am right Orange is owned/owns by T-Mobile. Hence they have the same network.
The puzzling part about this is why it happens. This is the second SIM I have gone through with my N1, I also had one go with my G1, my sister bought that G1 and the SIM went out again. My mom bought her G1 same day as me and hers has died once. My friend has a MT3G and his has died two times now. I find this extremely annoying.
I tried every suggestion on the internet for repairing or troubleshooting a SIM. It is a waste of time. Well, everything short of dropping it in isoproply alcohol to clean the contact.
I tried a 2G and a 3G SIM on mine, and had the same result, so my problem is different.
My device just doesn't register with the network, no matter what provider or SIM generation I choose.
Can I ask for a RMA if I unlocked the bootloader?
I do not know you definitely do not pass it under warranty
Ryan then you say you clean the contacts of the nexus or the sim with isopropyl
Mine is now doing that as well and so far everything that I tried isn't fixing it. I get it to connect briefly with edge and then nothing. I am going to try a new sim tonight after work and see if that helps, otherwise unsure of what to do after that...anybody got any answers or suggestions?
I've been suffering from this... have an RMA coming but I got mine to work. Make sure you also have CDMA preferred on there or whatever the default is. If it says unknown you have to reboot the radio somehow. I pulled my battery, waited 5-10 seconds. Then i went and checked airplane mode on and off. Then i checked the service menu again. I can't remember if i had to pull the battery another time but it came back from "unknown" to cdma preferred. You can also try turning the radio on and off via the service menu. Finally select your radio bands for your region by pressing the menu button under phone information again in the service menu and select radio bands. I'm not sure if automatic is a good or bad idea but it couldn't hurt testing it if you still have some issues even after selecting your region specific bands. After this you should be able to maybe search and register or you may need to turn the radio on and off again via airplane or the service menu. I played around with it alot to get it running again.
Also I'm tmobile usa using the one for t-mobile bands. I'm not sure if CDMA preferred is a world wide setting or if its gsm or something else.. but the bands are specific to your region definitely.
I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
a quick history of what I've done so far
Sumsung I897 captivate from ATT unlock and being used on Telus network was working great for about 4 days, then all kinds of problem started cropping up.
Phone came unlocked, I rooted using update.zip from xda, installed rom manager and started removing ATT bloatware, entered SMS and APN info which worked fine.
Yesterday I noticed that where I once got good reception I was now getting nothing and would have to drive down the street before I would get something descent. I thought maybe I'd put it back to stock with rom manager and see if that would help which it did not. It actually made it worse, decided to go all out and use the Odin3 one click downloader just to make sure I was back to stock firmware. This didn't work either but now I can enter the SMS and change the preferred network type but it doesn't save. Preferred network type is grayed out and even though I can change it it never save same as SMS.
Now I can't hold connecting in my living room where my wifes Milestone gets full bars. I tried taking the phone to where I had the best signal and change the preferred network, SMS, and set the network operator but it doesn't save any info, can't find on operator half the time on manual or auto and gave me an error and logged it to #*9900#
I've been at this for 2 days straight and can't figure out how to get it right back to stock, it seems to keep hanging onto the same preferred network and not saving anything I enter.
What can I do to get back to stock, and it has to be something that wipes everything clean, clean, clean, because even the GSM disconnects stay logged under *#*#4636#*#*
***I desperately even tried pulling the batt and SIM card for the night in hopes that would do something.
So, if I'm understand what happened correctly, you bought an unlocked Captivate, rooted it, deleted some bloatware, entered your Telus APN info and everything worked awesome for about four days. Now everything has gone down the hole. Is that right?
If that is the case, then we need to figure out what changed. Using Odin3 would have definitely put you back to stock/unrooted your phone, I don't think you could go back any further than that. If I were you, I would act like I first got the phone. As in, I would do everything you did to it, as if was day one. At one point, everything worked fine. Try to recreate that. You can always look into exchanging it or perhaps Samsung customer support can give you a little more insight to what's going on. Here's the number if you want to try them out.
Samsung customer service - 1.800.726.7864
Thanks, I've gone through the process a few times today from start to finish trying to figure it out ... maybe some of the problems aren't real problems and just limitations that I didn't know where their. I've since flash with odin3+re-partion to the bone stock i897UCJF6 as in not the one click method. It loaded fine but still have the same issue, I can't set preferred network type or get it to keep the number entered into SMSC. I think if I can get passed that I'll be be one the up side of winning. I keep noticing that the log of GSM disconnects never clears or the usage statistics under *#*#4636#*# , I'm thinking its in the same area that other bad data is being held onto instead of being cleared when flash firmware or factory reset.
Is anyone able to change preferred network type? maybe I was never able to change it but I think I should be able too.
I may be wrong in assuming this but I don't think ATT is going to be interested helping me connect one of their handset that I'm trying to use on foreign network, but I could be wrong and is an open option.
*#*#197328640#*#*
debug screen
phone control
network control
band selection
wcdma band
wcdma all
menu->end
used this to lock my phone to WCDMA only so that problem is solved
*** never mind posted to soon it still didn't stick after rebooting
be carefull using the service menu as I have no idea what most of this stuff does
I got the SMS service number issue fix by taking out my sim, swapping in another known working sim from the same network, setting the service number, pressing update and then swapping back. Before every time I tried to update the service number it spit out an "update error" can anybody tell where the SMS config data is stored? on the phone or sim.
The only problem I'm having now is with reception which maybe fixable if I can set the preferred network to WCDMA only. But the button for that option is a light blue colour vs other phones that I can change this setting on. Does the blue mean anything like a locked function or something that set by the firmware as unchangeable?
I'm unsure if my problem has to do with Verizon or if I need to run a factory reset or try other options. Here's my story:
As soon as the phone arrived today, I unlocked, rooted, and flashed TWRP. No sim was in at any point since I didn't have a nano sim to use for it.
I tried cutting my Galaxy Nexus micro sim into a nano sim (apparently this works for some people), but the N6 states "no sim card - no service" so I don't think it worked.
Went to a Verizon store and got a nano sim for 28 cents, but the clerk couldn't activate it or bind it to my account since Verizon doesn't have the N6 IMEI numbers in their database. He told me to call support. Support was actually helpful, somewhat knowledgeable at least, and tried to activate the sim card over the phone.
Apparently the sim is pending activation from the phone, but I'm still getting the "no sim card - no service" errors. Does anyone know if this error means that it can't connect to the network, or if the phone thinks the sim is physically missing? There seems to be only one way to add the sim to the little tray as far as I can tell (gold face up, matched corner).
Has anyone else had similar issues? Should I try reverting (unroot/stock recovery/etc)? I'm not sure what the best approach is to activate the sim as I'm uncertain if the issue is still with Verizon or the N6.
EDIT: Everything is working now. For those of you moving from a phone with a micro sim, all you need to do is:
1. Cut the micro card down to the size of a nano
2. Drop it in your nexus6
3. Make sure wifi is off if you've already run through the setup. This was my mistake!
4. Give it a few minutes and you'll see the mobile icon flash LTE
It may help if you change your mobile network settings to LTE preferred.
Same thing happened to me. Did you try spinning the sim card around? The notched corner didn't look so much like a notch by the time I was done trimming...
Larzzzz82 said:
Same thing happened to me. Did you try spinning the sim card around? The notched corner didn't look so much like a notch by the time I was done trimming...
Click to expand...
Click to collapse
Interesting. I trimmed off all the white plastic on the left and right sides so that I can rotate it or even flip it over. Going to try a few permutations... nothing yet. That's all it took eh?
That's all it took for me. Everything works. Data, voice, sms,mms... Everything.:good:
Larzzzz82 said:
That's all it took for me. Everything works. Data, voice, sms,mms... Everything.:good:
Click to expand...
Click to collapse
Still no dice. The gold face should be face up, right? I noticed that after a few minutes the error changes to "selected network unavailable", so maybe I'm putting it in right but now its just not being registered.
So far in my experience that message means you need to nuke and repave, including userdata.....YMMV
EDIT: Probably easier to get a new SIM from VZW, thats what I did
cmh714 said:
So far in my experience that message means you need to nuke and repave, including userdata.....YMMV
EDIT: Probably easier to get a new SIM from VZW, thats what I did
Click to expand...
Click to collapse
Thanks, I'll try a factory reset. I'm only running stock... can't imagine root or custom recovery would prevent the sim from being recognized. Perhaps when you click "skip" for the sim card part of the setup it can never be reconciled.
Factory reset didn't work either. Really irritating, it looks like the N6 that shipped from the play store came with android 5.0 instead of 5.0.0 or 5.0.1... possibly a development version from months ago?
I flashed the latest 5.0.1 factory images (boot, system, radio), then flashed TWRP, then did a factory reset to wipe data. At the setup prompt when I rebooted, it still says "insert sim card".
I'm not sure what else to try. If the sim card isn't activated I can't tell if that's why it wants me to insert a card, or if it physically thinks it is missing. I may need to order a nano sim to micro sim adapter, then put that in my old gnex and activate it that way, and finally move it over to the N6.
Does anyone have any other ideas or think I may have overlooked something?
mordrukk said:
Factory reset didn't work either. Really irritating, it looks like the N6 that shipped from the play store came with android 5.0 instead of 5.0.0 or 5.0.1... possibly a development version from months ago?
Click to expand...
Click to collapse
All of the stock shipped with 5.0 so far. Not 5.0.0. 5.0.1 update notification "should" arrive after initial bootup
Contacts screen side up. It took a while to get onto the network initially. .#.#4636#.#. On the dialer opens a testing menu. There is a drop down menu, middle of the phone info page. Mine is set to lte/cdma auto
Thanks, never knew about hidden dialer apps. I set mine to the same. It's been a few hours and still no connection, so I'm going to assume the fact that the sim isn't activated is what's causing the phone to believe it's not inserted. I really need another phone to test with... if the sim card can be activated or work on another device, and still doesn't work in the N6, then it'd be a hardware problem.
Also good to know 5.0 is standard.
Update: I tried using the cut micro sim again, but this time turned wifi off. Looks like cutting the micro sim worked after all. I'm somewhat recognized by the network, but the sim used no longer maps to my account, so I'm getting a verizon webpage stating "device error" and to call customer support. I think if I can get verizon to revert changes made on my account yesterday back to the gnex with my old sim that this will work.
Moral of the story - cutting micro sim cards will work, but turn off wifi when trying to test your sim!
I'll report back once this is finally resolved. Hopefully this helps someone else.
Got it working - just had to get a new micro sim for my gnex, re-activate that device, then I was able to cut it down to nano size and load it into my nexus6. With wifi off this time, everything worked, and it connected to the network.
I've updated the original post with instructions for anyone else who might be having this problem.
Hello all.
I got myself an used SM-N950U originally from Verizon and sold as unlocked. Now my problem is I cannot connect to/use my sim with it. Originally I thought it was locked since there's an app that says "not a Verizon sim", but then I realized this app is an userspace app so to say, part of the Verizon bloatware and doesn't mean the phone. I know specially since with that phone I also got an S10+ from a friend, also from Verizon, which does see and use my sim right and which also has that same message from the same app. But works well.
Now, I don't really have the option to return this phone, since it was shipped outside the US, and shipping back would cost me half as much as what the phone cost. So I'm on my own.
At least I'm resourceful, but not that knowledgeable so that's why I come here for help.
The phone diagnostics, for the network, says in a status line "Radio off". and no info on the network. and if I try to manually select a network on connection settings, I immediately get an error. This happens wether I'm using my local sim, the old deactivated Verizon sim from my friend, and no sim... since the phone should be abe by law to make emergency calls, and it should be able to see visible networks even if not to join them, it's my guess that rather than locked, it has the radio turned off, which in some web pages says can sometimes happen "for various reasons".
My problem is, as far as I know, I have no way to turn the radio off and on again to see if that boots it up. Since this VZW Pie from has no service codes available via dialer. Not even the most basic *#06# service menu.
I see there's supposedly a way to flash the firmware back to Nougat, and root that from, on This thread. I'm guessing if I can make that work (I hope it works) I can access the service menus somehow, with it being an older rom, and having root I can probably use "Phone INFO" to get to them and try to reset the radio.
But before I do all that, and since my firmware downloads, to update to a new firmware via odin (given the warning on the root page to not use a v8 bootloader that was updated from v7 to v8 via OTA but rather something with v8 flashed directly via Odin, to avoid a possible brick). and to install the rooteable nougat will take me days to download at my speeds, I take this time to ask for help on wether there's ANY way to check and flip the radio without having to go to Nougat and root (I think I can even be happy without root on Pie for a short while.)
Ok, I'm starting to think the power connector board got damaged or the connector partially disconnected during the shipping or something.
I've installed first a N950U1 xaa rom, to make sure the v8 was installed via odin and not OTA. Then loaded a combination from and rooted as per the root post shared in the first message. This one can use service codes with the factory time (I've not installed a normal rooted nougat rom yet, as I want to do tests beforehand and try to make the radio work).
Inside *#0011# My IMEI shows as passing, but I get an ASM MIPI DEVICE FAIL:
ASM MIPI DEVICE FAIL
DEVICE MOD=0x217 , PID=0x081
Non-Fatal MIPI DEVICE FAIL
DEVICE MOD=0x217 , PID=0x081
ASDiv : NOT SUPPORTED
Click to expand...
Click to collapse
I tried running the Samsung Mipi Repair Tool, it detects the info, I hit repair, says it's repaired and that it'll open a menu, which does NOT open. Yet, if I open a menu with *#27663368378# and then rebuild NV with: 2. Ue Setting Info-->1.Setting-->2.System-->3.nv rebuid-->3.all, and then turn the phone off (Factory doesn't seem to have reboot) and on, still the same MIPI issue.
So I'm guessing either the board around the charge port got damaged somehow during the trip (my friend tested the phone before shipping it to me from the US), or the connector for it got loose. Anyway, I'm worried I'll have to open the phone myself (I haven't found a trustworthy tech in here. Last time I took a phone to a "recommended" tech, they stole the OEM screen from my dad's J8. So, no more techs for me unless I can find one I can befriend, and trust). If the connector to the board is not lose (I'll reseat it) I'll have to look for a new board, either abroad or here, probably not oem and with a lousier usb-c port, and swap the boards... sigh.
Anyhow since this will take time, if anyone knows of any other program or procedure I can use to test things, please let me know. I will keep the factory rom on the phone, either as the sole one or in a rom slot in safestrap, so that I can keep doing tests.
I appreciate any hints or help anybody could provide.