[How To] Fix Roaming / Broken Activation After CM 10.1 Update

[funkymonk101]

Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed

Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)

Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.

1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself

You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.

Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.

 

[rossida]

Intro
The info on how to do this is scattered around, thought it might be good to have a post for this, was really annoying for me to get this fixed

Problem
After upgrading to the latest Cyanogenmod 10.1 (cm-10.1-20121224-NIGHTLY-d2vzw.zip), the phone will not connect to the cell network. Some symptoms of this:
- Cannot send/receive text messages
- Cannot make calls, all calls give error "Your account is not authorized to make calls to this phone number"
- On boot, activation starts ("Waiting for network...") but cannot complete
- In Settings -> About Phone -> Status, you see the following info:
-- Roaming: Roaming
-- Mobile Network State: Disconnected
-- My phone number : 000-000-0311 (or similar)

Solution
I tried a number of solutions, but the only way I've seen to fix this is to revert to stock ICS using Odin, then perform a full factory reset. Please note that you will lose ALL data, including anything on the internal storage. The SD card should not be touched. You will also lose your unlocked bootloader, although that is easily restored.

1. BACK UP any data you might need, including clockwork/titanium backups, get them off your phone
2. Follow instructions here to flash the rooted ICS image (stock.vzw_root66.tar) using Odin. The torrent is much faster to download the image.
3. If your phone goes into a boot loop (stuck on the LTE boot logo), boot into stock recovery (Vol Up + Home + Power) and clear data / factory reset
4. Boot up the phone, go into the dialer, type: *2767*3855#
5. Your phone will immediately factory reset itself

You should now have cell connectivity again, and should also have root. You can then unlock your bootloader (get v1.2 here) and finally use Clockwork to re-install another ROM.

Note that after doing the above to restore my cell connectivity, I tried to do a clean install of CM 10.1, with full data wipe and such, and I once again lost cell connectivity and had to factory reset again. It seems to me like something is very broken with CM 10.1 for the VZ S3, and until it's figured out I recommend staying with CM 10.0 (cm-10-20121216-NIGHTLY-d2vzw.zip), which does not appear to have this problem.

easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)

This should now let the ur phone have access to the network and get rid of the roaming issue.

 

[pupsinmytub]

Same problem

Having this exact problem. My problem is I do not have access to a windows computer and thus cannot use Odin. I have already performed a Factory reset so I may try the way that involves removing the sim card. I dont know how more people haven't posted on this yet...

---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------

easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)

This should now let the ur phone have access to the network and get rid of the roaming issue.

as far as I can tell this does not work. You must have a sim card to get past the second screen in boot up. There is no other option besides to turn of your phone.

 

[joebob296]

Thank you for the help! My phone as been out of commission for the past 2 days and the OP directions fixed it. However the second post did nothing to help out. Worth a shot though

 

[pupsinmytub]

Does anyone know if this can be done from a Mac?? I am a little desperate here. Ive spent most of Christmas day messing with this.

 

[BigErnM]

You'll have to find a Windows computer, or install a windows virtual machine using vmware fusion or parallels desktop.

 

[killerkiyoshi]

will this work for us cellular??

 

[jas88]

easier way is If you remove ur sim card and boot up and connect via wifi, u can then register and set up the phone. then shut down put sim card back in and boot up. go to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)

This should now let the ur phone have access to the network and get rid of the roaming issue.

This has happened to me twice. The second time I used this method and it worked for me. It was only successful when I switched to the executioner 2.5 rom which was on my sd card. Thanks!

 

[killerkiyoshi]

Nvm fixed it

 

[LLStarks]

*wrong thread*

 

[pupsinmytub]

Nvm fixed it

How???

 

[pupsinmytub]

Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas

 

[ajrty33]

Okay, finally have my service back in stock touchwiz. This is what I did for anyone that cares to know: In CM10 during "activation" I pulled my sim card out, let it finish activating, powered down put sim card back in. Then I booted it back up and went to system settings -> More... under wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV). THEN I did a factory reset in CM10 making it look as if I had just flashed it again. Then I booted into recovery and went back to stock TouchWiz where my 4g LTE came back magically and I could call and place texts. Not really any rhyme or reason but my service is back and I am beyond pleased. I am very nervous to flash any roms as of now I might wait til tomorrow luckily I have all my stuff backed up Hopefully it stays this way. Message me with any questions and I will help as much as I can. Merry Christmas

Yall all need to chill out. Just fix your mobile network settings, toggle airplane mode, and you'll be fine.
You have no reason to fear flashing any roms.... With common sense.

Sent from my SCH-I535 using xda app-developers app

 

[nevrlow]

Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:

Sent from my SCH-I535 using xda app-developers app

 

[micahansel]

None of this has worked for me. I have followed the post directions and still have roaming. I am not seeing this option some of you are talking about though " wireless and networks -> mobile networks -> CDMA subscription and choose RUIM/SIM (NOT NV)"... is this option supposed to be in the stock ics rom?
Update: the line had been suspended for some very odd reason

 

[randybennett23]

Got it working on VZW SG3 for now

This worked for me:

Reboot to recovery and fix permissions (not sure if this step helped just following some other posts) --> change mobile networks to the sim option ---> and most importantly enable National Data Roaming (this is the step that kicked over my signal)

