Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.
Alternatively is it possible to access the settings of this submenu through a different app or way?
hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen
True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages
Have you got any magisk module active?
estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP
Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:
Is there any risk involved concerning the encryption?
hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.
Stuck with the same issue. Did you manage to get it fixed somehow?
Actually the latest available oo update to 10.3.1 fixed it.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.
You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.
Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though
I recently updated to 10.3.1 from android 9 i was rooted using magisk and edxposed installed so after installing i didn't reboot i went to magisk manager and installed to other slot and rebooted.
Everything's fine but both sim shows emergency calls only so i downloaded offline package and installed it locally. Root is removed and both Sim are working fine but when i go to settings and open Sim & network it says com.android.phone keeps stopping.
I'm unable to send messages and check balance using ussd code. I don't know what to do.
haidermiz said:
I recently updated to 10.3.1 from android 9 i was rooted using magisk and edxposed installed so after installing i didn't reboot i went to magisk manager and installed to other slot and rebooted.
Everything's fine but both sim shows emergency calls only so i downloaded offline package and installed it locally. Root is removed and both Sim are working fine but when i go to settings and open Sim & network it says com.android.phone keeps stopping.
I'm unable to send messages and check balance using ussd code. I don't know what to do.
Click to expand...
Click to collapse
Hello bud,
this is the third time (including me) that I see such a thing.
Here i posted my experience, quite same like yours.
Here how i solved. (see posts below)
Backup all your stuff and good luck.. :fingers-crossed:
Cheers
i have tried updating though the normal way and flashing via twrp and it seems to work fine. reinstall twrp and still works fine.
but after flashing magisk 20.3 i no longer have any kind of connection connection and the sim cards no longer show up.
also.. can i flash the old 10.3.1 update over the newest or am i going to have to reload my backup?
cwtechshiz said:
i have tried updating though the normal way and flashing via twrp and it seems to work fine. reinstall twrp and still works fine.
but after flashing magisk 20.3 i no longer have any kind of connection connection and the sim cards no longer show up.
also.. can i flash the old 10.3.1 update over the newest or am i going to have to reload my backup?
Click to expand...
Click to collapse
EDIT: It was a module i has installed through magisk that was causing the issue..
sorry for posting but i could not find any reason as to why it was happening or find any info on it.
cwtechshiz said:
EDIT: It was a module i has installed through magisk that was causing the issue..
sorry for posting but i could not find any reason as to why it was happening or find any info on it.
Click to expand...
Click to collapse
Which module?
konsolite said:
Which module?
Click to expand...
Click to collapse
Magisk bricked my phone during the same situation
Hello, I've recently installed the newest version of LineageOS17.1 on my beloved S5. I'm using Magisk (latest version) and I tried hiding my root via 1st - changing the package name and 2nd - Magisk Hide. I used to play a lot of Pokemon GO and it was working perfectly fine on LineagesOS 15, back then. Sadly, it's no longer working - this time, however, I'm using my phone not only for Pokemon GO (that inflicts a problem with rooted phones) but also a bank app. It's crucial for me to use the bank app as it has a limit and whenever I'd like to spend >50$, I have to enter a code which is generated on the app only. So, is there a way to properly hide my root?
I'm on LineageOS17.1, with mod for increased speaker volume and custom kernel (Tuned Kernel by fbs).
inc0n3ck said:
Hello, I've recently installed the newest version of LineageOS17.1 on my beloved S5. I'm using Magisk (latest version) and I tried hiding my root via 1st - changing the package name and 2nd - Magisk Hide. I used to play a lot of Pokemon GO and it was working perfectly fine on LineagesOS 15, back then. Sadly, it's no longer working - this time, however, I'm using my phone not only for Pokemon GO (that inflicts a problem with rooted phones) but also a bank app. It's crucial for me to use the bank app as it has a limit and whenever I'd like to spend >50$, I have to enter a code which is generated on the app only. So, is there a way to properly hide my root?
I'm on LineageOS17.1, with mod for increased speaker volume and custom kernel (Tuned Kernel by fbs).
Click to expand...
Click to collapse
Did you try toggling Magisk hide off/on as per Magisk support thread?
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
@Didgeridoohan has a good article on the matter here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Principially Magisk Hide is working in this state and e. g. my banking app was, too.
Other users have full support, but i don't know what's wrong here.
Everything Magisk was special when i tried Los17. Bootlooping after a Magisk update with successful reboot after the umpteenth time.
Endless boot after installation of the Youtube Vanced module. Entering TWRP at boot also was impossible(but you could access Fastboot), but there seemed to be some watchdog timer and after about 30min Twrp came up instead of the os.
Hey everyone, I'm pretty new with ROMs and everything regarding Android, but I've been trying to flash an AOSP ROM, whether official or not, just to get GPAY or my banking app to work on my A20e.
You can download the apps, they run fine, you can add your card and input the SMS code and everything, only problem is at the last step where GPay just gives me a standard error and my banking app gives me a "Digitization not finalized".
I got both GPAY and BTPay (my banking app) to work with the stock rom, so It can't be the card itself.
Has anyone ran into this or managed to fix it?
Have you rooted the device with Magisk? If so, go to the Magisk settings and toggle on 'MagiskHide'
burningcreation said:
Have you rooted the device with Magisk? If so, go to the Magisk settings and toggle on 'MagiskHide'
Click to expand...
Click to collapse
It's not rooted.