it was working fine until yesterday and all of a sudden it wont give me LTE access. The access point was off but I turned it on and it still wont connect to LTE. I rooted and even flashed a stock radio. Nothing. Help?
Need more info.
You still get 3g?
Can you make and receive calls? Send texts?
What ROM?
... all radios are "stock". Just depends on what version you're running.
Sent from my SCH-I535 using xda app-developers app
epagib said:
Need more info.
You still get 3g?
Can you make and receive calls? Send texts?
What ROM?
... all radios are "stock". Just depends on what version you're running.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I do get 3g, some calls do not come in and some texts do not go out. And I used this thread
http://forum.xda-developers.com/showthread.php?t=1762709 (section 5)
to revert my sgs3 back to factory settings and touchwiz. I had cyanogenmod nightly running before and it was then that it stopped working.
Have you tried to turn the radio off and then back on?
That's always been a reliable solution for me when I've run into similar problems in the past..
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
I am having a similar problem to you. I flashed a CM nightly build for my S3 and am unable to make calls/send texts. LTE works, but only sort of. I was told to try these steps suggested by SlimSnoopOS, but none of them worked for me. I'd recommend getting a log viewer/ logcat application. I am going to do that later to see about my issue.
I was on CM 10.2 nightlies and lost LTE. Reset my phone and everything. Turned out CM screwed up my SIM card and I got a new one. After I powered on my phone with the new SIM, good to go.
Related
I just recently purchased a galaxy s3 from Verizon and it was working flawlessly until i flashed build 2 of aokp. Before that i had been using the cm10 nightlies and synergy ROM and both had worked no problem even after flashing the latest radio. I had no signal and the roaming R above the signal bars so i figured leaving the phone off all night would fix the problem. i woke up the next morning with 4g signal and 3 bars but i could not send or receive call/texts. I called tech support at Verizon but to avail. so I am now sending it back to get a new one. This same thing happened on my galaxy nexus but i had no warranty so I as just out of luck. Can someone please explain how this keeps happening???
JTlane16 said:
I just recently purchased a galaxy s3 from Verizon and it was working flawlessly until i flashed build 2 of aokp. Before that i had been using the cm10 nightlies and synergy ROM and both had worked no problem even after flashing the latest radio. I had no signal and the roaming R above the signal bars so i figured leaving the phone off all night would fix the problem. i woke up the next morning with 4g signal and 3 bars but i could not send or receive call/texts. I called tech support at Verizon but to avail. so I am now sending it back to get a new one. This same thing happened on my galaxy nexus but i had no warranty so I as just out of luck. Can someone please explain how this keeps happening???
Click to expand...
Click to collapse
If you know your issue as to where it went wrong then you know what the problem is...Check and make sure your imei is still there
Its still there. And I flashed back to synergy just to make sure and it did the same thing on synergy its as if my radio just have out and quit working.
Sent from my MB870 using xda app-developers app
JTlane16 said:
Its still there. And I flashed back to synergy just to make sure and it did the same thing on synergy its as if my radio just have out and quit working.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Back up anything you want on internal SD, and dial *2767*3855# on stock.
What's that number do^
Sent from my SCH-I535 using xda premium
Hulk0069 said:
What's that number do^
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Reprovisions your phone to factory. Has been known to fix radio issues at times.
I previously had CM10 (experimental) and was having issues with crashes so I decided to flash a new ROM on my device.
I then chose to flash onto LiquidSmooth 4.2.1. After playing around in Liquid, I found some bugs and decided to look for a new ROM to flash.
I chose to flash to CM10.1 Nightly, which I know has data issues. I wiped pretty much everything prior -Dalvik, formatted my SD, formatted system, and whatnot. After my first boot, the phone could not finish "activating the network"
Right now I cannot send/receive calls or texts or have data. I have a small "R" at the top of my signal bars where 4G usually is. I have tried dialing *#*#4636#8#* and made sure LTE/GSM/CDMA auto (PRL) was selected.
Would flashing to stock ROM resolve this issue? Or what could be causing this?
Thanks in advance
Saiko18 said:
I previously had CM10 (experimental) and was having issues with crashes so I decided to flash a new ROM on my device.
I then chose to flash onto LiquidSmooth 4.2.1. After playing around in Liquid, I found some bugs and decided to look for a new ROM to flash.
I chose to flash to CM10.1 Nightly, which I know has data issues. I wiped pretty much everything prior -Dalvik, formatted my SD, formatted system, and whatnot. After my first boot, the phone could not finish "activating the network"
Right now I cannot send/receive calls or texts or have data. I have a small "R" at the top of my signal bars where 4G usually is. I have tried dialing *#*#4636#8#* and made sure LTE/GSM/CDMA auto (PRL) was selected.
Would flashing to stock ROM resolve this issue? Or what could be causing this?
Thanks in advance
Click to expand...
Click to collapse
Flash an unofficial build and set CDMA subscription to ruim/sim under mobile settings. Tell all your friends too.
Sent from my SCH-I535 using xda app-developers app
ajrty33 said:
Flash an unofficial build and set CDMA subscription to ruim/sim under mobile settings. Tell all your friends too.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I flashed back to touchwiz. I have 4G capabilities, but still no phone service. Should I still try flashing an unofficial CM10 and setting CMDA sub to ruim/sim?
Saiko18 said:
I flashed back to touchwiz. I have 4G capabilities, but still no phone service. Should I still try flashing an unofficial CM10 and setting CMDA sub to ruim/sim?
Click to expand...
Click to collapse
Check your mobile settings in touchwiz
Sent from my SCH-I535 using xda app-developers app
Saiko18 said:
I flashed back to touchwiz. I have 4G capabilities, but still no phone service. Should I still try flashing an unofficial CM10 and setting CMDA sub to ruim/sim?
Click to expand...
Click to collapse
Well that's what the other guys said no? So I'm guessing you should :thumbup:
Sent from my SCH-I535 using xda app-developers app
Here's a somewhat interesting case, I think.
I installed CyanogenMod 10.1 and now have this problem where I can't hear/talk when I make a phone call. The call does connect to the other side (after a brief freeze of the phone app), but I hear nothing. Toggling the phone volume up/down during call makes no sound.
Here's what I've tried thus far:
Flash UXUMA7 modem.
Flash UCLI3 modem (current)
Take out SIM, shutdown phone. Insert SIM, reboot, reboot.
All other functions seem to work fine (messaging, etc.)
I'm on AT&T.
I was planning to reinstall a stock ROM and then flash CM again, but one thing confused me: I could call and hear fine when I was in Europe with a European (Vodaphone) SIM card last week. However, the same problem occurred when I used this SIM card to try to call the US (from Europe). So I'm wondering, is there setting I need to change?
Thanks in advance!
What ROM did you specifically install?
Sent from my HTC Express using xda premium
CyanogenMod version (after recent update):
10.1-20130304-EXPERIMENTAL-skyrocket-M2
Full wipe and use the latest nightly
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Full wipe and use the latest nightly
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Dang. I was hoping for a different answer. I appreciate the help!
Had the same problem yesterday. I ended up up flashing a stable build of cm10
Sent from my Nexus 7 using xda app-developers app
livefree79 said:
Had the same problem yesterday. I ended up up flashing a stable build of cm10
Click to expand...
Click to collapse
You could have stuck with 10.1-just not the experimental build. There was a commit added that fixed the no in-call audio bug. The audio is working fine now on the nightly builds. You can check out the thread and see which one has been the most stable for other users.
Hey so i was running the Cyanogenmod RC5 and decided to finally upgrade to the stable 10.1. Flashed, and now it boots the phone, and gets stuck on the activation part, and it wont activate. i can still see i have 4G service..but i can only receive data and texts, and im not able to send. Im on Verizon. Please help.
Anything is appreciated, i just want this up and running.
Can you get to the home screen or are you suck on the activation screen?
Sent from my SCH-I535 using xda app-developers app
tigerheli said:
Can you get to the home screen or are you suck on the activation screen?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can get to the homescreen but the phone never activates to make or receive calls.
Try downloading again and reflash. I flashed the new cm and it worked fine.
Sent from my SCH-I535 using xda premium
I'm having the same issue. I've got data, but can't make phone calls.
I've tried using Odin to flash a stock rom and still have the same results.
What version of CM did you flash to get it working?
I was using the 10.1.0 from the cm website. They have the new 10.1.0.1 release up now and I have not used that. Everything worked. Just flashed back this morning because I like bonestock rom features
Sent from my SCH-I535 using xda premium
Yup
I went ahead and flashed CM 10.1.0.1 along with the MF1 firmware just a little bit ago and I was having a constant no SIM error. Couldn't get it fixed, wiped everything but the external SD and tired again, changed the LTE mode back, still no go. So I ultimately just flashed back to my backup of CleanROM and rolled back to the MB1 firmware for my cameras sake.
I'll just wait until some more of the bugs get ironed out. I really miss having stable AOSP on my Droid Incredible, I was on CM7 from its initial release till retirement and beyond.
It seems like its kind of a hit or miss type of deal. Some phones work just fine, others, not so much.
http://forum.xda-developers.com/showthread.php?t=2344204
Same problem, its just the "stable releases" are jacked up. Flash a nightly and the baseband (and google apps) and you'll be fine.
Oh, and go into settings and change SIM mode from NV to SIM, then reboot. You'll be good to go.
Sent from my SCH-I535 using xda app-developers app
I have been trying to help a friend out who has Net 10 and wants to buy my old Skyrocket for cheap. I ran the Net 10 sim card in the skyrocket with the stock samsung rom that you need to unlock the network lock for free. After verifying that it worked by making calls and recieving texts and data we then began to talk about upgrading to a newer Rom. Well after upgrading to Cyanogen 4.3.1 the problem first began, then it happened again with Cyanogen 4.2.2, and again with this Embryo Rom. I have done everything to the T and its just getting ridiculous that the APN will not save. No matter what I do, as soon as that APN is finished I click save and its gone. What do I do.. I am running the ATT JB Radio that the Cyanogen Mod threads recomend for the 4.3 rom to work. I have not flashed anything other than the recovery, radio, and roms. I am using CWM btw.
Anything?
Sent from my MB886 using XDA Premium 4 mobile app
This isn't a solution for your issue but it may (or may not) offer some insight.
my girlfriend has a glide and when I put cm on it the apns would randomly disappear. Same with pa. the phone came from stock gb. Flashed stock ics and haven't had a problem with it yet.