Related
Ok, EVERY ics or above rom wipes my imei and renders the phone useless. I'm not a noob by any means, I follow the directions to the letter, and the imei number is toast EVERY time! I even backed it up, restored it... but it still shows just a bunch of stars. What in the world am I doing wrong?
The trouble started when I flashed the a mtd jb rom. I restored from the backup, got data back, but phone had no sound during calls. I had to go back to stock via a one click to restore the imei number. I was running jb right up until the mtd change. Now, I can't run ANYTHING, CM7 or above. No matter how or what I flash, it wipes the imei
I've been working on this for a week now, can't figure out what I'm doing wrong. I'm lost and back to gingerbread until I figure something out. Any help would be greatly appreciated.
klloyd said:
Ok, EVERY ics or above rom wipes my imei and renders the phone useless. I'm not a noob by any means, I follow the directions to the letter, and the imei number is toast EVERY time! I even backed it up, restored it... but it still shows just a bunch of stars. What in the world am I doing wrong?
The trouble started when I flashed the a mtd jb rom. I restored from the backup, got data back, but phone had no sound during calls. I had to go back to stock via a one click to restore the imei number. I was running jb right up until the mtd change. Now, I can't run ANYTHING, CM7 or above. No matter how or what I flash, it wipes the imei
I've been working on this for a week now, can't figure out what I'm doing wrong. I'm lost and back to gingerbread until I figure something out. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just wondering. Did you back it up with the EFS in the Infuse Toolkit? According to the OP, EFS Partition Backup (protect your phone's IMEI information, find unlock info) forum.xd
http://forum.xda-developers.com/showthread.php?t=1702026
No, I used what ever the app is posted on the jb pages. Quick and simple. Makes a folder called eds backup. Inside u find a .tar file with the whole folder zipped up. I didn't find a place in the toolkit for restoring just that info. I can't even do.cm7 now, anything above gingerbread wipes the imei number, every single time.
If there were a one click to ice or jb, might would help. Beats me. I'm.completely stumped now. Never had trouble flashing anything.
klloyd said:
No, I used what ever the app is posted on the jb pages. Quick and simple. Makes a folder called eds backup. Inside u find a .tar file with the whole folder zipped up. I didn't find a place in the toolkit for restoring just that info. I can't even do.cm7 now, anything above gingerbread wipes the imei number, every single time.
If there were a one click to ice or jb, might would help. Beats me. I'm.completely stumped now. Never had trouble flashing anything.
Click to expand...
Click to collapse
Which JB were you trying to use? You might as well one click back to GB, try the toolkit in CWM, back up the EFS, and then flash one of the ICS ROMS. After flashing ICS ROM and before you reboot, use the toolkit to restore EFS and test it to see if it works. Not sure why it is happening with ICS but you never know what will work sometimes. That's half the fun of testing and most of the frustration of testing.
I know ALL about frustrating! You know, with all I've done, restoring it BEFORE I reboot on the install hasn't even entered my mind! Ill give it a shot. As for which one.... all of them of course!
Ill look closer at the toolkit, maybe it will work. Ill let you know!
klloyd said:
I know ALL about frustrating! You know, with all I've done, restoring it BEFORE I reboot on the install hasn't even entered my mind! Ill give it a shot. As for which one.... all of them of course!
Ill look closer at the toolkit, maybe it will work. Ill let you know!
Click to expand...
Click to collapse
Just curious, but what version of cwm are you flashing from? It was suggested somewhere that it may depend upon if your flashing from cwm5/6 or 3/2, and I believe it may be true.
Sent from my SGH-I997 using xda app-developers app
OK, I've backed up the efs folder via the toolkit, BUT, nowhere.in there is there an option to restore it. I looked and looked! Whole rom,, different scripts, nothing about restoring the info u just backed up.
Now I went from red cwm to cm9, blue, early version. Everything was working fine until I switched from Scott's 8/31 build to cypher.(is that right?) Cyphers worked fine, but I've never been able to flash any other rom since, unless its a gingerbread rom. They all fail. The failures started with paranoid 2.0 9/6 build. I had no trouble until then. I've run every rom out there at one time or another, never had a moments trouble. Now on the other hand, I'm stuck!
BTW, I've even tried roms prior to mtd, still wipes the imei number. That is cm7, cm9 early versions.
klloyd said:
OK, I've backed up the efs folder via the toolkit, BUT, nowhere.in there is there an option to restore it. I looked and looked! Whole rom,, different scripts, nothing about restoring the info u just backed up.
Now I went from red cwm to cm9, blue, early version. Everything was working fine until I switched from Scott's 8/31 build to cypher.(is that right?) Cyphers worked fine, but I've never been able to flash any other rom since, unless its a gingerbread rom. They all fail. The failures started with paranoid 2.0 9/6 build. I had no trouble until then. I've run every rom out there at one time or another, never had a moments trouble. Now on the other hand, I'm stuck!
BTW, I've even tried roms prior to mtd, still wipes the imei number. That is cm7, cm9 early versions.
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/showthread.php?t=1858842&highlight=restore+efs
I actually did the search on here... most of which pertains to the nexus and its imei being incorrect due to a GPS file. The windows file, efspro I've found is missing files, or doesn't work in.windows 7. I've not made it to trying Odin yet, but I'm gonna try tonight. The part that is confusingbme is, why can't I flash files BEFORE mtd? Something has changed...
I've been flashing things since the very day the captivate came out, I've not had trouble till now. Maybe someone can make a heimdall one.click to jb with the new filing system...? I'd pay $20 for for one!
Hi there - I've been lurking on the forum for some time but this is my first post because I've reached a dead end on solving a problem.
Since installing a new ROM, my phone functions don't work. No calls in (goes straight to voicemail) and no calls out. Text messaging doesn't seem to work either (got a text in but can't send out). However, my IMEI number seems intact (tested by dialing *#06#).
Can anyone advise on what may have happened or what to do to get the phone back? Here are my details:
Verizon Galaxy SIII
Rooted and unlocked using this method: http://forum.xda-developers.com/showthread.php?t=1762709
ROM: lost phone function after moving to Paranoid Android 2.0. Currently using official CM nightly.
Kernel: KT747
I will respond asap if you have any questions or suggestions for me. Thank you so much for any help you can provide.
Go to settings > About Device > Status > scroll down until you see IMEI
Write the number down. Pull out the battery and see if the numbers match the imei on back of your phone
Sent from a SYNERGIZED GalaxySIII
I am having the same exact issue after trying paranoid android. Posted about this as well, my IMEI is correct and phone number exists. Gunna try flashing back to 100% stock unrooted, if that fails I'll try and have verizon reset my SIM.
epagib said:
Go to settings > About Device > Status > scroll down until you see IMEI
Write the number down. Pull out the battery and see if the numbers match the imei on back of your phone
Sent from a SYNERGIZED GalaxySIII
Click to expand...
Click to collapse
Yes, they match up, which is great because losing the IMEI seems to be a major nightmare.
Any other suggestions as to what might be the problem?
RedOrm said:
Yes, they match up, which is great because losing the IMEI seems to be a major nightmare.
Any other suggestions as to what might be the problem?
Click to expand...
Click to collapse
Good that imei checks out. I think you're stuck with having to Odin it back to either root66 or stock ROM.
I'm not a programmer so I couldn't guess what caused it. But based from what I've read, aosp based ROMs have had more issues than TW.
If you want to try JB, check out Incubus tw beta's or Remf4t touchmybeans. Both have GPS and minor bugs, but very fast and pretty stable.
Sent from a SYNERGIZED GalaxySIII
Go to stock. If you're still having problems - back up anything you may want and dial *2767*3855# . It will wipe your internal storage and reprovision your phone.
just restore to a backup you have.
Thank you for the input everyone. Going to an old back-up and starting fresh.
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.
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
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.