Can only send one sms - Verizon Samsung Galaxy S III

I have a weird problem where I can only send one sms but when I try to send another it won't go through. I can try to send a message to another person and it won't send either. I am limited to only one. After the one, I can't send sms at all. The only fix is to reboot or toggle the data. Not sure why this started happening. I am running CM 11.0M3. I tried doing a factory reset/cache wipe in recovery and reverting to CM10.2 but didn't fix the issue. Any help would be appreciated!

Using a TouchWiz rom is the only fix right now that I know. Many of us have the same exact issue as you, bud. I don't really think much progress has been made on fixing the issue, too. What I understand is that is actually a problem on Verizon's end.

cooldman224 said:
I have a weird problem where I can only send one sms but when I try to send another it won't go through. I can try to send a message to another person and it won't send either. I am limited to only one. After the one, I can't send sms at all. The only fix is to reboot or toggle the data. Not sure why this started happening. I am running CM 11.0M3. I tried doing a factory reset/cache wipe in recovery and reverting to CM10.2 but didn't fix the issue. Any help would be appreciated!
Click to expand...
Click to collapse
Try flashing back to stock and doing an NVrestore (only if you've previously done an nvbackup) or reprovisioning your service using *2767*3855# then just go back to CM

theraptscallion said:
Try flashing back to stock and doing an NVrestore (only if you've previously done an nvbackup) or reprovisioning your service using *2767*3855# then just go back to CM
Click to expand...
Click to collapse
What stock base did you odin back to?
Sent from my GT-N5110 using XDA Premium 4 mobile app

I went all the way back to the root66.tar which I think was vralg1, since it was basically stock plus root so I could use the terminal out of the box.

Same Issue but only in one area.
theraptscallion said:
Try flashing back to stock and doing an NVrestore (only if you've previously done an nvbackup) or reprovisioning your service using *2767*3855# then just go back to CM
Click to expand...
Click to collapse
Hey everyone, I've noticed this myself but only in one small town near my house. Which may very well be verizon towered. Most towers at my house are appalachian wireless or verizon leased to appalachian or vise versa. Either way, it doesn't happen at home. Only in Grundy, VA.
I was wondering if the fix the person posted above worked, and if so couldn't I just do that from a TW 4.3 rom since it should have the dialer that does those types of things, or maybe access a hidden menu somewhere?
Thanks a bunch and my apologies for resurrecting an old thread if this one is.

Grundy, VA huh? Are you at Appalachian?
The fix has been permanent for me, but it requires you to go back to stock ics or jellybean, since the reprovision code doesn't work on 4.2 on up.
For the full fix, download root66 and flash it (after backing up of course). Reprovision. Open a terminal window and type reboot nvrestore. Check if you have am imei. If you don't, reprovision again, open terminal and type reboot nvbackup. Restore your backup and begin testing. The cm11 unofficial nightly thread should have similar directions in the Op.

Grundy, VA huh? Are you at Appalachian?
The fix has been permanent for me, but it requires you to go back to stock ics or jellybean, since the reprovision code doesn't work on 4.2 on up.
For the full fix, download root66 and flash it (after backing up of course). Reprovision. Open a terminal window and type reboot nvrestore. Check if you have am imei. If you don't, reprovision again, open terminal and type reboot nvbackup. Restore your backup and begin testing. The cm11 unofficial nightly thread should have similar directions in the Op.

Related

No VZW service after flashing.....need some guidance please

I was running Paranoid android for a while and all was fine. Phone started glitching , so I did a reinstall. Thats when my mobile service went out. Here what I did.
1. Noticed IMEI was B00000, so i re-copied my backup and IMEI fixed. Still no network.
2. I reflashed a new VZW modem and still no network.
3. Checked out phone info, and it shows no service. Phone Info shows corrected IMEI, network type as LTE/CDMA. But says "searching for service"
4. I went ahead and unlocked, booted in to CWM 6.0.1.0 and installed CM10 and Gapps. All loaded fine, but still no network.
Anyone have any idea how I can fix this?
heynicebits said:
I was running Paranoid android for a while and all was fine. Phone started glitching , so I did a reinstall. Thats when my mobile service went out. Here what I did.
1. Noticed IMEI was B00000, so i re-copied my backup and IMEI fixed. Still no network.
2. I reflashed a new VZW modem and still no network.
3. Checked out phone info, and it shows no service. Phone Info shows corrected IMEI, network type as LTE/CDMA. But says "searching for service"
4. I went ahead and unlocked, booted in to CWM 6.0.1.0 and installed CM10 and Gapps. All loaded fine, but still no network.
Anyone have any idea how I can fix this?
Click to expand...
Click to collapse
Try flashing to stock with odin. Once you're back to stock dial:
*2767*3855# (which will wipe EVERYTHING on your internal SD and set your phone back to factory restore)
heynicebits said:
Anyone have any idea how I can fix this?
Click to expand...
Click to collapse
Zalithian said:
Try flashing to stock with odin. Once you're back to stock dial:
*2767*3855# (which will wipe EVERYTHING on your internal SD and set your phone back to factory restore)
Click to expand...
Click to collapse
Yup try that, sounds like you didn't reprovision it after restoring your backup
So I reloaded stock everything, locked back up the bootloader, loaded the original modem and took it back to verizon. They popped in a new sim which restored data, but the IMEI still read at 0. Data and calls worked, even got the 4g icon. They said it was fine that it read zero and that it was just a network issue. The look on my face was "wtf?"
flash back to stock
heynicebits said:
So I reloaded stock everything, locked back up the bootloader, loaded the original modem and took it back to verizon. They popped in a new sim which restored data, but the IMEI still read at 0. Data and calls worked, even got the 4g icon. They said it was fine that it read zero and that it was just a network issue. The look on my face was "wtf?"
Click to expand...
Click to collapse
So is it working like it should? and have you flashed a rom to see if it still works?
You can try this. When you said you backed up did you back up with qpst?
http://forum.xda-developers.com/showthread.php?p=29462348
Here's how to back up with a tutorial
http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/
I haven't had to restored just thought this might help but sounds like it may have worked its self out with Verizon.
Sent from my Amazon Kindle Fire using Tapatalk 2
Zalithian said:
Try flashing to stock with odin. Once you're back to stock dial:
*2767*3855# (which will wipe EVERYTHING on your internal SD and set your phone back to factory restore)
Click to expand...
Click to collapse
Seriously, READ, do this!!!!!
I did same thing as you. Had a backup of my imei that I pushed back to my phone, only nothing happened either. Then I reprovisioned it using this and it went back to 100% working and displaying accurately.
Sent from my Galaxy S3 using Tapatalk 2
Zalithian said:
Try flashing to stock with odin. Once you're back to stock dial:
*2767*3855# (which will wipe EVERYTHING on your internal SD and set your phone back to factory restore)
Click to expand...
Click to collapse
Had the same problem, this worked like a champ. Thank you!
LXative said:
Had the same problem, this worked like a champ. Thank you!
Click to expand...
Click to collapse
No problem. Glad it's helping some people. I had a roaming/no data issue when I flashed a CM10 nightly and that fixed it for me too, so hopefully more people will realize it's a possible fix for those sorts of problems (assuming they still have their IMEI)

[Q] Verizon Galaxy s3 roaming only, not activating

So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.

[Q] At a loss, data but no voice/sms

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

Cannot make calls/send messages

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.

Problem after flashing 4.3 rom causing me to be stuck in 2g

I am having a huge issue with my phone. I have been flashing custom roms for the past few years and this is the first time I have ever ran into a issue like this. I flashed SlimRom 4.3 build 2 a couple weeks back, it was taking forever to switch between 3g and LTE sometimes up to 5 mins to lock. Not to mention the signal was super low. I ignored it for the most part as it is a newer rom and figured it was just a bug and would hold off for now till kitkat released.
Then my phone would just start random rebooting about once or twice a day. Then on my way home from work i was bluetoothed to my vehicle when it did a random reboot. After that Ive been stuck in 1xRTT since. I also managed to loose my IMEI and PRL version they are both set at 0 and I do not have a backup. Has anyone else ever had this issue? I don't have a clue how to get it working again. My phone is out of warranty I am in the midst of flashing it back to stock to see if that works. Ive searched for hours trying to find a fix. Thanks.
Reverted back to stock.still no luck. Also play store won't work. No connection wirh retry button even while connected to wifi
What firmware/radio do you have? If you've been on custom roms a while you might need to update your radio baseband (most current is VRBMF1). You can flash an updated radio without regard for the Rom you're using.
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 10:29 AM ---------- Previous post was at 10:25 AM ----------
The imei thing is a separate issue. I lost mine without a backup when I first started flashing roms... I think it was cM at the time. I ended up going all the way back to an early stock image, grabbing the OTA updates and then rooting and flashing all over again. I don't know what part in particular got me my imei back.
Sent from my SCH-I535 using xda app-developers app
Do you mean a backup of efs partition or a nandroid? There is a thread at rootzwiki about recovering your imei-efs items. When u get it back do
Su
Reboot nvbackup
In a terminal then you wont have to worry about this again. If you have a nandroid restore it and you'll b good.
Yes my efs folder was completely empty. I reverted back to stock 4.0.4 still had a "0" for IMEI so i used QPST and entered in the IMEI manually and it stuck. I have signal back now. I just got factory mode off. Now my phone is stuck on "Activating", a factory reset should fix that. So this is resolved. Thanks for the help.
quicksilv312 said:
Yes my efs folder was completely empty. I reverted back to stock 4.0.4 still had a "0" for IMEI so i used QPST and entered in the IMEI manually and it stuck. I have signal back now. I just got factory mode off. Now my phone is stuck on "Activating", a factory reset should fix that. So this is resolved. Thanks for the help.
Click to expand...
Click to collapse
Is this the fix to get everything up and running again (flash back to ICS)? I was about to start my own thread until I read this. I lost my IMEI, ERI and MEID but didn't back it up first (I know I know ... boo). I manually input my IMEI using QPST like you did and was also able to fix my ERI and MEID and now I have data and text, but still no voice connection. I've flashed a stock (rooted) ROM and tried the reprovision code *2767*3855# and the RTN codes ##786# & ##72786# but nothing happens (I've seen in other forums this only works in ICS and not JB). Last night I downloaded a stock unrooted JB ROM (4.1.2) and ICS ROM (4.0.4) and am planning to ODIN back to stock and complete a factory reset to see if it will kick the gears back in motion again.
I'm not meaning to hi-jack this thread but confirm this is the solution to completing a non-backed-up IMEI/ERI/MEID fix.
-Edit-
There are tons of threads out there starting with "I've lost signal, what happened?" and ending with "I'll report back and let you know what I've found." or "Verizon replaced it for me." but none offer a viable user solution. I'd love to see the answer posted so other searchers out there can find help.
I can confirm everything you did will restore your IMEI/ERI and connectivity. I did all the steps you did (manually input IMEI and use the utility to repair ERI and MEID), then reverted back to unrooted stock using odin. I still didn't have signal until I did a factory restet IN THE ROM. Going back to stock using odin and doing a factory reset in CWM didn't fix the issue, but going into the phone's settings and completing a factory reset from there caused my signal and connection to come back.

Categories

Resources