Here is what happened. I was on Viper rom and I flashed Paranoid Android and that was just to not sense for me. So I went to flash back to Viper and it just roams. NO SERVICE! So I reflashed, no dice. So I tried another sense rom a stock one rooted nothing. I relocked my bloader and flashed old hboot per .torrent thread and radio and recovery, I then factory reset from stock recovery per a post I saw by .torrent waited and nothing! My verizon sim works fine in my nexus and galaxy S3 but dna just roams. I tried swithching off and on airplane mode tried switching it to cdma everytime and just get the little triangle that mean its trying to roam. ANY HELP IS APPRECIATED!
jhr5474 said:
Here is what happened. I was on Viper rom and I flashed Paranoid Android and that was just to not sense for me. So I went to flash back to Viper and it just roams. NO SERVICE! So I reflashed, no dice. So I tried another sense rom a stock one rooted nothing. I relocked my bloader and flashed old hboot per .torrent thread and radio and recovery, I then factory reset from stock recovery per a post I saw by .torrent waited and nothing! My verizon sim works fine in my nexus and galaxy S3 but dna just roams. I tried swithching off and on airplane mode tried switching it to cdma everytime and just get the little triangle that mean its trying to roam. ANY HELP IS APPRECIATED!
Click to expand...
Click to collapse
Noone has a clue I guess?
Hey man, sorry to hi-jack your thread, but I've been having nearly the exact same issues as you. I flashed the 11/27 of CM10.2 which messed up my radio I guess, tried to rol back to my backup of the Sense 5 ROM by Newt, still had a borked radio. Anyone out there that can help us? For me, only cellular data doesn't work, wifi, and LTE oddly work, just can't make or receive calls or texts
FCO2011 said:
Hey man, sorry to hi-jack your thread, but I've been having nearly the exact same issues as you. I flashed the 11/27 of CM10.2 which messed up my radio I guess, tried to rol back to my backup of the Sense 5 ROM by Newt, still had a borked radio. Anyone out there that can help us? For me, only cellular data doesn't work, wifi, and LTE oddly work, just can't make or receive calls or texts
Click to expand...
Click to collapse
TOO funny, I just jacked your thread also. Or maybe it was one of the other 5 people with the exact issue we are having. I luckily have other phones though. I am wondering why I am getting so many views and no replies. Are we experiencing a common issue with the DNA? I have only had mine about a month but starting to wish I had backed out of the deal now. I love my DNa but I have to have a phone that works! DEVS< please help solve this problem.
Solved
jhr5474 said:
TOO funny, I just jacked your thread also. Or maybe it was one of the other 5 people with the exact issue we are having. I luckily have other phones though. I am wondering why I am getting so many views and no replies. Are we experiencing a common issue with the DNA? I have only had mine about a month but starting to wish I had backed out of the deal now. I love my DNa but I have to have a phone that works! DEVS< please help solve this problem.
Click to expand...
Click to collapse
SOLVED, after doing the ruu I went to bootloader and did a factory reset not recovery and it worked!
http://forum.xda-developers.com/showthread.php?t=2335945&page=2s
Related
Hey guys,
I am sorry if this has been answered already, but the search function seems to be unavailable for the past couple hours that I have tried, so I am just going to create a new topic. I had a stock ROM corruption awhile ago and was forced to finally root and install a custom rom on my 3D (which turned out to be a blessing) and decided on the Gangnam style CM10 rom. It has worked perfectly and been amazing compared to stock for the past week until now. Now my phone is not retrieving text messages at all. I have confirmation that mine send ok, I just have not been able to receive any. I have installed GoPro sms, I have wiped all data and cache and finally now I have done a factory wipe and reinstall, but nothing has worked! Is there an easy fix I may be able to apply to make this work again? Thanks guys!
This seems to happen to people sometimes. People have suggested flashing a sense 3.6 ROM and then updating the profile and prl. Then reflash Gangnam.
coal686 said:
This seems to happen to people sometimes. People have suggested flashing a sense 3.6 ROM and then updating the profile and prl. Then reflash Gangnam.
Click to expand...
Click to collapse
I am assuming I have to do a full wipe each time? Kinda a pain in the ass. Thanks for the reply man!
EEEMasta said:
I am assuming I have to do a full wipe each time? Kinda a pain in the ass. Thanks for the reply man!
Click to expand...
Click to collapse
Yes unfortunately. I've encountered this a few times. However, sometimes a full wipe won't fix the issue. If this is the case, re-flash your RUU, re-unlock your device, flash your hboot then reflash the ROM and you'll be good to go.
Drove me crazy a few times before I figured it out
Desperado24 said:
Yes unfortunately. I've encountered this a few times. However, sometimes a full wipe won't fix the issue. If this is the case, re-flash your RUU, re-unlock your device, flash your hboot then reflash the ROM and you'll be good to go.
Drove me crazy a few times before I figured it out
Click to expand...
Click to collapse
Darn, that sucks. I hope that is something that will get fixed at some point. Thanks for all the info guys, I appreciate it!
Having same problem. In the process of updating profile and PRL. Will get back to you.
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
okay so last night i was flashing Roms trying them out to see witch one would be my daily driver
but the problems happened when i flashed MIUI. Then I flashed newts one xxx and i had the roaming triangle on my signal bar
now when ever i try to use my phone it says no service and the 4G is pretty slow
I already went to settings > mobile network > and the setting in there and still no luck
im s on
HTC unlocked
any help thanks
is ur radio up2date ?
did u flash the ruu of global rom ?
No i havent how would i go about doing that
what is your hboot?
Option1:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Option2:
Go into mobile network settings and change to Global Mode. If already on global. Change to CDMA/LTE auto
EDIT
I posted in the wrong thread
Thank you all for your help
Flyhalf205 I flashed the recovery and factory reset and that worked. Thanks a lot
Flyhalf205 said:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Click to expand...
Click to collapse
It's many months since Flyhalf's post, but I wanted to report that after getting a replacement unit, I also ran S-OFF and htc dev unlock and pushed the radios forward to the latest and found that I could no longer make or receive calls, send or receive texts, although data/4G/wifi and BT were all functioning nominally. Tech support couldn't solve it; a new SIM card couldn't change things, and when I finally rolled all the way back to the last GB RUU, and FINALLY did a factory reset WITHIN HBOOT that cleared the problem. I then let the handset download the OTA's one by one to bring it up to speed.
I'm putting this here because I didn't find anything else for "no phone service" or "lost cell service" and was about to open a new thread in troubleshooting when I found this thread, followed Flyhalf's advice and I am now fully operational again. Hppefully someone else doing a similar search will see this post.
hgoldner said:
It's many months since Flyhalf's post, but I wanted to report that after getting a replacement unit, I also ran S-OFF and htc dev unlock and pushed the radios forward to the latest and found that I could no longer make or receive calls, send or receive texts, although data/4G/wifi and BT were all functioning nominally. Tech support couldn't solve it; a new SIM card couldn't change things, and when I finally rolled all the way back to the last GB RUU, and FINALLY did a factory reset WITHIN HBOOT that cleared the problem. I then let the handset download the OTA's one by one to bring it up to speed.
I'm putting this here because I didn't find anything else for "no phone service" or "lost cell service" and was about to open a new thread in troubleshooting when I found this thread, followed Flyhalf's advice and I am now fully operational again. Hppefully someone else doing a similar search will see this post.
Click to expand...
Click to collapse
I wanted to 2nd this post with a small addition. After S-offing my rezound and flashing the latest CarbonRom, I ended up losing 4G. I mistakenly though it was related to gaining s-off and performing a full factory restore and update. I was left with a phone that did everything but receive 4G signal. I had reliable 3G data and could make/receive calls/SMS/MMS. I only lost 4G data. After finding this post, thank you hgoldner for talking it up, I flashed the ICS RUU and then performed a factory reset. I probably could have just flashed the stock recovery but the Goo.im servers appear to be acting up and I couldn't download it from Flyhalf's link above. For those of you with signal issues following a custom ROM flash, I'd definitely suggest giving this a try.
ive been having same issue Network not availiable and also where i normally have 4g service i know only get 3g.Ive flashed several different roms still same issue.Could this be glitch in vzw AWS system?Is there any other radios we can flash? I notice that it take a really long time to do network hand offs too. Like I am talking a few minutes to switch from 4g to 3g or 3g to 4g. Signal bars show full, but there is not data and then they go gray and then it takes a few mins and they go blue.
basically im having the same issue as post #2 in this thread.
http://forum.xda-developers.com/showthread.php?t=2332500
It also sounds similar to this thread too.
http://forum.xda-developers.com/showthread.php?t=2292982&highlight=signal+issue
Is there something that can be done to test my radios, access point apns, etc.? I am on liquidsmooth 2.8 and have this problem ever since i got the phone (i bought it and flashed cyanogenmod last week). I also notice that under access points, i dont have anything listed and when trying to add an apn, and hit save, nothing happened
Anyone have any issue similar. I found some threads but they were not any help
Try getting a new SimCard. Those can sometimes go bad when being transferred from phone to phone. They are free anyways too.
im going to try that a little later today. thanks
Got the new sim. No help
dougmod said:
Got the new sim. No help
Click to expand...
Click to collapse
Should I sent you info to go back to stock?
DarkMenace said:
Should I sent you info to go back to stock?
Click to expand...
Click to collapse
Sure. If you think that'll help I would really appreciate it. So you think go back to stock and then reflash to liquid?
dougmod said:
Sure. If you think that'll help I would really appreciate it. So you think go back to stock and then reflash to liquid?
Click to expand...
Click to collapse
Possibly. Something could have been corrupted in the process. If it still does it on stock go to Verizon and complain.
i flashed back to stock and my download speed is 800 and upload is 85. it shows I have a 4g signal and the system status shows that my signal is -102 or -98.
anyone else have any ideas?
So things ive tried:
1. new sim.
2. back to stock touchwiz through odin
3. flash stock modem through odin and stock kernel
4. doing the whole process to root and stuff manually, then installed a customer recovery manually and then flashed a new rom, still no results
are we going to call this hardware failure? or is there any other reset type thing i can do
dougmod said:
anyone else have any ideas?
So things ive tried:
1. new sim.
2. back to stock touchwiz through odin
3. flash stock modem through odin and stock kernel
4. doing the whole process to root and stuff manually, then installed a customer recovery manually and then flashed a new rom, still no results
are we going to call this hardware failure? or is there any other reset type thing i can do
Click to expand...
Click to collapse
Most likely Hardware issue since all the steps have been tried. Unless it's only in your area. Have you tried to go somewhere else on a different tower?
yes i have. my s3 does not have any issues here, so that i why im guessing its the phone
Not sure which forum this should be in so i'm asking it here. Apparently, I can't activate my new sim card for the 4G unless i'm stock, unrooted, locked bootloader. I guess I jumped the gun after I got my phone, but before I got the sim card and rooted, unlocked, etc. I think I know the steps to take to get it back to compltely stock, but I want to make sure.
I think I need to run the script and relock the bootloader, then flash the stock RUU file.
Is that correct? Is that the correct order? Am I missing any steps?
Thanks a bunch for any speedy repsonses because i'm in a bind right now and have to get this resolved by morning.
flyinjoe13 said:
Not sure which forum this should be in so i'm asking it here. Apparently, I can't activate my new sim card for the 4G unless i'm stock, unrooted, locked bootloader. I guess I jumped the gun after I got my phone, but before I got the sim card and rooted, unlocked, etc. I think I know the steps to take to get it back to compltely stock, but I want to make sure.
I think I need to run the script and relock the bootloader, then flash the stock RUU file.
Is that correct? Is that the correct order? Am I missing any steps?
Thanks a bunch for any speedy repsonses because i'm in a bind right now and have to get this resolved by morning.
Click to expand...
Click to collapse
I'm pretty sure being unrooted is not a requirement. Just install this ROM and boot the phone with your SIM inserted. It should activate fine.
OK. I will try that because I am having a heck of a time getting activated on my CM rom. Even had a Verizon tech trying to help me for over an hour.
I see that ROM requires me to flash a new boot.img. When I rooted, the directions said to flash dirtyracuns Hboot. Will flashing this one effect anything? If I change ROMs, do I need to flash DR hboot again?
Thanks for the info...
flyinjoe13 said:
OK. I will try that because I am having a heck of a time getting activated on my CM rom. Even had a Verizon tech trying to help me for over an hour.
I see that ROM requires me to flash a new boot.img. When I rooted, the directions said to flash dirtyracuns Hboot. Will flashing this one effect anything? If I change ROMs, do I need to flash DR hboot again?
Thanks for the info...
Click to expand...
Click to collapse
Boot and HBoot are two very different things. Flashing different boot images will not affect your engineered hboot.
You definitely don't want to talk to vzw reps if you're running cm. The more tech support requests they get from users running non-official builds, the less likely they will be to ever allow phones with unlocked bootloaders on their system.
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
flyinjoe13 said:
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
Click to expand...
Click to collapse
LTE/CDMA should be fine
simlar problem
flyinjoe13 said:
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
Click to expand...
Click to collapse
I am having a similar activation problem. What did you do to fix the radio? My problem started a few days ago.
I found the RUU for just the radio and applied it. No change. I get a LTE signal but the phone doesn't know it's own number and thinks it is roaming.
I followed the steps in this thread to restore my radio: http://forum.xda-developers.com/showthread.php?p=45476579#post45476579
Unfortunately, I never was able to get the radio to work with any of the CM based ROMs so I have ended up using a stock based ROM. ViperLTE. It is an excellent ROM and works great, but I got the phone recently so that I could run CM ROMs. Had I known I was going to have so many problems, I would have waited until February when my upgrade date came up and got one of the newer phones. I guess I still can, but I'd hate to waste the money I paid for this phone so soon.
sim issue
Turns out my SIM was actually bad. When you looked in the about, the SIM id number didn't show up. It had worked under 10.2 stable for several weeks before it stopped working. It had gotten worse over a week or so. At first a reboot would fix it. I did a clean flash of CM 11 at this point. After replacing the SIM the id number showed up but still couldn't make calls.
The problem went away after restoring a CM 10.2 back that had worked. I then did a dirty flash of CM 11 over it, with the kit kat gapps. It all worked out fine. I am speculating that a clean flash of CM 11, might not work.