Related
UPDATE: So I just finished finals and drinking and have gotten around to my phone. I downloaded Galaxy S Unlock, but a beta version (it has a 'Signal Fix Problem' tab) that I was (and still am) and bit worried about. Well, my fears were quelled and I used it with an internet connection while on Bionix 1.3.1 and it didn't work on the initial reboot. Said the phone wasn't registering on the network. Didn't work on the second reboot. Didn't say anything, but data didn't work. I rebooted again and OMG OMG OMG OMG OMG it worked.
Glad to be back! Time for the latest CM7 nightly!
OLD:
The quoted posts fully explain my issue.
UPDATE:
Hung0702 said:
So I can confirm that the phone works for T-Mobile SIMs and gets 3g to boot. I relocked and unlocked my phone (both by manually changing the nv_data.bin and then with 'Galaxy_S Unlock'). Neither helped. In fact, Galaxy_S Unlock returned FFFFF as the SIM unlock code.
This leads me to believe that this is definitely not a hardware issue and definitely an issue with the EFS. I'm assuming that a proper EFS would not return a SIM unlock of 'FFFFF'.
If anyone has an intimate knowledge of our phones' EFS, please tell them that I need help in that regard. Or RIL, although I think RIL is in the EFS partition.
I'm on JFD via Odin and checked EFS Clear.
Click to expand...
Click to collapse
SUMMARY: I am currently bone-stock. JFD with root and nothing else. I usually get 3G (I live in the city) and excellent reception and speeds. Right now, I get good reception, but absolutely no data, nor can I call or text. It's stuck on GPRS and occasionally switches to EDGE for some reason, but it doesn't make a difference because I still can't call or text on either. IMEI shown in the settings matches that which is labeled behind the battery. My two fears are that the radio itself is somehow physically broken or that AT&T blocked my IMEI (tried other AT&T SIM cards and none of them would work). My SIM worked in other phones). Talked with an AT&T rep, he assured me that it is not AT&T's policy to ban IMEIs. Also, it may have to do with the EFS, but I'm not sure how to access it. Can't download ROM Manager right now because there's no WIFI around.
Does anyone have any suggestions? I'm pretty desperate right now. I'm borrowing a dumbphone and it's absolute torture to text on a 10-key num pad.
Hung0702 said:
MAJOR PROBLEM:
So right after I left such a sterling recommendation of this kernel last night, I started listening to some music, hit pause, left the ear buds plugged in, and went to sleep.
I awoke this morning to no missed calls, no texts, no emails. I was confused and looked at the signal meter and saw a small 'x' next to the bars. I installed the new CM7 (from scratch), and my signal problems persisted.
I just used Odin to get back to JK2 (Froyo) and still I have NO SIGNAL!!! I normally have full bars.
Does anyone have any recommendations? I don't know if everything I wrote is significant, but hopefully the extraneous details could help someone give better insight into this issue.
Click to expand...
Click to collapse
Hung0702 said:
Definitely not the SIM card. It works in other phones. I just wiped everything on the phone using CWM and the problem still persists. My fear is that the radio may have been in full-use all night without my knowledge and burned itself out. Although I'm not even sure if that's possible.
Strangely, I received 1 text message not too long ago. Couldn't reply, however; and still can't make/receive phone calls or access the internet.
Anyone aware of a way to do a complete reset of my phone? I don't think CWM and Odin are doing the trick. It needs to be absolutely bone-stock.
Click to expand...
Click to collapse
Hung0702 said:
nickmcminn60 said:
A simpler way is to:
1) odin to JFD with Repartition and efs clear checked and auto reboot UNCHECKED
2) unplug and replug usb then load ''Eugenes Froyo'' in PDA
3) Load same 512 file you used for JFD
4) Uncheck...auto reboot, repartition, and EFS clear
5) Hit start
6) when complete unplug the usb and plug it back in
7) load JFD and 512 pit into ODIN
8) Check repartition,efs clear and auto reboot
9) Hit start
Click to expand...
Click to collapse
Ok, you got me there. It doesn't do anything. Auto reboot has to be checked. Otherwise it just hangs at SetupConnection...
Thanks for the advice, but it didn't help.
Click to expand...
Click to collapse
Have you tried to flash another modem? or a factory reset? Have you toggled airplane mode and data connection? I had a very similar problem not too long ago. I flashed 4 or 5 roms and they all had the same problem. Flashed a few modems and nothing. Then I flashed one of Eugene's roms and it wiped my phone and it seemed to work after that. It could have been a coincidence, I'm not sure. I spent a whole day working on and it seemed to fix itself when it wanted to. Just keep flashing roms and tinkering and see what happens.
Hung0702 said:
The quoted posts fully explain my issue.
SUMMARY: I am currently bone-stock. JFD with root and nothing else. I usually get 3G (I live in the city) and excellent reception and speeds. Right now, I get good reception, but absolutely no data, nor can I call or text. It's stuck on GPRS and occasionally switches to EDGE for some reason, but it doesn't make a difference because I still can't call or text on either. IMEI shown in the settings matches that which is labeled behind the battery. My two fears are that the radio itself is somehow physically broken or that AT&T blocked my IMEI (tried other AT&T SIM cards and none of them would work. My SIM worked in other phones). Also, it may have to do with the EFS, but I'm not sure how to access it. Can't download ROM Manager right now because there's no WIFI around.
Does anyone have any suggestions? I'm pretty desperate right now. I'm borrowing a dumbphone and it's absolute torture to text on a 10-key num pad.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1045713&page=4
Refer to my post #33
Sent from my SGH-T959 using XDA App
deadpass said:
Have you tried to flash another modem? or a factory reset? Have you toggled airplane mode and data connection? I had a very similar problem not too long ago. I flashed 4 or 5 roms and they all had the same problem. Flashed a few modems and nothing. Then I flashed one of Eugene's roms and it wiped my phone and it seemed to work after that. It could have been a coincidence, I'm not sure. I spent a whole day working on and it seemed to fix itself when it wanted to. Just keep flashing roms and tinkering and see what happens.
Click to expand...
Click to collapse
rubbamade said:
http://forum.xda-developers.com/showthread.php?t=1045713&page=4
Refer to my post #33
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks for the directions, but it didn't help
I've flashed many different modems. Tried KA7 and stock for 2.3; JK2 for 2.2; and JI5 for 2.1. Nothing helps. Does anyone know how I would go about checking my EFS partition if I had a root explorer? How would I know that it was normal? What symptoms would suggest a problem? I wouldn't be able to browse it right now, but I may be able to tomorrow.
@deadpass
Could you try a tad harder to recall which of Eugene's ROMs you used? I tried his JK2 base to no avail. Do you know if his 'Froyo that doesn't brick' is any different?
Hung0702 said:
@deadpass
Could you try a tad harder to recall which of Eugene's ROMs you used? I tried his JK2 base to no avail. Do you know if his 'Froyo that doesn't brick' is any different?
Click to expand...
Click to collapse
It was Eugene's 2.2.1 rom, GCR3.
Bumping. I hope everyone understands. Going from Android to a dumbphone (DURING FINALS, TOO) is terribly inconvenient and disheartening.
Looks like I'm giving up. I'm really busy with Finals and don't have time to learn everything required to figure out how to fix my phone. No one is informed enough about EFS or RIL to point me in the right direction. I've really enjoyed having this phone since August, and I'm definitely going to miss the ROMs and enthusiastic community. Not sure what to do now. I planned on keeping the Vibrant and selling whatever I upgrade to in August. Still going to have to sell, but I don't get to keep the Vibrant
Good luck with your Vibrants!
Before you give up, do you mind trying my Back to stock guide verbatim... it's in my signature. Would like some feedback. It certainly would not hurt. No reason I can see why we can't fix your phone.
Shoot, send it to me and I'll send it back if you can't find time.
Wait, so this will get you to stock JFD on the Vibrant... but you said you are on AT&T... are you unlocking it again after you go back to stock?
I do not do this, but first google result:
s15274n said:
Before you give up, do you mind trying my Back to stock guide verbatim... it's in my signature. Would like some feedback. It certainly would not hurt. No reason I can see why we can't fix your phone.
Shoot, send it to me and I'll send it back if you can't find time.
Wait, so this will get you to stock JFD on the Vibrant... but you said you are on AT&T... are you unlocking it again after you go back to stock?
I do not do this, but first google result:
Click to expand...
Click to collapse
Hey! Kind of in awe to see you in my thread! Followed your guide ~10-15 time I had to flash. I've actually flashed via Odin probably 25-30 times since Saturday. Played with ALL the settings and your guide is good. No room for improvement!
Anyway, I've been using essentially the same procedure. Used Repartition and EFS clear on a few runs, but nothing different that I didn't intend to have a purpose. I used the files posted here; the MD5 sums check out.
People have been telling me it's a hardware problem (i.e. my modem is dead). While fully possible, I find it unlikely since I haven't seen a single dead modem post in any part of the Q&A, nor have I heard any suspicions of possibly failing modems. I could just be the lucky one, but again, that sounds unlikely.
Took my phone apart just to make sure all the connections are solid. SIM card board is securely connected to the antennae. Need to get an ammeter to ensure an electrical connection, though.
So I can confirm that the phone works for T-Mobile SIMs and gets 3g to boot. I relocked and unlocked my phone (both by manually changing the nv_data.bin and then with 'Galaxy_S Unlock'). Neither helped. In fact, Galaxy_S Unlock returned FFFFF as the SIM unlock code.
This leads me to believe that this is definitely not a hardware issue and definitely an issue with the EFS. I'm assuming that a proper EFS would not return a SIM unlock of 'FFFFF'.
If anyone has an intimate knowledge of our phones' EFS, please tell them that I need help in that regard. Or RIL, although I think RIL is in the EFS partition.
I'm on JFD via Odin and checked EFS Clear.
if you did the efs backup to flash cm7 shouldn't you be able to put that back on your phone??
Nothing will work until you follow this thread:
http://forum.xda-developers.com/showthread.php?t=761045
It helped me when I cleared my EFS
EFS contain network information like network lock, etc...
Good luck.
Exactly what I was getting at, odin and then unlock.
neobuddy89 said:
Nothing will work until you follow this thread:
http://forum.xda-developers.com/showthread.php?t=761045
It helped me when I cleared my EFS
EFS contain network information like network lock, etc...
Good luck.
Click to expand...
Click to collapse
Thanks for replying. That's actually the thread I followed in order to pull the nv_data.bin and use Galaxy_S Unlock. But like I was saying, it's as though the EFS is not working properly. I pulled the nv_data.bin and it looked like the phone was already unlocked (I'm assuming it is, because it never asked me for the SIM unlock code). I changed the nv_data.bin to locked (by changing the hex value at 181469 from '00' to '01', after which it did begin asking for the SIM unlock code), then used Galaxy_S Unlock to unlock. I also tried to retrieve the unlock code using Galaxy_S Unlock and all I got were a bunch of F's, not what I was expecting.
s15274n said:
Exactly what I was getting at, odin and then unlock.
Click to expand...
Click to collapse
Please read above.
^ really unknown territory for me. Did you restore your EFS, I assume you can since you backed it up.
I saw this great thread from BT... maybe someone has an answer in there.
http://forum.xda-developers.com/showthread.php?t=1000962
I'll keep checking in to try and learn... EFS/unlocking is really not common to me, hopefully someone can chime in and well all learn something.
Hung0702 said:
Thanks for replying. That's actually the thread I followed in order to pull the nv_data.bin and use Galaxy_S Unlock. But like I was saying, it's as though the EFS is not working properly. I pulled the nv_data.bin and it looked like the phone was already unlocked (I'm assuming it is, because it never asked me for the SIM unlock code). I changed the nv_data.bin to locked (by changing the hex value at 181469 from '00' to '01', after which it did begin asking for the SIM unlock code), then used Galaxy_S Unlock to unlock. I also tried to retrieve the unlock code using Galaxy_S Unlock and all I got were a bunch of F's, not what I was expecting.
Click to expand...
Click to collapse
Dont use Galaxy_S unlock app. It gave me same bunch of F's.
Try unlocking again changing 01 to 00 and adb push.
Look up a youtube video on unlocking your device!
exchange it
neobuddy89 said:
Dont use Galaxy_S unlock app. It gave me same bunch of F's.
Try unlocking again changing 01 to 00 and adb push.
Click to expand...
Click to collapse
Yeah, I did unlock it again but there's still an issue with AT&T SIMs. T-Mobile works fine, but AT&T SIMs don't work and it doesn't ask for an unlock code.
Right after I flashed pio's ReVolt I seem to not have any vzw service. My SIM card is being read fine, I go to about settings and I still have the proper IMEI #, MEID, PRL, etc.
Whenever I get some sort of service, I'm stuck in Roaming mode (preferred system), and my MIN and phone number under phone status is 0000000000, 000-000-0000.
I factory reset, wiped caches, and now I'm running the PAC-rom. I'm s-off and rooted also, I have not ran into this problem and I was running CM-10.1, the 5/23 build. I've also tried reflashing back to it but still nothing.
If you need any other information, don't hesitate to ask!
Kingdomkey01 said:
Right after I flashed pio's ReVolt I seem to not have any vzw service. My SIM card is being read fine, I go to about settings and I still have the proper IMEI #, MEID, PRL, etc.
Whenever I get some sort of service, I'm stuck in Roaming mode (preferred system), and my MIN and phone number under phone status is 0000000000, 000-000-0000.
I factory reset, wiped caches, and now I'm running the PAC-rom. I'm s-off and rooted also, I have not ran into this problem and I was running CM-10.1, the 5/23 build. I've also tried reflashing back to it but still nothing.
If you need any other information, don't hesitate to ask!
Click to expand...
Click to collapse
You should have asked this in the PAC thread, but that sounds like you used the wrong ROM, there's a CDMA version for Verizon and a GSM version for any other carrier, a GSM ROM will have no data on Verizon and CDMA version no data on GSM.
Tapatalked from my HTC DNA - ReVolt
pio_masaki said:
You should have asked this in the PAC thread, but that sounds like you used the wrong ROM, there's a CDMA version for Verizon and a GSM version for any other carrier, a GSM ROM will have no data on Verizon and CDMA version no data on GSM.
Tapatalked from my HTC DNA - ReVolt
Click to expand...
Click to collapse
I am using the CDMA version, I reflashed it just in case, still no luck
Kingdomkey01 said:
I am using the CDMA version, I reflashed it just in case, still no luck
Click to expand...
Click to collapse
I had the same issue. If you're using TWRP, make sure you mount System and reflash. I hadn't mounted System, so the kernel didn't write properly.
God forbid he asks a ****ing question IN THE QUESTION SECTION. Goddamn XDA Nazis... t(-_-t)
Oopsies! I didn't realize that that was you who had responded, Pio.
I had this issue as well.
What fixed it for me was relocking the bootloader, using the RUU to go back to 100% stock, and then doing a factory reset through Sense.
phuckwithfire said:
I had the same issue. If you're using TWRP, make sure you mount System and reflash. I hadn't mounted System, so the kernel didn't write properly.
God forbid he asks a ****ing question IN THE QUESTION SECTION. Goddamn XDA Nazis... t(-_-t)
Oopsies! I didn't realize that that was you who had responded, Pio.
Click to expand...
Click to collapse
Yeah I figured a question or issue about a ROM would do better to be in the ROM thread, makes sense so the developer can see and address it. For any ROM. It was a specific ROM related question and should have been posted in the ROM thread, it wasn't a general question or hardware question which I would think belongs here vs a ROM thread. Otherwise can't say the dev may see it or address it, I rarely look here, just happened to this morning.
I didn't jump on him for it, just guided him for next time. I then offered a possible resolution. Not sure how that makes me a Nazi.
I hadn't realized there were people having issues on the CDMA version though, thanks for the hint at twrp. System isn't the kernel, though, system is the ROM, so it may be more ril related or maybe the APN file. Kernel goes into a different partition.
Tapatalked from my HTC DNA - ReVolt
pio_masaki said:
Yeah I figured a question or issue about a ROM would do better to be in the ROM thread, makes sense so the developer can see and address it. For any ROM. It was a specific ROM related question and should have been posted in the ROM thread, it wasn't a general question or hardware question which I would think belongs here vs a ROM thread. Otherwise can't say the dev may see it or address it, I rarely look here, just happened to this morning.
I didn't jump on him for it, just guided him for next time. I then offered a possible resolution. Not sure how that makes me a Nazi.
I hadn't realized there were people having issues on the CDMA version though, thanks for the hint at twrp. System isn't the kernel, though, system is the ROM, so it may be more ril related or maybe the APN file. Kernel goes into a different partition.
Tapatalked from my HTC DNA - ReVolt
Click to expand...
Click to collapse
Yeah, that was totally my bad, dude. That's why I edited my post saying 'oopsies.' I didn't realize it was you who had responded until after I had. I figured it was more of that classic XDA elitist attitude.
I guess I don't quite understand what writes to which partition. All I know is mounting System fixed the issue for me. Nice work on these ROMs, man. I'm loving CM10.1 on my DNA!!
phuckwithfire said:
I had the same issue. If you're using TWRP, make sure you mount System and reflash. I hadn't mounted System, so the kernel didn't write properly.
God forbid he asks a ****ing question IN THE QUESTION SECTION. Goddamn XDA Nazis... t(-_-t)
Oopsies! I didn't realize that that was you who had responded, Pio.
Click to expand...
Click to collapse
I just tried this, it did not work
dashshiron said:
I had this issue as well.
What fixed it for me was relocking the bootloader, using the RUU to go back to 100% stock, and then doing a factory reset through Sense.
Click to expand...
Click to collapse
Is there any other easier way? I don't want to relock the bootloader, possibly flashing sense then go back to cm?
Kingdomkey01 said:
I just tried this, it did not work
Is there any other easier way? I don't want to relock the bootloader, possibly flashing sense then go back to cm?
Click to expand...
Click to collapse
That's what I'd try.
Hey guys! So I moonshined and got S-OFF on my phone. I first backed up my factory ROM after I wiped all the data so I would have it to go back to in the future if needed, this was done through clockwork mod. So I first tried using the NOS M7 ROM, didn't like that as the home screen seemed too Window's 8 phone like to me. I then tried the CyanogenMod 10.1, I noticed that my phone was only getting 3G data at this point. I was using my wife's new Galaxy S4 that was getting 4G as a comparison to mine. We were traveling through town so it's not a tower based issue, as her phone showed 4G.
I then tried to switch to viperDNA1.3.1 and I had all sort of issues with it. Heck this morning it would not even show me my alarm notification when it was going off to shut the phone up. I had to power it off to silence it. It even stopped showing the notification bar on the top of the screen and I couldn't even do the drag down thing to see notifications and settings.
So today at work I downloaded RageDNA to see if an optimized stock app would work for me, no change..... I even formatted my sdcard to blank it and the did an adb push to transfer the ROM.zip back to my phone.
SO.... between each app I would launch into ClockWorkMod and 1. wipe dalvik cache. 2. format system. 3. wipe data/factory reset. 4. choose the zip from the sdcard (haha like we really have a true sdcard) and wait for the install and then launch into the phone and do the basic setup to get the ROM working.
HELP!!!! (me crying) I am afraid I did something to my phone during the flashing that jacked up the radio causing 4G to be broken. Is there something else you need to know from me to help me out, please let me know!
**********UPDATE**********
I double checked all my phones settings with a coworker who also has a DNA, but still S-ON. Everything is setup the same for settings on the APN's. I even recreated a duplicate APN that used the specified "LTE" network instead of the one that was defaulted on both of ours "unspecified". No change, even rebooted.
I also restored my CWM backup I did before making any changes to my phone via switching ROM's. The only difference is the fact that their network typeshows "LTE" where my shows "eHRPD". I am going to look into seeing how to reflash the radio to see if something got corrupt.
If it comes down to it I am going to reset my phone back to S-ON and reflash everything that I can find that I can do.
*********Resolution*********
After reflashing my radio, I did not get any 4G signal any more, I know Verizon towers were down for 4G near my work so not sure if they moved over to the towers by my home as I only live 10 minutes from work. So only after being at work for about an hour my 4G signal started on it's own without anything done by me today.
So as I was on the path to trying to take it back to stock I followed the guide that Phaded posted for getting back to S-ON http://forum.xda-developers.com/showthread.php?t=2293919. I had a few issues with that, as it turns out my phone was not showing anything about being "LOCKED" after running his first set of commands. So I pressed forward after talking with Phaded on this situation. I had even flashed from my CWM recovery back to the stock recovery (also notice when running the RUU that it flashes the recovery.) I ran the RUU and then got the 158 error then had to flash the HBOOT. After that flash the phone showed "***Tampered*** & ***LOCKED***". I then proceeded to run the RUU and it completed at that point with no issues. Then the last few DOS commands for fastboot and back to Locked and S-On. I updated back from 1.15 up through 2.06. Also doing so that made me realize you have to step from 1.15 to 2.04 and finally 2.06. So far the 4G is still working. I will keep it stock for a few days to ensure no further 4G issues then I will be moonshining again!!
Just a guess, you may have to flash the boot image. If so the directions are in the install directions for Viper
RLGL said:
Just a guess, you may have to flash the boot image. If so the directions are in the install directions for Viper
Click to expand...
Click to collapse
I just tried to restore my CWM files from prior to any ROM changes. So far I have 3G data, but I tend to get 3G more so at my house than 4G, so not sure if anything will change.
I am wondering if the SIM card could have anything to do with this issue as well.... could a ROM have written to the card and caused it to not read the 4G data, or whatever is on there.
I also see that my phone's network seems to be "eHRPD" not sure if this had anything to do with it or not.
I double checked all my phones settings with a coworker who also has a DNA, but still S-ON. Everything is setup the same for settings on the APN's. I even recreated a duplicate APN that used the specified "LTE" network instead of the one that was defaulted on both of ours "unspecified". No change, even rebooted.
I also restored my CWM backup I did before making any changes to my phone via switching ROM's. The only difference is the fact that their network typeshows "LTE" where my shows "eHRPD". I am going to look into seeing how to reflash the radio to see if something got corrupt.
If it comes down to it I am going to reset my phone back to S-ON and reflash everything that I can find that I can do.
U need a new SIM card. 99% sure that's ur problem. They r free from any Verizon store. Give it a shot before u go thru the hassle of going back to s on and stock.
Sent from my HTC6435LVW using xda premium
if you download from the play store this app (its free) https://play.google.com/store/apps/...GwsMSwxLDEwOSwibmV0LmFuZGlyYy5sdGVvbmZvZmYiXQ.. open it and scroll down what does it say under set preferred network type? that screen has more crucial settings then the normal one. if you running viper in viper tweaks its the first option under misc. If you need help ill put up a pick when i get back. someones borrowing mine cause they stepped on their phone lol.
EDIT: also if you are running viper 1.3.1 you should download ind flash after the normal rom the ota update(the one that says 1.3.1 to 1.3.3.
reaverclan said:
if you download from the play store this app (its free) https://play.google.com/store/apps/...GwsMSwxLDEwOSwibmV0LmFuZGlyYy5sdGVvbmZvZmYiXQ.. open it and scroll down what does it say under set preferred network type? that screen has more crucial settings then the normal one. if you running viper in viper tweaks its the first option under misc. If you need help ill put up a pick when i get back. someones borrowing mine cause they stepped on their phone lol.
EDIT: also if you are running viper 1.3.1 you should download ind flash after the normal rom the ota update(the one that says 1.3.1 to 1.3.3.
Click to expand...
Click to collapse
Too funny that you pointed me to that app, I just found another one LTE Settings.
So I tried your app also and they had the exact same data listed. So here's the screen shots I took from my app I pointed to. My phone will connect to 4G only and only if I choose "LTE only" if I move it to something else either by changing it through the OS settings, or changing it through this app, it goes back to getting 3G service. So at least this tells me my phone isn't broken, just some setting is F***ed up somewhere.
I have tried Global and CDMA/LTE settings with it always showing 3G.
yup that's freaking weird lol swing by a VZW store and get a free sim card since yours seems like it might be messed up what happnes if you flash something like crpalmers kernel though? your boot image might just be all screwed up. his latest version is June 24th.
reaverclan said:
yup that's freaking weird lol swing by a VZW store and get a free sim card since yours seems like it might be messed up what happnes if you flash something like crpalmers kernel though? your boot image might just be all screwed up. his latest version is June 24th.
Click to expand...
Click to collapse
Yeah weird! I just used the DNA Toolkit v1.0.5, I flashed the 2.06 radio and after it rebooted and what not, I went outside (as I have bad service inside this house) and now 4G won't even connect. Not sure if it's the towers, as the one by work went out around noon today.
So as it's a kernal and not a ROM how do I do that, just the same install from zip file in CWM? Do I need any certain ROM for it? As right now I have the factory one that I backed up with CWM when I did S-OFF. (it was a blank fresh factory reset)
chayos00 said:
Yeah weird! I just used the DNA Toolkit v1.0.5, I flashed the 2.06 radio and after it rebooted and what not, I went outside (as I have bad service inside this house) and now 4G won't even connect. Not sure if it's the towers, as the one by work went out around noon today.
So as it's a kernal and not a ROM how do I do that, just the same install from zip file in CWM? Do I need any certain ROM for it? As right now I have the factory one that I backed up with CWM when I did S-OFF. (it was a blank fresh factory reset)
Click to expand...
Click to collapse
if your using viper it supports only 2.04 as a base for its radios i believe. like I said try flashing crpalmer's one this one http://d-h.st/hu7
OH also yeah your towers by you could be experiencing maintenance try driving to somewhere else id say at least a mile away.
reaverclan said:
if your using viper it supports only 2.04 as a base for its radios i believe. like I said try flashing crpalmer's one this one http://d-h.st/hu7
OH also yeah your towers by you could be experiencing maintenance try driving to somewhere else id say at least a mile away.
Click to expand...
Click to collapse
I flashed palmer's and no change. I just texted a coworker who lives about .25 miles away to see if he's getting 4G.
Again right now I'm on the factory ROM.
chayos00 said:
I flashed palmer's and no change. I just texted a coworker who lives about .25 miles away to see if he's getting 4G.
Again right now I'm on the factory ROM.
Click to expand...
Click to collapse
does the factory restore work like your cwm one i mean?
Click on Mobile Data in your settings, and make your 'preferred' network LTE/CDMA.
I had the very same error with the stock phone, and once I switched it - I started getting 4G almost everywhere.
Amer28 said:
Click on Mobile Data in your settings, and make your 'preferred' network LTE/CDMA.
Click to expand...
Click to collapse
That doesn't work, I have tried that like 30 times with no change.
reaverclan said:
does the factory restore work like your cwm one i mean?
Click to expand...
Click to collapse
I'll try the factory restore in the ROM and see what it does. (haven't setup the rom due to the lack of 4g)
chayos00 said:
I'll try the factory restore in the ROM and see what it does. (haven't setup the rom due to the lack of 4g)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=17145857&postcount=2 found this and it seems like your towers might be experiencing something if they dropped from pure lte to this. like some equipment has failed and it has dropped to a lower communication lvl hardware wise. EDIT: when i meant factory i meant in cwm going to restore and restoring your whole backup(snapshot) of the factory rom that you made not in the rom itself.
chayos00 said:
That doesn't work, I have tried that like 30 times with no change.
Click to expand...
Click to collapse
I don't think you would notice the change instantly. You will see in a few hours, especially if you go somewhere, you will be getting 4G - or if you restart the phone.
Further, what you can do is flash the radio.
Here's the file you need to flash: https://docs.google.com/file/d/0B9yd_oFytDSzUjRpLTZhSFEwWnc/edit
That is a Verizon radio, and it works also with other providers.
Use fastboot to flash:
Code:
fastboot flash radio radio.img
Original thread of the radio: http://forum.xda-developers.com/showthread.php?t=2236633
PS: This is the original verizon radio.
reaverclan said:
http://forum.xda-developers.com/showpost.php?p=17145857&postcount=2 found this and it seems like your towers might be experiencing something if they dropped from pure lte to this. like some equipment has failed and it has dropped to a lower communication lvl hardware wise. EDIT: when i meant factory i meant in cwm going to restore and restoring your whole backup(snapshot) of the factory rom that you made not in the rom itself.
Click to expand...
Click to collapse
When I was at work, I compared a coworkers DNA and he was getting actual LTE signal. So don't think it's that with the eHRDP thing that I keep seeing. But yeah it looks like a "cheaters way" to get their CDMA hardware to work with LTE. lol
Sorry, I feel like a tard and not really following what you are talking about with the "factory" thing. If you mean in the hboot the factory restore, it takes you to the CWM recovery to do that factory restore. Plus the ROM restore seems to almost go through CWM as well, but does it automatically. I'm going to do a full wipe and set this thing back to factory settings. As when it's broke and not working, best thing to do is start fresh.
chayos00 said:
When I was at work, I compared a coworkers DNA and he was getting actual LTE signal. So don't think it's that with the eHRDP thing that I keep seeing. But yeah it looks like a "cheaters way" to get their CDMA hardware to work with LTE. lol
Sorry, I feel like a tard and not really following what you are talking about with the "factory" thing. If you mean in the hboot the factory restore, it takes you to the CWM recovery to do that factory restore. Plus the ROM restore seems to almost go through CWM as well, but does it automatically. I'm going to do a full wipe and set this thing back to factory settings. As when it's broke and not working, best thing to do is start fresh.
Click to expand...
Click to collapse
okay if you do it from hboot it wont do anything cause now cwm will stop that from running but that is the same as running factory reset in cwm, thats not what im talking about though when you first moonshined then booted cwm after getting it, did you run a backup of your factory(stock) ROM? if so it would be in sdcard/clockworkmod/backups it also would have been about 1.5-2GB's. you could also try the radio.img amer is taking about as well, that you need to flash with adb though in fastboot as he stated.
reaverclan said:
okay if you do it from hboot it wont do anything cause now cwm will stop that from running but that is the same as running factory reset in cwm, thats not what im talking about though when you first moonshined then booted cwm after getting it, did you run a backup of your factory(stock) ROM? if so it would be in sdcard/clockworkmod/backups it also would have been about 1.5-2GB's. you could also try the radio.img amer is taking about as well, that you need to flash with adb though in fastboot as he stated.
Click to expand...
Click to collapse
After I noticed my 4G issue, I restore my CWM backup. Yes the CWM backup is what I restored and I am running from right now. It's size is 1.39GB in size.
I will do the radio flash right now.
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
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.