So I decided to take the leap and flash 10.1. Flashed the most recent nightlies build. Everything seemed to work fine. I have full 4G data without a problem, I can receive messages, but I am unable to send them.
Any suggestions would be greatly appreciated. I don't want to ODIN back to stock...
Thanks in advance.
Related
Greetings, all. Long time reader, first time posting.
I had recently flashed the HFS and EB ICS roms, and both were running without issue. Then, out of the blue, I stopped receiving SMS. I could still send, but could not receive. I had read on the HFS thread that a few others had experienced this issue. After searching various threads and forums, I couldn't find a solution. After a re-flash of both HFS and EB didn’t fix the problem on either, I flashed a couple of GB roms, and was still unable to receive SMS. Finally, I restored back to Stock GB and SMS worked fine.
I am sometimes able to receive SMS on ICS when WIFI Calling is active, but it is inconsistent.
I’ve tried the following to remedy this issue, with no success:
CWM>Wipe Data, Cache, and Dalvik, Flash rom and Gapps.
CWM>Wipe Data, Cache, and Dalvik, Format Data, System, and Cache, Flash rom and Gapps.
Same steps as above, but with G2x Scrubber (sometimes scrubbing twice) thrown into the mix.
Re-downloading roms, in case of file corruption.
Fixing permissions before and after first boot.
Master reset before and after first boot.
GetRIL.
SMSC Update.
APN delete, restore, manually enter, etc.
Tried multiple SMS apps (Stock, GO, Handcent).
Flashing Gapps after first boot.
Skipping Google account setup on first boot.
I followed all rom installation instructions, including waiting ten minutes before touching the phone after first boot.
I suppose the only thing I haven’t tried is flashing a different Kernel after flashing the rom. My only other thought is to flash the Stock recovery, then re-flash CWM and try it all again.
If anyone has any suggestions, your assistance would be greatly appreciated.
Battery pull?
iArtisan said:
Battery pull?
Click to expand...
Click to collapse
If only it were that simple; but, no, I tried that as well.
Unfortunately I don't have anything to add other than I'm having the same issue with ICS and CM7 roms. I can receive SMS on MIUI and Bionix and have gone through the same troubleshooting steps. I'll add that I've tried a different SIM as well...no dice.
I saw someone post on another thread that they resolved this issue through T-mobile customer support, but I'm skeptical.
EDIT: Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
akelty said:
Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
Click to expand...
Click to collapse
Thanks. After reading that, I didn't bother trying. I'm happy to say I did a warranty excahnge and ICS is running beautifully on my new G2x, though I still wish I could've figured out what the issue was with the last one. Thanks again for your response and trying out that fix.
If anybody's still following this thread I found a solution for GB roms that cannot receive SMS. I had trouble with EaglesBlood and tried flashing the Trinity kernel...viola! Getting all my texts now.
Last night i made a backup, did a full wipe, and flashed liquid smooth RC8 and the gapps package for it. when the phone rebooted, I was no longer able to send text or make calls, but 4G worked fine. So i restored back to my previous backup, and still had the same issue. I odin'd back to root_66 and I am still not able to send text/calls, but 4G is working fine. Does anyone have any suggestions? I bought the phone from a friend so I don't think I would be able to bring it back to verizon besides replacing it under warranty. Thanks
I was running the latest stable version of CM10.1 on my GS3 and all was going well until someone sent me a text message and I tried to respond. I was greeted with the error of message not sent. I attempted to text someone else to have the same error. Attempting to call someone will just hang and eventually say call failed.
I thought it was a radio issue so attempted to flash different modems but had the same result. So I restored my previous rom Beans 11 that was working after wiping and the same issue. Data works perfect, but voice and text does not. I searched and odin'd back to stock VRLG1 and entered *2767*3855# in hopes of that fixing the problem, again no voice/text.
Any suggestions further help? I don't know what else to try!
*CM10.1 was working fine, and then calls/texting stopped but data continued to work without trouble.
*IMEI seems to be intact
*Flashed backup of known working rom and issue still persists
*Flashed back to VRLG1 and attempted *2767*3855# as per another post to no avail and this is where I sit.
Same thing. Installed jellybeans 12 now I can't call or text. Prior text was hit and miss some days....restored stock rooted image flashed other Roms....no help. Dialed the ** number....so screwed. Ayneegry should have backed up my few several times. No idea what to do.
Sent from my SCH-I535 using Tapatalk 2
When you say "Data" do you mean wifi or 3g/4g? If you have no phone/text/3g/4g then it's probably your imei. Check under phone settings, see if it's gone. If it's gone you gotta restore, do a search.
If you have 3g/4g then I don't know what the problem is. Sorry, just trying to help
Odin back to ICS and reprovision your phone by going into the dialer and typing *2767*3855#
rgrossie - data as in 3G/4G works no problem... phone showed IMEI still there but followed a thread to restore it anyway to make sure that wasn't the issue...
Edgehood -- I've tried that, and that's where I currently sit, stock ICS with 4G data but doing the re-provision doesn't seem to fix anything -- occasionally a text will slip through, but I'm unable to reply
astrocity said:
Same thing. Installed jellybeans 12 now I can't call or text. Prior text was hit and miss some days....restored stock rooted image flashed other Roms....no help. Dialed the ** number....so screwed. Ayneegry should have backed up my few several times. No idea what to do.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I hear ya, if I can't figure out what's up, I'll end up having to go back to verizon and see what I can do... It was out of the blue, everything was working and then suddenly it just stopped. Happened on a flash that was a little over a day old, so who knows.
Check Mobile network
I have thiss problem happen occasionally when I flash custom roms. Look under your mobile networks, see if either CDMA/SIM is checked or NV. If NV is checked switch to CDMA/SIM and then reboot. That seems to fix that problem most of the time.
Edit: After some tests found out this doesn't always stick, but I did find out that after switching from NV to CDMA/SIM turn on airplane mode so the radios are tunred off, wait a few moments, then turn airplane mode off. That worked more consistently than restarting it.
MrRevesz said:
rgrossie - data as in 3G/4G works no problem... phone showed IMEI still there but followed a thread to restore it anyway to make sure that wasn't the issue...
Edgehood -- I've tried that, and that's where I currently sit, stock ICS with 4G data but doing the re-provision doesn't seem to fix anything -- occasionally a text will slip through, but I'm unable to reply
Click to expand...
Click to collapse
Did you ever fix this? I currently have the same problem and have no idea what to do.
i had the same problem but a imei/efs restore fixed it. My imei was not missing but data worked and not calls or text. Changed sim and still same, even odined back to stock and unlockex and rooted no luck restored nandroid no luck. Then restored synergy imei/efs backup and good to go. Hope it helps.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
I had the same issue two days ago when I flashed to the latest MIUI Rom. Here's how I fixed it.
Go into settings, mobile networks, make sure subscription is set to SIM. After that open the phone, type *#*#4636#*#* make sure it's set to LTE/CDMA/AUTO
Reboot phone and all should be well.
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
If you Odin back to the original stock unroofed ROM, you'd have to take all the ota Verizon updates to vmf1. Then reset your phone.
Pain in the a$$ but has always worked for me. I had same problem running carbon.
I read in another post that Odin back to root66, them reset your phone would work too.
Sent from my SCH-I535 using xda app-developers app
Hi there,
I've been racking my brain on this but I can't seem to figure it out. I have been on both Carbon 4.2.2 and XenonHD for my XT926 but I can't for the life of me get MMS to send or receive. SMS work just fine but when I try to send a picture it just says sending... for infinity. When I flash back to stock 4.1.2, I can easily send MMS again. I've been searching for a while now for the answer but it seems to be working fine for most people. I've tried Go SMS apn settings, rebooting while sending, flashing back to stock then to rom, etc. Any ideas out there?
Thanks in advance.
Edit: Fixed it... somehow. I tinkered with APN backup and restore and Go Sms all to no avail. But then I dirty flashed the ROM over itself and for some reason that solved half the problem. I was able to do a fresh install after that and the MMS sending was still working.
Edit 2: Nevermind. It doesn't work again. It was fixed for about an hour and now just doesn't work again.
Edit 3: My second flash back to 4.1.2 Stock System, Kernel, and Radio and then clean install of XenonHD did the trick. Glad to have that over with. Fingers crossed. You can delete this thread.
I was on the Milestone release of PAC 4.2.2 for a while and then I started to get a lot of FCs and whatnot so I decided to do a clean wipe and upgrade to PAC 4.3 9/21 nightly. I did this last night and was experiencing a lot of FCs, mainly the "Blame Tyler" FCs. At this point I still able to send messages and whatnot. This morning I had tried to flash Carbon's most recent nightly and received more FCs from that. I then decided to revert back to stock using Odin because I wanted to start over and flash JellyBean's build 19, a ROM that I knew was stable. Well this is where the problems began. After I had flashed JellyBean's build 19, I had 'service' but I could not send or receive texts, make calls, or anything. I had looked into restesting my IMEI, but that did not help. Following one of the guides, I cannot find it right now, I was instructed to use the "Nand Erase All" in Odin. Could that have done something? I did not use until after I had started to experience these problems. Any help would be great
It sounds like you've lost your imei/Eri. To check go to settings>about>status. Your Imei should be the number under your battery and your Eri should say 5. Check to see what those are first.
Sent from the S3 of The Afro Samurai
TheAfroSamurai said:
It sounds like you've lost your imei/Eri. To check go to settings>about>status. Your Imei should be the number under your battery and your Eri should say 5. Check to see what those are first.
Sent from the S3 of The Afro Samurai
Click to expand...
Click to collapse
The numbers match up. I am not sure what else to do. I am running the root66 ROM. It says that it is 'Searching for Service'.
Also, I have been receiving text messages but I am not able to send them
Stran93r said:
The numbers match up. I am not sure what else to do. I am running the root66 ROM. It says that it is 'Searching for Service'.
Also, I have been receiving text messages but I am not able to send them
Click to expand...
Click to collapse
refer to thread below. should fix the problem. It's turning out to be a fairly common issue with some 4.3 builds.
If you're already Odin'ed back to root66, I'd try factory resetting the phone first.
http://forum.xda-developers.com/showthread.php?t=2445362
epagib said:
refer to thread below. should fix the problem. It's turning out to be a fairly common issue with some 4.3 builds.
If you're already Odin'ed back to root66, I'd try factory resetting the phone first.
http://forum.xda-developers.com/showthread.php?t=2445362
Click to expand...
Click to collapse
I had fixed the problem by restoring a backup. It would have been much easier if I had just done that in the first place... Thank you very much for providing that thread. It gave me much insight into what had actually caused the problem. I am sure I will be referencing it in the future.