Help! My phone is blocking ALL incoming phone calls! Help! - Android Q&A, Help & Troubleshooting

Suddenly, my phone has decided to block ALL calls, even from my favorite contacts and voicemail. I just cannot receive incoming calls. The notification shows "Missed call from (blocked) [contact name or phone number]." The [contact name or phone number] part shows the name of the contact or phone number that is being blocked.
EDIT: Outgoing calls work just fine.
I have disabled blocked/black lists on the phone app, removed any restrictions from Hangouts/Voice and any other apps that interfere with the phone functions. I have restarted the phone and restored the phone app from Titanium. I have frozen/uninstalled any third party apps that provide calling/texting functions, such as voice, hangouts, talkatone, etc. I have even cleared cache and removed default app options from phone/contacts.
This problem suddenly started and I just cannot figure out what may be causing this problem. When I search online, it shows listings of apps that block calls, etc., but nothing that addresses my problem.
I am an advanced user - I have root on my current phone (Galaxy s3 with 4.4.2), and have installed custom roms on previous phones (an old Charge, s2, S3), etc. I am not a newbie, so, PLEASE answer my issue without condescension - THANK YOU.
I do not want to factory reset my phone - any ideas about what might be causing this problem and how to resolve it?
Phone info: Galaxy s3 with 4.4.2, rooted, on Verizon (I535).
Thanks.

Verizon tier 2 tech not helping
Tier 2 tech hasn't helped at all!

My only thought would be that what ever file that handled blocked calls got corrupted, and it wasn't removed when you uninstalled it. The only thing that might help is reflashing the rom. Now I never advise a dirty flash due to issues that can come of it but as you don't want to factory reset then it might be an option.
As you are not a noob my suggestion would be to format just the system partition, and reflash. Or you could just reflash. Either way is not 100%

Verizon thinks it might be a SIM card problem. So, I'll replace it and see how that works. If not, a bloody re-flash it will be.
Any other ideas in the meantime?
Thanks.

Related

[Q] Can no longer receive calls!!! *resolved*

Seems that all of a sudden I can no longer receive calls. I thought it was just certain people since I had received calls before but now the people who were successful in the past can't get through any more. It's either just dead or says call not allowed from this device or those beeps you get when the recording says "if you'd like to make a call...".
I'm wondering if I inadvertently did something to cause this. I'm totally new to smartphones, android and sense. I've gone through settings that I know I went into and I can't find anything. I rebooted phone, leaving it off for a few minutes, still no incoming calls. I can call out though, even before reboot. Have not done any temp rooting since I'm still reading up on all that stuff and don't have a grasp on it yet.
I did install some apps but this seems to have started without connection to that although I can't be certain. I can gather a list of them if needed.
I'm thinking of doing a factory reset. I've backed up all the pics and videos I took over thanksgiving to my computer and I believe there's only one app that wasn't free that I got from the Amazon app store. Will all my contacts stay if I do a factory reset? I still have my old phone so I suppose I could get Verizon to transfer them over again, or maybe I can get them off my car since I just put them on there.
Oh!!! Would it have anything to do with me having set it up to use in my car? I was sending out music via bluetooth so I had to set it up as a "portable player" in my car. Maybe I changed something in the phone... I can't really remember and I'm not finding any settings in the music app or in the main settings.
Anybody know if there's something I might have done? Am I safe to do a factory reset?
Edit: One other thing I did to the phone was add a "Music" folder on the external sd and put in a bunch of music. I couldn't find how to do this in the manual or via google so I just hooked it up to my computer and tried that and it worked as far as listening to music. Doubt it would affect phone but wanted to be complete in this post.
Installing apps and making music folders should in no way affect your ability to receive phone calls. Sounds like you need to call Verizon.
punman said:
Installing apps and making music folders should in no way affect your ability to receive phone calls. Sounds like you need to call Verizon.
Click to expand...
Click to collapse
Agreed, before you go resetting anything call *611 from your handset or whatever Verizon's 800 number is and see if they screwed something up(more than likely)
punman said:
Installing apps and making music folders should in no way affect your ability to receive phone calls. Sounds like you need to call Verizon.
Click to expand...
Click to collapse
MrSmith317 said:
Agreed, before you go resetting anything call *611 from your handset or whatever Verizon's 800 number is and see if they screwed something up(more than likely)
Click to expand...
Click to collapse
Yeah, I called earlier but I don't have another phone to call from so I'll have to go down there. I made her promise they would compensate me for my time since I complained about switching from AT&T and having problems already.
Hahahaha.... I inadvertently turned on call forwarding and it was forwarding to number 9. I know exactly how I accidentally did it too. I was clearing out my old AT&T contacts which had come over and they all start with *. I wanted to be certain they were not Verizon numbers so I dialed each one first and one of them activated the forwarding. I didn't seem to get any notification of it being turned on that I noticed.
Needless to say I thanked the guy at Verizon for finding out what it was and did NOT ask for any compensation.
Glad you got it all figured out I would have been in panic mode!
I almost did that when he started talking about me having to return it to Amazon for a replacement. I immediately started thinking no! I have red buttons! My phone doesn't overheat or reboot on its own! What if I get a bad one. Plus they're on backorder there! I need a phone, my old one is AT&T!! LOL.

