So I just rooted my SM-G950F with magisk also installed the no verity.
Everything went fine except one thing.
I can not make any calls, recieve calls or send text.
Only thing that works is my mobile data and recieving texts.
How can I fix my calling issue?
Flash it back stock.
Did not work, tried that.
And you did not flash any custom roms? Just like installed Magisk and non verify patch?
Related
My OnePlus is running on Cyanogenmod 13 by @Grarak. It is so good, that i don't want to shift to any other rom. Thank you @GRArek. But a small problem persists. I can't receive calls. And when i receive a call, the phone reboots. And i don't get any notification about the call. I am pretty sure it's something to do with my phone. Because i tried Resurrection Remix too. The Problem still persisted. I can switch to Oxygen OS but i don't want to. Has anyone experienced the same error or does anyone have the fix?
Thank You very much.
Are you sure you were running OxygenOS 2.2.1 before flashing Graraks latest? Sounds like some of the partitions for the modem must be wrong, I'm using Graraks latest workout calling problems. Once suggestion is to use the Qualcomm restore method to restore back to 2.2.1 and then flash TWRP and clean flash Graraks.
First use twrp to flash full oxygen 2.2.1.
And start again installation of cm13.
If don't work then use fastboot images method.
Sent from my ONE A2005 using Tapatalk
Hi all,
When I flash the rooted boot image, everything goes fine. However, I can't make or receive phone calls or texts. I've tried resetting the PRL and profile, but that does nothing. The APNs look normal to me. I'm running Marshmallow. When I try to send a text I get an error "code 97."
Any suggestions?
silverHound said:
Hi all,
When I flash the rooted boot image, everything goes fine. However, I can't make or receive phone calls or texts. I've tried resetting the PRL and profile, but that does nothing. The APNs look normal to me. I'm running Marshmallow. When I try to send a text I get an error "code 97."
Any suggestions?
Click to expand...
Click to collapse
Any reason why you are rooting? Like a specific reason?
lvpre said:
Any reason why you are rooting? Like a specific reason?
Click to expand...
Click to collapse
Yeah, I got the Nougat OTA update, and wakelocks have been killing my battery life. I downgraded to Marshmallow and installed Xposed to use Amplify to control wakelocks.
Never mind. Got it working with this method: https://forum.xda-developers.com/sp...g930p-root-t3410604/post71266592#post71266592
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
SashaNT86 said:
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
Click to expand...
Click to collapse
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
If that fails try returning to stock to see if the problem persists. Occationally mms dysfunction can be upstream and require carrier involvement.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
A dirty flash seems to have done the trick,though I will say I used a different download for the flash. Loving it so far.
Thank you for the help!
Davey216, I will keep that in mind if it comes back. Stock is kinda icky but I need my mms. Thank you for the reply!
hey,
is there any one experiencing incoming call issue , from other end if someone calls rings from their side but on phone there is no ring is coming and that calls goes to voicemail
I get that sometimes but only when my phone has been locked for a long time. Feels like calls don't come in because of some doze setting.
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
alwynjoshy said:
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
Click to expand...
Click to collapse
Unfortunately I haven't found any solution. It still happens to me sometimes when my phone is locked for a while.
Now i. Am using non treble AeX rom, its okay still now no issues
Try change "preferred network type" to Global. Doing that solved the issue for me.
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Oki said:
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Click to expand...
Click to collapse
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSM or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
christoophat said:
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSMA or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
Click to expand...
Click to collapse
Sorry @christoophat, I wasn't answering you since you hav already found your fix. As you, I was adding info to bring some light to the issue, thinking on the other members still having the issue. I was asking them to try other things so we all could figure out all the possible causes of this behavior. I am in T-Mobile USA and I don't have the issue. I had to recover an old backup to reproduce the issue.
I am also on TMo USA too.
Hi all--
I wonder if you could please help me solve a tricky issue?
Before rooting, phone worked fine. Brand new Moto 5G Plus activated on Sprint network.
After rooting my G5 Plus with a custom rom (Dirty Unicorns), everything worked fine except I lost my LTE signal (Sprint). The phone functions in all other capacities (calls, SMS, wifi). To be clear, the phone is receiving a Sprint signal, but no data LTE/3G is passing through. Phone calls and SMS are fine.
When I go to Settings-Network & Internet-Mobile Network-Advanced-Carrier Settings, I get an error-- "com.android.phone has stopped."
I decided to test with another reliable custom rom so I installed LineageOS 15.1. Same exact problem-- no data, and carrier settings brings up ""com.android.phone has stopped."
Any ideas? I've googled myself to death and I've not found anything that has worked.
Thanks in advance, everyone.
Could you get us trough ur procedure of flashing ?
Sure
All done in TWRP
Factory reset (wipe data/dalvik/cache)
Install Custom Rom (either Lineage 15.1 or DU v12.5.2)
Wipe cache/dalvik
Install GApps (ARM64-- I tried to install 32-bit GApps as I've heard Moto G5 Plus runs on 32-bit architecture, but it failed-- install log told that ARM64 was the correct version for my device)
Wipe cache/dalvik
Install Magisk
Reboot
That's it-- one thing I noticed when restoring my manufacturer rom image was that I needed to issue a *#*# dialer command to get SprintDM to start recognizing the network. When I tried to issue that command in DU and LineageOS, nothing happened.
Following up on my last email
Does anyone know if the ##72786# or *#*#72786#*#* dialer command (which forces a system update to provision data with the carrier) is specific to Sprint or if it's part of Android? The reason I ask is because this command works fine on factory roms but doesn't seem to work on my rooted phones (in addition to the Moto G5 Plus, same thing happens with my wife's super old rooted Moto X with Renegade custom Rom-- but no problem with data on this phone). On stock factory rom, the phone resets and SprintDM provisions the data. On rooted Dirty Unicorns and LineageOS, nothing happens. I wonder if this broken command is related to the "com.android.phone" error I discussed above.
schleima said:
Hi all--
I wonder if you could please help me solve a tricky issue?
Before rooting, phone worked fine. Brand new Moto 5G Plus activated on Sprint network.
After rooting my G5 Plus with a custom rom (Dirty Unicorns), everything worked fine except I lost my LTE signal (Sprint). The phone functions in all other capacities (calls, SMS, wifi). To be clear, the phone is receiving a Sprint signal, but no data LTE/3G is passing through. Phone calls and SMS are fine.
When I go to Settings-Network & Internet-Mobile Network-Advanced-Carrier Settings, I get an error-- "com.android.phone has stopped."
I decided to test with another reliable custom rom so I installed LineageOS 15.1. Same exact problem-- no data, and carrier settings brings up ""com.android.phone has stopped."
Any ideas? I've googled myself to death and I've not found anything that has worked.
Thanks in advance, everyone.
Click to expand...
Click to collapse
A similar thing happened to me. I was rooted with a custom rom(Pixel Experience) but I switched carriers to Boost Mobile and now I have no data and com.android.phone crashes when I try to open carrier settings.