After doing this it has started to let me call out and receive sms. My only concern is what consequences will i have with the national data roaming enabled and secondly when I am in other networks if I will get better signal; i live in a small town and get 1x so I have no idea what will happen till i get into the city but this seems to be a good fix for now. Hope this helps.

 

[dougmac]

Tried all posted solutions and then some, still can't get CM 10.1 working on d2vzw

All,
I have a stock-rooted SCH-I535, and am also unable to get CM 10.1 working without losing the voice connection. It appears that my problem is corrupted NVRAM. Although my IMEI remains correct after flashing 10.1, my phone number and other info (ERI) gets corrupted. After a day of anxious attempts to fix the phone, the only fix I've found is flashing root66 (after which the phone still doesn't boot to the OS), factory reset (allows phone to boot), and then dialing factory-reset code *2767*3855#. For some reason the dialer-initiated reset seems to fix the NVRAM issue while the recovery-initiated reset does not.

After figuring out how to fix the problem, I've tried a handful of ways to get CM 10.1 working properly.

• Original try: flash 10.1 over rooted-VRBLK1 using TWRP 2.3.1. After fixing by flashing root66, recovery factory-reset, and dialer factory-reset, I was nervous and made a couple backups.
  • used the su ; reboot nvbackup commands in this RootzWiki post.
  • Made a QPST backup with the instructions in this XDA post.
• 2nd try: factory reset, wipe data/system partitions, re-flash 10.1 with TWRP. This attempt had the same roaming/corrupted phone info result, but this time I was confident because I was armed with the two backup methods above.
  • I tried using the Samsung MEID RepairV3.5 in this XDA thread, but it wouldn't connect to the phone running CM10.1. I've gotten that tool to connect to the root66 image, so I know I'm following the procedure correctly. However, the developer specifically states that the tool is intended for stock images, so I wasn't surprised that it failed to work on CM 10.1.
  • with su privilages, I used terminal command "reboot nvrestore". I expected this to work, but it resulted in an unbootable OS. I had to flash root66 and repeat the fix process described at top.
• Third try: flashed 10.1 again with TWRP 2.3.1. I tried using the QPST recovery I had created earlier. I got the phone into diagnostic mode (RMNET+DM+MODEM) using terminal commands for AOSP ROMs. For some reason I couldn't get the scripts to work, even with full permissions in the "root" directory -- the script resulted in the phone disconnecting from my computer in MTP mode, but it didn't connect in diagnostic mode. Terminal commands did the trick though -- I may be making some n00b mistake with the scripts. After typing the commands in manually and connecting to QPST, when I told QPST to "restore" the backup, it gave me an error message with incompatible phone, and if I checked the "allow phone/file ESN mismatch" box, the restore failed because the phone didn't respond to the QPST commands. I'm sure the phone was in diagnostic mode because it came up under Device Manager "ports" as depicted in the QPST instructions, so it seems like the corrupted NVRAM was causing problems with making a QPST connection.
• Fourth try: TWRP update to 2.3.3.0. Same results as 2.3.1.0.
• Fifth try: switch to clockworkmod touch recovery 6.0.2.3. Same result as both TWRP versions.

So, I'm pretty frustrated. I have the phone back up and running rooted-stock VRBLK3. I'd really like to get JB4.2 though, so if anyone can ID the problem, please post! I hope it's a simple fix from a n00b mistake, but after all the fruitless effort above, I expect that it's a more significant issue.

One last thought: I always rebooted into recovery to install the 10.1 image, and I never tried using the ClockworkMod ROM Manager or TWRP-compatible GooManager apps. My wife is tired of me spending the holiday weekend hunkered over my phone, so if anyone wants to try that route please let me know if it works.

The only other idea I have is to install 10.1, then try flashing the VRBLK3 baseband by itself. Again, I don't have the time to pursue this idea (or expertise to know if it's a good one), so any good insight would be appreciated. One last thought: personally, I'm not willing to wander around in voice or data "roaming" even if everything else is working fine. I rely on this phone for daily use, and am not comfortable without the radios working normally.


Happy new year!

 

[michaeldizzowns]

thank you. can confrim this method to work for a verity of roms. ha.

 

[weasleSS]

Flash cm10.1 go to settings/networks/cdma subscriptions and change it back to RUIM/SIM. U haz data now. :thumbup:

Sent from my SCH-I535 using xda app-developers app

This worked, just reboot the phone after you make this change and you'll have your activated phone back with voice/data. :good:

 

[Xgame2k10]

No Service

I flashed CM10.1-m a few days ago (using this method to root and unlock bootloader http://forum.xda-developers.com/show....php?t=2046439 then flashing CM10.1-m through Odin), and my phone worked flawlessly for 2 days. It started to lag a bit during swipe-style text entry (no tracing line or predictive words appeared), so I rebooted hoping to fix the problem.

After reboot I lost all verizon service. The phone said "No Signal" or "Emergency Calls Only." The phone would not identify a mobile network, and no option for CDMA/LTE was available under mobile network settings, although verizon APN's were still identified. I think I lost my IMEI/EFS but don't know enough to be sure.

First I flashed stock VRALG1 android 4.0.4 without success. However after I flashed stock VRBLK3 android 4.1.1 my verizon service was restored.

I would really like to figure out how to keep CM10.1... touchwhiz is awful. Can someone confirm this problem can be fixed through one of the following methods? http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2&nocache=1

Also don't want to trip my flash counter... any idea at what point this would happen?