[Q] SMS Error Code 98

EDIT: 11:15pm 9/25/2012 - ISSUE RESOLVED, SEE BOTTOM OF POST FOR SOLUTION
Okay, relevant information first:
Evo 4G LTE on Sprint
HBOOT 1.15 S-ON HTC DevUnlock
Current ROM CM10 Nightlies
Sprint-Google Voice integrated number
Now for the issue:
Texts can not be sent through the messaging app. When attempting to send a text, it will say "sending..." for a few seconds, then I get a notification saying "message not sent". Clicking on this notification takes me to the messaging app where the failed message has a red triangle next to it. When I long press the failed message, it comes up with a menu, and when I click "view details" it says "Error Code 98".
This happens both when connected to WiFi and when not connected to WiFi. It also happens both in my home town, and another town 45 minutes away (meaning the issue doesn't seem to be with the particular tower).
The last successful text sent or received was on Sept 13th.
Calls still operate as normal.
No changes were made by me between when my SMS was working properly, and when it stopped working. (Same ROM, Recovery, Kernel, etc). I haven't downloaded any SMS apps (handscent, gosms, etc) that could be interfering with the messaging app. I DO have the Google Voice app, but I had that when SMS was working properly as well, and the GV app hasn't been updated since March (meaning it shouldn't have changed how it was behaving).
Other peculiar behavior:
In addition to not being able to send texts via the messaging app, it seems that my number is also unable to receive texts. When texts are sent to my number, my phone does not receive them and they also do not show up in my Google Voice inbox. The sender is given no notice that the text has not been received. I am able to send texts from the Google Voice app, and others successfully receive them. When I send a text to myself from the Google Voice app, I receive it in my Google Voice app, but not in the stock messaging app (even though my Google Voice app settings say that texts will be received via the messaging app).
Things I've Tried (Updated: 3pm EST, 9/25/2012 ):
* Turning it off and on again
* Updating CM10
* Changing Google Voice settings (though it's possible I overlooked a setting)
* Factory Reset, Reflash ROM
* Flash Sense ROM, Update Profile/PRL
* Flash different AOSP ROM (Paranoid Android)
Things I've Not Tried (in order of how willing I am to do the things):
* Using an alternate SMS app (GoSMS, Handscent, etc)
* Un-integrating (and Re-integrating) Google Voice
* Giving the EvoLTE a relaxing bubble bath, to calm it down
* Flash Stock, Unroot, Update Radio
So, does anyone know what might cause this problem, and/or how to resolve it?
EDIT: Solution below
STORY:
I called Sprint Support, and had them reactivate my old phone (Evo4G running a CM9 alpha), by giving them the MEID for that phone. At this point I powered the phone back on, and called an activation number that they had given me (888-546-0314). On a Sense ROM, I would have simply updated my profile, instead of calling the number. We then tried SMS on the reactivated phone, and it worked (also, texts began showing up in Google Voice again at this time). I turned off my Evo 4G LTE, then I gave him the MEID for it and had him switch my number back to that phone. After he said he had switched it, I powered the Evo 4G LTE back up, and updated the profile, which I was able to do since I was still on Viper4G (note: I had to update the profile via WiFi, it might have worked over data, but it was taking longer than expected so we cancelled and just use WiFi for the update). Once the profile had updated, I called the test number again to confirm that the phone was activated. When I tried SMS, it worked as it should, including sending a copy to Google Voice.
TL;DR:
1. Find an old phone
2. Write down the MEID of both phones
3. Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call)
4. Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
5. Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
6. Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
7. Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
Update: Clean flash of Paranoid Android did NOT resolve the issue. Still getting "Error Code 98".
So, this tells me/us this is not an issue with CM10 (which is not surprising, since I have no idea how what ROM I have flashed would keep Google Voice from receiving the texts as well).
This may sound odd but try moving the time up an hour or back an hour, error 98 is a problem with home agent, it's a sprint network error. I don't know of anything else that's helped
Try calling sprint and ask them if they can do anything. When I went s-off I had to call them bc my calls and text had errors. Data worked though.
They pushed something that fixed it in less than 10 seconds. Just wanted me to verify my account.
I tried changing the time 1 hour forward, and 1 hour backward, neither of those resolved the issue.
On hold with the Sprint tech department (it's taking longer than 10 seconds, but hopefully they figure out how to fix it.)
EDIT:
Mini-Update: Flashed Viper4G (a sense ROM), problem persists.
Updated profile and PRL while in Viper4G, problem persists.
Was told by Sprint technical support to press ##6-digit-MSL-here# and edit something, then reboot. Did that. Problem persists.
SOLUTION
The problem has been resolved, and the OP has been edited to include the method used to solve the problem.
If this was a game, Anthonicia would win for being closest (though it took closer to 2 hours on the phone with Sprint to fix the issue, if we include all four calls I made, 20-30 minutes if we only include that final one).

[Q] "Message not sent" only on SMS

I have recently purchased a new i605, rooted, unlocked, and installed TWRP through Casual. And flashed CM10.2-20130827-Nightly-i605. I finally received my SIM cutter in the mail today, and pulled the full size Straight Talk SIM out of my Skyrocket that I have been using with no issues for almost 2 years, cut the SIM, put it in the Note 2, and entered the APN settings. It is receiving good signal, showing the "H" and "H+" the majority of the time. I can make voice calls, receive voice calls, send/receive MMS, and have good data sending and receiving. My only issue is, I can only receive SMS, and when I try to send (or reply to one already received) I get the "Message not sent" error. I saw a possible fix, of updating your SMSC, but I have no clue how to find what my SMSC is in order to input it, and haven't been able to find it either. I tried editing the way the telephone numbers are stored from +1 250-250-2500, to (250)250-2500, +12502502500, +1 (250)250-2500. I also saw where someone found a fix for their situation, where they had accidentally set Google Voice to send text messages. I went into the settings on my Voice app, and that setting was turned on, so I turned it off. But I am still having the same results when trying to send an SMS.
Does anyone have a clue as to how I can find what my SMSC is, so that I can try that fix for the issue?
Did I post this in the appropriate subsection of the Verizon Note 2 forum?
I'm in the exact same situation you are. Send/receive calls, receive texts but can't send texts. I received a new note 2 through insurance two days ago and did the same process of rooting the phone, except I flashed jedix17 on it. So I'm guessing the problem lies in the roms? I haven't had time to switch roms to see if that fixes it though. I'd like to see if there's an easier alternate solution as well.
Ok, I got to playing with the "fixes" I had already attempted, for a second time. Google Voice was set to send SMS, and I would change the setting in Voice to make the messaging app send SMS. Well, I noticed that after closing Voice, then going back to the settings in Voice, it would be set to Google Voice sending SMS again. So I Force Closed the Voice app, and uninstalled it, and the issue cleared up. I have no idea why the app would be automatically changing it's own settings back, after closing it though.
I see. Then it seems you and I don't have the same root problem. I don't have an alternative texting app, so I guess I'm off to reflash my rom.
kevinyoki said:
I see. Then it seems you and I don't have the same root problem. I don't have an alternative texting app, so I guess I'm off to reflash my rom.
Click to expand...
Click to collapse
Did you figure out your issue? If you flashed Gapps, you may have Voice+. Check in your app drawer just to make sure.
Yeah I have fixed it Thanks for asking (and yeah I did check and I did not have voice). Reflashing the rom did indeed work

Call History / Recent Calls Refuses to Display Actual Call history - Google and Stock

Hi All - I'm really hoping to get some ideas from the forum on this issue as it's been plaguing me for a while and I can't figure it out.
I have a Rooted Samsung S8+ on Nougat 7.0 which root was achieved flashing Partcyborg ROM through Odin. It's commonly used method for those that don't have S8+, the bootloader is locked though.
That being said my issue isn't with the rom / root method, it's with Google Dialer and the Stock Samsung Contacts / Phone application. For some reason I think the Call History backup is corrupt or something like that because no matter if it's an incoming or an outgoing call, my call history and recents menu in either application is blank. For example, if someone called me right now and I didn't answer, I'd see the call in the history as the only call but by the end of the day, or after a restart of the phone... My phone will show no recent calls and provide no record of call history for that call.
Even more strange, I do show a record of calls but they are 14-15 records of calls at random dates, I want to say the most recent is from April. No matter what, they always stay. DOesn't matter if data is cleared, cache is cleared, dalvik-cache wiped, preferences reset, app defaults reset, install/reinstall, install diff versions, change permissions, this happens.
I used SQLlite Browser to go into the database and the DB does show the records I talked about earlier, the 14-15 calls. I've even tried deleting the database in hopes that maybe it'd reset itself. Nope.
This behavior is persistent across device resets, it also occurs when I completely remove Google Dialer Framework and Google Dialer altogether. Im at a loss and trying not to get back to stock.
Any ideas as to where to dig further?

No sound on VoLTE and automatical hang-up on WiFi Calling

Unlocked phone on T-mobile, US.
I'm not sure when this gets started, but I've noticed it after the April update. When on VoLTE, there's no sound for incoming or outgoing calls. When on WiFi Calling, it auto hangs up as soon as the call is picked up.
Any input is highly appreciated. Thanks in advance!
judsonzhao said:
Unlocked phone on T-mobile, US.
I'm not sure when this gets started, but I've noticed it after the April update. When on VoLTE, there's no sound for incoming or outgoing calls. When on WiFi Calling, it auto hangs up as soon as the call is picked up.
Any input is highly appreciated. Thanks in advance!
Click to expand...
Click to collapse
I had an issue recently where all calls I made (wifi calling or though the stock dialer app) would auto hangup and never go through. Incoming calls seemed to work fine though.
I did a factory data reset and set everything up back from scratch, that was the only way to fix it. This maybe something worth trying if you haven't done it already.
If you do a restore of any backup data (i.e. smartswitch, google backup) I would suggest using the google backup and not the smartswitch this time. I made a smartswitch backup before the factory data reset, but ended up not being able to use it. Everytime I did a restore with the backup the same thing would happen. I had no problems with the google backup.
Also if the problem persists (or if you opt to do so anyways, maybe worth trying anyways) I would call T-Mobile support and ask them if there are any problems or etc. It maybe possible they are working on the towers near you, as one time my service was being a little quirky and it was due to them doing some low/mid band additions on nearby towers. They may just need to refresh your phone on there end or send you a replacement sim card in case a problem exists with the one you have..
scottusa2008 said:
I had an issue recently where all calls I made (wifi calling or though the stock dialer app) would auto hangup and never go through. Incoming calls seemed to work fine though.
I did a factory data reset and set everything up back from scratch, that was the only way to fix it. This maybe something worth trying if you haven't done it already.
If you do a restore of any backup data (i.e. smartswitch, google backup) I would suggest using the google backup and not the smartswitch this time. I made a smartswitch backup before the factory data reset, but ended up not being able to use it. Everytime I did a restore with the backup the same thing would happen. I had no problems with the google backup.
Also if the problem persists (or if you opt to do so anyways, maybe worth trying anyways) I would call T-Mobile support and ask them if there are any problems or etc. It maybe possible they are working on the towers near you, as one time my service was being a little quirky and it was due to them doing some low/mid band additions on nearby towers. They may just need to refresh your phone on there end or send you a replacement sim card in case a problem exists with the one you have..
Click to expand...
Click to collapse
Thank you so much for the input! I'm going to factory reset this evening. And if it still persists probably call Tmo. But I guess the chance is low, my other device works just fine with Tmo (both wifi calling and volte)
Let's see! Have a good one!

Categories

Resources