Related
I've run into this on multiple ROMs, and every time it seems like it only affects some people. As far as I've been able to find, the common link hasn't been found. It has now, and the fix is incredibly simple.
Settings > Applications > Manage Applications > All > Dialer > Clear Cache
Reboot
Do not restore SMS/MMS/APN Dialer storage data
This was posted in the VaelPak thread, but wanted to get it out there for everyone.
Edit:
I tested this on a fresh install before posting.. both breaking it and then fixing it. But when I restored my broken nand backup, the fix did not work. So mileage may vary, but flashing a fresh install and not restoring the dialer storage should still be a winner.
See post #4 for another confirmed cause and fix
THANKS! Been having this issue since and I didn't feel like searching everywhere for this...until you posted it up here, which made my day a breeze!
Thanks awesome find
There is more to this.
The original cause and solution were both confirmed, but another one has been found. It was caused by a battery mod. So conceivably MMS could be broken by any UI mod that includes /system/framework/framework-res.apk
The good news is, replacing the file with the one that came with your rom should fix MMS after a reboot.
This cause and solution have also both been confirmed. But what about the mod that did it is not known right now.
There seems to be many causes to this problem and seems a fix is based upon each individual and there phone. I see people with this error from a factory ROM and fresh phone. Some issues can also be fixed by un-checking delivery report/read report in messaging settings.
*UPDATE* ~ Possible Fix ~
Not sure if this applies to all but it fixed my problems altogether. In the apn settings there are 2 listed one for Internet and one for MMS. Take the MMSC, MMS Proxy, and the MMS Port settings from the MMS apn and copy those to the internet apn. No need to reset. And don't delete any apn's either.
I can t get this to work
hey can you help me out-I keep flashing unrevoked-forever-son.zip repeatedly and it doesnt work-It keeps saying s-off.I have clockworkmod recovery-I need to turn s-on because i have to take my evo back to a sprint repair shop.my 4g radio got hosed.I must have deleted the keys-I was able to correct my mac address however 4g will still not connect
clownberg said:
hey can you help me out-I keep flashing unrevoked-forever-son.zip repeatedly and it doesnt work-It keeps saying s-off.I have clockworkmod recovery-I need to turn s-on because i have to take my evo back to a sprint repair shop.my 4g radio got hosed.I must have deleted the keys-I was able to correct my mac address however 4g will still not connect
Click to expand...
Click to collapse
Don't worry about it?
This isn't even the right thread for that.
I just returned an Evo, rooted, with a custom ROM on it. They didn't care. The chance of them seeing S-OFF instead of S-ON is pretty much zero.
is this the same problem as
when roaming i am unable to make calls nor connect to the internet. i tried calling and i get this message
"unable to connect, this is an unauthorized devise on the Verizon network...please try your call again........"
I had this issue and it was due to a messed up xml file in system/customize/MNS/default.xml
Unfortunately for me, the only way I fixed it was to hard reset with with the proper edits to the file.
I was learning how to build ROMs and edit certain xml files and I guess I screwed up the syntax of this particular one and ruined my MMS
bluediablito said:
is this the same problem as
when roaming i am unable to make calls nor connect to the internet. i tried calling and i get this message
"unable to connect, this is an unauthorized devise on the Verizon network...please try your call again........"
Click to expand...
Click to collapse
Not the same. Call sprint and tell them you can't make calls while roaming and that you get the verizon message. Tell them you need to repush the network information. That'll fix it quick.
Voicemail problems
Don't know if you guys can help out, but I can't find a thread on this anywhere. My voicemail is not working period. I will call from another phone and leave myself a voicemail. Go to check it and it is no where to be found. I am running fresh 3.2 and kingkernel bfs #9. Any suggestions?
hounie2286 said:
Don't know if you guys can help out, but I can't find a thread on this anywhere. My voicemail is not working period. I will call from another phone and leave myself a voicemail. Go to check it and it is no where to be found. I am running fresh 3.2 and kingkernel bfs #9. Any suggestions?
Click to expand...
Click to collapse
I use Google Voice -- It will replace your current VM system and also sends you emails with your voicemail transcribed into text... give it a shot!
I also use it to ask me to use Google Voice to dial out or allow android to dial...because I hate dialer and if you hit connect/call it immediately dials the first number on the list.. googlevoice at least lets me choose which one I want or none at all.. Its like putting a condom on voice dialer! (Ok, not really, but....)
^ that or youmail. I like youmail because if the phone doesnt ring sometimes (out of reception or if youre on a call sometimes) youmail will send you a email or text showing the missed call. I archive all missed calls/voicemails (for work) so it works out perfectly.
back on topic, I tried deleting the dialer storage, but my mms settings still show some wierd Orange.UK url for the mnsc and i have no idea how that happened. I will try to reflash the rom and see if that fixes it...
Thanks for the suggestion, just got everything setup. Google voice works like a charm.
I'm posting this on the four android-related forums that I participate in, in hopes that someone has seen this before and knows what to do.
Here's what I had:
- Droid 2 Global, unlocked, rooted, with Fission ROM, using Rogers Wireless, a GSM network in Canada
- it had been working just fine for 5 months
Here's what I did:
- Used RSDLite and the SBF loader to flash the stock 2.4.330 firmware as seen here: http://droid.koumakan.jp/wiki/SBF
- ended up with a bootloop, as the directions said I would. cleared data and cashe, no problem, phone booted.
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- Used stock recovery mode to upgrade to 4.5.607 (gingerbread) firmware as seen here: http://droid.koumakan.jp/wiki/4.5.607_Firmware
- I used the file linked to from here: http://www.droid-life.com/2011/08/22/gingerbread-build-for-the-droid2-global-leaks/
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- rooted phone using the adb method that is out there. rebooted and confirmed root access. installed a couple apps that need root. tested phone functionality, all was well. used APN backup/restore and APN Manager to make backup files of my APNs
- As described here, http://droid.koumakan.jp/wiki/CyanogenMod Installed Droid 2 Recovery Bootstrap and ROM Manager in order to flash CWM. rebooted into CWM, factory reset, installed the latest release (10/06), and rebooted
- started up phone, switched to GSM mode, phone app crashed immediately (as is to be expected, based on known bugs), rebooted for it to take effect
Now here's the problem:
- phone can make calls and receive texts with no problem, but cannot get data. wifi also works.
- went into wireless settings, mobile networks, access point names, nothing shows up. Clicked "add APN". entered the APN info that had worked for me before at the past two junctions. hit menu button, then save. takes me back to the APN screen, but no APN shows up.
- repeated this cycle a few times following reboots, etc. Eventually the phone gets to the point where the "add APN" button will not even come up when the menu key is hit.
- during the above, was also checking the "network operators" setting. The phone does locate all of the networks that are "in the air" but no matter which one I choose it will tell me "your sim card does not allow a connection to this network"
- used root explorer to check /data/data/com.android.providers.telephony/databases/telephony.db. There is a list of about 1500 APNs. There are multiple entries for Rogers including all of the ones I tried to enter that appeared not to save.
- used APN backup/restore and APN manager to attempt deleting existing APNs, restoring the ones that were known to work, etc. Nothing works. These programs do work, and when I check the telephony.db file I can see what they have done to the file, but they are unfortnately unable to make any APN "stick" at the APN screen, and apparently that is the only way that it will work.
more info:
- I've noticed that the list of rogers entries seems to get larger and larger as I go through this process multiple times. I may be wrong, but it seems that this telephony.db file might not actually get changed or updated when you flash a new kernel/firmware/mod/rom to the phone.
- I'm sure that the lack of a list of APNs and the "sim card does not allow connection" message are related. For whatever reason there seems to be a bug in CM7 where the telephony.db file has problems "talking" to the APN screen in settings. But it must not affect most people.
- yes, I have tried a new SIM card.
- yes, I have tried clearing cache, data, dalvik, and fixing permissions.
- Anyone else on Rogers Running CM7 on a D2G? If so, I'd love to talk to you. Maybe I could convince you to send me a working CWM backup. I imagine that if you're a conscientious rommer, you have a backup made folling a fresh install of CM7.
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Edit: I have a XT860 which is in for repairs - once I get it back and I have a reliable daily phone I plan to experiment with the new GB based CM4D2G. Hopefully this week...
leobg said:
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Click to expand...
Click to collapse
Yes, everything works really well with stock rom. I was quite impressed, as it was my first GB experience. Unfortunately, as with cars, I am all about the "options", and I can't seem to let go of a feature once I have experienced it. I love CM7 and I really want to make it work for my D2G.
I posted this same thing at the rootzwiki thread, and one of the head developers said "You my friend may finally have identified where the gsm data issues are coming from. it isnt just you, it's 98% of the gsm users that arent having data". Another user got me to change a couple of permissions. I thought he was onto something but it didn't work, either. Nonetheless, I think I brought enough attention to this issue and also gave them something to work with through all my trial and error. I am optimistic.
But, for now, I think I have to take CM7. I want my data! I am really tempted to just give stock GB a shot. But Blur scares me. Most people don't seem to like it, though I admit I don't fully understand what Blur is! I see there is MIUI and apex, angel Hexen and VenusX. I might have to try them first.
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
greek_lover_69 said:
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
Click to expand...
Click to collapse
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
seventieslord said:
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
Click to expand...
Click to collapse
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
I wish it was that easy, but it's not. I have tried a number of solutions similar to that but no dice. I appreciate the attempt though.
Sent from my DROID2 GLOBAL using XDA App
For the record I have that problem on the D2g flashed with the latest builds of cyanogen rom, (with the same SIMs perfectly working on D3 and D2g with the stock rom), and the airplane mode trick doesn't works too.
So far I haven't found a solution
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Thanks, i guessed that if a proper fix may be hard to find, a workaround was easy enough, I'll try it later with the gingerbread froyo.
dobosininja said:
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Click to expand...
Click to collapse
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
seventieslord said:
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
Click to expand...
Click to collapse
I gave this a try, and no dice. Too bad.
Thanks anyways.
The Solutor said:
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
Click to expand...
Click to collapse
I now own a D3. CM9 is doing the exact same thing to me!
I tried what you said and I am still not getting data. phone and texts work though, just like before.
I previously had CM10 on my S3 and updated to the new CM 10.1 after that my phone started acting weird, wouldn't want to sync any google data like contacts. So I tried installing a different ROM like clean ROM and the executioner ROM. I can't make calls at all even though my phone says 4G. I don't know if the IMEI might have gotten messed up. It asks me if I want to enter global mode, I don't know what to do. I do have an IMEI back up that I made using QPST but i'm not sure how to restore it (yeah silly noob) can anyone help me get my phone back to normal?
84 views and no reply?
mep1127 said:
84 views and no reply?
Click to expand...
Click to collapse
After you make a call. Go to settings. Mobile Network Settings. CDMA Subscription. Switch from NV to RUIM/SIM. Reboot. Try to make a call.
fixes?
what was you resolution to this problem? im having the same problem.
I was having issues on my rooted verizon galaxy s3 running beans version 15. I would get a circle on data when tethering. I went back to root66 learned my IMEI and ERI were set to zero and now they are at 5 and the correct things...I have data I've had it 4g LTE that is and can tether just fine. I'm using my phone currently to ask this question. I cannot dial or send texts...on beans it just says dialing with no tone on root66 it would say no network available. My # shows my service is there...when I click LTE/CDMA in network it says searching and I hit ok. I don't know if that means it needs to search first or what...I really don't know what to do I have searched all day and done everything I know to do and now I'm just lost. I also did *228 and it said my sim wasn't registered then I rebooted and did it and it worked....so no clue what is going on.
Under phone status my phone said Service State: Out of Service when on root66 but now it says In Service. Still don't understand this.
Mobile network state: connected in root66 it was trying to connect randomly.
Phone #: Correctly displayed
Prl and ERI Version: 15211 and 5
Device State: normal.
Everything seems good : (
StriferZer0 said:
I was having issues on my rooted verizon galaxy s3 running beans version 15. I would get a circle on data when tethering. I went back to root66 learned my IMEI and ERI were set to zero and now they are at 5 and the correct things...I have data I've had it 4g LTE that is and can tether just fine. I'm using my phone currently to ask this question. I cannot dial or send texts...on beans it just says dialing with no tone on root66 it would say no network available. My # shows my service is there...when I click LTE/CDMA in network it says searching and I hit ok. I don't know if that means it needs to search first or what...I really don't know what to do I have searched all day and done everything I know to do and now I'm just lost. I also did *228 and it said my sim wasn't registered then I rebooted and did it and it worked....so no clue what is going on.
Under phone status my phone said Service State: Out of Service when on root66 but now it says In Service. Still don't understand this.
Mobile network state: connected in root66 it was trying to connect randomly.
Phone #: Correctly displayed
Prl and ERI Version: 15211 and 5
Device State: normal.
Everything seems good : (
Click to expand...
Click to collapse
I'm having the same problem. I haven't yet gone back to Root66, because that is going to be a major pain (really REALLY don't like using ODIN and haven't found a flashable zip to use from CWM), and my phone has had trouble staying connected to a computer ever since I took it out in a snowstorm a few months back, so I'm nervous that doing stuff via ODIN is going to end poorly. This was after I flashed to Carbonrom 1.7, which is Android 4.2.2. Initially I got stuck on the activation screen, with no phone number, nothing, but after I switched my CDMA subscription mode from NV to RUIM/SIM, I got the phone number and PRL version back. Phone number now appears correct, and PRL version is 15223. IMEI still reads 0, though. I had an IMEI backup from back when I first flashed from ICS to JB, but restoring it doesn't seem to have any effect. I'm going to keep looking for a flashable Root66 zip, and if not I'll see if I can get something to work via ODIN (or see if I can maybe get the AOSP modem solution thing to work though the script I found didn't run) and report back. I don't do a whole lot of phone calls, and data is working fine, so it's not a hugely pressing issue, but I do want to get this solved ASAP. If anyone's got any thoughts or input, I know we'd both appreciate help. In the meantime, I'll press on and we'll see what happens.
adiv.paradise said:
I'm having the same problem. I haven't yet gone back to Root66, because that is going to be a major pain (really REALLY don't like using ODIN and haven't found a flashable zip to use from CWM), and my phone has had trouble staying connected to a computer ever since I took it out in a snowstorm a few months back, so I'm nervous that doing stuff via ODIN is going to end poorly. This was after I flashed to Carbonrom 1.7, which is Android 4.2.2. Initially I got stuck on the activation screen, with no phone number, nothing, but after I switched my CDMA subscription mode from NV to RUIM/SIM, I got the phone number and PRL version back. Phone number now appears correct, and PRL version is 15223. IMEI still reads 0, though. I had an IMEI backup from back when I first flashed from ICS to JB, but restoring it doesn't seem to have any affect. I'm going to keep looking for a flashable Root66 zip, and if not I'll see if I can get something to work via ODIN (or see if I can maybe get the AOSP modem solution thing to work, though the script I found didn't run) and report back. I don't do a whole lot of phone calls, and data is working fine, so it's not a hugely pressing issue, but I do want to get this solved ASAP. If anyone's got any thoughts or input, I know we'd both appreciate help. In the meantime, I'll press on and we'll see what happens.
Click to expand...
Click to collapse
I had an issue installing carbon rom too a while back but just went back to stock and then redid everything from there...this is my first time encountering such a huge issue that I can't solve on my own. Everything seems FINE now..IMEI everything was repaired and fixed. Odin takes around 12-15 minutes if you wanted to try that...How did you change your subscription mode? Maybe there are some things I haven't tried yet....if so I'd like to know how and where.
StriferZer0 said:
I had an issue installing carbon rom too a while back but just went back to stock and then redid everything from there...this is my first time encountering such a huge issue that I can't solve on my own. Everything seems FINE now..IMEI everything was repaired and fixed. Odin takes around 12-15 minutes if you wanted to try that...How did you change your subscription mode? Maybe there are some things I haven't tried yet....if so I'd like to know how and where.
Click to expand...
Click to collapse
System Settings>More...>Mobile Networks>CDMA Subscription.
I had issues with Carbon 1.6.1, and flashed back to 1.5, which was great except that occasionally normal-pressing the home button would start registering as a long-press until I rebooted. Decided to try Carbon 1.7, then this happened. As I understand it, though, whether or not your IMEI gets borked is a bit of a matter of chance, not necessarily ineptitude on the part of a ROM's developer team. That's why you're encouraged to backup your IMEI before any serious system modification. Dunno why my backup isn't working, though... that part is what's most annoying.
adiv.paradise said:
System Settings>More...>Mobile Networks>CDMA Subscription.
I had issues with Carbon 1.6.1, and flashed back to 1.5, which was great except that occasionally normal-pressing the home button would start registering as a long-press until I rebooted. Decided to try Carbon 1.7, then this happened. As I understand it, though, whether or not your IMEI gets borked is a bit of a matter of chance, not necessarily ineptitude on the part of a ROM's developer team. That's why you're encouraged to backup your IMEI before any serious system modification. Dunno why my backup isn't working, though... that part is what's most annoying.
Click to expand...
Click to collapse
Man I don't know. I only use my phone when it comes to calls and keeping up with anything work and personal. I don't know where to begin..wish I could reset everything lol
StriferZer0 said:
Man I don't know. I only use my phone when it comes to calls and keeping up with anything work and personal. I don't know where to begin..wish I could reset everything lol
Click to expand...
Click to collapse
That you can do. There are multiple guides out there for completely resetting back to stock, for situations like needing to return a phone to Verizon and wanting to erase any trace of your fooling around with OS components. For me, I seem to be completely unable to connect the phone to computer via USB, so ODIN is completely out. Thinking I might bring it to Verizon and see what they can do. I've currently got it on JellyWiz RLS13, which is based on the stock TW JB OTA, so hopefully that's close enough that it won't throw any flags for them and they can do some magic or something and reset the IMEI.
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
TenderloinShadow said:
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
Click to expand...
Click to collapse
Go into About Phone -> status check your IMEI and PRL and such are they still there?
buhohitr said:
Go into About Phone -> status check your IMEI and PRL and such are they still there?
Click to expand...
Click to collapse
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
TenderloinShadow said:
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
Click to expand...
Click to collapse
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
The problem i had i couldn't recieved calls. Everything worked fine..
I ended up getting new sim card then the employee dialed *73 then my fone was back in action
buhohitr said:
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
Click to expand...
Click to collapse
yeah I figured that would have to be the answer from the beginning. Have to Odin back to stock first, won't be able to do that for probably another 3-4 hours because of a work meeting that's about to start, so I figured I'd ask around.
If anyone has any other ideas, I'm open to them. Otherwise I'll reprovision tonight and report back.
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
beepea206 said:
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
Click to expand...
Click to collapse
+1
Flash back to stock, or a stock based rom with stock messaging. Try to force the message through. My messages stopped sending on aosp messaging and was persistent through rom flashes. I eventually forced it through using touchwiz messaging.
Sent from my SCH-I535 using Tapatalk 2