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.
funkymonk101 said:
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.
Click to expand...
Click to collapse
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.
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 ----------
rossida said:
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.
Click to expand...
Click to collapse
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.
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
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.
You'll have to find a Windows computer, or install a windows virtual machine using vmware fusion or parallels desktop.
will this work for us cellular??
rossida said:
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.
Click to expand...
Click to collapse
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!
Nvm fixed it
*wrong thread*
killerkiyoshi said:
Nvm fixed it
Click to expand...
Click to collapse
How???
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
pupsinmytub said:
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
Click to expand...
Click to collapse
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
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
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
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.
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!
thank you. can confrim this method to work for a verity of roms. ha.
vabeachfc3s said:
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
Click to expand...
Click to collapse
This worked, just reboot the phone after you make this change and you'll have your activated phone back with voice/data. :good:
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?
So a week ago I did a fresh install of Lollipop via the factory image for LRX21O, rooted it, and installed Franco's kernel #68. Everything worked great until yesterday as it seems I've lost all mobile data connectivity. I can still make phone calls and text messages, but data is a no go when mobile. So far here's what I tried:
Made sure the APN was Correct
Cycled Flight Mode
Cycled Power
Pulled & Re-Installed SIM Card
Cleared the Cache
Factory Reset
Re-flashed Stock Kernel
Flashed Android 4.4.4 Radio
Re-Flashed Lollipop Factory Image
Restored Previous known working install of Android 4.4.4 via TWRP
Made sure there were no billing issues with my carrier.
Anyone have any ideas? I'm especially concerned and convinced its not specifically a Lollipop problem (though that doesn't mean it didn't cause it) since it did not restore functionality when I flashed back KitKat. I've never used 3rd Party ROMs on this phone, only rooted stock. My carrier is SimpleMobile.
Ron Overdrive said:
So a week ago I did a fresh install of Lollipop via the factory image for LRX21O, rooted it, and installed Franco's kernel #68. Everything worked great until yesterday as it seems I've lost all mobile data connectivity. I can still make phone calls and text messages, but data is a no go when mobile. So far here's what I tried:
Made sure the APN was Correct
Cycled Flight Mode
Cycled Power
Pulled & Re-Installed SIM Card
Cleared the Cache
Factory Reset
Re-flashed Stock Kernel
Flashed Android 4.4.4 Radio
Re-Flashed Lollipop Factory Image
Restored Previous known working install of Android 4.4.4 via TWRP
Made sure there were no billing issues with my carrier.
Anyone have any ideas? I'm especially concerned and convinced its not specifically a Lollipop problem (though that doesn't mean it didn't cause it) since it did not restore functionality when I flashed back KitKat. I've never used 3rd Party ROMs on this phone, only rooted stock. My carrier is SimpleMobile.
Click to expand...
Click to collapse
Maybe you need to contact your carrier?
You're not alone, I'm having the same problem since going to 5.0. I use Red Pocket on AT&T's network. Can't get mobile data working at all. Contacted Red Pocket and they reset my data on their end but still a no-go. Wi-Fi fine, calls and SMS fine. MMS, like data, doesn't work.
I guess I'll pick up another MVNO card to make sure it isn't still Red Pocket's issue. I have another SIM, but unfortunately my T-Mobile card, which is usually in a Lumia 1520, doesn't work for data on the Nexus 5 because that is on their blocked list of phones (stupid carriers).
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
Click to expand...
Click to collapse
Try restoring via fastboot for a clean slate. I understand from your post that you're flashing via custom recovery.
gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day
Click to expand...
Click to collapse
CM12.1 may flash the new radio that OxygenOS flashes, from which there is not necessarily an immediate return.
Possible you have that new radio. See here:
https://forums.oneplus.net/threads/oxygenos-back-to-cm11s.296219/#post-10851703
gqukyo said:
So I've been flashing back and forth and restoring nandroids the entire day trying to troubleshoot and get xposed to work for 5.1. As of now, I've lost all cellular connectivity as in no cell service at all. Thought it may be my sim but I tried it out on my old Xperia Z1s and it works fine, sent text and tried downloading something from play store. Both worked fine so it's not the sim card (Tmo). I've been flashing and restoring both CM12 (last one available through the updater) and CM12.1 (4/18 nightly and just now 4/19 to try). Wifi works fine but there's no cellular signal/service. It's not acting as if there's no sim, it's acting as if there's no service at all, not even emergency cell signal. My guess is my modem is fried so I tried to flash the latest modem from XNPH44S but that didn't work either. I've searched the forums and googled but no one seems to have my exact issue. Most were either of stuck airplane mode or issues with APN settings. I'd be more relaxed if those were my issues as I'm really hoping I didn't fry my modem (hardware) flashing back and forth all day. Any suggestions?
Click to expand...
Click to collapse
Can you still see your baseband and IMEI? Go into Settings/About Phone for the baseband version and Settings/About Phone/Status for the IMEI.
Transmitted via Bacon
Baseband is unknown and there's no mention of IMEI anymore... does that mean I lost my IMEI/it got corrupted? Am I screwed? I planned on trying the fastboot restore but only as one of the last resorts. If CM12.1 use the same radio then my 12.1 should work but that doesn't either. Nothing works. I've tried CM11s, CM12, CM12S, CM12.1... sigh...
I think I had a modem/efs backup in one of my nandroids and I tried restoring that too with no luck
Restored one of my CM12 nandroids and now I have a baseband of "DI.3.0.c6-00230-M8974AAAAANAZM-1". For some reason or another, that doesn't look right to me even though I've never really paid attention to what the baseband ever listed. Still can't seem to locate my IMEI #. I did the #*#*4636*#*# and the cell radio is on and turning it off and one still only shows emergency calls only. Obviously I'm not going to try to call 911 just to test if the radio gets service. However, I can see my IMEI # so I guess that's good. I must have some bad firmware update. Guess I'll copy out all my stuff to my otg usb and fastboot restore and see if that helps unless there's something else I can try.... please let me know...
gqukyo said:
Baseband is unknown and there's no mention of IMEI anymore... does that mean I lost my IMEI/it got corrupted? Am I screwed? I planned on trying the fastboot restore but only as one of the last resorts. If CM12.1 use the same radio then my 12.1 should work but that doesn't either. Nothing works. I've tried CM11s, CM12, CM12S, CM12.1... sigh...
I think I had a modem/efs backup in one of my nandroids and I tried restoring that too with no luck
Restored one of my CM12 nandroids and now I have a baseband of "DI.3.0.c6-00230-M8974AAAAANAZM-1". For some reason or another, that doesn't look right to me even though I've never really paid attention to what the baseband ever listed. Still can't seem to locate my IMEI #. I did the #*#*4636*#*# and the cell radio is on and turning it off and one still only shows emergency calls only. Obviously I'm not going to try to call 911 just to test if the radio gets service. It really does look like it's my IMEI # that got jacked... what can I do now?.... :T
Click to expand...
Click to collapse
You've got a corrupt EFS partition. There's a thread detailing how to fix your situation in our general section.
Transmitted via Bacon
tried to flash the persist.img from http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 but that just prevents my phone from booting up properly. I only see the OnePlus logo with not Powered by Android on the bottom...
I take it back, it does show the powered by android but only for a split second then it stays on the OnePlus logo and doesn't do anything... :T
Restored back most recent cm12.1 nandroid and now I do see IMEI number in the about settings but still only emergency calls only... Guess its a good start, no sure what else I can do at this point.
Now you see your imei but you dont have the signal,it means your modem file does not work.So the first thing to do is backing up the efs then you can flash 44s modem and proximity patch.Probably it will work.It worked for me.
Ok there may be hope then. Just flashed the 44s modem then nandroided back to my CM11s then flashed modem again just in case lol. Don't recall seeing a proximity fix but it's ok as long as my cellular connectivity works, I'll deal w/ other issues later. Otherwise all I have is an expensive media player... lol it's booting up now so we'll see... *fingers crossed*
Nope didnt work...going to try a fresh CM12 install...
Trying to flash roms and in the wizards it always states I don't have a sim installed so I'm not sure it's my modem that's messed up or if it's something else related to hardware related to the sim. The sim itself works in my other phone... tried a different sim and it's still emergency calls only. don't know what to do now. doing all this and it's still not working so I doubt even the fastboot restore would work... might just have to rma... which would probably take 4eva...
Pls flash your nandroid backup which gave you the imei first,after gain your imei ,back up it,then you can flash what rom you like,if you dont have your imei,just flash your imei backup.The most important thing is to back up your efs.
Sent from my A0001 using XDA Free mobile app
Think my efs is fine as I can see the IMEI now but no matter what nandroid and fresh install I try, I can't get the cellular connectivity to work. I backed up all partitions just in case.
gqukyo said:
Think my efs is fine as I can see the IMEI now but no matter what nandroid and fresh install I try, I can't get the cellular connectivity to work. I backed up all partitions just in case.
Click to expand...
Click to collapse
Being able to see your IMEI doesn't necessarily mean your EFS is ok.
Transmitted via Bacon
Well tried the persist.img but that didn't work so what else can I do?
The one thing that would definitely fix your issues would be if you had an EFS backup. I don't know why people don't do this. Without that I have no idea what you can do.
Transmitted via Bacon
Never had that issue before and I've own android phones from the HTC Hero. Lesson learned though, thankfully it's still under warranty and it's not that expensive a phone...
gqukyo said:
Never had that issue before and I've own android phones from the HTC Hero. Lesson learned though, thankfully it's still under warranty and it's not that expensive a phone...
Click to expand...
Click to collapse
Not all Android phones employ an EFS partition. I'd never heard of it before this phone but a bit of research on my part revealed the importance of an EFS backup.
Transmitted via Bacon
That would make sense then. As I was reading about EFS, seems like it was mostly Samsung phones. I guess I can try a fastboot restore... nothing else to lose. lol
Doh! apparently there is something to lose when fastboot restoring... phone stopped booting back up correctly after a few fastboot restores and now it won't even turn back on... lovely... at least I had a expensive android media player before, now I have a brick... lol
Edited - Sorry
I have the same issue with all verisons of CM12. I get No service. Although the XNPH44S radio was the best. Meaning I could atleast see 3-4 bars for about 1 second and then off for a couple of minutes and then back on again for 1 second and so on. I believe it is a problem with not having a proper radio. One plus should release a better working radio in my opinion. I am on PTEL Mobile network (uses T-Mobile). So until we get a good working version of the radio I think some people like us are stuck on cm11.
I was originally going to use a custom Rom Havoc specifically. I am using the global unlocked model. After flashing stock rom using recovery tool and the flash all bat in the zip file everything is working on the phone except cell service The phone recognizes the verizon sim card itself but I have no data or signal. I tried using older 9.5.3 and 9.5.10 versions and it has made no difference. Factory reset has been tried as well and I still have no data. This is a big deal for me as my gmail account I use for my phone uses two step authentication. Is there anything I can do here or something involving needing to get TWRP back on my phone to resolve? Any help will be appreciated as I've spent last 2 hours trying to fix with no solution
It's also picking up my phone number and the information via sim card, but when I try to run a call/ send a text I'm greeted with a message that says To make a call turn off AIrplane mode. (Verified airplane mode is not on)
I"m not sure which thing I did that fixed it, but I flashed modem.img and also went to recovery and did a settings wipe not a full factory reset but just for the settings and it seemed to fix it