Question No cell service after update to 11.2.4.4AA while keeping root

[elodin_89]

I'll try to keep this short. Global OP9 Pro on 11.2.2.2AA, bootloader unlocked, rooted w/Magisk. Been trying to find the best way to update. Decided on trying this:

1. Un-rooting by going in to Magisk and doing UNINSTALL->RESTORE IMAGES
2. Installing 11.2.4.4AA OTA incremental update from within phone settings (NOT from OxygenUpdater as that did not detect 11.2.4.4AA as available).
3. Did not reboot, went back in to Magisk, did Install to Inactive Slot (after OTA)

The phone booted up and everything was OK, except cell service. Icon in the status bar showed as if there was no SIM card inserted. Tapping on SETTINGS->WIFI & NETWORK->SIM & NETWORK, it did not open and simply immediately brought me back to the WIWI & NETWORK screen. I was able to get cell service back by going in to Magisk and doing step 1 again above, and then rebooting. However, I lost root. Now when I try to root, I lose cell service. When I lose cell server, every few mins there would be a popup saying com.android.phone stopped working and the only two options I had were APP INFO and FORCE STOP. Neither helped, though I noticed that going to APP INFO brought me to the APP INFO page of PHONE SERVICES and not the PHONE app as I was expecting.

I tried to download the 11.2.4.4AA boot images in the thread here by Steve007. I initially tried using (always fastboot boot, not fastboot flash boot) the provided magisk-patched boot image in that thread, but it resulted in the same SIM issue. I then used the stock boot img file and phone booted with SIM working. Copied that boot img to the phone, patched it with Magisk, then booted it (again, fastboot boot), SIM issue again. Booted stock boot img again to regain SIM service. Leaving like this for now as I don't want to wipe the phone and need cell service.

I read somewhere in the forum (after I had tried all of this) that someone said to first disable Magisk modules before proceeding with step 1 of the process I followed, not sure if that would've made a difference. Would love to re-gain root. Any help is much appreciated.

 

[dreinulldrei]

Do you have any modules installed in Magisk? Had the same issue when updating my son's OP6T and had Qualcomm Wifi Bonding module installed. Since this does modify the Wifi driver, I lost Wifi connectivity after an OS update. Solved by uninstalling and reinstalling the module, as this takes the original driver and modifies it. Maybe you have some module that messes with connectivity?

 

[elodin_89]

Do you have any modules installed in Magisk? Had the same issue when updating my son's OP6T and had Qualcomm Wifi Bonding module installed. Since this does modify the Wifi driver, I lost Wifi connectivity after an OS update. Solved by uninstalling and reinstalling the module, as this takes the original driver and modifies it. Maybe you have some module that messes with connectivity?

That must be it then. I had some modules installed, including one that installed the OP apps (contacts, messages, phone) and I believe that one may be the culprit as I had the OP dialer from that module set as the default phone app. Also had riru and a couple other ones. Looking in to removing them now with no root and no magisk. I'll you know how that goes. Thanks for the tip!

 

[dreinulldrei]

No worries, there's a button if my post solved your problem.

 

[elodin_89]

No worries, there's a button if my post solved your problem.

That did it. Not sure which module it was, I uninstalled all of them and will just reinstall them. Attached is a screenshot of what I had installed. I just booted the Magisk patched boot file, with no SIM service I did a direct install, rebooted. Then uninstalled all modules and rebooted. Now rooted and with SIM service back. Thanks for pointing me in the right direction @dreinulldrei!

Also, I assume the button you're referring to is the LIKE button? If so, pressed!

 

[lalo5alvarez]

I had the same issue happen to me. Though I am not rooted yet but am on 11.2.4.4. After an entire day I found this setting and it fixed everything instantly. Maybe give it a shot.
(The first option)

 

[elodin_89]

I had the same issue happen to me. Though I am not rooted yet but am on 11.2.4.4. After an entire day I found this setting and it fixed everything instantly. Maybe give it a shot.
(The first option)

Good to know, thanks. I've resolved it already but I'll keep this in mind for the next time I inevitably f*ck something up!

 

[dreinulldrei]

That did it. Not sure which module it was, I uninstalled all of them and will just reinstall them. Attached is a screenshot of what I had installed. I just booted the Magisk patched boot file, with no SIM service I did a direct install, rebooted. Then uninstalled all modules and rebooted. Now rooted and with SIM service back. Thanks for pointing me in the right direction @dreinulldrei!

Also, I assume the button you're referring to is the LIKE button? If so, pressed!

Thanks.

Yes, one of the mods is the culprit. Not sure which one. Maybe the OP apks, as they relate to the problem you're having. But you can just disable one module at a time, reboot, and see if the problem is solved.

Hint: Always disable ALL Magisk mods when doing a system upgrade. Then see which ones you really need, if they are messing with e.g. Wifi or connectivity, I'd always recommend reinstalling them (as in this case scripts that copy stuff together etc. will use the most recent version) instead of just re-enabling them. Like the Qualcomm module... if you'd simply re-enable it, it'd still load the old Wifi driver which was copied when the module was originially installed.

 

[toolhas4degrees]

That did it. Not sure which module it was, I uninstalled all of them and will just reinstall them. Attached is a screenshot of what I had installed. I just booted the Magisk patched boot file, with no SIM service I did a direct install, rebooted. Then uninstalled all modules and rebooted. Now rooted and with SIM service back. Thanks for pointing me in the right direction @dreinulldrei!

Also, I assume the button you're referring to is the LIKE button? If so, pressed!

You really don't need to uninstall them just disable them. Toggle them off then reboot then take the update

 

[elodin_89]

You really don't need to uninstall them just disable them. Toggle them off then reboot then take the update

Good to know for next time. Thankfully I only had a handul so installing them was quick. I'd also rather just bite the bullet and uninstall all at once and reboot once instead of doing them individually while rebooting between each. Thanks!

 

[dreinulldrei]

You really don't need to uninstall them just disable them. Toggle them off then reboot then take the update

Yeah, but for mods that copy system files during install, once you re-enable them, thex will overlay old system files which were copied from an earlier version and e.g. break wifi connectivity. Hence my recommendation to re-install modules that copy system files during their initial setup. If such venture gues wrong you might end up with e.g. bootloops as a worst case scenario. Remember we don't have TWRP, so repairs that need access to the file system are quite challenging.

 

[galaxys]

Agree, I always uninstall my Magisk modules...

 

[dreinulldrei]

Just in case anyone runs into this issue... Turn off the phone and enter the following into a shell on your computer where the platform tools are installed:

adb wait-for-device shell magisk --remove-modules

Now attach your phone...if it does not turn on by itself, turn it on.

 

[elodin_89]

Just in case anyone runs into this issue... Turn off the phone and enter the following into a shell on your computer where the platform tools are installed:

adb wait-for-device shell magisk --remove-modules

Now attach your phone...if it does not turn on by itself, turn it on.

Yeah, I saw and tried this. FWIW, I think because I had already uninstalled Magisk, it didn't recognize the command or said that the directory didn't exist or something along those lines.

 

[dreinulldrei]

Yes, that is correct. This calls a shell once the device is connected (wait for device) and then runs the command, which is Magisk itself. If this has been deinstalled, there's no chance it can do anything. But of course you won't run into any Magisk related problems if Magisk isn't installed.